Network Slice Rejection by Tracking Area for Flexible UE Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
User equipment (UE) often faces challenges in accessing desired network slices due to conventional network slice rejection mechanisms that apply rejections at the RA or AMF level, even when other tracking areas or AMFs within the RA support the requested network slices, leading to suboptimal user experience.
Innovation Solution
Implementing techniques for network slice rejection at the tracking area and AMF level, allowing the UE to identify supported network slices within the RA or AMF pool, and mechanisms for transferring existing PDU sessions between network slices to ensure seamless access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If network slice rejection is applied at RA or AMF level, then network management is simplified, but UE access to desired network slices is blocked even when other tracking areas or AMFs support them
Solution Approach 1:
The patent segments the network slice rejection mechanism from the RA/AMF level to the individual tracking area level. Instead of applying rejection uniformly across the entire RA or AMF pool, the network can now reject specific network slices in specific tracking areas while allowing them in others. This is achieved by maintaining separate rejection information for each tracking area, enabling fine-grained control that balances management simplicity with access flexibility.
Solution Approach 2:
The patent implements local quality by allowing different rejection states for different tracking areas within the same RA. Each tracking area can have its own network slice rejection configuration, meaning that a network slice may be rejected in one tracking area but accepted in another. This enables the network to optimize slice availability locally based on specific area conditions while maintaining overall network coherence.
2Reliability
If UE is rejected from a network slice at RA level, then network resources are protected, but user experience deteriorates due to inability to access supported slices
Solution Approach 1:
The patent introduces dynamic network slice rejection management where rejection status can vary by tracking area and be updated independently. The network can dynamically adjust which tracking areas allow access to specific network slices based on current resource conditions, load balancing requirements, or service quality considerations. This dynamic approach maintains resource protection while improving user experience by allowing access in areas where resources are available.
3Extent of automation
If network slice rejection is implemented, then network control is enhanced, but UE ability to access desired slices is reduced
Solution Approach 1:
The patent adds a new dimension to network slice rejection control by introducing tracking area as a granular level of management. Instead of binary rejection (accepted/rejected) at RA or AMF level, the system now operates in a multi-dimensional space where rejection status varies across tracking areas. This enables the network to maintain strong overall control while providing UEs with access paths through tracking areas where their desired slices are available.
Data Source
AI summary
A user equipment (UE) is configured to transmit a first registration request to a network, receive a registration accept message in response to the first registration request comprising a rejected network slice and an indication of a rejection cause corresponding to the rejected network slice and transmit a second registration request to the network comprising a requested network slice, wherein the requested network slice and the rejected network slice are a same network slice.