• Aucun résultat trouvé

Demo: Plug & play network application chaining for multi-service programmability in 5G RAN

N/A
N/A
Protected

Academic year: 2022

Partager "Demo: Plug & play network application chaining for multi-service programmability in 5G RAN"

Copied!
1
0
0

Texte intégral

(1)

Demo: Plug & Play Network Application Chaining for Multi-Service Programmability in 5G RAN

Navid Nikaein, Chia-Yu Chang, Robert Schmidt, Shahab Shariat, Konstantinos Alexandris, Xenofon Vasilakos

Communication Systems Department, Eurecom, France firstname.lastname@eurecom.fr

ABSTRACT

RAN slicing is one of the key enabler to enable virtualization of a BS and its delivery as a service with different levels of network isolation and sharing so as to accommodate the needs of mobile network operators and verticals. In this demonstration, we show a prototype of a RAN slicing run- time system to enable flexible slice customization on the top of a disaggregated RAN infrastructure [1] with different levels of isolation and sharing in terms of resources and net- work functions, while retaining the quality of service (QoS) for different slice instances. Furthermore, a novel plug &

play network application chaining framework empowered by a network software development kit (SDK) is demon- strated to show how the multi-service programmability on per-slice basis can be achieved. Our demonstration is based on the OpenAirInterface [3], Mosaic-5G FlexRAN [4] and LL-MEC [2] platforms. Finally, we highlight how the the pro- posed approach can be extended to an end-to-end network slicing scenario.

1 DEMONSTRATION

The proposed demonstration has the following goals:

• To show how the RAN runtime slicing system enables the dynamic creation of slices with quality of service (QoS) support, while providing functional and resource isolation among different slices (e.g., verticals).

• To highlight the efficiency and flexibility of the proposed RAN runtime to partition and allocate radio resources among different slices based on the QoS requirement as well as the corresponding service level agreement (SLA).

• To demonstrate a novel plug & play (P&P) execution envi- ronment for network control applications running on the top of the platform software development kits (SDKs) so

Permission to make digital or hard copies of part or all of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for third- party components of this work must be honored. For all other uses, contact the owner/author(s).

MobiSys ’18, Munich, Germany

© 2018 Copyright held by the owner/author(s). ACM ISBN: 978-1-4503- 5720-3/18/06...$15.00

DOI: 10.1145/3210240.3211116

Internet Edge

RAN Core Network and Internet

EPC MEC Platform

Edge Applications

MEC Platform RAN Controller

Radio API Data Plane API

FlexRAN S1 IP

Remote Servers Open vSwitch

192.168.12.79

eth1 192.168.12.240

eth1: 192.168.12.241 eth2: 172.16.1.1

eth2

172.16.1.253

IP MEC API

Control-Plane Data-plane

SDK

OAI eNodeB

S1-C RAN Slice 3 Control Apps RAN Slice 1

Control Apps RAN Slice 2 Control Apps

Figure 1: Multi-service programmability demo setup as to customize and control the RAN programmability as per slice requirements.

We will use the testbed setup illustrated in Fig. 1, includ- ing three commercial smart phones, three Intel-based mini PCs (Intel i7, 3.4GHz processor with 8GB RAM) and 1 Ettus USRP B205 software-defined radio (SDR). The SDR is con- nected to one of the PCs, over which the eNodeB (eNB) data plane and the RAN runtime is deployed. The RAN runtime communicates through an OpenFlow-enabled open virtual switch (OVS) to the multi-access edge computing (MEC) node, where the network control application chains of three RAN slices are deployed. Each slice-specific chain is deployed in the form of P&P virtual network functions on the top of MEC platform, running isolatedly between each other. The eNB also communicates with the third PC, which acts as an evolved packet core (EPC) and home subscriber server (HSS) shared among all three RAN slices.

REFERENCES

[1] C.-Y. Chang et al. 2018. Slice orchestration for multi-service disaggre- gated ultra dense RANs.IEEE Communications Magazine(2018).

[2] A. Huang et al. 2017. Low Latency MEC Framework for SDN-based LTE/LTE-A Networks. InIEEE International Conference on Communi- cations Conference (ICC ’17).

[3] N. Nikaein et al. 2014. OpenAirInterface: A flexible platform for 5G research.ACC SIGCOMM Comput. Commun. Rev.(2014).

[4] X. Foukas et al. 2016. FlexRAN: A Flexible and Programmable Plat- form for Software-Defined Radio Access Networks. InConference on Emerging Networking EXperiments and Technologies (CoNEXT ’16).

Références

Documents relatifs

Subsequently, a transport network that is able to jointly transport backhaul (BH), fronthaul (FH) and timing services is considered (Area 2 in Figure 1) in order to connect the

NRF Network Repository Function UDM Unified Data Management NSSF Network slice selection function. UEs

Under this condition, virtualize Radio Access Network (vRAN) can cooperate with virtualized core network functions to support end-to-end network slicing aiming to adaptively manage

3) Virtualization Manager: This RAN runtime service is in charge of providing the required level of isolation and sharing to each slice. It partitions on resources and states based

NRF Network Repository Function UDM Unified Data Management NSSF Network slice selection function. UEs UPF

Based on the slice service template and slice context, the slice manager determines the CP/UP pro- cessing chain for each slice and each traffic flow, and programs the forwarding

Service registry identity Identifies to which runtime services a slice is registered to, e.g., service manager Slice SLA Describes a business agreement between slice owner

Moreover, we show the control delegation and virtualized control function capabilities of FlexRAN by swapping a remote downlink MAC scheduler running at the master controller with