Professional Documents
Culture Documents
evolution aspects
Voice over NR in a 5G System and migration
from Evolved Packet System Fallback
Paper – 3
2 Ericsson | 5G voice – network evolution aspects
Abstract
Copyright
© Copyright 2020 Ericsson AB. All rights reserved.
Ericsson | 5G voice – network evolution aspects 3
EPS fallback is an additional mobility trigger for • all needed voice features are not in place in the
improving voice KPIs by using the most suitable access phone.
technology at any given time. EPS Fallback enables
The coverage and deployment scenario for voice over
phones to use the 5GC with NR, and to register in
NR incl. EPS Fallback is as follows:
IMS, but RAN may trigger moving the phone to LTE
• NR coverage connected to a 5G Core, embedded in
connected to EPC during call establishment. The reason
• Wide-area LTE coverage controlled by EPC
for moving the UE to LTE can be
supporting VoLTE
• temporary lack of radio resources in NR for voice
• the UE is in area where NR in 5GS is not dimensioned
and tuned for voice
NR in 5GS
LTE in 5G EPS (voice)
Figure 11 Typical coverage scenario for voice in EPS and 5GS in early 5GS deployments using EPS Fallback
A smartphone (UE), connected to NR, that tries to establish a voice connection, may perform an EPS fallback
at call setup. EPS Fallback is triggered by the attempt to establish the Quality-of-Service (QoS) flow for voice
media in NR.
E-UTRAN MME+
SGw
SMF
EPS
Fallback
AMF
NR NNI
T UPF
NG-RAN IMS
At the attempt to establish the QoS flow for the voice The EPS fallback procedure adds time to the call setup
media over NR during call set-up, the NG-RAN rejects time which should be kept as short as possible.
the QoS flow setup towards the SMF with an indication
EPS fallback with inter-system handover is
that mobility is in progress. The NG-RAN initiates
recommended as soon as the required features are
transfer of all PDU sessions from 5GS to EPS, using one
available in RAN, 5GC and in phones, since it has
of the two standardized procedures:
superior performance.
• Release with redirect
• Inter-system handover
Terminology
5GC 5G Core
5GS 5G System, consists of 5GC, NG-RAN and UE
5G Voice IMS voice in the 5G system
AMF Access and Mobility Management Function
EN-DC E-UTRA NR Dual Connectivity (in RAN connected to EPC)
EPC Evolved Packet Core, 4G packet core
EPS Evolved Packet System consist of EPC and LTE RAN
gNodeB Node providing NR user plane and control plane protocol
terminations towards the UE
HSS Home Subscriber Server in 4G
IMS IP Multimedia Subsystem
KPI Key Performance Indicator
MME Mobility Management Entity in EPC
NG-RAN Next Generation RAN, RAN connected to 5G Core
NR New Radio
NSA Non standalone
PCF Policy Control Function in 5GC
PGW PDN Gateway in EPC
PSAP Public Safety Answering Point
RAN Radio Access Network
RAT Radio Access Technology eg. LTE, NR
SA Standalone
SEPP Security Edge Protection Proxy
SGW Serving Gateway in the evolved packet core
SMF Session Management Function in 5GC
UDM User Data Management in 5GC
UE User Equipment
UNI User Network Interface
UPF User Plane Function in 5GC
Contributors
The contributors to Ericsson’s opinions and recommendations on this topic are:
• Ralf Keller, Expert, Business Area Digital Services - Solution Area Packet Core
– Architecture & Technology
• Anders Ryde, Senior Expert, Business Area Digital Services –Architecture and
Technology
Ericsson enables communications service providers to
capture the full value of connectivity. The company’s
portfolio spans Networks, Digital Services, Managed
Services, and Emerging Business and is designed to help
our customers go digital, increase efficiency and find new
revenue streams. Ericsson’s investments in innovation
have delivered the benefits of telephony and mobile
broadband to billions of people around the world. The
Ericsson stock is listed on Nasdaq Stockholm and on
Nasdaq New York.
ericsson.com The content of this document is subject to 13/287 01-FGD 101 073
revision without notice due to continued progress © Ericsson AB 2020
in methodology, design and manufacturing.
Ericsson shall have no liability for any error or
damage of any kind resulting from the use of this
document.