URSP Rule Handling for Redundant PDU Session Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing networks face challenges in managing terminals that do not support PDU session pair IDs and those that do, complicating the management of redundant PDU sessions.
Innovation Solution
Creating and transmitting URSP rules for terminals that do and do not support PDU session pair IDs to facilitate comprehensive network management of both types.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the network side initiates a PDU session modification procedure to update QoS parameters, then the QoS parameters can be updated, but the terminal cannot adjust uplink traffic sensitivity parameters, causing a loss of adaptability for uplink traffic variations
Solution Approach 1:
The patent segments the PDU session management into two independent parts: downlink QoS parameter management (controlled by network side) and uplink traffic sensitivity parameter management (controlled by terminal side). This segmentation allows the terminal to independently adjust uplink parameters based on local traffic conditions without requiring network side initiation, thereby improving adaptability while maintaining clear division of responsibilities
Solution Approach 2:
The terminal is empowered to autonomously adjust its own uplink traffic sensitivity parameters based on local traffic detection and QoS requirements, without needing to wait for network side instructions. This self-service capability enables the terminal to adapt to uplink traffic variations in real-time, improving system responsiveness and adaptability
2Adaptability or versatility
If the terminal autonomously adjusts QoS parameters based on local traffic conditions, then the adaptability to traffic variations improves, but the consistency of QoS management between network and terminal deteriorates
Solution Approach 1:
The patent clearly segments the QoS management responsibilities: the network side manages downlink QoS parameters and overall session configuration, while the terminal manages uplink traffic sensitivity parameters. This segmentation allows each side to operate independently within its domain, maintaining consistency through clear boundary definition rather than through constant coordination
Solution Approach 2:
The terminal monitors uplink traffic conditions and QoS parameter configurations, and when it detects that traffic sensitivity parameters need adjustment, it initiates a PDU session modification request to the network side. The network side acknowledges and applies the terminal's parameter adjustments, creating a feedback loop that maintains consistency while allowing terminal autonomy
3Speed
If the PDU session modification procedure is initiated from the network side, then the network can control QoS parameters, but the terminal cannot initiate modifications, causing delays in responding to uplink traffic changes
Solution Approach 1:
The patent inverts the traditional initiation direction of PDU session modification: instead of only the network side initiating modifications, the terminal can now initiate PDU session modification procedures when it needs to adjust uplink traffic sensitivity parameters. This inversion enables faster response to uplink traffic changes while maintaining the overall network-controlled architecture through the gNB's final approval and configuration application
Data Source
Figure 1
Figure 2
Figure 3
AI summary
One disclosure of the present specification provides a method by which a policy control function (PCF) performs communication. The method comprises the steps of: receiving a UE policy association establishment (UE association establishment) message from an access and mobility management function (AMF); and transmitting a UE route selection policy (URSP) rule to a user equipment (UE), wherein the URSP rule includes a first route selection descriptor (RSD) and a second RSD, the first RSD includes a protocol data unit (PDU) session pair identifier (ID), the PDU session pair ID is used to establish two redundant PDU sessions, and the second RSD does not include the PDU session pair ID.