5GTANGO proposes an integrated vendor-independent platform applied to the three pilot scenarios where the outcome of the SDK (i.e., service packages), are automatically tested in the V&V platform and stored in the Catalogue for their posterior deployment with the Service Platform. 5GTANGO system will be demonstrated in three vertical pilots: advanced Manufacturing, immersive Media, and real time Communications.

This post describes the functional and non-functional requirements of the four main functional blocks considered in 5GTANGO: catalogue (data store, decision support and optimization), V&V platform, NFV-enabled SDK, and extended service platform. It aims to provide inputs to derive functions as well as the overall architecture of the system, and to assess the outcomes of work packages with respect to completeness and functional correctness.

Functional Requirements

In software engineering, a functional requirement defines a function of a system or its component. Functional requirements may be calculations, technical details, data manipulation and processing and other specific functionality that defines what a system is supposed to accomplish. A function is described as a set of inputs, the behavior, and outputs. Usually the description also contains a unique name and number, a brief summary, and a rationale.

5GTANGO considers four main functional blocks; catalogue (data store, decision support and optimization), verification and validation (V&V) platform, NFV-enabled software development kit (SDK), and extended service platform to support vertical applications. For each of these main functional blocks, the both functional and non-functional requirements (sacalability, customizability, security, reliability, availability, authentication and confidentiality) have been analysed. As for the functional requiremeents, the following high-level requirements have been identified:


Catalogue

  • The 5GTANGO Catalogue should be offering a repository for persistently storing the developed VNFs/NS.
  • The 5GTANGO Catalogue should be offering support for metadata annotation of stored VNFs/NS.
  • The 5GTANGO Catalogue should be offering support for updating the metadata of stored VNFs/NS.
  • The 5GTANGO Catalogue should be offering interfaces for interacting with other components.
  • By using technologies for the automated analysis of metadata (including V&V metadata, deployment patterns, monitoring information, QoE/QoS parameters, SLAs, policies, etc) the catalogue should enable efficient selection and use of VNFs/NS.
  • By analyzing the updated VNFs/NS metadata (updated based on new information from SLAs, policies as well as monitoring – QoS and QoE data) new V&V tests should be triggered (feedback loop towards V&V) and actions towards the provision of QoS guarantees should be proposed.
  • Different versions of the same item should be present in the Catalogue tracking every change in its entire lifecycle and who made them.
  • It is possible for many instances of the 5GTANGO catalogue to exist at the same time. For the sake of consistency, there should be interfaces for synchronizing the data between those instances.

 

V&V Platform

  • The V&V shall present a set of tools that support test management (including generation,configuration & management), execution, collection and reporting
  • The V&V Platform should be able to instrument and collect the resulting metrics from any tests run
  • The V&V Platform should offer the following interfaces to other 5GTANGO components

 

NFV-enabled SDK

  • Development of service and component tests
  • Development of performance characterisation tools
  • Service- and Function Specific Manager development support

 

Service Platform

  • Support the complete DevOps lifecycle for NS/VNFs, including NS/VNF on-boarding, scaling, (re-) configuration, and updating
  • Support the virtualization of available vertical resources
  • Support of Network Slicing considering resource allocation, service contextualization, and monitoring.
  • Support of carrier-grade functionalities for highly reliable and large scale deployments.

 

Non-Functional Requirements

Non-functional requirement is a requirement that specifies criteria that can be used to judge the operation of a system. The following non-functional requirements have been considered for the 5GTANGO four main functional blocks:

  • Scalability: capability of a system, network, or process to handle a growing amount of work, or its potential to be enlarged to accommodate that growth
  • Customizability: ability of a piece of software to be customized to suit a particular need
  • Security: is the protection of the system from the theft or damage to their hardware, software or information
  • Reliability: the ability of a system or component to function under stated conditions for a specified period of time
  • Availability: the ratio of the total time a functional unit is capable of being used during a given interval to the length of the interval
  • Authentication: is the process of actually confirming the identity
  • Confidentiality: is the non-disclosure of information except to another authorized person