Network Slice Selection via Control Plane Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile networks face challenges in efficiently selecting and managing network slices, session management, and user plane functions for user equipment (UE), particularly in interworking between 4G/LTE and 5G systems, leading to unnecessary upgrades and inefficient resource allocation.
Innovation Solution
The proposed solution involves a control plane entity that selects a session management function and a user plane function for a UE based on specific data items, using a network repository function to delegate data retrieval and selection, ensuring efficient resource allocation and independent scaling of control and user planes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If dedicated entities (PCF+PCRF, PGW-C+SMF, UPF+PGW-U) are introduced for interworking, then interworking capability between 5GC and EPC is improved, but device complexity and resource allocation overhead increase for UEs not requiring interworking
Solution Approach 1:
The patent segments the core network into control plane functions (AMF, SMF, PCF) and user plane functions (UPF, PGW-U), allowing independent selection and instantiation of dedicated entities only where interworking is required. This segmentation enables granular deployment rather than requiring all UEs to connect to dedicated interworking entities.
Solution Approach 2:
The patent implements local quality by allowing different UEs to be routed to different entity types based on their specific interworking requirements. UEs requiring interworking are routed to dedicated entities (PCF+PCRF, PGW-C+SMF), while UEs not requiring interworking use standard 5GC entities, optimizing resource allocation for each UE's specific needs.
2Reliability
If all UEs are routed to dedicated interworking entities, then interworking support is guaranteed, but processing efficiency and resource utilization decrease for UEs not requiring interworking
Solution Approach 1:
The patent implements dynamic routing where the AMF dynamically selects appropriate target entities based on UE capabilities and interworking requirements. The system adapts its behavior per-UE rather than using a static routing approach, ensuring that only UEs requiring interworking are routed to dedicated entities while others use efficient 5GC paths.
Solution Approach 2:
The patent changes the routing parameter based on UE interworking capability indicators. The AMF evaluates UE parameters (capability flags, subscription data) and changes the target entity selection accordingly, selecting dedicated entities only when interworking parameters indicate a need, thereby optimizing processing efficiency while maintaining reliability for requiring UEs.
3Adaptability or versatility
If AMF selects both session management entity and user plane entity, then selection flexibility is improved, but control plane complexity and data retrieval overhead increase
Solution Approach 1:
The patent segments the entity selection process into distinct phases: the AMF selects the session management entity (SMF or PGW-C) based on control plane requirements, while the user plane entity (UPF or PGW-U) is selected separately based on data plane requirements. This segmentation allows independent optimization of each selection criterion.
Solution Approach 2:
The patent introduces the AMF as an intermediary that coordinates between UE requirements, network policies, and available entities. The AMF retrieves necessary data from the network repository function and uses it to make informed selection decisions, acting as a mediator that simplifies the overall selection process while maintaining flexibility.
Data Source
Figure 1A
Figure 1B
Figure 2~3
AI summary
Methods for selecting network slice, session management, and user plane functions for for user equipment (UE) are described. In one example, a control plane (CP) entity for mobility management may select a CP entity for session management for a session of a UE based on a first set of data items. The CP entity for mobility management may further select a user plane (UP) entity for the session of the UE based on a second set of data items, where second set of data items include at least some of the same data items of the first set. The CP entity for mobility management may send, to the selected CP entity, a message including an identity or indication of the selected UP entity for the session of the UE. The selected CP entity may select the identified or indicated UP entity for use in the session of the UE.