WO2013017020A1 - Procédé et système pour exploiter un nœud exécutable - Google Patents

Procédé et système pour exploiter un nœud exécutable Download PDF

Info

Publication number
WO2013017020A1
WO2013017020A1 PCT/CN2012/078904 CN2012078904W WO2013017020A1 WO 2013017020 A1 WO2013017020 A1 WO 2013017020A1 CN 2012078904 W CN2012078904 W CN 2012078904W WO 2013017020 A1 WO2013017020 A1 WO 2013017020A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
node
request message
response message
server
Prior art date
Application number
PCT/CN2012/078904
Other languages
English (en)
Chinese (zh)
Inventor
金志皓
Original Assignee
华为终端有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 华为终端有限公司 filed Critical 华为终端有限公司
Publication of WO2013017020A1 publication Critical patent/WO2013017020A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method and system for operating an executable node. Background technique
  • 0MA (Open Mobi le Al l iance) DM (Device Management) VI. 3 is a unified device management specification (hereinafter referred to as the DM specification) established by OMA DM WorkGrou.
  • the DM system provides a low-cost solution for third-party management and setting of environment and configuration information in terminal devices (such as mobile terminals and functional objects in terminals) to solve problems encountered during the use of these devices, such as Install and upgrade software and firmware through OTA (Over The Ai r, wireless network), and provide more personalized and personalized services to enhance user experience.
  • Third parties can be operators, service providers or cooperation. Party's information management department.
  • REST (REpresentat State State Transfer) 4 describes an architectural style network system.
  • REST refers to a set of architectural constraints and principles. The application or design that satisfies these constraints and principles is RESTful.
  • RESTful is a design style of a Web Service (an interface proposed to enable communication and sharing between isolated sites).
  • the standard HTTP (HyperText Transfer Protocol) method is adopted. Operate on resources.
  • a device management protocol that conforms to the RESTful design style can be called a RESTful DM.
  • the server uses the standard HTTP method to operate the M0 (Management Object) on the terminal. This kind of operation is easy to interface with existing Web standards, and DM management can also be implemented through standard Web methods. At the same time, by simplifying the protocol process, the capability requirements for the DM terminal can also be reduced.
  • the existing executable node of OMA DM is executed by the server as a bearer through HTTP.
  • the terminal sends a SyncML (Synchronized Markup Language) file, which is an XML (Extensible Markup Language) extension that defines various commands used by OMA DM by defining SyncML.
  • SyncML Synchronized Markup Language
  • XML Extensible Markup Language
  • the client needs to parse the semantics of SyncML to know the stage in which the current session is located and the commands issued by the server. It is necessary to parse the M0 that conforms to the SyncML format, that is, to manage the data. It also needs to parse the session and command information contained in the SyncML, that is, the management command, which has high requirements on the capabilities of the terminal device, and cannot directly manage the device by using the HTTP standard method. Not conducive to direct device management through web applications. SUMMARY OF THE INVENTION In view of the above problems, embodiments of the present invention provide a method and system for operating an executable node, and the device can be directly managed by using an HTTP standard method.
  • the embodiment of the invention provides a method for operating an executable node, including:
  • Receiving a trigger message sending a first request message
  • the first response message is a response message that is sent according to the first request message, where the first response message includes information indicating that the executable node performs an operation
  • the second response message is a response message that is sent according to the second request message, where the second response message includes an error code
  • the embodiment of the present invention further provides a method for operating an executable node, including: sending a trigger message;
  • Sending a first response message where the first response message is a response message that is sent according to the first request message, where the first response message includes information indicating that the executable node performs an operation;
  • the response message sent, the second response message includes an error code.
  • the embodiment of the present invention further provides a method for operating an executable node, where the executable node adds a node value, and the method includes:
  • the node is an executable node.
  • the embodiment of the present invention further provides a method for operating an executable node, where the executable node adds a node value, and the method includes:
  • the embodiment of the present invention further provides a client that operates on an executable node, where the client includes, a receiving unit, a message parsing unit, a message generating unit, a sending unit, a determining unit, and an executable node, where:
  • the receiving unit is configured to receive a message sent by the server, where the message sent by the server includes a trigger message, a first response message, and a second response message, where the trigger message is used to trigger a client to initiate a request message; a response message includes information indicating that the executable node performs an operation, the second response message includes an error code, and the second response message may further include information indicating that the executable node performs an operation;
  • the message is either the first request message and the second request message, the first request message includes an indication of the identity verification information and the requesting device information; the second request message is used to indicate that the node is an executable node, and Contains information indicating that the executable node performs an operation;
  • the message parsing unit is configured to parse the message received by the receiving unit, the message generating unit is configured to generate a message according to the parsing result of the message parsing unit, and the sending unit is configured to send a message to the server.
  • the message sent to the server includes a first request message and a second request message, where the first request message is used to be used by the client.
  • the device information is sent to the server, and the second request message is used to cause the server to return a specific error code; the message sent to the server is a first response message, and the first response message includes Device information
  • the determining unit is configured to determine, according to the parsing result of the message parsing unit, an executable node that the server needs to operate;
  • the executable node has an executable attribute for executing an operation command sent by the server to complete the corresponding operation.
  • the embodiment of the present invention further provides a server for operating an executable node, where the server includes: a receiving unit, a message parsing unit, a message generating unit, and a sending unit, where:
  • the receiving unit is configured to receive a message sent by the client, where the message sent by the client includes a first request message and a second request message, where the first request message is used to send device information of the device where the client is located.
  • the message parsing unit is configured to parse the message received by the receiving unit, the message generating unit is configured to generate a message according to the parsing result of the message parsing unit, and the sending unit is configured to send the message to the client
  • the message sent to the client includes a trigger message, a first response message, and a second response message, where the trigger message is used to trigger a client to initiate a request message; the first response message includes an indication that the executable node performs The second response message includes an error code, and the second response message further includes information indicating that the executable node performs an operation; the message sent to the client is the first request message.
  • the second request message the first request message includes an indication of the identity verification information and the requesting device information; the second request message is used to indicate that the node is an executable node, and includes an indication that the executable node performs an operation.
  • Information is configured to parse the message received by the receiving unit, the message generating unit is configured to generate a message according to the par
  • the embodiment of the present invention further provides a system for operating an executable node, where the system includes a client and a server.
  • the client includes a receiving unit, a message parsing unit, a message generating unit, a sending unit, a determining unit, and an executable node, where:
  • the receiving unit is configured to receive a message sent by the server, where the message sent by the server includes a trigger message, a first response message, and a second response message, where the trigger message is used to trigger a client to initiate a request message;
  • a response message includes an indication that the executable node performs an operation
  • the second response message includes an error code, and the second response message may further include information indicating that the executable node performs an operation;
  • the message sent by the server is either the first request message and the second a request message, the first request message includes an indication of the authentication information and the requesting device information;
  • the second request message is used to indicate that the node is an executable node, and includes information indicating that the executable node performs an operation;
  • the message parsing unit is configured to parse the message received by the receiving unit, the message generating unit is configured to generate a message according to the parsing result of the message parsing unit, and the sending unit is configured to send a message to the server.
  • the message sent to the server includes a first request message and a second request message, where the first request message is used to send device information of the client to the server, and the second request message is used to The server returns a specific error code; the message sent to the server is a first response message, and the first response message includes the device information;
  • the determining unit is configured to determine, according to an analysis result of the message parsing unit, an executable node that the server needs to operate;
  • the executable node has an executable attribute for executing an operation command sent by the server to complete a corresponding operation.
  • the client includes a receiving unit, a message parsing unit, a message generating unit, and a sending unit, and the towel:
  • the receiving unit is configured to receive a message sent by the client, where the message sent by the client includes a first request message and a second request message, where the first request message is used to send device information of the device where the client is located.
  • the message parsing unit is configured to parse the message received by the receiving unit, the message generating unit is configured to generate a message according to the parsing result of the message parsing unit, and the sending unit is configured to send the message to the client
  • the message sent to the client includes a trigger message, a first response message, and a second response message, where the trigger message is used to trigger a client to initiate a request message; the first response message includes an indication that the executable node performs The second response message includes an error code, and the second response message further includes information indicating that the executable node performs an operation; the message sent to the client is the first request message.
  • a second request message where the first request message includes identity verification information and a request The indication of the device information; the second request message is used to indicate that the node is an executable node, and includes information indicating that the executable node performs an operation.
  • FIG. 1 is a schematic diagram of a basic framework of an OMA DM
  • FIG. 2 is a flowchart of a method for operating an executable node according to an embodiment of the present invention
  • FIG. 3 is a flow chart of another method for operating an executable node according to an embodiment of the present invention.
  • FIG. 4 is a flow chart of still another method for operating an executable node according to an embodiment of the present invention.
  • FIG. 5 is a flow chart of still another method for operating an executable node according to an embodiment of the present invention.
  • FIG. 6 is a flow chart of still another method for operating an executable node according to an embodiment of the present invention.
  • FIG. 7 is a flow chart of still another method for operating an executable node according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a client operating on an executable node according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a server operating on an executable node according to an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of a system for operating an executable node according to an embodiment of the present invention.
  • the technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. example. Based on the embodiments of the present invention, those of ordinary skill in the art are not All other embodiments obtained under the premise of creative work are within the scope of the invention.
  • the overall structure of the OMA DM includes a terminal device and a server.
  • the DM client on the terminal device is used to interpret and execute the management commands issued by the DM server.
  • the DM server communicates with the DM client in the terminal device through the DM protocol to implement management of the terminal device.
  • the device management tree stored on the terminal device can be regarded as an interface for the DM server to manage the terminal device.
  • the device management tree includes some management objects.
  • the DM server achieves the purpose of managing the terminal device by operating the management object.
  • the operation commands are Get, Replace, Exec, Copy, De lete, and so on.
  • the existing executable node of OMA DM is implemented by the server as a bearer through HTTP, and sends a SyncML file to the terminal.
  • SyncML various commands used by OMA DM are defined.
  • the URI on the terminal needs to be executed as ". /FanOut/
  • the node of Opera t ions/S tar t first, the node must be an executable node, that is, the node attribute of the node is "Exec"; then the server needs to pass HTTP or other bearer mode during the specified session.
  • Send a SyncML packet to the terminal is in the form of an XML file containing the description of the node that needs to be executed as follows:
  • Ht tp / /www. syncml. org/mgmt-server ⁇ /LocURIX/Source>
  • the client receives such a file, first parses SyncHdr to know which server needs to be managed, and also needs to parse the ID of the management session, and the ID of the message itself, and also know the ID of the command.
  • the type of the command is "Exec”
  • the attribute of the target node of the command is "Exec”. In combination with the above information, the target node can be executed.
  • the client needs to parse the semantics of SyncML to know the stage in which the current session is located and the commands issued by the server. It is necessary to parse the M0 that conforms to the SyncML format, that is, to manage the data; and to parse the session and command information contained in the SyncML, that is, the management command.
  • the capability of the terminal device is high, and the device cannot be directly managed by using the HTTP standard method, which is not conducive to device management directly through the network application.
  • the server performs device management on the client through the standard HTTP method, it needs to follow the M0 design of the existing OMA DM, and operate the nodes in these M0s using the standard HTTP method.
  • the standard HTTP methods include PUT, DELETE, POST, GET.
  • the MO that carries the OMA DM using HTTP is to express the management command and the session flow by using the standard methods provided by HTTP itself, and only the part that manages the data needs to be parsed. This can reduce the server and client capacity requirements, reduce the burden of over-the-air transmission, and use the standard HTTP method to carry commands, which is beneficial for Web App to directly manage the management data of OMA DM.
  • HTTP server For the terminal, some terminals have the ability to configure HTTP Server (HTTP server), that is, can accept HTTP requests. Most terminals do not have HTTP Server configured. Capability, only HTTP Cl ient (HTTP client) can be configured, that is, only HTTP requests can be initiated, and HTTP requests cannot be accepted.
  • FIG. 2 it is a flowchart of a method for operating an executable node according to an embodiment of the present invention.
  • HTTP Server + HTTP Cl ient is deployed on the server side, and only HTTP Cl is deployed on the client side.
  • the ient the client requests the resource from the server through the standard HTTP method, and the server sends an indication to the client through the response message Response, and the response includes a set HTTP request initiated by the client.
  • the server sets a corresponding HTTP request in the Response, and after receiving the Response, the client initiates an HTTP request set in the Response to the server, and the server responds to the request, and the client responds according to the response.
  • the client does not deploy HTTP Server, so it cannot listen to HTTP messages at any time, nor can it receive HTTP requests.
  • the server needs to manage the client, it sends a notification message to the client through WAP PUSH or SIP PUSH or SMS, and the session is pulled up.
  • the client After receiving the notification message, the client first verifies the notification message and the server. Validity, and then initiate an HTTP request to the server.
  • the purpose of this HTTP request is to send the device information of the device where the client is located to the server.
  • This HTTP request is a POST request. This step can be considered as prior art.
  • For the HTTP POST information refer to the following example:
  • the server After receiving the last HTTP POST request sent by the client, the server needs to return an HTTP response.
  • the server sets the next HTTP request that needs to be initiated by the client in the form of text.
  • the HTTP request is included in the HTTP request.
  • the server needs to perform device management actions on the client. For example, when the server needs the client to update its own email settings, it will return an HTTP response as follows:
  • the last three lines are the contents of the text format carried by the HTTP response.
  • the client After receiving the HTTP response, the client directly sends the text format as the next HTTP request to the server to obtain an HTTP GET request to obtain the email settings of the device where the client is stored on the server. Since the OMA DM management data and HTTP method have GET commands, the client can directly perform an HTTP GET operation on M0.
  • the last three lines are the contents of the text format carried by the HTTP response.
  • the client After receiving the HTTP response, the client directly sends the text format as the next HTTP request to the server to initiate an HTTP PUT request. Since HTTP itself does not support the "Exec" command, subsequent steps 204 and 205 are required to determine the execution action.
  • the client initiates an HTTP request according to the HTTP response one in step 2.
  • the PUT command can also be a POST command. Since the target of the PUT or POST command (Universal Resource Locator) is ". /ManagementMO/Star t" under the root node of the client, it does not exist on the server. This node, so an PUT or POST operation on this URL will cause an error.
  • the purpose of this setup is to have the server return a specific error code.
  • the server After receiving the second request message in step 303, the server returns a second response message due to an error of the URL, and the second response message includes an error code.
  • the second response message further includes information indicating that the executable node performs an operation, that is, the node URI that needs to be executed may be carried again when the error code is sent.
  • An example of the server returning an error code for HTTP request 2 in step 203 is as follows: HTTP/1. 1 410 Gone
  • the error code returned by the server can carry the node URI that needs to be executed again, preventing the client from having the cached executable node URI:
  • the client After receiving the second response message, the client determines, according to the error code, that the second request message set by the server in the first response message is to execute the node.
  • the client determines, according to the first response message, a node that needs to be executed, and the node performs a corresponding operation, specifically by using ht tp in the first request message: //Server Addres s/Cl lent Addres s/ManagementMO/S tar Or determining, according to the second response message, the node that needs to be executed, and the node performs a corresponding operation.
  • the second response message needs to include information indicating that the executable node performs an operation.
  • the embodiment of the invention discloses a method for operating an executable node, which can be directly used.
  • the HTTP standard method manages the device, which facilitates device management directly through the network application, and also reduces the capability requirements for the terminal device.
  • FIG. 3 it is a flowchart of another method for operating an executable node according to an embodiment of the present invention.
  • HTTP Server + HTTP C ient is deployed on the server side, and only the client side is deployed.
  • HTTP C l ient the client requests resources from the server through the standard HTTP method, and the server sends an indication to the client through the response message Response, and the response includes a set HTTP request initiated by the client.
  • the server sets a corresponding HTTP request in the Response, and after receiving the Response, the client initiates an HTTP request set in the Response to the server, and the server responds to the request, and the client responds according to the request.
  • the response determines the execution action.
  • the client receives the trigger message sent by the server, and sends the first request message to the server according to the trigger message.
  • the specific implementation of this step is the same as step 201.
  • the 302. Receive a first response message, where the first response message is a response message that is sent according to the first request message, where the first response message includes information indicating that the executable node performs an operation, and the first response
  • the text directly in the message contains information that indicates that the executable node is performing the operation.
  • the server After receiving the first request message sent by the client, the server returns a response message. In the response, the server sets the next HTTP request required by the client in the form of text, and the server needs to be included in the HTTP request. Device management actions performed on the client.
  • step 202 The specific embodiment of this step is the same as step 202.
  • the client sends a second request message to the server according to the first response message in step 302.
  • the second request message includes address information of the executable node that needs to be executed, that is, the URL of the executable node. Since the node does not exist on the server, an operation error occurs on the operation of the URL, thereby causing the server Return a specific error code
  • step 203 The specific embodiment of this step is the same as step 203.
  • the response message sent, the second response message includes an error code.
  • the server After receiving the second request message in step 303, the server returns a second response message due to an error of the URL, and the second response message includes an error code.
  • the second response message further includes information indicating that the executable node performs an operation, that is, the node URI that needs to be executed may be carried again when the error code is sent.
  • step 204 The specific embodiment of this step is the same as step 204.
  • the client After receiving the second response message, the client determines, according to the error code, that the second request message set by the server in the first response message is to execute the node.
  • the client determines, according to the first response message, a node that needs to be executed, and the node performs a corresponding operation, specifically by using ht tp in the first request message: //Server Addres s/Cl lent Addres s/ManagementMO/S tar Or determining, according to the second response message, the node that needs to be executed, and the node performs a corresponding operation.
  • the second response message needs to include information indicating that the executable node performs an operation.
  • the embodiment of the invention discloses a method for operating an executable node, which can directly manage the device by using an HTTP standard method, which facilitates device management directly through the network application, and also reduces the capability requirement for the terminal device.
  • HTTP Server + HTTP Cl ient is deployed on the server side, and only HTTP is deployed on the client side.
  • Cl ient the client requests resources from the server through the standard HTTP method, and the server sends an indication to the client through the response message Response, and the response includes a set HTTP request initiated by the client.
  • the server sets a corresponding HTTP request in the Response, and after receiving the response, the client initiates an HTTP request set in the Response to the server, and the server responds to the request, and the client The execution of the action is judged based on the response.
  • the specific steps include:
  • the client does not deploy HTTP Server, so it cannot listen to HTTP messages at any time, nor can it receive HTTP requests.
  • the server needs to manage the client, it sends a notification message to the client through WAP PUSH or SIP PUSH or SMS to use for session pull.
  • the client after receiving the trigger message sent by the server, the client sends a first request message to the server according to the trigger message, and the server receives the first request message.
  • the first request message received by the server is the same as step 201.
  • Send a first response message where the first response message is a response message that is sent according to the first request message, where the first response message includes information indicating that the executable node performs an operation, and the first response
  • the text directly in the message contains information that indicates that the executable node is performing the operation.
  • the server After receiving the first request message sent by the client, the server returns a response message. In the response, the server sets the next HTTP request required by the client in the form of text, and the server needs to be included in the HTTP request. Device management actions performed on the client.
  • step 202 The specific embodiment of this step is the same as step 202.
  • the client sends a second request message to the server according to the first response message in step 403.
  • the second request message includes address information of the executable node that needs to be executed, that is, the URL of the executable node. Since the node does not exist on the server, an operation error occurs on the operation of the URL, thereby causing the server Return a specific error code
  • step 203 The specific embodiment of this step is the same as step 203.
  • the server After receiving the second request message in step 404, the server returns a second response message due to an error of the URL, and the second response message includes an error code.
  • the second response message further includes information indicating that the executable node performs an operation, that is, the node URI that needs to be executed may be carried again when the error code is sent.
  • step 204 The specific embodiment of this step is the same as step 204.
  • step 406 may be further included after step 405.
  • the client After receiving the second response message, the client determines, according to the error code, that the second request message set by the server in the first response message is to execute the node.
  • Client based The first response message determines a node that needs to be executed, and the node performs a corresponding operation, specifically, by using ht tp: //Server Addres s/Cl lent Addres s/ManagementMO/S tar t in the first request message; Or determining, according to the second response message, a node that needs to be executed, where the node performs a corresponding operation.
  • the second response message needs to include information indicating that the executable node performs an operation.
  • the embodiment of the invention discloses a method for operating an executable node, which can directly manage the device by using an HTTP standard method, which facilitates device management directly through the network application, and also reduces the capability requirement for the terminal device.
  • HTTP Server + HTTP Cl ient is deployed on both the server side and the client side. Both parties interact with each other using standard HTTP methods to carry device management data.
  • the server needs to perform an action on the executable node on the client, the first HTTP method is used to send a notification message to the client. After the client authenticates the server, the device information is returned.
  • the server uses the standard HTTP method to represent the executable node. Execution action. Specific steps are as follows:
  • the server sends a first request message, and the first request message is a GET request as follows, and carries a notification message therein for the client to verify the identity of the server.
  • the client is required to return device information, which facilitates subsequent device management.
  • This step can be considered as prior art.
  • the first request message is:
  • the client After the client verifies the notification message of the server, it returns a response message to the server, and carries the device information therein.
  • This step can be considered as a prior art, for example, the second response message is: HTTP/1. 1 200 0K
  • the node value of the executable node in the M0 of the 0MA DM does not exist.
  • node values are added to all executable nodes.
  • the attribute of the executable node is "Exec”
  • there is no node value in the existing standard and the node value is now added to all nodes whose attribute is "Exec”.
  • the value may be a string, a number, a character, or the like.
  • the PUT or POST request does not carry the modified value, just triggers the executable action.
  • the value may be a string.
  • the PUT or POST request needs to modify the node value of the executable node to the string "Exec".
  • the client will determine that it is using an execution command for that node.
  • the client after receiving the PUT or POST request of the method 1 in step 303, the client first determines After the client determines that the node attribute is "Exec", the client determines that the purpose of the operation is to execute the node, and the client is triggered to perform the corresponding action.
  • Method 2 after receiving the PUT or POST request of the method 2 in step 303, the client first determines the attribute of the target node, and after the client determines that the node attribute is "Exec", it continues to determine whether the value written to the node is a character.
  • the embodiment of the invention discloses a method for operating an executable node, which can directly manage the device by using an HTTP standard method, which facilitates device management directly through the network application, and also reduces the capability requirement for the terminal device.
  • FIG. 6 it is a flowchart of another method for operating an executable node according to an embodiment of the present invention.
  • HTTP Server + HTTP C ent is deployed on both the server side and the client side.
  • the two parties use the standard HTTP method to carry device management data for interaction.
  • the server needs to perform an action on the executable node on the client, the first HTTP method is used to send a notification message to the client. After the client authenticates the server, the device information is returned.
  • the server uses the standard HTTP method to represent the executable node. Execution action. Specific steps are as follows:
  • the server sends a first request message, and the first request message is a GET request as follows, and carries a notification message therein for the client to verify the identity of the server.
  • the client is required to return device information, which facilitates subsequent device management.
  • the specific embodiment of this step is the same as step 501.
  • step 602. Send a first response message, where the first response message includes the device information. After the client verifies the notification message of the server, it returns a response message to the server, carrying the device information therein.
  • the specific embodiment of this step is the same as step 502.
  • the node in the M0 of the OMA DM does not have a node value.
  • node values are added to all executable nodes.
  • the attribute of the executable node is "Exec”.
  • the embodiment of the invention discloses a method for operating an executable node, which can directly manage the device by using an HTTP standard method, which facilitates device management directly through the network application, and also reduces the capability requirement for the terminal device.
  • FIG. 7 it is a flowchart of another method for operating an executable node according to an embodiment of the present invention.
  • HTTP Server + HTTP C ent is deployed on both the server side and the client side.
  • the two parties use the standard HTTP method to carry device management data for interaction.
  • the server needs to perform an action on the executable node on the client, the first HTTP method is used to send a notification message to the client. After the client authenticates the server, the device information is returned.
  • the server uses the standard HTTP method to represent the executable node. Execution action. Specific steps are as follows:
  • the server sends a first request message, and the first request message is a GET request as follows, and carries a notification message therein for the client to verify the identity of the server.
  • the client is required to return device information, which facilitates subsequent device management.
  • the specific embodiment of this step is the same as step 501.
  • step 702. Receive a first response message, where the first response message includes the device information. After the client verifies the notification message of the server, it returns a response message to the server, carrying the device information therein.
  • the specific embodiment of this step is the same as step 502.
  • the node value of the executable node in the M0 of the OMA DM does not exist.
  • node values are added to all executable nodes.
  • the attribute of the executable node is "Exec”
  • there is no node value in the existing standard and the node value is now added to all nodes whose attribute is "Exec”.
  • the server needs to perform PUT on the executable node when it needs to execute an executable node on the client. Or POST request.
  • step 704 may be further included after step 703.
  • the embodiment of the invention discloses a method for operating an executable node, which can directly manage the device by using an HTTP standard method, which facilitates device management directly through the network application, and also reduces the capability requirement for the terminal device.
  • the embodiment of the present invention discloses a client.
  • the client 80 includes a receiving unit 801, a message parsing unit 802, a message generating unit 803, and a sending unit.
  • the receiving unit 801 is configured to receive a message sent by the server, where the message sent by the server includes a trigger message, a first response message, and a second response message, where the trigger message is used Triggering a client to initiate a request message, the trigger message is a WAP PUSH or a SIP PUSH or a short message; the first response message includes information indicating that the executable node performs an operation; the second response message includes an error code, where the The second response message also contains information indicating that the executable node performs the operation.
  • the message sent by the server is either a first request message and a second request message, where the first request message includes an indication of the identity verification information and the requesting device information, and the second request message is used to indicate that the node is
  • the execution node also contains information indicating that the executable node performs the operation.
  • the message parsing unit 802 is configured to parse the message received by the receiving unit 801.
  • the message generating unit 803 is configured to generate a message according to the parsing result of the message parsing unit 802.
  • the sending unit 804 is configured to send a message to the server, where the message sent to the server includes a first request message and a second request message, where the first request message is used to send the device information of the client 80 to the The server, the second request message is used to enable the server to return a specific error code; the message sent to the server is a first response message, and the first response message includes the device information.
  • the determining unit 805 determines an executable node that the server needs to operate according to the parsing result of the message parsing unit 802.
  • the executable node 806 is a node in the client management object, and has an executable attribute for executing an operation command sent by the server to complete the corresponding operation.
  • the embodiment of the present invention discloses a client that operates on an executable node, and can directly manage the device by using an HTTP standard method, which facilitates device management directly through the network application, and also reduces the capability requirement for the terminal device.
  • the embodiment of the present invention discloses a server.
  • the server 90 includes a receiving unit 901, a message parsing unit 902, and a message generating unit 903.
  • Sending unit 904 where:
  • the receiving unit 901 is configured to receive a message sent by the client, where the message sent by the client includes a first request message and a second request message, where the first request message is used to send device information of the device where the client is located to The server 90, the second request message is used to cause the server 90 to return a specific error code; the message sent by the client is a first response message, and the first response message includes the device information.
  • the message parsing unit 902 is configured to parse the message received by the receiving unit 901.
  • the message generating unit 903 is configured to generate a message according to the parsing result of the message parsing unit 902.
  • the sending unit 904 is configured to send a message to the client, where the message sent to the client includes a trigger message, a first response message, and a second response message, where the trigger message is used to trigger the client to initiate the request message, and the trigger message is The WAP response or the IP PUSH or the short message; the first response message includes information indicating that the executable node performs an operation; the second response message includes an error code, and the second response message further includes an indication The information that the executable node performs the operation.
  • the message sent to the client is either a first request message and a second request message, where the first request message includes an indication of the identity verification information and the requesting device information; the second request message is used to indicate the node It is an executable node that contains information indicating that the executable node performs operations.
  • the embodiment of the invention discloses a server that operates on an executable node, and can directly manage the device by using an HTTP standard method, which is convenient for directly managing the device through the network application, and also reduces the capability requirement for the terminal device.
  • the present invention is implemented
  • the example discloses a system, as shown in FIG. 10, including a client 80 and a server 90.
  • the client 80 includes a receiving unit 801, a message parsing unit 802, a message generating unit 803, a sending unit 804, a determining unit 805, and an executable node 806, where:
  • the receiving unit 801 is configured to receive a message sent by the server, where the message sent by the server includes a trigger message, a first response message, and a second response message, where the trigger message is used to trigger a client to initiate a request message, and the trigger message is P PUSH Or the SIP PUSH or the short message; the first response message includes information indicating that the executable node performs an operation; the second response message includes an error code, and the second response message further includes an indication executable node The information that performs the operation.
  • the message sent by the server is either a first request message and a second request message, where the first request message includes an indication of the identity verification information and the requesting device information, and the second request message is used to indicate that the node is
  • the execution node also contains information indicating that the executable node performs the operation.
  • the message parsing unit 802 is configured to parse the message received by the receiving unit 801.
  • the message generating unit 803 is configured to generate a message according to the parsing result of the message parsing unit 802.
  • the sending unit 804 is configured to send a message to the server, where the message sent to the server includes a first request message and a second request message, where the first request message is used to send device information of the device where the client 80 is located.
  • the second request message is used to cause the server 90 to return a specific error code; the message sent to the server is a first response message, and the first response message includes the Device Information.
  • the determining unit 805 determines an executable node that the server 90 needs to operate according to the parsing result of the message parsing unit 802.
  • the executable node 806 is a node in the client management object, and has an executable attribute for executing an operation command sent by the server 90 to complete the corresponding operation.
  • the server includes a receiving unit 901, a message parsing unit 902, a message generating unit 903, and a sending unit 904, where:
  • the receiving unit 901 is configured to receive the message sent by the client 80, where the message sent by the client includes a first request message and a second request message, where the first request message is used to send device information of the device where the client is located.
  • the second request message is used to cause the server 90 to return a specific error code;
  • the message sent by the client is a first response message, and the first response message includes the Device Information.
  • the message parsing unit 902 is configured to parse the message received by the receiving unit 901.
  • the message generating unit 903 is configured to generate a message according to the parsing result of the message parsing unit 902.
  • the sending unit 904 is configured to send a message to the client, where the message sent to the client includes a trigger message, a first response message, and a second response message, where the trigger message is used to trigger a client to initiate a request message, and trigger a message.
  • the first response message includes information indicating that the executable node performs an operation;
  • the second response message includes an error code, and the second response message further includes an indication The information that the executable node performs the operation.
  • the message sent to the client is either a first request message and a second request message, where the first request message includes an indication of the identity verification information and the requesting device information, and the second request message is used to indicate the node. It is an executable node that contains information indicating that the executable node performs operations.
  • the embodiment of the invention discloses a system for operating an executable node, which can directly manage the device by using an HTTP standard method, which facilitates device management directly through the network application, and also reduces the capability requirement for the terminal device.
  • All or part of the steps of implementing the above method embodiments may be performed by hardware related to the program instructions, and the program may be stored in a computer readable storage medium, and when executed, the steps including the foregoing method embodiments are performed.
  • the storage medium includes: R0M, RAM, disk or optical disc, and other media that can store program code.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)
  • Telephonic Communication Services (AREA)

Abstract

Des modes de réalisation de la présente invention concernent le domaine technique des communications, et portent spécifiquement sur un procédé et un système pour exploiter un nœud exécutable. Le procédé décrit pour exploiter le nœud exécutable consiste à : recevoir un message déclencheur, transmettre un premier message de requête ; recevoir un premier message de réponse, le premier message de réponse comprenant des informations donnant au nœud exécutable l'instruction d'exécuter une opération ; transmettre un second message de requête sur la base du premier message de réponse ; recevoir un second message de réponse, le second message de réponse comprenant un code d'erreur ; confirmer le déclenchement d'une opération exécutable sur la base du code d'erreur figurant dans le second message de réponse. Un système pour exploiter le nœud exécutable est également décrit. L'emploi des modes de réalisation de la présente invention permet d'utiliser directement un procédé standard HTTP pour la gestion d'un dispositif, ce qui facilite la réalisation de la gestion de dispositif directement par l'intermédiaire d'une application réseau, tout en réduisant en même temps des exigences sur des capacités de dispositif terminal.
PCT/CN2012/078904 2011-07-29 2012-07-20 Procédé et système pour exploiter un nœud exécutable WO2013017020A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110215400.0A CN102904742B (zh) 2011-07-29 2011-07-29 对可执行节点的操作方法及系统
CN201110215400.0 2011-07-29

Publications (1)

Publication Number Publication Date
WO2013017020A1 true WO2013017020A1 (fr) 2013-02-07

Family

ID=47576793

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/078904 WO2013017020A1 (fr) 2011-07-29 2012-07-20 Procédé et système pour exploiter un nœud exécutable

Country Status (2)

Country Link
CN (1) CN102904742B (fr)
WO (1) WO2013017020A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10266515B2 (en) 2013-12-30 2019-04-23 Lifesci Pharmaceuticals, Inc. Therapeutic inhibitory compounds
US10301284B2 (en) 2016-07-11 2019-05-28 Lifesci Pharmaceuticals, Inc. Therapeutic inhibitory compounds
US10308637B2 (en) 2015-07-01 2019-06-04 Lifesci Pharmaceuticals, Inc. Therapeutic inhibitory compounds

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101159958A (zh) * 2007-11-08 2008-04-09 中兴通讯股份有限公司 维护节点状态的方法
CN101313512A (zh) * 2006-08-11 2008-11-26 华为技术有限公司 一种通信系统中终端执行管理操作的方法、终端和系统
CN101374295A (zh) * 2007-08-21 2009-02-25 华为技术有限公司 选择接入网络的方法和终端
US20110004654A1 (en) * 2008-12-22 2011-01-06 Nokia Corporation Device management session trigger

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101313512A (zh) * 2006-08-11 2008-11-26 华为技术有限公司 一种通信系统中终端执行管理操作的方法、终端和系统
CN101374295A (zh) * 2007-08-21 2009-02-25 华为技术有限公司 选择接入网络的方法和终端
CN101159958A (zh) * 2007-11-08 2008-04-09 中兴通讯股份有限公司 维护节点状态的方法
US20110004654A1 (en) * 2008-12-22 2011-01-06 Nokia Corporation Device management session trigger

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"OMA Device Management Protocol. Approved Version 1.2", OPEN MOBILE ALLIANCE, 9 February 2007 (2007-02-09) *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10266515B2 (en) 2013-12-30 2019-04-23 Lifesci Pharmaceuticals, Inc. Therapeutic inhibitory compounds
US11021463B2 (en) 2013-12-30 2021-06-01 Attune Pharmaceuticals, Inc. Therapeutic inhibitory compounds
US10308637B2 (en) 2015-07-01 2019-06-04 Lifesci Pharmaceuticals, Inc. Therapeutic inhibitory compounds
US10301284B2 (en) 2016-07-11 2019-05-28 Lifesci Pharmaceuticals, Inc. Therapeutic inhibitory compounds
US10781200B2 (en) 2016-07-11 2020-09-22 Attune Pharmaceuticals, Inc. Therapeutic inhibitory compounds

Also Published As

Publication number Publication date
CN102904742B (zh) 2015-10-07
CN102904742A (zh) 2013-01-30

Similar Documents

Publication Publication Date Title
WO2021037175A1 (fr) Procédé de gestion de tranche de réseau et dispositif associé
JP2007525870A (ja) 装置管理システム内における管理ノードの指定
WO2008031314A1 (fr) Procédé de communication d'informations concernant la capacité d'un dispositif et terminal
EP2320329A1 (fr) Dispositif et système correspondant pour un service composite, et procédé d'établissement et d'utilisation du service composite
KR20170033424A (ko) 경량 기기 간 프로토콜을 디바이스 관리 프로토콜과 상호연동하기
WO2010034257A1 (fr) Procédé de configuration et de gestion d’un terminal et dispositif de terminal
WO2007112673A1 (fr) Procédé de négociation d'information de capacité de dispositif, procédé, système et dispositif de synchronisation
JP2005341535A (ja) モバイル装置の管理ツリーにおける接続オブジェクト
CN102427409A (zh) 基于网络配置协议的配置数据提交方法及服务器
EP2512064A1 (fr) Procédé et appareil de configuration de données
JP2008514079A (ja) モバイル・デバイスおよびサービスを管理する統合された方法および装置
WO2018059150A1 (fr) Procédé et appareil de mise en œuvre de capacité ouverte
WO2007025428A1 (fr) Procede, systeme et dispositif terminal de configuration de parametres de composants logiciels
WO2010028571A1 (fr) Procédé d’émission de gros objets de données, système d’émission, dispositif émetteur et dispositif récepteur
KR20120107022A (ko) 개인 정보 동기화 방법 및 장치
WO2012113329A1 (fr) Procédé et dispositif de gestion de dispositifs
WO2011127847A2 (fr) Procédé, appareil et terminal mobile pour mettre à jour un contenu de service de données de complément de service non structuré
US9237206B2 (en) Method and apparatus for updating personal information in communication system
WO2013017020A1 (fr) Procédé et système pour exploiter un nœud exécutable
WO2008145047A1 (fr) Procédé et dispositif pour initier la connexion de session
WO2010108432A1 (fr) Procédé et appareil de traitement de services, systèmes de communication et dispositif connexe
Gligorić et al. M2M device management in LTE networks
EP2424162A1 (fr) Procédé, appareil et système de gestion de dispositifs
EP3416351B1 (fr) Procédé d'implémentation, appareil et système destinés à l'accès à distance
EP4064616A1 (fr) Procédé et dispositif de souscription d'informations de configuration

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12820335

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12820335

Country of ref document: EP

Kind code of ref document: A1