Industry Harmonization for Unified Standards on Autonomic Management & Control of Networks and

Services, SDN, NFV, E2E Orchestration, and Software-oriented enablers for 5G

Report from the Joint SDOs/Fora Workshop hosted by TMForum during TMForum Live 2015 Event

Nice, France (June 4th, 2015) Joint SDOs/Fora White Paper Editors (the contributors list itself will be in the White Paper):

Ranganai Chaparadza (IPv6 Forum & representative in ETSI / NTECH/AFI WG) ; Tayeb Ben Meriem (ETSI /NTECH/ AFI WG); John Strassner (TMForum ZOOM, ETSI NFV, ONF Architecture and Frameworks); Steven Wright (ETSI NFV ISG) — (also invited: TBC); Joel Halpern (Contributor to IETF).

Notes Takers : Ranganai Chaparadza, Tayeb Ben Meriem, Philippe Lalande (MEF),

1. Brief Description of the Joint SDOs/Fora Industry Harmonization Initiative Today the industry is facing serious challenges in bringing about cost-effective and efficient use of the usually very limited human and financial resources for standardization activities pertaining to the growing number of emerging technologies, which are in turn generating numerous topics and requirements that are hard to match against the scarce standardization resources and can only be effectively addressed through efficient SDOs/Fora coordination/harmonization. The industry at large is calling for speeding up coordination of the various standardization groups towards synergies, since various groups are now looking into similar topics and should seek better coordination and reduce redundancies, duplication of work and collisions of standards. There is currently no instrument that enables to capture a holistic view on what is being addressed in which group and how to facilitate coordination of the various groups towards synergies and harmonization of standards. Key SDOs/Fora are now heeding to the call by the industry and international community at large for industry harmonization on standards for emerging technologies, and the need to build effective synergies and coordination across SDOs/Fora, beyond the traditional bi-lateral liaison based approaches, which are no longer effective due to the simultaneous and wide impact of emerging technologies on various SDOs/Fora. Hence this initiative was created by SDOs/Fora in 2014, and it already starts demonstrating the success factors for effective cross-SDO collaboration.

The Initiative on Joint SDOs/Fora Industry Harmonization on Unified Standards for AMC (Autonomic Management & Control of Networks and Services), SDN, NFV, E2E Orchestration of Services and Resources, and Software-Oriented Enablers for 5G, is driven by a joint SDOs/Fora White Paper (to be kept updated and maintained as a living/evergreen document) that is identifying the items requiring harmonization by standardization groups in coordination across various groups so as to unify key standards, reduce “silos”, duplication of work and standards

collisions. AMC is characterized by management & control software-logics that implement closed control-loops that enable dynamic self-management and self-optimization of resources in the network, dynamic network and services policing, real-time and predictive analytics for automated and intelligent management & control operations for network resources, services and parameters. The standards associated with the emerging complementary networking paradigms, namely: AMC, SDN, NFV and E2E Orchestration of Services and Resources, are supposed to be linked by Unified Architectural Frameworks (harmonized) that enable to holistically view the interworking of these paradigms together within a complete network architecture(s). Unified architectural frameworks and standards help systems/products developers, open-source projects, R&D and research projects, to work with harmonized and standardized unified frameworks and standards, so as to provide feedback on implementation experiences to the SDOs/Fora responsible of evolving the frameworks and standards. Also, standards gaps are exposed when relationships between these complementary emerging technologies and their reference models are articulated through a holistic unifying (harmonized) network framework. The NGMN 5G White Paper also specifies on high level the roles SDN, NFV, AMC and E2E Orchestration, should play in 5G networks as complementary software-oriented enablers for 5G, prompting the harmonization of standards for these complementary paradigms to commence as soon as possible. It is now the time to speed up coordination of the various groups towards synergies and working together as industry in ensuring that from architectural principles point of view, on the evolving network architectures and 5G network architecture, the standards associated with these complementary emerging paradigms are supposed to be linked by Unified Architectural Frameworks (harmonized). Bringing together the key stakeholders, and SDOs/Fora, is now critical, and not wait until harmonization increasingly becomes a challenge and costly.

2. Main Outcome from the Joint SDOs/Fora Workshop hosted by TMForum during TMForum Live Event (June 4th, 2015)

x One of the key strong messages from the workshop is that SDOs/Fora need each other and individual groups should seek to complement what other groups are doing by joining this initiative (driven by the Joint SDOs/Fora White Paper and recurring Joint SDOs/Fora workshop) so as to learn on a multi-groups level what to do to avoid collisions in standards and avoid duplication of work. Individual groups should respect the work of other groups and avoid duplicating work that is best done elsewhere in groups that have better competence on specific areas (refer to the presentation by Joel Halpern for details).

x Guidance on how each participant SDOs/Fora should contribute to the joint SDOs/Fora White Paper the topics and ideas of which they think better synergies or harmonization efforts with other groups could be pursued. Editors of the white paper will continue to engage the various groups in soliciting for the inputs.

x The recommendation on publication of the Joint SDOs/Fora White Paper was that there is need to publish the current version as soon as possible via a suitable channel that enables readers to access the white paper online very soon. It was suggested that to avoid unnecessary delays with publication of the first version of the white paper SDOs/Fora should simply be invited to contribute any of the following types of items for now (for the first version of the White Paper) which can easily be added into the paper without modifying the contribution as such: (1) Topics/items the group proposes or thinks are candidate for Cross-SDO collaboration; (2) Use Cases for AMC, SDN, NFV and E2E Orchestration that can be mapped to the Unified Architectural Framework proposed in sections 4 and 5 of this report. This is to avoid incurring an overhead of having to consolidate, analyze and review various input from the SDOs/Fora for “correctness”—a process that may end up unnecessarily delaying things resulting from approval processes. In the next phase (version 2 of the White Paper, i.e. an updated version), the groups will then employ the Template for input proposed earlier. This is because the White Paper is not supposed to be an un-coordinated collection of ‘vision statements’, ‘claims for ownership’ or ‘preemptive roadmaps’ from competing SDOs. Therefore, the Template for use in collecting SDOs inputs might help, and it may be

reasonable to consider trying to edit their inputs after collecting them for better consolidation of the input in the second version of the paper (after publication of first version). The White Paper Editors shall not need to wait for all inputs to be collected, as delayed inputs can be contributed to subsequent versions. After publication of the first version, we then keep updating the White Paper with continuous contributions and updates from the SDOs/Fora, and publish subsequent evolved versions or updates of the White Paper in channels such as IEEE Communications Standards Magazine: Supplement of IEEE Communications Magazine. The introductory short version of the Joint SDOs/Fora White Paper was published by IEEE Globecom 2014: (refer to http://dx.doi.org/10.1109/GLOCOMW.2014.7063423 ). Dissemination of subsequent versions of the White Paper will be through formal channels like IEEE Communications Standards Magazine, but dissemination through the communication channels of the involved SDOs/Fora will also be encouraged, to enable online access by readers. Also, Online Confluence-like for frequent updates and cross SDO collaboration on the White Paper and coordination topics should be considered.

x Introduction (Proposal) of the Unifying (Harmonized) Architectural Framework that combines AMC, SDN, NFV and E2E Orchestration Reference Models (see section 4 of this report, and also in the presentation on inputs compiled from various groups, architecturally consolidated and presented by Ranganai Chaparadza during the workshop).

x Introducing Joint SDOs/Fora PoCs/Catalysts Framework for Use Cases that combine AMC (Autonomics), SDN, NFV and E2E Orchestration, and can be based/mapped/aligned on the Unifying Architectural Framework (see section 5 of this report).

x Other Topics/Items for cross-SDO coordination (as part of harmonization) proposed include Building a Common Information Model(s) and bridging existing non-unified information models; (Meta-)Modeling for Dynamic Policing of Network Services and Resources; Addressing the Challenges in Dynamic Flexible Service Chaining (BBF, TMForum, ETSI NFV, IETF, are some of the groups working on such topic); Taxonomy harmonization on architectural models; APIs resulting from unified frameworks for AMC, SDN, NFV, E2E Orchestration;

x Plans to continuously engage Open Source Projects such as Open Source SDN projects (e.g. OpenDaylight, ONOS, etc.) and Open Source NFV (e.g. OPNFV) as well, such that the Joint SDOs/Fora PoCs/Catalysts to be created (soon) for combined use cases for AMC (autonomics), SDN, NFV, and E2E Orchestration software, can benefit the Open Source communities (see section 5). Also, the PoCs/Catalysts could adopt Open Source components from the various Open Source projects in their work and extend the Open Source code—thereby contributing the added code back to Open Source communities. The workshop also discussed on how to engage Open Source communities such that Open Source projects can find ways to guarantee quality and sustainability in Open Source products that are anchored on standards or are driven or linked to standardized frameworks in SDOs/Fora. As Open-Source and Standardization need to work together, especially for Open-Source projects that are anchored on standards, standardization professionals and software developers now need to understand each other much more, as “software/code” and a “standard” are two different things (refer to Joel Halpern’s presentation for details).

x Regarding engaging Open Source Projects, discussions with OPNFV where initiated during the workshop, and a section dedicated to contributions by Open Source Projects into the White Paper will be added.

x The study performed in the IEEE Communication Standards Magazine article “Standards Collisions Around SDN, by Joel Halpern” and also the study performed in projects like EU-funded UNIFY project, regarding information on what various groups are doing on SDN, needs to also be referenced by the Joint SDOs/Fora White Paper, as the studies augment what the SDOs/Fora are expressing as part of their roadmaps in the White Paper.

x It was also suggested that it would be good to also invite the “Best Practice Movements”, e.g. those doing “landscaping around Clouds, NFV, etc”, to follow the developments in this Joint SDOs/Fora Industry Harmonization Initiative. The question is how to also include the Best Practices centric communities, which do not have the same audience and culture as in SDOs/Fora communities. How can standardization professionals and business/operation people understand each other?

x Groups that were not represented in 2014, like ONF and MEF, managed to join the Joint SDOs/Fora initiative and presented a summary of their roadmaps. ONF also collaborates with SDOs/Fora/Best Practices organizations, and Open-Source communities (e.g. the recently launched OSSDN project) (see more details in the presentation by Peter Feil). MEF also collaborates with SDOs/Fora/Best Practices organizations, and also discussed how their certification program drives adoption (see more details in the presentation by Kevin Vachon). Other groups involved in the Joint SDOs/Fora Initiative from the beginning, such as ETSI NTECH/AFI WG (see more details in the presentation by Tayeb Ben Meriem), ETSI NFV, TMF (details in John Strassner’s presentation) provided their updates. Groups that could not make it to send a representative to the workshop requested to be engaged after the workshop so as to provide their contributions. The role of models in automation, knowledge representation for autonomic management & control was also presented and discussed to a significant depth by John Strassner (see more details in the presentation by John Strassner). Collaboration by the various groups on (Meta-)Modeling for Dynamic Policing of Network Services and Resources as well as other modeling aspects at design time (not at run-time) were also captured as key to addressing design and operation of automated systems that require multi-disciplinary approach to their designs.

x The Joint SDOs/Fora Industry Harmonization Initiative starts preparing for IEEE Globecom 2015, San Diego, California. A request for an Industry Forum Session at IEEE Globecom 2015 for the SDOs/Fora to jointly present the joint White Paper was submitted to IEEE Globecom 2015 IF&E Organizing committee.

3. Status and Executive Summary of the Joint SDOs/Fora White Paper on Industry Harmonization for Unified Standards

The SDOs/Fora are working on a Joint SDOs/Fora white paper that describes the benefits of harmonization efforts between SDO/Fora, industry, and research communities, in working on standards for SDN, NFV, and Autonomic Management and Control (AMC), E2E Orchestration, and Software-Oriented enablers for 5G. The white paper is aimed at capturing the items/topics requiring cross SDO/Fora (Joint-SDO) harmonization efforts by two or more groups in some coordinated fashion (e.g. bilaterally, etc), e.g. taxonomy harmonization on architectural models, etc. The benefits of the industry harmonization efforts reported in this white paper include efficient use of standardization resources (experts and committed time) as well as fostering information sharing and collaboration by SDOs/Fora.

The following are the key points of this white paper:

x Evolve network management. Currently, SDN and NFV do not address the evolution of network management.

x Integrate modern technologies. Currently, SDN and NFV do not address how Big Data, Analytics, and other related technologies can be integrated with network management.

x Better coordination among SDOs/Fora. The actions among interested SDOs/Fora must be better coordinated on how AMC (Autonomic Management & Control) may be used to govern SDN- and NFV-based systems through the unification of associated standardized architectural frameworks.

x More focused interaction between communities. SDOs/Fora must reach out with a single voice to stakeholders and technical experts in the research community and industry to help reduce silos present in architectural frameworks. This will also help promote unified standardized architectural frameworks for adoption by the research community as well as by industry, which will in turn provide SDOs/Fora useful feedback from implementation experiences that are vital to standards evolution.

x Reduce redundant and conflicting efforts (e.g. by addressing the problem of Standards Collisions around emerging technologies such as SDN). Coordination of SDO/Fora interaction will reduce redundancy and reconcile potentially harmful conflicts among different SDOs/Fora that are covering

different aspects of similar standards that are related to SDN, NFV, AMC, and E2E orchestration or services and resources.

x Synergy between SDN, NFV, E2E Orchestration, Software-oriented enablers for 5G, and AMC. There are a number of powerful synergies between SDN, NFV, 5G, and AMC that must be exploited as soon as possible.

x Synergy with R&D programs. There are also synergies required between organizations that are driving R&D programs in Europe, USA, Asia, and other regions, in aligning their intended R&D contributions to standardization to topics and standards gaps identified by the various SDOs/Fora through the white paper.

x Evergreen document. This white paper will be maintained and updated as a living document, for use in communicating harmonization activities to various stakeholders and the global audience. It will be disseminated to various conference platforms, such as IEEE Globecom Industry Forum Sessions.

Executive Summary of what the White Paper covers (the content being compiled):

x Business and technical drivers for AMC, SDN, NFV, E2E Orchestration of Services and Resources x Report on the discussion of problems in standardization of emerging networking paradigms, e.g. the

problem of “Standards Collisions Around SDN”, and how to address the problems x The actions the “Industry Harmonization Initiative for Unified Standards” is now implementing x How a cross-SDO combined approach on AMC, SDN and NFV helps achieve operators’ business objectives x How R&D/Research programs can play a role as key instruments for resourcing Standardization activities

to address topics being put forward by SDOs/Fora x Overview on the AMC, SDN, NFV, E2E Orchestration, as complementary emerging paradigms, and the

related standardization activities x Relationships between AMC, SDN, NFV, E2E Orchestration, and Software-oriented enablers for 5G (with

IPv6 consideration) x The Unified (Harmonized) Architectural Framework that combines AMC, SDN, NFV and E2E Orchestration

Reference Models x Joint SDOs/Fora PoCs/Catalysts Framework for Use Cases that combine AMC, SDN, NFV and E2E

Orchestration, based on the Unified Architectural Framework for the paradigms x How Open Source Projects such as Open Source SDN projects (e.g. OpenDaylight, ONOS, etc) and Open

Source NFV (e.g. OPNFV), can benefit from the Joint SDOs/Fora PoCs/Catalysts projects to be created (soon) for combined use cases for AMC (autonomics), SDN, NFV, and E2E Orchestration software. And how to engage Open Source communities and communicate feedback to Open-Source communities that should help Open Source projects to find ways to guarantee quality and sustainability in Open Source products that are anchored on standards or are driven or linked to standardized frameworks in SDOs/Fora.

x Brief summary of roadmaps by individual SDOs/Fora Groups that are working on SDN, NFV, AMC, and E2E Orchestration of Services and Resources

x How SDOs/Fora can use the White Paper in coordinating on Harmonization of Standards and Unification of Frameworks, Models, etc.

x How harmonization/coordination instruments can utilize the joint SDOs/Fora White Paper to select some items that require harmonization—of which they are able to address by triggering some joint coordination activities or joint-working groups in their groups if and when feasible

x How the Research/R&D Programs working on 5G (e.g. EU Project 5G initiative, USA NSF programs, Korea 5G Forum, programs in Japan, programs in China, etc) can align with the joint SDOs/Fora White Paper by adopting harmonized/unified standardized frameworks on AMC, SDN, NFV, and E2E Orchestration into research projects so as to later provide feedback to SDOs/Fora in terms of PoCs that are based on the standardized and unified frameworks for AMC, SDN, NFV and E2E Orchestration.

x Summary of Items calling for Harmonization or Coordination by two or more groups in coordination. Example harmonization or collaboration items/topics include Unified Architectural Framework for AMC, SDN, NFV, E2E Orchestration; Unified Common Information Models; (Meta-)Modeling for Dynamic Policing of Network Services and Resources; Addressing Challenges in Dynamic and Flexible Service Chaining (a topic being addressed in BBF (mainly), TMForum, ETSI NFV, IETF); Taxonomy Harmonization on architectural models; APIs; Joint SDOs/Fora PoCs/Catalysts projects; and many more topics to be proposed by SDOs/Fora into the White Paper

x Summary of the launched and ongoing Joint SDOs/Fora Harmonization Efforts, Conclusions, and Future Perspectives

4. The Unified (Harmonized) Architectural Framework that combines AMC, SDN, NFV, and E2E Orchestration Reference Models

The following figures are snapshots of the main diagrams pertaining to the Unified Architectural Framework for AMC, SDN, NFV and E2E Orchestration of Services and Resources, put forward and discussed during the workshop. They serve as a starting point for harmonization on these complementary paradigms, as the unification enables to holistically view the interworking of these paradigms together within a network architecture(s) model. This means that the reference points and characteristic information flow on the reference points will need to be discussed further so as to refine or modify the framework where necessary and provide more detailed specifications of the harmonized/unifying interfaces of the Functional Blocks (FBs).

Detailed descriptions can be found in the source contributions from the SDOs/Fora and detailed descriptions will also be included in the White Paper.

Repository also includes “Service, NFV and Infrastructure Description”

GUI/Editor for Editing Service Definitions/ Descriptions; Service Chaining with PNFs & VNFs; Configuration Data

VNF

EMS

VNF

EMS EMS’s (vApps)

OSS/BSS

Universal (E2E) Service Orchestrator e.g. MEF LSO + Other Functionality (for completeness)

(including Lifecycle Service Management)

NFV Orchestrator

(ETSI NFV MANO Component)

VNF Manager

(ETSI NFV MANO Component)

VIM

(ETSI NFV MANO Component)

Traditional NMS/EMS

SDN Framework (Hybrid SDN)

(Hybrid SDN: Multi-Protocol Southbound Interface(s) and Multi-APIs Northbound

Interface(s)) Federated SDN Controllers (multiple instances)

VNFs (vApps)

NFVI (Network Functions Virtualization Infrastructure):

ETSI NFV

Repository/Catalog/ Inventory/

Data Analytics

Cloud Management

Systems (CMS)

(Cloud Orchestrators)

ETSI NFV

Network Infrastructure, which includes physical functions such as legacy PNFs

(physical NEs)

External/Internal Customer Self-Care/Self-Service Portal

GANA Software modules for Autonomics/ Analytics

ETSI NTECH AFI GANA Software components for Autonomics/ Analytics for AMC

Virtualized Resources

for Cloud Services

Offerings

Managed Resources

Figure 1: The main Functional Blocks (FBs) required in hybrid networks with Telco-Cloud Platforms, Cloud-Based Service Offerings, and Innovation with Autonomics Algorithms for Management & Control

The Functional Block “ETSI NTECH AFI GANA Software” and its relations to the other Functional Blocks (FBs) is elaborated on the next figure (Figure 2).

Figure 2: Enabling “Advanced Management & Control Intelligence” at various Layers of Abstraction through Autonomic Management & Control (AMC) Software

SDN Controller

(Hybrid SDN: Multi-Protocol Southbound Interface and Multi-APIs

Northbound Interface, and the Controller “may” be capable of

controlling both physical & virtual elements (e.g. physical and virtual

switches))

NFV Orchestrator

GANA Knowledge Plane (KP) – With Network Analytics/Autonomics Algorithms for AMC Software

Monitoring Data Collector (1)

Cognitive Algorithms for Analytics, Knowledge

Derivation, Representation and Presentation to the

GANA KP

Monitoring Data Collector (n)

Cognitive Algorithms for Analytics, Knowledge

Derivation, Representation and Presentation to the

GANA KP

Monitoring Tools, Platforms, Probes

(Feed Data to Collectors)

Multi-Protocols SBI: OpenFlow, NETCONF, SNMP, PCEP, OVSDB, TR069, BGP, etc

Modular, Loadable, Evolvable or Replaceable GANA Network-Level Decision Elements/Engines (DEs) implement Autonomics Closed Control-Loops. [i.e. DEs can be replaced by DEs that exhibit better algorithms]

OSS

Big-Data Applications for Analytics-Driven

Orchestration

Universal (E2E) Service Orchestrator e.g. MEF LSO + Other

Functionality

Network infrastructure

ETSI NFV MANO Interfaces

Figure 3: The core part of the unifying framework for AMC, SDN, NFV, E2E Orchestration, Big-Data driven analytics (the KP being space for Innovation with algorithms for AMC)

Figure 4: FOCALE Principles and other principles validated in various research projects on autonomics can be applied to designing DE internal logic

The following Table provides a summary of the Mapping of ETSI NTECH AFI GANA Model for Autonomics/AMC to ETSI NFV MANO

5. Joint SDOs/Fora PoCs/Catalysts Framework for Use Cases that combine AMC, SDN, NFV, and E2E Orchestration, and can be based (mapped onto) on the unifying architectural framework

The SDOs/Fora have decided to introduce a Joint SDOs/Fora PoC/Catalysts Framework for Use Cases for AMC as well as Use Cases that combine AMC, SDN, NFV, and E2E Orchestration, to be based on the harmonized/unifying architectural framework being put forward by the Joint SDOs/Fora Industry Harmonization Initiative. The SDOs/Fora agreed to collaborate on joint SDOs/Fora PoCs/Catalysts projects for Use Cases that combine standardized components for AMC, SDN, NFV, and E2E Orchestration by adopting and extending PoCs/Catalysts that are currently running or were completed in ETSI NFV ISG, TMF ZOOM, MEF, ONF, and any other groups that have been driving PoCs on emerging technologies. Procedures on how to leverage and extend PoCs/Catalysts in the various groups through a call for proposals under a Joint SDOs/Fora collaborative PoCs/Catalysts framework are to be defined and communicated to the various SDOs/Fora groups interested to participate in the activities and projects. On this basis SDOs/Fora and member organizations can start making PoCs/Catalysts proposals.

6. List of SDOs/Fora, Open-Source Projects, and 5G R&D Program, invited to the Joint SDOs/Fora Industry Harmonization Initiative and Workshops

x SDOs/Fora: TMF, ETSI / ISG / NFV ISG (e.g. EVE Group), NGMN, IPv6 Forum, BBF, ETSI / E2NA / NTECH / AFI, MEF, ITU-T SG13 & SG2, IEEE NGSON, OMG SDN WG, OGF, NIST, ONF, 3GPP, OIF, ITU-T JCA, OMA, TSDSI (regional SDO in India), CCSA (regional SDO in China), Multi-SDO, ITU-T JCA-SDN, IEEE SDN and NFV ET subcommittee, any other groups interested to join)

x Open-Source Projects: Open Source Projects such as Open Source SDN projects (e.g. OpenDaylight, ONOS, etc.) and Open Source NFV (e.g. OPNFV), any other open source projects interested

x Research/R&D Programs working on 5G: EU 5G initiative, USA NSF programs, Korea 5G Forum, programs in Japan, programs in China, any other relevant programs of interest. Such programs can adopt and align with the Joint SDOs/Fora White Paper in order to shape their contributions to standards accordingly, while at the same time, adopting Unified Standards and Architectural Frameworks produced by the Joint SDOs/Fora collaborations, so as to provide useful feedback on PoCs implementation experiences to the SDOs/Fora that maintain and evolve the standards/frameworks.