Method and system for multi-domain-based low latency, low loss, and scalable throughput congestion control
A method, a network device, and a non-transitory computer-readable storage medium are described in relation to a coordinated domain-based low latency, low loss, and scalable throughput (L4S) service. The service may enable end-to-end congestion control based on a predetermined order of domains, which are associated with L4S devices that support a packet flow, for which congestion control responses are to be provided. The service may provide independent feedback loops of state information from each domain and associated L4S device. The feedback loops may operate on different timescales. The service may coordinate congestion control among domains of an end-to-end path that support the packet flow and prevent fragmented or contentious congestion control responses between the domains.
1 . A method comprising:
receiving, by one or more network devices comprising one or more processors and one or more memories, first state information from low latency, low loss, scalable throughput (L4S) capable devices associated with domains that support a packet flow end-to-end via a network;
analyzing, by the one or more network devices, the first state information;
determining, by the one or more network devices in response to the analyzing, congestion pertaining to the packet flow;
selecting, by the one or more network devices, a first L4S capable device of a first domain of the L4S capable devices and the domains based on a predetermined order of the domains for which congestion control responses are to be provided, wherein the predetermined order is configured prior to receiving the first state information;
generating, by the one or more network devices, a first congestion control response; and
transmitting, by the one or more network devices to the first L4S capable device, the first congestion control response.
2 . The method of claim 1 , wherein the domains include a user domain, a radio access network domain, a core network domain, and a transport network domain.
3 . The method of claim 1 , wherein the first congestion control response includes a schedule for the first L4S capable device to provide a congestion control mechanism.
4 . The method of claim 1 , wherein the first state information is received from each of the L4S capable devices according to different timescales relating to the domains.
5 . The method of claim 1 , wherein the first congestion control response includes invoking rate adaptation or explicit congestion notification marking.
6 . The method of claim 1 , further comprising:
receiving, by the one or more network devices after the transmitting, second state information from the L4S capable devices;
determining, by the one or more network devices, the congestion pertaining to the packet flow;
selecting, by the one or more network devices, a second L4S capable device of a second domain of the L4S capable devices of the domains based on the predetermined order; and
transmitting, by the one or more network devices to the second L4S capable device, a second congestion control response.
7 . The method of claim 1 , wherein the analyzing further comprises:
analyzing, by the one or more network devices, the first state information, historical state information, and historical L4S congestion control decisions and outcomes associated with an end-to-end network path of the packet flow.
8 . The method of claim 1 , wherein the L4S capable devices include an end device, a radio access network device, a core network device, a transport network device, and an application server device.
9 . One or more network devices comprising:
one or more processors, wherein the one or more processors are configured to:
receive first state information from low latency, low loss, scalable throughput (L4S) capable devices associated with domains that support a packet flow end-to-end via a network;
analyze the first state information;
determine, in response to the analysis, congestion pertaining to the packet flow;
select a first L4S capable device of a first domain of the L4S capable devices and the domains based on a predetermined order of the domains for which congestion control responses are to be provided, wherein the predetermined order is configured prior to receiving the first state information;
generate a first congestion control response; and
transmit to the first L4S capable device, the first congestion control response.
10 . The one or more network devices of claim 9 , wherein the domains include a user domain, a radio access network domain, a core network domain, and a transport network domain.
11 . The one or more network devices of claim 9 , wherein the first congestion control response includes a schedule for the first L4S capable device to provide a congestion control mechanism.
12 . The one or more network devices of claim 9 , wherein the first state information is received from each of the LAS capable devices according to different timescales relating to the domains.
13 . The one or more network devices of claim 9 , wherein the first congestion control response includes invoking rate adaptation or explicit congestion notification marking.
14 . The one or more network devices of claim 9 , wherein the one or more processors are further configured to:
receive, after the transmitting, second state information from the L4S capable devices;
determine, the congestion pertaining to the packet flow;
select a second L4S capable device of a second domain of the LAS capable devices of the domains based on the predetermined order; and
transmit to the second L4S capable device, a second congestion control response.
15 . The one or more network devices of claim 9 , wherein the one or more processors are further configured to:
analyze the first state information, historical state information, and historical L4S congestion control decisions and outcomes associated with an end-to-end network path of the packet flow.
16 . The one or more network devices of claim 9 , wherein the L4S capable devices include an end device, a radio access network device, a core network device, a transport network device, and an application server device.
17 . A non-transitory computer-readable storage medium storing instructions executable by one or more processors of one or more network devices, wherein the instructions are configured to:
receive first state information from low latency, low loss, scalable throughput (L4S) capable devices associated with domains that support a packet flow end-to-end via a network;
analyze the first state information;
determine, in response to the analysis, congestion pertaining to the packet flow;
select a first L4S capable device of a first domain of the L4S capable devices and the domains based on a predetermined order of the domains for which congestion control responses are to be provided, wherein the predetermined order is configured prior to receiving the first state information;
generate a first congestion control response; and
transmit to the first L4S capable device, the first congestion control response.
18 . The non-transitory computer-readable storage medium of claim 17 , wherein the domains include a user domain, a radio access network domain, a core network domain, and a transport network domain.
19 . The non-transitory computer-readable storage medium of claim 17 , wherein the first state information is received from each of the L4S capable devices according to different timescales relating to the domains.
20 . The non-transitory computer-readable storage medium of claim 17 , wherein the instructions are further configured to:
analyze the first state information, historical state information, and historical L4S congestion control decisions and outcomes associated with an end-to-end network path of the packet flow.