gNB-Level Network Slice Updates for Reliable UE Registration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network slice deployment in telecommunications networks is inflexible, as user devices cannot update supported network slices when moving to a new service node within the same tracking area, leading to registration issues.
Innovation Solution
Implement a slice management system that detects service node changes and updates user devices with the supported network slices corresponding to the new service node based on differences between the previous and new service nodes, allowing for flexible deployment at the node level.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If network slices are deployed on the Tracking Area (TA) level, then all nodes within the TA support the same set of network slices, but the user device cannot update supported network slices when entering a new node with the same TA, causing registration issues
Solution Approach 1:
The patent segments the network slice deployment from Tracking Area level to Service Node level. By dividing the TA-level deployment into individual node-level deployments, each service node can independently support different network slices. This allows the network to provide customized slice support at each node while maintaining TA-level coordination, resolving the conflict between deployment flexibility and registration reliability.
Solution Approach 2:
The patent implements local quality by allowing different service nodes within the same Tracking Area to have different network slice support configurations. Instead of uniform TA-level deployment, each node can be configured with specific network slices based on local requirements, enabling the network to optimize slice distribution at the node level while maintaining overall TA coherence.
2Adaptability or versatility
If network slices are updated at the Tracking Area level, then all nodes receive the same slice configuration, but this prevents flexible node-level slice deployment and causes registration failures when users move between nodes
Solution Approach 1:
The patent introduces an intermediary mechanism where the network maintains TA-level slice information and automatically updates the user device with appropriate slice configurations when moving between nodes. This intermediary layer at the network side manages the complexity of node-level slice deployment, allowing flexible node-specific configurations without requiring complex device-side management logic.
Solution Approach 2:
The patent implements preliminary action by pre-configuring network slice support information at each service node before the user device arrives. When a user moves to a new node, the network has already prepared the appropriate slice configuration and can immediately provide it to the user device, avoiding registration failures and eliminating the need for complex real-time negotiation.
Data Source
AI summary
Systems and methods are provided for deploying one or more network slices at a service node corresponding to a user device of a telecommunications network includes a slice management system communicatively coupled to the user device. The slice management system is to receive at least one of a service request or handover request corresponding to a user device, determine a service node change from the at least one of the service request or the handover request, determine one or more supported network slices corresponding to at least one of a new service node or a previous service node corresponding to the user device, and update the user device with the one or more supported network slices corresponding to the new service node based on a difference of at least one supported network slice between the previous service node and the new service node.