Multi-Domain Orchestration for the Deployment and Management of Services on a

Slice Enabled NFVIFrancesco Tusa*, Stuart Clayman*, Dario Valocchi, Alex Galis*

*University College London

MOBISLICE/5GNETApp Workshop27th November, Verona, Italy

Content

• Context • Slicing Concepts• Interworking of Management and Orchestration systems• Concluding Remarks

MOBISLICE/5GNETApp Workshop

Content

• Context• Slicing Concepts• Interworking of Management and Orchestration systems• Concluding Remarks

MOBISLICE/5GNETApp Workshop

• Allocation of resources in a (multi-provider) multi-domain federated end-to-end infrastructure

• Dynamic, software-based allocation of resources via functions virtualization and software defined networks

• Different Management and Orchestration (MANO) systems in each segment of the end-to-end infrastructure should interwork to support this scenario

• End-to-end slices are used to create groups of resources from the edge to the core and to introduce isolation at the control and data planes (different service requirements)

Context: 5G landscape

MOBISLICE/5GNETApp Workshop

Context: 5G landscape and considered scenario

MOBISLICE/5GNETApp Workshop

MANO A

MANO B MANO C

Edge Domain

CoreDomain

Core Domain

EdgeDomain

VIMVIM

VIM

VIMEnd-to-end Slice

backhaul core backhaul

Content

• Context• Slicing Concepts• Interworking of Management and Orchestration systems• Concluding Remarks

MOBISLICE/5GNETApp Workshop

• Aggregated set of resources that can be used in the context of end-to-end VNF-based networked services

• Basic unit of programmability based on isolated resources (between slices) that include network, computation and storage

• If we have slicing everywhere – including networks and DCs – then:

• there is a separation of physical / logical resources• there is isolation of services as no customers share physical / logical resources• it is secure as only specified customer can access a host, no sharing or cross

VM issues• different slices can support different features

Slicing Concepts

MOBISLICE/5GNETApp Workshop

• Where Slicing should be implemented?

• We introduce a DC Slice Controller able to allocate a slice of a DC and create an on-demand per-slice VIM

• Each slice and its associated VIM are independent of the other slices and VIMs

• Best type of VIM deployed in each segment of the end-to-end infrastructure

• Each of these slices will be allocated and de-allocated in an on-demand fashion via interacting with the DC Slice Controller

Slicing Concepts: VIM on-demand

MOBISLICE/5GNETApp Workshop

Slicing Concepts: VIM on-demand

MOBISLICE/5GNETApp Workshop

Content

• Context• Slicing Concepts• Interworking of Management and Orchestration systems• Concluding Remarks

MOBISLICE/5GNETApp Workshop

Interworking of MANO systems

DomainAdaptor

MANO A

MANO B

Domain Adaptor

VIM1 VIM2

Resource Orchestrator

Resource Orchestrator

DomainAdaptor

MOBISLICE/5GNETApp Workshop

MANO C

Domain Adaptor

VIM3

Resource Orchestrator

DomainAdaptor

Data Center Data Center Data Center

Infrastructure and Capabilities from each lower level MANO are exported to the higher MANO via Domain Adapters and APIs – north-south interaction and data models translations

VNF1 VNFn VNFn+1 VNFm VNF

m+1 VNFk

A Service Function Chain can be instantiated across the shared physical infrastructure

Distributed NFVI

S1

Interworking of MANO systems on a sliced NFVI

Domain

Adaptor

MANO A

MANO B

Domain Adaptor

Slice

ControllerVIM1

Slice

ControllerVIM2

VNF1 VNFnVNF

n+1VNFm

Resource Orchestrator

Resource Orchestrator

Domain

Adaptor

MOBISLICE/5GNETApp Workshop

MANO C

Domain Adaptor

Slice

ControllerVIM3

VNF

m+1VNFk

Resource Orchestrator

Domain

Adaptor

Slice Part Slice Part Slice Part

Distributed NFVI

Domain adapters play the role of a Slice orchestrator and

interact with the local Slice Controller to create slicesResources are assigned to each Slice partVIM instances are deployed on-demand in each Slice Part –

network connectivity is established between them

End-to-end slice topology as well as available service

components are propagated

A service function chain request can be submitted to the

higher level MANO that will perform the full service

orchestration on the end-to-end Slice

S1

End-to-end Slice

MOBISLICE/5GNETApp Workshop

Interworking of MANO systems: proof of concept

• Higher-level MANO: 5GEx orchestration system

• Lower-level MANO(s): SONATA Service Platform(s)

• On-demand instantiation of the VLSP (Very Lightweight Network & Service Platform for SDN Environments) lightweight VIM

• Newly implemented DC Slice Controller

• Simple Service function chain (forwarding) deployed on the created end-to-end slice (emulation in a single DC)

Content

• Context and introduction• Slicing Concepts• Interworking Management and Orchestration systems• Concluding Remarks

MOBISLICE/5GNETApp Workshop

• Different segments of a 5G SP’s infrastructure – from the edge cloud to the central DC – administered by separate divisions

• MANO systems configured in a north-south way – a hierarchy of service provisioning capabilities for the deployment of the end-to-end services

• Each domain can be managed independently of the others – but they need to be combined to form slices

• Slicing can provide a more effective resource management by partitioning resources, instantiating different VIMs on-demand and isolating services with different requirements

Concluding Remarks

MOBISLICE/5GNETApp Workshop

Questions?

email: francesco.tusa@ucl.ac.uk

Thank you!

MOBISLICE/5GNETApp Workshop