Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Introduction to 5G
Reference Document
www.mpirical.com
Introduction to 5G
Introduction to 5G
Reference Document
Mpirical classes have been developed in accordance with the technical specifications
published by the 3GPP. As such the 3GPP have granted Mpirical Limited the right to use the
3GPP logo to identify specifications, compliant products and services.
Contents
5G Concepts and Drivers ...................................................................................... 1
1.1 Key Drivers .................................................................................................... 1
1.2 5G Standardization ....................................................................................... 4
5G New Radio and NG-RAN ................................................................................. 4
2.1 NG-RAN Architecture .................................................................................... 5
2.2 NR and NG-RAN Features............................................................................ 6
2.3 Dual Connectivity .......................................................................................... 6
2.4 Small Cells .................................................................................................... 8
2.5 Increased Spectrum ...................................................................................... 9
2.6 Radio Enhancements .................................................................................... 9
2.7 Beam Forming and Steering ....................................................................... 10
2.8 Cloud RAN .................................................................................................. 11
2.9 5G RAN Deployment Options ..................................................................... 12
5G Core Network Architecture ............................................................................ 12
3.1 PDU Sessions ............................................................................................. 13
3.2 Core Network Elements .............................................................................. 13
3.3 Network Virtualization ................................................................................. 15
3.4 Network Slicing ........................................................................................... 16
5G Initial Procedures ........................................................................................... 17
4.1 Finding the Network .................................................................................... 17
4.2 Network Registration ................................................................................... 17
Utilizing the Network............................................................................................ 19
5.1 Idle and Connected Mode ........................................................................... 19
5.2 Establishing a PDU Session ....................................................................... 20
5.3 Moving to Idle .............................................................................................. 21
5.4 Getting Connected – Service Request........................................................ 22
5.5 Paging ......................................................................................................... 23
Mobility and Interworking .................................................................................... 24
6.1 Tracking Area Updates ................................................................................ 24
6.2 Handovers ................................................................................................... 24
6.3 Roaming ...................................................................................................... 26
Figures
3G 4G 5G
1.2 5G Standardization
The 3GPP is at the heart of 5G standardization. As such, it has already
mapped out:
5G Phase 1 - this is based on the Release 15 specifications, frozen in
September 2018. Unfortunately, this does not meet all the IMT2020
requirements.
5G Phase 2 - this is based on Release 16 specifications, frozen in
December 2019 - ready for the IMT2020 submission.
During the development phase of 5G, several 5G 3GPP work items were
brought forward to assist in “early deployments”.
Even though the standards are frozen long before 2020, it is typically one or
two years before actual deployments are seen, although there will
undoubtedly be early adopters of the technology. Typically, these deployments
are related to niche areas, for example showcasing 5G at specific global
events such as the FIFI World Cup. However, some service providers may
push forward with 5G solutions that are not 100% compliant with the 3GPP
specifications, simply to be first to market (particularly large service providers
who have support from equipment and handset vendors).
3GPP Releases
5G Phase 2
Deployment
Rel. 16
Release Release Release
14 15 16
5G Phase 1
Proprietary
Deployment
5G Systems
Rel. 15
5G NR Data
NG-RAN 5G Core Network
Network
UE
As can be seen in Figure 12, the RAN Nodes are classed as either a Master
RAN Node or a Secondary RAN Node. The difference between the two is that
the Master RAN Node is the base station which retains control of the data
bearers and also maintains a control connection with the core network. The
Master RAN Node will control the Secondary RAN Node through a control
connection between the two. In addition, the Master and Secondary will also
share a data plane connection for media splitting.
Note that there are several DC options available for deployment, based on the
technology type and combination used for the Master RAN Node and
Secondary RAN Node. RAN nodes could be:
A traditional 4G eNB which supports the LTE radio and connects to the
EPC (Evolved Packet Core).
An enhanced 4G eNB, termed a ng-eNB (New Radio eNB), which
supports the LTE radio but connects to the 5G core network.
A 5G gNB, which supports the 5G radio and connects to the 5G core.
Data Flow with Dual Connectivity
Figure 13 illustrates how both the Master and the Secondary RAN Node may
be sent user plane data from the core network. User plane connectivity that is
established between the core and the Secondary RAN Node is controlled by
the Master RAN Node. That is, the Master RAN Node will define exactly which
data should be sent to the Secondary (to the granularity of a QoS Flow).
At the RAN node, bearer splitting can then take place. This involves the RAN
node splitting a data stream so that both RAN nodes can be involved in the
downlink transmission to the device, hence raising the overall data rate
experience by the subscriber.
In Figure 20, the beam forming concept is taken one step further, in which the
beam of coverage is steered in order to first of all focus on a “target”, then
move in step with the movement of the “target”. This requires the device to
continuously provide feedback to the antenna array with information on the
received signal, since factors such as the subscriber turning their head, road
traffic passing by or street furniture may require the antenna to adjust its
beam steering so that optimal coverage is provided. Figure 20 shows that
beam steering can potentially accommodate a variety of subscriber mobility
scenarios, although fast moving devices will pose significant challenges.
Standalone
Non
Standalone Non
eNB ng-eNB
Standalone
gNB
gNB gNB
The PDU Session itself may carry IPv4, IPv6, Ethernet or unstructured traffic
(contrary to LTE, which only carries IP traffic on the user plane).
Note that in the 5G core network, these logical functions will be virtualized
(see Figure 28 for further information).
Core Access and Mobility Management Function
The primary task of the AMF is to manage the mobility of the subscriber. In
particular, the AMF will play a key role in the device registration process
(including security), as well as track the device’s mobility for reachability and
paging purposes.
5G Initial Procedures
4.1 Finding the Network
Prior to attaching to the 5G network, the device must first of all find its home
network and then find a suitable cell on which to “camp”. The high level
process that supports this is outlined in Figure 32 and is much the same as
earlier 2G, 3G and 4G technologies.
1 2 3 5 1 2 3
AMF
UDM
Data
Networks
EPC
4
PCF
Internet
2
gNB
UE
1 2 5 E-UTRAN IMS
3 UE Context Installation
Subscriber Identification
The device will typically provide to the network its last known temporary ID,
assuming it has one. As such, in order to support security and subscriber
profile acquisition, the network will need to ascertain the subscriber’s real
identity. If the AMF cannot resolve the temporary ID to the permanent ID of
the subscriber, the AMF will query the subscriber device directly.
UE Context Installation
Every valid subscriber has a subscriber profile stored in the UDM. This profile
will define the Data Networks that a subscriber is permitted to connect to,
including the QoS profile they are allowed to have for that network. Additional
Subscriber Profile
Allowed DN Connections -
QoS -
Bandwidth -
Roaming -
Subscriber Status -
AMF UDM
Policy Check
During the Registration procedure, the AMF may typically conduct a policy
check with the PCF. Policy control is often influenced by conditions, such as
the time of day, location of the user, network congestion, handset type etc.
Therefore, before the AMF allows the subscriber to register with the network,
a check can be made with the PCF, essentially requesting that based on the
current network conditions, is the subscriber permitted access to the network?
Policy Decision
Temporary ID Allocation
The final part of the Registration procedure is the allocation of a Temporary
Identity to the subscriber. This Temporary Identity is created by the AMF and
is used for the remainder of the registration period or until the device is
allocated a new Temporary Identity, potentially due to an AMF change.
Note that some IoT devices will behave differently in the network, since they
may have much stricter requirements on optimizing the life of the battery. As
such, devices will access the network on a much more infrequent basis, and
may even operate in MICO (Mobile Initiated Connection Only) mode, which
prevents the network from paging the device.
The data connections established include a radio bearer between the device
and the gNB and a connection between the gNB and the UPF. These
connections are logical in nature, with the network supporting thousands of
logically separate PDU Sessions.
When in Idle mode, the elements of the device’s PDU Session(s) which span
the RAN are not in place. This is due to the fact that the device, when Idle, will
be determining the best cell to use and will switch to a new cell without
informing the network (as long as the new cell is not in a new Tracking Area).
Therefore, there is no point in maintaining data connectivity at a particular
gNB if the device has already potentially decided to camp on a different cell.
When a device in an Idle state has user data to send, it will use a Service
Request to move back into a Connected State. Bearing in mind that until this
point the device was simply listening for paging, the first task it must complete
is to establish a radio connection to the gNB looking after the cell in which the
device is camping. Once this is achieved, a Service Request is sent from the
device to the AMF via the gNB.
The aim of the Service Request is to establish NG-RAN connectivity for each
of the PDU Sessions that the device currently has active (see Figure 42 – the
connectivity was torn down when the device transitioned to Idle). Note that in
5G, the device can be selective as to exactly which PDU Sessions have their
data plane connectivity re-established.
5.5 Paging
When the device is in an Idle state, it is possible that downlink data traffic
arrives at the UPF destined for the user. For example, the subscriber may
have been sent a WhatsApp message or perhaps a call establishment
request. The problem is, when the device is Idle, the network only knows the
location of the user to the accuracy of a Tracking Area. As such, when
downlink data arrives for the device, the AMF will conduct the Paging process
in which a Paging message is sent to every gNB within the subscriber’s
known Tracking Area. In turn, each gNB will broadcast the Paging message
within every cell that the gNB is responsible for (note that contrary to this, the
mobile service provider will undoubtedly use an optimized Paging strategy.
From the device’s perspective, in an Idle state it has camped on a particular
cell (typically the cell that provides the best signal) and is periodically
switching on the 5G radio and listening out for a Paging message. The Paging
message carries the temporary identity of the subscriber and as soon as the
device recognizes this, the phone is triggered into conducting a Service
Request procedure (outlined in Figure 44).
AMF
6.2 Handovers
Handovers take place when the device is in a Connected state, under the
control of the network. That is, the network decides when the device should
be handed over from one cell to the next.
Two mechanisms for conducting handovers are available, termed the Xn
Handover and N2 Handover.
Xn Handover
Xn based handovers are coordinated largely by the two gNBs involved in the
handover process – the Source and Target gNB. Using the Xn interface that
links them, the Source gNB will supply the Target gNB with all the information
it needs to receive the subscriber. Such information includes security
information, as well as the key characteristics of the PDU Session(s) that the
device is currently utilizing.
Figure 47 Xn Handover
Figure 48 N2 Handover
6.3 Roaming
The 5G System supports two different roaming scenarios, namely Home
Routed or Local Breakout.
Figure 49 Roaming in 5G
Figure 50 depicts the architecture for the Home Routed scenario, whereby all
User Plane traffic will be sent from the Visited Network to the Data Network
via the Home Network (utilizing the N9 reference point between the Visited
and Home Network). Control Plane traffic is also sent back to the Home
Network where necessary, utilizing the N8, N12 and N16 reference points. For
example, during registration the Visited AMF would acquire subscriber
information from the Home UDM via N8. Moreover, the V-SMF would liaise
with the H-SMF via N16 in order to establish the PDU Session.
Figure 51 shows the architecture associated with Local Breakout, in which the
User Plane traffic is sent to the Data Network directly from the Visited
Network. The Home Network’s involvement is only required for Control Plane
purposes.
Glossary
Contact Us
Tel: +44 (0) 1524 844669
Email: enquiries@mpirical.com
www.mpirical.com