5G UE Registration Handling Rejected Network Slices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In wireless communication systems, particularly in 5G networks, there is a challenge in preventing service use constraints due to mismatches between the slice information requested by terminals and the slice information allowed by the network, leading to inefficient service provision.
Innovation Solution
A registration method for user equipment (UE) in a wireless communication system, where a registration request message including requested network slice selection assistance information (NSSAI) is transmitted to the access and mobility management function (AMF), and if any S-NSSAI is rejected, the UE stores the reason for rejection and avoids using those S-NSSAI until they are no longer unavailable, focusing on available S-NSSAI for registration and service requests.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the terminal requests multiple S-NSSAI for network slice selection, then the service coverage and versatility are improved, but the service use constraint occurs when the requested S-NSSAI does not match the allowed S-NSSAI, reducing the reliability
Solution Approach 1:
The network sends feedback information to the terminal indicating whether the requested S-NSSAI is allowed or rejected, with rejection causes. The terminal uses this feedback to adjust its S-NSSAI selection, removing rejected S-NSSAI from its list and avoiding future requests for unavailable slices, thus resolving the service use constraint while maintaining versatile service coverage
Solution Approach 2:
The terminal dynamically adjusts its requested S-NSSAI list based on network feedback and current availability. When S-NSSAI availability changes or the terminal moves to a new registration area, it re-evaluates and updates its slice selection requests to match current network conditions, ensuring reliable service access
2Reliability
If the terminal stores rejected S-NSSAI information locally, then the service use constraint is prevented by avoiding unavailable slices, but the device complexity increases due to additional storage and management requirements
Solution Approach 1:
The terminal divides the S-NSSAI management into two segments: currently valid S-NSSAI for active use and rejected S-NSSAI with rejection causes for avoidance. This segmentation allows efficient storage and quick reference during service requests without requiring complex global management structures
Solution Approach 2:
The terminal stores rejected S-NSSAI information as temporary avoidance data rather than permanent configuration. The rejected S-NSSAI list can be cleared or updated when the terminal moves to a new registration area or receives updated network information, avoiding the need for complex long-term management while preventing service use constraints
Data Source
AI summary
A registration method of a user equipment (UE) in a wireless communication system is disclosed. The registration method includes transmitting a registration request message to an access and mobility management function (AMF), wherein the registration request message includes requested network slice selection assistance information (NSSAI) including single (S)-NSSAI corresponding to a network slice to which the UE intends to register with; and receiving, from the AMF, a registration accept message as a response to the registration request message, wherein if at least one of the S-NSSAI included in the requested NSSAI is rejected by the AMF, the registration accept message includes the rejected S-NSSAI and a reason for refusal for the rejected S-NSSAI.