Page 218 - ITU-T Focus Group IMT-2020 Deliverables

3 ITU-T Focus Group IMT-2020 Deliverables

• Function Name: VNF and topology validation: Based on the principle of providing security service,
IMT-2020 service framework by itself, or using third parties, must offer a validation capacity of VNFs
when it is deployed in the NFVI. This validation should cover the integrity of the VNF, user attestation
and data paths case.

IV Service Orchestration Functionality
• Main Function Name: Orchestrator: service orchestrator that maps services to connectivity,
computing, and storage resources and that
• processes the output of the IMT-2020 SDK to generate a resource mapping and composition of a
new service from virtualized building blocks,
• manages the service lifecycle (deployment, operation, modification, termination),
• supports isolation and policing between different virtual services, and virtual service providers.
• Uses abstract interfaces for interoperability with different underlying technologies such as
OpenStack, Apache Cloudstack, OpenVim, OPNFV, etc.

IV.1 Service Orchestration Primitives
• Function Name: VNF Placement: The programmability framework shall allow the customer to deploy
VNFs at arbitrary points into the network and set where the components/ gateways will be placed
on the operator network. For example, deploy a VNF as near as possible to a specific location or
select were the VNF will be deployed.
• Function Name: Manual Service Function Placement: It should be possible to manually decide and
configure where a service is to be placed. This can be very important for services where the service
developer knows that a Service Function has to run in a certain location / on a certain node, but is
either unable to or not confident with defining placement constraints in a way that placement can
be done by the orchestrator. This may be particularly the case in non-carrier verticals where
experience with services may be lacking, deployment are simple, and ease of use is the primary
objective.
• Function Name: SFC: Service chaining - the programmability framework shall allow the customer to
interconnect VNFs in an arbitrary graph.
• Function Name: Service Chaining Support Across Wide Area Networks: The Service Platform must
support service function chains that include service functions separated by a wide area network,
e.g. across different data centres, or between the core data centre and an edge cloud.
IV.2 Resource Orchestration Primitives

• Function Name: Abstract Programming Model: abstract programming models for networked
services, which enable a high level of automation in service development and deployment
processes. Such models refer to the installation of executable code as virtual machines representing
application-specific services components into the hosting elements in order to create the new
functionality at run time - realizing application-specific service logic, or performing dynamic service
provision on demand.
• Function Name: Multi NFVI orchestration: IMT-2020 Orchestrator should be able to orchestrate
multiple VNF execution environments (NFVI-PoPs) located in arbitrary places in the operator
network topology. The NFVI-PoPs are considered to be controlled and managed by VIMs.
• Function Name: Lifecycle Management: The lifecycle management plugin deal with triggering
(groups of) VM start-up, shutdown, … actions in the actual infrastructure; the service
contextualization executive plugin contextualizes VNFs/services via actions provided by the service
description.
• Function Name: Placement and Scaling: The placement and scaling logic executive executes
algorithms that place and scale a running service, both at start-up and continuously (e.g., when load
goes up). While we will provide a fall- back algorithm (based on-going projects), our contribution is
the ability to execute service-specific logics, provided in a service’s description. Challenges here are
e.g. security concerns, which we intend to address by sandboxing approaches.

212