We need you! 25+ new participants are needed to meet our goals for the ZOOM project. Join the project and change the future of the communications industry.
The ZOOM project is off and running with nine work streams identified for the first phase of delivery. This is critical work for our industry – it is what will unlock the value of NFV across the entire value chain. ZOOM is a very ambitious project that is absolutely relying on members like you to step up and staff the efforts.
Your contribution can be large (lead a work stream), small (review documents) or somewhere in between (contribute to one or several of the work streams – most people participate at this level.) To learn more and to get involved visit the NFV/SDN/Virtualization community or contact Dave Milham of TM Forum directly.
The ten work streams of the project are described below.
1. Blueprint and Roadmap for ZOOM Operations and Management
The Blue Print /Roadmap describes the migrations steps to evolve from today’s operations infrastructure to operations for virtualized infrastructure covering primarily operations management but supporting exemplar NFV functional roadmaps. This work is highly dependent on developing a list of user stories and use cases as described in the next item below. The Blueprint is a about recording the implications of those priorities in easy to assimilate Roadmaps with clear steps along a migration path. Initial Dates:
- Outline contents end March 2014
- First draft based on User Stories and initial priorities End April 2014
- Second draft consolidating TM Forum Live Nice End June 2014
2. User Stories / Use Case Analysis
Given that NFV and SDN are disruptive, the ZOOM program needs to prioritize User Stories /Use Cases that move towards DevOps from a SysOps and NetOps starting point and are used to underpin the Blueprint/ Roadmap. Both business and technical aspects of: design, deployment, and operation of NF and VNF-based services. Initial Dates:
- Comprehensive List of DevOps centric User Stories End March 2014 to prioritize technical and Catalyst work.
- Preliminary prioritization of User Stories End March 2014
- Second iteration .Updated Requirements linked to User Stories ZOOM Principle and available SDO assets End April 2014
3. Zoom /NFV Information Model based on SID Information Model
Early ZOOM discussions have identified the need for a simple common industry Information model covering both business and resource concepts – i.e. the SID, This is a critical need to ensure that near real time operations can be achieved with low integration cost with the required degree of automation between legacy applications and also new VF based services. This deliverable comprises:
- The modeling of the concepts introduced by NFV (e.g. VNFs, Network Service and VNF forwarding graph)
- A simple service information model as a subset of SID focused on service and resource models for virtualized resources: network, compute and storage. A specific focus is the service chaining model requirements across VF and legacy resources.
- Definition of an integration model and metamodel for combining models from multiple sources based on a technical study recommending best technical approach to integrating multiple models into SID.
- Create SID extensions for a simple service information model leveraging TR 3GPP, CIM and catalysts. First draft End April 2014 Final draft End Dec 2014.
4. Zoom Management and Orchestration
Define a management and orchestration architecture for ZOOM
- SID gap analysis to ETSI MANO work
- Define SID extensions to represent the architectural entities defined above
- Create SID extensions mapping the above to at least one Nice Catalyst
- Create SID extensions for a simple service information model leveraging 3GPP, OpenDaylight, OpenStack, and Nice Catalysts.
- Updated SID model and Technical report on SID extended model based on catalysts and example mapping of the proposed model to a specific version of OpenStack.
- Gap analysis. End March 2014
- SID Extensions in #2, Interim. End April 2014
- SID Extension in #4. Interim End May 2014; Sept 2014; Final Dec 2014
5. Future OSS/BSS and NFV Management Architecture
Early ZOOM discussions have identified a number of architectural topics which need to be addressed for both NFV and management of virtualized services that may require evolution of core Frameworx. This Deliverable comprises a technical report covering:
- Need for commonality of component approach for both Management and Control Applications/Functions (move away from separate management control plane notions) and across all virtualized functions, e.g. specifically the NFV Orchestrator or the SDN controller, in operational processes.
- Refine the concept of functional service component, with interfaces and views, required to manage NFV. Ensure an abstract representation of NFV functions as service components using a simplified common information model derived from SID.
- Supports recursive/fractal component model.
- Leads to extensions/enhancements of eTOM, TAM, SID for NFV/SDN, e.g. TAM extensions with relevant functional components of the ETSI NFV architectural framework.
- Describe the component model and input results to DSRA/TAM including representation of the NFV architectural framework functions in the TAM. End April 2014?
- SDO Briefing on Zoom/ NFV Management Architecture program to ETSI NFV + others. Explain the notion of service component as unit of functionality (for deployment) with (dynamic) exposed interfaces. End April 2014
6. SLA Management
Early ZOOM discussions concluded that the TM Forum reports on end to end SLA for Cloud are also relevant to NFV but that some revisions are needed, e.g. changed examples to cover NFV. This deliverable covers:
- Adapting SLA Model to the new NFV actors in the NFV value chain.
- Providing an SLA Management Reference Architecture to Digital Service in Multi-Partners environment NFV-oriented.
- Define new Metrics, KQIs adapted to NFV environment based on Metric Model defined by SID.
- Definition of terminology and impact of NFV.
- Define SLA metamodel, SLA template and SLS template with support for dynamic SLAs.
- Define SLA APIs (may be based on TIP performance management model).
- Draft proposals End April 2014
7. API/ Interface and NFV Management (TM Forum API Reuse)
This work explores the possibility of use the TM Forum existing Interfaces (TIP), and our new Open Digital APIs for ZOOM. The deliverable will be a Technical Report showing:
- Which TIP interface (functions) and Open Digital API are candidates for which NFV MANO Reference Points
- Use of tooling for creating interfaces and API Consoles
- Possible approaches for supporting dynamic interfaces
- API readout for ETSI MANO End March 2014 or upcoming meeting in May in Okinawa.
8. Policy Management for NFV
Initial ZOOM approach for policy:
- Virtualization means management policy needs to be in every function & operates at multiple levels
- Implies that ETSI / ISG / NFV MANO Orchestrator may need a declarative policy approach for its operation.
- Need to support multiple actors setting policy e.g. global and local levels and conflict resolution.
- Policy based systems need to address PDP (Policy Decision Point) and PE (Policy Enforcement) constructs supporting policy validation, policy application, policy execution, policy enforcement, policy decision and policy brokering.
This group will work to Add Policy Management (and security) as an intrinsic part of the Digital Services Reference Architecture service component model and to the SID Policy Model. Initial Dates:
- Draft proposals End April 2014
- Final Proposals End Sept 2014
9. NFV Management Procurement & RFx
The ZOOM group has noted that NFV not only disrupts technical solutions and operations but that it also potential impacts the way service providers procure Network Functions:
- With virtualized function and services, the network resource supply chain is potentially disrupted with different actors providing different parts of the solution.
- Need to create industry awareness so that SPs are ‘NFV ready’ when products hit the market otherwise procurement bottleneck could damage agility.
This group will:
- Develop User Stories for on-boarding pieces of the virtualized network functions, e.g. from ETSI NFV (likely to be several models used).
- Focus on raising industry awareness of the questions and raising industry ‘NFV procurement readiness’.
- Create ZOOM/NFV Procurement guidelines, standard T&Cs for ZOOM / NFV (similar to NGMN / NGCOR),
- Industry awareness — Draft proposal with User Stories End April 2014 Final proposal End Nov 2014 (timed to match TM Forum Live input).
- ZOOM/NFV Procurement guidelines, Draft end July 2014 final End Dec 2014
10. Security Fabric /Frameworks for ZOOM NFV Management
Initial ZOOM discussions have identified a gap that Functional Service component based frameworks – especially those that are composed – need an underpinning security architecture.
- Define a cross cutting security framework that allows a component based ZOOM frameworks to have a consistent security capabilities; define this as a requirement on all ZOOM Components
- Linked to policy framework.
- Supports Privacy for Multi-tenancy.
- Individual user PII Information privacy and access control determined by User.
- Federated ID Management and confidence measures on ID
- Security Framework End Sept 2014
Don’t forget – to learn more and to get involved visit the NFV/SDN/Virtualization community or contact Dave Milham of TM Forum directly. Dates are subject to staffing and review by the working teams as they form and refine the scope of each work item.