Systems and methods for low latency DOCSIS queueing and scheduling

1. A scheduling device for managing a packet queue of a communication gateway, comprising:

a receiving portion configured to receive data packets according to at least one communication protocol;

a processor; and

a classification module configured to separate the received data packets into a first traffic queue and a second traffic queue separate from the first traffic queue,

wherein the first traffic queue includes a low latency service flow classified to have strict priority,

wherein the second traffic queue includes a primary service flow classified as having a classic priority,

wherein the low latency service flow is routed to a low latency communication channel, a portion of the low latency service flow comprising non-congesting traffic, and

wherein the primary service flow is routed to a primary communication channel separate from the low latency communication channel.

2. The scheduling device of claim 1 , comprising a modem.

3. The scheduling device of claim 2 , wherein the modem comprises one or more of a cable modem, a satellite modem, an optical network unit, and a DSL unit.

4. The scheduling device of claim 1 , comprising a modem termination system (MTS).

5. The scheduling device of claim 4 , wherein the MTS comprises one or more of a cable modem termination system, an optical network terminal, an optical line termination, a network termination unit, and a satellite termination unit.

6. The scheduling device of claim 1 , wherein the at least one communication protocol comprises one or more of a data over cable service interface specification (DOCSIS), and 802.11 wireless communication protocol, and a transfer control protocol.

7. The scheduling device of claim 1 , wherein the classification module is further configured such that the second traffic queue implements active queue management (AQM) on the primary service flow.

8. The scheduling device of claim 7 , wherein the AQM comprises a management technique including one or more of proportional integral controller enhancement, controlled delay, fear/flow cueing, bottleneck bandwidth and round trip time, low latency loss scalable throughput, DualQ, TCP-Prague, congestion exposure, data center TCP, and accurate explicit congestion notification.

9. The scheduling device of claim 8 , wherein the management technique is DualQ, and wherein the primary service flow includes a first intermediate sub-flow classified to have high-priority and a second intermediate sub-flow classified to have classic priority.

10. The scheduling device of claim 9 , wherein the first intermediate sub-flow is separate from the second intermediate sub-flow, and wherein the high-priority classification is different than the strict priority classification.

11. The scheduling device of claim 1 , wherein a portion of the low latency service flow is routed to the primary communication channel.

12. A method of scheduling incoming data traffic over a communication network by an electronic device of the communication network implementing at least one processor, comprising the steps of:

classifying packets of the incoming data traffic as being one of latency-sensitive and latency-insensitive;

separating the classified packets into a first traffic queue having strict priority and a second traffic queue having classic priority;

determining first parameters of the separated packets for a communication protocol of the communication network;

calculating second parameters of the separated packets for the communication protocol;

establishing initial traffic conditions of the incoming data traffic;

building a bandwidth allocation map (MAP) for the separated packets; and

generating results of the calculations of the separated packets over the first and second traffic queues.

13. The method of claim 12 , wherein the communication protocol comprises a data over cable service interface specification.

14. The method of claim 12 , wherein the electronic device comprises at least one of a cable modem and a cable modem termination system (CMTS).

15. The method of claim 14 , wherein the step of the building is implemented by the CMTS.

16. The method of claim 12 , further comprising the step of generating simulation traffic.

17. The method of claim 12 , further comprising, after the step of establishing initial traffic conditions, the step of executing a simulation loop.

18. The method of claim 17 , wherein the step of executing comprises addressing regular packet fragmentation, managing a high-priority queue, and managing a regular packet queue.

19. A scheduling device for managing a packet queue of a communication gateway, comprising:

a receiving portion configured to receive data packets according to at least one communication protocol;

a processor; and

a classification module configured to separate the received data packets into a first traffic queue and a second traffic queue separate from the first traffic queue,

wherein the first traffic queue includes a low latency service flow classified to have strict priority,

wherein the second traffic queue includes a primary service flow classified as having a classic priority,

wherein a first portion of the low latency service flow is routed to a low latency communication channel,

wherein the primary service flow is routed to a primary communication channel separate from the low latency communication channel, and

wherein a second portion of the low latency service flow is routed to the primary communication channel.

20. A scheduling device for managing a packet queue of a communication gateway, comprising:

a receiving portion configured to receive data packets according to at least one communication protocol;

a processor; and

a classification module configured to separate the received data packets into a first traffic queue and a second traffic queue separate from the first traffic queue,

wherein the first traffic queue includes a low latency service flow classified to have strict priority,

wherein the second traffic queue includes a primary service flow classified as having a classic priority,

wherein the second traffic queue implements, on the primary service flow, a DualQ active queue management technique, and

wherein the primary service flow includes (i) a first intermediate sub-flow classified to have high-priority, and (ii) a second intermediate sub-flow classified to have classic priority.

21. The scheduling device of claim 20 , wherein the first intermediate sub-flow is separate from the second intermediate sub-flow, and wherein the high-priority classification is different than the strict priority classification.