5GS User Equipment S-NSSAI Storage for Per-Slice UE Limits
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The implementation method for managing the number of User Equipments (UEs) allowed for each network slice in the 5G System (5GS) is not clear, posing a challenge in network slicing enhancements.
Innovation Solution
A User Equipment (UE) is equipped with a transmission and/or reception unit, a storage unit, and a controller that receives Single Network Slice Selection Assistance Information (S-NSSAI) and a back-off timer value, allowing the controller to manage the storage and deletion of S-NSSAI, thereby controlling the number of UEs per slice.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the UE stores S-NSSAI in first NSSAI to enable network slice selection, then the network slicing capability is improved, but the device complexity increases due to managing multiple NSSAI lists and back-off timers
Solution Approach 1:
The UE performs preliminary actions by storing S-NSSAI in first NSSAI before actual network slice selection is needed. The back-off timer is pre-configured with the network, allowing the UE to proactively manage slice availability and anticipate connection requirements, reducing complexity during active communication.
Solution Approach 2:
The NSSAI information is segmented into first NSSAI (stored locally) and second NSSAI (received from network), with further division into allowed NSSAI and rejected NSSAI. This segmentation allows the UE to manage different slice information separately, reducing overall management complexity while maintaining comprehensive network slicing capability.
2Reliability
If the UE manages back-off timer for each S-NSSAI to control UE density per slice, then the network slice management is improved, but the loss of time occurs due to timer management operations
Solution Approach 1:
The back-off timer operates autonomously once configured by the network. The UE automatically manages timer start, stop, and reset operations based on S-NSSAI storage and deletion events without requiring continuous network intervention, reducing time loss while maintaining reliable slice management.
Solution Approach 2:
The system implements feedback mechanisms where the UE monitors its own NSSAI list state and automatically triggers timer start/stop operations in response to storage/deletion events. This closed-loop feedback ensures accurate slice management while minimizing unnecessary timer operations that would consume time.
3Adaptability or versatility
If the UE deletes S-NSSAI from first NSSAI when slice is no longer needed, then the adaptability is improved, but the device complexity increases due to continuous monitoring of NSSAI validity
Solution Approach 1:
The UE performs periodic monitoring of NSSAI validity based on trigger events such as timer expiration, network commands, or connection state changes. Rather than continuous monitoring, these periodic checks reduce the complexity of validity monitoring while maintaining dynamic adaptability when slices are no longer needed.
Solution Approach 2:
The UE prepares for potential S-NSSAI deletion by maintaining awareness of slice validity conditions in advance. When conditions indicate a slice is no longer needed (timer expiration, network rejection), the UE is already positioned to quickly delete the S-NSSAI from first NSSAI, achieving dynamic adjustment without requiring complex real-time monitoring.
Data Source
AI summary
In a 5GS, a communication unit is provided that is intended to implement functions related to management of information regarding a network slice. In the 5GS, a method and a communication unit are provided for initial registration of UE and for a periodic registration procedure or a registration procedure based on movement for achieving management of information regarding network slices. Furthermore, a method and a communication unit are provided for a network slice-specific authentication and/or authorization procedure, and a UE configuration update procedure, and a de-registration procedure after completion of a registration procedure.