Network Slice Registration Back-Off for Resource Limit Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing wireless communication systems face challenges in efficiently managing network slices due to resource allocation limits, leading to rejected or pending registration requests, which can overload networks and hinder efficient service provision.
Innovation Solution
A method and apparatus for user equipment (UE) and network entities to handle registration requests by including network slice assistance information (NSSAI), determining resource allocation limits, and implementing back-off timers or fallback strategies to manage network slice registration efficiently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If network slice registration requests are continuously transmitted when resource allocation reaches upper limit, then service availability is improved, but network overload increases
Solution Approach 1:
The patent applies preliminary anti-action by implementing back-off timers that prevent UE from transmitting registration requests during periods when network resources are exhausted. The timer creates a preemptive pause in registration attempts, counteracting potential network overload before it occurs, while still allowing service restoration when resources become available.
Solution Approach 2:
The patent implements dynamics by making the registration request transmission behavior adaptive based on network conditions. The back-off timer duration and registration suspension decisions are dynamically adjusted according to resource allocation status, allowing the system to flexibly respond to changing network capacity rather than following a fixed transmission pattern.
2Stability of the object's composition
If back-off timer is implemented to prevent network overload, then network stability is improved, but registration delay increases
Solution Approach 1:
The patent applies feedback by continuously monitoring network resource allocation status and using this information to adjust registration request transmission timing. The network entity provides feedback through rejection causes and resource status information, enabling UE to adapt its registration strategy and minimize delays when resources become available while maintaining stability during constrained periods.
Solution Approach 2:
The patent implements preliminary action by having UE prepare registration requests with appropriate back-off timer values in advance, based on current network conditions. This allows the system to proactively manage registration timing rather than reactively handling rejections, reducing overall registration delay while maintaining network stability.
3Productivity
If network slice resource allocation is strictly controlled, then resource efficiency is improved, but service flexibility deteriorates
Solution Approach 1:
The patent implements dynamics by making resource allocation and registration acceptance behavior adaptive rather than static. Network entities can dynamically adjust which network slices accept registration requests based on current resource availability, allowing strict control during constrained periods while maintaining flexibility when resources are abundant. This enables the system to switch between efficiency-oriented and flexibility-oriented modes as conditions change.
Solution Approach 2:
The patent applies parameter changes by modifying registration request handling parameters (such as back-off timer values, rejection causes, and slice-specific acceptance criteria) based on resource allocation status. These parameter adjustments allow the system to maintain efficient resource utilization while preserving service flexibility through configurable policy parameters that can be changed without altering the fundamental system architecture.
Data Source
AI summary
A method, performed by a user equipment (UE), in a wireless communication system, includes: transmitting, to a network entity, a registration request message including network slice assistance information (NSSAI) corresponding to a slice; receiving a response message including rejection information on a registration for the slice in case that resource allocation has reached an upper limit; and determining to suspend a registration request for the slice, based on the response message, wherein the rejection information on the registration for the slice includes information on a back-off timer or information on a rejection cause.


