Terminal Network Slice Attach Using Multiple EPS Bearer Contexts
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The definition of Network Slicing in core networks and the method for connecting to these slices are not clearly specified in existing technologies, hindering effective communication control for diverse terminal services.
Innovation Solution
A communication control method involving attach procedures with Activate Default EPS bearer context Requests to connect to multiple network slices, utilizing a Mobility Management Entity (MME) to transmit and receive messages for establishing connections to first and second network slices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a single PLMN core network is logically divided into multiple network slices to support diversifying services, then the adaptability to different service requirements is improved, but the complexity of connection management and procedure definition worsens
Solution Approach 1:
The core network is segmented into multiple network slices, each dedicated to specific services or terminals with different performance requirements. This segmentation allows the network to provide customized connectivity for diverse services (e.g., enhanced mobile broadband, machine type communication, mission critical services) while maintaining a unified physical infrastructure.
Solution Approach 2:
The attach procedure and bearer context activation mechanism are designed to be universal, capable of handling connections to a single network slice or multiple network slices simultaneously. The terminal apparatus can establish default EPS bearer contexts for each selected network slice through a standardized procedure, making the system multi-functional without requiring separate connection procedures for each slice.
2Adaptability or versatility
If multiple default EPS bearer contexts are activated for different network slices during attach procedure, then the capability to support multiple services simultaneously is improved, but the message processing complexity and procedure overhead worsens
Solution Approach 1:
The procedure merges the attach procedure with multiple default EPS bearer context activations into a single integrated process. Instead of separate procedures for each network slice connection, the terminal apparatus receives multiple Activate Default EPS Bearer Context Request messages (first, second, etc.) during the attach procedure and processes them collectively, reducing procedural overhead.
Solution Approach 2:
The network side prepares and sends multiple Activate Default EPS Bearer Context Request messages in advance during the attach procedure, before the terminal apparatus actually needs to communicate on each specific network slice. This preliminary action allows the terminal to have all necessary bearer contexts ready simultaneously, avoiding repeated message exchanges later.
3Adaptability or versatility
If network slicing is implemented without clear procedure definitions, then the flexibility for service customization is improved, but the reliability of communication control deteriorates
Solution Approach 1:
The procedure incorporates feedback mechanisms where the terminal apparatus reports the successful completion of attach procedure and network slice connections to the network side. The network side can track which network slices the terminal has connected to based on the bearer context activation confirmations, enabling reliable monitoring and control of network slice connectivity status.
Solution Approach 2:
The terminal apparatus autonomously selects network slices based on its own performance capabilities and service requirements, and automatically establishes connections by processing the attach procedure and bearer context activation messages. This self-service capability ensures reliable connection establishment without requiring complex external control for each connection decision.
Data Source
Figure 1
Figure 2A~2B
Figure 3
AI summary
Provided is a communication procedure for data transmission and/or reception suitable for a Network Slice and a DeCOR. One or a plurality of Netwok Slices are included in a core network managed by the network operator, the Netwok Slice is configured of one or a plurality of Network Funcitons, and based on registration information of a terminal apparatus or a request of the terminal apparatus, the terminal apparatus performs processing to connect to the one or the plurality of Netwok Slices corresponding to a service or an application. Furthermore, based on an authentication result from the network, the terminal apparatus performs processing to connect to a supplemental Netwok Slice.