NFV is really three pieces

NFV is really three pieces; the virtual network functions (VNFs) deployed to create service features, the NFV Infrastructure (NFVI) that serves as the platform for hosting/connection of the VNFs, and the management/orchestration (MANO) functions that do the deployment and management. The goal of all of this is to create a framework for deploying service logic in an agile way on a pool of virtualized resources.”
Tom Nolle on his blog.

Linux Foundation launched a working group (Open Platform for NFV) in conjunction with the NFV ISG (Network Function Virtualisation Industry Specifications Group). OpenStack has also officially launched a team that will aim to deliver to NFV specifications.

There is also a third player in the NFV standards / recommendations implementation space – specifically the MANO piece. TM Forum has introduced a new project, which it has called ZOOM (Zero-touch Orchestration, Operations and Management). ZOOM is the TMF’s approach to considering the long-term implications of NFV rather than looking at the shorter-term migration steps for current OSS/BSS.

ZOOM is apparently looking to draw insights from a broader perspective than just traditional operators. It is specifically seeking insights from the tripods discussed in this recent post.

If this article was helpful, subscribe to the Passionate About OSS Blog to get each new post sent directly to your inbox. 100% free of charge and free of spam.

Our Solutions

Share:

Most Recent Articles

No telco wants to buy an OSS/BSS

When you’re a senior exec in a telco and you’ve been made responsible for allocating resources, it’s unlikely that you ever think, “gee, we really

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.