CN101083608A - Method for enquiring node information of equipment management tree and its terminal equipment - Google Patents
Method for enquiring node information of equipment management tree and its terminal equipment Download PDFInfo
- Publication number
- CN101083608A CN101083608A CNA2006100784936A CN200610078493A CN101083608A CN 101083608 A CN101083608 A CN 101083608A CN A2006100784936 A CNA2006100784936 A CN A2006100784936A CN 200610078493 A CN200610078493 A CN 200610078493A CN 101083608 A CN101083608 A CN 101083608A
- Authority
- CN
- China
- Prior art keywords
- node
- information
- device management
- terminal equipment
- destination node
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Abstract
The invention discloses a device management tree's node information inquiring method, comprising: device management server issues inquiry request message for inquiring target node related information to terminal device; the terminal device finds the target node related information in the device management tree according to the inquiry request message; and feeds the found target node related information back to the device management server. Correspondingly, the invention discloses a terminal device. And the invention can make device management server reduce over occupation for air interface resources and processing resources of device management server system in the course of obtaining the target node related information.
Description
Technical field
The present invention relates to Open Mobile Alliance (OMA, Open Mobile Alliance) equipment control (DM, Device Management) technical field, especially relate to a kind of querying method and terminal equipment thereof of node information of equipment management tree.
Background technology
Open mobile alliance device management (OMA DM, Open Mobile Alliance DeviceManagement) standard is a kind of management, diagnosis and the technology of safeguarding mobile terminal device, it is by the aerial (OTA that downloads, Over The Air) mode manages terminal equipment, and wherein the bookkeeping to terminal equipment comprises: terminal equipment is carried out parameter setting, firmware update, software installation and upgrade and failure diagnosis etc.Wherein the mobile terminal device managed of OMA DM standard comprises mobile phone terminal, palmtop PC, notebook computer, embedded device and onboard system etc., does not get rid of any other mobile terminal device simultaneously.
As shown in Figure 1, for the holistic management framework model figure of existing DM standard, in this holistic management framework model figure, the equipment control agency (DM Agent) on the terminal equipment is used to explain and carry out the various administration orders that DM Server issues; The DM management tree of storing on the terminal equipment can be considered to the interface that a DMServer manages terminal equipment by the DM agreement, comprise the basic management object (MO of a cover in this DM management tree, Management Object), DM Server reaches by the bookkeeping to each MO in the DM management tree terminal equipment resource is controlled.Wherein the administration order of each MO of DM Server operation DM management tree comprises Get (obtaining order), Replace (replacing order), Exec (fill order), Copy (copy command) and Delete (delete command) etc.
As shown in Figure 2, configuration state schematic diagram for each management object in the management tree in the existing terminal equipment, the DM tree of each terminal equipment must have root node (Root), wherein has the father node of child node to be called internal node, does not have the node of child node to be called leaf node.Each node in the management tree comprises permanent node (permanent nodes) and dynamic node (dynamic nodes), and wherein permanent node is meant the node that DM Server can not generate and delete at run duration; Dynamic node is meant the node that allows DM Server dynamically to generate and delete at run duration.In OMA DM standard, defined the property value of a set of equipment management tree node, be used for each node is described, each property value mainly comprises: the mime type of control of authority tabulation (ACL, Access Control List), type (Type), form (Format), title (Name), size (Size), title (Title), timestamp (TStamp) and nodal value etc.
Correlation technique principle based on above-mentioned OMA DM agreement, if DM Server just manages and can add, delete by the software component management object (SCoMO, Soffware Component Management Object) during DM on the terminal equipment is set and revise to handle to wait and realize the component software of terminal equipment.Wherein executable application programs, dynamic link library and the UI interface etc. that are provided by a plurality of software suppliers can be provided the component software on the terminal equipment.As shown in Figure 3, the DM subtree view of being formed for software component management object in the device management tree, among the figure:
Internal node＜Interior Node〉be the root node of software component management object;
＜Inventory〉below the node storage downloaded or be installed to the component software information on the terminal equipment;
＜Deployed〉below the node storage component software information that is configured on the terminal equipment has been installed;
＜X〉be the placeholder node, this nodal value can be replaced by certain concrete component software relevant information, and the concrete information of child node storage on it is as sign (ID), title (Name) etc.;
＜ID〉node is the identification information of component software;
＜Name〉node is the name information of component software,＜X〉node also has a lot of child nodes, will not introduce in detail here;
＜Download〉below the node storage prepare to download to the component software relevant information of terminal equipment;
＜Ext〉be expanding node, expansion is used after giving over to.
In existing OMA DM standard, if DM Server has known the unified resource sign (URI of certain node in the terminal equipment, Unified Resource Identifier) information, just can be directly issue and obtain order accordingly and obtained the relevant information of this node according to this URI, this mode is called direct obtain manner, for example DM Server obtains the id information of certain software in the terminal equipment, if known the URI of this software node, just can directly issue following order and obtain the id information of this software in the terminal equipment to terminal equipment:
<Get>
<Item>
<Target>
<LocURI>./SCoMO/Inventory/Deployed/Visio?2000/ID</LocURI>
</Target>
</Item>
</Get>
If yet DM Server does not know the URI information of certain node in the terminal equipment, desire to want that this node is carried out obtaining of relevant information handles the structural information (being directory information) that just need at first obtain DM tree in the terminal equipment, and search the URI of this node according to the DM tree structure information of obtaining, and then the relevant information of this node is obtained processing according to this URI information, this mode is called classification and searches obtain manner.For example DM Server can issue following order to obtain the sub-tree structure information at node place to terminal equipment:
GET<URI>？list＝<attribute>
Wherein＜and attribute〉can be Struct, expression DM Server will obtain the structural information of relevant subtree;
＜attribute〉also can be StructData, expression DM Server will obtain the structural information of relevant subtree and the value of all leaf nodes;
＜attribute〉can also be TNDS, expression DM Server will obtain the later correlator tree structure information of serializing;
DM Server is according to the routing information of the required destination node of sub-tree structure information searching that obtains, and the URI information of promptly searching destination node is obtained target node related information according to this URI information again from terminal equipment.
As fully visible, if DM Server adopts classification to search obtain manner when the relevant information of certain node in the terminal equipment is obtained, need at first obtain the structural information of this node place DM subtree, again according to the URI information of this node of sub-tree structure information searching of getting access to, last issuing to terminal equipment according to the URI information of this node more relevant obtained order to search the relevant information of this node.This obtain manner is certainly existing following deficiency in implementation process:
1. if the position of certain node in terminal equipment DM tree is relatively near the lower level node position, just make when DM Server obtains the structural information of this node place subtree in terminal equipment, the amount of information that need obtain is bigger, thereby can occupy the more transfer resource of eating dishes without rice or wine, will cause waste the transfer resource of eating dishes without rice or wine of preciousness;
2.DM Server gets access to the sub-tree structure information at node place from terminal equipment after, also to search the URI information of node according to this structural information, also there is the bigger problem of searching work amount for the bigger situation of sub-tree structure amount of information equally, this will inevitably increase the Processing tasks load of DM Server, the system handles resource of waste DMServer.
Summary of the invention
The present invention proposes a kind of querying method of node information of equipment management tree, searches and can handle the wasting problem of resource to eat dishes without rice or wine transfer resource and device management server systems when obtain manner obtains the URI information of node to solve the available technology adopting classification.
Accordingly, the invention allows for a kind of terminal equipment.
For addressing the above problem, the technical scheme that the present invention proposes is as follows:
A kind of querying method of node information of equipment management tree comprises step:
Device management server issues the inquiry request message that is used for query aim node relevant information to terminal equipment;
Terminal equipment finds target node related information according to inquiry request message in device management tree;
And the destination node relevant information that finds fed back to device management server.
Preferably, described inquiry request message comprises destination node residing query path in device management tree of obtaining order and representing based on asterisk wildcard.
Preferably, described inquiry request message comprises and obtains the residing query path and be used to mate the value of destination node or the conditional expression of property value in device management tree of order, destination node.
Preferably, the residing query path in device management tree of described destination node is represented based on asterisk wildcard.
Preferably, described inquiry request message comprises look-up command.
Preferably, described inquiry request message also comprises destination node residing query path in device management tree of representing based on asterisk wildcard.
Preferably, described inquiry request message also comprises destination node residing query path and be used to mate the value of destination node or the conditional expression of property value in device management tree.
Preferably, the residing query path in device management tree of described destination node is represented based on asterisk wildcard.
Preferably, described target node related information is the unified resource sign of destination node in device management tree.
Preferably, the described terminal equipment process of searching the unified resource sign of destination node specifically comprises:
Terminal equipment is resolved the inquiry request message that receives, and obtains destination node residing query path information in device management tree of representing based on asterisk wildcard; And
Traversal meets the node of query path information one by one, determines the unified resource identification information of destination node in device management tree according to each nodal information that traverses.
Preferably, described method comprises that also terminal equipment judges the step whether search access right of each node traverse is opened to described device management server.
Preferably, the described terminal equipment process of searching the unified resource sign of destination node specifically comprises:
Terminal equipment is resolved the inquiry request message that receives, and obtains destination node residing query path information in device management tree, and is used to mate the value of destination node or the conditional expression of property value;
Terminal equipment travels through the node that meets query path information one by one, determines to meet the node cluster of query path information; And
The value of determining or property value meet the destination node of described conditional expression in the node cluster of determining;
Terminal equipment is determined the unified resource identification information of each destination node that determines in device management tree respectively.
Preferably, described method comprises that also terminal equipment judges the step whether search access right of each node traverse is opened to described device management server.
Preferably, described method comprises that also terminal equipment determines that respectively the value of each destination node that determines or property value are as the destination node relevant information of desiring to report device management server.
Preferably, terminal equipment specifically comprises the process that the destination node relevant information that finds feeds back to device management server:
Terminal equipment requires each destination node of searching according to inquiry request message, and each target node related information that finds is carried out buffer memory; And
Report device management server after each target node related information of buffer memory integrated.
A kind of terminal equipment comprises:
The message sink resolution unit is used to receive and the inquiry request message that is used for query aim node relevant information that issues of analyzing device management server;
Nodal information is searched the unit, is used for resolving according to the message sink resolution unit analysis result of inquiry request message, searches target node related information in device management tree;
Nodal information reports the unit, is used for that nodal information is searched the destination node relevant information that the unit finds and reports device management server.
Preferably, described nodal information is searched the unit and is specifically comprised:
First node traversal subelement, the destination node of representing based on asterisk wildcard that is used for resolving according to the message sink resolution unit that inquiry request message obtains is in the residing query path information of device management tree, and traversal meets the node of query path information one by one;
First node information is determined subelement, is used for traveling through each nodal information that subelement traverses according to first node, determines that the unified resource identification information of destination node in device management tree is as the target node related information that finds.
Preferably, described nodal information is searched the unit and is also comprised:
The first authority judgment sub-unit is used to judge whether the search access right of each node that first node traversal subelement traverses is all opened to described device management server respectively;
Described first node information determine subelement in the judged result of the first authority judgment sub-unit when being, determine the unified resource identification information of destination node in device management tree according to each nodal information that traverses.
Preferably, described nodal information is searched the unit and is specifically comprised:
Section Point traversal subelement, the destination node that is used for obtaining according to message sink resolution unit parsing inquiry request message is in the residing query path information of device management tree, traversal meets the node of query path information one by one, determines to meet the node cluster of query path information;
The condition distinguishing subelement, be used for being used to mate the value of destination node or the conditional expression of property value according to what the message sink resolution unit resolved that inquiry request message obtains, the value of determining or property value meet the destination node of described conditional expression in the node cluster that Section Point traversal subelement is determined;
Section Point information is determined subelement, be used for respectively determining each destination node that the condition distinguishing subelement determines at the unified resource identification information of device management tree as the target node related information that finds.
Preferably, described nodal information is searched the unit and is also comprised:
The second authority judgment sub-unit is used to judge whether the search access right of each node that Section Point traversal subelement traverses is all opened to described device management server respectively;
Described Section Point traversal subelement when being, meets the node of query path information by traversal in the judged result of the second authority judgment sub-unit, determines to meet the node cluster of query path information.
Preferably, described nodal information is searched the unit and is comprised that also the 3rd nodal information determines subelement, is used for determining respectively that the value of each destination node that the condition distinguishing subelement determines or property value are as the target node related information that finds.
Preferably, described nodal information reports the unit specifically to comprise:
The buffer memory subelement is used for each target node related information that cache node information searching unit finds;
The information integrated subelement that reports reports device management server after being used for each target node related information of buffer memory subelement buffer memory integrated.
The beneficial effect that the present invention can reach is as follows:
Technical solution of the present invention is by increasing the search access right to terminal equipment DM tree interdependent node for DM Server, thereby realized that DM Server is not when knowing the URI information of interdependent node, can use the URI information of search access right realization to destination node, and the value of destination node or property value carry out tape spare and search, thereby avoided that DM Server is a URI information of obtaining node in the prior art, the whole DM sub-tree structure at node place all need be obtained award again definite, thereby reduced Network Transmission pressure, saved the transfer resource of eating dishes without rice or wine, also reduce simultaneously DM Server required processing resource in the URI information process of determining node, reduced the processing load of DM Server.
Description of drawings
Fig. 1 is the holistic management framework model figure of existing DM standard;
Fig. 2 is the configuration state schematic diagram of each management object in the management tree in the existing terminal equipment;
The DM subtree view that Fig. 3 is formed for software component management object in the device management tree;
Fig. 4 is the main realization principle flow chart of the querying method of present device management tree nodal information;
Fig. 5 be one based on the nested equipment control tree structure diagram of asterisk wildcard;
Fig. 6 is the subtree view of software component management object in the embodiment of the invention;
Fig. 7 is the main composition structured flowchart of terminal equipment of the present invention;
First embodiment that Fig. 8 searches the unit for nodal information in the terminal equipment of the present invention forms structured flowchart;
Second embodiment that Fig. 9 searches the unit for nodal information in the terminal equipment of the present invention forms structured flowchart;
Figure 10 reports the concrete composition structured flowchart of unit for nodal information in the terminal equipment of the present invention;
Figure 11 carries out mutual schematic diagram for the main composition structure of terminal equipment of the present invention and with DM Server.
Embodiment
Technical solution of the present invention at DM Server in the prior art when not knowing the URI information of node, adopt classification to search the relevant information that obtain manner obtains node and can waste eat dishes without rice or wine transfer resource and DM Server inter-process problem of resource, proposition in existing OMA DM standard, make DM Server have terminal equipment in the query function of interdependent node information on the DM tree, even DM Server has the query manipulation authority to the DM tree, and in ACL information, increase the search access right of corresponding DMServer respectively for each node maintenance of DM tree, thereby can realize that DM Server can not know under the URI situation of node, use the interdependent node information to the DM tree of search access right realization tape spare to inquire about, avoid DM Server when knowing the URI information of node, the total information of the DM subtree at node place all need not obtained the URI information processing of determining node again with this, therefore can reach and save the purpose of transfer resource of eating dishes without rice or wine, and make DM Server can reduce the consumption of inter-process resource.
Be explained in detail to the main realization principle of technical solution of the present invention, embodiment and to the beneficial effect that should be able to reach below in conjunction with each accompanying drawing.
As shown in Figure 4, be the main realization principle flow chart of the querying method of present device management tree nodal information, its main implementation procedure is as follows:
Step S10, in the DM system, DM Server issues the inquiry request message that is used for query aim node relevant information to terminal equipment; Wherein in order to realize this purpose, need on the operating right basis of existing DM Server operation terminal device DM tree, increase search access right, and and then in the ACL information of setting each node maintenance for DM, increase the search access right information of the DM Server that is correlated with;
Step S20, terminal equipment finds target node related information according to inquiry request message in the DM tree;
Step S30, terminal equipment feeds back to DM Server with the above-mentioned destination node relevant information that finds, thereby realize making DM Server directly in the DM of terminal equipment tree, to find the relevant information of corresponding node based on inquiry request message, carry out determining of node relevant information again and need not again the total information of respective nodes place subtree all to be obtained, reached the purpose of saving eat dishes without rice or wine transfer resource and DM Server system handles resource.
Wherein in above-mentioned steps S10, DM Server can be according to the title of the structural information of DM tree, the destination node that will search or attribute information etc., sends to be used to inquire about the inquiry request message of this destination node relevant information to terminal equipment.
Wherein the inquiry request message that issues of DM Server can comprise destination node residing query path information in the DM tree of obtaining order (Get order) and representing based on asterisk wildcard, wherein asterisk wildcard can be used for substituting the part routing information of DM tree, as the name information that substitutes placeholder node or substitute node etc., be used for DM Server and when whole routing informations of not knowing destination node or name information, carry out fuzzy search in the DM tree, promptly can use asterisk wildcard to come unknown routing information of part in the replacement query path or the unknown character information in the nodename etc., basic asterisk wildcard has following three kinds:
1) "? " alternative single character;
2) " * " alternative any character;
3) any single character in the alternative charset character set of square brackets " [charset] ".
For example in inquiry request message, can use asterisk wildcard to substitute the placeholder node, obtain certain leaf node under all placeholder nodes with expression.
The occupation mode of asterisk wildcard also can be nested in addition, as shown in Figure 5, be one based on the nested equipment control tree structure diagram of asterisk wildcard, in the figure, if DM Server prepares to obtain all service names under the Proxy port in the DM tree, just can issue following inquiry request message to terminal equipment:
<Get>
<Item>
<Target>
<LocURI>./Proxy/Port/*/Services/*/Service?Name</LocURI>
</Target>
</Item>
</Get>
Because in OMA DM technology, DM Server generally only knows the DM tree structure on the terminal equipment, and placeholder node＜X〉the concrete nodename DM Server that refers to is normally ignorant, DMServer wants to obtain placeholder node＜X like this〉relevant information of bottom leaf node will be very difficult, replaces these placeholder nodes then very convenient with asterisk wildcard.After terminal equipment receives above-mentioned inquiry request message like this, all service names under all of the port will be returned to DM Server.
In addition, the inquiry request message that DM Server issues can also comprise look-up command (Search order), and then comprising destination node residing query path information in the DM tree of representing based on asterisk wildcard, the Search order can be used for DM Server and when knowing the routing information of destination node destination node do not carried out by the name access.Search order operating right wherein,＜Search for increasing newly on the operating right basis that DM Server can carry out terminal equipment in existing OMA DM standard〉being defined as follows of order:
<！ELEMENT?Search(CmdID，NoResp？，NoResults？，Cred？，Target？，Source+，Item+，Meta，Data)>
Wherein＜and Target〉element is used in reference to the mark node residing query path in DM tree that makes eye bright, if when not knowing the query path information of destination node fully, can indicate root node, inquire about to show under the root node of DM tree;
＜Data〉element is used to indicate the destination node relevant information that will search;
＜Meta〉element is used to indicate＜Data〉information such as classification of element, form, wherein classification mainly contains the value or the property value of destination node;
If search the property value or the value of destination node, can be at＜Type〉the lining definition, the value of searching node as using Node-value to indicate, use＜attribute 〉-value indicates to search the property value of node, such as can come that express time stabs with TStamp-value, Size-value, Name-value, the value of size, title.
If the inquiry request message that DM Server issues is based on above-mentioned situation, be that inquiry request message comprises Get order (or Search order) and the partial query routing information of destination node in the DM tree of representing based on asterisk wildcard, then terminal equipment is after receiving inquiry request message, can inquire the actual URI information of destination node in the DM tree based on inquiry request message, and give DM Server with the URI feedback information of the destination node that inquires, the URI information that DM Server just can the based target node specific object information further using Get to order to obtain this destination node or occurrence like this.Wherein the inquiry request message that issues according to DMServer of terminal equipment search the detailed process of the URI information of destination node can be as follows:
1, terminal equipment is resolved the inquiry request message that receives, and obtains destination node residing query path information in the DM tree of representing based on asterisk wildcard;
2, terminal equipment travels through each node that meets query path information one by one, and when traversing each node, according to this node ACL information that traverses, judge whether the search access right of the node that this traverses is opened to this DM Server, only under open situation, just can travel through next node, otherwise just can not normally carry out inquiry request message, terminal equipment is determined the actual URI information of destination node in the DM tree according to each nodal information that traverses like this.
Another situation is that inquiry request message that DM Server issues can comprise Get order (or Search order), destination node residing query path information and be used to mate the value of destination node or the conditional expression of property value in the DM tree; Destination node wherein described here residing query path information in the DM tree can be Actual path information complete or part, also can be based on the part or all of query path information that asterisk wildcard is represented.
Wherein conditional expression mainly is the destination node that is used to mate eligible value or eligible property value.Usually the attribute of each node mainly comprises following several aspect in the DM tree: control of authority tabulation (ACL), type (Type), form (Format), title (Name), size (Size), title (Title), timestamp (TStamp) etc., wherein the attribute information that can compare mainly contains time, size or character string etc., so conditional expression relates generally to these aspects.
Can come the desired condition of expression condition expression formula based on symbol, such as＞,＜,＞=,＜=,!=,==, |, ﹠amp; Deng, the concrete implication of its each symbol is as shown in the table:
| ＞ | ＜ | ＞＝ | ＜＝ | ！＝ | ＝＝ | ‖ | && | @ |
| Greater than | Less than | More than or equal to | Be less than or equal to | Be not equal to | Equal | Or | With | Comprise |
Can certainly use the CGI grammer to represent above-mentioned each symbol, shown in the table specific as follows:
| > | < | &GE | &LE | &NE | &EQ | &OR | &AND | &CON |
| Greater than | Less than | More than or equal to | Be less than or equal to | Be not equal to | Equal | Or | With | Comprise |
For conditional expression, can use following two kinds of forms to realize:
1) conditional expression is nested among the URI
If what conditional expression was used to mate is node attribute values, then can use following form:
<URI>？prop＝<attribute><condition><value>；
Wherein＜and URI〉represent that the unified resource of node identifies;
The beginning of expression conditional expression;
Prop=＜attribute〉expression node attribute;
＜condition〉be conditional code,＜value〉refer to be used for the property value of comparison.
For example DM Server desires to want to obtain on the terminal equipment nearest week downloaded software information, just can use as issuing orders:
<Get>
<Item>
<Target>
<LocURI>./SCoMO/Inventory/Deployed/*/ID？prop＝TStamp>；2006
0316T000000Z</LocURI>
</Target>
</Item>
</Get>
Will obtain the software I D that generates on the terminal equipment to show after 00: 00: 00 on the 16th March in 2006 on the DM tree, terminal equipment can return corresponding node URI information and node attribute values after receiving this request message.
If what conditional expression was used for comparison is nodal value, then can use following form:
<URI>？Value<condition><value>
Desiring to want to obtain the ID that has disposed on the terminal equipment such as DM Server is the software of Word, just can use as issuing orders:
<Get>
<Item>
<Target>
<LocURI>./SCoMO/Inventory/Deployed/*/ID？Value＝＝Word</LocURI>
</Target>
</Item>
</Get>
2) by using the SyncML label to be used for the storage condition expression formula
Typically can use＜Data label comes the storage condition expression formula, label the inside use＜attribute〉＜condition〉＜value〉form represents conditional expression, wherein＜attribute the expression node attribute,＜condition〉be conditional code,＜value〉refer to be used for the property value of comparison.If what specifically compare is nodal value,＜attribute〉can use Value; If what specifically compare is property value,＜attribute〉can be specific object, such as being Name, Size or TStamp etc.
For example DM Server desires to want to obtain on the terminal equipment nearest week downloaded software information, just can use as issuing orders:
<Get>
<Item>
<Target>
<LocURI>./SCoMO/Inventory/Deployed/*/ID</LocURI>
</Target>
<Data>Tstamp>；20060316T000000Z</Data>
</Item>
</Get>
Wherein＜and Data〉label the inside comprised conditional expression, terminal equipment is after receiving this request message like this, will filter out ineligible node, and, also can and then the value or the property value of qualified node be returned to DM Server with the URI information of qualified node.
Similarly, if conditional expression specifically is used for comparison is the value of node, just can using form Value＜condition〉＜value〉come the expression condition expression formula.
For example DM Server is if will to obtain the ID that has disposed on the terminal equipment be the software information of Word, just can use followingly to obtain order and ask:
<Get>
<Item>
<Target>
<LocURI>./SCoMO/Inventory/Deployed/*/ID</LocURI>
</Target>
<Data>Value&EQ；Word</Data>
</Item>
</Get>
Here it should be noted that some attribute,, then can not the service condition expression formula compare do not have the Size attribute, then can not use the Size attribute as Rule of judgment such as internal node if can't compare for node.
Certainly can also use logical connector to connect a plurality of conditional expressions, such as can Shi Yong ﹠amp; OR represent or relation, use ﹠amp; AND represent and relation, for example if will be illustrated on March 1st, 2006, just can use following conditional expression to represent to the timestamp information between 1 day April in 2006:
TStamp>；20060301T000000Z&AND；TStamp<；20060401T000000Z。
Because asterisk wildcard can be used to limit query path and realizes fuzzy search, as asterisk wildcard being used in＜URI〉in can limit query path, and be used in＜Data in can realize fuzzy search.Like this asterisk wildcard and conditional expression are used in combination and find destination node relevant information more targetedly.Desire to want to search on the terminal equipment software I D information to configuration between 1 day April in 2006 such as DMServer, just can use following look-up command to ask on March 1st, 2006:
<Search>
<Item>
<Target>
<LocURI>./ScoMO/Inventory/Deployed/*/ID</LocURI>
</Target>
<Data>Tstamp>；20060301T000000Z&AND；TStamp<；20060401T
000000Z</Data>
</Item>
</Search>
If the inquiry request message that DM Server issues is based on above-mentioned situation, be inquiry request message comprise Get order (or Search order) and the destination node represented based on asterisk wildcard in the DM tree the partial query routing information and the conditional expression that is used to mate destination node value or property value, then terminal equipment is after receiving inquiry request message, can inquire the actual URI information of destination node in the DM tree based on inquiry request message, further can also inquire the correlation or the correlation attribute value of destination node, and the URI information of the destination node that inquires and the value or the property value of destination node are fed back to DM Server.The inquiry request message that issues according to DM Server of the terminal equipment URI information of searching destination node wherein, further the detailed process of the value of query aim node or property value can be as follows:
1, terminal equipment is resolved the inquiry request message that receives, obtain destination node residing query path information in the DM tree and (may be based on the part or all of query path information that asterisk wildcard is represented, also may be actual part or all of query path information), and be used to mate the value of destination node or the conditional expression of property value;
2, terminal equipment travels through the node that meets query path information one by one, and when traversing each node, according to this node ACL information that traverses, judge whether the search access right of the node that this traverses is opened to this DMServer, only under open situation, just can travel through next node, otherwise just can not normally carry out inquiry request message, traversal determines respectively to meet the node cluster of query path information so successively;
3, terminal equipment is according to the conditional expression in the inquiry request message, and further the value of determining or property value meet the destination node of this conditional expression in the above-mentioned node cluster of having determined;
4, terminal equipment is determined the URI information of above-mentioned each destination node that determines in the DM tree respectively, and further terminal equipment can also be determined the occurrence or the specific object value of above-mentioned each destination node that determines respectively.
This query script with terminal equipment carries out more detailed elaboration by following argumentation below:
Terminal equipment receives the inquiry request message that DM Server issues, in this process, if the user selects to abandon or refuse inquiry request message, perhaps terminal equipment itself is not just supported this inquiry request message, or the inquiry request message form is not right, or inquiry request message do not allow to be performed etc., and in these cases, this inquiry request message all will be ended;
Terminal equipment is resolved the inquiry request message that receives, and determines search space and extracts querying condition, and inquiry wherein involved in the present invention is limited inquiry, and promptly search space is limited, adopts any exhaust algorithm can both finish this query task; And query object is static, can progressively not generate in query script, and promptly search space belongs to static space.Management object is generally pressed the management tree structural arrangement, or presses document directory structure and arrange, and is the target subtree between inquiry extremely like this.
In technical solution of the present invention, DM Server generally only knows the partial information of destination node, such as the part URI information of destination node, only knows promptly which management subtree destination node is positioned at, and does not know the concrete URI information of destination node; Or know the part attribute information of destination node, such as size, timestamp information etc., these information also can be used as querying condition and are included in the query requests;
Terminal equipment is in the inquiry request message process that parsing receives, and the complicated query conditional expression need be split becomes simple one by one conditional expression.
Terminal equipment is at first checked the root node on the relevant DM subtree in the search space that parsing obtains, judge whether DM Server has the Get authority or the Search authority of this DM subtree; If the query path of this subtree is represented with asterisk wildcard, then to carry out authority to each node that asterisk wildcard substituted and judge; If what inquired about is leaf node, then judge according to the ACL of node whether DM Server has the authority that its value or property value are conducted interviews; If judge DM Server certain node is not had search access right, then the child node of this node and this node thereof all will be omitted, and terminal equipment continues the brotgher of node of this node is carried out subsequent query.For example the ACL information of certain node is:
Get＝*&Replace＝ServerA&Delete＝ServerA
Represent that then any DM Server can carry out query processing to this node.
Terminal equipment obtains above-mentioned nodal value that inquires or node attribute values successively, and according to querying condition nodal value or node attribute values is judged coupling, obtains meeting each node of querying condition.
Above-mentioned exhaustive for search space has degree of depth traversal queries, range traversal queries, cost traversal queries, forward direction inquiry, the back is to inquiry, bidirectional inquiry or mix inquiry etc. on algorithm; Such as one tree is being carried out in the query script, can use degree of depth traversal queries algorithm, promptly earlier its first stalk tree is inquired about, wherein each leaf node is carried out condition judgment, after judgement is finished, need date back to source node, again its second stalk tree be inquired about, judges, mates, till each the subtree traversal in this tree is finished.
If wherein terminal equipment successively can find a plurality of target node related information at the inquiry request message that DM Server issues, can earlier each target node related information that finds be carried out buffer memory, at last each target node related information of buffer memory be carried out reporting DM Server after the integration processing.Wherein the destination node relevant information that reports of terminal equipment comprises the complete URI information of each destination node, and can comprise for the property value or the value of each destination node, also can not comprise; DM Server and then the complete URI information that can report according to terminal equipment issue occurrence or specific object value that destination node is obtained in relevant Get order again.
The execution result situation of the inquiry request message that terminal equipment can issue according to concrete execution DM Server, by returning the implementation status of different codes with the expression information order, specific as follows:
To enumerate a specific embodiment below is explained in detail the specific implementation process of the nodal information querying method of DM of the present invention tree.As shown in Figure 6, subtree view for software component management object in the embodiment of the invention, with this figure is example, if DM Server desired to want to search the software I D information that disposes on the terminal equipment during March 1 to 1 day April in 2006 in 2006, its detailed acquisition process can be as follows:
1, DM Server issues inquiry request message and gives terminal equipment
Suppose that DM Server has known the DM tree structure information on the terminal equipment, can limit the path is ./ScoMO/Inventory/Deployed/*/ID, dwindling query context, and the timestamp information of hypothesis known target node, can be with timestamp information as conditional expression.
According to above-mentioned these information, DM Server can be handed down to terminal equipment with following inquiry request command:
<Search>
<Item>
<Target>
<LocURI>./ScoMO/Inventory/Deployed/*/ID</LocURI>
</Target>
<Data>Tstamp>；20060301T000000Z&AND；TStamp<；20060401T000
000Z</Data>
</Item>
</Search>
In above-mentioned inquiry request command, asterisk wildcard * is used to limit query path,＜Data〉in the querying condition expression formula has been described,＜Search the order be look-up command.
2, terminal equipment is resolved the inquiry request command that DM Server issues, to determine search space and to obtain querying condition;
Search space is the Deployed subtree, be that terminal equipment need be inquired about all child nodes under the Deployed node, and the ID grandson's node under the inquiry child node, terminal equipment can decompose querying condition, resolve into two conditions, be about to timestamp greater than on March 1st, 2006 as a querying condition, with timestamp less than on April 1st, 2006 as another querying condition, and require these two querying conditions to satisfy simultaneously.
3, terminal equipment is judged the search access right of each relevant inquiring node in query script, need obtain the ACL of Deployed node as terminal equipment, sees whether DM ServerA has the Search authority to this node.If ACL such as the Deployed node:
Get＝*&Search＝ServerA&Replace＝ServerA
Show that then ServerA has the Search authority to the child node under the Deployed node; But this does not also mean that ServerA also has search access right to grandson's node of Deployed node, also needs to judge the search access right of ServerA to its grandson's node according to the ACL of its child node.If ACL such as 3 nodes of the Microsoft under the Deployed:
Get＝*&Replace＝ServerA
Which Server then shows does not have have Search authority to the child node under this Microsoft 3 nodes; So natural ServerA also will have no right to inquire about this node, and all child nodes under this node will be omitted in this query script.And for leaf node, terminal equipment will obtain its value and property value, then needs to judge according to its ACL information whether Server has the Get authority of this node.
4, terminal equipment each node under the access destination subtree successively, and obtain the value or the property value of node, according to querying condition the value or the property value of each node are judged coupling simultaneously, find the destination node that meets querying condition.
In query script to the target subtree, can use degree of depth traversal queries algorithm, promptly travel through a sub-tree node earlier, travel through the brotgher of node again.Such as to sub-tree structure shown in Figure 6, at first inquire about all nodes under the Microsoft1 node, such as ID node, Name node etc.,, preferentially inquire about its child node if the ID node also has child node down, visit again the Name node.After all querying nodes under Microsoft 1 node are finished, inquire about Microsoft 2 nodes and child node thereof again.
Algorithm to above-mentioned query script uses pseudo-code to be described as follows:
Function (RootNode) // visit one stalk tree
{
If (JudgeACL (ServerID, RootNode)==True) // decision node ACL authority
{
Time=GetTimeAttribute (RootNode); // obtain the time attribute of node
If (Compare (Time, Condition)==True) // comparison time attribute information
Store(URI)；
Function (RootNode-〉ChildNode); // recurrence is visited other child nodes
}
}
MainFunction()
{
RootNode=Deployed; // to the root node assignment
while(RootNode！＝Null)
{
Function (RootNode); // preferentially travel through a stalk to set
RootNode=GetBrotherNode (RootNode); // travel through its subtree brotgher of node again
}
...
}
For example in the present embodiment, terminal equipment is at first visited ./ScoMO/Inventory/Deployed/Microsoft 1/ID node, inquires about its Tstamp property value, is Tstamp﹠amp such as its value; EQ; 20060306T000000Z, terminal equipment judge it according to querying condition, if judged result for satisfying querying condition, is then noted the URI information of this node;
Then, terminal equipment visits again ./ScoMO/Inventory/Deployed/Microsoft 2/ID node, inquires about its Tstamp property value, through after the judgement of querying condition, also meets querying condition, then the URI information of this node is also noted;
Next, terminal equipment visit ./ScoMO/Inventory/Deployed/Microsoft 3/ID node finds that Server does not have the access rights to its node;
Last terminal equipment visit ./ScoMO/Inventory/Deployed/Microsoft 4/ID node finds that its Tstamp property value does not satisfy querying condition; So far inquiry finishes terminal equipment to the Deployed subtree.
5, terminal equipment carries out integration processing to each Query Result successively, and the Query Result information after the integration processing is returned to DM Server; The qualified software that finds such as terminal equipment has Word, Excel, and the form of message below then the object information that finds can being used returns to DM Server:
<Results>
...
<Item>
<Target>
<LocURI>./SCOMO/Inventory/Deployed/Microsoft?1/ID</LocURI>
</Target>
<Meta>
<Format?xmlns＝’syncml:metinf’>Chr</Format>
<Type?xmlns＝’syncml:metinf’>text/plain</Type>
</Meta>
<Data>Word</Data>
</Item>
<Item>
<Target>
<LocURI>./SCOMO/Inventory/Deployed/Microsoft?2/ID</LocURI>
</Target>
<Meta>
<Format?xmlns＝’syncml:metinf’>Chr</Format>
<Type?xmlns＝’syncml:metinf’>text/plain</Type>
</Meta>
<Data>Excel</Data>
</Item>
</Results>
6, after DM Server receives the above-mentioned information of terminal equipment feedback, if think further to obtain the concrete timestamp information that ID is the software of Word, just the ID that can return according to terminal equipment is the URI information of the node of Word, issues following Get order and obtains:
<Get>
<Item>
<Target>
<LocURI>
./SCOMO/Inventory/Deployed/Microsoft?1/ID？prop＝Tstamp
</LocURI>
</Target>
</Item>
</Get>
7, terminal equipment obtains the timestamp information that ID is the node of Word, and the timestamp information that gets access to is fed back to DM Server according to the Get order that DM Server issues:
<Results>
<Item>
<Target>
<LocURI>
./SCOMO/Inventory/Deployed/Microsoft?1/ID？prop＝Tstamp
</LocURI>
</Target>
<Meta>
<Format?xmlns＝’syncml:metinf’>time</Format>
<Type?xmlns＝’syncml:metinf’>MIME</Type>
</Meta>
<Data>20060306T000000Z</Data>
</Item>
</Results>
This shows, technical solution of the present invention is by increasing the search access right to terminal equipment DM tree interdependent node for DM Server, thereby realized that DM Server is not when knowing the URI information of interdependent node, can use the URI information of search access right realization to destination node, and the value of destination node or property value carry out tape spare and search, thereby avoided that DM Server is a URI information of obtaining node in the prior art, the whole DM sub-tree structure at node place all need be obtained award again definite, thereby reduced Network Transmission pressure, saved the transfer resource of eating dishes without rice or wine, also reduce simultaneously DM Server required processing resource in the URI information process of determining node, reduced the processing load of DM Server.
Querying method corresponding to the DM tree node information of the above-mentioned proposition of the present invention, the proposition that the present invention is also corresponding here a kind of terminal equipment, as shown in Figure 7, main composition structured flowchart for terminal equipment of the present invention, it comprises that mainly message sink resolution unit 10, nodal information are searched unit 20 and nodal information reports unit 30, and wherein the concrete effect of each component units is as follows:
Message sink resolution unit 10 is used to receive and resolve the inquiry request message that is used for query aim node relevant information that DM Server issues;
Nodal information is searched unit 20, is used for resolving according to message sink resolution unit 10 analysis result of inquiry request message, searches target node related information in the DM tree;
Nodal information reports unit 30, is used for that nodal information is searched the destination node relevant information that unit 20 finds and reports DM Server.
As shown in Figure 8, first embodiment that searches the unit for nodal information in the terminal equipment of the present invention forms structured flowchart, wherein nodal information is searched the unit and is comprised that mainly first node traversal subelement 210, the first authority judgment sub-unit 220 and first node information determines subelement 230, and wherein the concrete effect of each component units is as follows:
First node traversal subelement 210, the destination node of representing based on asterisk wildcard that is used for resolving according to message sink resolution unit 10 that inquiry request messages obtain is in the residing query path information of DM tree, and traversal meets each node of query path information one by one;
The first authority judgment sub-unit 220 is used to judge whether the search access right of each node that first node traversal subelement 210 traverses is all opened to DM Server respectively;
First node information is determined subelement 230, is used in the judged result of the first authority judgment sub-unit 220 according to each nodal information that first node traversal subelement 210 traverses, determining the relevant information of destination node in the DM tree when being.
As shown in Figure 9, second embodiment that searches the unit for nodal information in the terminal equipment of the present invention forms structured flowchart, wherein nodal information is searched the unit and is comprised that mainly Section Point traversal subelement 240, the second authority judgment sub-unit 250, condition distinguishing subelement 260, Section Point information determines that subelement 270 and the 3rd nodal information determine subelement 280, and wherein the main effect of each part is as follows:
Section Point traversal subelement 240, the destination node that is used for obtaining according to message sink resolution unit 10 parsing inquiry request messages is in the residing query path information of DM tree, traversal meets each node of query path information one by one, determines to meet the node cluster of query path information;
The second authority judgment sub-unit 250, whether the search access right that is used to judge each node that Section Point traversal subelement 240 traverses is all opened to DM Server respectively, wherein Section Point traversal subelement 250 only in the judged result of the second authority judgment sub-unit 250 when being, the node that ability meets query path information by traversal determines to meet the node cluster of query path information;
Condition distinguishing subelement 260, be used for being used to mate the value of destination node or the conditional expression of property value according to what message sink resolution unit 10 resolved that inquiry request messages obtain, the value of determining or property value meet the destination node of this conditional expression in the node cluster that Section Point traversal subelement 240 is determined;
Section Point information is determined subelement 270, is used for respectively determining each destination node that condition distinguishing subelement 260 determines URI information in the DM tree, with as the destination node relevant information that finds;
The 3rd nodal information is determined subelement 280, and the value or the property value of each destination node that is used for respectively determining that condition distinguishing subelement 260 determines are with as the destination node relevant information that finds.
As shown in figure 10, for nodal information in the terminal equipment of the present invention reports the concrete composition structured flowchart of unit, wherein nodal information reports the unit specifically to comprise buffer memory subelement 310 and the information integrated subelement 320 that reports, and the concrete effect of these two component units is as follows:
Buffer memory subelement 310 is used for each target node related information that cache node information searching unit 20 finds;
The information integrated subelement 320 that reports is used for each target node related information of buffer memory subelement 310 buffer memorys is carried out reporting DM Server after the integration processing.
Wherein the combination of above-mentioned each functional unit in the terminal equipment of the present invention can be referred to as the inquiry proxy (Search Agent) of terminal equipment, so the main composition structure of terminal equipment and and DM Server carry out mutual block diagram just as shown in figure 11, wherein DM Server is responsible for by the DM agreement terminal equipment being carried out equipment control, as management such as software download, parameter configuration, diagnosis monitoring.Mainly comprise parts such as bottom firmware, DM agency, inquiry proxy on the terminal equipment, also have device management tree.Wherein the DM agency is responsible for carrying out alternately with DM Server, is used to receive, resolve and carry out each administration order that DM Server issues.Inquiry proxy is responsible for handling the query requests from DM Server, carries out the localization process of destination node, and it is a logic entity, can serve as by the DM agency, and also can be external function entity for the DM proxy call.
Obviously, those skilled in the art can carry out various changes and modification to the present invention and not break away from the spirit and scope of the present invention.Like this, if of the present invention these are revised and modification belongs within the scope of claim of the present invention and equivalent technologies thereof, then the present invention also is intended to comprise these changes and modification interior.
Claims (23)
1, a kind of querying method of node information of equipment management tree is characterized in that, comprises step:
Device management server issues the inquiry request message that is used for query aim node relevant information to terminal equipment;
Terminal equipment finds target node related information according to inquiry request message in device management tree;
And the destination node relevant information that finds fed back to device management server.
2, the method for claim 1 is characterized in that, described inquiry request message comprises destination node residing query path in device management tree of obtaining order and representing based on asterisk wildcard.
3, the method for claim 1 is characterized in that, described inquiry request message comprises and obtains the residing query path and be used to mate the value of destination node or the conditional expression of property value in device management tree of order, destination node.
4, method as claimed in claim 3 is characterized in that, the residing query path in device management tree of described destination node is represented based on asterisk wildcard.
5, the method for claim 1 is characterized in that, described inquiry request message comprises look-up command.
6, method as claimed in claim 5 is characterized in that, described inquiry request message also comprises destination node residing query path in device management tree of representing based on asterisk wildcard.
7, method as claimed in claim 5 is characterized in that, described inquiry request message also comprises destination node residing query path and be used to mate the value of destination node or the conditional expression of property value in device management tree.
8, method as claimed in claim 7 is characterized in that, the residing query path in device management tree of described destination node is represented based on asterisk wildcard.
As claim 2 or 6 described methods, it is characterized in that 9, described target node related information is the unified resource sign of destination node in device management tree.
10, method as claimed in claim 9 is characterized in that, the process that described terminal equipment is searched the unified resource sign of destination node specifically comprises:
Terminal equipment is resolved the inquiry request message that receives, and obtains destination node residing query path information in device management tree of representing based on asterisk wildcard; And
Traversal meets the node of query path information one by one, determines the unified resource identification information of destination node in device management tree according to each nodal information that traverses.
11, method as claimed in claim 10 is characterized in that, comprises that also terminal equipment judges the step whether search access right of each node traverse is opened to described device management server.
As claim 3,4,7 or 8 described methods, it is characterized in that 12, described target node related information is the unified resource sign of destination node in device management tree.
13, method as claimed in claim 12 is characterized in that, the process that described terminal equipment is searched the unified resource sign of destination node specifically comprises:
Terminal equipment is resolved the inquiry request message that receives, and obtains destination node residing query path information in device management tree, and is used to mate the value of destination node or the conditional expression of property value;
Terminal equipment travels through the node that meets query path information one by one, determines to meet the node cluster of query path information; And
The value of determining or property value meet the destination node of described conditional expression in the node cluster of determining;
Terminal equipment is determined the unified resource identification information of each destination node that determines in device management tree respectively.
14, method as claimed in claim 13 is characterized in that, comprises that also terminal equipment judges the step whether search access right of each node traverse is opened to described device management server.
15, method as claimed in claim 13 is characterized in that, comprises that also terminal equipment determines that respectively the value of each destination node that determines or property value are as the destination node relevant information of desiring to report device management server.
16, the method for claim 1 is characterized in that, terminal equipment specifically comprises the process that the destination node relevant information that finds feeds back to device management server:
Terminal equipment requires each destination node of searching according to inquiry request message, and each target node related information that finds is carried out buffer memory; And
Report device management server after each target node related information of buffer memory integrated.
17, a kind of terminal equipment is characterized in that, comprising:
The message sink resolution unit is used to receive and the inquiry request message that is used for query aim node relevant information that issues of analyzing device management server;
Nodal information is searched the unit, is used for resolving according to the message sink resolution unit analysis result of inquiry request message, searches target node related information in device management tree;
Nodal information reports the unit, is used for that nodal information is searched the destination node relevant information that the unit finds and reports device management server.
18, terminal equipment as claimed in claim 17 is characterized in that, described nodal information is searched the unit and specifically comprised:
First node traversal subelement, the destination node of representing based on asterisk wildcard that is used for resolving according to the message sink resolution unit that inquiry request message obtains is in the residing query path information of device management tree, and traversal meets the node of query path information one by one;
First node information is determined subelement, is used for traveling through each nodal information that subelement traverses according to first node, determines that the unified resource identification information of destination node in device management tree is as the target node related information that finds.
19, terminal equipment as claimed in claim 18 is characterized in that, described nodal information is searched the unit and also comprised:
The first authority judgment sub-unit is used to judge whether the search access right of each node that first node traversal subelement traverses is all opened to described device management server respectively;
Described first node information determine subelement in the judged result of the first authority judgment sub-unit when being, determine the unified resource identification information of destination node in device management tree according to each nodal information that traverses.
20, terminal equipment as claimed in claim 17 is characterized in that, described nodal information is searched the unit and specifically comprised:
Section Point traversal subelement, the destination node that is used for obtaining according to message sink resolution unit parsing inquiry request message is in the residing query path information of device management tree, traversal meets the node of query path information one by one, determines to meet the node cluster of query path information;
The condition distinguishing subelement, be used for being used to mate the value of destination node or the conditional expression of property value according to what the message sink resolution unit resolved that inquiry request message obtains, the value of determining or property value meet the destination node of described conditional expression in the node cluster that Section Point traversal subelement is determined;
Section Point information is determined subelement, be used for respectively determining each destination node that the condition distinguishing subelement determines at the unified resource identification information of device management tree as the target node related information that finds.
21, terminal equipment as claimed in claim 20 is characterized in that, described nodal information is searched the unit and also comprised:
The second authority judgment sub-unit is used to judge whether the search access right of each node that Section Point traversal subelement traverses is all opened to described device management server respectively;
Described Section Point traversal subelement when being, meets the node of query path information by traversal in the judged result of the second authority judgment sub-unit, determines to meet the node cluster of query path information.
22, terminal equipment as claimed in claim 20, it is characterized in that, described nodal information is searched the unit and is comprised that also the 3rd nodal information determines subelement, is used for determining respectively that the value of each destination node that the condition distinguishing subelement determines or property value are as the target node related information that finds.
23, terminal equipment as claimed in claim 17 is characterized in that, described nodal information reports the unit specifically to comprise:
The buffer memory subelement is used for each target node related information that cache node information searching unit finds;
The information integrated subelement that reports reports device management server after being used for each target node related information of buffer memory subelement buffer memory integrated.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2006100784936A CN101083608A (en) | 2006-05-30 | 2006-05-30 | Method for enquiring node information of equipment management tree and its terminal equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2006100784936A CN101083608A (en) | 2006-05-30 | 2006-05-30 | Method for enquiring node information of equipment management tree and its terminal equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101083608A true CN101083608A (en) | 2007-12-05 |
Family
ID=38912887
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2006100784936A Pending CN101083608A (en) | 2006-05-30 | 2006-05-30 | Method for enquiring node information of equipment management tree and its terminal equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101083608A (en) |
Cited By (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009100632A1 (en) * | 2008-02-04 | 2009-08-20 | Huawei Technologies Co., Ltd. | Method, terminal, apparatus and system for device management |
| CN101854343A (en) * | 2009-04-01 | 2010-10-06 | 华为终端有限公司 | Method for providing node information, and method and device for acquiring node information |
| CN102201931A (en) * | 2010-03-23 | 2011-09-28 | 宏达国际电子股份有限公司 | Device management method and system and related apparatus |
| CN101820354B (en) * | 2009-02-26 | 2012-04-04 | 华为终端有限公司 | Collocation method based on TNDS (Total Network Data System) object, terminal equipment and server |
| CN102572957A (en) * | 2008-02-04 | 2012-07-11 | 华为技术有限公司 | Method, terminal, apparatus and system for device management |
| CN102665194A (en) * | 2012-03-30 | 2012-09-12 | 华为终端有限公司 | Equipment management method and equipment |
| CN103248649A (en) * | 2012-02-09 | 2013-08-14 | 宇龙计算机通信科技(深圳)有限公司 | Sort management method, equipment and system of applications |
| US8732280B2 (en) | 2008-11-27 | 2014-05-20 | Huawei Device Co., Ltd. | Device management server, device management client, and method for locating a target operation object |
| CN104111929A (en) * | 2013-04-17 | 2014-10-22 | 鸿富锦精密工业（深圳）有限公司 | Electronic device and server management control system and method |
| CN106951213A (en) * | 2017-03-27 | 2017-07-14 | 杭州迪普科技股份有限公司 | A kind of command analysis method and device |
| WO2017161749A1 (en) * | 2016-03-21 | 2017-09-28 | 乐视控股（北京）有限公司 | Method and device for information matching |
| CN107612833A (en) * | 2017-09-20 | 2018-01-19 | 郑州云海信息技术有限公司 | A kind of URI method for routing and relevant apparatus based on storage system |
| CN107679420A (en) * | 2017-10-23 | 2018-02-09 | 郑州云海信息技术有限公司 | A kind of authority setting method and system based on distributed file system |
| CN108512854A (en) * | 2018-04-09 | 2018-09-07 | 平安科技（深圳）有限公司 | Institutional information method for safety monitoring, device, computer equipment and storage medium |
| CN108563734A (en) * | 2018-04-09 | 2018-09-21 | 平安科技（深圳）有限公司 | Institutional information querying method, device, computer equipment and storage medium |
| CN110110153A (en) * | 2018-01-24 | 2019-08-09 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus of node searching |
| CN110442702A (en) * | 2019-08-15 | 2019-11-12 | 北京上格云技术有限公司 | Searching method, device, readable storage medium storing program for executing and electronic equipment |
| CN110866033A (en) * | 2018-08-28 | 2020-03-06 | 北京国双科技有限公司 | Feature determination method and device for predicting query resource occupancy |
| CN110888391A (en) * | 2019-12-12 | 2020-03-17 | 中启能科技有限公司 | Method and device for carrying out intelligent logic analysis control on cold station machine room |
| CN112583761A (en) * | 2019-09-27 | 2021-03-30 | 奇安信科技集团股份有限公司 | Management method and device of security entity, computer equipment and storage medium |
| CN112800119A (en) * | 2020-12-31 | 2021-05-14 | 深圳荆虹科技有限公司 | Equipment data management method and system |
-
2006
- 2006-05-30 CN CNA2006100784936A patent/CN101083608A/en active Pending
Cited By (41)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9246781B2 (en) | 2008-02-04 | 2016-01-26 | Huawei Technologies Co., Ltd. | Method, terminal, apparatus, and system for device management |
| US8613062B2 (en) | 2008-02-04 | 2013-12-17 | Huawei Technologies Co., Ltd. | Method, terminal, apparatus, and system for device management in network communications |
| CN102572957A (en) * | 2008-02-04 | 2012-07-11 | 华为技术有限公司 | Method, terminal, apparatus and system for device management |
| WO2009100632A1 (en) * | 2008-02-04 | 2009-08-20 | Huawei Technologies Co., Ltd. | Method, terminal, apparatus and system for device management |
| JP2011517792A (en) * | 2008-02-04 | 2011-06-16 | 華為技術有限公司 | Device management method, terminal, apparatus and system |
| CN102546760B (en) * | 2008-02-04 | 2015-11-25 | 华为技术有限公司 | The method of equipment control and terminal, device, system |
| CN102546760A (en) * | 2008-02-04 | 2012-07-04 | 华为技术有限公司 | Equipment management method, terminal, device and system |
| CN102572957B (en) * | 2008-02-04 | 2014-08-20 | 华为技术有限公司 | Method, terminal, apparatus and system for device management |
| US8732280B2 (en) | 2008-11-27 | 2014-05-20 | Huawei Device Co., Ltd. | Device management server, device management client, and method for locating a target operation object |
| US9009278B2 (en) | 2008-11-27 | 2015-04-14 | Huawei Device Co., Ltd. | Device management server, device management client, and method for locating a target operation object |
| US9350611B2 (en) | 2008-11-27 | 2016-05-24 | Huawei Device Co., Ltd. | Apparatus and method for locating a target operation object |
| CN101820354B (en) * | 2009-02-26 | 2012-04-04 | 华为终端有限公司 | Collocation method based on TNDS (Total Network Data System) object, terminal equipment and server |
| US9712403B2 (en) | 2009-04-01 | 2017-07-18 | Huawei Technologies Co., Ltd. | Method for providing node information, method for acquiring node information, and device |
| US8745190B2 (en) | 2009-04-01 | 2014-06-03 | Huawei Device Co. Ltd. | Method for providing node information, method for acquiring node information, and device |
| CN101854343B (en) * | 2009-04-01 | 2014-07-09 | 华为终端有限公司 | Method for providing node information, and method and device for acquiring node information |
| WO2010111959A1 (en) * | 2009-04-01 | 2010-10-07 | 华为终端有限公司 | Method for providing node information, method for obtaining node information and equipment thereof |
| CN101854343A (en) * | 2009-04-01 | 2010-10-06 | 华为终端有限公司 | Method for providing node information, and method and device for acquiring node information |
| CN102201931A (en) * | 2010-03-23 | 2011-09-28 | 宏达国际电子股份有限公司 | Device management method and system and related apparatus |
| CN102201931B (en) * | 2010-03-23 | 2014-05-28 | 宏达国际电子股份有限公司 | Device management method and system and related apparatus |
| CN103248649B (en) * | 2012-02-09 | 2016-08-24 | 宇龙计算机通信科技(深圳)有限公司 | Sort management method, equipment and the system of application |
| CN103248649A (en) * | 2012-02-09 | 2013-08-14 | 宇龙计算机通信科技(深圳)有限公司 | Sort management method, equipment and system of applications |
| CN102665194B (en) * | 2012-03-30 | 2015-03-18 | 华为终端有限公司 | Equipment management method and equipment |
| CN102665194A (en) * | 2012-03-30 | 2012-09-12 | 华为终端有限公司 | Equipment management method and equipment |
| CN104111929A (en) * | 2013-04-17 | 2014-10-22 | 鸿富锦精密工业（深圳）有限公司 | Electronic device and server management control system and method |
| WO2017161749A1 (en) * | 2016-03-21 | 2017-09-28 | 乐视控股（北京）有限公司 | Method and device for information matching |
| CN106951213A (en) * | 2017-03-27 | 2017-07-14 | 杭州迪普科技股份有限公司 | A kind of command analysis method and device |
| CN107612833A (en) * | 2017-09-20 | 2018-01-19 | 郑州云海信息技术有限公司 | A kind of URI method for routing and relevant apparatus based on storage system |
| CN107679420A (en) * | 2017-10-23 | 2018-02-09 | 郑州云海信息技术有限公司 | A kind of authority setting method and system based on distributed file system |
| CN110110153A (en) * | 2018-01-24 | 2019-08-09 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus of node searching |
| CN108512854B (en) * | 2018-04-09 | 2021-09-07 | 平安科技（深圳）有限公司 | System information safety monitoring method and device, computer equipment and storage medium |
| CN108512854A (en) * | 2018-04-09 | 2018-09-07 | 平安科技（深圳）有限公司 | Institutional information method for safety monitoring, device, computer equipment and storage medium |
| CN108563734A (en) * | 2018-04-09 | 2018-09-21 | 平安科技（深圳）有限公司 | Institutional information querying method, device, computer equipment and storage medium |
| CN108563734B (en) * | 2018-04-09 | 2023-04-18 | 平安科技（深圳）有限公司 | System information query method, device, computer equipment and storage medium |
| CN110866033B (en) * | 2018-08-28 | 2022-06-21 | 北京国双科技有限公司 | Feature determination method and device for predicting query resource occupancy |
| CN110866033A (en) * | 2018-08-28 | 2020-03-06 | 北京国双科技有限公司 | Feature determination method and device for predicting query resource occupancy |
| CN110442702B (en) * | 2019-08-15 | 2022-09-02 | 北京上格云技术有限公司 | Searching method and device, readable storage medium and electronic equipment |
| CN110442702A (en) * | 2019-08-15 | 2019-11-12 | 北京上格云技术有限公司 | Searching method, device, readable storage medium storing program for executing and electronic equipment |
| CN112583761A (en) * | 2019-09-27 | 2021-03-30 | 奇安信科技集团股份有限公司 | Management method and device of security entity, computer equipment and storage medium |
| CN112583761B (en) * | 2019-09-27 | 2023-03-28 | 奇安信科技集团股份有限公司 | Management method and device of security entity, computer equipment and storage medium |
| CN110888391A (en) * | 2019-12-12 | 2020-03-17 | 中启能科技有限公司 | Method and device for carrying out intelligent logic analysis control on cold station machine room |
| CN112800119A (en) * | 2020-12-31 | 2021-05-14 | 深圳荆虹科技有限公司 | Equipment data management method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101083608A (en) | Method for enquiring node information of equipment management tree and its terminal equipment | |
| CN100440809C (en) | Method and device for service configuration of network equipment | |
| CN101325509B (en) | Method, system and apparatus for installing software component | |
| US20200274764A1 (en) | Network slice management | |
| CN101188566B (en) | A method and system for data buffering and synchronization under cluster environment | |
| US20160217013A1 (en) | Method and system for generating a virtual device resource accessible by an application | |
| EP2107712B1 (en) | Method, apparatus and system for composite service process, replacement and concrete service invocation | |
| US20060101138A1 (en) | Network management apparatus and method | |
| JP2009545039A (en) | Methods, systems, and terminals for maintaining capability management objects and managing capabilities | |
| US20030140058A1 (en) | Method and apparatus for sharing information between applications using common objects | |
| CN100384154C (en) | Terminal equipment managing method and its system, and terminal equipment | |
| CN101854343A (en) | Method for providing node information, and method and device for acquiring node information | |
| CN101360121A (en) | Authority control method, system and terminal in apparatus management | |
| US10148486B2 (en) | Object version management | |
| US20090287800A1 (en) | Method, device and system for managing network devices | |
| CN102185899A (en) | Method for constructing service flow chart in browser/server (B/S) architecture and B/S architecture | |
| US7590618B2 (en) | System and method for providing location profile data for network nodes | |
| US20090165011A1 (en) | Resource management method, information processing system, information processing apparatus, and program | |
| CN102377590A (en) | Network device and data updating method thereof | |
| US20130297755A1 (en) | Network element configuration management | |
| CN101820354A (en) | Collocation method based on TNDS (Total Network Data System) object, terminal equipment and server | |
| CN100423492C (en) | Management information base processing method | |
| US7734640B2 (en) | Resource discovery and enumeration in meta-data driven instrumentation | |
| CN108092959B (en) | BACnet protocol analysis method based on configuration | |
| CN101222359B (en) | Command configuration method in network element |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Open date: 20071205 |