Remote-session-to-go method and apparatus

• US 9,374,426 B2
• Filed: 10/01/2014
• Issued: 06/21/2016
• Est. Priority Date: 04/15/2009
• Status: Active Grant

• Current Assignee: Dell Marketing Corporation (Dell Technologies Inc.)
• Original Assignee: Wyse Technology L.L.C. (Dell Technologies Inc.)
• Inventors: Pahlavan, Babak, Barreto, Daniel Ernesto, Schwebke, Curtis
• Primary Examiner(s): Kim, Jung
• Assistant Examiner(s): Ho, Thomas
• Application Number:
  US14/503,913
• Publication Number:
  US 20150019638A1
• Time in Patent Office: 629 Days
• Field of Search: 713/155
• US Class Current: 1/1
• CPC Class Codes: G06F 3/0481 based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
• CPC Class Codes: G06F 3/0484 for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
• CPC Class Codes: G06F 9/452 Remote windowing, e.g. X-Window System, desktop virtualisation protocols for virtual reality H04L67/131
• CPC Class Codes: G06Q 10/101 Collaborative creation, e.g. joint development of products or services
• CPC Class Codes: H04L 12/12 Arrangements for remote connection or disconnection of substations or of equipment thereof
• CPC Class Codes: H04L 43/0864 Round trip delays
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0853 using an additional device, e.g. smartcard, SIM or a different communication terminal cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234
• CPC Class Codes: H04L 63/0884 by delegation of authentication, e.g. a proxy authenticates an entity to be authenticated on behalf of this entity vis-à-vis an authentication entity
• CPC Class Codes: H04L 63/126 the source of the received data
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 67/148 Migration or transfer of sessions

Abstract

Examples of systems and methods are provided for communication and for facilitating establishing a remote session between a client device and a remote server. The system may facilitate establishing a trusted relationship between the client device and a host device. The system may be configured to receive login information from the host device for a first remote session established between the host device and the remote server. The system may facilitate continuing the first remote session previously established between the host device and the remote server as a continued remote session between the client device and the remote server.

Claims

1. A method for transferring a remote session comprising:

establishing a first remote session between a host device and a remote server, the host device being a first client device and an end point of the first remote session, the first remote session including the host device accessing at least one application running on the remote server;

saving a state of the first remote session;

establishing a trusted relationship between a second client device and the host device via a connection between the second client device and the host device;

receiving, at the second client device, login information from the host device for the first remote session;

continuing the first remote session, using the saved state, as a continued remote session between the second client device and the remote server at least by using the login information received from the host device; and

receiving display data at the second client device from the remote server and displaying a remote desktop.

2. The method of claim 1, further comprising sending from the second client device to the host device an indication that the second client device continued the first remote session with the remote server.

3. The method of claim 1, wherein establishing the trusted relationship comprises:

sensing presence of the host device near the second client device;

performing a message exchange to pair the second client device with the host device; and

performing an exchange of encryption information with the host device.

4. The method of claim 1, wherein establishing the trusted relationship comprises responding to a query message from the host device.

5. The method of claim 1, wherein the second client device is configured to communicate with the host device over a wireless connection.

6. The method of claim 3, wherein the code for sensing presence comprises code for estimating a received signal strength of a transmission received from the host device.

7. The method of claim 3, wherein sensing presence comprises:

calculating a round trip delay time for communication with the host device; and

determining the presence of the host device near the second client device based on whether the round trip delay time is below a threshold value.

8. The method of claim 1, wherein continuing the first remote session previously established between the host device and the remote server comprises continuing the remote session previously established between the host device and the remote server based on a state of the remote session stored on the remote server.

9. A system at a client device side for communication and for transferring a remote session between a host device and a remote server to the client device, the system comprising:

a processor; and

a memory communicatively coupled to the processor, the memory comprising instructions operable, when executed by the processor, to cause the processor to;

establish a first remote session between a host device and a remote server, the host device being a first client device and an end point of the first remote session, the first remote session including the host device accessing at least one application running on the remote server;

save a state of the first remote session;

establish a trusted relationship between a second client device and the host device via a connection between the second client device and the host device;

receive, at the second client device, login information from the host device for the first remote session;

use the login information received from the host device to continue the first remote session, using the saved state, as a continued remote session between the second client device and the remote server; and

receive display data from the remote server and display a remote desktop.

10. The system of claim 9, further comprising a remote session termination module of the second client device configured to send an indication to the host device that the second client device continued the first remote session with the remote server.

11. The system of claim 9, wherein establishing the trusted relationship comprises responding to a query message from the host device.

12. The system of claim 9, wherein the second client device is configured to communicate with the host device over a wireless connection.

13. The system of claim 9, wherein establishing the trusted relationship comprises:

sensing presence of the host device near the second client device by calculating a round trip delay time for communication with the host device and determining the presence of the host device near the second client device based on whether the round trip delay time is below a threshold value;

performing a message exchange to pair the second client device with the host device; and

performing an exchange of encryption information with the host device.

14. A non-transitory machine-readable medium encoded with instructions for execution at a client device side for communication and for transferring a remote session between a host device and a remote server to the client device, the instructions comprising code for:

establishing a first remote session between a host device and a remote server, the host device being a first client device and an end point of the first remote session, the first remote session including the host device accessing at least one application running on the remote server;

saving a state of the first remote session;

establishing a trusted relationship between a second client device and the host device via a connection between the second client device and the host device;

receiving, at the second client device, login information from the host device for the first remote session;

continuing the first remote session, using the saved state, as a continued remote session between the second client device and the remote server at least by using the login information received from the host device; and

receiving display data at the second client device from the remote server and displaying a remote desktop.

15. The machine-readable medium of claim 14, wherein the instructions for execution at a client device side for communication and for transferring a remote session between a host device and a remote server to the client device further comprise code for sending from the second client device to the host device an indication that the second client device continued the first remote session with the remote server.

16. The machine-readable medium of claim 14, wherein continuing the first remote session previously established between the host device and the remote server comprises continuing the remote session previously established between the host device and the remote server based on a state of the remote session stored on the remote server.