IP Library Granted Patent US 11,706,124
Granted Patent B2
US 11,706,124 · App. 17/529,708 · Granted Jul 18, 2023

Low latency for network devices not supporting LLD

Inventors: Sabarinathan Nagarajan (Karnataka, IN); Lakshmi Arunkumar (Karnataka, IN); Ian G. Wheelock (Cork, IE)
Assignee: ARRIS ENTERPRISES LLC
H04L45/121H04L45/123H04L45/302H04L45/38H04L47/24H04L47/2483
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 11,706,124
App. No.
17/529,708
Granted
Jul 18, 2023
Kind
B2
Abstract

An optimizing agent of a network device that does not support low latency DOCSIS can identify traffic or packets associated with a client resource for an optimization service flow. For example, the optimizing agent can receive a priority notification associated with a client resource from a low latency controller that is indicative of a low latency requirement associated with the client resource. The optimizing agent identifies the traffic for the optimized service flow based on the priority notification. The identifying can require modifying one or more parameters of an existing service flow, creating a new service flow, or selecting an existing service flow with low latency. The identified traffic can be routed to the optimized service flow to achieve low latency or high QoS.

Claims (67)

1. A method for an optimizing agent of a network device in a network, the method comprising:

establishing a connection to a low latency controller, wherein at least one access point device of the network does not support low latency data over cable service interface specification (LLD);

receiving a prioritization notification associated with a client resource from the low latency controller over one or more existing service flows, wherein the prioritization notification is indicative of a low latency requirement associated with the client resource; and

identifying traffic associated with the client resource for an optimized service flow, wherein the optimized service flow is a service flow that provides low latency as required by the client resource, and wherein identifying the traffic for the optimized service flow comprises one of:

modifying one or more service flow parameters of the optimized service flow, wherein the optimized service flow is one of the one or more existing service flows;

creating a new service flow as the optimized service flow; or

selecting a low latency service flow from the one or more existing service flows on which one or more low latency packets are currently routed as the optimized service flow.

2. The method of claim 1 , wherein when the identifying the traffic for the optimized service flow comprises selecting the low latency service flow from the one or more existing service flows on which one or more low latency packets are currently routed as the optimized service flow, the selecting the low latency service flow comprises:

determining one or more traffic class attributes associated with the low latency service flow;

determining a usage factor associated with the low latency service flow; and

identifying the low latency service flow based on the traffic class, the usage factor, or both.

3. The method of claim 1 , wherein when the identifying the traffic for the optimized service flow comprises creating the new service flow as the optimized service flow, the new service flow comprises one or more low latency parameters.

4. The method of claim 3 , further comprising:

sending a dynamic service addition (DSA) message to a broadband access equipment to create the new service flow, wherein the DSA message comprises the one or more low latency parameters.

5. The method of claim 1 , wherein when the identifying the traffic for the optimized service flow comprises modifying one or more service flow parameters of the optimized service flow, the modifying the one or more service flow parameters comprises sending a dynamic service change (DSC) message to a broadband access equipment.

6. The method of claim 1 , further comprising:

determining a cessation of the traffic associated with the client resource; and

altering the optimized service flow based on the cessation of the traffic associated with the client resource.

7. The method of claim 6 , wherein altering the optimized service flow comprises at least one of:

reverting the modification of the one or more service flow parameters;

deleting the optimized service flow; or

ceasing routing of the traffic on the optimized service flow.

8. A network device in a network, the network device comprising:

a memory storing one or more computer-readable instructions of an optimizing agent of the network device; and

a processor configured to execute the one or more computer-readable instructions to:

establish a connection to a low latency controller, wherein at least one access point device of the network does not support low latency data over cable service interface specification (LLD);

receive a prioritization notification associated with a client resource from the low latency controller over one or more existing service flows, wherein the prioritization notification is indicative of a low latency requirement associated with the client resource; and

identify traffic associated with the client resource for an optimized service flow, wherein the optimized service flow is a service flow that provides low latency as required by the client resource, and wherein identifying the traffic for the optimized service flow comprises one of:

modifying one or more service flow parameters of the optimized service flow, wherein the optimized service flow is one of the one or more existing service flows;

creating a new service flow as the optimized service flow; or

selecting a low latency service flow from the one or more existing service flows on which low latency packets are currently routed as the optimized service flow.

9. The network device of claim 8 , wherein when the identifying the traffic for the optimized service flow comprises selecting the low latency service flow from the one or more existing service flows on which one or more low latency packets are currently routed as the optimized service flow, the selecting the low latency service flow comprises:

determining one or more traffic class attributes associated with the low latency service flow;

determining a usage factor associated with the low latency service flow; and

identifying the low latency service flow based on the traffic class, the usage factor, or both.

10. The network device of claim 8 , wherein when the identifying the traffic for the optimized service flow comprises creating the new service flow as the optimized service flow, the new service flow comprises one or more low latency parameters.

11. The network device of claim 10 , wherein the processor is configured to execute one or more further instructions to:

send a dynamic service addition (DSA) message to a broadband access equipment to create the new service flow, wherein the DSA message comprises the one or more low latency parameters.

12. The network device of claim 8 , wherein when the identifying the traffic for the optimized service flow comprises modifying one or more service flow parameters of the optimized service flow, the modifying the one or more service flow parameters comprises sending a dynamic service change (DSC) message to a broadband access equipment.

13. The network device of claim 8 , wherein the processor is configured to execute one or more further instructions to:

determine a cessation of the traffic associated with the client resource; and

alter the optimized service flow based on the cessation of the traffic associated with the client resource.

14. The network device of claim 13 , wherein altering the optimized service flow comprises at least one of:

reverting the modification of the one or more service flow parameters;

deleting the optimized service flow; or

ceasing routing of the traffic on the optimized service flow.

15. A non-transitory computer-readable medium storing one or more instructions, which when executed by a processor of a network device of a network, cause the network device to perform one or more operations to:

establish a connection to a low latency controller, wherein at least one access point device of the network does not support low latency data over cable service interface specification (LLD);

receive a prioritization notification associated with a client resource from the low latency controller over one or more existing service flows, wherein the prioritization notification is indicative of a low latency requirement associated with the client resource; and

identify traffic associated with the client resource for an optimized service flow, wherein the optimized service flow is a service flow that provides low latency as required by the client resource, and wherein identifying the traffic on the optimized service flow comprises one of:

modifying one or more service flow parameters of the optimized service flow, wherein the optimized service flow is one of one or more existing service flows;

creating a new service flow as the optimized service flow; or

selecting a low latency service flow from the one or more existing service flows on which low latency packets are currently routed as the optimized service flow.

16. The non-transitory computer-readable medium of claim 15 , wherein when the identifying the traffic for the optimized service flow comprises selecting the low latency service flow from the one or more existing service flows on which one or more low latency packets are currently routed as the optimized service flow, the selecting the low latency service flow comprises:

determining one or more traffic class attributes associated with the low latency service flow;

determining a usage factor associated with the low latency service flow; and

identifying the low latency service flow based on the traffic class, the usage factor, or both.

17. The non-transitory computer-readable medium of claim 15 , wherein when the identifying the traffic for the optimized service flow comprises creating the new service flow as the optimized service flow, the new service flow comprises one or more low latency parameters.

18. The non-transitory computer-readable medium of claim 17 , wherein the one or more instructions when further executed by the processor cause the access point device to further perform the one or more operations to:

send a dynamic service addition (DSA) message to a broadband access equipment to create the new service flow, wherein the DSA message comprises the one or more low latency parameters.

19. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions when further executed by the processor cause the access point device to further perform the one or more operations to:

determine a cessation of the traffic associated with the client resource; and

alter the optimized service flow based on the cessation of the traffic associated with the client resource.

20. The non-transitory computer-readable medium of claim 19 , wherein altering the optimized service flow comprises at least one of:

reverting the modification of the one or more service flow parameters;

deleting the optimized service flow; or

ceasing routing of the traffic on the optimized service flow.

Assignments (9)
SECURITY INTEREST Recorded Apr 8, 2026
From: ARRIS ENTERPRISES LLC; RUCKUS IP HOLDINGS LLC
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 075476/0814 →
RELEASE OF SECURITY INTEREST AT REEL/FRAME 059350/0743 Recorded Jan 12, 2026
From: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
To: ARRIS ENTERPRISES LLC; COMMSCOPE TECHNOLOGIES LLC; COMMSCOPE NORTH CAROLINA, LLC (F/K/A COMMSCOPE, INC. OF NORTH CAROLINA)
Reel/Frame 074594/0156 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS AT REEL/FRAME NO. 59710/0506 Recorded Jan 9, 2026
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
To: ARRIS ENTERPRISES LLC; COMMSCOPE TECHNOLOGIES LLC; COMMSCOPE NORTH CAROLINA, LLC (F/K/A COMMSCOPE, INC. OF NORTH CAROLINA)
Reel/Frame 074282/0522 →
RELEASE OF SECURITY INTEREST AT REEL/FRAME 059350/0921 Recorded Dec 19, 2024
From: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
To: ARRIS ENTERPRISES LLC (F/K/A ARRIS ENTERPRISES, INC.); COMMSCOPE, INC. OF NORTH CAROLINA; COMMSCOPE TECHNOLOGIES LLC
Reel/Frame 069743/0704 →
SECURITY INTEREST Recorded Dec 17, 2024
From: ARRIS ENTERPRISES LLC; COMMSCOPE TECHNOLOGIES LLC; COMMSCOPE INC., OF NORTH CAROLINA; OUTDOOR WIRELESS NETWORKS LLC; RUCKUS IP HOLDINGS LLC
To: APOLLO ADMINISTRATIVE AGENCY LLC
Reel/Frame 069889/0114 →
SECURITY INTEREST Recorded Mar 9, 2022
From: ARRIS ENTERPRISES LLC; COMMSCOPE TECHNOLOGIES LLC; COMMSCOPE, INC. OF NORTH CAROLINA
To: WILMINGTON TRUST
Reel/Frame 059710/0506 →
TERM LOAN SECURITY AGREEMENT Recorded Mar 8, 2022
From: ARRIS ENTERPRISES LLC; COMMSCOPE TECHNOLOGIES LLC; COMMSCOPE, INC. OF NORTH CAROLINA
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 059350/0921 →
ABL SECURITY AGREEMENT Recorded Mar 8, 2022
From: ARRIS ENTERPRISES LLC; COMMSCOPE TECHNOLOGIES LLC; COMMSCOPE, INC. OF NORTH CAROLINA
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 059350/0743 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 18, 2021
From: NAGARAJAN, SABARINATHAN; ARUNKUMAR, LAKSHMI; WHEELOCK, IAN G.
To: ARRIS ENTERPRISES LLC
Reel/Frame 058152/0923 →
Continuity (2)
Provisional Application 63127240 · Dec 18, 2020
Related Publication 20220200890A1 · Jun 23, 2022
Cited By (3)
US 12,261,765 US 12,401,541 US 12,413,532