PDU Session QoS Flow Validation for Error Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing communication technologies face challenges in handling invalid Quality of Service (QoS) flow descriptions associated with Guaranteed Bit Rate (GBR) QoS flows in Protocol Data Unit (PDU) sessions, leading to errors and potential session failures due to missing mandatory parameters.
Innovation Solution
A method is implemented to detect and handle invalid QoS flow descriptions by determining the absence of parameters like Guaranteed Flow Bit Rate for uplink and downlink, Maximum Flow Bit Rate for uplink and downlink, and performing error handling operations such as releasing or deleting the invalid QoS flow descriptions and rules, and indicating appropriate error causes to the core network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the PDU session modification procedure is carried out to modify or create QoS rules or QoS flow descriptions, then the PDU session can be adapted to different service requirements, but invalid QoS flow descriptions with missing mandatory parameters may cause session failures
Solution Approach 1:
The patent applies preliminary action by performing validation checks on QoS flow descriptions before they are fully processed and applied to the PDU session. The UE examines whether mandatory parameters (GFBR UL, GFBR DL, MFBR UL, MFBR DL) are present in the received QoS flow description from the network, and identifies invalid descriptions in advance, preventing subsequent session failures.
Solution Approach 2:
The patent implements feedback mechanisms through error handling operations that provide information back to the network about invalid QoS flow descriptions. When invalid descriptions are detected, the UE generates error messages containing cause values (e.g., cause value 84 for syntactical error in QoS operation) and sends them to the network, enabling the network to correct the invalid descriptions and retry the modification procedure.
2Reliability
If error handling operations are performed to detect and correct invalid QoS flow descriptions, then session integrity is maintained, but additional processing time and complexity are introduced
Solution Approach 1:
The patent applies local quality by implementing targeted validation specifically for GBR QoS flows that require mandatory parameters, rather than uniformly processing all QoS flow descriptions. The UE checks whether a QoS flow is of GBR type (using 5QI or QFI to determine resource type) and only then validates the presence of mandatory parameters, reducing unnecessary processing for non-GBR flows.
Solution Approach 2:
The patent uses parameter changes by validating specific parameters (GFBR UL, GFBR DL, MFBR UL, MFBR DL) based on the QoS flow type. The error handling operations modify the processing approach based on the presence or absence of these parameters, and change the 5GSM cause value to indicate the specific type of error encountered, enabling differentiated error handling strategies.
Data Source
AI summary
A method can include receiving a non-access stratum (NAS) message for establishing or modifying a protocol data unit (PDU) session at a user equipment (UE) from a core network, determining whether there is a quality of service (QoS) flow description resulting from the establishment or modification of the PDU session that is associated with a guaranteed bit rate (GBR) QoS flow of the PDU session, and invalid, and when it is determined that there is the invalid QoS flow description associated with the GBR QoS flow of the PDU session, performing an error handling operation.