Jump to: navigation, search

Gluon/User-Story

< Gluon
Revision as of 17:15, 22 April 2017 by Bh526r (talk | contribs) (New Telco NFV Services)

New Telco NFV Service and User Story

New Telco NFV Services

Network Function Virtualization (NFV) uses the technologies of IT virtualization to virtualize entire classes of network node functions into building blocks that may connect, or chain together, to create communication services. NFV relies upon, but differs from, traditional server-virtualization techniques, such as those used in enterprise IT. For example, NFV traffic is typically pass-through and high throughput so that VNF (Virtualized Network Function) can provide high performance networking function. On the other hand, in case of enterprise IT and cloud, networking is never a bottleneck, and interoperability and API stability is key to those SaaS and PaaS.

The key driver of NFV is the need from Telco Service Providers to accelerate the deployment of new network services to support their revenue and growth objectives.

Because of the objectives and driver of NFV which is different from traditional enterprise IT and cloud, Telco Service Providers has been providing various NFV platforms globally, for example, AT&T ECOMP, China Mobile NovoNet, etc., and related open source platform Open Networking Automation Platform (ONAP).

The key feature that is common to various NFV platform is the separation of design environment and execution. And the key function is the capability to automate the API generation of new NFV Networking Services across multiple backend SDN Controllers so as to enable Telco Service Providers to speed up deployment and accelerate time-to-market.

User Story

The following Epic User Story describes the high level scenario of quick deployment of a new NFV Networking Service:

  1. AS AN Telco Service Provider ROLE TYPE
  2. I NEED TO have my Newly Innovated NFV Service loaded, executed and scaled on-demand on NFV Platform
  3. SO THAT I CAN deliver Newly Innovated NFV Service to my global customers at runtime, on-demand, within one day
  4. TO DO THIS, I NEED
    1. A Design Environment to model the Newly Innovated NFV Service with a user-friendly studio / GUI tooling
    2. A "Modeling Language" to describe the Newly Innovated NFV Service after it is designed in Design Environment
    3. A "Interpreter Tool" to read the model file of Newly Innovated NFV Service described in the "Modeling Language", and generate necessary elements for "Runtime Environment"
      1. The elements include, but not limited to, "API Endpoints", "Database Schema", etc. for Newly Innovated NFV Service
    4. A "Runtime Environment" to load the elements of Newly Innovated NFV Service, execute it, and scale it whenever necessary to serve global customers with Newly Innovated NFV Service.

This “Epic” User Story applies to "any" ""Newly Innovated NFV Services"" in the future.