UE Timer Start Logic for On-Demand Slice Deregistration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing core network in LTE/LTE-A systems faces challenges in accommodating high-speed, ultra-wide band services required by 5G mobile communication, particularly in scenarios requiring high reliability and low latency, such as autonomous driving and factory automation, due to insufficient latency support in 4G networks.
Innovation Solution
Implementing a method and user equipment (UE) that includes starting a slice deregistration inactivity timer upon release of a protocol data unit (PDU) session associated with an on-demand Network Slice Selection Assistance Information (NSSAI) when no user plane resources are established, allowing for efficient management of network slices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If the core network is designed for existing LTE/LTE-A systems, then the network structure is stable and established, but it cannot accommodate high-speed ultra-wide band services requiring low latency
Solution Approach 1:
The patent segments the network into different slices (network slicing) to accommodate diverse service requirements. By dividing the core network into multiple isolated slices, each optimized for specific services (eMBB, mMTC, URLLC), the system can achieve high-speed data transfer for ultra-wide band services while maintaining the stability of existing LTE/LTE-A infrastructure. This segmentation allows simultaneous support of legacy and advanced services without requiring complete network redesign.
2Adaptability or versatility
If network slicing is implemented to support diverse services, then service adaptability is improved, but slice management complexity increases
Solution Approach 1:
The patent implements preliminary action by pre-configuring slice deregistration inactivity timers during slice establishment. Instead of managing slice resources dynamically in real-time, the system pre-sets timer values that automatically trigger slice deregistration when inactivity thresholds are met. This preliminary configuration simplifies ongoing slice management while maintaining high service adaptability, as the timer-based mechanism handles resource cleanup automatically without complex real-time decision-making.
Solution Approach 2:
The slice management system employs self-service mechanisms through automatic timer-based deregistration. When slices become inactive, the pre-configured timers automatically trigger resource release and deregistration procedures without requiring manual intervention or complex control logic. This self-service approach reduces management complexity while preserving the ability to support diverse services through maintained slice configurations.
3Reliability
If slice resources are maintained continuously, then service availability is improved, but resource waste occurs when slices are inactive
Solution Approach 1:
The patent implements periodic action through slice deregistration inactivity timers that continuously monitor slice usage status. These timers periodically check whether slices remain active and automatically trigger deregistration when inactivity periods exceed threshold values. This periodic monitoring ensures service availability is maintained for active slices while automatically releasing resources from inactive slices, preventing resource waste without compromising reliability of currently serving slices.
Data Source
AI summary
According to one embodiment of this specification, there is provided a method performed by a user equipment (UE). The method may comprise: receiving a REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message including on-demand Network Slice Selection Assistance Information (NSSAI) and a slice deregistration inactivity timer. The on-demand NSSAI may include one or more on-demand single NSSAIs (S-NSSAIs). The method may further comprise: starting the slice deregistration inactivity timer for a first on-demand S-NSSAI, if a protocol data unit (PDU) session associated with the first on-demand S-NSSAI is released, if there is no established user plane resources of a multi-access (MA) PDU session associated with the first on-demand S-NSSAI and if there is no PDU session associated with the first on-demand S-NSSAI.