System for Automated Device-to-Device Transfer

• US 20160323389A1
• Filed: 07/07/2016
• Published: 11/03/2016
• Est. Priority Date: 09/17/2001
• Status: Abandoned Application

• Current Assignee: CRFD Research, Inc. (Marathon Patent Group, Inc.)
• Original Assignee: CRFD Research, Inc. (Marathon Patent Group, Inc.)
• Inventors: Miller, Michael J.
• Application Number:
  US15/204,926
• Publication Number:
  US 20160323389A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/148 Migration or transfer of sessions
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04W 88/16 Gateway arrangements

Abstract

A session transfer module of a session server provides the capability to a user to direct a transfer of an on-going session from one device to another device while maintaining the session. The session transfer module is invoked by a user in a way consistent with the user interface of the client application, including by a graphical user command, a command line prompt, or a voice command. The client provides a selection of possible devices that may receive the redirected session. The session transfer module receives the selected device with the session redirect common over a communication network. The communication network may be wired (e.g., public switched telephone network (“PSTN”), Internet, etc.,) a wireless network (e.g., digital telephone network, pager network, etc.,) or a combination of the wired and wireless networks. The session transfer module many be configured to discontinued the session with the current device to block any subsequent messages of the transferring session from reaching the device. The session transfer module may be further configured to access a device profile from a device profile database to convert the blocked messages into a format compatible to the format and/or modality of the redirected device. The session transfer module may be further configured to push the session to the redirected device in response to an activation (e.g., log-on) of the redirected device by the user. Alternatively, the session transfer module may be further grounded to push the session back to the device in response to a time-out in the activation of the redirected device.

Claims

1. A method for a user-directed transfer of an on-going session from a first device to a second device, comprising:

during a session between the first device and a session server, said session server configured to provide a session service between the first device and the session server over a network and further configured to discontinue said session with the first device and resume said session with the second device over said network in response to user command, a session transfer module of the session server suspending said session with the first device, wherein said session transfer module is invoked by a client software application allocated for the first device in a way consistent with a modality of a user interface of the first device;

pushing, by said session transfer module to said second device, an alert to the second device to notify a user that the session is available and that the user can access it by activating the session on the second device; and

responsive to activation of the session on the second device, said session server communicating said session to the second device in a data format compatible with the second device, wherein prior to communicating said session, said session transfer module accesses a transaction history of the session maintained by the session server.

2. The method of claim 1, wherein the session transfer module receives the transaction history from the first device prior to communicating said session to the second device.

3. The method of claim 1, wherein the session transfer module receives the transaction history from a session handler of the session server.

4. The method of claim 1, wherein the session transfer module stores the transaction history temporarily in a memory space allocated by the session transfer module in the session server.

5. The method of claim 1, wherein prior to communicating said session to the second device the session transfer module accesses a device profile of the second device and converts a current state of the session to a state compatible with the second device according the device profile.

6. The method of claim 5, wherein the device profile comprises user preference settings for the second device.

7. A method for a user-directed transfer of an on-going session from a first device to a second device, comprising:

during a session between the first device and a session server, said session server configured to provide a session service between the first device and the session server over a network and further configured to discontinue said session with the first device and resume said session with the second device over said network in response to user command, a session transfer module of the session server suspending said session with the first device, wherein said session transfer module is invoked by a client software application allocated for the first device in a way consistent with a modality of a user interface of the first device;

pushing, by said session transfer module to said second device, an alert to the second device to notify a user that the session is available and that the user can access it by activating the session on the second device, said session transfer module further setting an activation timer; and

responsive to activation of the session on the second device within a time period permitted by said activation timer, said session server communicating said session to the second device in a data format compatible with the second device, wherein prior to communicating said session said session transfer module accesses a transaction history of the session maintained by the session server, otherwise said session transfer module terminating said session.

8. The method of claim 7, wherein the session transfer module receives the transaction history from the first device prior to communicating said session to the second device.

9. The method of claim 7, wherein the session transfer module stores the transaction history temporarily in a memory space allocated by the session transfer module in the session server.

10. The method of claim 7, wherein prior to communicating said session to the second device the session transfer module accesses a device profile of the second device and converts a current state of the session to a state compatible with the second device according the device profile.

11. The method of claim 10, wherein the device profile comprises user preference settings for the second device.

12. The method of claim 7, wherein the session transfer module receives the transaction history from a session handler of the session server.