Methods and Systems for Device-Independent Portable Session Synchronization

• US 20090183242A1
• Filed: 01/15/2008
• Published: 07/16/2009
• Est. Priority Date: 01/15/2008
• Status: Active Grant

• Current Assignee: Sharp Kabushiki Kaisha (Hon Hai Precision Industry Co., Ltd.)
• Original Assignee: Sharp Kabushiki Kaisha (Hon Hai Precision Industry Co., Ltd.)
• Inventors: Barton, David C., Hanley, Mark Gregory, Rao, Vishnu-Kumar Shivaji
• Granted Patent: US 8,156,547 B2
• Time in Patent Office: Days
• US Class Current: 726/5
• 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/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding

Abstract

Aspects of the present invention relate to systems and methods for device-independent portable session synchronization between multiple devices connected to a server system.

Claims

1. A method for communicating between a first device and a second device, said method comprising:

a) establishing a first connection between a server system and a first device;

b) establishing a second connection between said server system and a second device;

c) establishing, on said server system, a database construct linking said first device and said second device;

d) receiving at said server system a first message from said first device;

e) receiving at said server system a first destination indicator associated with said first message; and

f) sending said first message to said second device using said database construct when said first destination indicator indicates said second device is an intended recipient of said first message, thereby synchronizing communication between said first device and said second device.

2. A method according to claim 1, wherein said first destination indicator further indicates a plurality of devices associated with a single user.

3. A method according to claim 2, wherein:

a) each of said plurality of devices is linked to said first device through said database construct; and

b) said first message is sent to each of said plurality of devices using said database construct.

4. A method according to claim 1, wherein said database construct persists when said first connection or said second connection is broken.

5. A method according to claim 1, wherein said establishing said first connection occurs in response to one of the group consisting of powering up of said first device, a single-button push on said first device, a multiple-button push on said first device and a menu selection on said first device.

6. A method according to claim 1, wherein said establishing said second connection occurs in response to one of the group consisting of powering up of said second device, a single-button push on said second device, a multiple-button push on said second device and a menu selection on said second device.

7. A method according to claim 1, wherein said establishing said first connection comprises:

a) receiving a first password from said first device at said server system, wherein said first password is associated with a first user;

b) authenticating said first user using said first password; and

c) sending a first discovery list to said first device when said authenticating said first user is successful.

8. A method according to claim 1, wherein said establishing said second connection comprises:

a) receiving a second password from said second device at said server system, wherein said second password is associated with a second user;

b) authenticating said second user using said second password; and

c) sending a second discovery list to said second device when said authenticating said second user is successful.

9. A method according to claim 1, wherein said establishing said database construct comprises:

a) receiving, at said server system, a first request from said first device;

b) entering said first request in said database construct, thereby producing a first entry in said database construct;

c) associating a first session identifier with said first entry;

d) associating a first entry identifier with said first entry;

e) receiving, at said server system, a first response from said second device, wherein said first response comprises a location identifier; and

f) entering said first response in said database construct.

10. A method according to claim 9, wherein said first response comprises a poll for a message.

11. A method according to claim 9, wherein said location identifier is a URL.

12. A method according to claim 9, wherein said first request comprises first-device credentials for said first device.

13. A method according to claim 9, wherein said first response comprises second-device credentials for said second device.

14. A method according to claim 9, wherein said first response and said first request are linked by said first entry identifier.

15. A system for communicating between a first device and a second device, said system comprising:

a) a first connection-request receiver for receiving a connection request from a first device;

b) a first authenticator for authenticating said first device;

c) a second connection-request receiver for receiving a connection request from a second device;

d) a second authenticator for authenticating said second device;

e) a database construct, wherein said first device and said second device are linked;

f) a message receiver for receiving a first message from said first device;

g) a destination-indicator receiver for receiving a first destination indicator associated with said first message, wherein said first destination indicator indicates said second device is an intended recipient for said first message, thereby synchronizing communication between said first device and said second device; and

h) a transmitter for sending said first message to said second device using said database construct.

16. A system according to claim 15, wherein said database construct persists when said first connection or said second connection is broken.

17. A system according to claim 15, said system further comprising:

a) a first updater for updating a first discovery list associated with said first device; and

b) a second updater for updating a second discovery list associated with said second device.

18. A system according to claim 15, said system further comprising:

a) a request receiver for receiving a first request from said first device;

b) a response receiver for receiving a first response from said second device, wherein said first response comprises a location identifier and said first response is associated with said first request;

c) a first recorder for entering said first request in said database construct, thereby producing a first entry;

d) a session associator for associating a first session identifier with said first entry;

e) an entry associator for associating a first entry identifier with said first entry;

f) a second recorder for entering said first response in said database construct, thereby producing a second entry;

g) a response transmitter for sending said first response to said first device; and

h) a location-identified receiver for receiving, at said location identifier, a second request from said first device.

19. A system according to claim 18, wherein said first response comprises a poll for a message.

20. A system according to claim 18, wherein said location identifier is a URL.