5G_SA

1 © 2019 Nokia
5G KT Testing BU
Intro to 5G SA, SBA, and 5G call flows
CNS-Testing
2 © 2019 Nokia
Introduction to 5G
Why 5G ?
 The promise of 5G
 5G Use case
 Deployment Options
5G Core Basics
 5G Service-Based Architecture (5G SBA)
 5G Network elements and Functionality
 Network Slicing
 5G QoS
 5G basic call flow
3 © 2019 Nokia
The Promise of 5G: Use Case and Trends
Reference: Nokia.com/5g
4 © 2019 Nokia
Promise of 5G: Target Applications and Use Cases per Category
Reference: 5G Services and Use Cases, 5G Americas Nov 2017

5 © 2019 Nokia
Promise of 5G: 5G as the Driver Powering the 4th “Industrial”
revolution
Reference: Connecting people and things in the connected world, Nokia White paper
6 © 2019 Nokia
5G targets and Use Cases as defined in ITU - IMT 2020
extreme Mobile BroadBand (eMBB):

• Higher data rates and better coverage.
• Faster communication and better quality multimedia
massive Machine-Type Communication

(mMTC):
• Support a very large number of devices (low cost,
long battery based sensors) in a small area.
• Typical applications fall under IoT based deployments
Ultra-Reliable Low-Latency Communications

(URLLC):
• Very strict requirements on latency and reliability
• Will be used for mission-critical applications.
Reference: Building a cloud-native core for a 5G world, Nokia White Paper

7 © 2019 Nokia
5G Technology – Key Components

8 © 2019 Nokia
5G Standards Development
9 © 2019 Nokia
5G Standards Roadmap
Current 4G deployments
Use-case specific 5G Standards developm

Reference: Scaling up with 5G, Nokia 5G eBook
10 © 2019 Nokia
Key 3GPP standards References for 5G Core
TS 23.501 – 5G System (5GS) Architecture

TS 23.502 – 5GS Call Flows
TS 23.503 – Policy and Charging Control for the 5GS
TS 29.5xx - SBA API Definitions for each SBA Interface

TS 33.5xx – Security aspects in 5GS
Reference: Specifications list at 3GPP: https://www.3gpp.org/dynareport/SpecList.htm?release=Rel-15&tech=4

11 © 2019 Nokia
5G Deployment Options
12 © 2019 Nokia
5G Deployment Options
Standalone (SA) and non-standalone (NSA)
Option 1 | SA LTE with EPC Option 2 | SA NR with 5GC Option 5 | SA eLTE with 5GC
EPC 5GC 5GC
Y
DA
TO
LTE NR eLTE
Option 3 | NSA LTE+NR with Option 4 | NSA NR+LTE with Option 7 | NSA eLTE+NR with
EPC 5GC 5GC
EPC 5GC 5GC
LTE NR NR eLTE eLTE N

S1 - MME N2 (CP) X2-C Xn-C R
S1 - U N3 (UP) X2-U Xn-U
Reference: : MG Core Basics, NAM 5G Workshop, Igor Giangrossi
13 © 2019 Nokia
14 © 2019 Nokia
15 © 2019 Nokia
Nokia Portfolio
5G
Core
Reference: Nokia.com/5g
16 © 2019 Nokia
Introduction to 5G
Why 5G ?
 The promise of 5G
 5G Standards development
 Deployment Options
5G Core Basics
 5G Service-Based Architecture (5G SBA)
 5G Network elements and Functionality
 Network Slicing
 5G QoS
17 © 2019 Nokia
Path to 5G: Evolving the 4G Core Architecture to CUPS 4G Core
Control User Plane Separation (CUPS) benefits
Traditional Architecture CUPS Architecture

HSS PCRF OCS HSS PCRF OCS
MME MME S/PGW-C
eNB S/PGW Internet eNB S/PGW-U Internet
Scales control and Lower integration Provides optimal Provides reduced

user planes costs to other EPC routing paths latency and better
independently functions QoS
Reference: MG Core Basics, NAM 5G Workshop, Igor Giangrossi

18 © 2019 Nokia
5G System Architecture
An open, cloud-native design
 Service Based Architecture Common Data Layer UDSF UDR
for all Control Plane Network
Functions (NFs): Protocol
uniformity between network
elements on SBA bus based Control Plane
AUSF CHF SMSF
3rd Party
on HTTP2 Apps
UDM PCF NEF
 GTP protocol on Access side SBA Bus
for Data plane SEPP Roaming

Partners
 Network Slicing AMF SMF NRF NSSF AF
 New QoS model based on

QoS Flows
UE gNB UPF UPF DN
User Plane
Reference: MG Core Basics, NAM 5G Workshop, Igor Giangrossi DN

19 © 2019 Nokia
5G System Architecture
Interface name representation
CHF
N28 N40
Reference: TS 23.501, 3GPP.org

20 © 2019 Nokia
5G Service Based Architecture
21 © 2019 Nokia
Service Based Architecture
Cloud friendly producer/consumer model
UDSF UDR
Based on HTTP/2 with JSON objects, using

a RESTful API (no more Diameter)
AUSF SMSF
UDM PCF NEF

Each NF publishes its own capabilities (API),
and any other NF can consume them SBA Bus
AMF SMF NRF NSSF AF
Enables reusability and flexibility, bringing

openness to the 5G Core AMF: Access & Mobility Mgmt.
Function
UDM: Unified Data Management
SMSF: SMS Function
SMF: Session Management Function PCF: Policy Control Function
NRF: NF Repository Function NEF: Network Exposure Function
NSSF: Network Slice Selection UDR: Unified Data Repository
Function UDSF: Unstructured Data Storage
AF: Application Function Function
AUSF: Authentication Server
22 © 2019 Nokia Function
Interaction models and functionalities
Consumer Producer
API Functionalities:
Service Registration and De-
Request registration: to make the NRF aware of
the available NF instances and supported
Response
services
Consumer Producer Service Discovery: to enable a NF Service

Subscribe Consumer to discover NF Service Producer
instance(s) which provide the expected NF
Notify service(s)
Service Authorization: to ensure the NF

Consumer Producer Consumer Service Consumer is authorized to access the
Subscribe NF service provided by the NF Service
Producer
Notify

23 © 2019 Nokia
5G Interface reference names
Network Functions (NF) on

the SBA bus interact with
other (NFs) via HTTP2
protocol.
Interface associated with
a particular NF is defined
via the convention shows
here
Example: Interface
associated with NRF is
named as Nnrf
The Numbered interfaces

are used on the data
plane, i.e., RAN-SGI
Reference: TS 23.501, 3gpp.org (5G System Architecture)
24 © 2019 Nokia
HTTP/2 Details
HTTP/2 was released in 2015 as a major UDSF UDR

revision to the HTTP/1.1 protocol. It was
derived from the SPDY protocol as a way to NUDSF NUDR
improve the online experience by speeding
up page loads and reducing round-trip time CHF AUSF SMSF UDM PCF NEF
(RTT), especially on resource-heavy web

pages. NCHF NAUSF NSMSF NUDM NPCF NNEF
SBA Bus NAMF NSMF NNRF NNSSF
The following HTTP methods are supported:

GET / POST / PUT / PATCH / DELETE AMF SMF NRF NSSF AF
AMF: Access & Mobility Mgmt.

Function UDM: Unified Data Management
SMF: Session Management Function SMSF: SMS Function
NRF: NF Repository Function PCF: Policy Control Function
NSSF: Network Slice Selection NEF: Network Exposure Function
Function UDR: Unified Data Repository
AF: Application Function UDSF: Unstructured Data Storage
AUSF: Authentication Server Function
Function
25 © 2019 Nokia CHF: Charging Function
5G SBA Protocol Stack
The service based interfaces use HTTP/2

protocol with JSON as the application layer
protocol
For the security protection at the transport

layer, all 3GPP NFs shall support TLS and
TLS shall be used within a PLMN if network
security is not provided by other means
TLS support in CMG (SMF-UPF), NRD (NRF-

NSSF) targeted for 11.0.Nov
Reference: TS 29.500, 3gpp.org (SBA Architecture)

26 © 2019 Nokia
5G Network Functions
27 © 2019 Nokia
28 © 2019 Nokia
AMF: Access and Mobility Management Function
Responsible for all mobility management tasks
PCF AUSF UDM NRF
Handles Registration, Connection,

Reachability and Mobility Management;
relays Session Management messages to SBA Bus
SMF
AMF SMF
Performs UE Authentication (via AUSF) and
N1 N4
Authorization, interacts with NSSF to validate N2
slicing permissions N3 N6
UE gNB UPF DN
Delivers SMS over NAS (from SMSF), interacts

with Location Function (LMF), provides UE
mobility notifications UE: User Equipment AUSF: Authentication Server
AMF: Access & Mobility Mgmt. Function
SMF: Session Management Function DN: Data Network
UPF: User Plane Function SBA: Service Based Architecture
29 © 2019 Nokia
SMF: Session Management Function
Responsible for all session management tasks
PCF AUSF UDM NRF
Handles establishment, modification and

release of PDU sessions. Interacts with the
access network via the AMF SBA Bus
Performs UPF selection (via NRF) and control AMF SMF
(via N4). Handles IP address management, N1

N2
N4
including DHCP, and ARP/ND for Ethernet

N3 N6
PDUs (via proxy on UPF)
UE gNB UPF DN
Interfaces with the Charging and Policy

functions. Determines the SSC mode of a
PDU session
UE: User Equipment AUSF: Authentication Server
30 © 2019 Nokia
UPF: User Plane Function
Responsible for all user plane forwarding tasks
PCF AUSF UDM NRF
Performs all user plane functions on the

packets: forwarding, routing, marking,
QoS, inspection, etc. SBA Bus
AMF SMF
Enforces policies received from the PCF (via
N1 N4
SMF). Sends traffic usage reporting to the N2
SMF for charging. N3 N6
UE gNB UPF DN
Connects to external networks (N6) or other

UPF in a daisy chain configuration (N9)
31 © 2019 Nokia
UDM: Unified Data Management Function
Responsible for subscriber management
PCF AUSF UDM NRF
UDM plays the role equivalent to HSS form

4G
The Initial Registration procedure involves SBA Bus
execution of Network Access Control

functions, i.e., user authentication and AMF SMF
access authorization based on subscription N1 N4
N2
profiles in UDM.
N3 N6
gNB
As result of the Registration procedure, the UE UPF DN
identifier of the serving AMF through which

the UE has registered will be registered in
UDM.
32 © 2019 Nokia
PCF: Policy Control Function
Responsible for policy management
PCF AUSF UDM NRF
PCF plays the role equivalent to PCRF form

4G
SBA Bus
Supports unified policy framework to

govern network behaviour and provides AMF SMF
policy rules information to the SMF N1 N4
N2
N3 N6
UE gNB UPF DN
Accesses subscription information relevant
for policy decisions in a Unified Data
Repository (UDR)
33 © 2019 Nokia
CHF: Charging Function
Responsible for Billing
PCF CHF UDM NRF
The interactions between SMF and CHF

enable online and offline charging.
SBA Bus
N40 reference point resides between the

SMF and CHF for charging. AMF SMF
N1 N4
N2
N3 N6
Interacts with PCF over the N28 interface UE gNB UPF DN

with Nchf_spending limit support service
enabling the PCF to access policy counter
status information relating to subscribers’
spending from CHF UE: User Equipment AUSF: Authentication Server
Reference: TS 23.503, 3gpp.org (Policy and Charging Control Framework)
34 © 2019 Nokia
N3IWF: Non-3GPP Interworking Function
Unified architecture for any access type
AUSF UDM
Common set of interfaces for UEs and
Access Nodes to access the 5G Core.
Common framework for Registration,
SBA Bus
Connection and Session Management
Current release targets untrusted access via AMF SMF
IPSec only (similar to ePDG/VoWiFi in LTE).

Release 16 will add trusted access via N1 N2
collaboration with BBF N3
gNB UPF DN
IP, Ethernet and Unstructured PDU types

UE N2
provide the flexibility needed for multiple
N3
access technologies
WLAN N3IWF

35 © 2019 Nokia
NRF: Intelligent Resource Discovery and Selection
Policy driven function selection for optimal performance
NRF NSSF AUSF UDM
Maintains the NF profile of available NF

instances and their supported services,
and provides NF discovery and selection SBA Bus
AMF SMF1 SMF2

Selection criteria can include location
N4 N4
(latency), load, Data Network Name
(application), access network type, slice, etc. N6
UE gNB UPF1 DN
N9 N6
Provides much more granular policies and UPF2 UPF3

dynamic capabilities when compared to DNS
selection
MEC

36 © 2019 Nokia
Common Data Layer
Shared storage for state efficient processing
UDSF UDR
UDSF can store data from any Network

Function in the 5G Core (unstructured
data)
AUSF SMSF
UDR can store policy data from the PCF, UDM PCF NEF
subscriber data from the UDM, and exposure SBA Bus
data from the NEF
AMF SMF NRF NSSF AF
This architectures allows stateless functions,

providing more robustness by decoupling AMF: Access & Mobility Mgmt.
Function
SMSF: SMS Function
compute and storage SMF: Session Management Function
NRF: NF Repository Function
NEF: Network Exposure Function
Reference: MG Core Basics, NAM 5G Workshop, Igor Giangrossi AUSF: Authentication Server
Network Capabilities Exposure
Allows external applications access to the 5G Core
UDSF UDR
Exposes 5G Core capabilities and events to

external applications. Uses the UDR as its
data source
AUSF SMSF
3rd Party
Apps
UDM PCF NEF
Allows 3rd parties to securely provision
information to the 5G Core (e.g. Expected UE SBA Bus
Behavior)
AMF SMF NRF NSSF AF
Handles masking of sensitive network

information to external parties AMF: Access & Mobility Mgmt.
Function
SMSF: SMS Function
SMF: Session Management Function PCF: Policy Control Function
NRF: NF Repository Function NEF: Network Exposure Function
SEPP: Roaming Interconnection via an HTTP Proxy
Simplifies and secures the control plane
UDSF UDR
The Security Edge Protection Proxy

interconnects the control plane in roaming
agreements
AUSF SMSF
UDM PCF NEF

Provides message filtering and topology
hiding between domains SBA Bus
SEPP Roamin
g
Partner
s
AMF SMF NRF NSSF AF
Implemented by an HTTP proxy to control

which APIs and values are accessible from AMF: Access & Mobility Mgmt.
Function
SMSF: SMS Function
other PLMNs SMF: Session Management Function
NRF: NF Repository Function
NEF: Network Exposure Function
NRF/NSSF
The NRF supports the following functionality:
• NF registration in the NRF
• NF availability monitoring based on NF heartbeats
• registration data updates from NFs
• NF profile maintenance of available NF instances and their supported services
• NF and service discovery
• NF status change notifications
To support these functions, the NRF provides the following services:
• NF management service – Nnrf_NFManagement
• NF discovery service – Nnrf_NFDiscovery
The NSSF provides the following functionality:

• slice selection during UE registration
• NRF selection during PDU session establishment
Both of these functions are performed using the Get NSSF slice selection service
operation. The NF for these functions is always the AMF.
Reference: NRD_NRF_NSSF_Guide_R11.0.R1
40 © 2019 Nokia
5G Network Slicing
41 © 2019 Nokia
Network Slicing Capabilities
Enables “Network-as-a-Service” model
NSSF
Network Slicing provides the ability to

deploy control and user plane functions for
SBA Bus
a group of UEs, independent of the access
type
AMF SMF SMF
An UE can connect to up to 8 slices
simultaneously. The AMF must be common to
all slices serving a UE. Network functions can
UPF DN
be shared or dedicated to each slice
UE gNB
The NSSF selects during the registration UPF DN

procedure which slices the UE can connect,
and the AMF that can serve the UE. AMF
redirection might occur

42 © 2019 Nokia
5G Network Slicing for “Network as a Service” via NSSF
Requires a dynamic, flexible transport network
SMF
SBA Bus
NSMF N4
NNSSF NAMF
N6
SMF
UPF DN
NSSF AMF N4
N2
N6
SMF
UPF DN
N4
N3
gNB SMF N6
UPF DN
N4
N6
UPF DN
43 © 2019 Nokia
Network Slice Identification and Selection
S-NSSAI Single NSSAI
An S-NSSAI (Single Network Slice Selection Assistance

information) identifies a Network Slice.
An S-NSSAI is comprised of:

MBB Slice MN
A Slice/Service type (SST), which refers to the expected O
NSSAI
Network Slice behaviour in terms of features and services
S- SST# SD#
NSSAI#1 1 A
A Slice Differentiator (SD). which is optional information S- SST# SD# ENTERPRISE
uRLLC Slice
that complements the Slice/Service type(s) to allow further NSSAI#2 2 B B
S- SST# SD#
differentiation for selecting an Network Slice instance from the NSSAI#3 2 C
potentially multiple Network Slice instances that all comply
with the indicated Slice/Service type. S-
NSSAI#8 IoT Slice ENTERPRISE
C
NSSAI NW Slice Selection Assistance Information
The NSSAI is a collection of S-NSSAIs (Single Network Slice

Selection Assistance Information).
Reference: NRF-NSSF Overview, NAM 5G Workshop, Eckhard Papproth

44 © 2019 Nokia
Network Slice Identification and Selection
TS 23.501 Table 5.15.2.2-1 - Standardised SST values

Slice/
SST
Service Characteristics.
value
type
eMBB 1 Slice suitable for the handling of 5G eMBB
URLLC 2 Slice suitable for the handling of URLLC
MIoT 3 Slice suitable for the handling of massive IoT.
• The S-NSSAI may include both the Slice Service/Type (SST) and Slice Differentiator (SD)
fields (in which case the S-NSSAI length is 32 bits in total), or the S-NSSAI may just
include the SST field (in which case the S-NSSAI length is 8 bits only).
• The SST field may have standardized and non-standardized values. Values 0 to 127
belong to the standardized SST range and they are defined in TS 23.501. Values 128 to
255 belong to the Operator-specific range.
• SD is operator defined only.
• A NSSAI is a set of S-NSSAIs
Reference: NRF-NSSF Overview, NAM 5G Workshop, Eckhard Papproth

45 © 2019 Nokia
Simplified Network Slice Selection Flow
Step-by-step UE registration to network slice
1. UE receives NSSAI configuration for the PLMN
2. UE sends registration request to the RAN with
desired S-NSSAI NRF NSSF AUSF UDM
3. RAN sends registration request to default AMF, or

to previously connected AMF if available 5 4
4. AMF queries UDM for UE subscriptions, including S- SBA Bus
NSSAIs
5. AMF queries the NSSF for allowed and rejected S-
NSSAIs. NSSF can also return the NSF and AMF to 6 AMF SMF
serve the slice(s)
6. AMF determines a Registration Area and sends 3
back to UE the allowed and rejected S-NSSAIs 1
UE 2 gNB UPF DN
After that, UE initiates a PDU Session establishment

procedure to the selected AMF, for a given S-NSSAI
and DNN. AMF uses the NRF received from the NSSF
to select the appropriate SMF to serve that request.
Standard PDU Session setup follows.
46 © 2019 Nokia
5G QoS
47 © 2019 Nokia
5GS QoS Model
EPC QoS model vs 5GS QoS Model
UE LTE RAN EPC
EPS Bearer #1
5G UE NG-RAN 5GC
DRB#1 N3 Tunnel
QFI-A
QoS
All 3 Services receive same QoS treatment Flows QFI-B
since mapped to a common QCI Bearer QFI-C
DRB#2
UE LTE RAN EPC 5G has no concept of bearers but instead introduces QoS
Flows. All traffic in the same QoS Flow receives the same
EPS Bearer #1 QoS treatment.
EPS Bearer #2 QoS Flows are created dynamically without the need for
e2e signaling
EPS Bearer #3 Short lived flows can receive differentiated QoS
treatment without the overhead of establishing EPS
bearers
QoS Differentiation requires separate
bearers be established with different QCI’s – Rather than a default Bearer 5GS works with a default
brings signaling overhead QoS Flow.
Reference: CMG 5G - SMF-UPF, NAM 5G Workshop, Jan Vandenhoudt

48 © 2019 Nokia
5G Flow-Based QoS Model
5G QoS Identifier (5QI) used to determine QoS characteristics of a flow (resource type,
priority, delay, loss, etc.), i.e., equivalent to QCI in 4G-EPC.
QoS Flow Identifier (QFI) uniquely identifies the QoS profile within a PDU session. It is
signaled by the SMF and spans UE, AN (radio), and UPF
Reflective QoS:
• The 5G QoS model also supports reflective QoS, which achieved by creating a derived
QoS rule in the UE based on the received downlink traffic based on RQI (Reflective QoS
Indicator)
• For traffic that is subject to reflective QoS, the UL packet gets the same QoS marking
as the reflected DL packet
• Targeted to be supported in 11.0.Nov
Reference: 23.501, 3gpp.org (%G System Architecture)

49 © 2019 Nokia
5G Basic Call Flow
50 © 2019 Nokia
Basic 5G Construct: PDU Session
Connects a UE to a data network
AUSF UDM
Each PDU session has a specific Data
Network Name, IP address, QoS, mobility
mode (SSC), charging characteristics, Policy,
and an exclusive ID. SBA Bus
N1
AMF SMF
There are 5 PDU Session types: IPv4, IPv6,
IPv4v6, Ethernet and Unstructured. PDU Session
UE gNB UPF DN
Established, modified and released via

NAS signaling (N1) between the UE and
SMF (relayed by the AMF).
51 © 2019 Nokia
Basic 5G call flow
52 © 2019 Nokia
Basic 5G call flow
53 © 2019 Nokia
Basic 5G call flow
54 © 2019 Nokia
5G PDU Establishment
55 © 2019 Nokia
56 © 2019 Nokia
57 © 2019 Nokia
58 © 2019 Nokia
5G Terminology
Identifier Description
SUPI Subscription Permanent Identifier

IMSI as defined in 23.003. Other forms are allowed but phase 1 will use IMSI.
SUCI Subscription Concealed Identifier
The Subscription Concealed Identifier (SUCI) is a privacy preserving identifier containing the
concealed SUPI. It is specified in TS 33.501 [29].
DNN Data Network Name
DNN is same as APN defined in 23.003.

59 © 2019 Nokia

5G_SA

Uploaded by

Copyright:

Available Formats

5G_SA

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

5G_SA

Uploaded by

Copyright:

Available Formats

1 © 2019 Nokia

Reference: 5G Services and Use Cases, 5G Americas Nov 2017

extreme Mobile BroadBand (eMBB):

massive Machine-Type Communication

Ultra-Reliable Low-Latency Communications

Reference: Building a cloud-native core for a 5G world, Nokia White Paper

Reference: Building a cloud-native core for a 5G world, Nokia White Paper

Use-case specific 5G Standards developm

TS 23.501 – 5G System (5GS) Architecture

TS 29.5xx - SBA API Definitions for each SBA Interface

Reference: Specifications list at 3GPP: https://www.3gpp.org/dynareport/SpecList.htm?release=Rel-15&tech=4

EPC 5GC 5GC

LTE NR NR eLTE eLTE N

Traditional Architecture CUPS Architecture

MME MME S/PGW-C

eNB S/PGW Internet eNB S/PGW-U Internet

Scales control and Lower integration Provides optimal Provides reduced

Reference: MG Core Basics, NAM 5G Workshop, Igor Giangrossi

for Data plane SEPP Roaming

 Network Slicing AMF SMF NRF NSSF AF

 New QoS model based on

Reference: MG Core Basics, NAM 5G Workshop, Igor Giangrossi DN

Reference: TS 23.501, 3GPP.org

Based on HTTP/2 with JSON objects, using

UDM PCF NEF

AMF SMF NRF NSSF AF

Enables reusability and flexibility, bringing

Consumer Producer Service Discovery: to enable a NF Service

Service Authorization: to ensure the NF

Reference: MG Core Basics, NAM 5G Workshop, Igor Giangrossi

Network Functions (NF) on

The Numbered interfaces

HTTP/2 was released in 2015 as a major UDSF UDR

(RTT), especially on resource-heavy web

SBA Bus NAMF NSMF NNRF NNSSF

The following HTTP methods are supported:

AMF: Access & Mobility Mgmt.

The service based interfaces use HTTP/2

For the security protection at the transport

TLS support in CMG (SMF-UPF), NRD (NRF-

Reference: TS 29.500, 3gpp.org (SBA Architecture)

PCF AUSF UDM NRF

Handles Registration, Connection,

Delivers SMS over NAS (from SMSF), interacts

PCF AUSF UDM NRF

Handles establishment, modification and

Performs UPF selection (via NRF) and control AMF SMF

(via N4). Handles IP address management, N1

including DHCP, and ARP/ND for Ethernet

Interfaces with the Charging and Policy

PCF AUSF UDM NRF

Performs all user plane functions on the

SMF for charging. N3 N6

Connects to external networks (N6) or other

PCF AUSF UDM NRF

UDM plays the role equivalent to HSS form

execution of Network Access Control

identifier of the serving AMF through which

PCF AUSF UDM NRF

PCF plays the role equivalent to PCRF form