Professional Documents
Culture Documents
5G Core Network
5G Core Network
5G Core
Acronyms & Abbreviations
Numeric
5GC 5G Core Network
A-C I-M
ABMF Account Balance Management I-CSCF Interrogating-Call Session
Function Control Function
AF Application Function ISTP International Signaling Transfer
AIOps Artificial Intelligence for IT Point
Operations K8s Kubernetes
AMF Access and Mobility LBO Local Breakout
Management Function LCM Life Cycle Management
APN Access Point Name L-NRF Low-level NRF
AS Application Server LSMS Local Service Management
ATS Advanced Telephony Server System
AUSF Authentication Server Function MAE MBB Automation Engine
BSF Binding Support Function MEC Multi-access Edge Computing
CBC Content-based Charging MME Mobility Management Entity
CC Charging Characteristic MO Mobile Originated
CCS Converged Charging System MSISDN Mobile Station International
CDF Charging Data Function ISDN Number
CDR Charging Detail Record
CGF Charging Gateway Function
CHF Charging Function
CHR Charging History Record
D-H N-O
DEA Diameter Edge Agent NEF Network Exposure Function
DNN Data Network Name NFV Network Functions Virtualization
DRA Diameter Routing Agent Network Functions Virtualization
NFVO
EPS FB EPS Fallback Orchestrator
FBC Flow-based Charging Number Portability
NPAC
Administration Center
FCAPS Fault, Configuration, Accounting,
Performance, Security NRF Network Repository Function
FQDN Fully Qualified Domain Name NS Network Service
F-TEID Fully Qualified Tunnel Endpoint NSD Network Service Descriptor
Identifier Network Slice Management
NSMF
GMLC Gateway Mobile Location Center Function
GPSI Generic Public Subscription Network Slice Selection
NSSAI
Identifier Assistance Information
GUAMI Globally Unique AMF Identifier NSSF Network Slice Selection Function
GUMMEI Globally Unique MME Identifier Network Slice Subnet
NSSMF
Management Function
HA High Availability
NSST Network Slice Subnet Template
HLR Home Location Register
OCF Online Charging Function
H-NRF High-level NRF
OCS Online Charging System
HSS Home Subscriber Server
Acronyms & Abbreviations
P-R U-Z
Policy and Charging Enforcement UDM Unified Data Management
PCEF
Function
UDR User Data Repository
PCF Policy Control Function
Unified Policy and Charging
Policy and Charging Rules UPCC
PCRF Controller
Function
Unified Policy Control
Proxy-Call Session Control UPCF
P-CSCF Function
Function
UPF User Plane Function
PDN Packet Data Network
Ultra-reliable Low-latency
PDU Packet Data Unit URLLC
Communication
PE Provider Edge Universal Subscriber Identity
USIM
P-GW PDN Gateway Module
PNF Physical Network Function UTA UDM Translation Agent
RF Rating Function Virtualized Infrastructure
VIM
RG Rating Group Manager
ROI Return on Investment VNFD VNF Descriptor
S-T
SBA Service Based Architecture
SBI Service-based Interface
SCP Service Communication Proxy
Serving-Call Session Control
S-CSCF
Function
SDN Software-Defined Networking
SEPP Security Edge Protection Proxy
SGSN Serving GPRS Support Node
S-GW Serving Gateway
SMF Session Management Function
SMSF SMS Function
SPR Subscription Profile Repository
Signaling Service Processing
SPS
System
STP Signaling Transfer Point
SUCI Subscription Concealed Identifier
SUPI Subscription Permanent Identifier
SVC Single Voice Core
TAI Tracking Area Identity
TAU Tracking Area Update
Telecommunications
TMN
Management Network
Topology and Orchestration
TOSCA Specification for Cloud
Applications
Contents
01 Deployment 1
02 Redundancy 9
03 4G-5G Interworking 19
5G Core 04 Vo5G 26
06 Charging 36
07 Signaling 41
09 Overview 54
10 VNF LCM 57
iMaster
MAE-CN
11 NFVO 59
14 O&M Solution 64
Three-Layer Architecture
A three-layer network architecture is used for 5GC deployment — the central DC deployed with
control plane NFs, the regional DC with the user plane, and the edge DC with the MEC and CDN.
A fully convergent 5GC cannot be built overnight. In the early phase of deployment, we usually
build a new 5GC and enable it to communicate with the existing EPC, with new MMEs/AMFs
pooled with the existing MMEs, or just upgrading the existing MMEs.
In addition, active-active, active/standby, and pool-based redundancy is applied for 5GC NFs to
maintain the highest possible security and reliability.
New 5GC
Existing EPC
DC 1 DC 2
Active-active
NRF NRF
Active-active
NSSF NSSF
HSS
IWF/Hybrid networking Active/standby
IWF/UDM/HSS IWF/UDM/HSS
PCRF Hybrid networking Active/standby
PCF/PCRF PCF/PCRF
Active-active
S/P-GW S/P-GW SCP/BSF SCP/BSF
Pool
N26-based interworking AMF AMF
Pool
MME+ MME+ SMF/PGW-C SMF/PGW-C
Regional
Full Mesh
Full mesh Full mesh Full mesh
User
plane
UPF/PGW-U UPF/PGW-U UPF/PGW-U
UPF/PGW-U UPF/PGW-U UPF/PGW-U
The UPF and PGW-U are
co-located for smooth
4G-5G interworking.
Edge
Full mesh Full mesh Full mesh
MEC/CDN
CDN
01
Deployment
NRF 1
NRF 1 NRF 3
AMF SMF UDM PCF NSSF AMF SMF UDM PCF NSSF AMF SMF UDM PCF NSSF
AMF SMF UDM PCF NSSF AMF SMF UDM PCF NSSF AMF SMF UDM PCF NSSF AMF SMF UDM PCF NSSF
L-NRF: An NRF at the lowest level of hierarchy. It manages the NFs in its home area.
PLMN-NRF: An NRF at the highest level of hierarchy. It can be deployed separately or co-
deployed with a group NRF to accommodate international roaming in the future. The group
NRF can be an H-NRF, L-NRF, or PLMN-NRF.
SEPP: It is part of the roaming security architecture and used to safeguard control plane
signaling interaction between 5G PLMNs.
02
Deployment
NSSF 1
NSSF 2
Area 1 Area 2
NSSF 1 NSSF 3
NSSF 2 NSSF 4
AMF set 1 AMF set 2 AMF set 3 AMF set 4 AMF set 5 AMF set 6 AMF set 7 AMF set 8
AMF AMF AMF AMF AMF AMF AMF AMF
AMF AMF AMF AMF AMF AMF AMF AMF AMF AMF AMF AMF AMF AMF AMF AMF
03
Deployment
A fully convergent 5G core network cannot be built overnight. In the initial construction phase, 5G
core networks will coexist with existing EPC networks.
Solution 1: Build a 5GC and interwork it with the EPC, without deploying new MMEs.
MME MME
Deploy a cloud-based 5GC with pool-based
AMF AMF redundancy.
Upgrade the existing MMEs to support the N26
interface and select convergent gateways,
maintaining service continuity.
SMF/GW-C
Highlight
SMF/GW-C
Solution 2: Build a 5GC and interwork it with the EPC, with new MMEs/AMFs pooled with the
existing MMEs.
.
Network Deployment
Deploy a cloud-based 5GC with pool-based
MME MME MME/AMF MME/AMF
redundancy.
Configure the new AMFs/MMEs and the existing
MMEs as a hybrid pool.
Highlight
SMF/
SMF/ GW-C Service requests from 5G UEs are anchored to the
GW-C convergent 4G/5G network, reducing interactions
across nodes and improving the service experience.
UPF/
S-GW/P-GW
GW-U
Weakness
UPF/ Service requests from the 4G-only UEs are also
GW-U
processed by the convergent 4G/5G network.
Consequently, existing MMEs are not used
efficiently.
eNodeB gNodeB The existing MMEs must be upgraded to select
EPC
New deployment convergent gateways, increasing network
deployment costs.
Option 2
5G UE
04
Deployment
Hybrid Network
Final evolution
Hybrid
HSS-BE HSS-BE network UDR UDR
UTA it to 5G data to
HSS-BE HSS-BE HSS-BE HSS-BE
provide 5G services.
HSS-FE UTA
HSS-FE HSS-FE HSS-FE HSS-FE
HSS UDM (Subscriber migration for HSS UTA (Transitional solution for
5G service provisioning) 5G service provisioning)
05
Deployment
Live 4G network
Provisioning system
Pool 1
SPR SPR
DRA
P-CSCF PCEF
06
Deployment
Region A Region B
CHF
PCF UDM
UDM PCF
AUSF PCF
AUSF UDM
UDM CHF
PCF
NRF NRF
SMF
AMF AMF
SMF AMF
SMF SMF
AMF
HPLMN VPLMN
Region A Region B
NRF SCP/BSF
LSCP LSCP
SCP/BSF NRF SEPP SEPP
07
Deployment
The 5GC user plane (UPFs) can be deployed in central, regional, or edge DCs, depending on service
latency and coverage requirements for different scenarios.
While being fully meshed with their serving SMFs through an IP transport network, the UPFs are
also pooled across DCs for redundancy, so that a faulty UPF does not affect the others. UPFs are
deployed depending on the following service types:
B2C services
UPFs are deployed in regional DCs to shorten the RTT and improve service experience.
B2B services
UPFs are deployed in edge or regional DCs to optimize traffic paths and reduce transmission
resource waste:
Edge DC deployment: It is recommended for security- or latency-sensitive applications, such as
industrial control and AR/VR-based live broadcast.
Regional DC deployment: It accommodates enterprise campus applications, where the UPFs
can be shared for Internet services or across campuses to improve resource utilization.
UPFs in a Central DC
B2C services
AMF/SMF/NRF/SMSF/UDM/PCF/CHF/...
The UPFs provide access to the
Internet.
Central DC
UPFs in a Regional DC
Internet Internet
B2C services
The UPFs transmit massive 5G data
UPF/GW-U
UPF/GW-U UPF/GW-U
UPF/GW-U with shorter latency to improve the
experience for Internet subscribers.
B2B services
The UPFs allow enterprise
subscribers to access a local DN.
The UPFs can also be shared across
Regional DC campus networks to offload local
services for multiple enterprises.
08
Redundancy
Challenges
As 5G drives new services, such as IoT, V2X, and VR, it puts more pressure on networks. These
services demand networks that can process massive data and online services anytime, anywhere.
Furthermore, service continuity and resilience are becoming more important than ever with the
increasing use of mobile services by both enterprises and individuals. However, the cloud-based NFs
are not as robust as traditional NEs due to changes in the network architecture – COTS hardware
and a virtualization layer are introduced. As such, ensuring service availability on 5GC NFs is urgent
and more difficult than on traditional NEs.
The 5GC redundancy solution addresses these challenges by deploying NFs as active/standby pairs,
active-active pairs, or pools across DCs at different locations.
Redundancy Networking
5GC cross-DC redundancy networking encompasses both cloud-based NFs and traditional NEs,
including the NSSF, NRF, convergent PCF/PCRF, convergent AUSF/HLR/HSS/UDM, IWF, SMSF,
convergent SMF/PGW-C, AMF, and convergent UPF/PGW-U.
Control-plane NFs are deployed in the central area, and user-plane NFs are placed at different
distances to users, meeting bandwidth and latency requirements at different levels. For example,
the convergent UPF/PGW-U can be deployed in a regional DC for Internet access, and it can also
be positioned closer to users, such as at the network edge to facilitate access to campus networks.
DC 1 Redundancy DC 2
Network Active-active or
management NSSF NRF active/standby
NSSF NRF
AUSF/HLR/ PCF/PCRF
AUSF/HLR/
PCF/PCRF HSS/UDM HSS/UDM
Active-active or
FE FE active/standby FE FE
Data/policy Active/standby
BE BE BE BE
SMS
SMSF Active-active SMSF
forwarding
Regional
Edge
Pool
gNodeB gNodeB UPF/ UPF/
PGW-U PGW-U
gNodeB
09
Redundancy
Redundancy Approaches
The 5GC can apply active/standby, active-active, or pool-based redundancy.
Networking
Active/Standby
Two NFs are deployed in separate DCs as
DC 1 DC 2 an active/standby pair. As always, only the
active NF processes services, with the
standby NF available as a backup.
The two NFs exchange heartbeat
NF 1 NF 2 messages to check each other's status, and
(Active) (Standby) synchronize data to maintain consistency.
If the active NF is faulty, the standby NF
takes over services.
Typical NFs
NRF, NSSF, UDM, and UPCF
Networking
Active-Active
Two NFs are deployed in separate DCs as
DC 1 DC 2 an active-active pair. As always, both NFs
process services.
Some NFs back up data with their paired
NFs, while some do not. If one NF is faulty,
NF 1 NF 2 the other NF takes over services.
(Active) (Active)
Typical NFs
NRF, NSSF, SMSF, UDM, and UPCF (the
SMSF does not back up data with the
paired SMSF)
Networking
Pool
NFs are pooled. When operational, all NFs
DC 1 DC 2 process services.
If an NF is faulty, other NFs take over
services.
Typical NFs
NF 1 … NF 2 NF 3 … NF 4
(Active) (Active) (Active) (Active) AMF, SMF, and UPF
10
Redundancy
NFs periodically check the status of links to their peers. If a link is faulty, services will be switched
to other operational NFs. The 5GC uses two types of interfaces — SBIs and traditional point-to-
point interfaces — over which different communication protocols and link status check
mechanisms are used.
HTTP is used over SBIs. The NFs check the status of links over SBIs via ping or subscription
notifications from the NRFs.
The NRFs exchange PATCH heartbeat messages with their served NFs to check their status. If
an NF is faulty, its NRF will set it to the SUSPENDED state and notify other NFs, which have
subscribed to the status of this NF. The other NFs determine whether to switch services to
operational NFs according to preset policies.
The SCTP, PFCP, GTP-U, ICMP are applied over traditional interfaces. The NFs check their link
status through heartbeat messages over SCTP associations or PFCP links, with an echo
request, or via server polling on the IP farm.
SBIs
PATCH
heartbeat
Subscription
Ping Ping Ping Ping Ping notification
Ping
Ping
Traditional
Interfaces
PFCP
SCTP
heartbeat
Echo UPF
11
Redundancy
The AMFs are pooled to provide redundancy. The pooled AMFs are fully meshed with gNodeBs
and control-plane NFs, efficiently preventing single points of failure. If an AMF is faulty, its
connected NFs will switch services to other operational AMFs.
DC 1 DC 2
1
AMF 1 AMF n AMF Pool AMF 1a AMF na
… …
12
Redundancy
An SMF pool consists of multiple SMFs that serve one radio area and are fully meshed with all
subordinate UPFs. SMF and UPF full mesh networking is also called CU full mesh networking,
which ensures that other NFs remain operational if one SMF or UPF becomes faulty.
Central DC
1
SMF 1 SMF 2 SMF 3 SMF 3
2
UPF 1 UPF 2 UPF 3 UPF 4
13
Redundancy
Two active NRFs are deployed across DCs for geographic redundancy. The two NRFs are presented
as two independent NFs with separate identifying information, such as different interface IP
addresses. This allows them to provide services for all other NFs or NFSs in their respective DCs
and to back up data for those in the peer DC. Service links are established between the other NFs,
namely the AMFs and SMFs, and the NRFs in two DCs. If one of the NRFs is faulty, these NFs
select the other NRF to process services, maintaining service continuity.
DC 1 DC 2
PCF 1 … … PCF 2
1 Data synchronization
NRF 1 2 NRF 2
3
4
Fault Peer
Scenario Redundancy Solution
Point NE/NF
The NFs in the same DC as the faulty NRF switch services to the
other NRF.
Control After the faulty NRF recovers, the other NRF backs up all data
1 An NRF is faulty.
plane NFs updates to the recovered NRF in one batch, to ensure that both
of them have the same up-to-date data. Data is synchronized
between the NRFs in real time in subsequent service procedures.
The NRFs process service requests from the NFs in their
The data respective DCs.
synchronization Control After the data synchronization path recovers, all data is
2 path between plane NFs synchronized between the NRFs in one batch to ensure that both
NRFs is faulty. of them have the same up-to-date data. Data is synchronized
between the NRFs in real time in subsequent service procedures.
The service The other NRF continues to process service requests from the
processing path NFs in the same DC as the faulty NRF.
3 between an NF NRF After the service processing path recovers, the NFs determine
and its NRF is whether to switch services back to the original NRF according to
faulty. preset policies.
The NRF sets this NF to the SUSPENDED state.
After the NF recovers, the NRF sets the NF to the REGISTERED
4 An NF is faulty. NRF state, and the NF then continues to provide services as normal.
The NRF notifies the other NFs, that have subscribed to the
status of this NF, of the status change.
14
Redundancy
Two active NSSFs are deployed across DCs for geographic redundancy. The two NSSFs are
presented as two independent NFs with separate identifying information, such as different
interface IP addresses. This allows them to provide services for all AMFs in their respective DCs
and to back up data for those in the peer DC. Service links are established between AMFs and the
NSSFs in two DCs. If one of the NSSFs, for example, the high-priority NSSF, is faulty, the AMFs
detect the fault, and select the other NSSF, for example, the low-priority NSSF, to process services,
maintaining service continuity.
DC 1 DC 2
Data
synchronization
1
NSSF 1 2 NSSF 2
AMF pool
15
Redundancy
Two active SMSFs are deployed across DCs for geographic redundancy. The two SMSFs back each
other up to provide redundancy. When the AMF or STP detects that one SMSF is faulty, it routes
service requests to the other SMSF.
IP-SM
SMSC
-GW
DC 1 DC 2
STP 1 STP 2
UDM 1 UDM 2
Data
1 synchronization
SMSF 1 NRF 1 NRF 2 SMSF 2
AMF 1 AMF 2
16
Redundancy
A UPCF can serve as a convergent PCF/PCRF. Logically, a UPCF consists of an FE and a BE. The FE
processes services, and the BE stores and manages data. It is recommended that FEs and BEs both
work as active/standby pairs.
If the active FE is faulty, the standby FE is selected to process new services. If the active BE is faulty,
the FE accesses the standby BE. Data is synchronized between the active and standby BEs.
Provisioning
system
Data
1 synchronization
BE 1 BE 2
DC 1 DC 2
2
FE 1 FE 2
17
Redundancy
A UDM can serve as the AUSF, UDM, HSS, and HLR. Logically, a UDM consists of an FE and a BE.
The FE processes services, and the BE stores and manages data. It is recommended that FEs and
BEs both work as active/standby pairs.
The active and standby FEs send registration requests to the NRF. The requests carry the SUPI
segment, GPSI segment, and group ID (optional).
Normally, the SMF and AMF discover and access the active FE through the NRF. However, if the
active FE is faulty, the SMF and AMF access the standby FE.
The FE accesses the BE over an internal interface. In most cases, the FE accesses the active BE. If
the active BE is faulty, however, the standby BE takes over data services.
If the standby BE is configured to work as an active BE, it processes all provisioning commands.
If the standby BE is not configured to do so, it processes only modification and query related
provisioning commands.
Provisioning
system
Data
1 synchronization
BE 1 BE 2
DC 1 DC 2
2
FE 1 FE 2
An STP, DRA, After detecting that the STP, DRA, NRF, SMF, or
3 NRF, SMF, or FE AMF is faulty, the FE sends messages to an
AMF is faulty. available STP, DRA, NRF, SMF, or AMF.
18
4G-5G Interworking
Overview
5G networks are gradually built from hotspots to an increasing number of areas. At the initial
stage of 5G network construction, 4G-5G interworking must be supported by both networks and
UEs. This way, when 5G subscribers move to a new area not covered by 5G, they can have
continued access to mobile services.
P-GW
MME pool SMF AMF pool
eNodeB gNodeB
eNodeB eNodeB
UE
UE
UE
4G and 5G networks may need to co-exist for a long time and work together, through inter-RAT
interoperability, to provide a seamless network experience for both existing and new subscribers.
For example, 4G networks feature wide coverage and are still used to carry voice services to
ensure that these services are stable and reliable; 5G networks feature abundant radio resources,
such as high frequency bands, and are used to carry data services to provide high data rates and
large capacity in hotspots. Therefore, 4G-5G interworking is necessary, and even mandatory for
some countries or operators.
4G-5G interworking allows a UE to move between a 5G SA system and 4G EPS. It involves cell
reselection, handover, and redirection on the (R)AN, as well as TAU, handover, and mobility
registration updates on the core network.
19
4G-5G Interworking
Networking
Typical Networking
At the early stage of 5G network deployment, some legacy EPC devices are repurposed through
upgrades or reconstruction to handle the procedures and signaling messages of 4G-5G
interworking.
IMS
EPC 5GC
UDM+HSS
S6a
N8
NRF
PCF+PCRF
Gx N7
S5-C
SMF+PGW-C
SGW N4
N11
S5-U UPF+GW-U
S11
N3
S1-U MME AMF
N26
S1-C N2
eNodeB gNodeB
Xn
LTE area SA area
NE Interworking Requirement
The eNodeB must be upgraded to support 5G neighboring cells/frequencies, handovers to 5G NR, and
eNodeB
EPS fallback.
The MME must be upgraded to support the N26 interface and the selection of a convergent SMF/PGW-C
MME
over the N26 interface.
DRA The DRA server must be upgraded to support the HTTP links destined to an SMF.
IMS The IMS must be upgraded to interwork with the 5GC, and to support 5G-initiated calls and EPS fallback.
The SMF and PGW-C must be integrated to keep the mobility anchor unchanged and to ensure service
SMF+PGW-C
continuity.
The PCF and PCRF must be integrated to centrally manage 4G and 5G subscriber policies, ensuring that
PCF+PCRF
policies are consistent and services run steadily.
The UDM and HSS must be integrated so that the UDM allows 5G subscribers to register with 4G
UDM+HSS
networks, ensuring that subscriber data is consistent.
NRF The convergent SMF/PGW-C must send the PGW-C FQDN when registering with the NRF.
The DNS server must be configured with records relevant to 4G-5G interworking.
For 4G-to-5G handover, the MME uses a 5G TAI to query the DNS server for the target AMF.
For 5G-to-4G TAU, the MME uses a GUAMI to query the DNS server for the original AMF.
page
DNS 02 For 5G-to-4G handover, the AMF uses a 4G TAI to query the DNS server for the target MME.
For 4G-to-5G registration, the AMF uses a 4G GUMMEI to query the DNS server for the source MME.
The MME uses an APN to query the DNS server for the SMF FQDN over the S5 interface, with
Service Parameter set to x-3gpp-pgw:x-s5-gtp+nc-smf.
20
4G-5G Interworking
Networking Diagram
5GS-to-EPS Reselection
DNS NRF
SMF+
Uses the GUMMEI SGW-C
6 PGW-C
to query for the peer AMF
Queries the NRF
3 Requests the SMF 2
for a convergent SMF/PGW-C.
8 Establishes a PDN to establish a
connection. PDU session.
eNodeB gNodeB
Key steps:
1. A UE registers with a 5G network, and sends a message to the AMF to request a PDU session.
2. If the UE supports 4G network access and its subscription data (DNN and NSSAI) indicates
that the UE supports 4G-5G interworking, the AMF queries the NRF for a convergent
SMF/PGW-C.
3. The AMF sends a PDU session establishment request to the SMF, indicating that the DNN
supports 4G-5G interworking. The SMF requires the AMF to allocate a 4G EPS bearer ID to the
PDU session. The SMF then constructs an N1 SM message containing 4G and 5G QoS mapping,
and sends the message to the UE through the AMF.
4. When the UE in idle mode moves from NG-RAN coverage to LTE coverage, it initiates a TAU.
5. The TAU request message carries the 4G-GUTI mapped from the 5G-GUTI and access-layer
signaling also contains the GUMMEI mapped from the 5G-GUTI.
6. The MME uses the GUMMEI to query the DNS server for the original AMF following the
procedure on a 4G network.
7. The MME obtains UE contexts from the AMF, including MM contexts for mobility
management and SM contexts for session management. When the AMF obtains SM contexts
from the SMF, the SMF allocates PGW-C and PGW-U tunnel information to an EPS bearer.
8. The MME then preferentially selects a convergent SGW-C/PGW-C according to the PGW-C
information in SM contexts, and sends a 4G session establishment request message to the
selected SGW-C.
9. The SGW-C selects an SGW-U, and sends their F-TEIDs over the S5/S8-C and S5/S8-U
interfaces to the convergent SMF/PGW-C. The convergent SMF/PGW-C then switches the data
tunnel to the SGW-U.
21
4G-5G Interworking
UDM+HSS
S6a
N8
PCRF
PCF+PCRF
N7
S1-U
N3
MME AMF
N26
S1-C N2
eNodeB gNodeB
Xn
5G UE registered 5G UE registered
on 5G on 5G
22
4G-5G Interworking
A convergent SMF/PGW-C ensures that the MME or AMF always discovers and selects the
specified gateway during 4G-5G handovers. To achieve this, the convergent SMF/PGW-C carries
the PGW-C FQDN when registering with the NRF and its information is also configured on the
DNS server. On this server, the value of Service Parameter contains the "nc-smf" flag, such as "x-
3gpp-pgw:x-s5-gtp+nc-smf".
2
Context transfer The UE is handed over to a 5G
network, and the MME transfers the
PGW-C FQDN of the convergent
SMF/PGW-C to the AMF.
23
4G-5G Interworking
24
4G-5G Interworking
4G and 5G networks use different formats and parameters to represent QoS levels. To provide a
seamless experience for subscribers moving between 4G and 5G networks, it is important to
provide them with consistent QoS levels. For this to happen, the convergent SMF/PGW-C must be
able to correctly map between 4G and 5G QoS levels. QoS levels are mapped either during 5G
PDU session establishment or 4G EPS bearer establishment.
GFBR GBR
If multiple QoS flows are mapped to one EPS bearer,
the GFBR is mapped to the GBR based on SMF
configurations. For example, the GBR is equal to the
highest GFBR in QoS flows.
If one QoS flow is mapped to one EPS bearer, one GFBR
is also mapped to one GBR.
MFBR MBR
If multiple QoS flows are mapped to one EPS bearer,
the GFBR is mapped to the GBR based on SMF
configurations. For example, the GBR is equal to the
highest MFBR in QoS flows.
Session AMBR APN AMBR One-to-one mapping
UE AMBR UE AMBR One-to-one mapping
This parameter defines the time window for calculating the
Average Window N/A GFBR/MFBR. It is used only for GBR QoS flows and can be
ignored on 4G networks.
25
Vo5G
Though the rise of 5G networks gives impetus to elevated data traffic, voice services are still the
pillar of telecom networks. Operators tend to agree that voice services should be provided through
the IMS in the 5G era. The Vo5G solution is conceived based on the preceding consensus. This
solution consists of the following subsets:
• VoNR: Applied when subscribers access the 5GC through 5G NR that supports voice services.
• EPS FB: Applied when subscribers access the 5GC through 5G NR that does not support voice
services. Subscribers have to fall back from the 5GC to EPC before using VoLTE services.
Huawei recommends the EPS FB solution for the early stages of 5G and the VoNR solution for an
SA 5GC.
EPS FB: NR does not support voice services. VoNR: NR supports voice services.
(1) The UE sends an INVITE (2) The 5GC triggers EPS FB. The UE sends an INVITE
message through the NR. message through the NR.
Internet
Internet
5GC 5GC
IMS
NR IMS
NR
EPC
EPC Data Data
traffic LTE traffic
(3) The UE accesses the
LTE IMS through EPC. Voice Voice
traffic traffic
In summary, solution 1 uses EPS FB as an interim step and is recommended because deployment is
fast and it maximizes the ROI.
26
Vo5G
EPS FB Network
An EPS FB network consists of the operations support system, NR and LTE networks, IMS, user
database, signaling network, policy control system, EPC, and 5GC.
Database IMS
IMS consists of the P-CSCF, I-CSCF,
S-CSCF, and ATS. The IMS allows
SCC AS/Anchor AS/ registration of 5G subscribers,
AP-AS MMTel AS/IM-SSF obtains 5G location information,
AP/BSF /IP-SM-GW and provides other functions
Sh/Cx/Zh similar to those offered for 4G
subscribers.
DNS/ Zh Sh ISC
ENUM
Rx User database stores 5G
Sh/J subscriber and service data in the
DRA
Cx UDM. The data is used for
selecting a terminating domain
and 4G-5G interworking.
Mp
Cx MRFP
Mw I/S-CSCF
/MRFC Signaling network consists of the
DRA, SCP, and BSF, and NRF. The
DRA/SCP steers received Diameter
N6 signaling to Diameter peers.
UDM
The BSF registers its NF profile with
Rx the NRF and binds UE IP addresses
with PCF IDs.
S6a PCF BSF The NRF functions as a warehouse
A-SBC
/P-CSCF administrator to automatically
/ATCF manage all NFSs, including
/ATGW N7/N15 registration, discovery, and status
N8/N10 detection.
27
Vo5G
Registration
5G subscribers must register with the 5GC and then the IMS before they can use the EPS FB service
and services provided by the IMS, such as IMS calls, SMS, and CRBT.
28
Vo5G
Basic Calls
ATS ATS
UDM UDM
I/S-CSCF I/S-CSCF
SBC/P-CSCF PCF SBC/P-CSCF PCF
The following figure illustrates the message sequence for an MO call during which EPS FB is
performed.
P-GW/
UE NG RAN E-UTRAN AMF MME S-GW PCF IMS
SMF/UPF
2. The AMF sends a request to the NG RAN, instructing it to establish the QoS flow dedicated for the
call. The NG RAN decides to trigger EPS FB and denies the request.[1]
[2]
3. The UE falls back from the 5GC to the EPC.
29
Vo5G
5GC IMS
Signaling
UDM+ ATS/
Media BSF IP-SM-GW
HSS
Configure interworking
between the SBC and PCF.
SMF+ SBC/
AMF PCF S-CSCF
PGW-C P-CSCF
UPF+ Terminating
UE NG RAN MRFP
PGW-U network
Prerequisites:
You have deployed VoLTE and 5GC networks.
The UDM and PCF have been deployed.
The structure and interfaces of the IMS network remain unchanged. Configure the following service
data on the IMS.
NE/NF Configuration
Add data about cells that provide access to 5G subscribers.
Configure policies for searching data tables, setting cell information, PANI
header field in CDRs, and access types in CCR messages.
ATS
Configure special services supported by the ATS during offline charging.
(Optional) Enable T-ADS to provide CS Retry for Vo5G subscribers. This is
recommended.
Configure the UDM to support query for 5G subscriber location and status.
UDM and HSS
Configure the HSS to support 4G-5G interworking.
Add location analysis data on the S-CSCF.
Configure the S-CSCF to determine whether to authenticate subscribers
CSCF based on access types.
Configure registration validity periods for subscribers based on their access
types.
Configure the SBC to allow access from 2G, 3G, 4G, and 5G subscribers.
Configure the SBC to transparently transmit the access network type sent by
SBC
the UE if it fails to obtain the access network type over the Rx interface.
Add mappings between location information and area codes.
Configure the BSF to support the 5G HTTP Signaling Session Binding Standard
BSF
Package feature.
30
Subscriber Migration &
Service Provisioning
When existing networks evolve to 5G, the UDM needs to integrate and manage 2G/3G/4G/5G
subscriber data, while ensuring services. A smooth evolution of existing networks optimizes
operator investment. That's why the UDM provides several 5G evolution solutions. From these,
operators can select the one that is most suitable for their existing services.
Evolution Solutions
Full migration:
All existing Severe impact on
Use the migration The provisioning
A quick increase subscribers can be existing network
tool to batch system only
in the 5G None simultaneously services, and
migrate subscriber connects to the
subscriber base migrated to the 5G massive upfront
data from existing UDR.
network. investment
HSSs to UDMs.
The provisioning
system only needs
Existing HSSs Only slightly affects 2G/3G/4G
to connect and
Hybrid network: must be existing network subscriber data on
deliver the service
Add UDMs to form deployed by services and user existing HSSs
provisioning
a hybrid network Huawei and experience, while needs to be
command to the
with existing HSSs. upgraded to optimizing operator gradually migrated
home UDR based on
HSS 19.1. investment. to UDMs.
the subscriber
number segment.
This solution is
HSS proxy: Add 2G/3G/4G
Requirements similar to the hybrid
UDMs to exchange The provisioning subscriber data on
on the network solution.
signaling with system connects to existing HSSs
provisioning However, it is also
existing HSSs and both the HSS and needs to be
system are suitable for HSSs
provide 5G services UDM. gradually migrated
higher. deployed by other
for subscribers. to UDMs.
vendors.
31
Subscriber Migration & Service Provisioning
Full Migration
Full migration is suitable in areas where 5G UEs have a high penetration rate and the 5G
subscriber base needs to grow quickly. UDMs provide 5G services for subscribers, as well as
integrate and manage 2G/3G/4G/5G subscriber data. All subscriber data on existing HSSs is
exported and converted, and then imported to UDMs.
This solution migrates subscriber data in batches to quickly provision 5G services for subscribers,
allowing existing networks to directly evolve to 5G SA. However, operators need to invest heavily
to build 5G networks for all their subscribers. Also, provisioning services must halt during migration,
and the switch from an HSS to a UDM severely impacts existing network services.
That said, full migration helps to quickly expand the number of 5G subscribers by integrally
managing subscriber data, which allows the UDM to provision both 5G and 2G/3G/4G/IMS services
to subscribers. In addition, subscribers do not need to change their SIM/USIM cards or MSISDNs to
access 5G services.
Hybrid Network
A hybrid network allows for a seamless transition from ATCA-based sites to UDM sites. ATCA-
based sites form a hybrid network with UDM sites, which is then gradually reconstructed into a 5G
network. This solution reduces impacts on the existing network and optimizes operator investment.
Transitional Existing
Target network
Existing network devices
network
Convergent
devices
Provisioning Provisioning Provisioning
System System Peripheral System
devices
Provisioning
command
forwarding
HSS-BE HSS-BE UDR UDR
Hybrid network
32
Subscriber Migration & Service Provisioning
In this case, cloud-based UDM devices form a hybrid network with existing ATCA-based devices,
facilitating a smooth evolution to 5G. Operators enjoy the following advantages:
The provisioning system only connects to a UDM. Remote provisioning sites are deployed to
obtain routing data according to subscriber numbers and forward it to the relevant BE for
processing.
Signaling on a hybrid network can be forwarded between FEs. If subscriber data is available in
the local partition, the FE processes signaling requests locally. Otherwise, the FE forwards
requests to another partition's FE, ensuring service continuity.
Operators can plan 2G/3G/4G to 5G upgrades, since the system can automatically migrate new
5G subscribers or batch migrate existing ones by subscriber number segment.
New 5G subscribers
Provisioning
System 1
1. The provisioning system delivers the subscriber 1. The provisioning system delivers the 4G service
definition command to the home UDR based on parameters to the home UDR based on the
the subscriber number segment. subscriber number segment.
2. The UDR forwards the provisioning command 2. The UDR forwards the provisioning command to
to the BE. the BE.
3. The BE defines 4G subscribers. 3. The BE provisions 4G services.
33
Subscriber Migration & Service Provisioning
UTA
The UTA is ideal for early-stage 5GC. This solution improves user experience and quickly promotes
5G services while maintaining stable 2G/3G/4G services.
VLR/ 2G/3G
SGSN
HSS UTA SMF
4G
MME
Existing
IMS devices
CSCF/AS Convergent NRF
devices
Peripheral
2G/3G/4G/IMS network 5GC network
devices
UTAs help operators seamlessly evolve to 5G. Compared with the hybrid network solution, UTAs:
Are compatible with the third-party HLR/HSS to provision 5G services without migrating
subscriber data or changing their SIM/USIM cards or MSISDNs.
Require few resources during initial small-scale deployment. UDMs can be added as the 5G
subscriber base increases.
Do not affect 4G services on existing devices and maintain a highly reliable network.
UTAs interwork with the existing HLR/HSS to convert authentication and subscription data. They
then provide the 5G authentication and subscription data (still stored on the HSS/HLR) for
subscriber access to the 5G network.
UTAs are a temporary solution, which operators eventually need to replace with UDMs.
HSS/HLR HSS/HLR
(reconstructed) (removed)
All subscribers Migration-
+ +
based
5GC evolution UDM/UDR
34
Subscriber Migration & Service Provisioning
UTAs obtain 4G subscription data from the convergent HLR/HSS over the S6a interface, and
convert it to 5G subscription data according to the locally saved template. There are two types of
subscription data:
Shared 4G/5G data
Basic 5G data
HSS Proxy
This solution is similar to the hybrid network solution. The two main differences are:
The provisioning system needs to interwork with both the HSS and UDM.
The HSS needs to forward signaling data.
Existing
HSS proxy devices
Convergent
devices
Subscribers 5G subscribers
HSS-BE UDR
HSS-FE UDM
35
Charging
Introduction
5G imposes new requirements on how charging is performed and how it interacts with the
network. To address this, 3GPP Release 15 defines a new charging architecture with a new API —
a Converged Charging System (CCS):
The 5G CCS combines the 4G Online Charging System (OCS) and its separate offline charging
system.
The Nchf interface, which is an SBI, replaces the previous Ga and Gy interfaces, to interwork
with 5G NFs.
Bx Bx
Bx
OCS CCS
ABMF RF CGF
ABMF RF
OCF CHF
Offline charging system
CGF
Ga
CDF SBI
4G NEs 5G NFs
The CCS introduces the Charging Function (CHF) to interact with the billing system, over the
existing Bx interface. With the Rating Function (RF), Account Balance Management Function
(ABMF), and Charging Gateway Function (CGF), the CHF can perform both online and offline
charging.
This evolution conforms to the SBA used by 5GC, meeting the requirement of IT system
cloudification and flexible deployment.
In spite of the changes, the purposes of the CCS and traditional online and offline charging
systems are essentially the same, that is, to charge for traffic usage by volume or duration, collect
information such as the RAT, QoS, and URL, and perform credit control for online charging
services, no matter what charging interfaces and functions are used, and where the systems are
deployed.
36
Charging
Charging Network
Network Architecture
N1 N2 N4
N3 N6
UE (R)AN UPF DN
37
Charging
Converged charging is used for a PDU session or a service. Both online charging with quota
management and offline charging without quota management can be provided.
QoS flow Different QoS flows use different RGs for roaming subscribers.
38
Charging
CHF Selection
When multiple CHFs are deployed, the SMF selects a CHF using approach 1, 2, 3, or 4, as
illustrated in the figure below.
PCF CHF 1
1
SMF-configured CC
UDM-provided
UDM 2 4 SMF
subscribed CC
3
NRF CHF 2
Trigger Condition
A charging event, initiated by the CHF, is a trigger condition which the CHF delivers to the SMF.
The SMF applies for new quotas or reports used quotas to the CHF when this condition is met. For
example, when the traffic used by a service reaches a specified threshold, the SMF requests the
CHF to update the charging session and obtain a new quota. Trigger conditions are classified into
the following types:
By charging scope:
PDU session: A PDU session trigger condition takes effect for all RGs in a PDU session.
RG: An RG trigger condition takes effect only for the current RG.
By report types:
Immediate: When an immediate trigger condition occurs, the SMF needs to immediately
report the quota usage to the CHF.
Deferred: When a deferred trigger condition occurs, the SMF temporarily stores the quota
usage corresponding to the current trigger condition, and reports the quota usage when the
next immediate trigger condition occurs.
39
Charging
Procedure
2. The SMF
selects the CHF.
.
5. A new quota is required when a trigger
condition is met.
5G Charging 4G Charging
Service Operation Function
Message Message
Charging Data
Nchf_ Charging session
Request/Response CCR-I/CCA-I
ConvergedCharging_Create establishment
[Initial]
Charging Data
Nchf_ Charging session
Request/Response CCR-T/CCA-T
ConvergedCharging_Release termination
[Termination]
CHF-initiated re-
Nchf_ Charging Notify
authorization or RAR/RAA
ConvergedCharging_Notify Request/Response
deactivation notification
40
Signaling
Challenges
NMS
International International International 5G
2G/3G network 4G network network
SPS (ISTP) SPS (ISTP) SPS (DEA) SPS (DEA) SPS (SEPP) SPS (SEPP) NPAC
National network
PCC Fixed
IMS 2G/3G 5GC
network
HSS OCS
SMSC AMF
GPRS/EPC
41
Signaling
4G 5G NSA 5G SA
Other network
Diameter Other network Diameter Diameter & HTTP
Other network
DRA DEA DRA+ DEA+ DRA+&SCP DEA+&SEPP
Evolving to support 5G SA
Upgrading software to support deployment based on the SBA
Migrating the DRA and DEA 5G NSA deployment
to the cloud
Accelerating 5G network Safeguarding signaling
Maximizing 4G signaling construction
Uniformly monitors 4G&5G signaling and
Supports 4G&5G session binding data
network investment returns sharing and reduces overlapping
identifies signaling attacks.
Supports the smooth evolution to 5G. configurations.
IMS
SPS with the BSF and DRA co-located:
Supports 4G&5G session binding data sharing,
reducing database resource consumption. EPC 5GC
MSC
The SPS will ultimately converge the ISTP, DEA, server
and SEPP to connect multiple PLMNs and secure IPX/PLMN
HLR SMSC
an inter-network signaling exchange. (SS7)
SPS
SPS with the ISTP, DEA, and SEPP co-located: HSS/UDM
ISTP
Interworks with other PLMNs or IPXs, hides
IPX/PLMN
network topologies, and encrypts inter- PCRF/PCF
DEA (Diameter)
network transmission.
MME/AMF
Acts as a firewall to block invalid messages SEPP
and identify attacks by detecting abnormal
GW/SMF SMSF IPX/PLMN
behaviors and analyzing security data. (HTTP)
42
Signaling
SCP Functions
The SPS provides the SCP functions to converge HTTP signaling. This simplifies network topology
and facilitates O&M.
NRF NRF
NRF SCP SCP NRF
SCP Deployment
SCPs are deployed in pairs for redundancy. SCPs in a pair (SCP A and SCP B) share traffic load with
each other and communicate over C links. If the HTTP link between SCP A and an NF becomes
faulty, SCP A forwards messages to SCP B over C links. SCP B then forwards the messages to the
target NF. This enhances service reliability.
SBI
C links
Nnrf
SCP A SCP B
SCP A SCP B
NRF
N12 N10 N7
N8 N15 N40
43
Signaling
The SCP can route messages based on IP addresses in URIs, FQDNs, GPSIs, SUCIs, SUPIs, and DNNs.
The FQDN-based message routing is used as an example here.
01 HTTP request
03 HTTP request
FQDN
Routing Policy
npcf-
N7 SMF – PCF Npcf_SMPolicyControl Yes Yes Yes Yes Yes
smpolicycontrol
Nudm_Subscriber
nudm-sdm Yes Yes Yes Yes
DataManagement
N8 AMF – UDM
N10 SMF – UDM
N21 SMSF – UDM
Nudm_UEContext
nudm-uecm Yes Yes Yes Yes
Management
Nausf_
N12 AMF – AUSF nausf-auth Yes Yes Yes Yes
UEAuthentication
Nudm_
N13 AUSF – UDM nudm-ueau Yes Yes Yes Yes
UEAuthentication
npcf-am-policy-
Npcf_AMPolicyControl Yes Yes Yes Yes
control
N15 AMF – PCF
npcf-ue-policy-
Npcf_UEPolicyControl Yes Yes Yes Yes
control
N5g-eir_
N17 AMF – 5G-EIR EquipmentIdentity n5g-eir-eic Yes Yes Yes Yes
Check
Nchf_ nchf-
N40 SMF – CHF Yes Yes Yes
ConvergedCharging convergedcharging
44
Signaling
BSF Functions
The SPS provides the 3GPP-compliant BSF functions. The BSF facilitates target PCF addressing on
a 5G network.
If multiple PCFs are deployed on a 5G network, the BSF queries session binding data for the PCF
serving a subscriber, such as the IP address or DNN. Afterwards, it sends the PCF information to
the NEF or AF. The NEF or AF then can route messages received from the subscriber over different
interfaces (N7, N5, and Rx) to the target PCF during data and voice services.
NF profile registration
Nnrf_NFManagement_NFRegister
NF profile update
Nnrf BSF -> NRF
Nnrf_NFManagement_NFUpdate
NF profile deregistration
Nnrf_NFManagement_NFDeregister
HTTP/2.0
Session binding information registration
Nbsf_management_Register
BSF <- PCF
Session binding information deregistration
Nbsf
Nbsf_management_Deregister
45
Signaling
BSF Deployment
Networking
5G voice services are still provided by the IMS network. To support VoNR services for 5G subscribers,
the BSF needs to be able to interwork with the DRA on the IMS network over the Rx interface. The
BSF can act as a proxy agent or a redirect agent to help the DRA address a PCF, as defined in 3GPP
TS 29.513.
Proxy agent: After receiving an AAR message from the DRA, the BSF obtains the host name of
the target PCF, includes the PCF host name in the AAR message, and sends the message to the
target PCF over the Diameter link.
Redirect agent: After receiving an AAR message from the DRA, the BSF obtains the host name of
the target PCF and returns a response carrying the PCF host name to the DRA. The DRA then
redirects the AAR message to the target PCF.
When the BSF acts as a proxy agent, Diameter links between the BSF and PCF are required.
When the BSF acts as a redirect agent, Diameter links between the BSF and PCF are not required.
5GC
N7
01 PCF 1
AMF SMF
05
IMS Rx
Rx
PCF 3
The DRA on the live
network remains
unchanged.
IMS AF DRA
UE
Proxy
… NF/NE Deployment
46
Telco Cloud
Telco Cloud
Positioning
Telco Cloud is a cloud platform for telecom services. It leverages advanced technologies, such as
NFV, SDN, Cloud Native, container, and AI. With these technologies, it endows solutions, including
5GC, MEC, and SVC, with full-cloud, full-stack, ultimate experience, and multi-network convergence
features.
… …
MEC
5GC adopts SBA and NFV architectures to deploy core NFs on an SA network, empowering agile,
simplified, efficient networking.
MEC moves core network applications, content, and some MBB service processing and resource
scheduling functions to the network edge, closer to users. Applications, content, and networks
collaborate with each other, providing the ultimate service experience.
SVC converges voice services of different RATs into the same network. It simplifies networks and
O&M, and improves the overall voice service experience.
47
Telco Cloud
Solution Architecture
VNF layer
NFV_FusionSphere
Hardware layer
eSight
48
Telco Cloud
Networking
SDN is recommended for Telco Cloud because it centrally controls and manages routing and
switching, provides a unified network view, and automatically and intelligently manages networks
and orchestrates services. Services can be quickly deployed, and network efficiency can be improved.
Networking Categories
Network overlay NFVI management & storage traffic is routed over VLANs, and service traffic over network
(recommended) overlay-based VXLANs.
NFVI management & storage traffic is routed over VLANs, and service traffic over host
Host overlay
overlay-based VXLANs.
NFVI management & storage traffic is routed over VLANs, some service traffic over network
Hybrid overlay
overlay-based VXLANs, and other service traffic over host overlay-based VXLANs.
Non-SDN VLANs for both NFVI management & storage and service networks.
PE PE
NFVO/VNFM
VIM
DC GW DC GW
SDN controller
Border leaf Border leaf
VXLAN VXLAN
MS: NFVI management & storage
SDN mgmt.
& config.
VXLAN VXLAN channel
VM VM VM VM
Provides a way to extend Layer 2 networks across Layer 3 infrastructure using MAC-in-
VXLAN
UDP encapsulation.
An entity for SDN. It converts the VNF network interconnection model into the NFVI
NFVO
network model, and manages service and network life cycles.
A network automation control center for SDN. It controls switches to automatically
SDN controller
generate network interconnection data.
Start point of a VXLAN tunnel. It encapsulates and parses VXLAN packets, and allows
Server leaf
VNFs to access the VXLAN.
Distributed gateway at Layer 2 or 3 of a VXLAN. It allows VXLAN packets to be
L2/L3 GW
transmitted over the nearest Layer 2 or 3 network.
The switching center of network traffic. It provides high-speed IP forwarding, and
Spine
connects to each server leaf through high-speed interfaces.
A VXLAN Layer 3 gateway and the end point of a VXLAN tunnel. It allows external traffic
Border leaf
to access the VXLAN of a DC.
49
Telco Cloud
Host Overlay
PE PE
NFVO/VNFM
VIM
DC GW DC GW
SDN controller
Border leaf Border leaf
VXLAN VXLAN
MS: NFVI management & storage
SDN mgmt.
& config.
VXLAN VXLAN channel
vSwitch vSwitch
CE1800V CE1800V
VM VM VM VM
CE1800V is a new component for host overlay. In essence, it is a software switch and functions as
a server leaf at the start point of a VXLAN tunnel.
50
Telco Cloud
Automatic Deployment
One of the advantages of SDN is that it automatically deploys networks, improving deployment
efficiency.
With the SDN controller, network devices automatically deliver network interconnection data.
Complete installation, interconnection configurations, VNF pre-configurations, and underlay network configurations.
Synchronizes VM images.
Instantiates NSs
and VNFs.
Sets network and
deployment
parameters. Creates northbound external networks and subnets and automatically completes related
configurations on network devices or the CE1800V.
Notifies
FusionStage to
create a network
stack.
Creates a network stack.
Notifies
FusionStage to
manage the VMs.
A VNFD template describes the resource models, internal connections, and deployment models
required for VNF instantiation.
An NSD template describes the network service functions, network topologies, and external
connections of VNFs.
A TOSCA template describes the topology structure of a service application, services contained in
the application, service resources, and relationships and dependencies among the services.
51
Telco Cloud
Container Overview
Both VMs and containers are virtualization technologies. Containers start up faster than VMs,
utilize resources more efficiently, and leverage lighter, higher-performance resource isolation
mechanisms.
VM: The NFVI creates VMs, and the OSs of VMs are isolated from one another.
VM-based container: The container platform creates containers over VMs. Containers share the
guest OS and can be started quickly.
Bare-metal container: The container platform directly creates containers over the infrastructure,
resulting in higher performance, quicker startup, and greater resource utilization.
Project/Namespace Project/Namespace
Host Host
VM/Node VM/Node
Huawei container management platform. It manages container life cycles and provides routine
FusionStage
O&M for containers.
FusionStage can create multiple projects, each with their own resource quota. In this way,
Project resources of different projects are isolated. A project is similar to a VPC at the NFVI layer. To unify
the resource models of FusionStage and NFVI, a project corresponds to a VPC in most cases.
Each project has its namespace. When FusionStage creates a project, K8s creates a namespace
Namespace
with the same name as the project. Resources are isolated logically by namespaces.
Each namespace is mapped to one or more hosts. The resources logically isolated by a namespace
Host
are the sum of resources provided by these hosts.
Each VM is managed by FusionStage as a node in the target namespace. A node carries and runs
VM containers.
Each host houses one or more VMs and these VMs/nodes share the host resources.
A pod is the smallest deployable unit in K8s. Resources are logically isolated among pods. Each
Pod
node contains one or more pods.
One or more containers thrive in a pod and share the pod resources. Microservices run on
Container
containers.
52
Telco Cloud
connected to
2
1 Container interfaces are mapped to VM interfaces, and communicate with each other through
the VM network.
2 Container interfaces within the same VLAN use the internal Layer-2 switch network for intra-
server communication, and an external Layer-2 switch for inter-server communication.
3 Container interfaces in different VLANs communicate via a Layer-3 switch, no matter if
interfaces reside on the same or different servers.
Pod Pod
3
Container Container Container Container
FusionStage
Guest OS Guest OS
2
Host OS+Hypervisor FusionSphere
OpenStack
Compute, storage, and network
1 VNFM manages VNF life cycles. It deploys VNFs with uploaded VNFD files, software packages,
image packages, service templates, and service image packages.
2 FusionSphere OpenStack manages VM life cycles. It applies for VM resources described in
the VNFD and creates VMs.
3 FusionStage manages container life cycles. It creates containers on VMs based on TOSCA
service templates.
53
iMaster MAE-CN
Overview
The architecture of cloud core O&M systems has evolved from silo-like to convergent, and the
mechanism behind the O&M itself moved from auxiliary O&M to SDN/NFV cloud-based O&M.
Ultimately, O&M systems are expected to become an engine for autonomous driving networks,
achieving simplified O&M and enhancing O&M efficiency.
Autonomous driving
network engine
R20.1 or later
Cloud-based
SDN&NFV O&M
(R19.1)
Auxiliary O&M
R18.1 or earlier
iMaster MAE-CN
Network Network
optimization maintenance
mAOS CN NFVO
Network Service
Unified planning provisioning
Comprehensive,
orchestration &
flexible KPI
resource
report analysis
management
PRS KPI Network
NFVO
deployment
Unified
Comprehensive, orchestration &
flexible KPI resource
report analysis U2020-CN
management
CCE
Convergent Convergent
Unified data
Scenario- Enhanced management management
base
specific NFV O&M plane /control
configuration
NFV O&M
CSM VNF life cycle
management
Basic FCAPS
VNF life cycle management
U2000/M2000 management
/N2000
Basic FCAPS
management
for PNFs/VNFs
54
Overview
iMaster MAE-CN
Unified data
management
Unified resource management Unified alarm management Unified KPI management
Autonomous management
and control unit
IMS
Service enabling/control Autonomous management
and control unit
LCM
Service enabling/control
CSP Edge
LCM
UPF MEC
COTS Infrastructure
resource agent
CSP
PCF UDM NRF
FusionSphere
/FusionStage
Convergent: The EMS, VNF LCM, NFVO, and SmartTestKit & CCNFMA tools are converged into
one system, and functions such as slicing and MEC management are added, forming an
autonomous network driving engine.
Unified: Unified engineering deployment and O&M portals are provided to manage northbound
and southbound interface, platform, and service data, reducing interconnections, resource
consumption, and expenditure.
Flexible: One architecture is used as base. Services can be flexibly combined to adapt to various
service scenarios, such as slicing, telecom cloud, and MEC.
Efficient: CD/CT automation and AIOps are enabled to ensure efficient delivery of functions and
services.
55
Overview
Everything
Cross- IP-based Web & mobile
2G 3G 4G connected 5G
generation
management
Cross-platform
management
Cross-layer management: MAE supports cross-layer topology and alarm management. The unified
cross-layer topology centrally displays the relationships between components at the hardware layer,
virtualization layer, and VNF layer, which helps quickly identify NE/NF faults, if any. Cross-layer
alarm management enables MAE to display VNF and NFVI alarms in the same view. MAE can mask
correlative alarms and display only root alarms. VM and host locations can also be displayed.
Cross-generation management: MAE can manage 2G, 3G, 4G, and 5G wireless and CN NEs/NFs.
Cross-domain management: MAE can manage various cloud core NEs/NFs, including CS, IMS, PS,
and 5GC.
Cross-platform management: MAE can manage both traditional platform NEs (PNFs) and cloud
platform NEs/NFs (VNFs).
MAE
SNMP alarm
RESTful
SFTP
NFVI FusionSphere
Virtual Virtual Virtual OpenStack OM
compute storage network
PNF
FusionSphere
SNMP
eSight
OpenStack
Server Server Third-
party SNMP/
RESTful
Network device hardware MongoDB
VNF Alarms/KPIs
VNF -> MAE: VNF alarms and KPIs are directly reported to MAE.
eSight Alarms/KPIs
eSight -> MAE: eSight alarms and KPIs are directly reported to MAE.
Hardware Alarms/KPIs
COTS hardware -> eSight -> MAE: Hardware alarms and KPIs are reported to eSight and then to MAE.
FusionSphere Alarms/KPIs
FusionSphere OpenStack -> FusionSphere OpenStack OM -> eSight -> MAE: FusionSphere alarms are
reported to eSight and then to MAE.
56
VNF LCM
5GC provides higher bandwidth and lower latency for subscribers to satisfy their service
requirements. Besides VMs, it also uses a container-based architecture to provide better network
experience.
VNF LCM allows users to upload VNFD files and software packages required for VNF deployment.
The VNF LCM automatically parses the VNFD files and deployment parameters, then interacts with
the VIM and FusionStage to create VMs and pods accordingly. In this way, VNF software can be
installed easily. The deployment progress is displayed during installation, and fault demarcation
and handling advice is provided if a step needs redoing, or a task fails.
4
NFVI VM
1 VNFD upload Users upload VNFD files and related software packages on VNF LCM.
3 VNF VNF LCM applies for resources from the VIM to create VMs required by VNFs.
instantiation
VNF software After the VMs start up, VNFs download the software packages from the SFTP
5 installation server, install the VNF software, and notify VNF LCM of the completed installation.
6 EMS notification VNF LCM notifies the EMS of the completed VNF software installation.
EMS processing
7 The EMS configures the newly connected VNFs.
VNF configuration
57
VNF LCM
4
NFVI VM FusionStage
1 VNFD upload Users upload VNFD files and related software packages on VNF LCM.
3 VNF LCM applies for resources from the VIM to create VMs required
by VNFs.
VNF instantiation
After the pods start up, VNFs download the software packages from the
6
VNF software
SFTP server, install the VNF software, and notify VNF LCM of the
installation
completed installation.
7 EMS notification VNF LCM notifies the EMS of the completed VNF software installation.
8
EMS processing
The EMS configures the newly connected VNFs.
VNF configuration
VNF LCM also monitors VNF counters, adds or deletes VMs or pods, and uses a stack-based
method to scale VNFs, improving resource utilization.
VNF LCM provides the VNF self-healing management function, which enables VNFs to self-heal in
the case of faults. The system allows users to power on, power off, and live migrate VMs. If a VM
is faulty, users can reboot or rebuild the VM for quick restoration. If a pod is faulty, users can
rebuild the pod. VNF LCM also allows users to delete invalid VNF VMs to improve resource
utilization.
58
NFVO
OSS/BSS Os-Ma
NFV Orchestrator
(MAE-Orchestrator)
Or-Vnfm
Or-Vi
Vn-Nf
NFVI Vi-Vnfm
Nf-Vi
Virtualised
Virtualization Layer
Infrastructure
Manager(s)
Vi-Ha
Execution reference points Other reference points Main NFV reference points
59
NFVO
Automated NS
life cycle
management 3
1 Users can edit NSDs to quickly orchestrate NSs, including VNF deployment, network setting,
and scaling.
2 NSs can be deployed with ease. The detailed process is as follows:
1. Users upload NSDs and import VNFDs, software packages, and image packages
required for VNF deployment on the MAE-Orchestrator client.
2. Users select the NSDs to be deployed and set deployment parameters.
3. MAE-Orchestrator parses NSDs, interacts with the VIM to create NSs, and interacts with
the VNFM to create VNFs. In this way, NSs are deployed easily.
4. Users configure VNFs on the EMS or VNF maintenance platform.
5. Services are brought online.
4 NSs can be deleted on the MAE-Orchestrator client when they are no longer required.
60
NFVO
MAE-Orchestrator
DC 1 DC 2 … DC n
Physical resources
Virtual resources
AZ
Physical server
HA VDC
Storage device Host
VM VPC
Network device
Region 2
AZ
HA VDC
Host
VPC
VM
…
61
NFV Unified Cross-layer View
Introduction
The NFV unified cross-layer view feature provides a cross-layer topology and unified device panel,
helping O&M personnel quickly locate the root cause of NE faults.
Cross-layer topology: Displays the relationships between VNFs and VMs, hosts, host groups, and
cloud services in a vertical manner. This helps O&M personnel understand relationships between
components and locate faults.
Device panel: Displays the status of servers and VMs on the servers, helping O&M personnel
identify the impact scope of a fault.
After interconnection with eSight, MAE obtains cross-layer topology data from eSight to obtain
and display relationships between NEs/NFs and VMs, hosts, host groups, and cloud services, as well
as between VMs, hosts, and hosts. The following figure shows the path used to report data.
RESTful
MAE-CN
NE
NFVI
Network eSight
Server Server
device
Third-party hardware
NFVI-> eSight
eSight obtains details about virtual and hardware resources from the NFVI.
1. MAE obtains the relationships between VMs, hosts, and servers from eSight.
2. MAE obtains details about virtual and hardware resources from eSight.
62
Network Slice Management
Introduction
The 5G network slice management function is built on the SBA. This function is provided by the
NSMF and NSSMF to implement E2E network slice collaboration and full life cycle management
across the access network, the transport network, and the core network. The NSSMF is responsible
for managing and orchestrating slice subnet instances.
With this function, operators can:
Design the NSST, based on which the system creates slice subnet instances.
Set the SLA parameters of a slice subnet, such as the uplink and downlink rates, latency, and
maximum number of subscribers.
Define the NSD file.
This function enables users to deploy services on demand and to scale slice instances in or out
when services change, improving resource efficiency. When a slice instance is no longer required,
the slice instance is terminated to promptly release and reclaim resources. The NSSMF supports
slice subnet alarm reporting and SLA metric monitoring, helping users learn the slice running
status, prevent network accidents, and forecast the network running status.
Purchases
slices.
BSS/CSMF
Tenant
OSS/NSMF
RAN TN
Slice Slice Service SLA
design deployment activation assurance
5GC
VR/AR
SMF PCF …
IoV
Network slice 2
Smart campus
Network slice 3
NFVI
63
O&M Solution
Overview
Huawei offers a comprehensive set of O&M activities, features, and tools to ensure that the 5GC
network runs smoothly.
Change Preventive Emergency
Routine O&M Troubleshooting
Management Inspection Management
• Scenario-based data
collection (via OM portal)
EMS capabilities
Alarm monitoring Signaling trace Scenario-based data collection Intelligent KPI anomaly detection
(using the NIC tool)
Tool capabilities
Metrics and KPIs display CHRs display Offline MML tool Scenario-based health check
Alarms display Traffic counter comparison NFVI unified log analysis (CLLI)
64
O&M Solution
Our service-centric O&M model maintains VNFs on a 5G network. It offers basic FCAPS capabilities,
including alarm and performance monitoring, performance statistics, data collection, as well as
configuration, log, and license management.
EMS
MML/SNMP/SFTP/FTPS/SOAP/NETCONF/RESTful
OM portal
Web
Portal
EMS
interconnection
Software upgrade Configuration maintenance
Node
management O&M security Service monitoring
The EMS is a remote O&M center for centralized and intelligent O&M of diverse VNFs.
The O&M portal supplements the EMS, providing basic local emergency O&M capabilities for users
to maintain each VNF.
O&M capabilities of the EMS and OM portal:
Software
MML Log Trace Data
package
configuration management management collection
management
65
O&M Solution
The EMS is a device maintenance center that centralizes cross-layer O&M for VNFs and the NFVI.
OSS
EMS
(MAE-Access/U2020)
FusionStage
COTS hardware
Provides local O&M for FusionSphere Provides enhanced O&M services in the VIM
OpenStack; but does not support O&M for and is the unified O&M center for the NFVI
COTS hardware. in a DC.
eSight centrally monitors FusionSphere
OpenStack and hardware, including
compute servers, disk arrays, and switches.
Manages VNF life cycles and obtains their Provides O&M for its managed VNFs,
infrastructure monitoring data from eSight. obtains NFVI monitoring data from eSight
and the VNFM, and provides correlation
analysis between the VNFs and NFVI
resources.
66
O&M Solution
IES-A (IES-Assurance) is a centralized ICT O&M center and NFVO (MAE-Orchestrator) manages
service life cycles. Collectively, IES-A and NFVO are referred to as NFVO+.
OSS
NFVO+
(NFVO/IES-A)
EMS
Third-party EMS
(MAE-Access/U2020)
FusionStage
FusionSphere OpenStack/ Cloud OS
FusionSphere OpenStack OM
eSight
COTS hardware Third-party hardware
Manages VNF life cycles and obtains their Provides O&M for managed VNFs, and
infrastructure monitoring data from eSight. obtains virtual resource and monitoring
data for the VNFs and NFVI from the
VNFM.
IES-A
Obtains VNF O&M data from the EMS and NFVI monitoring data from eSight, provides cross-
vendor, cross-layer, and cross-domain O&M, and reports the O&M monitoring data of the entire
5G network to the operator's OSS.
67
Cross-Layer O&M Features
MAE/U2020
EMS
Web portal
(MAE-Access/U2020)
sso
VNF OM portal
eSight portal
FusionStage
FusionSphere OpenStack/
FusionSphere OpenStack OM
Compute Disk eSight
Switches
servers arrays
68
Cross-Layer O&M Features
SSO
SSO is an access management feature, which allows a user to access any of the several related,
yet independent, application systems with just one set of credentials.
With this feature enabled, users can:
1. Switch to the VNF OM portal, FusionStage OM portal, or VNF LCM Web portal from the
topology page of the EMS.
2. Switch to the web portals of NFVI components, such as FusionSphere OpenStack, E9000, and
disk arrays, from the eSight topology page.
MAE/U2020 Web
eSight Web portal
portal
FusionSphere
FusionStage OM VNF LCM Web OpenStack OM
VNF OM portal
portal portal Web portal
DeviceManager
Web portal
FusionSphere
FusionSphere OpenStack OM Web portal
OpenStack
eSight DeviceManager Web portal Disk arrays
69
Cross-Layer O&M Features
To locate a VNF fault, you may need to view the correlation between the VNFs, virtual resources,
and hardware resources.
The EMS can display this as a layered topology, or in a device panel view.
Board status:
VNF UNC_NSSF Normal Offline Unknown Faulty
VM status:
NF Service Framework NSSF Normal Offline Unknown Faulty
Appctrl-pod Netm-Pod-d5...
Pod
VM
Host
Host
aggregate
HA
/Cluster
Cloud
Cloud
service DC
Description Description
Helps users easily find the VMs housing the Displays the status of servers and
VNFs to locate a fault. boards on a device panel.
70
Cross-Layer O&M Features
KPI anomaly detection plays a critical role in O&M, as it helps O&M personnel promptly identify faults
and provides a basis for further analysis.
The EMS intelligently detects KPI anomalies for 5G NFs. It uses AI algorithms to detect abnormal KPIs
and multi-metric correlation to analyze faults.
This function significantly reduces the time required to locate faults.
Classification result
Feature Real-time
classifier data
Training Module
1. The feature classifier in the training module classifies historical KPIs according to their features and
generates a classification result.
2. After the historical KPIs and classification are provided for the algorithm library, the training module
selects an appropriate algorithm to train KPI data, and then generates a training model.
Detection Module
1. After real-time KPI data is input into the detection model, the model predicts dynamic KPI thresholds
and KPI anomalies.
2. KPI anomalies and dynamic thresholds are displayed on the GUI and alarms are reported.
Relationship Description
Direct relationship The correlated KPIs directly cause the abnormal KPI.
The measurement object of a correlated KPI is part of the
Part-to-whole relationship
measurement object of the abnormal KPI.
Intra-NF service flow Correlated KPIs represent some stages in the procedure of the primary
relationship KPI.
Inter-NF service flow KPIs of multiple NFs are correlated based on services and are assigned
relationship into a correlation group, facilitating cross-NF fault locating.
71
Key O&M Activities
Routine Maintenance
Routine maintenance is an important part of keeping systems up to date and functional, and helps
O&M personnel mitigate risks.
Address critical and some major alarms immediately, as they can affect system services.
Set KPI thresholds based on services, as well as observe and handle KPI fluctuation.
Huawei provides advanced tools to efficiently collect fault data in different scenarios.
The table below lists the tools available for collecting fault data.
72
Key O&M Activities
Scenario-based Template-based
Customized items
collection collection
Incidents Service
issues
Items available Items selected
Before
Reset
and after an
issues Offline
operation
Template
Online
Upgrade Network
evaluation
Health
check
Inspection Process
VNFs are regularly inspected online or offline. The NIC tool provided by the MAE/U2020 collects
data online, and the NetCare platform performs offline inspections.
SmartKit and FusionCare help to inspect the NFVI.
Analyze data
Inspected Objects Checked Items
Generate a risk list FusionSphere
Statuses of FusionSphere OpenStack
OpenStack
components
Manage risks components
73
Key O&M Activities
Responsible-party
Data collection Fault locating Troubleshooting Summary
determination
Horizontal analysis
No more
Preliminary analysis and conclusion
horizontal analysis
UNC UDG
VM VM
Pod Pod Pod
Relevant to virtual compute, storage, or network
FusionStage
Determination
point 2 FusionSphere OpenStack
Servers
Determination point 3
COTS hardware
TOR TOR
Storage EOR
Determination point 4
Customer
networks
74
Key O&M Activities
Blade fault
Incident Summary Disk array fault VM migration
Analyze the root cause of the incident and Network port Host restart/power-
summarize the incident handling experience. fault/packet loss and off/isolation
error
AN
75
Find Out More
We hope this brochure shows how 5G can benefit and unlock new
opportunities to boost your business.
https://support.huawei.com/
Bookshelf
Click 5G Core.
5G Core (5G Core/UNC/UDG/UDM/UPCF/
Telco Cloud)
All other trademarks and trade names mentioned in this document are the
property of their respective holders.
Notice
The information in this document may contain predictive statements including,
without limitation, statements regarding the future financial and operating
results, future product portfolio, new technology, etc. There are a number of
factors that could cause actual results and developments to differ materially
from those expressed or implied in the predictive statements. Therefore, such
information is provided for reference purposes only, and constitutes neither an
offer nor a commitment. Huawei may change the information at any time
without notice.
No part of this document may be reproduced or transmitted in any form or by
any means without prior written consent of Huawei Technologies Co., Ltd.