IP Library Granted Patent US 12,425,499
Granted Patent B2
US 12,425,499 · App. 17/876,074 · Granted Sep 23, 2025

Load balancing and session persistence in packet networks

Inventor: Chia J. Liu (Marlton, NJ)
Assignee: Comcast Cable Communications, LLC
H04L69/22H04L45/74H04L67/1027H04L69/16H04L69/161H04L61/58H04L61/59H04L2101/00
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,425,499
App. No.
17/876,074
Granted
Sep 23, 2025
Kind
B2
Abstract

A node may generate a data packet comprising an Internet Protocol (IP) header and a destination options extension header (DOEH). The DOEH may comprise one or more data fields and an IP payload. The node may send the data packet to another node in a data network.

Claims (53)

1. A method comprising:

receiving, by a first computing device and from a second computing device, a first packet comprising an extension header, wherein the extension header comprises:

a client field comprising an address of a client device; and

a server field;

generating, by the first computing device and based on the extension header of the first packet, a modified extension header that comprises:

the client field comprising the address of the client device; and

a modified server field comprising an address of the first computing device; and

sending, by the first computing device and to the second computing device, and based on the first packet, a second packet that comprises a fixed header and the modified extension header, wherein the modified extension header is not part of the fixed header, the first packet and the second packet each comprise an Internet Protocol (IP) data packet, the fixed header is an IP header, and the extension header and the modified extension header each comprise a destination options extension header (DOEH).

2. The method of claim 1 , further comprising determining, by the first computing device, that the server field of the extension header is null.

3. The method of claim 1 , wherein the first packet is a Hyper Text Transfer Protocol (HTTP) packet, and the second packet is a Hyper Text Transfer Protocol Secure (HTTPS) packet.

4. The method of claim 1 , further comprising:

receiving, by the first computing device and from the second computing device, a third packet comprising the modified extension header; and

sending, by the first computing device and to the second computing device, and based on the third packet, a fourth packet, wherein the fourth packet comprises the modified extension header.

5. The method of claim 4 , further comprising determining, by the first computing device and based on the third packet comprising the modified extension header, that the third packet is associated with a same session as the first packet and the second packet.

6. The method of claim 1 , wherein the first computing device comprises a server and the second computing device comprises a load balancer.

7. The method of claim 1 , further comprising encrypting, by the first computing device, a portion of the modified extension header.

8. The method of claim 1 , further comprising generating, by the first computing device, the fixed header, wherein the fixed header comprises the address of the first computing device.

9. An apparatus comprising:

one or more processors; and

memory storing instructions that, when executed by the one or more processors, cause the apparatus to:

receive, from a computing device, a first packet comprising an extension header, wherein the extension header comprises:

a client field comprising an address of a client device; and

a server field;

generate, based on the extension header of the first packet, a modified extension header that comprises:

the client field comprising the address of the client device; and

a modified server field comprising an address of the apparatus; and

send, to the computing device and based on the first packet, a second packet that comprises a fixed header and the modified extension header, wherein the modified extension header is not part of the fixed header, the first packet and the second packet each comprise an Internet Protocol (IP) data packet, the fixed header is an IP header, and the extension header and the modified extension header each comprise a destination options extension header (DOEH).

10. The apparatus of claim 9 , the memory storing instructions that, when executed by the one or more processors, cause the apparatus to:

determine that the server field of the extension header is null.

11. The apparatus of claim 9 , wherein the first packet is a Hyper Text Transfer Protocol (HTTP) packet, and the second packet is a Hyper Text Transfer Protocol Secure (HTTPS) packet.

12. The apparatus of claim 9 , the memory storing instructions that, when executed by the one or more processors, cause the apparatus to:

receive, from the computing device, a third packet comprising the modified extension header; and

send, to the computing device and based on the third packet, a fourth packet, wherein the fourth packet comprises the modified extension header.

13. The apparatus of claim 9 , wherein the apparatus comprises a server and the computing device comprises a load balancer.

14. The apparatus of claim 9 , the memory storing instructions that, when executed by the one or more processors, cause the apparatus to:

encrypt a portion of the modified extension header.

15. A non-transitory computer-readable medium storing instructions that, when executed, cause:

receiving, by a first computing device and from a second computing device, a first packet comprising an extension header, wherein the extension header comprises:

a client field comprising an address of a client device; and

a server field;

generating, by the first computing device and based on the extension header of the first packet, a modified extension header that comprises:

the client field comprising the address of the client device; and

a modified server field comprising an address of the first computing device; and

sending, by the first computing device and to the second computing device, and based on the first packet, a second packet that comprises a fixed header and the modified extension header, wherein the modified extension header is not part of the fixed header, the first packet and the second packet each comprise an Internet Protocol (IP) data packet, the fixed header is an IP header, and the extension header and the modified extension header each comprise a destination options extension header (DOEH).

16. The non-transitory computer-readable medium of claim 15 , wherein the instructions, when executed, further cause:

determining, by the first computing device, that the server field of the extension header is null.

17. The non-transitory computer-readable medium of claim 15 , wherein the instructions, when executed, further cause:

receiving, by the first computing device and from the second computing device, a third packet comprising the modified extension header; and

sending, by the first computing device and to the second computing device, and based on the third packet, a fourth packet, wherein the fourth packet comprises the modified extension header.

18. The non-transitory computer-readable medium of claim 17 , wherein the instructions, when executed, further cause:

determining, by the first computing device and based on the third packet comprising the modified extension header, that the third packet is associated with a same session as the first packet and the second packet.

19. The non-transitory computer-readable medium of claim 15 , wherein the instructions, when executed, further cause:

encrypting, by the first computing device, a portion of the modified extension header.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 12, 2023
From: LIU, CHIA J
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 062356/0033 →
Continuity (5)
Continuation 16815643 · Mar 11, 2020
Continuation 15720727 · Sep 29, 2017
Continuation 14331993 · Jul 15, 2014
Continuation 13407167 · Feb 28, 2012
Related Publication 20220407948A1 · Dec 22, 2022
References Cited (36)
US 20010037358A1 · Clubb et al. · 2001 [cited by applicant]
US 20020032777A1 · Kawata et al. · 2002 [cited by applicant]
US 20030093560A1 · Ono et al. · 2003 [cited by applicant]
US 20030117988A1 · Asano et al. · 2003 [cited by applicant]
US 20030185236A1 · Asano et al. · 2003 [cited by applicant]
US 20050005006A1 · Chauffour et al. · 2005 [cited by applicant]
US 20050080890A1 · Yang et al. · 2005 [cited by applicant]
US 20050172133A1 · Brumme et al. · 2005 [cited by applicant]
US 20050190694A1 · Ben-Nun et al. · 2005 [cited by applicant]
US 20050232277A1 · See · 2005 [cited by examiner]
US 20050243820A1 · Chen · 2005 [cited by applicant]
US 20060013190A1 · Leroy et al. · 2006 [cited by applicant]
US 20060095969A1 · Portolani et al. · 2006 [cited by applicant]
US 20060233106A1 · Achlioptas et al. · 2006 [cited by applicant]
US 20070030824A1 · Ribaudo et al. · 2007 [cited by applicant]
US 20070094373A1 · Brendel · 2007 [cited by applicant]
US 20080159288A1 · Nagarajan · 2008 [cited by examiner]
US 20080181216A1 · Breau · 2008 [cited by examiner]
US 20100063988A1 · Khalid et al. · 2010 [cited by applicant]
US 20100128665A1 · Kahn · 2010 [cited by applicant]
US 20110286425A1 · Chen · 2011 [cited by applicant]
US 20120087330A1 · Zhu · 2012 [cited by examiner]
US 20130227165A1 · Liu · 2013 [cited by applicant]
Deering, Cisco, Hinden, Nokia—Internet Protocol, Version 6 (IPv6) Specification, RFC 2460, Dec. 1998. [cited by applicant]
Extended European Search Report—EP 13156970.9—Mailing date: May 31, 2013. [cited by applicant]
R. Moskowitz et al., “Host Identity Protocol”, The Boeing Company, Apr. 2008, 105 pages. [cited by applicant]
S. Krishnan et al., “Localized Routing for Proxy Mobile 1Pv6 draft-ietf-netext-pmip-Ir-03”, NIKSUN, Jun. 3, 2011, 26 pages. [cited by applicant]
European Office Action—EP 13156970.9—Mailing date: Jan. 10, 2017. [cited by applicant]
Extended European Search Report, EP Application 14182848.3, Sent Jan. 30, 2015. [cited by applicant]
Deering, Cisco, Hinden, Nokia, “Internet Protocol, Version 6 (IPv6) Specification”, Dec. 1998. [cited by applicant]
Response to European Search Report—EP 14182848.3—Dated Sep. 2, 2015. [cited by applicant]
Nov. 23, 2018—European Office Action—EP 14182848.3. [cited by applicant]
Dec. 18, 2018—Canadian Office Action—CA 2,807,793. [cited by applicant]
Dec. 19, 2019—Canadian Office Action—CA 2,807,793. [cited by applicant]
Oct. 21, 2020, Canadian Office Action, CA 2,807,793. [cited by applicant]
Feb. 14, 2022—Canadian Office Action—CA 3,110,193. [cited by applicant]