RAN ECN Packet Marking for Faster Congestion Response

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing congestion notification mechanisms in wireless communication networks, such as Over-The-Top (OTT) notifications, are too slow to enable efficient adaptation to rapidly changing network conditions, particularly affecting services that require rapid rate adjustments like live video and extended reality applications.

Innovation Solution

Implementing Explicit Congestion Notification (ECN) in a Radio Access Network (RAN) by marking packet headers with a congestion indicator, allowing the application server to quickly respond to congestion conditions through devices like a Centralized Unit (CU) monitoring parameters and marking packets with ECN based on threshold violations or buffer status.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If Over-The-Top (OTT) notification mechanisms are used for congestion notification, then implementation complexity is reduced, but response speed is too slow for efficient adaptation

Engineering Contradiction:
Improvecongestion notification response speedVSAvoidcongestion notification mechanism complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary mechanism by implementing ECN markings at the RAN level (base station/gNodeB) rather than relying on end-host detection. The base station acts as an intermediary that directly monitors network conditions and marks packets with ECN codes, enabling faster congestion notification to the application server without waiting for OTT notifications from the mobile device.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces the mechanical/protocol-based OTT notification system with a network-layer ECN mechanism. Instead of relying on application-layer protocols to detect and report congestion, the system uses IP packet header modification (ECN bits) at the network layer to directly signal congestion conditions, achieving faster response times.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Productivity

If ECN is implemented in the RAN, then congestion notification speed is improved, but network infrastructure complexity increases

Engineering Contradiction:
Improverate adaptation efficiencyVSAvoidRAN infrastructure complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent applies universality by implementing ECN functionality within the existing RAN architecture (base station/gNodeB) that already handles packet routing and quality of service management. The base station utilizes its existing processing capabilities to monitor data flow parameters and apply ECN markings, avoiding the need for separate dedicated ECN hardware and integrating the function into the universal RAN platform.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent changes the parameter used for congestion indication from implicit packet dropping (traditional TCP mechanism) to explicit ECN codes (0-3) marked in packet headers. This parameter change enables the application server to detect congestion conditions and trigger rate adaptation more efficiently, improving productivity while the implementation leverages existing RAN parameter monitoring capabilities.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12621709B2Systems and methods for explicit congestion notification in a radio access network
Publication Date: 2026.05.05 VERIZON PATENT & LICENSING INC
  • US12621709B2 patent drawing
  • US12621709B2 patent drawing
  • US12621709B2 patent drawing

AI summary

A device may include a processor configured to monitor a data flow, associated with a user equipment (UE) device, in a Radio Access Network (RAN). The processor may be further configured to detect a congestion condition for the monitored data flow associated with the UE device; generate an Explicit Congestion Notification (ECN) in response to detecting the congestion condition; and mark packets associated with the data flow with the generated ECN.