Network Slice Service Area Mapping for Reliable 5G Handover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing technologies fail to accurately identify and manage network slices supported and permitted in Radio Access Network (RAN) and core network nodes due to heterogeneous support and operator policies, leading to potential network slice availability issues during mobility and handover processes in 5G networks.
Innovation Solution
A method is introduced to identify and manage network slices supported and permitted in RAN and core network nodes by exchanging information through interfaces like N2 and Xn, utilizing the Network Slice Selection Function (NSSF) to determine the intersection of operator policies and node capabilities, enabling informed handover decisions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If network slice information is exchanged between RAN and core network nodes during setup and configuration updates, then handover reliability is improved, but device complexity increases due to additional information exchange protocols
Solution Approach 1:
The patent applies preliminary action by establishing slice support information exchange during the initial setup phase (N2 setup request/response) and configuration update phase before handovers occur. The AMF and RAN node exchange slice capability information in advance, so that when handover is needed, the target node already has the necessary information to support the UE's active slices, eliminating the need for complex real-time slice negotiation during handover execution.
Solution Approach 2:
The AMF acts as an intermediary between the RAN node and the NSSF, managing the slice support information exchange. The AMF receives slice support information from the RAN node, determines the intersection of supported and permitted slices, and provides this processed information to the RAN node. This intermediary role simplifies the overall system complexity by centralizing the slice management logic in the core network while keeping the RAN node relatively simple.
2Measurement precision
If slice support information is determined by intersection of operator policies and inherent support, then service area accuracy is improved, but processing time increases due to additional policy checks
Solution Approach 1:
The patent applies preliminary action by determining the intersection of operator policies and inherent slice support during the N2 setup phase and configuration update phase. The AMF obtains slice support information from the NSSF (which contains operator policies) and compares it with the RAN node's inherent slice support capabilities in advance. This pre-computation ensures that when handover occurs, the service area information is already accurately determined, avoiding time-consuming policy checks during the handover execution itself.
3Reliability
If comprehensive slice support information is maintained across all network nodes, then network slice management reliability is improved, but information storage requirements increase
Solution Approach 1:
The patent applies local quality by having each network node store only the slice support information relevant to its specific role and location in the network. The RAN node stores information about slices it can support in its coverage area, the AMF stores slice support information for its served UEs and the corresponding TAs, and the NSSF stores operator policies. Each node maintains the necessary slice support information locally rather than duplicating comprehensive information across all nodes, reducing overall storage requirements while maintaining management reliability through distributed information availability.
Data Source
Figure 1
Figure 2A
Figure 2B
AI summary
The present disclosure is directed to a method in a radio access node 14 and to a radio access node 14 for performing the method in a cellular communications network 10. The method comprises: sending 102 to a mobility function entity 18 in a core network of the cellular communications network 10, first information indicative of one or more tracking areas supported by the radio access node 14 and one or more network slices supported by the radio access node 14; and receiving 112B from the mobility function entity 18, second information indicative of one or more network slices that are: (a) supported by the radio access node 14 and the mobility function entity 14 and (b) permitted by one or more network policies, for each of at least one of the one or more tracking areas supported by the radio access node 14; or (a) supported by the mobility function entity 14 and (b) permitted by one or more network policies, for each of at least one of the one or more tracking areas supported by the radio access node 14. The disclosure is also directed to a corresponding method in a mobility function entity and a corresponding configured mobility function entity.