IP Library Granted Patent US 12,438,952
Granted Patent B2
US 12,438,952 · App. 18/525,524 · Granted Oct 7, 2025

Managing network packet flows based on device information

Inventors: Yiu Leung Lee (Philadelphia, PA); Charles Allen Helfinstine (Wynnewood, PA)
Assignee: Comcast Cable Communications, LLC
H04L67/303H04L12/66H04L45/033H04L61/5007H04L67/02H04L2101/622
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,438,952
App. No.
18/525,524
Granted
Oct 7, 2025
Kind
B2
Abstract

Methods and apparatus are disclosed that enable information about devices connected behind a gateway, such as a home gateway, to be made available to and used by other entities, such as servers and routers, on a communications network.

Claims (31)

1. A method, comprising:

receiving, by a gateway of a communications network, from a device configured to communicate with the gateway, one or more packets of a packet flow initiated by the device;

determining at least one of the one or more packets comprise a Transmission Control Protocol synchronization (TCP/SYN) packet;

appending, based on the determining and to the one or more of the packets of the packet flow, at least a portion of information associated with the device, wherein the information associated with the device is maintained by the gateway and comprises at least an identifier associated with the device; and

sending, by the gateway, to a network device of the communications network, the one or more packets of the packet flow with the appended information, wherein the appended information facilitates enforcement of a per-device policy.

2. The method of claim 1 , wherein the information associated with the device further comprises one or more of a media access control (MAC) address of the device, a hostname associated with the device, and an identifier associated with the packet flow received from the device.

3. The method of claim 1 , wherein the information associated with the device further comprises a Hypertext Transfer Protocol (HTTP) header of at least one of the packets of the packet flow.

4. The method of claim 1 , wherein the information associated with the device further comprises a source IP address associated with the packet flow.

5. The method of claim 1 , wherein the appending comprises inserting the at least a portion of the information in the TCP/SYN packet of the packet flow.

6. The method of claim 5 , wherein inserting the at least a portion of the information in the TCP/SYN packet comprises inserting the at least a portion of the information in a Network Service Header (NSH) of the TCP/SYN packet.

7. The method of claim 1 , wherein the per-device policy comprises a rate-limit policy, an application control policy, a web domain filter, or a combination thereof.

8. A method, comprising:

receiving, by a gateway of a communications network, from a device configured to communicate with the gateway, one or more packets of a packet flow initiated by the device;

determining a profile associated with the device comprises updated profile information, wherein the profile associated with the device is maintained by the gateway and comprises at least an identifier associated with the device;

appending, based on the determining and to one or more of the packets of the packet flow, at least a portion of information associated with the device; and

sending, by the gateway, to a network device of the communications network, the one or more packets of the packet flow with the appended information, wherein the appended information facilitates enforcement of a per-device policy.

9. The method of claim 8 , wherein the information associated with the device further comprises one or more of a media access control (MAC) address of the device, a hostname associated with the device, and an identifier associated with the packet flow received from the device.

10. The method of claim 8 , wherein the information associated with the device further comprises a Hypertext Transfer Protocol (HTTP) header of at least one of the packets of the packet flow.

11. The method of claim 8 , wherein the information associated with the device further comprises a source IP address associated with the packet flow.

12. The method of claim 8 , wherein the appending comprises inserting the at least a portion of the information in a Transmission Control Protocol synchronization (TCP/SYN) packet of the packet flow.

13. The method of claim 12 , wherein inserting the at least a portion of the information in the TCP/SYN packet comprises inserting the at least a portion of the information in a Network Service Header (NSH) of the TCP/SYN packet.

14. The method of claim 8 , wherein the per-device policy comprises a rate-limit policy, an application control policy, a web domain filter, or a combination thereof.

15. A method, comprising:

receiving, by a gateway of a communications network, from a device configured to communicate with the gateway, data indicative of an initiation of a communication session of the device;

embedding, to one or more data packets corresponding to the communication session, at least a portion of information associated with the device, wherein the information associated with the device is maintained by the gateway and comprises at least an identifier associated with the device; and

sending, by the gateway, to a network device of the communications network, the one or more data packets with the embedded information, wherein the embedded information facilitates enforcement of a per-device policy.

16. The method of claim 15 , wherein the information associated with the device further comprises one or more of a media access control (MAC) address of the device, a hostname associated with the device, and an identifier associated with the one or more data packets received from the device.

17. The method of claim 15 , wherein the information associated with the device further comprises a Hypertext Transfer Protocol (HTTP) header of at least one of the one or more data packets.

18. The method of claim 15 , wherein the information associated with the device further comprises a source IP address associated with the one or more data packets.

19. The method of claim 15 , wherein the embedding comprises inserting the at least a portion of the information in a Transmission Control Protocol synchronization (TCP/SYN) packet of the one or more data packets.

20. The method of claim 19 , wherein inserting the at least a portion of the information in the TCP/SYN packet comprises inserting the at least a portion of the information in a Network Service Header (NSH) of the TCP/SYN packet.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 12, 2024
From: LEE, YIU LEUNG; HELFINSTINE, CHARLES ALLEN
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 066116/0904 →
Continuity (4)
Continuation 17885142 · Aug 10, 2022
Continuation 16995066 · Aug 17, 2020
Continuation 16265562 · Feb 1, 2019
Related Publication 20240223405A1 · Jul 4, 2024
References Cited (32)
US 6771757B1 · Torkki · 2004 [cited by examiner]
US 6901378B1 · Linker et al. · 2005 [cited by applicant]
US 7240364B1 · Branscomb et al. · 2007 [cited by applicant]
US 7774464B2 · Vuori et al. · 2010 [cited by applicant]
US 8131837B1 · Nayfeh · 2012 [cited by applicant]
US 8997176B1 · Znidarsic et al. · 2015 [cited by applicant]
US 10088818B1 · Mathews · 2018 [cited by examiner]
US 10123232B2 · Mishra et al. · 2018 [cited by applicant]
US 10523546B1 · Kavanagh et al. · 2019 [cited by applicant]
US 10785058B2 · Lee · 2020 [cited by examiner]
US 11463281B2 · Lee · 2022 [cited by examiner]
US 11888653B2 · Lee · 2024 [cited by examiner]
US 20010024425A1 · Tsunoda et al. · 2001 [cited by applicant]
US 20040002896A1 · Alanen et al. · 2004 [cited by applicant]
US 20050202392A1 · Allen et al. · 2005 [cited by applicant]
US 20060239254A1 · Short et al. · 2006 [cited by applicant]
US 20080261191A1 · Woolf et al. · 2008 [cited by applicant]
US 20090281902A1 · McNamara · 2009 [cited by applicant]
US 20100138370A1 · Wu et al. · 2010 [cited by applicant]
US 20160352729A1 · Malik · 2016 [cited by applicant]
US 20170039584A1 · Slavin et al. · 2017 [cited by applicant]
US 20170270130A1 · Sadovsky · 2017 [cited by applicant]
US 20180220301A1 · Gallagher et al. · 2018 [cited by applicant]
US 20200010880A1 · Ku et al. · 2020 [cited by applicant]
US 20200097731A1 · Gupta et al. · 2020 [cited by applicant]
CA 3051705A1 · 2019 [cited by examiner]
CA 2991833C · 2020 [cited by examiner]
WO WO0135269A2 · 2001 [cited by examiner]
WO WO2004100492A1 · 2004 [cited by examiner]
WO 2019027580A1 · 2019 [cited by applicant]
US Patent Application filed Aug. 10, 2022, entitled “Managing Network Packet Flows Based on Device Information”, U.S. Appl. No. 17/885,142. [cited by applicant]
US Patent Application filed Aug. 17, 2020, entitled “Managing Network Packet Flows Based on Device Information”, U.S. Appl. No. 16/995,066. [cited by applicant]