Massive IoT EPC Overview VNPT NET2 IoT and 5G Workshop Ha Nguyen H 2018 12 12 Agenda ▪ IoT ▪ Overview of IoT Architecture ▪ Ericsson Solution for IoT ▪ 5G ▪ 5G Architecture and Standardization ▪ Erics.
Trang 1VNPT NET2 IoT and 5G
Workshop
Ha Nguyen H
2018-12-12
Trang 2Agenda
Trang 3Agenda
Trang 4Massive IoT EPC Overview | Ericsson Internal | 27/221 09-FGB 101 256 Uen, Rev D | 2018-04-16
>0.9 billion are Massive IoT connections
$200 billion
in revenue by 2025
New use cases
New business model
Source: Ericsson and Analysys Mason
Cellular IoT market outlook
Trang 5Massive IoT EPC Overview | Ericsson Internal | 27/221 09-FGB 101 256 Uen, Rev D | 2018-04-16
Massive IoT
Low-bitrate applications with extreme coverage and low cost devices
NB-IoT
Wider range of applications with low-medium bitrate, mobility and voice support
Cellular for Massive IoT
Meeting diversity of use case requirements
Trang 6Massive IoT EPC Overview | Ericsson Internal | 27/221 09-FGB 101 256 Uen, Rev D | 2018-04-16
Technology characteristics
Coverage Battery life ThroughputPeak Mobility
164dB (+20dB) 10+ Year
473/473 kbps (97/97 kbps)
160dB (+15dB) 10+ Year
0.8/1 Mbps (300/375 kbps) Connected & idle mode mobility
164dB (+20dB) 10+ Year
227/250 kbps (21/63 kbps) Idle mode mobility
Trang 7Cellular IoT Module Cost
Trang 8Massive IoT Architecture & Approaches
Trang 9Commercial in confidence | © Ericsson AB 2014 | 2015-12-14 | Page 9
Device trigger over SGd
Trang 10Massive IoT EPC Overview | Ericsson Internal | 27/221 09-FGB 101 256 Uen, Rev D | 2018-04-16
PtP IP tunnel for non-IP data
S1-MME (NAS (encrypted
• Attach procedure changes
• Data over NAS
• CN selection procedures
• UP/RRC Resume
Standalone function including:
• Ability for the external entities (partners) to discover the exposed service capabilities
• Authentication and Authorization
• Non-IP Data Delivery
• Policy enforcement towards AS
SGd or SGs over MSC/SMS-IWF
Trang 11Massive IoT EPC Overview | Ericsson Internal | 27/221 09-FGB 101 256 Uen, Rev D | 2018-04-16
Ericsson Target Architecture – Massive IoT
Commercial in confidence | © Ericsson AB 2018
PDN Type “Non-IP” PDN Type “IPv4/IPv6”
T8 T8’ Extension
Local operator Apps &
ecosystem
IoT-A
SGi PtP tunnelling using UDP/IP
Trang 12Ericsson Internal | 2018-02-21
Why a Service Capability Exposure Function?
Limited control by operator on the traffic generated by and towards M2M devices (threat of congestion!)
Control over the M2M traffic generated by partners/customers (e.g Authentication, Authorization, Throttling)
No communication between network and AS Network informs SCEF about the location, reachability, status,
etc., SCEF informs ASComplex communication and protocols Easy to integrate for partners/customer applications by means of
RESTful interface, short TTM for application developers, no need
to understand network complexity Add new RESTful interfaces
Only single point-to-point connection between device and
No added value by operator apart from being a bitpipe Offering additional functionality in order to become part of the
value chain (e.g monitoring, high latency comm., ID/IMSI mapping, grouping, etc.)
Mobile Network
M2M
AS
AS
Trang 13Massive IoT EPC Overview | Ericsson Internal | 27/221 09-FGB 101 256 Uen, Rev D | 2018-04-16
Massive IoT Core
Main operator choices
Use case 1 & 2
1 EPC Native HW
(combined MBB & IoT Core)
– SW upgrade to SGSN-MME 1 & EPG 1 – Build on installed Ericsson Core
– Start Massive IoT launch before EPC virtualization and slicing
2 vEPC MBB VNS & DMBB VNS (combined
MBB & IoT Core)
– SW upgrade to SGSN-MME 1 & EPG 1– Start Massive IoT launch before EPC slicing
3 vEPC IoT VNS
(Separate Core for IoT)
– Optimization and scaling for fast IoT growth– Separation of concerns
Trang 142018-10-23 | Cloud Packet Core Roadmap | Ericsson Confidential | Page 14
DECOR NB-IoT
C-SGN MME
CN #2: IoT S-NSSAI #2
— RAN based CN selection by using NB-IoT info
— Simple - requires RAN support only
— All device types supported
— Slice selection based on UE info (S-NSSAI)
— Requires UE, CN and RAN support
— E2E slicing (RAN slice aware)
— Connectivity to multiple slices simultaneously
Roadmap
APN / PLMN
APN 2 APN 1
CN #1: MBB
APN 1
CN #2: IoT APN 2
— Requires RAN and Core support
— Policy-controlled GW selection
Common LTE Access HSS
eDECOR
— CN selection by RAN:
Retrieving UE belonging from network (at first attach in PLMN)
— Backward compatible with DECOR
— Requires UE, RAN, EPC and HSS support
Trang 15Massive IoT EPC Overview | Ericsson Internal | 27/221 09-FGB 101 256 Uen, Rev D | 2018-04-16
Trang 16Agenda
Trang 172018-07-30 | 5G Technology and Standardization | Ericsson Confidential | Page 17 (45)
5G Drivers and use cases
Enhanced MBB
Critical MTC
Fixed Wireless Access Massive MTC
Trang 182018-08-02 | 5G Architecture Readiness WS4_TrueMove Master Plan | Ericsson Confidential |
New eMBB use cases are pushing connectivity limits
Source: Qualcomm
Trang 19| PA1 | 2018-07-13 | 5G Core | Commercial in confidence | Page 19
5G UE-RAN-CN Connectivity options
Two architecture tracks in 3GPP Rel-15
Trang 20| PA1 | 2018-07-13 | 5G Core | Commercial in confidence | Page 20
First 5G NR Specs approved
Mobile industry works together to deliver complete 5G system standard on time
Dec 2017: Approval of the first set of specifications
for Non-Standalone (NSA) operation Jun 2018: Approval of specifications for Standalone (SA) operation
Trang 21| PA1 | 2018-07-13 | 5G Core | Commercial in confidence | Page 21
NSA Architecture Sub-options
Possible to split UL & DL With split of UL & DL, risk of limited UL coverage Possible to split UL & DL
Possible for radio resource utilization coordination
between LTE and NR within RAN Not possible for RAN to coordinate radio resource utilization across LTE and NR Possible for radio resource utilization coordinationbetween LTE and NR within RAN
Major up-sizing of eNB processing needed to
handle both LTE and NR Handling of multiple UP paths adds complexity and signaling Avoids pushing higher bandwidth 5G data through LTE eNB
NR LTE
5G EPC
X2
NR LTE
5G EPC
X2
• S1-C always to eNB
• S1-U terminates on eNB
• LTE eNB decides if UP traffic is routed via NR
gNB and/or LTE eNB (split bearer terminated in
LTE eNB, a.k.a Master Node)
• S1-C always to LTE eNB
• S1-U terminates on NR gNB
• NR gNB decides if UP traffic is routed via NR gNB and/or LTE eNB (split bearer terminated
in gNB, a.k.a Secondary Node)
• S1-C always to LTE eNB
• LTE eNB decides if a bearer is routed
to LTE eNB or NR gNB (bearer switching in SGW)
NR LTE
Option 3
3GPP TR 38.801
Option 3x allows early 5G launch through reusing the LTE control plane and more efficient use of LTE and NR resources
Trang 22| PA1 | 2018-07-13 | 5G Core | Commercial in confidence | Page 22
No impact to legacy services and in-market devices (incl early 5G devices) while the network evolves
— Introduce NGC and NG services without disturbing existing deployment
— Leverage VoLTE for voice while NR matures
— Introduce NR air interface to offer peak data rates early
— Leverage VoLTE for voice while NR matures
SW Upgrade
SW Upgrade with new functions
Trang 235G EPC
Trang 24| 2018-07-13 | 5G Core | Commercial in confidence | Page 24
5G EPC functions
Ericsson 5G Core | Get to the core of 5G
—
5G Enabled SGW/PGW
— Separation of CP and UP with maximum topology
flexibility and completely independent capacity
scaling of control and user planes
— Support for individual high data rates for 5G
5G Enabled MME and HSS
— 5G data rate support
— 5G subscription control
— Network slicing – DECOR, 5G GW selections
— RAN volume reporting of Secondary RAT use
— Slicing database
(Ericsson value added features in bold italics)
S5 S10
Sx S1-MME
Gx
SGi S1-U
Rx S6a
EPC NAS
CP/UP separation S11
LTE/EPC NR/EPC
GW CP MME
U U
CUPS – Not mandatory for 5G EPC
Trang 25| 2018-07-13 | 5G Core | Commercial in confidence | Page 25
5G EPC Architecture and Overview Functions
Services &
Internet
5G/NRRAN
• 5G user data rates
• DPI and Traffic Filtering
Support for
• 5G User and Policy Profile provisioning
in CUDB and SAPC
• NW Slicing Profile provisioning in Slicing Routing DB
• 5G user data rates (gNB)
• 5G/NR usage reporting (eNB)
• 5G/NR access control (eNB)
• UP path control (1/3/3a/3x) (gNB)
• Dual-Connectivity LTE/NR
Slicing Routing DB
Support for
• NW Slicing of Subscriptions
• Automated Provisioning
Support for
• Policy Control on LTE/NR access
• QoS data rates control
• LTE/NR mobility based policy
Note: UDM = HSS, SAPC, CUDB/Slicing Routing DB and EDA
➔
Trang 265G EPC Overview | Commercial in confidence | © Ericsson AB 2018 | 2018-03-28 | Page 26
5G EPC key content overview
-indicative end-to-end relations
OSS SAPC/ PCRF
Note: Relations identified on some ticked () boxes may or may not be needed depending on operator use cases.
➔
Trang 27Ericsson Internal | 2018-02-21
UDM & Policy ready for 5G EPC in 2H 2018
5G General Available features in UDM & Policy
5G subscription profiles (NEW)
CUDB supports a new profile for HSS EPC 5G subscriptions to allow storage of these new profiles and tracking of 5G subscriptions
5G QoS auth in LTE/NR access (NEW)
SAPC supports dynamic QoS authorization depending on dynamic conditions, for 5G access too 5G QoS parameters can be authorized only under certain conditions that the operator can set in the subscriber profile.
5G Policy Control on LTE/NR access (NEW)
SAPC supports dynamic policy control on the 5G subscribers too, based on events occurring during the session lifecycle Those events could change initial QoS settings and move QoS between 4G or 5G ranges based on the event type.
5G QoS Profiles (NEW)
SAPC supports the extension of the current QoS profiles to include the new high peak rates defined along with the 5G
NR technology, together with the new QCIs for V2x and Low latency communications (eMBB).
Network Instance Selection with Ericsson MME
SAPC implements 5G PGW selection based on Mobility Based Policies with MME It includes the possibility to select a
GW and, with it, a packet core network instance leveraged on the new interface between Ericsson MME and SAPC It can be considered a pre-NSSF for dynamic slice selection in 5G.
Subscription Based 5G authorization (NEW):
HSS-FE supports 5G NR as secondary RAT of LTE and corresponding access restriction data
Extended bit rates for subscribed AMBR (NEW):
The AMBR range supported by HSS-FE is extended to support above 4Gbp/s to allow full bandwidth utilization of the NR.
UE Usage Type support for Dedicated Core (Décor)
A new HSS parameter “UE Usage Type” has been introduced to select a Dedicated Core Network (DECOR) as specified in 3GPP Rel-13, supporting deployment of one (or more) dedicated core networks (DCN) within a PLMN with each DCN dedicated for specific type(s) of subscriber
Support for 5G User and Policy Profile provisioning (NEW) – EPC 5G activation
EDA supports the provisioning for 5G NR as secondary RAT of LTE and corresponding access restriction data Aggregated max bit rate is extended to support new 5G bit rates
Trang 28Ericsson Internal | 2018-02-21
5G EPC - Main UDM and Policy functions
Authorize the Access to 5G-NR
Set the 5G QoS Levels
Select the 5G-vEPC slice (eg: 5G MME, 5G PGW )
Determine the “low latency” traffic paths
Based on Subscription
+eg: Based on the data plans, device type ,location, ToD,…
+ eg: Based on the subscription type , dynamic network and session context
+ eg: Based on the EPC resources available to provide 5G Services
UDM & Policy
UDM and Policy in 5G | Commercial in Confidence |
Trang 29Ericsson Internal | 2018-02-21
5G EPC – UDM and Policy commercial view
HSS 1.19, March 18
— 5G EPC , VP (New)
— Subscription based 5G (NR) authorization
— Extended bit rates for Subscribed AMBR
— Extended bit rates over Gx/Rx
— Support of new QCI’s for low latency services
EDA 1 , Feb.18
— 5G EPC, VP (New)
— Subscription based 5G (NR) authorization
— Extended bit rates for SubscribedAMBR
NR-NSA
Support
Slice Enablement
Focus on Access and QoS Control of the NR Capability with fine granular subscription and policy control
Focus on capacity and latency and new end-user services for
full 5G experience
HSS-FE
— UE Usage Type support for Dedicated Core (Décor), VP (New)
— Select the 5G-EPC (DCN)
Trang 30Orange Spain April 2018 | Commercial in confidence | © Ericsson AB 2018 | 2018-03-27
5G Core
Trang 31Ericsson Internal | 2018-02-21
5G Core Architecture
SMF
UPF AMF
Packet Core GW
Packet CoreController
IMS
AUSF UDR
BSF SEPP
N3IWF
TDF-U AGF
SMSF SGW-C
NEF SCEF
DRA
PCRF HSS
Subscription Manager ResourceController
Policy Controller
Exposure Suite
Signaling Controller
Data-Storage Manager
LTE SALTE/NR NSA
NR SA
Notes:
1 All legacy EPC interfaces interconnecting NFs are not shown in the picture
2 Some functionality is pending conclusion of 3GPP rel-16 standardization
NRF
NSSF
CHF
Revenue Manager
SBA architecture
LMF
Mobile Positioning System
5GC Network Function as specified by 3GPP EPC Network Function as specified by 3GPP
TDF-C
Trang 32Ericsson Internal | 2018-02-21
N4
UPF
SMFNSSF AMF
PCFUDM
NamfNnssf
NpcfNudm
Nsmf
AUSFNausf
NRFNnrf
User Plane Function (UPF)
SGW UP
PGW UP
5G Core architecture overview
Changes and improvements compared to 4G
PGWSGW
Mapping the EPC functions to new 5G
CN functions
Access & Mobility management Function (AMF)
MME
Policy Control Function (PCF)
PCRF
Session Management Function (SMF)
SGW
CP PGWCP MME
Authentication Server Function (AUSF) and User Data Management (UDM)
HSS/
AAA
Trang 332018-10-18 | UDM Bootcamp 2018 - Cloud Core Policy Controller | Commercial in confidence | Page 33 (27)
Policy Function mapping from 5G EPC to 5GC
5GC 5G-EPC
SM-PCF
SMF AMF
UPF
UAM-PCF NSSF
N22
PCRF
SAPC-GW-C MME
GW-U
MBP
SAPC-CCPC CCRC
Trang 342018-10-18 | UDM Bootcamp 2018 - Cloud Core Policy Controller | Commercial in confidence | Page 34 (27)
PCF
PGW/
SMF AMF
Cloud Core Data Storage Manager
Policy Studio
Core Policy Studio
One touch configuration
Common data storage for 5G enabled UEs
Non-5G data kept in SPR
N25 Ud
Trang 35Ericsson Internal | 2018-02-21
Interworking CUDB and 5G UDR
Via CUDB to CCDM Proxy
— Smooth migration at speed chosen by customer
— Suited for longer migrations and where a CUDB upgrade makes sense
Nudm
AMFSMF
Trang 36EPC vs 5GC Comparison | Commercial in confidence | BICP-17:003758 Uen, Rev E | 2018-07-19 | Page 36
5G Core - Dual Mode
Data Network
(e.g operator
or Internet)
LTE and EN-DC
ENM support for FCAPS management of Core Network Applications
Infrastructure support for deployment of Core Network Applications
Business values
— Dual-mode (5G EPC, 5GC) support for “any
device” attaching over “any access”
— Control plane based on SBA concept for cloud
optimizations and flexible service creation
— Deployment in containers/VMs with
automation workflows
— Support for 5G service characteristics
including high capacity data processing and
individual high data rates
— Separation of Control and User planes for
independent capacity scaling and flexible
deployment
— Support for service-based network slice
selection for new business opportunities
— Support for voice in 5G devices through EPS
fallback
— Smooth 5G introduction as network upgrade
through software upgrades
Packet Core Control Plane
UDM and Policy in 5G | Commercial in Confidence |