5G Control Plane Entity Routing via Message Identifiers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In 5G network slicing, there is a lack of clear solutions for devices to distinguish between different types of control plane entities for messages, leading to inefficiencies in message routing and resource allocation.
Innovation Solution
Incorporating identifiers in messages to specify the control plane entity type or network slice, allowing devices to determine and route messages accordingly, using a combination of identifiers within NAS PDU and RRC messages to ensure accurate routing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If network slicing is introduced to support diversified service types and user requirements, then service performance and network resource utilization are improved, but device complexity increases due to the need to distinguish between multiple control plane entity types
Solution Approach 1:
The patent introduces an intermediary identifier mechanism (first identifier and second identifier) that acts as a mediator between the terminal and multiple control plane entities. These identifiers are embedded in messages to indicate message type and network slice, enabling the terminal to route messages to the correct control plane entity type (common or private) without the device itself becoming complex. The identifier system serves as a simple intermediary that resolves the complexity of distinguishing between multiple control plane entity types.
2Adaptability or versatility
If multiple network slices coexist with different control plane entity types, then service diversity is improved, but message routing accuracy deteriorates due to lack of clear distinction mechanisms
Solution Approach 1:
The patent segments the message structure by introducing distinct identifier fields (first identifier for message type, second identifier for network slice) that clearly separate and categorize different control plane entity types. This segmentation allows messages to be precisely routed to either common control plane entities or private control plane entities based on the identifier values, thereby maintaining high message routing accuracy while supporting diverse service types across multiple network slices.
3Measurement precision
If identifier fields are added to messages to indicate control plane entity type, then message routing accuracy is improved, but message overhead increases
Solution Approach 1:
The patent employs parameter changes by using compact identifier fields with defined value ranges to represent different control plane entity types. The first identifier indicates message type (common or private entity) and the second identifier indicates the network slice. These parameters are efficiently encoded within the existing message structure (NAS PDU or RRC message), achieving precise message routing while minimizing the increase in message overhead through efficient parameter representation.
Data Source
AI summary
The present disclosure relates to communication methods and communications apparatus. One example method includes receiving a first message that is sent by a terminal through an access network device and that includes a first identifier, where the first identifier is used to indicate a message type of the first message, and the message type corresponds to a control plane entity type, and determining the control plane entity type to receive the first message based on the first identifier.