You are on page 1of 56

3GPP 5G system architecture

TP00002-W-0002-03_Ed3
After completing this course you will be able to:

List the requirements guiding the 5G architecture

Explain the need for a new system architecture

Review 5G Network deployment options in 3GPP Release 15

Explain overall 5G System architecture

Before we begin

Course contents

Need for a new architecture

5G Network deployment options

5G System architecture
Lesson 1 of 5

Before we begin

Adjust display settings Turn sound on

The content of this training is protected by Nokia. Access Nokia copyright and confidentiality disclaimer
affecting this content before proceeding.

I co n rm I h ave read th e ab o ve d is claim er


Lesson 2 of 5

Course contents

The Need for a new architecture

GO TO

5G Network deployment options

GO TO

5G System architecture

GO TO

C O NT I NU E
Lesson 3 of 5

Need for a new architecture

There are 3 topics included in this lesson:

1 Three Key Factors

2 Requirements guiding the 5G architecture

3 Towards a layered architecture for the 5G evolved core cloud

Three Key Factors

One of the main challenges for 5G will be to support diverse and heterogeneous use cases in a flexible
and reliable way. To deliver the network requirements demanded by the broad range of services will
require fundamental change to all aspects of network architecture. Obviously, the “one-size-fits-all”
network solution we have today for all use cases and services to every device everywhere is no longer
viable.
A fundamental rethinking of the end-to-end network architecture
is needed to support all use cases and all requirements:

The network architecture must shift from the current network


of entities to a network of capabilities architecture.

Network models must shift from the current network for


connectivity to a network for services model.

The 5G Access-agnostic Core network will serve 3GPP access


technologies, including one or more New Radio and E-UTRA as well
as non-3GPP access technologies. Interoperability among the
various access technologies will be imperative. For optimization
and resource efficiency, the 5G system will select the most
appropriate 3GPP or non-3GPP access technology for service,
potentially allowing multiple access technologies to be used
simultaneously for one or more services active on a UE.
Network slicing offers an effective way to meet all of the diverse use
case requirements and exploit the benefits of a common network
infrastructure. It enables operators to establish different
capabilities, deployments, and architectural flavors for each use
case or service group and run multiple network instances in
parallel.
5G System is designed and built using all the capabilities of the
cloud and adopts a more agile and distributed architecture to
achieve the faster service definition and delivery required to
support new socioeconomic models and behaviors.

To recap, new network architecture will be essential to meet the


requirements beyond 2020, to manage complex multi-layer and
multi-technology networks, and to achieve built-in flexibility.

C O NT I NU E

Requirements guiding the 5G


architecture

 

 

 

Flexibility

•Fast introduction of new services


•Automated scaling of services

Quality and user experience

•Monetization of OTT traffic


•More efficient network utilization

Latency

New business opportunities in verticals (automotive, industry)


Reliability

New business opportunities in verticals (Vehicle2X, Industry 4.0)


Network as a Service (NaaS)

•Better network efficiency


•New business opportunities,
e.g. verticals, network sharing

Session on demand

•Extended battery life


•Efficient use of resources

Scalability

•Better network efficiency


•TCO optimization

Mobility on demand

•TCO optimization
•Better use of network resources

C O NT I NU E

Towards a layered architecture for


the 5G evolved core cloud
Today: 3GPP box-driven function split

5G: Layered architecture for the core cloud


1. Logical and physical separation of user plane

2. Session states separated from the control plane

3. Consolidated control plane


01:21

Script

The abstraction of network functions from the underlying hardware is essential. network functions will
run as software components on top of operators’ telco cloud systems rather than using dedicated
hardware components. In LTE, virtualization is applied in a box-driven way. In 5G, virtualization should be
used as the underlying principle for the new architecture design. The breaking down and reassembly of
network functions to better use Network Function Virtualization (NFV) technologies for best scalability
and agility is vital.
Also, separation of the control and user plane functions is the basic SDN principle, which enables
dynamic allocation of user plane resources at the best place for a given service. Some example use cases
that will benefit from a flexible gateway allocation depending on the service are low latency services
and/or Content Delivery Network (CDN) which require the gateway close to the radio access while the
best option for basic Internet access may still be a central gateway.
Software-defined networking (SDN) and network function virtualization (NFV) will play an important role
in the shift to network slicing. Virtualization will enable the separation of the software from the hardware
and offer the possibility to instantiate many functions on a common infrastructure. With this approach,
the infrastructure can be shared by different tenants and provide different services.

What are the requirements for 5G Architecture?

Network architecture shall allow for deployment flexibility


(e.g. to enable context-aware service delivery, low latency
services)

Network architecture shall allow for C-plane/U-plane


separation

Network architecture shall allow deployments using


Network Function Virtualization

Network architecture shall allow for the operation of


Network Slicing

The design of the 5G architecture shall allow the


deployment of new services rapidly and efficiently

All of the above


SUBMIT

Why is the current EPC/System Architecture Evolution not ready for the 5G era?

The existing architecture is not able to support VoIP


services natively for example, especially when they are
combined with fast mobility.

The existing architecture is not able to support C-RAN, to


make this happen LTE will utilize virtualization which is
applied in a box-driven way.

The existing architecture is not able to support low latency


services for example, especially when they are combined
with fast mobility.

LTE System supports a unified authentication framework


and "stateless“ Network Functions.

SUBMIT
C O NT I NU E

In this lesson, we have explained these topics:

1 Three Key Factors

2 Requirements guiding the 5G architecture

3 Towards a layered architecture for the 5G evolved core cloud


Lesson 4 of 5

5G Network deployment options

There are 3 topics included in this lesson:

1 5G Network architecture options in 3GPP

2 Stand-Alone Versus Non-Stand Alone

3 5G Architecture main migration strategy

5G Network architecture options in


3GPP

TW O PRI MA RY O PTI O NS F O R 2 0 18 : . . . NO N- STA NDA L O NE O PTI O N FA MI LY . . .


Two primary options for 2018: EPC-based or 5G Core-based

5G System can be deployed as a standalone solution without LTE. This approach


is called Option 2 in 3GPP. 5G can also use a non-standalone solution with dual
connectivity to LTE. That approach is called Option 3. The very first 5G networks
must use Option 3 because it is available in 3GPP 6 months before Option 2.
Dual connectivity also has other benefits: it allows the combination of LTE and
5G data rates and allows the reuse of existing Evolved Packet Core (EPC). Option
2 with 5G core network enables new end-to-end services including low latency.
Option 2 allows lower latency and faster setup time than dual connectivity
solution where LTE protocols are used.

TW O PRI MA RY O PTI O NS F O R 2 0 18 : . . . NO N- STA NDA L O NE O PTI O N FA MI LY . . .


Non-standalone Option family 7 and Option family 4

3GPP Standards will bring also the option to connect LTE eNodeB to 5G core
network with Options 7 and 4.

Option 3 variants
3X seems most preferred

3A does not facilitate aggregation for a single bearer, as no


user plane routing between BTS

Option 3 part of 12/2017 specs

01:20

Script

Option 3 is a dual connectivity deployment with E-UTRA as the anchor Radio Access Technology (RAT)
and NR as the secondary RAT in a non-standalone configuration based on the existing EPC.
Both 5G base stations (gNodeB) and LTE base stations (eNodeB) are connected to the EPC. The control
plane goes via LTE.
There are 3 possible variants as displayed on the slide. The option 3X seems favored by most operators
for enhanced mobile broadband.
Within option 3 variants, the UE is connected to one eNB that acts as a Master Node and one gNodeB
that acts as a Secondary Node. From a UE perspective, three bearer types exist: a radio bearer with an
RLC bearer only in the Master Node, a radio bearer with an RLC bearer only in the Secondary Node and a
split bearer with RLC bearers both in Master and Secondary Node.

In Option 3: there is a Master Node split: EPC establishes the bearer to Master LTE eNodeB, then
Master LTE ENodeB splits the bearer for forwarding packets to LTE radio and/or 5G radio.

In Option 3a: there is user plane traffic split at the core network: EPC establishes separate bearers
to LTE and 5G as depicted in the figure in the middle of the slide.

In Option 3x: The user plane goes via both eNodeB and gNodeB with bearer split at gNodeB.

C O NT I NU E

Stand-Alone Versus Non-Stand


Alone
W HY DU A L C O NNE C TI VI TY W I TH NS. . . W HY STA NDA L O NE SA ?

Available 6 months earlier than SA

Existing EPC core used

Existing LTE idle mode used

Data rate aggregation LTE + 5G

VoLTE in LTE

W HY DU A L C O NNE C TI VI TY W I TH NS. . . W HY STA NDA L O NE SA ?

5G end-to-end for new services


Lower latency without LTE leg

Lower setup time in 5G

No need for LTE network upgrades

01:37

Script

5G is the first radio solution closely integrated with the existing radio network, offering a smooth rollout
and a seamless experience for users. As discussed above, there are two primary options: EPC-based or
5G Core-based:

Non-standalone (option 3) adding New Radio (NR) as secondary under LTE with EPC core

Standalone (option 2) with 5G New Radio (NR) under the new 5G core.
From a practical standpoint, it’s easy to understand why operators pushed hard to accelerate the
standardization of the 5G non-stand-alone (NSA) radio architecture with EPC. This architecture can use
the existing 4G EPC as the core and 4G/LTE RAN for network coverage, which allows them to add 5G NR
to address network capacity constraints with minimal changes to their infrastructure and operations.
Nonetheless, an NSA network isn’t a complete 5G end-to-end network until the core supports the new
5G core (5GC) functions. Upgrading an existing EPC with a new 5G NR to expand existing mobile
broadband services may be a short-term solution for some operators, but it won’t satisfy their long-
term objectives.
Simply put, operators cannot economically, nor technically, support the variety and multitude of
devices connecting to the network and meet the broad range of new and varied 5G services
requirements by merely upgrading an existing EPC. To meet the scalability, flexibility and performance to
cost-effectively deliver 5G services requires a cloud-native, 5G service-based core architecture that
includes separate user and control planes and high-bit rate provisioning.

C O NT I NU E

5G Architecture main migration


strategy
In the near term, operators will likely deploy a 5G NSA network
(most likely option 3X as mentioned earlier) to roll out the initial
set of services and to get familiar with the new radio technology.
This “step-by-step” approach minimizes the disruption and
change within the network. But the full benefits of 5G cannot be
realized until a 5G core is deployed. operators that are early
adopters to a full 5G end-to-end network will have a competitive
advantage in their network by providing the scalability,
performance and flexibility needed to economically deliver the
broad range of services envisioned. The race for 5G leadership is
on.
01:25

Script

There are therefore several possible “paths” operators can follow to introduce a 3GPP compliant 5G
system migrating from their 3GPP 4G network. The figures above show the potential migration strategies
that may be considered.
As there can be multiple paths to reach the final target configuration that an operator intends to deploy,
it is essential to consider migration steps that would comprise different paths.
To follow the appropriate path, operators should first consider the ability of the path in addressing 5G
use cases. Second, they should take into account the support for early 5G devices, core network and
radio access network deployment considerations of the migration step. Third, operators need to
consider also the impact of the migration step on device and network. And Finally, the impact on voice
service including service continuity.
5G network may look complex to launch but it can be done also with a simple and fast approach. Initial
5G launch can be simplified by focusing on the mobile broadband use case, by re-using existing
architecture, by re-using existing network grid and sites, by re-using existing packet core. The first phase
of 5G brings higher data rates and a lot more capacity. Further evolution of 5G can then gradually
enhance the network capability with new low latency and IoT use cases, with new cloud architecture, with
small cells, with higher millimeter bands and with a new 5G core network.
C O NT I NU E

In this lesson, we have explained these topics:

1 5G Network architecture options in 3GPP

Stand-Alone Versus Non-Stand Alone


2
3 5G Architecture main migration strategy
Lesson 5 of 5

5G System architecture

There are 4 topics included in this lesson:

1 Baseline end-to-end architecture

2 Key principles and concept

3 5G System architecture

4 5G Core architecture

Baseline end-to-end architecture


01:27

Script

All the new technologies enabled by 5G—the Internet of Things, artificial intelligence, robotics, virtual
reality—require a new network approach, both for the access network and the next-generation core
(5GC).
5G System is more than just a radio access technology. A number of architectural improvements in the 5G
Core have been adopted in the 3GPP specifications starting from Release 15. The 5G standardization has
defined the functional architecture where implementation technologies can be evolved and replaced
over time.
The 5G core now becomes an intelligent interconnection hub residing at the heart of the network,
forming a globally interconnected fabric and acting as an anchor point for multi-access technologies
including 3GPP and non-3GPP Access. It needs to deliver a seamless service experience across fixed and
wireless access technologies, with the advanced 5G New Radio (5G NR for short) being an important new
radio access technology.
The 5G system will support 3GPP access technologies, including one or more NR and E-UTRA as well as
non-3GPP access technologies. Interoperability among the various access technologies will be imperative.
For optimization and resource efficiency, the 5G system will select the most appropriate 3GPP or non-
3GPP access technology for service, potentially allowing multiple access technologies to be used
simultaneously for one or more services active on a UE.
C O NT I NU E

Key principles and concept

01:39
Script

The 5G System architecture should provide a common core to support multiple access technologies,
multiple services, multiple networks and service operators. This will be enabled by Network Function
Virtualization (NFV) and Software-defined networking (SDN) technologies which allow building systems
with a high level of abstraction.
The 5G System architecture shall leverage service-based interactions between Control Plane (CP)
Network Functions where identified. Some key principles and concept are to:

Separate the User Plane (UP) functions from the Control Plane (CP) functions, allowing independent
scalability, evolution and flexible deployments e.g. centralized location or distributed (remote)
location.

Modularize the function design, e.g. to enable flexible and efficient network slicing.

Wherever applicable, define procedures (i.e. the set of interactions between network functions) as
services so that their re-use is possible.

Minimize dependencies between the Access Network (AN) and the Core Network (CN). The
architecture is defined with a converged core network with a common AN - CN interface which
integrates different Access Types e.g. 3GPP access and non-3GPP access.

Support a unified authentication framework.

Support "stateless" NFs, where the "compute" resource is decoupled from the "storage" resource.

Support capability exposure.

Support concurrent access to local and centralized services. To support low latency services and
access to local data networks, UP functions can be deployed close to the Access Network.

Support roaming with both Home routed traffic as well as Local breakout traffic in the visited
PLMN.

C O NT I NU E
3

5G System architecture

5G System is a 3GPP system consisting of 5G Access Network (AN), 5G Core Network and UE

5G Access Network: An access network comprising an NG-RAN and/or non-3GPP AN connecting to a 5G


Core Network

NG-RAN (Next Generation Radio Access Network): A radio access network that supports one or more of
the following options with the common characteristics that it connects to 5GC:

Standalone New Radio.

New Radio is the anchor with E-UTRA extensions.

Standalone E-UTRA.

E-UTRA is the anchor with New Radio extensions.


The 5G System architecture is defined as service-based and the interaction between network functions is
represented in two ways:

A service-based representation, where network functions within the Control Plane enables other
authorized network functions to access their services. This representation also includes point-to-
point reference points where necessary. Network functions within the 5GC Control Plane shall only
use service-based interfaces for their interactions.

A reference point representation described by a point-to-point reference point (e.g. N2) between
any two network functions. This representation shows the interaction existing between the NF
services in the network functions.

C O NT I NU E

4
5G Core architecture

The 5G Core Network (5GC) consists of the functional elements shown in this diagram. Some of these core
functions perform similar roles as the existing EPC while others, such as the Network Functions Repository
Function (NRF), are new.

The 5GC introduces a new Services Based Architecture (SBA) where the 5GC control plane (CP) design is
based on services exposed by network functions (NFs) using new service-based interfaces (SBIs). Once a
5GC function registers its services with the new 5G Core Network Functions Repository Function (NRF), it
then simply expose services that any authorized consumer can consume, rather than having to define a
new point-to-point interface and the procedures between the two network functions as an EPC requires.
This offers operators greater flexibility and more efficiency by decoupling the service consumer from the
service producer.

5G Core Network Functions will be described in a dedicated tutorial. Primary functions are shown in this
figure. Click on each NF to display its role.
   

  


Authentication Server Function (AUSF)

Facilitates a common authentication framework for all access types.


User Plane Function (UPF)

Equivalent to the user plane of the EPC serving/packet data network gateway (S/P-GW), but enhanced to support
flow-based QoS and a new session and service continuity mode that allows a ”make before break” approach
quintessential for URLLC. Multiple UPF instances are possible within distributed and centralized deployments,
allowing completely disjointed paths from the access network for the sessions of the same user endpoint.

Policy Control Function (PCF)

Provides a common policy framework by exposing policies as a service that are consumed by any authorized client.
Besides QoS and charging, it supports network slicing, roaming and mobility policies.

Session Management Function (SMF)

The only function that establishes and manages sessions for all access types according to the network policy. It
absorbs in one function session management functionality spread across the control plane functions of the
Evolved Packet Core (EPC).

Access and Mobility management Function (AMF)

The single control plane component that terminates the interface from the access networks and from the UE,
manages access control and mobility, and plays a key role in network slice functionality by serving all slices a UE is
accessing.

Network Exposure Function (NEF)

An extension of the Service Capability Exposure Function (SCEF) in 4G networks.


Network Repository Function (NRF)

New functionality with no equivalent in 4G networks. NRF provides registration and discovery functionality to
enable other network functions/services to discover and communicate with each other.

Uni ed Data Management (UDM)

Stores subscriber data and profiles, similar to the home subscriber server (HSS) or home location register (HLR).

Non-3GPP Interworking Function (N3IWF)

A core network function for the integration of the stand-alone untrusted non-3GPP access to the access agnostic,
universal core. N3IWF terminates IPSec and IKE v2 and exposes towards the common core N2, N3 like the RAN
does.

A secondary alternative, more aligned to the traditional packet


core, is a point-to-point architecture with functions
interconnected with specific interfaces.
Reference point-based architecture diagram is provided by the
stage 2 specifications, which represent more specifically the
interactions between network functions for providing system-level
functionality and to show inter-PLMN interconnection across
various network functions.

What are the key principles of the new 5G architecture?

Control and User Plane Separation (CUPS)

Service Based Architecture (SBA)

Support of an unified authentication framework

Common Core Network and Access-agnostic Core

SUBMIT

What best describe a Network Function?


A logical network that provides specific network capabilities
and network characteristics

A 3GPP adopted or 3GPP defined processing function in a


network, which has defined functional behavior and 3GPP
defined interfaces

A network function can be implemented either as a network


element on a dedicated hardware, as a software instance
running on a dedicated hardware

A network function can be implemented as a virtualized


function instantiated on an appropriate platform, e.g. on a
cloud infrastructure

SUBMIT

C O NT I NU E

In this lesson, we have explained these topics:

1 Baseline end-to-end architecture


2 Key principles and concept

3 5G System architecture

4 5G Core architecture

Thank you for attending this course.

You might also like