Systems and methods for quick user datagram protocol internet connection (QUIC) with multipath

Patent metadata

Field	Value
Publication number	US-10791485-B2
Application number	US-201816161951-A
Country	US
Kind code	B2
Filing date	Oct 16, 2018
Priority date	Oct 16, 2018
Publication date	Sep 29, 2020
Grant date	Sep 29, 2020

Abstract

A disclosed method is performed at a server (e.g., a content delivery network (CDN) server). The server receives from a QUIC client a first token, where the first token includes a first connection identifier that identifies a first path connecting the QUIC client to the server. The server validates the first token, including validating path properties associated with the first path extracted from the first token. The server further generates a second token associated with a second connection identifier that identifies a second path connecting the QUIC client to the server in accordance with a successful validation of the first token. Additionally, the server transmits the second token to the QUIC client.

First claim

The invention claimed is:

1. A method comprising:
at a server including one or more processors and a non-transitory memory:
receiving from a Quick User Datagram Protocol (UDP) Internet Connection (QUIC) client a first token and an address of the QUIC client, wherein the first token includes a first connection identifier that identifies a first path connecting the QUIC client to the server;
validating the first token, including validating path properties associated with the first path extracted from the first token;
generating a second token associated with a second connection identifier that identifies a second path connecting the QUIC client to the server in accordance with a successful validation of the first token; and
transmitting the second token to the QUIC client.

2. The method of claim 1 , further comprising issuing the first token during an initial setup of the first path between the server and the QUIC client via a first service provider.

3. The method of claim 1 , wherein:
the first path connects the QUIC client to the server via a first service provider with a first coverage area;
the second path connects the QUIC client to the server via a second service provider with a second coverage area; and
the address of the QUIC client is acquired from the second service provider in response to the QUIC client moving into the second coverage area and moving away from the first coverage area.

4. The method of claim 1 , wherein the address is included in an ADD_ADDRESS message received from the QUIC client over the first path.

5. The method of claim 1 , wherein:
receiving from the QUIC client the first token includes receiving the first token included in a PATH_MODIFICATION_REQUEST message over the first path;
transmitting the second token to the QUIC client includes transmitting the second token included in a PATH_MODIFICATION_RESPONSE message over the first path; and
the method further includes receiving a PATH_RESUME_INDICATION message encapsulating the second token over the second path.

6. The method of claim 1 , wherein receiving from the QUIC client the first token includes receiving the first token included in a PATH_RESUME_INDICATION message over the second path, and transmitting the second token to the QUIC client includes transmitting the second token over the second path.

7. The method of claim 1 , further comprising:
mapping the first connection identifier to the path properties associated with the first path and streaming properties of content delivered to the QUIC client over the first path;
storing an entry identifying mapping of the first connection identifier to the path properties associated with the first path and the streaming properties; and
mapping the second connection identifier to path properties associated with the second path and the streaming properties.

8. The method of claim 7 , wherein the first connection identifier is the same as the second connection identifier, and the method further includes:
updating the entry with mapping of the second connection identifier to the path properties associated with the second path.

9. The method of claim 7 , wherein the second connection identifier is different from the first connection identifier, and the method further includes:
adding a sub-entry to the entry with mapping of the second connection identifier to the path properties associated with the second path.

10. The method of claim 7 , further comprising:
delivering the content over the first path to the QUIC client;
obtaining the streaming properties of the content; and
resuming delivery of the content over the second path in accordance with the streaming properties and using the second token.

11. The method of claim 1 , further comprising continuing processing a first set of packets received from the QUIC client over the first path for a threshold duration and ceasing processing a second set of packets received from the QUIC client over the first path after the threshold duration.

12. A device comprising:
one or more processors;
a non-transitory memory coupled to the one or more processors; and
one or more programs stored in the non-transitory memory, which, when executed by the one or more processors, cause the device to:
receive from a Quick User Datagram Protocol (UDP) Internet Connection (QUIC) client a first token and an address of the QUIC client, wherein the first token includes a first connection identifier that identifies a first path connecting the QUIC client to the device;
validate the first token, including validating path properties associated with the first path extracted from the first token;
generate a second token associated with a second connection identifier that identifies a second path connecting the QUIC client to the device in accordance with a successful validation of the first token; and
transmit the second token to the QUIC client.

13. The device of claim 12 , wherein:
the first path connects the QUIC client to the device via a first service provider with a first coverage area;
the second path connects the QUIC client to the device via a second service provider with a second coverage area; and
the address of the QUIC client is acquired from the second service provider in response to the QUIC client moving into the second coverage area and moving away from the first coverage area.

14. The device of claim 12 , wherein the address is included in an ADD_ADDRESS message received from the QUIC client over the first path.

15. The device of claim 12 , wherein:
receiving from the QUIC client the first token includes receiving the first token included in a PATH_MODIFICATION_REQUEST message over the first path;
transmitting the second token to the QUIC client includes transmitting the second token included in a PATH_MODIFICATION_RESPONSE message over the first path; and
the one or more programs further cause the device to receive a PATH_RESUME_INDICATION message encapsulating the second token over the second path.

16. The device of claim 12 , wherein receiving from the QUIC client the first token includes receiving the first token included in a PATH_RESUME_INDICATION message over the second path, and transmitting the second token to the QUIC client includes transmitting the second token over the second path.

17. The device of claim 12 , the one or more programs further cause the device to:
map the first connection identifier to the path properties associated with the first path and streaming properties of content delivered to the QUIC client over the first path;
store an entry identifying mapping of the first connection identifier to the path properties associated with the first path and the streaming properties; and
map the second connection identifier to path properties associated with the second path and the streaming properties.

18. The device of claim 17 , wherein the first connection identifier is the same as the second connection identifier, and the one or more programs further cause the device to:
update the entry with mapping of the second connection identifier to the path properties associated with the second path.

19. The device of claim 17 , wherein the second connection identifier is different from the first connection identifier, and the one or more programs further cause the device to:
add a sub-entry to the entry with mapping of the second connection identifier to the path properties associated with the second path.

20. The device of claim 17 , the one or more programs further cause the device to:
d

Assignees

• Cisco Tech Inc

Inventors

• Patil Prashanth
• Ravindranath Ram Mohan

Classifications

• H04W36/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 title

• H04W12/043

  using a trusted network node as an anchor · CPC title

• H04W12/03

  Protecting confidentiality, e.g. by encryption · CPC title

• H04W12/041

  Key generation or derivation · CPC title

• H04L45/24

  Multipath · CPC title