MA PDU Session Parameter Compatibility Check
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In 5G wireless communication networks, there is a challenge in determining whether the parameters of a 3GPP PDN leg are compatible with an existing MA PDU session that already has a non-3GPP leg, and handling the scenario when the parameters are not compatible, especially when establishing a PDN connection as a user-plane resource for an MA PDU session.
Innovation Solution
A method is proposed where the UE performs a local release of the MA PDU session and registration procedures if any critical parameters in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message do not match the stored values of the MA PDU session established over non-3GPP access, and includes sending a REGISTRATION REQUEST message with a PDU session status IE over non-3GPP access, and a TRACKING AREA UPDATE REQUEST message over 4G 3GPP access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a UE attempts to add a 3GPP PDN leg to an existing MA PDU session with non-3GPP leg, then multi-access connectivity is improved, but parameter compatibility and session stability deteriorate due to potential parameter mismatches
Solution Approach 1:
The patent applies preliminary action by checking parameter compatibility between the new 3GPP PDN leg and existing MA PDU session parameters before adding the leg. The UE performs a compatibility check procedure that compares parameters such as PDU session type, PDU address, SSC mode, 5GSM cause, S-NSSAI, and DNN. If parameters are compatible, the PDN leg is added successfully; if not, the UE rejects the addition, preventing session instability. This preliminary verification ensures that multi-access connectivity is enhanced only when parameter compatibility is maintained.
2Reliability
If the UE performs parameter compatibility checking before adding PDN leg, then session stability is maintained, but processing time and complexity increase
Solution Approach 1:
The patent applies partial action by performing only the necessary parameter compatibility checks required for MA PDU session operation. Rather than verifying all possible parameters, the UE checks the critical set defined in the standard: PDU session type, PDU address, SSC mode, 5GSM cause, S-NSSAI, and DNN. This selective checking approach maintains session stability while minimizing unnecessary processing time, implementing just enough verification to ensure compatibility without excessive overhead.
3Adaptability or versatility
If the UE allows adding PDN leg with non-matching parameters, then adaptability is improved, but network transparency and congestion management deteriorate
Solution Approach 1:
The patent applies feedback by implementing a parameter compatibility check mechanism that provides feedback on whether the new 3GPP PDN leg parameters are compatible with the existing MA PDU session. The UE compares parameters and provides a binary outcome: compatible or not compatible. This feedback loop ensures that only parameter-matching PDN legs are added, maintaining network transparency and preventing congestion caused by incompatible parameter configurations, while still allowing flexible multi-access connectivity when parameters align.
Data Source
AI summary
A method of handling multi-access (MA) Protocol data unit (PDU) session establishment procedure for adding a 3GPP PDN leg to an MA PDU session already established with a non-3GPP leg is proposed. In one novel aspect, for a 5GS MA PDU session already established on non-3GPP access, upon receipt of an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message for establishing a PDN connection as a user-plane resource for the MA PDU session over 3GPP access, the UE sends an ACTIVATE DEFAULT EPS BEARER CONTEXT REJECT message if any value of at least one of the critical parameters, including the PDN type, ESM cause, PDN address, S-NSSAI, SSC mode (set to SSC mode 1), and APN IEs in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message does not match/sync/compatible to the corresponding stored value of the MA PDU session with a non-3GPP leg.