VoLTE Bandwidth Aggregation with Hysteresis Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In VoLTE call scenarios, especially during call waiting, hold, or 3-way calling, existing systems reserve excessive bandwidth, leading to inefficient usage of RAN resources as they do not accurately account for the actual bandwidth needed, resulting in waste.
Innovation Solution
Implementing hysteresis in bandwidth aggregation by tracking the last used bandwidth for GBR bearers and excluding disabled traffic flows, ensuring that only the necessary resources are allocated, thereby optimizing radio resource usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If excessive bandwidth is reserved during VoLTE call scenarios (call waiting, hold, 3-way calling), then call quality and reliability are maintained, but RAN bandwidth efficiency deteriorates and radio resources are wasted
Solution Approach 1:
The system dynamically adjusts bandwidth allocation based on call state transitions. During call waiting, hold, or 3-way calling scenarios, the network temporarily increases reserved bandwidth to ensure call quality and reliability. When these scenarios end, the system releases the excessive bandwidth, thereby maintaining both call quality and RAN efficiency through dynamic adaptation.
Solution Approach 2:
The network performs preliminary bandwidth reservation during call setup to ensure sufficient resources are available for VoLTE calls. This preliminary action guarantees call quality from the start, and the system later optimizes the reservation by excluding disabled traffic flows (such as held calls) from the aggregated bandwidth calculation, thus preventing resource waste.
2Reliability
If guaranteed minimum bandwidth is reserved for VoLTE calls at the RAN level, then call reliability is ensured, but radio resource utilization deteriorates due to finite radio resources
Solution Approach 1:
The system applies different bandwidth reservation strategies for different traffic flows within the same call. Enabled traffic flows (active voice communication) receive full bandwidth guarantees, while disabled traffic flows (held calls, control signaling) have their bandwidth requirements excluded from the aggregation. This local differentiation ensures call reliability for active flows while optimizing overall radio resource utilization.
Solution Approach 2:
The network continuously monitors call state transitions and traffic flow status, using this feedback to adjust bandwidth reservations. When calls transition to held state or 3-way calling scenarios occur, the system receives feedback about the actual bandwidth needs and adjusts the reservation accordingly, excluding disabled flows from the aggregated calculation to improve radio resource utilization while maintaining reliability for active calls.
3Quantity of substance
If bandwidth is aggregated for multiple GBR traffic flows during call scenarios, then sufficient bandwidth is allocated, but unnecessary bandwidth is reserved leading to resource waste
Solution Approach 1:
The system extracts and excludes disabled traffic flows from the bandwidth aggregation calculation. When calls are put on hold or during 3-way calling, the network identifies which traffic flows are disabled and removes them from the aggregated bandwidth requirement. This extraction ensures that only enabled traffic flows contribute to the reserved bandwidth, preventing allocation of unnecessary resources while maintaining sufficient bandwidth for active communication.
Data Source
AI summary
Bandwidth for a radio access network may be efficiently allocated for certain voice over LTE (VoLTE) services. In one implementation, a request associated with traffic flows may be received. Each of the traffic flows may be associated with an amount of guaranteed bit rate (GBR) traffic. The method may further include selectively summing the GBR traffic, to obtain an aggregate bandwidth value. The method may further include reserving an amount of GBR bandwidth corresponding to the previous version of the aggregate bandwidth value when a comparison indicates that the aggregate bandwidth value is less than the previous version of the aggregate bandwidth value; and reservation an amount of GBR bandwidth corresponding to the aggregate bandwidth value when a comparison indicates that the aggregate bandwidth value is not less than the previous version of the aggregate bandwidth value.