Network Slice Subscription Changes Through Back-Off Timer Clearing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users attempting to dynamically change network slicing subscriptions face high latency and inefficient network operations due to back off timers triggered by rejected PDU session requests, preventing immediate access to newly subscribed network slices.
Innovation Solution
A network-connected device receives a network subscription status update, allowing it to clear active back off timers and immediately attempt PDU sessions with newly subscribed network slices, thereby reducing latency and conserving resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a back off timer is triggered when a PDU session request is rejected, then network security and stability are improved, but access latency increases and user productivity deteriorates
Solution Approach 1:
The system performs preliminary actions by pre-configuring multiple network slices with different back off timer durations based on service type. Critical slices have shorter timer durations while non-critical slices have longer durations, allowing the system to prepare for different scenarios in advance and reduce overall access latency while maintaining security.
Solution Approach 2:
The back off timer mechanism is made dynamic by allowing the timer duration to be adjusted based on the specific network slice being accessed and the user's subscription status. The system can extend or reduce timer durations dynamically during the session establishment process, optimizing the balance between security and accessibility.
2Reliability
If a back off timer is used to prevent permanent failure errors, then network stability is improved, but device power consumption increases
Solution Approach 1:
The system pre-establishes multiple network slices with differentiated back off timer configurations before actual access is needed. This preliminary configuration allows the device to use shorter timer durations for critical services, reducing the time the device needs to wait and thereby reducing power consumption while maintaining network stability.
Solution Approach 2:
The system changes the back off timer parameter dynamically based on the network slice type and service requirements. By adjusting the timer duration parameter according to the specific access scenario, the system optimizes the balance between maintaining network stability and minimizing device power consumption.
3Ease of operation
If power cycling is used to clear back off timers, then access to network slices is restored, but time loss and operational inefficiency increase
Solution Approach 1:
The system performs preliminary actions by configuring multiple network slices with appropriate back off timer settings before access is needed. This allows the device to manage timer expiration and access restoration through normal operational processes rather than requiring power cycling, thereby reducing time loss while maintaining ease of operation.
Solution Approach 2:
The device can clear back off timers through normal operational processes such as session re-establishment or timer expiration management, without requiring power cycling. The system enables self-service timer clearance through standard operational mechanisms, reducing both time loss and operational complexity.
Data Source
AI summary
In some implementations, a network-connected device may receive, from a network entity, a network subscription status update that indicates that the network-connected device is permitted to access a network slice for which the network-connected device has an associated back off timer running. The network-connected device may clear the back off timer based on receiving the network subscription status update. The network-connected device may transmit, to the network entity, a packet data unit session request associated with the network slice based on clearing the back off timer.