SEAMLESS APPLICATION CONNECTIVITY

• US 20150085823A1
• Filed: 09/25/2013
• Published: 03/26/2015
• Est. Priority Date: 09/25/2013
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Jain, Arvind
• Granted Patent: US 9,241,292 B2
• Time in Patent Office: Days
• US Class Current: 370/331
• CPC Class Codes: H03C 1/16 by means of discharge device having at least three electrodes H03C1/28 - H03C1/34, H03C1/50, H03C1/52, H03C1/62 take precedence
• CPC Class Codes: H04L 69/321 Interlayer communication protocols or service data unit [SDU] definitions; Interfaces between layers
• CPC Class Codes: H04W 36/00692 using simultaneous multiple data streams, e.g. cooperative multipoint [CoMP], carrier aggregation [CA] or multiple input multiple output [MIMO] allocation of physical resources in CoMP or in CA H04L5/0035
• CPC Class Codes: H04W 36/18 for allowing seamless reselection, e.g. soft reselection
• CPC Class Codes: H04W 36/185 using make before break

Abstract

In some implementations, a request to switch to using a second network connection is received at a first computing device that is currently communicating with a second computing device over a first network connection. While still using the first network connection, the second network connection may be initiated. During a period of transition, the first computing device may communicate with the second computing device using both the first network connection and the second network connection. To use both the first and second network connections, data from the second computing device may be received over the first network connection, and data may be sent to the second computing device over the second network connection. The first computing device may identify an end of the period of transition. In response, the first computing device may communicate with the second computing device using only the second network connection.

Claims

1. A computer-implemented method comprising:

receiving, at a first computing device that is currently communicating with a second computing device over a first network connection, a request to switch to using a second network connection;

initiating, while still using the first network connection, the second network connection;

communicating, by the first computing device during a period of transition from the first network connection to the second network connection, with the second computing device using both the first network connection and the second network connection, wherein using both the first and second network connections comprises;

receiving data from the second computing device over the first network connection, and

sending data to the second computing device over the second network connection;

identifying, by the first computing device, an end of the period of transition; and

communicating, by the first computing device and in response to identifying the end of the period of transition, with the second computing device using only the second network connection.

2. The computer-implemented method of claim 1, wherein the communicating with the second computing device using both the first network connection and the second network connection is managed by a middleware layer that is running on the first computing device, the middleware layer acting as an intermediate network layer between an application layer and a kernel layer on the first computing device.

3. The computer-implemented method of claim 2, wherein the middleware layer comprises an application programming interface.

4. The computer-implemented method of claim 2, wherein the middleware layer maps the first network connection and the second network connection to a single connection alias that is used by the application layer to communicate with the second computing device.

5. The computer-implemented method of claim 1, wherein the identifying comprises receiving notice that the first network connection has closed.

6. The computer-implemented method of claim 5, wherein the notice is provided by a socket API of the first computing device.

7. The computer-implemented method of claim 1, wherein the identifying comprises receiving, over the first network connection, information that indicates that the first network connection has been terminated by the second computing device.

8. The computer-implemented method of claim 1, wherein the identifying comprises identifying expiration of a timer that is associated with the switch from the first network connection to the second network connection has expired.

9. The computer-implemented method of claim 1, further comprising:

providing a notification to the second computing device regarding the switch from the first network connection to the second network connection.

10. The computer-implemented method of claim 1, further comprising:

determining whether the communication between the first computing device and the second computing device is bounded;

identifying whether the second computing device is configured to use connection aliasing for the first and second network connections; and

determining, based on (i) the determination of whether the communication is bounded and (ii) whether the second computing device is configured to use connection aliasing for the first and second network connections, whether to proceed with switching between the first and second network connections using the first and second network connections simultaneously.

11. The computer-implemented method of claim 10, wherein:

proceeding with the switching is determined when the communication is determined to be bounded regardless of the configuration of the second computing device, and

the sending of the data to the second computing device over the second network connection is based on a reissued range request.

12. The computer-implemented method of claim 10, wherein proceeding with the switching is determined when the communication is determined to not be bounded and the second computing device is configured to seamlessly transition between the first and second network connections.

13. The computer-implemented method of claim 10, wherein communication over hypertext transfer protocol (HTTP) is determined to be bounded.

14. The computer-implemented method of claim 10, wherein streaming audio or video content is determined to not be bounded.

15. A computing device comprising:

one or more processors;

an interface that is programmed to receive a request to switch from using a first network connection to using a second network connection for communicating with another computing device;

a connectivity manager that is configured to;

initiate, while still using the first network connection, the second network connection;

communicate, during a period of transition from the first network connection to the second network connection, with the other computing device using both the first network connection and the second network connection, wherein using both the first and second network connections comprises;

receiving data from the other computing device over the first network connection, and

sending data to the other computing device over the second network connection;

identify an end of the period of transition; and

communicate, in response to identifying the end of the period of transition, with the other computing device using only the second network connection.

16. The computing device of claim 15, wherein the communicating with the other computing device using both the first network connection and the second network connection is managed by a middleware layer that is running on the computing device, the middleware layer acting as an intermediate network layer between an application layer and a kernel layer on the computing device.

17. The computing device of claim 16, wherein the middleware layer comprises an application programming interface.

18. The computing device of claim 16, wherein the middleware layer maps the first network connection and the second network connection to a single connection alias that is used by the application layer to communicate with the other computing device.

19. The computing device of claim 15, wherein the end of the period of transition is identified by receiving notice that the first network connection has closed.

20. A computer program product embodied on a computer storage device storing instructions that, when executed, cause one or more computing devices to perform operations comprising:

receiving, at a first computing device that is currently communicating with a second computing device over a first network connection, a request to switch to using a second network connection;

initiating, while still using the first network connection, the second network connection;

communicating, by the first computing device during a period of transition from the first network connection to the second network connection, with the second computing device using both the first network connection and the second network connection, wherein using both the first and second network connections comprises;

receiving data from the second computing device over the first network connection, and

sending data to the second computing device over the second network connection;

identifying, by the first computing device, an end of the period of transition; and

communicating, by the first computing device and in response to identifying the end of the period of transition, with the second computing device using only the second network connection.