Apparatus and method for synchronizing presence attribute data between terminal and server

• US 8,037,207 B2
• Filed: 03/29/2004
• Issued: 10/11/2011
• Est. Priority Date: 10/17/2003
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: Seo, Ho-Sub, Park, Jee-Hoon
• Primary Examiner(s): Avellino; Joseph
• Assistant Examiner(s): MCLEOD, MARSHALL M
• Application Number:
  US10/811,546
• Publication Number:
  US 20050086376A1
• Time in Patent Office: 2,752 Days
• Field of Search: 709/248, 709/227, 709/228
• US Class Current: 709/248
• CPC Class Codes: H04L 67/54 Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

An apparatus and method for synchronizing data between a terminal and a server. The apparatus synchronizes presence attribute data when the terminal and the server are connected to each other to establish a messenger service between them. The client terminal requests presence attribute data to be updated from a server when it is reconnected to the server having been previously connected to the client terminal to perform the messenger service, and updates presence attribute data stored at a time of a previous connection upon receiving the presence attribute data to be updated from the server. The server receives a presence attribute data request to be updated from the client terminal, and transmits only updated presence attribute data, created after releasing the previous connection, from among current presence attribute data to the client terminal.

Claims

1. A method for updating a presence attribute data in a client terminal, having a messenger service, comprising the steps of:

reading a session IDentification (ID), which is an ID of a previous session between the client terminal and a server;

reading a client ID for identifying the client terminal;

reading a transaction ID, which designates between the client terminal and the server before a termination of a previous connection;

generating a synchronization key having the session ID, the client ID, and the transaction ID, the synchronization key for requesting, from the server after the termination of the previous connection between the client terminal and the server, only presence attribute data updated after the termination of the previous connection; and

transmitting the generated synchronization key to the server.

2. The method as claimed in claim 1, wherein the transaction ID is generated according to a last response of the server for a request of a client terminal.

3. The method as claimed in claim 1, wherein the presence attribute data includes at least one of a list of friends, statuses of the friends, addresses of the friends and contact information of the friends, and

wherein the presence attribute data is stored in the client terminal for a messenger service.

4. The method as claimed in claim 1, further comprising whenever a session between the server and the client terminal is established, updating the presence attribute data, the session ID, the client ID, and the transaction ID.

18. The method as claimed in claim 1, further comprising step of receiving the attribute data updated after a previous connection between the client terminal and the server if the transmitted synchronization key is the same as a previous synchronization key stored in the server.

19. The method as claimed in claim 1, wherein, in receiving the updated presence attribute data from the server, the client terminal does not receive presence attribute data that has not been updated after the previous connection between the client terminal and the server.

5. A method for sending a presence attribute data for providing a messenger service in a server, comprising the steps of:

receiving a presence synchronization request from a client terminal, the presence synchronization request having a previous session IDentification (ID), a client ID, and a transaction ID;

identifying the received presence synchronization request;

identifying whether the client terminal was previously connected to the server to perform the messenger service according to the received presence synchronization request;

if the client terminal is a previous client terminal used for a previous connection, checking presence attribute data updated after a termination of the previous connection between the client terminal and the server, wherein the updated presence attribute data is requested from the client terminal using the previous session ID according to the client ID and the transaction ID; and

transmitting the updated presence attribute data updated after the termination of the previous connection to the client terminal, wherein the transmitted updated presence attribute data does not include presence attribute data updated before the termination of the previous connection.

6. The method as claimed in claim 5, further comprising identifying the client ID from the received presence synchronization request, wherein the client ID is a unique ID of the client terminal.

7. The method as claimed in claim 5, further comprising identifying the transaction ID from the received presence synchronization request, wherein the transaction ID is designated between the client terminal and the server before a termination of the previous connection.

8. The method as claimed in claim 5, wherein transmitting the updated presence attribute data to the client terminal includes:

identifying the previous session ID, the client ID, and the transaction ID from the received presence attribute data request; and

transmitting the updated presence attribute data to the client terminal corresponding to the identified previous session ID, the identified client ID and the identified transaction ID, using the session ID, the client ID, and the transaction ID, wherein the updated presence attribute data is transmitted to the client terminal after a termination of the previous connection.

20. The method as claimed in claim 5, wherein the previous session ID is an ID of a previous session between the client terminal and the server.

21. The method as claimed in claim 5, wherein the transaction ID is an ID which designates the server'"'"'s response to the client terminal'"'"'s request, or the client terminal'"'"'s response to the server'"'"'s request between the client terminal and the server before a termination of a previous connection.

9. A client terminal for updating presence attribute data for a messenger service, the client terminal comprising:

a processor for reading a previous session IDentification (ID) between the client terminal and a server before a reconnection to the server, reading a client ID, which is a particular ID of the client terminal, reading a transaction ID which designates between the client terminal and the server before a termination of a previous connection, and generating a synchronization key by using session ID, the client ID and the transaction ID, the synchronization key for requesting, from the server, only presence attribute data updated after a termination of the previous connection between the client terminal and the server; and

a transmitter for transmitting the generated synchronization key to the server.

10. The client terminal as claimed in claim 9, wherein the transaction ID is generated according to a last response, of the server, to a request of a client terminal.

11. The client terminal as claimed in claim 9, further comprising a memory for storing presence attribute data having a list of friends, statuses of the friends, addresses of the friends, and contact information of the friends for operating a messenger service.

12. The client terminal as claimed in claim 11, wherein the memory stores the previous session ID, the client ID, and the transaction ID.

13. The client terminal as claimed in claim 9, wherein whenever a session between the server and the client terminal is established, the processor updates the presence attribute data, the session ID, the client ID, and the transaction ID.

22. The client terminal as claimed in claim 9, wherein the transmitter receives, from the server, presence attribute data updated after a previous connection between the client terminal and the server, if the transmitted synchronization key is the same as a previous synchronization key stored in the server.

23. The client terminal as claimed in claim 9, wherein, in receiving the updated presence attribute data from the server, the client terminal does not receive presence attribute data that has not been updated after the previous connection between the client terminal and the server.

14. A server for transmitting presence attribute data for messenger service to a client terminal, the server comprising:

a receiver for receiving a presence synchronization request from a client terminal, the presence synchronization request having a previous session IDentification (ID), a client ID, and a transaction ID;

a processor for identifying the received presence synchronization request, identifying whether the client terminal was previously connected to the server to perform the messenger service based on the received presence synchronization request, and, if the client terminal is a previous client terminal used for a previous connection, checking presence attribute data updated after a termination of the previous connection between the client terminal and the server, wherein the updated presence attribute data is requested from the client terminal using the previous connection according to the session ID, the client ID, and the transaction ID; and

a transmitter for transmitting the updated presence attribute data to the client terminal, wherein the transmitted updated presence attribute data does not include presence attribute data updated before the termination of the previous connection.

15. The server as claimed in claim 14, wherein the server identifies the client ID from the received presence synchronization request, the client ID being a unique ID of the client terminal.

16. The server as claimed in claim 14, wherein the server identifies the transaction ID from the received presence synchronization request, the transaction ID being designated between the client terminal and the server before a termination of the previous connection.

17. The server as claimed in claim 14, wherein the processor identifies the previous session ID, the client ID, and the transaction ID from the received presence synchronization request, and

wherein the transmitter transmits the updated presence attribute data to the client terminal corresponding to the identified previous session ID, the identified client ID, and the identified transaction ID, the updated presence attribute data being transmitted to the client terminal after a termination of the previous connection.

24. The server as claimed in claim 14, wherein the previous session ID is an ID of a previous session between the client terminal and the server.

25. The server as claimed in claim 14, wherein the transaction ID is an ID which designates the server'"'"'s response to the client terminal'"'"'s request, or the client terminal'"'"'s response to the server'"'"'s request between the client terminal and the server before a termination of a previous connection.