WO2010043150A1 - Procédé permettant de rapporter des informations de dispositif, terminal utilisateur et serveur associés - Google Patents

Procédé permettant de rapporter des informations de dispositif, terminal utilisateur et serveur associés Download PDF

Info

Publication number
WO2010043150A1
WO2010043150A1 PCT/CN2009/074255 CN2009074255W WO2010043150A1 WO 2010043150 A1 WO2010043150 A1 WO 2010043150A1 CN 2009074255 W CN2009074255 W CN 2009074255W WO 2010043150 A1 WO2010043150 A1 WO 2010043150A1
Authority
WO
WIPO (PCT)
Prior art keywords
server
device information
reported
user terminal
information
Prior art date
Application number
PCT/CN2009/074255
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 WO2010043150A1 publication Critical patent/WO2010043150A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration

Definitions

  • the present invention relates to the field of mobile communications, and in particular, to a method for reporting device information, a user terminal, and a server. Background technique
  • the Open Mobile Alliance Device Management (OMA DM) VI.2 specification is a standard developed by the OMA International Organization for Standardization to implement user terminal management.
  • the DM system provides a low-cost solution for third-party management and setting of environment and configuration information in wireless network user terminals (such as mobile terminals and functional objects in terminals) to solve these wireless network user terminals during use.
  • the problem is to install and upgrade software and firmware through the over-the-air (OTA) mode, and provide more personalized and personalized services to enhance the user experience.
  • Third parties can be mobile operators.
  • OMA DM device management consists of two phases, the first phase is called initialization or boot
  • the second phase is the management phase.
  • the server can manage or provision the user terminal ( Provisioning).
  • the DM management phase can be divided into two phases: the session establishment phase and the management session phase, as shown in Figure 1 for the prior art DM. Schematic diagram of the management phase of equipment management.
  • OMA DS Data Synchronization
  • a typical application for DS is data synchronization between a mobile terminal and a web server.
  • DS can also be used for peer-to-peer data synchronization, such as data synchronization between two personal computers.
  • the terminal and the server can send each other's changed data to ensure the synchronization of the data of both parties.
  • the user has the same address book in the mobile phone, personal digital assistant (PDA), office, and home computer.
  • PDA personal digital assistant
  • the DS can be passed.
  • FIG. 2 is a schematic flowchart of data synchronization between a terminal and a server in the prior art.
  • the inventors have found that at least the following problems exist in the prior art: As can be seen from FIG. 1 and FIG. 2, whether the device management session service or the data synchronization session service is initiated, between the terminal and the server, When a new session is initiated, the terminal needs to report the device information to the server, and the basic device information of the terminal does not change easily. Therefore, the device information is reported every time the session is established, which will undoubtedly cause waste of transmission resources. Summary of the invention
  • the embodiments of the present invention provide a method for reporting device information, a user terminal, and a server, which can effectively report device information when the user terminal and the server establish a service session, thereby saving transmission resources.
  • an embodiment of the present invention provides a method for reporting device information, including: when establishing a session service with a server, determining whether to save the reported identity information that has been reported to the server for reporting device information; When the report identifier information is not saved, the device information is reported to the server; and the report identifier information that the device information is reported to the server is saved.
  • the embodiment of the invention further provides a user terminal, including:
  • a judging module configured to determine, when the session service is established with the server, whether the identifier information that has been reported to the server for reporting the device information is saved;
  • a first reporting module configured to report device information to the server when the report identifier information is not saved
  • the saving module is configured to save, when the device information is reported to the server, the report identifier information that has been reported to the server by the device.
  • the embodiment of the invention further provides a server, including:
  • a determining module configured to determine whether the user terminal reports device information when establishing a service session with the user terminal
  • a saving module configured to save the device information when the user terminal reports the device information.
  • the user terminal When reporting the device information to the server, the user terminal saves the report identifier information that has been sent to the server to report the device information.
  • the new session service it is determined whether the identifier information that has been reported to the server for reporting the device information is saved.
  • the device information When the device information has been reported to the server, it is not necessary to report again, which saves transmission resources and reduces communication traffic.
  • FIG. 1 is a schematic flowchart of a management phase of a DM device management in the prior art
  • FIG. 2 is a schematic flowchart of data synchronization between a terminal and a server in the prior art
  • FIG. 3 is a schematic structural diagram of an OMA DM system according to an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of a DM Account management object according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of a DM Dev lnfo management object according to an embodiment of the present invention
  • FIG. 6 is a schematic flowchart of a method for reporting device information according to an embodiment of the present invention
  • FIG. 7 is a schematic diagram of a DM server management subtree according to an embodiment of the present invention
  • FIG. 8 is a schematic diagram of a DM Account management object according to an embodiment of the present invention
  • FIG. 9 is a schematic diagram of a DS server management subtree according to an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of a user terminal according to an embodiment of the present invention.
  • FIG. 11 is another schematic structural diagram of a user terminal according to an embodiment of the present invention.
  • FIG. 12 is still another schematic structural diagram of a user terminal according to an embodiment of the present invention.
  • FIG. 13 is a schematic structural diagram of a server according to an embodiment of the present invention.
  • FIG. 14 is a schematic diagram of a specific scenario for recording an identifier of a server that has been identified by a reporting device by using a DM management object tree according to an embodiment of the present invention
  • FIG. 15 is a schematic diagram of another specific scenario for recording an identifier of a server that has been identified by a reporting device by using a DM management object tree according to an embodiment of the present invention
  • FIG. 16 is a schematic diagram of a specific scenario for recording an identifier of a server that has been identified by a reporting device by using a DS management object tree according to an embodiment of the present invention. detailed description
  • the embodiment of the present invention provides a method for reporting device information, a user terminal, and a server.
  • the user terminal reports device information to the server, and saves the report information that has been reported to the server.
  • a new session service is initiated, it is determined whether the device information has been reported to the server according to the saved report information.
  • the device does not need to report again, which saves the transmission resource.
  • the object of the present invention can be achieved by storing the report identification information in a management object tree on the user terminal.
  • the managed object (Management Object, MO) in the user terminal generates a tree of the corresponding hierarchical structure according to a certain standard, and manages each node of the object tree ( That is, the managed object) is identified by a unique Uniform Resource Ident if ier (URI), each node Both can be managed by the server, and the server achieves the purpose of controlling the managed objects in the user terminal by operating on these nodes.
  • MO Management Object
  • URI Uniform Resource Ident if ier
  • FIG. 3 is a schematic structural diagram of an OMA DM system according to an embodiment of the present invention, where a DM proxy (Agent) in a user terminal is used to interpret and execute a management command delivered by a device management server, and the DM management object tree may be considered. It is an interface that the device management server manages the user terminal through the DM protocol.
  • a DM proxy Agent in a user terminal
  • the DM management object tree may be considered. It is an interface that the device management server manages the user terminal through the DM protocol.
  • the DM management object tree and managed objects are composed of nodes, such as root nodes, internal nodes, and leaf nodes.
  • the nodes have their own Framework attributes.
  • the framework attributes of a node include the access type (Acces sType ), the default value ( Defaul tVa lue ), the number of occurrences ( Occurrence ), the node type ( DFType ), etc., to identify the characteristics of a node.
  • DFType describes its MIME type for the leaf node and its management object identifier (M0I) for the internal node or is null.
  • M0I management object identifier
  • there is a class of unnamed nodes in the management object tree which acts as a placeholder. When a server or user terminal instantiates it, it will be named. This type of node is called an X node.
  • FIG. 4 and FIG. 5 are schematic diagrams showing the structure of a DM Account management object and a DM Devlnfo management object according to an embodiment of the present invention.
  • FIG. 6 is a schematic flowchart of a method for reporting device information according to an embodiment of the present invention, where the method includes the following steps:
  • Step 61 When establishing a session service with the server, determine whether the report identifier information indicating that the device information has been reported to the server is saved. Step 62: Report the device information to the server when the report identifier information is not saved. Step 63: When reporting the device information to the server, save the report identifier information that the identifier has reported to the server.
  • Step 64 When the reported identifier information is saved, the subsequent session service is directly performed without reporting the device information.
  • the foregoing report identifier information may be any identifier information indicating that the device information has been reported to the server, for example, an identity identification number (ID) of the server, a name of the server, an address of the server, and the The time when the server reports the device information, and/or the identifier child node that identifies whether the device information has been reported to the server.
  • ID identity identification number
  • step 61 when it is determined in step 61 that the report identification information has been saved, it indicates that the device information has been reported to the server, and there is no need to report again.
  • the above methods also include:
  • the device information When receiving the request for acquiring the device information sent by the server, the device information is reported, and the report identifier information indicating that the device information has been reported to the server is saved.
  • the reporting identifier information may be saved in a plurality of manners.
  • the reporting identifier information may be saved in the management object tree of the user terminal, thereby querying the management object. Tree, to determine whether device information has been reported to the server.
  • the above identification information can be saved in the management object tree in two ways.
  • the first method is to create a server management subtree in the management object tree, and add a child node that identifies the device information that has been reported to the server.
  • the saved information of the server includes: the ID of the server, and may of course include the server.
  • Other reported information such as the address of the server, the time of reporting the device information, etc., as shown in FIG. 7 is a schematic diagram of the DM server management subtree according to the embodiment of the present invention.
  • the server REV ( ServerRev ) node is the parent node of all device management servers that have received device information.
  • the description of the node is shown in the following table: Status Tree Forma t Min. Acces s
  • the node is a placeholder for the device management server that has received the device information.
  • the description of the node is shown in the following table:
  • the server ID (Server lD) node is a leaf node, and the ID of the device management server that stores the received device information is used to uniquely indicate the identity of the device management server.
  • the description of the node is as follows:
  • the address (Addres s) node is a leaf node, indicating the address of the corresponding device management server.
  • the time (Time) node is a leaf node, indicating the time when the device information was reported to the device management server.
  • the parameter is optional.
  • the description of the node is as follows:
  • MO I This is the leaf node, which stores the identifier of the reported device information management object. This parameter is optional.
  • the description of the node is as follows:
  • the server management subtree is first queried to determine whether the device information needs to be reported to the server, and the identifier is saved to the server in the server management subtree.
  • the device information is not required to be reported again.
  • the device information is reported to the server, and the report is reported to the server.
  • a child node that identifies that the device information has been reported to the server is added.
  • the child node of the server management subtree needs to be cleared, so that the updated device information is re-reported when a new session is initiated.
  • the server may change the report identifier information saved on the server management sub-tree of the user terminal, and the specific implementation method is: when the server needs to change the report identifier information, the server sends a request for changing the report identifier information to the user terminal, where the user terminal Upon receiving the request, the child node that identifies that the device information has been reported to the server is deleted, so that the device information is re-reported when a new session is initiated.
  • the second method is: in each DM Account management object, an identifier sub-node for identifying whether the device information has been reported to the corresponding server, as shown in FIG. 8 is a schematic diagram of the DM Account management object according to the embodiment of the present invention.
  • the application ID (AppID), the server ID (Server ID), and the name (Name) node are existing nodes, which respectively represent the session service type, the server ID, and the server name.
  • the embodiment of the present invention increases the cornerstone of the existing node. Identification of REV (FlagRev), time (Time) and M0I nodes;
  • the flagRev node is the above-mentioned identifier sub-node for identifying whether the device information has been reported to the server.
  • the node adopts a Boolean type. When the node value is "1", it indicates that the device information has been reported to the server corresponding to the DM Account management object. If the node value is "0", the device information is not reported to the server.
  • the description of the node is as follows:
  • the Time node is a leaf node, indicating the time when the device information was reported to the server.
  • M01 is a leaf node, which indicates the identifier of the reported device information management object. This parameter is an optional parameter.
  • the description of the node is as follows:
  • the server When the user terminal initiates a new device management session to the server, first querying the identifier child node in the DM Account management object corresponding to the server, determining whether the device information needs to be sent, and querying the identifier child node in the DM Account management object.
  • the node value when the device information has been reported to the server, the device information is not required to be reported again; when the identifier child node of the DM Account management object is queried, the device information is not reported to the server,
  • the server reports the device information, and when the device information is reported, the node value of the identifier child node is identified as having reported the device information to the server.
  • the node values of all the identified child nodes are identified as the unreported device information, so that the updated device information is re-reported when a new session is initiated.
  • the server may also change the report identifier information that is saved on the server management sub-tree of the user terminal, and the specific implementation method is: when the server needs to change the report identifier information, the server sends a request for changing the report identifier information to the user terminal, where the user When receiving the request, the terminal identifies the identifier sub-node corresponding to the server as the unreported device information, so that the device information is re-reported when a new session is initiated.
  • the node value of the F lagRev node in the DM Account management object corresponding to the server is set to 0.
  • the method for storing the report identification information of the device information to the server may be used to manage the first method in the session service, that is, in the management object tree of the user terminal, adding the identifier to the office
  • FIG. 9 A sub-node of the server reporting device information is shown in FIG. 9 as a schematic diagram of a DS server management subtree according to an embodiment of the present invention.
  • the user terminal needs to report the capability information of the database to be synchronized in addition to the device information of the user. Therefore, in order to reduce the waste of the wireless resources, the server management subtree saves the reported device information. In addition to the logo, you can also save the ID of the reported database capability information.
  • the ServerRev node is the parent node of all synchronization servers that have received device information or database capability information.
  • the description of the node is shown in the following table: S tatus Tree Format Min. Acces s
  • the REQUIRED One Node Get node is a placeholder for the synchronization server that has received device information or database capability information.
  • the description of the node is shown in the following table:
  • the Server lD node is a leaf node. It records the synchronization server ID that has received the device information or database capability information, and is used to uniquely indicate the identity of the synchronization server.
  • the description of the node is as follows:
  • the time node is a leaf node, indicating the time when the device information or database capability information is reported to the synchronization server.
  • the parameter is optional.
  • the description of the node is as follows:
  • the data storage ID ( Da taStorelD ) node is a leaf node, which represents the device information management object or the identifier of the database capability information.
  • the description of the node is as follows:
  • the DS server management subtree is first queried to determine whether the device information needs to be reported, and the identifier is saved in the DS server management subtree.
  • the device information is reported to the synchronization server when the child node of the DS server management subtree is not saved and the device information is reported to the server.
  • the device information is reported, a child node that identifies that the device information has been reported to the server is added to the DS server management subtree.
  • the child node of the DS server management sub-tree needs to be cleared, so that the updated device information is re-reported when a new session is initiated.
  • the server may change the report saved on the DS server management subtree of the user terminal.
  • the identification information is implemented by: when the server needs to change the information, the server sends a request for changing the report identifier information to the user terminal, and when receiving the request, the user terminal deletes the identifier that has sent the device information to the server.
  • the node in order to re-report the device information when a new session is initiated.
  • the method for reporting the device information reported to the server is saved, and when the new session is initiated to the server, the report information is queried.
  • the device information is not reported to the server again, which saves transmission resources and reduces communication traffic.
  • FIG. 10 is a schematic structural diagram of a user terminal according to an embodiment of the present invention, where the user terminal includes:
  • the judging module 1 01 is configured to determine, when the session service is established with the server, whether the identifier information of the device information that has been reported to the server is saved.
  • the first reporting module 102 is configured to report device information to the server when the report identifier information is not saved.
  • the saving module 1 03 is configured to: after reporting the device information to the server, save the report identifier information that has been reported to the server by the device.
  • the report identifier information is any one or more of the following: an identifier number of the server, a name of the server, an address of the server, a time for reporting the device information to the server, and whether the identifier has been sent
  • the server reports an identifier child node of the device information.
  • the determining module 101 determines whether the information has been reported to the server by the user terminal, and determines whether the information has been reported to the server.
  • the user terminal may save the report identifier in multiple manners.
  • the management object tree may be queried by using the management object tree in the management object tree of the user terminal to identify the report information that has been reported to the server. To determine whether device information has been reported to the server.
  • the server management subtree can be used to save the report information indicating that the device information has been reported to the server.
  • FIG. 11 is another schematic structural diagram of a user terminal according to an embodiment of the present invention, in FIG. 10
  • the above user terminal further includes:
  • the creating module 104 is configured to create a server management subtree in the management object tree of the user terminal.
  • the saving module 103 includes:
  • the first saving unit 1 031 is configured to add, on the server management subtree, a child node that identifies that the device information has been reported to the server when the device information is reported to the server.
  • the user terminal needs to clear the child node in the server management sub-tree, so that when the new session is initiated, the updated device information is re-reported, and therefore, the user
  • the terminal also includes:
  • the first processing module 105 is configured to clear the child nodes of the server management subtree when the device information changes.
  • the server may send a request for changing the report identifier information to the user terminal.
  • the user terminal may delete the save identifier to report the device information to the server.
  • the second processing module 106 is configured to: when receiving the request to change the report identifier information of the server, delete the child node that identifies the device information to the server.
  • the existing DM Account management object may be used to save the upper "3 ⁇ 4 identification information. .
  • FIG. 12 is still another schematic structural diagram of a user terminal according to an embodiment of the present invention.
  • the user terminal further includes:
  • the adding module 107 is configured to add, in each DM Account management object, an identifier child node that is used to identify whether the device information has been reported to the corresponding server.
  • the saving module 103 includes:
  • the second saving unit 1 032 is configured to: when the device information is reported to the server, identify a node value of the identifier sub-node corresponding to the server as that the device information has been reported.
  • the user terminal When the device information of the user terminal changes, the user terminal needs to identify the node value of the identifier child node as not being the device information, so as to re-report the updated device when a new session is initiated.
  • the user terminal further includes:
  • the third processing module 108 is configured to identify, when the device information changes, the node values of all the identifier child nodes as not reporting the device information.
  • the server may send a request for changing the report identifier information to the user terminal.
  • the user terminal may identify the node value of the identifier child node corresponding to the server. If the device information is not reported, the device information is re-reported when a new device management session is initiated. Therefore, the user terminal further includes: a fourth processing module 109, configured to receive the change report of the server When the request for the information is identified, the node value of the identifier child node corresponding to the server is identified as not reporting the device information.
  • the foregoing user terminal further includes:
  • the second reporting module 11 0 is configured to report the device information to the server when receiving the request for acquiring the device information sent by the server.
  • the user terminal after reporting the device information to the server, saves the report identifier information that has been reported to the server by the device, and when the new session is initiated to the server, the report information is sent according to the report. , no need to report device information again, saving transmission resources and reducing communication traffic.
  • FIG. 13 is a schematic structural diagram of a server according to an embodiment of the present invention.
  • the server includes: a determining module 21, configured to determine, when establishing a service session with a user terminal, whether the user terminal reports device information.
  • the saving module 22 is configured to save the device information when the user terminal reports the device information.
  • the query module 23 is configured to query whether the device information has been saved when the user terminal does not report the device information.
  • the obtaining module 24 is configured to send, to the user terminal, a request for acquiring the device information when the device information is not saved.
  • the above server may be the device management server or the synchronization server in the above embodiment.
  • the server may send a request to the user terminal to change the reported identification information, so that when the user terminal initiates a new session service, the user terminal re-reports the device information. Therefore, the server further includes:
  • the requesting module 25 is configured to send a change identifier to the user terminal, and report the device letter to the server Request for information on >3 ⁇ 4.
  • the server provided by the foregoing embodiment may save the device information after receiving the device information reported by the user terminal, and query whether to save the device information when the user terminal does not report the device information in the next session. When the device information has been saved, it is not necessary to acquire the device information from the user terminal.
  • the method for reporting device information is described in detail below in the specific application scenario of the device management session service and the data synchronization session service.
  • a device management session service needs to be established between the user terminal and the device management server, and the IMEI (International Mobile Identity Identification) of the user terminal is 493005100592800, and the management thereof is performed.
  • the device management server preset in the DM Account management object in the object tree is: DM Server, the address of the device management server is: ht tp: / /www. syncml. org/dm- server.
  • the user terminal and the device management server perform a device management session at the time point: 20080202T020202Z. It is assumed that the device management session is the first device management session of the user terminal and the device management server. Therefore, the user terminal needs to report the device information to the server. After the device information is reported, the user terminal adds the child node to the created server management subtree to save the report identifier information that has been reported to the device management server, indicating that the device information has been reported to the server. At the time, the server management subtree of the user terminal is as shown in FIG. 14, where node 1 represents the first child node.
  • the user terminal When the user terminal initiates a new device management management session to the device management server, the user terminal first queries whether the server identification sub-tree has saved the report identification information that has been reported to the device management server, and the query information is When the server management sub-tree stores the report identifier information that has been reported to the device management server, that is, the device information has been reported to the device management server, the initialization session information sent to the device management server is No longer carry device information.
  • the device management server After receiving the initialization session information, the device management server queries whether the device information of the user terminal is saved according to the identifier of the user terminal, and if it has been saved, then passes the response message. The management command is sent to perform subsequent device management. If the device information of the user terminal is not saved, the device management server may acquire the device information by using a "Get" command.
  • the user terminal needs to delete the node "1" in the server management subtree and all its child nodes.
  • the device management session service needs to be established between the user terminal and the device management server, and the IMEI of the user terminal is 493005100592800, and the device management server preset in the DM Account management object in the management object tree is: DM Server , the address of the device management server is: hup: / /www. syncml. org/dm- server.
  • the user terminal initiates a device management session to the device management server, and the device management session is the first device management session of the user terminal and the device management server. Therefore, the user terminal needs to report the device information to the server, and after reporting the device information, the user The terminal identifies the node value of the identifier sub-node of the DM Account management object corresponding to the device management server as the device information.
  • the server management sub-tree of the user terminal is as shown in FIG. 15 , where the FlagRev node (ie, the identifier) The node value of the child node is set to "1", indicating that the device information has been reported to the device management server.
  • the user terminal When the user terminal and the device management server initiate a new device management session, the user terminal first queries the node value of the FlagRev node in the DM Account management object, and queries the node value of the FlagRev node to be 1 (that is, The device information is reported to the device management server, and the device information is no longer carried in the initial session information sent to the device management server.
  • the server After receiving the initial session information, the server queries whether the device information of the user terminal is saved according to the identifier of the user terminal. If the server saves the information, the server sends a management command to the subsequent device management. If the user is not saved. Device information of the terminal, then the server can obtain device information through the "Get" command.
  • the user terminal needs to set the value of the FlagRev node in all DM Account management objects to "0", and when the user terminal initiates the next device management session, the value of the FlagRev node is queried. When 0", the device information needs to be reported again.
  • a data synchronization session service needs to be established between the user terminal and the device management server.
  • the IMEI of the user terminal is 493005100592800, and two databases are saved on the user terminal: . /Contact s and . /Ca lendar , With address is
  • Ht tp / /www. syncml.
  • the data server of org/sync-server is synchronized.
  • the corresponding synchronization database in the data server is divided into 'J is: . /dev-contac t s and . /dev_Ca lendar.
  • the user terminal and the server are the first session, so the user terminal needs to report the device information to the data server.
  • the database address of the device information is: . /Devinfo/DevCap
  • the time of the last time is: 20080101T010101Z, after the device information is reported, the user terminal adds the child node to the created server management subtree to save the report information indicating that the device information has been reported to the data server, indicating that the device has indicated
  • the device information has passed on the data server.
  • the server management subtree in the user terminal is as shown in FIG. 16.
  • the user terminal When the user terminal synchronizes with the data server. /Ca lendar and . /dev-ca lendar, the user terminal first queries the server management subtree before reporting the device information, and queries the server management subtree to save the logo.
  • the data server reports the child node of the device information (that is, the device information has been reported to the data server), the device information does not need to be reported again in the initialization session information sent to the data server.
  • the server After receiving the initialization session information, the server queries whether the device information of the user terminal is saved according to the identifier of the user terminal. If it is saved, the subsequent data synchronization operation is performed through the response message. If the device information of the user terminal is not saved, then The data server can get device information through the "Get" command.
  • the user terminal needs to delete the node "1" in the server management subtree and all its child nodes, so as to report the updated device information when a new data synchronization session is initiated.
  • the present invention can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is a better implementation. the way.
  • the technical solution of the present invention may be embodied in the form of a software product in essence or in the form of a software product stored in a storage medium, including a plurality of instructions for making One terminal
  • the apparatus performs the methods described in various embodiments of the invention.

Landscapes

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

Abstract

L’invention concerne un procédé permettant de rapporter des informations de dispositif, un terminal utilisateur et un serveur associé. Ledit procédé consiste : à vérifier la mémorisation des informations d’identification de rapport, qui servent à déterminer que les informations de dispositif ont été rapportées à un serveur, lorsqu’un service de session est mis en place avec le serveur; à rapporter au serveur les informations de dispositif lorsque les informations d’identification de rapport n’ont pas été mémorisées; à mémoriser les informations d’identification de rapport qui servent à déterminer que les informations de dispositif ont été rapportées au serveur. Les modes de réalisation de la présente invention permettent de rapporter efficacement les informations de dispositif dans le contexte des services de session de gestion de dispositifs et des services de session de synchronisation de données, et permettent également d’économiser des ressources de transmission.
PCT/CN2009/074255 2008-10-15 2009-09-27 Procédé permettant de rapporter des informations de dispositif, terminal utilisateur et serveur associés WO2010043150A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200810224452.2 2008-10-15
CN 200810224452 CN101753604B (zh) 2008-10-15 2008-10-15 上报设备信息的方法、用户终端和服务器

Publications (1)

Publication Number Publication Date
WO2010043150A1 true WO2010043150A1 (fr) 2010-04-22

Family

ID=42106229

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/074255 WO2010043150A1 (fr) 2008-10-15 2009-09-27 Procédé permettant de rapporter des informations de dispositif, terminal utilisateur et serveur associés

Country Status (2)

Country Link
CN (1) CN101753604B (fr)
WO (1) WO2010043150A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111225019A (zh) * 2019-10-29 2020-06-02 中国银联股份有限公司 会话控制处理方法、装置、设备及介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1553630A (zh) * 2003-06-08 2004-12-08 华为技术有限公司 一种自动配置终端设备的方法
CN1838087A (zh) * 2005-03-21 2006-09-27 华为技术有限公司 故障告警上报管理方法
CN1867147A (zh) * 2005-09-16 2006-11-22 华为技术有限公司 一种自动设备探测系统及方法
US20070082657A1 (en) * 2005-10-07 2007-04-12 Samsung Electronic Co., Ltd. Method and system for notifying service information to wireless terminal
CN101146346A (zh) * 2006-09-13 2008-03-19 华为技术有限公司 设备能力信息上报方法及终端设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1553630A (zh) * 2003-06-08 2004-12-08 华为技术有限公司 一种自动配置终端设备的方法
CN1838087A (zh) * 2005-03-21 2006-09-27 华为技术有限公司 故障告警上报管理方法
CN1867147A (zh) * 2005-09-16 2006-11-22 华为技术有限公司 一种自动设备探测系统及方法
US20070082657A1 (en) * 2005-10-07 2007-04-12 Samsung Electronic Co., Ltd. Method and system for notifying service information to wireless terminal
CN101146346A (zh) * 2006-09-13 2008-03-19 华为技术有限公司 设备能力信息上报方法及终端设备

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111225019A (zh) * 2019-10-29 2020-06-02 中国银联股份有限公司 会话控制处理方法、装置、设备及介质

Also Published As

Publication number Publication date
CN101753604A (zh) 2010-06-23
CN101753604B (zh) 2013-03-20

Similar Documents

Publication Publication Date Title
KR100822361B1 (ko) 장치 관리 시스템에서 관리노드들의 지정
EP2432154B1 (fr) Procédé, terminal, appareil et système pour la gestion de dispositifs
US9009278B2 (en) Device management server, device management client, and method for locating a target operation object
KR100896942B1 (ko) 이동 장치들 및 서비스들을 다루기 위한 통합된 방법 및장치
WO2009062410A1 (fr) Procédé et dispositif pour instancier un objet de gestion d'une arborescence de gestion dans un dispositif terminal
WO2007025428A1 (fr) Procede, systeme et dispositif terminal de configuration de parametres de composants logiciels
US20100287253A1 (en) Method, apparatus, and system for data synchronization
WO2011137793A1 (fr) Procédé, appareil et système de réseau pour effectuer une mise à jour à distance de dispositifs zigbee
WO2007112673A1 (fr) Procédé de négociation d'information de capacité de dispositif, procédé, système et dispositif de synchronisation
WO2010028571A1 (fr) Procédé d’émission de gros objets de données, système d’émission, dispositif émetteur et dispositif récepteur
WO2018059150A1 (fr) Procédé et appareil de mise en œuvre de capacité ouverte
FI116703B (fi) Solmujen määrittäminen laitteenhallintajärjestelmässä
WO2010111959A1 (fr) Procédé de fourniture d'information de noeud, procédé d'obtention d'information de noeud, et équipement à cet effet
WO2008019559A1 (fr) Procédé, système, extrémité client et serveur permettant de localiser un noeud d'opération dans un système de communication
WO2010118702A1 (fr) Terminal pour la gestion de dispositifs et procede pour le lancement de session de gestion correspondant
WO2010012157A1 (fr) Procédé de rapport et de mise à jour d’une information de structure de profil d’un équipement, équipement et système associés
WO2010124571A1 (fr) Procédé, client et serveur d'acquisition d'informations de noeud
WO2009049542A1 (fr) Un procédé, un système et un appareil corrélatif pour transmettre une commande de demande de procédure distante
WO2010043150A1 (fr) Procédé permettant de rapporter des informations de dispositif, terminal utilisateur et serveur associés
WO2012075965A1 (fr) Procédé, appareil et système de gestion de dispositifs
CN107800564A (zh) 一种网络设备管理方法、系统和计算机可读取介质
WO2013017020A1 (fr) Procédé et système pour exploiter un nœud exécutable
WO2007022723A1 (fr) Procede de mise a jour d'un logiciel/de configuration de parametre destine a un terminal mobile
WO2013082817A1 (fr) Procédé et dispositif d'identification d'un terminal mobile
JP5095831B6 (ja) 機器管理の方法、端末、装置およびシステム

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: 09820226

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: 09820226

Country of ref document: EP

Kind code of ref document: A1