CONTINUING AN APPLICATION SESSION USING A DIFFERENT DEVICE FROM ONE THAT ORIGINALLY INITIATED THE APPLICATION SESSION WHILE PRESERVING SESSION WHILE PRESERVING SESSION STATE AND DATA

• US 20090063690A1
• Filed: 09/05/2007
• Published: 03/05/2009
• Est. Priority Date: 09/05/2007
• Status: Abandoned Application

• Current Assignee: Motorola, Inc. (Motorola Solutions, Inc.)
• Original Assignee: Motorola, Inc. (Motorola Solutions, Inc.)
• Inventors: VERTHEIN, WILLIAM G., BHATT, YOGESH
• Application Number:
  US11/850,598
• Publication Number:
  US 20090063690A1
• Time in Patent Office: Days
• US Class Current: 709/228
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms

Abstract

The present invention discloses a solution for migrating an application session from one device to another. In the solution, a migration event can be detected during an application session involving an application server and an original device. Client-side session information and server-side session information can be stored. The client-side session information can be conveyed to a transfer device, which establishes a communication connection with the application server. This session can occur after an arbitrary delay from an occurrence of the migration event. Transfer device settings can be changed in accordance with the client-side session information and application server settings can be changed in accordance with the stored server-side information. An application session involving the transfer device and the application server can be conducted, beginning in a state approximately equivalent to that which existed at the time of the migration event.

Claims

1. A method for migrating an application session comprising:

identifying an application session comprising an application server and an original device;

during the application session, detecting a migration event;

responsive to the migration event, storing client-side session information and server-side information pertaining to the application session;

conveying the client-side session information to a transfer device;

establishing a communication connection between the transfer device and the application server;

changing transfer device settings in accordance with the client-side session information;

adjusting application server parameters in accordance with the stored server-side information; and

conducting an application session involving the transfer device and the application server that begins in a state approximately equivalent to a state in which the identified application session involving the original device ended.

2. The method of claim 1, where a substantial delay period exists between the application session involving the original device ends and the application session involving the transfer device begins.

3. The method of claim 1, wherein the application session involving the original device and the application session involving the transfer device also involve at least one participant device used by an entity that communicates in real-time with an entity that is utilizing the original device and the transfer device, wherein the steps of claim 1 are performed in a manner transparent to the at least one participant device.

4. The method of claim 1, wherein the original device and the transfer device each execute a client-side application used for interacting during the application session, said method further comprising:

the client-side application of the transfer device loading client-side session information before the conducting step.

5. The method of claim 1, further comprising:

The application server time stamping application session information received after the migration event was detected, wherein the information from the time stamping is used to ensure the application session involving the transfer device begins in the state approximately equivalent to a state in which the identified application session involving the original device ended.

6. The method of claim 1, wherein the application session is at least one of a Web browsing session, an email session, and a voice communication session.

7. The method of claim 1, wherein the client-side session information is conveyed directly from the original device to the transfer device.

8. The method of claim 1, wherein the client-side session information is conveyed from the original device to the application server, and is conveyed form the application server to the transfer device.

9. The method of claim 1, further comprising:

detecting a user selection within an interface of the original device, which causes a migration request to be conveyed from the original device to the application server, wherein receipt of the migration request triggers the migration event.

10. The method of claim 1, further comprising:

detecting a user selection within an interface of the transfer device, which causes a migration request to be conveyed from the transfer device to the application server, wherein receipt of the migration request triggers the migration event.

11. The method of claim 1, wherein said steps of claim 1 are steps performed automatically by at least one machine in accordance with at least one computer program having a plurality of code sections that are executable by the at least one machine, said at least one computer program being stored in a machine readable medium.

12. A communication device comprising:

a client-side application for conducting an application session comprising an application server; and

a transceiver for connecting the communication device to a network, wherein the network communicatively links the communication device to the application server, wherein the client-side application is able to begin an application session with the server in a state in which an application session between an original device and the application server ended.

13. The communication device of claim 12, wherein the communication device is a mobile communication device, and wherein the transceiver is a wireless transceiver.

14. The communication device of claim 12, where a substantial delay period exists between the application session involving the original device ends and the application session involving the communication device begins.

15. The communication device of claim 12, wherein the original device is a personal computer, and wherein the communication device is a mobile telephone.

16. The communication device of claim 12, wherein the application session involving the original device and the application session involving the communication device also involve at least one participant device used by an entity that communicates in real-time with an entity that is utilizing the original device and the communication device, wherein a transfer between the original device and the communication device occurs without a substantial delay period and occurs in a manner transparent to the at least one participant device.

17. The communication device of claim 12, wherein the original device comprises an original client-side application configured to interact with the application server;

said communication device further comprising;

a transfer client-side application configured to interact with the application server, wherein the transfer client-side application is initiated in approximately a same start state as that of the original client-side application when the application session between the original device and the application server ended.

18. An application server configured to execute at least one application during an application session involving a remotely located original device, said application server comprising:

a migration engine configured to handle migration requests, wherein a migration request is a user initiated request to end the application session involving the original device and configured to after an arbitrary delay initiate a transfer session handled by the application server, said transfer session involving a transfer device, wherein the transfer session begins in a state at which the application session involving the original device ends.

19. The application server of claim 18, further comprising:

a data store accessible by the application server configured to store server-side session information related to the application session, wherein said stored server-side session information is used when initiating the transfer session, wherein at least a portion of the server-side session information is time stamped.

20. The application server of claim 18, further comprising:

a data store accessible by the application server configured to store client-side session information conveyed from the original device, wherein the client-side information is conveyed from the application server to the transfer device when the transfer session is initiated.