Low latency for network devices not supporting LLD

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.

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.