1. The need for Research Projects to adopt emerging Standards and contribute to Standards for Autonomic Future Internet
ECIAO Workshop (Co-located with EWSDN 2014, Budapest) : AUTONOMIC FUTURE INTERNET STANDARDIZATION
AND SDN, NFV & IPv6 IMPACTS WORKSHOP
Unified Standards for Autonomic Management & Control (AMC) of Networks and Services, SDN, and NFV, as complementary emerging paradigms,
and Bridging Research and Standardization Activities
ETSI/NTECH/AFI (Autonomic Future Internet) GANA Autonomic Management & Control (AMC) Reference Model and its integration with SDN and NFV Reference Models
Dr. Ranganai Chaparadza: IPv6 Forum representantive in ETSI AFI; Chair of the Industry Harmonization for Unified Standards Initiative and IEEE Globecom Industry Forum Sessions Chair,
Dr. Tayeb Ben Meriem (Orange): ETSI NTECH/AFI Rapporteur & acting Chair

3. Autonomic Management & Control (AMC) and Automated Management of Networks and Services
*Definition: Autonomic Management & Control (AMC) of Networks and Services: “Autonomic Network Management & Control (includes the notion of Autonomic Networking)” can be expressed in the following way: AMC = Autonomics in the Management Plane + Autonomics in the Control Plane (whether distributed or centralized) AMC is about Autonomics (i.e. control-loops) introduced in the Management Plane as well as Autonomics (i.e. control-loops) introduced in the Control Plane (whether the control-plane is distributed or centralized). A control-loop realizes self-* features (self-configuration, self-optimization, etc). Autonomic Management (Control-Loops, with Learning and Reasoning to effect adaptation) can be contrasted to Automated Management (workflow reduction and automation i.e. automation of the processes involved in the creation of network configuration input using specialized Task Automation Tools, e.g. Scripts, network planning tools, policy generators for conflict-free policies)

4. Autonomic Management & Control (AMC) and Automated Management of Networks and Services
“Control” in AMC is about:
“Control Logic(s)” that realize a control-loop in order to dynamically adapt network resources and parameters or services.
 The control-logics, as a software or a behavior specification, may be loaded or replaced in nodes and network  Notion of Software-Driven Networks or Software-Empowered Networks
From an architecture perspective, a control-loop can be based on
a “distributed model” (for fast control-loops). That means, the logic is embedded in the nodes (Physical or Virtualized).
Whereas, a “centralized model” (for slow control-loops), the logic is embedded (implemented) outside of the node.
Both kinds of control-loops act towards a global goal to ensure a stable state of the network.
A control-logic can negotiate with another control-logic, to realize dynamic adaptation of network resources and parameters, or services, via reference points.

5. AFI Liaisons with diverse Groups in SDOs and Fora
AFI and Broadband Forum (BBF): Autonomicity and Self-Management in BBF Architecture
AFI and 3GPP: Autonomicity and Self-Management Functions in the Backhaul and Core Networks to complement SON in the RAN and also their global synchronization with SON
AFI and NGMN: NGCOR Requirements calling for Autonomics-Awareness in the Management Architecture. Autonomics-awareness is also in NGMN 5G initiative
AFI in Multi-SDO Initiative: AFI to specify Autonomics and Self-Management for various NGCOR Use Cases and the Converged Management of Fixed and Mobile Networks
AFI and TMF (liaison is going to be established on evolution of Information & Data Models as impacted by Autonomics and Self-Management)
AFI and ITU-T SG13: Autonomic Management and Control in FN Architecture and in NGN
AFI and ITU-T SG2, SG15 and : Autonomic Management and Control in NGN and other Architectures, including Network Resilience, Autonomic Fault Management and Recovery
AFI and CAC in the USA and also with NIST: CAC and AFI have regular exchange of invitations and information including invitation to events)
AFI and IEEE (Liaison envisaged, contacts have been established )
AFI and OMG SDN WG (contacts established and a Liaison is to be established )
AFI and NMRG (This Liaison/collaboration can also be formalized like the other Liaisons) 5 5

6. The GANA Reference Model for Autonomic Networking, Cognitive Networking and Self-Management, i.e. Reference Model for AMC
© ETSI All rights reserved

7. AFI GANA Reference Model, and Modularization of logically centralized Control Software (GANA Knowledge Plane)
Decision Elements (DEs) = Centralized and Distributed Control Software Logics (DEs) that operate in different time-scales but interworking harmoniously in realizing autonomic behaviors
DE algorithms imply DE vendor differentiation.
DEs MAY be “loaded or replaced”  notion of “Software-Driven or Software-Empowered Networks” i.e. the broader picture than Software-Defined Networks
MBTS: Model-Based-Translation Service
ONIX :Overlay Network for Information eXchange
3-Levels of Hierarchical Control-Loops demonstrate how Autonomics can be introduced
in architectures.
“Fast Control-Loops” in the Nodes/NEs, while “Slow but network-wide Control-Loops“ should operate in the outer centralized GANA Knowledge Plane (i.e. SDN – Controller & Net-Apps realm) 7 7

8. Impact of SDN on GANA Knowledge Plane Proposal on integrating GANA Knowledge Plane DEs with SDN Controllers, to enable Autonomcity (Approach 1)
GANA Knowledge Plane DEs as second party logic with algorithms that drive an SDN Controller via the API  Using the same Northbound API as Network Application
© ETSI All rights reserved

9. Impact of SDN on GANA Knowledge Plane Proposal on integrating GANA Knowledge Plane DEs with SDN Controllers, to enable Autonomcity (Approach 2)
(2) GANA Knowledge Plane DEs as Modules of an SDN Controller
GANA Knowledge Plane DEs can use the same Northbound API as used by Network Applications
Note: GANA also incorporates concepts from the 4D architecture upon which OpenFlow was founded (see in AFI GANA Spec)
© ETSI All rights reserved

10. Impact of Virtualization on GANA (ETSI / ISG / NFV mapping to be discussed)
Simplified ETSI /NFV / MANO
NFV
Orchestrator
VNF Manager
Virtualized Infrastructure
Manager (VIM)
OSS/
BSS ?
EMS
To be investigated:
Input into GANA
Network Profiles
Introduce GANA Level 2 / 3 DEs
NFVI
Storage HW
Computing HW
Network HW
Virtualization layer
Virtual
Storage
Computing
Network
GANA Level 2&3 DEs can be introduced in Physical node or a Virtual Node/VNF

11. GANA, NFV, SDN combination (Proposal for discussion purpose)
GANA Network Governance Interface
Simplified ETSI /NFV / MANO
NFV
Orchestrator
VNF Manager
Virtualized Infrastructure
Manager (VIM)
OSS/
BSS ?
EMS
To be investigated:
Input into GANA Network Profiles
NFVI
Introduce GANA Level 2 / 3 DEs
Storage HW
Computing HW
Network HW
Virtualization layer
Virtual
Storage
Computing
Network
GANA Level 2&3 DEs can be introduced in Physical node or a Virtual Node/VNF

12. © ETSI 2014. All rights reserved
Research Projects can adopt the Standardized Autonomics-Enabled Architectures that result from GANA Instantiation onto a particular target architecture, and then to peform the following:
Use the Instantiated GANA Functional Blocks and Reference Points for enabling Autonomicity/Self-Management in a target architecture, to specify Autonomic Behaviours within the Management and the E2E Control & Data Plane Architectures
Specify Behaviours of instantiated GANA Functional Blocks (including DEs and their Control-Loops)
Develop the GANA DE algorithms for autonomics
© ETSI All rights reserved

13. GANA Instantiations onto target architectures such as the BBF (Broadband Forum), Mesh, IMS architectures, PTDN, etc
© ETSI All rights reserved

14. Instantiation of GANA onto the BBF Architecture

17. Instantiation of the ETSI AFI GANA Reference Model onto the PTDN Architecture to create an Autonomicity- Enabled PTDN architecture
© ETSI All rights reserved

18. As is being done for other architectures (BBF,Mesh, IMS,etc), the GANA can be instantiated onto the PTDN to create an Autonomics-Enabled PTDN Architecture
See next slides on Guidelines on how to perform Instantiation of GANA Model onto a target architecture to create an Autonomics- Enabled Architecture

19. Guidelines on how to perform Instantiation of GANA Model onto a target architecture to create an Autonomics-Enabled Architecture
R. Chaparadza, Tayeb Ben Meriem, Benoit Radier, Szymon Szott, Michal Wodczak, Arun Prakash, Jianguo Ding, Said Soulhi, Andrej Mihailovic: Implementation Guide for the ETSI AFI GANA Model: a Standardized Reference Model for Autonomic Networking, Cognitive Networking and Self-Management: In the proceedings of the 5th IEEE MENS Workshop at IEEE Globecom 2013, December, Atlanta, Georgia, USA
© ETSI All rights reserved

20. Steps Towards Architectural Enhancements and Autonomic Behaviour Specifications for ANY Architecture
Instantiate Functional Blocks and Reference Points for Autonomicity/Self-Management from AFI’s Reference Model onto ANY Architecture and its Management Architecture
Functional Blocks of the Knowledge Plane (Net-Level-DEs, MBTS, ONIX)
Network-Level-DEs perform the role of Policy-Decision Points (PDPs) and so PDPs can be evolved by the DEs
Network-Level-DEs (in the Knowledge Plane) evolve EMSs or NMSs
ONIX Information sharing/exchange servers facilitate advanced Auto-Discovery
Establish the type of Autonomic Functions (Decision Elements and their associated Control-Loops and Managed Entities) that should be instantiated into what type of Network Elements
How are the Network Elements, EMSs/NMSs enhanced by DEs and the Reference Points instantiated to all the Functional Blocks that are specific to Autonomics/Self- Management
Use the Instantiated Functional Blocks (FBs) and Reference Points for Autonomicity/Self- Management from the Reference Model, to specify Autonomic Behaviours within the Management and the E2E Transport Architecture
Specify Behaviours of instantiated GANA FBs (including DEs and their Control- Loops) 20

21. Panel Session Topics for Discussion
© ETSI All rights reserved

22. Reflections on IPv6 and Autonomic Networking
IPv6 Forum is collaborating with ETSI in TC NTECH AFI WG, following on EC-FP7 EFIPSANS project results on IPv6 & Autonomics : ETSI-IPv6 Forum MoU & work in AFI)
There are new potential work items related to IPv6 and Autonomic Networking that were proposed in ETSI AFI during the ETSI 2013 Future Networks Technologies workshop
It is now necessary for industry to consider linking Autonomic Networking Standardization with IPv6 by launching the proposed new Work Items in ETSI AFI

23. IPv6 and Autonomic Networking Standards
New AFI Work Items are envisaged on the IPv6 Feature(s) Usage Requirements in Autonomic Networks:
Reference: ETSI Future Networks Workshop 2013:
The IPv6 Community can launch the following Work Items envisaged by ETSI NTECH / AFI:
IPv6-Feature(s) Usage Requirements in Autonomic 3GPP and Non-3GPP Mobile Network Reference Architectures;  IPv6 Features that enable the Autonomics
IPv6-Feature(s) Usage Requirements in Autonomic Broadband Forum (BBF) Reference Architecture;  IPv6 Features that enable the Autonomics
IPv6-Feature(s) Usage Requirements in Autonomic NGN/IMS Architecture;  IPv6 Features that enable the Autonomics
IPv6-Feature(s) Usage Requirements in Autonomic TISPAN CDN Reference Architecture;  IPv6 Features that enable the Autonomics
 IPv6-Feature(s) Usage Requirements in Autonomic Wireless Adhoc/Mesh/Sensor network architectures;  IPv6 Features that enable the Autonomics

24. Some Reflections on 5G
There are now a lot of activities around the 5G related Topics, both in Research (in particular) and also in Industry (e.g. NGMN, TMForum / ZOOM, and other Groups)
In regard to 5G, we can observe that the following points are worthy to take note of:
SDN, NFV and AMC will play key roles in the 5G architecture, due to the complementarities of the three paradigms in addressing the dynamics, flexibility in network & service compositions, and intelligence expected in 5G networks
Regarding Autonomics:
5G embedded Autonomic Functions (AFs) are enablers for the edge, backhaul and core network nodes to intelligently, optimally and adaptively provision resources in such a way as to handle the anticipated huge traffic volumes and diversified traffic flows of various requirements that must be transported over the 5G network. Also, advanced Autonomicity in network & services resilience is needed.
In 5G, more advanced Self-Organizing Network (SON) Functions could be envisaged, beyond SON functions already introduced for 2G/3G/4G). Enrichment of SON with advanced Autonomicity/cognitive algorithms/behaviors is also desirable; and also may be desirable is autonomic coordination of SON functions on inter-system interfaces of Multi-RATs and Fixed/Mobile convergence interfaces.