Chapter 1................................................................................................................................

154
1. introduction to 5G..........................................................................................................154
1.1 5G Evolution toward 6G................................................................................154
1.2 Release 15............................................................................................................164
1.3 Release 16............................................................................................................164
1.4 Release 17............................................................................................................164
1.5 NR air interface.................................................................................................165
1.6 NR provides a flexible air interface........................................................165
1.8 Network slicing..................................................................................................171
1.9 5G Core Network Functions........................................................................173
1.10 Edge computing..............................................................................................174
Salient Features of 5G...........................................................................................175
1.11 Key benefits with 5G....................................................................................176
1.12 Speed upgrades..............................................................................................176
1.13 Low Latency.....................................................................................................177
1.14 Enhanced capacity........................................................................................177
1.15 increased bandwidth....................................................................................178
1.16 5G availability and network coverage................................................178
1.17 5G LAN.................................................................................................................180
1.19 Critical Medical Applications..................................................................183
1.20 5G V2X.................................................................................................................185
1.21 Unmanned Aerial Vehicle or UAV.........................................................187
1.22 Audio-visual production..............................................................................188
1.23 Cyber-Physical Control Applications...................................................189
1.24 Haptic Service...............................................................................................194
1.25 Miscellaneous services..............................................................................195
1.26 NR Enhanced 15.............................................................................................197
1.27 NR Unlicensed (NRU)...................................................................................199
1.28 URLLC enhancements.................................................................................201
 1.29 Industrial Internet of Things (IIoT).......................................................203
1.30 New frequency band.....................................................................................204
Chapter 2................................................................................................................................210
2. New Radio: Architecture...............................................................................................210
2.1 Overview of the NG-RAN Architecture..................................................210
2.2. Architecture Options and Migration Paths........................................212
2.3 NR gNB Connected to the 5GC (Option 2)...........................................213
2.5 Multi-RAT DC with the 5GC, NR as Master (Option 4)...................214
2.6 LTE ng-eNB with to the 5GC (Option 5)................................................214
2.7 Multi-RAT DC with the 5GC, E-UTRA as Master (Option 7)........214
2.8 Migration Considerations.............................................................................215
2.9 G NR Base Station (gNB) Architecture.................................................216
2.10 Higher Layer Split (HLS) of the gNB....................................................217
2.11 Separation of CP and UP with Higher Layer Split (HLS)...........220
2.12 Xx Interface Family.......................................................................................221
2.13 NR Radio Interface Protocol....................................................................222
2.14.1 Service data adaptation protocol (SDAP)............................................................223
2.15 Control plane....................................................................................................225
Chapter 3................................................................................................................................228
3. NR Radio Access Technology........................................................................................228
3.1 overview of the NR radio access technology....................................228
3.2 NR KEY FEATURES..........................................................................................229
3.2.1Higher frequencies and spectrum flexibility......................................................229
3.2.2 Ultra-lean design..................................................................................................230
3.2.3 Transmission scheme, bandwidth parts, and frame structure........................231
3.2.4 Duplex schemes....................................................................................................235
3.2.5 Low latency support............................................................................................237
3.2.6 Scheduling and data transmission......................................................................238
3.2.7 Control channels..................................................................................................240
3.2.8 Beam-centric design and multi-antenna transmission.....................................242
3.2.9 Initial access........................................................................................................245
3.3 Interworking and LTE coexistence..................................................246
Chapter 4................................................................................................................................249
4.1 Introduction to VoNR......................................................................................249
4.3 Voice services in an NSA.............................................................................262
4.4 Voice services using EPS fallback..........................................................265
4.4.1 Network interworking requirements supporting voice services......................265
4.4.2Registration procedure – aspects for voice support..........................................268
4.4.3 5G IMS support...................................................................................................272
4.4 .4 EPS fallback........................................................................................................282
4.5 Voice services using NG-eNB....................................................................290
4.6 Voice services with RAT fallback............................................................292
4.7 Voice over NR (VoNR)..............................................................................295
4.7.1 VoNR radio parameter support recommendation............................................298
4.8 Network deployment and connectivity options supporting voice
............................................................................................................................................301
4.10 Supplementary Voice Service, Emergency Call and SMS........311
4.10.1 Supplementary Voice Service...........................................................................311
4.10.2 SMS in 5G...................................................................................................312

FIGURE1. 2:4G AND 5G ARCHITECTURE.....................................................................................................................166

FIGURE1. 3 NON-STANDALONE 5G...........................................................................................................................166
FIGURE1. 4 DATA EXCHANGE OVER NON-STANDALONE 5G...........................................................................................167
FIGURE1. 5STANDALONE 5G WITH SBA....................................................................................................................167
FIGURE1. 6 5G RAN..............................................................................................................................................168
FIGURE1. 7: SBA IN 5G......................................................................................................................................... 169
FIGURE1. 8: NETWORK FUNCTION OPERATION............................................................................................................169
FIGURE1. 9: NON-STANDALONE 5G RELIES ON A 4G CORE, WHILE STANDALONE 5G USES A 5G CORE...................................170
FIGURE1. 10 :5G NETWORK SLICING........................................................................................................................171
FIGURE1. 11: 5G NETWORK SLICING........................................................................................................................171
FIGURE1. 12 5G NETWORK SLICING ON PHYSICAL LAYER...............................................................................................172
FIGURE1. 135G NETWORK SLICING..........................................................................................................................173
FIGURE1. 14 EDGE COMPUTING...............................................................................................................................174
FIGURE1. 15: FEATURES OF 5G TECHNOLOGY.............................................................................................................175
FIGURE1. 16: EVOLUTION TO 5G.............................................................................................................................178
Y

FIGURE2. 1:5G NG-RAN INTERFACE........................................................................................................................210

FIGURE2. 2:OVERALL NG-RAN ARCHITECTURE...........................................................................................................211
FIGURE2. 3: OVERALL LTE (E-UTRAN)-NR DC ARCHITECTURE.....................................................................................213
FIGURE2. 4:FUNCTION SPLIT ALTERNATIVES................................................................................................................216
FIGURE2. 5:HIGHER LAYER SPLIT OF THE GNB.............................................................................................................217
FIGURE2. 6: OVERALL RAN ARCHITECTURE WITH CU-CP AND CU-UP SEPARATION.NG-RAN KEY INTERFACES AND PROTOCOLS
................................................................................................................................................................. 220
FIGURE2. 7:XN AND X2 PROTOCOL STACKS.................................................................................................................221
FIGURE2. 8:USER PLANE PROTOCOL STACK.................................................................................................................223
FIGURE2. 9:NR RRC STATE MODEL...........................................................................................................................225
FIGURE2. 10:CONTROL PLANE PROTOCOL STACK........................................................................................................226
FIGURE3. 1:NR SPECTRUM......................................................................................................................................232
FIGURE3. 2:NR TIME-DOMAIN STRUCTURE.................................................................................................................234
FIGURE3. 3...........................................................................................................................................................247

FIGURE4. 1:DEPLOYMENT SCENARIOS SUPPORTING VOICE IN 5G....................................................................................262

FIGURE4. 2:DEPLOYMENT SCENARIO EN-DC SUPPORTING VOLTE AND INTERNET SPLIT BEARER NR AND LTE.........................265
FIGURE4. 3:REFERENCE POINTS BETWEEN EPC, 5GC AND IMS TO ENSURE TIGHT INTERWORKING FOR VOICE SUPPORT............268
FIGURE4. 4:VOICE REGISTRATION PROCEDURE.............................................................................................................270
FIGURE4. 5:PROTOCOL LAYER OF MTSI.....................................................................................................................280
FIGURE4. 6: PDU SESSION ESTABLISHMENT OF IMS VOICE............................................................................................282
FIGURE4. 7: EPS...................................................................................................................................................284
FIGURE4. 8: EPS RESERVED SIGNALLING MESSAGE FLOW (TS 23.502)............................................................................286
FIGURE4. 9: EPS...................................................................................................................................................288
FIGURE4. 10: EPS FALLBACK SIGNALLING SCENARIO EXTRACT FROM THE R&S®CMX500...................................................290
FIGURE4. 11: VOICE SERVICES USING NB-ENB............................................................................................................291
FIGURE4. 12: RAT BACKUP SUPPORTING VOICE SERVICES..............................................................................................293
FIGURE4. 13: IMS VOICE RAT DELAY.......................................................................................................................294
FIGURE4. 14: VOICE NR (VONR).............................................................................................................................296
FIGURE4. 15: VOICE MESSAGE FLOW OVER NR...........................................................................................................298
FIGURE4. 16: VOICE OVER NR RADIO LAYER REQUIREMENTS NR....................................................................................300
FIGURE4. 17: NETWORK OPTION 3 FOR NSA (EN-DC) SUPPORTING VOICE SERVICES....................................302
FIGURE4. 18: NETWORK OPTION 7 FOR NSA (NGEN-DC) SUPPORTING VOICE SERVICES...............................303
FIGURE4. 19: NETWORK OPTION 4 FOR NSA (NE-DC) SUPPORTING VOICE SERVICES....................................304
FIGURE4. 20: NETWORK OPTION 2 FOR SA SUPPORTING VOICE SERVICES.......................................................305
FIGURE4. 21: TRANSITION SCENARIOS FROM VOLTE TO VONR IN RELATION TO NETWORK DEPLOYMENT SCENARIOS [REF. 2]
................................................................................................................................................................. 306
FIGURE4. 22: EVOLUTION OF AUDIO BANDWIDTH.......................................................................................................307
FIGURE4. 23: EVS MODE, AUDIO BIT RATE AND BANDWIDTH.........................................................................................309
FIGURE4. 24: AUDIO PROCESSING FUNCTIONS OF EVS CODEC, TX SIDE (TS 26.441)........................................................310
FIGURE4. 25: SMS IN 5G [REF. 1].................................................................................................................313

5G Evolution
Chapter 1
 1. introduction to 5G
The evolution of mobile networks by analog cellular systems in 1980
transformed mobile network technologies into network services. This radio
technology evolution in telecommunication networks improves network
connectivity, latency, and devices' mobility.5G, the fifth-generation mobile
network, is the current evolution in mobile networks. It is a unique global
wireless communication standard after the 4 G LTE (Long term Evolution)
mobile network standard. The 5G, the novel mobile network, allows connection
to everyone, everything and everywhere, including machines, objects, and
devices. It provides high speed, low latency, wide coverage, more connectivity,
and flexible wireless services for everyone. Furthermore, it offers more network
capacity, better availability, and a consistent user experience. 5G network
performance and efficiency empower connects to new industries. The 5G
mobile network is a complete transformation of telecommunication networks
and provides benefits that pave the way for new capabilities and support
connectivity for the latest applications like smart cities, autonomous vehicles,
remote healthcare, and more. It also enables wireless services and technologies
in various sectors, such as agriculture, medical and educational domains.

1.1 5G Evolution toward 6G

After evolution in mobile cellular networks (1G… 4G, or now 5G), digital
wireless communication systems work always to fulfil growing needs of the
human beings. The NR Release 15 in the initial phase of 5G development,
3GPP standardized radio technologies focused on enhanced mobile broadband
(eMBB) and a part of ultra-reliable and low latency communications
(URLL).5G is the 5th generation mobile network that launches a novel network
that links virtually any devices, anywhere and anytime together including
computers, objects, and devices. The 5G improves the speed of the mobile data,
reduces the delay of transmission of the data, increases the consistency in the
connections of the devices, and improves the flexibility of wireless services.

The 3GPP introduced 5G Phase 1 (R15) to frame policies for 5G. The Phase 1
(R15) lays a solid foundation for future releases of 5GWith NR air interface
and network architecture. The air interface connects two mobile stations in the
wireless communication networks. It works with both the physical and data link
layers (layers 1 and 2) of the OSI model for a connection. R16 and later
releases in 3GPP expand applications of wireless communications. The 3GPP
releases several 5G designed standards like R15, R16 and others. The eMBB
based R15, R16 and later releases expand the supported services of 5G.
5Gbenefits the lifestyle with faster download speeds, low latency, and high
network capacity. There are vast network capacity and connectivity for billions
of devices in Virtual reality (VR), IoT and Artificial Intelligence (AI) 5G LAN
replaces wireless LAN with flexibility and higher performance. 5G applications
in seaports use case: Normally, seaports have challenges such as complex
turnarounds, a large and diverse workforce, and many moving assets.5G
solution for these challenges is an integrated seaport management solution
based on a 5G private network. It benefits operational efficiency, enhances
safety, and increases security. 5G enables prompt communication without
categorizing between vehicles, humans, and implanted sensors, as they share
the same access technology. In non-terrestrial networks, satellites use 5G to
provide service ubiquity, service continuity and service scalability.
 Figure 1.1: 5G Radio Access Network gNB

5g performance improves main medical applications and healthcare and reduces

costs. 5G empowers new V2X use cases such as platooning, advanced driving
and remote driving. 5G based UAVs support various scenarios like delivery of
medical supplies in disaster situations. 5G supports multimedia production
services at studios. A cyber-physical system (cps) or intelligent system
integrates sensing, computation, control, and networking concepts into the
hardware and network infrastructure. And it connects the hardware and
infrastructure to the internet.

The novel 5G mobile network transforms the early industry standard into the
existing advanced industry standard 4.0. So, it boosts manufacturing, production
and related industrial activities and value creation processes. New Radio (NR)
based positioning in the mmWave band, a 5G radio link behaves partially as an
optical wave and possesses optical properties such as reflection, refraction, and
diffraction. The optical wave properties, along with beam forming in 5G, are
used to locate objects and their position accurately. This NR positioning
supports many use cases like emergencies, UAV operations, AR/VR/XR and
factory automation.

Haptic communication with the haptic sense improves the user experience to a
large extent NR-New radio on unlicensed spectrum, improves many features
and supports carrier aggregation and dual connectivity after R16.

IAB (integrated access and backhaul) is an important Rel-16 feature in 5G New

Radio (NR) that enables rapid and cost-effective millimeter wave (mmWave)
deployments through self-backhauling in the same spectrum. Wireless self-
backhauling uses the same wireless channel for coverage and backhaul
connectivity to other base stations, which leads to greater performance, more
efficient use of spectrum resources and lower equipment costs, while also
reducing the reliance on the availability of wired backhaul at each access node
location. Every service provider with rolling out 5G cells knows fibre optic
transport connectivity to a cell site is a vital to maximize operation. fiber is
placed in the ground. This comes with various challenges, never mind the costs
involved. The challenge with small cells is that these are typically deployed in
already densely populated areas where the connectivity of fibre may be an issue.
One obvious situation is to utilize 5G to backhaul 5G user traffic. Whilst this
concept is not new, the key is the implementation within the 3GPP 5G
standards. Figure 1.2 illustrates the basic concept of IAB. At the heart of the
concept is the deployment of C-RAN (centralized RAN) and the functional split
of the gNB New Radio Node B) into a CU (Centralized Unit) with multiple
DUs (Distributed Units). IAB defines the IAB-Donor which supports both 5G
access from devices, as well as the 5G IAB Backhaul. Thus, enabling the IAB-
Node(s) to get connectivity. These IAB-Nodes include the gNB-DU
functionality and thus provides 5G Access.
 Figure1. 2: Integrated Access and Backhaul in 5G

IAB implementation used IAB concepts in the stand-alone (SA) and non-
standalone (NSA) networks. The IAB concept works equally well for NSA
(Non-Standalone) operations. An IAB-Node could provide the 5G access for the
NSA device. In Figure 1.3, the device is in NSA operation, i.e., using the EPC
(evolved packet core). However, in this example, the IAB-Node itself, which
also has a USIM (Universal Subscriber Identity module) or eSIM (embedded
SIM), operates in SA mode, i.e., it is using the 5GC (5G Core). It is very
flexible, supporting both “in-band” (using the same band as the 5G access) or
“out-of-band” (using a different band).
 Figure 1.3: Using IAB and interworking with NSA Operation

These analyses typically focus on spectrum availability, interference constraints,

and the typical issues of TDD (Time Division Duplexing) operation. The
answer depends on the service provider’s implementation, and the IAB-Node
(s) predicted capacity requirements. Previously, it has illustrated a single hop,
i.e., one IAB-Node. It designs Systems with multi-hop capabilities, which
provides more range and the capability to “hop” around obstacles, fix it or adapt
based on changes to the physical environment, e.g., seasonal foliage or vehicles,
e.g., buses/trucks affecting the signal. In addition, if using the High-band
frequencies (which have limited range), then multi-hop proves invaluable.
Typically, when describing multi-hop deployments, the terms “Spanning Tree”
and “Directed Acyclic Graph” represent how the hops may be structured. This
enables the Fiber topology to be adapted based on various scenarios, e.g.,
blockage or capacity issues–such that the end-user should be unaffected. Figure
1.4 shows the IAB in multi-hop topology. IAB is a multi-hop approach to
network deployment and allows mm-wave base stations centralised or without
Fiber backhaul transport.

Figure 1.4: IAB Multi-hop Topology

It works by having a fraction of the deployed BSS act as donor nodes, using a
Fiber/wired connection. The remainder without a wired connection is called
IAB nodes. Both BSs generate an equivalent cellular coverage area and appear
identical to user equipment (UE) in their coverage area. IAB allows operators to
leverage their existing mm-wave spectrum licenses and have the freedom to
deploy separate backhaul where needed, without additional interference analysis
that can be subject to regulatory review (and potential denial).

IAB is a compliant “cloud RAN” architecture with a split CU (Centralized Unit)

and DU (Distributed Unit). It is essential to centralize Various functions, such
as RRM (Radio Resource Management), RRC (Radio Resource Control) and
PDCP (packet Data Convergence Protocol). The donor DU is a conventional
fibre-fed BS connected to the CU using an F1 interface. The IAB node may
serve as a first-hop or second hop node. Both donor and IAB nodes also directly
support UEs multiplexed with the backhaul Ur interface. The Uu interface is
directly between a UE and an IAB or donor node. IAB permits the use of
spectrum for backhaul besides traditional access to deployment costs and
simplifies radio-core connectivity, URLLC-centric enhancements reliability,
faster processing, more flexible HARQ, uplink cancellation and uplink power
control. Industrial IoT NR developments support TSN refence times and
Ethernet, flexible grants, and scheduling.

Frequency bands in 5G networks: The frequency bands for 5G networks are two
ranges, FR1 and FR2. The frequency range, FR1, ranges from 450 MHz to 6
GHz, including the LTE frequency range. Frequency range 2 (FR2) ranges from
24.25 GHz to 52.6 GHz. The sub-6 GHz range is the name for FR1, and the
mmWave spectrum is the name for FR2. these bands support many use cases
such as densification, industrial IoT, backhaul, fronthaul and an intelligent
transportation system ITS. The new radio NR significantly improves MIMO
operation, mobility concept, positioning, and UE power savings. Release R15
significantly defines virtualization-friendly service-based architecture (SBA).
This enhanced architecture is suitable for the vehicle to any (V2X), network
automation, CLI / RIM, eCAPIF, and IMS.

V2X-related enhancements include support for the NR-based PC5 interface.

NWDAF and its interaction with other NFs improve automation and facilitate
AI-based operations. The goal of CLI / RIM is to enable dynamic TDD while
reducing overall interference. ECAPIF supports multiple API providers and
solves load-bearing applications. It improved IMS to cooperate with the SBA
and support cutting edge computing. 3GPP is still defining SEAL and SON for
5G and strengthening the security framework. At the application layer, SEAL
cooperates with the vertical application layer (VAL) to provide services such as
group management and configuration management for applications in various
industries. 5G SON supports traditional algorithms like LTE, such as ANR and
PCI configurations, and new algorithms related to network partitioning.

Security is being further strengthened, especially considering the expansion into

new vertical areas. Although the R16 and subsequent versions of 5G have
substantial untapped potential, 6G will elevate the experience to a whole new
level and completely change many industries. Data rates of approximate
terabytes per second, delays of a few microseconds, and high energy efficiency
of equipment and networks may be signs of 6G. High-fidelity holographic
communication and multisensory communication have become part of daily
life. Although 5G affects the healthcare, manufacturing, entertainment, and
transportation industries, they are undergoing further transformation through
6G. The future enhancements will significantly shape the world of wireless
communications. Deployment of 5G systems began in 2018, and we will see
many additional features for this technology in the future. The key feature
added to 5G is Massive MIMO that increases link capacity, the maximum data
transferred between network locations over a link and throughput and improves
link reliability. A flexible frame structure supports various services and
industries; advanced channel coding schemes such as polar coding and LDPC
coding reduce the error rate and overall power consumption, Millimetre-wave
bands (e.g., greater than 24 GHz) with large bandwidth and significant
propagation.

Challenges, Spectrum sharing between cellular technologies and non-cellular

technologies (e.g. radar), including sharing with devices using unlicensed
spectrum , Low latency, low power, highly reliable wireless connections to
support IoT applications , Ability to support much greater density in the
deployment of user devices, primarily to support IoT , Multi-access edge
computing (MEC) to reduce end-to-end latency and bandwidth requirements for
the transport network , Network slicing to realize custom and comprehensive
QoS for diverse services and customer requirements , Virtualization and
automation technologies like network function virtualization (NFV) and
software defined networking (SDN) to implement cloud based radio access
networks, core networks and service networks for service agility, enhanced
service experience, scalability and cost-effective, end-to-end network design,
maintenance and optimization processes.3GPP defined the fifth generation (5G)
mobile technology in Release 15 is to meet ITU’s IMT-2020 performance
requirements that 20 Gbps peak data rate, 1ms latency, 10 Mbps per m2 area
throughout and 1 million (low-rate) IoT devices per square kilometre and
enabling a variety of services associated with usage scenarios that ultra-reliable
low latency communications (URLLC), enhanced mobile broadband (eMBB)
and massive machine-type communications (mMTC).

The fundamental elements in the 5g system are a New Radio (NR) air interface,
new radio, core network architectures, Virtualization, automation technologies
and new types of devices. These building blocks enable 5G to offer targeted 5G
services. When Release 15 provides a solid framework for enhanced network
performance and mass offering of excellent services, 3GPP actively enhances
the framework, as shown in Fig. 1.5.

Figure1. 5: Evolution path from 5G to 6G

1.2 Release 15
3GPP stands for Third Generation Partnership Project. 3GPP has specifications
for the third-generation mobile system, Universal Mobile Telecommunication
System (UMTS) and fourth-generation mobile systems, long-term evolution
(LTE). International Mobile Telecommunications (IMT)-2020 defined 5G
performance requirements in release 15 pahase1. Key features of R15 include
the New Radio (NR) air interface, new radio network architecture called next-
generation radio access network (NG-RAN), new core network architecture
called next-generation core (NGC) or 5G core (5GC), service-based architecture
(SBA), network slicing and edge computing.

1.3 Release 16.

Planned features of Release 16 (R16), called 5G Phase 2, includes NR
unlicensed (NR-U), integrated access and backhaul (IAB), enhanced vehicle-to-
everything, URLLC and industrial IoT (IIoT) enhancements and service enabler
architecture layer (SEAL) for industries.
1.4 Release 17
The release 17(R17) of 3GPP defined significantly 5g features for non-
terrestrial networks (NTN) with satellites, new frequency bands (e.g., 7 GHz to
24 GHz and more than 53 GHz), NR side link and NR optical improvements.
Some companies have recently begun the first phase of 5G implementation, and
versions after R15 will continue to take 5G advantage. 3gpp introduced some
5G features in one version and developed them in the next version. it is the
3GPP work in R16 and R17 described into the following categories: (i) service
expansion, (ii) NR enhancement, (iii) network architecture enhancement, and
(iv) other updates. Before delving into R16 and above, let us take a quick look
at the salient features of 5G R15

► 6G. Mobile companies have started the deployment of 5G networks in some

parts of the world. In addition, they tapped in other features beyond release 15,
R15. since a new generation of cellular technology appears every ten years; We
expect that 6G cellular technology deploys in the year2030. The new exited
features of 6G are high-fidelity holograms, multisensory communications,
terahertz (THz) communications and artificial intelligence (AI).

1.5 NR air interface

The new radio interface uses an OFDM radio interface to uplink and downlink
data transmission.it has variable sub-carrier spacing, flexible radio frame
structure, self-contained slot, and carrier bandwidth parts. 5G NR has both the
7GHz sub frequency spectrum and Millimetre-wave frequency spectrum and the
new high-performance channel coding techniques of low-density parity-check
coding and polar coding. 5g improves the concepts Spatial multiplexing
techniques, MIMO and MU-MIMO3, used in LTE. NR is a beam formed air
interface with fewer beams at low-frequency bands and more high-frequency
bands.5G supports hybrid beamforming Massive MIMO in 5G enables
enhanced combining of beamforming methods with spatial multiplexing.

1.6 NR provides a flexible air interface

In release 15, it introduced the dynamic spread spectrum sharing concept. The
sub-carrier frequencies of 4G and 5G are dynamically allocated to the same
channel. NG-RAN is an access network for 5G mobile networks. By which,
user devices UEs access the internet and intern other applications. The NG-
RAN comprises 5th generation base stations called gNBs. Each gNB can be
decomposed into the central unit and distributed unit. The 5G network has more
network functions with fewer responsibilities. The NFV network manages this
function's virtualization. 5G defines more network functions managed by NFV,
including network security and firewalls, network address translation (NAT),
domain name services (DNS), caching, intrusion detection, and more.5G has
more NFs with fewer responsibilities. While LTE uses a few nodes in the
developed packet core (EPC),
 Figure1. :4G and 5G architecture

Figure1. Non-Standalone 5G

Figure1. Data Exchange over non-Standalone 5G

 Figure1. Standalone 5G with SBA

R15 fully presents two deployment options for the network architecture: non-
standalone (NSA) NR and standalone (SA) NR. So, non-standalone NR with the
EPC uses the LTE eNB like the master node and uses a gNB's NR radio
resources when possible. Standalone NR with the NGC does not rely on the
LTE eNB at all the time and permits direct communications between the UE
and the gNB.

1.7 NG-RAN, NGC, and SBA

NG-RAN NR based 5G base stations called gNBs.

The 5G mobile network architecture comprises NG-RAN to access the data

from users. NG-RAN is a set of gNB base stations. The gnB decomposed into a
central unit and a distributed unit. This gNB architecture reduces infrastructure
and transport costs and provides scalability.
While LTE uses a few nodes in the evolved packet core (EPC), 5G defines more
network functions managed by NFV including network security and firewalls,
network address translation (NAT), domain name services (DNS), caching,
intrusion detection and more.5G has more NFs that have fewer responsibilities.

Figure1. 5G RAN

SBA is a vital network segment in the 5G system, where NFs communicate

using service-based interfaces. The SBA enables the design and deployment of
the 5G system using virtualization and automation technologies such as
Network function virtualization (NFV), software-defined networking (SDN),
OpenStack and Orchestration.

►deployment options. R15 comprehensively defines two implementation

options for network architecture: non-autonomous NR (NSA) and autonomous
NR (SA). Non-autonomous NR with EPC uses LTE eNB as the master node
and uses the additional NR radio resources of gNB when possible. Independent
NR with NGC is entirely independent of LTE eNB and allows direct
communication between UE and gNB.
 Figure1. : SBA in 5G

Figure1. : Network Function Operation

Figure1. : Non-standalone 5G relies on a 4G core, while standalone 5G uses a 5G
core.

1.8 Network slicing

3GPP defines network slicing where different logical networks are created on
the standard physical layer using software virtualization and software-defined
network concepts. We design this network to cater to different services and
customer requirements. We define eMBB, URLLC and massive IoT to support
many operators defining network slices for use cases. Each network slice is an
isolated end-to-end network tailored to fulfil diverse requirements requested by
a particular application. As the Network always must carry out some essential
functions, such as communicating with the UE, storing its subscription and
credentials, allowing access to external networks & services, providing security,
and managing network access and mobility. 5G assures significant
improvements in bandwidth and latency, making virtual network slices a
possibility.
 Figure1. :5G Network Slicing

. Each virtual network instance created by 5G network slicing provides an

isolated, end-to-end network optimized for a specific business purpose.

Figure1. : 5G Network Slicing

 Figure1. 5G Network Slicing on physical layer

1.9 5G Core Network Functions

As the Network always must carry out some essential functions, such as
communicating with the UE, storing its subscription and credentials, allowing
access to external networks & services, providing security, and managing
network access and mobility. 5G assures significant improvements in bandwidth
and latency, making virtual network slices a possibility.

Each virtual network instance created by 5G network slicing provides an

isolated, end-to-end network optimized for a specific business purpose. What
are the significant benefits of the 5G network slicing technique? Compared to
existing 4G and LTE (Long term Evolution) networks, 5G promises significant
improvements in bandwidth and latency, making virtual network slices a
possibility. Each virtual network instance created by 5G network slicing
provides an isolated, end-to-end network optimized for a specific business
purpose.
 Figure1. 5G Network Slicing

1.10 Edge computing.

Figure1. Edge Computing

3GPP supports edge computing, where the application is near the UE. 3GPP
allows the selection of a gateway close to the gNB. Since user traffic passes
through the local gateway instead of a remote gateway in the core network, it
reduces end-to-end latency and transmission requirements.

Salient Features of 5G
5the generation mobile network is revolutionary in 5G mobile technology. Its
features and mobility are beyond the expectation of the human being. The high
speed in the 5G data increases the usability of cell phones. With several
innovative features, an intelligent cell phone replaces the laptop now. The 5G
network technology implements significant features in smart mobile devices
such as gaming options, more comprehensive multimedia options, connectivity
everywhere, zero latency, faster response time, and high-quality sound and HD
video, improving multimedia services and user experience.

Figure1. : Features of 5G Technology

The mobile phone at 5G caters for most network users. We list the few key
benefits of 5 G below.
1.11 Key benefits with 5G
The 5G network features lower latency, higher capacity, and increased
bandwidth compared to 4G.

 We expect peak 5G speeds up to 100x faster than 4G LTE networks.

 Reduced latency supports new applications that leverage the power of

5G, the Internet of Things (IoT), and artificial intelligence.

 Increased capacity on 5G network data capacity can minimize the impact

of load spikes, like those during sporting events and news events.

1.12 Speed upgrades

Every wireless network generation enhances the speed of the mobile data in
manifolds. Further, 5g networks increase the data speed 100 times more than the
speed of 4G LTE, improving exciting possibilities for consumers and
businesspeople. It reduces the download speed from 7 seconds to 6 seconds
from 4GLTE speed. The speed feature of the 5G saves time at the critical
moment. After implementing 5g features in full range, the 5g network replaces
broadband, and it becomes the best network for businesses and consumers in the
future.

1.13 Low Latency

Latency is the unit that measures the round-trip time of a data packet traveling
from the source to the receiver and back from the receiver to the source in
seconds. The primary aim of mobile network evolution is to reduce the latency
time. The latency of 5g is one millisecond. So, it enables devices to operate in
real-time with less human response time. Because high-speed data in 5g, 5g and
IoT applications are free from human responses, we expect 5G applications
from many industries to launch soon. Applications such as agriculture,
manufacturing, and logistics, including the game industry, benefit from this low
latency. High speed and low latency are perfect requirements for virtual reality
(VR) and augmented reality (AR) applications. This feature has exploded in
popularity since the connectivity improvements created a more seamless,
immersive experience.

1.14 Enhanced capacity

The capacity of the Network is the maximum data that flows in the Network.
The 5g network, because of enhanced capacity, improves business technology
initiatives and business scale. 5G delivers up to 1,000x more capacity than 4G,
provides facilities for IoT development.

It redefines 5G and IoT with an increased 5g network capacity with internet and
wireless network. With 5G devices communicating capacity, applications for
cities, factories, farms, schools, and homes are growing, and 5G applications
bring thousands of sensors on hundreds of different machines, automating
supply chain management processes and ensuring just-in-time delivery of
materials while using predictive maintenance to minimize work stoppages.
Smart homes and cities also take a giant leap forward in the future of 5G. Using
more connected devices, AI to place, has no edge on computing. From houses
that give personalized energy-saving suggestions, maximize the environmental
impact of traffic lights that change their patterns based on traffic flow. 5G
applications relying on added network capacity affect everyone.

1.15 increased bandwidth

The high speed, high bandwidth, and network capacity of 5G enables extensive
data to be transmitted than the traffic of the data in the 4G LTE network. A
unique 5G network architecture than 4G allows optimization of the network
traffic and smooth handling of usage spikes. The 5G broadcast network
provides seamless streaming connectivity to large audiences from crowded
stadiums and other venues than 4G. Each audience in the stadium can broadcast
seamlessly to any place in the world. The increased capacity and bandwidth in
5G influence more data across network devices. It leads to big data. The
companies collect data from customers, suppliers, and teams more than to
process and analyse for insights. Today, with 5G connectivity and big data
analytics, businesses turn a large volume of data into operational knowledge.

1.16 5G availability and network coverage

The limit 5G network coverage while users are expecting 5G benefits. Today,
all major US cellular carriers deploy 5G networks in major cities to prepare for
more comprehensive rollouts.

Figure1. : Evolution to 5G

Service Expansion Beyond Release 15

3gpp focussed more on eMBB usage scenarios’ in R15, but most of the work in
R15 is helpful for URLLC and mMTC usage scenarios. Fig 3.0 explains the
extended service scenarios beyond eMBB by 3gpp in R16. The 3gpp focuses on
different industries. Many of these services that related to different industries.
They are not distinctively different but overlap each other to some extent. We
describe these services in sections 3.1 to 3.10.

Figure1.21: New or enhanced services beyond 5G Phase 1

1.17 5G LAN
Figure 1.22 shows the key concepts related to 5Glocal area network (LAN)
services [TR22.821]. Like fixed or wireless LAN's, 5G LAN provides reliable
communications between a group of restricted UEs in residential, commercial,
or industrial environments. The 5G system can enhance, supplement the
existing fixed wireless local area network, or completely replace such a local
area network. Uses the 5G system to create a virtual private network (PVN).
Compared to traditional LAN, based on 5G.

5G LAN redefines 5G, and the Internet of Things increases the capacity of the
5G network in virtual private networks for internet and wireless networks and
provides benefits such as superior performance, remote access, mobile support,
and enhanced security. In a residential environment, different devices in a single
house or different users in an apartment building can get enhanced 5G QoS and
maintain privacy and isolation of communications when needed.
5G LAN helps connect computers, printers, scanners, and servers in the
enterprise setting and supports access to private and secure settings across a
wide area or even across distant sites.

Figure 1.22: key Concepts Related to 5G Local Area Network (LAN) Services

The 5G LAN connects controllers, actuators, and sensors without wires and low
latency communications in the industrial environment. Reliable 5G wireless
connectivity cancels Ethernet cables in a hazardous environment or in moving
or rotating parts and facilitates factory reconfiguration to improve productivity.

In IoT devices, two communications endpoints span countries: a pipeline sensor

in one country and a pipeline valve in another country. As a network that offers
private communications services, such a network is a non-public network.
(NPN), is simply a private network. Only selected devices that are members of
the NPN can get the Network's services. Devices that are not members of the
NPN get services from the regular "public" network. The 5g LAN dedicates the
network resources (e.g., radio and core networks) to the private entity that
controls the non-public Network (NPN).
5G Access (Fig. 2.3) Service ubiquity, service continuity, and service scalability
are the three use case categories. These categories are not mutually exclusive; a
use case could fall under multiple categories.

Use case categories are service ubiquity, service continuity and service
scalability. These categories are not mutually exclusive; a use case may belong
to over one category.

```

Figure1.23:5G Access

► Service ubiquity. This category describes how a terrestrial 5G network is

unavailable, but a satellite network is. Some rural or difficult-to-reach places,
unserved or underserved by a terrestrial network. Some IoT use cases, such as
smart agriculture, small industrial and offshore wind farms, not be economically
viable for a terrestrial network, but they are possible for a wireless network.

► Service continuity. In some circumstances, the UE establishes contacts with

a terrestrial 5G network but then leaves the coverage region of the terrestrial
system. Satellite access can assure service continuity. Asset tracking for IoT
devices and individuals boarding trains, aircraft, and ships are two examples of
application cases.
► Service scalability. Because satellites cover a large geographic area (for
example, an area equivalent to thousands of terrestrial base stations), some
broadcast content, such as ultra-high-definition content or three-dimensional
content, can be transmitted efficiently, and many economic users at the same
time. Any non-time-sensitive data transmission can also be downloaded from
the terrestrial network to the satellite network.

1.19 Critical Medical Applications

5G improves healthcare significantly by strengthening preventive care,
shortening treatment time, and reducing overall costs [TR22.826]. In a key
medical application, patients and medical experts are juxtaposed. We can divide
this category into "static-local" or "mobile-local", depending on whether the
team or person is moving while providing care. Since such care delivery occurs
within the facility, we provide indoor communication services on a dedicated
5G network. In another type of critical medical application, patients

Medical experts are in various places. We can further divide this category into
"static-remote" or "mobile-remote" according to whether the equipment or
person is moving while providing care. Since this type of care takes place on a
large scale, PLMN 5G provides communication services.

► private 5G network use cases. The doctor configures a remote operating

system in the operating room. The surgeon uses the console, and the robotic
system operates on the patient under the surgeon's guidance. When the surgeon
processes the 3D model of the patient's body, URLLC and MEC are essential.
The MEC application processes the patient measurements to match the robotic
system and the surgeon's commands. In another image-guided surgery case,
real-time video is wirelessly copied to multiple monitors. The operator uses a
video monitor to control the imaging equipment in a specific part of the
operating room, and the surgeon watches the video on a separate monitor. In
augmented reality assisted surgery, the surgeon uses a head-mounted display
(HMD) to perform the surgery. 4) In robotic surgery, the robotic system can
perform more precise surgery with the instruments (for example, in a small
area), and the tremor of the surgeon's hand movement can be calculated by the
edges of multiple access (MEC). It softens. Real-time video footage and
medical erence images are displayed on the headset to facilitate surgery.

►5G PLMN uses cases. In emergencies, distance is usually a key factor. When
providing intensive care for patients, 5G can help overcome these distance
limitations. In the emergency care case, an ambulance nurse can perform an
ultrasound at the accident scene and take actions under remote guidance (for
example, applying pressure to a specific part of the body to prevent bleeding or
injury) as a medical expert. The most suitable medical institution (such as a
heart hospital) can be selected according to the patient's situation. We can place
various sensors on the patient's body and the emergency room (ER) is prepared
even before the patient is transported to the emergency room. Without an
exceptional surgeon present in person, remote surgery or remote, we can also
perform surgery, which significantly expands medical care to remote areas. In
another case, from the moment the ambulance arrives at the accident site to the
moment the patient is taken to the operating table in the operating room, a
networked ambulance can transmit essential patient data to the emergency
room. Come to receive patients. In another case, a sensor was installed on a
recently discharged patient from the hospital to track essential measurement
data and notify the appropriate medical institution. If necessary, medical
assistance can be provided to the patient immediately.

1.20 5G V2X
Although LTE can solve some Internet vehicles (V2X) use cases, the 5G V2X
significantly expands the types of use cases supported by 5G's high data rate,
ultra-low latency, and high reliability. Please note that the NR-based V2X is a
supplement to the LTE-based V2X, not a replacement. For example, the LTE-
based V2X can be used to send important security messages, and scenarios that
require stricter SOS requirements (for example, delay, reliability, and data rate)
can benefit from the NR-basedThe V2XV2X is a subcategory of side-chain
communication, supporting vehicles and supporting public safety through EU-
to-EU communication. R17 will solve the unresolved V2X problems in R15 and
R16 and introduce research projects to expand NR side link communication
capabilities and applications. We expect R17 to contribute to energy saving,
reliability, and latency. Figure 1.24 summarizes 3GPP's use case group for 5G
V2X [TR22.886].

Platooning. is operating a group of vehicles in a tightly coupled manner. This

operation is like a train using virtual cables between vehicles. To maintain the
distance between vehicles, the vehicles taking part in the platoon share their
status information, such as speed, heading, and intention (for example, braking
or speeding up). We should share information about the platoon with non-
platoon vehicles so as not to disturb the platoon.

Figure1.24 5G V2X use case groups.

This platoon improves safety by maintaining a safe distance while reducing the
distance required between vehicles. Queuing reduces overall fuel consumption
and makes traffic flow smoother. It can also reduce the number of drivers
required to operate a specified number of vehicles.

► Advanced driving. Vehicles share various information to improve safety and

prevent accidents. For example, collaborative collision avoidance involves
using safety messages (cooperative awareness messages or CAM and
decentralized environment notification messages or DENM), sensor data, and
braking and acceleration commands to assess the likelihood of accidents and
coordinate manoeuvres. In emergency route alignment, when the vehicle detects
an obstacle on the road through the onboard sensor, it will calculate the
manoeuvre to avoid the accident and notify other nearby vehicles. These
vehicles can then adjust their trajectories to coordinate emergency responses.
Similarly, at intersections, a local dynamic map (LDM) server can use road
radar and traffic signs to monitor the road, Generate LDM information and pass
the information to the vehicle through the road unit (RSU).

► Extended sensors. Vehicles can share their raw or processed sensor data with
other vehicles and MSW to create situational awareness. This exchange of
information allows vehicles to make tactical or manoeuvring decisions. For
example, the exchange of sensor data, including high-resolution video, can
detect objects that local sensors cannot see directly (such as behind other
vehicles, in curves, or behind building corners).

► Remote driving. In remote driving, the operator or cloud server remotely

controlled the vehicle. For example, a bus travels on a predetermined route. The
operator can drive the bus with data (for example, a video containing the inside
and outside views of the bus). If a human driver cannot drive because of
personal circumstances (such as fatigue) or health conditions, the vehicle can be
driven remotely to a suitable destination, such as your home or medical
institution.

1.21 Unmanned Aerial Vehicle or UAV

An unmanned aerial vehicle (UAV) or UAV is a low-altitude vehicle (for
example, up to a few hundred meters) that can provide communication in a brief
time or within a limited time. Geographical area. UAVs can usually operate for
up to 1 hour [TR22.829]. After providing communication for a period, the drone
returns to the base for charging. A cloud controller can control the drone, and
delay-sensitive applications can be compatible with multi-access edge
computing (MEC). It uses artificial intelligence (AI) to control drones. Because
the traditional antennas in the cellular network are tilted downwards, the support
of UAVs requires adjustments to the existing antenna system or a separate
antenna system. The following are examples of use cases where drones can be
used.

►Live video. They can equip the drone with a 360˚ spherical camera. The
drone can communicate with the gNB on the ground and send 4k / 8k video to
the cloud server. People wearing augmented reality glasses can enjoy live video
broadcasts as if they were in a stadium.

►Temporary radio access with an Internet connection. In a disaster or

emergency, the drone can act as a gNB (connect to the core network via
wireless backhaul) or relay (connect to a terrestrial gNB that provides a
connection to the 5G core) to provide coverage quickly and cost-effective.

►With dedicated isolated radio access for connection. Sometimes, such as

construction in remote areas, there is no traditional cellular wireless access
coverage or backhaul. Compared to ground solutions, drones can provide
coverage faster and cheaper. The UEs in the private group can communicate
with each other via the drone.

►A fleet of drones for logistics. They can use a group of drones in a

coordinated way to deliver packages. Even if the ground infrastructure is
damaged and unusable, it can deliver medicine and food in disaster situations.

1.22 Audio-visual production

5G networks can facilitate audio-visual production (AV) services by providing
flexibility, reducing costs, and reducing communication setup time. We can
produce the media on or off the premises of the production company. The
following are examples of AV production use cases that 3GPP can contribute
[TR22.827].

►Production based on research. You can use wireless microphones connected

to various audio sources, including singers, musical instruments, and mixers, to
produce media in the studio. 5G systems can replace inflexible and expensive
fixed infrastructure.

►Newsgathering. This use case represents an unplanned temporary production,

such as a report of a significant event. It can quickly configure the 5G system to
generate relevant AV media and provide the media r further processing and
distribution.

►Planned external emissions. Elaborate AV infrastructure with many cameras,

microphones, and mixers that can be installed for planned events (for example,
elections or sports events). 5G systems can facilitate the streaming of media
from such event facilities to central production bases. Some media pre-
processing can also be done locally. Sometimes a large coverage area is
required (like a bike race), and they can deploy onboard 5G NGRAN. Examples
of audio production use cases include live audio presentations (mixing of
speaker talks and questions from the audience) and streaming audio (mixing of
the singer's voice and streaming audio of musical instruments, mixing of
amplification signal and distribution combined) transmission of audio in lobby
speakers). The right teams can communicate with 5G systems to facilitate media
production and distribution.

►Immersive multimedia services in real-time. It can instal multiple cameras in

various locations and players throughout the stadium to create an immersive
experience for local and global audiences. The Olympic Games are an example
of an event that can be enjoyed through this immersive experience.

1.23 Cyber-Physical Control Applications

The cyber-physical control application controls the physical processes of the
cyber-physical system, comprising the design and interactive network of
physical components and computing components. Cyber-physical control
applications can be used in vertical fields such as industrial automation and
energy automation. The following are example use cases related to these
verticals [TR22.104] [TR22.832].

►The factory of the future. Industry 4.0 is revolutionary to improve flexibility,

versatility, resource efficiency, profitability, worker support, and industrial
production and logistics [TR22.104]. The cyber-physical system is an enabling
technology that can use 5G. 5G can be applied to all aspects of automated
factories, such as factory automation, process automation, human-machine
interface (HMI), production IT, logistics warehousing, monitoring, and
maintenance. Automation involves robotics and computer-aided manufacturing
and has seen an upward trend in mobile and modular production systems.
Process automation involves automating processes that control the production
and handling of chemicals, food, and beverages. 5G can help establish
communication between sensors, actuators, and controllers. Various HMI
devices such as production line related panels and headsets using AR / VR (for
example, gradual support of specific tasks by remote experts) will benefit from
5G connectivity. Logistics and warehousing involve using automated guided
vehicles (AGVs) and forklifts to control the flow and storage of substances.
Monitoring and maintenance involve processing data from suitable sensors to
ensure the plant's long-term operation and perform predictive maintenance.

► Power distribution. The smart grid is an emerging power distribution

network in which knowledge is used to manage power distribution. The
increasing focus on renewable energy sources (such as solar and wind power),
two-way power flows, and increasingly dynamic energy systems require
intelligent management of the right resources. 5G can help connect many local
generators (such as solar generator sets and wind turbines) to the smart grid.
5G-based communications can facilitate fault detection and automatic power
recovery by using appropriate measurement and control mechanisms.

►Central power generation. Centralized power generation involves the

conversion of chemical energy and other forms of energy into electrical energy.
Large gas turbines, steam turbines, combined cycle power plants, and wind
farms can help produce 100 MW or more electricity. 5G can facilitate the
operation, monitoring and maintenance of such factories. Time-sensitive
networks (TSN) are an essential aspect of cyber-physical systems. Traditional
TSN uses a wired network based on IEEE802.3 Ethernet to ensure that packet
transmission has limited delay, delay variation, and packet loss. We expect 5G
to be used with TSN based on IEEE802.1. Both device-to-device
communication and UE network communication can be used. Since Ethernet-
based communication is standard in factories today, 5GLAN services will play a
key role in automated factories.3.8 Positioning
Although 4G LTE and 5G Phase 1 can certainly support location-based
services, the use cases for R16 and beyond are significantly expanded due to
improved positioning accuracy. Figure 1.25 summarizes examples of vertical
industries that can benefit from positioning use cases [10].

In emergencies, even in challenging environments such as urban canyons and

deep interiors, precise positioning allows users to get help from first responders
by contacting a public safety response point (PSAP).

► Mission-critical.

►Location-based services. Augmented reality glasses and head-up displays

(HUDs) use precise positioning to overlay contextual information on the user's
real-world view for more straightforward navigation, video recording, and
target recognition. Shared bike services can benefit from precise positioning,
and users pick up and place bikes in suitable locations. Outdoor sports and
leisure activities such as motorcycles, skiing, and games can also take
advantage of precise positioning.
 Figure 1.25: Verticals for positioning use cases

► Industrial and e-health. Accurate positioning is important in many factory

automation applications, including container assembly and management.
Medical staff and equipment can be detected in the hospital setting to promote
high-quality and timely care.

► Highway. In the vehicle environment, 3D positioning makes it easy to

monitor, manage and control traffic for a smoother traffic flow thus.we are
reducing travel time, saving fuel, and supporting emergencies. The road user
charge (RUC) charges users based on the use of the road infrastructure.

► Rail and maritime transport. Asset tracking in rail and marine applications
can improve transportation efficiency, reduce the possibility of container loss or
theft, and facilitate logistics.

► Antenna. UAVs or drones significantly benefit from automatic landing and

precise positioning for personal or professional tasks, such as transporting
medical supplies. Image and sensor data (such as infrared sensor data) can be
combined with positioning data to facilitate drone operations.
►E911 and regulations. The UE's location supports E911 calls and helps meet
(or even exceed) regulatory requirements. 3GPP aims to support various
positioning technologies to support the above use cases [TR38.305]. Standard
positioning methods supported by NGRAN access include Global Network
Assisted Navigation Satellite Navigation System (GNSS) method, Observed
Time Difference of Arrival (OTDOA) positioning, enhanced cellular
identification method, WLAN positioning, Bluetooth positioning®, and
Terrestrial Beacon System (TBS) positioning, And sensor-based methods (for
example, air pressure sensors and motion sensors). It also supports hybrid
positioning using various positioning methods. To support these methods, the
UE or the network measure signals (such as GNSS and LTE/NR signals) and
estimate the position. GNSS-based methods utilize UEs and GNSS radio
receivers, such as Global Positioning System (GPS) receivers. Different GNSS,
such as GPS and Galileo, can be used alone or to find the UE. In the OTDOA
positioning method, the UE times the downlink signals received from multiple
transmission points (TP) such as LTE / NR base stations. Enhanced Cell ID
Positioning (ECID) involves the use of Cell ID with UE measurements or
NGRAN.

Measurements. The air pressure sensor method uses an air pressure sensor to
determine the vertical component of the UE position. In the WLAN positioning
method, the access point identifier (AP), the WLAN measurement performed by
the UE, and the database are used to find the UE. The Bluetooth® positioning
method involves measurement using beacon identifiers and Bluetooth®
beacons. In the TBS positioning method, the UE measures the TBS signal. TBS
comprises a network of terrestrial transmitters that broadcast signals only for
positioning purposes. TBS signals include Metro Beacon System (MBS) signals
and Positioning erence Signals (PRS). The motion sensor method uses various
sensors such as accelerometers, gyroscopes, and magnetometers to determine
the displacement of the UE.

 1.24 Haptic Service

Haptic is a sensation felt when touching an object. Haptics includes tactile
perception (touching the surface) and kinaesthetic perception (perceiving
movement within the body) [TR22.987]. We have applied the latest haptic
feedback devices to different applications (haptic feedback from game
controllers to simulate the touch or kinesthetics of players in virtual reality
games). Due to their low latency, 5G systems can provide tactile feedback
related to vibration, temperature, texture, or electrical stimulation. Examples of
tactile sensations include vibration tactile sensation, shear sensation, wind chill,
and pneumatic sensation. The haptic service transmits haptic information from
one party to the other. This service can be initiated by the UE or the Network
and can be delivered asynchronously or synchronously. Here are some
examples of haptic services.

► Delivery of touch emoji. The service provides tactile information or tactile

emoticons that enhance the communication experience by conveying emotions
or feelings such as laughter and heartbeat. Tactile emoticons can be transmitted
synchronously in real-time with voice and video or asynchronously transmitted
in SMS, MMS, or IM.

► Personalized alarms. This service replaces the default or custom alarm tones
with multi-modal tones that combine custom haptic alarms with sound, video,
and other senses. When the calling party attempts to establish a call with the
caller party, customized tactile alert information and specific information about
the incoming call will be sent to the UE of the called party. The called party UE
generates customized tactile alert feedback suitable for the user.
► Call waiting for a sign. When a subscriber takes part in an active call or a
call on hold, we can notify them of incoming calls using tactile feedback. We
can customize this tactile feedback for different callers. By avoiding
interruptions, haptic feedback can lead to a smoother communication
experience.

► Accident or health crisis. The elderly may fall, thus alerting the server and
allowing timely help. Even if a person cannot move, the rescue will be on the
road because of autonomous driving during a crisis.

1.25 Miscellaneous services

3GPP is evaluating NR-based broadcast and multicast services (MBS), extended
reality services (XR) and multi-user identity modules (SIM) as part of the R17
work/research project. Broadcast and multicast services can significantly
improve system efficiency and user experience. MBS on 5G systems (5GS) can
apply to public safety, mission-critical services, V2X, transparent IPv4/IPv6
multicast delivery, IPTV, software delivery over wireless networks, group
communications, and IoT applications. All NR RRC states will support MBS in
5GS: RRC_CONNECTED, RRC_INACTIVE, and RRC_IDLE. The group
scheduling mechanism will allow UEs to receive broadcast/multicast services.

Furthermore, it will support dynamic switching between multicast and unicast.

It will also support mobility with continuity of service. In the initial
implementation, the R15 physical layer will be reused. Any changes needed to
improve reliability will also be studied (for Example, via uplink feedback). The
resource allocation between unicast and multicast will be flexible. XR is a
general term covering augmented reality (AR), virtual reality (VR) and mixed
reality (MR). We expect edge computing to promote the realization of XR
applications. NR on R15 is designed to support low-latency and high-reliability
communications. In R17, 3GPP will evaluate all aspects of XR support, such as
power consumption, capacity, and mobility. Since users can have personal
subscriptions and commercial subscriptions, the Multi-Universal Subscriber
Identity Module (MUSIM) can be beneficial. The USIM can be a physical SIM
card or an electronic SIM card (eSIM). The USIM can belong to the same
operator or different operators. Currently, MUSIM supports a specific
implementation. Due to the more predictable UE behaviour, standardized
MUSIM support can improve performance. For example, standardized MUSIM
support reduces paging failures (for example, a page sent on one Network when
the UE is on another network) and reduces the possibility of packet loss (for
example, the user is scheduled but cannot receive traffic).

1.26 NR Enhanced 15
3GPP has created an ultra-flexible and high-performance NR air interface in
R15. I expected the NR air interface to become a solid foundation for later
versions. As the picture shows. 3.1 lists the enhancements of NR 5) in R16 and
higher to support the various new services described in section 2.0. I explain
these NR characteristics in Sections following. Figure 1.26: NR enhancement
beyond 5G Phase 1 Integrated Access and Backhaul.

Figure1. 26 NR Enhancements Beyond 5G Phase 1

(IAB) Integrated Access and Backhaul (IAB) means that spectrum can be
shared between (i) wireless access service UE and (ii) wireless backhaul to
achieve a station core network connectivity base. In the future, we can use IAB
for small cell deployments outdoors, indoors, and even on mobile relays (for
example, on buses or trains). We can view IAB as a cost-effective deployment
solution that simplifies radio core connections and reduces the complexity of
Fiber-based transmission networks. IAB also reduced the total implementation
time. As the picture shows. Adapted from [TR38.874] 3.2 illustrates an example
of IAB implementation. 5) 3GPP has extensively studied an adventurous
multiple access scheme called non-orthogonal multiple access (NOMA) but
decided not to continue. This means that OFDMA (and optional SCFDMAjF)
will soon continue to be the p erred multiple access scheme.
 .

Figure1. 26 Integrated access and backhaul

In Figure 1.26, two base stations, IAB node X and IAB node Z use the spectrum
to provide wireless access to their UEs and communicate with the IAB donor
base station that provides connectivity to the network centre (CN). The IAB
node is not directly connected to the CN, and the IAB donor has a CN
connection. In addition, IAB donors can provide wireless access to their own
UEs. 5G gNB can decompose into a central unit (CU) and distributed unit (DU)
specified in R15. IAB also supports multi-hop links, where the IAB node A
base station is connected to the IAB donor through the IAB node Y

Twork synchronization between base stations is essential for effective IAB

implementation. It is also vital to effectively manage the cross-link interference
(CLI) between the access link and the backhaul link. The IAB node contains a
DU and a mobile terminal (MT) 6). The IAB node uses the DU to establish the
RLC channel leading to the UE and MT of the downstream IAB node. The IAB
node uses MT to connect to the upstream IAB node or donor IAB. The IAB
donor includes a CU for its own DU, DU of all its IAB nodes, and a DU to
support its UE and MT of downstream IAB nodes. The following are potential
features or characteristics of the IAB.

► Return in and out of band. In-band backhaul means that the access link and
the backhaul link overlap at least partially in frequency. There is no such
frequency overlap for out-of-band backhaul. Supports spectrum below 6 GHz
and spectrum above 6 GHz.

► RAT and SA and NSA modes. Although NR-based backhaul is the primary
concern, LTE-based backhaul can be supported. The IAB node can operate in
independent NR mode or non-independent NR mode.

► Topological adaptation. This feature can autonomously reconfigure the

backhaul network to reduce the impact of congestion and load shifts. Vehicles,
leaves, or new buildings can cause blockages. Due to traffic changes, load shifts
and consequent node congestion can occur. 6) The radio interface layer of the
mobile terminal (MT) backhaul Uu interface faces the IAB donor or IAB node.

1.27 NR Unlicensed (NRU)

LTE-based Licensed Assisted Access (LAA) uses licensed spectrum as the
anchor carrier frequency and uses unlicensed spectrum carriers based on the
opportunity to increase performance. LAA uses licensed and unlicensed
spectrum carrier aggregation to transmit data in parallel. Since unlicensed
spectrum can immediately get an enormous amount of unlicensed spectrum,
LAA will use the spectrum when the interference is below the threshold. R16
reuses the LAA concept with the NR-based air interface and supports other
deployment scenarios that use unlicensed spectrum [TR38.889]. They
summarize the possible deployment scenarios for NRU below. Scenario A: CA
between the spectrum with licensed NR (primary cell or PCell 7) and the
spectrum without NR license (secondary cell or SCell). The NR SCell in the
unlicensed spectrum can have DL and UL, or just DL. The gNB serving small
cells can quickly implement this type of CA. Scenario B: Dual connectivity
between LTE licensed spectrum (PCell) and unlicensed NIR spectrum (Primary
SCell or PSCell). Dual connectivity means that two base stations have two
independent controllers, LTE eNB and NR gNB. Scenario C: Independent NR
in the spectrum without a license. Here, the frequency of the anchor carrier does
not need to be in the licensed spectrum. NR is only used for the unlicensed
spectrum. This scenario is like MulteFire, where LTE is used for unlicensed
spectrum and does not rely on licensed spectrum. Scenario D: Downlink on
unlicensed spectrum and uplink on licensed spectrum. NR-based gNB uses an
unlicensed spectrum for the downlink but a licensed spectrum for the uplink for
a given UE. This scheme is for DL heavy traffic conditions, such as streaming
video. Scenario E: Dual connection between spectrum with license NR (PCell)
and spectrum without license NR (PSCell). One gNB uses a licensed spectrum
to provide PCell, while the second gNB uses an unlicensed spectrum. NRU
initially focused on unlicensed spectrum below about 7 GHz and is expected to
support higher frequency unlicensed spectrum in future releases. NRU target
frequency bands include the widely used 5 GHz band (such as 5.150 GHz to
5.925 GHz) and the new 6 GHz band (such as 5.925 GHz to 7.125 GHz in the
United States and 5.925 GHz to 6.425 GHz in Europe.). 7) The primary cell or
PCell provides the UE with RRC signalling connections (and radio resources
often used for user services) on a specific carrier frequency. The secondary cell
or SCell provides additional radio resources for user services on a separate
carrier frequency.

1.28 URLLC enhancements

R15 NR defines a frame structure that can be used as a baseline to support
URLLC applications. It supports HARQACK out of order, where the
HARQACK of the second PDSCH can be sent before the HARQACK of the
first PDSCH. Example enhancements include UL Cancellation, and Improved
UL Power ControlR15 supports configuration authorization to facilitate
unlicensed transmission on the uplink. After R15, there may be multiple Type 1
and Type 2 authorizations for configurations that are activated at the same time.
Type 2 authorization means that. The configuration is provided by RRC
signalling, but activation and deactivation are done by PDCCH signalling.
Multiple Simultaneously Activated Configuration Authorization (CG) and
Semi-Persistent Scheduling (SPS) configurations will support a given UE BWP.

R15 NR defines a frame structure that can be used as a baseline to support

URLLC applications. However, to improve AR / VR in the entertainment
industry, factory automation, transportation industry (such as ITS use cases and
remote driving use cases), and power distribution require additional NR
enhancements to improve reliability (such as 10 to 5 to 10–6 errors) Rate) to
reduce latency (for example, 0.5 ms to 1 ms) and ensure tight timing (for
example, a few microseconds). As the picture shows. Figure 1.27 Outlined
specific enhancements to support more URLLC use cases.

► PHY / L1 and MAC improvements. It directed improvements to various

aspects of the physical layer, such as PDCCH, PUSCH, UCI, and
HARQ/scheduling. PDDCH can use compact DCI to achieve faster processing
and configurable field size. More PDCCHs can be monitored in one time slot.
PUSCH can be repeated in one-time slots or consecutive time slots. UCI can
support multiple PUCCHs for HARQACK transmission and can support at least
two HARQACK codebooks to fulfil Different services for a given UE
 Figure1.27: NR enhancements for URLLC

. It supports HARQACK out of order, where the HARQACK of the second

PDSCH can be sent before the HARQACK of the first PDSCH. The second
PUSCH can be programmed before the end of the first PUSCH.

► UL Inter UE transmission priority/multiplexing. Example enhancements

include UL Cancellation and Improved UL Power Control. An indication about
the cancellation of UL can be sent to the UE. If the transmission has already
started, the UE cancels the UL transmission. Otherwise, the UE does not initiate
transmission. Potential power control enhancements include increased dynamic
power from URLLC, improved TPC parameters such as a more extensive TPC
range, and finer transmit power tuning granularity.

► Improved UL Unauthorized Transmission. R15 supports configuration

authorization to facilitate unlicensed transmission on the uplink. After R15,
there may be multiple Type 1 and Type 2 authorizations for configurations that
are activated at the same time. Type 1 authorization means that RRC signalling
is used for activation and deactivation of configuration and authorization. In
contrast, type 2 authorization means that RRC signalling provides the
configuration, but activation and PDCCH does deactivation signalling.

1.29 Industrial Internet of Things (IIoT)

The Industrial Internet of Things has specific requirements that require further
enhancements. For example, you need to support wireless Ethernet and a time-
sensitive network (TSN). The following are specific IIoT enhancements
targeted by 3GPP [TR38.825].

► Repeat PDCP. R15 supports PDCP replication to improve reliability. After

R15, multiple RLC entities (e.g., up to 4) can be configured to allow multiple
PDCP copies of data. The actual subset of RLC entities can be dynamically
controlled (for example, using MAC control elements). Since mirroring
consumes more resources, when PDCP mirroring is active, a mechanism to
improve resource utilization efficiency becomes particularly important. PDP
replication enhanced Selective replication, selective discard, and
activation/deactivation are examples of such mechanisms.

► Prioritization within the EU. To serve higher priority IIoT traffic, an

appropriate prioritization method may be helpful. Examples include the
subsequent dynamic authorization having a higher priority than the previous
dynamic authorization, the configuration authorization has a higher priority than
the dynamic authorization, and the resolution of traffic from higher priority and
lower priority user traffic—the transmission conflicts between the scheduling
requests.

► TSN erence timing. To facilitate accurate time synchronization, broadcast

and Unicast RRC signalling can transmit the erence time from the gNB to the
UE. The goal of time granularity is at least 50 ns.

► Programming. To facilitate scheduling of QoS-aware TSN traffic, the core

network can provide the RAN with information about the TSN traffic pattern,
such as message period, message size, gNB DL message arrival time, and time
arrival date of the UE UL message. Multiple Simultaneously Activated
Configuration Authorization (CG) and Semi-Persistent Scheduling (SPS)
configurations will support a given UE BWP. Supporting SPS cycles that are
shorter than current cycles will further reduce latency.

► Wireless Ethernet. It will support Ethernet header compression to reduce

overhead.

1.30 New frequency band

In R15, 3GPP initially defined FR1 to cover 450 MHz to 6 GHz and FR2 to
cover 24.250 GHz to 52.6 GHz. 3GPP is studying various waveforms that differ
from the currently used OFDM waveforms. These new waveforms may be
better suited for higher frequencies. These higher frequencies provide the
benefits of high channel bandwidth and the high throughput, low latency, and
high capacity that come with it. Higher frequency bands are suitable for the
small cell deployments needed for network densification. The availability of
large bandwidth at higher frequencies makes these frequencies suitable for
wireless. Backhaul. Heavy indoor or outdoor data traffic demand can be met by
deploying large bandwidth, high-frequency hotspots; large bandwidths enable
wireless transfer of high-definition videos and sensor data between the vehicles
and high-definition maps from the infrastructure to the vehicles. Larger sub-
carrier spacing can reduce latency, and broader channel bandwidths can achieve
high data rates and high reliability.

In R15, 3GPP initially defined FR1 to cover 450 MHz to 6 GHz and FR2 to
cover 24.250 GHz to 52.6 GHz. FR1 was later extended in R15 to cover 410
MHz to 7.125 GHz to include the unlicensed 6 GHz spectrum at the highest
frequency and any spectrum available around 400 MHz (for example, GSM 410
or GSM link system from about 410 MHz to about 410 MHz). 430 MHz). 3GPP
is exploring further increases in the 7.125 GHz to 24.250 GHz range and
frequency bands above 52.6 GHz. The 7.125 GHz to 24.250 GHz frequency
band can be divided into multiple frequency bands, such as 7.125 GHz to about
1013 GHz, 101618 GHz to 101618 GHz and 1618 GHz to 24.250 GHz.
Existing FR1/FR2 can be extended, or new FR can be defined. At higher
frequencies (for example, 52.6 GHz to 71 GHz), new OFDM parameter sets can
be defined. Higher propagation path loss, higher phase noise, higher insertion
loss at the RF interface characterizes higher frequencies (for example, higher
low-noise amplifier noise (LNA) and more analogue-to-digital converters. The
challenge of (ADC) noise and lower power amplifier efficiency compared to
lower frequencies 8). 8) 3GPP is studying various waveforms that differ from
the currently used OFDM waveforms. These new waveforms may be better
suited for higher frequencies. However, these higher frequencies provide the
benefits of high channel bandwidth and the high throughput, low latency, and
high capacity that come with it. Figure 1.29 shows an example use case that can
be supported using a spectrum above 52.6 GHz. Figure 1.29: Example use case
for spectrum above 52.6 GHz.

Figure1.29 Example use cases for the spectrum above 52.6 GHz

network densification. With the ultrahigh definition displays, AR/VR

applications and mobile 3D projects, we expect traffic demand to soar even
further. Network densification is an effective mechanism to fulfil the ever-
increasing data traffic demand. The Higher frequency bands are suitable for the
small cell deployments network densification—backhaul and front haul.
availability of large bandwidth at higher frequencies makes these frequencies
suitable for wireless backhaul. Decomposition or disaggregation of the gNB
requires two logical parts of the gNB to communicate with each other. In one
scenario, baseband and RF portions can communicate using wireless front haul
—indoor hotspots and stadiums. Heavy indoor or outdoor data traffic demand
can be met by deploying large bandwidth, high-frequency hotspots. Higher
frequency reuse is possible due to small cells. ITS. They typically carry V2V
and V2X communications in an intelligent transport system out over short
distances. Large bandwidths enable wireless transfer of high-definition videos
and sensor data between the vehicles and high-definition maps from the
infrastructure to the vehicles. Industrial IoT. Factory automation can benefit
from private 5G networks using a high-frequency spectrum. Larger sub-carrier
spacing can reduce latency, and broader channel bandwidths can achieve high
data rates and high reliability.

1.31 Miscellaneous NR Enhancements

Example mobility enhancements include random access channel (RACH)less

handover, fast handover failure recovery, and handover or secondary cell group
(SCG) change with simultaneous connectivity with source cell and target cell.
Another interference of interest is remote interference, where a remote gNB
signal from a macro cell undergoes tropospheric bending and interfere with
another macro gNB. Network densification is an effective mechanism to meet
the ever-increasing data traffic demand. Deploying high bandwidth hotspots
meets data traffic demand. Larger sub-carrier spacing reduces latency, and
broader channel bandwidths achieve high data rates and high reliability

► UE power saving. The UE battery life is a fundamental feature of the user's

overall service experience. Several techniques bring the UE's battery
consumption in connected mode and non-connected mode [TR38.840]. For
example, monitoring of control channels such as PDCCHs, RRM
measurements, suitable transitions between the connected mode and power-
efficient mode, adaptation of MIMO layers, BWP switching, efficient paging,
cross slot scheduling and flexible DRX cycles influence the UE's power
consumption. The UE may aid information such as mobility history and power
p erences, which the network can use to decrease power consumption while
avoiding a significant adverse impact on the service performance (e.g., latency).

► MIMO enhancements. R15 brings benefits such as enhanced codebooks,

erence signal design resilience and support for advanced antenna techniques for
both sub 6 GHz and above 6 GHz deployments. Beyond R15, it can further
enhance MIMO to increase robustness, reduce overhead, and reduce latency.
For example, supporting over two layers in CSI Type II feedback, reducing
PAPR for erence signals, control signalling for noncoherent joint
transmission, more antenna panels and enhanced beam failure recovery and
enhanced DL/UL beam selection enhances the operation of MU-MIMO.►
Mobility enhancements. R15 uses Flute like handover, where the network
controls mobility based on measurements provided by the UE. However,
meeting the 0 ms interruption time target challenge in the current break before
approaching a change in the gNB or secondary cell group (SCG). In particular,
the beam formed NR interface introduces complexities. Example mobility
enhancements include random access channel (RACH) less handover, fast
handover failure recovery, and handover or secondary cell group (SCG) change
with simultaneous connectivity with source cell and target cell. With mobility
enhancements, it supports Various R15supported scenarios, such as intra
frequency handover, inter-frequency handover, inter CU handover,
intraCU/inter handover and intra DU handover.
► NR positioning. NR based positioning techniques aim to achieve &; 3 m
accuracy in horizontal and vertical positioning for indoor deployments and &;
10 m accuracy in horizontal positioning, and &; 3 m accuracy in vertical
positioning for outdoor deployments [TR38.855]. It uses new positioning
erence signals. Example positioning techniques include DL time difference of
arrival (DLTDOA), DL angle of departure (DLAoD), UL time difference of
arrival (ULTDOA), UL angle of arrival (AOA), round trip time (RTT) and
enhanced cell identity (ECID). The UE and the gNB make measurements to
support these techniques. The UE observes erence signals from serving and
neighbouring gNBs and makes DL measurements such as erence signal time
difference (RSTD), erence signal received power (RSRP) and UE RXTX time
difference. In the radio network, it made the following measurements at serving
and neighbouring gNBs:

Relative time of arrival (RTOA)

The angle of arrival (AOA) (including azimuth and zenith angles)

RSRP and gNB RXTX time difference

► CLI and RIM. In a TDD system, when two gNBs use the same slot format
on a carrier frequency, co-channel interference and adjacent channel
interference are minimized. However, if dynamic TDD is implemented and
gNBs independently choose their slot

Formats, co-channel cross-link interference (CLI) occurs. 3GPP's work includes

the definition of refence signals and measurements to quantify CLI,
investigate CLI mitigation mechanisms, and identify coexistence requirements
[TR38.828]. Another interference of interest is remote interference, where a
remote gNB signal from a macro-cell undergoes tropospheric bending and
interferes with another macro gNB. 3GPP is exploring remote interference
management (RIM) mechanisms (e.g., a erence signal to facilitate detection of
remote interference and change of the guard period) to mitigate such remote
interference.

Network densification. With the ultrahigh definition displays, AR/VR apps and
mobile 3D projects, data traffic demand is expected to soar even further.
Network densification is an effective mechanism to meet the ever-increasing
data traffic demand. Higher frequency bands are suitable for the small cell
deployments needed for network densification. Backhaul and fronthaul. The
availability of large bandwidth at higher frequencies makes these frequencies
suitable for wireless backhaul. Decomposition or disaggregation of the gNB
requires two logical parts of the gNB to communicate with each other. In one
scenario, baseband and RF portions can communicate using wireless fronthaul
—indoor hotspots and stadiums. Deploying large bandwidth and high-frequency
hotspots meets heavy indoor or outdoor data traffic demand. Higher frequency
reuse is possible because of small cells. ITS. Large bandwidths enable wireless
transfer of high-definition videos and sensor data between the vehicles and
high-definition maps from the infrastructure to the vehicles. Industrial IoT.
Factory automation can benefit from private 5G networks using a high-
frequency spectrum in a local area with significant frequency reuse thanks to
small cells. Larger sub-carrier spacing can reduce latency, and wider channel
bandwidths can achieve high data rates and high reliability.

5G New Radio

Chapter 2

2. New Radio: Architecture

2.1 Overview of the NG-RAN Architecture

NGRAN provides both NR and LTE radio access. An NG-RAN node is a gNB
(i.e., a 5G base station), shows NR user plane and control plane services or a
ng-eNB, providing LTE/E-UTRAN services towards the UE.

The gNBs and ng-eNBs are connected employing the NG interfaces to the 5G
Core (5GC), to the AMF (Access and Mobility Management Function)
employing the NG-C interface and to the UPF (User Plane Function) employing
the NG-U interface. Both the user plane and control plan for NG-RAN same as
the same high-level architecture scheme, as depicted in Figure 2.1 below.

NG-RAN provides NR and LTE radio access services. An NG-RAN node (base
station) is a gNB (i.e., a 5G base station), services both NR e services, and an
ng-eNB, providing LTE/E-UTRAN services towards the UE.

Figure2. :5G NG-RAN Interface

The gNBs and ng-eNBs using the Xn interface. The gNBs and ng-eNBs are also
connected using NG interfaces to the 5G Core (5GC), more specifically to the
AMF (Access and Mobility Management Function) using the NG-C interface
and to the UPF (User Plane Function) using the NG-U interface. The overall
relation of NG-RAN with the overall 5G system is shown in Figure 2.1. The
user plane and control plane architectures for NG-RAN follow the same high-
level architecture scheme, as depicted in Figure 2.2 below.

Figure2. :Overall NG-RAN Architecture

2.2. Architecture Options and Migration Paths

An essential feature of NG RAN is its ability to operate in standalone (SA) and
"non-standalone" (NSA) operations. They interconnected the gNB through the
Xn interface. In this option, commonly erred to as ENDC (LTENR Dual
Connectivity), ENDC (Evolved Universal Terrestrial Radio Access New Radio)
ers to EUTRA NR Dual Connectivity. This feature allows the mobile device to
exchange data between itself and the NR base station while connecting with the
LTE base station. The UE is connected to the eNB acting as the MN and the
engNB acting as the SN (see Figure 2.3. engNB can send UP to EPC directly or
through eNB. In this option, UE connects to gNB acting as MN and ngeNB
acting as SN. ngeNBs are interconnected via the Xn interface. This option
allows the existing LTE radio infrastructure to connect to the new 5G core
network. In this option, the UE connects to the ngeNB acting as the MN and the
gNB acting as the SN. gNB can send

NG RAN to 5GC directly or through ngeNB. One of the distinguishing features

of NG RAN is the ability to operate in so-called "standalone" (SA) operation
and "non-standalone" (NSA) operation. In SA operation, gNB is connected to
the 5G major network (5GC); in NSA operation, NR and LTE are tightly
integrated and connected to the existing 4G core network (EPC), using dual
connectivity (DC) to the terminal. In the dual connectivity architecture, the
master node (MN) and the auxiliary node (SN) provide wireless resources to the
terminal simultaneously to increase the bit rate of the terminal user. We
specified the NSA and SA architecture options as part of the 3GPPin Release 15
Phase 1 5G standard. It Can derive several configuration options from the
overall architecture, and each of these options represents a viable deployment
option for network operators.

2.3 NR gNB Connected to the 5GC (Option 2)

In this option, they connected the gNBs to the 5G Core Network (5GC) through
the NG interface. The gNBs interconnect through the Xn interface.

2.4 Multi-RAT DC with the EPC (Option 3)

This option, commonly known as EN-DC (LTE-NR Dual Connectivity),

connected a UE to an eNB that acts as an MN and an en-gNB that acts as an SN
(see Figure 2.3. An en-gNB differs from agNB in that it only implements part of
the 5G base station functionality required to perform SN functions for EN-DC.
The eNB is connected to the EPC via the S1 interface and the en-gNB via the
X2 interface. The en-gNB may also be connected to the EPC via the S1-U
interface and other en-gNBs via the X2-U interface. The resulting architecture is
shown in Figure 2.3 below. Notice that the en-gNB may send UP to the EPC
either directly or via the eNB.
 Figure2. : Overall LTE (E-UTRAN)-NR DC architecture.

2.5 Multi-RAT DC with the 5GC, NR as Master

(Option 4)
This option connected a UE to a gNB that acts as an MN and to a ngeNB that
acts as an SN. This option needs the 5G Core to be deployed. The gNB is
connected to 5GC, and the ng-eNB is connected to The gNB via the Xn
interface. The ng-eNB may send UP to the 5G Core either directly or via the
gNB.

2.6 LTE ng-eNB with to the 5GC (Option 5)

In this option, the ng-eNBs are connected to the 5G Core Network (5GC)
through the NG interface. The ng-eNBs interconnect through the Xn interface.
This option allows the existing LTE radio infrastructure (through an upgrade to
the eNB) to connect to the new 5G Core.

2.7 Multi-RAT DC with the 5GC, E-UTRA as Master

(Option 7)
In this option, a UE is connected to an ng-eNB that acts as an MN and to a gNB
that acts as an SN. The ng-eNB is connected to the 5GC, and the gNB is
connected to the ng-eNB via the Xn interface. The gNB may send UP to the
5GC either directly or via the ng-eNB.

2.8 Migration Considerations

When 5G is first rolled out with NR, a scenario is to deploy NR on higher
frequencies than for LTE. When it decided to introduce the 5G Core, this will
“unlock” a new set of deployment scenarios, among which the support for NR
as a standalone Radio Access Technology (RAT) (Option 2), while at the same
time leveraging the deployed LTE nodes as secondary nodes through Dual
Connectivity (DC) (Option 4). possibility for introducing 5G Core is to keep
LTE as the main “anchor”, connecting it to the 5G Core (Option 5) while still
leveraging NR as a secondary node through DC (Option 7). The primary
functions of the E1 interface include the E1 interface management function and
E1 bearer context management function

When 5G is first rolled out with NR, a scenario is to deploy NR on higher

frequencies than for LTE. Here, NR coverage is typically much smaller than
LTE coverage, especially with frequencies above 6 GHz. Then, it is desirable to
leverage the existing LTE coverage to provide continuous nationwide coverage
and mobility while boosting User-plane capacity with NR in target areas with
high traffic load. Option 3 enables operators to launch the NR service in this
way, building on top. Of their existing investments for E-UTRAN and EPC.
When operators decide to introduce the 5G Core, this will “unlock” a new set of
deployment scenarios, among which the support for NR as a standalone Radio
Access Technology (RAT) (Option 2), while leveraging the deployed LTE
nodes as secondary nodes through Dual Connectivity (DC) (Option 4). Another
possibility for the introduction of 5G Core is to keep LTE as the main “anchor”,
connecting it to the 5G Core (Option 5) while still leveraging NR as a secondary
node through DC (Option 7). The choice between deploying NR with 5GC as
“anchor” and keeping LTE as “anchor” with the new 5GC will typically be a
business decision by each operator. It will typically depend on deployed LTE
network density, availability of new frequencies, rate of increase for end-user
traffic demand, and relative “weight” in the business case of new functionality
(such as e.g., slicing) only the new networks can provide.

2.9 5G NR Base Station (gNB) Architecture

The 4G RAN architecture was based on a “monolithic” building block, the eNB.
This resulted in a simple RAN architecture, where few interactions between
logical nodes need to be specified. Since the earliest phases of the NR study,
however, it was felt that splitting up the gNB (the NR logical node) between
Central Units (CUs) and Distributed Units (DUs) would bring additional
benefits. Some benefits in this regard were identified in the early study phase,
including • A flexible hardware implementation that allows scalable, cost-
effective solutions. • A split architecture allows coordination of performance
features, load management and real-time performance optimization. It also
enables virtualized deployments. • Configurable functional splits enable
adaptation to various use cases, such as variable transport latency. The choice of
how to split NR functions in the architecture depends on radio network
deployment scenarios, constraints, and envisaged services. For example, it
depends On the need to support specific QoS settings per offered services (e.g.,
low latency, high throughput, specific user density and load demand per given
geographical area (which may influence the level of RAN coordination), or the
need to interoperate with transport networks having different performance
levels: from ideal to non-ideal. Several possible CU-DU split options, shown in
Figure 2.4, were considered during the study phase. The E-UTRA protocol
stack, which includes PHY, MAC, RLC, PDCP, and RRC, was taken as a basis
for this investigation. The investigation analyzed the split points across the
protocol stack. These split points are depicted in Figure 2.4 as different
enumerated options. After a detailed comparison, 3GPP decided to take Option
2 (based on centralized PDCP/RRC and decentralized RLC/MAC/PHY) as a
basis for normative specification work.

Figure2. :Function Split alternatives.

The prime reason for selecting this option was the close similarity to the
protocol stack split applied in Dual Connectivity: in a DC configuration, the
Master Node (MN) and the Secondary Node (SN) are “split” along the same
point as Option 2.

2.10 Higher Layer Split (HLS) of the gNB

The overall NG-RAN architecture with a split gNB is shown in Figure 2.5
below. As shown in Figure 2.5, in NG-RAN, a set of gNBs is connected to the
5G Core Network (5GC) through the NG interface, and it can interconnect them
through the Xn interface. A gNB may then comprise a gNB-CU and one or
more gNB-DU(s), and the interface between gNB-CU and gNB-DU is called
F1. The NG and XnC interfaces for a gNB terminate in the gNB-CU. The
implementation only limits the maximum number of gNB-DUs connected to a
gNB-CU. In the 3GPP standard, one gNB-DU connects to only one gNB-CU,
but implementations allow multiple gNB-CUs to connect to a single gNB-DU,
e.g., for added resiliency, are not precluded. One gNB-DU may support one or
more cells. The internal structure of the gNB is not visible to the core network
and other RAN nodes, so the gNB-CU and connected gNB-DUs are only visible
to other gNBs and the 5GC as a gNB. The F1 interface supports signalling
exchange and data transmission between the endpoints, separates Radio
Network Layer and Transport Network Layer, and enables the exchange of UE-
associated and non-UE-associated signalling

Figure2. :Higher Layer split of the gNB.

. In addition, they divide F1 interface functions into F1-C and F1-U functions.
F1-C (Control Plane) Functions: • F1 Interface Management Functions: F1
setup, gNB-CU Configuration Update, gNB-DU Configuration Update, error
indication and reset function. • System Information Management Functions: The
gNB-DU is responsible for the scheduling and broadcasting of system
information. For system information broadcasting, the encoding of NR-MIB
and SIB1 is performed by the gNB-DU, while the gNB-CU performs the
encoding of other SI messages. The F1 interface also provides signalling
support for on-demand SI delivery, enabling UE energy saving. • F1 UE
Context Management Functions: These functions are responsible for the
establishment and modification of the necessary UE context. The gNB-CU
initiates the establishment of the F1 UE context, and the gNB-DU can accept or
reject the establishment based on admission control criteria (e.g., the gNB-DU
can reject a context setup or modification request in case resources are not
available). In addition, an F1 UE context modification request can be initiated
by either gNB-CU or gNB-DU. The receiving node may accept or reject the
modification. The F1 UE context management function can also be used to
establish, modify, and release Data Radio Bearers (DRBs) and Signalling Radio
Bearers (SRBs). • RRC Message Transfer Function: This function is responsible
for transferring RRC messages from the gNB-CU to the gNB-DU and vice
versa. F1-U (User Plane) Functions: • Transfer of User Data: This function
allows to transfer of user data between gNB-CU and gNB-DU. • Flow Control
Function: This function allows to control the downlink user data transmission
towards the gNB-DU. Several functionalities are introduced for improved
performance on

an outage, discarding redundant PDUs, retransmitting data indication, and the

status report. The following connected-mode mobility scenarios are supported
in CU-DU split: • Inter-gNB-DU Mobility: The UE moves from one gNB-DU
to another within the same gNB-CU. • Intra-gNB-DU inter-cell mobility: The
UE moves from one cell to another within the same gNB-DU, supported by UE
Context Modification (gNBCU initiated) procedure. • EN-DC Mobility with
Inter-gNB-DU Mobility using MCG SRB: The UE moves from one gNB-DU to
another within the same gNB-CU when only MCG SRB is available during EN-
DC operation. • EN-DC Mobility with Inter-gNB-DU Mobility using SCG
SRB: The UE moves from one gNB-DU to another when SCG SRB is available
during EN-DC operation.

2.11 Separation of CP and UP with Higher Layer

Split (HLS)
To optimize the location of different RAN functions according to different
scenarios and performance requirements, the gNB-CU can be It is further
separated into its CP and UP parts (the gNB-CU-CP and gNB-CU-UP,
respectively). The interface between CU-CP and CU-UP is called E1 (purely a
control plane interface). The overall RAN architecture with CU-CP and CU-UP
separation is shown in Figure 2.6. The gNB-CU-CP hosts the RRC and the
control-plane part of the PDCP protocol; it also terminates the E1 interface
connected with the gNB-CU-UP and the F1-C interface with the gNB-DU. The
gNB-CU-CP hosts the user-plane part of the PDCP protocol of the gNB-CU for
an en-gNB, and the user plane part of the PDCP protocol and the SDAP
protocol of the gNBCU for a gNB. The gNB-CU-UP terminates the E1 interface
connected with the gNB-CU-CP and the F1-U interface connected with the
gNB-DU.

A gNB may consist of a gNB-CU-CP, multiple gNB-CU-UPs, and multiple

gNB-DUs. The gNB-CU-CP is connected to the gNB-DU through the F1-C
interface, and gNB-CU-UP is connected to the gNB-DU through the F1-U
interface. One gNB-CU-UP is connected to only one gNB-CU-CP, but
implementations allowing a gNB-CU-UP to connect to multiple gNB-CU-CPs,
e.g., for added resiliency, are not precluded. One gNB-DU can be connected to
multiple gNB-CU-UPs under the control of the same gNB-CU-CP. One gNB-
CU-UP can be connected to multiple DUs under the control of the same gNB-
CU-CP. The primary functions of the E1 interface include the E1 interface
management function and E1 bearer context management function.
 Figure2. : Overall RAN architecture with CU-CP and CU-UP separation.NG-RAN
Key Interfaces and Protocols

2.12 Xx Interface Family

NG-RAN nodes can be interconnected using the horizontal Xn and X2
interfaces, which are primarily used for three purposes: mobility, multi-
connectivity, and SON (Self Optimized Networks). Xn follows a similar design,
interconnecting two gNBs. Xn and X2 protocol stacks are similar. It relies on
GTPU running on top of UDP and IP. This is illustrated in Figure 2.7: The Xn-
U/X2-U interface provides non-guaranteed user plane PDUs between two NG-
RAN nodes to support dual/multi connectivity or mobility operation. It supports
the flow control function through the Downlink Data Delivery Status procedure.
The Xn-C/X2-C interface uses Xn-AP/X2-AP protocols respectively for
interface maintenance, mobility and dual/multi connectivity operation.

NG-RAN nodes can be interconnected using the horizontal Xn and X2

interfaces, which are primarily used for three purposes: mobility (i.e.,
handover), multi-connectivity and SON (Self Optimized Networks). X2 was
initially defined as the interface between two E-UTRAN nodes, later extended
to support EN-DC (i.e., as the interface between eNB and en-gNB) and further
extended to support NR-DC. Xn follows a similar design, interconnecting two
gNBs. Xn and X2 protocol stacks are similar. In the user plane, it relies on
GTPU running on top of UDP and IP. In the control plane, SCTP is used.
 Figure2. :Xn and X2 protocol stacks

This is illustrated in Figure 2.7: The Xn-U/X2-U interface provides non-

guaranteed user plane PDUs between two NG-RAN nodes to support dual/multi
connectivity or mobility operation. It supports the flow control function through
the Downlink Data Delivery Status procedure. The Xn-C/X2-C interface uses
Xn-AP/X2-AP protocols for interface maintenance, mobility (handover, UE
context retrieval, etc.) and dual/multi connectivity operation.

2.13 NR Radio Interface Protocol

We summarize the architecture of the radio interface protocols that operate
between NG-RAN and the UE and gives some details of the features of each
protocol. The protocols will have some familiarity to those already
knowledgeable of 4G LTE radio protocols, and the description will identify
some of the key differences and reasons for them. The radio protocol
architecture consists of a user plane, used for the transfer of the user data (IP
packets) between the network and the UE, and a control plane that is used for
control signalling between NG-RAN and the UE.
2.14 User plane

The SDAP protocol is a notable difference in the user plane architecture

compared to that of LTE, and I introduced it to support the new flow based QoS
model of the 5G core network. With this new QoS model, the core network can
configure different QoS requirements for different IP flows of a PDU session.
Like LTE MAC, the functionality provided includes multiplexing and
demultiplexing of data from different radio bearers to the transport blocks
carried by the physical layer, priority handling between data from different
radio bearers, and error correction through Hybrid ARQ. A notable addition to
LTE is that the MAC protocol carries control signalling used for beam
management within the physical layer. Figure 2.8 shows the user plane
protocols stack within the UE and the gNB.

2.14.1 Service data adaptation protocol (SDAP)

The SDAP protocol is a notable difference in the user plane architecture
compared to that of LTE, and they introduced it to support the new flow based
QoS model of the 5G core network. With this new QoS model, the core network
can configure different QoS requirements for different IP flows of a PDU
session.
 Figure2. :User plane protocol stack

The SDAP layer provides a mapping of IP flows with different QoS

requirements to radio bearers configured appropriately to deliver that required
QoS. RRC signalling may configure and reconfigure the mapping between IP
flows and radio bearers, but it can also be changed more dynamically without
the involvement of RRC signalling through a lective mapping process.

2.14.2 Packet data convergence protocol (PDCP)

The main functions of the PDCP protocol are to provide header compression
and decompression using RoHC (Robust Header Compression), security
functions including ciphering/deciphering and integrity protection, duplication
of transmitted PDCP PDUs, and reordering and duplicate detection of received
PDCP PDUs. The most significant differences in NR PDCP compared to LTE
are introducing the data duplication over different transmission paths to achieve
extremely high reliability for URLLC (Ultra-Reliable Low Latency)
applications and introducing integrity protection for user plane data.

2.14.3 Radio link control protocol (RLC)

NR RLC is similar in functionality to LTE RLC, with the primary functions

being to provide segmentation, to match the transmitted PDU size to the
available radio resources, and error correction through ARQ. One The
difference compared to LTE RLC is that it does not provide concatenation of
RLC SDUs, with equivalent functionality now provided by the MAC layer, and
does not provide reordering, with the protocol stack instead relying only on the
reordering within PDCP.

2.14.4 medium access control (MAC)

 Like LTE MAC, the functionality provided includes multiplexing and
demultiplexing of data from different radio bearers to the transport blocks
carried by the physical layer, priority handling between data from different
radio bearers, and error correction through Hybrid ARQ. A notable addition
compared to LTE is that the MAC protocol carries control signalling used for
beam management within the physical layer.

2.15 Control plane

The Radio Resource Control (RRC) protocol terminates in the UE and the 5G-
RAN and is used to control and configuration the radio-related functions in the
UE. A significant difference in NR RRC compared to LTE RRC is introducing
a 3-state model with the addition of the RRC INACTIVE state, as shown in
figure 2.9 below.

Figure2. :NR RRC state model

The other significant additions relative to LTE RRC are the support of an ’on
demand’ system information mechanism that enables the UE to request when
specific system information is required instead of the NG-RAN consuming
radio resources to provide frequent periodic system information broadcast, and
the extension of the measurement reporting framework to support beam
measurements for handover within a high-frequency beam-based deployment.

Figure 2.9 shows the control plane protocol stack. The Non-Access Stratum
(NAS) protocols terminate in the UE and the AMF of the 5G core network and
are used for core network-related functions such as registration, authentication,
location updating and session management. The Radio Resource Control (RRC)
protocol terminates in the UE and the 5G-RAN and is used to control and
configuration the radio-related functions in the UE

Figure2. :Control Plane Protocol Stack

. A significant difference in NR RRC compared to LTE RRC is introducing a 3-

state model with the addition of the RRC INACTIVE state, as shown in the
figure below. RRC Inactive provides a state with battery efficiency like RRC
Idle but with a UE context remaining stored within

The NG-RAN so that transitions to/from RRC Connected are faster and incur
less signalling overhead. See Figure 2.10 above. The other significant additions
relative to LTE RRC are the support of an ’on demand’ system information
mechanism that enables the UE to request when specific system information is
required instead of the NG-RAN consuming radio resources to provide frequent
periodic system information broadcast, and the extension of the measurement
reporting framework to support beam measurements for handover within a high-
frequency beam-based deployment.

Summary

As described in this paper, the NG-RAN architecture builds on the success of

the 4G LTE radio architecture while introducing several. Keys, revolutionary
and forward-looking concepts both on the overall architecture front as well as in
protocols.

3GPP has taken several steps to specify interfaces and protocols that ease the
migration of LTE-based cellular networks to 5G and NR. It is expected that
these steps will help the uptake of NR and 5GC while making it easier to evolve
networks in the most cost-efficient manner possible. Enhancements beyond
phase-1 will address requirements and functions needed for industries beyond
cellular mobile broadband: automated driving, industry automation, e-health
services, etc. The 5G platform is promising to deliver the foundation for the
next decade in the digital age.

5G New Radio
Chapter 3

3. NR Radio Access Technology

NR ("New Radio") is the new 5G radio-access technology being developed by
3GPP. The technical work on NR was initiated in the year 2016, with the first
release, being part of the 3GPP release 15 of the NR specifications finalized by
the end of 2017. This first release is limited to non-standalone NR operation,
implying that NR devices rely on LTE for initial access and mobility. The
difference between standalone and non-standalone operations primarily affects
higher layers and the interface to the core network; the basic radio technology is
the same in both cases.

3.1 overview of the NR radio access technology

NR (“New Radio”) is the new 5G radio-access technology being developed by
3GPP. The technical work on NR was initiated in theSpring of 2016 with the
first release, being part of the 3GPP release 15 of the NR specifications
finalized by the end of 2017. This first release is limited to non-standalone NR
operation, implying that NR devices rely on LTE for initial access and mobility.
The final release-15 specifications, to be available in June 2018, will also
support standalone NR operation. The difference between standalone and non-
standalone operations is primarily affecting higher layers and the interface to
the core network; the basic radio technology is the same in both cases.

3.2 NR KEY FEATURES

3.2.1Higher frequencies and spectrum flexibility

One key feature of NR is a substantial expansion of the range of spectrum in
which the radio-access technology can be deployed with support for operation
from below 1 GHz up to 5050 GHz, that is, well into the mm-wave bands,
already in the first release. Higher frequencies are associated with higher radio-
channel attenuation. This can partly be compensated for using advanced multi-
antenna transmission/reception. A substantial coverage disadvantage remains,
especially in non-line-of-sight and outdoor-to-indoor propagation conditions. A
higher-frequency layer with access to a large amount of spectrum can provide
service to a significant fraction of the mobile devices despite the more limited
coverage. This will reduce the load on the more bandwidth constrained lower-
frequency spectrum, allowing this to focus on devices in bad coverage
situations. This will reduce the load on the more bandwidth constrained lower-
frequency spectrum, allowing this to focus on devices in bad coverage
situations.

Operation at mm-wave frequencies offers the possibility for large amounts of

spectrum and very wide transmission bandwidths, enabling extremely high
traffic capacity and extreme data rates. However, higher frequencies are also
associated with higher radio-channel attenuation. Although this can partly be
compensated for using advanced multi-antenna transmission/reception, a
substantial coverage disadvantage remains, especially in non-line-of-Sight and
outdoor-to-indoor propagation conditions. Thus, operation in lower frequency
bands will remain important also in the 5G era. Furthermore, joint operation in
lower and higher spectrum can provide substantial benefits. A higher-frequency
layer with access to a large spectrum can provide service to a significant
fraction of the mobile devices despite the more limited coverage. This will
reduce the load on the more bandwidth constrained lower-frequency spectrum,
allowing this to focus on devices in bad coverage situations. [1]

3.2.2 Ultra-lean design

An issue with current mobile communication technologies is the number of
transmissions carried by network nodes regardless of user traffic. Such “always-
on” transmissions include, for example, signals for base-station detection,
broadcast of system information, and always-on erence signals for channel
estimation. Under typical traffic conditions for which LTE was designed, such
transmissions constitute only a minor part of the overall network transmissions
and have a negligible impact on the network performance. The ultra-lean-design
principle aims at minimizing the always-on transmissions, thereby enabling
higher network energy performance and higher achievable data rates. There is
no spectrum identified for NR between 6 GHz and 24.25 GHz, but requirements
can be added at a later stage if such spectrum becomes available1 GHz 3 GHz
10 GHz 30 GHz 100 GHz in LTE, all devices support the maximum LTE
carrier bandwidth of 20 MHz given the vast maximum bandwidth, it is not
reasonable to require all NR devices to support the maximum NR carrier
bandwidth. Since a slot is defined as a fixed number of OFDM symbols, a
higher subcarrier spacing leads to a shorter slot duration. In principle, this could
be used to support lower-latency transmission, but as the cyclic p ix shrinks
when increasing the subcarrier spacing, it is not a feasible approach in all
deployment scenarios. Operation in the mm-wave domain is another example of
the usefulness of “mini-slot” transmissions as the available bandwidth in such
deployments often is significant, and even a few OFDM symbols can be
sufficient to carry the available payload. This is especially beneficial in
conjunction with Analog beamforming where transmissions to multiple devices
in different beams must be separated in time.

An issue with current mobile communication technologies is the number of

transmissions carried by network nodes regardless of user traffic. Such “always-
on” transmissions include, for example, signals for base-station detection,
broadcast of system information, and always-on erence signals for channel
estimation. Under typical traffic conditions for which LTE was designed, such
transmissions constitute only a minor part of the overall network transmissions
and thus have a negligible impact on the network performance. However, in
very dense networks deployed for high peak data rates, the average traffic load
per network node can be expected to be low, making the always-on
transmissions a more substantial part of the overall network transmissions.

 The always-on transmissions have two negative impacts:

they impose an upper limit on the achievable network energy performance, and

they cause interference to other cells, thereby reducing the achievable data rates.
The ultra-lean-design principle aims at minimizing the always-on transmissions,
thereby enabling higher network energy performance and higher achievable
data rates.

3.2.3 Transmission scheme, bandwidth parts, and frame structure

Like LTE, NR is based on OFDM. However, unlike LTE, where DFT-precoded
OFDM is the sole uplink transmission scheme, NR uses conventional (non-
precoded) OFDM as the baseline uplink transmission scheme due to less
complex receiver structure, especially in combination withUplink spatial
multiplexing[1] and a general desire to have the same transmission scheme in
uplink and downlink. Nevertheless, uplink DFT-precoding can be used as a
complement to enable higher device power-amplifier efficiency in the case of
single-layer transmission.

NR supports a wide range of deployment scenarios, from large cells operating

below 1 GHz up to mm-wave deployments with extensive spectrum allocations.
NR supports flexible numerology with subcarrier spacings ranging from 15 kHz
to 120 kHz with a proportional change in cyclic p ix duration. A smaller sub-
carrier spacing has the benefit of providing a more extended cyclic p ix with
reasonable overhead, while higher subcarrier spacings are needed to handle, for
example, the increased phase noise at higher carrier frequencies. A carrier may
consist of up to 3300 sub-carriers, resulting in a maximum carrier bandwidth of
50/100/200/400 MHz for subcarrier spacings of 15/30/60/120 kHz, respectively.
To realize even larger bandwidths, carrier aggregation can be used.

Although the NR physical-layer specification is band agnostic, not all supported

numerologies are relevant for all frequency bands. The ore, for each frequency
band, radio requirements are defined for a subset of the supported
numerologies, as illustrated in Figure 2.10. There is no spectrum identified for
NR between 6 GHz and 24.25 GHz, but they can easily add requirements later if
such spectrum becomes available.
 Frequency Range 1 Frequency Range 2

Subcarrier spaciing15/30/60 kHz Max carrier Subcarrier spacing

bandwidth 50/100/200 MHz 60/120 kHz Max carrier
bandwidth 200/400 MHz

1 GHz 3 GHz 10 GHz 30 GHz 100 GHz

Figure3. :NR spectrum

In LTE, all devices support the maximum LTE carrier bandwidth of 20 MHz.
However, given the extensive maximum bandwidth, it is not reasonable to
require all NR devices to support the maximum NR carrier bandwidth.
Furthermore, NR allows for device-side receiver-bandwidth adaptation to
reduce the device energy consumption. Bandwidth adaptation ers to using a
modest bandwidth for monitoring control channels and receiving medium data
rates and dynamically open a wideband receiver only when needed to support
extremely high data rates.To handle this, NR defines bandwidth parts that
indicate the bandwidth over which a device is currently assumed to receive
transmissions of specific numerology.

The NR time-domain structure is illustrated in Figure 2.11, with a 10 ms radio

frame divided into ten 1 ms subframes. A subframe is, in turn, divided into slots
comprising 14 OFDM symbols each. That is, the duration of a slot in
milliseconds depends on the numerology. Thus, for the 15 kHz subcarrier
spacing, an NR slot has the same structure as an LTE subframe which is
beneficial from a coexistence perspective. Since they define a slot as a fixed
number of OFDM symbols, a higher subcarrier spacing leads to a shorter slot.
In principle, this could be used to support lower-latency transmission, but as the
cyclic p ix also shrinks when increasing the subcarrier spacing, it is not a
feasible approach in all deployment scenarios. The ore, NR supports a more
efficient approach to low latency by allowing for transmission over a fraction of
a slot, sometimes erred to as “mini-slot." Transmission. Such transmissions
can also pre-empt an already ongoing slot-based transmission to another device,
allowing for immediate transmission of data requiring exceptionally low
latency. Having the flexibility of starting a data transmission not only at the slot
boundaries is also useful when operating in an unlicensed spectrum. In an
unlicensed spectrum, the transmitter is typically required to ensure that other
transmissions do not occupy the radio channel before starting a transmission, a
procedure commonly known as “listen-before talk.” Once the channel is found
to be available, it is beneficial to start the transmission immediately, rather than
wait until the start of the slot, to avoid that some other transmitter initiates a
transmission on the channel. Operation in the mm-wave domain is another
example of the usefulness of “mini-slot” transmissions as the available
bandwidth in such deployments often is significant, and even a
 Figure3. :NR time-domain structure

few OFDM symbols can be sufficient to carry the available payload. This is
especially beneficial in conjunction with analog beamforming, where
transmissions to multiple devices in different beams must be separated in time.

3.2.4 Duplex schemes

The spectrum allocation typically gives the duplex scheme at hand. For lower
frequency bands, allocations are often paired, implying frequency-division
duplex (FDD). TDD increases in importance when moving to higher frequency
bands where unpaired spectrum allocations are more common. These frequency
bands are less useful for wide-area coverage with large cells but are highly
relevant for local-area coverage with smaller cell sizes. In such denser
deployments with smaller cell sizes, the per-cell traffic variations are more rapid
than large-cell deployments with many active devices per cell to address such
scenarios. NR supports dynamic TDD where time-domain resources can be
dynamically assigned to downlink or uplink depending on the instantaneous
traffic needs. In a wide-area macro network with above-rooftop antennas, the
inter-cell interference situation requires coordination of the uplink-downlink
allocation between the cells in such situations. A semi-static allocation is
appropriate with an operation like LTE.

The spectrum allocation typically gives the duplex scheme at hand. For lower
frequency bands, allocations are often paired, implying frequency-division
duplex (FDD). At higher frequency bands, unpaired spectrum allocations are
increasingly common, calling for time-division duplex (TDD). Given the
significantly higher carrier frequencies supported by support for unpaired
spectrum is thus even more pronounced in NR compared to LTE. In contrast to
LTE, NR can operate in paired and unpaired spectrums using a standard frame
structure. The basic frame structure supports both half-duplex and full-duplex
operations. In half-duplex, the device cannot transmit and receive at the same
time. Examples hereof are TDD and half-duplex FDD. In full-duplex operation,
on the other hand, simultaneous transmission and reception are possible with
FDD as a typical example.

As already mentioned, TDD increases in importance when moving to higher

frequency bands where unpaired spectrum allocations are more common. These
frequency bands are less useful for wide-area coverage with large cells but
arehighly relevant for local-area coverage with smaller cell sizes. Furthermore,
some of the problematic interference scenarios in wide-area TDD networks are
less pronounced in local area deployments with lower transmission power and
below-rooftop antenna installations. At the same time, in such denser
deployments with smaller cell sizes, the per-cell traffic variations are more rapid
than large-cell deployments with many active devices per cell. To address such
scenarios, NR supports dynamic TDD where the allocation of time-domain
resources can be dynamically assigned to downlink or uplink depending on the
instantaneous traffic needs. Dynamic TDD enables following rapid traffic
variations, which are particularly pronounced in dense deployments with a
small number of users per cell.

The basic approach to dynamic TDD is for the device to monitor for downlink
control signalling and follow the scheduling decisions. It instructed if the device
to transmit; it transmits in the uplink. Otherwise, it will attempt to receive any
downlink transmissions. The uplink-downlink allocation is then entirely under
the scheduler's control, and any traffic variations can be dynamically tracked.
There are deployment scenarios where dynamic TDD may not be helpful, but it
is much simpler to restrict the dynamics of a dynamic scheme in those scenarios
when needed rather than trying to add dynamics to a Fundamentally semi-static
design as LTE. For example, in a wide-area macro network with above-rooftop
antennas, the inter-cell interference situation requires coordination of the
uplink-downlink allocation between the cells. In such situations, a semi-static
allocation is appropriate with an operation like LTE.

3.2.5 Low latency support

Support for low latency is an essential part of NR that affects many of the
design details. By locating the erence signals and downlink control signalling
carrying scheduling information at the beginning of the transmission and not
using time-domain interleaving across OFDM symbols, a device can start
processing the received data immediately without prior buffering minimizing
the decoding delay. The higher-layer protocols MAC and RLC have been
designed with low latency in mind, with header structures chosen to enable
processing without knowing the amount of data to transmit. This is especially
important in the uplink direction as the device may only have a few OFDM
symbols after receiving the uplink grant until the transmission occurs.Support
for low latency is an essential part of NR that impacts many of the design
details. One example uses “front-loaded” erence signals and control
signalling, as illustrated in Figure 2.11 above. By locating the erence signals
and downlink control signalling carrying scheduling information at the
beginning of the transmission and not using time-domain interleaving across
OFDM symbols, a device can start processing the received data immediately
without prior buffering thereby minimizing the decoding delay.

The requirements on the device (and network) processing times are significantly
tighter in NR compared to LTE. For example, a device is assumed to respond
with a HARQ acknowledgement one slot (or even less for some device
categories) after receiving downlink data. The time from a scheduling grant to
uplink data transfer is in the same range. The higher-layer protocols MAC and
RLC have also been designed with low latency in mind, with header structures
chosen to enable processing without knowing the amount of data to transmit.
This is especially important in the uplink direction as the device may only have
a few OFDM symbols after receiving the uplink grant until the transmission
occurs.

3.2.6 Scheduling and data transmission

One key characteristic of mobile radio communication is the significant and
typically rapid variations in the instantaneous channel conditions stemming
from frequency-selective fading, distance-dependent path loss, and random
interference variations due to transmissions in other cells and by other devices.
Given the extremely high data rates supported by NR, channel coding for data
transmission is based on low-density parity-check (LDPC) codes [2].NR
supports retransmissions on a finer granularity known as code-block group
(CBG). This can be useful when handling pre-emption. An urgent transmission
to a second device may use only one or a few OFDM symbols and cause high
interference to the first device in some OFDM symbols only. In this case, it may
be sufficient to retransmit the interfered CBGs only and not the whole data
block. Dynamic scheduling is the essential operation of NR. It can configure
operations without a dynamic grant. In this case, it configured the device in
advance with resources that can be used for uplink data transmission. Once a
device has data available, it can immediately commence uplink transmission
without going through the scheduling request-grant cycle, thereby enabling
lower latency.

One key characteristic of mobile radio communication is the significant and

typically rapid variations in the instantaneous channel conditions stemming
from frequency-selective fading, distance-dependent path loss, and random
interference variations due to transmissions in other cells and by other devices.
Instead of combatting these variations, it can exploit them through channel-
dependent scheduling where the time-frequency resources are dynamically
shared between users. On a prominent level, the NR scheduling framework is
like the one in LTE. The Scheduler, residing in the base station, takes
scheduling decisions based on channel-quality reports obtained from the
devices. It also takes different traffic priorities and quality-of-service
requirements into account when forming the scheduling decisions.

Each device monitors several physical downlink control channels (PDCCHs),

typically once per slot, although it is possible to configure more frequent
monitoring to support traffic requiring extremely low latency. Upon detecting a
valid PDCCH, the device follows the scheduling decision and receives (or
transmits) one unit of data (a transport block).

Given the extremely high data rates supported by NR, channel coding for data
transmission is based on low-density parity-check (LDPC) codes [2]. LDPC
codes are attractive from an implementation perspective, especially at higher
code rates where they can offer a lower complexity than the Turbo codes used
in LTE.

Hybrid automatic repeat request (ARQ) retransmission using incremental

redundancy is used where the device reports the outcome of the decoding
operation to the base station. In case of erroneously received data, the network
can retransmit the data, and the device combines the soft information from
multiple transmission attempts. However, retransmitting the entire transport
block may sometimes be inefficient. NR, the ore, supports retransmissions on a
finer granularity known as code-block group (CBG). This can also be useful
when handling pre-emption. An urgent transmission to a second device may use
only one or a few OFDM symbols and the ore cause high interference to the
first device in some OFDM symbols only. In this case, it may be sufficient to
retransmit the interfered CBGs only and not the whole data block. Handling of
pre-empted transmission can be further assisted by the possibility to indicate to
the first device the impacted time-frequency resources such that it can take this
information into account in the reception process. Although dynamic scheduling
is the essential operation of NR, operation without a dynamic grant can be
configured. In this case, the device is configured in advance with resources that
can be used for uplink data transmission (or downlink data reception). Once a
device has data available, it can immediately commence uplink transmission
without going through the scheduling request-grant cycle, thereby enabling
lower latency.

3.2.7 Control channels

The operation of NR requires a set of control channels to carry the scheduling
decisions in the downlink and provide feedback information in the uplink. One
significant difference compared to LTE is the more flexible time-frequency
structure of downlink control channels where PDCCHs are transmitted in one or
more control resource sets (CORESETs) which can be configured to span only
part of the carrier bandwidth. The short PUCCH is transmitted in the last one or
two symbols of a slot and can support high-speed feedback of hybrid-ARQ
acknowledgements to realize so-called self-contained slots where the delay
from the end of the data transmission to the reception of the acknowledgement
from the device is in the order of an OFDM symbol, corresponding to a few ten
microseconds depending on the numerology used This can be compared to 3 ms
in LTE and is yet another example on how the focus on low latency in NR has
impacted the design. For situations when the duration of the short PUCCH is
too short of providing sufficient coverage, there are possibilities for longer
PUCCH durations.The operation of NR requires a set of control channels to
carry the scheduling decisions in the downlink and provide feedback
information in the uplink. Downlink control channels are known as PDCCHs
(Physical Downlink Control Channel). One significant difference compared to
LTE is the more. Flexible time-frequency structure of downlink control
channels where PDCCHs are transmitted in one or more control resource sets
(CORESETs) can be configured to span only part of the carrier bandwidth.
Another significant difference compared to LTE is the support for beamforming
of the control channels, which has required a different erence-signal design
with each control channel having its own dedicated erence signal.

Uplink control information such as hybrid-ARQ acknowledgements, channel-

state feedback for multi-antenna operation, and scheduling request for uplink
data awaiting transmission is transmitted using the physical uplink control
channel (PUCCH). There are several different PUCCH formats, depending on
the amount of information and the duration of the PUCCH transmission. The
short PUCCH is transmitted in the

last one or two symbols of a slot and can support high-speed feedback of
hybrid-ARQ acknowledgements to realize so-called self-contained slots where
the delay from the end of the data transmission to the reception of the
acknowledgement from the device is in the order of an OFDM symbol,
corresponding to a few ten microseconds depending on the numerology used.
This can be compared to 3 ms in LTE and is yet another example of how the
focus on low latency in NR has impacted the design. For situations when the
duration of the short PUCCH is too short of providing sufficient coverage, there
are also possibilities for longer PUCCH durations.

3.2.8 Beam-centric design and multi-antenna transmission

Channel-state information (CSI) for the operation of massive multi-antenna
schemes can be obtained by the feedback of CSI reports based on the
transmission of CSI erence signals in the downlink as well as using uplink
measurements exploiting channel reciprocity.With a massive number of antenna
elements for lower frequency bands, the possibility to separate users spatially
increases both in uplink and downlink but requires that the transmitter has
channel knowledge.
For NR, extended support for such multi-user spatial multiplexing is introduced,
either by using high-resolution channel-state-information feedback using a
linear combination of DFT vectors or uplink sounding erence signals targeting
the utilization of channel reciprocity.

Twelve orthogonal demodulation erence signals are specified for multi-user

MIMO transmission purposes, while an NR device can maximally receive eight
MIMO layers in the downlink and up to four layers in the uplink.

Additional configuration of a phase tracking erence signal is introduced in NR

since the increased phase noise power at high carrier frequency bands otherwise
will degrade demodulation performance for higher-order modulation
constellations such as. 64 QAMSupport for a massive number of steerable
antenna elements for both transmission and reception are a key feature of NR.
Many antennas' elements are primarily used for beamforming to extend
coverage at higher frequency bands, while at lower frequency bands, they
enable full dimensional MIMO, sometimes erred to as massive MIMO, and
interference avoidance by spatial separation.

NR channels and signals, including those used for control and synchronization,
have been designed to support beamforming. Channel-state information (CSI)
for the operation of massive multi-antenna schemes can be obtained by the
feedback of CSI reports based on the transmission of CSI erence signals in the
downlink and uplink measurements exploiting channel reciprocity. NR is
deliberately supporting functionality to support analog beamforming and digital
preceding/beamforming to provide implementation flexibility. At high
frequencies, analog beamforming, where the beam is shaped after digital-to-
analogue conversion, may be necessary from an implementation perspective, at
least initially. It can only form analog beamforming results in the constraint that
a receive or transmit beam in one direction at a given time instant and requires
beam-sweeping where the same signal is repeated in multiple OFDM symbols,
but different transmit beams. By having beam-sweeping possibility, they
ensured that it could transmit any signal with a high gain beamformed to reach
the entire intended coverage area.

Signalling to support beam-management procedures is specified, such as

indication to the device to assist the selection of a receiver beam (in case of
analog receive beamforming) for data and control reception. For many antennas,
beams are narrow, and beam tracking can fail. The ore beam-failure/recovery
procedures have been defined using which a device detecting beam failure can
trigger a beam-recovery procedure to rapidly re-establish connectivity.
Additionally, uplink-centric, and reciprocity-based beam management are
possible by utilizing uplink signals.

With a massive number of antenna elements also for lower frequency bands, the
possibility to separate uses spatially increases both in uplink and downlink but
requires that the transmitter has channel knowledge. For NR, extended support
for such multi-user spatial multiplexing is introduced, either by using high-
resolution channel-state-information feedback using a linear combination of
DFT vectors or uplink sounding erence signals targeting the utilization of
channel reciprocity.

We specified twelve orthogonal demodulation refrence signals for multi-user

MIMO transmission purposes, while an NR device can maximally receive eight
MIMO layers in the downlink and up to four layers in the uplink. Moreover,
additional configuration of a phase. The tracking erence signal is introduced
in NR since the increased phase noise power at high carrier frequency bands
otherwise will degrade demodulation performance for higher-order modulation
constellations. 64 QAM.

3.2.9 Initial access

Initial access is when a device finds a cell to camp on, receives the necessary
system information, and requests a connection through random access. Due to
the longer period between consecutive SS blocks, compared to the
corresponding signals/channels in LTE, a device searching for NR carriers must
dwell on each frequency for a longer time. To reduce the overall search time
while keeping the device complexity comparable to LTE, NR supports a sparse
frequency raster for SS block. This implies that the frequency-domain positions
of the SS block could be significantly sparser than the positions of an NR
carrier. Network-side beam-sweeping is supported for both downlink SS-block
transmission and uplink random-access reception to improve coverage,
especially in operation at higher frequencies. At lower carrier frequencies, beam
sweeping may not be needed.

Initial access is when a device finds a cell to camp on, receives the necessary
system information, and requests a connection through random access. The
basic structure of NR initial access is like the corresponding functionality of
LTE [3] with a Primary Synchronization Signal (PSS) and Secondary
Synchronization Signal (SSS) used to find, synchronize to, and identify a
network and a Physical Broadcast Channel (PBCH) that carries a minimum
amount of system information. In the context of NR, the PSS, SSS, and PBCH
are jointly erred to as a Synchronization Signal (SS) block.

Like LTE, there is also a four-stage random-access procedure commencing with

the uplink transmission of a random-access preamble. However, there are some
significant differences between LTE and NR in terms of initial access. These
differences come from the ultra-lean principle and the beam-centric design,
which has required significant changes to the initial access procedures
compared to LTE.
To enable higher NR network energy performance in line with the ultra-lean
principle, the SS block is, by default, transmitted once every 20 ms, compared
to every 5 ms for the corresponding signals of LTE. Because of the more
extended period between consecutive SS blocks, compared to the corresponding
signals/channels in LTE, a device searching for NR carriers must dwell on each
frequency for a longer time. To reduce the overall search time while keeping the
device complexity comparable to LTE, NR supports a sparse frequency raster
for SS block. This implies that the possible frequency-domain positions of the
SS block could be significantly sparser than the possible positions of an NR
carrier (the carrier raster). The sparse SS-block raster enables significantly
reduced time for initial cell search, at the same time as it can significantly
improve the network energy performance due to the longer SS-block period. i

Network-side beam-sweeping is supported for both downlink SS-block

transmission and uplink random-access reception to improve coverage,
especially in case of operation at higher frequencies. It is essential to realize that
beam sweeping is a possibility enabled by the NR design. It does not imply that
it must be used. Especially at lower carrier frequencies, beam sweeping may not
be needed.

3.3 Interworking and LTE coexistence

As it is difficult to provide full coverage at higher frequencies, interworking
with systems operating at lower frequencies is essential.

LTE/NR spectrum coexistence, that is, the possibility for an operator to deploy
NR in the same spectrum as an already existing LTE deployment, has been
identified to enable early NR deployment in lower frequency spectrum without
reducing the amount of spectrum available to LTE.In the second scenario, there
is coexistence only in the uplink transmission direction, typically within the
uplink part of lower frequency paired spectrum, with NR downlink transmission
taking place in spectrum dedicated to NR, typically at higher frequencies.This
scenario attempts to address the uplink-downlink imbalance discussed above.
Dual connectivity within NR and NR will be added in a later release.

As it is difficult to provide full coverage at higher frequencies, interworking

with systems operating at lower frequencies is essential. A coverage imbalance
between uplink and downlink is a common scenario. The power for the base
station compared to the mobile device results in the downlink achievable data
rates often are bandwidth limited, making it more relevant to operate the
downlink in a higher spectrum where wider bandwidth may be available. In
contrast, the uplink is more often power limited, reducing the need for wider
bandwidth. Instead, higher data rates may be achieved on a lower-frequency
spectrum, despite less available bandwidth, because of less radio-channel
attenuation.

Through interworking, a high-frequency NR system can complement a low-

frequency system. The lower frequency system can be either NR or LTE, and
NR supports interworking with either of these. The interworking can be realized
at various levels, including intra-NR carrier aggregation, dual connectivity[2]
with a standard packet data convergence protocol (PDCP) layer, and handover.

However, the lower frequency bands are often already occupied by current
technologies, primarily LTE. Furthermore, an additional low-frequency
spectrum is planned to be deployed with LTE soon. LTE/NR spectrum
coexistence, that is, the possibility for an operator to deploy NR in the same
spectrum as an already existing LTE deployment, has the ore been identified to
enable early NR Deployment in lower frequency spectrum without reducing the
amount of spectrum available to LTE.

It identified two coexistence scenarios in 3GPP and guided the NR design.

In the first scenario (left part of Figure 2.12), it is LTE/NR coexistence in both
downlink and uplink. Observe that this is relevant for both paired and unpaired
spectrum, although the paired spectrum is used in the illustration.

In the second scenario (right part of Figure 2.12), it is coexistence only in the
uplink transmission direction, typically within the uplink part of the lower
frequency paired spectrum, with NR downlink transmission do in the spectrum
dedicated to NR at higher band frequencies. This scenario attempts to address
the uplink-downlink imbalance discussed above. NR supports a supplementary
uplink (SUL) to handle this scenario specifically.

DELETE
NRNR

Downlink and uplink coexistence Uplink-only coexistence

Figure3.

the options for an LTE-compatible NR numerology based on 15 kHz sub-carrier

spacing, enabling identical time/frequency resource grids for NR and LTE, is
one of the fundamental tools for such coexistence. The flexible NR scheduling
with a scheduling granularity as small as One symbol avoids scheduled NR
transmissions colliding with key LTE signals, such as cell-specific erence
signals, CSI-RS, and the signals/channel for LTE initial access. Reserved
resources, introduced for forwarding compatibility, can also be used to enhance
NR-LTE coexistence further. to configure reserved resources matching the cell-
specific erence signals in LTE, enabling an NR-LTE to overlay in the
downlink.

[1] Note that the first releases of LTE did not support uplink spatial
multiplexing

[2] In release 15, dual connectivity is only supported between NR and LTE.
Dual connectivity within NR and NR will be added in a later release.

5GVoice over New

Radio(VoNR)
Chapter 4
4.1 Introduction to VoNR
Voice over New Radio(VoNR) is a novel technology to broadcast voice in 5G
Mobile Networks. It provides significant benefits for mobile users in the future.
Advanced data services, such as high mobile data And low latency is the key
factor affecting the development of 5G mobile networks. However, traditional
voice and video communication services remain key elements of mobile
services, and users continuously need them. The analyst says that the number of
global voice subscriptions will double by 2025. Mobile users demanding voice
services ensure these services are still part of the service provider's package and
business model. However, 5G network voice is more than just satisfying
customers; voice can also play a role in data services provided by 5G.

Voice over New Radio(VoNR) is a novel technology to broadcast voice in 5G

Mobile Networks. It provides significant benefits for mobile users in the future.
Advanced data services, such as high mobile data and low latency, are the key
factors affecting the development of 5G mobile networks. Any solution
implementation must adapt to existing network deployment, so a single solution
is not viable. This IMS architecture plays an increasingly key role in 5G
VoNR.SA implementation involves NR with a 5G core (5GC). This deployment
model is called option 2. The IMS core provides voice as a 5G application
service. Voice services on such networks are called Voice for New Radio
(VoNR). We provide detailed guidance for navigating 5G VoNR in terms of
network implementation, as well as connection options to support NR voice and
enable related VoNR data services. A general introduction to the basic
principles, procedures, technical drivers, and aspects of 5G systems and services
can be found in [ erences]. twenty]

It is simple to keep the existing voice services already in place, but this
achievement requires solving some complex technical challenges. Any solution
implementation must adapt to existing network deployment, so a single solution
is not viable.

This IMS architecture plays an increasingly key role in 5G VoNR. It

implements 5G voice calls as end-to-end Voice over IP (VoIP) connections in
5G. This implementation is managed by the IMS core. Voice and video
communication services on these networks are based. On IP data connections.
Unlike voice services provided by external applications (so-called OTT voice
services), IMS Voice supports quality of service (QoS) management for an
entire 5G system (5GS). The IMS architecture plays an increasingly vital role in
5GVoNR. The IMS core manages end-to-end VoIP connections in 5G. Voice
calls are allowed over VoIP connections. Although IMS can provide voice
services for any type of access (fixed, wired and 2G / 3G) and any 5G
deployment model, 5G is not as flexible. There must be an IMS network to
handle voice services. It does not matter what kind of implementation is
involved. Just as we can link the adoption of IMS with the emergence of
VoLTE, the introduction of 5G is a catalyst to accelerate the modernization of
the voice core from old technology on the 5G network.

As we mentioned before, a single technical approach to 5G VoNR is

impossible. However, VoNR must adapt to the existing deployment model,
namely non-standalone architecture (NSA) or standalone architecture (SA). The
NSA implementation mode, called Option 3, involves LTE plus NR with
Evolved Core Packet (EPC). In contrast, SA implementation involves NR with
a 5G core (5GC). This deployment model is called option 2.

Once it is determined whether the RAT is 5G NR or EUTRA, it is necessary to

consider whether these are coexisting SA networks or dual connectivity
scenarios, namely EUTRAN New Radio Dual Connectivity (ENDC) or
NREUTRA Dual Connectivity (NEDC). Of course, it is also essential to know
if the RAT supports voice services.

The recent 5G implementation has adopted option 3, which means that the
network provider owns the existing 4G LTE network and has implemented a 5G
network alongside it. As a result, 5G NR is a secondary cell, and the core
technology remains the Evolved Packet Core (EPC). During Option 3 operation,
the UE registers with the IMS through the Evolved Packet System (EPS). When
a 5G UE initiates (or receives) a voice call, the EPS system follows the typical
VoLTE procedure. When the service provider chooses option 2, they implement
the 5G network as an SA network without depending on In this option, the IMS
core provides voice as a 5G application service. Voice services on such
networks are called Voice for New Radio (VoNR). Even option 2 has
challenges. In the initial stages of 5G, the geographic coverage of 5G will be
incomplete. When the mobile device moves out of the 5G NR coverage area,
the ongoing VoNR voice call will need to be switched to use VoLTE on the 4G
network. It Needs meticulous network planning and coverage. In the early
VoLTE systems, circuit-switched reservations (CSFB) caused delays and
interrupted calls. The process discussed in detail in this article is called "EPS
support for IMS voice." This process avoids such dropped calls by instructing
the UE to call on the EPS immediately after initiating any voice call. EPS
reservation will cause a handover during the initial setup rather than during a
call. To avoid affecting the user's call experience. With the support of EPS, the
European Union will adopt the highest priority 5G RAT. Since full 5GC support
is not currently needed, EPS can be used as an intermediate step to accelerate
market voice services.

The benefits of 5G VoNR for pure voice calls are the call quality and ultra-high
definition. However, as we noted above, and most importantly, 5G VoNR can
also play a key role in the data services provided by 5G.

This section provides detailed guidance for navigating 5G VoNR in terms of

network implementation and connection options to support NR voice and enable
related VoNR data services. A brief overview of the network and UE signalling
parameters is provided to better understand the control plane.

This section explains the architecture the NG-RAN architecture builds on the
success of the 4G LTE radio architecture while introducing several keys,
revolutionary and forward-looking concepts both on the overall architecture
front and protocols.

The sparse SS-block raster enables significantly reduced time for initial cell
search, at the same time as it can significantly improve the network energy
performance due to the longer SS-block period. At the end of the section, how
to make NR voice successful in testing and measurement is solved. The
consideration was done in laboratory tests and field tests and briefly described
the actual settings that allowed testing of NR voice.
While long term evolution (LTE) uses a few nodes in the evolved packet core
(EPC), 5G defines more network functions managed by network function
virtualization (NFV) include network security and firewalls, network address
translation (NAT), domain name services (DNS), caching, intrusion detection
and more.5G has more NFs that have fewer responsibilities. The next-
generation radio access network (NG-RAN) architecture builds on the success
of the 4G LTE radio architecture while introducing several keys, revolutionary
and forward-looking concepts both on the overall architecture front and
protocols. The technical work on NR was started in the spring of 2016, with the
first release, being part of the 3GPP release 15 of the NR specifications
finalized by the end of 2017. It limited this first release to non-standalone NR
operation, implying that NR devices rely on LTE for initial access and mobility.
The sparse Synchronization Signal (SS)-block raster enables significantly
reduced time for initial cell search, at the same time as it can significantly
improve the network energy performance due to the longer SS-block period.

► Policy control function (PCF) with Rx / N5 PCF: When the session

indication comes through the Rx / N5 interface, and the UE does not have the
priority of the signalling quality of service (QoS) flow, the PCF derives the
priority from allocation and reservation (ARP)) and 5G QoS identifier (5QI)
parameters, as well as related QoS characteristics, are used for signalling
transmission in accordance with service provider policy

The analyst says that the number of global voice subscriptions will double by
2025. Mobile users demanding voice services ensure these services are still part
of the service provider's package and business model. However, 5G network
voice is more than just satisfying. Customers: voice can also play a role in the
new data services provided by 5G.
It is simple to keep the existing voice services already in place, but this
achievement requires solving some difficult technical challenges. Any solution
implementation must adapt to existing network deployment, so a single solution
is not viable.

It is simple to keep the existing voice services already in place, but this
achievement requires solving some complex technical challenges. Any solution
implementation must adapt to existing network deployment, so a single solution
is not viable.

This IMS architecture plays an increasingly key role in 5G VoNR. It

implements 5G voice calls as end-to-end Voice over IP (VoIP) connections in
5G. The IMS core manages this implementation. Voice and video
communication services on these networks are based on IP data connections.
Unlike voice services provided by external applications (so-called OTT voice
services), IMS Voice supports quality of service (QoS) management for an
entire 5G system (5GS). The IMS architecture plays an increasingly vital role in
5GVoNR. The IMS core manages end-to-end VoIP connections in 5G. Voice
calls are allowed over VoIP connections. Although IMS can provide voice
services for any type of access (fixed, wired and 2G / 3G) and any 5G
deployment model, 5G is not as flexible. There must be an IMS network to
handle voice services. It does not matter what kind of implementation is
involved. Just as we can link the adoption of IMS with the emergence of
VoLTE, the introduction of 5G is a catalyst to accelerate the modernization of
the voice core from old technology on the 5G network.

As we mentioned before, a single technical approach to 5G VoNR is

impossible. However, VoNR must adapt to the existing deployment model,
namely non-standalone architecture (NSA) or standalone architecture (SA). The
NSA implementation mode, called Option 3, involves LTE plus NR with
Evolved Core Packet (EPC). In contrast, SA implementation involves NR with
a 5G core (5GC). This deployment model is called option 2.Once it is
determined whether the RAT is 5G NR or EUTRA, it is necessary to consider
whether these are coexisting SA networks or dual connectivity scenarios,
namely EUTRAN New Radio Dual Connectivity (ENDC) or NREUTRA Dual
Connectivity (NEDC). Of course, it is also essential to know if the RAT
supports voice services.

The recent 5G implementation has adopted option 3, so the network provider

owns the existing 4G LTE network and has implemented a 5G network
alongside it. As a result, 5G NR is a secondary cell, and the core technology
remains the Evolved Packet Core (EPC). During Option 3 operation, the UE
registers with the IMS through the Evolved Packet System (EPS). When a 5G
UE starts (or receives) a voice call, the EPS system follows the typical VoLTE
procedure. When the service provider chooses option 2, they implement the 5G
network as an SA network with no other network. In this option, the IMS core
provides voice as a 5G application service. Voice services on such networks are
called Voice for New Radio (VoNR).Even option 2 has challenges. In the initial
stages of 5G, the geographic coverage of 5G will be incomplete. When the
mobile device moves out of the 5G NR coverage area, the ongoing VoNR voice
call will need to be switched to use VoLTE on the 4G network. It Needs
meticulous network planning and coverage. In the early VoLTE systems,
circuit-switched reservations (CSFB) caused delays and interrupted calls. The
process discussed in this article is called "EPS support for IMS voice." This
process avoids such dropped calls by instructing the UE to call on the EPS
immediately after initiating any voice call. EPS reservation will cause a
handover during the initial setup rather than during a call. To avoid affecting the
user's call experience. With the support of EPS, the European Union will adopt
the highest priority 5G RAT. Since full 5GC support is not currently needed, we
can use EPS as an intermediate step to speed up the time to market voice
services.

The benefits of 5G VoNR for pure voice calls are the call quality and ultra-high
definition. However, as we noted above, and Most importantly, 5G VoNR can
also play a key role in the new data services provided by 5G.

5G VoNR provides integration points with applications and content (such as

announcements, music, meetings, etc.). It will also offer enhanced support for
real-time communications, including Rich Communications Service (RCS)
integration. For example, the integration of RCS will allow 5G VoNR to enable
interactive features such as real-time language translation. Many more advanced
features can only work in the 5G NR environment supported by the 5GC
infrastructure.

This section provides detailed guidance for navigating 5G VoNR regarding

network implementation and connection options to support NR voice and enable
related VoNR data services. It provided a brief overview of the network and UE
signalling parameters to understand the control plane better.

4.2 Voice Call Aspects in 5G NR

Ultra-Reliable Low Latency Communications (URLLC) and Mass Machine

Type Communications are the key drivers behind the evolution of 5G.
Traditional services such as voice and video communications remain the
services that major service operators want to provide to their subscribers. Like
Voice for Long Term Evolution (VoLTE), IMS voice in 5GS supports OS; this
is a significant difference compared to voice services provided by external
applications, such as so-called OTH voice services (OTT). The evolution path
describes whether EUTRA only supports voice on the NSA. Connection, and
whether the synchronous NR data connection can be maintained or will be
suspended. This option is called Voice over LTE (VoLTE) in the ENDC
configuration. The current core network is supposed to support voice services,
but the current RAT, which is NR, do Not. In this case, the connection is only
transferred from NR to EUTRA.NR Voice (VoNR) indicates that the NR
network supports voice services, and the 5GC provides a connection to the IMS.
The call is a famous emergency service by-product in the automotive industry
and can be run on LTE as the generation eCall (NGeCall). It is currently
studying how to implement future-oriented emergency call services on 5G NR.

Ultra-Reliable Low Latency Communications (URLLC) and Mass Machine

Type Communications (mMTC) are the key drivers behind the evolution of 5G.
Traditional services such as voice and video communications remain the
services that major service operators want to provide to their subscribers. As
part of technological evolution, a significant shift from a circuit-switched 2G
network initially focused on telephones to a fully packet-switched 4G network
that focused on data communications over the Internet.

This article develops the technical details of how 5G networks support voice
services. Unfortunately, the 5G system will not provide a single technical
solution for voice services, including radio access technology, infrastructure
deployment, and the protocol layer. The purpose here is to describe the
technological evolution required to support voice services and to ensure that the
introduction of 5G will not restrict these services.

From a high-level perspective, whether using NSA or SA mode, EPC is core

network or 5GC, Voice over NR needs to adapt to the existing implementation.
The type of voice support in 5G depends on the radio access technology (RAT)
provided in 5G NR or EUTRA and whether it used the two as independent
networks for coexistence or in dual connectivity scenarios (ENDC or NEDC).
Which RAT supports voice services is also essential. The second issue related
to The types of voice services are the availability of the core network (EPC or
5GC). Which core network supports voice services.

The purpose of this article is to introduce various 5G voice services and some
evolution paths in more detail, to explain how the voice services provided will
change with the evolution of the 5G system (5GS) and 5G access network
(5GAN). The realization of equipment (UE). Finally, some complimentary
support services are considered, such as emergency services, SMS or eCall car
emergency services. NR voice is voice over IP using the IP Multimedia
Subsystem (IMS) infrastructure from a high-level perspective. The advantage of
using IMS is establishing and guaranteeing the quality of Service (QoS) for
each application. The task of IMS is to establish, control and maintain protocol
data unit (PDU) sessions, including all relevant data bearers with corresponding
QoS flows, to obtain the best quality experience for the end-user. Compared
with the data PDU session in 5G, one difference is that through the PDU session
establishment request of the no-access stratum signalling process (NAS), the
UE requests the PDU session to signal IMS. Like Voice for Long Term
Evolution (VoLTE), IMS voice in 5GS also supports QoS. This is a significant
difference compared to voice services provided by external applications, such as
so-called OTH voice services (OTT).

So, there is a question about how to connect IMS to the next generation 5GC
network. The evolution path describes whether EUTRA only supports the voice
on the NSA connection and whether the synchronous NR data connection can
be maintained or suspended. This option is called Voice over LTE (VoLTE) in
the ENDC configuration.

The Evolved Packet System fallback use case describes a situation where 5GC
does not provide voice services. If necessary, it will transfer the connection to
the EPS (VoLTE) connection. Another backup mode is RAT backup. The
current core network is supposed to support voice services, but the current RAT,
which is NR, does not. Here, the connection is only transferred from NR to
EUTRA.NR Voice (VoNR) indicates that the NR network supports voice
services, and the 5GC provides a connection to the IMS. Usually, VoNR is
independent of dual connection so that it can be used with ENDC. However, the
focus is on NR SA, where 5GC is connected to IMS that supports voice
services. Since LTE is running in parallel here, intersystem handover is
mandatory to ensure UE mobility and avoid dropped calls and take advantage of
high-quality key performance indicators (KPIs). Please note that in 3GPP
Release 15, the switch between 5G and 3G/2G is not defined. The ore, no
circuit switch flyback scheme (CSFB) is also possible. 2G / 3G circuit
switching can only be completed in two steps by temporarily connecting to 4G.
In the 16th release of 3GPP, Single Radio Voice Call Continuity (SRVCC) was
introduced, in which VoNR connections can be transferred to 3G. The goal is to
avoid dropped calls when the coverage of 5G services is weakened, and LTE
coverage is unavailable. See Figure 4.1 for related settings. Besides the terminal
capabilities, support for voice services in 5G NR must consider the various
network deployment options. Critical questions are, for example, which RAT to
use (EUTRA or NR), which core network is available (EPC or 5GC) and
whether the evolved NodeB (eNB) is a next generation evolved NodeB
(NGeNB) or just a legacy eNB. We may speak about EPS fallback, RAT
fallback, voice-over NGeNB (NGENDC) or standalone VoNR. The frequency
band allocation applies to such voice call deployment options, i.e., network
operators plan to orm legacy frequency bands in the lower frequencies from
LTE to 5G. With such enhanced coverage, services like VoNR also become
feasible.NR Voice (VoNR) indicates that the NR network supports voice
services and the 5GC provides a connection to the IMS. Normally, VoNR is
independent of dual connection, so it can be used with ENDC. However, the
focus is on NR SA, where 5GC is connected to IMS that supports voice
services. Since LTE is running in parallel here, intersystem handover is
mandatory to ensure UE mobility and avoid dropped calls and take advantage of
high-quality key performance indicators (KPIs). Please note that in 3GPP
Release 15, the switch between 5G and 3G/2G is not defined. The ore, no
circuit switch flyback scheme (CSFB) is also possible. 2G / 3G circuit
switching can only be completed in two steps by temporarily connecting to 4G.
In the 16th release of 3GPP, Single Radio Voice Call Continuity (SRVCC) was
introduced, in which VoNR connections can be transferred to 3G. The goal is to
avoid dropped calls when the coverage of 5G services is weakened and LTE
coverage is unavailable. See Figure 4.1 for related settings. Besides the terminal
capabilities, support for voice services in 5G NR must consider the various
network deployment options. Critical questions are, for example, which RAT to
use (EUTRA or NR), which core network is available (EPC or 5GC) and
whether the evolved NodeB (eNB) is a next generation evolved NodeB
(NGeNB) or just a legacy eNB. We may speak about EPS fallback, RAT
fallback, voice-over NGeNB (NGENDC) or standalone VoNR. The frequency
band allocation applies to such voice call deployment options, i.e., network
operators plan to orm legacy frequency bands in the lower frequencies from
LTE to 5G. With such enhanced coverage, services like VoNR also In addition
to the technological evolution of RAT and core network from 4G to 5G, we
have also witnessed an evolution, especially introducing more complex and
higher-quality voice and video services. The accompanying term for VoNR is
Enhanced Voice Service (EVS), which has a broader audio capacity, higher
sampling rate, better quantization, and higher resolution. become

The EVS voice codec has been introduced into various networks with LTE, but
5G voice services rely more widely on this advanced voice coding algorithm. It
also briefly introduces the principles of EVS and the corresponding voice codec.
Due to the interoperability of N3IWF, you can even choose to establish voice
calls via IMS on access networks other than 3GPP (such as WLAN) and switch
to VoNR. For brevity, the details of this process are omitted here but can be
found in TS 23.502.

feasible.

Figure4. : Deployment scenarios supporting voice in 5G

Although eCall is a popular emergency service by-product in the automotive

industry and can be run on LTE as the next generation eCall (NGeCall), it is
currently studying how to implement future-oriented emergency call services on
5G NR.

4.3 Voice services in an NSA

dual connectivity setup Recent 5G implementations have shown that option they
widely used three as an option in the context of the connection scenario of
infrastructure evolution.

The prerequisite for the voice service is to support IMS.

This is the case with ENDC because EPC is already connected to IMS.

For voice content inheriting QCI = 1, as already recommended, that is VoLTE

Since this configuration supports dual connectivity, it is recommended that the

third default PDN bearer with QCI = 9 can operate as a separate bearer to
provide additional data packets through EUTRA and NR radio interfaces.

5G uses the mid-frequency band, and LTE uses the lower frequency band,
which can cause some coverage limitations

Another drawback is a higher power or battery consumption because the UE

needs to operate on two radio connections simultaneously.

Another drawback is a higher power or battery consumption because the UE

needs to operate on two radio connections simultaneously. It is recommended
that RAN features such as RLC unrecognized mode, Transmission Time
Interval Clustering (TTI), and Strong Header Compression (RoHC), improve
service KPIs with optimized QoERecent 5G implementations have shown that
option they widely used three as an option in the context of the connection
scenario of infrastructure evolution. The ore, ENDC is provided, which has
two radio links, EUTRA and 5G. To speed up the introduction of voice services,
the main aspect of this method is that NR does not support voice services at all
because LTE will cover them. The criterion of the ENDC mode is that NR
cannot exist independently; the ore, LTE coverage is a prerequisite. Operators
who have implemented VoLTE for 4G can continue to use IMS services via
EUTRAN (partially or fully upgraded to ENDC). No impact on IMS. The IMS
system does not even know the upgrade from EUTRAN to ENDC. As before,
all location information disclosed to IMS is based on LTE. All the principles of
VoLTE still apply. PDN connection with IMS Access Point Name (APN) is
used for Session Initiation Protocol (SIP) signalling on the default bearer with
QCI = 5 and voice media on the dedicated bearer with QCI = 1 1]. The
prerequisite for the voice service is to support IMS. This is the case with ENDC
because EPC is already connected to IMS. Suggestions include establishing an
IMS Packet Data Network (PDN) connection for Session Initiation Protocol
(SIP) signalling messages inheriting the LTE QCI = 5 QoS profile and
establishing a parallel PDN connection. For voice content inheriting QCI = 1, as
already recommended, that is VoLTE. Since this configuration supports dual
connectivity, it is recommended that the third default PDN bearer with QCI = 9
can now operate as a separate bearer to provide additional data packets through
EUTRA and NR radio interfaces. Whether the NR link is suspended or held to
the EUTRA bearer at the same time depends on the network implementation
and the maturity of the UE. This proposal represents an early implementation of
supporting voice services when implementing 5G, as it reuses the operator's
investment in its LTE network. Bit rate and delay requirements can be easily
met via LTE. From a long-term launch perspective, ENDC option 3 may
represent a transition phase, extending existing EPSs through the simultaneous
implementation of 5GC and enabling support for VoNR. The challenge and a
slight downside involve providing reliable voice services in the first standalone
NR deployments. In a typical scenario, 5G uses the mid-frequency band, and
LTE uses the lower frequency band, which can cause some coverage
limitations. Another drawback is a higher power or battery consumption
because the UE needs to operate on two radio connections simultaneously.
[ erence. 1] It is recommended that RAN features such as RLC unrecognized
mode, Transmission Time Interval Clustering (TTI), and Strong Header
Compression (RoHC), improve service KPIs with optimized QoE.
Figure4. :Deployment scenario EN-DC supporting VoLTE and internet split bearer
NR and LTE

4.4 Voice services using EPS fallback

4.4.1 Network interworking requirements supporting voice services

Regardless of whether the 5G deployment is based on the NSA or SA mode, the
lessons learned from the introduction of traditional networks have shown that
the initial deployment will not have full coverage.

► Policy control function (PCF) with Rx / N5 PCF: When the session

indication comes through the Rx / N5 interface and the UE does not have the
priority of the signalling QoS flow, the PCF derives the priority from allocation
and reservation (ARP)) and 5G QoS identifier (5QI) parameters, as well as
related QoS characteristics, are used for signalling transmission in accordance
with service provider policy.

Thanks to these interworking and erence points, one can ensure an IP flow
controlled via UPF and SMF independent of whether the UE is camping on
LTE or NR.Regardless of whether the 5G deployment is based on the NSA or
SA mode, the lessons learned from the introduction of traditional networks have
shown that the initial deployment will not have full coverage. The ore, 5GC
must be tightly coupled with EPC, especially the existing IMS VoLTE
supporting infrastructure, to provide seamless voice services throughout the
network, with an acceptable quality of experience (QoE) as a KPI. The goal is
to register UEs on 5G networks, even if voice services are not supported and
need to be switched to LTE. This method is independent of RAT and IMS. The
support for voice services can be obtained through EPC. UEs residing in NR
will be redirected to EPC as the core, and the serving RAT can also be changed
from NR to EUTRA.

Please note that only the backup process of changing the RAT from NR to
EUTRA is called RAT backup voice service. To achieve a tight coupling
between EPC and 5GC, the goal is first to introduce an additional interface
between the entities and functions of the core network. Note that your
implementation depends on the deployment strategies of the infrastructure
providers and operators. Some of these new connections include the following.

► The N6 interface is used to connect the 5GC user plane function (UPF) to the
IMS. TS 23.501 defines N6 as the erence point between UPF and the data
network. For voice support, the data network is now represented by the IMS
signalling system. PDU connections can be established using the QoS flows
required for voice services. N6 is also a prerequisite for full VoNR support.

► S5 interface, used for the control and connection of the user plane between
the session management function (SMF) / UPF that represents the 5GC entity
and the service gateway (SGW) that represents the EPC entity. From an EPC
perspective, the S5U interface replaces the public data network (PGW) gateway
for voice services because they are now established through UPF logic.
► The N26 interworking interface between the mobility management entity
(MME) and the mobility and access management function (AMF) to implement
context transmission and network-controlled mobility scenarios, such as
handover between LTE and 5G. N26 means optional network implementation.
As a primary benefit, TS 23.501 indicates that the interworking process with
N26 provides IP address continuity for mobility between systems for UEs that
support 5GC Non-Access Stratum (NAS) and EPC NAS and operate in single
sign-on mode. Without the N26 interface, assuming the UE is in single
registration mode, the control coordination between MME and AMF must be
routed through SMF and PGW.

► The Home Subscriber Server (HSS) interoperates with Unified Data

Management (UDM), provides a connection to the IMS, and supports querying
the AMF service when the IMS is requested (for details, see TS 29.563).

► Policy control function (PCF) with Rx / N5 PCF: When the session

indication comes through the Rx / N5 interface and the UE does not have the
priority of the signalling QoS flow, the PCF derives the priority from allocation
and reservation (ARP)) and 5G QoS identifier (5QI) parameters, as well as
related QoS characteristics (as applicable), are used for signalling 23.503).

Figure4. : erence points between EPC, 5GC and IMS to ensure tight interworking
for voice support

transmission in accordance with service provider policy (for details, see TS.
Thanks to these interworking and erence points, one can ensure an IP flow
controlled via UPF and SMF independent of whether the UE is camping on
LTE or NR. In addition, mobile terminated connections initiated by IMS can be
routed properly. Even in a single registration situation, due to the optional N26
interworking it is possible to maintain the IP address allocated to the UE.

4.4.2Registration procedure – aspects for voice support

The first important process in a possible 5GS voice service product is the
registration process. If the UE intends to use voice, the UE usage setting must
indicate a voice-centric mode Another important indicator in this control
message is the S1 mode indicator contained in the 5G Mobility Management
Capability Element (5GMM). Using this flag, the UE indicates whether the
possible downgrade process from EPS's IMS voice from 5GS to EPC is
feasible. The dual registration mode requires the UE to independently process
5GMM and EMM contexts at the same time In this mode, the UE independently
maintains the identifiers 5GGUTI and.Wireless devices and networks must
implement these features to ensure high-quality, interoperable IMS-based
communication services for voice, video, and messaging are delivered over
5GC-connected Generation Radio (NG) access.

The first important process in a possible 5GS voice service product is the
registration process. In this process, the UE and the network exchange the
intentions and capabilities of the two entities. More detailed information about
the NAS message flow registration process is provided in TS 24.501. Through
the registration request message, the UE displays its usage settings to the
network. Use settings can be data-centric or voice-centric. If the UE intends to
use voice, the UE usage setting must indicate a voice-centric mode. Another
important indicator in this control message is the S1 mode indicator contained
in the 5G Mobility Management Capability Element (5GMM). Using this flag,
the UE indicates whether the possible downgrade process from EPS's IMS voice
from 5GS to EPC is feasible. Through the exchange of capacity information, the
UE reveals its IMS-related parameters. Common IMS parameters that the UE
can support include, for example, the voice bearer indication on EUTRA, the
voice bearer on the secondary cell group (SCG) bearer, and the echo indication
in EPS. The voiceOverNR parameter indicates the UE's support for NR voice. If
the UE does not support Voice over NR and only supports EPS fallback, it is
recommended to set the parameter flag to voiceOverNR = False and
voiceFallbackIndicationEPSr16 = True. Please note that UE capability is a
process between the UE and the NG Radio Access Network (NGRAN) (TS
38.331). When 5GC receives a registration request, it must provide an
appropriate response based on the network's capabilities or quotation.
Obviously, one of them is the support of the network part for voice services. By
registering to accept the message, the network not only confirms the successful
transition to the 5GMM_REGISjected state, but also confirms the compatibility
with the voice call-related functions. The 5GS network function support
information element that registers to receive messages deserves to be mentioned
in more detail. This information element (IE) contains indicators such as
support for "IMS packet-switched (PS) voice session for 3GPP access", "non-
3GPP voice support", "emergency call service" or "emergency call reservation
support", and whether to support the presence or absence of network interface
N26. In the figure 4.4 below, the registration process focuses only on voice-
specific control information. More detailed information about the NAS
registration procedure is provided in TS 24.501.

Figure4. :Voice registration procedure

TS 23.501 defines some interworking scenarios between 5GS and EPC and
provides more information about N26 and other interfaces. S1 mode means EPS
connection is successful, N1 mode means 5GC connection is successful. The
definition in TS 24.501 is that in N1 mode, the UE accesses the 5G core
network through the 5G access network. Single or double registration means
that the mobile status is processed at the same time. In single sign-on mode,
there is only one mobile state active at any one time. The UE remains in 5GC
NAS mode or EPC NAS mode. Regarding the UE identifier [ . [Figure 20],
during the movement between EPC and 5GC, the UE maps the globally unique
temporary ID EPC (EPCGUTI) to 5GGUTI. As mentioned above, if the
network supports the N26 interface, the UE will maintain the 5G context, such
as IP address allocation, for reuse when moving from 5GC to EPC. To interact
with the EUTRAN connected to the EPC, UEs that support both S1 mode and
N1 mode can work in single registration mode or dual registration mode. For
UEs that support both S1 mode and N1 mode, the first mode (single registration
mode) is mandatory. The dual registration mode requires the UE to
independently process 5GMM and EMM contexts at the same time. In this
mode, the UE independently maintains the identifiers 5GGUTI and EPCGUTI.
The UE can use the corresponding GUTI to perform a new 5GC or EPC
registration/TAU.

A UE operating in dual registration mode can be registered only in N1 mode, S1

mode only, or N1 mode and S1 mode.

In the EPS connection process or initial registration process, if the UE supports

both S1 mode and N1 mode and the network supports interworking, the
interworking mode is selected. According to the support of the N26 interface,
the UE has different options, which can operate in single registration mode or
dual registration mode and certain sub-modes. If 5GMM and EPS Mobility
Management (EMM) are enabled at the same time, the UE operating in single
registration mode must maintain a common registration for 5GMM and EMM.
A UE that supports N1 mode and S1 mode and operates in dual registration
mode does not require coordination between 5GMM and EMM. TS 24.501
defines the coordination details between 5GMM and EMM in single sign-on
mode as supported by the N26 interface.

4.4.3 5G IMS support

The IP Multimedia Subsystem (IMS) represents connection management for
voice services in 5G, as in traditional LTE networks. 3GPP Release 5
introduced IMS to develop the Universal Mobile Telecommunications System
(UMTS) network to provide IP-based multimedia mobile users. Readers
unfamiliar with Basic IMS can er to [ . 6] for more information. IMS has
become a principal component of 3G, cable TV and 4G networks. Technical
improvements have been made in later versions. However, IMS is considered
independent of 5GS.

Initially, IMS was an all-IP system designed to help mobile operators cost-
effectively provide next-generation interactive and interoperable services on an
architecture that provides Internet flexibility.

Session Initiation Protocol (SIP) was selected as the IMS signalling mechanism,
allowing voice, text, and multimedia services to traverse all connected
networks. 3GPP works closely with IETF experts to ensure maximum reuse of
Internet standards and avoid fragmentation of IMS standards. For more
information on the general aspects of IMS, see TS 22.228 and TS 23.228.

Since 5G voice service is not mandatory for the UE and the network, 3GPP has
agreed a general implementation and training strategy to ensure the normal
operation of the voice service when it is provided. The GSM Association
(GSMA) has issued a permanent erence document [ . 8] to define a
configuration file using the minimum set of mandatory features defined in the
3GPP and GSMA specifications. Wireless devices and networks must
implement these features to ensure high-quality, interoperable IMS-based
communication services for voice, video, and messaging are delivered over 5GC-
connected Next Generation Radio (NG) access.
The network that provides voice services in 5GS must support IMS with the
following functions:

► Tell the UE if it should support voice sessions over IMS PS ► The ability to
transfer the address of the call session control function Proxy (PCSCF) to UE

► IMS

► IMS Emergency Service

► Domain Selection for UE

Initiated Session

► IMS Voice Termination Domain Selection

► Supports PCSCF Recovery Process

► PCSCF Discovery based on network repository function (NRF)

► Based on NRF or SCP HSS discovers that

serves the Public Land Mobile Network (PLMN) AMF should send an
indication to UE via 3GPP access during registration process to indicate if IMS
voice sessions are compatible with 3GPP access and non-3GPP access. The UE
usage setting applies to UE with voice capabilities in 5GS and indicates whether
the UE p ers voice services or data services. When the UE chooses to use the
setting as "voice-centric", this includes the IMS voice. When the UE chooses to
use the setting as "data centric", the data service includes any type of user data
transmission without voice media components (TS 24.501).

Mobile devices providing voice services on 5GS must support the IMS
functions required by the Gm and Ut benchmarks. The Gm erence point
supports communication related to session registration and control between UE
and IMS. The Ut erence point helps to manage subscriber information related
to services and configurations [ . 9]. To ensure the normal operation of IMS-
based services, 3GPP and GSMA recommend a set of 11 common IMS
functions that should be supported. More details can be found in [ . 8].

1. SIP registration

UE needs to register with IMS via the SIP protocol, and must support and
implement certain aspects of this registration process:

► A unique SIP registration for an access point name / network name of

Known IMS data (APN / DNN) applies to all IMS services. This is mandatory
for all UEs regardless of local operator or roaming conditions.

► Two separate IMS registries use different APN / DNNs, each of which
supports a subset of IMS services. The app can register with IMS at IMS APN /
DNN and at the same time register with Home Operator Service (HOS) APN /
DNN to combine voice services with Rich Communication Services (RCS).
This depends on the RCS VoLTE single register parameter [ . 10] and applies
if at least one of the rich calling services based on the RCS messaging service or
the Message Session Relay Protocol (MSRP) is enabled. If this parameter is set
to zero, the UE processes two separate IMS records. If set to 1, the UE uses a
single record. If set to 2, if the UE is registered in the home network, the only
IMS registration is used; otherwise, it processes two IMS records.

► PCSCF discovery before initial IMS registration using protocol

configuration option settings during PDU session establishment.

► The verification of SIP registration depends on the relevant APN/DNN. Two

authentication methods are used: IMS Authentication and Key Agreement
(IMSAKA) and SIP Digest [ . 8].
► The IMS user and device identifier in the SIP registry. Based on registration
and APN/DNN authentication, the UE is allowed to derive public and private
IMS identities. Some examples are the well-known International Mobile
Subscriber Identity (IMSI) or International Mobile Equipment Identity (IMEI)
and IMS Private Subscriber Identity (IMPI) as part of the IP Multimedia Service
Identity Module (ISIM) application. (UICC).

► Registration of IMS service. The UE must register for multimedia telephony

voice service (MMTel voice), short message service over IP (SMSoIP), video
service (MMTel conversation video), and MMTEL call editor, always through
the well-known IMS APN. Optionally, through the second concurrent
registration, the UE promotes supplementary services based on the home
network, such as the RCS message service and the MSRP-based rich call
service.

► SIP registration procedure. The UE and IMS network must follow the SIP
registration process defined in TS 24.229. To protect privacy, the UE should
include the user part in the contact address URI, so that the user part is globally
unique and does not reveal any private information. Note that the UE can
perform two separate IMS registration procedures for the default DNN

► Register in IMS with specific services. During the registration process, if the
UE registers for the MMTEL service, the UE will display information related to
the service, such as the IMS Communication Service Identifier (ICSI), to
indicate IMS multimedia phone and multimedia feature labels, such as "audio"
or "video." Similar information disclosure is defined as services such as SMS,
call editor, or RCS (see [ erence 8]).

2. Identity verification:
To ensure secure access to the network, IMS also requires verification of the
identity of the device and the user. GSMA requirements in [ erences]. 8] It
implies the support of two authentication mechanisms (IMSAKA defined in TS
33.203 or SIP authentication through the summary method defined in GSMA [
erence 10]) and provides more details and requirements for these authentication
procedures. The last authentication method includes mandatory UE and optional
network support for HTTP content server authentication. Protecting the integrity
of the network and the UE is mandatory, while protecting the confidentiality of
SIP signalling is optional for the network, depending on whether radio link
layer security is enabled.

3. Addressing

Correct addressing of the user identity is a prerequisite for successful

communication. The UE and IMS core network must support the public user
identity based on the structure defined in TS 23.003, such as the Uniform
Resource Identifier of the Alphanumeric Session Initiation Protocol (SIPURI)
and the international subscriber directory number of the station. mobile
(MSISDN) expressed as a digital phone. URI or SIP URI.). For easy-to-use
graphical user interface (GUI) operations, TS 24.229 defines the ability to use
local numbers such as geographic local numbers, local operator local numbers,
or other private local numbers. The UE and the IMS must support the local
number and the PcallpartyID header in the SIP header. No global routable user
agent URI is required [ . 8].

4.Call establishment and termination:

Regarding IMS call processing parameters, 5G needs the same strategy as LTE,
TS 24.229 defines the exact details. Optionally, domestic operators can
configure a timer for the UE to estimate the round-trip time (T1), the maximum
retransmission time of INVITE responses (T2), or the maximum duration of
messages in the network (T4) (see TS 24.167). The slight difference is that
when the connection is terminated by a CANCEL or BYE message, the UE
includes the reason information as the reason. If available, the UE shall insert
Paccess network info [ . 8]. To take advantage of user availability, some
connection extensions and modification services are also required. For example,
the UE and the network should be able to add video calls to the voice session by
transmitting SDP messages during session establishment. If available, the UE
must support the service provided by the MMTEL call combiner and the RCS
message service defined by GSMA [ erence. 10].

5. SIP prerequisite considerations

TS 24.229 specifies the prerequisite mechanism for MMTEL voice dialogue

services, according to [ . 8]. The network can disable the use of prerequisites
through explicit signalling. For RCS services, SIP preconditions should not be
used.

6. Initial Media and Notification UE must support the reception of voice and
video media related to the initial dialogue, for example. When the SIP 180
message follows the SIP INVITE, and the UE must support the Pearly media
header field. TS 24.628 provides more details on how the UE presents the
locally generated communication progress information.

7. Fork

As a reminder, SIP fork represents a mechanism for dividing SIP calls into
multiple clones of multiple endpoints. This increases usability, for example an
incoming call can ring at multiple endpoints at the same time. With SIP
branching, your desk phone can ring simultaneously with your softphone or SIP
phone on your mobile device. The fork of the
network is determined by the operator. For reasons of interoperability and
forward compatibility, the UE must be prepared to receive the response
generated by the fork request and operate according to the procedures specified
in TS 24.229. In addition, the UE should be able to maintain at least 40 parallel
early conversations until a final response is received in one of the early
conversations, and the UE should support media reception in one of these early
conversations [ erence 8].

8. Signalling Compression

[ . [8] indicates that when the initial IMS registration is completed on the 5G
RAN, the UE should not use methods such as Signaling Compression
(SIGCOMP).

9. SIP Timer Operation

To enable connection flow and handle unexpected timeouts and timeouts, the
UE must handle the session timeout timer during the INVITE process, such as
RFC 4028 [ . 15].

10. Capability Discovery of RCS Features capability or service discovery

mechanism is a process that enables users to understand the subset of RCS
services that can be used to access and / or communicate with their contacts on
certain moments [ erences. 10]. If the UE and the network support this
function, the CAPACITY DISCOVERY MECHANISM configuration
parameter can enable this function exchange process. For the dual registration
situation mentioned above, the capacity swap can occur on either of the two
registers. In the current version of 5G IMS support, capability discovery is
applicable to the following services: MMTEL conversational voice and video,
MMTEL call editor, RCS message service, and MSRP-based rich call services.

11. User agent

The user agent and server headers are used to show the release version and
product information of the instant messaging (IM) client and server. The UE
must include the user-agent header in all SIP request messages and the server
header in all SIP reply messages. In addition, we must include the user agent
header in XCAP's HTTP request. [ eree. 10] Provides more detailed
information about the compiled format of these header files.

Like traditional networks, the upper layers describe voice services and other
applications such as Multimedia Telephony Services (MTSI) or MMTEL. We
define them in TS 26.980. Voice or video is an application layer that is
transmitted through the User Datagram Protocol (UDP) / IP protocol through
the Real Time Protocol (RTP) [ . 13]. In this protocol layer view, the RAT
layer can be EUTRAN on VoLTE or 5G NR on VoNR. Besides transmitting
audio visual content via RTP, the Real Time Control Protocol (RTCP) also adds
additional information about the corresponding RTP stream, such as the
calculated jitter value. IMS uses RTP as a media transmission protocol
independent of the radio layer. RTP and RTCP are in IETF RFC 3550 [ . 13].
The primary purpose of RTP is to allow the receiver to play the received media
at an appropriate rate, because IP networks will introduce delay and packet loss
and jitter. For example, if two IP packets are sent to the same destination with a
delay of 10 milliseconds, there is no guarantee that these two packets will also
reach the destination with a delay of 10 milliseconds. IP packet number 2 can
arrive immediately after packet number 2.1, or later or even earlier. The RTP
timestamp is used to restore the correct time relationship between the IP data
packets.

Since voice or video can be run using streaming media services, the Internet
Engineering Working Group (IETF) is a network control protocol in RFC 2326
[ . 19] designed for entertainment and communication systems to control
streaming media servers. The transmission of streaming data itself is not the job
of RTSP. Most RTSP servers combine RTP with the RTP Control Protocol
(RTCP) for streaming media. In the control plane, there are two main protocols,
namely SIP and Session Description Protocol (SDP). Since some SIP messages
can be transmitted through an IPsec tunnel, an optional IP key exchange (IKE)
can be additionally performed.

Figure4. :Protocol layer of MTSI

This section describes the PDU session details related to IMS connection
configuration. First, we assume that the UE has registered and established a
5GMM context as a prerequisite. The PDU session establishment message is
transmitted to the AMF through the uplink non-access layer transport container
message (UL NAS). Here, the parameter message type indicates the NAS
message PDU session establishment request as the initial request, and the DNN
is set as the name of the corresponding IMS network. SMF connects to IMS, so
the PDU session establishment request contains parameters indicating the IMS
connection request (see TS 24.501). For example, the SSC mode should be set
on the request for SSC mode 1 by the UE. The PDU IE session type shows
whether the UE p ers IPv4 or IPv6 addresses, or one of the two. In the 5GSM
capability, the UE should indicate support for S1 mode and lected QoS. Using
the extended protocol configuration option (PCO), the UE can indicate that an
IMS session should be established (TS 24.008). If the UE establishes a PDU
session for the IMS and the UE is configured to discover the PCSCF address
during connection establishment, the UE must include an indicator in the
Session Management Container (SM) IE (TS 23.502) that it is requesting the
PCSCF IP address. Upon success with establishing a PDU session, the network
responds with the configuration of the PCSCF address in the session
establishment acceptance message, and the network uses the QoS flow 5QI = 5
that inherits the IMS signalling QoS profile to activate the PDU session. IMS
support is clearly a prerequisite for VoNR.

Figure4. : PDU session establishment of IMS voice

4.4 .4 EPS fallback

From a high-level perspective, EPS reservation represents a situation in which
voice calls have been directed from NR to LTE during the connection
establishment process to minimize the connection establishment time. The ore,
the UE can full use the 5GS services provided, and the operator can maintain
the expected KPI through this additional EPC mobility enabler. For example,
during this handover process, the advertised 5G QoS flow parameters will be
mapped to the corresponding EPC bearer. The EPS reservation trigger may be
UE-based, for example, when the UE shows that it only supports EPS with
limited voice support and the ore indirectly requests EPS approval, or it may
be network-based. Specifically, the network can use two standardized mobility
procedures to activate EPS reservations: connection release and redirection to E
UTRAN (here, the N26 interface is helpful to reduce call setup time) or
handover commands between systems. The

backup EPS EPC5GC interconnection with upgraded infrastructure simplifies

the transition to VoNR deployment. If the operator initially implements support
for backup EPS without supporting NR voice, then migrating to VoNR involves
changing the RAN configuration to not enable backup and allowing the voice
QoS flow to stabilize to the NR connected to the 5GC. Then, this transformation
provides a future-oriented and traditional path that can only introduce VoNR
services from a network perspective without risking limiting the services to
existing UEs. The reason the network instructs the UE to use VoLTE may be,
for example. For example, there is a temporary lack of radio resources for voice
in NR, and the connection is transferred to LTE for capacity reasons, or voice
services are not provided at all in 5G. The latter can be applied to 5G operators
that only focus on data services such as eMBB or URLLC. Operators have not
yet intentionally implemented IMS services connected to 5GC. The UE can also
indicate that it only supports the voice EPS service through its capacity
information. The ore, the UE indirectly requests redirection to EPS.

From a protocol layer perspective, the EPS fallback scenario is shown in Figure
4.6. First, the UE camps on 5G NR and establishes a 5G connection. 5GC
provides at least one SIP control connection to recognize that the UE requests a
voice connection. The connection is moved from 5G NR to EUTRA through
rerouting or switching procedures.
The advantage of EPS reservation is that UE or NodeB (gNB) only needs to
support IMS signalling channel (SIP over NR, low real-time requirements) and
does not need to support IMS voice / video communication channels (RTP or
RTCP over NR, high requirements in real time)). and the network. RTP or
RTCP over NR requires lower latency and better 5G NR radio coverage [ .
two]. The ore, it can be considered as an intermediate step to provide VoNR,
depending on the maturity of the equipment backup solution Once all the
necessary voice functions are installed on the network, the migration to VoNR
can be completed. When inputting NR voice, the device input before this step
will still be on site. The capabilities of these devices will determine whether
these devices use NR voice or continue to rely on EPS support. The ore, the
network will support NR voice, including EPS support [ . 1] for a long time.

Figure4. : EPS
When attempting to establish a QoS flow for voice media on NR during call
setup, NGRAN used to establish a QoS flow to SMF and indicated that the
move was in progress.

NGRAN uses one of the following two standardized procedures to initiate

transmission of all PDU sessions from 5GS to EPS:

► Version using redirection messages

► Handover between systems

TS 23.501 and TS 23.502 define intercommunication between 5GC and EPC

and the General Strategy register. In short, the UE performs a registration
process when moving from EPC to 5GC and performs a tracking area update or
initial connection process when moving from 5GC to EPC.

If the UE has at least one PDU session to support session continuity during
interworking, the UE performs the tracking area update process, i.e., the UE has
an EPS bearer ID and QoS parameters mapped EPS.

If the UE does not register a PDU session in the 5GC, or the UE only registers a
PDU session and does not support session continuity during interworking with
the EPC, the UE performs the initial connection procedure, and the UE or EPC
does not support attaching a PDN connection.

Tracking area update details (TS 23.501): "When the UE performs

CMCONNECTED in 5GC and switches to EPS, AMF selects the target MME
according to the source AMF area ID, AMF set ID and target location
information. AMF forwards the UE context through the N26 interface for the
selected MME. In the UE, the AMF also includes the UE usage type if it is
received as part of the subscription data. When the handover process is
successfully completed, the UE performs tracking area update. This completes
the UE’s target EPS Register."

When the UE is served by 5GC, the UE has one or more PDU sessions in
progress, and each session includes one or more QoS flows. The serving PLMN
AMF sends a sign to support the IMS Voice over PS session to the UE during
the registration process, triggering the IMS registration. During this registration
process, the network will show whether it supports the N26 interface. The
signalling flow of EPS backhaul is shown in Figure 4.8 (TS 23.502):

1. The UE resides in NGRAN, and the establishment of a voice session has

started, whether it is the termination of the mobile terminal or the initiation of
IMS (see Figure 6). 2. Modify the PDU session initiated by the network through
the N2

Figure4. : EPS reserved signalling message flow (TS 23.502)

interface and configure the QoS flow to 5QI=1 to make the voice reach
NGRAN.
3. NGRAN is configured to support EPS support for IMS voice and decides to
enable EPS support, considering the capabilities of the UE. During the initial
context configuration (TS 38.413), AMF indicated that "EPS backup voice can
be redirected". In addition, it provides network settings (such as N26
availability) and radio conditions. NGRAN can initiate measurement report
requests from UEs, including EUTRAN as a target.

4. NGRAN establishes a QoS flow for the IMS voice received in step 2
indicating the rejection of the PDU session modification and sends a response
message to the PDU session modification to PGWC + SMF via AMF and
indicates that mobility due to IMS voice reservation is in progress.

5. Considering the capabilities of the UE, NGRAN initiates the access network
handover or release (AN release) through inter-system redirection to EPS.

6. 6a. In the case of the transfer from 5GS to EPS and in the case of redirecting
to EPS with N26 interface between systems, the UE initiates the monitoring
area update process (TAU).

7. 6b. In the case of inter-system redirection to EPS without an N26 interface,

the UE uses a PDN connection request of the request type "handover" to initiate
an attachment.
8. After completing the move to EPS process or as part of the 5GS to EPS
handover process, SMF/PGW restarts to configure dedicated bearers for the
maintained PCC rules, including dedicated bearers for IMS voice. To map 5G
QoS to EPC QoS parameters. PGWC + SMF reports successful resource

allocation and network access information. As in traditional VoLTE, the IMS

signalling related to IMS voice call establishment continues after step 1. At least
during the voice call in EPS, EUTRAN is configured not to trigger any switch
to 5GS. Figure 4.9 shows a message flow with more IMS signalling
information. In this example, we use the redirect command to EUTRA and
assume that the call originates from the N26 interface supported by the mobile
device and the network:

Figure4. : EPS

reserved signalling procedure uses the procedure in step 1, as shown in more

detail Explanation 4. The UE is registered in 5GMM. Assuming that the UE
configuration is voice-centric, the S1 mode is p erred, and the network
supports the N26 interface plus voice services. During the registration process,
the UE and the network exchange their capabilities. The UE can trigger EPS
kickback indirectly. If the UE capability flag UE Capability Information NR
sets the Voice Over NR flag to FALSE, this can be understood as an indirect
request for EPS rollback. NGRAN informs AMF in the UE Radio Capability
Check Response message that the IMS Voice Support Indicator is set to
FALSE. In response, AMF instructs NGRAN to set Redirection EPS Fallback
Indicator to TRUE in the Intial Context Setup Req message. When activated by
a higher layer, the UE starts from steps 2 and 3 and establishes a 5G NR PDU
session for the IMS, as shown in Figure 4.6, and establishes a general Internet
DNN PDU session in parallel.

The IMS registration process in step 4 provides some specific voice details.
Like a general IMS session, the network assigns an IP address for the UE and
informs the PCSCF of the address. SIP REGISTRAR and SUBSCRIBE
signalling messages contain the main access network information (PANI)
[ erence. 16] Such as "3GPPNRFDD" or "3GPPNRTDD" and the SIP
definition of cellular network, with parameters such as mobile country code
(MCC), mobile network code (MNC), tracking area code (TAC) and NR cell
identity (NCI) (TS 24.229). In the above example, the UE is registered in IMS
via 5G; the ore, the length of TAC is 6 hexadecimal digits (for example, the
length in LTE is 4), and there is also NCI. The UE requests the establishment of
a voice call based on the Enhanced Voice Service (EVS) audio codec through
the SDP. To indicate the pending response, IMS sends a session 183 in progress
message. During the dedicated QoS flow establishment and resource
reservation, since VoNR cannot be established, 5GC decides the EPS
reservation of the voice call. The decision is based on the UE's earlier request
for EPS rollback or triggered due to lack of VoNR support for 5GC. The ore,
NRRAN initiates the release of the radio resource control (RRC) connection
(via the RRC Release command or transfer request) and redirects to the
EUTRAN information to return to EPS. In our example, we assume that the
N26 interface is compatible between 5GC and EPC. This enables the TAU
process and the continuation of the DNN and IMS PDU session; the ore, the
UE and PCSCF IP addresses are reserved. In the TAU message, several
parameters are set to specific values: the field containing the oldGUTI is set to
the value "5GGUTI", and the EPS bearer status is set to "Internet and IMS
PDU" as description and "active" as status information. Through the SIP
REREGISTER message, the UE sets the new PANI equal to
"3GPPEUTRAFDD" as the new network access identifier. The last step 6 of
this call establishment process is to establish a voice bearer that inherits QCI =
1. As an example of a real message record, the following figure contains two
excerpts from the signalling procedure of the EPS reservation scenario using the
R & S®CMX500 radio communications tester [ erence]. twenty-four]. First,
the message on the right indicates the establishment of a PDU session. The
excerpt provided here actually indicates two PDU sessions: one with default
5QI and the second with IMS signalling 5QI details. Through the RRC message
(not shown in this excerpt), the 5G NR network triggers the RC RC Release
message with a redirect indication to EUTRA.

Figure4. : EPS fallback signalling scenario extract from the R&S®CMX500

4.5 Voice services using NG-eNB

Since 5G allows multiple deployment methods, the result is multiple
connectivity options. For example, Option 4 and Option 7 introduce 5GC as the
core network to upgrade eNB from LTE to next generation eNodeB (NGeNB).
The goal is to provide application layer bearer and core network services with
5G QoS profiles in the initial stages of 5G deployment. This connection option
may include the provision of voice services, so 5GC needs to connect to IMS to
support these services. One aspect of this deployment scenario is that the UE
camps on the EUTRA carrier in advance; the ore, no handover is required. The
advantage is that the call setup time is shorter. In terms of the protocol structure,
the difference shown in the following figure is the upgrade within the LTE
protocol stack, which causes the Packet Data Convergence Protocol (PDCP)
layer to upgrade from LTE PDCP to NR PDCP. The advantage is full control
over the service, as in the current situation, the 5GC voice service. This type of
voice scenario does not require option 4 or the dual connection in option 7 of
the connection scenario. The ore, if VoNR cannot be achieved due to lack of
coverage, it may represent a viable implementation to upgrade existing LTE
networks to 5GC connections to provide traditional services (such as NGeNB
voice). Obviously, the UE should support the enhancement of NR PDCP
implementation, so it does not support traditional networks. In this case,
NGeNB still needs to provide VoLTE functions in parallel.

Figure4. : Voice services using NB-eNB

4.6 Voice services with RAT fallback
RAT rollback is like EPS rollback. The goal is related to the fact that 5G NR
may not be able to provide full coverage of the voice service. The main
difference is that the EPS backing is a double change. First, it includes the
change of RAT from NR to LTE, and second, the handover of the core network
from 5GC to EPC, as shown in Figure 11. The purpose of the RAT reservation
is to support enhanced eNB ( NGeNB) and provide 5GC as a core like the voice
services provided by NGeNB and 5GC, but the difference is that UE has
previously resided in NR. The ore, when the UE establishes a voice connection
to the network, only the RAT is changed. The goal of 5GC is to define QoS
flow parameters for voice services at an early stage, for example even during
5G NR radio bearer setup, and to maintain them for as long as possible, even
after changes of RAT. TS 23.502 defines this process as an interRAT
reservation for IMS voice in 5GC, because this process includes any RAT as a
target. The ore, it can be used to switch from one NR RAT to another NR
RAT, assuming the operator runs services in parallel on multiple NR RATs, or
it can involve redirection to a target RAN like the traditional EUTRA, which
appears to be the most Useful. Situation. As with EPS support, the conversion is
initiated by a direct change command or by a redirect program. The advantage
is that this mode does not necessarily require dual connections. 5G NR does not
need to provide full voice service coverage, including RTP and RTCP; only a
basic SIP signalling connection is required. The disadvantage is like EPS
reservation, that is, a long call setup time will affect the QoE of the user.
 Figure4. : RAT backup supporting voice services

the RAT backup procedure can be used to trigger RAT changes (not necessarily
EUTRA, because RAT changes from NR to NR are also possible). The
prerequisites are like the EPS reservation scheme; the UE is served by 5GC and
there are one or more PDU sessions in progress, with each session including one
or more QoS flows. The PLMN AMF service indicates support for the IMS
Voice over PS session during the registration process and activates the IMS
registration. The following figure shows the message flow.

1. The UE resides in the originating NGRAN in the 5GS, and the MO or MT

IMS voice session establishment has started.

2. The network initiated PDU session is modified and the QoS flow is
established so that the IMS voice reaches the NGRAN source through the N2
interface.
 Figure4. : IMS Voice RAT Delay

3. If the source NGRAN is configured to support RAT support for IMS voice,
the source NGRAN decides to enable RAT fallback, considering UE
capabilities, network configuration, and radio conditions. To ensure reliable
mobility scenarios, the source NGRAN can initiate measurement report requests
from UEs that include the destination NGRAN. 4. The source NGRAN
responds with a PDU session response message to SMF via AMF indicating the
rejection of the PDU session modification to establish a QoS flow for the IMS
voice and indicates that the mobility due to IMS voice reservation is ongoing. 5.
Initiate NGRAN to initiate Xn-based handover between NGRAN or N2-based
handover or redirection between NGRAN and EUTRA connected to 5GC.

6. After completing the handover or redirection from NGRAN (interRAT) to

EUTRA, connect to 5GC, SMF restarts PDU session modification, and
configures QoS flow for IMS voice. SMF reports successful resource allocation
and access network information.
The IMS signaling related to the establishment of an IMS voice call continues
after step 1, just like in a traditional VoLTE connection. At least for the duration
of the IMS voice call, the destination NGRAN is configured to not trigger a
handover between NGRANs back to the originating NGRAN.

4.7 Voice over NR (VoNR)

Voice over NR stands for voice services provided by 5G RAN, 5GC and IMS.
In addition to assuming voice support in all relevant entities, IMS is also
integrated into the deployment scenario. The advantage is that IMS
management (as in VoLTE) uses PDU sessions established by related QoS
flows to optimize voice quality. The prerequisite for VoNR is UE support for
IMS voice on PS, signalling support for IMS voice and network emergency
service support indicator. It is also assumed that 5GC can be used as a core
network and is likely to represent the standalone implementation of 5G. Option
2 is the underlying infrastructure. VoNR or NSA mode may be compatible with
Option 3, but carriers most likely to implement Option 3 will have voice
connections over LTE . Due to the proliferation of voice services, VoNR can be
seen as a prerequisite for the successful deployment of 5G in standalone
operations, such as the deployment of Option 2. The VoNR protocol stack
includes the 5G NR stack at the link layer of radio. At the application layer,
IMS and voice services, including related voice codecs, are fully supported, ie
the EVS required by 3GPP. Although not related to VoNR support, it is strongly
recommended that 5GC and NR support emergency services; otherwise,
multiple UEs can avoid camping in cell NR.

Figure4. : Voice NR (VoNR)

Voice processing requires that both NR and UE support the QoS flow of the
wireless access voice, that is, the establishment of the QoS flow must be
supported by gNB. VoNR QoS considers non-GBR voice or video QoS
transmissions that support conversational voice and video, IMS signalling, and
MSRP services. It is worth mentioning that the UE can have two IMS registers
according to the configuration of the RCS support parameters .To meet the
voice gap KPI and avoid dropped calls, a certain relationship and
interconnection between 5GS and EPS needs to exist to support mobile
scenarios, that is, the traditional handover between systems from VoNR to
VoLTE. Although

is not a mandatory requirement, it is strongly recommended that, in

implementations that support 5GS voice, they interconnect both SMF and UPF
via the S5 interface, and the existence of the N26 erence point ensures close
intercommunication between AMF and MME. Compliance with this
recommendation increases the opportunity to provide seamless inter-system
mobility with good voice characteristics and short handover outage time? Inter-
system handover, such as initiates transmission of all PDU sessions from 5GS
to EPS, and all QoS flows in IMS PDU / IMS PDN sessions are transmitted
between AMF and MME using inter-system handover signalling to via N26.
SMF and UPF ensure that the IP address of the QoS flow in the IMS PDU
session is reserved and the QoS mapping between the 5QI and the service flow
template (TFT). The change from EPS to 5GS follows the same procedure. In
actual implementation, the handover function can be introduced in stages,
starting with one-way handover (NR in 5GS to LTE in EPS). Bidirectional
handover from EPS to 5GS or reverse handover may be supported in the later
implementation phase. In the case of a one-way handover, the phone remains on
the underlying LTE network for the remainder of the call, even if it returns to
NR coverage. The VoNR message flow follows the connection establishment
message flow in the case of VoLTE [ . 6] Except for EUTRA and EPS, it
involves 5G RAN and 5GS. First, the serving PLMN AMF sends an indication
to the UE during the registration process to indicate whether the IMS Voice
over PS session is supported in the 3GPP access network. When making the
core network domain selection, UEs with IMS Voice over PS capabilities
accessed via 3GPP will consider this indication. The UE and the network
establish a PDU session for the IMS DNN, the QoS flow 5QI = 5, the SSC
mode is 1, and the ON flag is always set to TRUE. In this process configuration,
the UE includes the extended protocol configuration option (ePCO) in the PDU
session establishment request sent to the AMF. In this signalling container, the
UE includes the IPv4 / IPv6 PCSCF Request Information Element to indicate
the IMS DNN [ erence] target. 7]. In addition, AMF forwards these ePCO
options to SMF. SMF obtains the PCSCF address according to the DNN
configuration file, which maintains IMS-related data, and includes the IPv4 or
IPv6 address of the PCSCF in the N1 message sent to AMF. If the UE does not
set the PCSCF container option in the ePCO field, the SMF does not include the
PCSCF address.
 Figure4. : Voice message flow over NR

Optionally, if the UE wants to change the QoS rules, it can request PDU session
modification. Based on the selected media or voice or video codec, the network
sends a complete session modification with negotiated QoS parameters, and the
UE will confirm with a complete modification message. Following these QoS
and media configuration protocols, the UE and UPF use the agreed audio or
video codec on the N3 interface to initiate a user plane data session.

4.7.1 VoNR radio parameter support recommendation

The support for voice services is to integrate and support IMS to connect to
5GC, but to ensure the best QoS for voice and video, a recommended document
[ . 8] has been published and it also describes some functions of the lower
layer. The network and UE must support these radio layer features. To support
voice services with sufficient QoS, these protocol layers must support the
following functions: PDCP layer

-strong header compression method. One function provided by the PDCP layer
is RoHC defined in TS 38.323. At least the UE and the network must support
the "RTP / UDP / IP" configuration file (0x0001) to compress RTP packets and
the "UDP / IP" configuration file (0x0002) to compress RTCP packets. The UE
and the network must support these profiles for IPv4 and IPv6 address
assignment.

Radio bearer: To support 5G voice and video services, the UE and the network
establish signalling and data radio bearers with specific QoS profiles. The RLC
layer provides transmission services in recognized mode (AM) and
unrecognized mode (UM). For the transmission of IMS signalling, the UE and
the network establish an AM data radio bearer (DRB) with 5QI = 5. An
additional AM DRB and 5QI as one of the 6/7/8/9 values are likely to be set for
non-guaranteed bit rate (non-GBR) services at the same time. Depending on
whether the service is voice or video recommended by 3GPP, the UE and the
network configure the UM DRB to 5QI = 1 for voice and/or 5QI = 2 for video.
One suggestion to avoid timeouts is to let NGRAN set a discard Timer (discard
Timer) for IMS and set DRB to an "infinite" value.

Discontinuous reception mode (DRX): To maximize the service life and

effectively manage UE battery consumption, [ . [8] recommends that the UE
and the network should support the MAC layer DRX function.

PHY layer configuration: There is no direct recommendation on VoNR support

that affects the physical layer, such as 3GPP specifications or [ . 8]. 5G NR
does not specify functions like EUTRA's famous TTI packet. Starting from
version 16, some repetitions of the physical uplink shared channel (PUSCH) can
be programmed through the downlink control indicator (DCI), but there is no
automatic grouping in the downlink direction. The RRC layer can schedule
radio resources in semi-persistent mode (SPS). Since voice and video are
characterized by a synchronous data flow, SPS can represent a scheduling
mechanism to reduce signalling overhead on VoNR connections. However, this
is more of a suggestion for physical layer programming than an actual
requirement. The characteristic of voice is its relative tolerance without delay
and the requirement of a specific data rate. The ore, it is recommended to use
GBR DRB for voice services. [ erence. 8] Classify non-GBR bearers as
unsuitable for IMS-based voice services.

Figure4. : voice over NR Radio layer requirements NR

Radio bearer configuration and support request

UM DRB 5QI = 1 (dialogue voice)

UM DRB 5QI = 2 (dialogue video)

AM DRB 5QI = 5 (signalling IMS SIP)) 5QI = AM DRB from 6 to 9 (non-GBR

video)

1 or 2 IMS registration:

► IMS DNN applies to all IMS services

► HOS IMS DNN applies to home operator RCS services

UE PDCP must support RTP and RTCP RoHC compression and the UE MAC
layer will support DRX.

IMS VoNR Signalling and Quality of Service Considerations

As a summary of IMS support in VoNR, this section briefly discusses signalling

flow issues and QoS considerations. There can be two IMS records: one is the
default IMS APN / DNN, and the second is the optional HOS IMS DNN. By
default, the UE registers with the well-known IMS and obtains single network
segment selection assist information (SNSSAI), IPv4 or IPv6 address, and
discovers the PCSCF address. IMS signalling uses 5CQI = 5 and is reserved for
IMS signalling only. The UE shall prevent non-IMS applications from using
this QoS flow.

Optionally, for RCS service support, the UE can register with the IMS DNN of
the Home Operator (HOS) at the same time. We can use the second QoS flow
using the same 5QI for home operator specific HTTP signalling messages with
XCAP or HTTP content. According to the service, [ erence. 8] We recommend
that 5QI = 1 for voice, 5QI = 2 for video, and 5QI = 6 to 9 for non-GBR voice /
video. Note that emergency services and conversational voice share the same
QoS flow. A detailed description of other IMS signalling parameters and
characteristics for voice services can be found in [ erences]. 8].

4.8 Network deployment and connectivity options

supporting voice
This section provides an overview of network connectivity and deployment
options, with a focus on how they support the provision of voice services.
Previously, various voice scenarios were described, focusing on the protocol
and bearer concepts and the underlying architecture. Now, look at these same
scenarios again from the perspective of low-level deployment options.

Option 3 supports voice services

Option 3 ENDC is the implementation of NSA in 5G. The ore, the LTE
connection is mandatory. With this option 3, the EUTRA and EPC core
networks support voice services. According to TS 37.340, the primary cell
group (PCG) (or primary carrier) supports the LTE PDCP or NR PDCP protocol
layer. The ore, there are two ways to implement voice services in Network
Option 3 mode: Traditional VoLTE or Enhanced VoLTE using NR PDCP

Figure4. : Network option 3 for NSA (EN-DC) supporting voice services

. The following figure simplifies these voice service implementations; only the
logical voice flow is described, and the coded voice is summarized as user plane
data and SIP signalling. Dual connectivity between LTE and 5G is only
described symbolically. The advantage of this voice implementation is that it
does not require any upgrades to the existing voice support infrastructure,
except for the slight transition from PDCP to NR PDCP.

Option 7 supporting voice services: Option 7 can be seen in the

background of non-standalone access (NSA) schemes. It represents the NGEN-
DC mode including the connection to 5GC and an upgraded eNB to NG-eNB
but still with LTE as the primary cell RAT. It provides an LTE PCG bearer and
an NR SCG bearer in a dual connectivity scenario. This deployment offers the
flexibility to either run voice services as enhanced VoLTE over NG-eNB
including 5GC, or additionally support to run VoNR over the secondary cell
bearer directly as VoNR and then provide a smooth transition from VoLTE to
VoNR.

Figure4. : Network option 7 for NSA (NGEN-DC) supporting voice services

Option 4 supporting voice services: Option 4 can also be considered as a

non-standalone (NSA) mode. In detail, it represents the NE-DC mode including
the connection to 5GC and an upgraded eNB to NG-eNB. Compared to option
7, however, the NR gNB is the PCG. It provides an NR PCG bearer and an LTE
SCG bearer in a dual connectivity scenario. Like the option 7 connectivity
scenario, this deployment offers the flexibility to either run voice services as
enhanced VoLTE over NG-eNB including 5GC, or additionally support to run
VoNR over the secondary cell bearer directly as VoNR and then provide a
smooth transition from VoLTE to VoNR.

Figure4. : Network option 4 for NSA (NE-DC) supporting voice services

Option 2 standalone (SA) supporting voice services Option 2 represents

the standalone (SA) deployment of 5G NR. If voice services should be
supported in the 5G system, it is completely up to the operator to make sure that
IMS and the speech codes are fully supported. The voice services are offered
based on the technology and methodologies described as voice over NR
(VoNR). Just for completeness and as is also known from legacy technology
deployments (e.g., LTE with CSFB), in the option 2 network deployment it is
likely that an LTE carrier provides radio coverage in addition to NR radio
coverage. Thus, many of the previously described voice scenarios are possible
as well, i.e., EPS fallback providing a handover during connection setup from
NR to LTE, or a RAT fallback if the LTE NG-eNB is connected to the 5GC.
Further details on these setups can be found in [ . 2].

Figure4. : Network option 2 for SA supporting voice services

Strongly recommended: LTE and 5G coexisting in parallel to support inter-

system mobility for best voice QoS. Figure 4.21 attempts to depict the various
voice services in 5G related to the network deployment options. Of course, this
is a simplified view. Real implementations are naturally more complex and
allow mixed modes depending on the UE capability support and network
maturity. The RAT fallback mode is not directly depicted here since it can be
understood as a similar scenario to voice over NG-eNB with 5GC support. The
only difference is the assumption of whether the UE camps before call setup on
the E-UTRA carrier or on the NR carrier and a subsequent handover or
redirection procedure is needed.
 Figure4. : Transition scenarios from VoLTE to VoNR in relation to network 
deployment scenarios [ . 2]

4.9 Speech codec aspects and EVS

I We are not going to go back to the history of telephone services introduced by

John Philip Rice and Alexander Graham Bell as the fathers of modern
communications. Compared with the requirement to provide audible services,
voice transmission on the channel is affected by data rate limitations. In the
early days of 2G (GSM), the limitation of the maximum throughput of 9.6 kbps
led to the introduction of the principle of speech coding. The ore, the audio
signal itself is not directly transmitted as PCM digitized samples as in the
corresponding fixed-line telephone service (such as ISDN) but is a "digital
voice encoder model" that transmits the audio signal. However, the basis of this
speech codec method is the first step to limit the audio bandwidth and digital
samples with a specific quantization ratio. The first full-rate GSM voice codec
limited the audio bandwidth to a lower limit of 300 Hz and an upper limit of 3.4
kHz. The sampling rate is 8 kHz, which can meet the maximum throughput
limit of 9.6 kbps. Some people even proposed the idea of using a voice codec at
half speed to obtain greater network capacity. In the face of competition with
landline networks and the voice quality provided there, the trend of wireless
communications is clearly moving towards an overall better voice quality. This
is first achieved through higher audio bandwidth and higher sampling rate to
reduce quantization granularity. The bandwidth evolution ranges from
narrowband (NB) to wideband (WB), then to ultra-wideband (SWB), and finally
to full band (FB), covering the audible frequency range of 20 Hz to 20 kHz
typical of human ears.

Figure4. : Evolution of Audio Bandwidth

► 300 Hz to 3400 Hz: Narrowband (NB)

► 50 Hz to 7000 Hz: Wideband (WB)

► 50 Hz to 14000 Hz: Ultra-Wideband (SWB)

► 20 Hz to 20000 Hz: fullband (FB)

in future versions, Introduced the concept of a multi-rate adaptive speech

(AMR) codec to cope with rate fluctuations due to changes in radio interface
conditions. The voice encoder provides a variety of voice codec rates and
selects the most appropriate voice rate according to the current radio link quality
or channel speed. The lower voice codec rate allows more channel coding
overhead and ensures stronger voice calls when radio conditions deteriorate.
The speed can be changed every 20 milliseconds, which is the duration of the
speech frame. Tandem Free Operation (TFO) in the context of AMR describes a
protocol in which the same codec is used in either direction in a two-way
communication scheme. To achieve the interoperability and future life of
VoLTE and VoNR, GSMA issued a requirement document [ . 8]. In addition
to the list of voice codecs that the UE must support, this document also
describes in detail how the SDP should indicate and select the available audio
codecs.

The motivation for the introduction of Enhanced Voice Services (EVS) is to

allow a combination of high-quality audio, such as music and voice [ . 3]. For
example, in commercial networks, there is a product called FullHDVoice,
which represents the EVS voice codec that has been implemented in multiple
LTE Advanced networks. The original voice codecs developed in GSM only
focused on voice services, while newer codecs focused on high-end multimedia
services. To ensure interoperability with traditional voice codec technology,
EVS supports all nine AMRWB codec rates. This is called interoperability
mode (AMRWB IO). The audio encoder accepts its input and can output to the
decoder as a 16-bit unified pulse code modulation (PCM) signal at a sampling
rate of 8 kHz, 16 kHz, 32 kHz, or 48 kHz. The audio can be converted by Alaw
or µlaw (8 kHz) 13-bit narrowband PCM or wideband (16 kHz) 14-bit unified
in the audio part of the UE or initiated and terminated from the network side or
the public switched telephone network (PSTN). The source codec provides a
total of 11 bit rates and supports various audio bandwidths as the primary EVS
mode. For traditional interworking, nine different voice codec bit rates
(AMRWB) are supported. In detail, the source codec maps audio samples (20
milliseconds) as input to the 16-bit unified PCM format to generate coded
speech blocks. The EVS codec uses a hybrid coding scheme, combined with a
linear prediction (LP) coding technology based on Algebraic Code Excited
Linear Prediction (ACELP), which is used for speech signals and transform
coding methods for general content. Like traditional codecs,
 Figure4. : EVS mode, audio bit rate and bandwidth

Voice Activity Detection (VAD) can output Discontinuous Transmission (DTX)

signals instead of non-existent audio, and the receiving entity will reproduce
Comfort Noise Generating (CNG) audio signals to disguise maintaining the link
and saving bandwidth. The EVS codec can switch between these

different encoding modes without artefacts (TS 26.445).

AMR-WB interoperable mode for legacy codecs compliance

Since our objective is to provide a concise introduction to the speech codec

evolution to better understand voice aspects in 5G, enhanced voice services
(EVS) are illustrated in Figure 4.24 in an exemplary manner.

Figure4. : Audio processing functions of EVS codec, TX side (TS 26.441)

The Enhanced Voice Service Speech Scrambler includes a multi-rate audio

encoder optimized for mixed content signal operation (voice and music), a
source control rate scheme, a voice or sound activity detector, a comfort noise
generation system and error concealment. Mechanism to combat the effects of
transmission errors and loss of voice packets (TS 26.441). Since voice data
packets can be transmitted over a packet switched network, the jitter buffer
management can ensure that the audio signal is output in time alignment
without excessive delay.

The focus of this section is on the speech codec. Other popular modern cellular
communication systems include video communication. This requires support
and definition of video codecs. In TS 26.114, 3GPP stipulates those networks
and UEs supporting Video over NR (ViNR) services must support IUT
Recommendation H.264 as a video codec. There are multiple video codecs, and
due to their evolution, GSMA has issued a list of requirements. To ensure
interoperability, these video codecs must be compatible with the UE [ . 8]:

► ITUT recommends H.264: Restricted Baseline Profile (CBP) ► ITUT

recommends H.264: Advanced Video Coding (AVC)) Or restricted high profile
(CHP)

► ITUT recommends H.265: High Efficiency Video Encoding (HEVC) Main

Profile

4.10 Supplementary Voice Service, Emergency Call

and SMS

4.10.1 Supplementary Voice Service

Along with organizations such as and GSMA and Open Together with
organizations such as the Mobile Alliance (OMA), TS 24.173 defines and
promotes certain supplementary service telephones (MMTEL) for multimedia
telephony. Although they are not related to 5G, [ . 8] It is recommended to
approve these services for proactive service support and longevity of use cases.
In addition to the direct IMS configuration parameters, the UE should also
support a wide range of supplementary voice services. Among these voice
services, there are some well-known candidate services, such as calling party
presentation, waiting indication, incoming or outgoing call blocking,
international call blocking, temporary multi-party conferences, etc. See
[ erence. 8] Obtain a complete list of supplementary services that are requested
to be compatible with the UE.

Complementary MMTEL services include services such as XML Configuration

Access Protocol (XCAP) [ . 14], which is an application layer protocol that
allows clients to read, write, and modify application configuration data stored
on the server. Multi-party conferences can be established instantly through the
three-way session creation process. The IMS core network must support a
specific list of conference attributes, such as conference information, maximum
number of users, user screen, media support (such as voice and / or video), and
indication of connection or disconnection status. As is familiar in traditional
networks, 5G supplementary voice services must also support mechanisms for
message and call waiting instructions, initiation or termination of identification
restrictions, and communication transfer. 5G IMS supplementary services, ue to
security issues such as spam and tracking, or just to avoid high costs, also
support a wide range of communication blocking mechanisms.

4.10.2 SMS in 5G
The concept of short message service (SMS) introduced in the early days of 2G
is still an important use case for 5G. There are two ways to transmit SMS
messages through 5G access (like LTE). The first method is to use IMS as SMS
(SMSoIP) on the IP of the management and coordination network to ensure
correct data transmission. The second method is SMS over 5G NAS
(SMSoNAS), which is a method of encapsulating SMS data containers in 5G
control messages. In SMSoNAS, initiated and terminated SMS messages are
transmitted between UE and AMF through NAS messages. According to [ . 8],
for UEs claiming to be SMS capable, both SMS transmission methods are
mandatory, and the network can choose which options to provide. For the sake
of completeness, we must mention that it is also possible to transmit short
messages through the RCS message service, but this is not the focus of this
section. The Short Message Service Function (SMSF) is defined in 5GS, which
is used to use the traditional MAP transmission protocol or Diameter [ . 12] It
is used for SMS exchange between UE and SMS Service Center (SMSSC). In
SMSoIP, an SMS Service Gateway for SMS over IP (IPSMGW) must exist to
start and end SMS. The IPSMGW can also perform the MT domain selection
for other accesses (4G, 3G, 2G), and the transmission of SMS between

UE and IPSMGW is done through IP.

5GS UE support voice should support SMS on NAS and SMS on IP, and each
operator can freely decide whether to support SMS on NAS, SMS on IP or both.
These SMS solutions can be used in combination or in the case of EPS backup
for voice [ . 1]. During the 5GS registration process, the UE includes an
indication of "SMS support" in the registration request, indicating the ability of
the UE to transmit SMS via NAS. TS 23.502 provides more detailed
information about the registration process and various SMS connection
scenarios involving MS messages initiated or terminated on the mobile device
when the UE is in the CM_IDLE or CM_CONNECTED state.

Figure4. : SMS in 5G [ . 1]
By way of example, the message flow for a mobile originating SMS over NAS
in the CM_IDLE state is illustrated in Figure4.25. The main function applied to
the 5G system is the short message service function (SMSF). This represents the
5G function that provides the ability to deal with SMS and interconnect to the
legacy SMS interworking MSC (SMSIWMSC). The SMSIWMSC ensures
delivery of the SMS to the endpoint regardless of the RAT of the destination
UE.

References:

1) [1] J. G. Andrews et al., “What will 5G be?,” IEEE Journal on Selected Areas in
Communications, vol. 32, no. 6, pp. 1065–1082, 2014, doi:
10.1109/JSAC.2014.2328098.

[2] A. Neubacher and V. Ramamurthi, “ NG‐RAN Deployment Considerations ,” 5G

Radio Access Network Architecture: The Dark Side of 5G, pp. 379–395, Feb. 2021,
doi: 10.1002/9781119550921.CH7.

[3] B. Bertenyi, R. Burbidge, G. Masini, S. Sirotkin, and Y. Gao, “NG Radio Access
Network (NG-RAN),” Journal of ICT Standardization, vol. 6, no. 1, pp. 59–76, 2018,
doi: 10.13052/JICTS2245-800X.614.

[4] “5G fundamental air interface design,” 5G System Design: An End to End Perspective,
pp. 35–225, Sep. 2019, doi: 10.1007/978-3-030-22236-9_2.

[5] “All Library Papers | Semantic Scholar.”

https://www.semanticscholar.org/me/library/all (accessed Aug. 05, 2021).

[6] J. Boccuzzi, “Introduction to Cellular Mobile Communications,” 2019.

[9] M. Yang, Y. Li, D. Jin, L. Su, S. Ma, and L. Zeng, “OpenRAN: a software-defined ran
architecture via virtualization,” Proceedings of the ACM SIGCOMM 2013 conference
on SIGCOMM, 2013.

[10] D. Sabella et al., “RAN as a service: Challenges of designing a flexible RAN

architecture in a cloud-based heterogeneous mobile network,” 2013 Future Network &
Mobile Summit, pp. 1–8, 2013.

[11] F. Tian, P. Zhang, and Z. Yan, “A Survey on C-RAN Security,” IEEE Access, vol. 5,
pp. 13372–13386, 2017.