D3.1 “Description of protocol and component design”

EXECUTIVE SUMMARY

This description of protocol and component design is the first technical deliverable of the project and is based i) on the ongoing architravedefinition and ii) on a bottom-up component design. The project executionis structured into three agile cycles of architecture, use and business case definitions (plan) – design & implementation (build) – experimentation (measure) – feedback (learn). Correspondingly, the current design’s scope is on key enablers  or multi-provider operation: discovery, value added connectivity control, resource orchestration and SLA management components. Further, our goal was to explore and include pre-existing know-how from UNIFY, T-NOVA, ETICS projects as well and SME products into the preliminary design. It is non-scope of this report to achieve full integration or to define and design the complete set of 5GEx features.

Our design approach is based on a three-fold approach: i) on the topdown architecture design is an ongoing work in WP2; ii) on a bottom-up component-based design building on functional blocks of UNIFY, T-NOVA and ETICS projects and iii) on a gap analysis between the former two. In the case of the gaps, we have again pursued agile approaches with focus on the key enablers, the definition of a simple design and quick prototype implementation to follow.

The main innovations (findings) reported in this document are:

  1.  The specification of multi-domain discovery, bilateral negotiation interface, to exchange resource and catalogues among multi-domain orchestrators, provisioning and assurance methods, and corresponding interfaces for automated end-to-end network service orchestration across resource slices at multiple-providers.
  2. The introduction of resource Slicing as a Service (SlaaS) – a new multidomain business interface for automated service creation – at a multidomain Resource Orchestrator (RO), where an RO is a split of a Network Function Virtualization Orchestrator (NFVO) into a Network Service Orchestrator (NSO) and a RO. Combination of network services and resource slice orchestration.
  3. Enabling multi-domain SLA-management via an Intelligent Monitoring Subsystem design.
  4. The specification of an open-source proof of concept prototype of a fully automated NFV service deployment from an NFV marketplace (based on the open source components developed by the EU FP7 T-NOVA project) to multi-provider NFV Infrastructures (based the open source framework developed within the EU FP7 UNIFY project). This prototype will be provided as a reference implementation and evaluation framework for the community.
  5. The definition of Value Added Connectivity control for transport domains to support distributed NFV applications via “legacy” transit domains in a multi-domain environment.

The current development work is focused on releasing a reference prototype based on our design approach at the end of year one for experiments to be performed over the project European wide testbed. In addition to the reference implementation, the development of existing products such as RedZinc’s VELOX are being upgraded with the concepts
developed within the project as well as to able to interoperate with the 5GEx reference implementation. Multiple implementation efforts are also a useful innovation towards pre-standards validation.

In conclusions, the presented design in components, interfaces and features are aligned with the current architecture design; this includes the definition of multi-provider discovery protocols, multi-provider resource orchestration with (protocol and data model) and SLA monitoring framework.

Future work includes the incorporation of multi-provider Network Service Orchestration (NSO), the detailed specification of the multi-provider NSONSO interfaces and how various business cases and operational policies may apply during secure operations.

In addition, we are envisaging as next steps the completion our first proof of prototype according to the presented design to validate our design assumptions and key value propositions. The plan is to deploy the first prototype into the  sandbox for experimentation. As soon as the first version of the architecture is defined at M12 we will revisit our design. We plan to showcase our first prototype at various public events (e.g., Conferences or the 5G-PPP Global Events in November, 2016) to solicit early community feedbacks.