Telecom IQ
Showing results for 
Search instead for 
Did you mean: 

NFV Management and Orchestration: Monetization using Multi-tenancy and Quota features



Everyone knows that OpenStack has been developed to share resources using multiple compute, storage and network nodes but did you know that Management and Orchestration (MANO) is one of the most important frameworks as defined by ETSI in their model to be responsible for the management and orchestration of all resources in the cloud data center and there are important features to be monetized?

With the NFV concept created a few years ago allowing you to centralize services and also share resources among customers has helped to reduce some costs but has been hard to monetize the Management and Orchestration part.

Customers have paid for the service in full instead of on-demand use for network services. For example, billing for a network service as Internet/VPN Service is very similar to residential TV service at home where we pay a full service independently if a setup box is on or off because the rate is based on number of channels or package selected by the user.

With that being said, how can the management and orchestration of multi-tenancy and quota features help customers pay for service on-demand and increase the Return of Investment (RoI) for Communication Service Provider (CSP)?

Virtualized Infrastructure Manager (VIM) introduced the concept of tenants to allow CSPs to separate the resources among customers blocking the communication between them but the tenant feature at VIM layer may not be enough to create a monetization because NFV Orchestrator and VNF managers also should support the concept of tenancy and quota to create an environment ready for monetization. If NFV Orchestrator and VFN managers are deployed in a NFV Solution, CSPs can easily create services and charge for it when all NFV components are synced using the same features.

For example, CSPs could be able to charge end customers per resource utilized, and the multi-tenancy will allow the customer to access the system in real-time to initiate new services.

Given access to the customers, CSPs could establish a quota per end customer as a flat rate fee to make sure the hardware will be reserved whenever it needs to be used and a fee per resource utilized. If NFV Orchestrator does not provide a multi-tenancy and quota feature, CSPs will need to use these features directly at VIM layer bringing more complexity to get the system ready for monetization.

For example, reservation and quota fees would be very similar to our electrical fees because we normally pay a flat rate fee to have a service and additional fee is paid per Kwh consumed during the month. Then, NFVO with support to Multi-tenancy and quota will allow CSPs to provide the service similar to our commodities services.

Also, there are network services that require a premium infrastructure to support a high demand of CPU, high bandwidth utilization and so on, then it is very important that the NFV Orchestrator is able to manage the Enhanced Platform Awareness features (EPA) such as SR-IOV, CPU Pinning…to provide the right resources to the network services and give the ability to the CSPs to charge the customers per specific feature utilized.

Do you think is a trend to charge end customers per resource utilized for network services? Please, do not hesitate to post your comments.

Please feel free to check our webpage regarding HPE solutions for NFV, including NFV Orchestrator and VNF Manager (

Want to learn more? Follow us on Twitter at @HPE_NFV & @HPE_CSP

hpe.com_csp_nfv.png CSPResources.jpg NFVResources.png @hpe_csp.jpg @hpe_nfv.png

Juliano Forti
0 Kudos
About the Author


HPE Sr. Product Manager working in product definition and go-to-market strategies for NFV Orchestrator and VNF Manager. 16 years’ experience working as a Product Manager, Systems Engineer in Enterprise and Service Provider Networks, and with extensive market knowledge of data center, service provider and enterprise networking.