US 12,149,596 B2
QUIC and anycast proxy resiliency
Kyle Andrew Donald Mestery, Woodbury, MN (US); and Vincent E. Parla, North Hampton, NH (US)
Assigned to Cisco Technology, Inc., San Jose, CA (US)
Filed by Cisco Technology, Inc., San Jose, CA (US)
Filed on Dec. 15, 2023, as Appl. No. 18/542,094.
Application 18/542,094 is a continuation of application No. 17/719,829, filed on Apr. 13, 2022, granted, now 11,924,299.
Claims priority of provisional application 63/273,306, filed on Oct. 29, 2021.
Claims priority of provisional application 63/272,985, filed on Oct. 28, 2021.
Claims priority of provisional application 63/271,437, filed on Oct. 25, 2021.
Claims priority of provisional application 63/244,599, filed on Sep. 15, 2021.
Prior Publication US 2024/0129378 A1, Apr. 18, 2024
This patent is subject to a terminal disclaimer.
Int. Cl. H04L 67/561 (2022.01); H04L 9/40 (2022.01); H04L 12/46 (2006.01); H04L 45/00 (2022.01); H04L 45/42 (2022.01); H04L 61/103 (2022.01); H04L 61/4511 (2022.01); H04L 67/02 (2022.01); H04L 67/101 (2022.01); H04L 67/1012 (2022.01); H04L 67/141 (2022.01); H04L 67/562 (2022.01)
CPC H04L 67/561 (2022.05) [H04L 12/4633 (2013.01); H04L 12/4641 (2013.01); H04L 45/42 (2013.01); H04L 45/66 (2013.01); H04L 61/103 (2013.01); H04L 61/4511 (2022.05); H04L 63/0236 (2013.01); H04L 63/0281 (2013.01); H04L 63/029 (2013.01); H04L 63/0435 (2013.01); H04L 67/02 (2013.01); H04L 67/101 (2013.01); H04L 67/1012 (2013.01); H04L 67/141 (2013.01); H04L 67/562 (2022.05)] 20 Claims
OG exemplary drawing
 
1. A method comprising:
establishing, by an internet protocol security (IPSec) proxy service, a first IPSec connection with a client device;
establishing, by the IPSec proxy service, a second IPSec connection with a first application node, wherein data is streamed between the client device and the first application node via the first IPSec connection and the second IPSec connection;
storing, by the IPSec proxy service and in a data store, a mapping between first connection information associated with the client device and second connection information associated with an application executing on the first application node;
detecting an event indicating that the client device is to communicate with a second application node executing the application; and
establishing, by the IPSec proxy service and based at least in part on the mapping between the first connection information and the second connection information, a third IPSec connection with the second application node, wherein the data is streamed between the client device and the second application node via the first IPSec connection and the third IPSec connection.