「 Open5G − Open Source and

Open Architecture 5G 」

Tsinghua National Laboratory for Information Science and

Technology (TNList)

Zhigang tian
2017.04.29

1
Placeholder for introduction of
open5G Community

Open5G
– 5G Open Source Community
Open Architecture for IoT/MTC
Recall the interface between IT and CT
Dominate era Compromise era Open era

Traffic Traffic Traffic

Telecomm.
Telecom Telecom Telecom

Telecom Infrastructure Partial IT Infrastructure

COTS IT Infrastructure

?
Bearer Session Service
 IoT is not a new story Ericsson backs away from
•Global M2M connections (2013): expectation of 50B connected
195 million
devices by 2020, now sees 26B
•Growth (2010~2013): • Since late 2009, vision of what
38% CAGR it calls the "Networked
•Global M2M connections (forecast): Society" has included a key
375 million in 2017 prediction: that by 2020 there
•Leading M2M applications: will be 50 billion connected
Asset management devices around the world.
Automotive
• In its latest Ericsson Mobility
Energy and utility Report, the network vendor
and Healthcare noted that "M2M is a rapidly
growing segment and our
forecast points to
there being 26
billion connected
devices by 2020."
Internet of Everything
IoT Application Software Framework
 oneM2M
 ETSI and other SDOs
 OM2M @ Eclipse Community
 AllSeen Alliance
 Qualcomm, etc.
 AllJoyn @ Linux Foundation
 OCF
 Intel, Samsung, etc.  oneM2M inter-op with OCF
 IoTivity @ Linux Foundation  OCF run on Thread  How to integrate cellular IOT
 Thread  AllJoyn run on Thread connectivity (e.g., NB-IOT) with
 Alphabet Nest (google) them?
 OpenThread @ github  Merge together better than
integration
 What’s the indication to the
Legend
design of 5G slicing?
Open community
Open source project  open source  exploding
ecosystem
 OCF Model
• OCF Model
– RESTful + CoAP Messaging Queue System
– How to replace WiFi in below Example as 3GPP MTC/NB-IOT?
 NB-IoT & IoT Application
 Control Plane CIoT EPS optimizations
PDN

UE/MTC Device MME S-GW PDN-GW

 MTC Architecture S1-MME(NAS(encrypted

S 11 ( Small data) S5/S8 (Small data) IP traffic (Small data)
Small data))
 From rel-9 to rel-13
 clean slate NB-IoT
• Features of deep merging of Network and
 EC : extended coverage
Application in 3GPP TS 22.368 & TS 23.682
 LC : low cost
– Device Triggering Function
• … IP-SM-GW SMS-SC/ Tsms

– Group Message Delivery

GMSC/ SME
IWMSC

• eMBMS, …
E
CDF/ MTC
HSS
SGd T4 CGF AAA
S6n

– Monitoring Events
Gd
Rf/Ga

S6m

FS_M 2M
2005.9 SP#29
• handover, location update,…
2006.1 Control plane
MTC-IWF Tsp

– PSM & eDRX

2007.3 SP#35 Use r pla ne
TR 22.868
S6t
FS_U M 2M Rel-8 (SP#30~SP#43) Servi ces

• …
2007.9 SP#37 2008.3 Capability
SCEF Server
2009.12 SP#46 API
TR 33.812 2009.1 (SCS) Application

– …
2009.3 Rel-9 (SP#39~SP#47)
N IM TC Server 1
2008.9 SP#41 (AS)
sig Fo x 2010.1 T6a
2011.3 SP#51 2010.3
Founded in 2009 Rel-10 (SP#42~SP#52) Gi/SGi
TR 33.812
Raise 100M$ in
2015 GGSN/
SIM TC
2010.6 SP#48
P-GW Application
Rel-11 (SP#46~SP#59)
2012.12 SP#58 2011.6 T6b Server 2
FS_LC _M TC _LTE ??? Gi/SGi (AS)
2011.9 RP#53
2013.6 RP#60 M TC e 2012.9
TR 36.888 2012.6 SP#56
LoR a 2014.3 SP#63 2013.3
Semtech ICs in LC _M TC _LTE ??? Rel-12 (SP#52~SP#67)
2013 2013.6 RP#60
LoRa Alliance in 2015.3 RP#67 MSC SGs
2015 FS_IO T_LC 1
???? Rel-13 (SP#57~SP#72) Indirect Mode l
2014.5 GP#62 2014.9
2015.9 GP#67 LTE_M TC e2_L1
MME
FS_A E_C IO T 2015.3 Direct Model 2
TR 45.820 MTC UE
2015.3 SP#67
2016.3 SP#71 C IO T (N B _IO T) C IoT_EC _G SM
2014.9 ????
???? Application UE RAN
2015.12 SP#70 2015.8 GP#67 ???
SGSN Hyb rid Mo del 1 + 2
TR 23.720 Rel-14 (SP#65~SP#76)
???? SP#72 ???? 2016.6
???? ????
S-GW
2017.6
Um /
Uu /
 Merge of OCF and 3GPP MTC Architecture
• RESTful
– Merge with Global Database of Network

• CoAP Messaging System

– Merge with “Control
Plane CIoT EPS
optimizations”
THU Open Architecture
Evolution of THU Open Architecture
Toolset for
5G Open Architecture

Terminal AN Internet
Traffic Traffic Traffic Traffic

Open
Core
Traffic

Concept
NAS
Operation Driver
NaaS Core
Forwarding
Internet
Core Network
Coverage Mobility
HCA
Network L1/L2/L3 Nostack4UE
Subsystem
Nostack
PHY Air Interface
Waveform
Internet
Virtualization YaRAN4UE Ya!RAN
Open Virt.

Air
Framework Layer Terminal
Domain
Interface
Coverage Process Internet

Open
Architecture

Open
Source
 Motivation going to be clear
Before 5G Since 5G
Stable Requirement What is stable is only changing itself

tri-angle of
requirement
8 KPI
• Performance
• Efficiency
Finally ? no …
No one Net meet all requirements
• Ultra Reliable
Performance • eMBB and Low Latency
leading VAN
model
• IoT
• Mission Critical
Application
Agile to change
Flexible to expand
• Promise for Data
Rate, Mobility
and Coverage
Slicing across open framework/architecture

RAN + Core Internet Top Down Slicing

M Plane & APP
 Infrastructure Resource : VM,
Container, HW Virtualization
APP
Gateway-M APP

Application
Network
Base
Station-M
Gateway-
M
Gateway-
M
 Network Protocol : RAN Sharing
Controller
 Operation : MVNO
Base
Station-C
Gateway-
C
APP
Gateway-C
Gateway-
C Vertical Slicing
EDGE - Coverage Subsys Global Network
 E2E: local, cellular, EDGE, Radio
Local
Ant1

Coverage
Flow1
U Plane
Report

Context
View
Buffer Network
M Plane & APP Slicing
NAS-M APP O&M Session
RRC-M Ant2 Forming Flow2 Base Gateway- APP Gateway-
Station-U U Gateway-U U
Controller MAC-C L2-C

RRC-C
NAS-C L1-C Ant3 Flow3
U Plane Toolset for
PHY MAC-U L2-U IP
Ant4 Flow4 5G Open Architecture
Network
Terminal AN Internet
Traffic Traffic Traffic Traffic
Infrastructure Core
Traffic

NAS
Operation Driver
NaaS Core
Forwarding
Internet
Core Network
Coverage Mobility
HCA
Network L1/L2/L3 Nostack4UE
Subsystem
Nostack
PHY Air Interface
Waveform
Internet
Virtualization YaRAN4UE Ya!RAN
Virt.

Air
Layer Terminal
Interface
Coverage Process Internet
Domain
 Framework of 4 Domains X 3 Layers and Architecture including 4 Building Blocks

 Open Cellular Networking : HCA (Hyper Cellular Architecture)

 Decouple of C/U coverage  modular coverage
 Agile reconfiguration of RAT

 Open FrontHaul : Coverage Subsystem

 Soft defined mapping of user flow to Antenna
 CPRI or Sync Ethernet Networking

 Open Network Protocol : NoStack (Not only Stack)

 SDN solution for 5G RAN
 Open S Bound Interface, N Bound Interface
 Flat U Plane, Controller (C Plane), M Plane Environment, GNV

Toolset for
5G Open Architecture

Traffic
Terminal
Traffic
AN
Traffic
Internet
Traffic
 Open Infrastructure : YaRAN ( Yet another RAN)
Core
Traffic  NFV solution for 5G RAN
NAS  VNF @ INF. Orchestrator （USRT）@ INF. VIRT. @ INF. BASE
Operation NaaS
U plane @ Bare Metal environment, C Plane @ Event Driven FSM
Core
Driver Forwarding 
Internet
Core
Mobility
Network environment
HCA Coverage
Network L1/L2/L3 Nostack4UE
Subsystem
Nostack
PHY Air Interface
Waveform
Internet
Virtualization YaRAN4UE Ya!RAN
Virt.
 Open Terminal Architecture : Nostack4UE, YaRAN4UE
Layer Terminal
Air
Coverage Process Internet
 Open Air Interface Waveform : SDAI (Soft Defined Air Interface)
Interface  Open Operation & Business : NaaS (Networking/Operation as a Service)
Domain
 Consolidated Features — 4 Building Blocks
 NoStack
 SDN solution for 5G RAN : Open S Bound Interface, N Bound Interface, GNV,
Controller (C Plane), M Plane Environment
 Focus on Hetnet, UDN, IoT Scenarios
 Need a lot of infrastructure supporting
from YaRAN, e.g., GNV based on distributed in-
memory KV DB of YaRAN

 YaRAN
 NFV solution for 5G RAN : VNFINF.
Orchestrator （USRT）INF. VIRT. INF. BASE
 Bare Metal environment for U plane
 Event Driven FSM environment C Plame
 design of YaRAN
 NFV solutions for 5G RAN
 VNF @ INF. Orchestrator （USRT）@ INF. VIRT. @
INF. BASE
 U plane @ Bare Metal environment, C Plane @
Event Driven FSM environment
 U Plane
 bare metal : Affinity + Dynticks + DPDK
 DPDK accelerated openvswitch
 SHMEM, IVSHMEM, RDMA, ETCD in CoreOS
 C Plane
 libevent或Poll/Select
 DPDK event mechanism
 M Plane
 Kubernete
 Orchestrator – USRT
 Hardware Accelerator
 DPDK + AXI switch @ ARM
 Open Network Protocol—NoStack
 Framework of NoStack
– Flat U Plane
 Global Network View – Flow Table based South Bound Interface
 Special Plug-in of Access Network OS – Access Network OS with Plug-in(s)
 Consistent guaranty together with Access – Logical centralized C plane
Network OS – Open M Plane upon North Bound Interface
 Decouple session, report, context from
control FSM D2D Handover Joint RACH UE State Antenna
Grouping Decision Decision Management Group
Policy APP APP APP Forming
APP

M Plane & APP

North Bound
Interface
Handover Joint RACH PC Cmd
Command Dispatcher Forming
Seq GNV
ANOS Core Service Service Service
Consistent,timing,... Joint RACH
Handover Cmd Detection PC Cmd Tx Service
Tx Process Process Process

Open S Bound Interface

& Driver
Driver Driver Driver
Coverage Unit
Robust Control Controller
Open N Bound Interface Coverage Antenna1 Resource
1
South Bound
Interface
Global Network View

Coverage
Open GNV Antenna2
Forming
Resource
Report
2

Open Plug-in ANOS(C Plane)

Flow Table
Traffic Coverage Context Session
Antenna3 Resource

Open M Plane Environment 3 Buffer

User Sense Antenna4 Resource U Plane Internet

Coverage 4

Coverage NoStack
HCA Subsystem
 Consolidated Features — 4 Building Blocks (cont.)
 HCA & mmWave PoC
 Decouple of C/U coverage modular
coverage Open cellular networking
 Narrow beam per user
 User Oriented Coverage
 Dual Connectivity of Macro carrier and
mmWave carrier
 Macro carrier enable C coverage
 mmWave carrier enable U coverage

 Coverage Subsystem
 CPRI or Sync Ethernet Networking
 Soft defined mapping of user flow to
Antenna
 Distributed Beamforming
“1”Integral PoC

 FIT Testbed
 Continuous Building since 2012,
funded by 5 National Projects
 Total 60 Antennae
 Outdoor 3 Cells 6F

 Indoor 18 Cells
 YaRAN & NoStack in Room 4-510 5F

 Coverage Subsystem in shaft &

passage of Floor 3~5 4F

 HCA & mmWave PoC in Room #

3F
 open5G HW Suite
 Infrastructure of Coverage Subsystem/FrontHaul
 Preparing for release – manufacturing, testing, …
 Use YoctoTM to build SDK for programmer, user, …
 Build repositories server as software package distributing center
 Porting to UHD/OAI

PCIe
Accelera
tor & RF

open5G Coverage
Subsystem
HW Suite Phase I
Thanks！
Open Cellular Networking
Decouple of C/U coverage  modular coverage Open cellular networking

Hype Cellular
Architecture
 Other Use Cases
May or may not change the standard

• NO Stack Support Legacy Stack

– Case 1 : EPC Architecture & EPS Bearer
• NO Stack Encourage Emerging Stack
– Case 4 : 3GPP CoMP
• NO Stack Short (Legacy) Stack and (Emerging) Stack
– Case 2 : CSFB
– Case 3 : Traffic Offloading
 EPC Architecture & EPS Bearer (Conventional)

• Network Element Function

– SGW = GW + Mobile Anchoring
E-UTRAN EPC Internet
– PGW = GW + PCRF + DNS
UE eNB S-GW P-GW Peer

– MME = Controller of EPS, Mobility, NAS Entity

– SGW/PGW deal with mobility tunnel End-to-end Service

– ENB = Uu Processer + GW EPS Bearer External Bearer

E-RAB S5/S8 Bearer

Radio Bearer S1 Bearer

Radio S1 S5/S8 Gi
 EPC Architecture & EPS Bearer (NO Stack)

• Redefine Network Element

– MME is extended as Global
Controller
– Mobile anchoring of SGW
moved to Global Network
View
– DNS of PGW is moved to
Global Controller
– PCRF of PGW moved to Global
Controller, PCRE kept in xGW
 Use Case 1 — EPS Bearer Establishment
Benefit: Stateless in U plane  reduce complexity, increase flexibility
Parallel Atom Transaction  reduce latency

Conventional

No Stack
 Use Case2 –
Handover of Multi-RAT

From ～50 Serial Message To

 ～20 Service Invocation of
Centralized C Plane
 1 Transaction with 6 parallel
instruction to U Plane
 1 Bulk Data Modification of Database
 Use Case 3 – Offloading

Conventional No Stack
• Hetnet • Benefit
• Add signaling between • Flat User Plane + Orchestrator
NEsComplex Fast RAT transition
• Handshaking in a long path to sync • Orchestrator + Global Report View
the state  Slow  Better Performance
 Use Case 4 - CoMP (NoStack)
• NoStack-Core
– UE EPS bearer have no relation
with Uu processor
• NoStack-Process
– Use parallel South Bound
Interface replace serialized
X2AP
– Uu Processer per User Flow
– Coverage Process per Macro
Cell
• Coverage
– Provide coverage service for Uu
Process & Coverage Processor
– Controlled by Global Controller
• HCA
– Use Macro coverage to TX
control signaling for small cells