UE Collision Handling For Emergency Services In 5G
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 MRU or SR procedures and network-initiated de-registration procedures, informing upper layers of the 5GMM protocol stack to initiate remedial actions, such as local de-registration and re-registration attempts, or attempting emergency services in alternative networks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the UE follows current 3GPP specifications for collision handling between MRU/SR procedures and network-initiated de-registration, then the basic collision resolution is provided, but the UE behavior is not consistently specified and emergency service setup may fail
Solution Approach 1:
The patent applies preliminary action by having the UE detect the collision condition between MRU/SR procedures and network-initiated de-registration procedures before completing the emergency service setup. The UE determines whether to abort the MRU/SR procedure or proceed with local de-registration and re-registration attempts based on pre-established collision detection mechanisms, ensuring reliable emergency service setup while managing procedural complexity through advance preparation.
2Ease of operation
If the UE aborts the MRU/SR procedure upon detecting collision with network-initiated de-registration, then the de-registration procedure can progress, but the upper layer is not informed about the failure and emergency service establishment may be compromised
Solution Approach 1:
The patent applies feedback by establishing a mechanism where the UE informs the upper layer about the failure of the MRU/SR procedure when collision with network-initiated de-registration is detected. This feedback loop ensures that the upper layer is aware of the procedure failure and can initiate appropriate remedial actions, while the UE maintains operational simplicity by following standardized collision handling procedures.
3Reliability
If the UE proceeds with local de-registration and re-registration attempts, then emergency services can be established, but additional procedures and time are required
Solution Approach 1:
The patent applies dynamics by enabling the UE to adapt its behavior based on the collision detection outcome. When collision with network-initiated de-registration is detected, the UE dynamically switches from the standard MRU/SR procedure to local de-registration and re-registration attempts, allowing emergency services to be established through alternative means while managing the time implication through conditional procedure execution.
Data Source
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. 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.