Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
evolution aspects
SMS and emergency calls
Paper – 5
2 Ericsson | 5G voice – network evolution aspects
Abstract
Copyright
© Copyright 2019 Ericsson AB. All rights reserved.
Disclaimer
SMS in 5GS
SMS stays an important use case also in 5GS. There are For SMSoIP, an IP-SM-GW must be present for
two methods to transport the SMS over the 5G access, originating and terminating SMS. This IP-SM-GW may
namely SMS over IP (SMSoIP) using IMS and SMS over also perform MT domain selection to other accesses
5G NAS (SMSoNAS). (4G, 3G, 2G), and the SMS transport between UE and
IP-SM-GW is via IP.
For SMSoNAS, originated and terminated SMS are
transport between UE and AMF via NAS. An SMSF has Both SMS over NAS and SMS over IP must be supported
been defined in 5GS for handling these originating and by a 5GS UE supporting voice, whereas each operator
terminating SMS, using MAP (or Diameter) for SMS has the freedom to decide whether to support SMS over
transport with SMS-C. NAS, SMS over IP or both. These SMS solutions can be
combined and can be used also in case EPS Fallback is
used for voice.
AMF SMSF
NR SMS-C
NG-RAN
SIP-
UPF SM-GW
IMSCore SMS over NAS
SMS over IP
SMS over IP
Figure 17 SMS in 5GS
4 Ericsson | 5G voice – network evolution aspects
Emergency call
In networks supporting EN-DC, emergency call is still supported and used over LTE connected to EPC. IMS and
PSAP are not aware of EN-DC.
ll
Ca
gency
er LTE EPC IMS PSAP
Em
NR
In 5GS, the 3GPP has specified four different behaviors NG-RAN. This solution is depending on the UE
for emergency call (denoted as solutions a) to d) access selection.
below), two of which are addressing new mobility
b) EPS Fallback – Service Request for emergency: This
cases compared to 4G. All emergency behaviors must
solution is new in 5GS, i.e., there is no equivalent
be supported by a UE while the support by the network
in 4G. The UE uses service-request for emergency
depends on operator and regulatory requirements. The
towards AMF if support for this feature has been
UE is made aware of emergency support by the AMF
indicated by the AMF. If receiving the service request
indicating to the UE that emergency service (see d)
for emergency, the AMF interacts with gNB to
below) or that service request for emergency (see b)
perform EPS Fallback. In this solution, there is no
below) is supported.
need for NR and 5GC to support emergency features
a) UE Reselection: at emergency attempt the UE other than needed for service-request for emergency
re-selects to E-UTRAN or other access providing handling. However, voice over NR (possibly including
emergency support if there is no local regulatory EPS Fallback) has to be supported on NR and 5GC
requirement to indicate emergency support on (otherwise the UE would not even camp on NR).
Ericsson | 5G voice – network evolution aspects 5
Registered
NR 5GC IMS PSAP
Figure 19 Emergency with (a) UE reselection to LTE and (b) EPS fallback with service request for emergency
c) EPS Fallback – QoS triggered for emergency: This d) Emergency call over NR: In this solution, NR is
solution is new in 5GS, i.e., there is no equivalent used for emergency communication with seamless
in 4G. In this solution (and like EPS Fallback for mobility between 5GS and EPS using IRAT
voice) the UE is falling back to Emergency call over handover. It requires that NR and 5GC support
LTE during emergency call establishment on 5GS, emergency features incl. impacts on GMLC/LRF.
when the network attempts to establish the QoS
flow for voice. NR and 5GC must support emergency
features incl. impacts on GMLC/LRF.
6 Ericsson | 5G voice – network evolution aspects
EPS
Fallback Emergency Call
(QoS)
Emergency
Call setup
Figure 20 Emergency over NR (d) incl. QoS triggered EPS Fallback for emergency (c)
Solutions a) and b) have no or very limited requirements and hence any regulatory requirement related to
regarding support of emergency related functionalities emergency PDU session, IMS registration and attempt
on 5GS since the emergency call is established on 4G. of IMS emergency call must be fulfilled equally.
Solutions c) and d) differ regarding whether the radio
bearer used for the voice media is established on NR
Ericsson | 5G voice – network evolution aspects 7
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)
eLTE LTE in NG-RAN connected to 5GC
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
I-MME Intermediate MME
KPI Key Performance Indicator
MME Mobility Management Entity in EPC
NG-RAN Next Generation RAN, RAN connected to 5G Core
NR New Radio
PCF Policy Control Function in 5GC
PGW PDN Gateway in EPC
RAN Radio Access Network
RAT Radio Access Technology eg. LTE, NR
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 – Solutions and
Architecture
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.
www.ericsson.com
ericsson.com The content of this document is subject to 15/287 01-FGD 101 073
revision without notice due to continued progress © Ericsson AB 2019
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.