# US 12,010,025 B2 · System and method for accelerating or decelerating a data transport network protocol based on real time transport network congestion conditions > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,010,025 B2 - Document ID: US12010025B2 - Status: Granted - Kind: B2 - Application number: 17/847,539 - Filed: 2022-06-23 - Published: 2022-10-06 - Granted: 2024-06-11 - Earliest claimed: 2017-11-27 - Assignees: Opanga Networks, Inc. - Applicants: Opanga Networks, Inc. - Inventors: Ben Hadorn; John Burnette; Dave Gibbons; Ethan Nordness - Web page: https://patentgrep.com/patent/US12010025B2 ## CPC - H04L 47/20: Traffic policing - H04L 47/11: Identifying congestion - H04L 47/193: at the transport layer, e.g. TCP related - H04L 47/196: {Integration of transport layer protocols, e.g. TCP and UDP} - H04L 47/2416: Real-time traffic - H04L 47/2466: using signalling traffic - H04L 47/2483: involving identification of individual flows - H04L 47/25: with rate being modified by the source upon detecting a change of network conditions - H04L 47/629: Ensuring fair share of resources, e.g. weighted fair queuing [WFQ] - H04W 28/0231: {based on communication conditions (dynamic wireless traffic scheduling definition based on channel quality criteria H04W72/54)} - H04W 28/0284: {detecting congestion or overload during communication (monitoring arrangements H04L43/00)} - H04W 28/0289: {Congestion control (load shedding arrangements in network planning H04W16/08; performing reselection for handling the traffic H04W36/22; wireless traffic scheduling H04W72/12)} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract A method is performed by a computing device in a data transport network. The computing device receives congestion-related information corresponding to current conditions of a portion of the network. The computing device determines whether a data transport session has a fair-share protocol. When the data transport session has the fair-share protocol, determining a congestion policy for the data transport session, and applying, using the congestion-related information, the congestion policy to the data transport session. ## Claims ### Claim 1 A non-transitory computer readable media (CRM) storing instructions that, when executed by a computing device, cause the computing device to perform steps comprising: receiving congestion-related information corresponding to current conditions of a portion of the network; determining whether a data transport session has a fair-share transport protocol, the data transport session having a first endpoint and a second endpoint, and the endpoints of the data transport session not including the computing device; and in response to determining that the data transport session has the fair-share transport protocol: selecting, according to a type of a subnetwork including the first endpoint, a database from among a plurality of databases, the subnetwork including a plurality of networked devices and being a physical Radio Access Network (RAN), a physical Internet Access Network (IAN), or both; determining a congestion policy for the data transport session by selecting, according to an identifier of a networked device including the first endpoint, according to an identifier of a networked device including the second endpoint, or according to the subnetwork, the congestion policy from among a plurality of transport congestion profiles included in the selected database, and applying, using the congestion-related information, the congestion policy to the data transport session. ### Claim 2 (depends on 1) The CRM of claim 1, wherein determining the congestion policy for the data transport session comprises determining the congestion policy according to a transport level protocol of the data transport session. ### Claim 3 (depends on 1) The CRM of claim 1, wherein determining the congestion policy for the data transport session comprises selecting the congestion policy from among the plurality of transport congestion profiles according to the identifier of the networked device. ### Claim 4 (depends on 1) The CRM of claim 1, wherein determining the congestion policy for the data transport session comprises selecting the congestion policy from among the plurality of transport congestion profiles according to the subnetwork. ### Claim 5 (depends on 1) The CRM of claim 1, wherein applying the congestion policy to the data transport session comprises providing an indication of congestion to the first endpoint or to the second endpoint. ### Claim 6 (depends on 5) The CRM of claim 5, wherein the indication is to adjust a congestion window of the data transport session. ### Claim 7 (depends on 5) The CRM of claim 5, wherein providing the indication of congestion to the first endpoint or to the second endpoint is performed by altering one or more bits in a Transport layer header of a message of the data transport session. ### Claim 8 (depends on 1) The CRM of claim 1, wherein receiving the congestion-related information comprises: receiving the congestion-related information from a network node, wherein the computing device is outside the path carrying the data transport session, and performs the method by communicating with devices in the data transport network that are in the path carrying the data transport session. ### Claim 9 (depends on 8) The CRM of claim 8, wherein the network node is a base station of a Radio Access Network (RAN) being used to communicate the transport data session, and wherein the congestion-related information includes one or more of information selected from the group consisting of throughput information, jitter information, number of competing concurrent flows information, real-time throughput information for one or more users of the RAN, information on a delay due to excess resource demand, and priority information regarding a data transport session of the RAN. ### Claim 10 (depends on 1) The CRM of claim 1, wherein the data transport session is one of a plurality of session in a same network, and wherein the congestion policy includes prioritizing the data transport session if the data transport session has been transmitting for less time, or transmitted less bytes, or both, than one of the other sessions in the same network. ### Claim 11 (depends on 10) The CRM of claim 10, wherein the congestion policy prioritizing the data transport session is implemented when the computing device detects a network transmission delay over the same network due to cross-traffic contention from the plurality of sessions.