PDU Session Registration for EPC-to-5GC Network Slice Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing communication devices face challenges in efficiently handling protocol data unit (PDU) sessions and network slices during intersystem changes, particularly when transitioning from an evolved packet core (EPC) to a 5G core network (5GC), as the mapping of PDU sessions to network slices is unclear.
Innovation Solution
A communication device equipped with storage and processing circuits to manage PDN connections, transmitting a Registration Request message with a PDU Session Identifier and receiving a Registration Accept message containing a slice identifier, enabling efficient association of PDU sessions with network slices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a communication device establishes a PDN connection with a first network (EPC), then the device can communicate with the first network, but the mapping of the PDN connection to network slices is unclear when transitioning to a second network (5GC)
Solution Approach 1:
The patent applies preliminary action by including the PDU session identifier in the Registration Request message before the actual PDU session establishment with the second network. This allows the second network to pre-associate the PDU session with the appropriate network slice based on the slice identifier received during registration, ensuring continuous and accurate mapping without requiring additional information exchange later in the connection establishment process.
Solution Approach 2:
The patent uses the slice identifier as an intermediary element that bridges the PDN connection from the first network and the PDU session in the second network. The slice identifier acts as a mediator that carries the network slice information through the registration procedure, enabling the second network to correctly map the PDU session to the appropriate network slice without direct complex interaction between the first and second networks.
2Adaptability or versatility
If the device transmits a Registration Request message with PDU Session Identifier to the second network, then the device can maintain PDN connection context, but the processing complexity increases
Solution Approach 1:
The patent applies universality by making the PDU session identifier serve multiple functions: it identifies the PDN connection context from the first network, establishes the PDU session in the second network, and enables correct network slice mapping. By making this single identifier multi-functional, the patent avoids the need for separate message elements for each purpose, thereby reducing overall message handling complexity while increasing adaptability.
3Reliability
If the second network receives and processes the Registration Request with PDU Session Identifier, then network slice association is established, but the network processing time increases
Solution Approach 1:
The patent applies preliminary action by having the second network process and store the PDU session identifier and slice identifier association during the registration procedure before the actual PDU session establishment. This pre-processing allows the second network to quickly associate the PDU session with the correct network slice when the session is later established, reducing overall processing time while maintaining high accuracy in network slice association.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A communication device for handling a packet data network (PDN) connection and a network slice comprises at least one storage device; and at least one processing circuit, coupled to the at least one storage device. The at least one storage device stores, and the at least one processing circuit is configured to execute instructions of establishing a PDN connection with a first network; transmitting a Registration Request message of a Registration procedure to a second network, wherein the Registration Request message comprises a protocol data unit (PDU) Session Identifier (ID) identifying the PDN connection; and receiving a Registration Accept message comprising a slice identifier associated to the PDN connection, from the second network.