Reflective EPS Bearers for QoS Differentiation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wireless communication systems face challenges in efficiently routing network traffic to ensure appropriate Quality of Service (QoS) for dynamic applications and complex protocols, particularly in scenarios where Traffic Flow Templates (TFTs) are inadequate or resource-intensive, leading to difficulties in differentiating between various data streams and managing congestion.
Innovation Solution
Implementing reflective EPS bearers, which allow User Equipment (UE) to send uplink packets via the same bearer as received downlink packets, based on determining that an application requires specific QoS characteristics, thereby eliminating the need for frequent TFT updates and Deep Packet Inspection (DPI) for QoS differentiation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If Traffic Flow Templates (TFTs) are used for QoS differentiation, then data streams can be differentiated and routed appropriately, but the system becomes resource-intensive and requires frequent updates
Solution Approach 1:
The patent uses reflective QoS parameters copied from downlink bearers to configure uplink bearers. Instead of maintaining complex TFT rules, the system creates a mirror copy of the downlink QoS configuration for uplink traffic, eliminating the need for frequent TFT updates and reducing management overhead while maintaining accurate QoS differentiation
Solution Approach 2:
The patent inverts the traditional approach by having uplink QoS parameters derived from downlink parameters rather than defining separate TFT rules for uplink. The network sends downlink packets with QoS parameters, and the UE reflects these same parameters back for uplink traffic, reversing the conventional TFT-based unidirectional configuration model
2Adaptability or versatility
If Deep Packet Inspection (DPI) is used for QoS differentiation, then complex protocols can be handled, but signaling traffic increases and resource consumption increases
Solution Approach 1:
The patent extracts the QoS differentiation function from complex DPI processing by using reflective QoS parameters embedded in downlink packets. This extraction eliminates the need for resource-intensive DPI inspection while maintaining the ability to handle complex protocols, as the QoS information is directly provided in the packet headers
Solution Approach 2:
The system enables self-service QoS configuration where downlink packets carry QoS parameters that automatically configure the corresponding uplink bearers. This self-configuration mechanism eliminates the need for external DPI analysis and reduces processing resource consumption while maintaining adaptability to various protocols
3Reliability
If separate bearers are configured for uplink and downlink, then QoS can be optimized for each direction, but signaling traffic increases and management becomes complex
Solution Approach 1:
The patent merges uplink and downlink QoS configuration by using the same reflective QoS parameters for both directions. Instead of maintaining separate bearer configurations with independent signaling, the system combines the QoS management into a single reflective parameter set that applies to both uplink and downlink traffic, reducing signaling overhead while maintaining QoS reliability
Data Source
Figure 1
Figure 2
Figure 3
AI summary
QoS differentiation between IP data flows is carrierd out by sorting data packets into bearers. According to certain scenarios (many new IP flows, use of complex protocols requiring Deep Packet Inspection), the Packet Data Network Gateway (PDN-GW), configures the downlink bearers to request reflective bearer processing at the User Equipment (UE). If the UE detects the downlink bearers carrying this request, it sends the uplink data packets using the same donwlink bearers. In this way, the correct QoS for the uplink traffic is maintained. Downlink packets or bearers can be configured to request reflective bearer treatment through reserved QoS Class Identifier (QCI) values, Allocation and Retention Priority (ARP) values, or through an indicator specifically defined for requesting such treatment.