In this blog post we describe the workflow followed by the 5GTANGO’s Validation and Verification Platform (VnV) to validate and verify the network services as a mechanism to improve their quality and their availability.

This entire VnV process is performed by the following four roles:

  • Developer: develops, tests, publishes network services.
  • Operator: selects, tests, deploys existing network services.
  • VnV Platform: provides testing environment, develops and executes tests, check the functional and non functional test conditions that need to be passed by the services.
  • Catalogue: stores network services and metadata, offers decision support.

Creating Test Plans

The packages are created via the 5GTANGO SDK resulting as:

  • Service package: includes all the Service components such as VNF and NS descriptors, SSM/FSM plugins, etc.
  • Test package: includes the Test descriptor that contains the test probes definition, the relation with the services to test and the conditions to
    validate and verify.
  • Service and Test package: includes both service and test related

The Test Plan creation can be generated in two ways:

  • uploading a package: once a package is uploaded in the VnV Catalogue, a test request is automatically generated to validate and check the package
    content (service, test or both).
  • requesting a test via VnV portal: the operator can request a test of the already uploaded Tests and Services.

With the test request information, the VnV platform obtain from catalogue the information about service and test that needs to execute, scheduling a new test

Executing Test Plans

Once the scheduled test starts, the VnV platform performs the Service instantiation in the Service Platform. 5GTANGO’s VnV can instantiate services in
these three types of service platforms: Sonata, Open Source MANO (OSM) and ONAP.

With the Service Instance ready, the VnV already knows the service parameters which will be used by the Test probes. So, VnV can instantiate the Test Probes,
containerized docker images that execute functional and/or not functional tests against the instantiated services, collecting the interchanged information.

Validating and Verifying the Test Results

The gathered information is reviewed to check if the conditions defined in the test descriptor are fulfilled by the tested service. The conditions can be:

  • validation conditions: steps that need to be passed to determine if the service meets their needs and goals (“the service does what it is supposed
    to do).
  • verification conditions: steps that need to be passed to determine if the service meets their specifications (“the service does something how it is
    supposed to do it”).


“Building the right service” vs “Building the service right”

Storing Test Results

The final results are stored in the Test Results Repository for later retrieval by the end user, the Monitoring Manager or the Analytics Engine, the component
responsible to provide insights for efficiency of the VNFs and NSs with regards to resources usage and performance aspects, producing analysis outcomes.

Restoring the Testing Environment

Once all the tests are executed and the results are stored in the repository, the last step is to provide a final cleanup of the environment:

  • Network Service is removed from the service platform, releasing the used resources.
  • Testing Probe container is removed from the VnV host, maintaining their volumes and the stored data.


We use cookies to facilitate navigation and improve your experience across our website. By clicking "Accept", you will be storing these cookies.