1、 ETSI GR ENI 003 V1.1.1 (2018-05) Experiential Networked Intelligence (ENI); Context-Aware Policy Management Gap Analysis Disclaimer The present document has been produced and approved by the Experiential Networked Intelligence (ENI) ETSI Industry Specification Group (ISG) and represents the views o
2、f those members who participated in this ISG. It does not necessarily represent the views of the entire ETSI membership. GROUP REPORT ETSI ETSI GR ENI 003 V1.1.1 (2018-05)2 Reference DGR/ENI-003 Keywords management, network, policy management 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 GR ENI 003 V1.1.1 (2018-05)3 Contents Intellectual Property Rights 5g3Foreword . 5g3Modal verbs terminology 5g3Introduction 5g31 Scope 6g32 Referen
10、ces 6g32.1 Normative references . 6g32.2 Informative references 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 10g34 Introduction and Approach . 11g34.1 Base Assumptions 11g34.2 Introduction to Policy Management . 11g34.2.1 Policy Definition . 11g34.2.2 Uses of Policy
11、 Management . 11g34.2.3 Managing and Controlling Behaviour Using Policy . 13g34.3 The Policy Continuum 13g34.4 Types of Policy Paradigms . 15g34.4.1 Considered Policy Paradigms . 15g34.4.2 Imperative Policies . 15g34.4.3 Declarative Policies 16g34.4.4 Intent Policies . 17g34.5 Policy Translation. 17
12、g34.6 Model-Driven DSL. 18g34.7 Policy Conflict Detection and Remediation . 18g34.8 Types of Logic Supported by Policies 19g34.9 The Ramifications of Changing Policies 19g34.10 Other Types of Policies 20g34.11 The MEF Policy-Driven Orchestration Project 20g34.11.1 Introduction to MEF PDO 20g34.11.2
13、The MEF PDO Information Model . 20g34.11.3 The MEF PDO Data Models. 22g34.11.4 The MEF PDO Architecture . 22g34.12 Approach Going Forward . 23g34.13 Key Features to be Compared in the Gap Analysis 24g35 Analysis of the MEF PDO Model 25g35.1 Characteristics of the MEF PDO Model . 25g35.1.1 Comprehens
14、ive Policy Information Model . 25g35.1.2 YANG Data Model . 26g35.1.3 Design Patterns Used in the MEF PDO 26g35.1.4 Use of the Policy Continuum 26g35.1.5 Extension of the MEF LSO RA 27g35.2 Supported Policy Paradigms. 27g35.2.1 Imperative Policy 27g35.2.1.1 Description 27g35.2.1.2 Formal Model 28g35.
15、2.2 Declarative Policy . 28g35.2.2.1 Description 28g35.2.2.2 Formal Model 28g35.2.3 Intent Policy 29g35.2.3.1 Description 29g35.2.3.2 Formal Model 29g3ETSI ETSI GR ENI 003 V1.1.1 (2018-05)4 5.2.3.3 Example 1: Application Developer . 29g35.2.3.4 Example 2: Application Developer/Architect/Business Lev
16、el 30g35.2.3.5 Business Level 30g35.3 MEF PDO Model Features Comparison 30g36 Analysis of the IETF SUPA Policy Model 32g36.1 Characteristics of the IETF SUPA Policy Model . 32g36.1.1 Overview 32g36.1.2 Support for the Policy Continuum 33g36.1.3 Policy Entities . 33g36.1.3.1 Policy Entity Overview .
17、33g36.1.3.2 Policy Rule Structure Entities . 33g36.1.3.3 Policy Rule Component Structure Entities 33g36.1.3.4 Policy Rule Metadata Entities . 33g36.1.4 Design Patterns . 34g36.2 Supported Policy Paradigms. 34g36.3 IETF SUPA Model Features Comparison 34g37 Analysis of the TM Forum SID Policy Model .
18、35g37.1 Characteristics of the TM Forum SID Policy Model 35g37.1.1 Overview 35g37.1.2 Support for the Policy Continuum 36g37.1.3 Policy Entities . 36g37.1.3.1 Policy Entity Overview . 36g37.1.3.2 Policy Content Entities 36g37.1.3.3 Policy Specification Entities . 36g37.1.3.4 Policy Application Entit
19、ies . 36g37.1.4 Design Patterns . 37g37.2 Supported Policy Paradigms. 37g37.2.1 Characteristics of the TM Forum SID Policy Model 37g37.3 TM Forum SID Model Features Comparison . 37g3Annex A: Authors Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is av
20、ailable from the ETSI Secretariat. Latest updates are 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 S
21、R 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 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 wh
22、ich are indicated as being the property of ETSI, and 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 T
23、his Group Report (GR) has been produced by ETSI Industry 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
24、 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. Introduction A critical foundation of experiential networked intelligence is context- and situation-awareness. The present
25、document will analyse work done in various SDOs on policy management in general, and context-aware policy management specifically, to determine what work can be reused from external SDOs, and what work needs to be developed in ENI. When gaps are found on existing interfaces that have been developed
26、by other SDOs and ISG ENI needs to reuse, then the recommendation on how these gaps should be filled will be discussed in co-operation with the SDO that defined these interfaces within Phase 1 and beyond. The requirements documented in the present document will be considered during the architecture
27、design work. ETSI ETSI GR ENI 003 V1.1.1 (2018-05)6 1 Scope The present document analyses the work done in various SDOs and open source consortia on policy-based modelling. This information will be used to develop a specification for a context-aware, policy-based management model and architecture fo
28、r enhancing the operator experience through the use of network intelligence. 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 ve
29、rsion 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. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot
30、 guarantee their long term validity. 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 IETF draft-ietf-supa-generic-policy-info-model-03: “Generic Policy Information Model for Simpli
31、fied Use of Policy Abstractions (SUPA)“, May 30, 2017. i.2 Strassner, J.: “Policy-Based Network Management“, Morgan Kaufman, ISBN 978-1558608597, September 2003. i.3 Liskov, B.H.: Wing, J.M., “A Behavioral Notion of subtyping“, ACM Transactions on Programming languages and Systems 16 (6): 1811 - 184
32、1, 1994. i.4 Martin, R.C.: “Agile Software Development, Principles, Patterns, and Practices“, Prentice-Hall, 2002, ISBN: 0-13-597444-5. i.5 Strassner, J.: editor: “MEF Technical Specification: Policy-Driven Orchestration“, Call for Comments v0.7, August 2017. i.6 Riehle, D.: “Composite Design Patter
33、ns“, Proceedings of the 1997 Conference on Object-Oriented Programming Systems, Languages and Applications (OOPSLA 97), ACM Press, 1997, pages 218-228. i.7 Davy, S., Jennings, B., Strassner, J.: “The Policy Continuum - A Formal Model“, Proc. of the 2ndIntl. IEEE Workshop on Modeling Autonomic Commun
34、ication Environments (MACE), Multicon Lecture Notes, No. 6, Multicon, Berlin, 2007, pages 65-78. i.8 Gamma, E., Helm, R., Johnson, R., Vlissides, J.: “Design Patterns - Elements of Reusable Object-Oriented Software“, Addison-Wesley, 1994, ISBN 0-201-63361-2. i.9 Strassner, J., de Souza, J.N., Raymer
35、, D., Samudrala, S., Davy, S., Barrett, K.: “The Design of a Novel Context-Aware Policy Model to Support Machine-Based Learning and Reasoning“, Journal of Cluster Computing, Vol 12, Issue 1, pages 17-43, March, 2009. i.10 MEF: “Lifecycle Service Orchestration Architecture: Reference Architecture and
36、 Framework“, MEF 55, March, 2016. i.11 MEF: “Service Orchestration Functionality“, Call for Comments v0.7, August 2017. ETSI ETSI GR ENI 003 V1.1.1 (2018-05)7 i.12 MEF: “Policy Driven Orchestration Kickoff v3“. NOTE: Available at https:/ i.13 Dey, A.: “Providing architectural support for building co
37、ntext-aware applications“. Ph.D. Thesis (2000). i.14 MEF: “MEF Core Model“, Call for Comments v0.95, January 2018. i.15 ETSI ISG ENI(17)0002-014r3: “Improved Operator Experience through Experiential Networked Intelligence (ENI)“, first edition, May 2017. i.16 IETF draft-ietf-supa-generic-policy-data
38、-model-04: “Generic Policy Data Model for Simplified Use of Policy Abstractions (SUPA)“, June 18, 2017. i.17 Standford Encyclopedia of Philosophy: “Deontic Logic“. NOTE: Available at https:/plato.stanford.edu/entries/logic-deontic/. i.18 Standford Encyclopedia of Philosophy: “Modal Logic“. NOTE: Ava
39、ilable at https:/plato.stanford.edu/entries/logic-modal/. i.19 IEFT: “Simplified Use of Policy Abstractions (supa)“. NOTE: Available at https:/datatracker.ietf.org/wg/supa/about/. i.20 IETF draft-ietf-supa-policy-based-management-framework-03: “SUPA Policy-based Management Framework“, July 2017. i.2
40、1 IETF draft-cheng-supa-applicability-01: “Applicability of SUPA“, March 2017. i.22 TM Forum: “Information Framework (SID); Common Business Entities - Policy“, GB922 Policy, Release 14.5.1, March 2015 (part of Release 17.0). i.23 TM Forum: “Information Framework (SID); Common Business Entities - Roo
41、t Business Entities“, GB922 Root, Release 17.0.0, June 2017 (part of Release 17.0). i.24 Strassner, J.: “Using the MEF Core Model in ONAP“, December 2017. i.25 MEF PDO CfC: “Policy-Driven Orchestration“, v0.8, February 2018. i.26 MEF: “Lifecycle Service Orchestration (LSO): Reference Architecture an
42、d Framework“, MEF 55, March 2016. i.27 IETF RFC 3060: “Policy Core Information Model - Version 1 Specification“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: abstraction: process of focusing on the important char
43、acteristics and behaviour 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. action: set of operations that may b
44、e 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 execution of an Action may be influenced by applicable attributes and m
45、etadata i.25. ETSI ETSI GR ENI 003 V1.1.1 (2018-05)8 capability: set of features that are available from a component NOTE: These features may, but do not have to, be used. All Capabilities should be announced through a dedicated Interface. condition: set of attributes, features, and/or values that a
46、re to be compared with a set of known attributes, features, and/or values in order to determine what decision to make data model: representation of concepts of interest to an environment in a form that is dependent on data repository, data definition language, query language, implementation language
47、, and/or protocol (typically, but not necessarily, all five) declarative policy: type of policy that uses statements to express the goals of the policy, but not how to accomplish those goals NOTE 1: State is not explicitly manipulated, and the order of statements that make up the policy is irrelevan
48、t. NOTE 2: In the present document, Declarative Policy will refer to policies that execute as theories of a formal logic i.25. event: anything of importance to the management system (e.g. a change in the system being managed and/or its environment) occurring on a time-axis formal logic: use of infer
49、ence applied to the 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 i.25. formal methods: set of mathematical theories, such as logic, automata, graph or set theory, and provide associated notations for describing and analysing systems functional block: modular unit that defines the prop
