5G Core Network Deployment and Evolution Solutions ISSUE 1.7

5G Core Network Deployment and
Evolution Solutions
www.huawei.com
Copyright © Huawei Technologies Co., Ltd. All rights reserved.

Objectives
 Upon completion of this course, you will be able to:
 Describe the characteristics of NSA/SA networking.
 Understand the 5G NSA/SA deployment and evolution strategy.
 Understand the 5G network cloudification evolution strategy.
Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 3

Contents
1. Selection of NSA or SA
2. NSA Network Deployment and Evolution Suggestions
3. SA Network Deployment and Evolution Suggestions
4. 5GC Cloud Evolution

NSA & SA
NSA (Non Standalone) SA (Standalone)
N26
EPC EPC 5GC
Control plane Control plane
User plane S1-C User plane
S1-U S1-U N2 N3
S1-C
X2
LTE 5G NR 5G NR
MN SN
LTE
*Using option 3x as Option 2

an example
• The existing LTE network and EPC are used as anchor points for mobility • The 5G NR is independently deployed and directly connected to the 5G
management and coverage. 5G access is added. core network.
• The dual connectivity concept is introduced. The control plane service is • The UE maintains only the 4G or 5G user-plane connection at the same
processed by the master node. The user plane service can be processed by time.
the master node or secondary node. Option 3 is used as an example. The • The 5G and 4G networks can use the handover procedure for interworking,
LTE eNodeB serves as the master node and the 5G gNodeB serves as the which may involve 4G/5G core network interworking.
secondary node.
• The 5G/4G interworking is controlled by the master node.

NSA & SA Mobility Management Comparison
Control Plane Handover in NSA NSA Fills the Experience Gap When
e Coverage Is Not Continuous
5G tNR
LTE
5G NR 5G NR • Signaling anchored on
D el e
LTE, and no handover in g. NSA + Dual-Connectivity
occurs.
Throughput
r a in NSA
k t
• A higher handover r
o g. SA
success rate when the n e tw in
s i n
handover starts from
e lesa k tra
r
low band. wi twor
y to ne
o n l co r e
b e or
lin
Control Plane Handover i a
c idSA e f
l
a p p i s sl LTE Site 5G Site LTE Site
LTE e is th
5G NR 5G sNRlid • Signaling anchored on
is
Th NR, and more handovers
occur.
• Continuous coverage vital
1 2 3 for SA (low band)
CP
Multiple Choices for 5G Network Evolution
NSA Networking SA Networking
Signaling anchored on LTE, Signaling anchored on eLTE, 5G Signaling anchored on NR, 5G Signaling anchored on NR, 5G
EPC+core network core network core network core network
EPC+ 5GC 5GC 5GC

S1 N2 N2 N2
X2 Xn Xn
LTE NR eLTE NR eLTE NR NR
Option 3 Option 4
Option 7 Option 2
Finalized at June 2018 (Phase
Finalized at the Finalized at the 1.2)
end of 2017 end of 2018 (Phase 1.3) Finalized at December 2019
Finalization (Phase 2.0)
time
Service
eMBB Slicing, MEC….. URLLC, mMTC
type
Weak Strong
NR
coverage

NSA Traffic Splitting Policies
Option 3/7 Option3a/7a Option 3x/7x

User-plane traffic splitting point
Core Core
Core
S1 S1
X2 X2
LTE X2
LTE NR NR LTE NR
• The transmission on the LTE network • There is no requirement for the BBU on the • There is no requirement for the BBU on
needs to be upgraded. live network. the live network.
• The BBU bandwidth on the live network is • The RAB traffic distribution is used and • Packet-based traffic distribution can
limited and needs to be upgraded. cannot adjust traffic based on the radio link provide optimal performance based on
status. the radio link status.

5G Network Evolution Path Selection
EPC EPC+ Cloud EPC+ EPC+

CUPS Convergent 5GC Convergent 5GC
Pool Pool
s .
ork
S1 netwNG NG NG NG
s e s
e l
LTE LTE LTE LTE
w ir
LTE eLTE NR LTE eLTE NR NR
w ei ide.
NR
H ua is slNR NR eLTE
Live network Option 3 f or n thOption3 Option7 Option 2 Option 4 Option 2
d ed o n o
5G NSA (Option3) (EPC+) me
n nti
Phase
m tte 5GC&EPC Interworking Convergent CN
e c o ial a • URLLC and mMTC

r
o t s p ec
Application • High bandwidth (eMBB)
scenario
s n
• The live network7isiupgraded to
/ P aysupport NSA, and • The cloud-based EPC is upgraded to the 5G convergent • All eNodeBs are upgraded to eLTE eNodeBs for
n 4 EPC is introduced, forming hybrid

the cloud-based control plane. evolution to all-5G networks.
Network o
tiarchitecture is introduced, supporting high- • 5G
networking. • NSA supports 4G/5G interworking (such as N26). • Existing EPCs are gradually retired.
reconstruction • O p
CUPS NR gNodeBs are newly deployed to access the 5G core
bandwidth services. network.
• eNodeBs are gradually upgraded to eLTE eNodeBs.
Network • Cloud-based EPC and CUPS • 4G/5G interworking

capability • SBA, network slice, QoS enhancement, and non-3GPP access

Q&A
 Question 1: What are the characteristics of the three typical traffic distribution modes of the NSA
network?
 Question 2: What are the options for NSA network evolution?

Contents

Network Function Changes in 5G NSA (Option 3)
HSS
• Extended QoS
UTRAN • 4G/5G subscription &
MME
authorization PCRF
• Extended QoS SGSN
• DCNR and E-RAB modification • Extended QoS (MBR, GBR, APN-
(Option 3a/3x) GERAN HSS AMBR, and UE-AMBR values
• NR access restriction S3 extended to 4 Tbit/s)
• NR traffic statistics & reporting
S 1- MME S 6a
• 5G gateway selection
MME
• 5G UE statistics PCRF
S 12 Rx
S 11 Gx
S4
LTE - Uu S 10
Serving S5 PDN SGi Operator 's IP
UE E- UTRAN Gateway Gateway Services
S 1-U (e.g. IMS, PSS etc .)
X2
S1-u
NR CG
S-GW/P-GW
• Extended QoS
CG • High bandwidth per subscriber
• Processing of fields in • 5G NR traffic charging
CDRs generated for NR • (Optional) NR traffic statistics
subscribers

Requirements of 5G NSA for CN NEs
5G NSA Requirements MME Gateway HSS PCRF
The E-RAB modification procedure Interfaces and routes between the gateway and
Option 3a/3x networking N/A N/A
supports 4G/5G bearer update. NR
Extended QoS negotiation (a maximum of 4

Tbit/s)
Extended QoS negotiation (a maximum of Extended QoS subscription (a Extended QoS policy processing (a
High bandwidth 10+ Gbit/s forwarding for a single subscriber;
4 Tbit/s) maximum of 4 Tbit/s) maximum of 4 Tbit/s)
cloud-based CUPS gateway recommended
(optional)
NR access control and authorization NR access control and authorization

Dual connectivity N/A N/A
(based on ARD) (based on ARD)
Identifying 4G/5G subscribers and

5G subscriber and service charging
Charging (Optional) 5G NR traffic statistics N/A delivering different charging control
(Optional) 5G NR traffic statistics
policies
(Optional) UE Usage Type parameter

MME selection (Optional) DÉCOR N/A N/A
for DCN selection (DÉCOR)
Large-bandwidth gateway selection based

Gateway selection on UE capabilities (DNS configuration High bandwidth per subscriber/service N/A N/A
required)
5G voice Same as VoLTE* Same as VoLTE* Same as VoLTE* Same as VoLTE*
*Note: In option 3/3a/3x networking, the user plane of 5G NSA voice can be established either on the LTE network or on the NR (determined by the RAN). The requirements for the
CN are the same as those in a VoLTE call. The CSFB voice solution can also be used in the NSA scenario.

Requirements of 5G NSA for Peripheral NEs/Systems
5G NSA
UE RAN Billing System CRM System
Requirements
5G air interface protocol stack
Option 3a/3x gNodeB and NR interconnection
5G NSA protocol stack
networking Service distribution decision-making
(Optional) 5G NR traffic statistics
Dual-connectivity high-bandwidth user-plane
Dual-connectivity high-bandwidth
forwarding See the charging 5G subscriber and
High bandwidth user-plane forwarding
High-bandwidth QoS processing over the S1 and air analysis slide. service management
High-bandwidth QoS processing
interfaces
Allowing or restricting the access of 5G subscribers to
Dual connectivity for services
Dual NR as authorized by the MME 5G subscriber and
Flow reordering by the UE in the
connectivity Flow reordering by the gNodeB in the option 3x service management
option 3x scenario
scenario
(Optional) 5G NR 5G subscriber and

Charging N/A (Optional) 5G NR traffic statistics
traffic statistics service management
MME reselection by the eNodeB using a rerouting
procedure, and DÉCOR (MME selection based on
MME selection (Optional) eDÉCOR
DCN-ID)
(Optional) eDÉCOR
Gateway
UE capability reporting N/A
selection
5G voice Same as VoLTE* Same as VoLTE* Same as VoLTE* Same as VoLTE*

NSA Deployment Solution 1: New Overlay EPC+ and PLMN-based
EPC+ Selection
MME pool MME+ pool  Deployment plan
• Deployment of cloud-based MME+ and CUPS-based GW to support
PLMN: 4G
MME PLMN: 5G vMME+
NSA. Remain legacy MMEs and S-GWs/P-GWs unchanged.
• MOCN supported by existing eNodeBs and independent PLMNs used by
5G UEs.
S-GW/P- GW-C • DNS reconstruction, addition of the suffix "+nc-nr" to the 'app-protocol'
GW
name of the DNS domain name for the NSA-capable S-GW/P-GW.
GW-U  Network selection policies
• The eNodeB broadcasts two 4G/5G PLMNs, and the 5G UEs select a 5G
PLMN to access the MME+ pool that supports NSA.
PLMN: 4G eNodeB
(MOCN)
gNodeB • The MME+ selects the gateway whose suffix is +nc-nr for the 5G UE
PLMN: 5G
that supports the 5G service.
4G UE 5G UE

NSA Deployment Solution 2: New Overlay EPC+, Cutover of NSA
eNodeB to the New Overlay EPC+
 Deployment plan
MME pool MME+ pool
• Deployment of cloud-based MME+ and CUPS-based GW to
MME vMME+ support NSA. Remain legacy MMEs and S-GWs/P-GWs
unchanged.
• Cutover of the eNodeBs in the NSA deployment scope to the
new MME+.
S-GW/P- GW-C
GW • DNS reconstruction, addition of the suffix "+nc-nr" to the 'app-
protocol' name of the DNS domain name for the NSA-capable S-
GW-U
GW/P-GW.
 Network selection policies
• 4G/5G UEs in NSA areas are selected to the new MME+.
eNodeB eNodeB gNodeB • The MME+ selects a gateway with the suffix of "+nc-nr " for the
UE that allows to use 5G services.
Inter TAU NSA
4G UE 5G UE

NSA Deployment Solution 3: MME Upgrade to Support NSA and a
Hybrid Pool
Hybrid pool  Deployment plan
• Deployment of cloud-based MME+ and CUPS-based GW. Legacy
MME+ vMME+ MME upgrades to support NSA. Hybrid pool formed by the cloud-
based MME+ and traditional MME+.
• DNS reconstruction, addition of the suffix "+nc-nr" to the 'app-
GW-C protocol' name of the DNS domain name for the NSA-capable S-
GW/P-GW.
S/PGW
GW-U  Network selection policies
• The eNodeB selects an MME+ based on load sharing principles.
• The MME+ selects a gateway with the suffix of "+nc-nr" for the UE
that allows to use 5G services.
eNB gNB
4G UE 5G UE

Summary of NSA Deployment Solution: Hybrid Pool Is the Optimal
Deployment Solution for NSA
Solution 2
Solution 1 Deployment of overlay EPC+, NSA Solution 3
Deployment of overlay EPC+, PLMN- eNodeB cutover to the newly deployed MME upgrades on the live network to
based EPC+ selection EPC+. support NSA, hybrid pool
PLMN planning, replacement of 5G
UE SIM cards Gradual eNodeB cutover -
Network reconstruction
eNodeB enabled with MOCN - -
DNS reconfiguration DNS reconfiguration DNS reconfiguration
eNodeB - - -
Software
upgrade MME - - Upgrades to support NSA
HSS - - -
Resource utilization MME resources not shared MME resources not shared MME resource sharing
 Main focus
Reconstruction
• Fast deployment, live network reconstruction reduction
• EPC+ reuse by 5GC, 5GC architecture readiness. Architecture Ready SBA
 Deployment suggestions
• Cloud-based device used for CUPS architecture during
CUPS 5GC
Cloud-based
NSA deployment.
• Option 3 is the optimal. deployment NSA SA

5G NSA Voice Deployment Same as VoLTE Deployment, with IMS
Reused
vIMS
5G NSA EPC CS
eNB gNB eNB
5G NSA Option 3 4G VoLTE 2G/3G

VoLTE VoLTE VoLTE CS voice
PS HO PS HO eSRVCC
eSRVCC
eSRVCC
• In NSA option 3 networking, NAS signaling is transmitted through the eNodeB and EPC. IMS SIP signaling/media is controlled by the RAN and can
pass through the eNodeB or gNodeB. The IMS considers that the signaling is transparently transmitted by the P-GW (4G RAN and cell information).
The procedure is the same as a VoLTE procedure.
• Conclusion: In NSA option 3 networking, the IMS does not need to be changed. It is recommended that the existing IMS be used.

2G/3G/4G/5G Unified Charging Recommended Because NSA
Supports Offline Charging of 5G NR Traffic
Control Plane Anchored to LTE and  Option 3/3x: LTE and NR share a bearer on the 5G NSA side, and 5G NSA cannot distinguish 4/5G
Connected to EPC+ traffic by RAT type.
 Option 3a: Although 5G NSA creates two bearers, the eNodeB does not report the RAT type.
EPC
Therefore, 5G NSA cannot distinguish traffic by RAT type.
S1-C S1-U
LTE eNB gNB
 Standards progress: IEs are added to the S1-C interface. The eNodeB reports NR traffic periodically or
as triggered by events. 5G NSA records the NR traffic in CDRs. This is not applicable to real-time
UE charging.
NSA Option 3 – MCG Split (LTE PDCP)
eNodeB MME Serving GW PDN GW
EPC
The Secondary RAT usage reporting field is
S1-C S1-U S1-U RAN reports Secondary RAT added to SGW-CDRs/PGW-CDRs to record
LTE eNB gNB usage data RAN-reported content.
UE 1. Change Notification
{dataVolumeUplink [1]
NSA Option 3a – EPC Split (CN)
2. Change Notification DataVolumeGPRS,dataVolumeDownlink [2]
DataVolumeGPRS,rANStartTime [3]
EPC TimeStamp,rANEndTime [4]
3. Change Notification Ack TimeStamp,secondaryRATType [5]
S1-C S1-U
LTE eNB gNB 4. Change Notification Ack SecondaryRATType}
UE
NSA Option 3x – SCG Split (NR PDCP)

Suggestion: 5G traffic is charged together with 2G/3G/4G traffic.

Q&A
 Question 1: What is the optimal NSA solution? Why?

Contents

Contents
3.1 5GC Control Plane Networking Scheme
3.2 5GC User Plan Deployment Principles
3.3 5GC SMS and Voice Solutions

5GC Service Based Architecture Overview
NF_A NF_B NF_A NF_B

NEF NRF UDM PCF AF (Consumer) (Producer) (Consumer) (Producer)
Request Subscribe
Nnef Nnrf Nudm Npcf Naf
Response Notify
Namf Nsmf Nausf Nsmsf
5GC-CP
AMF SMF AUSF SMSF
Request --> Response Subscribe --> Notify
N1 N2 N4
N6 5G control plane use service based interface
N3
UE AN UPF DN
1. Each NF provides its own business capabilities to other network
5GC-UP elements in a service manner
2. The service discovery of the NF is carried out through NRF;
SBA features • NF registration and deregistration

• NF decoupling and modularization; • NF services are upgraded independently and can
• NF service discovery;
• NF service authorization;
• SBI; be orchestrated; 3. NF service authorization consists of two parts;
• NF combination and deployment on demand; • Network service opening to external network • Service providers provide authorization for service
• High efficiency support for new business • NRF authorization for discovery

SA 5GC Convergent Deployment
Native convergence
 Native convergence of three types of NEs:
HSS +
UDM • Subscriber data: HSS+UDM convergence ensuring subscriber data consistency
• Policy data: PCRF+PCF convergence ensuring policy consistency and continuity
N10 PCF +
S6a PCRF • User plane: SMF+PGW-C convergence and UPF+PGW-U convergence;
N8
N7 unchanged mobility anchors ensuring data continuity
SMF + N15  Deep convergence of the AMF and MME:
S5-C PGW-C
• Better user experience: less signaling exchange between the MME and AMF, to
N4
prevent signaling storms caused by frequent handovers at the early stage of 5G
UPF +
N11 •
PGW-U Shared resources: independent service logic and shared public (micro) services
S5-U
SGW • Simplified O&M: one NE displayed on the management UI for unified O&M,
S11
improving efficiency
N26
MME AMF  Convergent NEs are compatible with 4G/5G interfaces.
Deep convergence (optional) • 5G interfaces are used between native convergent NEs.
S1-MME S1-U N3 N2 • 4G interfaces are used between native convergent NEs and EPC NEs.
N1 • 5G interfaces are used between native convergent NEs and 5GC NEs.
E-UTRAN NG-RAN • The logical NEs, AMF and MME, provide independent external interfaces.
UE UE

4G/5G Interworking with and Without an N26 Procedure
HSS/
UE eNB gNB AMF MME GW UE eNB gNB MME AMF GW
UDM
Handover triggering Network search
Handover
TAU or attach (handover)
preparations; Context information delivery
Transmission
transmission not
is interrupted TAU/attach procedure
interrupted
Handover before a target
Indirect forwarding tunnel
completion establishment PDN
Air interface Location update and P-GW/SMF ID acquisition
connection is
handover; a
established.
short period
Bearer update
of UE-requested PDN connection establishment
interruption
TAU and indirect forwarding tunnel deletion PGW-initiated old PDN connection deletion
N26-based 4G/5G interworking (handover) 4G/5G interworking without an N26 interface (same procedure
for the idle and connected states)
With N26 Without N26
A bearer and an indirect forwarding tunnel are preconfigured through the N26
A UE triggers a TAU/attach/registration procedure to re-access 4G or 5G. During this process,
Interoperations interface on the target side. There is only a short period of interruption during air
QoS cannot be guaranteed.
interface handover.
A P-GW/SMF allows the registration of a UE anchor (PGW-C+SMF ID) to an HSS/UDM.
Network requirements MMEs are upgraded to support the N26 interface (S10-based 5G enhancement). An MME/AMF can obtain PGW-C+SMF IDs from an HSS/UDM. UE anchors remain
unchanged.
IP session anchor IP addresses remain unchanged. IP addresses remain unchanged.
Transmission
Hundreds of milliseconds (applicable to real-time services, such as voice service) Several seconds
interruption

MME/AMF Convergence: Optimized 4G/5G Interworking, Shared
Resources, and Simplified O&M
Advantages of the convergent MME/AMF:
 Optimized interworking and better user experience
Independent MME/AMF Convergent MME/AMF
• 4/5G handovers are changed from inter-MME/AMF TAUs to intra-MME/AMF
TAUs. This reduces signaling exchange between the MME and AMF and between
the AMF and UDM and prevents signaling storms caused by frequent handovers at
4G NMS 5G NMS 5G NMS the early stage of 5G.
• The 4G-5G inter-RAT interoperability success rate increases.
• The 4G-5G handover latency is reduced.
UD HSS UD  Improved resource utilization because the MME and AMF share resources
HSS M M
 Higher efficiency and less cost with the unified O&M of 4/5G control planes
MME AMF MME&AMF
Handover signaling TAU KPI TAU latency
16 100.5 1000
14
99.5 900 800
12
15 98.5 99.6 800
97.5 98.6 700
600 500
10 96.5
8 95.5 500
6
9 94.5 400
300
4G 5G 4G 5G 4
93.5
92.5 200
2 91.5 100
0 90.5 0
Separated Converged Separated Converged Separated Converged
Messages exchanged Handover success rate: Handover latency:

between devices during increased by 1 to 2% reduced by 30 to 40%
handovers:
reduced by 40% to 50%
* Referring to protocol-defined * Statistics about the EPC TAU success rate on the live network of an operator.
procedures Handovers at the early stage of 5G are more frequent, and the impact is greater.

5GC Deployment Solution 1: PLMN-based Subscriber Identification and
Traffic Distribution on LTE Networks (MOCN) – Option 2
Network deployment
• Deploy a cloud-based convergent 5GC, including AMFs/MMEs, SMFs/GW-Cs,
and UPFs/GW-Us.
MME MME MME/AMF MME/AMF • Deploy a PLMN for 5G UEs to select a network, and use new USIM cards for 5G
5G-PLMN
UEs.
4G-PLMN
• Enable MOCN for LTE, and broadcast existing PLMNs and 5G PLMNs.
• (Optional) Enable MOCN for 2G/3G, and broadcast existing PLMNs and 5G
PLMNs.
SMF/GW-C
• Set the service parameters of the DNS domain name of 5G gateways to x-3gpp-
SPGW pgw:x-s5-gtp+nc-smf.
UPF/GW-U
Network selection policies
• When a 5G UE accesses 4G, a 5G PLMN is selected. The eNodeB selects a
combined AMF/MME based on the PLMN. It is recommended that 2G/3G/4G be
LTE NR co-deployed.
 If 2G/3G does not support MOCN and the UE falls back to 2G/3G, the UE
Option 2 uses a 2G/3G PLMN. When the UE switches to 5G, a new PLMN needs to be
selected. It takes about 6 minutes to 8 hours (1 hour by default) for the UE to
4G-PLMN
4G UE 5G UE 5G-PLMN return to 5G (HPLMN).
• An AMF/MME selects convergent 5G gateways (SMF/GW-C and UPF/GW-U)
5G interface 4G interface for the 5G UE.

5GC Deployment Solution 2: Independent 5GC and Cross-Pool 4G
and 5G Interoperations – Option 2
Network deployment
N26 (recommended)
• Deploy a cloud-based 5GC, including AMFs, SMFs/GW-Cs, and
MME MME AMF AMF UPFs/GW-Us.
• Upgrade MMEs to support the N26 interface and convergent
gateway selection.
• Set the service parameters of the DNS domain name of 5G
SMF/GW-C gateways to x-3gpp-pgw:x-s5-gtp+nc-smf.
S/P-GW
UPF/GW-U • When a 5G UE accesses LTE, an MME selects a convergent
gateway for the 5G UE.
• When a 5G UE accesses NR, it is connected to an AMF and a
LTE NR
convergent 5G gateway.
• When a 5G UE moves between 4G and 5G, the MME and AMF
Option 2 interwork through the N26 interface.
5G UE
5G interface 4G interface

5GC Deployment Solution 3: Hybrid Pool – Option 2
5G capacity 5G capacity
Network deployment
4G capacity 4G capacity 4G capacity 4G capacity
N26
• Deploy a cloud-based convergent 5GC, including AMFs/MMEs,
(optional) SMFs/GW-Cs, and UPFs/GW-Us.
MME MME MME/AMF MME/AMF
• Deploy the AMFs/MMEs and existing MMEs in a hybrid pool.
• Add the suffix +nc-nr to the app-protocol name in the DNS domain name of
5G gateways.
SMF/GW-C • Properly plan MME/AMF IDs. After a cross-node interoperation within the
pool, the 5G UE is anchored to an AMF/MME.
S/P-GW  AMF Region ID = MME group ID
UPF/GW-U
 AMF Set ID+AMF Pointer = MME Code
 The MMEs/AMFs and UEs use the following method to map 5G-GUTIs
and GUTIs so that the same convergent node is selected during 4G/5G
5G interface LTE NR interoperations:
• An MME or AMF/MME selects convergent 5G gateways (SMF/GW-C and
4G interface Option 2
5G UE UPF/GW-U) for the 5G UE.
AMF
AMF Region ID<8bit> AMF Set ID<10bit> 5G-TMSI<32bit>
5G-GUTI Pointer<6bit>
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63
MME G roup ID<16bit> MME Code<8bit> M-TMSI<32bit>

4G-GUTI
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63

5GC Deployment Solution 4: MME/AMF/UPF Full Cloudification
Pool, Option 2
Network deployment
• Deploy a cloud-based convergent 5GC, including AMFs/MMEs, SMFs/GW-
DC1 DC2 DC3
Cs, and UPFs/GW-Us.
N14/N26 • Deploy the AMFs/MMEs and existing MMEs in a hybrid pool.
MME/AMF MME/AMF MME/AMF
• Set the service parameters of the DNS domain name of 5G gateways to x-
3gpp-pgw:x-s5-gtp+nc-smf.
SMF/GW-C
• Properly plan MME/AMF IDs. After a cross-node interoperation within the
pool, the 4G/5G UE is anchored to an AMF/MME.
S1-C N2 UPF/GW-U
 AMF Region ID = MME group ID
 AMF Set ID+AMF Pointer = MME Code
4G 5G
 The MMEs/AMFs and UEs use the following method to map 5G-GUTIs
MME Pool Area = AMF Region and GUTIs
• Convergent 5G gateways (SMF/GW-C and UPF/GW-U) work as pool for all
UEs.
Cross POOL
Inner Pool interworking based
interworking
on convergence node.
based on N14/N26
AMF
AMF Region ID<8bit> AMF Set ID<10bit> 5G-TMSI<32bit>
5G-GUTI Pointer<6bit>
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63
MME G roup ID<16bit> MME Code<8bit> M-TMSI<32bit>

4G-GUTI
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63

5GC Deployment Solution 5: LTE Upgrade to eLTE and Access to
EPC and 5GC – Option 7/4/2
.
Network deployment
n i ng
r i
aconvergent
• Deploy a cloud-based
e t 5GC, including AMFs/MMEs, SMFs/GW-
MME MME AMF/MME AMF/MME
e th
Cs, and UPFs/GW-Us.
r
fo to eLTE and enable EPC&5GC dual access. Both N2/N3 and
• Upgrade b eLTE
id e
l
S1 interfaces are supported.
h is sConfigure the CN to support NSA Option 2/4/7 and hybrid access.
t •
SMF/GW-C lete Network selection policies
D e
e d . • Option 4/7 eLTE eNodeBs can connect to both EPC and 5GC, NR gNodeBs
S/P-GW
e nd
UPF/GW-U are connected to 5GC, and the CN access capability indication (EPC and
m m
c o 5GC) is broadcast through an air interface.
t re • When a UE accesses the RAN, it provides a NAS capability indication (EPC
n o
is NAS or 5GC NAS). The RAN selects EPC or 5GC based on the indication
4 /7
ion (EPC for a 4G-only UE and 5GC for a 5G UE).
p t • Access requests of subscribers who have not subscribed to 5G may be
NR OeLTE NR eLTE
rejected (based on network policies). In this case, the subscribers can try
Option 7 Option 2/4 EPC NAS access.
5G interface 4G interface

Summary of 5GC Deployment Solutions
Independent 5GC (N26- Heterogeneous Hybrid LTE Upgrade to eLTE and Dual
Solution MOCN All-Cloud Pool
based Interworking) Pool Connectivity
• New PLMN • (Recommended)

• MOCN enabled for Network-wide MME • Network-wide LTE upgrade to
Convergent gateway
Live network LTE (It is upgrade to support Convergent gateway eLTE (Option 4/7)
selection by all
reconstruction recommended that N26 selection by all MMEs • Simultaneous support for
MMEs
MOCN be enabled for • Convergent gateway option 7/4/2
2G/3G.) selection by all MMEs
• 4G SIM cards
• New SIM cards for 5G • 4G SIM cards reused
Subscriber • 4G SIM cards reused reused
subscribers • Large number of • 4G SIM cards reused
migration and • 5G UEs anchored to • 5G UEs anchored
• 5G UEs anchored to cross-pool • 5G UEs anchored to 5GC; no
4G/5G 5GC; no cross-node to 5GC; no cross-
5GC; no cross-node interworking, reducing cross-node interworking
interworking interworking node
interworking user experience
interworking
4G-only UEs connected All types of UEs

Existing EPC reused, and
Existing EPC reused, and to convergent 5GC, connected to Existing EPC reused, and 5GC
Resource 5GC capacity increase
5GC capacity increase which may reduce the convergent 5GC, capacity increase with 5G
efficiency with 5G subscriber
with 5G subscriber growth use efficiency of existing Balanced use of subscriber growth
growth
MMEs 5GC resources.
In option 2, solution 4 (heterogeneous hybrid pool) is recommended. In option 7/4 scenarios, solution
5 (eLTE and dual connectivity) is recommended.

4G USIM Cards Reused in 5G Networks
USIM Card Stored Information and
EPC USIM Card 5G USIM Card Same
Functions
Subscriber ID IMSI IMSI Yes

Stored
information
Key Ki Ki Yes
EPS-AKA* (5G AKA; AUSF secondary

Authentication
EPS AKA authentication) Yes
algorithm
EAP-AKA’
Service logic
USIM cards must support IMSI encryption to

IMSI
prevent IMSI information from being intercepted
privacy NA No (new in 5G)
from the air interface during subscriber
protection
registration.
Suggestion: Existing 4G USIM cards are reused on 5G networks to support 4G subscriber migration. New
subscribers use 5G USIM cards so that enhanced functions are supported.

Converged Subscriber Data Management, Reusing 4G USIM Cards or
Phone Numbers
5G subscriber management characteristics
HSS/UDM/AUSF (1) The HSS/UDM uniformly manages subscribers from different types of
HSS access networks.
(2) The unified authentication frame, authentication calculation, and

MME MME AMF SMF authentication vector distribution prepare for the exposure of 5G
network authentication capabilities.
Terminal
Access EPC NGC
Network
4G 4G 5G SUPI(Subscription Permanent Identifier),
3GPP IMSI, MSISDN GPSI(Generic Public Subscription
Subscriber Identifier)
identifier
Non-3GPP, SUPI
IMSI
3GPP
EAP-AKA'/EPS-AKA*(5G AKA)
3GPP EPS AKA Note: EPS AKA* enhances the control of
Converged subscriber data management Authenticatio
n algorithm
subscriber authentication in the home
• Data consumers and providers directly communicate with Non-3GPP, EAP AKA/EAP location. There is no new requirement for
3GPP AKA' USIM cards.
each other and obtain subscription data as required.
• A unified authentication framework is used to enhance home
location processing during subscriber authentication, Note: The 5G USIM card has the IMSI privacy protection mechanism
preventing roaming fraud (5G AKA). (optional function). The IMSI encryption function can be enabled for newly
issued cards.

Evolution and Network Construction Solutions for the HSS Inventory
Market in Different Phases
Phase 1: Evolution Towards Cloud-based Phase 2: Evolution Towards
Phase 3: Evolution Towards SA
Networks NSA
Scenario 1: Existing ATCA-based
Provisioning HSSs on the live network: Provisioning
Newly deployed cloud-based UDM,
hybrid networking
BE BE ATCA ATCA UDR UDR
ATCA ATCA vBE vBE BE BE
BE BE
FE FE ATCA ATCA
ATCA ATCA
vFE FE FE UDM UDM
FE FE vFE
STP/DRA/MME STP/DRA/MME AMF SMF

STP/DRA/MME
Scenario 2: Existing cloud-based HSSs:
Upgrade+Reconstruction (details to be added)
• Use the hybrid networking solution, uniformly • Upgrade the existing ATCA-based • Hybrid networking of existing ATCA-based HSS
provision services, and automatically migrate or cloud-based HSSs to HSS+ 19.1 and 5G UDM, assuring smooth evolution
subscribers to the cloud-based platform by to support high bandwidth • Cloud-based HSS software version upgrade+One-
segments. subscription and dual connectivity click UDM reconstruction
authorization.

Phase 1: Evolution Towards Cloud-based Networks
Solution
Subscription data of Migrated subscribers  Upgrade the existing ATCA-based devices to 19.1, and deploy dual-DC CloudDB (19.1).
subscribers with with inventory
 FE full mesh for cloud-based and legacy ATCA-based devices, BE full mesh for cloud-based and legacy
existing segments segments + new
subscribers Provisioning devices.
 The provisioning system is connected to the cloud-based BE.
 The STP/DRA/MME/MSC creates links to the cloud-based FE and enables service provisioning by
Cloud- Cloud- segments.
ATCA BE ATCA BE
based BE based BE  After all existing subscribers are migrated to the cloud-based platform, the ATCA-based devices retire from
the network.
Notes: The cloud-based BE can inherit the provisioning commands of the BE. The provisioning system does not
Cloud- Cloud-
HSS FE HSS FE based FE based FE need to customize the provisioning commands.
Capacity Planning Principles for Cloud-based Sites

 New subscribers and their services (expanded capacity) are provided by the cloud-based platform.
STP/DRA/MME
 Cloud-based platform capacity = Number of new subscribers + Number of subscribers to be migrated
 The capacity of existing sites where ATCA-based devices are deployed does not need to be changed.

Phase 3: Evolution Towards SA Using Existing ATCA-based Devices
Solution
Provisioning
 Upgrade the existing ATCA-based devices to 19.1.
 Newly deploy dual-DC 5GC UDMs (20.X or later)
 FE full mesh between UDM and ATCA-based devices, BE full mesh between UDM and ATCA-based devices
ATCA BE  The provisioning system switches to the UDR access mode.

ATCA BE UDR UDR
 The STP/DRA remains service routes unchanged and still routes 4G services of existing subscribers using
legacy number segments to HSS FEs.
 The STP/DRA routes only services of subscribers using new number segments to the 5GC UDM
HSS FE HSS FE UDM UDM

Notes: The UDR can inherit the provisioning commands of the BE. The provisioning system does not need to
customize the provisioning commands.
STP/DRA/MME AMF SMF

Capacity Planning Principles for 5GC Sites
 5GC UDR storage: Discrete new subscriber data with inventory segments + 5G SA subscriber data with
inventory segments + Subscriber data with new segments
 5GC platform capacity = Number of newly registered subscribers + Number of existing subscribers that have
registered with 5G SA
 The capacity of existing sites where ATCA-based devices are deployed does not need to be changed.

Convergent 5GC Networking Key Points
 NSA phase
Hybrid pool Hybrid pool • Upgrade existing NEs and introduce cloud-based devices to support NSA access
and prepare for cloudification.
HSS+ HSS+UDM PCRF+PCF PCRF+ • Introduce cloud-based CUPS gateways to deploy a distributed network
architecture.
 SA phase
N26
MME+ MME+AMF GW-C+SMF • Upgrade software of cloud-based NEs to support 5GC. Cloud-based and
Hybrid pool CUPS traditional NEs form a hybrid pool.
N4
S1-C S1-C/N2 convergent  Key solutions: smooth subscriber migration and 4G/5G interworking
S/PGW
S/P-GW GW-U+UPF gateway pool
• The eLTE/NR selects the MME and AMF based on UE capabilities.
• The MME selects gateways based on UE capabilities and subscription
S1-U S1-U/N3 information, to support flexible deployment of 5G gateways. For example, the
MME selects a traditional gateway for a 4G UE and a CUPS convergent gateway
LTE LTE NR eLTE NR
for a 4G/5G UE.
• The MME is upgraded to support the N26 interface and 4G/5G handovers.
4G 4G 5G 4G 5G
EPC+ UE • Hybrid pools are provided. 5G subscriber data migration and IMSI/MSISDN-
EPC UE 5GC UE
(dual connectivity)
based routing are supported.

Summary
 For 4G/5G interworking, it is recommended that MME upgrades support the N26 interface to ensure service
continuity experience.
 Four types of NE convergence suggestions:
 Subscriber data: HSS+UDM convergence to ensure subscriber data consistency;
 Strategy data: PCRF+PCF convergence to ensure policy consistency and continuity;
 User plane: SMF+PGW-C convergence, UPF+PGW-U convergence, mobile anchor point invariance
guarantees data continuity;
 AMF and MME deep convergence
 Option 2 recommended for the MME/AMF convergent pool solution

Contents

Inheritance and Convergence Evolution of 4G CUPS Architecture in
5G Gateways
EPC CUPS Network Architecture 5GC Network Architecture  Inherited protocol: The Sxa/Sxb and
N4 interfaces use PFCP.
HSS UDM
 Simplified architecture: The S-GW
MME PCRF AMF PCF and P-GW are integrated.
 Enhanced capability: MEC and
SGW-C PGW-C SMF(S/PGW-C) uplink classifier (UL CL) are
Sxa Sxb N4 supported.
 Convergent deployment: Smooth
SGW-U PGW-U UPF(S/PGW-U)
4G/5G handover is supported.
EPC CUPS 5G CUPS

Control plane: SGW-C/PGW-C Control plane: SMF
Network architecture
User plane: SGW-U/PGW-U User plane: UPF
Interface protocol Sxa/Sxb (PFCP) N4 (PFCP extension)
Independent and flexible CP/UP deployment
Key features Independent and flexible CP/UP deployment MEC and UL CL
Mobility enhancement (SSC mode 1/2/3)

5GC CUPS Deployment Suggestions
 SMFs/GW-Cs are deployed in centralized mode in multiple DCs for disaster recovery.
GW-U
SMF … SMF  UPFs/GW-Us are deployed distributively in different areas and work in load-sharing mode.
/GW-C /GW-C
Redundancy modes are selected based on scenarios.
Central 2
 Appropriate NE capacities balance resource efficiency, network reliability, and O&M
efficiency.
Regional  It is recommended that the capacity of an SMF/GW-C be no more than 10 million PDP
3 contexts and the UPF/GW-U throughput not exceed 200 Gbit/s per 1 million PDP
UPF
GW-U UPF
GW-U
GW-U
GW-U
UPF
1 contexts. More than 10 UPFs can be connected to each SMF.
GW-U
/GW-U /GW-U /GW-U
Service area 1 Service area 2 Service area 3
Large Capacity and Fewer Sites Small Capacity and More Sites
Redundancy Mode Advantage Application Scenario Simple networking and O&M Low network risks and high resource
Intra-area redundancy: Services There are a large number of
NE faults easily cause signaling storms. redundancy efficiency (N+1)
Good user experience Complex networking and O&M
on a faulty UPF/GW-U are taken UPFs/GW-Us in an area, and
1 because services are
over by other UPFs/GW-Us in the the N+1 redundancy efficiency
switched to near nodes
same area. is high.
…
There are a small number of
Cross-area central redundancy:
High resource usage UPFs/GW-Us in an area, and
2 Services on a faulty UPF/GW-U are
efficiency no direct transmission is
taken over by a central UPF/GW-U.
available between areas.
Redundancy between neighboring There are a small number of

Balance between
areas: Services on a faulty UPFs/GW-Us in an area, and
3 resource efficiency and
UPF/GW-U are taken over by a direct transmission is available
user experience
UPF/GW-U in a neighboring area. between areas.

Relationship Between User Plane Deployment Position and RTT
Assumed forwarding latency of a
single device: < 50 us Assumed fiber latency: 5 us/km
Access
Aggregation Core
About 30 km
About 100 km
About 250 km
Access Aggregation Metro Core

Transmission distance About 30 km About 100 km About 250 km
Prerequisites
Ring nodes 8 8 8
Total forwarding latency 50 x 8 x 1 = 400 us = 0.4 ms 50 x 8 x 2 = 800 us= 0.8 ms 50 x 8 x 3 = 1200 us= 1.2 ms
Calculation Fiber latency 30 x x 5 = 471 us = 0.5 ms 100 x x 5 = 1570 us = 1.6 ms 250 x x 5 = 3925 us = 3.9 ms
Results
RTT 0.9 ms 2.4 ms 5.1 ms
• Total forwarding latency = Forwarding latency of a single device (50 us) x Average number of hops on each ring (8) x Number of rings
on the transmission path
• Fiber latency = Transmission distance (km) x 𝜋 x Fiber latency (5 us/km)
• RTT = Total forwarding latency+ Fiber latency

On-demand Distributed Gateway Deployment to Meet Latency
Requirements of Various Services
Edge DC (about 30 km) Regional DC (about 100 km) Central DC (about 250 km)
ACC MEC/UP AGG MEC/UP Metro EPC/M-IoT
Base station
0.9 ms
2 ms (eMBB; unidirectional) 2.4 ms
0.4 ms (uRLLC; unidirectional)
5.1 ms
Position Edge DC (ms) Regional DC (ms) Central DC (ms)

Transmission latency (base
station-gateway)
0.9 2.4 5.1 Standard Latency Requirements of
Typical 5G Services
Latency UE <-> Base Base Station Standards

UE Processing Gateway App Processing Base Station <-> 5G Latency
Service Requirement Station RTT Processing Position Compliance
(ms) Processing (ms) (ms) Gateway RTT (ms)
(ms) (ms) (ms)
V2X 3 ms to 10 ms TS 22.186
eMBB 10 0.5 2x2=4 0.5 0.5 1 < 3.5 ms (10 – 6.5) Regional DC
eMBB 10 ms TR 22.863
V2X 3 0.2 0.4 x 2 = 0.8 0.2 0.2 0.5 < 1.1 ms (3 –1.9) Edge DC mMTC Latency-insensitive TR 22.861

Gateway Deployment at an Edge DC, Reducing Transmission
Bandwidth Used by Multicast Services
IPTV IPTV Multicast replication point
Edge Edge
Edge DC (30 km) Regional DC (110 km) Central DC (230 km) Internet
UE
ACC MEC/UP AGG MEC/UP Metro Cloud EPC

/M-IOT
Base station IPTV
STB/PC Center
100 Gbit/s x n x m 2 Gbit/s
100 Gbit/s x m 2 Gbit/s
100 Gbit/s 2 Gbit/s
IPTV channels (number of multicast groups): 200

IPTV Replication Point Access Ring Bandwidth Aggregation Ring MAN Bandwidth
Average bandwidth of a multicast group: 10 Mbit/s Position (Gbit/s) Bandwidth (Gbit/s) (Gbit/s)
Number of subscribers in an edge DC: 10,000
Edge DC 100 2 2
Central DCs:Regional DCs = 1:n
Regional DC 100 100 x m 2
Regional DCs:Edge DCs = 1:m
IPTV center -> multicast replication point: 200 x 10 Mbit/s Central DC 100 100 x m 100 x n x m
= 2 Gbit/s
For multicast services (IPTV and V2X), a gateway functions as the multicast replication point. If the
Multicast replication point -> UE: 10,000 x 10 Mbit/s =
gateway is deployed nearer to the network edge, fewer transmission resources are used.
100 Gbit/s

Downward Gateway Deployment with CDN, Saving Transmission
Resources, Reducing Latency, and Improving User Experience
ACC AGG Metro

MEC/UP Core DC
CDN
Test conditions
CDN
EPC Service Required Tested Air
Bandwidth Interface Provincial
720p 1.5 Mbit/s 15 Mbit/s MAN edge backbone
1080p 2.5 Mbit/s 15 Mbit/s Lower latency

VR 26 Mbit/s 35 Mbit/s Less transmission bandwidth required
CDN MEC
MEC+CDN test result of a tier-1 operator in China:
KPI SD Video (720p) HD Video (1080p) VR Video
UE
Video download rate 14.71% ↑ 47.41% ↑ 7.76% ↑
RTT 19.04% ↓ 32.58% ↓ 27.10% ↓
Drag delay 61.18% ↓ 14.65% ↓ 12.12% ↓
If gateways are deployed together with a CDN at the network edge, fewer transmission resources are required, and the transmission latency is reduced.

Mobility and Transmission Path Optimization in Distributed User
Plane Deployment
Core
MME/AMF GW-C/SMF MME/AMF GW-C/SMF
Central
AGG
Regional
Other
Service area 2 Service area A provinces
Service area 1
UPF UPF
GW-U
GW-U GW-U UPF
GW-U UPF
GW-U
ACC /UPF
/UPF /UPF /UPF /UPF
Downward UPF deployment must

balance mobility and roundabout 3
transmission paths.
1 2
Mobile Scenario Impact on User Planes Deployment Requirement
Movement within a
1 GW-Us/UPFs remain unchanged. The eNodeBs in the service area are fully interconnected with GW-Us/UPFs.
service area
Interconnection between UPFs in neighboring service areas. Direct links are
Movement across
2 Two-level UPF interconnection recommended so that packets do not need to pass through the backbone
service areas
network.
Home-routed: two-level interconnection between the vSMF/hSMF

Inter-province
3 and vUPF/hUPF Cross-province interconnection between SMFs and between UPFs
roaming
Local breakout: re-attach and PDU session activation
SSC modes (1/2/3) are introduced in 5G. UPF relocation can be performed based on service requirements, and transmission paths in mobile scenarios are optimized.

Flexible User Plane Selection Based on Services, Load, and Locations
Gateway selection by an MME: The original processing remains
unchanged because the MME is unaware of CUPS.
MME/AMF GW-C/SMF
SMF selection by an AMF: The AMF selects SMFs based on DNNs,
Central slice IDs, load, and access types.
Regional
Service slices
GW-U/UPF UPF
GW-U/UPF GW-U GW-U UPF UPF UPF
UPF UPF UPF UPF
/UPF /UPF
Near user plane selection User plane selection IPv6 user plane SSC user plane 5G dedicated user ...
based on access locations based on selection based on selection based on plane selection
and dynamic load APNs/DNNs and session types SSC modes based on access
slice IDs types
SGW-U  Location- and slice-based user plane deployment

UP PGW-U Selection
Selection by an UPF Selection by an SMF
Selection by a PGW-C
SGW-C (1) Service-slice-based user plane deployment: Independent user planes are
planned for VoLTE, MBB, enterprise APN, and IoT. User planes are
selected based on services and dynamic load.
APN (optional),
APN, location area, DNN, location area, dynamic
Reference location area, (2) Location-based distributed user plane deployment: User planes are
dynamic load, and load, session type, SSC mode,
factors dynamic load, deployed in different areas and selected based on subscriber locations
weight access type, and slice ID
and weight (TAs).

Q&A
 Question 1: What are the factors that need to be considered in the deployment of the UPF?

Contents

Two 5GC Voice Solutions
Solution 1: VoNR Solution 2: VoLTE EPS Fallback
Data IMS IMS
Voice
5GC EPC
5GC EPC
Voice over LF (for example,

Data over HF 700M/800M) NR (HF) LTE
NR LTE
Solution 1: VoNR Solution 2: VoLTE EPS Fallback

Good NR coverage, for example, NR low-frequency coverage; Low NR coverage requirements, for example, high-frequency hotspot coverage;
Suggested scenario
used for voice and mMTC used to improve eMBB capacity
Discussed and approved in standard R15 (The specific solution is being
Standards Standard R15
developed.)
Data service Inconsistent. Data falls back to 4G during a call, affecting high-speed data
Consistent. Data services are kept on 5G during 5G calls.
experience service experience (such as video service).
Voice connection 3s-4s. Inter-system measurement and handover are added during a fallback to
1.5s-2s
duration LTE.
Network The IMS adapts to 5G access (such as NR access and 5G cell
NR and 5GC support 4/5G handovers triggered by voice services.
requirements information) and domain selection.

SMS Solution Evolution
SMS messages of mobile users are sent to the IMS domain. Data cards and IoT SMS messages are sent to the PS domain.
HSS
IMS
Vo5G 5GC S6c
5G SGd
CPE
VoLTE CSCF IP-SM-GW SMSC

AMF SMSF SMSC
• The VoLTE/Vo5G message continues to be carried by the IMS. Therefore, the • The CPE supports PS only SMS messages.
SMSF is not required in the 5GC. • The SMSF needs to be added to the 5GC. In addition, the SMSC has enabled the
• The VoLTE network supports future Vo5G SMS messages. SGd interface to communicate with the SMSF, and the SMSC has enabled the S6c
interface to communicate with the HSS.
IP-SM-GW is used for protocol conversion.

HSS
5GC
5G SGd
• The SMSC does not need to be reconstructed.
CPE
• The IP-SM-GW can convert the SGd interface and the
AMF SMSF IP-SM-GW SMSC original MAP interface.

Contents

Contents
4.1 Evolution of Network Cloudification
4.2 Infrastructure Planning

Four Principles of Evolution: Continuous Service, Optimal Signaling,
Convergent Access, and Simplified OAM
Continuous service Optimal signaling Convergent access Simplified OAM
Internet HSS/UDM EMS EMS CG L PCF …

I
Location update signaling
Handover
signaling MME
MME Convergent CP Convergent CP
Convergent CP
EPC GW-U
4G 5G Convergent UP
LTE NR
LTE NR
Massive Small Coverage Small Coverage
Massive
Handover
Handover Convergent UP
IP anchors unchanged The control plane remains Core Network Convergent Control plane and user
during handover unchanged Pool plane separation
• In each evolution phase the • Reduce external signaling • A RAN in a location area only needs • Centralized interfaces and control
LTE, NSA, and SA terminals consumption to access one pool to avoid network plane, simplified operation and
maintain the unique anchor • Increase handover success rate selection problems maintenance,
point and IP address during • Simplified operation and • In the pool coverage, the control • User plane deployment for flexible
handover between maintenance plane remains unchanged distribution.
2G/3G/4G/5G. • Smooth migration of users
Key Technology: 2G/3G/4G/5G Key Technology: 2G/3G/4G/5G Key Technologies: 2G/3G/4G/5G Key technology: centralized
convergent user plane convergent control plane convergent control plane pool control plane convergence

Network Evolution Proposal: Two Phases and Three Steps Towards
One Converged 5G Target Network
SAE-GW MME
3 Phase1:Cloudification+NSA
Pool
2G/3G
2
GW-U Sx 6
4 vHSS vPCRF vDRA
NB-IoT 3 GW-C vMME
Sx
GW-U Cloud 1
7
OS Telecom Cloud
Unified
LTE
5 AMF SMF UDM MME Phase2: 5G
Service Chain
MEC Slicing
mCDN URF PCF AUSF AF
NR IP Metro Convergent UP IP Core
Cloud OS Cloud OS
Converged UP
Unified Telecom Cloud Unified Telecom Cloud
Edge Region Center
1 Unified telecom cloud, IaaS 2 PNF VNF convergence pool 6 Convergent control plane
convergence
GW dedicated hardware and user 2G/3G/4G/5G all-access
3 7
plane upgrade
4 CUPS 5 MEC (V2X)
Step1 Step 2 Step 3
2018 2019 2020

Step 1: Deploy One Unified Telecom Cloud to Implement the Agile,
Open, and Flexible Infrastructure
Select the vendor according to service
Network Function vEPC 3rd App type
Layer APP
• Stateless, efficient, and flexible
MME S/PGW PCRF App1 App2 App3
services
• Cross-DC deployment for greater
Stable support for multiple flexibility and reliability
telecommunication services • Flexible, hitless upgrades,
Virtual
dramatically accelerating TTM
Virtual ComV Virtual
StoVrairgteual NetVwiortrukal
piruttueal
StoVrairgteual NetVwiortrukal
ComVpiruttueal
Virtualized Layer Compute Storage Network
• Single vendor in a single area
• Uniform allocation of resources
Cloud OS throughout the region
• Upward support for multiple
Mature, open and compatible cloud OS is the core element of NFV unified
tenants
telecom cloud.
• Downward guarantee of hardware
independence
Hardware
Infrastructure
Multi-vendor COTS, flexible purchase
Multiple regional DCs

Step 2: PNF and VNF Hybrid Pool Smoothly Introduce NSA EPC+
Unified planning of
Reusing interface links
capacity
Internet NSA IoT
Multi- GGSN/PGW GGSN/PGW  Reuse interface links of Due to the uncertainty of the
Services devices such as handover between the networks
HSS/PCRF/AAA and the large changes, it is very
 No interface modification difficult to assess the capacity
such as S1, no need to add of VNF and PNF separately.
interfaces such as
Ga/S11/S6a
One Core NSA SGW HSS PCRF DRA
- Reusing interface links Handover signaling
- Unified planning of capacity Smooth user migration
- Smooth user migration
reduction
- Handover signaling reducing The initial coverage of the NR is
In the Converged Pool, the users
- Unified management and small, UE access the same
move smoothly and the
maintenance converged MME within pool.
- NFV reliability NSA MME NSA traditional equipment exit
4G/5G handover between pools
naturally along with the life
vMME cycle
becomes intra-system handover
and reduces the cost of signaling.
NR Unified management
NFV reliability
ONE LTE and maintenance
- Co-site 2/3/4/C-IOT NR NR Pools in the same manufacturer can
- Unified planning  Simple network structure
 Simple commissioning do migration within the pool
 Simple operation and without service interruption.
At the beginning of stage 1 NSA, NR is deployed in
small quantities, covering small areas. maintenance
 Simple troubleshooting

Step 2: The MEC Combines the C/U Separation Architecture to
Support the Smooth Network Evolution Towards 5G
Step 1: Gateway deployment optimization Step 2: Gateway CUPS reconstruction Step 3: 5GC C/U convergence
MME PCRF AAA DHCP MME PCRF AAA DHCP

Center … …
EPC GW GW-C 5G Convergent CP
5G
5G 5G Convergent
Region GW-U GW-U GW-U Convergent Convergent UP
UP UP
Edge
5G Convergent UP
Edge GW Edge GW (ULCL/BP) …
MEC CUPS 5G C/U Evolution

Advantages: Advantages: Advantages:
• User experience improvement • Reduced interface • Unified policy and control
• Improve transmission efficiency • Centralized configuration • More agile deployment
• Reduce network node types
• Converged control plane and user plane

Step 3: The Cloud Core Smoothly Evolution to NGC and
2G/3G/4G/5G Converges One Core network
URLLC
Target NGC mMTC Charging Service Awareness
2G/3G eMBB
Gb/Iu
Convergent CP Mobility Mgmt. QoS
SMF Policy Control Forwarding

2G/3G/4G AMF
eNB Function
Subscriber DB Optimizer
S1
Device Mgmt. Session Mgmt.
SBA based Repository Function(extensible)
eNB---NR UDM PCF Other LBO (UL CL/BP) Classifier

Function
S1
2G/3G/4G Other Function
function
NR
• NGC has ability of
NG2/NG3 all kinds of access
NR---E-eNB
• Modularly
Unified programmable to meet
E-eNB---NR Auto Deploy Auto Scale
user plane agile deployments of
Health Check Load Balance diverse slices

Contents
4.1 Evolution of Network Cloudification
4.2 Infrastructure Planning

5G Network Target Architecture
Fully Convergent Cloud-based Service Based Distributed Architecture E2E Network Slices
Network Architecture (SBA) CUPS/MEC On-demand generation of
2G/3G/4G/5G convergence Microservice components; Centralized control plane slices to meet service
Cloud Native software on-demand deployment and requirements in different
flexible orchestration Distributed DCs scenarios
Unified telecom cloud infrastructure
mMTC Slice UPF 5GC-CP
eMBB Slice UPF Gi-LAN CDN 5GC-CP
UPF MEC 5GC-CP

URLLC Slice
Edge DC Regional DC Central DC

RTT < 5 ms RTT < 20 ms RTT < 50 ms
CU UPF MEC UPF Gi-LAN CDN UPF 5GC-CP
MANO
Fiber Cloud OS Cloud OS Cloud OS
CSG CSG
ACC AGG Metro
Microwave

Microservice-Centric Architecture (MCA) for Implementing Cloud
Native and 5G SBA
CloudNative
Horizontal
data processing
decoupling
+ +
Separation of
decoupling
Vertical
Service logic
decoupling Agile Automatic
infrastructure life cycle
Monolithic software MCA software
Appropriate design in a specific (1) Microservice instantiation and scaling

environment can maximize maximize resource efficiency. (2) Too
Resource
efficiency. If the environment small granularities will increase basic
efficiency
changes, huge resource waste may overhead and cross-service
occur. communication overhead. MCA Characteristics
• Service self-governance, self-containing, and self-management
Development and maintenance (1) A full-function team maintains
complexity increases rapidly with microservices, improving development • Independent service development states and separate platform and
Maintenance language selection
software volume. Appropriate design and O&M efficiency. (2) Too many details
efficiency • Independent service running states and independent upgrades
can simplify end users' operations. will increase management and
maintenance costs. • Contractual interfaces between services
Agility Weak. Agile release is not supported. Excellent. Good decoupling significantly Three Principles of Microservices
improves agility.
• Independent life cycle
Performance Excellent. Good performance is Medium. Too small granularities will • Independent resource scaling
usually provided. increase latency. • Independent optional components

VM Containers Recommended, Improving O&M Efficiency and
Supporting MCA Implementation
Container-based VNF Container-based VNF Container-based VNF
Existing Existing
VNF VNF
Container platform Container platform Container platform
VM Bare-metal device VM Pure Bare metal

IaaS IaaS
VM Container NFVI Extended Bare-Metal Container Pure-Bare-Metal Container
Infrastructure sharing with existing
Yes Yes No
VNFs
No. The container platform is integrated with
Container platform decoupled from No. The container platform needs to
Yes. The NFVI platform shields hardware. the NFVI, and the NFVI is coupled with
hardware infrastructure manage hardware infrastructure.
hardware.
Yes. The NFVI provides multi-vendor integration
No. Container platforms are still in quick development. Multi-vendor integration is difficult
Multiple-vendor integration capabilities, and different vendors can use their
before container platforms are standardized.
own container platforms.
Security isolation of containers from VMs are used to isolate containers. This enables Physical machines are used to isolate tenants. This method is not as flexible as container
multiple vendors security isolation between tenants. isolation by VMs.
Performance Similar to VM performance Similar to physical machine performance
Reliability Container OS faults are within VMs. Container OS faults are within bare-metal devices.
VM capabilities can be used to implement
Resource management flexibility advanced functions, such as live migration of Advanced functions, such as live migration of containers, are unavailable.
containers.
Use VM containers because bare-metal containers do not support multi-vendor integration before they are standardized.

VNF Built-in Container Platform Recommended Because Container
Platforms Have Not Been Standardized
VNF VNFM VNF VNFM VNF VNFM
CaaS container platform
Impacts on peripheral NFVI VIM NFVI VIM NFVI VIM

devices/components
VNF Built-in Container Platform VNFM Integrated Container Platform VIM Integrated Container Platform
Container platform
A container platform can be shared by multiple VNFs of A container platform can be shared by multi-vendor VNFs. However, the
sharing and impacts on
the same vendor. This has no impact on peripheral VNFM or VIM will interwork with the VNFs, and its reliability and scalability
peripheral
modules in NFV architecture. need to be improved.
devices/components
Standardization is not required. This is internal ETSI NFV architecture needs to be enhanced and standardized, and container
Standardization implementation and is compatible with the existing platforms need to be standardized. Otherwise, multi-vendor integration is
cloud-based NFV environment. difficult.
Deployed on VMs:
Appropriate container Deployed on bare-metal devices,
•Hardware coupling and vendor lock-in are prevented.
deployment mode providing better performance
•VMs are used for security isolation between VNFs of different vendors.
Fast introduction: VNF built-in container management platform

Long-term evolution: VIM integrated container management platform

5GC Cloud-based Infrastructure – Enhancement and Evolution of
CloudEPC Infrastructure
OSS/BSS OSS/BSS
NFVO NFVO
VNF Layer VNF Layer
VNF1 VNF2 VNF3 VNF VNF1 VNF2 VNF3 VNF
M M
PaaS (container management)
Virtualization Layer Virtualization Layer

VIM &
VIM SDN
Hardware Resource Hardware Resource Controller
Computing Storage Network Computing Storage Network
 CloudEPC  Evolution: independent standard PaaS deployment

• Hardware, cloud OSs, and VNFs • Standard PaaS provides VM and container resources for VNFs. PaaS
are decoupled. can be integrated in the NFVI.
• VNF stateless design: Data • PaaS can run on VMs and bare-metal devices and mask bottom-layer
forwarding, service processing, and differences.
database decoupling • You are advised to use the VNFM to provision resources and mask
PaaS differences.
• SDN controllers are introduced to automate networks

Summary
 Three types of traffic steering modes and characteristics of NSA networking, evolution path
selection.
 Six deployment scenarios and features of the SA network.
 5GC network and infrastructure evolution.

Acronyms and Abbreviations
 5GC 5G Core Network
 5GS 5G System
 AUSF Authentication Server Function
 AMF Access and Mobility Management Function
 CP Control Plane
 DN Data Network
 NEF Network Exposure Function
 NF Network Function
 NR New Radio

Acronyms and Abbreviations
 NRF Network Repository Function
 NSSF Network Slice Selection Function
 PCF Policy Control function
 SBA Service Based Architecture
 SMF Session Management Function
 UDM Unified Data Management
 UDR Unified Data Repository
 UDSF Unstructured Data Storage Function
 UPF User Plane Function

References
 3GPP TS 23.501

Thank You
www.huawei.com

5G Core Network Deployment and Evolution Solutions ISSUE 1.7

Uploaded by

Copyright:

Available Formats

You might also like

5G Core Network Deployment and Evolution Solutions ISSUE 1.7

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 Network Deployment and Evolution Solutions ISSUE 1.7

Uploaded by

Copyright:

Available Formats

5G Core Network Deployment and

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

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

2. NSA Network Deployment and Evolution Suggestions

3. SA Network Deployment and Evolution Suggestions

4. 5GC Cloud Evolution

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

*Using option 3x as Option 2

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

EPC+ 5GC 5GC 5GC

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

Option 3/7 Option3a/7a Option 3x/7x

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

EPC EPC+ Cloud EPC+ EPC+

e c o ial a • URLLC and mMTC

n 4 EPC is introduced, forming hybrid

Network • Cloud-based EPC and CUPS • 4G/5G interworking

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

 Question 2: What are the options for NSA network evolution?

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

2. NSA Network Deployment and Evolution Suggestions

3. SA Network Deployment and Evolution Suggestions

4. 5GC Cloud Evolution

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

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

Extended QoS negotiation (a maximum of 4

NR access control and authorization NR access control and authorization

Identifying 4G/5G subscribers and

(Optional) UE Usage Type parameter

Large-bandwidth gateway selection based

5G voice Same as VoLTE* Same as VoLTE* Same as VoLTE* Same as VoLTE*

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

(Optional) 5G NR 5G subscriber and

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

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

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

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

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

eNB gNB eNB

5G NSA Option 3 4G VoLTE 2G/3G

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

NSA Option 3x – SCG Split (NR PDCP)

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

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

2. NSA Network Deployment and Evolution Suggestions

3. SA Network Deployment and Evolution Suggestions

4. 5GC Cloud Evolution

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

2. NSA Network Deployment and Evolution Suggestions

3. SA Network Deployment and Evolution Suggestions

3.1 5GC Control Plane Networking Scheme

3.2 5GC User Plan Deployment Principles

3.3 5GC SMS and Voice Solutions

4. 5GC Cloud Evolution

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

NF_A NF_B NF_A NF_B

SBA features • NF registration and deregistration

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

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