Simplified 3GPP Core Architecture for EPS to 5GS Mobility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Enterprise private 3GPP networks face inefficiencies and complexity when upgrading from 4G/LTE/EPC to 5G, requiring simplified core architectures for improved management and operation, while maintaining seamless user equipment mobility between Evolved Packet System (EPS) and Fifth Generation System (5GS).
Innovation Solution
A simplified 3GPP core architecture is introduced, integrating EPC/5GC core components, with control plane nodes of EPC and 5GC interfacing via the N26 interface to manage handovers and mobility through new Information Elements (IEs) in GTPv2 messages, enabling seamless session continuity and IP address preservation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a full 3GPP EPC and 5GC architecture is deployed for enterprise private networks, then seamless session continuity and mobility management are achieved, but device complexity and operational management burden increase significantly
Solution Approach 1:
The patent combines EPC and 5GC core network functions into a single integrated core network entity. The control plane nodes of both EPC and 5GC are merged, allowing them to share common infrastructure while maintaining distinct functional capabilities. This merging reduces device complexity and operational burden while preserving seamless session continuity through the integrated N26 interface implementation.
Solution Approach 2:
The integrated core network entity performs multiple functions simultaneously - it acts as both EPC and 5GC control plane nodes, handling mobility management and session continuity for both 4G and 5G systems. The N26 interface is implemented within the same entity, enabling universal interworking procedures across different radio access technologies without requiring separate dedicated infrastructure.
2Adaptability or versatility
If separate EPC and 5GC infrastructures are maintained for interworking, then comprehensive mobility management is achieved, but ease of operation and network management deteriorate
Solution Approach 1:
The patent merges the management of EPC and 5GC infrastructures into a single operational framework. By implementing the N26 interface within an integrated core network entity, network management functions can operate uniformly across both 4G and 5G systems, significantly improving ease of operation while maintaining comprehensive mobility management capabilities through the preserved interworking procedures.
3Reliability
If traditional 3GPP interworking architecture with N26 interface between separate MME and AMF is used, then seamless handover is achieved, but device complexity and resource requirements increase
Solution Approach 1:
The patent combines the MME and AMF control plane nodes into a single integrated entity that implements the N26 interface internally. This merging maintains the handover continuity functionality of the traditional architecture while eliminating the need for separate physical infrastructure, thereby reducing device complexity and resource requirements while preserving seamless handover capabilities.
Data Source
AI summary
An enterprise private network includes a simplified Third Generation Partnership Project (3GPP) core architecture for interworking between an Evolved Packet System (EPS) and a Fifth Generation (5G) system (5GS). The architecture includes an Evolved Packet Core (EPC) control plane (CP) (EPC CP) unit and a 5G core (5GC) CP (5GC CP) unit. The 5GC CP unit receives, from the EPC CP unit via an N26 interface, a message indicating a forward relocation request responsive to an indication of a handover of a Packet Data Network (PDN) connection at a user plane node from the EPS to the 5GS. The 5GC CP node establishes a Protocol Data Unit (PDU) session corresponding to the PDN connection based on PDN connection information in the message, which includes establishing a Quality of Service (QoS) Flow corresponding to an EPS bearer, and manages the PDU session at the user plane node.