5G Architecture

1. Introduction to 5G Architecture
The 5G architecture was influenced by several factors, including:
 The need for cloud-based implementations.

 Handling higher data rates and lower latency than previous generations.

 Supporting new services like massive IoT, enhanced Mobile Broadband

(eMBB), and Ultra-Reliable Low-Latency Communication (URLLC).

Key aspects:
 The new 5G Core (5GC) enables more efficient cloud implementations than
LTE’s Evolved Packet Core (EPC).

 It supports network slicing, which allows operators to divide the network into
virtual slices, each optimized for specific services.

2. 5G Architecture Options
Initially, eight different architecture options were proposed for 5G deployment, but
two main options emerged:
2.1 Option 3 (Non-Standalone)
 LTE (4G) acts as the main control plane, while 5G improves data rates.

 This option allows for dual connectivity where LTE and 5G work together.

 Several variants exist within Option 3, where data is split between LTE and 5G
in different ways (discussed in Figure 5.2).
2.2 Option 2 (Standalone)

 5G operates independently with its own 5G core.

 It supports advanced services like network slicing and URLLC s Ultra

Reliable Low Latency Communication and enhanced MBB Mobile
Broadband.

 No LTE-5G dual connectivity is needed, making it the ultimate goal for 5G

deployment.
  Non-Standalone (Option 3): LTE acts as the control plane, while 5G
improves data speeds. It uses the existing LTE eNodeB for control and 5G for
data handling.
 Standalone (Option 2): 5G works independently using a 5G core, supporting
new features like network slicing.

 Option 3: The data from the Evolved Packet Core (EPC) is split at the LTE
eNB, allowing both LTE and 5G to handle user data. Both 4G and 5G transmit
and receive data simultaneously, improving the overall data rate for the user.
 Option 3A: Data is split in the EPC, with one network (either LTE or 5G)
handling a service. This limits data aggregation but is simpler for low-data-rate
services like VoLTE

 Option 3X: Data is split by the 5G gNB, which is preferred for reducing the
load on LTE especially since LTE wasn’t designed for high data rates. Most
data is handled by 5G, reducing latency and improving speed.

Figure 5.3 (Page 9) – Further 3GPP Architecture Options

This figure presents other architecture options:

 Option 4: The 5G gNB is the master anchor, with LTE secondary. It is suitable
when 5G coverage is extensive and reliable, avoiding the need for LTE
control.
 Option 7: The LTE eNB is the master anchor, with 5G secondary. This is
useful in areas where LTE coverage is better than 5G, such as with mmWave
5G, which has a limited range.

 Option 7X : would then refer to the case when the user plane from the 5G
core is routed via the 5G gNB
Interpretation: This figure shows that depending on the coverage, either LTE or 5G
can control the connection. Option 4 works when 5G coverage is reliable, while
Option 7 is better when LTE coverage is stronger. It highlights the flexibility of 5G in
integrating with existing LTE networks.

3. 5G Core Network Architecture

The 5G Core Network (5GC) is designed for cloud-native deployment, supporting
virtualized network functions (NFV) and software-defined networking (SDN).
This makes the network more scalable and flexible.
 Distributed edge cloud architectures: With control and user plane
separation, functions like the user plane can be processed closer to the user,
especially for latency-sensitive applications.

 Simultaneous connection to edge and central cloud: Users can connect to

both the edge cloud (for quick responses) and the central cloud (for overall
network management).
 Stateless network functions: Compute and storage are separated, which
allows for scalable and resilient architecture.

 Unified Data Management (UDM): The 5G core stores user data, session
data, policies, and operational data in the Unified Data Repository (UDR).
This setup enables easier data sharing across multiple network slices.
 Multi-access support: 5G enables devices to connect through different
network types (e.g., fixed or mobile), maximizing reliability and speed.
 Point-to-point architecture: Traditionally used up to 4G, this approach is still
partly used in 5G. It connects various network functions over standardized
interfaces, allowing multivendor compatibility.
 Service-Based Architecture (SBA): 5G introduces SBA to replace point-to-
point for some core network interfaces. SBA allows functions to interact
through HTTP-based interfaces, making it easier to add, modify, or remove
services.
 In SBA, functional agility and service agility are enhanced by decoupling
services from underlying network infrastructure, which allows the network to
respond faster to market demands.

Key Components:
 AMF (Access and Mobility Management Function): Manages user
authentication and mobility.
  SMF (Session Management Function): Handles session establishment and
IP management.
 UPF (User Plane Function): Handles data forwarding and routing.
(passerelle)
 PCF (Policy Control Function): Ensures policies for Quality of Service (QoS)
are enforced.

Figure 5.4 (Page 14) – 5G Core Network Architecture (RAKZOU AALIHA

SUR )
5G system architecture, interfaces between the user equipment (UE) and the core (N1), the access
network and the core (N2 and N3), and the control and user plane (N4) will still use a point-to-point
architecture

Service-based interfaces are all based on HTTP and are all denoted with the legend Nxxx in
Figure 5.4.

This diagram shows the modular nature of the 5G core, with components like:

 AMF managing mobility and authentication.

 SMF managing sessions.

 UPF handling data routing and QoS.

 PCF managing policies for user services.

Interpretation: This figure showcases the modular nature of the 5G core. Each
function is decoupled, making it easier to scale, manage traffic, and adapt to different
services such as voice, data, and low-latency communication. The separation of
control plane and user plane adds flexibility to network management.

The AMF is responsible for managing user equipment (UE) access and mobility in the 5G Core.
Key functions of AMF:

 Handles Radio Access Network (RAN) signaling (N2 interface).

 Manages NAS signaling (N1 interface) from the UE.

 Provides authentication, authorization, and ciphering for access.

 Supports various mobility-related tasks like registration management, connection

management, and location services.

The SMF handles session-related tasks, such as establishing, modifying, and releasing data
sessions between the user and the network.

Key functionalities of the SMF:

 Manages UE IP address allocation and coordinates charging data.

 Controls the User Plane Function (UPF) and selects UPF for routing user traffic.

 Coordinates with policy functions to ensure proper Quality of Service (QoS) for each session

User Plane Function (UPF)

 The UPF handles the user data traffic, performing tasks like routing, forwarding, and applying
Quality of Service (QoS).

 Low-latency services are handled by UPFs placed near the user (local UPF), minimizing
delays.

UPF functions:

 Manages packet forwarding, routing, and inspection.

 Acts as an anchor for mobility between different radio technologies (like 4G/5G handovers).

 Connects to external networks through N6 interface.

Data Storage Architecture in 5G Core

 The Unified Data Repository (UDR) stores different types of data like subscription, policy,
and application data.

 Unified Data Management (UDM) manages authentication credentials, user identities, and
session information.

 5G also introduces the Unstructured Data Storage Function (UDSF), allowing network
functions to store unstructured data, making these functions stateless and more scalable.

Policy Control Function (PCF)

 The PCF governs network behavior by applying consistent policies across the network. It is
responsible for managing both session management and access policies.

 PCF’s role includes:

 o Creating and applying QoS policies and charging rules.

o Interacting with the Unified Data Repository (UDR) to ensure correct policies are
applied based on user data.

o Working with the Network Exposure Function (NEF) to provide application-driven

traffic control.

Network Exposure Function (NEF)

 The NEF exposes 5G Core services to external applications in a secure manner.

 It allows third-party services to interact with the 5G network, while hiding sensitive network
information.

 NEF uses the Unified Data Repository (UDR) to securely share data with external entities.

Network Repository Function (NRF)

 The NRF maintains a database of network function (NF) instances, helping in the discovery
and selection of the appropriate NF for a task.

 It ensures that services are allocated based on criteria like location, load, and network type.

 NRF provides more granular control over network function selection compared to traditional
DNS-based approaches.

Network Slice Selection Function (NSSF)

 The NSSF is responsible for selecting network slices for the UE.

 It identifies which Access and Mobility Management Function (AMF) should be used for the
UE, depending on its needs.

 The NSSF ensures that each UE is assigned the appropriate network slice based on its
subscription data and service requirements, as configured by the PCF.

Non-3GPP Interworking Function (N3IWF)

 The N3IWF enables UEs to connect to the 5G Core via non-3GPP networks like Wi-Fi.

 Its primary functions include:

o IPsec tunnel establishment between the UE and 5G Core for secure

communication.

o Handling user plane traffic by relaying packets between the UE and the User Plane
Function (UPF).

o Handling control plane signaling between the UE and the AMF.

4. 5G Radio Access Network (RAN) Architecture
The 5G RAN is divided into two main units:

 Central Unit (CU): Handles higher-layer processing, which can be done

centrally (e.g., in the cloud).
 Distributed Unit (DU): Located near the cell site and deals with time-sensitive
tasks, like real-time data processing close to the user.
This architecture allows for low-latency and distributed processing.

Figure 5.5 (Page 27) – 5G RAN Architecture (rakaz aaliha)

This figure shows the relationship between the CU and DU, where the CU manages
complex functions and the DU handles fast, real-time processing.

Interpretation: This architecture splits processing between central and distributed

units, improving response times for critical services while allowing for more
flexibility .

Interfaces in 5G RAN:

 F1 Interface: Connects the CU to the DU, enabling centralized control while

maintaining fast processing at the network edge.
 Xn Interface: Connects different CUs together or connects DU to DU, allowing
handover between gNBs (5G base stations) or between LTE and 5G.
 The NG interface toward the 5G Core (5GC). It is divided into the user plane
part (NG-U) and the control plane part (NG-C)

Figure 5.6 (Page 30) – 5G RAN Architecture with Control and User Plane
Separation
This figure emphasizes the separation of the control plane (for signaling) and the
user plane (for data). This allows for more flexible and efficient handling of data
traffic.
Interpretation: This architecture is designed to optimize data flow and minimize
latency, with real-time operations being managed closer to the user (DU), while
higher-level operations are centralized (CU).

Lower Layer Functional Split

 In 5G, more processing tasks are moved to the CU for centralized control,
leaving simpler tasks for the DU.

 This design reduces the need for large amounts of data transmission between
the CU and DU, making the network faster and more efficient.

(Figure 5.7) – Impact on Backhaul Connectivity

 The figure shows the data rates needed for different setups:
o Using the CPRI interface (which sends raw data) requires high
bandwidth.
o Moving functions like retransmission to the CU reduces the amount of
data that needs to be transmitted.

 This setup allows the network to handle more users and data without
overloading.
– Enhanced CPRI (eCPRI)
 The eCPRI interface is packet-based (like Ethernet), allowing more flexible
and lower-cost data transmission.
  5G splits data processing into parts (e.g., between antennas and core
network) to improve speed and efficiency.

(Figure 5.9) – NG-Interface Protocol Stacks (Rakzou aaliha)

This figure shows the protocol stacks for the control plane and user plane in the NG-
interface, which connects the gNB (5G base station) to the 5G Core (5GC).

It handles both control signals (like user registration) and data transfer (user traffic).
 It uses GTP-U (GPRS Tunneling Protocol) for user data and SCTP (Stream
Control Transmission Protocol) for control signals.

UPF (User Plane Function): Handles user data/ AMF This manages user access to the network/
NG-U (User Plane)/ NG-C (Control Plane)/ L2 (Layer 2) and L1 (Layer 1): These represent the
lower layers in the network protocol stack that handle data link and physical transmission

(Figure 5.10) – Xn-Interface Protocols (rakzou aaliha)

This figure shows the protocol stacks for the Xn-interface, which connects two gNBs
(5G base stations) to allow handover between base stations.
Xn User Plane:
 This transfers user data between two gNBs using GTP-U over UDP and IP. It
handles the forwarding of data packets when a user moves between cells (handover).

Xn Control Plane:
 This handles the control signals using SCTP over IP.

XnAP (Xn Application Protocol):

 A protocol used in the control plane for exchanging information between

gNBs, such as handover messages.
L2 (Layer 2) and L1 (Layer 1):

 The lower layers that handle the data link and physical transmission (radio
signaling) between gNBs.

This figure shows the protocol stacks for the Xn-interface, which connects two gNBs
(5G base stations) to allow handover between base stations.

(Figure 5.12) – F1-Interface Protocol Stacks

 The F1 interface connects the CU and DU within the 5G RAN.

 It handles control tasks (e.g., radio resource management) and user data
transmission.

5. Network Slicing in 5G
Network slicing is a key feature of 5G, allowing multiple virtual networks to coexist
on the same physical infrastructure. Each slice can be optimized for a specific use
case:
  Low-latency slice: For applications like industrial automation or remote
surgery.

 High-bandwidth slice: For applications like 4K video streaming.

 IoT slice: For devices with low power and low data needs.

Figure 5.13 – Example Network Slicing Use Case (rakzou aaliha)

This figure shows two User Equipment (UE) connected to different slices:
 One UE is using mobile broadband with high mobility.

 The other UE is using a low-latency service with minimal mobility.

Interpretation: This figure demonstrates how 5G's network slicing allows

customized network experiences for different types of users or applications, ensuring
optimized performance for each use case.

5G-RAN: The Radio Access Network that connects the UE to the core network. It handles
radio communication between devices and the network.

User Plane Function at Core Site: A UPF that handles regular mobile broadband
services (high-speed internet) for users that don’t need low latency.

User Plane Function at Edge: A UPF closer to the user, designed to handle low-latency
services by reducing the delay in data transmission.

Figure 5.14 (Page 42) – Setting Up a Slice for UE (Rakzou aaliha)

Interpretation: This process ensures that each UE is connected to the slice that best
suits its requirements, such as low-latency communication or high-bandwidth
services.
AMF (Access and Mobility Management Function):

 Responsible for handling the device’s access to the network and managing its
mobility. It communicates with the NSSF to assign the correct slice to the
device.
NSSF (Network Slice Selection Function):

 This function determines which network slices the UE is allowed to connect to,
based on its subscription and service needs.

6. Interworking with LTE

5G is designed to interwork with LTE in both idle and active modes:

 In idle mode, a UE can switch between 5G and LTE seamlessly, depending

on network coverage.
 In active mode, handovers are possible between LTE and 5G, ensuring
continuous service.
Figure 5.15: Reselection from 5G to LTE (rakzou aaliha)

Interpretation:
 Reselection allows seamless transitions from 5G to LTE when 5G coverage is lost,
ensuring that users can stay connected without interruptions.

 The figure highlights the context transfer mechanism between the 5G and LTE
networks to maintain the user’s session.
This process is essential to ensure a smooth user experience when switching
between 5G and LTE, especially in areas where 5G coverage is not fully available.
EPC (Evolved Packet Core): The core network for LTE, which takes over once the device
reselections to LTE. The context of the user session (e.g., connection state) is transferred
from the 5G Core to the EPC.

Tracking Area Update: A process that allows the UE to inform the network about its new
location as it moves between different areas of coverage (from 5G to LTE).

Figure 5.16 (Page 46) – 5G to LTE Inter-System Handover (Rakzou aaliha)

Interpretation: The figure illustrates the smooth handover process between 5G and
LTE, ensuring consistent service even when moving between coverage areas. The
UE reports the signal strength, and based on this, the network decides when to
switch (during an ongoing session).
gNB :The 5G base station currently serving the device before the handover.

eNB (eNodeB):The LTE base station that takes over the connection when the
device moves out of 5G coverage.
AMF :Manages the UE’s connection in the 5G network. It helps coordinate the
handover to the LTE network.
MME (Mobility Management Entity):Manages the UE’s mobility and session in the
LTE network once it hands over from 5G.
SGW (Serving Gateway):Part of the LTE core network that handles the user plane
during the handover, ensuring that the data session continues uninterrupted.
Handover Command & Notifications:These are the messages exchanged between
the gNB, eNB, and the core network to ensure the UE is seamlessly handed over
from 5G to LTE without dropping the session.
Figure 5.17: Example Interworking Between Architecture Options 2 and 3

This figure shows how 5G Standalone (Option 2) and 5G Non-Standalone (Option

3) architectures can work together within a network.

This figure shows how 5G Standalone (Option 2) and 5G Non-Standalone (Option

3) architectures can work together within a network.

Interpretation:

 This figure demonstrates how operators can deploy both Standalone 5G

(Option 2) and Non-Standalone 5G (Option 3) in parallel, ensuring backward
compatibility with LTE devices while also supporting new 5G devices.
 Interworking between these two options allows the network to handle a mix of
devices—those relying on LTE and those fully leveraging 5G capabilities.

 This flexibility ensures a smooth transition to full 5G deployment over time,

supporting different devices and use cases.
This figure essentially shows how 5G can coexist with LTE during the transition
phase, providing seamless connectivity across multiple technologies.

4o

7. Summary
The 5G architecture provides significant improvements over LTE, including:

 Lower latency and higher data speeds.

 Network slicing, allowing operators to create custom virtual networks for different
services.

 Flexible, cloud-native deployment with the separation of the control and user
planes.

 Interworking with LTE, ensuring smooth transitions between networks.

5G enables not only faster mobile broadband but also new use cases like industrial IoT,
smart cities, and real-time communications. The architecture is designed to scale
efficiently, meet various performance requirements, and support future applications.