Method for device capability negotiation, method, system and device for synchronization

• US 8,051,186 B2
• Filed: 09/30/2008
• Issued: 11/01/2011
• Est. Priority Date: 03/30/2006
• Status: Active Grant

• Current Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Original Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Inventors: Guo, Xiangzhou, Tian, Linyi, Kang, Jiao
• Primary Examiner(s): Meky; Moustafa M
• Assistant Examiner(s): Williams; Clayton R
• Application Number:
  US12/241,937
• Publication Number:
  US 20090144434A1
• Time in Patent Office: 1,127 Days
• Field of Search: None
• US Class Current: 709/228
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 69/24 Negotiation of communication capabilities

Abstract

Method for device capability negotiation, and method, system and device for synchronization. The synchronization system includes a synchronization server and a synchronization client. The synchronization server or the synchronization client is adapted to skip the device capability negotiation and directly perform a synchronization with the synchronization server and the synchronization client when the negotiated device capability or status ID, or the status ID indicating that the device capability has not been changed and has been stored. The method for device capability negotiation includes receiving an operation request carrying a parameter requesting a device capability negotiation; determining that the session is a device capability negotiation session according to the parameter requesting the device capability negotiation, carried by the request; returning a response and performing the device capability negotiation; storing results of the device capability negotiation. Embodiments of the present invention can improve the synchronization efficiency.

Claims

1. A method for SyncML data synchronization comprising:

receiving, by a first device, a request for data synchronization from a second device;

determining, by the first device, if the first device has a first status ID, which corresponds to an ID of a synchronization client of the second device initiating the request, indicating completion of a previous device capability negotiation between the first and second devices, or, has a second status ID indicating that the device capability of the first device and the second device has not been changed since the previous device capability negotiation between the first and second devices;

skipping the device capability negotiation, if it is determined that the first device has the first status ID or the second status ID, and further performing a synchronization operation;

returning, by the first device, to the second device a response requesting performing a part of the device capability negotiation, if it is determined that the first device does not store both the first status ID and the second status ID;

where the performing a part of the device capability negotiation comprises;

negotiating a part of the device capability which has been changed since the previous device capability negotiation;

or

negotiating a part of the device capability which is specified for negotiation by a URI.

2. The method of claim 1, after returning to the second device a response requesting performing a part of the device capability negotiation, the method further comprises:

receiving an operation request, the operation request carries a parameter requesting a device capability negotiation;

determining that a session is a device capability negotiation session according to the parameter requesting a device capability negotiation, carried by the operation request;

returning a response and performing the device capability negotiation; and

storing results of the device capability negotiation and updating the status ID.

3. The method of claim 1, wherein the second status ID indicating that the device capability of the second device has not been changed is included in the request for data synchronization from a second device.

4. A method for device capability negotiation for SyncML data synchronization, comprising:

receiving an operation request through a device capability operation session, the operation request carries a parameter requesting a device capability negotiation;

determining that a session is a device capability negotiation session according to the parameter requesting the device capability negotiation, carried by the operation request;

wherein the parameter requesting the device capability negotiation is;

a data type indicative of negotiating all of the device capability, a data type carrying the information of negotiating the associated device capability, a URI specifying the device capability to be negotiated, or an expression specifying the device capability to be negotiated;

returning a response and performing the device capability negotiation according to the parameter; and

storing results of the device capability negotiation;

where the performing a device capability negotiation comprises;

negotiating a part of the device capability which has been changed since a previous device capability negotiation;

or

negotiating a part of the device capability which is specified for negotiation by a URI;

wherein the operation request includes add, update, delete or query commands, and when the parameter is the URI specifying the device capability to be negotiated, the manner used for a device capability negotiation comprises;

acquiring the device capability via operation commands of XCAP protocol according to the URI.

5. A method for device capability negotiation for SyncML data synchronization, comprising:

sending a request for device capability to a DM client;

initiating a device management procedure, sending an operation request carrying a parameter requesting a device capability negotiation to a DM server, and informing the DM server to acquire the device capability after the DM client receives the device capability;

receiving the operation request via a device management (DM) protocol, the operation request carries the parameter requesting the device capability negotiation;

determining that a session is a device capability negotiation session according to the parameter requesting a device capability negotiation, carried by the operation request;

returning a response and performing the device capability negotiation, wherein the performing a device capability negotiation comprises;

sending, by the DM server, the device capability to a synchronization server; and

storing results of the device capability negotiation;

where the performing a device capability negotiation comprises;

negotiating a part of the device capability which has been changed since a previous device capability negotiation;

or

negotiating a part of the device capability which is specified for negotiation by a URI;

wherein;

the initiating the device management procedure, sending the operation request and informing a DM server to acquire a client device capability comprise;

reading data to which a configured synchronization management object of a synchronization client corresponds and acquiring device capability of a synchronization client to be reported;

sending a request for initial session connection to the DM server and carrying the synchronization client device capability in the request for initial session connection;

or

initiating, by the client, a request for initial session connection to the DM server and carrying in the request for initial session connection a client synchronization management object identifier requiring the DM server to acquire;

issuing an operation command, by the DM server, according to the received client synchronization management object identifier;

reading data to which the configured client synchronization management object corresponds according to the operation command and acquiring the client device capability to be reported;

sending response information to the request for initial session connection to the DM server and carrying the client device capability in the response information.

6. A system for SyncML data synchronization, comprising:

a synchronization server having a processor, a memory coupled to the processor and a synchronization client,

wherein the synchronization server comprises a receiving unit adapted to receive a request for data synchronization from the synchronization client;

the synchronization server is adapted to determine if the synchronization server has a first status ID, which corresponds to an ID of the synchronization client initiating the request, indicating the completion of the previous device capability negotiation between the synchronization server and the synchronization client, or a second status ID indicating that the device capability of the synchronization server and the synchronization client has not been changed since the previous device capability negotiation between the synchronization server and the synchronization client;

skip the device capability negotiation, if it is determined that the synchronization server has the first status ID or the second status ID, and further perform a synchronization operation;

return to the synchronization client a response requesting performing a part of the device capability negotiation, if it is determined that the synchronization server does not store both the first status D and the second status ID;

where the performing a part of the device capability negotiation comprises;

negotiating a part of the device capability which has been changed since the previous device capability negotiation;

or

negotiating a part of the device capability which is specified for negotiation by a URI.

7. A server for SyncML data synchronization, comprising:

a processor and a memory coupled to the processor;

a request receiving unit adapted to receive in a session an operation request carrying a parameter requesting a device capability negotiation, wherein the receiving the operation request comprises receiving the operation request through a device capability operation session;

a session type determination unit adapted to determine that the session is a device capability negotiation session according to the parameter requesting the device capability negotiation, carried by the operation request;

wherein the parameter requesting the device capability negotiation is;

a data type indicative of negotiating all of the device capability, a data type carrying the information of negotiating the associated device capability, a URI specifying the device capability to be negotiated, or an expression specifying the device capability to be negotiated;

a negotiation unit adapted to perform the device capability negotiation according to the parameter after the session is determined to be a device capability negotiation session; and

a session control unit adapted to store the results of the device capability negotiation;

where the performing the device capability negotiation comprises;

negotiating a part of the device capability which has been changed since the previous device capability negotiation;

or

negotiating a part of the device capability which is specified for negotiation by a URI;

wherein the operation request includes add, update, delete or query commands, and when the parameter is the URI specifying the device capability to be negotiated, the manner used for a device capability negotiation comprises;

acquiring the device capability via operation commands of XCAP protocol according to the URI.

8. A method for SyncML data synchronization, comprising:

initiating, by a synchronization client, an operation request towards a synchronization server;

determining, by synchronization server, if the synchronization server has a first status ID, which corresponds to an ID of the synchronization client initiating the request, indicating the completion of the previous device capability negotiation between the synchronization server and the synchronization client, or a second status ID indicating that the device capability of the synchronization server and the synchronization client has not been changed since the previous device capability negotiation between the synchronization server and the synchronization client;

performing synchronization if the synchronization server determines that the received operation request is a request for data synchronization and the synchronization server has the first status ID, or the second status ID; and

performing a part of device capability negotiation if the synchronization server determines that the received operation request is a request for a device capability negotiation and that the synchronization server does not store both the first status ID and the second status ID;

returning, to the synchronization client, a response requesting a device capability negotiation if the synchronization server determines that the received operation request is a request for data synchronization and confirms that that the synchronization server does not store both the first status ID and the second status ID, and performing the part of the device capability negotiation according to the returned device capability from the client, and performing synchronization;

where the performing a part of the device capability negotiation comprises;

negotiating a part of the device capability which has been changed since the previous device capability negotiation;

or

negotiating a part of the device capability which is specified for negotiation by a URI.