UE Collision Handling for Emergency PDU Session and De-registration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current 3GPP specifications do not consistently specify user equipment (UE) behavior in the event of collisions between procedures triggered for initiating an emergency PDU session and network-initiated de-registration procedures, leading to unclear procedural actions and potential failures in emergency service setups.
Innovation Solution
The UE determines collisions between emergency PDU session procedures and network-initiated de-registration procedures, informing upper layers of the 5GMM protocol stack to initiate remedial mechanisms, such as local de-registration and re-registration attempts, ensuring proper emergency service establishment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the UE follows current 3GPP specification for collision handling, then the MRU or SR procedure is aborted, but the upper layer is not informed about the failure of the emergency PDU session initiation
Solution Approach 1:
The patent implements feedback by notifying the upper layer about the failure of emergency PDU session initiation when collision occurs. The NAS layer informs the upper layer that the MRU/SR procedure failed due to collision with network-initiated de-registration, enabling the upper layer to take appropriate remedial actions such as attempting emergency services through alternative access methods.
2Ease of operation
If the UE procedure is aborted due to collision, then the de-registration progresses, but the emergency service setup may fail without proper notification
Solution Approach 1:
The patent applies preliminary action by detecting the collision between MRU/SR procedure and network-initiated de-registration procedure before the emergency PDU session is fully established. The UE identifies the collision condition and proactively notifies the upper layer, allowing remedial actions to be taken before the emergency service setup fails completely.
3Adaptability or versatility
If the UE follows current specification, then the collision handling is defined for MRU and SR, but UE behavior is not consistently specified for emergency PDU session initiation collision
Solution Approach 1:
The patent extends the collision handling mechanism to cover emergency PDU session initiation procedures in addition to the existing MRU and SR procedures. The solution creates a universal notification mechanism that applies to all emergency-related procedures, ensuring consistent UE behavior across different procedure types when collision with network-initiated de-registration occurs.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Solutions pertaining to user equipment, UE, behavior for collisions between network-initiated de-registration/detachment and emergency service procedures in mobile communications are proposed. An apparatus implemented in a UE determines that a mobility and periodic registration update, MRU, procedure or a service request, SR, procedure triggered for initiating an emergency protocol data unit, PDU, session collides with a network-initiated de-registration procedure while the UE interfaces with a network (310). In response to the determining, the apparatus performs one or more operations comprising a UE non-access-stratum, NAS, layer in a 5th Generation Mobility Management, 5GMM, protocol stack informing one or more upper layers of the 5GMM protocol stack of a failure of the corresponding procedure such that an upper layer of the 5GMM protocol stack initiates a mechanism for remedying the failure, or performing a local de-registration and attempting an initial registration for emergency services in the network (320).