CN102546237B - 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
- CN102546237B CN102546237B CN201110424358.3A CN201110424358A CN102546237B CN 102546237 B CN102546237 B CN 102546237B CN 201110424358 A CN201110424358 A CN 201110424358A CN 102546237 B CN102546237 B CN 102546237B
- Authority
- CN
- China
- Prior art keywords
- management
- management object
- information
- node
- target operation
- 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.)
- Active
Links
Landscapes
- Computer And Data Communications (AREA)
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 communication system, is a kind of device management server, client and target operation object positioning method concretely.
Background technology
The equipment control version 1.2 (OMA DM V1.2:Open Mobile Alliance Device Management Version1.2) of Open Mobile Alliance, hereinafter to be referred as DM specification, is the equipment control unified standard that OMA DM work group formulates.DM system provides a kind of lower cost solution, manage and arrange environment and the configuration information in wireless network terminal equipment (such as the functional object of mobile phone terminal and terminal) for third party, solve the problem that these network equipments in use run into, carry out the operation such as installation, upgrading of software and firmware by wireless network (OTA:over the air) mode, and hommization more and personalized service are provided, improve user and experience.Third party can be mobile operator, the information management department of service provider or partner.
Be illustrated in figure 1 OMA DM system construction drawing in prior art, the agency (DM Agent) on terminal equipment is for explaining and carry out the administration order that DM server issues.The management tree of storing on terminal equipment can be considered to the interface that a DM Server manages terminal equipment by DM agreement.Comprising some basic management objects (MO:Management Object), DM Server is by reaching the object of control terminal management object to the operation of management tree object.Operational order has Get (obtaining), Replace (replacement), Exec (execution), Copy (copying), Delete (deletion) etc.
MO has the mark of oneself, is called MOI, in order to management object of unique mark.
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 management tree, leaf node can have nodal value, but can not have child node, internal node can not have nodal value again, but can have child node.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 management subtree.Node carrys out addressing by URI, and URI is divided into absolute URI and relative URI, and definitely URI is the URI starting with root node, and for example " ./A/B/C/D ", relative URI is the URI that certain position is reference, for example " A/B/C/D ".
In management tree, exist the unnamed node of a class, it plays the effect of placeholder, and in the time that server or user terminal carry out instantiation to it, it just can be named, and this category node is called x node.After name, this node and child node below thereof are called as example.If this node is just in time the root node of MO, be called MO example.
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 while connecting, as connected with reference to, server address and authentication information etc.
OMA DM has also defined inbox (Inbox) standard management object, use this object, server adds when management object user terminal, can not provide the absolute path of interpolation, and informs that user terminal MOI allows the path of the own analysis object of user terminal.
The prerequisite that DM server manages user terminal is the management tree relevant information that need to understand in active user's terminal, position, title and the nodal value etc. of such as node, but not these information of notification server of user terminal sometimes, and these information in multiple terminal also may be different.
Prior art one, by use relative URI in administration order, and add MOI information and locate a management object example, the problem that prior art exists is as follows, this technical scheme is the prerequisite that the relative URI based in multiple terminals is consistent, if relative URI is also inconsistent in each terminal, this technology cannot 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, can not carry out for distinct device administrative client the problem of the location of target operation object for solving prior art, just can obtain locating information by an administration order, by find corresponding locating information in the device management tree of facility management client, obtain URI accurately, finally reach the object that object run node is operated.
The present invention also aims to provide the device of a kind of facility management client receiving equipment administration order, for realizing the method for the said equipment administrative client receiving equipment administration order, in solution prior art, device management server need to provide the problem of the URI of detailed facility management client equipment control tree node, realize and just can obtain locating information by an administration order, by find corresponding locating information in the device management tree of facility management client, obtain URI accurately, finally reach the object that object run node is operated.
The present invention also aims to provide the device of a kind of device management server transmitting apparatus administration order, for realizing the method for the said equipment management server transmitting apparatus administration order, solve the problem that device management server in prior art need to be directed to distinct device administrative client and generate different device management commands, to realize different facility management client by the object of the accurate localizing objects running node of this administration order.
In order to solve above-mentioned deficiency, the embodiment of the present invention also provides the method for a kind of target operation object location, the method comprises, obtains the administration order that comprises management object locating information, management object example aspects nodal information and target operation object information that device management server sends; According to described administration order, described target operation object is operated, the locating information of described management object is for unique management object of mark, management object example aspects nodal information is for example corresponding to management object described in unique identification, and described target operation object information is used for representing object run node or tree and description serializing TNDS object; Describedly according to described administration order, described target operation object is operated specifically and comprised: determine the second unified resource mark according to described management object locating information, management object example aspects nodal information; Described the second unified resource mark is coupled together with the relatively uniform resource identification of object run node, obtain the unified resource mark of object run node, and this object run node is operated; Or described TNDS object is replaced to described the second unified resource and identify corresponding management object example.
In order to solve above-mentioned deficiency, the embodiment of the present invention also provides a kind of facility management client, and this device comprises, receiving element, processing unit; Described receiving element, sends the administration order of the locating information, management object example aspects nodal information and the target operation object information that comprise management object for receiving equipment management server; Described processing unit, for described target operation object being operated according to described administration order, the locating information of described management object is for unique management object of mark, management object example aspects nodal information is for example corresponding to management object described in unique identification, and described target operation object information is used for representing object run node or tree and description serializing TNDS object; Described processing unit comprises target operation object unit, and described target operation object unit, for the second unified resource mark is coupled together with the relatively uniform resource identification of object run node, obtains the unified resource mark of object run node; This object run node is operated, or TNDS object is replaced to described management object example corresponding to characteristic node that the match is successful, and wherein said the second unified resource mark is determined according to described management object locating information, management object example aspects nodal information.
In order to solve above-mentioned deficiency, the embodiment of the present invention also provides a kind of device management server, and this server comprises, order generation unit and transmitting element; Described order generation unit is for adding locating information, management object example aspects nodal information and the target operation object information of management object in described administration order; Described transmitting element is for sending above-mentioned administration order by described transmitting element, determine the second unified resource mark so that receive the facility management client of described administration order according to described management object locating information, management object example aspects nodal information, described the second unified resource mark is coupled together with the relatively uniform resource identification of object run node, obtain the unified resource mark of object run node, and this object run node is operated; Or described TNDS object is replaced to described the second unified resource and identify corresponding management object example; The locating information of described management object is for unique management object of mark, management object example aspects nodal information is for example corresponding to management object described in unique identification, and described target operation object information is used for representing object run node or tree and description serializing TNDS object.
Beneficial effect of the present invention is, by the facility management client of the embodiment of the present invention with according to the method for device management command localizing objects operand by once just obtaining the locating information of object run node accurately with communicating by letter of device management server, save and the repeatedly communication process of device management server, improved efficiency; A kind of device management server by the embodiment of the present invention can send corresponding device management command to described facility management client, makes described facility management client realize above-mentioned purpose
Brief description of the drawings
Accompanying drawing described herein is used to provide a further understanding of the present invention, forms the application's a part, does not form limitation of the invention.In the accompanying drawings:
Figure 1 shows that OMA DM system construction drawing in prior art;
Figure 2 shows that the first embodiment flow chart of present device management server transmitting apparatus administration order;
Figure 3 shows that present device management server transmitting apparatus administration order the second embodiment flow chart;
Fig. 4 is that present device management tree first is implemented illustration;
Figure 5 shows that present device management server transmitting apparatus administration order the 3rd embodiment flow chart;
Figure 6 shows that present device management server transmitting apparatus administration order the 4th embodiment flow chart;
Figure 7 shows that 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;
Figure 9 shows that present device management server transmitting apparatus administration order device example structure figure;
Figure 10 shows that present device administrative client is according to the first embodiment flow chart of device management command localizing objects operand;
Figure 11 shows that the specific embodiment flow chart of step 1002 in present device administrative client localizing objects operand;
Figure 12 shows that present device administrative client is according to the second embodiment flow chart of device management command localizing objects operand;
Figure 13 shows that present device administrative client is according to the 3rd embodiment flow chart of device management command localizing objects operand;
Figure 14 shows that present device administrative client is according to the 4th embodiment flow chart of device management command localizing objects operand;
Figure 15 shows that present device administrative client is according to the 5th embodiment flow chart of device management command localizing objects operand;
Figure 16 shows that receiving equipment administrative client example structure figure
Figure 17 shows that the processing unit 1602 example structure figure of present device administrative client;
Figure 18 shows that the target operation object unit 1703 example structure figure of present device administrative client.
Embodiment
For making the object, technical solutions and advantages of the present invention clearer, below in conjunction with execution mode and accompanying drawing, the present invention is described in further details.At this, exemplary embodiment of the present invention and explanation thereof are used for explaining the present invention, but not as a limitation of the invention.
The embodiment of the present invention provides a kind of device management server, client and target operation object positioning method.Below in conjunction with accompanying drawing, the present invention is described in detail.
Be illustrated in figure 2 present device management server transmitting apparatus administration order the first embodiment flow chart.
Comprise step 201, add the locating information of management object at device management server in the administration order issuing, management object of locating information unique identification of this management object, finds the management object that will operate according to this identification information for terminal.
Step 202, in the administration order issuing at described device management server, add management object example aspects nodal information, this management object example aspects nodal information comprises the information of unique identification management object example, finds the position (URI) of management object example for facility management client according to this management object example aspects nodal information.
Step 203, in the administration order issuing at described device management server, add target operation object information, this target operation object comprises " tree and description serializing " (TNDS:Tree aNd Description Serialization) object or object run nodal information.
This object run nodal information finds the node that will operate for facility management client according to this object run nodal information.
Step 204, sends described administration order.
Step 201 described in the embodiment of the present invention, 202,203 do not limit sequencing, in this example just a kind of special case wherein of described order.
Be illustrated in figure 3 present device management server transmitting apparatus administration order the second embodiment flow chart.
As shown in Figure 4, wherein node 1 is the root node of DMAcc management object to device management tree, and ServerID is server identification (server identification in each admin instance is different), and AAuthPref is first-selected auth type.If server is wished the value of configuration node AAuthPref, but it does not also know the position of this management object in terminal management tree, the root node of also not knowing this management object example is node 1, the particular location that can inquire with management object and management object example aspects nodal information this node of AAuthPref is configured simultaneously.
Server uses alternative (Replace) to order the value of replacing AAuthPref node, sends in the Item element of ordering and uses respectively TargetParent, Target and Data unit usually to carry management object locating information, object run nodal information and the node data to destination node to be replaced at server.
Step 301, use management object mark (MOI:Management Object Identifier) to be used as the locating information of management object, in this example, be urn:oma:mo:oma-dm-dmacc:1.0, but the present invention does not limit and uses the MOI defining in existing DM agreement to be used as the locating information of management object, needs only facility management client and can find the object that needs operation by this locating information.This example is used LocName unit usually to carry above-mentioned MOI in TargetParent element, but the present invention does not limit and carries the element of MOI and more title, type, the number of upper strata element.
As preferred embodiment, for example can only use management object ID (the MOID:Management Object ID) unit of a new definition 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.
Step 302, certain characteristic node in use management object and nodal information thereof are as management object example aspects nodal information, as the ServerID node in this example and nodal value www.sonera.fi-8765 thereof.This characteristic node and nodal information thereof can be in one or more facility management client management object example of unique identification, which node the present invention does not limit by as characteristic node, does not limit yet and uses nodal value as nodal information.This example is used the filtration element (Filter) in Target to carry above-mentioned information, specifically carry characteristic node relative URI with daughter element Record/Item/Target/LocURI, it is ServerID node, carry characteristic node information, i.e. www.sonera.fi-8765 with daughter element Record/Item/Data.Note, the benchmark URI of characteristic node (base URI) is not the root node of equipment here, but the root x node of management object.
As preferred embodiment, the present invention does not limit and specifically carries the element of 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</MOInstIDGreatT.Gr eaT.GT, wherein ServerID is characteristic node, www.sonera.fi-8765 is characteristic node value, does not limit the position of this locating information in administration order as preferred embodiment.
Step 303, the relative URI information that object run node usually carries in the LocURI unit of this example in Target element, as the AAuthPref node in this example.And in Data element, add the data content of replacement.But different from 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 example, the root node of management object example obtains by above-described management object example aspects nodal information location, and concrete position fixing process is described below.
Step 304, device management server sends above-mentioned replace command to facility management client.
As preferred embodiment, arrange the order of position fixing process according to the sequencing of arrangement of elements in order, for example in previous example, management object locating information comes foremost (being the information in TargetParent element).Also can determine by other supplementary the order of position fixing process, for example use an element S equenceItem, in this element, write locating information, management object example aspects nodal information and the target operation object information of management object, mark is processed according to each sequence of information in this element.The method of distinguishing position fixing process order here is also suitable in other parts of the present invention, follow-up repeating no more.
Be illustrated in figure 5 present device management server transmitting apparatus administration order the 3rd embodiment flow chart.
If server need to be deleted certain management object example, for example DMAcc management object example node 1 in Fig. 4.
Step 501 still writes management object locating information at Item/TargetParent/LocName element in this Delete order.Using management object mark to be used as the locating information of management object, is urn:oma:mo:oma-dm-dmacc:1.0 in this example.
Step 502, writes certain characteristic node in management object and nodal information thereof as management object example aspects nodal information, as the ServerID node in this example and nodal value www.sonera.fi-8765 thereof.Coexist in Filter element and carry management object example aspects nodal information with embodiment two-phase.
Step 503, the relative URI of the object run node in Target/LocURI element is empty, this node that shows administration order operation is exactly the root node of management object example, i.e. node 1, now whole management object example is deleted.
As preferred embodiment, in Target element, do not comprise that it is exactly the root node of management object example that LocURI element also can be expressed the node of administration order operation, reaches the object of the whole management object example of deletion of node 1.
Step 504, device management server sends above-mentioned delete command to facility management client.
Be illustrated in figure 6 present device management server transmitting apparatus administration order the 4th embodiment flow chart.
In this example, device management server transmits as the Replace administration order in embodiment bis-, and the destination address in its Target element is ./Inbox node, represents that server upgrades a management object example by inbox function.This device management tree as shown in Figure 4.
Step 601, Filter element in the Replace administration order issuing, (characteristic node is ServerID in this example to write management object example aspects nodal information, the nodal value of characteristic node is www.sonera.fi-8765), show the node 1 that TNDS object that in order, Data element comprises will add to.It in Item/Data element, is the management object example to device management tree to be updated, wherein <NodeName><NodeN ame/> represents that the root node name of management object example is called sky, because server is not known the concrete locating information of this example, so do not specify.
As preferred embodiment, in TNDS object, also can comprise management object example aspects nodal information, for example node ServerID and nodal value www.sonera.fi-8765 thereof are comprised at TNDS object, so the 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 administration order extract management object instance characteristic node information from TNDS object.
Step 602 adds management object locating information in the RTProperties/Type element of TNDS object root node, i.e. management object mark.
Step 603, in Data element, comprise the target operation object that administration order need to operate, be TNDS object, comprising needing the nodal information of operation as <NodeName>AAuthPrefLEssT.LTss T.LT/NodeName> etc.
Step 604, device management server sends above-mentioned replace command to facility management client.
As preferred embodiment, the Replace administration order in this example can not comprise Target element, does not comprise destination address.
Be illustrated in figure 7 present device management server transmitting apparatus administration order the 5th embodiment flow chart.
Server need to be replaced as the value of node AAuthType in 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 example is node 1, and the root node of also not knowing to manage subtree example 2 is nodes 2, using on the basis of management object and management object example aspects nodal information, re-use management subtree example locating information, as AAuthLevel node and nodal value thereof in figure, the particular location that inquires this node of AAuthType is configured simultaneously.
Step 701, in this replace command, writes management object locating information at Item/MOID element.Using management object mark (MOID) to be used as the locating information of management object, is urn:oma:mo:oma-dm-dmacc:1.0 in this example.
Step 702, in Item/MOInstID element, write management object example aspects nodal information, be characteristic node and nodal value thereof, <MOInstID>ServerID in this example? value=www.sonera.fi-8765</MOInstIDGreatT.Gr eaT.GT, ServerID in this example is characteristic node, and www.sonera.fi-8765 is this characteristic node value.
Step 703, in Item/SubMOInstID element, write the characteristic node information of management subtree example, in Item/SubMOInstID element, write characteristic node and the nodal value thereof in subtree, <SubMOInstID>AAuthLevel in this example? value=SRVCRED</SubMOInstID>, the characteristic node that wherein AauthLevel is subtree, SRVCRED is the nodal value of AauthLevel characteristic node.
Step 704, in Taget/LocURI element, write the relative URI of object run node, be <Target><LocURIG reatT.GreaT.GTAAuthType</LocURIGreatT.GreaT .GT</Target> in this example, wherein running node is AauthType.In Data element, write HTTP-BASIC as the data that will replace.
Step 705, device management server sends above-mentioned replace command to facility management client.
As preferred embodiment, the locating information of management subtree example can have multiple, has multiple SubMOInstID, for locating the more management subtree example 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 Target element.
Be illustrated in figure 9 present device management server transmitting apparatus administration order device example structure figure.
Comprise order generation unit 901 and transmitting element 902.
Described order generation unit 901 is for adding locating information, management object example aspects nodal information and the target operation object information of management object in described administration order; Described transmitting element 902 is for sending above-mentioned administration order by described transmitting element.
In the administration order that described order generation unit 901 issues at server, add the locating information of management object, this management object locating information comprises for management object of unique identification, finds this management object for terminal 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 example, find management object example for terminal according to this management object example aspects nodal information; Also add target operation object information, this target operation object information comprises object run nodal information and TNDS object information, find the node that will operate for terminal according to this object run nodal information, or find the management subtree example that will operate by this TNDS object information.Send described administration order by described transmitting element 902.
Be that present device administrative client is according to the first embodiment flow chart of device management command localizing objects operand as shown in figure 10.
Step 1001, obtains the administration order that comprises management object locating information, management object example aspects nodal information and target operation object information that device management server sends.
Step 1002, operates described target operation object according to described administration order.
By above-described embodiment, different facility management client can be according to same device management command localizing objects operand.
Be the specific embodiment flow chart of step 1002 in present device administrative client localizing objects operand as shown in figure 11.Step 1101, obtains a URI of the management object example root node mating with described management object locating information.
Step 1102, the characteristic node information of management object example corresponding with a described URI described management object example aspects nodal information is matched (utilizing characteristic node and nodal value thereof to mate), obtain the 2nd URI of the management object example root node that the characteristic node that the match is successful is corresponding
Step 1103, according to the target operation object information in described administration order and described the second unified resource mark, operates described target operation object.
As preferred embodiment, in step 1101, if directly stored the mark of management object and the correspondence relationship information of management object position in facility management client, and the correspondence relationship information of management object position and each management object example, position fixing process is different, and facility management client directly finds corresponding father node URI 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 example:
Table 1
| Management object identification information | Father node URI | Management object example |
| urn:oma:mo:oma-dm-dmacc:1.0 | ./MngmtSvr | 1 |
| urn:oma:mo:oma-dm-dmacc:1.0 | ./MngmtSvr | 2 |
| urn:oma:mo:oma-scomo:1.0 | ./Application/Software | 2 |
| urn:oma:mo:oma-scomo:1.0 | ./Application/Software | 3 |
| urn:oma:mo:oma-lawmo:1.0 | ./Mngmet/LockAndWipe | 1 |
As preferred embodiment, described target operation object comprises, object run node and TNDS object.
Be that present device administrative client is according to the second embodiment flow chart of device management command localizing objects operand as shown in figure 12.
Be directed to the replacement management order that device management server sends, as shown in Figure 4, facility management client is handled as follows the device management tree of described facility management client:
Comprise step 1201, facility management client receives described replace command.
Step 1202, in the position of the device management tree coupling DMAcc of facility management client management object, utilizes management object locating information urn:oma:mo:oma-dm-dmacc:1.0 to mate in this example.Matched N (N>0) management object example, for example root node of these management object examples is node 1,2,3 etc.Facility management client is obtained the URI (being an above-mentioned URI) of these example root nodes.
Step 1203, according to these URI, facility management client recycling management object example aspects nodal information mates each management object example, mate the characteristic node ServerID in each example, judge whether its nodal value equals www.sonera.fi-8765, if equal, facility management client is obtained the management object example root node that this node is corresponding, be node 1 in this example, facility management client is obtained the URI (being the 2nd above-mentioned URI) of node 1.
Step 1204, facility management client is taking the URI of node 1 as benchmark, object run node AAuthPref to facility management client device management tree operates, the relative URI of the URI of node 1 and object run node is coupled together, then carry out replacement operation, the value of former AAuthPref node is replaced with to the content in Data element in replace command.
As preferred embodiment, for above-mentioned steps 1202 and 1203, facility management client can be distinguished according to the sequencing of arrangement of elements in order the order of position fixing process in the time that operational order is resolved, for example in previous example, management object locating information comes foremost (being the information in TargetParent element), terminal is first processed it, so just realize the first object of orientation management object, namely 1202 steps above.Can certainly determine by other supplementary the order of position fixing process, for example in administration order, use an element S equenceItem, in this element, obtain locating information, management object example aspects nodal information and the target operation object information of management object, terminal can order processing locating information.The method of distinguishing position fixing process order here is also suitable in other parts of the present invention, follow-up repeating no more.
Be that present device administrative client is according to the 3rd embodiment flow chart of device management command localizing objects operand as shown in figure 13.
If server need to be deleted certain management object example, for example DMAcc management object example 1 in Fig. 4, described facility management client is handled as follows flow process:
Step 1301, facility management client receives described delete command.
Step 1302, in the position of the device management tree coupling DMAcc of facility management client management object, utilizes management object locating information urn:oma:mo:oma-dm-dmacc:1.0 to mate in this example.Matched N (N>0) management object example, for example root node of these management object examples is node 1,2,3 etc.Facility management client is obtained the URI of these example root nodes.
Step 1303, according to these URI, facility management client recycling management object example aspects nodal information mates each management object example, mate the characteristic node ServerID in each example, judge whether its nodal value equals www.sonera.fi-8765, if equal, facility management client is obtained the management object example root node that this node is corresponding, be node 1 in this example, facility management client is obtained the URI of node 1.
Step 1304, facility management client is taking the URI of node 1 as benchmark, owing in Target/LocURI element being sky, the node of the administration order operation that representative is deleted is the root node of management object example, so the object run node 1 of sweep equipment administrative client device management tree in this step, now the node 1 of whole management object example and child node thereof are all deleted.
As preferred embodiment, in Target element, do not comprise LocURI element, also node 1 and child node thereof all can be deleted.
Be that present device administrative client is according to the 4th embodiment flow chart of device management command localizing objects operand as shown in figure 14.
What in this example, facility management client received is as the Replace administration order in the second embodiment of facility management client receiving management order, destination address in its Target is ./Inbox node, and indication equipment administrative client is by upgrading a management object example to the administration order that is sent to inbox.The device management tree of this facility management client as shown in Figure 4.
Step 1401, facility management client receives described replace command.
Step 1402, in the position of the device management tree coupling DMAcc of facility management client management object, utilizes management object locating information urn:oma:mo:oma-dm-dmacc:1.0 to mate in this example.Matched N (N>0) management object example, for example root node of these management object examples is node 1,2,3 etc.Facility management client is obtained the URI of these example root nodes.
Step 1403, according to these URI, facility management client recycling management object example aspects nodal information mates each management object example, mate the characteristic node ServerID in each example, judge whether its nodal value equals www.sonera.fi-8765, if equal, facility management client is obtained the management object example root node that this node is corresponding, be node 1 in this example, facility management client is obtained the URI of node 1.In TNDS object, comprise described management object example aspects nodal information.
Step 1404, facility management client, taking the URI of node 1 as benchmark, is replaced described management object example corresponding to characteristic node that the match is successful by the TNDS object in Data.
As preferred embodiment, this routine administration order does not comprise Target element, does not comprise destination address, can realize above-mentioned location, replacement function yet.
Be that present device administrative client is according to the 5th embodiment flow chart of device management command localizing objects operand as shown in figure 15.
As shown in Figure 8, facility management client receives the corresponding administration order of device management server to the device management tree of facility management client, is replace command in this example, replaces the value of node AAuthType.
Comprise step 1501, facility management client receives described replace command.
Step 1502, in the position of the device management tree coupling DMAcc of facility management client management object, utilizes the management object locating information urn:oma:mo:oma-dm-dmacc:1.0 in MOID element to mate in this example.Matched N (N>0) management object example, for example root node of these management object examples is node 1,3 etc.Facility management client is obtained the URI of these example root nodes.
Step 1503, according to these URI, management object example aspects nodal information in facility management client recycling MOInstID element mates rope to each management object example, mate in this example the characteristic node ServerID in each example, judge whether its nodal value equals www.sonera.fi-8765, if equal, facility management client is obtained the management object example root node that this node is corresponding, be node 1 in this example, facility management client is obtained the URI of node 1.
Step 1504, according to the URI of management object example 1, the locating information of the management subtree example in facility management client recycling SubMOI nstID element is mated each management subtree example, mate the characteristic node AAuthlevel in each subtree, judge whether its nodal value equals SRVCRED, if equal, facility management client is obtained the root node of the management subtree example that this AAuthlevel node is corresponding, be now node 2, facility management client is obtained the URI of node 2.
Step 1505, judges whether to also have lower layer-management subtree example locating information, if had, enters step 1506, otherwise enters step 1507.
Step 1506, find lower layer-management subtree example positions according to definite management subtree example URI and lower layer-management subtree example aspects nodal information, the characteristic node information that facility management client recycles the management subtree example in next SubMOInstID element is mated each management subtree example of lower floor, mate the characteristic node in each lower layer-management subtree example, judge whether its nodal value equals default nodal value, if equal, facility management client is obtained the management subtree example root node that this node is corresponding, facility management client is obtained the URI of the management subtree example root node that the characteristic node that the match is successful is corresponding, then return to step 1505.
Step 1507, facility management client is taking the URI of node 2 as benchmark in this example, and to object run node, AAuthType operates, and the relative URI of the URI of node 2 and object run node is coupled together, and then carries out replacement operation.
Be present device administrative client example structure figure as shown in figure 16.
Comprise receiving element 1601, processing unit 1602;
Described receiving element 1601, sends the administration order of the locating information, management object example aspects nodal information and the target operation object information that comprise management object for receiving equipment management server;
Described processing unit 1602, for operating described target operation object according to described administration order.
By above-described embodiment, different facility management client can be according to same device management command localizing objects operand.
Be the described processing unit 1602 example structure figure of present device administrative client as shown in figure 17.
Comprise management object positioning unit 1701, management object example positioning unit 1702, target operation object unit 1703.
Described management object positioning unit 1701, for obtaining a URI of the management object example root node mating with described management object locating information, a URI can be multiple or one or can be also the zero not finding.
Described management object example positioning unit 1702, described management object example aspects nodal information is matched with the characteristic node information that described the first unified resource identifies corresponding management object example, obtain the 2nd URI of the management object example root node that the characteristic node that the match is successful is corresponding.
Described target operation object unit 1703, described target operation object unit, according to the target operation object information in described administration order and described the second unified resource mark, operates described target operation object.As preferred embodiment, also comprise management subtree example positioning unit, be connected in described management object example positioning unit 1702, according to the characteristic node information of the management subtree example in described administration order, the characteristic node of coupling from each management subtree example of the management object example root node of described management object example positioning unit output, the unified resource of obtaining the management subtree example root node that this characteristic node is corresponding identifies (i.e. the 2nd URI).
As preferred embodiment, also there is a mapping table in described facility management client, described management object positioning unit is according to a URI of described management object locating information and described mapping table match management object.
Be the described target operation object unit 1703 example structure figure of present device administrative client as shown in figure 18.
Described target operation object unit also comprises link block 1801 and Executive Module 1802, and described link block 1801, for the relative URI of described the 2nd URI and object run node is coupled together, obtains the URI of object run node;
Described Executive Module 1802 is for this object run node is operated, or management object example corresponding to characteristic node that described in TNDS object is replaced, the match is successful.
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 in the situation of more specific location information of not understanding management object once property location operational administrative object, while managing multiple terminal especially at the same time, can avoid each terminal inner structure and the inconsistent problem of instance name; Facility management client can receive after incomplete administration order, find corresponding object run node in this facility management client device management tree, save and device management server communication steps repeatedly, saved the efficiency of Internet resources and raising device management server configuration device administrative client device management command.
Above-described embodiment; object of the present invention, technical scheme and beneficial effect are further described; institute is understood that; the foregoing is only the specific embodiment of the present invention; the protection range being not intended to limit the present invention; within the spirit and principles in the present invention all, any amendment of making, be equal to replacement, improvement etc., within all should being included in protection scope of the present invention.
Claims (14)
1. the method for a target operation object location, it is characterized in that the method comprises, obtain the administration order that device management server sends, described administration order comprises management object locating information, management object example aspects nodal information and target operation object information; According to described administration order, described target operation object is operated;
The locating information of described management object is for unique management object of mark, management object example aspects nodal information is for example corresponding to management object described in unique identification, and described target operation object information is used for representing object run node or tree and description serializing TNDS object;
Describedly according to described administration order, described target operation object is operated specifically and is comprised:
Determine the second unified resource mark according to described management object locating information, management object example aspects nodal information;
Described the second unified resource mark is coupled together with the relatively uniform resource identification of object run node, obtain the unified resource mark of object run node, and this object run node is operated; Or described TNDS object is replaced to described the second unified resource and identify corresponding management object example.
2. the method for target operation object according to claim 1 location, is characterized in that, described facility management client is obtained described management object example aspects nodal information from the TNDS object of described administration order;
Or in the filtration element from described administration order, obtain described management object example aspects nodal information.
3. the method for target operation object according to claim 1 location, is characterized in that, describedly determines that according to described management object locating information, management object example aspects nodal information the second unified resource mark comprises:
Obtain the first unified resource mark of the management object example root node mating with described management object locating information;
Described management object example aspects nodal information is matched with the characteristic node information that described the first unified resource identifies corresponding management object example, obtain the second unified resource mark of the management object example root node that the characteristic node that the match is successful is corresponding.
4. the method for target operation object according to claim 3 location, it is characterized in that, described according to described management object example aspects nodal information, obtain after identifying the second unified resource mark of corresponding management object example root node with described the first unified resource and also comprise
According to the characteristic node information of the management subtree example in described administration order, mate the characteristic node in each management subtree example of the management object example root node lower floor in described facility management client, obtain the second unified resource mark of the management subtree example root node that the characteristic node that the match is successful is corresponding.
5. the method for target operation object according to claim 1 location, is characterized in that,
According to the unified resource mark of the mapping table match management object in described management object locating information and facility management client;
Or according to described management object locating information, the unified resource of match management object mark in device management tree.
6. the method for target operation object according to claim 1 location, is characterized in that, if the target operation object information in described administration order is empty, target operation object is that described the second unified resource identifies corresponding management object example.
7. the method for target operation object according to claim 1 location, is characterized in that, obtains in order locating information, management object example aspects nodal information and the target operation object information of management object in described administration order; Or in described administration order, obtain the element of order of representation, the locating information of obtaining management object, management object example aspects nodal information and the target operation object information of order from this element.
8. the method for target operation object according to claim 1 location, it is characterized in that, obtain management object locating information, management object example aspects nodal information and the target operation object information of described administration order from the ./Inbox node of device management tree.
9. the method for target operation object according to claim 1 location, it is characterized in that, if the target operation object information in described administration order is empty, determine the second unified resource mark according to described management object locating information, management object example aspects nodal information;
Described the second unified resource is identified to corresponding management object example as target operation object.
10. a facility management client, is characterized in that this device comprises, receiving element, processing unit;
Described receiving element, sends the administration order of the locating information, management object example aspects nodal information and the target operation object information that comprise management object for receiving equipment management server;
Described processing unit, for operating described target operation object according to described administration order;
The locating information of described management object is for unique management object of mark, management object example aspects nodal information is for example corresponding to management object described in unique identification, and described target operation object information is used for representing object run node or tree and description serializing TNDS object;
Described processing unit comprises target operation object unit, and described target operation object unit, for the second unified resource mark is coupled together with the relatively uniform resource identification of object run node, obtains the unified resource mark of object run node; This object run node is operated, or TNDS object is replaced to described management object example corresponding to characteristic node that the match is successful, and wherein said the second unified resource mark is determined according to described management object locating information, management object example aspects nodal information.
11. a kind of facility management client according to claim 10, is characterized in that described processing unit also comprises:
Management object positioning unit, management object example positioning unit
Described management object positioning unit, for obtaining the first unified resource mark of the management object example root node mating with described management object locating information;
Described management object example positioning unit, described management object example aspects nodal information is matched with the characteristic node information that described the first unified resource identifies corresponding management object example, obtain the described second unified resource mark of the management object example root node that the characteristic node that the match is successful is corresponding.
12. a kind of facility management client according to claim 11, it is characterized in that, also have a mapping table in described facility management client, described management object positioning unit is according to the unified resource mark of described management object locating information and described mapping table match management object.
13. a kind of facility management client according to claim 11, it is characterized in that, also comprise management subtree positioning unit, be used for according to the characteristic node information of the management subtree example of described administration order, the characteristic node of coupling from each management subtree example of the each management object example root node lower floor of described management object example positioning unit output, obtains the unified resource mark of the management subtree example root node that the characteristic node that the match is successful is corresponding.
14. 1 kinds of device management servers, is characterized in that this server comprises, order generation unit and transmitting element;
Described order generation unit is for adding locating information, management object example aspects nodal information and the target operation object information of management object in described administration order; Described transmitting element is for sending above-mentioned administration order by described transmitting element, determine the second unified resource mark so that receive the facility management client of described administration order according to described management object locating information, management object example aspects nodal information, described the second unified resource mark is coupled together with the relatively uniform resource identification of object run node, obtain the unified resource mark of object run node, and this object run node is operated; Or described TNDS object is replaced to described the second unified resource and identify corresponding management object example;
The locating information of described management object is for unique management object of mark, management object example aspects nodal information is for example corresponding to management object described in unique identification, and described target operation object information is used for representing object run node or tree and description serializing TNDS object.
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 CN102546237A (en) | 2012-07-04 |
| CN102546237B true 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) |
Families Citing this family (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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102546237A (en) | 2012-07-04 |
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 | |
| KR101495341B1 (en) | Method and System for assigning IDs to software compoents | |
| CN101421978A (en) | Device management system for remotely accessing terminal equipments | |
| CN101345657B (en) | Method and system for cluster management of multiple network elements based on simple network management protocol | |
| CN101677441A (en) | Method, device and system of authorization control | |
| US20090318125A1 (en) | Method and system for provisioning content in a mobile device management system | |
| US20100199291A1 (en) | Method, system and apparatus for transmitting remote procedure call commands | |
| CN102546237B (en) | Device management server, client and target operation object positioning method | |
| CN102571390B (en) | Equipment management method, equipment and system | |
| CN102547667B (en) | Method and device for device management | |
| CN101753604B (en) | Method for reporting equipment information, user terminal and server | |
| CN101442791B (en) | Method and apparatus for sending node information | |
| CN101547460A (en) | Method, device and system for processing DDF information | |
| CN101351046B (en) | Method for activating terminal equipment software component, terminal equipment and equipment management server |
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. |