tx-haut-débit

5G Network Architecture Overview

5G introduces a more flexible and scalable architecture, handling higher data
rates and lower latency than previous generations (like 4G/LTE). A key feature
of this flexibility is the
separation of network functions into different units, specifically the Central
Unit (CU) and Distributed Unit (DU).

Figure5.5 Overall 5G radio access network (RAN)

architecture

CU -Central Unit- handles higher-layer processing, linked to 5G Core via

NG.

DU -Distributed Unit- located at the cell site, processes time-sensitive

tasks and connects to the CU through F1.

Multiple DUs can be managed by a single CU. CUs communicate with each
other via the Xn interface, ensuring coordination and seamless
handovers. The 5G Core interfaces with the CU to manage user data and
control signaling.

tx-haut-débit 1
 Why separate? While the CU can be centralized (even cloud-based), the
DU remains close to the cell site to handle tasks that require fast response
times → less need for every site to manage high-level tasks and less costs.

Interfaces in 5G Architecture
F1: Connects the CU to one or more DUs.

Xn: Connects different CUs, enabling smooth handovers.

E1: Facilitates separation of the control and user plane processing of the CU
for the CU-CP and CU-UP parts.

NG: Divided into two plane parts, NG-U (user plane part) is called the
N3 interface, and NG-C (control plane part) is called the N2 interface.

Figure5.9 NG-interface control and user plane

protocol stacks

NG-C is based on the use of the Stream Control Transmission Protocol

(SCTP) on top of an IP connection. Its key features are NG interface
management, UE context and mobility management, Transport of NAS
messages, Paging and PDU session management.

NG-U transports the user data.

Figure5.10 Xn control and user plane protocols

tx-haut-débit 2
 The Xn-interface, 5GC (X2-interface, 4G EPCC) connects gNBs to another
gNB (or to eNB).

For the UP side, the key functionality is data forwarding and flow control

For the CP side, key functionalities are Xn-interface management, UE

mobility management, including context transfer and RAN paging and
dual connectivity.

Figure 5.13 Example network slicing use case

5G network slicing divides the network into multiple virtualized networks

(slices), each tailored to specific service requirements (latency/mobility)
The figure shows the different handling for two slices with different types of
service requirements:

tx-haut-débit 3
 Slice 1: Handles services w/ low latency but no mobility, such as local
edge computing. The User Plane Function (UPF) for this service is
placed closer to the user at the network edge, reducing latency.

Slice 2: Supports mobile broadband (MBB) services (streaming, internet

browsing), w/ mobility requirements. Here, the UPF is placed deeper in
the core network, prioritizing connectivity and scalability.

Figure 5.14 Setting up a slice for UE

Different UEs (User Equipment-devices) connect to slices based on their

service needs. Accessing a local service without mobility → low-latency slice,
while another user needing mobile broadband → mobility slice.

Figure 5.15 Reselection from 5G to LTE

tx-haut-débit 4
 This figure demonstrates the interworking between 5G and LTE (4G) during a
UE mobility scenarios. It focuses on the concept of context transfer between
the 5G Core and the EPC (Evolved Packet Core) for seamless connectivity.

When losing the coverage of the 5G signal, two alternatives are available:

1. In idle mode: the UE can reselect the LTE cell, in which case the UE mobility
management (MM) and SM context will be transferred from the 5G core to
the EPC.

2. In the active mode: the UE can switch between 5G and LTE without
requiring a full reconnection process, maintaining continuity for ongoing
sessions: seamless handover.

Figure 5.16 5G to LTE inter-system handover

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.

tx-haut-débit 5
 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.

tx-haut-débit 6