Page 15 - 5G Proof-of-Concept Demonstrations

5G Proof-of-Concept Demonstrations

2.4 Softwarized LTE in FLARE network slices - how to slice eNodeB (eNB) and
Evolved Packet Core (EPC) on a FLARE node

Akihiro Nakao, Ping Du, The University of Tokyo; Softwarizarion
Masayuki Kashima, Yoshihiro Nakahira, Oki Electric Industry Co., Ltd.
Presentation

The demo showed how to slice eNodeB (eNB) and Evolved Packet Core (EPC) on the FLARE node,
highly programmable network node, as Proof-of-Concept (PoC) of network softwarization and
network slicing for IMT-2020. In this PoC demo, engineers softwarized both eNB and EPC using
modified OpenAirInterface, and implemented an LTE network in a slice on top of a FLARE node,
where signalling-related EPC entities (e.g. MME) and eNB are implemented in a control plane, while
user data forwarding and processing (e.g. SGW and PGW) are implemented in a data plane. In the
data plane, EPC is divided into function elements and parallelize packet processing across many
on-chip core processors. FLARE enables rapid deployment of data-plane network functions with Click
network-programming framework. In the control plane, demo runs signalling-related EPC, eNB and
HSS in Docker instances within the same FLARE slice. Each LTE network slice is Dockerized
(implemented in Docker), i.e. in a minimal resource environment. LTE network slice instances are
isolated without interfering each other. Showcase demonstrates playback of YouTube videos on a
smartphone (Nexus 5) connected to an OAI slice on FLARE.
Demonstration

2.5 5G operating platform: Infrastructure-agnostic orchestration
Antonio Manzalini, TIM; Fulvio Risso, Politecnico di Torino

Presentation

This demo showed an overarching orchestration software architecture that was based on a
continuous advertisement of capabilities and resources from underlying infrastructure-layer
domains, allowing the orchestration to adapt its service logic to exploit the most up-to-date
capabilities. The demo showed how to set up a complex NFV service across multiple domains, such
as two OpenStack instances connected by an SDN network, where all the service functions (e.g. NAT,
firewall, etc.) are launched in the data centre and the intermediate SDN network is used only to
connect all the different components together. However, when the SDN network also advertises the
capability to host a given set of network applications (e.g. a NAT), the orchestrator adapts its service
logic and it instantiates part of the service in the data centre (e.g. as virtual machines), part in the
SDN domain (e.g. as ONOS applications), hence enabling more aggressive optimization strategies in
the overarching orchestrator.
Demonstration

7