NECOS keynote at the UFRN Telecomday 2019.

1. NECOS Project: Lessons Learned and Vision
Towards Deeper Cloud Network Slicing
http://www.h2020-necos.eu
UFRN Telecom Day
Centro de Tecnologia UFRN
1st November 2019
1
Prof. Augusto Neto
DIMAP/PPgSC - UFRN
augusto@dimap.ufrn.br

2. Agenda
• https://youtu.be/8l9mzVf48oM
• Context and Motivation
• NECOS Approach: Lightweight Slice Defined Cloud (LSDC)
• Results & Achievements
• Key Value Proposition & Concluding Remarks
2

3. Networking Context & Trends
3
L1-L5SpecializedHardware
L5-L7ClosedH/W
withembeddedS/W
L2 - L7
Software:
Components
and platforms
on
General
purpose
Hardware
L1 Hardware
2. Softwarization
3. Dynamic Interaction between groups of communication, compute, storage and network
services/applications elements/devices in all network segments (edge, core, wire/wireless access, space)
4. Cross Layers new requirements /characteristics: different and very stringent non-functional requirements
including the strict low latency and high data exchange requirements and guaranties for KPIs and/or SLA
characteristics per parts of the infrastructure (SLICES).
1. 5G+ is an integrated, highly automated and intelligent infrastructure (communication, compute, storage and network
services/applications paradigm), which contain a number of operational domains in all network segments (wire/wireless access,
core, edge, space or mixture of segments) , that may be accessed by a user from one or more locations.

4. Network Services Evolution
4
• Delivery of stringent KPIs / SLAs per service (e.g. Gbps Tbps,
less than 20 ms for round trip latency)
• Guarantees and monitor mission critical services;
• New Telco Precision Service Cloud, Industrial Internet Services,
Hologram as a Service, New Secure Network Services
• Integration at Hyper Scale of elements for service de livery (i.e.
network devices, network (virtual) functions, edge elements
and digital objects)
• Agility & Programmability (service functional change on
demand)
• Anonymity and security support for all service operations

5. 5
Infrastructure
Web
Multimedia APPs
Connectivityfor
Everything
Abundant
Bandwidth
everywhere
Critical CommunicationServices
Extreme and
Stringent QoS/
SLA
Secured/
Trusted
Network
Services
Industrial
Internet
Services
New Media /
Hologram
as a Services
New TelcoCloud
as a Service
Present Digital Network Services 2020-2030 Network Services 2030 AndBeyondNetworkServices
Network
Services
Evolution
Evolution
Evolution
`Tactile
Network
Services
Network Services Evolution

6. 6
Academia
ONF
3GPP MEF
ETSI
IETF
What is a Slice?

7. NECOS Drivers
Driving issue
It is inefficient and expensive to build a separate infrastructure for
each service.
The NECOS project
Vision
Services delivered through Slicing will become the new norm
across resource types and administrative multi-domains cloud
networks as the way to deliver service specific KPIs.
Approach
Take the resource sharing paradigm to the next level of resource
sharing as a service. 7

8. Novel Enablers for Cloud Slicing
NECOS

9. Novel Enablers for Cloud Slicing
NECOS

10. What is a cloud network slice?
Once upon a time…..
5G PPP Architecture Working Group
View on 5G Architecture (Version 2.0)
From network slicing to cloud network slicing

11. Net App
Net App
NFs
Net App
Net App
L7 Apps
Network
Resources
NIM
Slicing
Application Services
Vertical
Use
Case i
Control & Management plane
Infrastructure
Business (Application & Service) plane
Slicing
Compute
Resources
VIM
Slicing
MonitoringMonitoringMonitoring
VIM-independent Slicing
[Mode 0]
[Infrastructure Slice aaS]
(“Bare-metal”)
VIM-dependent Slicing
[Mode 1] [Resource Slice aaS]
(R) Orchestration
Service-based Slicing
[Mode 3] [Service Slice aaS]
Network Service Orchestration
MANO-based Slicing
[Mode 2] [NFV aaS]
Slicing
S
Vertical
S
Service
iS
Slicing Models & Approaches

12. NECOS Approach:
Lightweight Slice Defined Cloud (LSDC)
• LSDC a novel cloud network approach for Edge and Core that extends the virtualization to all the
resources in the involved networks and data centers, providing a uniform management with
advanced levels of orchestration.
• LSDC usage in
– abstracting, isolating, orchestrating and separating logical
behaviors from the underlying physical network& cloud resources
– creation of logically or physically isolated groups of network & service resources and (virtual)
network functions configurations
– helping adoption and integration of cloud computing in their large networks
– supporting edge devices with low computation and storage capacity
• LSDC cloud network - Differentiated Factors
– The Slice as a Service –- a new deployment model. Grouping of resources managed as a whole,
and that can accommodate service components, independent of other slices.
– Embedded methods for an optimal allocation of resources to slices in the cloud and networking
infrastructure, to respond to the dynamic changes of the various service demands.
– A Management and Orchestration approach making use of methods and artificial intelligence
techniques in order to tackle with the complexity of large-scale virtualized infrastructure
environments
– Making reality of the lightweight principle, in terms of small footprint components deployable
on large number of small network and cloud devices at the edges of the network 12

13. Project Use Cases and Requirements
13
Project addresses the limitations of current cloud computing
infrastructures to respond to the demand of new services, as presented
in two use-cases (UCs), instantiated in a set of scenarios that resulted in
50 elicited functional and non-functional requirements

14. NECOS Project High Level Architecture
14

15. NECOS Architecture and Interfaces
Defining a set of functional components and their interactions.

16. NECOS Information Model
16
Revisited specification of an information model that takes into account the views of the different
stakeholders. Used for designing Client-to-Cloud and Cloud-to-Cloud APIs
NECOS Slice Specification ModelNECOS Information Model

17. NECOS Slice-as-a-Service Model
Slice as a Service Interface Specification:
• the Slice Request Interface
• provides the mechanisms to initiate the instantiation of a Slice
• the Slice Marketplace Interface
• for interaction between marketplace actors to implement
mechanisms for the propagation of resource offerings between
resource domains.
• the Slice Instantiation Interface
• used to allocate resources for each single Slice Part of the Slice.
• the Slice Runtime Interface
• provides functionalities to dynamically modify the resource
allocation and to perform lifecycle operation on a Slice.

18. Slice / Features Selection/ Elasticity
workflows
18
The design ( i.e. internal functions) for the
components of the NECOS architecture and
workflows among these components
necessary to support the slice creation, slice
elasticity and slice decommission are
published in deliverable D6.2

19. 90 secs Video
19

20. Concluding Remarks: 5G+ Networking
Service Adapted
Network Slices
Enabled by
Network Functions
Including NFV
Dedicated ICT Service
Network Slice
High-Precision Service
Network Slice
Mobility Network Slice
Light Weight Smart Network as a Service & APIs – Multi-domain Network
Operating System Facilities: Automation, Autonomicity, Network Abstraction & programmability,
Allocate (virtual) network resources/ slices, Maintain network state, Ensure network Reliability in a multi
domain environment
Management & Control
CORE
Smart Cloud &
Network Fabric
Enabled by
Programmability
EDGEMETRO
Execution
Environment
Node API
Node OS
RADIO
ACCESS
Execution
Environment
Node API
Node OS
FIXED
ACCESS
Execution
Environment
Node API
Node OS
Node API
Node OS
Execution
Environment
Execution
Environment
Node API
Node OS
Execution
Environment
Node API
Node OS
E2E Multi-Domain Orchestrator
E2E coordination, conflict resolution, multi-domain information exchange
Slice Cognitive and Autonomic

21. Q&A
22

22. What do we mean by Cloud Network Slices?
Cloud Network Slice – A set of infrastructure (network, cloud, data center)
components/network functions, infrastructure resources (i.e., managed connectivity,
compute, storage resources) and service functions that have attributes specifically designed
to meet the needs of an industry vertical or a service.
A Network/Cloud Slice is a managed group of subsets of resources, network and service
functions at the data, control, management/orchestration, and service planes at any given
time. The behaviour of the slice is realized via infrastructure slice instances (i.e. activated
infrastructure slices, dynamically and non-disruptively re-provisioned).
– An infrastructure slice is programmable and has the ability to expose its capabilities.
– An end-to-end logical network/cloud running on a common underlying (physical or
virtual) infrastructure, mutually isolated, with independent control and management
that can be created on demand.
– A network slice may consist of cross-domain components from separate domains in
the same or different administrations, or components applicable to the access
network, transport network, core network, edge networks and clouds.
34

23. Types of Slices and Control Responsibilities
Additional viewpoints:
• From a business point of view, a slice includes a combination of all the relevant network & cloud
resources, functions, and assets required to fulfill a specific business case or service, including
management and DevOps processes.
• From the infrastructure point of view, infrastructure slice instances require the partitioning and
assignment of a set of resources that can be used in an isolated, disjunctive or non- disjunctive
manner for that slice.
• From the tenant point of view, infrastructure slice instance provides different capabilities,
specifically in terms of their management and control capabilities, and how much of them the
network service provider hands over to the slice tenant. As such there are two types of slices:
• (1) Internal slices, understood as the partitions used for internal services of the provider,
retaining full control and management of them.
• (2) External slices, being those partitions hosting customer services, appearing to the
customer as dedicated networks/clouds/datacentres.
• From the management plane point of view, infrastructure slices refers to the managed fully
functional dynamically created partitions of physical and/or virtual resources, network and service
functions that can act as an independent instance of a connectivity network and/or as a network
cloud. Infrastructure resources include connectivity, compute, and storage resources.
• From the date plane point of view, infrastructure slices refers to dynamically created partitions of
forwarding devices and servers with guarantees for isolation and security. 35

24. Analysis of the priorities
and relevance of requirements
36
• 50 elicited functional and non-functional requirements
• Analysis based on the Quality Function Deployment (QFD) methodology
developed by Y. Akao.
– For each scenario, we evaluated correlations between the identified requirements and
NECOS Critical Success Factors/NECOS Key Performance Indicators /NECOS Expected
Differentiated Factors (NECOS Characteristics).
– As such, we evaluated how each requirement is contributing to solve/enable each
Project Critical Success Factors/Project Performance Indicators/Project Expected
Differentiated Characteristics as seen from each scenario.
• Analysis Published in deliverable D3.1
0
50
100
150
200
250
300
RF.vRAN.1-Service Level Agreement
RF.vRAN.2-AccountabilityRF.vRAN.3-On-demand slice provisioning
RF.vRAN.34-Isolation of slice provisioning
RN.vRAN.5 -Fairness
RN.vRAN.6 -Fault detection
RF.5G.1-Service Level Agreement
RF.5G.2-Accountability
RF.5G.3-On-demand slice provisioning
RF.5G.4-External control and management of…
RN.5G.5-Isolation of slice resources
RN.5G.6-Fairness
RN.5G.7-Fault detection
RF.vCPE.1-On-demand slice provisioning
RF.vCPE.2-Manageable slice
RF.vCPE.3-VIM-independence
RF.vCPE.4-Bare-metal slice
RF.vCPE.5-Lightweight virtualization
RF.vCPE.6-Elasticity
RF.vCPE.7-Zero touch service provisioning
RF.vCPE.8-Fault detection
RN.vCPE.9-Isolation of slice resources
RN.vCPE.10-SLA monitoring (QoS)
RN.vCPE.11-Low latency
RN.vCPE.12-High throughputRN.vCPE.13-High availabilityRF.Touristic(CD).1-Slice and slice-resource…RF.Touristic(CD).2-Automated Virtual Machine…
RF.Touristic(CD).3-Traffic load-balancingfor…
RF.Touristic(CD).4-Slice resource and service…
RF.Touristic(CD).5-Service planning
RN.Touristic(CD).6-Transparent end-user…
RN.Touristic(CD).7-Heterogeneity handling
RN.Touristic(CD).8-Elasticity
RN.Touristic(CD).9-Resource-efficiency
RN.Touristic(CD).10-Scalability
RF.Touristic(APP).1 Service function chain…
RF.Touristic(APP).2 Resource and user-demand…
RF.Touristic(APP).3 Resource offloading…
RF.Touristic(APP).4 Resource federation and…
RF.Touristic(APP).5 Scalability
RF.Touristic(APP).6 Efficient next-generation…
RF.Touristic(APP).7 Elasticity
RF.emergency.1 Dynamic slice management
RF.emergency.2 Dynamic service definition
RF.emergency.3 Timely slice management
RF.emergency.4 Orchestration
RF.emergency.5 High Reliability
RF.emergency.6 High Availability
RF.emergency.7 High SurvivabilityAverage Score per Aggregated Requirement
NECOS Requirements - Importance in realising Expected DifferentiatedCharacteristics
based on Combining All Scenarios
0
50
100
150
200
250
RF.vRAN.1-Service Level Agreement
RF.vRAN.2-Accountability
RF.vRAN.3-On-demand slice provisioning
RF.vRAN.34-Isolation of slice provisioning
RN.vRAN.5 -Fairness
RN.vRAN.6 -Fault detection
RF.5G.1-Service Level Agreement
RF.5G.2-Accountability
RF.5G.3-On-demand slice provisioning
RF.5G.4-External control and management of the offered slices
RN.5G.5-Isolation of slice resources
RN.5G.6-Fairness
RN.5G.7-Fault detection
RF.vCPE.1-On-demand slice provisioning
RF.vCPE.2-Manageable slice
RF.vCPE.3-VIM-independence
RF.vCPE.4-Bare-metal slice
RF.vCPE.5-Lightweight virtualization
RF.vCPE.6-Elasticity
RF.vCPE.7-Zero touch service provisioning
RF.vCPE.8-Fault detection
RN.vCPE.9-Isolation of slice resources
RN.vCPE.10-SLA monitoring (QoS)
RN.vCPE.11-Low latency
RN.vCPE.12-High throughputRN.vCPE.13-High availabilityRF.Touristic(CD).1-Slice and slice-resource managementRF.Touristic(CD).2-Automated Virtual Machine deployment
RF.Touristic(CD).3-Traffic load-balancingfor content delivery
RF.Touristic(CD).4-Slice resource and service monitoring
RF.Touristic(CD).5-Service planning
RN.Touristic(CD).6-Transparent end-user performance
RN.Touristic(CD).7-Heterogeneity handling
RN.Touristic(CD).8-Elasticity
RN.Touristic(CD).9-Resource-efficiency
RN.Touristic(CD).10-Scalability
RF.Touristic(APP).1 Service function chain orchestration
RF.Touristic(APP).2 Resource and user-demand prediction
capabilities
RF.Touristic(APP).3 Resource offloading between edge, core clouds
and cloud providers
RF.Touristic(APP).4 Resource federation and intelligent multi-
domain orchestration
RF.Touristic(APP).5 Scalability
RF.Touristic(APP).6 Efficient next-generation touristicapplication
performance
RF.Touristic(APP).7 Elasticity
RF.emergency.1 Dynamic slice management
RF.emergency.2 Dynamic service definition
RF.emergency.3 Timely slice management
RF.emergency.4 Orchestration
RF.emergency.5 High Reliability
RF.emergency.6 High Availability
RF.emergency.7 High Survivability
Average Score per NECOS Requirement
NECOS Requirements- Importance in realising Critical Success Factors based on Combining All Scenarios

25. Next Great Challenge: E2E Multi-Domain Slicing
Current wholesale and interconnection services and mechanisms
are not enough in the era of virtualization and programmability
• Vertical customers requesting services that lay outside the footprint of their
primary provider
– How to resolve this?
37

26. Slicing Key Characteristics & Impact
• A managed group of infrastructure resources, network functions and services (e.g.
Service Instance component, A Network Slice Instance component, Resources
component , Slice Capability exposure component).
• Concurrent deployment of multiple logical, self-contained and independent, shared or
partitioned networks on a common infrastructure platform.
• is a dedicated network part that is built on an infrastructure mainly composed of, but
not limited to, connectivity, storage, and computing.
• it is related to an operator that sees it as a complete network infrastructure and uses
part of the network resources to meet stringent resource requirements.
• Supports dynamic multi-service support, many/multi-tenancy and the integration
means for vertical market players.
• NS is programmable and has the ability to expose its capabilities. The behavior of the
network slice realized via network slice instance(s).
• Service customized Network Slices (enabled by NFV) + Smart Network Fabric for
coordinating/orchestration, control of network resource
• Guaranteeing service level for end to end across multiple (administrative) domains
• Flexible customizability
– automation as the way for simplifying the provisioning 38

27. Highlights - Summary
• All performed work is fully aligned to the DoW with
exception of WP5
• Change in the WP5 work focuss (i.e. platform
implementation design) for better alignment with the
rest of WPs with no changes to the WP5 objectives.
39
5
WP1 –> Project Management
WP7 –> Project Impact
WP3 –> Architecture &
components
WP4 –> Information Model
and I/Fs
WP2 –> UCs description& Requirements
WP5 –> Platform design &
implementation
WP6–> PoCs & Validation

28. Change in WP5 work focus
40
Change in the WP5 work focuss for better alignment with the rest of
WPs with no changes to the WP5 objectives
• WP5 was initially conceived to deploy a monitoring an abstraction layer (Task 5.1) and the intelligent orchestration
functionality for the LSDC platform (Task 5.2). Each of these tasks were also associated to the two deliverables of the project,
which adopted names associated to the above referred tasks. Therefore, D5.1 was initially conceived to report the design of
the monitoring framework and policies to be used in the context of the project showcases, and D5.2 to address the
orchestration and other functionalities.
• Nevertheless, at the early beginning of the project we realized two facts. The first fact was that starting any task in WP5
without clear reference architecture, as pursued in WP3, was very difficult and prone to make serious mistakes that would be
hard to revert. The second fact was that WP5 should be aligned with WP6 requirements because the main objective of WP6,
also stated in the DoA, is to showcase the ability of an integrated platform to serve both as a testbed of the integration of the
prototyping results and as a ground for demonstrating the NECOS use cases. The testing and demonstrations needed in WP6
are then requiring the implementation of specific functionality in WP5, likely a subset of functions of those specified in WP3.
In summary, to effectively and efficiently start WP5 we had to wait until WP3 and WP4 work reached a high mature level.
• Despite the limitations exposed above, we decided to start WP5 activity at the early beginning of the project to allow the
development teams to get acquainted with already existing development tools and development modules that could be used
in subsequent stages. By doing this, we could anticipate eventual challenges and make better decisions in the next steps.
• The project has been shaping these initial developments in alignment with the evolution of the NECOS architecture and its
testing and demonstration requirements. As a result of this approach we are able today to show the building blocks of what
we call “proofs of concept” units; in other words, several independent testing and demonstration modules. The platform
development strategy planned up to end of the project is based on two phases. The first phase, which has been reached at the
end of the project year one, is centred on the above-mentioned building blocks. The second phase will be reached at the end
of the project and will consist of the same blocks with augmented functionality or new ones if necessary.

29. Slicing Models & Approaches
Net App
Net App
NFs
Net App
Net App
L7 Apps
Network
Resources
NIM
Slicing
Application Services
Vertical
Use
Case i
Control & Management plane
Infrastructure
Business (Application & Service) plane
Slicing
Compute
Resources
VIM
Slicing
MonitoringMonitoringMonitoring
VIM-independent Slicing
[Mode 0]
[Infrastructure Slice aaS]
(“Bare-metal”)
VIM-dependent Slicing
[Mode 1] [Resource Slice aaS]
(R) Orchestration
Service-based Slicing
[Mode 3] [Service Slice aaS]
Network Service Orchestration
MANO-based Slicing
[Mode 2] [NFV aaS]
Slicing
S
Vertical
S
Service
iS

30. Requirements contributing most(✓) / least (✗) to
realising NECOS Critical Success Factors if a
Scenario is considered in isolation
42
Requirements contributing most (✓ ) / least (✓ ) to realising NECOS Critical Success Fanctors if a Scenario is considered in isolation
Scenario Scenario Scenario Scenario Scenario
Index Requirement ID & Name 5G Networks vCPE Scenario Touristic Scenario Emergency Scenario All Scenaros
1 RF.vRAN.1-Service Level Agreement ✗ ✗
2 RF.vRAN.2-Accountability
3 RF.vRAN.3-On-demand slice provisioning ✗ ✗ ✗ ✗ ✗
4 RF.vRAN.34-Isolation of slice provisioning ✗ ✗ ✗ ✗
5 RN.vRAN.5 -Fairness ✗ ✗ ✗ ✗ ✗
6 RN.vRAN.6 -Fault detection ✗ ✗ ✗ ✗ ✗
7 RF.5G.1-Service Level Agreement ✗ ✗ ✗
8 RF.5G.2-Accountability ✗ ✗ ✗ ✗ ✗
9 RF.5G.3-On-demand slice provisioning ✗ ✗ ✗ ✗ ✗
10 RF.5G.4-External control and management of the offered slices ✗ ✗ ✗ ✗ ✗
11 RN.5G.5-Isolation of slice resources ✗ ✗ ✗ ✗ ✗
12 RN.5G.6-Fairness
13 RN.5G.7-Fault detection
14 RF.vCPE.1-On-demand slice provisioning ✗ ✗ ✗ ✗ ✗
15 RF.vCPE.2-Manageable slice ✗ ✗ ✗ ✗
16 RF.vCPE.3-VIM-independence ✗ ✗ ✗
17 RF.vCPE.4-Bare-metal slice ✗ ✗
18 RF.vCPE.5-Lightweight virtualization ✗ ✗
19 RF.vCPE.6-Elasticity
20 RF.vCPE.7-Zero touch service provisioning
21 RF.vCPE.8-Fault detection
22 RN.vCPE.9-Isolation of slice resources
23 RN.vCPE.10-SLA monitoring (QoS) ✗ ✗ ✗ ✗
24 RN.vCPE.11-Low latency ✗
25 RN.vCPE.12-High throughput
26 RN.vCPE.13-High availability
27 RF.Touristic(CD).1-Slice and slice-resource management ✗ ✗ ✗ ✗
28 RF.Touristic(CD).2-Automated Virtual Machine deployment ✗ ✗ ✗ ✗ ✗
29 RF.Touristic(CD).3-Traffic load-balancing for content delivery ✗
30 RF.Touristic(CD).4-Slice resource and service monitoring ✗ ✗ ✗
31 RF.Touristic(CD).5-Service planning ✗
32 RN.Touristic(CD).6-Transparent end-user performance
33 RN.Touristic(CD).7-Heterogeneity handling
34 RN.Touristic(CD).8-Elasticity
35 RN.Touristic(CD).9-Resource-efficiency ✗
36 RN.Touristic(CD).10-Scalability
37 RF.Touristic(APP).1 Service function chain orchestration ✗ ✗ ✗ ✗ ✗
38 RF.Touristic(APP).2 Resource and user-demand prediction capabilities
39 RF.Touristic(APP).3 Resource offloading between edge, core clouds and cloud providers ✗ ✗ ✗ ✗
40 RF.Touristic(APP).4 Resource federation and intelligent multi-domain orchestration
41 RF.Touristic(APP).5 Scalability ✗
42 RF.Touristic(APP).6 Efficient next-generation touristic application performance
43 RF.Touristic(APP).7 Elasticity ✗ ✗ ✗ ✗
44 RF.emergency.1 Dynamic slice management
45 RF.emergency.2 Dynamic service definition ✗
46 RF.emergency.3 Timely slice management
47 RF.emergency.4 Orchestration ✗ ✗ ✗ ✗
48 RF.emergency.5 High Reliability ✗ ✗ ✗ ✗ ✗
49 RF.emergency.6 High Availability
50 RF.emergency.7 High Survivability ✗ ✗ ✗ ✗ ✗

31. Requirements contributing most (✓) / least (✗)
to realising NECOS Key Performance Indicators if
a Scenario is considered in isolation
43
Requirements contributing most (✓ ) / least (✓ ) to realising NECOS Key Performance Indicators if a Scenario is considered in isolation
Scenario Scenario Scenario Scenario Scenario
Index Requirement ID & Name 5G Networks vCPE Scenario Touristic Scenario Emergency Scenario All Scenaros
1 RF.vRAN.1-Service Level Agreement ✗ ✗ ✗ ✗
2 RF.vRAN.2-Accountability ✗ ✗
3 RF.vRAN.3-On-demand slice provisioning ✗
4 RF.vRAN.34-Isolation of slice provisioning ✗
5 RN.vRAN.5 -Fairness ✗
6 RN.vRAN.6 -Fault detection ✗ ✗ ✗ ✗ ✗
7 RF.5G.1-Service Level Agreement ✗
8 RF.5G.2-Accountability ✗
9 RF.5G.3-On-demand slice provisioning ✗ ✗ ✗ ✗ ✗
10 RF.5G.4-External control and management of the offered slices ✗ ✗ ✗ ✗ ✗
11 RN.5G.5-Isolation of slice resources ✗ ✗ ✗ ✗ ✗
12 RN.5G.6-Fairness
13 RN.5G.7-Fault detection
14 RF.vCPE.1-On-demand slice provisioning ✗
15 RF.vCPE.2-Manageable slice ✗ ✗ ✗ ✗ ✗
16 RF.vCPE.3-VIM-independence ✗ ✗ ✗ ✗ ✗
17 RF.vCPE.4-Bare-metal slice ✗ ✗ ✗ ✗ ✗
18 RF.vCPE.5-Lightweight virtualization ✗
19 RF.vCPE.6-Elasticity ✗ ✗ ✗ ✗
20 RF.vCPE.7-Zero touch service provisioning
21 RF.vCPE.8-Fault detection
22 RN.vCPE.9-Isolation of slice resources
23 RN.vCPE.10-SLA monitoring (QoS) ✗ ✗
24 RN.vCPE.11-Low latency ✗ ✗ ✗ ✗
25 RN.vCPE.12-High throughput ✗ ✗ ✗ ✗
26 RN.vCPE.13-High availability ✗
27 RF.Touristic(CD).1-Slice and slice-resource management ✗ ✗ ✗ ✗ ✗
28 RF.Touristic(CD).2-Automated Virtual Machine deployment ✗
29 RF.Touristic(CD).3-Traffic load-balancing for content delivery
30 RF.Touristic(CD).4-Slice resource and service monitoring ✗ ✗
31 RF.Touristic(CD).5-Service planning
32 RN.Touristic(CD).6-Transparent end-user performance
33 RN.Touristic(CD).7-Heterogeneity handling ✗
34 RN.Touristic(CD).8-Elasticity ✗ ✗ ✗
35 RN.Touristic(CD).9-Resource-efficiency ✗
36 RN.Touristic(CD).10-Scalability
37 RF.Touristic(APP).1 Service function chain orchestration ✗
38 RF.Touristic(APP).2 Resource and user-demand prediction capabilities ✗
39 RF.Touristic(APP).3 Resource offloading between edge, core clouds and cloud providers ✗ ✗
40 RF.Touristic(APP).4 Resource federation and intelligent multi-domain orchestration ✗
41 RF.Touristic(APP).5 Scalability
42 RF.Touristic(APP).6 Efficient next-generation touristic application performance
43 RF.Touristic(APP).7 Elasticity ✗
44 RF.emergency.1 Dynamic slice management
45 RF.emergency.2 Dynamic service definition ✗
46 RF.emergency.3 Timely slice management ✗ ✗ ✗ ✗
47 RF.emergency.4 Orchestration
48 RF.emergency.5 High Reliability ✗
49 RF.emergency.6 High Availability
50 RF.emergency.7 High Survivability ✗ ✗

32. Requirements contributing most (✓) / least (✗)
to realising NECOS Expected Differentiated
Factors if a Scenario is considered in isolation
44
Requirements contributing most (✓ ) / least (✓ ) to realising NECOS Expected Differentiated Fanctors if a Scenario is considered in isolation
Scenario Scenario Scenario Scenario Scenario
Index Requirement ID & Name 5G Networks vCPE Scenario Touristic Scenario Emergency Scenario All Scenaros
1 RF.vRAN.1-Service Level Agreement ✗ ✗ ✗ ✗ ✗
2 RF.vRAN.2-Accountability
3 RF.vRAN.3-On-demand slice provisioning
4 RF.vRAN.34-Isolation of slice provisioning
5 RN.vRAN.5 -Fairness
6 RN.vRAN.6 -Fault detection ✗ ✗ ✗ ✗ ✗
7 RF.5G.1-Service Level Agreement ✗
8 RF.5G.2-Accountability ✗ ✗ ✗
9 RF.5G.3-On-demand slice provisioning ✗ ✗ ✗ ✗ ✗
10 RF.5G.4-External control and management of the offered slices ✗ ✗
11 RN.5G.5-Isolation of slice resources ✗ ✗ ✗ ✗
12 RN.5G.6-Fairness ✗ ✗ ✗ ✗
13 RN.5G.7-Fault detection ✗ ✗ ✗ ✗
14 RF.vCPE.1-On-demand slice provisioning ✗ ✗ ✗ ✗
15 RF.vCPE.2-Manageable slice ✗ ✗ ✗ ✗ ✗
16 RF.vCPE.3-VIM-independence ✗ ✗
17 RF.vCPE.4-Bare-metal slice ✗ ✗ ✗ ✗
18 RF.vCPE.5-Lightweight virtualization ✗ ✗ ✗ ✗
19 RF.vCPE.6-Elasticity ✗ ✗ ✗ ✗ ✗
20 RF.vCPE.7-Zero touch service provisioning ✗
21 RF.vCPE.8-Fault detection
22 RN.vCPE.9-Isolation of slice resources
23 RN.vCPE.10-SLA monitoring (QoS) ✗ ✗ ✗
24 RN.vCPE.11-Low latency ✗ ✗ ✗ ✗
25 RN.vCPE.12-High throughput ✗ ✗ ✗ ✗
26 RN.vCPE.13-High availability ✗ ✗
27 RF.Touristic(CD).1-Slice and slice-resource management
28 RF.Touristic(CD).2-Automated Virtual Machine deployment ✗
29 RF.Touristic(CD).3-Traffic load-balancing for content delivery ✗ ✗ ✗
30 RF.Touristic(CD).4-Slice resource and service monitoring ✗
31 RF.Touristic(CD).5-Service planning
32 RN.Touristic(CD).6-Transparent end-user performance ✗ ✗ ✗
33 RN.Touristic(CD).7-Heterogeneity handling ✗ ✗ ✗ ✗
34 RN.Touristic(CD).8-Elasticity ✗ ✗ ✗ ✗ ✗
35 RN.Touristic(CD).9-Resource-efficiency ✗
36 RN.Touristic(CD).10-Scalability
37 RF.Touristic(APP).1 Service function chain orchestration
38 RF.Touristic(APP).2 Resource and user-demand prediction capabilities ✗ ✗ ✗
39 RF.Touristic(APP).3 Resource offloading between edge, core clouds and cloud providers
40 RF.Touristic(APP).4 Resource federation and intelligent multi-domain orchestration
41 RF.Touristic(APP).5 Scalability ✗ ✗ ✗ ✗
42 RF.Touristic(APP).6 Efficient next-generation touristic application performance ✗ ✗ ✗ ✗
43 RF.Touristic(APP).7 Elasticity
44 RF.emergency.1 Dynamic slice management ✗ ✗ ✗ ✗
45 RF.emergency.2 Dynamic service definition ✗ ✗ ✗ ✗
46 RF.emergency.3 Timely slice management ✗
47 RF.emergency.4 Orchestration
48 RF.emergency.5 High Reliability
49 RF.emergency.6 High Availability ✗ ✗ ✗ ✗
50 RF.emergency.7 High Survivability ✗ ✗ ✗ ✗

33. Requirements Priority: Requirements - Importance
in realising Expected Differentiated Characteristics
combining All Scenarios (II)
45
0
50
100
150
200
250
300
RF.vRAN.1-Service Level Agreement
RF.vRAN.2-AccountabilityRF.vRAN.3-On-demand slice provisioning
RF.vRAN.34-Isolation of slice provisioning
RN.vRAN.5 -Fairness
RN.vRAN.6 -Fault detection
RF.5G.1-Service Level Agreement
RF.5G.2-Accountability
RF.5G.3-On-demand slice provisioning
RF.5G.4-External control and management of…
RN.5G.5-Isolation of slice resources
RN.5G.6-Fairness
RN.5G.7-Fault detection
RF.vCPE.1-On-demand slice provisioning
RF.vCPE.2-Manageable slice
RF.vCPE.3-VIM-independence
RF.vCPE.4-Bare-metal slice
RF.vCPE.5-Lightweight virtualization
RF.vCPE.6-Elasticity
RF.vCPE.7-Zero touch service provisioning
RF.vCPE.8-Fault detection
RN.vCPE.9-Isolation of slice resources
RN.vCPE.10-SLA monitoring (QoS)
RN.vCPE.11-Low latency
RN.vCPE.12-High throughputRN.vCPE.13-High availabilityRF.Touristic(CD).1-Slice and slice-resource…RF.Touristic(CD).2-Automated Virtual Machine…
RF.Touristic(CD).3-Traffic load-balancingfor…
RF.Touristic(CD).4-Slice resource and service…
RF.Touristic(CD).5-Service planning
RN.Touristic(CD).6-Transparent end-user…
RN.Touristic(CD).7-Heterogeneity handling
RN.Touristic(CD).8-Elasticity
RN.Touristic(CD).9-Resource-efficiency
RN.Touristic(CD).10-Scalability
RF.Touristic(APP).1 Service function chain…
RF.Touristic(APP).2 Resource and user-demand…
RF.Touristic(APP).3 Resource offloading…
RF.Touristic(APP).4 Resource federation and…
RF.Touristic(APP).5 Scalability
RF.Touristic(APP).6 Efficient next-generation…
RF.Touristic(APP).7 Elasticity
RF.emergency.1 Dynamic slice management
RF.emergency.2 Dynamic service definition
RF.emergency.3 Timely slice management
RF.emergency.4 Orchestration
RF.emergency.5 High Reliability
RF.emergency.6 High Availability
RF.emergency.7 High SurvivabilityAverage Score per Aggregated Requirement
NECOS Requirements - Importance in realising Expected DifferentiatedCharacteristics
based on Combining All Scenarios

34. Requirements Priority: Requirements - Importance
in realising Critical Success Factors based on
Combining All Scenarios
46
0
50
100
150
200
250
RF.vRAN.1-Service Level Agreement
RF.vRAN.2-Accountability
RF.vRAN.3-On-demand slice provisioning
RF.vRAN.34-Isolation of slice provisioning
RN.vRAN.5 -Fairness
RN.vRAN.6 -Fault detection
RF.5G.1-Service Level Agreement
RF.5G.2-Accountability
RF.5G.3-On-demand slice provisioning
RF.5G.4-External control and management of the offered slices
RN.5G.5-Isolation of slice resources
RN.5G.6-Fairness
RN.5G.7-Fault detection
RF.vCPE.1-On-demand slice provisioning
RF.vCPE.2-Manageable slice
RF.vCPE.3-VIM-independence
RF.vCPE.4-Bare-metal slice
RF.vCPE.5-Lightweight virtualization
RF.vCPE.6-Elasticity
RF.vCPE.7-Zero touch service provisioning
RF.vCPE.8-Fault detection
RN.vCPE.9-Isolation of slice resources
RN.vCPE.10-SLA monitoring (QoS)
RN.vCPE.11-Low latency
RN.vCPE.12-High throughputRN.vCPE.13-High availabilityRF.Touristic(CD).1-Slice and slice-resource managementRF.Touristic(CD).2-Automated Virtual Machine deployment
RF.Touristic(CD).3-Traffic load-balancingfor content delivery
RF.Touristic(CD).4-Slice resource and service monitoring
RF.Touristic(CD).5-Service planning
RN.Touristic(CD).6-Transparent end-user performance
RN.Touristic(CD).7-Heterogeneity handling
RN.Touristic(CD).8-Elasticity
RN.Touristic(CD).9-Resource-efficiency
RN.Touristic(CD).10-Scalability
RF.Touristic(APP).1 Service function chain orchestration
RF.Touristic(APP).2 Resource and user-demand prediction
capabilities
RF.Touristic(APP).3 Resource offloading between edge, core clouds
and cloud providers
RF.Touristic(APP).4 Resource federation and intelligent multi-
domain orchestration
RF.Touristic(APP).5 Scalability
RF.Touristic(APP).6 Efficient next-generation touristicapplication
performance
RF.Touristic(APP).7 Elasticity
RF.emergency.1 Dynamic slice management
RF.emergency.2 Dynamic service definition
RF.emergency.3 Timely slice management
RF.emergency.4 Orchestration
RF.emergency.5 High Reliability
RF.emergency.6 High Availability
RF.emergency.7 High Survivability
Average Score per NECOS Requirement
NECOS Requirements- Importance in realising Critical Success Factors based on Combining All Scenarios

35. Concepts (VI)
Network Slice Representation
Forwarding Network
Element
Network Slice 1
Tenant A
Control
Infrastructure
Tenant B Control
Infrastructure
Network Slice 2
NF Network Function /
Virtual NF
NF1
NF2
NF4NF3
Network Service
Tenant A
NF1
NF2
NF4NF3
Network Service
Tenant B
Physical Network
EInfrastructure
47

36. Early Definitions of Network Slicing &
References(II)
ITU-T Slicing (2011) as defined in [ITU-T
Y.3011- http://www.itu.int/rec/T-REC-
Y.3001-201105-I] is the basic concept of the
connectivity and compute Softwarization.
Slicing allows logically isolated network
partitions (LINP) with a slice being
considered as a unit of programmable
resources such as network, computation
and storage.
Slice capabilities (2009) “Management and Service-aware Networking Architectures (MANA) for Future
Internet” – A. Galis et all - Invited paper IEEE 2009 Fourth International Conference on Communications and
Networking in China (ChinaCom09) 26-28 August 2009, Xi'an, China,
http://www.chinacom.org/2009/index.html
3 Slices Capabilities
– “Resource allocation to virtual infrastructures or slices of virtual infrastructure.”
– “Dynamic creation and management of virtual infrastructures/slices of virtual infrastructure across
diverse resources.”
– “Dynamic mapping and deployment of a service on a virtual infrastructure/slices of virtual
infrastructure.”
17 Orchestration capabilities
19 Self-functionality mechanisms
14 Self-functionality infrastructure capabilities
48

37. Early Definitions of Network Slicing &
References (III)
NGMN Slice capabilities (2016) - consist of 3 layers: 1) Service Instance Layer, 2) Network Slice Instance
Layer, and 3) Resource layer.
• The Service Instance Layer represents the services (end-user service or business services) which are to
be supported. Each service is represented by a Service Instance. Typically services can be provided by
the network operator or by 3rd parties.
• A Network Slice Instance provides the network characteristics which are required by a Service Instance
A Network Slice Instance may also be shared across multiple Service Instances provided by the network
operator.
• The Network Slice Instance may be composed by none, one or more Sub-network Instances, which may
be shared by another Network Slice Instance.
3GPP TR23.799 Study Item “Network Slicing’ 2016
ONF Recommendation TR-526 “Applying SDN architecture to Network Slicing” 2016
EU 5GPPP
• 30 Large Scale Research projects – all based on Network Slicing (https://5g-ppp.eu) (2015- 2018+)
• White Papers on 5G Architecture centered on network slicing (mark 1 - https://5g-ppp.eu/wp-
content/uploads/2014/02/5G-PPP-5G-Architecture-WP-July-2016.pdf) (2016) (mark 2 https://5g-
ppp.eu/wp-content/uploads/2018/01/5G-PPP-5G-Architecture-White-Paper-Jan-2018-v2.0.pdf)
(2018)
49

38. Infrastructure Slicing Value Chain
• Capability exposure: trough this utilization model, the providers can offer Application Programming
Interfaces (APIs) to the vertical business customers for granting the capability of managing their own
slices. Such management actions can include e.g. dimensioning, configuration, etc.
• Integration at customer premises: complementary network segments, in some cases pertaining to
the vertical business customer, become an integral part of the solution, requiring a truly convergent
network including the integration in existing business processes as defined by the vertical customer.
• Hosting applications: the provider offer the capability of hosting virtualized versions of network
functions or applications, including the activation of the necessary monitoring information for those
functions.
• Hosting on-demand 3rd parties /OTTs: empower partners (3rd parties / OTTs) to directly make
offers to the end customers augmenting operator network or other value creation capabilities.
50