5G Core 21.1 Solution Overview ISSUE 2.0

5G Core Solution Overview
www.huawei.com
Copyright © 2020, Huawei Technologies Co., Ltd. All rights reserved.

This document is Huawei's confidential information. All content is for internal use by Huawei-authorized training customers and is prohibited for any other purpose.
Without permission, no one may copy, modify, adapt, or provide this material or any part of it or derivative works based on this material to others.
Objectives
 Upon completion of this course, you will be familiar with:

 5G Core solution overview
 5G Core solution overall architecture
 5G Core solution key features
Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 3

Contents
1. 5G Core Solution Overview
2. 5G Core Solution Overall Architecture
3. 5G Core Solution Key Features

Contents
1.1 Industry Requirements on 5G Core Networks
1.2 Network Architecture Defined in 3GPP
1.3 5G Core Solution Composition

New Service Environment Facing 5G Core Networks
V2X High reliability: 99.999%

E2E latency < 5 ms, network latency < 2 ms
10 Gbit/s
Ultra-high bandwidth
communication (eMBB)
1 ms 0.5 ms 0.1 ms 1 ms 0.1 ms 0.5 ms 1 ms 3D video, UHD screen

Gigabit UBB
Digital entertainment
Smart home and office
VR
AR/VR
Network bandwidth: 4.93 Gbit/s
Network latency < 7 ms Industrial automation
Voice
Remote surgery
• Resolution: 23040 x 11520
• View: 360⁰ IoT city Autonomous driving
• Frame rate: 120 fps
IoT Low power consumption: 10+ years' battery life

Transmission bit rate < 200 kbit/s, latency < 10s
Superscale sensor
communication
Extreme
communication
1 million/km2 1 ms
NB-IoT NB-IoT NB-IoT NB-IoT

Device RAN Core Service Platform

5G Core Network Key Capabilities
10 Gbit/s  Service Based Architecture (SBA)

Ultra-high bandwidth
communication (eMBB)
Agile  Container and microservice-based
architecture
3D video, UHD screen
 Network slicing
Gigabit UBB
Digital entertainment
Smart home and office AR/VR
Industrial automation  2G/3G/4G/5G full convergence, co-deployment and co-

Voice
Remote surgery Simplified 
management
Centralized configuration and automatic site deployment
 Networking automation
Autonomous driving
IoT city
Superscale sensor Extreme

communication communication
 High forwarding capability
1 million/km 2
1 ms Efficient  High computing capability
 Low granularity lifecycle

Contents

Network Architecture Defined in 3GPP – SBA (1/2)
NSSF NEF NRF PCF UDM AF
Nnssf Nnef Npcf Npcf Nudm Naf
Nausf Namf Nsmf

AUS
AMF SMF
F
N1 N2 N4
UE (R)AN N3 UPF N6 DN
4G architecture (non-roaming) 5G non-roaming architecture (SBA)
5G key technologies and capabilities

 SBA: The 5G control plane uses the SBA, where control-plane functions are decoupled and reconstructed into network functions (NFs), and network function services
(NFSs) are defined for each NF.
 Modular control plane: Control-plane functions are modularized. To be precise, the AMF and SMF are used to separate the mobility management (MM) from the session
management (SM), and the authentication function is performed by the AUSF.
 Uniform user plane: The 5G architecture inherits the 4G control and user plane separation (CUPS) feature. The UPF functions as a normalized entity for the user plane,
and the S-GW and P-GW are no longer used.
 Network slicing: This technology accommodates different services and applications, with each network slice customized as required and slice resources mutually isolated.
 Support for mobile edge computing (MEC): MEC is enhanced on 5G networks, allowing UEs to access local networks based on uplink classifier (UL CL) and multi-
homing technologies.
 Unified authentication: 3GPP and non-3GPP access use a unified authentication mechanism and NAS.

Network Architecture Defined in 3GPP – SBA (2/2)
5G Core NF Function 4G NE Providing Similar Functions
Functions as an access point between UEs and the control plane on a core network, and
provides functions such as UE registration management, connection management,
Access management function (AMF) MME: access control and mobility management
reachability management, mobility management, authentication & authorization, and short
message (SM).
Provides functions such as session management, IP address allocation and management,

Session management function (SMF) MME&SGW-C&PGW-C: session management
UPF selection, policy enforcement, QoS control, charging data collection, and roaming.
User plane function (UPF) Forwards PS packets, processes policies and QoS, and provides traffic usage reports. SGW-U&PGW-U
Policy control function (PCF) Controls QoS policies and charging policies for service flows and IP bearer resources. PCRF
Provides subscriber data management functions, such as authentication, identification,

Unified data management (UDM) HSS
authorization, registration, and location management.
Authentication server function
Provides unified authentication services for both 3GPP and non-3GPP access. MME: authentication and AAA
(AUSF)
Network slice selection function
Selects a group of network slice instances for UEs. N/A
(NSSF)
Provides service registration, discovery, and authorization functions, and maintains
Network repository function (NRF) N/A
available NF instance information.
SMSF (Short Message Service
Function)
Provides short message function. N/A
CHF (Charging Function) Provides charging function. CG,OCS

4G/5G Network Architecture Comparison
SCS/AS
3GPP AAA SCS/AS 7 3 4
Server NSSF NEF NRF PCF UDM AF
3 5 SCS/AS
Other
4 PCRP S2b-C SDOs Nnssf Nnef Nnrf Npcf Nudm Naf
HSS Diameter 6 T8 3GPP
2 Scb S2b-U API 2 API 3 ...7 API n Nausf Namf Nsmf
PGW-C PGW-U API 1 2
Diameter 1
5 AUSF SMF
2 GTP-C
2 Sxa
GTP-U 6 AMF
1 MME
GTP-C
SGW-C SGW-U
Service Capability Exposure Function
SCTP
ePDG TRUST
eNB GTP-U N1 N2 N4
DOMAIN
S6t Rx, Nu T6a/ MB2 ISC Ns 3GPP
AP 6
Nt T6b ... interface
UE (R)AN UPF DN
EPC UE N3 N6
PCR MME/ BM- S- RCA Network
HSS PFDF
F SGSN SC CSCF F Entity
• The AMF performs access control and mobility management • The UPF is equivalent to the SGW-U and PGW-U.
functions in the MME. • The NEF is equivalent to the SCEF. However, the exposure
• The SMF performs session management of the MME, and it capabilities of the NEF do not include the IMS part.
integrates SGW-C and PGW-C functions. • The NSSF is a new NF used to select network slices.
• The PCF is equivalent to the PCRF. • The NRF is a new NF used for service registration and
• The UDM is equivalent to the HSS. discovery in SBA.
• The AUSF is equivalent to the 3GPP AAA server.

Network Architecture Defined in 3GPP – 4G/5G Convergence Networking
Architecture
Convergence and interworking defined in 3GPP
 Combined HSS and UDM

 Combined PCRF and PCF
 Combined PGW-C and SMF
 Combined PGW-U and UPF
 MME and AMF interworking
over the N26 interface

R16 ETSUN Intra-PLMN Roaming Network Architecture
Application scenarios:
1. Inter-region roaming in home routed (HR) mode: After UDM CHF
NSSF AUSF N13
inter-region roaming, an I-UPF needs to be inserted because
the (R)AN cannot communicate with the UPF in the home N12 N8 N10 N40
location. The inserted I-UPF cannot be controlled by the SMF N22 N38
in the home location, and therefore an I-SMF needs to be
N11 N16a N7 N5
inserted. AMF I-SMF SMF PCF AF
2. Enterprise services: Dedicated SMF and UPF are used for
enterprise services. When a subscriber moves out of an N14 N15
enterprise area, the enterprise UPF cannot communicate with
N1 N4 N4
the (R)AN. In this case, an I-UPF needs to be inserted. If the N2
inserted I-UPF cannot be managed by the enterprise SMF, an I-
SMF needs to be inserted.
3. International roaming in HR mode N3 N9 N6
UE (R)AN UPF UPF DN
N9 N9
I-SMF is the N11 and NAS signaling anchor. The architecture is similar to the S-GW/P-GW separation architecture of the EPC. Only the AMF/A-SMF/I-UPF is aware of the I-
SMF/I-UPF on the network. Other peripheral NFs do not need to be aware of the I-SMF/I-UPF. (The NRF adapts only to the selection procedure.) Compared with the EPC
architecture, the I-SMF/I-UPF is inserted only for bridging (without considering the UL CL/BP scenarios) and provides more simple functions (charging not involved).
NRF: 1. I-SMF/A-SMF selection process adaptation

NSSF: 1. Adaptation of the I-SMF/A-SMF selection procedure 2. Whether to insert the I-SMF/I-UPF based on the slice type (URLLC slices are not applicable)
AMF: 1. I-SMF and A-SMF selection 2. E2E service process adaptation (I-SMF/A-SMF information storage)
A-SMF: 1. N16a interface process adaptation 2. UPF selection 3. Roles adaptation 4. Policy transfer to the I-SMF in UL CL/BP scenarios
A-UPF: 1. N9 interface adaptation 2. Role adaptation

Contents

5G Core Solution Composition (1/2)
NFVO OSS/BSS  The 5G Core solution provides the core network NFs and NSA
functions defined in the 5G SA network, as well as the
convergence and interworking functions of the 2G/3G/4G for
EMS (U2020) 5G UEs.
 The 5G Core solution provides NFs, including the UNC, UDG,

VNF
VNF VNF
VNF VNF
VNF VNF
VNF UPCF, and UDM. Through the use of templates, an NF type
(UNC)
(UNC) (UDG)
(UDG) (UPCF)
(UPCF) (UDM)
(UDM) can consist of multiple NFs at the same or different times.
 Based on the NFV architecture, the 5G Core solution provides

AMF SMF NRF UPF PCF UDM
VNFM E2E service capabilities spanning hardware, cloud OS, and
MME GW-C NSSF GW-U PCRF HSS VNFs.
SGSN AUSF
Cloud OS (FusionSphere, etc.)

VIM
Hardware (E9000, RH2288, etc.)

5G Core Solution Composition (2/2)
Component Huawei Product Function
OSS IES Provides the service provider (SP) management function.
EMS U2020 An O&M management system in the core network vendor domain.
Provides NFs on the control and user planes of the 5G core network, as well as converged 2G/3G/4G functions
including:
UNC (AMF, MME, SGSN, SMF, GW-C, NRF, and NSSF)
VNF UNC, UDG, UPCF, and UDM
UDG (UPF and GW-U)
UPCF (PCF and PCRF)
UDM (UDM, HSS, and AUSF)
A network service (NS) lifecycle management module. The NFVO coordinates the control and management of
NFVO CloudOpera Orchestration NFV
the NS, VNFs for the NS, and virtual resources for the VNFs.
A VNF management module that controls VNF lifecycles (such as instantiation, configuration, and
VNFM U2020 VNF LCM
termination).
An NFVI management module that usually runs within the corresponding infrastructure domains. Its primary
VIM FusionSphere OpenStack OM functions include resource discovery, virtual resource management and allocation, and troubleshooting, as well
as resource support for VNF operating.
Provides hardware and software required by VNFs. Of the two, the hardware is a collection of compute,
Cloud OS FusionSphere OpenStack network, and storage resources, while the software includes the hypervisor, network controller, storage
manager, and other tools. The NFVI virtualizes physical resources into virtual resources for VNFs.

MEC Solution Architecture
ETSI MEC architecture MEC Key Function Domains
Mx1
CFS 1 OSS:
OSS: MEC
MEC service
service integration/orchestration/deployment/O&M
integration/orchestration/deployment/O&M
MEC system level

portal Mm8 Operations Support System center
center
User 1
Device app

 BSS:
BSS: MEC
MEC service
service provisioning
provisioning and
and billing
billing center
center
app LCM Mm1
proxy
Mx2 2
Mm9 Multi-access edge

 MEAO:
MEAO: service
service orchestration
orchestration center
center of
of MEC
MEC apps
apps
2
orchestrator
3
 MEPM:
MEPM: management
management of
of FCAPS
FCAPS and
and app
app rules
rules on
on MEPs
MEPs
MEC host level

Mm2 Mm3
Other 4 Mm4
MEC MEC
platform service 4
3  MEP:
MEP: third-party
third-party app
app integration/LCM,
integration/LCM, app
app service
service registration,
registration,
MEC discovery,
discovery, status monitoring, KPI collection management, and
status monitoring, KPI collection management, and
Mp1 Mp1 Service registry MEC
app MEC app corresponding
corresponding rule
rule and
and policy
policy management
management
platform
rules& lifecycle
eiment  MEC
MEC service:
service: built-in
built-in MEC
MEC services,
services, such
such as
as NAT/FW,
NAT/FW, LB,
LB, DNS,
DNS,
Service Traffic reqts mgmt 
DNS mgmt
rules Mm5 mgmt and
and IPsec
IPsec
handing
MEC MEC MEC control MEC platform manager
app app app From the perspective of products, the MEC host deployed at the edge is
MEC platform
Mm6 integrated with software and hardware. The MEC platform must have the
Mp2 horizontal and vertical capabilities.
Data plane
Virtualisation infrastructure Horizontal capabilities: include UPF traffic distribution, MEC service, and
Other MEC Virtualisation infrastructure manager traffic distribution association.
host Mm7
MEC host Vertical capabilities: include app integration, virtualization platform,
heterogeneous hardware, and dedicated hardware.

MEC: a Convergence of 3GPP and ETSI at the Network Edge
Logical NF Product
SMF UNC
Central UPF UDG
Edge UPF UEG
MEP UEG
MEAO MAE-CN
MEPM MAE-CN

Contents

Contents
2.1 Cloud and Microservice-based NFV Architecture
2.2 Converged Architecture

Cloud and Microservice-based NFV Architecture – Cloud-based NFV
Architecture Foundation
Network function virtualization orchestration (NFVO):
Orchestrates NSs and VNF software packages.
Manages NS lifecycles.
Globally manages, authenticates, and authorizes NFVI
resource requests.
NFVO
NFVO Manages policies on NS instances.
(Manages
(Manages NS NS
lifecycles.)
lifecycles.)
Virtualized network function manager (VNFM):

Virtualized
Virtualized Network
Network Function
Function
VNF (Such VNFM
VNFM  Manages VNF instance lifecycles.
(Such as
as CloudIMS/CloudEPC)
CloudIMS/CloudEPC)  Provides overall coordination between the NFVI and EMS.
(Manages
(Manages VNF
VNF
lifecycles.)
lifecycles.)
Cloud
Cloud OS
OS Virtualized infrastructure manager (VIM):
NFVI (Hypervisor+Management
(Hypervisor+Management Module)
Module) VIM
VIM  Controls and manages compute, storage, and network resources.
(Provisions  Collects and reports infrastructure performance counters and events.
(Provisions
virtualized
virtualized
Hardware
Hardware resources.)
resources.)
(Server/Storage/Network)
MANO

Cloud and Microservice-based NFV Architecture – Containers Are
Ideal Carriers for Running Microservices
Microservices are the best way to achieve service agility. Containers are ideal carriers for running microservices.
Function service interface
Monolithic application Microservice

Lifecycle operation:
Microservice:
Customized design in a specific environment Function running
Deployment/Scaling
Resource efficiency Microservice-specific instantiation
can maximize efficiency. However, if the entity
and scaling maximize resource
environment changes, a large amount of
efficiency.
resources may be wasted. Container: lifecycle entity
Maintenance efficiency The development and O&M Core of microservice architecture Principles for defining microservices
Development and maintenance complexity efficiency of the independent
increases rapidly with service volume. microservice team is greatly
improved.  Decoupling software logic into  Independent lifecycle
microservices. An application is broken  Independent resource scaling
down into its core functions  Independent optional
Agility Agile release is not supported.
Low granularity release significantly independent of one another. components
improves service agility.
Microservice architecture characteristics

Excessive decoupling increases the
Performance This method is generally preferred.
delay.
 Service self-governance, self-containing, and self-management
 Independent service development states and separate platform and language
selection
 Independent service running states and independent upgrades
 Contractual interfaces between services

Cloud and Microservice-based NFV Architecture – Container
Introduction (1/3)
Network function virtualization orchestration

Containers run in VNFs to (NFVO):
Orchestrates NSs and VNF software packages.
NFVO

carry microservices.
NFVO  Manages NS lifecycles.
(Manages
(Manages NS NS  Globally manages, authenticates, and authorizes
lifecycles.) NFVI resource requests.
lifecycles.)  Manages policies on NS instances.
New container management Virtualized network function manager (VNFM):

functions: Virtualized
Virtualized Network
Network Function
Function  Manages VNF instance lifecycles.
Provides container  Provides overall coordination between the NFVI
orchestration, deployment, Container Container
Container Container
Container
and scheduling capabilities.
Container VNFM
VNFM and EMS.
Provides container CT (Manages
(Manages VNF
VNF
 VNF container resource management portal
enhancement capabilities:  Manages container-based VNF lifecycles,
Container management lifecycles.)
lifecycles.) including instantiation, uninstallation, autoscaling, and
Hugepage memory, shared
memory, DPDK, CPU core transparent transmission upgrade interface.
binding, and isolation  Provides alarm reporting and KPI monitoring functions.
Supports container network
capabilities, SR-
IOV+DPDK, and multiple Cloud
Cloud OS
OS
network planes. (Hypervisor+Management
(Hypervisor+Management Module)
Module) VIM
VIM Virtualized infrastructure manager (VIM):
Supports the IP SAN
storage capability of the VM (Provisions

(Provisions
 Controls and manages compute, storage, and network
resources.
container. virtualized  Collects and reports infrastructure performance counters and
virtualized events.
Hardware
Hardware resources.)
resources.)
MANO
Management and
Orchestration

Cloud and Microservice-based NFV Architecture – Container Introduction
(2/3)
The CaaS platform is required since 5GC NFs use the microservice architecture and are deployed in containers. The
overall deployment strategy is as follows:
OSS/BSS NFVO  Smooth Introduction: Existing NFVI, VNFM,

and NFVO service processes are not affected.
Container capabilities are seamlessly introduced
Or-Vnfm Or-Vi to existing systems. Open architecture: Based
EMS EMS
on the community's container platform K8S,
Ve- Huawei container platform uses an open
Vnfm
VNF VNF VNF VNFM architecture that enables it to support a wide
range of applications. In addition, Huawei
App App K8S-Vnfm container platform keeps pace with K8S to
App pod pod pod pod Nf- ensure that the latest K8S capabilities can be
K8S CaaS-Master integrated.
CaaS-Agent CaaS-Agent  Evolvable architecture: The platform is built
Vi-Vnfm
towards the target architecture. All 5G NFs can
be deployed on the same container platform.
(Guest OS) (Guest OS) (Guest OS)
VM VM VM Vi-K8S
 Shared infrastructure: The existing NFVI can
be inherited completely without reconstruction.
Nf-Vi
Hypervisor VIM
Compute/Network/Storage PIM
* CaaS = Container as a Service

Cloud and Microservice-based NFV Architecture – Container Introduction
(3/3)
Container-based VNF Container-based VNF Container-based VNF
Existing Existing
VNF VNF
Container management Container management Container management
VM Bare-metal container VM Bare-metal container

IaaS IaaS
VM Container Bare-Metal Container Delivered by NFVI Pure Bare-Metal Container
Sharing infrastructure with existing VNFs Yes Yes No
No. The container platform is deeply integrated

Container platform decoupled from No. The container platform manages
Yes. The NFVI shields hardware. with the NFVI, and the NFVI is decoupled from
hardware infrastructure hardware infrastructure.
hardware.
Yes. The NFVI provides the multi-vendor

No. The container platform is under rapid development. It is difficult to implement multi-vendor
Multiple-vendor integration integration capability. Different vendors can
integration before standardization.
provide specific container platforms.
VMs are used to isolate containers. This enables Physical machines are used to isolate tenants. This method is not as flexible as container isolation
Multi-vendor container isolation
security isolation between tenants. by VMs.
Performance Similar to VMs Similar to physical machines

Reliability Container OS faults are within VMs. Container OS faults are within bare-metal devices.
Containers can be migrated in live mode through

Resource management flexibility Containers cannot be migrated in live mode.
VMs.
VM containers are used because bare-metal containers do not support multi-vendor integration before they are standardized.

Contents
2.1 Cloud and Microservice-based NFV Architecture
2.2 Converged Architecture

Converged Architecture
Based on CloudEdge architecture evolution, 5GC further implements 2G/3G/4G/5G full convergence.
Key architecture changes:
 Services, including basic services such as LB and

DB, are provided on a unified platform to reduce
Converged NF
system resource consumption through sharing.
3 Unified O&M (CSP)  Different microservices are used to provide

2G/3G/4G/5G service capabilities, facilitating full
Management service Resource management Service governance High availability
service convergence.
(SCF) (RMF) (CSR) management (HAF)
 Unified O&M, communication, orchestration
5G business 5G business 2G/3G/4G 2G/3G/4G
2 5G business management, reliability management, and
microservice microservice business business
microservice consistent 2G/3G/4G/5G management experience
A B microservice microservice
are provided.
Distributed transparent communication (SDR)
CSDB CSLB IPsec LI ...

1
PAE

Cloud and Microservice-based NFV Architecture – Microservice
Examples
The following tables list examples of various NF microservices.
Microservice Function NF Microservice Function NF
Data storage, synchronization, PES Policy engine service PCF

CSDB All
and backup
PAS AMF policy service PCF
Data distribution and load
CSLB All DBS Data interconnection PCF
sharing
LINK Link management UNC 2G/3G/4G business
CCU UDM
processing
2G/3G/4G subscriber
Legacy-AM UNC
management N8/N10 business
UDM UDM
processing
5G-AM 5G subscriber management UNC
AUSF N12 business processing UDM
SM Session management UNC

Contents

Contents
3.1 SBA and NRF
3.2 CUPS
3.3 2G/3G/4G/5G Full Convergence
3.4 Network Slicing
3.5 MEC

SBA and NRF – Architecture Advantages
4G point-to-point architecture 5G SBA
MME PCRF PCF UDM NEF
UE AN S-GW P-GW
Network: fixed to flexible UE
 Inter-NF relationships are locked in P2P mode: The PCRF only interworks with the P-GW strategically. Function: repeated to reused AN AMF SMF UPF
The real-time location can only be reported through the following path: AN->MME->S-GW->P-GW-  NFs can be flexibly combined: The PCF can coordinate with the UE, AMF, and SMF
>PCRF. in policies.
The real-time location can be reported through the following path: AN->AMF->PCF.
SCEF/PFDF HLR CG HSS/OCS/PCRF DNS server

HTTP
HTTP MAP GTP' Diameter DNS Any NF Any NF
Protocol: closed and messy to
SGSN/ GTP-C
S-GW
GTP-C/ open and unified
MME PMIP P-GW  The unified HTTP protocol facilitates ICT service operation.
 CT Walled Garden uses seven interface protocols. The collaboration with third-party NFs is complex.
PCF
PCRF NRF
DNS server DRA UDM
HSS
CHF
OCS AMF SMF 1 SMF 2
SGSN/ P-GW 1 P-GW 2
NF: homogeneous to differentiated.
MME Services 1, 2, and 3 Services 1, 2, 3, and 4
Version 1 Version 2  Differences between NF versions/features can be explicitly managed in a unified manner in the
Features 1, 2, and 3 Features 1, 2, 3, and 4 NRF.
 The NRF in the 5GC system can discover NFs based on the version and feature/service.
 The differences in NF versions and supported features cannot be explicitly displayed and
Traffic is flexibly diverged for businesses. The DNS/DRA does not need to be statically configured
applied in the DNS/DRA. with the traffic diversion mode.
Traffic is diverted for businesses only through software customization for specific NFs.

SBA and NRF – NRF and Network Autonomy
NRF
API capability exposure interface
Number segment
management Layering & roaming
Self- Intelligent
optimization Registration & discovery Update & heartbeat policy
engine Authentication & framework Policy library
Subscription & notification authorization
Automatic Profile attribute
Service-layer
topology NF profile attribute
address pool comprehensive
library
management management
Service discovery based on multi-dimensional attribute combinations

Service logic interface address allocation Real-time load and status reporting
& profile attribute delivery
DC 1 DC 2 DC 3
AMF SMF UPF UPF UPF AMF SMF UPF
AMF UPF AMF SMF UPF

SMF UPF UPF
Self-registration – quick launch without Automatic discovery – NF service chain

Self-optimization – real-time
1 commissioning 2 orchestration 3 load balancing
4 Deployment –
security/layering/reliability
 The NF becomes available when it The NRF can define and implement NF
 The NRF monitors the status  As the OAuth2.0 server, the NRF
automatically registers with the NRF on discovery policies based on multi-
dimensional attributes. and load of all NFs in real supports token management and
the network. The interfaces between time and broadcasts the status
Dedicated NF service chain orchestration availability authorization.
NFs/services are service-based and do not and load to all invokers of the  The NRF supports the hierarchical
need to be commissioned. can be associated with specific user
groups to implement precise traffic corresponding NFs. architecture and cross-NRF NF
 The NF/service registration/deregistration,  The NRF can select NFs based
diversion. discovery. Recursive or iterative
update/heartbeat, and on the real-time load,
A specific user group can be customized query applies to cross-NRF NF
subscription/notification mechanisms are multiplying the service
based on the number segment, region, UE discovery.
supported between NFs and the NRF. balancing speed of NFs in a  The NRF supports active/standby
capability, and specific NF.
pool. deployment, automatic failover, and
manual/automatic failback.

SBA and NRF – Comparison Effects of Applying 4G/5G Networks
4G:
5G:
Autonomy 4G 5G
Local and peer ends for each new NF need to be manually planned, and can only
The new NF/service automatically registers with an NRF to make it
be used after they are manually configured. Once a new NF goes online,
Self-registration NF onboarding available. After going online, a new NF only needs to register with the
neighboring NF configurations are affected. In this case, manual planning and
NRF.
configuration are required.
The NRF allows you to customize new network selection policies. The
Network selection policies are separately and statically configured on requested
discovery policies are centrally configured on the NRF, facilitating
New discovery NFs, such as the MME/P-GW. The policies cannot be reused or aligned with
capability reuse.
policy those of other vendors.
Self-discovery On the NRF, you can customize discovery policies based on user attributes,
The software needs to be upgraded to support new network selection parameters.
network attributes, and real-time NF status.
NF selection The MME interacts with the DNS server multiple times to select an S-GW/P- NFs can be selected based on multiple parameter combinations through an
process GW based on multiple parameter combinations. interaction with the NRF.

Contents
3.1 SBA and NRF
3.2 CUPS
3.4 Network Slicing
3.5 MEC

CUPS – Architecture for Flexible Network Deployment
5GC-CP
AMF AUSF SMF
Unified operation Central DC

Unified control plane/data/policy UDM NEF MME
Traffic steering 5GC-UP

Local processing of main MBB 5GC-UP
traffic Regional DC UPF NEF UPF NEF Internet
Distributed deployment of user
planes
Business promotion UPF MCDN UPF AR/VR V2X GW V2X App UPF 3rd App
MEC pilots in new scenarios, Edge DC
such as V2X Hotspot videos eMBB IoV Stadiums
Stadiums and
and enterprises
enterprises
2G/3G/4G/5G IoT LTE-V/5G V2X 4G/5G

CUPS – Full Meshing
Value of full meshing:
SMF SMF SMF  High reliability
1. If an SMF is faulty, only activated subscribers served by this
SMF are affected, with other SMFs and UPFs operating
normally.
2. If a UPF is faulty, only activated subscribers served by this UPF
are affected, with other UPFs and SMFs operating normally.
UPF UPF UPF UPF UPF  Fewer redundant resources required

The ratio of redundant resources required by the SMF and UPF in a
group is 1/N.
Full meshing between SMFs and UPFs:  Decoupled control-plane and user-plane and elastic scaling
 A UPF can be registered with multiple SMFs, and supports If the number of subscribers increases but the traffic volume does
subscriber activation requests and service processing requests not, only the SMF needs to be scaled out. If the traffic volume
from multiple SMFs. increases but the number of subscribers does not, only the UPF
 One SMF group can manage multiple UPF groups.
needs to be scaled out.
 Each UPF group can be configured with unique service
attributes (such as VoLTE and MBB) or location attributes
(service-specific areas).

Contents
3.1 SBA and NRF
3.2 CUPS
3.4 Network Slicing
3.5 MEC

2G/3G/4G/5G Full Convergence: Core Network Convergence Reduces
Investment and Smooth Evolution Simplifies O&M
AMF+MME+ SMF+ PCF+ UDM+HS

SGSN GW-C PCRF S+HLR
UPF+
GW-U
VO SA URL Filter
Service Governance
Firewall TCP Acc. Cache Web Acc.

NEF AUSF AF NRF
Converged control plane Unified user plane

eLTE eNodeB eLTE eNodeB
2G/3G eNodeB NR NR&eNodeB Fixed
&NR &NR
Option 3 Option 2 Option 4 Option 7
Mobility management 1 2 3 4 User plane convergence 5

convergence Session management User data convergence
(AMF+MME) convergence Policy convergence (UDM+HSS) (UPF+GW-U)
(SMF+GW-C) (PCF+PCRF)
Reduced signaling overheads Unchanged SIM card Unchanged IP address and
Unified 4G/5G policy uninterrupted data
Consistent experience and MSISDN
management

2G/3G/4G/5G Full Convergence – AMF/MME/SGSN Convergence
Solution
UNC (AMF/MME/SGSN) Solution overview

 Support of 2G/3G/4G/5G/non-3GPP (to be planned)/fixed (to be planned) all-RAT
CSDB access
 Sharing of OM/CSDB/CSLB/LINK microservices in a variety of RAT access modes
 Separation of processing logic between 5G and 2G/3G/4G services
2/3/4G-AM 5G-AM
 Deployment of 5G service processing logic and 2G/3G/4G service processing logic on
OM the same VM, sharing VM-level resources
Solution competitiveness
GB LINK  Unified O&M experience in various RAT access modes
 Sharing of data services in various RAT access modes
CSLB  Separation between the interface processing layer and service logic processing layer,
decoupling link management from service logic processing, and supporting
independent upgrades and elastic scaling
 The 5G service logic and 2G/3G/4G service logic are decoupled and deployed on the
CN same VM. In this way, resources can be adaptive between different RATs, and
RAN
independent upgrades can be supported.
 You can perform orchestration based on service requirements and deploy services of
2G/3G eNodeB gNR Fixed different RATs as required. If GB interface processing is not required, you do not need
to deploy GB microservices.

2G/3G/4G/5G Full Convergence – SMF/GW-C Convergence Solution
UNC (SMF/PGW-C/SGW-C/GGSN-C)
Solution overview
 2G/3G/4G/5G/non-3GPP (to be planned)/fixed (to be planned) all-RAT access is
CSDB supported.
 The data in various RAT access modes is converged to support the anchor function of
interworking services.
SM CM  5G UEs access 2G/3G/4G/5G networks over the N40/N7 interface.
OM  4G UEs access 2G/3G/4G networks over the Ga/Gy/Gx interface.
PCC INTF
Benefits
 Unified O&M experience in various RAT access modes
CSLB  The service processing logic is converged and session context data is converged in
various RAT access modes, ensuring the continuity of interworking services between
different RAT access modes.
 Orchestration can be performed based on service requirements, and services of different
N4/Sx RAT access modes can be deployed on demand. If 4G UE access is not supported, there
is no need to deploy 2G/3G/4G charging and policy management.
Gn/S11/S5-S/S5-P/S8-S/S8-P/N11 UDG

2G/3G/4G/5G Full Convergence – UPF/GW-U Convergence Solution
UDG (UPF/GW-U) Solution overview

 Support for 2G/3G/4G/5G user plane processing
CSDB  Sharing of OM/CSDB/CSLB/LINK microservices in a variety of RAT
access modes
UP-C UP-U
OM Solution competitiveness
 Unified O&M experience in various RAT access modes
SEC  Sharing of data services in various RAT access modes
 Separation between the interface processing layer and service logic
processing layer, decoupling link management from service logic
CSLB
processing, and supporting independent upgrades and elastic scaling
 Atomic-level convergence of 2G/3G/4G/5G user plane processing,
providing optimal forwarding efficiency
AN DN PCRF SMF

2G/3G/4G/5G Full Convergence – PCF/PCRF Convergence Solution
UPCF (PCF/PCRF) Solution overview

 Support for 2G/3G/4G/5G/IMS multi-domain service, data, billing, and
CloudDB dynamic resource convergence
 Sharing of the OM/CloudDB/CSLB microservice in multiple domains
 Convergence of 2G/3G/4G/5G/IMS service processing logic, implementing
PES PAS DBS NCS unified VM types and improving system integration
OM
DLB HLB Solution competitiveness

 Smooth evolution from PCRF to PCF
 Unified O&M experience
CSLB  Sharing of unified data services
 All SBA, supporting on-demand deployment, single service upgrade, as
well as A/B testing and auto scaling of containers in seconds
 2G/3G/4G/5G/IMS multi-domain collaborative flow control and associated
switching
GGSN P-GW AMF SMF

2G/3G/4G/5G Full Convergence – UDM/HSS/HLR Convergence
Solution
UDM (UDM/AUSF/HSS/HLR) Solution overview
 Support for 2G/3G/4G/5G/IMS multi-domain service, data, billing, and dynamic
CloudDB resource convergence
 Sharing of the OM/CloudDB/CSLB microservice in multiple domains
 Separation between 5G service processing logic and 2G/3G/4G/IMS service
CCU UDM NRF processing logic, decoupling service logic
AUSF
Client  Deployment of 5G service processing logic and 2G/3G/4G/IMS service processing
OM logic on the same VM, sharing VM-level resources
BSG HSF HLB

Solution competitiveness
 Smooth evolution from HSS to UDM
 Unified O&M experience
CSLB
 Sharing of unified data services
 Separation between the interface processing layer and service logic processing
layer, decoupling link management from service logic processing, and supporting
independent upgrades and elastic scaling
 The 5G service logic and 2G/3G/4G/IMS service logic are decoupled and deployed
on the same VM. In this way, resources can be adaptive between different domains,
MME MSC/VLR AMF SMF
and independent upgrades can be supported.
 2G/3G/4G/5G/IMS multi-domain collaborative flow control and associated
switching

2/3/4/5G Full Convergence – Benefits
U2020 HLR/HSS/UDM U2020 HLR/HSS/UDM
OM
N8
OM Gr/S6a/N8 Gr/S6a
UNC (AMF/MME/SGSN) converged node UNC (MME/SGSN) independent node UNC (AMF) independent node
CSDB CSDB CSDB
Legacy AM 5G AM
vs
Legacy AM 5G AM
OM
OM
OM
GB LINK GB LINK LINK
N26
CSLB CSLB CSLB
CN
RAN
2G/3G eNodeB gNR Fixed 2G/3G eNodeB gNR Fixed
Inter-RAT handover Inter-RAT handover
User Management Resource Usage Service Switchover Device O&M
Unified access to the provisioning system,

Fewer O&M nodes are required and routine
automatic migration of subscribers who have Public services (such as OM, CSDB, Internal interfaces S10 and N26 are
operations are simple.
subscribed to 5G services to 5G devices, and and CSLB) can be shared, and the provided to reduce the number of handover
Subscribers reside on the same device,
"unchanged SIM card and MSISDN" are overall resource usage is high. signaling messages and handover delay.
simplifying troubleshooting.
supported.
External interfaces S10 and N26 are More O&M nodes are required and routine
The function of "unchanged SIM card and Each non-converged NF has its own
provided. The numbers of handover operations are complex.
MSISDN" is not supported. public services. The overall resource
signaling messages and tests increase, Subscribers reside on multiple devices,
usage is low.
affecting KPIs. resulting in difficult troubleshooting.
The core value of convergence is to improve resource utilization, reduce O&M costs, reduce signaling overheads, and improve user experience.

Contents
3.1 SBA and NRF
3.2 CUPS
3.4 Network Slicing
3.5 MEC

Network Architecture Defined in 3GPP – Network Slicing
Network slicing divides a physical network into multiple virtual logical networks, each corresponding to a specific scenario.

Network Slicing – Flexible Deployment
SMF UPF
AMF Slice 1
UDM PCF Slice 2
Common large network slice Industry with aggressive isolation requirements

Industry with moderate
isolation requirements
Different slice instances share an NF. Different slice instances exclusively use their own VNFs but share a Different slice instances exclusively use their own VNFs and
host group. host groups.
Slice 1 Slice 2 Slice 1 Slice 2

SMF UPF
Slice 1
AMF UDM PCF AMF SMF AMF SMF AMF SMF
AMF SMF
UDM PCF UDM PCF UDM PCF UDM PCF
SMF UPF Host group 1 Host group 1 Host group 2
UDM PCF Slice 2
NFVI layer NFVI layer
 Network slice instances include standard 3GPP logical NFs such as the AMF, SMF, UPF, UDM, PCF, NRF, and NSSF.
 Whether AMF network slices are shared or deployed independently is determined based on service planning and isolation requirements.
 SMF and UPF network slice instances are deployed independently.
 It is recommended that the PCF and UDM share network slices. In scenarios featuring high requirements on service isolation (such as key
industries and separation of people and things), network slices can be deployed independently.

Network Slicing – Slice Selection Process
NSSF
UE attach scenario 2 If the default AMF cannot provide services for the
subscriber,
4
The RAN selects an obtain information about the serving slice.
AMF (Allowed-NSSAI, Target AMF) Note:
1 or connects the default  Network Slice Selection Assistance Information (NSSAI)
AMF Default
AMF contains a maximum of eight S-NSSAIs.
Attach request Obtain user subscription information.
 Single Network Slice Selection Assistance Information (S-
(Requested-NSSAI) 3 (Subscribed-NSSAI)
5 Common NSSAI) identifies a slice. An S-NSSAI is comprised of a
Reroute to the target AMF. slice/service type (SST) and a slice differentiator (SD).
RAN
RAN (Allowed-NSSAI)  Network slice selection policy (NSSP) is used by the UE to
UDM PCF
associate the app ID with the S-NSSAI.
7
The attach procedure is successful. Obtain subscription information and

(Allowed-NSSAI, NSSP) 6 policies.
Target (NSSP)
AMF
Slice 1
Session establishment Obtain service slice information based on information such Flexible slice selection capabilities:
1
scenario NSSF 2 as S-NSSAI.
PDU session establishment (NRF IP, NSI ID)
 AMF rerouting and is independent of the RAN.
(S-NSSAI)
 Slice selection in standard mode (S-NSSAI).
 Slice selection in enhanced mode (mapping policies
between number segments, DNNs, and slices are
RAN
RAN AMF SMF UPF
configured), which is applicable to scenarios where early
Slice 1 peripheral standards are not fully supported.
Default
Common AMF
 Flexible NSSF deployment.
3
The SMF serving the slice has

completed session establishment. SMF UPF
Slice 2

Contents
3.1 SBA and NRF
3.2 CUPS
3.4 Network Slicing
3.5 MEC

MEC Solution Architecture
Central site:
MEC Platform Architecture and Deployment Location 1.MEAO/MEPM: provides MEC service
orchestration and life cycle management.
2.Core CP: functions as a control-plane NF
API
API GW
GW of the 5G core network.
VNFM /
GW-U
UPF
Agent
LB
Edge DC:
DNS NEF
App App VAS 1.UPF: functions as a 5GC user-plane NF
MEAO/
Central
MEPM
VNFM
Central
VNFM
U2020
U2020
MEP deployed at the edge.
Storage Core 2.MEP: functions as an MEC platform,
Container
Container Container
Container Container/VM
Container/VM VM
VM VM
VM CP which provides service registration,
discovery, deregistration, and platform
MEC IaaS
VIM Central DC NFVI capability exposure.
3.MEP preconfigured capabilities: DNS/LB,
MEC hardware
NAT/FW, IPsec, and capability exposure
API.
4.App: works as an edge application
developed by OTT vendors and integrated
on the MEP platform, such as V2X server,
Center DC CDN, and AR/VR.
MEC 5.Hardware acceleration: heterogeneous
hardware platform and dedicated hardware
capabilities such as GPU, encryption and
decryption, and AI.
MEC
MEP supports co-deployment of VMs and containers.

Key MEC Technology: UL CL Traffic Steering
Uplink traffic steering process of the UL CL UPF Downlink traffic aggregation process of the UL CL UPF
The UL CL UPF functions as a traffic classifier for IPv4 and IPv6 packets sent Downlink packets in response to the uplink packets steered to the local DNs are
by the (R)AN over the N3 interface through the uplink GTP tunnel. It matches transmitted to the PSA2 UPF, along the route advertised by the NAT server or
these packets with Layer 3/Layer 4 rules according to the IP addresses and through the tunnel over the N6 interface. The PSA2 UPF encapsulates these
ports, or Layer 7 rules according to the domain names. If a packet matches a downlink packets using GTP and sends them to the UL CL UPF.
rule, the UL CL UPF forwards the packet to the PSA2 UPF over the N9 Downlink packets in response to the uplink packets routed to the central DN are
interface (the UL CL UPF and PSA2 UPF are co-deployed currently), and then transmitted to the PSA1 UPF along the route advertised by the NAT server. The
to the local DN over the N6 interface. If a packet fails to match any rules, the PSA1 UPF encapsulates these downlink packets using GTP over the N9 interface
UL CL UPF forwards the packet to the PSA1 UPF over the N9 interface, and and sends them to the UL CL UPF.
then to the central DN (generally the Internet) over the N6 interface. The UL CL UPF aggregates the downlink packets from both PSA1 UPF and PSA2
UPF, encapsulates the packets using GTP over the N3 interface, and then sends them
to the (R)AN.

APPD
Key MEC Technology: App On-boarding 1) App basic information:
AppVendor: Huawei
APPType: xxx
APPVersion: 1.0
…
0 App package 2) App resource template
(APPD+App
image)
vCPU: 4vCPU
1 mem: 200M
…
3) App configuration plan:
Vendor management plane DNS: xxx;
Central trafficRule: xxx
2 MEAO …
MEPM
3 Procedure
Procedure
0
SMF 4 ••The
The operator
operator imports
imports the
the app
app package
package to
to the
the MEAO
MEAO on
on the
the vendor's
vendor's
5 1
management
management plane.
plane.
••The
The operator
operator issues
issues the
the app
app on-boarding
on-boarding request
request with
with the
the target
target edge
edge
2 specified.
site
site specified.
••MEAO
MEAO parses
parses the
the app
app package
package toto obtain
obtain the
the APPD
APPD and
and app
app image.
image.
App App App
Edge UPF 3
••MEAO
MEAO uploads
uploads the
the app
app image
image to
to the
the lightweight
lightweight VIM.
VIM.
MEP
6
4
••MEAO
MEAO triggers
triggers on-boarding
on-boarding via
via MEPM.
MEPM.
Lightweight VIM ••MEAO
MEAO issues
issues the
the service
service configurations
configurations of
of the
the app
app via
via MEPM.
5 MEPM.
Hardware ••MEP
MEP synchronizes
synchronizes traffic
traffic steering
steering rules
rules to
to the
the UPF.
UPF.
6

Key MEC Technology: Synchronization of Traffic Steering Rules for Apps
Management plane 5G Core 21.1 supports:
•Manual configuration of traffic steering rules for apps
•Dynamic delivery of the configured rules via the Mm5 interface
•Automatic synchronization of the configured rules to the UPF
AMF SMF UPF PSA 0 Configuration procedure:
1.Configure the Mp1 and Mm5 interfaces on the UEG. The IP address
Internet of the Mp1 interface is the same as that of the API GW, and that of the
Mm5 interface is the same as that of the OM interface.
N9 2.Configure service IP addresses for apps, including the IP address of
N4
the Mp1 interface on the UEG.
3.Enable the apps to register with the MEP through the Mp1 interface.
N6 The MEP allows the apps to subscribe to services and pushes services
N3
UL CL+PSA 1 MEP App App to the apps.
Container
Local DN 4.Add traffic steering rules (based on domain names or app IDs) for
UE RAN VM apps on the UEG, and add DNS traffic steering rules.
FusionStage
5.On all the SMFs interworked with the UEG, add app IDs for the
FusionSphere corresponding locations. The traffic for new sessions at the network
E9000H-4 x86/Arm edge can be steered based on the app IDs.
Edge site
6.After being on-boarded, apps invoke the Mp1 interface to activate the
traffic rules on the UEG and the DNS traffic steering rules.
Apps are deployed at the network edge, where all-in-one
UPFs are used.

Summary
5G Core Solution Key Features
3.1 SBA and NRF

3.4 Network Slicing
 Supports standard SBA capabilities.
 Deployment modes with different isolation
 Provide further optimization capabilities. levels
3.2 CUPS  Flexible slice selection

 After the CUPS, the user plane is deployed at the network edge. 3.5 MEC
 CUPS full meshing  LBO
 Centralized CU configuration simplifies O&M.  APP Integration

 Unified O&M
 Service sharing for reducing costs
 Reduced signaling overheads

Q&A
1. Question 1: Compared with the NFV architecture, what features does the 5G Core solution
have to further decouple and agile the system?
2. Question 2: Is it better to split microservices into smaller ones?

Q&A
3. Question 3: The SBA transforms the point-to-point connected network into a service-oriented
bus connection. Is there any substantial change in functions except for the form change?
4. Question 4: In the 5G Core solution, CU full meshing means that the SMF and UPF are fully
meshed separately.

Q&A
5. Question 5: What are the advantages of the fully converged architecture used by the 5GC?
6. Question 6: What functions can be provided by the MEC platform?
7. Question 7: Different slices must exclusively use their own NFs and be deployed in independent VNFs.

Thank You
www.huawei.com

5G Core 21.1 Solution Overview ISSUE 2.0

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

5G Core 21.1 Solution Overview ISSUE 2.0

Uploaded by

Copyright:

Available Formats

5G Core Solution Overview

Copyright © 2020, Huawei Technologies Co., Ltd. All rights reserved.

 Upon completion of this course, you will be familiar with:

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 3

1. 5G Core Solution Overview

2. 5G Core Solution Overall Architecture

3. 5G Core Solution Key Features

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 4

1. 5G Core Solution Overview

1.1 Industry Requirements on 5G Core Networks

1.2 Network Architecture Defined in 3GPP

1.3 5G Core Solution Composition

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 5

V2X High reliability: 99.999%

1 ms 0.5 ms 0.1 ms 1 ms 0.1 ms 0.5 ms 1 ms 3D video, UHD screen

Smart home and office

IoT Low power consumption: 10+ years' battery life

NB-IoT NB-IoT NB-IoT NB-IoT

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 6

10 Gbit/s  Service Based Architecture (SBA)

Smart home and office AR/VR

Industrial automation  2G/3G/4G/5G full convergence, co-deployment and co-

Superscale sensor Extreme

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 7

1. 5G Core Solution Overview

1.1 Industry Requirements on 5G Core Networks

1.2 Network Architecture Defined in 3GPP

1.3 5G Core Solution Composition

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 8

Nausf Namf Nsmf

4G architecture (non-roaming) 5G non-roaming architecture (SBA)

5G key technologies and capabilities

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 9

Provides functions such as session management, IP address allocation and management,

Provides subscriber data management functions, such as authentication, identification,

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 10

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 11

 Combined HSS and UDM

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 12

NRF: 1. I-SMF/A-SMF selection process adaptation

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 13

1. 5G Core Solution Overview

1.1 Industry Requirements on 5G Core Networks

1.2 Network Architecture Defined in 3GPP

1.3 5G Core Solution Composition

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 14

 The 5G Core solution provides NFs, including the UNC, UDG,

 Based on the NFV architecture, the 5G Core solution provides

Cloud OS (FusionSphere, etc.)

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 15

Component Huawei Product Function

OSS IES Provides the service provider (SP) management function.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 16

MEC system level

MEC host level

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 17

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 18

1. 5G Core Solution Overview

2. 5G Core Solution Overall Architecture

3. 5G Core Solution Key Features

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 19

2. 5G Core Solution Overall Architecture

2.1 Cloud and Microservice-based NFV Architecture

2.2 Converged Architecture