5G Core Protocols and

Procedures (eLecture)

5G Core Protocols and

Procedures (eLecture)

e)
ur
ct
es es
Le
© Ericsson AB 2019 | Course Name | LZU108xxxx Rxy | Figure - 0
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 0

 5G Core Protocols and
Procedures (eLecture)

Course Objectives

On completion of this course the participants will be able to:

› Explain the basic conceptual network architecture and technology for the 5G Core
› List and explain Identifiers relevant for the 5GC
› List the interfaces and explain the signaling, protocols and service exchange between
the network functions
› Analyze the basic procedures for 5GC

e)
ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -1
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 1

 5G Core Protocols and
Procedures (eLecture)

Table of contents

Chapters……………………………………………………………… Page
1 Introduction ………………………………………………………................................. 003
2 5GC Identifiers.……………………………………………………………………………... 043
3 5GC Interfaces and Protocols……………………………………………………… 064
4 5GC Basic Procedures………………………………………………………………….. 172
5 Acronyms & Abbreviations …………………………………............................. 187

e)
ur
ct
es es
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -2

Le
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 2

 5G Core Protocols and
Procedures (eLecture)

5G Core Protocols and

Procedures

Chapter 1
Introduction

e)
ur
ct
es es
Le
ur vic
© Ericsson AB 2020 | 5G Core Protocols and Procedures (eLecture) | LZU1082900 R1B | Figure - 3
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 3

 5G Core Protocols and
Procedures (eLecture)

Chapter Objectives

On completion of this chapter, the participants will be able to:

— Explain the basic conceptual network architecture and technology for the 5G Core

e)
ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -4
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 4

 5G Core Protocols and
Procedures (eLecture)

5G Core Basic Architecture

— Support:
Authentication Network Network Policy Unified
— SA & NSA NR Server Exposure Repository Control Data Mgmt.
— non-SIM devices
— non-3GPP access
— Service Based Architecture
— Fast new service creation w/o standards Service-Based Interfaces
(SBI)
impact (some limits)
— Cloud Native core implementation Network Slice Access & Session
Selection Mobility Mgmt.
— Capabilities:
— UE connect to multiple Application
network slices simultaneously N1 N2 N4
— Improved and simplified QoS Data
N3 User Plane N6 Network
— UE access local and
User Plane
centralized networks

e)
within single connection N9

ur
ct
SA: Stand Alone

es es
Le
NSA: Non-Stand Alone
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -5 FWA: Fixed Wireless Access
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 5

 5G Core Protocols and
Procedures (eLecture)

5G Core for fixed broadband

Conceptual architecture – work in progress
Network Slice Authentication Network Network Policy Unified
Selection Server Exposure Repository Control Data Mgmt.
5G CPE; wireline access termination,
terminates N1 interface towards 5G Core

N1
Access & Session
Mobility Mgmt.
Fixed Access
5G CPE Access Gateway
N2
Fixed Wireless Access (FWA)

N3

N1 N2
Application
Wi-Fi N4

e)
N3 N6 Data

ur
User Plane Network

ct
User Plane

es es
Le
N9
ur vic
CPE – Customer Premises Equipment

(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -6
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 6

 5G Core Protocols and
Procedures (eLecture)

5G System Architecture
3GPP TS 23.501 V15.0.0 (2017-12)
5G architecture defined as service-based, interaction between NFs represented in 2 ways:

Service-based representation. Reference point representation.

where network functions (e.g. AMF) within the control plane Shows that interaction exist between the NF services in the
enables other authorized network functions to access their network functions described by point-to-point reference point (e.g.
services N11) between any two network functions (e.g. AMF and SMF)

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -7
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 7

 5G Core Protocols and
Procedures (eLecture)

5G Network Definitions
3GPP TS 23.501

— 5G System (5GS)
— 3GPP system consisting of 5G Access Network (AN), 5G Core Network (5GC) and UE
— 5G Access Network (AN)
— An access network comprising a 5G-RAN and/or non-3GPP AN connecting to a 5G Core Network
— 5G Core Network (5GC)
— Core network specified in 3GPP TS 23.501. Connects to 5G AN.
— 5G-RAN
— Radio access network; supports standalone (SA) and non-standalone (NSA) New Radio (NR)

e)
ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -8
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 8

 5G Core Protocols and
Procedures (eLecture)

3GPP 5G System
5GS
S
S S D
S
D S S S
AUSF NRF UDM PCF NSSF NEF AF

Nausf Nnrf Nudm Npcf Nnssf Nnef Naf

5GC
Namf Nsmf

S S
AMF SMF

N1
N2
5G AN N4

e)
Data
B G Network

ur
N3 N6
NG UE 5G RAN UPF (e.g. operator

ct
or Internet)

es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -9
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 9

 5G Core Protocols and
Procedures (eLecture)

5G Core Architecture
Reference Point Representation
S
S S S
D D
N13
NSSF AUSF UDM PCF

N12 N8 N10 N7 N5
N22

N1
N14
S S
AMF N11 SMF

N15
N2
N4

B G Data

e)
5G RAN UPF
N3 N6 Network

ur
(e.g. operator
NG UE

ct
or Internet)

es es
N9

Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -10
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 10

 5G Core Protocols and
Procedures (eLecture)

3GPP Definition of Network Function

— Network function (NF)

— 3GPP adopted or 3GPP defined processing function in network, with defined functional
behaviour and 3GPP defined interfaces
— Physical Network Function (PNF)
— NF implemented as software instance on dedicated hardware
— Virtual Network function (VNF)
— NF implemented as software instance on cloud infrastructure

e)
ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -11
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 11

 5G Core Protocols and
Procedures (eLecture)

5G System Architecture
Includes 21 5GC NFs (Rel-15)
5GC
S S S S
S S S
NRF SMSF
D
BSF
D
N32
5G- CHF GMLC SEPP
› 5GC with Service Based Interface EIR
(SBI) between Control Plane (CP) Nnrf Nsmsf Nbsf N5g-eir Nchf Ngmlc
network functions S D
s s
S S D S S
d d
LMF UDSF NEF
› CP/UP split of GW like CUPS, AUSF UDR UDM PCF NSSF AF

realized by SMF/UPF
› NSSF for slice selection Nausf Nudr Nudm Npcf Nnssf Nlmf Nudsf Nnef Naf

› NRF for NF registration and service Namf Nsmf Nnwdaf

discovery N1
S S S
AMF SMF NWDAF
N2

N2 N4
B N3 G N6
Data
Network
NG- UPF (e.g. operator

e)
or Internet)
RAN
B

ur
G
NG UE N3

ct
Non- N3IWF

es es
Le
3GPP
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -12 access
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 12

 5G Core Protocols and
Procedures (eLecture)

5GC Network Functions

— 5G-EIR 5G Equipment Register — SMSF Short Message Service Function
— AF Application Function — UDM Unified Data Management
— AMF Access and Mobility Management Function — UDR Unified Data Repository
— AUSF Authentication Server Function — UDSF Unstructured Data Storage Function
— BSF Binding Support Function — UPF User Plane Function
— CHF Charging Function
— GMLC Gateway Mobile Location Center
— LMF Location Management Function
— N3IWF Non-3GPP InterWorking Function
— NEF Network Exposure Function
— NRF Network Repository Function
— NSSF Network Slice Selection Function
— NWDAF Network Data Analytics Function
— PCF Policy Control Function

e)
ur
— SEPP Security Edge Protection Proxy

ct
— SMF Session Management Function
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -13
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 13

 5G Core Protocols and
Procedures (eLecture)

5G System architecture
Reference points (Rel-15)
N-interface Node Node N-interface Node Node
N1 UE AMF N21 SMSF UDM
N2 AN AMF N22 AMF NSSF
N3 AN UPF N23 PCF NWDAF
N4 SMF UPF N24 vPCF hPCF
N5 PCF AF N25 - -
N6 UPF DN N26 AMF MME
N7 SMF PCF N27 NRF NRF
N8 AMF UDM N28 CHF PCF
N9 UPF UPF N29 NEF SMF
N10 SMF UDM N30 NEF PCF
N11 AMF SMF N31 vNSSF hNSSF
N12 AMF AUSF N32 vSEPP hSEPP
N13 UDM AUSF N33 NEF AF
N14 AMF AMF N34 NSSF NWDAF
N15 AMF PCF N35 UDM UDR
N16 vSMF hSMF N36 PCF UDR
N17 AMF 5G-EIR N37 NEF UDR

e)
N18 NF UDSF N38 - -

ur
N19 - - N39 - -

ct
es es
Le
N20 AMF SMSF N40 SMF CHF
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -14
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 14

 5G Core Protocols and
Procedures (eLecture)

5G Core Architecture
Non-3GPP Access
S S
— Connectivity via untrusted
S S S S D D Rx (for legacy IMS)
non-3GPP access networks, NSSF AUSF NEF NRF UDM PCF
e.g. WLAN access
Nnssf Nausf Nnef Nnrf Nudm Npcf

— Non-3GPP Inter-Working Namf Nsmf

Function (N3IWF);
interfaces CP & UP NFs S S
via N2 and N3 AMF SMF
N1 Naf

S
NWu N2 N4 AF

N9
Y1 H S G Data
Network
Un- UPF

e)
trusted Y2 N3IWF N3 N6 (e.g. operator
or Internet)

ur
Wi-Fi
NG UE

ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -15 N3IWF: Non-3GPP Interworking Function
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 15

 5G Core Protocols and
Procedures (eLecture)

5G Core Architecture
Distributed UP Function in serial

S S
— Leverage new CP/UP split S D D
N13
— Enables flexible deployment options AUSF UDM PCF
— Local service network support
N12 N8 N10 N7 N5

N1
S S
AMF N11 SMF
N2
N15
N4
N4
Local

B G G
Data
Network
N6 Data
5G RAN N3 UPF N9 UPF N6 Network

e)
(e.g operator
NG UE

ur
or Internet)
Remote Location Central Location

ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -16
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 16

 5G Core Protocols and
Procedures (eLecture)

Roaming 5GS Architecture – Local Breakout

e)
ur
ct
SEPP – Security Edge Protection Proxy

es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -17
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 17

 5G Core Protocols and
Procedures (eLecture)

Roaming 5GS Architecture –

Local Breakout (Reference Points)

e)
ur
ct
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -18
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 18

 5G Core Protocols and
Procedures (eLecture)

Roaming 5GS Architecture –

Home Routed

e)
ur
ct
es es
Le
SEPP – Security Edge Protection Proxy
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -19
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 19

 5G Core Protocols and
Procedures (eLecture)

Roaming 5GS Architecture –

Home Routed (Reference Points)

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -20
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 20

 5G Core Protocols and
Procedures (eLecture)

Roaming 5GS Architecture – Non-3GPP Access Local

Breakout

e)
ur
ct
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -21
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 21

 5G Core Protocols and
Procedures (eLecture)

Roaming 5GS Architecture – Non-3GPP Access Home

Routed
VPLMN HPLMN

N11 N16
AMF vSMF hSMF
N2

3GPP Access N4 N4

N3 N9 Data
UPF UPF
Network

N2

N1 N3

N3IWF

Non-3GPP Y2
NWu N1
Networks

e)
Y1

ur
Untrusted Non-
UE 3GPP Access

ct
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -22
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 22

 5G Core Protocols and
Procedures (eLecture)

5G Core compared to EPC

EPC today
S
S D S S S
D
S
D S
S1-MME MME S6a HSS PCRF
AUSF UDM PCF NRF

S11 Gx
S
D S S
NausfHSS/ Nudm PCRF Npcf Nnrf
S S DNS
G G AAA
S1-U SGW S5 PGW SGi
Nnssf Namf Nsmf

After CUPS S S S
S S
D S
NSSF AMF SMF

S1-MME MME S6a HSS PCRF S S S S

MME MME SGW PGW
S11 Gx CP CP

S S Mapping EPC N4
SGW
CP
PGW
CP
functions to 5GC
functions G

e)
G G

ur
UPF

ct
SGW PGW
S1-U SGi G G
es es
UP UP

Le
PGW SGW
UP UP
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -23

(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 23

 5G Core Protocols and
Procedures (eLecture)

Authentication Architecture - EAP

UDM as ARPF

SIM based UE SIM-less UE

5G Core S
(IMSI + AKA) (ID/IMSI + non-AKA)
D IMSI + AKA Keys
non-3GPP IDs
Additional Credentials UDM Alternative Keys

- non-3GPP IDs and keys

- Alternative auth methods
5G-RAN AUSF as EAP Back End Auth Server;

S
Performs Authentication
EAP-AKA’
S S
D Additional UCs
EAP-Method D EAP-Method
External ID - 3PP Identity Provider
Provider
AMF AUSF
EAP-AKA’
non-3GPP IDs
Alternative Keys
Non-3GPP

e)
AMF as SEAF EAP Pass

ur
Through Authenticator

ct
EAP –Extensible Authentication Protocol

es es
SEAF – Security Anchor Function

Le
ARPF – Authentication Credential Repository and Processing Function
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -24
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 24

 5G Core Protocols and
Procedures (eLecture)

Authentication Architecture – 5G AKA

SIM based UE
5G Core S
(IMSI + AKA)
D IMSI + AKA Keys
UDM
(ARPF)
5G-RAN
5G-AKA
S 5G-AKA
S
AMF D
(SEAF) AUSF
5G-AKA 5G-AKA
Non-3GPP

e)
ur
SEAF – Security Anchor Function

ct
ARPF – Authentication Credential Repository and Processing Function

es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -25
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 25

 5G Core Protocols and
Procedures (eLecture)

5G Network Slicing

— Network slice may include:

— 5GC CP and UP NFs
— 5G RAN
— N3IWF for non-3GPP Access Network
— UE simultaneously served by one or more Network Slice instances via 5G-AN
— AMF serving UE logically belong to each Network Slice instances
 Common function for Network Slice instances serving UE
— 1 PDU session belongs only to 1 Network Slice instance per PLMN
— Different slices may have slice-specific PDU sessions using same DNN

e)
ur
ct
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -26
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 26

 5G Core Protocols and
Procedures (eLecture)

5G Network Slicing Introduction

Network slice selection rarely
Across Slice Network Functions performed, e.g. at Initial Attach
RAN usually shared RAN S S
(Shared
resource in NSSF NRF
Possible verify network slice selection
gNB) based on e.g. subscription data
Device usually connect to one NSI CIoT
network slice. Limited use cases S S
S
D G
connect simultaneously to AMF/
SMF
AUSF NRF
UPF
/UDM
multiple network slices.
NSI # 0
C S
D
S
S CN of NSI contains different
Device D
AUSF
/UDM PCF NRF functionality sets. CN may be divided
CIoT Device into common (shared NFs across
S S G NSIs) and specific NFs.
C AMF SMF
UPF
Device

Device #0 NSI #1
C S
D
S
S
Virtual
Device B AUSF
D
PCF SMF G
#1
C 5G RAN
/UDM UPF

C
Device
S S S NSI #2
AMF NRF S D

e)
Virtual
Device
#2
Device #1 (Shared
resource)
SMF PCF G

ur
Shared NFs UPF

ct
NSI CN Common part

es es
NSI CN Specific part NSI – Network Slice Instance

Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -27 CIoT – Cellular IoT
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 27

 5G Core Protocols and
Procedures (eLecture)

Network Slice Selection in 5GS

Across Slice Network Functions
3) NSSF performs slice selection on request from AMF.
RAN
(Shared
S S AMF reroute to different AMF if not serve selected
resource in NSSF NRF NSIs. Selection based e.g. on NSI selection
gNB) 3 assistance information, subscription, and selection
logic in NSSF
NSI CIoT
1) Information of supported network slices S S
S
sent to RAN by CN part of NSIs AMF/ AUSF
D
NRF
G
1 SMF /UDM UPF

NSI # 0
C S
D
S
S
Device
AUSF
D
PCF NRF
/UDM
CIoT Device

2) RAN select NSI (i.e. select AMF) based on S S G SMF taking into account, NSI
Cand other information in 1 AMF SMF
4) AMF selects
NSSAI from UE selectionUPF
information, DNN, subscription
RAN Device
3) Slice Selection data and/or other policies
Device #0
Request NSI #1
C S
D
S
S
Virtual
Device B AUSF
D
PCF SMF G
#1
C 5G RAN
/UDM UPF
5) SMF may select UPF function based on e.g.
1
Device
S S

e)
C DNN,
NSI #2UE location, policies
S
2 S

ur
Virtual AMF NRF D
Device Device #1 (Shared
SMF PCF G
Shared NFs4

ct
#2 resource)
UPF

es es
5

Le
ur vic
(e
NSI – Network Slice Instance
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -28 CIoT – Cellular IoT
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 28

 5G Core Protocols and
Procedures (eLecture)

PDU Session Concepts

— PDU Connectivity Service

— Provides exchange of PDUs between UE and Data Network
— PDU Session
— Association between UE and Data Network that provides PDU Connectivity Service
— Data Network Name (DNN)
— Identifier of Data Network (DN)
— DN Access Identifier (DNAI)
— Identifier of UP access to one or more DN(s) where applications are deployed
— 5G QoS Flow
— Finest granularity for QoS forwarding treatment in 5G System. All traffic mapped to same 5G QoS Flow
receive same forwarding treatment.

e)
— 5G QoS Indicator (5QI)

ur
— Scalar used as reference to specific QoS forwarding behaviour

ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -29
PDU: Protocol Data Unit
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 29

 5G Core Protocols and
Procedures (eLecture)

PDU Session and QoS flows

QoS Flows
Associated with Application Data
5QI & ARP packets

B G

DNAI1 DNAI2
Access Data
Node UPF Network

AN Resources

e)
PDU Session

ur
(Data Radio bearers)

ct
es es
Le
5QI: 5G QoS Indicator
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -30 ARP: Allocation and Retention priority
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 30

 5G Core Protocols and
Procedures (eLecture)

PDU Session Types

— 5GC supports exchange of PDUs between UE and data network identified by DNN (PDU Connectivity
Service)
— PDU Connectivity Service realized via PDU sessions established upon UE requests
— Each PDU Session supports single type of PDU:
— IPv4
— IPv6
— IPv4v6
— Ethernet
— Unstructured (PDU type totally transparent to the 5GS)

e)
ur
ct
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -31
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 31

 5G Core Protocols and
Procedures (eLecture)

PDU Session Establishment

— PDU Sessions handled using NAS SM signaling over N1 between UE and SMF
— Established upon UE request
— Modified upon UE and 5GC request
— Released upon UE and 5GC request
— Application request 5GC to trigger UE to establish PDU session to specific DNN

e)
ur
ct
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -32

(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 32

 5G Core Protocols and
Procedures (eLecture)

PDU Session Attributes

PDU session attribute Modification allowed during Notes
PDU session lifetime
S-NSSAI and DNN are used by AMF to select a SMF to handle a new
S-NSSAI
session.

DNN If it is not provided by UE, network determines the parameter based

(Data Network Name) on default information received in user subscription. Subscription to
different DNN(s) and S-NSSAI(s) may correspond to different
default SSC modes and different default PDU Session Types.
S-NSSAI and DNN are used by AMF to select a SMF to handle a new
session.

No Each PDU Session supports a single PDU Session type i.e. supports
PDU session Type the exchange of a single type of PDU requested by the UE at the
establishment of the PDU Session. The following PDU Session types
are defined: IPv4, IPv6, Ethernet, Unstructured.

SSC mode If it is not provided by the UE, the network determines the parameter
based on default information received in user subscription.
Subscription to different DNN(s) may correspond to different default
SSC modes and different default PDU session Types

e)
PDU Session Id Must be provided by the UE

ur
ct
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -33

es es
Le
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 33

 5G Core Protocols and
Procedures (eLecture)

AMF and SMF interaction (N2&N4)

— N2:
— Unique termination in AMF regardless of S
PDU session for a UE S S N13 D D
— N4: NSSF AUSF UDM PCF
— SMF e2e control of PDU session
(no downlink N3 tunnel info, N12 N8 N10 N7 N5
UPF -> SMF -> AMF -> UE (trigger paging)) N22

N1
N14
S S
AMF N11 SMF

N15
N2
N4

B G

e)
Data
UPF Network

ur
5G RAN N3 N6
(e.g. operator

ct
NG UE or Internet)
es es
Le
N9
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -34
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 34

 5G Core Protocols and
Procedures (eLecture)

5G Policy Framework

D S S
D S S
— PCF, SA function UDR CHF PCF NWDAF NEF
— Policy decisions to SMF & AMF
— Policy subscription profile from UDR Nudr Nchf Npcf Nnwdaf Nnef
— Same functionality as in EPC;
usage monitoring, gating, traffic Namf Nsmf Naf
steering, spending limits… Rx
— Rx i/f to AF S S S
— New N15 i/f to AMF: AMF SMF AF
— Access and MM policies
— UE route selection policies
N4 G
UPF
— NWDAF (Network Data Analytics Function);
— Slice specific network data analytics for
5G non-roaming policy framework architecture SBA representation

e)
policy decisions to PCF (N23) & NSSF (N24)

ur
— I/f NEF for exposure & new use cases

ct
es es
Le
NWDAF: Network Data Analytics Function
CHF: Charging Function
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -35
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 35

 5G Core Protocols and
Procedures (eLecture)

Policy Architecture Policy enforcement control part:

- Request for policy decisions
- Enforces and distributes policy
decisions to 5G UP and 5G RAN
New interface for mobility
management policies.
Also convey UE policies.
N25/Nudr D N25/Nudr Provides policy decisions at reception of:
- Request from 5G Core Control functions
UDR - Other events (e.g. request from service
Policy decisions propagated
network)
to 5G RAN for enforcement

S S
N13
N15
Enforces policy decisions S D D
PCF
N23 S
received from Core UDM N10 NWDAF
AUSF New i/f for
N8 Analytics input

N12
S S N7

N11
Network status
Policies provided
analytics (e.g. congestion
to UE via N1
AMF SMF Based on evolution info for specific slice)
of Gx interface N5
N1 N2
Policy enforcement control part:
N4 Policy decisions propagated
to UP for enforcement Based on evolution
- Request for Mobility based policy
of Rx interface
decisions

B - Enforces and distributes mobility

policy decisions to 5G RAN G IP

e)
services
5G RAN N3 UPF N6 network

ur
(e.g. operator

ct
Policy enforcement in UP or Internet)
es es
Le
5G UE enforces policy decisions
ur vic
in UP (e.g. QoS)

(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -36
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 36

 5G Core Protocols and
Procedures (eLecture)

5G QoS Overview

› QoS flow; finest granularity of QoS differentiation in PDU

session
– Each QoS flow associated with QoS parameters used to
enforce correct traffic forwarding treatment
– Each packet belongs to one QoS flow
N3 Tunnel
› One PDU session carry one or several QoS flows
– All QoS flows sent over same N3 tunnel

› Radio Bearer carry one or several QoS flows

– Each PDU session have unique set of Radio bearers
– RAN decide which Radio Bearer one QoS flow sent over

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -37
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 37

 5G Core Protocols and
Procedures (eLecture)

Mapping of QoS Flows to Access Network

resources
Data packets from applications

QoS rules
(UL; mapping packets to QoS flows
and apply QoS flow marking)
QoS flow
(packets marked with
same QFI )

Mapping QoS PDRs

flows (DL; classify packets for
to AN QoS flow marking
Resources and other actions)
AN Resources
PDU session
UE AN UPF

e)
ur
ct
es es
Le
QFI – QoS Flow Identifier
ur vic
PDR – Packet Detection Rule

(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -38
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 38

 5G Core Protocols and
Procedures (eLecture)

Control of QoS Flows

— Two options:
1. Standardized or pre-configured 5QIs are used as QFI
— Used for Non-GBR QoS flows with 5QI < 64
— Pre-configured 5QIs cannot be used when the UE is roaming
2. Dynamically assigned QFI
— Used for all other cases

e)
ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -39
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 39

 5G Core Protocols and
Procedures (eLecture)

5GC and EPC tight interworking

S
EPC + 5GC

N26 between MME and AMF for UDM/

UE context transfer HSS

EPC
S
PCF/

B S1-MME
S S6a
S
PCRF

4G RAN MME Common function for

SGW N7
S1-U S5-C SMF and PGW-C.
N26 Mapping:
5GC 5QIQCI

SS
N1 QFIEBI

Handover from 5GC to EPC; CP

S N8 N10
SMF/S
SMF/
AMF N11 PGW-C
moved from N2 to S1-MME, SMF/
PGW-C
PGW-C 5G UPF selected for 5G
UP moved from N3 to S1-U
N2
capable UEs, both by
S5-U N4
MME and 5G SMF

GG

e)
B

ur
Control plane UPF/

ct
N3 N6/Gi
User plane 5G RAN UPF/
PGW-U

es es
Le
PGW-U
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -40 EBI – EPS Bearer Id
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 40

 5G Core Protocols and
Procedures (eLecture)

3GPP: EPC-5GC tight interworking + CUPS

UDM handles
user data incl. PCF has UE
HSS functionality policies for 4G
Enables voice and data service continuity The UE is anchored to the same SMF and UPF and 5G access
regardless if connecting over 4G or 5G

The architecture is built on: IP address

• Tight interworking between 5GC and EPC using N26 preservation
as specified in 3GPP TS 23.501
• Single-registration functionality in the UE and the core
network
SGW deployed
• SMF and UPF with S5 towards SGW according to
• Combined HSS/UDM CUPS

• PCF with Rx
• 3GPP Rel-14 CUPS

Seamless mobility between NG-RAN and

e)
E-UTRAN/EN-DC with good voice KPI’s

ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -41
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 41

 5G Core Protocols and
Procedures (eLecture)

5GC and EPC Interworking

Roaming Architecture Local Breakout
HSS +
UDM

— From 3GPP 23.501 h-PCF +

HPLMN h-PCRF

VPLMN N24
N10
v-PCF +
v-PCRF
S6a N8
N7
SMF +
PGW-C N15
S5-C
N4
UPF +
PGW-U N11
S5-U
S11 SGW

N26 AMF
MME
S1-U U

N3 N2
S1-MME

e)
N1

ur
E-UTRAN NG-RAN

ct
es es
Le
ur vic
(e
UE UE
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -42
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 42

 5G Core Protocols and
Procedures (eLecture)

5G Core Protocols and

Procedures

Chapter 2
5GC Identifiers

e)
ur
ct
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -43
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 43

 5G Core Protocols and
Procedures (eLecture)

Chapter Objectives

On completion of this chapter, the participants will be able to:

› List and explain the identifiers relevant for the 5GC

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -44
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 44

 5G Core Protocols and
Procedures (eLecture)

Tracking Area (TA) & Registration Area

PLMN:

S S
TA1
MCC + MNC

TA2 MNC TAC

AMF 1 AMF 2 MCC

TA3
PLMN ID

TAI

B B
UE
gNB1 gNB3
RA Tracking Area List
1
B B
gNB2 UE gNB4
2
Registration area
= {TAC1, TAC2}

e)
RA – Registration Area
Registration area TA – Tracking Area

ur
= {TAC2, TAC3} TAC – Tracking Area Code

ct
TAI – Tracking Area Identity

es es
Le
MCC – Mobile Country Code
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -45 MNC – Mobile Network Code

(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 45

 5G Core Protocols and
Procedures (eLecture)

Identifiers
5G Globally unique Temporary Identity (5G-GUTI)

— AMF allocates 5G-GUTI to UE, common for both 3GPP and non-3GPP access, and may re-assign new
5G-GUTI to UE at any time

— 5G-GUTI shall be structured as:

— <5G-GUTI>=<GUAMI><5G-TMSI>
— GUAMI identifies AMF and 5G-TMSI identifies UE uniquely within AMF

— Globally Unique AMF Id (GUAMI) shall be structured as:

— <GUAMI>=<MCC><MNC><AMF Region ID><AMF Set ID><AMF Pointer>

— 5G-S-TMSI shortened form of GUTI defined as:

e)
— <5G-S-TMSI>=<AMF Set Id><AMF Pointer><5G-TMSI>

ur
ct
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -46
(e TMSI – Temporary Mobile Subscription Identifier
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 46

 5G Core Protocols and
Procedures (eLecture)

5G-GUTI Format

5G-GUTI

GUAMI 5G-TMSI

PLMN ID AMFI

AMF AMF AMF

MCC MNC
Region ID Set ID Pointer

12 bits 8 or 12 bits 8 bits 10 bits 6 bits 32 bits

5G-S-TMSI

e)
48 bits

ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -47
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 47

 5G Core Protocols and
Procedures (eLecture)

Identifiers
Subscriber Permanent Identifier (SUPI)

— Globally unique SUPI shall be allocated to each subscriber in 5GS

— Following identified valid SUPI types:
— IMSI as defined by TS 23.003
— Network Access Identifier (NAI) defined by RFC 7542 and applied according to TS 23.003
— Using NAI possible to also use non-IMSI based SUPIs
— Possible for representation of IMSI within NAI for SUPI
— Used over non-3GPP Access
— SUPI shall contain address of home network in order to enable roaming
— MCC and MNC in case of IMSI based SUPI
— SUPI allocated for 3GPP UE always based on IMSI
— To enable EPC interworking

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -48
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 48

 5G Core Protocols and
Procedures (eLecture)

SUPI Two Formats

NAI Format: username@realm

Example: IMSI@realm

e)
IMSI: International Mobile Subscription Identity

ur
MCC: Mobile Country Code

ct
MNC: Mobile Network Code
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -49 MSIN: Mobile Subscriber Identification Number
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 49

 5G Core Protocols and
Procedures (eLecture)

Identifiers
Subscriber Concealed Identifier (SUCI)

— One-time use subscription identifier

— Constructed by UE including:
— Protection scheme Id (stored on USIM)
— Home Network public key (stored on USIM)
— Home network Id, e.g. MCC and MNC (not concealed)
— Protection scheme-output
— Calculation of SUCI shall be performed by USIM or ME
— Indicated by USIM
— No Indication present  Calculated in ME
— Provisioning and updating of Home Network public key can be done with the Over the Air (OTA)
mechanism

e)
— ME shall support the null-scheme if no public key available

ur
— No SUPI protection in initial registration

ct
3GPP 33.501
es es
Le
3GPP 23.003
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -50
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 50

 5G Core Protocols and
Procedures (eLecture)

SUCI Two Formats

0:IMSI 0: MCC & MNC Provided by HPLMN Encrypted MSIN or username
1: NAI 1: Home Realm

Provided by HPLMN
Provisioned in USIM
Used to route to Home UDM and AUSF -
instances serving the user

e)
NAI Format: username@realm

ur
Example: SUCI@realm

ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -51
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 51

 5G Core Protocols and
Procedures (eLecture)

SUPI concealment and de-concealment

SUCI
SUPI
S
SUCI
UE D
UDM
(SIDF)

SUPI Concealment in the UE SUPI De-Concealment in the SIDF

Home NW Home NW
SUPI Public Key SUCI Private Key
Refreshing Refreshing
MCC MNC MSIN Parameter MCC MNC Encrypted MSIN Parameter

Encyption Algorithm (ECIES) Decyption Algorithm (ECIES)

MCC MNC Encrypted MSIN MCC MNC Decrypted MSIN

e)
SUCI SUPI

ur
ct
es es
Le
SIDF – Subscriber Identity De-concealing Function
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -52 ECIES – Elliptic Curve Integrated Encryption Scheme
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 52

 5G Core Protocols and
Procedures (eLecture)

Identifiers
Permanent Equipment Identifier (PEI)

— PEI defined for 3GPP UE accessing 5GS

— PEI can assume different formats for different UE types and use cases
— UE shall present PEI to network together with indication of PEI format used

— If UE supports at least one 3GPP access, PEI must be allocated in IMEI format

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -53
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 53

 5G Core Protocols and
Procedures (eLecture)

PEI Two Formats

3GPP 23.003

IMEI: International Mobile station Equipment ID

IMEISV: IMEI and Software Version Number

e)
TAC: Type Allocation Code

ur
SNR: Serial Number

ct
CD/SD: Check Digit / Spare Digit

es es
Le
SVN: Software Version Number
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -54
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 54

 5G Core Protocols and
Procedures (eLecture)

Identifiers
Generic Public Subscription Identifier (GPSI)

— GPSIs public identifiers used both inside and outside of 3GPP system

— GPSI either MSISDN or External Identifier (TS 23.003)

— If MSISDN included in subscription data, same MSISDN value can be supported in both 5GS and
EPS

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -55
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 55

 5G Core Protocols and
Procedures (eLecture)

GPSI Two Formats

MSISDN:

3GPP 23.003

username@domain
External ID: Example: MSISDN@domain

e)
ur
ct
CC: Country Code

es es
Le
NDC:National Destination Code
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -56
ur vic
SN: Subscriber Number
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 56

 5G Core Protocols and
Procedures (eLecture)

Identifiers
Network Slice (NSSAI)
— Network Slice NSSAI
— Logical network that provides specific network capabilities and network
characteristics S-NSSAI #1
— Network Slice instance S-NSSAI #2
— Set of Network Function instances and required resources (e.g. compute, storage
and networking resources) which form deployed Network Slice S-NSSAI #3
— NSSAI (Network Slice Selection Assistance Information)
— The NSSAI is a collection of S-NSSAIs S-NSSAI #4
— S-NSSAI (Single Network Slice Selection Assistance Information)
S-NSSAI #5
— Identifies a Network Slice instance
— There can be at most 8 S-NSSAIs in the NSSAI sent in signaling messages S-NSSAI #6
between the UE and the Network
— The same Network Slice instance may be selected by means of different S-NSSAIs S-NSSAI #7

e)
— Can have standard values or PLMN-specific values
S-NSSAI #8

ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -57
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 57

 5G Core Protocols and
Procedures (eLecture)

S-NSSAI Format

— An S-NSSAI is comprised of:

— Slice/Service Type (SST), which refers to the expected Network Slice behavior in terms of features
and services
— Slice Differentiator (SD), which is optional information that complements the Slice/Service type(s)
to differentiate amongst multiple Network Slices of the same Slice/Service type
Slice/Service type SST Characteristics
value
eMBB 1 Slice suitable for the handling of 5G enhanced Mobile
Broadband
URLLC 2 Slice suitable for the handling of ultra- reliable low latency
communications
MIoT 3 Slice suitable for the handling of massive IoT

e)
ur
3GPP 23.003

ct
es es
Le
eMBB – enhanced Mobile Broad Band
ur vic
(e
URLLC – Ultra Reliable Low Latency Communication
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -58 MIoT – Massive IoT
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 58

 5G Core Protocols and
Procedures (eLecture)

NSSAI ”Types”

— Requested NSSAI
— The NSSAI that may provided by the UE (in NAS messages) to the Serving PLMN during Registration
— Subscribed NSSAI
— The S-NSSAI based on subscriber information, which a UE is subscribed to use in a PLMN
— One or more of the Subscribed S-NSSAIs can be marked as default S-NSSAI
— Allowed NSSAI
— The NSSAI provided by the serving PLMN during e.g. a Registration procedure, indicating the NSSAI allowed
by the network for the UE in the serving PLMN for the current Registration Area
— Configured NSSAI
— The NSSAI that may be provisioned in the UE, per one or more PLMNs
— Rejected NSSAI
— The UE shall not re-attempt to register to an S-NSSAI rejected in the PLMN; or until it moves out of the

e)
current Registration Area

ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -59
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 59

 5G Core Protocols and
Procedures (eLecture)

S-NSSAI Usage in Network Slicing

NWDAF: It provides slice specific network UDM: It is used for administration of PCF: It is used for policy-based slice decisions. It uses the UE Route
data analytics to a NF (e.g.PCF). slicing information for the subscriber, Selection Policy (URSP), which includes Network Slice Selection NRF: It is used
- Input @Subscription (S-NSSAI) such as Subscribed S-NSSAI(s), Default Policy (NSSP). Operator specific policies, e.g. time dependent, can for Service
- Output: Slice performance data S-NSSAI S-NSSAI(s) and Default DNN per be used to associate UE applications with S-NSSAI. discovery, and
Subscribed S-NSSAI. provides a NF
instance to the
requester based

S S S S S S
NSSF: It selects the set on S-NSSAI
of Network Slices
granted to the UE,
when AMF is unable by D D D
NSSF NWDAF AUSF UDM
itself. It determines the PCF NRF
Allowed S-NSSAIs,
further determines the
AMF, possibly by AMF: Whenever possible, based
querying the NRF. The

S S
on the UE Requested NSSAI, it
NSSF is an optional provides the UE with the Allowed
network function, on NSSAI. If necessary, it requests SMF: It may select UPF
PLMN level, external to, re-allocation of AMF via R(AN) or based on S-NSSAI.
but accessible from,
multiple slices.
directly to target AMF. AMFs are AMF SMF
shared across slices that are

S
UE: It provides supported simultaneously, or may
the Requested be dedicated to a slice. AMF
NSSAI to the selects SMF based on S-NSSAI.
network as input
AF
G
to Network Slice
RAN: It uses the NSSAI to select a
Selection.
suitable AMF for further slice and Data
B
AMF selection handling. NG RAN

e)
may make use of NSSAI for UPF Network

ur
resource allocation. (e.g. operator
or Internet)
5G RAN

ct
es es
Le
5G ©UE
Ericsson AB 2019 | | LZU1082900 R1A | Figure -60
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 60

 5G Core Protocols and
Procedures (eLecture)

Network Slice Selection Principle

S S
Subscribed S-NSSAIs
D NSSF
UDM

5
Slice #1 Slice #2 Slice #3
AMF validates the Requested
3
NSSAI based on Subscribed
AMF fetchs Subscribed S S-NSSAIs and evaluates if it
S S-NSSAIs AMF 4 can serve the UE.
AMF Otherwise, AMF asks NSSF to
gNB selects an AMF perform slice selection
based on the
Requested NSSAI 2 S
AMF

6
B
5G RAN
AMF redirects UE

e)
Registration towards
1 AMF within UE target

ur
slice

ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -61
Requested NSSAI
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 61

 5G Core Protocols and
Procedures (eLecture)

5G Core Protocols and

Procedures

Chapter 3
Interfaces and Protocols

e)
ur
ct
es es
Le
© Ericsson AB 2020 | 5G Core Protocols and Procedures (eLecture) | LZU1082900 R1B | Figure - 62
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 62

 5G Core Protocols and
Procedures (eLecture)

Chapter Objectives

On completion of this chapter, the participants will be able to:

— Explain service-based interfaces

— Explain the N1 and N2 control plane interfaces towards access networks
— Explain the N3 user plane interface towards access networks
— Explain the N4 interface between control plane and user plane

e)
ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -63
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 63

 5G Core Protocols and
Procedures (eLecture)

5G Core Protocols and

Procedures

3.1. Service Based Interfaces

e)
ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -64
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 64

 5G Core Protocols and
Procedures (eLecture)

Service-based interface in 5GC

Services and Operations

— CP NF provide one or more NF services

— NF service consist of operations based on request-response or subscribe-notify model
— Common control protocol using e.g. HTTP based API replacing protocols like Diameter and GTP-C

Service Based Interface (SBI)

NF Service Operations

NF A NF B
Request
NF Service A1 NF Service A1
Producer Response Consumer

e)
Subscribe

ur
NF Service B1 NF Service B1

ct
Consumer Notify Producer
es es
Le
ur vic
(e
ed er

NF Service Operations
d rni py
oc S

© Ericsson AB 2019 | | LZU1082900 R1A | Figure -65

an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 65

 5G Core Protocols and
Procedures (eLecture)

Service Based Interface Protocol Stack

content type:
application/json
Application/JSON IETF RFC 8259 (JSON)

HTTP/2 IETF RFC 7540

TCP IETF RFC 793

IP

L2

e)
L1

ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -66
JSON: JavaScript Object Notation
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 66

 5G Core Protocols and
Procedures (eLecture)

JSON (JavaScript Object Notation)

› Minimal readable format for structuring data

› Used to transmit data between server and web application
› Alternative to XML

› Primary parts: Keys and Values, make a Key/Value Pair

String enclosed in string, number, boolean,

quotation marks array or object
› Example: “firstName” : “Kent”

e)
ur
ct
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -67

(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 67

 5G Core Protocols and
Procedures (eLecture)

HTTP Session

S HTTP Request (Method)

HTTP Response (Status Code)

S
Client Server
NF Consumer NF Producer

Methods: Status Codes:

• POST • 1xx – Informational
• PUT • 2xx – Successful

e)
• GET • 3xx – Redirection

ur
• DELETE • 4xx – Client Error

ct
• PATCH • 5xx – Server Error
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -68
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 68

 5G Core Protocols and
Procedures (eLecture)

HTTP status codes supported for SBI

M: Mandatory
O: Optional
C: Conditional
N/A: Not Applicable

C1: Used to
Modify Resource or
INVOKE Method  O
else  N/A

C2: Used to
Create Resource  M

e)
else  N/A

ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -69
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 69

 5G Core Protocols and
Procedures (eLecture)

Mandatory HTTP standard headers

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -70
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 70

 5G Core Protocols and
Procedures (eLecture)

Server-initiated Communication

— Used for Subscribe-Notify service operations

— Require bidirectional communication between NFs
— Supported with two TCP connections, one per direction

NF A NF B
POST (Subscribe)
Client Server
2xx Success
NF Service B1 NF Service B1
Consumer Producer
POST (Notify)

e)
Client

ur
Server 2xx Success

ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -71
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 71

 5G Core Protocols and
Procedures (eLecture)

Resource URI Structure

— URI uniquely identifies a resource

— For 5GC SBI APIs resource URI specified as follows:
— {apiRoot}/{apiName}/{apiVersion}/{apiSpecificResourceUriPart}

— apiRoot: http(s):// host(:port)

— apiName: defines the name of the API, e.g. “namf-comm” Base URI
— apiVersion: Version of the API, e.g. “v1”
— apiSpecificResourceUriPart: Defines a resource URI of the API relative to the base URI,
e.g. “../ue-contexts/{ueContextId}”

e)
ur
3GPP 29.501

ct
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -72
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 72

 5G Core Protocols and
Procedures (eLecture)

Creating a Resource

— Two HTTP methods be used:

— POST
— Producer selects Resource URI
— PUT
— Consumer selects Resource URI

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -73
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 73

 5G Core Protocols and
Procedures (eLecture)

Reading a Resource

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -74
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 74

 5G Core Protocols and
Procedures (eLecture)

Updating a Resource

— Two HTTP methods be used:

— PUT
— Complete replacement of resource
— PATCH
— Partial replacement of resource

e)
ur
ct
es es
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -75

Le
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 75

 5G Core Protocols and
Procedures (eLecture)

Deleting a Resource

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -76
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 76

 5G Core Protocols and
Procedures (eLecture)

Subscribe/Notify Service Operations

— Two types of subscriptions:

— Implicit: Not explicitly created and cannot be deleted only modified, suspended or resumed
— Example: AMF is implicitly subscribed in the PCF to be notified of changes in policies
— Explicit: Explicitly created and a callback URI is provided for the corresponding notifications
— HTTP methods
— Create a subscription: POST
— Modify a subscription: PUT or PATCH
— To unsubscribe: DELETE

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -77
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 77

 5G Core Protocols and
Procedures (eLecture)

Creation of an Explicit Subscription

Body Contains callback URI

Location header = URI of created resource

e)
ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -78
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 78

 5G Core Protocols and
Procedures (eLecture)

Modify a Subscription

— Two HTTP methods be used:

— PUT
— Complete replacement of
subscription
— PATCH
— Partial replacement of subscription

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -79
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 79

 5G Core Protocols and
Procedures (eLecture)

Delete a Subscription

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -80
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 80

 5G Core Protocols and
Procedures (eLecture)

Notifications

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -81
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 81

 5G Core Protocols and
Procedures (eLecture)

NF Services Naming

— NF Service naming
— Nnfname_ServiceName (<service-based interface name>_<service name>)
— Example from AMF: Namf_Communication
— NF Service operation naming
— Nnfname_ServiceName_ServiceOperation[Method]
— Example from AMF: Namf_Communication_UEContextTransfer[Request]

e)
ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -82
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 82

 5G Core Protocols and
Procedures (eLecture)

NF Services – 3GPP 23.502

AMF Example

— AMF NF services according to 23.502

— Service operation examples:
— Namf_Communication_UEContextTransfer
[Request/Response]
— Namf_EventExposure_Subscribe

EBI: EPS Bearer Id

e)
LMF: Location Management Function

ur
GMLC: Gateway Mobile Location Center

ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -83
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 83

 5G Core Protocols and
Procedures (eLecture)

AMF Resource Structure {apiRoot}/namf-evts/v1

Structure defined in 3GPP 29.518

/subscriptions

//{apiRoot}/namf-comm/v1
/{subscriptionId}

/ue-contexts

/{ueContextId} //{apiRoot}/namf_mt/v1

/ue_contexts
/n1-n2-messages

/subscriptions
/{ueContextId}
/{n1N2MessageId}

/{subscriptionsId} /ue_reachind

/subscriptions
/non-ue-n2-messages

/subscriptions /{subscriptionsId} //{apiRoot}/namf-loc/v1

/{n2NotifySubscriptionId}

e)
/{ueContextId}

ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -84
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 84

 5G Core Protocols and
Procedures (eLecture)

Resources Map to Service Operations

Description
HTTP method or
Resource name Resource URI custom operation
(Mapped Service
Operations)
UEContextTransfer,
PATCH RegistrationCompleteNotify,
…/ue-contexts/{ueContextId} N2InfoNotify
PUT CreateUEContext
Individual ueContext (POST)
…/ue-contexts/{ueContextId}/release ReleaseUEContext
release
(POST)
…/ue-contexts/{ueContextId}/assignEbi EBIAssignment
assignEbi
ueContext collection …/ue-contexts POST N1MessageNotify
…/ue-contexts/{ueContextId}/n1-n2-
n1N2Message collection POST N1N2MessageTransfer
messages
N1N2 Subscriptions Collection ../ue-contexts/{ueContextId}/n1-n2- N1MessageSubscribe,
POST
for Individual UE Contexts messages/subscriptions N2InfoSubscribe.

e)
ur
… … … …

ct
es es
Le
3GPP 29.518
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -85
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 85

 5G Core Protocols and
Procedures (eLecture)

N1N2MessageTransfer Service Operation

NF Service
AMF
Consumer

1. The NF Service Consumer should send a HTTP POST request to the N1N2MessageCollection resource URI:
• Resource URI: {apiRoot}/namf-comm/v1/ue-contexts/{ueContextId}/n1-n2-messages
{apiRoot}: HTTP authorization of the AMF NF instance, discovered from NRF
{ueContextId}: SUPI ("imsi-[0-9]{5,15}|nai-.+") or PEI ("imei-[0-9]{15}") of the target UE.
• Payload: N1/N2 message information container

e)
• Optional: Callback-URI for N1N2MessageTransfer Notification

ur
2. If the request is accepted, the AMF shall create a sub-resource with a new unique resource id and return the URI of the created sub-
resource in "Location" header in response with the status code 204 No Content.

ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -86
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 86

 5G Core Protocols and
Procedures (eLecture)

Service Registration and Discovery

Service Registration
— Service instances are defined when system is set up, but number of instances
is dynamic (scale up/down, failures, programmed maintenance).
NF ①Service
(provider) Registration
— Need for a new NF (NRF-Network Repository Function) that supports:
— NF service instance registration and deregistration in NRF as a service producer.
NF
(consumer)
NRF — NF service consumer instance discovers/selects in NRF available service producers.
— NRF authorizes NF service consumer access to a producer.
— Service Status Awareness.

Service Discovery Service Status Aware

NF NF
(provider) (provider) ①Service
② Service ③Service Response Status Aware
Request

e)
NF NF

ur
NRF NRF
(consumer) (consumer)

ct
①Service
Discovery

es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -87
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 87

 5G Core Protocols and
Procedures (eLecture)

NF Service Discovery and Selection

— NF and NF service discovery

- NF Instance ID
implemented via NRF
- NF Type
- PLMN ID
— NF Consumer provides NF type or
specific service + slice info in NRF
- NW Slice IDs S
- FQDN or IP of NF
request - NF Capacity Info. D
- Names of supported NRF
— NRF Replies with target NF (FQDN or services
IP or relevant NF service) - Endpoint info of Nnrf
instances for spec.
service Nnf
- ID of stored data

e)
ur
NF

ct
es es
Le
Service
Consumer
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -88

(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 88

 5G Core Protocols and
Procedures (eLecture)

NF Service Registration

NF Service Consumer
Becomes operative
for 1:st time

e)
ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -89
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 89

 5G Core Protocols and
Procedures (eLecture)

NF Service Update

E.g. Scale in/out operation

performed

e)
ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -90 ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 90

 5G Core Protocols and
Procedures (eLecture)

NF Service Deregistration

E.g. NF Graceful shut down

or NF Disconnects from NW

e)
ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -91
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 91

 5G Core Protocols and
Procedures (eLecture)

NF/NF Service Discovery – Same PLMN

(NF Service Name, NF Type, SUPI, S-NSSAI)

(FQDN, IP address or service URLs)

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -92
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 92

 5G Core Protocols and
Procedures (eLecture)

NF/NF Service Discovery – Across PLMNs

(NF Service Name, NF Type,

SUPI, S-NSSAI, PLMN IDs)

e)
(FQDN, IP address or

ur
service URLs)

ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -93
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 93

 5G Core Protocols and
Procedures (eLecture)

NRF General Flows

s s s
g
NF NF
Service Service
NRF Provider
Consumer

NF Service Producer is
Instantiated/Updated/Decommissioned

Nnrf_NFMgmt_NFReg/Upd/deReg
(NF Profile)

NRF stores/updates/deletes NF
Service Producer Profile
Nnrf_NFDiscovery
Nnrf_NFMgmt_NFStatusSubs/Unsub NF profile includes applicable selection params, e.g. …
(list of available NF Service providers) - AMF: AMF SetId, AMF Region Id, GUAMI.
- SMF: NSSAI, DNN, TAI, PGWID.
Nnrf_NFMgmt_NFStatusNotify - UPF: DNN, NSSAI, SMF Area Id.
- AUSF/UDM/UDR: SUPI/GPSI Ranges, Group ID, Routing
ID, Data Type (UDR).
NF Service Consumer stores updated list
of available NF Service Providers

e)
ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -94
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 94

 5G Core Protocols and
Procedures (eLecture)

AMF Selection

— Used by:
— 5G Access Network (e.g. RAN and N3IWF) to select AMF for given UE
— AMF for AMF relocation
— Other NFs e.g. SMF when original AMF unavailable

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -95
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 95

 5G Core Protocols and
Procedures (eLecture)

AMF Selection Criteria's

— 5G-AN factors for selecting AMF Set:

— AMF Region Id and AMF Set Id derived from GUAMI
— Requested NSSAI
— Local Operator Policies
— 5G-AN or CP NFs factors for selecting AMF in AMF Set:
— Availability of candidate AMFs (by NRF look up)
— Load balancing across candidate AMFs
— 5G-AN AMF Selection priorities:
1. 5G-S-TMSI if present
2. Requested NSSAI if present
3. Configured default AMF

e)
ur
ct
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -96
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 96

 5G Core Protocols and
Procedures (eLecture)

Slice and AMF Selection

AMF may consume
Nudm_SubscriberDataM AMF may consume the
anagement (SDM) Nnssf_NSSelection service:
Service: • Allowed NSSAI

S
• Subscribed S-NSSAIs • Target AMF Set or, based on
S (including Default) configuration, the list of candidate
AMF(s).
D NSSF • …
UDM
AMF Reroutes the NAS
AMF Receives a message:
Registration Request: 2 3 • Registration Request
• Requested NSSAI • Target AMF

S
• TAI of the UE • Slicing information for
• … 1 They may be the same UE Context
or different NFs • …
Initial

B
AMF
Triggers slice 4
S
5G RAN selection Serving AMF sends the
5 AMF Registration response:

e)
AMF provides to 5G RAN: 6 • Slicing information for

ur
5G UE Holds the UE
• Allowed NSSAI the UE

ct
Context (including
• …
es es
Le
slicing information)
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -97
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 97

 5G Core Protocols and
Procedures (eLecture)

SMF Selection

— Supported by AMF to allocate SMF to manage PDU Sessions

— AMF utilizes NRF to receive IP address or FQDN for SMF instance
— SMF can optionally be locally configured in AMF
— Applicable for both 3GPP and non-3GPP access

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -98
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 98

 5G Core Protocols and
Procedures (eLecture)

SMF Selection Criteria's

— Selected Data Network Name (DNN)

— S-NSSAI
— Subscription information from UDM, e.g.:
— per DNN: whether Local Breakout (LBO) roaming allowed
— per S-NSSAI: subscribed DNN(s)
— Local operator policies (default SMF config)
— Load conditions of candidate SMFs
— Access technology (3GPP or Non-3GPP) used by UE

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -99
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 99

 5G Core Protocols and
Procedures (eLecture)

SMF Selection Procedure

Slice Specific

NRF for the Actual Slice

SMF for the Actual Slice

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -100
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 100

 5G Core Protocols and
Procedures (eLecture)

UPF Selection

— Performed by SMF by means of

— Local configuration about available UPFs
— Using NRF to discover UPF instances

— Roaming cases:
— UPF(s) in Home PLMN selected by SMF(s) in H-PLMN
— UPF(s) in Visited PLMN selected by SMF(s) in V-PLMN

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -101
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 101

 5G Core Protocols and
Procedures (eLecture)

SMF Provisioning of UPF instances using NRF

UPF Provisioning Information: Information about available

• S-NSSAI UPFs in the NW
• DNN
• Served SMF Area ID
(Used to define which UPFs
serves a specific SMF)

Alt. 1

Alt. 2

e)
ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -102
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 102

 5G Core Protocols and
Procedures (eLecture)

UPF Selection Criteria's

— UPF's dynamic load

— UPF's relative static capacity among UPFs supporting same DNN
— UPF location available at SMF
— UE location information
— Capability of UPF and functionality required for particular UE session
— Data Network Name (DNN)
— PDU Session Type (i.e. IPv4, IPv6, Ethernet Type or Unstructured Type)
— SSC mode selected for PDU Session
— UE subscription profile in UDM
— DNAI as included in PCC Rules
— Local operator policies
— S-NSSAI
— Access technology used by UE

e)
ur
ct
es es
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -103

Le
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 103

 5G Core Protocols and
Procedures (eLecture)

AUSF Selection

— AMF performs AUSF Selection using:

— NRF to discover AUSF instance(s)
— Local AMF configuration

— Used for both 3GPP and non-3GPP access

— AUSF selection criteria’s

— SUPI
— Home Network identifier of SUCI

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -104
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 104

 5G Core Protocols and
Procedures (eLecture)

PCF Selection

— AMF selects PCF for UE

— Utilizing NRF or locally configured

— SMF selects PCF for PDU session

— Utilizing NRF or locally configured based on:
— Local operator policies
— Selected DNN
— PCF selected by AMF

— Selected PCF same or different for AMF & SMF

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -105
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 105

 5G Core Protocols and
Procedures (eLecture)

UDM Discovery function

— NF Consumer discovers UDM instance in HPLMN

— Utilizing NRF or locally configured

— Applicable for both 3GPP and non-3GPP access

— NF Consumer discovers UDM based on:

— Home Network identifier of SUPI (e.g. MNC and/or MCC)
— GPSI (used by NEF or PCF)
— Home Network identifier of SUCI (e.g. MNC and/or MCC)

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -106
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 106

 5G Core Protocols and
Procedures (eLecture)

UDR Discovery Function

— NF Consumer discovers UDR instance

— Utilizing NRF or locally configured

— Applicable for both 3GPP and non-3GPP access

— NF Consumer discovers & selects UDR based on:

— SUPI or GPSI or External Group identifier
— Data Set identifier, four exist in 3GPP R15:
— Subscription Data
— Policy Data
— Data for Exposure

e)
ur
— Application Data

ct
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -107
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 107

 5G Core Protocols and
Procedures (eLecture)

Network Exposure

Exposure of:
- Network Events
- Provisioning Capabilities
- Policy and Charging Capabilities
S
NEF
- Network Capabilities for Analytics

Nnef

Nnf

S
NF

e)
Service

ur
Consumer

ct
es es
Le
Internal or External
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -108
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 108

 5G Core Protocols and
Procedures (eLecture)

Exposure of Network Events

If event requires AMF
assistance

(Ex. events:
Loss of connectivity
UE Reachability, etc)

e)
ur
ct
es es
Le
3GPP 23.502
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -109
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 109

 5G Core Protocols and
Procedures (eLecture)

Exposure
with bulk
Subscription
New NF Instantiates UE or Group of UEs

› NEF Subscribes to the NFs that provides

a specific service for a chosen UE or group
of UEs
› NEF stores information (Events) about the
specific service in UDR
› NEF provides information about the service
when applications request it

e)
ur
ct
3GPP 23.502
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -110
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 110

 5G Core Protocols and
Procedures (eLecture)

Exposure of Provisioning Capabilities

Allows external party to provision UE behavioral information to 5G NFs

e)
ur
ct
es es
Le
3GPP 23.502
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -111
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 111

 5G Core Protocols and
Procedures (eLecture)

5G Core Protocols and

Procedures

3.2. N1 and N2

e)
ur
ct
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -112
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 112

 5G Core Protocols and
Procedures (eLecture)

Protocol Stack over N2

3GPP 38.413
AMF
RFC 4960

N1
N2

UE (R)AN

e)
ur
ct
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -113
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 113

 5G Core Protocols and
Procedures (eLecture)

Procedures defined over N2

— Procedures related with N2 Interface management (not related to an individual UE)

— Procedures related to an individual UE:
— Procedures related to NAS Transport management
— Procedures related to UE Context management
— Procedures related to PDU Session Resource management
— Procedures related to Mobility management
— Two Types of Elementary Procedures (EPs)
— Class 1 – With response (success and/or failure)
— Class 2 – Without response

e)
ur
ct
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -114
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 114

 5G Core Protocols and
Procedures (eLecture)

NGAP Elementary Procedures, class 1(1/2)

Elementary Procedure Initiating Message Successful Outcome Unsuccessful Outcome
Response message Response message
AMF Configuration Update AMF CONFIGURATION AMF CONFIGURATION UPDATE AMF CONFIGURATION UPDATE
UPDATE ACKNOWLEDGE FAILURE

RAN Configuration Update RAN CONFIGURATION RAN CONFIGURATION UPDATE RAN CONFIGURATION UPDATE NG Interface
UPDATE ACKNOWLEDGE FAILURE Management
NG Reset NG RESET NG RESET ACKNOWLEDGE
procedures

NG Setup NG SETUP REQUEST NG SETUP RESPONSE NG SETUP FAILURE

Handover Preparation HANDOVER REQUIRED HANDOVER COMMAND HANDOVER PREPARATION

FAILURE UE Mobility
Handover Resource Allocation HANDOVER REQUEST HANDOVER REQUEST HANDOVER FAILURE
ACKNOWLEDGE Management
Handover Cancellation HANDOVER CANCEL HANDOVER CANCEL procedures
ACKNOWLEDGE
Path Switch Request PATH SWITCH REQUEST PATH SWITCH REQUEST PATH SWITCH REQUEST
ACKNOWLEDGE FAILURE

e)
ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -115
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 115

 5G Core Protocols and
Procedures (eLecture)

NGAP Elementary Procedures, class 1(2/2)

Elementary Procedure Initiating Message Successful Outcome Unsuccessful Outcome
Response message Response message
PDU Session Resource Modify PDU SESSION RESOURCE PDU SESSION RESOURCE
MODIFY REQUEST MODIFY RESPONSE

PDU Session Resource Modify PDU SESSION RESOURCE PDU SESSION RESOURCE PDU Session
Indication MODIFY INDICATION MODIFY CONFIRM
Management
PDU Session Resource Release PDU SESSION RESOURCE PDU SESSION RESOURCE procedures
RELEASE COMMAND RELEASE RESPONSE

PDU Session Resource Setup PDU SESSION RESOURCE PDU SESSION RESOURCE
SETUP REQUEST SETUP RESPONSE
UE Context Modification UE CONTEXT UE CONTEXT MODIFICATION UE CONTEXT MODIFICATION
MODIFICATION REQUEST RESPONSE FAILURE UE Context
UE Context Release UE CONTEXT RELEASE UE CONTEXT RELEASE
COMMAND COMPLETE management
Initial Context Setup INITIAL CONTEXT SETUP INITIAL CONTEXT SETUP INITIAL CONTEXT SETUP procedures
REQUEST RESPONSE FAILURE

e)
ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -116
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 116

 5G Core Protocols and
Procedures (eLecture)

NGAP Elementary Procedures, Class 2

Elementary Procedure Message

Configuration Downlink RAN Configuration Transfer DOWNLINK RAN CONFIGURATION TRANSFER

Transfer
Downlink RAN Status Transfer DOWNLINK RAN STATUS TRANSFER
procedures NG Interface
Downlink NAS Transport DOWNLINK NAS TRANSPORT
Management
Error Indication ERROR INDICATION
Uplink RAN Configuration Transfer UPLINK RAN CONFIGURATION TRANSFER
procedures
UE Mobility
Management Uplink RAN Status Transfer UPLINK RAN STATUS TRANSFER
procedures Handover Notification HANDOVER NOTIFY
Initial UE Message INITIAL UE MESSAGE NAS Transport
Paging NAS Non Delivery Indication NAS NON DELIVERY INDICATION procedures
Paging PAGING
procedure PDU Session Resource Notify PDU SESSION RESOURCE NOTIFY
Reroute NAS Request REROUTE NAS REQUEST
UE Context
PDU Session UE Context Release Request UE CONTEXT RELEASE REQUEST
management

e)
Uplink NAS Transport UPLINK NAS TRANSPORT
Management

ur
AMF Status Indication AMF STATUS INDICATION procedures

ct
procedures
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -117
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 117

 5G Core Protocols and
Procedures (eLecture)

N1: NAS-MM
AMF
N1
N2
UE (R)AN

— Supports
— registration management
— connection management
— user plane connection activation and
deactivation * *

— Responsible for ciphering and integrity

protection of NAS signaling

e)
* This set of protocols/layers depends on the 5G-AN.

ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -118
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 118

 5G Core Protocols and
Procedures (eLecture)

NAS Procedures

NAS
Procedures
SMF

AMF
5GMM 5GSM

PDU Session Establishment

PDU Session Modification
PDU Session Release
5GMM 5GMM Connection 5GSM Status
Common Specific Management
Primary AKA Registration Service Request
Security mode control Deregistration Paging
Identification Notification

e)
UE configuration update

ur
NAS transport MM: Mobility Management

ct
5GMM status SM: Session Management
es es
Le
3GPP 24.501
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -119
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 119

 5G Core Protocols and
Procedures (eLecture)

5G MM NAS Messages
 Authentication Request Service Reject
 Authentication Response Configuration Update Command
 Authentication Result Configuration Update Complete
 Authentication Failure Identity Request
 Authentication Reject Identity Response
 Registration Request
Notification
 Registration Accept
 Registration Complete Notification Response
 Registration Failure Security Mode Command
 UL NAS Transport Security Mode Complete
 DL NAS Transport Security Mode Reject
 De-registration Request Security Protected 5GS NAS
 De-registration Accept Message

e)
 Service Request

ur
5GMM Status

ct
 Service Accept
es es
Le
ur vic
(e
ed er

© Ericsson AB 2019 | | LZU1082900 R1A | Figure -120

d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B

 5G Core Protocols and
Procedures (eLecture)

5G SM NAS Messages
 PDU Session Establishment PDU Session Modification Request
Request PDU Session Modification Reject
 PDU Session Establishment PDU Session Modification Command
Accept PDU Session Modification Complete
 PDU Session Establishment
Reject PDU Session Modification Command
Reject
 PDU Session Authentication
Command PDU Session Release Request
 PDU Session Authentication PDU Session Release Reject
Complete PDU Session Release Command
 PDU Session Authentication PDU Session Release Complete
Result

e)
ur
ct
 5GSM Status
es es
Le
ur vic
(e
ed er
d rni py
oc S

© Ericsson AB 2019 | | LZU1082900 R1A | Figure -121

an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B

 5G Core Protocols and
Procedures (eLecture)

Registration Management (RM)

— Registration Management:
— Used to register and de-register UE/user with network
— Establish user context in network
— Initial Registration procedure involves:
— User authentication and access authorization based on subscription profiles in UDM
— Result of procedure serving AMF registered in UDM
— Once registered UE updates its registration with network:
— Periodically (Periodic Registration Update)
— Upon mobility events (Mobility Registration Update)
— To update its capabilities or re-negotiate protocol parameters (Mobility Registration Update)
— UE in Limited Service State
— Emergency Registration
— Applicable over both 3GPP and non 3GPP access

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -122
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 122

 5G Core Protocols and
Procedures (eLecture)

RM State Model in the UE

5GMM-NULL — Deregistration requested and accepted
(power off and not power-off)
— NW-initiated deregistration requested
— Enable — Disable — Non-initial registration rejected (fatal
N1 mode N1 mode causes)
— Service Request rejected or failed (fatal
causes)
5GMM- 5GMM-
DEREGISTERED REGISTERED
— Initial registration requested and
accepted

— Initial registration — Non-initial registration requested and

rejected or failed — accepted

e)
— rejected or failed (non-fatal causes)

ur
— Service Request initiated and

ct
— accepted
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -123 — rejected or failed (non-fatal causes)
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 123

 5G Core Protocols and
Procedures (eLecture)

RM State Model in the Network

— UE-initiated deregistration requested
— NW-initiated deregistration requested
— Non-initial registration rejected (fatal
causes)
— Service Request rejected (fatal causes)
— Implicit deregistration
— Common procedure failed (fatal
causes)

5GMM- 5GMM-
DEREGISTERED REGISTERED
— Initial registration successful
— Common procedure successful

— Common — Common procedure

e)
procedure failed — Successful

ur
— Failed (non-fatal causes)

ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -124
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 124

 5G Core Protocols and
Procedures (eLecture)

UE context in AMF (1/3) – General

Field Description

SUPI SUPI (Subscription Permanent Identifier) is the subscriber's permanent identity in 5GS.
SUPI-unauthenticated indicator This indicates whether the SUPI is unauthorized.
GPSI The GPSI(s) of the UE. The presence is dictated by its storage in the UDM.
5G-GUTI 5G Globally Unique Temporary Identifier
PEI Mobile Equipment Identity
Internal Group ID-list List of the subscribed internal group(s) that the UE belongs to.
UE Specific DRX Parameters UE specific DRX parameters
UE Network Capability Indicates the UE network capabilities
List of the events subscriptions by other CP NFs. Indicating the events being subscribed as well as any information
Events Subscription on how to send the corresponding notificators.
AM Policy Information Information on AM policy provided by PCF.
Subscribed RFSP Index An index to specific RRM configuration in the RAN that is received from the UDM.
RFSP Index in Use An index to specific RRM configuration in the RAN that is currently in use.
MICO Mode Indication Indicates the MICO Mode for the UE.
An indication whether the UE radio capabilities are compatible with the network configuration. The AMF uses it as
Voice Support Match Indicator an input for setting the IMS voice over PS Session Supported Indication.

UE Radio Capability for Paging Information Information used by the RAN to enhance the paging towards the UE (see clause 5.4.4.1 of TS 23.501 [2]).

Information sent by the NG RAN, and used by the AMF when paging the UE to help determining the NG RAN nodes
Information on Recommended Cells and RAN nodes For to be paged as well as to provide the information on recommended cells to each of the RAN nodes, in order to

e)
Paging optimize the probability of successful paging while minimizing the signalling load on the radio path.

ur
SMSF Identifier The identifier of the SMSF serving the UE in RM-REGISTERED state.

ct
Indicates whether the UE supports SMS delivery over NAS via 3GPP access, or via non-3GPP access, or via both the

es es
Le
SMS Supported 3GPP and non-3GPP access. ur vic
SEAF data Master security information received from AUSF.
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -125
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 125

 5G Core Protocols and
Procedures (eLecture)

UE context in AMF (2/3) – per access type

For each access type level context within the UE access and mobility context:
Access Type Indicates the access type for this context.
RM State Registration management state.
Registration Area Current Registration Area (a set of tracking areas in TAI List).
TAI of last Registration Update TAI of the TA in which the last registration request was initiated.
User Location Information Information on user location.
Mobility Restrictions restrict mobility handling or service access of a UE in the
5G System. It consists of RAT restriction, Forbidden area, Service area
Mobility Restrictions restrictions and Core Network type restriction.
Security Information for CP As defined in TS 33.501.
Security Information for UP As defined in TS 33.501.
Allowed NSSAI consisting of one or more S-NSSAIs for serving PLMN in the
Allowed NSSAI present Registration area.

e)
Network Slice Instance (S) The Network Slice Instance selected by 5GC for this UE.

ur
ct
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -126
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 126

 5G Core Protocols and
Procedures (eLecture)

UE Context in AMF (3/3) – per PDU Session

For each PDU Session level context:

S-NSSAI The associated S-NSSAI for the PDU Session

Network Slice Instance id The network Slice Instance information for the PDU Session
PDU Session ID The identifier of the PDU Session

SMF addressing information The associated SMF for the PDU Session
Access Type The current access type for this PDU session

e)
ur
ct
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -127
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 127

 5G Core Protocols and
Procedures (eLecture)

UE Registered over both 3GPP and Non 3GPP

access
— AMF associates multiple access-specific RM contexts for UE with
— Common globally unique Temporary Identifier for 3GPP and Non-3GPP access
— Registration state per access type (3GPP/Non-3GPP)
— Registration Areas (RA) per access type
— Periodic registration timer for 3GPP access
— UE not perform periodic registration update over non-3GPP access
— Temporary Identifier only be used if both accesses in same PLMN
— UE registered via 3GPP access and selects N3IWF in same PLMN
— Deregistration indication:
— All accesses or only access over which procedure is run

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -128
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 128

 5G Core Protocols and
Procedures (eLecture)

Connection Management (CM)

— Connection Management:
— Includes functions of establishing and releasing signaling connection between UE and AMF over
N1
— Used to enable NAS signaling between UE and core network
— Includes signaling connection between UE and AN
— Includes N2 connection for UE between AN and AMF

(NAS)

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -129
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 129

 5G Core Protocols and
Procedures (eLecture)

5GS CM State models

CM State model in UE
AN signaling connection
established
(Initial NAS message)
CM-IDLE CM-CONNECTED
AN signaling connection
released

CM State model in AMF

N2 connection established
CM-IDLE CM-CONNECTED

e)
ur
N2 connection released

ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -130
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 130

 5G Core Protocols and
Procedures (eLecture)

UE connected over both 3GPP and Non 3GPP

access
— AMF manages two CM states for UE:
— CM state for 3GPP access
— CM state for Non-3GPP access

— UE connected over both 3GPP and Non-3GPP access has two N2 interfaces
— UE be in any combination of CM states between 3GPP and Non-3GPP access
— Access1: CM-IDLE Access2: CM-CONNECTED
— Access1: CM-CONNECTED Access2: CM-IDLE
— Access1: CM-IDLE Access2: CM-IDLE
— Access1: CM-CONNECTED Access2: CM-CONNECTED

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -131
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 131

 5G Core Protocols and
Procedures (eLecture)

AMF and SMF Interaction (N1&N11)

— Single N1 NAS used for MM (RM & CM) and

SM-related procedures for UE
— AMF handles NAS-MM
— SMF handles NAS-SM
— AMF forwards NAS-SM to SMF (N11)
— SMF indicates to AMF if UP session is NAS (RM,CM, SM)
released
— Upon successful UP session RM,CM SM

establishment:
— AMF stores UE-id and serving SMF-id
— SMF stores UE-id and serving AMF-id

e)
RM – Registration Management

ur
CM – Connection Management

ct
MM – Mobility Management

es es
Le
SM – Session Management ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -132
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 132

 5G Core Protocols and
Procedures (eLecture)

N1: NAS-SM and SMS

— Protocols needed to be transported between UE and core network function (non-AMF) over N1 via
NAS-MM

e)
ur
ct
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -133
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 133

 5G Core Protocols and
Procedures (eLecture)

N1: NAS-SM

— Supports handling of Session management between UE and SMF

— SM signaling message handled in NAS-SM layer of UE and SMF. Content of message not interpreted
by AMF.

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -134
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 134

 5G Core Protocols and
Procedures (eLecture)

SM State Model in the UE

— PDU Session Release Request

— PDU Session Modification reject
(fatal causes)

PDU Session PDU Session

Inactive Active
— PDU Session Establishment
requested and accepted

— PDU Session
— PDU Session Establishment request
Establishment reject
— PDU Session Modification complete
— PDU Session Modification reject (non-fatal)

e)
— PDU Session Release reject

ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -135
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 135

 5G Core Protocols and
Procedures (eLecture)

SM State Model in the Network

— PDU Session Release accept

— PDU Session Modification reject
(fatal causes)

PDU Session PDU Session

Inactive Active
— PDU Session Establishment
accept

— PDU Session
— PDU Session Modification complete
Establishment reject
— PDU Session Modification reject (non-fatal)
— PDU Session Release reject

e)
ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -136
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 136

 5G Core Protocols and
Procedures (eLecture)

Session Management Concepts

— Local Area Data Network

— DN accessible by UE only specific locations that provides connectivity to specific DNN
— Service Continuity
— Uninterrupted user experience of service, including cases where IP address and/or anchoring
point changes
— Session Continuity
— Continuity of PDU session. For PDU session of IP type, "session continuity" implies IP address
preserved for PDU sessions lifetime
— PDU Session Anchor
— UP function providing interface to DN

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -137
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 137

 5G Core Protocols and
Procedures (eLecture)

Session Management Subscription Data

Session Management Subscription data contains one or more S-NSSAI level subscription data:
S-NSSAI Indicates the value of the S-NSSAI.
Subscribed DNN list List of the subscribed DNNs for the S-NSSAI.
For each DNN in S-NSSAI level subscription data:
Data needed for PDU DNN DNN for the PDU Session.
session establishment UE Address Indicates the subscribed static IP address(es) for the IPv4 or IPv6 or IPv4v6
type PDU Sessions accessing the DNN, S-NSSAI.
Data Structure Allowed PDU Session Types Indicates the allowed PDU Session Types (IPv4, IPv6, IPv4v6, Ethernet, and
Unstructured) for the DNN, S-NSSAI.
- 5GS: Subscriber
Default PDU Session Type Indicates the default PDU Session Type for the DNN, S-NSSAI.
 Slice level  DNN level
Allowed SSC modes Indicates the allowed SSC modes for the DNN, S-NSSAI.
- EPS: Subscriber
 APN-level Default SSC mode Indicate the default SSC mode for the DNN, S-NSSAI.
Interworking with EPS indication Indicates whether interworking with EPS is supported for this DNN and S-
NSSAI.
5GS Subscribed QoS profile The QoS Flow level QoS parameter values (5QI and ARP) for the DNN, S-
NSSAI.
Charging Characteristics This information is defined in TS 32.240; it may e.g. contain information on
how to contact the Charging Function. This information, when provided shall
override any corresponding predefined information at the SMF

Subscribed-Session-AMBR The maximum aggregated uplink and downlink MBRs to be shared across all
Non-GBR QoS Flows in each PDU Session, which are established for the

e)
DNN, S-NSSAI.

ur
Static IP address/prefix Indicate the static IP address/prefix for the DNN, S-NSSAI.

ct
User Plane Security Policy Indicates the security policy for integrity protection and encryption for the

es es
Le
user plane.
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -138
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 138

 5G Core Protocols and
Procedures (eLecture)

Session and Service Continuity (SSC)

—Session and Service Continuity (SSC) mode

— SSC mode associated with PDU sessions lifetime
— Meets various continuity requirements
— Three types of SSC mode:
— SSC mode 1
— SSC mode 2
— SSC mode 3

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -139
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 139

 5G Core Protocols and
Procedures (eLecture)

SSC Mode 1
— SSC Mode 1 (keep PDU session)
— UPF acting as PDU session anchor at PDU session establishment, maintained regardless of access
technology
— IP continuity supported regardless of UE mobility events

B
A
DN
UPF IP@X
IP@C (Example: IMS)
B

e)
B

ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -140
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 140

 5G Core Protocols and
Procedures (eLecture)

SSC Mode 2
— SSC Mode 2 (Break before make; new PDU session)
— Network trigger release of PDU session, instruct UE to establish new PDU session to same data
network immediately
— Establishment of new PDU Session, new UPF (anchoring point) selected based on UE mobility,
local policy (e.g. info of serving area of assigned target UPF)
— IP continuity not supported, different IP assigned for target UPF

B S-UPF1 IP@X
A
DN -1
T-UPF2 IP@Y

e)
IP@C

ur
ct
es es
Le
B ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -141
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 141

 5G Core Protocols and
Procedures (eLecture)

SSC Mode 3
— SSC Mode 3 (Make before break; keep PDU session)
— Allows establishment of UE connectivity via new target UPF (anchoring point) before previous
serving UPF released
— When trigger conditions apply network decides whether to select UPF suitable for UEs new
conditions (e.g. network attachment point)
— IP continuity not supported, different IP assigned for target UPF
Timer for keeping the

B
dual UPFs expires
IP@X IP@X

A
S-UPF1 DN -1 BA
S-UPF1
DN -1
DN -1
IP@C

B IP@Y
T-UPF2
B
IP@Y
IP@C

B
T-UPF2
B

e)
B

ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -142
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 142

 5G Core Protocols and
Procedures (eLecture)

SSC mode selection

— UE provisioned with one or more SSC mode selection policy rules

— UE can determine SSC mode associated with an application(s)
— Policy may include default SSC mode selection policy matching all UE applications

— SMF receives list from UDM of supported SSC modes and default SSC mode per DNN as part of
subscription information

— SMF selects SSC mode by either accepting requested SSC mode from UE or modifying SSC mode
based on subscription information

— SMF informs UE of selected SSC mode for PDU Session

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -143
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 143

 5G Core Protocols and
Procedures (eLecture)

5G Core Protocols and

Procedures

3.3. N3

e)
ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -144
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 144

 5G Core Protocols and
Procedures (eLecture)

Protocol Stack over N3

N3
(R)AN UPF

e)
ur
ct
es es
Le
ur vic
(e
ed er
d rni py
oc S

© Ericsson AB 2019 | | LZU1082900 R1A | Figure -145

an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 145

 5G Core Protocols and
Procedures (eLecture)

User Plane Tunneling

S
— UP tunneling between RAN and UPF used to
D
handle mobility, different PDU types, etc. UDM
— Per-PDU-Session tunneling preferred (i.e. per- S S S
D
bearer tunneling not supported) N2
AMF SMF PCF
— UP tunneling protocol for N3 is GTP-U
N4

— Additional UP options been discussed in 3GPP, B G

e.g. for fixed access, but not included in phase 1. 5G RAN N3 Data
UPF N6 Network
(e.g operator
or Internet)

e)
ur
ct
GTP – GPRS Tunneling Protocol

es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -146
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 146

 5G Core Protocols and
Procedures (eLecture)

GTP – GPRS Tunnelling Protocol

GTP GTP I/F GTP

Node A Node B

TEID=xxx TEID=yyy

Destination Port: GTP GTP TUNNEL GTP

GTPv1-U=2152 UDP UDP

IP Address = AAA
IP IP
Protocol ID:
UDP=17 IP Address = BBB
L1/L2 L1/L2

GTP TUNNEL
Identified in each node by:
[TEID, IP-addr, Port number]

TS 29.281

e)
ur
ct
es es
Le
GTP GPRS Tunneling Protocol
ur vic
TEID Tunnel Endpoint Identifier

(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -147
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 147

 5G Core Protocols and
Procedures (eLecture)

GTPv1 Headers

Bits
Octets 8 7 6 5 4 3 2 1
1 Version PT Res. E S PN
2 Message Type
st
3 Length (1 Octet)
nd
4 Length (2 Octet)
st
5 Tunnel Endpoint Identifier (1 Octet)
nd
6 Tunnel Endpoint Identifier (2 Octet)
rd
7 Tunnel Endpoint Identifier (3 Octet)
th
8 Tunnel Endpoint Identifier (4 Octet)
st
9 Sequence Number (1 Octet)
nd
10 Sequence Number (2 Octet)
11 N-PDU Number

e)
12 Next Extension Header

ur
ct
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -148
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 148

 5G Core Protocols and
Procedures (eLecture)

Extension Header for 5GS – PDU Session Container

TS 38.415

DL PDU Session Information UL PDU Session Information

e)
QFI: QoS Flow Indicator
RQI: Reflective QoS Indication

ur
PPP: Paging Policy Presence

ct
PPI: Paging Policy Indicator

es es
Le
DL: Down Link
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -149
UL: Up Link
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 149

 5G Core Protocols and
Procedures (eLecture)

Reflective QoS
— Enables UE to map UL User Plane traffic to QoS Flows without SMF provided QoS rules.

— UE derives the UL QoS rules based on the received DL traffic

— UE should indicate support of Reflective QoS for every PDU session towards SMF

— Derived UL QoS rule contains:

— UL Packet Filter – derived from DL Packet Filter
— QFI – same as for DL Packet
— Precedence value for the QoS rule

— Controlled on per-packet basis using the Reflective QoS Indication (RQI) over N3 signaled in GTP-U.
QFI and RQI mapped to DL QoS Flow, RQI=1
Radio Protocols

B G

e)
5G RAN

ur
Node UPF

ct
QoS Rule mapping

es es
Le
DL  UL UL QoS Flow
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -150 Data Radio bearer PDU Session
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 150

 5G Core Protocols and
Procedures (eLecture)

Distributed UPFs in serial

S S
— Leverage new CP/UP split S D D
N13
— Enables flexible deployment options AUSF UDM PCF
— Local service network support
N12 N8 N10 N7 N5

N1
S S
AMF N11 SMF
N2
N15
N4
N4
Local

B G G
Data
Network
N6 Data

e)
5G RAN N3 UPF N9 UPF N6 Network

ur
(e.g operator
NG UE or Internet)

ct
Remote Location Central Location
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -151
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 151

 5G Core Protocols and
Procedures (eLecture)

UPF Chaining
S S
D D
— SMF may chain multiple UPFs PCF
UDM
to build the UP path
— N9 is the UP inteface between
N8 N10 N7
UPFs

— Each UPF may act in different

roles for a PDU Session, e.g.:
S S
— PDU Session Anchor (PSA): AMF N11 SMF
UPF with the N6 interface to the N2
data network
N4
— Intermediate UPF (I-UPF):
N4
A UPF that has been inserted
between RAN and a PSA
B G G Data
— I-UPF is needed when UE move 5G RAN N3 UPF N9 UPF N6 Network
location and current RAN node (I-UPF) (PSA) (e.g operator

e)
or Internet)
cannot connect to UPF/PSA

ur
— SGW relocation in EPC Example with two UPFs

ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -152
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 152

 5G Core Protocols and
Procedures (eLecture)

S S
Multiple PDU Session Anchors D
UDM
D
PCF

N8 N10 N7

— Single PDU Session may have S S

multiple PSAs AMF N11 SMF
N2
— Additional UPF roles allow N4
”forking” of traffic within a N4
single PDU session
— Up-Link Classifier (UL-CL):
routes traffic based on packet
B G G Data
5G RAN N3 UPF N9 UPF Network
filters received by SMF (UL-CL/BP)
N6
— Branching Point (BP): (PSA) (e.g operator
or Internet)
Routes up-link traffic based on N9
source IPv6 prefix, and is applied
for IPv6 multi-homed PDU Sessions
G

e)
ur
N6 Local
UPF Data

ct
Network
Can be implemented in one VNF (PSA)
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -153
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 153

 5G Core Protocols and
Procedures (eLecture)

5G Core Protocols and

Procedures

3.4. N4

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -154
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 154

 5G Core Protocols and
Procedures (eLecture)

Protocol Stack over N4

 

PFCP PFCP
N11 SMF
UDP UDP
N4 New Protocol
IP IP

N3 N6 L2 L2
N9 UPF
L1 L1

CP function UP function

Sx and N4 reference point

e)
ur
ct
es es
Le
ur vic PFCP: Packet Forwarding Control Protocol
3GPP TS 29.244
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -155
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 155

 5G Core Protocols and
Procedures (eLecture)

PFCP Session Contexts

— CP function controls packet processing in UP function by

1. establishing, modifying or deleting PFCP Session contexts
2. provisioning (per PFCP session context)
— PDRs (Packet Detection Rules)
— FARs (Forwarding Action Rules)
— QERs (QoS Enforcement Rules)
— URRs (Usage Reporting Rules) and/or BAR (Buffering Action Rule)
— In 5GC, PFCP session context corresponds to
— individual PDU session
— standalone PFCP session (not tied to any PDU session)

e)
ur
ct
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -156
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 156

 5G Core Protocols and
Procedures (eLecture)

Packet Processing Flow

PDR
PFCP
PFCP session’s PDR
Session look PDR look up
PDR FARs QERs URRs
up (find
Packet In Packet Out
(find PFCP matching PDR
session with PDR of the Apply Instructions set in the
a matching PFCP session ... matching PDR
PDR ) with highest
precedence)

e)
ur
PDR: Packet Detection Rule

ct
FAR: Forwarding Action Rule
es es
Le
QER: QoS Enforcement Rule
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -157
URR: Usage Reporting Rule
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 157

 5G Core Protocols and
Procedures (eLecture)

Forwarding Action Rule (FAR) Handling

— CP function provision only one FAR for each PDR provisioned in PFCP session

— FAR provides instructions to UP function how to process packets matching PDR

— Setting flag(s) in Apply Action IE in FAR, CP function request UP function to:

— Drop packets (DROP flag)
— Forward packets (FORW flag)
— Buffer downlink packets (BUFF flag)
— Notify CP function about arrival of first DL packet being buffered (NOCP flag)
— Duplicate packets (DUPL flag)

e)
ur
ct
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -158
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 158

 5G Core Protocols and
Procedures (eLecture)

Buffering Action Rule (BAR) Handling

— Request UP function to apply specific buffering behavior for packets requested to be buffered and
associated to BAR

— Created by CP function for N4 session, associated to FAR(s) of PFCP session

— Sent in N4 Session establishment or N4 Session modification requests

— Buffering parameters:
— Downlink Data Notification Delay
— DL Buffering Duration
— DL Buffering Suggested Packet Count

e)
ur
ct
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -159
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 159

 5G Core Protocols and
Procedures (eLecture)

QoS Enforcement Rule (QER) Handling

— CP request UP to perform QoS enforcement of UP traffic

— Provisioned for PCFP session in N4 Session establishment or N4 Session modification requests

— QoS enforcement actions:

— Gating control
— QoS control, i.e. MBR, GBR or packet rate enforcement
— DL flow level marking for application detection
— Reflective QoS for uplink traffic (for 5GC)

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -160
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 160

 5G Core Protocols and
Procedures (eLecture)

Message Format
Bits
Octets 8 7 6 5 4 3 2 1
1 to m PFCP message header PFCP Message Format
m+1 to n Zero or more Information Element(s)

Bits
Octets 8 7 6 5 4 3 2 1
1 Version Spare Spare Spare MP S
2 Message Type
3 Message Length (1st Octet)
4 Message Length (2nd Octet)
PFCP Header Format
m to k(m+7) If S flag is set to 1, then SEID shall be placed into octets 5-12. Otherwise,
SEID field is not present at all.

e)
n to (n+2) Sequence Number

ur
(n+3) Spare

ct
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -161
(e SEID: Session Endpoint Identifier
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 161

 5G Core Protocols and
Procedures (eLecture)

Message Types Message Type value (Decimal) Message Applicability

Sxa Sxb Sxc N4
0 Reserved
1 PFCP Heartbeat Request X X X X
2 PFCP Heartbeat Response X X X X
3 PFCP PFD Management Request - X X X
4 PFCP PFD Management Response - X X X
5 PFCP Association Setup Request X X X X
6 PFCP Association Setup Response X X X X
7 PFCP Association Update Request X X X X
1-49: PFCP Node 8 PFCP Association Update Response X X X X
related messages 9 PFCP Association Release Request X X X X
10 PFCP Association Release Response X X X X
11 PFCP Version Not Supported Response X X X X
12 PFCP Node Report Request X X X X
13 PFCP Node Report Response X X X X
14 PFCP Session Set Deletion Request X X -
15 PFCP Session Set Deletion Response X X -
16 to 49 For future use
50 PFCP Session Establishment Request X X X X
51 PFCP Session Establishment Response X X X X
52 PFCP Session Modification Request X X X X
53 PFCP Session Modification Response X X X X
50-99: PFCP Session 54 PFCP Session Deletion Request X X X X
related messages

e)
55 PFCP Session Deletion Response X X X X

ur
56 PFCP Session Report Request X X X X
57 PFCP Session Report Response X X X X

ct
58 to 99 For future use

es es
Le
100-255: Other messages 100 to 255 For future use
ur vic
(e
ed er

© Ericsson AB 2019 | | LZU1082900 R1A | Figure -162

d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 162

 5G Core Protocols and
Procedures (eLecture)

PFCP Session Establishment Request

Information P Condition / Comment Appl. IE Type
elements Sxa Sxb Sxc N4
Node ID M This IE shall contain the unique identifier of the sending Node. X X X X Node ID
CP F-SEID M This IE shall contain the unique identifier allocated by the CP function identifying the session. X X X X F-SEID
M This IE shall be present for at least one PDR to be associated to the PFCP session. X X X X
Create PDR Several IEs with the same IE type may be present to represent multiple PDRs. Create PDR
Create FAR M This IE shall be present for at least one FAR to be associated to the PFCP session. X X X X
Several IEs with the same IE type may be present to represent multiple FARs. Create FAR
Create URR C This IE shall be present if a measurement action shall be applied to packets matching one or more PDR(s) of this PFCP session. X X X X
Several IEs within the same IE type may be present to represent multiple URRs. Create URR

Create QER C This IE shall be present if a QoS enforcement action shall be applied to packets matching one or more PDR(s) of this PFCP session. - X X X
Several IEs within the same IE type may be present to represent multiple QERs. Create QER

Create BAR O When present, this IE shall contain the buffering instructions to be applied by the UP function to any FAR of this PFCP session set X - - X
with the Apply Action requesting the packets to be buffered and with a BAR ID IE referring to this BAR. Create BAR

PDN Type C This IE shall be present if the PFCP session is setup for an individual PDN connection or PDU session. X X - X
When present, this IE shall indicate whether this is an IP or non-IP PDN connection/PDU session. PDN Type

SGW-C FQ-CSID C This IE shall be included according to the requirements in clause 23 of 3GPP TS 23.007. X X - FQ-CSID
MME FQ-CSID C This IE shall be included when received on the S11 interface or on S5/S8 interface according to the requirements in clause 23 of X X - -
FQ-CSID
3GPP TS 23.007.
PGW-C FQ-CSID C This IE shall be included according to the requirements in clause 23 of 3GPP TS 23.007. X X - - FQ-CSID
ePDG FQ-CSID C This IE shall be included according to the requirements in clause 23 of 3GPP TS 23.007. - X - - FQ-CSID

e)
TWAN FQ-CSID C This IE shall be included according to the requirements in clause 23 of 3GPP TS 23.007. - X - - FQ-CSID

ur
User Plane O This IE may be present to request the UP function to send a User Plane Inactivity Report when no user plane packets are received - X X - User Plane
Inactivity Timer for this PFCP session for a duration exceeding the User Plane Inactivity Timer.
Inactivity

ct
When present, it shall contain the duration of the inactivity period after which a User Plane Inactivity Report shall be generated.
Timer

es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -163
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 163

 5G Core Protocols and
Procedures (eLecture)

Example of PFCP Session Establishment Request

Message Header

Information Elements (IEs)

e)
ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -164
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 164

 5G Core Protocols and
Procedures (eLecture)

Example of PFCP Session Establishment Response

Message Header

Information Elements

e)
ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -165
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 165

 5G Core Protocols and
Procedures (eLecture)

Example of PDR Creation IE for UL

Access Core

PDR
PFCP
PFCP session’s PDR
Session look PDR look up
PDR FARs QERs URRs
up (find
Packet In Packet Out
(find PFCP matching PDR
session with PDR of the Apply Instructions set in the
a matching PFCP session ... matching PDR
PDR ) with highest
precedence)

e)
ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -166
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 166

 5G Core Protocols and
Procedures (eLecture)

Example of Created PDR IE for UL

Access Core

PDR
PFCP
PFCP session’s PDR
Session look PDR look up
PDR FARs QERs URRs
up (find
Packet In Packet Out
(find PFCP matching PDR
session with PDR of the Apply Instructions set in the
a matching PFCP session ... matching PDR
PDR ) with highest
precedence)

e)
ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -167
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 167

 5G Core Protocols and
Procedures (eLecture)

Example of PDR Creation IE for DL

Core Access

PDR
PFCP
PFCP session’s PDR
Session look PDR look up
PDR FARs QERs URRs
up (find
Packet In Packet Out
(find PFCP matching PDR
session with PDR of the Apply Instructions set in the
a matching PFCP session ... matching PDR
PDR ) with highest
precedence)

e)
ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -168
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 168

 5G Core Protocols and
Procedures (eLecture)

Example of FAR Creation IE UL

Access Core

PDR
PFCP
PFCP session’s PDR
Session look PDR look up
PDR FARs QERs URRs
up (find
Packet In Packet Out
(find PFCP matching PDR
session with PDR of the Apply Instructions set in the
a matching PFCP session ... matching PDR
PDR ) with highest
precedence)

e)
ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -169
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 169

 5G Core Protocols and
Procedures (eLecture)

Example of FAR Creation IE DL

Core Access

PDR
PFCP
PFCP session’s PDR
Session look PDR look up
PDR FARs QERs URRs
up (find
Packet In Packet Out
(find PFCP matching PDR
session with PDR of the Apply Instructions set in the
a matching PFCP session ... matching PDR
PDR ) with highest
precedence)

Tunnel End Point @ NodeB

e)
ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -170
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 170

 5G Core Protocols and
Procedures (eLecture)

Example of Create QER IE

PDR
PFCP
PFCP session’s PDR
Session look PDR look up
PDR FARs QERs URRs
up (find
Packet In Packet Out
(find PFCP matching PDR
session with PDR of the Apply Instructions set in the
a matching PFCP session ... matching PDR
PDR ) with highest
precedence)

e)
ur
ct
es es
Le
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -171
ur vic
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 171

 5G Core Protocols and
Procedures (eLecture)

5G Core Protocols and

Procedures

Chapter 4
5GC Basic Procedures

e)
ur
ct
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -172
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 172

 5G Core Protocols and
Procedures (eLecture)

Chapter Objectives

On completion of this chapter, the participants will be able to:

— Analyze the basic procedures for 5GC

— Explain the Registration Procedures
— Explore the Service Request Procedures
— Examine the Session Management Procedures
— Interpret the Handover Procedures

e)
ur
ct
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -173
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 173

 5G Core Protocols and
Procedures (eLecture)

Initial Registration with AKA Authentication over

NR (1/2)
7
Nudm_UEAuthentication_Get
4 Request
Nnrf_NFDiscovery - SUCI
AUSF discovery 6 Response
Nnrf_NFDiscovery - EAP-AKA AV

S UDM discovery
S - SUPI
s
NRF 5
AUSF d
Nausf_UEAuthentication_ UDM
Authenticate Request
1 2 8 - SUCI

AN Message N2 Message Nausf_UEAuthentication_

- N2 Parameters Authenticate Response
- AN Parameters
RM-NAS Registration RM-NAS Registration - EAP Request/AKA
Request: Request: Challenge
- Registration type: Initial
- Registration type: Initial
Registration 10
Registration
- SUCI/5G-GUTI
- SUCI/5G-GUTI Nausf_UEAuthentication_Authenticate
- Security parameters
- Security parameters
- Requested NSSAI
- Requested NSSAI Request

B S
- EAP Response / AKA Challenge
Nausf_UEAuthentication_Authenticate
Response
RAN AMF - EAP Success || Anchor key || SUPI

3 11

e)
RRC
Identity Request 9 N1 Message
s

ur
- Requesting SUCI EAP-SUCCESS NGAP
Auth-Req
d
Identity Response

ct
- SUCI EAP Request / AKA Challenge NAS

es es
Le
Auth-Res HTTP (Service based)
EAP Response / AKA Challenge
ur vic PCF
PFCP
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -174
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 174

 5G Core Protocols and
Procedures (eLecture)

Initial Registration with AKA Authentication over

NR (2/2)
S S s
NRF AUSF d
UDM

13
12
Nudm_UECM_Registration
Nnrf_NFDiscovery AMF registers with UDM
UDM discovery
19 14
16 Nudm_SDM_Get
Registration Accept
- 5G-GUTI Nnrf_NFDiscovery AMF retrieves:
- Registration Area PCF discovery Access and Mobility Subscription data
- Mobility restrictions SMF selection subscription data
- Allowed NSSAI

B S
- IMS Voice over PS 15
indication Nudm_SDM_Subscribe
AMF subscribes to changes in
AMF subscription data
20 RAN
Registration Complete

17
Npcf_AMPolicyControl_Get

e)
Request: SUPI
RRC Response: Policy information

ur
NGAP 18

ct
NAS Namf_EventExposure_Subscribe s
es es
Le
HTTP (Service based)
d
ur vic
(e
PFCP
PCF
ed er
d rni py

© Ericsson AB 2019 | | LZU1082900 R1A | Figure -175

oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 175

 5G Core Protocols and
Procedures (eLecture)

UE Requested PDU Session Establishment (1/2)

S s
d
s
d
NRF PCF UDM
2 5
Nnrf_NFDiscovery Nudm_UECM_
SMF discovery Registration
- PDU Session ID
4 - SUPI
3
Nsmf_PDUSession_ Nnrf_NFDiscovery - SMF iD
UDM discovery
CreateSMContext Request
- PDU Session ID 6
- AMF ID
- S-NSSAI
Nudm_SDM_Get
- SUPI - SSC-mode
- 5QI

B S S
- DNN
1 - Request type - AMBR
NAS Message - N1 SM Container
7
- S-NSSAI(s)
RAN - DNN AMF 8 SMF Nudm_SDM_Subscribe
- PDU Session ID
- Request Type: Initial Nsmf_PDUSession_
request CreateSMContext Response
- N1 SM Container: PDU - Result Indication
Session Establishment - PDU Session Id
Request - S-NSSAI
- N2 SM Information
- N1 SM Container

RRC

e)
NGAP
G

ur
NAS
UPF

ct
HTTP (Service based)

es es
Le
PFCP
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -176
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 176

 5G Core Protocols and
Procedures (eLecture)

UE Requested PDU Session Establishment (2/2)

S s s
NRF 12 d d
Nnrf_NFDiscovery PCF UDM
UPF discovery

10
9 Npcf_SMPolicyControl_Get
PCF provides Session-AMBR; 5QI, ARP
Nnrf_NFDiscovery
PCF discovery
16 11
17 N2 PDU Session Request 15 Nsmf_EventExposure_Subscribe
RRC Connection Reconfiguration - N2 SM Info Namf_Communication_
NAS: N1N2MessageTransfer 13
NAS:
- PDU Session ID - PDU Session ID - N2 SM information (CN Tunnel Info, QoS Nsmf_EventExposure_Notify

B S
- PDU Session - PDU Session profile(s), PDU Session ID) Allocated IP address

S
Establishment Accept Establishment Accept - N1 SM container (PDU Session
- UE IP addr - UE IP addr Establishment Accept , UE IP addr)

RAN AMF
18
SMF 14
19 N4 Session Establishment
N2 PDU Session Response
- N2 SM Info (AN tunnel info) Nsmf_PDUSession_ Request:
UpdateSMContextRequest - Packet detection,
- N2 SM info enforcement and reporting
rules
21 Response:
RRC Nsmf_PDUSession_
- CN Tunnel Info

NGAP UpdateSMContextResponse 20
NAS N4 Session Modification

e)
Request:
HTTP (Service based) - AN Tunnel Info + forwarding

ur
G
rules
PFCP

ct
User Plane

es es
UPF

Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -177
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 177

 5G Core Protocols and
Procedures (eLecture)

UE Triggered Service Request

3GPP Access
4
3
UPF Selection
Nsmf_PDUSession_UpdateSMContext - N2 parameters
1 2 Request - Service Request
- PDU Session ID
RRC message N2 message

B S S
- Operation Type: UP activate
- AN parameters - N2 parameters - UE location information
- Service Request - Service Request - Access Type

RAN AMF SMF

7
RRC connection 6 8 5 9
reconfiguration N2 Request N2 Request Ack Nsmf_PDUSession_ Nsmf_PDUSession_ 10
- N2 SM Information - N2 SM Information UpdateSMContext UpdateSMContext N4 Session Modification
- Security context (AN Tunnel Info, Request
Response Request
- AMF Signaling Acceptes QoS
- N2 SM Information - N2 SM information - AN Tunnel Info
Connection Id Flows, Rejected QoS
(PDU Session ID, - RAT Type
Flows)
QFI(s), QoS 11
profile(s), CN n3 N4 Session Modification
Tunnel Info, S-
NSSAI, User Plane Response
RRC Security

G
Enforcement)
NGAP
NAS

e)
UPF
HTTP (Service based)

ur
PFCP

ct
User Plane
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -178
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 178

 5G Core Protocols and
Procedures (eLecture)

Network Triggered Service Request

3GPP Access
4
Namf_Communication_N1N2MessageTransfer
- SUPI
- PDU Session ID
- N2 SM information

S
- ARP
6
Paging
B 5
Paging
S
AMF
- 5QI

SMF
RAN
Namf_EventExposure_Notify (Optional)
7 2
Data Notification
8 - N4 Session ID
UE Triggered
Service Request 3
RRC Data Notification Ack

NGAP

G
NAS 9 1
Downlink data Downlink data
HTTP (Service based)

e)
PFCP UPF

ur
ct
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -179
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 179

 5G Core Protocols and
Procedures (eLecture)

Inter-RAT HO: 5GS to EPS (1/2)

4
Create Session request
6 - Bearer context(s)

B S S
- PGW-U addresses and
Handover request TEIDs for uplink traffic
UL TEID@SGW

E- MME SGW
Handover request Ack Create Session
UTRAN DL TEID@eNB response
- UL TEID@SGW
7
5

3 8

G
2b

S
Relocation request Relocation response
- MME UE context N4 Session Modification
- Target eNB ID PGW-U
- Target TAI PGW-C
PGW-C - Establish CN Tunnel EP for
+UPF
- Serving NW +SMF
+SMF each mapped EPS Bearer
- PGW-U address
- TEID@PGW-U

Handover command 2a
1
- Indication of EBIs to be setup at HO Nsmf_PDUSession_Context

B
Handover required
10 -
-
Target eNB ID
5G Qos Flows indication S Request/Response
- SM Context(s)

e)
- UL TEID@PGW-U
NG AMF

ur
RAN Handover command
- CN tunnel info per

ct
PDU Session

es es
Le
- QoS Flows
9 Control Plane
ur vic
(e
User Plane
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -180
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 180

 5G Core Protocols and
Procedures (eLecture)

Inter-RAT HO: 5GS to EPS (2/2)

14

S S
Modify Bearer request

B 12
Handover Notify
MME
MME
-
-
eNodeB address
DL TEID at eNodeB
SGW 15
E-
E-
11 UTRAN
UTRAN Modify Bearer response Modify Bearer request
- SGW-U address
Handover complete 18 - DL TEID @ SGW
- UL UP Traffic can be sent - Serving network
- TEID @ PGW

17
Modify Bearer
13
Relocation complete
response
S 16
N4 Session Modification
G
PGW-C
PGW-C PGW-U
notification/ack
+SMF
+SMF - DL User Plane Switched to E- +UPF
UTRAN

B S

e)
AMF
NG

ur
RAN Control Plane

ct
User Plane (UL/DL)

es es
Le
User Plane UL
ur vic
(e
User Plane DL
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -181
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 181

 5G Core Protocols and
Procedures (eLecture)

Inter-RAT HO: EPS to 5GS (1/2)

2

S
Handover Required

B -
-
EPS Bearers Indications
Target TAI S
MME SGW
S
E-
UTRAN 5
13
3 Npcf_SMPolicyControl_ PCF +
1 Forward Relocation response
Forward - Serving SW change indication 4 Update PCRF
Handover
- EPS Bearer setup list Nsmf_PDUSession_
initiation Relocation request
- AMF tunnel endpoint ID for CP
- EPS MM Context
- Addresses & TEIDs UpdateSMContext
- Target TAI request
S
- Direct
- UE EPS PDN
Forwarding flag
Connection +
- Serving NW 7 Bearer contexts
- AMF ID PGW-C 6
Nsmf_PDUSession_
UpdateSMContext
+SMF
response N4 Session
- PDU Session ID Modifica0tion
8 - S-NSSAI UL Tunnel Info
Handover Request - N2 SM Info 10
- Source to Target
Transparent Container
Nsmf_PDUSession_
UpdateSMContext
11 G
B S
- N2 SM info
request N4 Session PGW-U
- Handover restriction list Modification
12 - PDU Session ID +UPF
- N2 SM response NG RAN UP Adrress + TEÌD
NG AMF Nsmf_PDUSession_

e)
Handover Request Ack
UpdateSMContext
RAN - Traget to Source

ur
Transparent Container response
- N2 SM Response - PDU Session ID

ct
9
- EPS Bearer Setup list Control Plane

es es
Le
User Plane
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -182
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 182

 5G Core Protocols and
Procedures (eLecture)

Inter-RAT HO: EPS to 5GS (2/2)

B 14
Handover Command
S S
MME SGW
15
Handover Command
E-
UTRAN
21
Npcf_SMPolicyControl_
S
Update
PCF +
- RAT type PCRF
- UE location
18
19
Forward Relocation

S
complete notification Nsmf_PDUSession_
UpdateSMContext
request
- Handover complete PGW-C
indication for PDU +SMF
Session ID

20

G
17
Handover Notify 22 N4 Session
16 - N2 SM info Nsmf_PDUSession_ Modification

B S
Handover Confirm - N3 DL tunnel info UpdateSMContext - N3 DL Tunnel Info PGW-U
response +UPF
- PDU Session ID
NG AMF

e)
RAN

ur
Control Plane

ct
es es
Le
User Plane (UL/DL)
User Plane UL
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -183
(e User Plane DL
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 183

 5G Core Protocols and
Procedures (eLecture)

Handover of PDU Session

3GPP to untrusted non-3GPP (1/2)
3
Nsmf_PDUSession_UpdateSMContext
- SUPI
- S-NSSAI(s)
1 2 - PDU Session ID
PDU Session Establishment Request SMF Selection - AMF ID
- N1 SM Container

Untrusted S S - Access type & RAT type

S
Wi-Fi N3IWF AMF
Namf_Communication_
SMF
IKE_Create_Child_SA N2 PDU Session Request N1N2MessageTransfer
- SA - PDU Session ID - PDU Session ID
- Notify (QFIs, PDU - QoS Profile(s) + associated QFI - N2 SM info
Session ID) - PDU Session Establishment - N1 SM container (PDU
Accept Session Accept) 4
7 6 N4 Session Modification
5 - Packet detection,
enforcement & reporting
rules
- CN tunnel info

e)
G

ur
UPF

ct
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -184
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 184

 5G Core Protocols and
Procedures (eLecture)

Handover of PDU Session

3GPP to untrusted non-3GPP (2/2)

11
Nsmf_PDUSession_UpdateSMContext request
8
PDU Session Establishment Accept S 9
N2 PDU Session Request Ack S - N2 SM Info
S
Untrusted N3IWF AMF SMF
Wi-Fi N2 PDU Session Response
- PDU Session ID
Nsmf_PDUSession_UpdateSMContext response
- N2 SM Info (AN Tunnel info,
Accepted/Rejected QFI(s)) 13

10
12
N4 Session Modification
- AN Tunnel info

e)
ur
UPF

ct
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -185
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 185

 5G Core Protocols and
Procedures (eLecture)

Course Summary

On completion of this course the participants will be able to:

› Explain the basic conceptual network architecture and technology for the 5G Core
› List and explain Identifiers relevant for the 5GC
› List the interfaces and explain the signaling, protocols and service exchange between
the network functions
› Analyze the basic procedures for 5GC

e)
ur
ct
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -186
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 186

 5G Core Protocols and
Procedures (eLecture)

Acronyms & Abbreviations

(R)AN (Radio) Access Network
3GPP 3rd Generation Partnership Project
5G-AN 5G Access Network
5GC 5G Core Network
5G-GUTI 5G Globally Unique Temporary Identifier
5GS 5G System
5G-S-TMSI 5G S-Temporary Mobile Subscription Identifier
5QI 5G QoS Identifier
AF Application Function
AMF Access and Mobility Management Function
ANDSF Access Network Discovery and Selection Function
AS Access Stratum
AUSF Authentication Server Function
CDN Content Delivery Network
CEE Cloud Execution Environment
CN Core Network
COMPA Control Orchestration Management Policy Analytics

e)
CP Control Plane

ur
CPE Customer Premises/Provided Equipment

ct
CUPS CP/UP Split
es es
Le
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -187
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 187

 5G Core Protocols and
Procedures (eLecture)

Acronyms & Abbreviations

DC Dual Connectivity
DCN Dedicated Core Network
DECOR Dedicated Core Network
DL Downlink
DMBB Dedicated MBB
DN Data Network
DNAI DN Access Identifier
DNN Data Network Name
eDECOR enhanced DECOR
EM Element Management
EN-DC E-UTRA-NR Dual Connectivity
EPC Evolved Packet Core
EPS Evolved Packet System
E-UTRA Evolved Universal Terrestrial Radio Access
FQDN Fully Qualified Domain Name
GBR Guaranteed Bit Rate
GFBR Guaranteed Flow Bit Rate
GMLC Gateway Mobile Location Centre

e)
GPSI Generic Public Subscription Identifier

ur
GTP GPRS Tunneling Protocol

ct
es es
Le
GUAMI Globally Unique AMF Identifier
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -188
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 188

 5G Core Protocols and
Procedures (eLecture)

Acronyms & Abbreviations

HOT Heat Orchestration Template
HR Home Routed (roaming)
ICT Information and Communication Technology
IMSI IP Multimedia Subsystem
IMSI International Mobile Subscriber Identity
IMT International Mobile Telecommunications
IoT Internet of Things
IPsec Internet Protocol Security
ITU International Telecommunication Union
LADN Local Area Data Network
LBO Local Break Out (roaming)
LCM Life Cycle Management
LMF Location Management Function
LRF Location Retrieval Function
MANO Management and Orchestration
MBB Mobile BroadBand
MCC Mobile Country Code
MCG Master Cell Group
MFBR Maximum Flow Bit Rate

e)
MICO Mobile Initiated Connection Only

ur
MME Mobility Management Entity

ct
es es
Le
MN Master Node ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -189
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 189

 5G Core Protocols and
Procedures (eLecture)

Acronyms & Abbreviations

MNC Mobile Network Code
MOCN Mobile Operator Core Network
MR-DC Multi-RAT Dual Connectivity
MTC Machine Type Communication
MVNO Mobile Virtual Network Operator
N3IWF Non-3GPP InterWorking Function
NAI Network Access Identifier
NAS Non-Access Stratum
NaaS Network as a service
NE-DC NR-E-UTRA Dual Connectivity
NEF Network Exposure Function
NF Network Function
NFV Network Function Virtualization
NFVI NFV Infrastructure
NGEN-DC NG-RAN E-UTRA-NR Dual Connectivity
NGMN Next Generation Mobile Networks
NR New Radio
NRF Network Repository Function

e)
NSA Non Stand-Alone

ur
NSI ID Network Slice Instance Identifier

ct
NSSAI Network Slice Selection Assistance Information
es es
Le
NSSF Network Slice Selection Function
ur vic
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -190
(e
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 190

 5G Core Protocols and
Procedures (eLecture)

Acronyms & Abbreviations

NSSP Network Slice Selection Policy
NWDAF Network Data Analytics Function
OVF Open Virtualization Format
PCF Policy Control Function
PDU Protocol Data Unit
PEI Permanent Equipment Identifier
PER Packet Error Rate
PFD Packet Flow Description
PPD Paging Policy Differentiation
PPI Paging Policy Indicator
PSA PDU Session Anchor
QFI QoS Flow Identifier
QoE Quality of Experience
RAT Radio Access Technology
RFSP RAT Frequency Selection Priority
RQA Reflective QoS Attribute
RQI Reflective QoS Indication
RRC Radio Resource Control

e)
SA NR Standalone New Radio

ur
SBA Service Based Architecture

ct
SBI Service Based Interface
es es
Le
SCEF Service Capability Exposure Function
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -191
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 191

 5G Core Protocols and
Procedures (eLecture)

Acronyms & Abbreviations

SCG Secondary Cell Group
SD Slice Differentiator
SDF Service Data Flow
SDN Software Defined Networks
SEAF Security Anchor Functionality
SEPP Security Edge Protection Proxy
SMF Session Management Function
SN Secondary Node
S-NSSAI Single Network Slice Selection Assistance Information
SSC Session and Service Continuity
SST Slice/Service Type
SUCI Subscription Concealed Identifier
SUPI Subscription Permanent Identifier
TAU Tracking Area Update
TOSCA Topology and Orchestration Specification for Cloud Application
TTC Time to Customer
TTM Time to Market
UDC User Data Consolidation

e)
UDR Unified Data Repository

ur
UDSF Unstructured Data Storage Function

ct
es es
UL Uplink

Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -192
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 192

 5G Core Protocols and
Procedures (eLecture)

Acronyms & Abbreviations

UL CL Uplink Classifier
URLLC Ultra-Reliable and Low Latency Communications
UPF User Plane Function
URSP UE Route Selection Policy
V2X Vehicle to Anything
VIM Virtualized Infrastructure Manager
VNF Virtualized Network Function
VNFM VNF Manager
YAML Yet Another Markup Language
YANG Yet Another Next Generation

e)
ur
ct
es es
Le
ur vic
(e
© Ericsson AB 2019 | | LZU1082900 R1A | Figure -193
ed er
d rni py
oc S
an ea t co
Pr ng
ol n L no
oc o o
ot ss D
s
Pr Eric
©
e
or
C
5G

© Ericsson AB 2020 | LZU1082900 R1B 193

 5G
C
or ©
e
Pr Eric

© Ericsson AB 2020 | LZU1082900 R1B

ot ss D
oc o o
ol n L no
s
an ea t co
d rni py
Pr ng
oc S
ed er
ur vic
es es
(e
Le
ct
ur
e)

194
5G Core Protocols and
Procedures (eLecture)