Flexible Packet Filter Scope for Reflective QoS Rule Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing 5G QoS model's Reflective QoS (RQoS) mechanism is limited by its fixed scope definition, leading to a large number of derived QoS rules, which can cause memory storage and processing issues in user equipment (UE), especially in high-bandwidth, short-lived communication scenarios, as it requires binding uplink packets to QoS flows based on symmetric port numbers, restricting its usability and increasing computational load.
Innovation Solution
Adapting the scope of packet filters for RQoS by indicating to the UE whether to include both source and destination IP addresses or only one of them, and similarly for MAC addresses and IEEE 802.1Q tags, allowing for a reduced scope of packet filters, thereby reducing the number of derived QoS rules and improving memory and processing efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the fixed scope definition is used for packet filters in RQoS, then the QoS rules can be derived systematically, but the number of derived QoS rules becomes excessively large, causing memory storage and processing issues in UE
Solution Approach 1:
The patent applies dynamics by making the packet filter scope adjustable rather than fixed. The network can dynamically configure the scope parameter to match actual traffic patterns, allowing the system to adapt between full-scoped filters (for accuracy) and reduced-scoped filters (for efficiency) based on operational needs.
Solution Approach 2:
The patent changes the scope parameter of packet filters from a fixed state to a configurable state. By modifying the scope parameter (including or excluding certain IP address fields), the system can control the number of derived QoS rules while maintaining necessary filtering accuracy for different traffic scenarios.
2Measurement precision
If the fixed scope definition includes both source and destination IP addresses and port numbers, then packet filtering precision is maintained, but computational load and memory requirements increase significantly
Solution Approach 1:
The patent applies local quality by allowing different parts of the packet filter to have different levels of specificity. Certain fields (like source IP) may be included while others (like destination port) are excluded, based on the local requirements of each QoS rule, rather than applying a uniform full-scope filter to all rules.
Solution Approach 2:
The patent modifies the scope parameter to control which packet header fields are included in filter derivation. This parameter change allows the system to reduce filtering precision selectively in scenarios where full precision is not necessary, thereby reducing computational load while maintaining adequate filtering capability.
3Reliability
If symmetric port number binding is required for RQoS, then QoS flow binding accuracy is improved, but usability is restricted and computational load increases
Solution Approach 1:
The patent makes the binding requirements dynamic rather than static. The network can configure whether symmetric port binding is required based on the specific service and traffic pattern, allowing the system to relax this requirement for services that don't need it, thereby improving usability without compromising accuracy where needed.
Solution Approach 2:
The patent creates a universal RQoS mechanism that can accommodate both symmetric and asymmetric port binding scenarios. By making the scope configurable, the same RQoS infrastructure can serve diverse applications with different binding requirements, enhancing versatility while maintaining binding accuracy for applications that require it.
Data Source
AI summary
Systems and methods provide for controlling the derivation of QoS rules in the UE by flexibly defining the scope of packet header fields over which packet filter derivation is performed. The scope of packet header fields for derivation of QoS rules may be provided by the network to the UE upon PDU Session establishment or modification. For PDU Session of IP type, the network indicates to the UE whether the scope of RQoS includes both the Source/Destination IP address pair and the Source/Destination Port numbers, or only the former. For PDU Session of Ethernet type, the network indicates to the UE whether the scope of RQoS includes both the Source/Destination MAC address pair and the IEEE 802.1Q tag, or only the former. The UE may indicate to the network whether it supports the flexible scope of packet filters for RQoS for a PDU session.