White Papers

Understanding OPNFV

Issue link: https://read.uberflip.com/i/1344850

Contents of this Issue

Navigation

Page 19 of 144

Understanding OPNFV 19 link from one year to one hour. Telstra's PEN Offering Improved Customer Satisfaction With an agile infrastructure, no one service runs out of resources as each service is dynamically provisioned with the exact amount of infrastructure required based on the utilization at that specific point in time. (Of course, there's still a limit on the aggregate amount of infrastructure.) For example, no longer will mobile end users experience reduced speed or service degradation. Customer satisfaction also improves due to rapid self-service deployment of services, a richer catalog of services and the ability, if offered by the operator, to try-before-you-buy. Reduced Operational Expenditure (Opex) NFV obviates numerous manual tasks. Provisioning of underlying infrastructure, network functions and services can all be automated; even offered as self-service. This removes a whole range of truck rolls, program meetings, IT tickets, architecture discussions, and so on. At a non- telco user, cloud technologies have been able to reduce operations team sizes by up to 4x, freeing up individuals to focus on other higher-value tasks. The standardization of hardware also slashes operational costs. Instead of managing thousands of unique inventory items, your team can now standardize on a few dozen. A bonus to reduced opex is reduced time-to-break-even. This occurs because, in addition to just virtualizing individual functions, NFV also allows complex services consisting of a collection of functions to

Articles in this issue

view archives of White Papers - Understanding OPNFV