5G / NEW RADIO

5G NR and 5G Core Study Guide

Fourteen topics from the air interface to the core network, each with diagrams, a step-by-step explanation and the 3GPP references.

Prefer to read offline?
The complete guide as one PDF: 88 pages, 9.8 MB.

Download PDF ↓
01

1. From EPC to the 5G Core

How MME, S-GW and P-GW became AMF, SMF and UPF, in two steps.

1.1The 4G core today

The 4G core today

In the EPC, the MME handles signalling, mobility and session control. The S-GW and P-GW each do two jobs at once: they take part in the signalling and they forward the user data.

TS 23.401 §4.2

1.2Step one: CUPS

Step one: CUPS

Release 14 split each gateway in two. SGW-C and PGW-C keep the control part. SGW-U and PGW-U only forward packets. The control part steers the user part over the new Sx interfaces, so user plane nodes can be scaled and placed close to the user.

TS 23.214 · TS 29.244

1.3Step two: regroup the functions

Step two: regroup the functions

5G regroups these pieces. The mobility part of the MME becomes the AMF. Its session part joins SGW-C and PGW-C in the SMF. The two user plane gateways merge into the UPF. The HSS becomes UDM and AUSF, and the PCRF becomes the PCF.

TS 23.501 §4.2 · TS 23.214

1.4The 5G core as reference points

The 5G core as reference points

N1 and N2 carry signalling from the UE and the gNB to the AMF. N3 carries user data to the UPF. The SMF controls the UPF over N4, using PFCP, the same protocol CUPS introduced for Sx.

TS 23.501 §4.2.3 · TS 29.244

1.5The 5G core as services

The 5G core as services

The control functions no longer need a dedicated interface for every pair. Each one offers services over HTTP/2 and the others call them. NRF, NSSF and NEF are new: service discovery, slice selection and exposure to applications.

TS 23.501 §4.2.6 · TS 29.500

1.6Who does what: NG-RAN and 5GC

Who does what: NG-RAN and 5GC

The radio side keeps radio resource management and scheduling. The AMF handles NAS security and idle mode mobility. The SMF allocates the UE IP address and controls PDU sessions. The UPF anchors mobility and handles the packets.

TS 38.300 §4.2

1.7Three changes to remember

Three changes to remember

The 5G core is the EPC taken apart and put back together: control separated from user plane, mobility separated from sessions, and services in place of fixed interfaces.

TS 23.501 · TS 23.214 · TS 38.300
02

2. 5G Core Network Functions

Who does what in the 5G core: one page per network function, then the reference points and the 4G to 5G vocabulary.

AMF, Access and Mobility Management Function: the front door of the core. Terminates N2 from the RAN and N1 NAS signalling from the UE, NAS ciphering and integrity protection, registration, connection, reachability and mobility management, access authentication and authorization (SEAF), transports session management messages between UE and SMF. 4G equivalent: MME mobility part. Reference points N1, N2, N8, N11, N12, N22. TS 23.501 §6.2.1
SMF, Session Management Function: sets up and looks after PDU sessions. PDU session establishment, modification and release, UE IP address allocation, selects and controls the UPF and configures traffic steering, session management part of NAS, interface to the policy function, charging support, downlink data notification. 4G equivalent: MME session part plus SGW-C and PGW-C. Reference points N4, N7, N10, N11. TS 23.501 §6.2.2
UPF, User Plane Function: the only core function that touches user data. Anchor point for intra-RAT and inter-RAT mobility, PDU session point of interconnect to the data network, packet routing, forwarding and inspection, QoS handling with rate enforcement and packet marking, traffic usage reporting, downlink buffering. 4G equivalent: SGW-U plus PGW-U. Reference points N3, N4, N6, N9. TS 23.501 §6.2.3
UDM and AUSF, subscriber data and authentication. UDM, Unified Data Management: generates the 3GPP AKA authentication credentials, handles the SUPI and de-conceals the SUCI, access authorization from subscription data, tracks the serving AMF and SMF; 4G equivalent HSS, TS 23.501 §6.2.7. AUSF, Authentication Server Function: authentication for 3GPP and untrusted non-3GPP access, compares RES* with XRES* in 5G AKA and delivers the anchor key; TS 23.501 §6.2.8, TS 33.501
PCF and AF, policy and the applications that influence it. PCF, Policy Control Function: unified policy framework, provides policy rules to the control plane functions, reads subscription information from the UDR; 4G equivalent PCRF, TS 23.501 §6.2.4. AF, Application Function: an application such as IMS talking to the core, application influence on traffic routing, reaches the core directly if trusted, otherwise through the NEF; TS 23.501 §6.2.10
NSSF, NRF and NEF, new in 5G: slices, discovery and exposure. NSSF, Network Slice Selection Function: selects the network slice instances, determines the Allowed NSSAI and the AMF set; TS 23.501 §6.2.14. NRF, Network Repository Function: functions register their profile and others discover them; §6.2.6. NEF, Network Exposure Function: exposes capabilities and events to applications and third parties, closest 4G equivalent SCEF; §6.2.5
Reference points table: N1 UE to AMF, NAS signalling. N2 RAN to AMF, NGAP. N3 RAN to UPF, user data in GTP-U tunnels. N4 SMF to UPF, PFCP. N5 PCF to AF. N6 UPF to data network. N7 SMF to PCF, session policy. N8 AMF to UDM, subscription and registration data. N9 UPF to UPF. N10 SMF to UDM. N11 AMF to SMF, PDU session control. N12 AMF to AUSF, authentication. N13 AUSF to UDM, authentication vectors. N14 AMF to AMF, UE context transfer. N15 AMF to PCF, access and mobility policy. N22 AMF to NSSF, slice selection. TS 23.501 §4.2.7
4G terms and their 5G counterparts: APN becomes DNN, PDN connection becomes PDU session, EPS bearer becomes QoS flow identified by QFI, QCI becomes 5QI, Attach becomes Registration, IMSI becomes SUPI sent concealed as the SUCI, GUTI becomes 5G-GUTI, S1-MME and S1-U become N2 and N3, S1AP becomes NGAP, tracking area list becomes registration area. TS 23.501, TS 23.502, TS 23.401
Summary: AMF is the entry point for registration, mobility and NAS security and forwards session messages to the SMF. SMF controls PDU sessions and the UE IP address and instructs the UPF over N4. UPF is the only function in the user data path, N3 from the RAN and N6 to the data network. UDM and AUSF replace the HSS, PCF replaces the PCRF. NSSF, NRF and NEF are new: slice selection, service discovery and exposure.
03

3. 5G Protocol Stacks

Which protocol runs on which interface: control plane, user plane, and the stack of every RAN and core interface.

Control plane protocol stack, UE to gNB to AMF. UE: NAS, RRC, PDCP, RLC, MAC, PHY. gNB: RRC, PDCP, RLC, MAC, PHY towards the UE over Uu, and NGAP, SCTP, IP towards the AMF over N2 (NG-C). NAS runs end to end between UE and AMF inside RRC and NGAP. RRC ends in the gNB. NGAP runs over SCTP. NAS-MM ends in the AMF, NAS-SM is passed on to the SMF. TS 38.300 §4.4.2, TS 23.501 §8.2, TS 38.413, TS 24.501
User plane protocol stack, UE to gNB to UPF. UE: application, PDU layer, SDAP, PDCP, RLC, MAC, PHY. gNB: SDAP, PDCP, RLC, MAC, PHY over Uu, and GTP-U, UDP, IP towards the UPF over N3 (NG-U). The PDU layer is the user traffic: IPv4, IPv6, Ethernet or unstructured. SDAP maps QoS flows to data radio bearers and marks the QFI. One GTP-U tunnel per PDU session. TS 38.300 §4.4.1, TS 23.501 §8.3, TS 37.324, TS 29.281
What each layer does. NAS: registration, authentication and session management, TS 24.501. RRC: system information, connection control, radio bearers, measurements and mobility, TS 38.331. SDAP: maps QoS flows to data radio bearers, TS 37.324. PDCP: ciphering, integrity protection, header compression, reordering and duplication, TS 38.323. RLC: segmentation and ARQ, modes TM, UM and AM, TS 38.322. MAC: scheduling, multiplexing, HARQ and random access, TS 38.321. PHY: channel coding, modulation, OFDM and beamforming, TS 38.201, TS 38.211 to 38.214
NG and Xn interface stacks. NG-C (N2), signalling to the AMF: NGAP over SCTP over IP. NG-U (N3), user data to the UPF: user PDUs in GTP-U over UDP over IP. Xn-C, handover and dual connectivity signalling between gNBs: XnAP over SCTP. Xn-U, data forwarding between nodes: GTP-U over UDP. TS 38.410 to 38.414, TS 38.420 to 38.425
F1, E1 and N4 interface stacks. F1-C, CU to DU signalling carrying RRC messages: F1AP over SCTP. F1-U, user data between DU and CU: GTP-U over UDP. E1, CU-CP to CU-UP, no user data: E1AP over SCTP. N4, SMF tells the UPF how to treat packets: PFCP over UDP. TS 38.470 to 38.475, TS 38.460 to 38.463, TS 29.244
Service-based interface between the control functions of the 5G core: JSON over HTTP/2 over TLS over TCP over IP, between an NF service consumer and an NF service producer. TCP in place of SCTP. APIs are described in OpenAPI, one specification per function, such as TS 29.518 for the AMF. TS 29.500, TS 29.501, TS 23.501 §7
One-page summary of interface, protocol, transport and specification. N1: NAS inside RRC and NGAP, TS 24.501. Uu: RRC over PDCP, RLC, MAC, PHY, TS 38.331. N2 (NG-C): NGAP over SCTP, TS 38.413. Xn-C: XnAP over SCTP, TS 38.423. F1-C: F1AP over SCTP, TS 38.473. E1: E1AP over SCTP, TS 38.463. N4: PFCP over UDP, TS 29.244. SBI: HTTP/2 and JSON over TCP with TLS, TS 29.500. N3, Xn-U, F1-U: GTP-U over UDP, TS 29.281. Rule of thumb: RAN signalling over SCTP, user data in GTP-U over UDP, the core talks HTTP/2 over TCP.
04

4. Inside the gNB

CU, DU and RU: where the base station is cut, and what F1 and E1 carry.

4.1The classic base station

The classic base station

A gNB can be one box that holds the whole radio protocol stack, from RRC down to RF. That is simple, but every site then needs the full processing, and sites cannot share it.

TS 38.300 §4 · TS 38.401

4.2Eight places to cut

Eight places to cut

3GPP studied eight options for splitting the stack between a central and a remote part. The further right the cut, the more is centralised. Three matter in practice: option 2, option 7 and option 8.

TR 38.801 §11

4.3The 3GPP split: CU and DU

The 3GPP split: CU and DU

3GPP standardised option 2. The gNB-CU hosts RRC, SDAP and PDCP. The gNB-DU hosts RLC, MAC and PHY. The F1 interface connects them. To the core and to other gNBs the pair still looks like one gNB.

TS 38.401 §6.1.1

4.4What F1 carries

What F1 carries

F1-C carries F1AP signalling: interface management, UE context management and the RRC messages, which the DU passes on without reading. F1-U carries the user data in GTP-U tunnels, with flow control so the CU does not overfill the DU.

TS 38.470 · TS 38.473 · TS 38.425

4.5Splitting the CU as well

Splitting the CU as well

The CU can be split again into a control part and a user part. CU-CP hosts RRC and the PDCP for signalling. CU-UP hosts SDAP and the PDCP for user data. E1 connects the two, and it carries no user data.

TS 38.401 §6.1.2 · TS 38.460

4.6Fronthaul, midhaul, backhaul

Fronthaul, midhaul, backhaul

A split gNB needs three transport segments. Fronthaul runs from the radio unit to the DU. Midhaul is F1, from the DU to the CU. Backhaul is NG, from the CU to the core.

TS 38.401 · eCPRI and O-RAN specifications

4.7Why the cut position matters

Why the cut position matters

A high layer split is easy on transport: its bitrate follows the user traffic and it tolerates delay. A low layer split needs far more capacity and very low latency, but allows close coordination between cells.

TR 38.801 §11.1

4.8Who hosts what

Who hosts what

CU-CP for signalling, CU-UP for user data, DU for the real-time layers and RU for the radio. F1 and E1 are open 3GPP interfaces, so the parts can come from different vendors.

TS 38.401 §6.1 · TS 38.470 · TS 38.460
05

5. 5G Deployment Options

Six ways to combine the LTE and NR radios with the EPC and the 5G core, and where SA and NSA fit.

5.1Two radios, two cores

Two radios, two cores

5G brought a new radio, NR, and a new core, 5GC. Each can be paired with the LTE radio or the LTE core, EPC. 3GPP numbered these combinations as options. Options 6 and 8, NR anchored on the EPC alone, were dropped, so six remain.

TR 38.801 · TS 38.300 §4.1 · TS 37.340

5.2Option 1: LTE as it is

Option 1: LTE as it is

Option 1 is the 4G network as it is: an LTE eNB connected to the EPC over S1. It is the starting point of every migration path.

TS 36.300

5.3Option 3: EN-DC, the NSA launch

Option 3: EN-DC, the NSA launch

Option 3 adds NR without a new core. The LTE eNB is the master node and holds the control plane to the EPC. An NR node, the en-gNB, is the secondary node and adds capacity. This is EN-DC, the non-standalone 5G most networks launched with.

TS 37.340 §4.1.2

5.4Option 3, 3a and 3x

Option 3, 3a and 3x

The three variants differ in where user data splits. In 3, the eNB splits it. In 3a, the core sends separate bearers to each node. In 3x, the en-gNB splits it, so the NR node carries the load.

TS 37.340 §4.2 · MCG, SCG and split bearers

5.5Option 2: standalone 5G

Option 2: standalone 5G

Option 2 is standalone 5G: an NR gNB connected to the 5G core over NG, with no LTE involved. The 5G core brings network slicing and the service-based architecture.

TS 38.300 §4.1 · TS 23.501

5.6Option 5: LTE on the 5G core

Option 5: LTE on the 5G core

Option 5 keeps the LTE radio but connects it to the 5G core. The upgraded eNB is called an ng-eNB and uses the NG interface. The UE needs 5G NAS to use it.

TS 38.300 §4.1

5.7Option 7: NGEN-DC

Option 7: NGEN-DC

Option 7 is dual connectivity on the 5G core with LTE as the anchor. The ng-eNB is the master node and an NR gNB is the secondary node. This is NGEN-DC.

TS 37.340 §4.1.3

5.8Option 4: NE-DC

Option 4: NE-DC

Option 4 turns it around. The NR gNB is the master node and an ng-eNB is the secondary node. This is NE-DC: NR leads and LTE adds capacity.

TS 37.340 §4.1.3

5.9The six options side by side

The six options side by side

Most operators started with option 3 and are moving to option 2. Options 4, 5 and 7 are in the specifications but rarely deployed. Two NR nodes on the 5G core is called NR-DC.

TS 37.340 §4.1 · TS 38.300 §4.1
06

6. Dual Connectivity

One UE, two base stations at once: cell groups, signalling bearers and the three kinds of data bearer.

6.1One UE, two nodes

One UE, two nodes

In dual connectivity the UE uses radio resources of two base stations at the same time. The master node holds the control plane connection to the core. The secondary node adds capacity. The two nodes talk over X2 or Xn.

TS 37.340 §4.1

6.2Two cell groups

Two cell groups

The cells of the master node form the master cell group, with a PCell. The cells of the secondary node form the secondary cell group, with a PSCell. Inside each group, carrier aggregation can add SCells.

TS 37.340 §3.1 · TS 38.331

6.3Control plane: one RRC state

Control plane: one RRC state

The UE has a single RRC state, set by the master node. Each node still has its own RRC entity. The secondary node writes its own configuration, and the master node carries it to the UE inside its own RRC message.

TS 37.340 §4.2.1

6.4Split SRB and SRB3

Split SRB and SRB3

With a split SRB, the master node sends the same RRC message over both radio paths, which protects it when one path is weak. With SRB3, a gNB acting as secondary node exchanges RRC messages with the UE directly, for example its own measurements and reconfigurations.

TS 37.340 §4.2.1

6.5Three bearer types

Three bearer types

From the UE side there are three kinds of data bearer. An MCG bearer uses only the master cell group. An SCG bearer uses only the secondary cell group. A split bearer has one PDCP and an RLC leg in each group.

TS 37.340 §4.2.2

6.6Where PDCP sits in the network

Where PDCP sits in the network

On the network side each bearer is terminated in one node: the one that hosts its PDCP and its connection to the core. For a split bearer, that node sends part of the data to the other node over X2-U or Xn-U.

TS 37.340 §4.2.2

6.7Carrier aggregation or dual connectivity

Carrier aggregation or dual connectivity

Both add carriers, but in different places. Carrier aggregation works inside one node and splits the data at MAC. Dual connectivity uses two nodes and splits at PDCP, so it tolerates a slower link between them. The two can be combined.

TS 38.300 §5.4.1 · TS 37.340

6.8Three things to remember

Three things to remember

Dual connectivity is two nodes sharing one UE: the master node leads, the secondary node adds capacity, and PDCP is the layer that ties the two paths together.

TS 37.340 §4
07

7. Secondary Node Addition

How a UE on LTE gets its NR leg in EN-DC, message by message.

7.1The trigger

The trigger

The UE is connected on LTE. The MeNB asks it to measure NR with event B1. When the UE reports an NR cell that is strong enough, the MeNB decides to add an NR secondary node.

TS 36.331 · TS 37.340 §10.2.1

7.2SgNB Addition Request

SgNB Addition Request

The MeNB asks the SgNB to allocate resources. The request carries the bearers to serve, the UE capabilities, the measurement results and the security key for the SgNB, S-KgNB.

TS 37.340 §10.2.1 step 1 · TS 36.423

7.3The SgNB accepts

The SgNB accepts

The SgNB admits the bearers, picks the PSCell and reserves radio resources. Its answer contains the NR RRC configuration for the UE, the secondary cell group configuration, packed in a container.

TS 37.340 §10.2.1 step 2

7.4The UE is reconfigured

The UE is reconfigured

The MeNB sends RRCConnectionReconfiguration and puts the NR configuration inside it unchanged. The UE applies both parts and answers Complete. The MeNB then tells the SgNB that the UE has accepted.

TS 37.340 §10.2.1 steps 3–5 · TS 36.331

7.5Random access on NR

Random access on NR

The UE synchronises to the PSCell of the SgNB and performs random access there. From now on it has two radio links: LTE to the MeNB and NR to the SgNB.

TS 37.340 §10.2.1 step 6 · TS 38.321

7.6Bearer state moves over

Bearer state moves over

If a bearer moves to the SgNB, the MeNB sends its PDCP sequence number status in SN Status Transfer and forwards the buffered data, so nothing is lost or duplicated.

TS 37.340 §10.2.1 steps 7–8

7.7The core path is updated

The core path is updated

For bearers that now end in the SgNB, the MeNB tells the MME the new downlink tunnel address. The S-GW switches the path and sends an end marker on the old one. User data now reaches the UE through NR.

TS 37.340 §10.2.1 steps 9–12 · TS 36.413

7.8The same procedure on the 5G core

The same procedure on the 5G core

With a 5G core the steps are the same and only the names change. X2AP becomes XnAP, E-RABs become PDU sessions and QoS flows, and the path update goes to the AMF.

TS 37.340 §10.2.2 · TS 38.423 · TS 38.413
08

8. The 5G QoS Model

PDU session, QoS flow, QFI and radio bearer: how a packet gets its treatment from the core to the air.

8.1Three levels

Three levels

A PDU session carries all traffic to one data network. Inside it, QoS flows are the finest unit of treatment, each with its own identifier, the QFI. On the radio, the gNB packs the flows into data radio bearers.

TS 23.501 §5.7.1 · TS 38.300 §12

8.2Downlink: marking in the UPF

Downlink: marking in the UPF

The UPF classifies each downlink packet with its packet detection rules and writes the QFI into the GTP-U header. The gNB reads the QFI and SDAP places the packet on the right radio bearer.

TS 23.501 §5.7.1 · TS 29.281 · TS 37.324

8.3Uplink: QoS rules in the UE

Uplink: QoS rules in the UE

In the uplink there are two steps in the UE. NAS-level QoS rules decide which QoS flow a packet belongs to. Then the access stratum decides which radio bearer carries that flow. The gNB passes the QFI on to the UPF.

TS 23.501 §5.7.1.4 · TS 38.300 §12

8.4Who gets what from the SMF

Who gets what from the SMF

The SMF decides the QoS and tells three parties. The UE gets QoS rules over NAS. The gNB gets a QoS profile for each flow over N2. The UPF gets detection and enforcement rules over N4.

TS 23.501 §5.7.1.2 · TS 23.502 §4.3.2

8.5Flows onto radio bearers

Flows onto radio bearers

How flows map to radio bearers is up to the gNB. Flows with similar needs can share a bearer, and a demanding flow can have one to itself. Uplink packets that match no mapping rule go to the default bearer.

TS 38.300 §12 · TS 37.324

8.6The SDAP header

The SDAP header

SDAP is the new layer that does this mapping. Its header is a single octet with the QFI. Two downlink bits switch on reflective behaviour, so the UE can learn its uplink mapping from the downlink packets without extra signalling.

TS 37.324 §6.2.2

8.7GBR and non-GBR flows

GBR and non-GBR flows

Every PDU session has a default QoS flow, which is non-GBR and stays for the life of the session. GBR flows are added for traffic that needs a guaranteed rate, and delay-critical GBR flows for traffic with hard deadlines.

TS 23.501 §5.7.2 · §5.7.3

8.8What changed from 4G

What changed from 4G

In 4G one EPS bearer meant one radio bearer and one core tunnel. In 5G the core tunnel is per PDU session, the QoS flow is the unit of QoS, and the gNB is free to group flows on the radio.

TS 23.401 · TS 23.501 §5.7
09

9. 5G QoS: Rules, Parameters and 5QI

The reference side of QoS: the QoS rule, the parameters and characteristics, and the standardised 5QI tables.

The QoS rule, sent to the UE by the SMF or derived by reflective QoS. It contains a QoS rule identifier, the QFI, a packet filter set and a precedence value. IP packet filter set: source and destination address or prefix, port numbers, protocol ID, type of service or traffic class, flow label, security parameter index, direction. Ethernet packet filter set: MAC addresses, Ethertype, VLAN tags. Every PDU session has a default QoS rule, evaluated last. TS 23.501 §5.7.1.4, §5.7.6, TS 24.501 §9.11.4.13
QoS parameters signalled for a QoS flow. 5QI, all flows. ARP, allocation and retention priority, all flows. GFBR and MFBR, guaranteed and maximum flow bit rate, GBR flows. Notification control, GBR flows. RQA, reflective QoS attribute, non-GBR flows. Session-AMBR per PDU session, enforced in the UPF and the UE. UE-AMBR per UE, enforced in the gNB. TS 23.501 §5.7.2
QoS characteristics, what a 5QI stands for: resource type (non-GBR, GBR or delay-critical GBR), priority level, packet delay budget (PDB) between UE and UPF, packet error rate (PER), averaging window for GBR flows with default 2000 ms, maximum data burst volume for delay-critical GBR. For a standardised 5QI the characteristics are not signalled. TS 23.501 §5.7.3
Standardised GBR 5QI values with priority, delay budget, error rate and example services. 5QI 1: 20, 100 ms, 10^-2, conversational voice. 2: 40, 150 ms, 10^-3, conversational video. 3: 30, 50 ms, 10^-3, real-time gaming, V2X. 4: 50, 300 ms, 10^-6, buffered streaming. 65: 7, 75 ms, 10^-2, mission-critical push-to-talk. 66: 20, 100 ms, 10^-2, push-to-talk. 67: 15, 100 ms, 10^-3, mission-critical video. 71 to 74 and 76: live uplink streaming. 75: 25, 50 ms, 10^-2, V2X. TS 23.501 Table 5.7.4-1
Standardised non-GBR 5QI values with priority, delay budget, error rate and example services. 5QI 5: 10, 100 ms, 10^-6, IMS signalling. 6: 60, 300 ms, 10^-6, buffered video, TCP. 7: 70, 100 ms, 10^-3, voice, live video, gaming. 8: 80, 300 ms, 10^-6. 9: 90, 300 ms, 10^-6, often the default. 10: 90, 1100 ms, 10^-6, satellite access. 69: 5, 60 ms, 10^-6, mission-critical signalling. 70: 55, 200 ms, 10^-6, mission-critical data. 79: 65, 50 ms, 10^-2, V2X. 80: 68, 10 ms, 10^-6, low-latency eMBB. TS 23.501 Table 5.7.4-1
Standardised delay-critical GBR 5QI values with priority, delay budget, error rate, maximum data burst volume and example services. 5QI 82: 19, 10 ms, 10^-4, 255 B, discrete automation. 83: 22, 10 ms, 10^-4, 1354 B. 84: 24, 30 ms, 10^-5, 1354 B, intelligent transport systems. 85: 21, 5 ms, 10^-5, 255 B, electricity distribution. 86: 18, 5 ms, 10^-4, 1354 B, V2X advanced driving. 87: 25, 5 ms, 10^-3, 500 B. 88: 25, 10 ms, 10^-3, 1125 B. 89: 25, 15 ms, 10^-4, 17000 B. 90: 25, 20 ms, 10^-4, 63000 B, cloud and edge rendering. TS 23.501 Table 5.7.4-1
Where the QoS is signalled, the same flow described per interface. N1 NAS: PDU Session Establishment Accept with authorized QoS rules, QoS flow descriptions and Session-AMBR. N2 NGAP: PDU Session Resource Setup Request with QoS flow list and QFI. F1 F1AP: UE Context Setup Request with DRBs and mapped flows. E1 E1AP: Bearer Context Setup Request. N4 PFCP: Session Establishment Request with PDR, QER and FAR. Uu RRC: RRCReconfiguration with DRB configuration and SDAP mapping. TS 24.501, TS 38.413, TS 38.473, TS 38.463, TS 29.244, TS 38.331
Summary: a QoS rule is QFI, packet filter set and precedence, and the default rule catches everything else. Parameters are per flow: 5QI and ARP always, bit rates for GBR flows, AMBR limits for non-GBR flows. Characteristics are what the 5QI stands for: resource type, priority, delay budget and error rate. 5QI 1, 5 and 9 are the ones in most logs: voice, IMS signalling and default data. TS 23.501 §5.7, TS 24.501, TS 38.413
10

10. RM, CM and RRC States

Three state machines run in every 5G UE at the same time. What each one tracks, and how they fit together.

10.1Three state machines

Three state machines

A 5G UE is always in three states at once. RM says whether it is registered. CM says whether it has a signalling connection to the core. RRC says what kind of radio connection it has. The first two are NAS states. The third is a radio state.

TS 23.501 §5.3.2 · §5.3.3 · TS 38.331 §4.2.1

10.2Registration management

Registration management

In RM-DEREGISTERED the network cannot reach the UE. A successful registration moves it to RM-REGISTERED, where the AMF holds its context. The UE then refreshes its registration when it moves to a new area and periodically on timer T3512.

TS 23.501 §5.3.2

10.3Connection management

Connection management

CM-CONNECTED means the UE has an N1 signalling connection to the AMF. That connection is made of two parts: the RRC connection on the radio side and the N2 connection between the gNB and the AMF. In CM-IDLE neither exists.

TS 23.501 §5.3.3

10.4Three RRC states

Three RRC states

NR has three RRC states. RRC setup takes the UE from idle to connected. A plain release sends it back to idle. A release with suspendConfig sends it to RRC_INACTIVE, and a resume brings it back to connected.

TS 38.331 §4.2.1 · §5.3

10.5What changes in each RRC state

What changes in each RRC state

Idle and inactive look alike for the UE: it reselects cells on its own and listens for paging. The difference is in the network. In inactive the gNB keeps the UE context, pages the UE itself, and the core still sees it as connected.

TS 38.331 §4.2.1 · TS 38.300 §7.2

10.6One UE over time

One UE over time

Follow one UE. It registers and all three states change together. When the data stops, the gNB suspends the UE: RRC goes to inactive, but CM stays connected. When data returns, a resume is enough. After long inactivity everything goes back to idle.

TS 23.501 §5.3.3.2.5 · TS 38.300 §9.2.2

10.7Why RRC_INACTIVE exists

Why RRC_INACTIVE exists

From idle, getting back to data needs a full setup with the core involved. From inactive, the UE resumes with the context and keys it already has. That saves signalling and time for devices that send small amounts of data often.

TS 38.300 §9.2.2 · TS 38.331 §5.3.13

10.8Three things to remember

Three things to remember

RM and CM are tracked by the UE and the AMF. RRC is tracked by the UE and the gNB. RRC_INACTIVE is the one state where the radio side and the core side see the UE differently.

TS 23.501 §5.3 · TS 38.331 §4.2
11

11. RRC Inactive

Suspend, the RAN notification area, resume and RAN paging: how the gNB keeps a UE on standby.

11.1Suspend: what the UE is given

Suspend: what the UE is given

The gNB moves a UE to RRC_INACTIVE with an RRCRelease that contains suspendConfig. It gives the UE an identity for its stored context, the I-RNTI, an area to move in, a paging cycle and a timer.

TS 38.331 §5.3.8 · SuspendConfig

11.2The RAN notification area

The RAN notification area

The RAN notification area is a set of cells, given as a cell list or as RAN area codes. It lies inside the registration area. Within it the UE reselects cells freely and tells no one.

TS 38.300 §9.2.2.3

11.3Resume at the same gNB

Resume at the same gNB

To return to connected, the UE sends RRCResumeRequest with its I-RNTI and a short integrity check. The gNB finds the stored context and answers RRCResume. The bearers come back as they were.

TS 38.331 §5.3.13 · TS 38.300 §9.2.2.4.1

11.4Resume at a different gNB

Resume at a different gNB

If the UE has moved, the new gNB reads the I-RNTI to find the last serving gNB and fetches the UE context from it over Xn. After the resume it switches the path at the core and releases the old context.

TS 38.300 §9.2.2.4.1 · TS 38.423

11.5RAN paging

RAN paging

The core still thinks the UE is connected, so downlink data simply arrives at the last serving gNB. That gNB pages the UE in its own cells and asks its neighbours over Xn to page in theirs. The UE answers with a resume.

TS 38.300 §9.2.2.4.2 · TS 38.423

11.6RNA update

RNA update

The UE reports in when timer T380 expires or when it enters a cell outside its notification area. It sends a resume request with the cause rna-Update. The gNB can answer with a new suspend, so the UE stays inactive.

TS 38.300 §9.2.2.5 · TS 38.331 §5.3.13.8

11.7Security at resume

Security at resume

The resume request goes out unprotected on SRB0, so it carries a short MAC-I to prove the UE is genuine. Both sides then derive a fresh key, and everything from RRCResume onwards is ciphered and integrity protected.

TS 33.501 §6.8.2 · TS 38.331 §5.3.13.3

11.8Idle and inactive side by side

Idle and inactive side by side

RRC_INACTIVE moves the standby job from the core to the RAN: the gNB keeps the context, the gNB pages, and the gNB is told when the UE leaves its area.

TS 38.300 §9.2.2 · TS 38.331 §4.2.1
12

12. 5G Access Control

How a congested network stops access attempts before they are sent: cell barring and Unified Access Control.

12.1Two mechanisms

Two mechanisms

When a cell is overloaded, the cheapest request is the one that is never sent. 5G has two tools for that. Cell barring keeps UEs off a cell altogether. Unified Access Control filters single access attempts, by who is asking and what for.

TS 22.261 §6.22 · TS 38.304 §5.3 · TS 38.331 §5.3.14

12.2Cell barring and reservation

Cell barring and reservation

The MIB carries cellBarred, so the UE learns the status before it reads anything else. SIB1 can reserve the cell for operator use or for other use. A UE that finds a cell barred leaves it out of cell selection for up to 300 seconds.

TS 38.331 MIB, SIB1 · TS 38.304 §5.3.1

12.3Who is asking, and what for

Who is asking, and what for

UAC describes every access attempt with two things. The access identity says who the subscriber is, for example an ordinary user or a priority service user. The access category says what the attempt is for.

TS 24.501 §4.5.2 · TS 22.261 §6.22

12.4Access categories

Access categories

The standardised categories cover paging response, emergency, signalling, voice, video, SMS and data. Operators can define their own in the range 32 to 63. For most categories NAS also sets the matching RRC establishment cause.

TS 24.501 Table 4.5.2.2 · Table 4.5.6.1

12.5What the cell broadcasts

What the cell broadcasts

SIB1 lists the barring for each access category as a set of three values: a barring factor, a barring time, and seven bits that say which special access identities are barred.

TS 38.331 §6.3.2 · UAC-BarringInfoSetList

12.6The barring check

The barring check

Category 0, the response to paging, is never barred. A UE with a special identity whose bit is zero is allowed. Everyone else draws a random number. If it is below the barring factor the attempt goes ahead. If not, the UE waits for timer T390.

TS 38.331 §5.3.14.5

12.7NAS classifies, RRC checks

NAS classifies, RRC checks

The work is shared inside the UE. NAS maps the request to an access category and hands it to RRC with the access identities. RRC runs the check against the latest SIB1 and reports back. The network is not asked.

TS 24.501 §4.5 · TS 38.331 §5.3.14

12.8Three things to remember

Three things to remember

One framework replaces the separate barring schemes of LTE. The operator turns a few values in SIB1, and each UE decides for itself whether to send.

TS 22.261 · TS 24.501 §4.5 · TS 38.331 §5.3.14
13

13. 5G SA Initial Registration

From the first SSB beam to the first IP packet: cell search, random access, registration and PDU session establishment, message by message.

13.1Find the cell: SSB

Find the cell: SSB

The gNB sweeps SSB beams. PSS and SSS give timing and the physical cell ID. The MIB on PBCH gives the SFN and where to find SIB1. The UE keeps the strongest SSB index. That beam choice decides which PRACH occasion it will use.

TS 38.213 §4.1 · TS 38.331 MIB

13.2Read SIB1

Read SIB1

DCI 1_0 scrambled with SI-RNTI in CORESET#0 schedules SIB1 on PDSCH. SIB1 carries the PLMN list, tracking area code, cell selection thresholds and the RACH configuration. The UE now camps on the cell.

TS 38.331 §5.2.2 · TS 38.304

13.3Msg1: PRACH preamble

Msg1: PRACH preamble

The UE sends a randomly chosen preamble in the PRACH occasion mapped to its SSB. It has no identity on the cell yet. The gNB measures the timing offset. The UE ramps its power on each retry.

TS 38.321 §5.1 · TS 38.213 §8.1

13.4Msg2: Random Access Response

Msg2: Random Access Response

DCI 1_0 with RA-RNTI schedules the RAR. It gives the timing advance, an uplink grant for Msg3 and a Temporary C-RNTI. The UE computes the RA-RNTI itself from the PRACH occasion it used, and listens inside the RA response window.

TS 38.321 §5.1.4 · TS 38.213 §8.2

13.5Msg3: RRCSetupRequest

Msg3: RRCSetupRequest

On the granted PUSCH the UE sends ue-Identity and establishmentCause, here mo-Signalling. ue-Identity is ng-5G-S-TMSI-Part1 if the UE has one, otherwise a 39-bit random value.

TS 38.331 §5.3.3.3

13.6Msg4: RRCSetup

Msg4: RRCSetup

The Contention Resolution MAC CE echoes the Msg3 identity. The UE that sees its own identity has won. RRCSetup configures SRB1. The Temporary C-RNTI becomes the C-RNTI and the UE is RRC_CONNECTED.

TS 38.321 §5.1.5 · TS 38.331 §5.3.3.4

13.7Registration Request reaches the AMF

Registration Request reaches the AMF

RRCSetupComplete carries the NAS Registration Request: type initial, SUCI or 5G-GUTI, UE security capability, requested NSSAI. The gNB selects an AMF and forwards the NAS PDU in NGAP Initial UE Message. The UE starts T3510.

TS 24.501 §5.5.1.2.2 · TS 23.502 §4.2.2.2.2 · TS 38.413

13.85G AKA authentication

5G AKA authentication

UDM resolves the SUCI and creates the vector. The AMF sends RAND, AUTN, ngKSI and ABBA. The USIM checks AUTN and the UE returns RES*. The AMF checks HRES* against HXRES*, the AUSF checks RES* against XRES*. K_SEAF and K_AMF follow.

TS 33.501 §6.1.3.2

13.9NAS security

NAS security

The AMF selects the NAS ciphering and integrity algorithms and replays the UE security capabilities to stop bidding down. Security Mode Complete carries the full Registration Request in the NAS message container. From here NAS is ciphered and integrity protected.

TS 24.501 §5.4.2 · §5.5.1.2.2 · TS 33.501 §6.7.2

13.10UE context and AS security

UE context and AS security

The AMF registers in UDM and fetches subscription data. Initial Context Setup gives the gNB K_gNB, the UE security capabilities and the allowed NSSAI. The gNB activates AS security with keys derived from K_gNB. It can also ask for the UE radio capabilities.

TS 23.502 §4.2.2.2.2 steps 14–21 · TS 38.413 · TS 38.331 §5.3.4

13.11Registration Accept

Registration Accept

Registration Accept assigns the 5G-GUTI, the TAI list, the allowed NSSAI and 5GS network feature support, such as IMS voice over PS. RRCReconfiguration sets up SRB2. The UE answers Registration Complete. It is registered, but still has no data path.

TS 24.501 §5.5.1.2.4 · TS 38.331 §5.3.5

13.12PDU Session Establishment Request

PDU Session Establishment Request

The UE asks for a PDU session: session ID, type, SSC mode and PCO, with DNN and S-NSSAI in the UL NAS Transport. The AMF selects an SMF. The SMF reads subscription data, gets policy from the PCF, selects a UPF, allocates the IP address and sets up N4.

TS 23.502 §4.3.2.2.1 steps 1–10 · TS 24.501 §6.4.1

13.13Accept and user plane

Accept and user plane

The SMF returns the Accept with the UE IP address, QoS rules and Session-AMBR, plus N2 information with the QoS flows and the UPF tunnel. The gNB sets up the DRB and returns its tunnel endpoint. The SMF updates the UPF over N4, and data can flow.

TS 23.502 §4.3.2.2.1 steps 11–17 · TS 38.413
14

14. 5G NR Bands, NR-ARFCN and Bandwidth

Where a 5G carrier sits in the spectrum, how its channel number works, and how wide it can be.

14.1Two frequency ranges

Two frequency ranges

NR works in two frequency ranges. FR1 runs from 410 MHz to 7.125 GHz. FR2, the millimetre wave range, runs from 24.25 to 52.6 GHz. Release 17 extends it to 71 GHz.

TS 38.104 §5.1

14.2Operating bands

Operating bands

A network does not pick any frequency it likes. It uses operating bands, each with a number, the letter n in front, and a duplex mode. n28 and n1 are FDD. n41 and n78 are TDD. All FR2 bands are TDD.

TS 38.104 §5.2 · TS 38.101-1 Table 5.2-1

14.3Band combinations

Band combinations

Bands can be combined, for carrier aggregation or for dual connectivity with LTE. Only combinations listed in the specification are allowed. The phone reports the ones it supports in its UE capability message, and the network configures only those.

TS 38.101-1 §5.5A · TS 38.101-3 · TS 38.331 §5.6.1

14.4The channel number: NR-ARFCN

The channel number: NR-ARFCN

The exact carrier position is given by a channel number, the NR-ARFCN. Frequency = offset + step × (channel number − its offset). The step is 5 kHz below 3 GHz, 15 kHz up to 24.25 GHz, and 60 kHz above that.

TS 38.104 §5.4.2.1

14.5Try it on a real log

Try it on a real log

Channel 154570 × 5 kHz gives 772.85 MHz, in band n28. Channel 641760 is above 600000, so we use 15 kHz steps starting at 3 GHz. The result is 3626.4 MHz, in band n78.

NR-ARFCN values from a live-network log · TS 38.104 §5.4.2.1

14.6Channel raster

Channel raster

Not every point of the global grid can be used. Each band has its own channel raster. In n41 it is 15 kHz, so only every third point of the 5 kHz grid is a valid carrier position. A coarser synchronization raster tells the phone where to search for the SSB.

TS 38.104 §5.4.2.3 · §5.4.3

14.7Channel bandwidth and guard bands

Channel bandwidth and guard bands

The channel bandwidth is not all usable. Resource blocks fill the middle and a guard band is left on each side. At 15 kHz spacing, a 50 MHz channel carries 270 resource blocks: 48.6 MHz, with about 700 kHz of guard on each side.

TS 38.101-1 §5.3.2 · §5.3.3

14.8Maximum bandwidth per subcarrier spacing

Maximum bandwidth per subcarrier spacing

The widest channel depends on the subcarrier spacing. In FR1, 15 kHz reaches 50 MHz and 30 kHz reaches 100 MHz with 273 resource blocks. In FR2, 120 kHz reaches 400 MHz. Each is about 3200 subcarriers, which fits a 4096-point FFT.

TS 38.101-1 Table 5.3.2-1 · TS 38.101-2 Table 5.3.2-1

14.9Five ideas to read any log

Five ideas to read any log

To sum up: range, then band, then channel number, then raster, then bandwidth. With these five ideas you can read the frequency part of any 5G log.

TS 38.104 · TS 38.101-1 · TS 38.101-2

Written from the 3GPP specifications. Diagrams are simplified and not to scale. Clause numbers refer to the Release 15 to 18 versions of the specifications named; check the current version before relying on a detail.