1、 ETSI GS ENI 002 V1.1.1 (2018-04) Experiential Networked Intelligence (ENI); ENI requirements Disclaimer The present document has been produced and approved by the Experiential Networked Intelligence (ENI) ETSI Industry Specification Group (ISG) and represents the views of those members who particip
2、ated in this ISG. It does not necessarily represent the views of the entire ETSI membership. GROUP SPECIFICATION ETSI ETSI GS ENI 002 V1.1.1 (2018-04) 2 Reference DGS/ENI-002 Keywords artificial intelligence, management, network, requirements ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cede
3、x - 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 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document ma
4、y 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 p
5、rint, 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
6、 this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be rep
7、roduced 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 restrict
8、ion extend to reproduction in all media. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMare trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Part
9、ners. oneM2M logo is protected for the benefit of its Members. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI GS ENI 002 V1.1.1 (2018-04) 3 Contents Intellectual Property Rights 4g3Foreword . 4g3Modal verbs terminology 4g31 Scope 5g32 References 5g32.1 Norm
10、ative references . 5g32.2 Informative references 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 Introduction 6g34.1 Categorization of the requirements. 6g35 Service and network requirements . 7g35.1 Overview 7g35.2 General requirements . 7g35.3 Service orchestrat
11、ion and management 7g35.4 Network planning and deployment 8g35.5 Network optimization . 8g35.6 Resilience and reliability 9g35.7 Security and privacy . 9g36 Functional requirements . 10g36.1 Overview 10g36.2 Data Collection and Analysis . 10g36.3 Policy Management 10g36.3.1 General Policy Management
12、 requirements . 10g36.3.2 Context Aware related Policy Requirements 11g36.4 Data Learning . 11g36.5 Interworking with Other Systems . 12g37 Non-functional requirements 12g37.1 Overview 12g37.2 Performance requirements 12g37.3 Operational requirements . 12g37.4 Regulatory requirements 12g37.5 Non-Fun
13、ctional Policy Requirements 13g3Annex A (informative): Authors 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 (https:/ipr.etsi.org/). Pursuant to the ETSI IPR
14、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. Trademarks The
15、 present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of tho
16、se trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Group Specification (GS) has been produced by ETSI Industry Specification Group (ISG) Experiential Networked Intelligence (ENI). Mod
17、al verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “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
18、NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI GS ENI 002 V1.1.1 (2018-04) 5 1 Scope The present document captures the requirements of how intelligence is applied to the network in different scenarios to improve operators experience of service provision and network o
19、peration as well as how intelligence enables dynamic autonomous behaviour and adaptive policy driven operation in a changing context. The requirements documented in this specification are intended to be used during the architecture design work. 2 References 2.1 Normative references References are ei
20、ther 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 referenced document (including any amendments) applies. Referenced documents whic
21、h are not found to be publicly available in the expected location might be found at https:/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. The following referenced documents are neces
22、sary for the application of the present document. Not applicable. 2.2 Informative 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 reference
23、s, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of t
24、he present document but they assist the user with regard to a particular subject area. i.1 ETSI GR ENI 001: “Experiential Networked Intelligence (ENI); ENI use cases“. i.2 ETSI TS 102 165-1 (V5.2.3): “CYBER; Methods and protocols; Part 1: Method and pro forma for Threat, Vulnerability, Risk Analysis
25、 (TVRA)“. i.3 ETSI GR ENI 004: “Experiential Networked Intelligence (ENI); Terminology for Main Concepts in ENI“. i.4 ETSI GS NFV-MAN 001 (V1.1.1): “Network Functions Virtualisation (NFV); Management and Orchestration“. i.5 Service Operations Specification MEF 55: “Lifecycle Service Orchestration (L
26、SO): Reference Architecture and Framework“. i.6 Regulation (EU) 2016/679 of the European Parliament and of the Council on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection
27、Regulation). i.7 ETSI GR ENI 003: “Experiential Networked Intelligence (ENI); Context-Aware Policy Management Gap Analysis“. i.8 ETSI TS 101 158: “Telecommunications security; Lawful Interception (LI); Requirements for network functions“. ETSI ETSI GS ENI 002 V1.1.1 (2018-04) 6 i.9 ETSI GS ENI 005:
28、“Experiential Networked Intelligence (ENI); System Architecture“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ETSI GR ENI 004 i.3 apply. 3.2 Abbreviations For the purposes of the present document, the following abbrevia
29、tions apply: AI Artificial Intelligence API Application Programming Interface BP Back Propagation CAPEX Capital Expenditure DSL Domain-Specific Language ENI Experiential Networked Intelligence GDPR General Data Protection Regulation IoT Internet of Things IP Internet Protocol IT Information Technolo
30、gy LI Lawful Interception LSO RA Lifecycle Service Orchestration-Reference Architecture LSO Lifecycle Service Orchestration MANO Management And Orchestration MEC Multi-access Edge Computing MEF Metro Ethernet Forum NFV Network Functions Virtualisation OPEX OPerational EXpenditure SDN Software Define
31、d Networking SLA Service Level Agreement SVM Support Vector Machine TCO Total Cost of Ownership TVRA Threat, Vulnerability and Risk Analysis VNF Virtualised Network Function WAN Wide-Area Network 4 Introduction 4.1 Categorization of the requirements The present document structure addresses the requi
32、rements in the following areas: 1) Service and network requirements: - General requirements - Service orchestration and management - Network planning and deployment - Network optimization - Resilience and reliability ETSI ETSI GS ENI 002 V1.1.1 (2018-04) 7 - Security and privacy 2) Functional requir
33、ements: - Data Collection and Analysis - Policy Management - Data Learning - Interworking with Other Systems 3) Non-functional requirements: - Performance requirements - Operational requirements - Regulatory requirements - Non-functional policy requirements 5 Service and network requirements 5.1 Ove
34、rview The requirements in this clause are addressed from service and network point of view and are derived directly from the related use cases. 5.2 General requirements This clause captures the requirements that are general and independent from other requirements categorized in other specific clause
35、s. GR.1 The ENI framework shall use history data, context, and decisions taken to learn, process and provide responses to events, whether generated from devices or from management systems. GR.2 The ENI framework shall use context information as part of the computations that result in recommendations
36、, advisement, predictions, and decisions that are used to assist other network systems, e.g. orchestration and management systems. NOTE: As an example, MANO (from ETSI GS NFV-MAN 001 i.4) or the LSO RA (from MEF i.5) are different types of orchestration and management systems. GR.3 The ENI architect
37、ure shall be flexible enough to support extensibility support new requirements. 5.3 Service orchestration and management This clause captures requirements related to the ENI framework service provisioning, e.g. how to compile the service intent and orchestrate the service atoms and work flows, as we
38、ll as automatic service on boarding. SOM.1 The ENI framework shall invoke policies based on models that describe and/or define traffic behaviour, such as SLAs (e.g. past or current telemetry). SOM.2 The ENI framework shall support the closed loop control model when different orchestration and manage
39、ment systems are used. NOTE 1: As an example, MANO (from ETSI GS NFV-MAN 001 i.4) or the LSO RA (from MEF i.5) are different types of orchestration and management systems. ETSI ETSI GS ENI 002 V1.1.1 (2018-04) 8 SOM.3 The ENI framework should not directly manage, control or orchestrate physical or v
40、irtual entities, either at the infrastructure or services level. NOTE 2: ENI framework may interact with the Orchestration, EMS or OSS/BSS to influence the state of the resources or services. 5.4 Network planning and deployment This clause captures requirements related to network planning and deploy
41、ment, e.g. how to allocate network resources to VNFs, or automatic VNF on boarding. NOTE 1: The network resources that can be managed are not limited to the requirements addressed in this clause. NPD.1 The ENI framework shall allocate and retrieve network resources, e.g. IPv4 addresses and IPv6 pref
42、ixes to end users or service flows, in an intelligent way to improve the efficiency of resource utilization. This ENI framework function may be implemented in a centralized and/or distributed manner, according to what is defined in ETSI GR ENI 004 i.3 and according to ETSI GS ENI 005 i.9. NPD.2 The
43、ENI framework shall assist the network equipment to use the resource pools that are used for resource allocation (e.g. IP addresses), in an intelligent way in order to improve the efficiency of resource utilization. NPD.3 The ENI framework should dynamically and intelligently compute and manage the
44、required network resources, including both IPv4 and IPv6 resources as well as other resources. NPD.4 The ENI framework shall compute the network resources required to dynamically and intelligently deploy a given network service efficiently. NPD.5 IT resources to enable network services shall be mana
45、ged within the ENI framework. NOTE 2: Similar capabilities within the data centre are outside the network scope of this phase of ENI. NPD.6 The ENI framework shall be capable of understanding the context that a set of devices is operating within. NPD.7 The ENI framework shall be capable to perform t
46、he proper planning and deployment of resources to ensure that applicable deployed policies are not violated. NPD.8 The ENI System shall identify different types of rollouts for different types of resources that lead to the upgrade of virtualized software-based resources. NPD.9 The ENI System shall,
47、in an efficient and dynamic manner, combine network slices, slice/service prioritization and resource allocation concepts, e.g. in order to resolve resource allocation conflicts between competing network slices deployed on top of a shared infrastructure. 5.5 Network optimization This clause captures
48、 requirements related to network optimization, e.g. how to adjust the network configurations to improve its efficiency and performance, as well as the user experience of the service. NO.1 The ENI framework shall collect and process the necessary data according to specific algorithms in order to achi
49、eve network optimization. NOTE: Data collection algorithms for systems will be specified in the Functional Architecture. NO.2 The ENI framework shall meet or exceed all performance requirements when improving the target performance. NO.3 The ENI framework shall support central optimization, local optimization and distributed joint optimization, according to what is defined in ETSI GR ENI 004 i.3. NO.4 The ENI framework shall support an adaptive optimization process where changes in the environment are ref
