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

3 ITU-T Focus Group IMT-2020 Deliverables

• Function Name: No Unnecessary Information - No unnecessary information duplication when
NS/VNFs and the NFVI are operated by different SPs: Information held by an instance of an IMT-2020
system must not create unnecessary duplication or other dependencies. In particular, a IMT-2020
system offering NFV Infrastructure as a service must not hold specific information about the type of
VNFs or network services into which the VNFs are composed. Similarly, an IMT-2020 system of a
client SP composing network services hosted on NFV Infrastructure controlled by another service
provider must not hold implementation details of the infrastructure.

II Service Development Functionality

• Main Function Name: SDK - Service Development Kit: It supports the development of software
running inside the actual infrastructure (i.e., both simple virtual network functions and, more
importantly, composed services) or running inside the service platform (e.g., decision algorithms
about placement or scaling of a service). It also supports the packaging and analysis of services.

II.1 SDK Primitives
• Function Name: SDK: Service Development Kit (SDK) for fast service specification based on a
common and uniform resource abstractions model for connectivity, computing and storage.
• Function Name: Invariant specification methods: invariant specification methods for developers and
corresponding verification and debugging tools for invariant checking and reporting during testing
and operations.
• Function Name: Profiling tools: profiling tools for monitoring and reporting of service performance
and scaling behaviour at run time as feedback to developers.
• Function Name: SDK Packaging: service package that can be handed over to the service platform for
execution. This package needs to describe constituting components (individual NFVs, how the
composition looks like, scaling properties, certificates for authorization, etc.). We define a package
format that describes and encapsulates all such components and that can be processed by the
gatekeeper. Support the developer in two ways. One is a set of editors for the various description
formats (e.g., for service compositions, for placement optimizations logics). The second is the
packaging function, which takes input from the editors, collects all the necessary software artefacts
(e.g., required NFV virtual machine images), and produces a package.
• Function Name: SDK Catalogue Access: support the developer in reusing existing NFVs, services, or
decision logics. It can interface with, query, or browse existing catalogues, e.g., a private one of the
developer, those of the target service platform, or even public marketplaces (like developed by T-
Nova or Murano), possibly handling licensing and payment issues. This is akin to dynamically
installing libraries in scripting languages from public repositories.
• Function Name: VNF Catalogue: The SDK must provide a location to store the different IoT related
VNFs. It should be possible for the VNF developer to add update or delete VNFs from that location.
Using this list the IMT-2020 service developer can compose a complex service. The system shall offer
a VNF catalogue from which the customer can select the desired VNFs.
• Function Name: VNF Scaling metadata: The SDK must allow definition of SLA levels for selected
VNFs, other metadata should be possibly be specified as well, such as when and how the IMT-2020
operator should scale the VNF, as well as the scaling strategy (up/down, in/out). This information
can be used by the IMT-2020 platform to automatically scale the IoT gateways using appropriate
methodologies. The developer should describe in the VNF Descriptor recipes for scaling VNF; VNF
composing the network service have to be able to scale up or down depending of the users’ demand.
IMT-2020 SDK should have the capability to specify different parameters (VM load, BW, latency) to
be used by IMT-2020 Orchestrator for scaling (up or down). The developer should describe in the
VNF Descriptor recipes for scaling his/her VNF.

208