ETSI TS 103 194-2014 Network Technologies (NTECH) Autonomic network engineering for the self-managing Future Internet (AFI) Scenarios Use Cases and Requirements for Autonomic Self-.pdf

《ETSI TS 103 194-2014 Network Technologies (NTECH) Autonomic network engineering for the self-managing Future Internet (AFI) Scenarios Use Cases and Requirements for Autonomic Self-.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 103 194-2014 Network Technologies (NTECH) Autonomic network engineering for the self-managing Future Internet (AFI) Scenarios Use Cases and Requirements for Autonomic Self-.pdf（67页珍藏版）》请在麦多课文档分享上搜索。

1、 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 TECHNICAL SPECIFICATION ETSI ETSI TS 103 194 V1.1.1 (2014-10)2Reference DTS/NTE

2、CH-AFI-0014-GS01 Keywords autonomic networking, requirements, self-management, use case 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 d

3、e 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 pr

4、ior 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

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

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

7、sion 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. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI regis

8、tered 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 TS 103 194 V1.1.1 (2014-10)3Contents Intellectua

9、l Property Rights 4g3Foreword . 4g3Modal verbs terminology 4g31 Scope 5g32 References 5g32.1 Normative references . 5g32.2 Informative references 5g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 9g34 Main drivers towards Autonomic Management and Control (AMC) of Network

10、s and Services 11g34.1 Global background and general requirements on the need for autonomics 11g34.2 Future network vision and expected further requirements for Autonomics and its interworking with other emerging paradigms 12g34.3 Operators requirements that enable derivation of a reference model fo

11、r introducing AMC in networks 12g34.4 Management requirements input to derivation to automated management workflow and architectural aspects of an autonomic network . 13g34.4.1 Identifying players that drive network management aspects as basis for capturing requirements for automated management and

12、autonomic behaviours . 14g34.4.2 Requirement framework for a Policy- based management as input towards derivation of a reference model for introducing AMC in networks 16g34.4.3 Operators Policy-based autonomics network vertical framework (cross-layer) . 18g34.4.4 Operators Policy-based autonomics ne

13、twork horizontal framework (cross-domain). 21g34.5 AFI Requirement template . 22g34.6 AFI high level requirements attached to network environment 23g34.6.1 Basic requirements an Autonomic Network shall support 23g34.6.2 Requirements for specific network environments. 23g34.6.3 A guide towards implem

14、entation of the requirements and associated autonomic functionality and automated processes . 41g35 Use Case and Scenarios 42g35.1 Use Case and Scenario Template . 42g35.2 Autonomics in legacy network (NGN) . 43g35.3 Auto-Configuration of Routers using Routing Profiles in a Fixed Network Environment

15、 44g35.4 Self-Management of Coverage and Capacity in Future Internet Wireless Systems . 45g35.5 Cognitive event management (Fault/Anomaly/Intrusion Detection) 47g35.6 Coordination of Self-* mechanisms in autonomic networks 49g35.7 Autonomic Network Monitoring 50g35.8 Scenarios Overlay Virtual Networ

16、k Service Breakdown . 52g35.9 Scenarios Overlay Virtual Network Service Quality Degradation . 55g35.10 Monitoring in Carrier Grade Wireless Mesh Networks 58g35.11 Network self-management based on capabilities of network behaviours as described to the overlying OSS processes 60g35.12 Wi-Fi Network Ro

17、bustness: “Flexible Architecture for Virtualizable future wireless Internet Access“ 61g35.13 Scenarios, requirements and references relationship 62g3Annex A (informative): Current NGN network as an example of a reference network architecture in which autonomics could be introduced 64g3Annex B (infor

18、mative): Change History 65g3Annex C (informative): Bibliography . 66g3History 67g3ETSI ETSI TS 103 194 V1.1.1 (2014-10)4Intellectual 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

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

20、 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 m

21、ay 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“, “nee

22、d 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 ETSI TS 103 194 V1.1.1 (201

23、4-10)51 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/

24、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 and 2) specific requirements pertaining to aspects requiring “automation“ and “behaviour“ in a particular ne

25、twork/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 documen

26、t (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 lo

27、ng 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 use

28、r with regard to a particular subject area. i.1 P. Horn. Autonomic Computing: “IBMs 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 auton

29、omic 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 M

30、anagement 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“. ETS

31、I ETSI TS 103 194 V1.1.1 (2014-10)6i.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 versio

32、n 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 Generic Autonomic Network Arc

33、hitecture (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 futur

34、e 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

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

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

37、for Synergy of Self-management and Future Internet Evolution“, Proceedings of ICT Mobile Summit, June 2009. ETSI ETSI TS 103 194 V1.1.1 (2014-10)73 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: automated management:

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

39、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 b

40、ehaviour 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 behavio

41、ur 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 (se

42、lf-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 t

43、heir 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 th

44、at 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

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

46、 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 i

47、s mapped to one DE. future internet: framework Interoperating Multi-Service Self-Managing Future Networks that evolve from todays networking models, paradigms and protocols, and will also include newly designed networking models that succeed to be “deployed“ NOTE: The motivation behind Future Intern

48、et 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 / Sens

49、or Networks. The Future Internet will interconnect and inter-operate IP(v4 Self-Healing; Self-Optimization and Self-Protection. CIM Common Information Model CLI Command-Line InterfaceCM 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 NetworkIaaS Infrastructur