5G Case Study
Mohammad Fazel Salimi
[email protected]www.linkedin.com/in/mohammad-fazel-salimi1988
ToC
1. The path to the CNF & Virtualization
2. The path to the Final 5G implementation
3. Network Slicing
4. MEC
prerequisite
The path to the CNF & Virtualization
Telecom Implementtaion’s History
Ref: Apis “Cloud, NFV and SDN” document
VM(NFV) v.s Container
VM VM Container Container
APP
APP
APP
APP
APP
APP
Gust Gust Bins Bins
OS OS Libs Libs
Hypervisor Docker
Host OS Host OS
HW
Assist
Hardware
Hardware
Micro Service Architecture
Monolith Micro Service
Docker and Kubernetes (K8s)
s
er rs
t ai
n
ai ne
n nt
Co Co
rs er
s
ne ers rs
nt
ai ain ne
nt t ai
n ai
Co Co n n t
Co Co
s s
er n er
tai
n t ai Containers
n n
Co Co
5G over Container
Pod (UPF)
Container
Pod (UPF)
Pod (AMF)
Pod (AMF) JVM
Container
Pod Container
(AMF) Pod (UPF)
Container JVM
Container
5G Radio Container
JVM
JVM Service C
JVM JVM
Service C
Service A
Service A Service C
Service A Pod (SMF)
Pod (SMF)
Container
Container
JVM
Pod (SMF)
JVM
Container
Service B
JVM
Service B
Service B
5G in Cloud Native
AMF SMF
Pod (MM
Service)
Pod (MM
Container
Service)
Container
JVMPod (MM Other SMF pods
Service)
JVM
Container
Pod (HTTP Proxy) Pod
Pod (AMF)
Container
(AMF)
Pod (NGAP Proxy) Service B Container Container
JVM Pod (HTTP Proxy) Container
JVM
Pod
Pod (AMF)
Container
(AMF) Service B JVM JVM
Container
PodContainer
(HTTP Proxy) JVM
5G Radio Container
JVM Service B JVM
Container Service A
JVM Service C Service A
JVM JVM Service A
Service A Service C
Service
Service AA Service C
Pod (SM Service) Pod (HTTPP Proxy)
Pod (SM Service)
Container PodContainer
(HTTPP Proxy)
Container
Pod
JVM(SM Service) JVM
PodContainer
(HTTPP Proxy)
JVM
Container JVM
Container
Service B Service C
JVM JVM
Service B Service C
Service B Service C
Service Mesh (Istio)
Pod Pod
Container Container
JVM JVM
Service NGAP Proxy Service HTTP Proxy
The sidecar (Envoy) intercepts all network traffic
Sidecar Container Sidecar Container
Pod
Sidecar Container
Container
JVM
Service SM
Service Mesh (Istio)
Data Pod Pod Pod
Plane Container Container Container
JVM JVM JVM
HTTP1.1, HTTP2, Service A HTTP1.1, HTTP2, Service B HTTP1.1, HTTP2, Service C
gRPC, TCP w/TLS gRPC, TCP w/TLS gRPC, TCP w/TLS
Envoy Sidecar Envoy Sidecar Envoy Sidecar
Control Mixer
Plane Galley Pilot (telemetry, policy)
Citadel
API, config mTLS, SPIFFE
Service Mesh Ecosystem
Ref: Red Hat OpenShift Meetup - Tokyo, October 2019, Maria Bracho.
3GPP Rel16: Service Communication Proxy
End to End Cloud Native Network
Ref: Cisco “Reimagining the End-to-End Mobile Network in the 5G Era”
The path to the Final 5G implementation
Overview of SA and NSA Options
Ref: GSMA “Road to 5G Introduction”
Actual Path
Ref: Cisco “Mapping Success, Evolving to software-defined mobile networks”
Network Slicing
ITU IMT 2020 Use cases/Requirement
Peak data Rate, User experienced data rate. Area traffic capacity, user plane
latency, control plane latency, Mobility, Mobility interruption time
Connection
Density User plane latency, Control plane latency, Reliability,
Mobility interruption time
Minimum Technical Performance Requirement (1/2)
Ref: S01-1_Requirements for IMT-2020_Rev
Minimum Technical Performance Requirement (2/2)
Ref: S01-1_Requirements for IMT-2020_Rev
Network Slicing for eMBB
• UEs in Vehicles! • Coverage everywhere -Microcells • High capacity in UPFs and transport NW
• Smartphones etc • High capacity –Small cells • Use of multiple Session Anchors (UPFs)
• 100 000’s UEs per km2 • Carrier Aggregation, Dual Connectivity • Use of Multi-Access Edge Computing (MEC )
• 1000’s Gb/s per km2 • Massive MIMO, Beamforming
• High peak rates • Tight interworking with E-UTRA
• Normal mobility • Use of unlicensed spectrum
-except FWA • Aggregation with WiFi
Ref: Apis “Core Architecture” Traning document
S-NSSAI: Single-Network Slice Selection Instance Identifier
8 bits 24 bits
SST: Slice/service type SD: Slice differentiator
• It is MNO(owned by MNO) or MVNO subscriber?
eMBB • In case of MNO, It is B2C or B2B segment?
URLLC • It is local subscriber or outbound roamer?
• For B2C (or oven B2B), what is the subscriber type? Gold? Silver?
mMTC
Normal?
V2X • Which kind of services/use cases we are going to provide?
• Some B2B customers need more than 1 DNN? What should be
strategy?
To provide same slice for all of DNNs of this customer?
To provide different slice for each DNN of this customer
To provide different slices for different service of this customer
instead of taking care about DNNs. Because 1 DNN an have multiple
use case with different QOS attributes.
Common and Specific NF(Network Functions) for each Slice
?
MEC (Multi access Edge Computing)
MEC
MEC Deployments
Thank You
