Browser session mobility system for multi-platform applications

• US 20050066037A1
• Filed: 04/01/2003
• Published: 03/24/2005
• Est. Priority Date: 04/10/2002
• Status: Abandoned Application

• Current Assignee: NTT Docomo Incorporated (Nippon Telegraph and Telephone Corporation)
• Original Assignee: NTT Docomo Incorporated (Nippon Telegraph and Telephone Corporation)
• Inventors: Rosen, Dan, Song, Yu, Kurakake, Shoji, Katagiri, Masaji, Chu, Hao-hua, Islam, Nayeem
• Application Number:
  US10/404,849
• Publication Number:
  US 20050066037A1
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: G06F 16/95 Retrieval from the web
• CPC Class Codes: H04L 67/148 Migration or transfer of sessions

Abstract

A browser session mobility (BSM) system allows a user to save and restore the runtime state of active sessions of multi-platform network applications established with a browser. A platform specific runtime state of an active session with a browser that includes a current browser state and a current server state may be captured from a platform specific version of a multi-platform network application. The platform specific runtime state may be transformed to a platform independent runtime state and stored. The stored platform independent runtime state may be retrieved and transformed to another platform specific version of the multi-platform network application and instantiated as the same active session.

Claims

1. A method of transferring the runtime state of an active session established with a browser between platform specific versions of a multi-platform network application, the method comprising:

capturing a current browser side runtime state of a platform specific version of a multi-platform network application;

selectively transforming the browser side runtime state to a platform independent runtime state; and

storing the platform independent runtime state.

2. The method of claim 1, further comprising:

capturing a server side runtime state of the platform specific version of the multi-platform network application;

transforming the server side runtime state to a platform independent runtime state; and

storing the server side runtime state with the browser side runtime state.

3. The method of claim 1, further comprising restoring the browser side runtime state on a different platform specific version of the multi-platform network application with the platform independent runtime state.

4. The method of claim 1, wherein capturing the current browser side runtime state comprises capturing state data and session data representative of the runtime state of an active session.

5. The method of claim 1, wherein transforming the browser side runtime state comprises directing the mapping of the browser side runtime state that is platform specific to a browser side runtime state that is platform independent.

6. The method of claim 1, wherein transforming the browser side runtime state comprises selectively converting at least one of state data and session data that is platform specific to corresponding platform independent state data and session data.

7. A method of transferring the runtime state of an active session established with a browser between platform specific versions of a multi-platform network application, the method comprising:

generating a first platform specific snapshot representative of state data and session data of at least one of a browser state and a server state of a first platform specific version of a network application;

converting the first platform specific snapshot to a platform independent snapshot;

converting the platform independent snapshot to a second platform specific snapshot representative of the state data and session data; and

re-instantiating at least one of the browser state and the server state on a second platform specific version of the network application with the second platform specific snapshot.

8. The method of claim 7, wherein generating the first platform specific snapshot comprises capturing both the server state and the browser state each with a different platform specific snapshot.

9. The method of claim 7, wherein generating the first platform specific snapshot comprises capturing at least one of a document object model, a scripting object, a browser history, a browser cache and a cookie.

10. The method of claim 7, wherein converting the first platform specific snapshot comprises selectively mapping at least one of the state data and session data to unique platform independent names to create the platform independent snapshot.

11. The method of claim 7, wherein converting the first platform specific snapshot comprises transforming runtime state data of the first platform specific snapshot to runtime state data of the platform independent snapshot as a function of a mapping description file.

12. The method of claim 7, wherein converting the first platform specific snapshot comprises:

accessing a master mapping file to identify a mapping description file; and

selectively transforming the first platform specific snapshot with the identified mapping description file to create the platform independent snapshot.

13. The method of claim 7, wherein converting the first platform specific snapshot comprises modeling the structure of a platform specific presentation of the first platform specific version of the network application and the structure of a platform specific presentation of the second platform specific version of the network application with respective finite state machine models.

14. A method of transferring the runtime state of an active session established with a browser between platform specific versions of a multi-platform network application, the method comprising:

capturing a first platform specific runtime state of an active session from a first platform specific version of a network application, wherein the active session includes at least one of a current browser state and a current server state;

transforming the first platform specific runtime state to a platform independent runtime state;

storing the platform independent runtime state;

retrieving the stored platform independent runtime state;

transforming the platform independent runtime state to a second platform specific runtime state; and

instantiating the second platform specific runtime state as the active session of a second platform specific version of the network application.

15. The method of claim 14, wherein capturing the first platform specific runtime state comprises extracting a page and data of the active session of the first platform specific version of the network application from a browser presentation.

16. The method of claim 14, wherein transforming the first platform specific runtime state comprises mapping the transformation of at least a portion of a platform specific snapshot to create a corresponding platform independent snapshot.

17. The method of claim 14, wherein transforming the platform independent runtime state comprises mapping at least a portion of the platform independent runtime state to the corresponding second platform specific runtime state.

18. The method of claim 14, wherein capturing the first platform specific runtime state comprises identifying partially filled data fields in a page of a presentation to indicate the state a user occupied at the time of the capture.

19. The method of claim 14, wherein transforming the first platform specific runtime state to a platform independent runtime state comprises selectively mapping data in the first platform specific runtime state to a unique previously assigned platform independent name to the create the platform independent runtime state.

20. The method of claim 14, wherein instantiating the second platform specific runtime state comprises displaying the identified state within the active session of the second platform specific version of the network application.

21. A browser session mobility system for transferring an active session established with a browser between platform specific versions of a multi-platform network application, the browser session mobility system comprising:

a network application server;

a communication device in communication with the network application server, wherein the network application server is operable to serve a platform specific version of a network application to a browser of the communication device to form an active session; and

a repository server in communication with at least one of the communication device and the network application server,

wherein the runtime state of the active session is captured and transformed to a platform independent runtime state with at least one of the communication device, the network application server and the repository server.

22. The browser session mobility system of claim 21, wherein the repository server is operable to store the platform independent runtime state.

23. The browser session mobility system of claim 21, wherein the captured runtime state includes at least one of a current server side runtime state and a current browser side runtime state of the active session.

24. The browser session mobility system of claim 21, wherein the active session is captured in a platform specific snapshot.

25. The browser session mobility system of claim 21, wherein the runtime state of the platform specific version of the network application is transformed to create a platform independent snapshot.

26. The browser session mobility system of claim 21, further comprising a second communication device in communication with the network application server and the repository server, wherein the platform independent runtime state is retrievable from the repository server to re-instantiate the same active session between the network application server and the second communication device.

27. The browser session mobility system of claim 21, wherein the network application server includes a platform adaptor module that is operable to capture and reinstantiate a server side runtime state of the active session.

28. The browser session mobility system of claim 21, wherein the communication device includes a browser session mobility module that is operable to capture and reinstantiate a browser side runtime state of the active session.

29. The browser session mobility system of claim 28, wherein the browser session mobility module is a browser plug-in.