CN101442791B

CN101442791B - Method and apparatus for sending node information

Info

Publication number: CN101442791B
Application number: CN2008102411597A
Authority: CN
Inventors: 宋悦; 王睿; 刘海涛
Original assignee: Huawei Device Co Ltd
Current assignee: Global Innovation Polymerization LLC; Tanous Co
Priority date: 2008-12-26
Filing date: 2008-12-26
Publication date: 2010-08-25
Anticipated expiration: 2028-12-26
Also published as: CN101442791A

Abstract

The embodiment of the invention provides a node information transmission method and device. The method comprises: receiving node establishment message from equipment management server; establishing corresponding node in terminal equipment management tree according to node establishment message; transmitting the node information of corresponding node to equipment management server. The invention can simply and conveniently keep node information symmetry of server and terminal in equipment management, which facilitates subsequent management operation.

Description

A kind of sending method of nodal information and device

Technical field

The present invention is about wireless communication field, and the equipment control specification technique in the radio communication is a kind of sending method and device of nodal information concretely.

Background technology

Open mobile alliance device management standard V1.2 (Open Mobile Alliance DeviceManagement V1.2 is hereinafter to be referred as the DM standard) is that standard is unified in the equipment control that OMA DM WG formulates.The DM standard provides a kind of lower cost solution, be used for third party management and environment and configuration information in the wireless network terminal equipment (such as the functional object of mobile phone terminal and terminal) are set, solve the problem that these network equipments in use run into, carry out the operation such as installation, upgrading of software and firmware by OTA (over the air wireless network) mode, and hommization more and personalized service are provided, improve user experience.Wherein, the third party can be mobile operator, the information management department of service provider or partner.

As shown in Figure 1, be the overall structure figure of existing DM standard, wherein, the DM agency (DM Agent) on the terminal equipment is used to explain and carry out the administration order that the DM server issues.The DM management tree of storing on the terminal equipment can be considered to the interface that a DM server manages terminal equipment by the DM agreement.Wherein the DM management tree comprises some basic management object (MO, ManagementObject), the DM server reaches the purpose of control terminal management object by the operation to the management tree object, and operational order is obtained (Get), replaces (Replace), carries out (Exec), duplicated (Copy), deletion (Delete) etc.Wherein, described basic management object has the sign of oneself, is called management object sign (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 each node all has the attribute of oneself.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.Also exist the unnamed node of a class in management tree, it plays the effect of placeholder, and when server or terminal were 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 example.If this node just in time is the root node of MO, then be called the MO example.

All belong to internal node as the connection parameter management object among Fig. 2, equipment information management object etc., and device id, manufacturer, terminal models all belong to leaf node.OMA DM normalized definition the property value of a set of equipment management tree node, be used for node is described, each property value mainly comprises: control of authority tabulation, type, form, title, size, position (unified resource sign, URI, Unified ResourceIdentifier) etc.

Because the competition of device fabrication manufacturer, dissimilar terminals has different internal structures, the attributes of the structure of management object and its node that comprises etc. are also inequality, therefore before the DM server can manage terminal equipment, need a kind of method of regulation that the manufacturer of equipment can be described terminal equipment, and inform the DM server, like this, the DM server just can manage terminal according to this description, and this describing method is called DDF (device description framework).

The DM specification technique comprises two stages, and wherein first stage is called Bootstrap (initialization, or guiding), this stage can make an equipment never the dummy status of parameter configuration be transformed into can be to the state of DM server initiating management session.Except basic link information, equipment and user use configuration information and also can be configured in the Bootstrap process.Second stage is management phase, just can manage or the setting of information terminal equipment at this stage server.

Bootstrap can realize that a kind of is CP by two kinds of methods, i.e. client configuration, and a kind of is DM, promptly uses the message of DM to come initialization.

OMA DM has defined DMAcc (equipment control account number) standard management object, this object storage be terminal and server needed relevant parameter when connecting, as connecting with reference to, server address and authentication information etc.If the information spinner of DMAcc disposes by the Bootstrap technology.

OMA DM has also defined Inbox (inbox) standard management object, uses this object, when server adds management object to terminal, can not provide the absolute path of interpolation, and informs that terminal MOI allows the path of the own analysis object of terminal.

The prerequisite that the DM server manages terminal is the management tree relevant information that needs to understand on the current terminal, the for example position of node, title and nodal value etc., but terminal these information of notification server are not perhaps unilaterally revised these information sometimes, cause both sides' information asymmetry.

Prior art has a kind of method, and to be server obtain order or search command are searched a node on management tree position, i.e. URI by transmission.

In realizing process of the present invention, the inventor finds that there are the following problems at least in the prior art: prior art needs server to send order and provides some node relevant informations simultaneously, the relevant information of terminal search node on management tree could obtain node location then, this makes at first both sides need set up a session and finishes this search mission that next need design a search utility on terminal and spended time is carried out this program.So this technical scheme is the way of a kind of poor efficiency and waste resource.

Summary of the invention

The object of the present invention is to provide a kind of sending method of nodal information, in order to solve between existing server and the terminal to obtaining the problem that nodal information causes the wasting of resources.

The object of the present invention is to provide a kind of dispensing device of nodal information, in order to solve between existing server and the terminal to obtaining the problem that nodal information causes the wasting of resources.

To achieve these goals, the embodiment of the invention provides a kind of sending method of nodal information, and this method comprises: slave unit management server receiving node is set up message; Set up message according to described node and in terminal equipment management tree, set up respective nodes; Send the nodal information of described respective nodes to described device management server; Wherein: described node is set up and is comprised characteristic node information or management object sign in the message, and this characteristic node information or management object sign are used to identify described respective nodes.

To achieve these goals, the embodiment of the invention provides a kind of dispensing device of nodal information, and this device comprises: node is set up the message acquiring unit, is used for slave unit management server receiving node and sets up message; Obtain described node and set up characteristic node information in the message or management object sign; This characteristic node information or management object sign are used to identify described respective nodes; Node is set up the unit, is used for setting up message according to described node and sets up node corresponding in terminal equipment management tree; The nodal information transmitting element is used for sending to described device management server the nodal information of described respective nodes.

The beneficial effect of technique scheme is, can be easy make server end in the equipment control and terminal easily nodal information keep symmetry, convenient follow-up bookkeeping.

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 limitation of the invention.In the accompanying drawings:

Fig. 1 is the overall structure figure of open mobile alliance device management standard;

Fig. 2 is the configuration state schematic diagram of each management object in the management tree in the existing terminal equipment;

The flow chart of the sending method of the nodal information that Fig. 3 provides for the embodiment of the invention;

The flow chart of the sending method of the nodal information that Fig. 4 provides for another embodiment of the present invention;

The flow chart of the sending method of the nodal information that Fig. 5 provides for another embodiment of the present invention;

Fig. 6 is the flow chart of the sending method of further embodiment of this invention nodal information;

The structure chart of the dispensing device of the nodal information that Fig. 7 provides for the embodiment of the invention.

Embodiment

For making the purpose, technical solutions and advantages of the present invention clearer,, the present invention is described in 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 a limitation of the invention.

As shown in Figure 3, be the flow chart based on the nodal information symmetry approach of terminal equipment that the embodiment of the invention provides, this method comprises:

Step 301, slave unit management server receiving node is set up message; No matter be in the Bootstrap stage or at management phase, node on the terminal is generally created by server, and may produce some new nodal informations in the constructive process, at this moment, it is follow-up again to the trouble of terminal inquiry that terminal has just been saved server to server feedback these information immediately.Wherein, in the Bootstrap stage, according to prior art, server carries out Bootstrap to terminal earlier, and this moment, server can be CP message or DM message to the message that terminal sends.At management phase, server is directly set up instruction to the terminal sending node.

Step 302 is set up message according to described node and set up node corresponding in terminal equipment management tree; (especially DMAcc management object interdependent node);

Step 303, send the nodal information of described respective nodes to described device management server, in the Bootstrap stage, relevant information after terminal initiation session notification server node is created, at management phase, the relevant information after terminal is created by the mode notification server node of answer or asynchronous answer synchronously.

The beneficial effect of the foregoing description is, can be easy make server end in the equipment control and terminal easily nodal information keep symmetry, convenient follow-up bookkeeping.

Embodiment one

In the Bootstrap stage, server sends CP message, and is specific as follows:

<wap-provisioningdoc?version＝″1.0″>

<characteristic?type＝″APPLICATION″>

<parm?name＝″APPID″value＝″w7″/>

＜!--APPID represents that this message is to use at the DM on the terminal--〉

<parm?name＝″PROVIDER-ID″value＝″com.mgmtsrv.manage″/>

＜!--PROVIDER-ID represents the DM server identification--〉

……

</characteristic>

</wap-provisioningdoc>

Server sends under the situation of CP message, description according to prior art, terminal can be mapped to the related parameter values in the CP message on the management tree, for example parameter values such as APPID, PROVIDER-ID is mapped in the AppID of a newly-generated DMAcc management object and the ServerID node and goes.This moment, terminal then can be named the root node of this DMAcc management object, had so just generated the nodal information of a server the unknown.

In order to make the instant nodal information of understanding described the unknown of server, these information of notification server in the session that terminal can be initiated after Bootstrap.Be an example below:

<SyncML?xmlns＝′SYNCML:SYNCML?1.2′>

<Alert>

＜Data〉1224＜/Data〉＜!--client event--〉

<Item>

<LocURI>./DMServer/Server1/ServerID</LocURI>

＜!--node path that feeds back for terminal among the LocURI--〉

</Source>

…

<Data>com.mgmtsrv.manage</Data>

＜!--nodal value that feeds back for terminal among the Data--〉

</Item>

</Alert>

</SyncBody>

</SyncML>

In this conversation message, terminal orders the nodal information of notification server Bootstrap some server the unknowns afterwards by Alert, wherein in Item/Source/LocURI, carried a node URI, be ./DMServer/Server1/ServerID, in Item/Data, carried nodal value again, be com.mgmtsrv.manage, by these two information, server just can know that account number parameter relevant with com.mgmtsrv.manage in the CP message has been mapped in this management object example of Server1, this is a DMAcc management object example, the URI of this example is ./DMServer/Server1, so just make server know the position of relevant parameter mapping in the Bootstrap message, made things convenient for the follow-up management of server these parameters.

Wherein, suppose that server can know the father node URI of this terminal D MAcc management object, for example know by DDF, then can include only the title of management object example in the nodal information that terminal sends, in this example, terminal only sends Server1 and these two information of server identification com.mgmtsrv.manage get final product for example.

And only comprised the relevant parameter of a server in the hypothesis Bootstrap message, the relevant account number parameter that for example only comprises com.mgmtsrv.manage, then terminal can change ./DMServer/Server1 and these two information of urn:oma:mo:oma-dm-dmacc:1.0 of sending into, wherein the latter is the MOI of DMAcc management object, and server can know that also the account number parameter relevant with com.mgmtsrv.manage has been mapped on this management object example of Server1 like this.Know under the condition of terminal D MAcc management object father node URI that at server terminal only sends Server1 and these two information of urn:oma:mo:oma-dm-dmacc:1.0 get final product equally.

As shown in Figure 4, the node that the terminal judges server sends is set up the title that does not comprise node in the message, then terminal names the back by sending the title of characteristic node this node of information notification in device management tree to node voluntarily, as in the above-described embodiments, the nodal information that the node that server sends is set up message and terminal feedback all comprises characteristic node information " com.mgmtsrv.manage ", and the title that also comprises the node of foundation in the nodal information of terminal feedback, server is called Server1 with regard to the name of node in terminal equipment management tree that gets cicada foundation by characteristic node information " com.mgmtsrv.manage " like this.

Wherein, if setting up, node has only a management object example in the message, then terminal also can identify the title of node in device management tree that MOI informs foundation by management object, because each management object has the management object sign (MOI) of oneself, in order to management object of unique sign, so server also can obtain the title of node in terminal equipment management tree of foundation by this MOI.

Promptly, described node is set up and is comprised characteristic node information or management object sign in message and the nodal information, this characteristic node information or management object sign are used to identify described respective nodes, if at this moment the described node of terminal judges is set up the title that message does not comprise node, the nodal information of the described respective nodes of then described transmission comprises: the nodename that sends described respective nodes.

Embodiment two

Carry out Bootstrap if server sends DM message to terminal earlier, by description of the Prior Art, DM message is specific as follows in this step:

<SyncML?xmlns＝′SYNCML:SYNCML1.2′>

<Add>

<Item>

<Target><LocURI>./Inbox</LocURI></Target>

＜!--Target is illustrated in and adds node among the Inbox--〉

…

<Data>

<Node>

<NodeName>ServerX</NodeName>

＜!--top is DMAcc management object title--〉

…

<Type><DDFName>urn:oma:mo:oma-dm-dmacc:1.0</DDFName></Type>

＜!--top is DMAcc management object sign--〉

</RTProperties>

<Node>

<NodeName>AppID</NodeName>

…

</Node>

<Node>

<NodeName>ServerID</NodeName>

…

<Value>com.mgmtsrv.manage</Value>

＜!--the value of ServerID is com.mgmtsrv.manage--〉

</Node>

…

</Node>

</MgmtTree>

</Data>

</Item>

</Add>

</SyncBody>

</SyncML>

(annotate: in the example of DM message,, adopted the xml form, in the Bootstrap of reality message, should adopt the wbxml form, omitted some irrelevant parts in addition in the example for the implication of distinct message.)

After the Bootstrap message of server transmission based on DM, according to the description of prior art, terminal can rename management object, for example DMAcc management object title ServerX in the above-mentioned example is renamed RNTO Server1.Perhaps, server is not just specified the title of management object root node in Bootstrap message, and at this moment terminal can be specified voluntarily.Under the both of these case, all be equivalent to the nodal information that terminal has generated a server the unknown.

Terminal can be used the nodal information of method notification server the unknown identical with embodiment one after the Bootstrap.Terminal can also use the method for Generic Alert (generic alert) to reach same purpose.Be an example below:

<SyncML?xmlns＝′SYNCML:SYNCML?1.2′>

<Alert>

＜Data〉1226＜/Data〉＜!--generic alert--〉

<Item>

<LocURI>./DMServer/Server1/ServerID</LocURI>

＜!--node path that feeds back for terminal among the LocURI--〉

</Source>

<Meta>

<Type?xmlns＝″syncml:metinf″>

Reversed-Domain-Name:

org.openmobilealliance.BootstrapComplete.dmacc

</Type>

＜!--message identification among the Type the following Data element data type of carrying--〉

<Format?xmlns＝″syncml:metinf″>chr</Format>

<Mark?xmlns＝″syncml:metinf″>critical</Mark>

</Meta>

<Data>com.mgmtsrv.manage</Data>

＜!--nodal value that feeds back for terminal among the Data--〉

</Item>

</Alert>

</SyncBody>

</SyncML>

From top generic alert, server has been recognized ./DMServer/Server1/ServerID and these two information of com.mgmtsrv.manage equally, by these two information, server just can know that management object root node title ServerX relevant with this ServerID of com.mgmtsrv.manage in the Bootstrap message is by RNTO Server1, its URI is ./DMServer/Server1, so just make server know the position of ServerX management object example, made things convenient for the follow-up management of server it.

Also have an Item/Type element in generic alert, it has indicated the data type that the Data element carries, and is specially in this example:

Reversed-Domain-Name:org.openmobilealliance.BootstrapComplete.dmacc

What this represented that this generic alert carries is the nodal information data of being sent by the DMAcc management object after Bootstrap finishes.

Suppose that server can know the father node URI of this terminal D MAcc management object, for example know by DDF, then can include only the title of management object example in the nodal information that terminal sends, in this example, terminal only sends Server1 and these two information of server identification com.mgmtsrv.manage get final product for example.

And only comprised the relevant parameter of a server in the hypothesis Bootstrap message, the relevant account number parameter that for example only comprises ServerX, then terminal can change ./DMServer/Server1 and these two information of urn:oma:mo:oma-dm-dmacc:1.0 of sending into, wherein the latter is the MOI of DMAcc management object, and server can know that also ServerX is renamed as Server1 like this.Know under the condition of terminal D MAcc management object father node URI that at server terminal only sends Server1 and these two information of urn:oma:mo:oma-dm-dmacc:1.0 get final product equally.

From as can be known above-mentioned, as shown in Figure 5, the method that the embodiment of the invention provides comprises: slave unit management server receiving node is set up message; Set up message according to described node and in terminal equipment management tree, set up respective nodes; Wherein, when setting up node in device management tree, terminal changes the title of node, and by sending the title of node in device management tree that characteristic node information ServerID or management object sign MOI informs foundation, as in the above-described embodiments, the nodal information that the node that server sends is set up message and terminal feedback all comprises characteristic node information " com.mgmtsrv.manage ", and also comprise the title of the node of foundation in the nodal information of terminal feedback, server just gets the title of node in terminal equipment management tree that cicada is set up by characteristic node information " com.mgmtsrv.manage " like this.

Embodiment three

Under the scene of embodiment two, also have a kind of method can realize the function of notification server unknown node information, the preorder step is identical with embodiment two, the message below adopting when terminal to server feedback node information:

<SyncML?xmlns＝′SYNCML:SYNCML?1.2′>

<Alert>

＜Data〉...＜/Data〉＜!--warning of certain type--〉

<Item>

<LocURI>./DMServer/Server1</LocURI>

＜!--node path that feeds back for terminal among the LocURI--〉

</Source>

…

<Data>./Inbox/ServerX</Data>

＜!--being the node path of the original appointment of service among the Data--〉

</Item>

</Alert>

</SyncBody>

</SyncML>

Adopt this message, server can learn that path (the comprising nodename) ./Inbox/ServerX of original appointment is becoming ./DMServer/Server1 through after the terminal processes.

From as can be known above-mentioned, the method that the embodiment of the invention provides comprises: slave unit management server receiving node is set up message; Set up message according to described node and in terminal equipment management tree, set up respective nodes; Wherein, when setting up node in device management tree, terminal changes the title of node, sending node is set up back nodal information and this node in described terminal equipment management tree and is set up title in the message to described device management server at node then, and described nodal information comprises the title of this node in terminal equipment management tree.Terminal also can be corresponding with the nodename in the terminal equipment management tree with the nodename of setting up in the message by such method.

Embodiment four

Terminal also might change some nodal values when treatments B ootstrap message, the Bootstrap message that for example terminal processes is following:

<SyncML?xmlns＝′SYNCML:SYNCML?1.2′>

<Add>

<Item>

<Target><LocURI>./Inbox</LocURI></Target>

＜!--Target is illustrated in and adds node among the Inbox--〉

…

<Data>

<Node>

<NodeName>ServerX</NodeName>

＜!--top is DMAcc management object title--〉

…

<Type><DDFName>urn:oma:mo:oma-dm-dmacc:1.0</DDFName></Type>

＜!--top is DMAcc management object sign--〉

</RTProperties>

<Node>

<NodeName>PrefConRef</NodeName>

<Value>./Inbox/Internet</Value>

＜!--being the value that connects with reference to PrefConRef among the Value--〉

</Node>

…

<NodeName>Internet</NodeName>

＜!--connection management object--〉

…

</Node>

</MgmtTree>

</Data>

</Item>

</Add>

</SyncBody>

</SyncML>

Message shows a child node PrefConRef under the ServerX node, its value is ./Inbox/Internet, the address of another management object, i.e. Internet connection management object in this value refer message.Terminal at first can leave Internet connection management object on the corresponding position of management tree in after receiving this Bootstrap message, for example under the ./Connectivity path, terminal is changed the value of PrefConRef more then, ./Inbox is replaced with ./Connectivity, if terminal again rename Internet connection management object be Internet234, then this moment PrefConRef value then change to ./Connectivity/Internet234.This has been equivalent to generate the nodal information of a server the unknown.Terminal is by a DM conversation message notification server, for example:

<SyncML?xmlns＝′SYNCML:SYNCML?1.2′>

<Alert>

＜Data〉1224＜/Data〉＜!--client event--〉

<Item>

<LocURI>./DMServer/Server1/PrefConRef</LocURI>

＜!--node path that feeds back for terminal among the LocURI--〉

</Source>

…

<Data>./Connectivity/Internet234</Data>

＜!--nodal value that feeds back for terminal among the Data--〉

</Item>

</Alert>

</SyncBody>

</SyncML>

The sending method of this similar embodiment one, server know that certain nodal value is changed by terminal after receiving message, and from as can be known above-mentioned, as shown in Figure 6, the method that the embodiment of the invention provides comprises: slave unit management server receiving node is set up message; Set up message according to described node and in terminal equipment management tree, set up respective nodes, wherein, change the nodal value of node when terminal is set up node in device management tree; The nodal information that terminal sends comprises this node and sets up the nodal value of back in described terminal equipment management tree.

Embodiment five

At Bootstrap stage and management phase, server can created some other nodes except that the management object root node on the terminal, the title of these nodes also may be named by terminal or be renamed, terminal is after renaming node, make server know the information of this node by sending the node URI and the node URI in device management tree of this node in setting up message, for example server sends following message:

<SyncML?xmlns＝′SYNCML:SYNCML1.2′>

Add>

<Item>

<Target><LocURI>./DMSerVer/Server1/AppAuth</LocURI></Target>

＜!--Target is illustrated in and adds node among the ./DMSerVer/Server1/AppAuth--〉

…

<Data>

<Node>

<NodeName>AppAuthX</NodeName>

＜!--top AppAuthX is the nodename of server appointment--〉

<Node>

<NodeName>AAuthLevel</NodeName>

＜!--AAuthLevel is a child node--〉

<Value>CLCRED</Value>

</Node>

…

</Node>

</MgmtTree>

</Data>

</Item>

</Add>

</SyncBody>

</SyncML>

Terminal finds that the last layer nodename of AAuthLevel is AppAuthX after receiving message, and terminal wishes it is renamed afterwards, for example called after AppAuth345.Terminal is fed back this information in replying message afterwards, as:

<SyncML?xmlns＝′SYNCML:SYNCML1.2′>

…

<SourceRef>./DMServer/Server1/AppAuth/AppAuthX</SourceRef>

＜!--the URI--that server issues 〉

<Item>

<LocURI>./DMServer/Server1/AppAuth/AppAuth345</LocURI>

＜!--reply the URI--of end eventually 〉

</Source>

</Item>

</Status>

…

</SyncBody>

</SyncML>

Wherein, terminal has provided the node URI that server issues in feedback message, and having provided node URI after the terminal rename, they are respectively ./DMServer/Server1/AppAuth/AppAuthX and ./DMServer/Server1/AppAuth/AppAuth345.Terminal is only feedback node name information, i.e. AppAuthX and AppAuth345 also.That is, the terminal sending node is set up back nodal information and this node in described terminal equipment management tree and is set up title in the message to described device management server at node, and described nodal information comprises the title of this node in terminal equipment management tree.

Wherein,, can provide its child node URI and its nodal value when then terminal is fed back if the name of certain node is called sky in the message that server issues, as:

<SyncML?xmlns＝′SYNCML:SYNCML1.2′>

…

<SourceRef>./DMServer/Server1/AppAuth</SourceRef>

<Item>

<LocURI>./DMServer/Server1/AppAuth/AppAuth345/

AAuthLevel</LocURI>

＜!--reply certain child node URI--of end eventually 〉

</Source>

<Data>CLCRED</Data>

＜!--replying the nodal value of end eventually--〉

</Item>

</Status>

…

</SyncBody>

</SyncML>

In this way, server also can recognize terminal feedback the AppAuth345 correspondence be which example.

The example that is to use Status to reply synchronously that provides in this example also can use equally the method for the asynchronous answer of generic alert under the situation of terminal processes overlong time, the content of feedback with above be similar.

Corresponding to the method for the maintenance DM tree node information symmetry of the above-mentioned proposition of the present invention, the invention allows for a kind of terminal equipment of correspondence, as shown in Figure 7, be the main composition structured flowchart of terminal equipment of the present invention, it mainly comprises:

Node is set up message acquiring unit 701, is used for slave unit management server receiving node and sets up message;

Node is set up unit 702, is used for setting up message according to described node and sets up node corresponding in terminal equipment management tree;

Nodal information transmitting element 703 is used for sending to described device management server the nodal information of described respective nodes.

In another embodiment of the present invention, described node is set up the message acquiring unit, also is used for obtaining characteristic node information or the management object sign that described node is set up message; This characteristic node information or management object sign are used to identify described respective nodes; Described nodal information transmitting element also comprises first subelement, and described first subelement is used to send described characteristic node information or management object sign.

In another embodiment of the present invention, described device also comprises: the nodename sending controling unit, be used to judge that described node sets up the title whether message comprises node, and if not, then trigger the nodal information transmitting element; Described nodal information transmitting element also comprises second subelement, and described second subelement is used for the triggering according to described nodename sending controling unit, sends the nodename of described respective nodes to described device management server.

In another embodiment of the present invention, described device also comprises: nodal value changes the unit, is used for changing the nodal value of described respective nodes when terminal equipment management tree is set up respective nodes; Described nodal information transmitting element also comprises the 3rd subelement, and described the 3rd subelement is used for the nodal value after described device management server sends described respective nodes change.

In another embodiment of the present invention, described device also comprises: nodename changes the unit, is used for changing the title of described respective nodes when terminal equipment management tree is set up respective nodes; Described nodal information transmitting element also comprises the 4th subelement, and described the 4th subelement is used for the title after described device management server sends described respective nodes change.

In another embodiment of the present invention, described device comprises that also nodename changes the unit, is used for changing the title of described respective nodes when terminal equipment management tree is set up respective nodes; Described nodal information transmitting element also comprises the 5th subelement, and described the 5th subelement is used for sending title after described respective nodes changes and this node are set up message at node nodename to described device management server.

In the above embodiment of the present invention, described node is set up message and is meant: client configuration message or device management message.Described node is set up the nodal information of back in described terminal equipment management tree and is sent by client event, generic alert or status command.

Above-described embodiment; purpose of the present invention, technical scheme and beneficial effect are further described; institute is understood that; the above only is the specific embodiment of the present invention; and be not intended to limit the scope of the invention; within the spirit and principles in the present invention all, any modification of being made, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.

Claims

1. the sending method of a nodal information is characterized in that, described method comprises:

Slave unit management server receiving node is set up message;

Set up message according to described node and in terminal equipment management tree, set up respective nodes;

Send the nodal information of described respective nodes to described device management server;

Wherein:

Described node is set up and is comprised characteristic node information or management object sign in the message, and this characteristic node information or management object sign are used to identify described respective nodes.

2. method according to claim 1 is characterized in that, comprises characteristic node information or management object sign in the described nodal information, and this characteristic node information or management object sign are used to identify described respective nodes.

3. method according to claim 2, it is characterized in that, described method also comprises: judge that described node sets up the title whether message comprises node, if not, the nodal information of the described respective nodes of described transmission comprises: the nodename that sends described respective nodes.

4. method according to claim 2 is characterized in that, described method also comprises: when setting up respective nodes in terminal equipment management tree, change the nodal value of described respective nodes;

The nodal information of the described respective nodes of described transmission comprises: send the nodal value after described respective nodes changes.

5. method according to claim 2 is characterized in that, described method also comprises: when setting up respective nodes in terminal equipment management tree, change the title of described respective nodes;

The nodal information of the described respective nodes of described transmission comprises: send the title after described respective nodes changes.

6. method according to claim 1 is characterized in that, described method also comprises: when setting up respective nodes in terminal equipment management tree, change the title of described respective nodes;

The nodal information of the described respective nodes of described transmission comprises: send title after described respective nodes changes and this node and set up nodename in the message at node.

7. according to each described method of claim 1 to 6, it is characterized in that described node is set up message and is meant: client configuration message or device management message.

8. according to each described method of claim 1 to 6, it is characterized in that described nodal information sends by client event, generic alert or status command.

9. the dispensing device of a nodal information is characterized in that, this device comprises:

Node is set up the message acquiring unit, is used for slave unit management server receiving node and sets up message; Obtain described node and set up characteristic node information in the message or management object sign; This characteristic node information or management object sign are used to identify described respective nodes;

Node is set up the unit, is used for setting up message according to described node and sets up node corresponding in terminal equipment management tree;

The nodal information transmitting element is used for sending to described device management server the nodal information of described respective nodes.

10. device as claimed in claim 9 is characterized in that, described nodal information transmitting element also comprises first subelement, and described first subelement is used to send described characteristic node information or management object sign.

11. device according to claim 10 is characterized in that, described device also comprises:

The nodename sending controling unit is used to judge that described node sets up the title whether message comprises node, if not, then triggers the nodal information transmitting element;

Described nodal information transmitting element also comprises second subelement, and described second subelement is used for the triggering according to described nodename sending controling unit, sends the nodename of described respective nodes to described device management server.

12. device according to claim 10 is characterized in that, described device also comprises: nodal value changes the unit, is used for changing the nodal value of described respective nodes when terminal equipment management tree is set up respective nodes;

Described nodal information transmitting element also comprises the 3rd subelement, and described the 3rd subelement is used for the nodal value after described device management server sends described respective nodes change.

13. device according to claim 10 is characterized in that, described device also comprises: nodename changes the unit, is used for changing the title of described respective nodes when terminal equipment management tree is set up respective nodes;

Described nodal information transmitting element also comprises the 4th subelement, and described the 4th subelement is used for the title after described device management server sends described respective nodes change.

14. device according to claim 9 is characterized in that, described device comprises that also nodename changes the unit, is used for changing the title of described respective nodes when terminal equipment management tree is set up respective nodes;

Described nodal information transmitting element also comprises the 5th subelement, and described the 5th subelement is used for sending title after described respective nodes changes and this node are set up message at node nodename to described device management server.