ETSI GS AFI 001-2011 Autonomic network engineering for the self-managing Future Internet (AFI) Scenarios Use Cases and Requirements for Autonomic Self-Managing Future Internet (V1 .pdf

1、 ETSI GS AFI 001 V1.1.1 (2011-06)Group Specification Autonomic network engineering forthe self-managing Future Internet (AFI);Scenarios, Use Cases and Requirements forAutonomic/Self-Managing Future InternetDisclaimer This document has been produced and approved by the Autonomic network engineering f

2、or the self-managing Future Internet (AFI) ETSI Industry Specification Group (ISG) and represents the views of those members who participated in this ISG. It does not necessarily represent the views of the entire ETSI membership. ETSI ETSI GS AFI 001 V1.1.1 (2011-06) 2Reference DGS/AFI-0001 Keywords

3、 Autonomic Networking, Cognition, OAM, ontology, Self-Management ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88

4、 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version

5、is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the 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.

6、 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

7、 No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2011. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI regi

8、stered for the benefit of its Members. 3GPPTM 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 ETSI GS AFI 001 V1.1.1 (2011-06) 3Contents Intellect

9、ual Property Rights 4g3Foreword . 4g31 Scope 5g31.1 Global description background. 5g31.2 AFI Methodology . 6g31.3 AFI Process 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 E

10、TSI 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

11、 may become, essential to the present document. Foreword This Group Specification (GS) has been produced by ETSI Industry Specification Group Autonomic network engineering for the self-managing Future Internet (AFI). ETSI ETSI GS AFI 001 V1.1.1 (2011-06) 51 Scope The present document contains a desc

12、ription of scenarios, use cases, and definition of requirements for the autonomic/self-managing future internet based on a Top-down NGN management; Operations Support Systems Architecture“. i.6 TeleManagement Forum TR133-REQ V1.2: “NGN Management Strategy: Policy Paper“. AFI DeliverablesAFI and its

13、stakeholdersWI 1 RequirementsUse CasesScenariosWI 2Translation into WI 3Feedback/Adjustment(2009) (2010) (2011)Update- MaintenanceFeedback/AdjustmentIANAGANAETSI ETSI GS AFI 001 V1.1.1 (2011-06) 9i.7 “White Paper MUSE Business Model in BB Access“ Multi Service Access Everywhere FP6 project http:/www

14、.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 http:/www.efipsans.org/. i.9 EC funded FP7 CARMEN Project: “CARrier grade MEsh Networks“ http:/www.ict-carmen.eu/. i.10 A Requirement Specifica

15、tion by the NGMN Alliance NGMN Recommendation on SON and O Generic Autonomic Network Architecture“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: Autonomic Behaviour (AB): It is linked to understanding how desired

16、 elements behaviours are learned, influenced or changed, and how, in turn, these affect other elements, groups and network i.13. autonomic manager element: functional entity that drives a control-loop meant to configure and adapt (i.e. regulate) the behaviour of a managed resource e.g. a protocol mo

17、dule or some other type of a managed entity such as a component, by 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 au

18、tonomic networking: “new networking paradigm“ that involves the design of network devices and the overall network architecture in such a way as to embed “control-loops and feedback mechanisms“ that enable the individual devices and the networked systems as a whole, to exhibit the so-called self-mana

19、ging 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, we are unaware of

20、its workings because it functions in an involuntary, reflexive manner - for example, we do not notice when our heart beats faster or our blood vessels change size in response to temperature, posture, food intake, stressful experiences and other changes to which we are exposed. And our autonomic nerv

21、ous system is always working i.2 Alan Ganek, VP Autonomic Computing, IBM. 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 ETSI ETSI GS AFI 001 V1.1.1 (2011-06) 10Decision El

22、ement (DE): ETSI GS AFI 002 i.15 produced by WI#2 defines in more detail so-called Decision-Making-Elements (DMEs) referred in short as Decision Elements (DEs) that fulfil the role of Autonomic Manager Elements, each of which is designed and assigned to autonomically manage and control some Managed

23、Entities (MEs) assigned to be managed and controlled by a concrete DE. An ME is 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

24、Managed Entities (MEs). Therefore, in AFI, self-* functionalities are functionalities implemented by Decision Element(s). GANA (Generic Autonomic Network Architecture): Conceptual Architectural Reference Model for Autonomic Network Engineering, Cognition and Self-Management, whose purpose is to serv

25、e 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: It is not an implementation architecture

26、 per se. Refer to ETSI GS AFI 002 i.15 produced by WI#2 for more details. Managed Entity (ME): protocol or mechanism implemented by some functional entity that does a specific job for which it is designed to perform and can be managed by an Autonomic Manager Element (i.e. a Decision Element) in term

27、s 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 acce

28、ssed, which provides a layer on top of the Internets IP addressing. self-advertise: An autonomic entity should be able to advertise its self-model, capability description model, or some information signalling message (such as IPv6 routing advertisement) to the network in order to allow communication

29、 with it or to allow other entities to know whatever is being advertised. self awareness: autonomic application/system which “knows itself“ and is aware of its state and its behaviors i.1 NOTE: Knowledge about “self“ is described by a “self-model“. self configuration: autonomic application/system sh

30、ould be able to configure and reconfigure itself under varying and unpredictable conditions i.1 self-descriptive: ability of a component or system to provide a description of its self-model, capabilities and internal state i.3 self healing: autonomic application/system should be able to detect and r

31、ecover from potential problems and continue to function smoothly i.1 self-monitoring: ability of a component or system to observe its internal state, for example, including such quality-of-service metrics as reliability, precision, rapidity, or throughput i.3 self optimisation: autonomic application

32、/system should be able to detect suboptimal behaviors and optimize itself to improve its execution i.1 self organizing: self-organising function in network includes processes which require minimum manual intervention i.12 self partioning: introducing level of automation within the partioning process

33、 self protecting: autonomic application/system should be capable of detecting and protecting its resources from both internal and external attack and maintaining overall system security and integrity i.1 self-regulation: ability of a component or system to regulate its internal parameters so as to a

34、ssure a quality-of-service metric such as reliability, precision, rapidity, or throughput i.3 ETSI ETSI GS AFI 001 V1.1.1 (2011-06) 113.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AB Autonomic Behaviour ABGet Available Bandwidth Get AC ME Admission Co

35、ntrol Managed Entity AF Autonomic Function AFI Autonomic network engineering for the self-managing Future Internet AP Access Point API Application Protocol Interface App_DE Application Decision Element BS Base Station BSS Business Support System CLI Command-Line InterfaceDE Decision Element DHT Dist

36、ributed Hash Tables DME Decision Making Element E2E End to End EMS Element Management System EPC Evolved Packet Core GANA Generic Autonomic Network Architecture HAN Home Area Network IaaS Infrastructure as a Service IANA Implementable Autonomic Network Architecture IDS Intrusion Detection Systems IM

37、S IP Multimedia SubSystem IPv4/IPv6 Internet Protocol version 4 or 6 ISP Internet Service Provider KPI Knowledge Plane Information LTE Long Term Evolution MANET Mobile Ad-hoc NETworks ME Managed Entity NE Network Element NGN Next Generation Network NGOSS New Generation Operations System and Software

38、 NMS Network Management System NO Network OperatorOAM Operating and Maintenance OPEX OPeration EXpediture OSS Operation Support System OTT Over The Top OVN Overlay Virtual Network P2P Peer to Peer QoE Quality of Experience QoS Quality of Services QoS_DE Quality of Service Decision Element Saas Servi

39、ce as a service SLA Service Level Agreement SMS Short Message Service SOHO Small Office Home Office SON Self Organising Network TSPEC Traffic Specification VNO Virtual Network Operator WI Work Item ETSI ETSI GS AFI 001 V1.1.1 (2011-06) 124 AFIs Requirements for an Autonomic Network Figure 4 depicts

40、the global diagram describing the process and tools used by AFI Work Item 1 for designing “AFI requirements“. The starting point is capturing autonomic issues and global context from top level in order to shape the current and Future network vision. This serves as input to formulate operators requir

41、ements from operation view point. The result is shaping AFI high level requirements thanks to a dedicated template as tool. From the bottom level, this AFI requirement template is refined by inputs coming from AFI Use Cases & Scenarios structured within appropriate template as tool. Figure 4: AFI pr

42、ocess and tools for designing requirements & scenarios 4.1 Current NGN network Next Generation Network (NGN) is a network architecture that almost all operators are deploying. Within NGN, the core network is based on IP and multiple access technologies and devices that may coexist alongside this IP

43、core network. IP connectivity among users is a must. IP Multimedia subsystem (IMS) is the first distributed control service architecture for fixed/wired and mobile access network. It is deployed to facilitate service convergence. NGN is the current network architecture for operators to fulfil the re

44、quirements that arise from new market realities: Open competition (especially in terms of new services deployment, to provide the best QoS, to reduce prices/costs/OPEX) Deregulation of markets (e.g. separation between network and service planes) Explosion of digital traffic Convergence (fixed/mobile

45、) Mobility (inside converged networks, between several networks (Web services) AFI captured autonomics Issues and global contextCurrent NGN network Future network visionOperators & other RequirementsAFI requirements(AFI requirement template) AFI Use Case & Scenarios(AFI template Use Case & Scenarios

46、)4.1 4.24.2 4.3 4.44.6AFI Use Case & Scenarios(AFI template Use Case & Scenarios)AFI Use Case & Scenarios(AFI template Use Case & Scenarios)AFI requirements(AFI requirement template) AFI requirements(AFI requirement template) AFI Requirements(AFI requirement template) AFI Use Case & Scenarios(AFI Us

47、e Case & Scenarios template)5ETSI ETSI GS AFI 001 V1.1.1 (2011-06) 13Next Generation Network (NGN) is defined by ITU-T as a layered network and services architecture using a packet-based transport network and a unified control layer that is able to provide telecommunication services with QoS over di

48、fferent broadband access networks i.4. NGN supports generalized mobility/nomadic functions allowing consistent and ubiquitous access to services. Figure 5: NGN Architecture overview Network and service decoupling is one of the main NGN concepts. Such decoupling is reflected in the NGN architecture.

49、As it can be viewed in figure 5, there is a clear separation between Service and Transport layers. NGN covers different access networks through a common IP core. For NGN, it is necessary to have IP connectivity among users. 4.2 Future network vision In the future, processing, storage and communication services will be highly pervasive, intertwined and strongly related to each other. What we expect is that people, smart objects, machines and the surrounding space will all be embedded with devices such as sensors, RFID t