Patent Application
20120079093
The present invention relates to the field of network communication technologies, and in particular, to a Device Management (DM) method, a DM apparatus and a DM system.
An Open Mobile Alliance (OMA) DM system in the conventional art includes: a Device Management Authority (DMA), a Device Management Server (DMS), a gateway device, and a terminal device.
A Device Management Client (DMC) on the terminal device is used to parse and execute a management command delivered by the DMS, and a management tree stored on the terminal device may be regarded as an interface through which the DMS manages the terminal device through a DM protocol. The management tree includes some basic Management Objects (MOs) used to implement respective functions. Through a management interface between the DMS and the DMC, the DMA operates the basic MOs in the management tree, thereby achieving an objective of performing DM operations on the terminal device. Operation commands of the DMS include Get, Replace, Exec, Copy, and Delete.
In the process of implementing the present invention, the inventors find the following problems in the conventional art:
When the DMS needs to perform the DM operations on the multiple DMCs through a gateway device, the DMS needs to set up mutually independent DM sessions with the multiple DMCs respectively through the gateway device even if the operations are the same, and the operations are executed repeatedly in the independent DM sessions. Consequently, lots of repeated management data (including management control instructions and software/firmware upgrade packages) is transmitted on an external interface of the gateway device connected to the DMS, and a link congestion of the external interface of the gateway device is caused, so as the efficiency of the system performance is reduced and the experience of the users is disturbed.
Embodiments of the present invention provide a DM method, a DM apparatus, and a DM system to solve the problem in the conventional art that lots of repeated management data is transmitted via an external interface of a gateway device connected to a DMS and a link congestion of the external interface of the gateway device is caused.
To achieve the foregoing objectives, the embodiments of the present invention adopt the following technical solutions:
In an aspect, an embodiment of the present invention provides a DM method, which includes:
receiving a DM instruction;
parsing the DM instruction to be used for managing at least two terminal devices, in which management data, used for managing the at least two terminal devices, indicated in the DM instruction, is the same;
obtaining the management data indicated in the DM instruction only once; and
delivering the obtained management data to the at least two terminal devices so that the at least two terminal devices perform DM according to the management data.
In another aspect, an embodiment of the present invention provides a Device Management Proxy (DMP), which includes:
an instruction receiving unit, configured to receive a DM instruction;
an instruction parsing unit, configured to parse the DM instruction to be used for managing at least two terminal devices, in which management data, used for managing the at least two terminal devices, indicated in the DM instruction is the same;
a data obtaining unit, configured to obtain the management data indicated in the DM instruction only once; and
an information delivering unit, configured to deliver the obtained management data to the at least two terminal devices so that the at least two terminal devices perform DM according to the management data.
In still another aspect, an embodiment of the present invention provides a DM system, which includes:
a DMP, configured to: receive a DM instruction sent by a DMS; parse the DM instruction to be used for managing at least two terminal devices, in which management data, used for managing the at least two terminal devices, indicated in the DM instruction is the same; obtain the management data indicated in the DM instruction only once; and deliver the obtained management data to the at least two terminal devices so that the at least two terminal devices perform DM according to the management data;
a terminal device, configured to receive the management data delivered by the DMP; and
the DMS, configured to deliver the DM instruction to the DMP, in which the DM instruction is used for managing the at least two terminal devices, and the management data indicated in the DM instruction is the same.
With the DM method, the DM apparatus, and the DM system according to the embodiments of the present invention, if the received DM instruction is parsed to judge that the DM instruction is used for managing at least two terminal devices, and management data indicated in the DM instruction is the same, the management data indicated in the DM instruction is obtained only once, thereby greatly saving the interface resources for obtaining the management data indicated in the DM instruction, reducing the adverse impact on the user service experience, and relieving the load on the system for receiving the management data.
The following describes a DM method, a DM apparatus, and a DM system according to the embodiments of the present invention in detail with reference to accompanying drawings.
Step 101: Receive a DM instruction.
Specifically, a DMP receives the DM instruction sent by a DMS. The DM instruction may carry different information as required. Examples of the information are: a management data link for managing at least two terminal devices respectively; a management data link identifier for managing at least two terminal devices and a management data identifier for managing at least two terminal devices; management data for managing a first terminal device and at least one management data link identifier for managing other terminal device(s); management data for managing the first terminal device and a management data identifier for managing the first terminal device, at least one management data link identifier for managing other terminal device(s) and a management data identifier for managing other terminal device(s); or, one copy of management data and DM indication information.
It should be noted that, the information in the DM instruction may be sent by the DMS to the DMP in the form of at least one DM message. If the information of the DM instruction is sent by the DMS to the DMP through one DM message, the DM message is used for managing at least two terminal devices; if the information of the DM instruction is sent by the DMS to the DMP through at least two DM messages, the DM messages are used for managing at least one terminal device.
Step 102: Parse the DM instruction to be used for managing at least two terminal devices, in which management data, used for managing the at least two terminal devices, indicated in the DM instruction is the same.
In step 102, the DMP performs parsing and judging according to the received DM instruction; and performs different parsing processing according to the received DM instruction. The scenarios of parsing are as follows:
Scenario 1: If the DM instruction carries management data link identifiers for managing at least two terminal devices, the DM instruction is parsed to be used for managing at least two terminal devices and that the management data link identifiers for managing at least two terminal devices are the same.
Scenario 2: If the DM instruction carries management data link identifiers for managing at least two terminal devices and carries management data identifiers for managing at least two terminal devices, the DM instruction is parsed to be used for managing at least two terminal devices and the management data link identifiers for managing at least two terminal devices or the management data identifiers in the DM instruction are the same.
Scenario 3: If the DM instruction carries management data for managing a first terminal device and at least one management data link identifier for managing other terminal devices, the DM instruction is parsed to be used for managing at least two terminal devices and the management data link identifier for managing other terminal devices is linked to the management data of the first terminal device.
Scenario 4: If the DM instruction carries management data for managing a first terminal device and a management data identifier of the first terminal device, at least one management data link identifier for managing other terminal devices and a management data identifier for managing other terminal devices, the DM instruction is parsed to be used for managing at least two terminal devices, and the management data link identifier for managing at least one other terminal device in the DM instruction is linked to the management data of the first terminal device, or the management data identifier for managing the at least one other terminal device in the DM instruction is the same as the management data identifier of the first terminal device.
Scenario 5: If the DM instruction carries one copy of management data and DM indication information, the DM instruction is parsed to be used for managing at least two terminal devices and the DM indication information indicates the management data is used for managing the at least two terminal devices.
It should be noted that, the process of the DMP performing instruction parsing on the received DM instruction may be understood as follows: The DMP receives and parses a DM instruction, judges the DM instruction, and stores the judgment result and the obtained management data locally; afterward, the DMP receives and parses a next DM instruction, and judges the next DM instruction, where the parse and judgment may be made not only with respect to the information carried in the DM instruction, but also with respect to the judgment result previously stored locally by the DMP and the previously obtained management data; if the management data indicated in the next received DM instruction is the same as the management data previously stored locally by the DMP, the DMP obtains the locally stored management data.
Step 103: Obtain the management data indicated in the DM instruction only once.
Step 104: Deliver the obtained management data to the at least two terminal devices so that the at least two terminal devices perform DM according to the management data. Here, it can be understood that, the terminal device(s) may regard the DMP as a DMS, and the DMP delivers the obtained management data to the terminal device(s) required to perform a DM operation.
It should be further noted that, when the DMP needs to store the obtained management data in a preset storage location of the DMP, the step of delivering the DM instruction and the obtained management data to the at least two terminal devices further includes:
allocating a local link identifier to the obtained management data;
delivering the DM instruction that carries the local link identifier of the management data to the at least two terminal devices; and
delivering the management data to the at least two terminal devices, if the at least two terminal devices request obtaining the management data according to the local link identifier of the received management data, so that the at least two terminal devices perform DM according to the DM instruction.
When the DMP needs to store the obtained management data onto a corresponding location of MO of the terminal device in a local management tree of the DMP, the step of delivering the obtained management data to the at least two terminal devices so that the at least two terminal devices perform DM according to the management data further includes:
delivering the DM instruction that carries the management data to the at least two terminal devices separately, so that the at least two terminal devices perform DM according to the DM instruction.
an instruction receiving unit 201, configured to receive a DM instruction;
an instruction parsing unit 202, configured to parse the DM instruction to be used for managing at least two terminal devices, in which management data, used for managing the at least two terminal devices, indicated in the DM instruction is the same;
a data obtaining unit 203, configured to obtain the management data indicated in the DM instruction only once; and
an information delivering unit 204, configured to deliver the obtained management data to the at least two terminal devices so that the at least two terminal devices perform DM according to the management data.
The instruction parsing unit 202 may make different judgment according to the information carried in the DM instruction; if the DM instruction carries management data link identifiers for managing at least two terminal devices, the instruction parsing unit parses the DM instruction to be used for managing at least two terminal devices and that the management data link identifiers for managing at least two terminal devices are the same.
Alternatively, if the DM instruction carries management data link identifiers for managing at least two terminal devices and management data identifiers for managing at least two terminal devices, the instruction parsing unit parses the DM instruction to be used for managing at least two terminal devices and that the management data link identifiers for managing at least two terminal devices or the management data identifiers for managing at least two terminal devices in the DM instruction are the same.
Alternatively, if the DM instruction carries management data for managing a first terminal device and at least one management data link identifier for managing other terminal device(s), the instruction parsing unit parses the DM instruction to be used for managing at least two terminal devices and that the management data link identifier for managing other terminal device(s) is linked to the management data of the first terminal device.
Alternatively, if the DM instruction carries management data for managing a first terminal device and a management data identifier for managing the first terminal device, at least one management data link identifier for managing other terminal device(s) and a management data identifier for managing other terminal device(s), the instruction parsing unit parses the DM instruction to be used for managing at least two terminal devices, and that the management data link identifier for managing at least one other terminal device in the DM instruction is linked to the management data for managing the first terminal device, or the management data identifier for managing at least one other terminal device in the DM instruction is the same as the management data identifier for managing the first terminal device.
Alternatively, if the DM instruction carries one copy of management data and DM indication information, the instruction parsing unit parses the DM instruction to be used for managing at least two terminal devices and that the DM indication information indicates the management data is used for managing the at least two terminal devices.
It should be noted that, when the DMP with the foregoing instruction parsing unit needs to store the obtained management data in a preset storage location of the DMP, the information delivering unit 204 may further include:
a local identifier configuring subunit, configured to allocate a local link identifier to the obtained management data;
an instruction delivering subunit, configured to deliver the DM instruction that carries the local link identifier of the management data to the at least two terminal devices; and
a data delivering subunit, configured to deliver the management data to the at least two terminal devices if the at least two terminal devices request obtaining the management data according to the local link identifier of the received management data, so that the at least two terminal devices perform DM according to the DM instruction.
When the DMP needs to store the obtained management data onto a corresponding location of MO of the terminal device in a local management tree of the DMP, the information delivering unit further includes:
an information delivering subunit, configured to deliver the DM instruction that carries the management data to the at least two terminal devices separately so that the at least two terminal devices perform DM according to the DM instruction.
It should be noted that, the DMP may further include:
an authorization message receiving unit, configured to receive authorization message(s) of the at least two terminal devices, where the authorization message(s) carries (carry) the identifier information of the DMS to be accessed by the at least two terminal devices;
an authorization message parsing unit, configured to parse the authorization message(s), and judge whether the DMS is supported according to the identifier information of the DMS;
a request message sending unit, configured to send a proxy DM request to the at least two terminal devices if the DMS is supported; and
an authorization command receiving unit, configured to receive DM authorization command(s) sent by the at least two terminal devices.
It should be further noted that, the DMP may further include:
an account information configuring unit, configured to allocate account information to the at least two terminal devices; and
a session managing unit, configured to: set up a DM sessions with the at least two terminal devices according to the allocated account information, for example, obtain the MO data information of the at least two terminal devices through the DM session and map the MO data information to a local location; or deliver the obtained management data to the at least two terminal devices through the DM sessions.
a DMP, configured to: receive a DM instruction sent by a DMS; parse the DM instruction to be used for managing at least two terminal devices, and that management data, used for managing the at least two terminal devices, indicated in the DM instruction is the same; obtain the management data indicated in the DM instruction only once; and deliver the obtained management data to the at least two terminal devices so that the at least two terminal devices perform DM according to the management data;
terminal devices, configured to: receive the management data delivered by the DMP, authorize the DMP to perform proxy management, and exchange information with the DMP through the account information allocated by the DMP to the terminal devices; and
the DMS, configured to: deliver a DM instruction to the DMP, where the DM instruction is used for managing at least two terminal devices and management data indicated in the DM instruction is the same; receive a DM session setup message sent by the DMP, and obtain MO data information of the at least two terminal devices according to the DM session setup message; and deliver the DM instruction according to the received session message and the obtained MO data information.
The DMP includes:
a DMC module, configured to receive a DM instruction sent by the DMS and exchange information with the DMS;
a batch processing module, configured to: parse the DM instruction to be used for managing at least two terminal devices, and that management data, used for managing the at least two terminal devices, indicated in the DM instruction is the same; and obtain the management data indicated in the DM instruction only once; and
a DMS module, configured to: deliver the obtained management data to the at least two terminal devices so that the at least two terminal devices perform DM according to the management data; and exchange information with the at least two terminal devices.
It should be noted that, in this embodiment, a DMP is added to the gateway device so that the DMS can combine transmission of signaling and data when performing the same DM operation on multiple terminal devices.
On the interface between the gateway device and the network-side DMS, the DMP in the gateway device sets up a DM session with the network-side DMS through a DMC module, receives the DM instruction(s) specific to multiple terminal devices sent by the network-side DMS, and returns a command execution result to the network-side DMS. Through the interface between the gateway device and each terminal device, the DMP in the gateway device sets up DM sessions with the DMC in each terminal device through a DMS module, delivers the corresponding DM instruction to the DMC on each terminal device on behalf of the network-side DMS, and receives the result of performing the DM operation on the terminal device. When the DMP receives the DM instructions specific to multiple terminal devices from the network-side DMS, the batch processing module in the DMP first parses the DM instruction(s) to judge whether the DM instruction(s) is(are) the same, for example, judge whether the same management data needs to be downloaded; if the same management data needs to be downloaded, the batch processing module combines the same DM instructions, instructs the DMC module in the gateway device to obtain only one copy of management data, and then instructs the DMS module to distribute the same copy of management data to DMCs in multiple terminal devices.
It should be further noted that, the DMP in the present invention can be deployed not only in a gateway device, but also in a server or functional entity between the terminal device and the network-side DMS. Therefore, unless otherwise specified herein, the DMP is described as an independent logical functional entity, and the physical device where the DMP is practically deployed is not limited.
Step 401: A DMP negotiates with each terminal device through authorization to perform DM. The negotiation process includes the following step: The DMP judges whether the DMP supports a DMS accessed by the terminal devices, and whether the terminal devices are willing to authorize the DMP to perform proxy management.
Step 402: The DMP configures a legal account for each terminal device through a bootstrap technique. The account is used for setting up a DM session between the DMP and the terminal device.
Step 403: The DMP maps the MO data of the terminal device to a local management tree of the DMP.
Step 404: The DMP receives a DM instruction delivered by the DMS.
Step 405: The DMP parses the received DM instruction to be used for managing at least two terminal devices, in which management data indicated in the DM instruction is the same; and obtains the management data indicated in the DM instruction only once.
Step 406: The DMP delivers the obtained management data to the at least two terminal devices separately, namely, the DMP processes the downloaded DM data locally and forwards the DM data to the at least two terminal devices.
Step 407: When the DMP needs to cancel the proxy DM relationship with each terminal device, the DMP clears the mapped MO data of the terminal device in the DMP. The mapped MO data of the terminal device in the DMP is the MO data information of the terminal device that needs to cancel the DM proxying relationship in the local management tree.
Step 408: The terminal device clears the account information configured by the DMP through the bootstrap technique and clears the proxy DM authorization for the DMP.
Step 407 and step 408 may be performed selectively according to practical situations.
It should be noted that, after the terminal device is separated from the gateway device where the DMP is located, the terminal device may choose whether to keep or clear the DM account information configured by the DMP through the bootstrap technique, and whether to keep or cancel the authorization for the DMP, and the DMP may choose whether to keep or clear the locally mapped MO data information of the terminal, which is not limited by the technical solution of the present invention.
The following uses specific embodiments to describe how the DMP negotiates and configures the proxy DM relationship with each terminal device and describe the DM process in detail.
To set up a DM proxying relationship between the DMP and each terminal device, on one hand, the DMP needs to be capable of accessing the DMS on behalf of multiple terminal devices, and on the other hand, the DMP needs to be capable of performing DM operations on multiple terminal devices on behalf of the DMS. That is, the DMP needs to be authorized to access the MO data on all terminal devices, and meanwhile needs to configure DM account information available for each terminal device to access the DMP.
For example, assuming that DM account information is pre-configured for multiple terminal devices for accessing the same DMS, when each terminal device accesses an external network separately, the terminal devices may use the DM account information to access the DMS and obtain the DM service. In this embodiment, when the terminal devices access the external network through a common gateway device or a common another server, the terminal devices can set up a proxy DM relationship with the DMP in the gateway device or the other server, and then obtain the DM service provided by the DMS through the DMP. The detailed implementation procedure is as follows:
Step 501: Terminal device x sends an authorization message to the DMP. The authorization message may indicate that the DMP supports a standard DM protocol, and may provide the ID of the DMS (DMS-ID) to be accessed by terminal device x. When multiple DMSs need to be accessed, the authorization message may provide a list of DMS-IDs.
Step 502: The DMP judges whether the DMP comprises DM account information for accessing the DMS. If such DM account information for accessing the DMS exists, the DMP performs step 503; if no such DM account information for accessing the DMS exists, the DMP returns an error response. If multiple DMSs need to be accessed but the DMP supports only a part of the DMSs, the DMP performs step 503 and returns the IDs of DMSs not supported by the DMP to terminal device x.
It should be noted that, for the DMSs not supported by the DMP, terminal device x may obtain the DM service by accessing the DMS separately with reference to a DM protocol.
Step 503: The DMP sends a proxy DM request message to terminal device x, requesting performing proxy DM for terminal device x. The proxy DM request message provides a DMP-ID which specifies the DMP itself as a proxy DMS so that terminal device x authorizes the DMP.
Step 504: Terminal device x authorizes the DMP to perform proxy DM according to the confirmation of the user, for example, adds the DMP-ID to an Access Control List (ACL) of the relevant MOs, and configures the DMP with access right to add, delete, and modify the MO data.
Step 505: Terminal device x returns an authorization success message to the DMP.
Step 506: The DMP configures DM account information for terminal device x through the bootstrap technique. The DM account information is used for accessing the DMP. Specifically, based on the DM bootstrap technique, the DM account information may be bootstrapped onto terminal device x through an Object Exchange (OBEX) protocol on a local connection between the DMP and terminal device x.
Step 507: Terminal device x sets up a DM session with the DMP by using the DM account information configured through the bootstrap technique in step 506.
Step 508: In the session process, the DMP obtains the relevant MO data information on terminal device x. For example, through a <Get> command, the DMP can obtain the complete management tree structure on terminal device x and the detailed data of MOs in the management tree.
Step 509: Terminal device x returns its MO data information to the DMP, for example, in the format of a Device Management-Tree and Description Serialization (DM-TNDS) document.
Step 510: The DMP terminates the DM session with terminal device x.
Step 511: The DMP maps the MO data information of terminal device x obtained in step 509 to the local management tree of the DMP, for example, adds the MO data information as a management subtree under a branch node in the DMP management tree. Depending on the extent of detail of the MO data information content obtained in step 509, the mapped MO data information of terminal device x may be exhaustive or partial, or may only be empty MO root nodes that include no specific value information.
Step 512: Optionally, the DMP registers the notification address of terminal device x in the DMP with the DMS, and therefore, when the DMS needs to perform DM operations on terminal device x, the DMS sends a DM notification message to the DMP first, and then the DMP performs the proxy DM function.
To describe the DM process in step 402 more clearly, the following gives three specific examples for detailed description. It is assumed that the DMS needs to perform the same DM operation on multiple terminal devices through the DMP, and the DMS performs the same software upgrade on terminal device 1 and terminal device 2 through the DMP.
Step 601: If the DMS judges it is necessary to perform a DM operation of software upgrade on terminal device 1 and terminal device 2 according to a request of the DMA, the DMS instructs the DMP to set up a DM session with the DMS by sending a DM notification message to the DMP. This step is performed selectively according to practical situations.
Step 602: The DMP requests the DMS to set up a DM session. In this process, the DMP provides account information for the DMS first so that the DMS can authenticate the legal identity of the DMP. The DMP may also provide the MO data information of the terminal device(s) locally mapped by the DMP for the DMS.
Step 603: According to the MO data information of the terminal device(s) maintained by the DMS or provided by the DMP, the DMS judges to perform the DM operation of software upgrade on terminal device 1 and terminal device 2. Therefore, the DMS sends a DM instruction for configuring a software upgrade package download URL to the DMP, where the software upgrade package download URL is a link identifier of the management data. The DM instruction may have the following content based on the existing DM protocol:
The <Replace> command is used for instructing the DMP to replace the mapped MO data information of the terminal device(s), where the replaced data item is described by the <Item> element; the <Target>/<LocURI> subelement indicates the destination location of the replaced data item, namely, the location of the mapped node of the MO in the management tree in DMP; and the <Data> subelement indicates the specific content of the replaced data item. Specifically, the destination location ./PNE1/SCM/Download/Package123/PkgID and the destination location ./PNE2/SCM/Download/Package456/PkgID are used for configuring the unique identifier of the software upgrade package of terminal device 1 and terminal device 2 respectively, namely, configuring the management data identifiers, which are both pkg1 in this example; the destination location ./PNE1/SCM/Download/Package123/PkgURL and the destination location ./PNE2/SCM/Download/Package456/PkgURL are used for configuring the download URL of the software upgrade package of terminal device 1 and terminal device 2 respectively, namely, configuring the management data link identifiers, which are both ftp://example.org/pkg1 in this example. The DM instruction may further include other necessary operation instructions. For example, when the mapped MO node does not exist in the destination location, the DMS needs to execute an <Add> command to create the node, which can be implemented with reference to the DM protocol, and details are not described herein again.
Step 604: The DMP configures the mapped MO data information of the corresponding terminal device in the management tree in DMP according to the DM instruction in step 603, and then returns a configuration success response message to the DMS.
Step 605: The DMS sends a DM instruction for executing “download and installation” of the software upgrade package of terminal device 1 and terminal device 2 to the DMP. The following is an example of the content of the DM instruction based on the DM protocol:
The <Exec> command is used for instructing the DMP to execute the specific DM operation which is described by the <Item> element; the <Target>/<LocURI> subelement indicates the location of the MO node corresponding to the operation, and, in this embodiment, the location is the nodes mapped by the DMP and used by terminal device 1 and terminal device 2 for the “download and installation” operation. The DM instruction may further include other necessary operation instructions, which can be implemented with reference to the DM protocol, and details are not described herein again.
Step 606: The DMP judges that the two software upgrade packages are the same according to the software upgrade package information configured by the DMS for upgrading software of terminal device 1 and terminal device 2, namely, according to the unique identifier and/or URL link identifier of the software upgrade package. Specifically, if the two software upgrade packages have the same unique identifier (namely, pkg1) or the same URL (namely, ftp://example.org/pkg1) used for downloading the two software upgrade packages, the two software upgrade packages are the same.
Step 607: The DMP combines the download procedures of the foregoing two software upgrade packages, that is, the download procedure is executed only once and no software upgrade package is downloaded repetitively. In this embodiment, assuming that the download URL of the software upgrade packages points to the DMS, the DMP downloads and obtains the software upgrade packages from the DMS. In practical deployment, the URL may point to another server, and the DMP may download and obtain the software upgrade packages from the another server.
Step 608: To implement the DM operation of software upgrade on terminal device 2, the DMP sends a DM notification message to terminal device 2 so as to instruct terminal device 2 to set up a DM session with the DMP.
Step 609: Terminal device 2 requests the DMP to set up a DM session by sending a DM session setup request message that carries account information configured for terminal device 2 by the DMP through the bootstrap technique, and the account information configured for terminal device 2 by the DMP is used by the DMP for authenticating the legal identity of terminal device 2.
Steps 610 to 611: Similar to steps 603 to 604, the DMP sends a DM instruction to terminal device 2 to configure the download URL of the software upgrade package. The following is an example of the content of the DM instruction based on the DM protocol:
The DMP modifies the URL of the software upgrade package to be downloaded by terminal device 2 to ftp://dmp.example.org/pkg1 which is the local link address of the DMP.
Step 612: Similar to step 605, the DMP sends a DM instruction for executing “download and installation” of the software upgrade package to terminal device 2.
Step 613: Terminal device 2 downloads the software upgrade package from the DMP according to the URL of the software upgrade package configured in step 611 or according to the management data identifier, namely, the unique identifier of the software upgrade package.
Steps 614 to 616: After installing the downloaded software upgrade package, terminal device 2 returns a download and installation success response message to the DMP, and the DMP ends the DM session with terminal device 2.
Step 617: Similar to steps 608 to 616, the DMP finishes the software upgrade management operation for terminal device 1.
Step 618: The DMP reports the result of the proxy DM state for terminal device 1 and the result of the proxy DM state for terminal device 2 to the DMS, namely, reports success of downloading and installing the software upgrade package.
Step 619: The DMS ends the DM session with the DMP, and finishes DM for terminal device 1 and terminal device 2.
It should be noted that:
The DMP may report the result of the DM state for terminal device 1 and the result of the DM state for terminal device 2 in an “asynchronous” reporting mode specified in the existing DM protocol. In this case, after step 607, the DMS may perform step 619 immediately to end the DM session with the DMP; after step 617, the DMP may set up a new DM session with the DMS to report the result of the DM state for terminal device 1 and the result of the DM state for terminal device 2, and details are not described herein again.
It should be further noted that, in steps 608 to 617, for the software upgrade management operation performed by the DMP on terminal device 1 and terminal device 2, the software upgrade packages may be delivered to terminal device 1 and terminal device 2 in the direct delivery mode in the DM protocol, and specifically, reference is made to steps 707 to 714 in the specific embodiment shown in
Steps 701 to 702: Same as steps 601 to 602, and details are not described herein again.
Step 703: According to the MO data information of the terminal device maintained by the DMS or provided by the DMP, the DMS judges it is necessary to perform the same DM operation of software upgrade on terminal device 1 and terminal device 2. Therefore, the DMS sends a DM instruction that carries the software upgrade package to the DMP. The following is an example of the content of the DM instruction based on the DM protocol:
The <Item> element can carry multiple <Target>/<LocURI> subelements (by extending the syntax rule of the DM protocol) to indicate that the same <Data> element in the <Item> element is applicable to multiple destination locations. Specifically, the destination location ./PNE1/SCM/Inventory/Delivered/Package123/PkgID and destination location ./PNE2/SCM/Inventory/Delivered/Package456/PkgID are used for configuring the unique identifier of the software upgrade package of terminal device 1 and terminal device 2 respectively, namely, configuring the management data identifiers, which are both pkg1 in this example; the destination location ./PNE1/SCM/Inventory/Delivered/Package123/Data and destination location ./PNE2/SCM/Inventory/Delivered/Package456/Data are used for storing the software upgrade package instead of the URL of the software upgrade package.
Step 704: The DMP configures the mapped MO data information of the terminal device in the management tree in the DMP according to the DM instruction in step 703, and then returns a delivery success response message to the DMS.
Step 705: The DMS sends a DM instruction for executing “installation” of the software upgrade package of terminal device 1 and terminal device 2 to the DMP. The following is an example of the content of the DM instruction based on the DM protocol:
The a “direct delivery” embodiment differs from the “indirect delivery” embodiment in that: The <Target>/<LocURI> subelement indicates the location of the MO node corresponding to the operation, and the location is the nodes mapped by the DMP and used by terminal device 1 and terminal device 2 for the “installation” operation instead of the node used for the “download and installation” operation. Meanwhile, according to the extended syntax rule in step 703, one <Item> element may carry multiple <Target>/<LocURI> destination locations.
Step 706: According to indication of multiple destination locations in the same <Item> element in step 703, the DMP judges that the software upgrade package is applicable to both terminal device 1 and terminal device 2.
It should be noted that, when the DMP judges that the software upgrade package is applicable to both terminal device 1 and terminal device 2, the DMP may replicate the software upgrade package into two copies according to the multiple destination locations indicated in the DM instruction, and allocate the two copies to the mapped MO of terminal device 1 and terminal device 2 in the management tree in DMP respectively. Alternatively, the DMP does not replicate the software upgrade package at the time, but stores it in another local location of the DMP separately.
Steps 707 to 708: Similar to steps 608 to 609 in the foregoing embodiment, and details are not described herein again.
Steps 709 to 710: By using a “direct delivery” method in the DM protocol, the DMP delivers the software upgrade package to terminal device 2, and terminal device 2 returns a delivery success response message. Step 709 differs from step 703 in that: Each <Item> in step 709 has only one <Target>/<LocURI> subelement, which indicates the target MO node location corresponding to terminal device 2.
Steps 711 to 714: Similar to step 705, the DMP sends a DM instruction for executing “installation” of the software upgrade package to terminal device 2. Terminal device 2 installs the software upgrade package and then returns an installation success response to the DMP, and the DMP ends the DM session with terminal device 2.
Step 715. Similar to steps 707 to 714, the DMP finishes the software upgrade management operation for terminal device 1.
Steps 716 to 717. Similar to steps 618 to 619, and details are not described herein again.
It should be noted that:
The DMP may report the result of the DM state for terminal device 1 and the result of the DM state for terminal device 2 in an “asynchronous” reporting mode in the DM protocol. In this case, after step 705, the DMS may perform step 717 immediately to end the DM session with the DMP; after step 715, the DMP may set up a new DM session with the DMS to report the result of the proxy DM state for terminal device 1 and the result of the proxy DM state for terminal device 2.
It should be further noted that:
In steps 707 to 715, for the software upgrade management operation performed by the DMP on terminal device 1 and terminal device 2, the software upgrade packages may be delivered to terminal device 1 and terminal device 2 in the “indirect delivery” mode in the DM protocol, and specifically, reference is made to steps 608 to 617 in the foregoing embodiment.
It should be further noted that: in step 703 and step 705, the DMS may further extend the syntax rule of the DM protocol, and use a wildcard such as “*” in the DM instruction; or use a special management tree node with a wildcard meaning such as “./ALL” to indicate multiple destination locations. For example, the following DM instruction is applied in step 703:
“./*” represents the MO root node locations of all terminal devices mapped in the management tree in DMP, and this instruction means that the same software upgrade package (with the identifier of pkg1) is delivered to all terminal devices managed by the DMP. Correspondingly, in step 705, a similar mode may be applied to instruct the DMP to “install” the software upgrade package for all terminal devices.
In fact, in the solution in this embodiment, the wildcard or the special management tree node with a wildcard meaning may be further used to represent all terminal devices already managed or to be managed by the DMP no matter whether MO data information of the terminal devices is mapped in the DMP beforehand. Therefore, the DMP performs the same DM operation for all terminal devices already managed or to be managed by the DMP.
Step 801 to 802: Same as steps 601 to 602, details are not described herein again.
Step 803: If the DMS judges that the software version of the terminal device is excessively low according to the MO data information of the terminal device maintained by the DMS or provided by the DMP, or, if the DMS judges it is necessary to upgrade the software of the terminal device according to the instruction of the DMA, the DMS decides to perform the DM operation of software upgrade on terminal device 1 and terminal device 2. Therefore, the DMS sends to the DMP a DM instruction configured with the software upgrade package download URL. The following is an example of the content of the DM instruction based on the DM protocol:
Differentiate from the “direct delivery” mode and “indirect delivery” mode is that: The DMS downloads the same software upgrade package (pkg1) for terminal device 1 and terminal device 2 in the “direct delivery” mode and the “indirect delivery” mode respectively. For terminal device 1, the DMS directly downloads the software upgrade package to the mapped MO destination location of terminal device 1 in the DMP, namely, to ./PNE1/SCM/Inventory/Delivered/Package123/Data; for terminal device 2, the DMS configures the URL used for downloading the software upgrade package to the mapped MO destination location of terminal device 2 in the DMP, namely, to ./PNE2/SCM/Download/Package456/PkgURL. This URL may point to the mapped MO destination location for storing the software upgrade package of terminal device 1 in the DMP, namely, to ./PNE1/SCM/Inventory/Delivered/Package123/Data; or point to the address of the DMS or another server, for example, ftp://example.org/pkg1.
Step 804: The DMP configures the mapped MO data of the terminal devices in the management tree in DMP according to the DM instruction in step 803, and then returns a delivery success response to the DMS.
Step 805: the DMS sends a corresponding DM instruction for installing the software upgrade package to the DMP according to the different delivery modes applied to terminal device 1 and terminal device 2 in step 803. The following is an example of the content of the DM instruction based on the DM protocol:
Differentiate from the “direct delivery” mode and “indirect delivery” mode is that: For terminal device 1, the MO node location corresponding to the <Target>/<LocURI> subelement is the node used for the “installation” operation; for terminal device 2, the MO node location corresponding to the <Target>/<LocURI> subelement is the node used for the “download and installation” operation.
Step 806: The DMP judges that the two software upgrade packages are the same according to the software upgrade package information configured by the DMS and used for terminal device 1 and terminal device 2. Specifically, the judgment method is as follows, if the two software upgrade packages have the same unique identifier (namely, pkg1), or, if the URL used for downloading the software upgrade package required by terminal device 2 points to the mapped MO node location for storing the software upgrade package required by terminal device 1 in the DMP, the two software upgrade packages are the same.
Steps 807 to 808: The DMP uses the indirect delivery mode in steps 608 to 616 in the foregoing embodiment or the direct delivery mode in steps 707 to 714 in the foregoing embodiment to finish the software upgrade management operation for terminal device 1 and terminal device 2 respectively.
Steps 809 to 810: Similar to steps 618 to 619 in the foregoing embodiment, and details are not described herein again.
It should be noted that:
The DMP may also report the result of the proxy DM state for terminal device 1 and the result of the proxy DM state for terminal device 2 in an “asynchronous” reporting mode in the DM protocol. In this case, after step 805, the DMS may perform step 810 immediately to end the DM session with the DMP; after step 808, the DMP may set up a new DM session with the DMS to report the result of the DM state for terminal device 1 and the result of the proxy DM state for terminal device 2, and details are not described herein again.
Another DM method is provided in an embodiment of the present invention, and differs from the foregoing DM method in that:
In step 603 and step 605 in the “indirect delivery” DM method embodiment, and in step 803 and step 805 in the “hybrid delivery” DM method embodiment, the DM instruction sent by the DMS to the DMP includes a configuration command, a download-and-install command, and a download command; the DM instruction is transferred by the same DM message in the same DM session in parallel. In fact, in the DM method according to the embodiments of the present invention, the DM instruction may also be sent in series, namely, the DM instruction specific to at least two terminal devices is sent by the DMS through multiple DM messages consecutively, and the DM messages may be sent to the DMP through multiple DM sessions consecutively. In this case, the DMP performs corresponding proxy DM operations for some terminal devices according to the first arrived DM message, and buffers the management data of the at least two terminal devices and the relevant information such as the software upgrade package and the unique identifier of the software upgrade package; the buffered management data and relevant information can be used to parse the subsequently arrived DM message to judge the DM operation for other terminal devices, namely, judge whether the terminal devices to be managed subsequently require the same DM data. If the subsequently arrived DM message needs the management data stored in the DMP, the DM data such as the software upgrade package is not obtained repeatedly, but the buffered DM data is used to finish the proxy DM operation for other terminal devices.
With the DM method, the DM apparatus, and the DM system according to the embodiments of the present invention, if the received DM instruction is parsed to judge that the DM instruction is used for managing at least two terminal devices, and management data indicated in the DM instruction is the same, the management data indicated in the DM instruction is obtained only once, thereby greatly saving the interface resources for obtaining the management data indicated in the DM instruction, reducing the adverse impact on the user service experience, and relieving the load on the system for receiving the management data.
Persons of ordinary skill in the art should understand that all or part of the steps of the method specified in any embodiment above may be implemented by a program instructing relevant hardware. The program may be stored in a computer-readable storage medium such as a Read Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk. When the program runs, the program executes the steps of the method specified in any embodiment above.
The above descriptions are merely exemplary embodiments of the present invention, but not intended to limit the scope of the present invention. Any modifications, variations or replacements that can be easily derived by those skilled in the art shall fall within the scope of the present invention. Therefore, the scope of the present invention is subject to the appended claims.
| Number | Date | Country | Kind |
|---|---|---|---|
| 200910147982.6 | Jun 2009 | CN | national |
This application is a continuation of International Application No. PCT/CN2010/073790, filed on Jun. 11, 2010, which claims priority to Chinese Patent Application No. 200910147982.6, filed on Jun. 12, 2009, both of which are hereby incorporated by reference in their entireties.
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/CN2010/073790 | Jun 2010 | US |
| Child | 13312776 | US |
