1

Tsinghua National Laboratory for Information Science and Technology (TNList) Zhigang tian 2017.04.29

「 Open5G − Open Source and Open Architecture 5G 」

Placeholder for introduction of open5G Community

Open5G– 5G Open Source Community

Open Architecture for IoT/MTC

Telecomm.

Traffic

Dominate era

Traffic

Compromise era

Telecom Telecom

Traffic

Open era

Telecom

COTS IT Infrastructure Partial IT Infrastructure Telecom Infrastructure

? Bearer Session Service

Recall the interface between IT and CT

IoT is not a new story •Global M2M connections (2013): 195 million •Growth (2010~2013): 38% CAGR •Global M2M connections (forecast): 375 million in 2017 •Leading M2M applications: Asset management Automotive Energy and utility and Healthcare

Ericsson backs away from expectation of 50B connected devices by 2020, now sees 26B • Since late 2009, vision of what

it calls the "Networked Society" has included a key prediction: that by 2020 there will be 50 billion connected devices around the world.

• In its latest Ericsson Mobility Report, the network vendor 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. IoTivity @ Linux Foundation

Thread Alphabet Nest (google) OpenThread @ github

How to integrate cellular IOT connectivity (e.g., NB-IOT) with them? Merge together better than

integration What’s the indication to the

design of 5G slicing? open source exploding

ecosystem

Legend Open community Open source project

oneM2M inter-op with OCF OCF run on Thread AllJoyn run on Thread

OCF Model • OCF Model

– RESTful + CoAP Messaging Queue System – How to replace WiFi in below Example as 3GPP MTC/NB-IOT?

FS_M 2M2005.9 SP#292007.3 SP#35

TR 22.868

2006.1

2009.3

2010.3

2008.3Rel-8

Rel-9

2011.6

Rel-10

2009.1

(SP#30~SP#43)

(SP#39~SP#47)

(SP#42~SP#52)

FS_U M 2M2007.9 SP#37

2009.12 SP#46TR 33.812

N IM TC2008.9 SP#412011.3 SP#51

TR 33.812

SIM TC2010.6 SP#48

2012.12 SP#58???

2010.1

Rel-11

2013.3

(SP#46~SP#59)

Rel-12

2015.3

(SP#52~SP#67)

2012.9

Rel-13 (SP#57~SP#72)

2016.6

2017.6

2014.9

Rel-14 (SP#65~SP#76)

M TCe2012.6 SP#562014.3 SP#63

???

FS_LC_M TC_LTE2011.9 RP#532013.6 RP#60TR 36.888

LC_M TC_LTE2013.6 RP#602015.3 RP#67

???? FS_IO T_LC2014.5 GP#622015.9 GP#67TR 45.820

FS_A E_CIO T2015.3 SP#672016.3 SP#71TR 23.720

CIO T (N B_IO T)2015.12 SP#70

???? SP#72????

CIoT_EC_G SM2015.8 GP#67

????????

LTE_M TCe2_L12014.9 ????

???????

sigFoxFounded in 2009Raise 100M$ in

2015

LoRaSemtech ICs in

2013LoRa Alliance in

2015

MTC Architecture From rel-9 to rel-13

clean slate NB-IoT EC : extended coverage LC : low cost

NB-IoT & IoT Application PDN

UE / MTC Device MME S - GW PDN - GW S 1 - MME ( NAS ( encrypted

Small data )) S 11 ( Small data ) IP traffic ( Small data ) S 5 / S 8 ( Small data )

Services Capability

Server(SCS)

Gi/SGi

TspControl plane

User plane

Indirect Model

Direct Model

Hybrid Model

GGSN/P-GW

SMS-SC/GMSC/IWMSC

2

1

1

T4

S6m

Rf/Ga

Um /Uu /

MTC UE Application

MME

Gi/SGi

SGSN

S-GW

UE

MSC

RAN

T6a

T6b

HSS

Tsms

Application Server

(AS)1

Application Server

(AS)2

IP-SM-GW

CDF/CGF

2+

SME

MTC-IWF

MTCAAA

S6n

E

SGd

Gd

SCEFAPI

S6t

SGs

Control Plane CIoT EPS optimizations

• Features of deep merging of Network and Application in 3GPP TS 22.368 & TS 23.682 – Device Triggering Function

• … – Group Message Delivery

• eMBMS, … – Monitoring Events

• handover, location update,… – PSM & eDRX

• … – …

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

Open Concept

Open Framework

Open Architecture

Open Source

HCA

Ya!RAN

Nostack

NaaS

Nostack4UE

YaRAN4UE

NASDriver

InternetNetwork

InternetVirt.

InternetTraffic

TerminalTraffic

Toolset for5G Open Architecture

Air InterfaceWaveform

CoverageSubsystem

Terminal Air Interface Coverage Process Internet

Virtualization

Network

Operation

Traffic ANTraffic

LayerDomain

Core

Traffic

Core

Forwarding

Core

MobilityL1/L2/L3

PHY

Performance leading VAN model • Promise for Data

Rate, Mobility and Coverage

tri-angle of requirement • eMBB • IoT • Mission Critical

Application

8 KPI • Performance • Efficiency • Ultra Reliable

and Low Latency

Motivation going to be clear Before 5G

Stable Requirement Since 5G

What is stable is only changing itself

Agile to change Flexible to expand

Finally

?

no … No one Net meet all requirements

HCA

Ya!RAN

Nostack

NaaS

Nostack4UE

YaRAN4UE

NASDriver

InternetNetwork

InternetVirt.

InternetTraffic

TerminalTraffic

Toolset for5G Open Architecture

Air InterfaceWaveform

CoverageSubsystem

Terminal Air Interface Coverage Process Internet

Virtualization

Network

Operation

Traffic ANTraffic

LayerDomain

Core

Traffic

Core

Forwarding

Core

MobilityL1/L2/L3

PHY

Slicing across open framework/architecture

Top Down Slicing Infrastructure Resource : VM,

Container, HW Virtualization Network Protocol : RAN Sharing Operation : MVNO Vertical Slicing E2E: local, cellular, EDGE, Radio

Network

Internet

Local

Controller

RRC-C NAS-C L1-C

MAC-C L2-C

PHY MAC-U L2-U IP

U Plane

M Plane & APPO&MAPPNAS-M

RRC-M

Controller

M Plane & APP

U Plane

Base Station-U

Gateway-U

APP Gateway-U

Gateway-U

Base Station-C

Gateway-C

APP Gateway-C

Gateway-C

Base Station-M

Gateway-M

APP Gateway-M

Gateway-M

APP

Global Network ViewReport

Session

BufferContext

RAN + Core

EDGE - Coverage SubsysAnt1

Ant2

Ant3

Ant4

CoverageSlicing Forming

Flow1

Flow2

Flow3

Flow4

Network

Infrastructure

ApplicationNetwork

Framework of 4 Domains X 3 Layers and Architecture including 4 Building Blocks

HCA

Ya!RAN

Nostack

NaaS

Nostack4UE

YaRAN4UE

NASDriver

InternetNetwork

InternetVirt.

InternetTraffic

TerminalTraffic

Toolset for5G Open Architecture

Air InterfaceWaveform

CoverageSubsystem

Terminal Air Interface Coverage Process Internet

Virtualization

Network

Operation

Traffic ANTraffic

LayerDomain

Core

Traffic

Core

Forwarding

Core

MobilityL1/L2/L3

PHY

Open Terminal Architecture : Nostack4UE, YaRAN4UE Open Air Interface Waveform : SDAI (Soft Defined Air Interface) Open Operation & Business : NaaS (Networking/Operation as a Service)

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

Open Infrastructure : YaRAN ( Yet another RAN) NFV solution for 5G RAN VNF @ INF. Orchestrator （USRT）@ INF. VIRT. @ INF. BASE U plane @ Bare Metal environment, C Plane @ Event Driven FSM

environment

NoStack SDN solution for 5G RAN : Open S Bound Interface, N Bound Interface, GNV,

Controller (C Plane), M Plane Environment

Consolidated Features — 4 Building Blocks

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 : VNFINF.

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

Coverage Subsystem

NoStack

Flow Table

U Plane

Coverage Unit

Antenna1

Antenna2

Antenna3

Antenna4

Coverage Forming

Resource1

Resource2

Resource3

Resource4

Controller

M Plane & APP

Internet

Global Network View

Report

Session

Buffer

Context

Joint RACHDecision

APP

Handover Decision

APP

D2D Grouping

Policy

ANOS Core

Driver

Handover Cmd Tx Process

Driver

Service

HandoverCommand

SeqService

Consistent,timing,...

AntennaGroup

FormingAPP

South BoundInterface

North BoundInterface

Service& Driver

GNV

UE State Management

APP

Driver

Joint RACH Detection Process

Service

Joint RACH Dispatcher

PC Cmd Tx Process

PC Cmd Forming

HCA

Robust Control Coverage

Traffic Coverage

User SenseCoverage

Framework of NoStack – Flat U Plane – Flow Table based South Bound Interface – Access Network OS with Plug-in(s) – Logical centralized C plane – Open M Plane upon North Bound Interface

Global Network View Special Plug-in of Access Network OS Consistent guaranty together with Access

Network OS Decouple session, report, context from

control FSM

Open Network Protocol—NoStack

Open S Bound Interface Open N Bound Interface Open GNV Open Plug-in ANOS(C Plane) Open M Plane Environment

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

Consolidated Features — 4 Building Blocks (cont.)

FIT Testbed Continuous Building since 2012,

funded by 5 National Projects Total 60 Antennae

Outdoor 3 Cells Indoor 18 Cells

YaRAN & NoStack in Room 4-510 Coverage Subsystem in shaft &

passage of Floor 3~5 HCA & mmWave PoC in Room #

“1”Integral PoC

6F

5F

4F

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

PCIeAccelerator & RF

Coverage Subsystem

Phase I

open5GHW Suite

Thanks！

Hype Cellular Architecture

Decouple of C/U coverage modular coverage Open cellular networking

Open Cellular Networking

Other Use Cases

• 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

May or may not change the standard

EPC Architecture & EPS Bearer (Conventional)

P-GWS-GW PeerEntity

UE eNB

EPS Bearer

Radio Bearer S1 Bearer

End-to-end Service

External Bearer

Radio S5/S8

Internet

S1

E-UTRAN EPC

Gi

E-RAB S5/S8 Bearer

• Network Element Function – SGW = GW + Mobile Anchoring – PGW = GW + PCRF + DNS – MME = Controller of EPS, Mobility, NAS – SGW/PGW deal with mobility tunnel – ENB = Uu Processer + GW

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

Conv

entio

nal

No

Stac

k

Benefit: Stateless in U plane reduce complexity, increase flexibility Parallel Atom Transaction reduce latency

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 Case2 – Handover of Multi-RAT

Use Case 3 – Offloading

• Hetnet • Add signaling between

NEsComplex • Handshaking in a long path to sync

the state Slow

• Benefit • Flat User Plane + Orchestrator

Fast RAT transition • Orchestrator + Global Report View Better Performance

Conventional No Stack

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