1、 ETSI GR ENI 004 V1.1.1 (2018-06) Experiential Networked Intelligence (ENI); Terminology for Main Concepts in ENI 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
2、members who participated in this ISG. It does not necessarily represent the views of the entire ETSI membership. GROUP REPORT ETSI ETSI GR ENI 004 V1.1.1 (2018-06)2 Reference DGR/ENI-004 Keywords artificial intelligence, network, terminology ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex
3、 - 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 may
4、 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 pr
5、int, 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 repr
7、oduced 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 restricti
8、on 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 Partn
9、ers. 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 GR ENI 004 V1.1.1 (2018-06)3 Contents Intellectual Property Rights 4g3Foreword . 4g3Modal verbs terminology 4g31 Scope 5g32 References 5g32.1 Normat
10、ive references . 5g32.2 Informative references 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 12g3Annex A: Authors Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates ar
11、e available on the ETSI Web server (https:/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) wh
12、ich are, or may be, or may become, essential to the present document. Trademarks The 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
13、 conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Group Report (GR) has been produced by ETSI Indu
14、stry Specification Group (ISG) Experiential Networked Intelligence (ENI). Modal verbs terminology In the present document “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 th
15、e expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI GR ENI 004 V1.1.1 (2018-06)5 1 Scope The present document provides terms and definitions used within the scope of the ETSI ISG ENI. The purpose is to define a common
16、 lexicon for use across all deliverables of ENI. 2 References 2.1 Normative references Normative references are not applicable in the present document. 2.2 Informative references References are either specific (identified by date of publication and/or edition number or version number) or non-specifi
17、c. For specific references, only the cited version applies. For non-specific references, 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 va
18、lidity. 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 ETSI GS NFV 003 (V1.3.1): “Network Functions Virtualisation (NFV); Terminology for Main Concepts in NFV“. i.2 MEF PDO CfC:
19、“Policy-Driven Orchestration“, v0.8, February 2018. i.3 MEF 55.0.3: “Amendment to MEF 55: Service Orchestration Functionality“, January 2018. i.4 MEF 55: “Lifecycle Service Orchestration (LSO): Reference Architecture and Framework“, March 2016. i.5 MEF MCM CfC: “MEF Core Model“, March 2018. i.6 Gamm
20、a E., Helm R. Johnson R. and Vlissides J.: “Design Patterns: Elements of Reusable Object-Oriented Software“, Addison-Wesley, November 1994. ISBN 978-0201633610. i.7 ISO/IEC 2382-28: “Information technology - Vocabulary“. i.8 ISO/IEC/IEEE 42010: “Systems and software engineering - Architecture descri
21、ption“. ETSI ETSI GR ENI 004 V1.1.1 (2018-06)6 3 Definitions and abbreviations 3.1 Definitions The purpose of the present document is to provide the terms and definitions to be used in ETSI ISG ENI deliverables. 0 to 9 Void. A abstraction: process of focusing on the important characteristics and beh
22、aviour of a concept and realizing this as a set of one or more elements in an information or data model NOTE: When applied to modelling, it defines a generic set of characteristics and behaviours for a class that all of its subclasses inherit. This enables the definition of concepts to be separated
23、from their implementation. action: set of operations that may be performed on a set of managed entities, it represents a transformation or processing in the system being modelled NOTE: An Action either maintains the state, or transitions to a new state, of the targeted managed entities. The executio
24、n of an Action may be influenced by applicable attributes and metadata. As defined in MEF PDO CfC i.2. Artificial Intelligence (AI): computerized system that uses cognition to understand information and solve problems NOTE 1: ISO/IEC 2382-28 i.7 defines AI as “an interdisciplinary field, usually reg
25、arded as a branch of computer science, dealing with models and systems for the performance of functions generally associated with human intelligence, such as reasoning and learning“. NOTE 2: In computer science AI research is defined as the study of “intelligent agents“: any device that perceives it
26、s environment and takes actions to achieve its goals. NOTE 3: This includes pattern recognition and the application of machine learning and related techniques. NOTE 4: Artificial Intelligence is the whole idea and concepts of machines being able to carry out tasks in a way that mimics the human inte
27、lligence and would be considered “smart“. B Void. C capability: set of features that is available from a Component NOTE: These features may, but do not have to, be used. All Capabilities should be announced through a dedicated Reference Point. As defined in MEF PDO CfC i.2. choreography: set of proc
28、esses that define how entities interact from a global point-of-view NOTE: That is without a single point of control. Compare this definition to Orchestration. closed loop control: self-regulating mechanism in which outputs of a system are provided to a system that compares the current state to a des
29、ired state (or set of states); the comparison is then used to adjust the behaviour of the system NOTE 1: Positive feedback increases the correction value, while negative feedback reduces the correction value. NOTE 2: Positive and negative feedback can be combined to achieve the needs of a system. In
30、 addition, more complex forms of closed loop control exist, such as proportional-integral-derivative (PID) control. See control theory. ETSI ETSI GR ENI 004 V1.1.1 (2018-06)7 component: part of a System that has operational and/or management significance NOTE: A Software Component is an encapsulatio
31、n of a set of related functions and/or data that perform a set of specific purposes and have a set of associated semantics and behaviour. compute node: object that performs a set of calculations according to a set of algorithms condition: set of attributes, features, and/or values that are to be com
32、pared with a set of known attributes, features, and/or values in order to determine what decision to make container: object that stores collections of other objects in an organized manner control plane: communication between entities that enables forwarding and routing of traffic to work NOTE: Contr
33、ol plane packets are destined to, or locally originated, by entities themselves (e.g. they go to a network entity and direct how traffic flows). Compare to Data Plane. control theory: application of mechanisms to regulate the behaviour of a target system NOTE: Control theory includes linear and nonl
34、inear control mechanisms. D data model: representation of concepts of interest to an environment that is dependent on data repository, data definition language, query language, implementation language, and/or protocol (typically, but not necessarily, all five) NOTE: As defined in MEF PDO CfC i.2. da
35、ta plane: path that the end-user traffic takes through a network NOTE It is made up of traffic that goes through network entities, not to a network entity. Compare to Control Plane. declarative policy: type of policy that uses statements to express the goals of the policy, but not how to accomplish
36、those goals NOTE 1: State is not explicitly manipulated, and the order of statements that make up the policy is irrelevant. NOTE 2: In the present document, Declarative Policy will refer to policies that execute as theories of a formal logic. NOTE 3: As defined in MEF PDO CfC i.2. domain: collection
37、 of entities that share a common purpose, and which are governed in a common way NOTE: As defined in MEF MCM CfC i.5. E ENI framework: set of abstractions that provide reusable and extensible mechanisms to provide generic functionality NOTE 1: The ISO/IEC/IEEE 42010 i.8 defines the term architecture
38、 framework as: “An architecture framework establishes a common practice for creating, interpreting, analysing, and using architecture descriptions within a particular domain of application or stakeholder community“. NOTE 2: The ENI Framework also uses its abstractions to enable the ENI System to dyn
39、amically adapt to changing business goals, user needs, and environmental conditions. The ENI Framework hence provides a standard way to build and deploy applications and application components. ETSI ETSI GR ENI 004 V1.1.1 (2018-06)8 ENI system: set of entities, based on the “observe-orient-decide-ac
40、t“ control loop model, that produces commands, recommendations, and knowledge to assist or direct the management of another system NOTE: The ENI system is an innovative, policy-based, model-driven entity that uses artificial intelligence and other mechanisms to provide intelligent service operation
41、and management. It is the enabler of intelligent Infrastructure management, Network Operations Service Operation and Management, and Assurance. It automates complex human-dependent decision-making processes. It also provides the ability to ensure that automated decisions taken by the system are corr
42、ect and are made to increase the reliability, security and maintenance of the network and the applications that it supports. It also includes hardware and software components, programs, and system and user documentation. Event-Condition-Action (ECA): type of imperative policy in which actions can on
43、ly execute if the event and condition clauses are true NOTE: An ECA policy rule is activated when its event clause is true; the condition clause is then evaluated and, if true, enables the execution of one or more actions in the action clause. This type of policy explicitly defines the current and d
44、esired states of the system being managed. Experiential Networked Intelligence (ENI): processes associated with assimilating and understanding knowledge and learning through experience NOTE: Adding closed-loop artificial intelligence mechanisms based on context-aware, metadata-driven policies enable
45、s the network to more quickly recognize and incorporate new and changed knowledge, and hence, make actionable decisions. This enables the network functionality to evolve and become better able to meet the demands of its operators with continued usage. F formal logic: use of inference applied to the
46、form, or content, of a set of statements NOTE: The logic system is defined by a grammar that can represent the content of its sentences, so that mathematical rules may be applied to prove whether the set of statements is true or false. Refer to MEF PDO CfC i.2. formal methods: set of mathematical th
47、eories, such as logic, automata, graph or set theory, that provide associated notations for describing and analysing systems NOTE: As used in MEF PDO CfC i.2. functional block: modular unit that defines the properties, behaviour, and relationships of a part of a system NOTE: With respect to ENI, fun
48、ctional blocks may be categorized as external (meaning that other systems external to ENI can see them) and internal (meaning that the functional block is only visible to other ENI functional blocks). External functional blocks use Reference Points to provide access to their functionality. Internal
49、functional blocks use private interfaces to provide access to their functionality. As used in MEF 55.0.3 i.3. G to H Void. I imperative policy: type of policy that uses statements to explicitly change the state of a set of targeted objects NOTE 1: The order of statements that make up the policy is explicitly defined. NOTE 2: In the present document, Imperative Policy will refer to policies that are made up of Events, Conditions, and Actions. As defined in MEF PDO CfC i.2. information model: representation of concepts of interest to an env
