NFV Transformation


The NFV Challenges


Network Function Virtualization (NFV) is a critical technology that is driving the transformation of Telecom Networks.
The vision of NFV is to move Telecom Application Software from vendor-specific platforms, to run as pure software applications, (Now called Virtual Network Function, VNF) on top of one or a few instantiations of shared cloud infrastructure.

It is this cloud infrastructure we call "Network Function Virtualization Infrastructure" (NFVI). NFVIs are today typically based OpenStack cloud management SW and KVM as hypervisors, eventually moving to Kubernetes and docker containers. An NFVI solution is a quite complex solution, containing SW from between 15 and 20 different Opensource communities, and HW from several different vendors. Solution integration is, therefore, a substantial task, and the resulting Infrastructures can have quite a significant variation both in functionality and performance characteristics.

The above described gives the Operator three new challenges that must be addressed:

  • How can a VNF vendor promise performance/availability/reliability in the RFQ phase, if he has not tested on top of the NFVI that will be used?
  • When a VNF doesn't perform, how to handle middleman position between NFVI and VNF vendor?
  • How to handle the life cycle of an NFVI with upgrades and expansions?

Transformation To a Cloud Architecture





Testing, verification, procurement or Life Cycle Management, our focus is always on the demarcation point between the NFV infrastructure and the VNFs.