development of thu open architecture & open5g community...live migration •scenario –x2...

25
1 Beijing National Research Center for Information Science and Technology (BNRist) Tsinghua National Laboratory for Information Science and Technology (TNList) Zhigang tian 2018.06.21 Development of THU Open Architecture & Open5G Community

Upload: others

Post on 19-Sep-2020

0 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Development of THU Open Architecture & Open5G Community...Live Migration •Scenario –X2 handover requires co-operation of 2 eNBs and UE configuration changes –Migration will not

1

Beijing National Research Center for Information Science and Technology (BNRist)Tsinghua National Laboratory for Information Science and Technology (TNList)

Zhigang tian2018.06.21

「 Development of THU Open Architecture & Open5G Community 」

Page 2: Development of THU Open Architecture & Open5G Community...Live Migration •Scenario –X2 handover requires co-operation of 2 eNBs and UE configuration changes –Migration will not

Open5G Community

Page 3: Development of THU Open Architecture & Open5G Community...Live Migration •Scenario –X2 handover requires co-operation of 2 eNBs and UE configuration changes –Migration will not

3

Objectives of Open5G

Promoting innovation and finding new growth pole for ICT Contributations from volunteer partners, especially from universities Exploring a new open-source path Providing paradigms for innovation of industrial organizations Enhancing the integration between 5G and Vertical Industry (Vehicles, IoT, etc.) Setting up the impartial third party innovation development platform Reducing invalid competition and input Integrating resources rapidly Establishing orderly ecology

1st Objective

2nd

Objective

3rd Objective4th Objective

Page 4: Development of THU Open Architecture & Open5G Community...Live Migration •Scenario –X2 handover requires co-operation of 2 eNBs and UE configuration changes –Migration will not

Members of Open5G

4

* more applications are processing ...

Page 5: Development of THU Open Architecture & Open5G Community...Live Migration •Scenario –X2 handover requires co-operation of 2 eNBs and UE configuration changes –Migration will not

5

Organizational Structure

Developer Maintainer

Administration Committee

Page 6: Development of THU Open Architecture & Open5G Community...Live Migration •Scenario –X2 handover requires co-operation of 2 eNBs and UE configuration changes –Migration will not

Key Techniques

Research and development of 5G soft base

station and testbed with high throughput

Research and validation of Millimeter wave indoor wireless access technology with super capacity

Research and validation of 5G wireless network virtualization technology

Future radio access technologies, e.g., physical layer and system’s security

Research and development of new modulation and coding technology

Appeal in MOST 863 5G Program

Cooperation Among up to 17 Projects

Sharing Knowledge and Platforms

Several Tens of Contribution Project to Open5G

Step from the first objective,move to the second, …

Progress of Open5G - First Step

Ultra Dense Networking, High

Capacity & Hyper-Cellular

High Efficient 5G Wireless Transmission

&Massive Cooperation

5G System Framework5G Vision, Requirements, Spectrum

& Enabling Techniques

5G Evaluation & Test Methodology

5G Wireless Network

High dense networking

High capacity

Hyper-cellular network

5G Wireless Transmission

Massive collaboration

High efficient wireless transmission

5G General Technology

General technologies for 5G mobile communications

5G Testing Technology

5G testing and validation technologies

Page 7: Development of THU Open Architecture & Open5G Community...Live Migration •Scenario –X2 handover requires co-operation of 2 eNBs and UE configuration changes –Migration will not

Cross-strait 5G Co-funding Program

Great Cooperation & Progress› Papers: 188+

› Patents: 57+

› SDO Contributions: 1+

› PoC/Testbed : 5+

› PHD/Master Students: 100+

› Visit: 2-3 per year

› Publications: White paper…

› Official Events: 9 joint 5G working meetings、6 Joint-exhibition、10 Brainstorming

workshops and 5 Summit Conferences, etc.

Page 8: Development of THU Open Architecture & Open5G Community...Live Migration •Scenario –X2 handover requires co-operation of 2 eNBs and UE configuration changes –Migration will not

Open Architecture & Open Source

open5G—Open Source Community

• Strategy Cooperation with Openforg, OAI

• Joint Testbed of OAI&open5G

NoStack—Open Protocol Architecture for Pre-5G/5G/B5G

• Supported by Intel、HUAWEI、CMCC

• Porting OAI to NoStack Framwork, SBA Prototype for CMCC

YaRAN—Advanced Cloud Native IaaS

• Docker + Kubernetes

• FIT Testbed

Page 9: Development of THU Open Architecture & Open5G Community...Live Migration •Scenario –X2 handover requires co-operation of 2 eNBs and UE configuration changes –Migration will not

THU Open Architecture

Page 10: Development of THU Open Architecture & Open5G Community...Live Migration •Scenario –X2 handover requires co-operation of 2 eNBs and UE configuration changes –Migration will not

Evolution of THU Open Architecture

Open

Concept

Open

Framework

Open

Architecture

Open

Source

HCA

Ya!RAN

Nostack

NaaS

Nostack4UE

YaRAN4UE

NAS

DriverInternet

Network

Internet

Virt.

Internet

TrafficTerminal

Traffic

Toolset for

5G Open Architecture

Air Interface

Waveform

Coverage

Subsystem

TerminalAir

InterfaceCoverage Process Internet

Virtualization

Network

Operation

TrafficAN

Traffic

Layer

Domain

Core

Traffic

Core

Forwarding

Core

Mobility

L1/L2/L3

PHY

Page 11: Development of THU Open Architecture & Open5G Community...Live Migration •Scenario –X2 handover requires co-operation of 2 eNBs and UE configuration changes –Migration will not

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

HCA

Ya!RAN

Nostack

NaaS

Nostack4UE

YaRAN4UE

NAS

DriverInternet

Network

Internet

Virt.

Internet

TrafficTerminal

Traffic

Toolset for

5G Open Architecture

Air Interface

Waveform

Coverage

Subsystem

TerminalAir

InterfaceCoverage Process Internet

Virtualization

Network

Operation

TrafficAN

Traffic

Layer

Domain

Core

Traffic

Core

Forwarding

Core

Mobility

L1/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 coveragemodular 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

Page 12: Development of THU Open Architecture & Open5G Community...Live Migration •Scenario –X2 handover requires co-operation of 2 eNBs and UE configuration changes –Migration will not

6F

5F

4F

3F

FIT TestbedTotal 60 Antennae

Outdoor 3 Cells

Indoor 18 Cells

YaRAN & NoStack

in Room 4-510

Coverage Subsystem

in shaft & passage ofFloor 3~5

Page 13: Development of THU Open Architecture & Open5G Community...Live Migration •Scenario –X2 handover requires co-operation of 2 eNBs and UE configuration changes –Migration will not

Switch

Server0

eNB

Docker

Bridge

...

eNB

Docker

Brid

ge

Server1

eNB

Docker

Brid

ge

...

eNB

Docker

Bridge

Docker Swarm

10Gbps

10Gbps

Switch

EPC

Server

Internet

UE UE

Open HW suite

Open HW suite

Demo of Open Architecture

Architecture• RRU : Open5G HW suite

• Xilinx Zynq 7030 + AD9361• Gigabit Ethernet

• OAI eNB + OAI EPC• Docker + K8S/Swarm

Page 14: Development of THU Open Architecture & Open5G Community...Live Migration •Scenario –X2 handover requires co-operation of 2 eNBs and UE configuration changes –Migration will not

YaRAN

Candidate technologies evaluated DPDK Dynticks SHMEM Libevent K8S SR-IOV RSS ..

K8S used as VIM of YaRAN micro-service framework of NoStack instead of K8S

Page 15: Development of THU Open Architecture & Open5G Community...Live Migration •Scenario –X2 handover requires co-operation of 2 eNBs and UE configuration changes –Migration will not

Key Component of NoStack

CU (Pool) 0

WorkerThread/

Core

WorkerThread/

Core

WorkerThread/

Core

message bus

UE0NF1

UE0NF2

UE1NF1

UE1NF2

UExNF1

UExNF2

Replicate GNV0

Global GNV

CU (Pool) 1

WorkerThread/

Core

WorkerThread/

Core

WorkerThread/

Core

message bus

UE0NF1

UE0NF2

UE1NF1

UE1NF2

UExNF1

UExNF2

CommonNF2

DispatchNF

CommonNF1

DispatchNF

Replicate GNV1

CommonNF2

CommonNF1

Topology View

Core (Pool) 1

WorkerThread/

Core

WorkerThread/

Core

WorkerThread/

Core

message busDispatch

NF

Replicate GNV2

CommonNF2

CommonNF1

Global Controller

PD CP-URLC-U

UP M ACPH Y-U

Uu

-C

D ispatcher

Uu

-U

South Bound Interface

North Bound Interface

PH Y-C

M AC-C

MACControl Element

RLC-U-C

RLCSTATUS PDU

PD CP-U-C

PDCPStatus Report

RLC-C PD CP-C

RRC

RRC IE

N AS

NAS IE

Core APP

Msg

Msg

RRM

Global Network View

D B M ng Global Session View

Global Resource View(Air)

Global Buffer ViewSync

PD CP-URLC-U

Sync

TRP

RN O rchetrator

NFV-I Interface

NFV MANO NFV Storage

G lobal Resource View (IN F)M sg Broker @ SCTP @ UD P

Global Orchetrator

Mapping

Mapping

Manage

FW D APP-Proc

Coverage Subsys

CP M AC

Msg

Message Bus/Broker Service mesh above IP Enable agile scheduling of NF/routing Enable flexible management of

Stateful and Stateless service …

GNV SBA Compatible RESTful compatible Enable stateless NFs

Page 16: Development of THU Open Architecture & Open5G Community...Live Migration •Scenario –X2 handover requires co-operation of 2 eNBs and UE configuration changes –Migration will not

Next Generation Control @ Service Based Architecture framework a SDN practice

C/U separate Logical centric of C plane

Following NFV concept NF (network functions) orchestrated by MANO

Service decoupling Independent service provided by each NF RESTful api

Page 17: Development of THU Open Architecture & Open5G Community...Live Migration •Scenario –X2 handover requires co-operation of 2 eNBs and UE configuration changes –Migration will not

Brief History of Docker, K8S and Service Mesh• Container Virtualization & DevOps era

– 2007, cgroups appear in Linux kernel– 2013.3, Docker announcement– 2014, DevOps: Docker images. Docker registries. , Build, Ship, Run

– 2014.3, libcontainer appear to replace LXC – 2015.6, OCI (Open Container Initiative) announcement

• Orchestrator & micro-service era– 2015, Kubernetes 1.0 released by Google and RedHat– 2015, Cloud Native Computing Foundation (CNCF) founded– 2015, Docker release Compose+Swarm+Machine– 2016, Docker release containerd and join CNCF– 2017.10, Docker include Kubernetes in Docker EE

• Service Mesh & Serverless @ K8S/CNCF eco-system– 2016.9, Buoyant announce linkerd– 2016.9, Envoy 1.0 release– 2017.5, Istio project announced by Lyft, IBM

and Google– 2017, openFaaS, kuberless, etc.

Page 18: Development of THU Open Architecture & Open5G Community...Live Migration •Scenario –X2 handover requires co-operation of 2 eNBs and UE configuration changes –Migration will not

Live Migration

• Scenario– X2 handover requires co-operation of 2

eNBs and UE configuration changes

– Migration will not change UE configurations such as IP-address, etc. So UE is unaware

• Our solution: CRIU + Docker– Checkpoint & restore in userspace

– Docker-native

Page 19: Development of THU Open Architecture & Open5G Community...Live Migration •Scenario –X2 handover requires co-operation of 2 eNBs and UE configuration changes –Migration will not

Live Migration

• S1 connection of eNB– CRIU does not support kernel SCTP sockets

– Apply lib-usrsctp to OAI: A userland SCTP stack

– Fix SCTP over UDP Encapsulation and pure SCTP support in CRIU

• FrontHaul connection of eNB– Fix raw socket support in CRIU

• Some tricky applied to air interface– Stop/resume scheduling for target UE to avoid L1 procedure interrupt

– Re-sync of timing to RRU (open5G HW Suite)

Page 20: Development of THU Open Architecture & Open5G Community...Live Migration •Scenario –X2 handover requires co-operation of 2 eNBs and UE configuration changes –Migration will not

We have a dream…• While you travelling around the world

– Your stateless 5G NG core network @ NoStack is following you … without inflexible re-location– Your stateful per-user 5G NR base station @ NoStack is migrated along with you … without inflexible

handover– Your stateful EDGE application server @ YaRAN is migrated along with you … without interrupted enjoy

Adrian Reber, Mike Rapoport, Container Migration All Around The World, Open Source Summit Europe 2017

Page 21: Development of THU Open Architecture & Open5G Community...Live Migration •Scenario –X2 handover requires co-operation of 2 eNBs and UE configuration changes –Migration will not

SBA is workable

Page 22: Development of THU Open Architecture & Open5G Community...Live Migration •Scenario –X2 handover requires co-operation of 2 eNBs and UE configuration changes –Migration will not

Round-Robin Scheduling of Workers by Message Bus

SBA @ NoStack is workable

Page 23: Development of THU Open Architecture & Open5G Community...Live Migration •Scenario –X2 handover requires co-operation of 2 eNBs and UE configuration changes –Migration will not

ICT & GDP

Page 24: Development of THU Open Architecture & Open5G Community...Live Migration •Scenario –X2 handover requires co-operation of 2 eNBs and UE configuration changes –Migration will not

5G need ICT Convergence

Monthly ARPU

AT&T:41.5USD

CMCC:10USD

Facebook:1.25USD

Tencent:2.5USD

Page 25: Development of THU Open Architecture & Open5G Community...Live Migration •Scenario –X2 handover requires co-operation of 2 eNBs and UE configuration changes –Migration will not

Thanks!