Personal tools
 

5G Core Migration

5G_Core_Migration_Metaswitch_062020A
(5G Core Migration - Metaswitch)

- Overview

Migrating from an Evolved Packet Core (EPC) to a 5G Core (5GC) is a fundamental shift for mobile operators, enabling new 5G capabilities like ultra-low latency, network slicing, and massive IoT. 

Operators often start with a 5G Non-Standalone (NSA) architecture, which uses 5G New Radio (NR) alongside the existing EPC, before moving to a full 5G Standalone (SA) core, which requires a new, cloud-native, service-based architecture. 

This migration is a complex, evolutionary process involving upgrading or replacing core network functions, leveraging virtualization and cloud technologies, and implementing new interfaces and software-based functions. 

1. Migration paths and strategies: 

  • 5G Non-Standalone (NSA) migration: Many operators begin by deploying the NSA architecture (e.g., Option 3x), where the 5G NR radio connects to the existing 4G EPC for data and control. This allows for an earlier entry into 5G services while leveraging existing investments in the EPC network for a period of time.
  • Hybrid core architecture: Some operators use a hybrid approach, maintaining parts of the EPC network while introducing new 5G core components. This can be necessary to support specific services, such as those for legacy devices or roaming.
  • 5G Standalone (SA) migration: The eventual goal for many is to deploy a full 5G SA core, which requires a separate 5G Core network for 5G NR connections. This is a more significant undertaking that enables the full potential of 5G.

 

2. Key changes in the 5GC architecture:

  • Cloud-native and service-based architecture (SBA): Unlike the integrated, physical function-based EPC, the 5G core uses a cloud-native, software-based SBA. This makes it more flexible, scalable, and agile.
  • Virtualized network functions: The 5GC moves away from dedicated hardware to virtualized network functions (VNFs) running on commercial off-the-shelf (COTS) hardware in cloud infrastructure.
  • Network slicing: 5GC supports network slicing, which allows operators to create customized, isolated virtual networks tailored to specific use cases, such as enhanced mobile broadband (eMBB), ultra-low latency communication, and massive machine-type communication.
  • New interfaces and APIs: The 5GC introduces new interfaces and APIs, enabling greater programmability and easier integration with third-party applications and services.

 

3. Challenges and considerations:
  • Complexity: The transition is a complex, evolutionary journey that requires a holistic strategy across the entire network, as explained by Ericsson.
  • Security: The move to IP-based signaling and the proliferation of connected devices also present new security vulnerabilities that need to be addressed.
  • Investment: Migrating to a new 5GC is a significant investment that requires careful planning and strategic choices about which path to take.

 

[More to come ...]


Document Actions