5G Service Based
Architecture and Signaling
Understanding with Practical Demonstration
Course Agenda
• Topic 1: 5G Basic Introduction
• Topic 2: 5G Network architecture
• Topic 3: 5G Protocol
• Topic 4: Service based interface
• Topic 5: High Level Call Flow Using Lab
TOPIC 1: 5G BASIC INTRODUCTION
Introduction to the course
5G enablers technology
Where we are today?
Release 16 study items
Release 17 study items
WHERE WE ARE TODAY
• At the TSG#88e Plenary meetings - ending July 3, 2020 - Release 16 was
completed with both the Stage 3 freeze and ASN
RELEASE 16
• Work has progressed on around 25
Release 16 studies, on a variety of topics:
• Multimedia Priority Service,
• Vehicle-to-everything (V2X) application layer
services,
• 5G satellite access,
• Local Area Network support in 5G,
• wireless and wireline convergence for 5G,
• Terminal positioning and location,
• communications in vertical domains and
network automation
• 5GS enablers for new verticals like: Industrial
Automation inc. Time Sensitive
Communication (TSC), NPNs, CIoT support
for 5GS, V2X
UPCOMING RELEASE 17
TOPIC 2: 5G NETWORK ARCHITECTURE
5G Architecture Framework
5GS in reference point representation
5GS in Service Based Interface representation
Various Network Functions of 5GS
5G ARCHITECTURE FRAMEWORK
• 5G Architecture consist of 5G Core and 5G
Access Network (AN)
• Unlike pervious 3GPP technologies – 5G Core
is compliant , proficient to work seamlessly
with more than one access technology
• The possibility of E-UTRA & NR connecting to 5GC
creates several connectivity scenarios which have
listed and studied in TR23.799
5GS ARCHITECTURE IN REFERENCE POINT REPRESENTATION
TOPIC 3: 5G PROTOCOL
5G User plane protocol stack
5G Control plane protocol stack
SBI Protocol stack
Introduction to HTTP/2 for SBI
5G USER PLANE PROTOCOL STACK
5G CONTROL PLANE PROTOCOL STACK
SBI PROTOCOL STACK
APIs
(Application
programming
interface)
- JSON as the application layer
serialization protocol
Traditional layers
TOPIC 4: SERVICE BASED INTERFACE
Service framework
Service and service operation example
Service API - example
SERVICE FRAMEWORK
Discovery component - A service
consumer queries for a specific service in Registration component -
the service registry. Implemented based on a service
registry which is a database of available
(currently active)
Registration services and their reachability.
Discovery
Authorization
Authorization component - The authorization of a service is
required in order to control if a service can be called by other
services. This component is really necessary when (alien)
third party services are using native services of the network
INTERACTION
• Interaction between network functions / services follows two basic mechanism:
• Request – Response
• Subscribe-Notify
e.g. during registration
process AMF requests
Subscriber profile from UDM
e.g. AMF subscribes to SMF
Subscription service (notify
me access type change)
EXAMPLE – NETWORK FUNCTION AMF
SERVICE AND SERVICE OPERATION EXAMPLE
Service : Namf_communication Target is to enable other NF ( e.g. SMF) to communicate
with the UE and/or the gNB
Service operation : N1 N2 message transfer
(e.g. PDU session establishment)
AMF SMF
1. Http method post
N1 N2 message transfer req data
2. Success 3. 200 Ok
( N1 N2 message transfer)
N1 N2 message transfer resp data
( N1 N2 transfer initiated)
SBA OF 5G CORE NETWORK
“Service-based”
interface
Reference Point Interfaces
SERVICE API - EXAMPLE
Service : Namf_communication Target is to enable other NF ( e.g. SMF) to communicate
with the UE and/or the gNB
Service operation : N1 N2 message transfer
(e.g. PDU session establishment)
Resource URI structure //{apiRoot}/namf_comm/v1
/ ue-contexts
/ {ue-contextid} SUPI (IMSI)
HTTP method : POST
/ n1-n2-messages
Comply with OpenAPI
specs Data structure in
POST rest body
N1N2 message transfer req. data
NRF & NPF
• In order to facilitate 5G Service based architecture , additional network functions
are required:
NEF is a kind of network NRF is a kind of that
function which enables app Information desk which
function to get more works on the consumer
information for better services requirement and match
them with the producer
TOPIC 5 CALL FLOW