SyncML data sync system and data exchanging method for data exchange between clients

• US 20060200596A1
• Filed: 02/13/2006
• Published: 09/07/2006
• Est. Priority Date: 03/03/2005
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: So, Young-Jun
• Granted Patent: US 7,917,653 B2
• Time in Patent Office: Days
• US Class Current: 710/38
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

Disclosed is a SyncML data sync system and a data exchanging method thereof for data exchange between clients. A sync server receives data to be provided to another client and authentication of a target client to which the data is provided from a first client, and transmits a signal reporting that the data has been provided to the target client. A second client according to the authentication information of the target client transmits its own authentication information to the remote sync server if it receives the signal reporting that the data has been provided. The sync server receives the authentication information of the second client, authenticates whether the second client is the target client, and provides the data to the second client. Accordingly, the data can be exchanged between a certain client and another client.

Claims

1. A SyncML (Synchronization Markup Language) data synchronization (sync) system for data exchange between clients, comprising:

a first client having client data to be provided to another client and authentication information of a target client to which the client data is provided;

a second client corresponding to the authentication information of the target client; and

a sync server for providing the client data to the second client if a sync request is received from the first client by performing a sync with the first client, receiving the client data through the sync, transmitting a sync request signal to the second client using the target authentication information of the first client, receiving authentication information from the second client and authenticating the second client, requesting a data access password from a user of the second client and authenticating the user of the second client, and performing a sync with the second client.

2. The SyncML data sync system as claimed in claim 1, wherein the sync server comprises:

a sync request and push module for transmitting the sync request signal and a signal for reporting the providing of the client data to the second client if an input of the client data from the first client is completed;

a client registration module for storing information on the first client and the authentication information of the target client provided from the first client;

an authentication module for authenticating whether the second client is the target client according to the authentication information of the target client; and

a sync server control unit for transmitting the signal for reporting the providing of the client data to the second client by controlling the sync request and push module, performing the sync with the second client according to an authentication result of the second client provided from the authentication module, and transmitting the client data to the second client.

3. The SyncML data sync system as claimed in claim 1, wherein if a signal reporting that the data has been provided from the sync server, the second client transmits the authentication information of the second client in response to the received signal.

4. The SyncML data sync system as claimed in claim 1, the authentication information is one of a caller identification (ID) of the corresponding client and user information of the corresponding client.

5. The SyncML data sync system as claimed in claim 1, wherein the client data is one of PIM (Personal Information Management) data of the first client and contents data stored in the first client.

6. The SyncML data sync system as claimed in claim 1, wherein the sync server receives authentication information and appliance information of the second client from the second client through a SyncML protocol remote interface of an OMA (Open Mobile Alliance), and provides the client data to the second client through one of the SyncML protocol of the OMA and a remote interface according to the appliance information.

7. The SyncML data sync system as claimed in claim 6, wherein the appliance information is information on whether the second client can use the remote interface.

8. The SyncML data sync system as claimed in claim 6, wherein the remote interface is one of an HTTP protocol and a TPC/IP protocol.

9. The SyncML data sync system as claimed in claim 1, wherein the first client and the second client are mobile communication terminals which are connected to the sync server using one of a remote interface and a local interface.

10. A data exchanging method for data exchange between clients in a SyncML (Synchronization Markup Language) data synchronization (sync) system including a sync server and first and second clients connected to the sync server using one of a remote interface and a local interface, the method comprising:

an authentication information providing step of the sync server receiving client data to be provided to the second client and authentication information of the second client from the first client;

an authenticating step of the sync server informing the second client of the providing of the client data and authenticating the second client according to the authentication information and a data access password received from a second client; and

a client data providing step of the sync server providing the client data to the second client according to appliance information received from the second client if the second client is a target client.

11. The data exchanging method as claimed in claim 10, wherein the authentication information is one of a caller identification (ID) of the second client and user information of the target client.

12. The data exchanging method as claimed in claim 10, wherein the authenticating step comprises:

receiving a signal by the second client for reporting the providing of the client data from the sync server;

transmitting the authentication information of the second client and the appliance information of the second client in response to the signal for reporting the providing of the client data;

first authenticating of the second client according to the received authentication information by the sync server;

requesting, by the sync server, the data access password input by a user of the first client to the second client if the second client is the authenticated client as a result of the first authentication;

receiving the data access password from a user of the second client in response to the password request and transmitting the received data access password to the sync server;

checking by the sync server by second authenticating whether the user of the second client is the user authenticated by the user of the first client according to the received data access password; and

performing the sync by the sync server with the second client if the user of the second client is the authenticated user as a result of the second authentication.

13. The data exchanging method as claimed in claim 12, wherein at the first authenticating step, the second client transmits the authentication information, the appliance information and the data access password to the sync server through one of a SyncML protocol of an OMA (Open Mobile Alliance) and a remote interface.

14. The data exchanging method as claimed in claim 13, wherein the appliance information is information on whether the second client can use the remote interface.

15. The data exchanging method as claimed in claim 14, wherein at the client data providing step, if the second client can use the remote interface, the client data is provided through the remote interface, while if the second client cannot use the remote interface, the client data is provided through a SyncML protocol of an OMA, according to the appliance information of the second client.