System for automated device-to-device transfer

• US 8,650,307 B2
• Filed: 10/15/2009
• Issued: 02/11/2014
• Est. Priority Date: 09/17/2001
• Status: Expired due to Fees

• Current Assignee: CRFD Research, Inc. (Marathon Patent Group, Inc.)
• Original Assignee: CRFD Research, Inc. (Marathon Patent Group, Inc.)
• Inventors: Miller, Michael J.
• Primary Examiner(s): Donabed, Ninos
• Application Number:
  US12/588,433
• Publication Number:
  US 20100042729A1
• Time in Patent Office: 1,580 Days
• Field of Search: 709/227, 713/182
• US Class Current: 709/227
• 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 command 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 may be configured to discontinue the session with the current device and 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 configured 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 of transferring a session from a first device to a second device, comprising:

in response to a second device log-on, transferring an on-going session from a first device;

obtaining a converting profile specifying a format for said second device;

converting a session history associated with said on-going session of said first device, to said format that is compatible with said second device;

communicating said session history to said second device after said second device log-on; and

transmitting data associated with said on-going session to said second device.

2. The method of transferring a session from a first device to a second device according to claim 1, further comprising:

pushing said session to said second device in response to said transferring said on-going session transfer.

3. The method of transferring a session from a first device to a second device according to claim 1, further comprising:

pushing a notification to said second device in response to said transferring said on-going session transfer.

4. A session server for transferring a session from a first device to a second device, comprising:

receiving, at a physical session server, an on-going session transfer request for initiating an on-going session transfer from a first device to a second device;

accessing, at said physical session server, a converting profile specifying a format for said second device;

converting, with said physical session server, a session history relating to said first device, to said format that is compatible with said second device; and

after a log-on of said second device, communicating said session history associated with said on-going session to said second device.

5. The session server for transferring a session according to claim 4, wherein:

said physical session server pushes said on-going session to said second device in response to initiation of said automatic session transfer.

6. The session server for transferring a session according to claim 4, wherein:

said physical session server pushes a notification to said second device in response to initiation of said automatic session transfer.