PDU Session PDB Allocation for Round-Trip Delay QoS
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multi-UE scenarios, existing technologies fail to effectively allocate packet delay budgets (PDBs) for uplink and downlink data flows carried in different PDU sessions, leading to potential violations of round-trip (RT) delay requirements and inadequate QoS monitoring across different user equipment.
Innovation Solution
A configuration method and device that determine PDBs for uplink and downlink data flows based on RT delay requirements, using network devices to associate and allocate PDBs across different PDU sessions, and implement QoS monitoring to ensure compliance with RT delay constraints.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If PDBs are allocated for uplink and downlink data flows in different PDU sessions of multi-UE scenarios, then QoS collaboration between UEs is improved, but system complexity increases due to cross-session coordination requirements
Solution Approach 1:
The patent introduces a PCF (Policy Control Function) as an intermediary that receives RT delay requirements from AFs and coordinates PDB allocation across multiple PDU sessions. The PCF acts as a central controller that manages the complex interactions between different UEs and network slices, thereby improving QoS collaboration without proportionally increasing overall system complexity.
Solution Approach 2:
The patent segments the PDB allocation process into separate PDU sessions while maintaining coordination through the PCF. Each PDU session can be independently managed with its own PDB parameters, allowing flexible allocation for different services and UEs while the PCF ensures the sum of PDBs meets RT delay requirements.
2Manufacturing precision
If PDB allocation is performed across multiple PDU sessions to meet RT delay requirements, then delay constraint compliance is improved, but control complexity increases due to multi-session coordination
Solution Approach 1:
The patent implements preliminary action by having the PCF receive RT delay requirements from AFs before PDB allocation is performed. The PCF proactively calculates and determines appropriate PDB values for each PDU session based on the declared RT delay requirements, ensuring delay constraint compliance is built into the allocation process from the beginning rather than being adjusted reactively.
Solution Approach 2:
The patent incorporates feedback mechanisms where the PCF monitors the actual delay performance and can adjust PDB allocations accordingly. The system collects information about delay violations or excesses and uses this feedback to optimize PDB distribution across PDU sessions, improving delay constraint compliance while adapting to changing network conditions.
Data Source
AI summary
A first network device is configured to perform: receiving a first message, where the first message indicates a round-trip (RT) delay requirement; and determining, based on the RT delay requirement, at least one of: a packet delay budget (PDB) of an uplink data flow of a service or a PDB of a downlink data flow of the service. The uplink data flow of the service is carried in a first protocol data unit (PDU) session, and the downlink data flow of the service is carried on a second PDU session.