CN102546237A - Device management server, client and target operation object positioning method - Google Patents
Device management server, client and target operation object positioning method Download PDFInfo
- Publication number
- CN102546237A CN102546237A CN2011104243583A CN201110424358A CN102546237A CN 102546237 A CN102546237 A CN 102546237A CN 2011104243583 A CN2011104243583 A CN 2011104243583A CN 201110424358 A CN201110424358 A CN 201110424358A CN 102546237 A CN102546237 A CN 102546237A
- Authority
- CN
- China
- Prior art keywords
- management
- information
- node
- management object
- instance
- 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.)
- Granted
Links
Images
Abstract
The invention relates to the communication field. In order to overcome the shortage that in prior art a device management server needs to communicate with a user terminal for a plurality of times to obtain a uniform resource identifier of different user terminal device management nodes, the invention provides a device management server, client and target operation object positioning method. The method comprises obtaining a management instruction transmitted by the device management server, wherein the management instruction includes management object positioning information, management object instance characteristic node information and target operation object information; and operating on the target operation object according to the management instruction. The invention has the beneficial effects that the target operation object of the device management client can be positioned through such communication, and the communication efficiency between the device management server and the user terminal is improved.
Description
Technical field
The present invention relates to the communications field, particularly device management techniques in the communication system is a kind of device management server, client and object run object localization method concretely.
Background technology
The equipment control version 1.2 of Open Mobile Alliance (OMA DM V1.2:Open Mobile Alliance Device Management Version1.2) hereinafter to be referred as the DM standard, is that standard is unified in the equipment control that OMA DM work group formulates.The DM system provides a kind of lower cost solution; Be used for third party's management and environment and the configuration information in the wireless network terminal equipment (such as the functional object at mobile phone terminal and terminal) is set; Solve the problem that these network equipments in use run into; Carry out the operations such as installation, upgrading of software and firmware through wireless network (OTA:over the air) mode, and hommization more and personalized service are provided, improve user experience.The third party can be mobile operator, the information management department of service provider or partner.
Be illustrated in figure 1 as OMA DM system construction drawing in the prior art, the agency on the terminal equipment (DM Agent) is used to explain and carry out the administration order that the DM server issues.The management tree of storing on the terminal equipment can be considered to the interface that a DM Server manages terminal equipment through the DM agreement.Comprising some basic management objects (MO:Management Object), DM Server reaches the purpose of control terminal management object through the operation to the management tree object.Operational order has Get (obtaining), Replace (replacement), Exec (execution), Copy (duplicating), Delete (deletion) etc.
MO has the sign of oneself, is called MOI, in order to management object of unique sign.
DM management tree, management object are made up of node, for example root node, internal node and leaf node, and root node is the node of the superiors in the management tree; Leaf node can have nodal value; But child node can not be arranged again, and internal node can not have nodal value, but child node can be arranged.And the node of the superiors also can be described as the root node of MO and the root node of management subtree in MO or the management subtree.Node comes addressing through URI, and URI is divided into absolute URI and relative URI, and absolute URI is the URI that begins with root node, and for example " ./A/B/C/D ", relative URI is that certain position is the URI of reference, for example " A/B/C/D ".
In management tree, exist one type of unnamed node, it plays the effect of placeholder, and when server or user terminal carried out instantiation to it, it just can be named, and this category node is called the x node.After the name, this node and following child node thereof are called as instance.If this node just in time is the root node of MO, then be called the MO instance.
OMA DM has defined equipment control account number (DMAcc:Device Management Account) standard management object; This object storage be user terminal and server needed relevant parameter when connecting, as connecting with reference to, server address and authentication information etc.
OMA DM has also defined inbox (Inbox) standard management object, uses this object, when server adds management object to user terminal, can not provide the absolute path of interpolation, and informs that user terminal MOI lets the path of the own analysis object of user terminal.
The prerequisite that the DM server is managed user terminal is to need to understand the management tree relevant information on the active user terminal; The for example position of node, title and nodal value etc.; But user terminal these information of notification server not sometimes, and these information in a plurality of terminal also may be different.
Prior art one; Through in administration order, using relative URI; And add MOI information and locate a management object instance, the problem that prior art exists is following, and this technical scheme is based on the consistent prerequisite of relative URI in a plurality of terminals; If relative URI is also inconsistent in each terminal, then this technology can't be used.
Summary of the invention
The object of the present invention is to provide the method for a kind of facility management client receiving equipment administration order; Be used for solving the problem that prior art can not be carried out the location of object run object to the distinct device administrative client; Just can obtain locating information through an administration order; Through in the device management tree of facility management client, seeking corresponding locating information, obtain URI accurately, reach the purpose that the object run node is operated at last.
The present invention also aims to provide the device of a kind of facility management client receiving equipment administration order; Be used to realize the method for the said equipment administrative client receiving equipment administration order; Device management server need provide the problem of the URI of detailed facility management client equipment control tree node in the solution prior art; Realization just can obtain locating information through an administration order; Through in the device management tree of facility management client, seeking corresponding locating information, obtain URI accurately, reach the purpose that the object run node is operated at last.
The present invention also aims to provide the device of a kind of device management server transmitting apparatus administration order; Be used to realize the method for the said equipment management server transmitting apparatus administration order; Device management server need be directed to the problem that the distinct device administrative client generates different device management commands in the solution prior art, to realize the purpose of different facility management client through the accurate localizing objects running node of this administration order.
In order to solve above-mentioned deficiency; The embodiment of the invention also provides the method for a kind of object run object location; It is characterized in that this method comprises, obtain the administration order that comprises management object locating information, management object example aspects nodal information and object run object information that device management server sends; According to said administration order said object run object is operated.
In order to solve above-mentioned deficiency, the embodiment of the invention also provides a kind of facility management client, it is characterized in that this device comprises, receiving element, processing unit; Said receiving element is used for the administration order that the receiving equipment management server sends the locating information, management object example aspects nodal information and the object run object information that comprise management object; Said processing unit is used for according to said administration order said object run object being operated.
In order to solve above-mentioned deficiency, the embodiment of the invention also provides a kind of device management server, it is characterized in that this server comprises, order generation unit and transmitting element; Said order generation unit is used for adding in said administration order locating information, management object example aspects nodal information and the object run object information of management object; Said transmitting element is used for above-mentioned administration order is sent through said transmitting element.
Beneficial effect of the present invention is; Facility management client through the embodiment of the invention with according to the method for device management command localizing objects operand through once just obtaining the locating information of accurate target running node with communicating by letter of device management server; Save the repeatedly communication process with device management server, improved efficient; A kind of device management server through the embodiment of the invention can send the corresponding apparatus administration order to said facility management client, makes said facility management client realize above-mentioned purpose
Description of drawings
Accompanying drawing described herein is used to provide further understanding of the present invention, constitutes the application's a part, does not constitute qualification of the present invention.In the accompanying drawings:
Shown in Figure 1 is OMA DM system construction drawing in the prior art;
Shown in Figure 2 is the first embodiment flow chart of present device management server transmitting apparatus administration order;
Shown in Figure 3 is the present device management server transmitting apparatus administration order second embodiment flow chart;
Fig. 4 is that present device management tree first is implemented illustration;
Shown in Figure 5 is present device management server transmitting apparatus administration order the 3rd embodiment flow chart;
Shown in Figure 6 is present device management server transmitting apparatus administration order the 4th embodiment flow chart;
Shown in Figure 7 is present device management server transmitting apparatus administration order the 5th embodiment flow chart;
Fig. 8 is that present device management tree second is implemented illustration;
Shown in Figure 9 is present device management server transmitting apparatus administration order device example structure figure;
The first embodiment flow chart that is the present device administrative client according to device management command localizing objects operand shown in Figure 10;
Shown in Figure 11 is the specific embodiment flow chart of step 1002 in the present device administrative client localizing objects operand;
The second embodiment flow chart that is the present device administrative client according to device management command localizing objects operand shown in Figure 12;
The 3rd embodiment flow chart that is the present device administrative client according to device management command localizing objects operand shown in Figure 13;
The 4th embodiment flow chart that is the present device administrative client according to device management command localizing objects operand shown in Figure 14;
The 5th embodiment flow chart that is the present device administrative client according to device management command localizing objects operand shown in Figure 15;
Shown in Figure 16 is receiving equipment administrative client example structure figure
Shown in Figure 17 is the processing unit 1602 example structure figure of present device administrative client;
Shown in Figure 180 is the object run object unit 1703 example structure figure of present device administrative client.
Embodiment
For making the object of the invention, technical scheme and advantage clearer,, the present invention is explained further details below in conjunction with execution mode and accompanying drawing.At this, exemplary embodiment of the present invention and explanation thereof are used to explain the present invention, but not as to qualification of the present invention.
The embodiment of the invention provides a kind of device management server client objectives operand localization method.Below in conjunction with accompanying drawing the present invention is elaborated.
Be illustrated in figure 2 as the present device management server transmitting apparatus administration order first embodiment flow chart.
Comprise step 201, in the administration order that device management server issues, add the locating information of management object, management object of the locating information unique identification of this management object is used for the terminal and finds the management object that will operate according to this identification information.
This object run nodal information is used for facility management client and finds the node that will operate according to this object run nodal information.
The said step 201 of the embodiment of the invention, 202,203 do not limit sequencing, and described in this example order is wherein a kind of special case just.
Be illustrated in figure 3 as the present device management server transmitting apparatus administration order second embodiment flow chart.
Device management tree is as shown in Figure 4, and wherein node 1 is the root node of DMAcc management object, and Serve rID is server identification (server identification in each admin instance is different), and AAuthPref is first-selected auth type.If server is hoped the value of configuration node AAuthPref; But it does not also know the position of this management object in the terminal management tree; The root node of also not knowing this management object instance is a node 1; Then can the use and management object and management object example aspects nodal information inquire the particular location of this node of AAuthPref, be configured simultaneously.
Server use to substitute the value that the AAuthPref node is replaced in (Replace) order, in server sends the Item element of order, uses TargetParent, Target and Data unit usually to carry management object locating information, object run nodal information respectively and waits to be substituted into the node data of destination node.
As preferred embodiment, for example can only use management object ID (the MOID:Management Object ID) unit of a redetermination usually to carry MOI, as<mOID>Urn:oma:mo:oma-dm-dmacc:1.0</MOID>, do not limit the position of MOI information in administration order simultaneously yet.
As preferred embodiment, the present invention does not limit the element that specifically carries locating information and more title, type, the number of upper strata element, for example can only use a MOInstID unit usually to carry, as<mOInstID>ServerID? Value=www.sonera.fi-8765</MOInstID>, wherein ServerID is a characteristic node, www.sonera.fi-8765 is the characteristic node value, does not limit the position of this locating information in administration order as preferred embodiment.
The relative URI information that the object run node usually carries in step 303, this example LocURI unit in the Target element is like the AAuthPref node in this example.And the data content of adding replacement in the Data element.But different with existing DM agreement is; The base URI of this object run node is not the root node of equipment; But the root node of management object instance; The root node of management object instance obtains through above-described management object example aspects nodal information location, and concrete position fixing process is described below.
As preferred embodiment, according to the order of sequencing Laian County registration process of arrangement of elements in the order, for example the management object locating information comes foremost (being the information in the TargetParent element) in the previous example.Also can confirm the order of position fixing process through other supplementary; For example use an element S equenceItem; In this element, write locating information, management object example aspects nodal information and the object run object information of management object, sign is handled according to each sequence of information in this element.The method of distinguishing the position fixing process order here also is suitable for follow-up repeating no more in other part of the present invention.
Be illustrated in figure 5 as present device management server transmitting apparatus administration order the 3rd embodiment flow chart.
If server need be deleted certain management object instance, for example the DMAcc management object instance node 1 among Fig. 4.
Step 502 writes certain characteristic node and nodal information thereof in the management object as management object example aspects nodal information, like ServerID node in this example and nodal value www.sonera.fi-8765 thereof.Coexist with the embodiment two-phase and to carry management object example aspects nodal information in the Filter element.
As preferred embodiment, do not comprise in the Target element that it is exactly the root node of management object instance that the LocURI element also can be expressed the node of administration order operation, reaches the purpose of the whole management object instance of deletion of node 1.
Be illustrated in figure 6 as present device management server transmitting apparatus administration order the 4th embodiment flow chart.
Device management server transmits like the Replace administration order among the embodiment two in this example, and the destination address in its Target element is the ./Inbox node, and the expression server upgrades a management object instance through the inbox function.This device management tree is as shown in Figure 4.
As preferred embodiment; In the TNDS object, also can comprise management object example aspects nodal information; Node ServerID and nodal value www.sonera.fi-8765 thereof for example in the TNDS object, have been comprised; So present embodiment can remove the management object example aspects nodal information that above-mentioned use Filter element carries separately in administration order, facility management client is received after the administration order extract management object instance characteristic node information from the TNDS object.
Step 602 adds the management object locating information in the RTProperties/Type element of TNDS object root node, i.e. the management object sign.
Step 603 has comprised the object run object that administration order need be operated in the Data element, i.e. TNDS object, comprising as<nodeName>AAuthPref</NodeName>Deng the nodal information that needs operation.
As preferred embodiment, the Replace administration order in this example can not comprise the Target element, does not promptly comprise destination address.
Be illustrated in figure 7 as present device management server transmitting apparatus administration order the 5th embodiment flow chart.
Server need be replaced the value like node AAuthType among Fig. 8; But it does not also know the position of this management object in management tree; The root node of also not knowing this management object instance is a node 1, and the root node of also not knowing to manage subtree instance 2 is nodes 2, then on the basis of use and management object and management object example aspects nodal information; Re-use management subtree instance locating information; Like AAuthLevel node and the nodal value thereof among the figure, inquire the particular location of this node of AAuthType, be configured simultaneously.
Step 701 in this replacement order, writes the management object locating information at the Item/MOID element.Use and management object identity (MOID) is used as the locating information of management object, is urn:oma:mo:oma-dm-dmacc:1.0 in this example.
Step 702 writes management object example aspects nodal information in the Item/MOInstID element, i.e. characteristic node and nodal value thereof do in this example<mOInstID>ServerID? Value=www.sonera.fi-8765</MOInstID>, the ServerID in this example is a characteristic node, www.sonera.fi-8765 is this characteristic node value.
Step 703 writes the characteristic node information of managing the subtree instance in the Item/SubMOInstID element, promptly in the Item/SubMOInstID element, write characteristic node and nodal value thereof in the subtree, does in this example<subMOInstID>AAuthLevel.? Value=SRVCRED</SubMOInstID>, wherein AauthLevel is the characteristic node of subtree, SRVCRED is the nodal value of AauthLevel characteristic node.
Step 704 writes the relative URI of object run node in the Taget/LocURI element, do in this example<target><locURI>AAuthType</LocURI></Target>, wherein running node is AauthType.In the Data element, write HTTP-BASIC as the data that will replace.
As preferred embodiment, the locating information of management subtree instance can have a plurality of, a plurality of SubMOInstID is promptly arranged, to be used to locate the more management subtree instance of lower floor.The present invention does not limit the position of these elements in administration order, and for example they can be placed in the Target element.
Be illustrated in figure 9 as present device management server transmitting apparatus administration order device example structure figure.
Comprise order generation unit 901 and transmitting element 902.
Said order generation unit 901 is used for adding in said administration order locating information, management object example aspects nodal information and the object run object information of management object; Said transmitting element 902 is used for above-mentioned administration order is sent through said transmitting element.
Said order generation unit 901 adds the locating information of management object in the administration order that server issues, this management object locating information comprises and is used for management object of unique identification, is used for the terminal and finds this management object according to this identification information; And add management object example aspects nodal information, this management object example aspects nodal information comprises the information of unique identification management object instance, is used for the terminal and finds the management object instance according to this management object example aspects nodal information; Also add the object run object information; This object run object information comprises object run nodal information and TNDS object information; Be used for the terminal and find the node that to operate, perhaps find the management subtree instance that to operate through this TNDS object information according to this object run nodal information.Send said administration order through said transmitting element 902.
The first embodiment flow chart that is the present device administrative client according to device management command localizing objects operand shown in figure 10.
Through the foregoing description, different facility management client can be according to same device management command localizing objects operand.
Shown in figure 11 is the specific embodiment flow chart of step 1002 in the present device administrative client localizing objects operand.Step 1101 is obtained the URI with the management object instance root node of said management object locating information coupling.
As preferred embodiment; In the step 1101; If directly stored the sign of management object and the correspondence relationship information of management object position in the facility management client; And the correspondence relationship information of management object position and each management object instance, position fixing process is then different, and facility management client directly finds corresponding father node URI and gets final product in correspondence relationship information.For example table 1 has provided the URI of the father node at management object place, and each corresponding management object instance:
Table 1
| The management object identification information | Father node URI | The management object instance |
| urn:oma:mo:oma-dm-dmacc:1.0 | ./ |
1 |
| urn:oma:mo:oma-dm-dmacc:1.0 | ./ |
2 |
| urn:oma:mo:oma-scomo:1.0 | ./Application/ |
2 |
| urn:oma:mo:oma-scomo:1.0 | ./Application/Software | 3 |
| urn:oma:mo:oma-lawmo:1.0 | ./ |
1 |
As preferred embodiment, said object run object comprises, object run node and TNDS object.
The second embodiment flow chart that is the present device administrative client according to device management command localizing objects operand shown in figure 12.
Be directed to the replacement management order that device management server sends, the device management tree of said facility management client is as shown in Figure 4, and facility management client is handled as follows:
As preferred embodiment; For above-mentioned steps 1202 and 1203; Facility management client can be distinguished the order of position fixing process according to the sequencing of arrangement of elements in the order when operational order is resolved, for example the management object locating information comes foremost (being the information in the TargetParent element) in the previous example, and then handle it earlier at the terminal; So just realized the at first purpose of orientation management object, 1202 just top steps.Can certainly confirm the order of position fixing process through other supplementary; For example in administration order, use an element S equenceItem; In this element, obtain locating information, management object example aspects nodal information and the object run object information of management object, then the terminal can the order the processing locating information.The method of distinguishing the position fixing process order here also is suitable for follow-up repeating no more in other part of the present invention.
The 3rd embodiment flow chart that is the present device administrative client according to device management command localizing objects operand shown in figure 13.
If server need delete certain management object instance, the DMAcc management object instance 1 among Fig. 4 for example, said facility management client is carried out following handling process:
As preferred embodiment, in the Target element, do not comprise the LocURI element, also can node 1 and child node thereof all be deleted.
The 4th embodiment flow chart that is the present device administrative client according to device management command localizing objects operand shown in figure 14.
What facility management client received in this example is like the Replace administration order among second embodiment of facility management client receiving management order; Destination address among its Target is the ./Inbox node, and the indication equipment administrative client is through upgrading a management object instance to sending out to the administration order of inbox.The device management tree of this facility management client is as shown in Figure 4.
As preferred embodiment, this routine administration order does not comprise the Target element, does not promptly comprise destination address, can realize above-mentioned location, replacement function yet.
The 5th embodiment flow chart that is the present device administrative client according to device management command localizing objects operand shown in figure 15.
The device management tree of facility management client is as shown in Figure 8, and facility management client receives the corresponding administration order of device management server, is replacement order, the value of replacement node AAuthType in this example.
Shown in figure 16 is present device administrative client example structure figure.
Comprise receiving element 1601, processing unit 1602;
Said receiving element 1601 is used for the administration order that the receiving equipment management server sends the locating information, management object example aspects nodal information and the object run object information that comprise management object;
Said processing unit 1602 is used for according to said administration order said object run object being operated.
Through the foregoing description, different facility management client can be according to same device management command localizing objects operand.
Shown in figure 17 is the said processing unit 1602 example structure figure of present device administrative client.
Comprise management object positioning unit 1701, management object instance positioning unit 1702, object run object unit 1703.
Said management object positioning unit 1701 is used to obtain the URI with the management object instance root node of said management object locating information coupling, and a URI can be a plurality of or one or also can be the zero that does not find.
Said management object instance positioning unit 1702; The characteristic node information of the management object instance that said management object example aspects nodal information is corresponding with said first unified resource sign is complementary, and obtains the 2nd URI of the corresponding management object instance root node of the successful characteristic node of coupling.
Said object run object unit 1703, said object run object unit according to object run object information in the said administration order and said second unified resource sign, is operated said object run object.As preferred embodiment; Also comprise management subtree instance positioning unit; Be connected in said management object instance positioning unit 1702; According to the characteristic node information of the management subtree instance in the said administration order, coupling is respectively managed the characteristic node the subtree instance from the management object instance root node of said management object instance positioning unit output, obtains the unified resource sign (i.e. the 2nd URI) of the corresponding management subtree instance root node of this characteristic node.
As preferred embodiment, also have a corresponding relation table in said facility management client, said management object positioning unit is according to a URI of said management object locating information and said mapping table match management object.
Shown in figure 18 is the said object run object unit 1703 example structure figure of present device administrative client.
Said object run object unit also comprises link block 1801 and Executive Module 1802, and said link block 1801 is used for coupling together the relative URI of said the 2nd URI and object run node, obtains the URI of object run node;
Said Executive Module 1802 is used for this object run node is operated, perhaps that the said coupling of TNDS object replacement is the successful corresponding management object instance of characteristic node.
The present device administrative client is not limited only to mobile communication terminal, can also comprise that other meets the communication equipment of device management protocol.
Beneficial effect of the present invention is; Device management server can be at the situation of the more specific location information of not understanding management object property location and operational administrative object next time, can avoid each terminal inner structure and the inconsistent problem of instance title when managing a plurality of terminal especially at the same time; Facility management client can be after receiving incomplete administration order; Seek corresponding object run node in this facility management client device management tree; Saved and device management server communication steps repeatedly, saved the efficient of Internet resources and raising device management server configuration device administrative client device management command.
Above-described embodiment; The object of the invention, technical scheme and beneficial effect have been carried out further explain, and institute it should be understood that the above is merely embodiment of the present invention; And be not used in qualification protection scope of the present invention; All within spirit of the present invention and principle, any modification of being made, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (21)
1. the method for object run object location; It is characterized in that this method comprises; Obtain the administration order that device management server sends, said administration order comprises management object locating information, management object example aspects nodal information and object run object information; According to said administration order said object run object is operated.
2. the method for object run object according to claim 1 location; It is characterized in that; The locating information of said management object is used for management object of unique sign; Management object example aspects nodal information is used for the corresponding instance of the said management object of unique identification, and said object run object information is used to represent object run node or TNDS object.
3. arbitrary method of object run object according to claim 2 location is characterized in that said said object run object the operation specifically according to said administration order comprises:
Confirm second unified resource sign according to said management object locating information, management object example aspects nodal information;
Couple together the relatively uniform resource identification of said second unified resource sign, obtain the unified resource sign of object run node, and this object run node is operated with the object run node; Perhaps said TNDS object is replaced the corresponding management object instance of said second unified resource sign.
4. the method for object run object according to claim 2 location is characterized in that said facility management client is obtained said management object example aspects nodal information from the TNDS object of said administration order;
Perhaps obtain said management object example aspects nodal information in the filtration element from said administration order.
5. the method for object run object according to claim 3 location is characterized in that, saidly confirms that according to said management object locating information, management object example aspects nodal information second unified resource sign comprises:
Obtain first unified resource sign of the management object instance root node that matees with said management object locating information;
The characteristic node information of the management object instance that said management object example aspects nodal information is corresponding with said first unified resource sign is complementary, and obtains second unified resource sign of the corresponding management object instance root node of the successful characteristic node of coupling.
6. the method for object run object according to claim 5 location; It is characterized in that; Said according to said management object example aspects nodal information, second unified resource sign of obtaining the management object instance root node corresponding with said first unified resource sign also comprises afterwards
Characteristic node information according to the management subtree instance in the said administration order; What mate management object instance root node lower floor in the said facility management client respectively manages the characteristic node in the subtree instance, and second unified resource of obtaining the corresponding management subtree instance root node of the successful characteristic node of coupling identifies.
7. the method for object run object according to claim 3 location is characterized in that,
Unified resource sign according to the mapping table match management object in said management object locating information and the facility management client;
Perhaps according to said management object locating information, the unified resource of match management object identifies in device management tree.
8. the method for object run object according to claim 3 location is characterized in that, if the object run object information in the said administration order is empty, then the object run object is the corresponding management object instance of said second unified resource sign.
9. the method for object run object according to claim 3 location is characterized in that, in said administration order, obtains locating information, management object example aspects nodal information and the object run object information of management object in order; Perhaps in said administration order, obtain the element of order of representation, the locating information of obtaining management object, management object example aspects nodal information and the object run object information of order from this element.
10. the method for object run object according to claim 1 location; It is characterized in that the ./Inbox node of slave unit management tree obtains the management object locating information of said administration order, management object example aspects nodal information and object run object information.
11. the method for object run object according to claim 1 location; It is characterized in that; If the object run object information in the said administration order is empty, then confirm second unified resource sign according to said management object locating information, management object example aspects nodal information;
The management object instance that said second unified resource sign is corresponding is as the object run object.
12. a facility management client is characterized in that this device comprises, receiving element, processing unit;
Said receiving element is used for the administration order that the receiving equipment management server sends the locating information, management object example aspects nodal information and the object run object information that comprise management object;
Said processing unit is used for according to said administration order said object run object being operated.
13. a kind of facility management client according to claim 12 is characterized in that said processing unit also comprises:
The management object positioning unit, management object instance positioning unit and object run object unit;
Said management object positioning unit is used to obtain first unified resource sign with the management object instance root node of said management object locating information coupling;
Said management object instance positioning unit; The characteristic node information of the management object instance that said management object example aspects nodal information is corresponding with said first unified resource sign is complementary, and obtains second unified resource sign of the corresponding management object instance root node of the successful characteristic node of coupling;
Said object run object unit according to object run object information in the said administration order and said second unified resource sign, is operated said object run object.
14. a kind of facility management client according to claim 13; It is characterized in that; Said object run object unit also comprises link block and Executive Module; Said link block is used for coupling together the relatively uniform resource identification of said second unified resource sign with the object run node, obtains the unified resource sign of object run node; Said Executive Module is used for this object run node is operated, perhaps that the said coupling of TNDS object replacement is the successful corresponding management object instance of characteristic node.
15. a kind of facility management client according to claim 13; It is characterized in that; Also have a corresponding relation table in said facility management client, said management object positioning unit is according to the unified resource sign of said management object locating information and said mapping table match management object.
16. a kind of facility management client according to claim 13; It is characterized in that; Also comprise management subtree positioning unit; Be used for the characteristic node information according to the management subtree instance of said administration order, coupling is respectively managed the characteristic node the subtree instance from each management object instance root node lower floor of said management object instance positioning unit output, and the unified resource of obtaining the corresponding management subtree instance root node of the successful characteristic node of coupling identifies.
17. a device management server is characterized in that this server comprises, order generation unit and transmitting element;
Said order generation unit is used for adding in said administration order locating information, management object example aspects nodal information and the object run object information of management object; Said transmitting element is used for above-mentioned administration order is sent through said transmitting element.
18. the method for an object run object location is characterized in that this method comprises, obtains the delete command that device management server sends, said delete command comprises management object locating information and management object example aspects nodal information; Confirm the root node of management object instance according to said management object locating information, management object example aspects nodal information;
Delete said management object instance root node and child node thereof.
19. the method for object run object according to claim 18 location is characterized in that said management object locating information and management object example aspects nodal information are carried in the It em/Source/LocURI element of said delete command.
20. the method for an object run object location is characterized in that this method comprises, obtains the delete command that device management server sends, and comprises the management object locating information in the said delete command;
Confirm the cura generalis object instance according to said management object locating information;
Delete said cura generalis object instance.
21. the method for object run object according to claim 20 location is characterized in that said management object locating information is carried in the Item/Source/LocURI element of said delete command.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110424358.3A CN102546237B (en) | 2008-11-27 | 2008-11-27 | Device management server, client and target operation object positioning method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110424358.3A CN102546237B (en) | 2008-11-27 | 2008-11-27 | Device management server, client and target operation object positioning method |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200810181563A Division CN101778486B (en) | 2008-11-27 | 2008-11-27 | Equipment management server, client and target operation object positioning method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102546237A true CN102546237A (en) | 2012-07-04 |
| CN102546237B CN102546237B (en) | 2014-08-20 |
Family
ID=46352244
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110424358.3A Active CN102546237B (en) | 2008-11-27 | 2008-11-27 | Device management server, client and target operation object positioning method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102546237B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103944950A (en) * | 2013-01-22 | 2014-07-23 | 中兴通讯股份有限公司 | TNDS (tree and description serialization)-based terminal device firmware optimization method, client and system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1885986A (en) * | 2005-06-20 | 2006-12-27 | 华为技术有限公司 | Method for operating resource in device management |
| CN1983962A (en) * | 2006-06-08 | 2007-06-20 | 华为技术有限公司 | Extended network managing system and method |
| CN101141306A (en) * | 2007-10-19 | 2008-03-12 | 杭州华三通信技术有限公司 | Equipment parameter loading method and apparatus |
-
2008
- 2008-11-27 CN CN201110424358.3A patent/CN102546237B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1885986A (en) * | 2005-06-20 | 2006-12-27 | 华为技术有限公司 | Method for operating resource in device management |
| CN1983962A (en) * | 2006-06-08 | 2007-06-20 | 华为技术有限公司 | Extended network managing system and method |
| CN101141306A (en) * | 2007-10-19 | 2008-03-12 | 杭州华三通信技术有限公司 | Equipment parameter loading method and apparatus |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103944950A (en) * | 2013-01-22 | 2014-07-23 | 中兴通讯股份有限公司 | TNDS (tree and description serialization)-based terminal device firmware optimization method, client and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102546237B (en) | 2014-08-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101778486B (en) | Equipment management server, client and target operation object positioning method | |
| US20080244049A1 (en) | Method and System for Device Management | |
| CN101854343B (en) | Method for providing node information, and method and device for acquiring node information | |
| CN101123794B (en) | A method, system and client for locating operation node in communication system | |
| CN102301760A (en) | Method and apparatus for tracking device management data changes | |
| CN101345657B (en) | Method and system for cluster management of multiple network elements based on simple network management protocol | |
| CN101599865A (en) | A kind of management method of the cluster network based on unique public network IP address | |
| CN101409632B (en) | Transmission method, system and apparatus for remote procedure call command | |
| CN103856520A (en) | Communication processing method, server and terminal | |
| CN102546237B (en) | Device management server, client and target operation object positioning method | |
| CN102571390B (en) | Equipment management method, equipment and system | |
| CN101588255B (en) | Fusion device management platform, mobile terminal and method for managing same | |
| CN102547667B (en) | Method and device for device management | |
| CN101753604B (en) | Method for reporting equipment information, user terminal and server | |
| CN101547460A (en) | Method, device and system for processing DDF information | |
| CN101442791B (en) | Method and apparatus for sending node information | |
| CN103477663A (en) | Method and device for identifying mobile terminal |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 518129 Building 2, B District, Bantian HUAWEI base, Longgang District, Shenzhen, Guangdong. Patentee after: Huawei Terminal (Shenzhen) Co., Ltd. Address before: 518129 Building 2, B District, Bantian HUAWEI base, Longgang District, Shenzhen, Guangdong. Patentee before: Huawei Device Co., Ltd. |