ETSI TS 103 194 V1.1.1 (2014-10)

Network Technologies (NTECH); Autonomic network engineering for the self-managing Future Internet (AFI); Scenarios, Use Cases and Requirements for Autonomic/Self-Managing Future Internet

DTS/NTECH-AFI-0014-GS01

General Information

• Status: Published
• Publication Date: 01-Oct-2014
• Technical Committee: NTECH AFI - Evolution of Management towards Autonomic Future Internet
• Current Stage: 12 - Completion
• Due Date: 06-Oct-2014
• Completion Date: 02-Oct-2014

Standards Content (Sample)

ETSI TS 103 194 V1.1.1 (2014-10)






TECHNICAL SPECIFICATION
Network Technologies (NTECH);
Autonomic network engineering for
the self-managing Future Internet (AFI);
Scenarios, Use Cases and Requirements for
Autonomic/Self-Managing Future Internet

---------------------- Page: 1 ----------------------
2 ETSI TS 103 194 V1.1.1 (2014-10)



Reference
DTS/NTECH-AFI-0014-GS01
Keywords
autonomic networking, requirements,
self-management, use case
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2014.
All rights reserved.

TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI TS 103 194 V1.1.1 (2014-10)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 5
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 9
4 Main drivers towards Autonomic Management and Control (AMC) of Networks and Services . 11
4.1 Global background and general requirements on the need for autonomics . 11
4.2 Future network vision and expected further requirements for Autonomics and its interworking with
other emerging paradigms . 12
4.3 Operator's requirements that enable derivation of a reference model for introducing AMC in networks . 12
4.4 Management requirements input to derivation to automated management workflow and architectural
aspects of an autonomic network . 13
4.4.1 Identifying players that drive network management aspects as basis for capturing requirements for
automated management and autonomic behaviours . 14
4.4.2 Requirement framework for a Policy- based management as input towards derivation of a reference
model for introducing AMC in networks . 16
4.4.3 Operator's Policy-based autonomics network vertical framework (cross-layer) . 18
4.4.4 Operator's Policy-based autonomics network horizontal framework (cross-domain). 21
4.5 AFI Requirement template . 22
4.6 AFI high level requirements attached to network environment. 23
4.6.1 Basic requirements an Autonomic Network shall support . 23
4.6.2 Requirements for specific network environments. 23
4.6.3 A guide towards implementation of the requirements and associated autonomic functionality and
automated processes . 41
5 Use Case and Scenarios . 42
5.1 Use Case and Scenario Template . 42
5.2 Autonomics in legacy network (NGN) . 43
5.3 Auto-Configuration of Routers using Routing Profiles in a Fixed Network Environment . 44
5.4 Self-Management of Coverage and Capacity in Future Internet Wireless Systems . 45
5.5 Cognitive event management (Fault/Anomaly/Intrusion Detection) . 47
5.6 Coordination of Self-* mechanisms in autonomic networks . 49
5.7 Autonomic Network Monitoring . 50
5.8 Scenarios Overlay Virtual Network Service Breakdown . 52
5.9 Scenarios Overlay Virtual Network Service Quality Degradation . 55
5.10 Monitoring in Carrier Grade Wireless Mesh Networks . 58
5.11 Network self-management based on capabilities of network behaviours as described to the overlying
OSS processes . 60
5.12 Wi-Fi Network Robustness: "Flexible Architecture for Virtualizable future wireless Internet Access" . 61
5.13 Scenarios, requirements and references relationship . 62
Annex A (informative): Current NGN network as an example of a reference network
architecture in which autonomics could be introduced . 64
Annex B (informative): Change History . 65
Annex C (informative): Bibliography . 66
History . 67

ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 103 194 V1.1.1 (2014-10)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://ipr.etsi.org).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Network Technologies (NTECH).
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "may not", "need", "need not", "will",
"will not", "can" and "cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms
for the expression of provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 103 194 V1.1.1 (2014-10)
1 Scope
The present document contains a description of scenarios, use cases, and definition of requirements for the
autonomic/self-managing future internet. Scenarios and use cases selected in the present document reflect real-world
problems which can benefit from the application of autonomic/self-management principles. Two types of high-level
requirements are covered:
1) basic requirements that enable to derive an architectural reference model for introducing Autonomic
Management & Control (AMC) of networks (resources, protocols, parameters) and services in various
reference network architectures; and
2) specific requirements pertaining to aspects requiring "automation" and "behaviour" in a particular
network/service management problem.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are necessary for the application of the present document.
Not applicable.
2.2 Informative references
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] P. Horn. Autonomic Computing: "IBM's perspective on the State of Information Technology"
October 2001, IBM Corp.
NOTE: Available at http://people.scs.carleton.ca/~soma/biosec/readings/autonomic_computing.pdf.
[i.2] IBM: "An architectural blueprint for autonomic computing". Technical report, IBM White paper
(June 2005).
[i.3] J.L. Crowley, D. Hall, R. Emonet: "Autonomic computer vision systems" in J. Blanc-Talon (Ed.),
IEEE Advanced Concepts for Intelligent Vision Systems ICIVS 2007.
[i.4] Recommendation ITU-T M.3060/Y.2401 (03/2006): "Principles for the Management of Next
Generation Networks".
[i.5] ETSI TS 188 001 (V1.1.1): "Telecommunications and Internet Converged Services and Protocols
for Advanced Networking (TISPAN); NGN management; OSS Architecture Release 1".
[i.6] TeleManagement Forum TR133-REQ V1.2: "NGN Management Strategy: Policy Paper".
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 103 194 V1.1.1 (2014-10)
[i.7] "White Paper MUSE Business Model in BB Access" Multi Service Access Everywhere FP6
project.
NOTE Available at http://www.ist-muse.org/Deliverables/WhitePapers/White_Paper_Business_roles.pdf.
[i.8] EC funded FP7 EFIPSANS Project: "Exposing the Features in IP version Six protocols".
NOTE: Available at.http://secan-lab.uni.lu/efipsans-web.
[i.9] EC funded FP7 CARMEN Project: "CARrier grade Mesh Networks".
NOTE: Available at http://www.ict-carmen.eu/.
[i.10] A Requirement Specification by the NGMN Alliance NGMN Recommendation on SON and
O&M Requirements, NGMN alliance, (2008).
NOTE: Available at
http://www.ngmn.org/uploads/media/NGMN_Recommendation_on_SON_and_O_M_Requirements.pdf.
[i.11] EC Funded Autonomic Computing and Networking: "The operators' vision on technologies,
opportunities, risks and adoption roadmap" P1855 Eurescom.
[i.12] Next Generation Mobile Networks Use Cases related to Self Organising Network, Overall
Description, NGMN alliance, 2007.
[i.13] Autonomic Communication, White Paper, Fraunhofer FOKUS November 2004.
[i.14] IEEE 802.11: "IEEE Standard for Information technology - Telecommunications and information
exchange between systems - Local and metropolitan area networks - Specific requirements -
Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)
Specifications".
[i.15] ETSI ETSI ETSI GS AFI 002: "Autonomic network engineering for the self-managing Future
Internet (AFI); Generic Autonomic Network Architecture (An Architectural Reference Model for
Autonomic Networking, Cognitive Networking and Self-Management)".
NOTE: Available at http://www.etsi.org/deliver/etsi_gs/AFI/001_099/002/01.01.01_60/gs_AFI002v010101p.pdf.
[i.16] EC funded FP7 FLAVIA Project: "Flexible Architecture for Virtualizable future wireless Internet
Access".
NOTE Available at http://www.ict-flavia.eu/.
[i.17] Celtic Authone project: "Autonomic Home Networking" 2006-2008.
[i.18] IETF RFC 2461: "Neighbor Discovery for IP version 6 (IPv6)" 2007.
[i.19] David D. Clark, Craig Partridge, and J. Christopher Ramming: "A knowledge plane for the
Internet". In SIGCOMM, pages 3-10, 2003.
[i.20] Stephen Quirolgico, Kevin Mills, and Doug Montgomery: "Deriving Knowledge for the
Knowledge Plane". Draft from National Institute of Standards and Technology Advanced Network
Technologies Division Gaithersburg, June 2003. MD 20899-8920.
[i.21] J Lu, C Dousson, F Krief: "A self-diagnosis algorithm based on causal graphs" ICAS 2011.
[i.22] A. Mihailovic, I. Chochliouros, A. Kousaridas, G. Nguengang, C. Polychronopoulos, J. Borgel,
M. Israel, V. Conan, M. Belesioti, E. Sfakianakis, G. Agapiou, H. Aghvami and N. Alonistioti:
"Architectural Principles for Synergy of Self-management and Future Internet Evolution",
Proceedings of ICT Mobile Summit, June 2009.
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 103 194 V1.1.1 (2014-10)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
automated management: 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
Autonomic Behaviour (AB): process which understands how desired Managed Entity (ME) element's behaviours are
learned, influenced or changed, and how, in turn, these affect other elements, groups and network [i.13]
NOTE: Managed Entity can be physical or logical resource.
autonomic manager element: functional entity that drives a control-loop meant to configure and adapt (i.e. regulate)
the behaviour of a managed entity
NOTE: E.g. a protocol module or some other type of a managed entity such as a component, processing sensory
information from the managed resource and from other types of required information sources and reacting
to observed conditions by effecting a change in the behaviour of the managed resource to achieve some
goal.
autonomic networking: networking paradigm enabling network devices and the overall network architecture to exhibit
the so-called self-managing properties, namely: auto-discovery, self-configuration (auto-configration), self-diagnosing,
self-repair (self-healing), self-optimization, etc.
NOTE: The term autonomic comes from the autonomic nervous system, which controls many organs and muscles
in the human body. Usually, human are unaware of its workings because it functions in an involuntary,
reflexive manner – for example, human do not notice when their heart beats faster or their blood vessels
change size in response to temperature, posture, food intake, stressful experiences and other changes to
which human are exposed. And their autonomic nervous system is always working [i.2].
context awareness: property of an autonomic application/system that enables it to be aware of its execution
environment and be able to react to changes in the environment [i.1]
Decision Element (DE): functional entity designed and assigned to autonomically manage and control some Managed
Entities (Mes)
NOTE 1: Decision-Making-Elements (DMEs) [i.15] referred in short as Decision Elements (Des) that fulfil the role
of Autonomic Manager Elements.
NOTE 2: In accordance with note 1, an ME can be a protocol or a mechanism implemented by some functional
entity. A Decision Element (DE) in an Autonomic Manager Element implements the logic that drives a
control-loop over the management interfaces of its assigned Managed Entities (Mes). Therefore,
self-* functionalities are functionalities implemented by Decision Element(s).
NOTE 3: Mes and their associated configurable parameters are assigned to be managed and controlled by a
concrete DE such that an ME parameter is mapped to one DE.
future internet: framework Interoperating Multi-Service Self-Managing Future Networks that evolve from today's
networking models, paradigms and protocols, and will also include newly designed networking models that succeed to
be "deployed"
NOTE: The motivation behind Future Internet is to address deficiencies in current networks such as Scalability,
and lack of "Network Intelligence ( through Autonomics and Cognition)", and also incorporate missing
capabilities such as Self-Management Capabilities. Future Internet includes all sorts of Fixed(Wired) /
Mobile / Wireless / Sensor Networks. The Future Internet will interconnect and inter-operate IP(v4&v6)
and any Post-IP Networks that emerge and get deployed as some other types of "islands" within the
global space of the "Future Internet". As the Future Internet evolves, some "islands" identified by old
technology will disappear and new "islands" identified by new technology will appear in the picture.
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 103 194 V1.1.1 (2014-10)
GANA (Generic Autonomic Network Architecture): conceptual architectural reference model for autonomic network
engineering, cognition and self-management
NOTE 1: GANA purpose is to serve as a "blueprint model" that prescribes design and operational principles of
autonomic decision-making manager elements responsible for autonomic and cognitive management and
control of resources (e.g. individual protocols, stacks and mechanisms).
NOTE 2: GANA is a functional architecture and not an implementation architecture [i.15].
knowledge plane: pervasive system within the network that builds and maintains high-level models of what the
network is supposed to do, in order to provide services and advice to other elements of the network [i.19]
NOTE: It is a distributed and decentralized construct within the Internet to gather, aggregate and act upon
information about network behaviour and operation [i.20]. The subject of the kind of functional entities
(mainly GANA Network-Level-DEs) that realize the Knowledge Plane, is covered in clause 9.13 of the
GS AFI 002 [i.15]: "Cognition and Knowledge Plane as part of the GANA Decision Plane".
Managed Entity (ME): physical or logical resource that can be managed by an Autonomic Manager Element (i.e. a
Decision Element) in terms of its orchestration, configuration and re-configuration through parameter settings
overlay: logical network that runs on top of another network
EXAMPLE: Peer-to-peer networks are overlay networks on the Internet. They use their own addressing system
for determining how files are distributed and accessed, which provides a layer on top of the
Internet's IP addressing.
self-advertise: ability to advertise its self-model, capability description model, or to send some information signalling
message [i.18] to the network in order to allow communication with it or to allow other entities to know whatever is
being advertised
self-adaptation: ability of a system or component to change its state of operation e.g. by changing its configuration, in
response to context changes that define the service(s) it is supposed to provide to the outside world, or changes in
workload, or in response to internal and external challenges (e.g. manifestation of faults, errors and failures)
NOTE: Self-features of a system or component, such as self-optimization and self-healing are special cases of
self-* adaptation.
Self awareness: ability to "know itself" and be aware of its state and its behaviours [i.1]
NOTE: Knowledge about "self" is described by a "self-model".
self-care services: ability of a system (e.g. network) to promote and provide an interface for external users to request
and consume its services without intervention of the system-administrator, and to update services available to users of
such services
self configuration: ability to configure and reconfigure itself under varying and unpredictable conditions [i.1]
self-descriptive: able to provide a description of its self-model, capabilities and internal state [i.3]
self-diagnosis: ability of a system or component to perform fault-diagnosis (also called fault-localization or fault-
isolation) procedures by employing various methods to determine the root cause of a failure or malfunction, without
external intervention [i.21]
NOTE: Identifying abnormal behaviour (symptom) of a running system or component based on values received
by the sensors, by launching some testing (e.g. to discriminate remaining ambiguities), or using the
information available in its system or component model and its analysis knowledge-base (e.g. the use of
model-based techniques for fault-diagnosis/localization/isolation).
self healing: able to detect and recover from potential problems and continue to function smoothly [i.1]
self-monitoring: able to observe its internal state [i.3]
EXAMPLE: Observation of internal state can be quality-of-service metrics such as reliability, precision,
rapidity, or throughput.
self optimization: ability to detect suboptimal behaviours and optimize itself to improve its execution [i.1]
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 103 194 V1.1.1 (2014-10)
self organizing: able to organize itself with minimum manual intervention [i.12]
self partioning: introducing level of automation within the partioning process
self protecting: able to detect and protect its resources from both internal and external attacks and maintain overall
system security and integrity [i.1]
self-regulation: ability to regulate its internal parameters so as to assure a quality-of-service metric such as reliability,
precision, rapidity, or throughput [i.3]
self services: ability to promote and update services available to public
self-testing: ability to test the conformance of its systems
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
rd
3GPP 3 Generation Partnership Project
AB Autonomic Behaviour
ABGet Available Bandwidth Get
AC Admission Control
AC_ME Admission Control Managed Entity
AF Autonomic Function
AFI Autonomic network engineering for the self-managing Future Internet
AMC Autonomic Management & Control of Networks and Services
AP Access Point
API Application Programming Interface
App_DE Application Decision Element
BBF Broadband Forum
BS Base Station
BSS Business Support System
CaaS Communication as a Service
CHOP Configuration-Healing-Optimization-Protection
NOTE: For implying Self-* features of an autonomic system, namely: Self-Configuration; Self-Healing; Self-
Optimization and Self-Protection.
CIM Common Information Model
CLI Command-Line Interface
CM Consistency Manager
DE Decision Element
DHT Distributed Hash Tables
DME Decision Making Element
DMTF Distributed Management Task Force
E2E End to End
EMS Element Management System
EPC Evolved Packet Core
GANA Generic Autonomic Network Architecture
GS Group Specification
GUI Graphical User Interface
HAN Home Area Network
IaaS Infrastructure as a Service
IANA Implementable Autonomic Network Architecture
IB Information Base
IDS Intrusion Detection Systems
IMS IP Multimedia SubSystem
IP Internet Protocol
Ipv4/Ipv6 Internet Protocol version 4 or 6
IRP Integration Reference point
ISP Internet Service Provider
ISV Independent Software Vendor
ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 103 194 V1.1.1 (2014-10)
IT Information Technology
ITU-T International Telecommunication Union
KPI Knowledge Plane Information
LTE Long Term Evolution
M2M Machine to Machine
MAC Medium Access Control
MANET Mobile Ad-hoc NETworks
ME Managed Entity
MM Monitoring Module
MVNE Mobile Virtual Network Enabler
MVNO Mobile Virtual Network Operator
NaaS Network as a Service
NE Network Element
NGN Next Generation Network
NGOSS New Generation Operations System and Software
NMS Network Management System
NO Network Operator
OAM Operating And Maintenance
OPEX Operation Expediture
OSS Operation Support System
OTT Over The Top
OVN Overlay Virtual Network
P2P Peer to Peer
PC Personal Computer
QoE Quality of Experience
QoS Quality of Services
QoS_DE Quality of Service Decision Element
RAN Radio Access Network
RFID Radio-Frequency IDentification
RQ Requirement
Saas Service as a service
SDN Software Defined / Driven Network
SDO Standardization Organization
SID Shared Information Data/Model
SLA Service Level Agreement
SMS Short Message Service
SOHO Small Office Home Office
SON Self Organizing Network
TCP Transmission Control Protocol
TISPAN Telecoms and Internet converged Services and Protocols for Advanced Networks
TMF Tele Management Forum
TSPEC Traffic Specification
TV Television
UE User Equipment
VNO Virtual Network Operator
WMP Wireless Media Access Control (MAC) Processors
ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 103 194 V1.1.1 (2014-10)
4 Main drivers towards Autonomic Management and
Control (AMC) of Networks and Services
4.1 Global background and general requirements on the need
for autonomics
As network operators need to address numerous issues such as deregulated markets, open competition, explosion of
digital services, converged fixed-mobile services, converged IT-Network (virtualisation, Clouds) and operation
efficiency, they are facing new business and technical challenges. Consequently, they are striving to build a new
ecosystem comprising end-to-end solutions, created through strategic alliances within the telecommunications sector
including third parties (e.g. Mobile Virtual Network Operator (MVNO) / Mobile Virtual Network Enabler (MVNE),
competitors becoming partners (Radio infrastructure sharing or "Radio Access Network (RAN) Sharing" agreement, for
instance), Clouds Services Providers, Virtual Network Providers, consumers becoming content producers, outsourcing
partners, integrators. For this reason the networks they are operating and the associated 'Operations Support System'
(OSS) need to be intelligent, agile, open, secure, flexible and autonomic (i.e. operating with minimum human
intervention).
As driving forces from the network evolution perspective, industries can highlight the deployment of key emerging
technologies such as IP Multimedia Subsystem (IMS) / Next Generation Network (NGN), Long Term
Evolution (LTE)/Evolved Packet Core (EPC), Future Internet, Interne
...