ETSI GS ZSM 009-1 V1.1.1 (2021-06)

Zero-touch network and Service Management (ZSM); Closed-Loop Automation; Part 1: Enablers

DGS/ZSM-009-1_Cla_enab

General Information

• Status: Not Published
• Technical Committee: ZSM - Zero-touch network and Service Management
• Current Stage: 12 - Completion
• Due Date: 23-Jun-2021
• Completion Date: 15-Jun-2021

Standards Content (Sample)

ETSI GS ZSM 009-1 V1.1.1 (2021-06)






GROUP SPECIFICATION
Zero-touch network and Service Management (ZSM);
Closed-Loop Automation;
Part 1: Enablers
Disclaimer
The present document has been produced and approved by the Zero-touch network and Service Management (ZSM) 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.

---------------------- Page: 1 ----------------------
2 ETSI GS ZSM 009-1 V1.1.1 (2021-06)

Reference
DGS/ZSM-009-1_Cla_enab
Keywords
automation, management, network, service

ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
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 prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
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 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
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
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 version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2021.
All rights reserved.

ETSI

---------------------- Page: 2 ----------------------
3 ETSI GS ZSM 009-1 V1.1.1 (2021-06)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definition of terms, symbols and abbreviations . 7
3.1 Terms . 7
3.2 Symbols . 7
3.3 Abbreviations . 7
4 Description of ZSM 009 multi-part deliverable . 8
5 Requirements for Closed-Loop Automation . 8
5.1 Introduction . 8
5.2 General requirements . 8
6 Introduction to Closed-Loop Automation . 10
7 Closed loops within the ZSM framework . 10
7.1 Introduction . 10
7.2 Functional view . 11
7.2.1 Introduction. 11
7.2.2 Closed loops data and control flow . 13
7.2.2.1 Introduction . 13
7.2.2.2 Primary flow . 13
7.2.2.3 Knowledge-enabled flow . 14
7.2.2.4 Customization flow . 15
7.3 Deployment view . 15
7.4 Closed loop types . 17
8 Closed-Loop Automation enablers . 18
8.1 Closed Loop Governance . 18
8.1.1 Introduction. 18
8.1.2 Options for governing a Closed Loop . 18
8.1.3 Lifecycle management of Closed Loops . 19
8.1.3.1 Closed loops lifecycle phases and activities . 19
8.1.3.2 Preparation phase . 20
8.1.3.3 Commissioning phase . 20
8.1.3.4 Operation phase . 20
8.1.3.5 Decommissioning phase . 20
8.1.4 Closed loop models . 21
8.1.4.1 Introduction . 21
8.1.4.2 Closed loop class . 21
8.1.4.3 Closed loop goal class . 23
8.1.4.4 Managed entity class . 24
8.1.4.5 Closed loop component class . 24
8.1.5 Interactions between Closed Loops and external entities . 25
8.1.5.1 Introduction . 25
8.1.5.2 Interactions based on policies . 25
8.1.5.3 Interactions based on intents . 25
8.2 Closed Loop Coordination . 26
8.2.1 Introduction. 26
8.2.2 Relationships between different Closed Loops . 27
8.2.3 Coordination between hierarchical Closed Loops . 28
8.2.4 Coordination between peer Closed Loops . 28
ETSI

---------------------- Page: 3 ----------------------
4 ETSI GS ZSM 009-1 V1.1.1 (2021-06)
8.2.5 Closed Loop Coordination services . 28
8.2.5.1 Introduction . 28
8.2.5.2 Interactions identification . 29
8.2.5.3 Goal coordination . 30
8.2.5.4 Pre-execution coordination . 30
8.2.5.4.1 Introduction . 30
8.2.5.4.2 Action plans conflict detection . 30
8.2.5.4.3 Action plans selection . 30
8.2.5.5 Post-execution coordination . 31
8.2.5.5.1 Introduction . 31
8.2.5.5.2 Action enabling and disabling . 31
8.2.5.5.3 Concurrency coordination . 31
8.2.5.5.4 Impact assessment . 31
9 Specification of management services relevant to Closed Loops . 32
9.1 New management services . 32
9.2 Management services for Closed Loop Governance . 32
9.2.1 Introduction. 32
9.2.2 Closed Loop Governance service . 32
9.2.3 Closed loop information reporting service . 33
9.2.4 Closed loop execution management service . 33
9.2.5 Closed loop usage statistics management service . 34
9.3 Management services for Closed Loop Coordination . 34
9.3.1 Introduction. 34
9.3.2 Pre-execution coordination service . 34
9.3.3 Post-execution coordination service . 35
Annex A (informative): Possible implementation of pause points . 36
Annex B (informative): Change History . 37
History . 40


ETSI

---------------------- Page: 4 ----------------------
5 ETSI GS ZSM 009-1 V1.1.1 (2021-06)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are 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 on the
ETSI Web server (https://ipr.etsi.org/).
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
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 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 those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its

Members. 3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and of the 3GPP
Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of the
®
oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Foreword
This Group Specification (GS) has been produced by ETSI Industry Specification Group (ISG) Zero-touch network and
Service Management (ZSM).
The present document is part 1 of a multi-part deliverable covering Closed-Loop Automation (CLA) based on the ZSM
architectural framework, as identified below:
Part 1: "Enablers";
Part 2: "Solutions for automation of E2E service and network management use cases";
Part 3: "Advanced topics".
Full details of the entire series can be found in clause 4.
Modal 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 NOT allowed in ETSI deliverables except when used in direct citation.

ETSI

---------------------- Page: 5 ----------------------
6 ETSI GS ZSM 009-1 V1.1.1 (2021-06)
1 Scope
The present document describes enablers for Closed-Loop Automation (CLA) based on the ZSM architectural
framework. The present document initially specifies Closed Loop-specific requirements and introduces Closed Loops
within the ZSM framework, from both functional and deployment perspectives. The specifications include enablers for
Closed Loop Governance (CLG), covering the definitions of Closed Loop lifecycle management as well as Closed Loop
models. Such enablers allow automatic deployment and configuration of Closed Loops involving both the end-to-end
service management domain and the individual management domains. Then, the present document specifies enablers
for Closed Loops coordination within the ZSM framework, including means for delegation and escalation between
Closed Loops as well as other coordination means. Finally, the deliverable specifies stage-2 generic enablers for
Closed-Loop Automation (CLA) and includes new management services in addition to those identified in ETSI
GS ZSM 002 [2]. Closed loops running entirely within the managed entities are out-of-scope.
2 References
2.1 Normative 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
referenced document (including any amendments) applies.
Referenced documents which 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 necessary for the application of the present document.
[1] ETSI GS ZSM 001: "Zero-touch network and Service Management (ZSM); Requirements based
on documented scenarios".
[2] ETSI GS ZSM 002: "Zero-touch network and Service Management (ZSM); Reference
Architecture".
[3] ETSI GS ZSM 007: "Zero-touch network and Service Management (ZSM); Terminology for
concepts in ZSM".
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 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 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] ETSI GS ZSM 009-2: "Zero-touch network and Service Management (ZSM); Closed-loop
automation; Part 2: Solutions for automation of E2E service and network management use cases".
[i.2] ETSI GR ZSM 009-3: "Zero-touch network and Service Management (ZSM); Closed-loop
automation; Part 3: Advanced topics".
ETSI

---------------------- Page: 6 ----------------------
7 ETSI GS ZSM 009-1 V1.1.1 (2021-06)
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ETSI GS ZSM 007 [3] and the following apply:
delegation: action taken by a ZSM entity to assign responsibility for one or more goals to one or more other ZSM
entities within stated limits
NOTE 1: Delegation defines the operation autonomy the receiving ZSM entity may use to achieve the assigned
goal(s) and defines conditions for escalation (i.e. to address situations leading to breach in operation
autonomy).
NOTE 2: Delegation is often combined with the concept of escalation in the context of operation autonomy.
Operation autonomy is a central concept in Closed-Loop Automation (see clause 7 of ETSI
GS ZSM 002 [2]).
NOTE 3: Delegation can define the escalation entity or entities.
NOTE 4: Delegation relies on acknowledgment by the receiving entity, and may contain a phase of negotiation
between the entity that originates the delegation and the entity/entities that receive the delegation (e.g. if
the receiving entity can achieve, entirely, partly, or not the delegated goal).
escalation: action taken by a ZSM entity to inform one or more ZSM entities about a breach in its operation autonomy
NOTE 1: A ZSM entity escalates an issue that prevents it from achieving its goal properly, and that is not solvable
with means under its control. An escalation differs from other types of issue or problem reporting in the
sense that an escalation signals a breach in operation autonomy.
NOTE 2: Escalation is often combined with the concept of delegation in the context of operation autonomy.
Operation autonomy is a central concept in Closed-Loop Automation (see clause 7 of ETSI
GS ZSM 002 [2]).
NOTE 3: Escalation can target explicitly an entity or list of entities. Escalation can be with or without
acknowledgment by the receiving entity or entities.
NOTE 4: Escalation can contain contextual information about the problematic situation faced, attempt(s) to solve it,
and other contextual information that could be useful to the recipient of the escalation, or any other
information defined by the corresponding policies.
managed entity: managed resource, a managed service or a managed Closed Loop
NOTE: This term differs from the definition in ETSI GS ZSM 007 [3] because a Closed Loop may also be
managed, similarly to managed resources ( e.g. VNFs, PNFs) and managed services ( e.g. cloud services,
RFSs, CFSs).
3.2 Symbols
For the purposes of the present document, the symbols given in ETSI GS ZSM 007 [3] apply.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI GS ZSM 007 [3] and the following apply:
AI Artificial Intelligence
CL Closed Loop
CLA Closed-Loop Automation
CLC Closed Loop Coordination
CLG Closed Loop Governance
E2E End-to-End
ETSI

---------------------- Page: 7 ----------------------
8 ETSI GS ZSM 009-1 V1.1.1 (2021-06)
E2ES End-to-End Service
KPI Key Performance Indicator
LCM Lifecycle Management
M2O-CL Made-to-Order Closed Loop
MD Management Domain
ML Machine Learning
MnF Management Function
MnS Management Service
RDBMS Relational DataBase Management System
RM-CL Ready-Made Closed Loop
ZSM Zero-touch network and Service Management
4 Description of ZSM 009 multi-part deliverable
The present document specifies part 1 of a multi-part deliverable that focuses on Closed-Loop Automation (CLA) based
on the ZSM framework architecture.
The present document specifies the enablers for Closed-Loop Automation (CLA) that can be used in different use cases.
It includes aspects of Closed Loop Governance (CLG) in clause 8.1 and Closed Loop Coordination (CLC) in clause 8.2.
The present document also extends the ZSM framework architecture specified in ETSI GS ZSM 002 [2] with new
management services and capabilities needed for the specified Closed Loop enablers (clause 9).
ETSI GS ZSM 009-2 [i.1] specifies solutions for end-to-end service and network automation use cases, based primarily
on the enablers and architectural elements specified in ETSI GS ZSM 009-1 (the present document).
ETSI GR ZSM 009-3 [i.2] investigates advanced topics related to Closed-Loop Automation (CLA) such as learning and
cognitive capabilities. It documents problem statements and technical challenges, derives potential requirements and
provides recommendations for the evolution of Closed-Loop Automation (CLA) standardization activities.
5 Requirements for Closed-Loop Automation
5.1 Introduction
This clause defines the requirements relevant to Closed-Loop Automation (CLA) within the ZSM framework
architecture. The requirements are derived from ETSI GS ZSM 001 [1] and ETSI GS ZSM 002 [2], as well as new
requirements introduced specifically for Closed-Loop Automation (CLA).
The requirements are considered for the specification of the Closed-Loop Automation (CLA) enablers in clause 8.
5.2 General requirements
[CL-general-1] Closed loops within the ZSM framework shall have access to the data necessary to allow its proper
operation.
NOTE 1: Examples of data include system log data, historical data, policy data, other external data input, etc.
[CL-general-2] The ZSM framework shall allow establishing different types of relationships between Closed
Loops.
NOTE 2: Examples of relationships are peer Closed Loops, hierarchical or nested Closed Loops.
[CL-general-3] Closed loops stages should be able to expose their outcomes to the authorized entities.
NOTE 3: Examples of authorized entities are other Closed Loops and ZSM framework consumers.
[CL-general-4] Authorized Closed Loops within the ZSM framework shall be able to interact with other Closed
Loops within the ZSM framework in different management domains.
ETSI

---------------------- Page: 8 ----------------------
9 ETSI GS ZSM 009-1 V1.1.1 (2021-06)
[CL-general-5] Closed loops within the ZSM framework shall be able to be defined across multiple management
domains.
NOTE 4: The management services for different Closed Loop stages may be provided by different management
domains, e.g. data can be collected from one management domain and execution of actions may be
performed in another management domain, etc.
[CL-general-6] Closed loops within the ZSM framework working in a management domain shall be able to
request other Closed Loops in the E2E service management domain to take necessary action(s) in
different management domains.
[CL-general-7] Closed loops stages should support influences from authorized entities outside the Closed Loop,
but within the ZSM framework.
[CL-general-8] The actions taken by Closed Loops shall be logged.
[CL-general-9] The period for which Closed Loops logs are retained should be configurable.
[CL-general-10] The ZSM framework should support capabilities to present external instructions to the Closed
Loops in a declarative form.
[CL-general-11] Closed loops within the ZSM framework should understand external instructions received in a
declarative form.
[CL-general-12] Closed loops within the ZSM framework should support the capability to provide the state of each
stage for its proper operation.
[CL-general-13] Closed loops within the ZSM framework should support the capability to detect abnormal states of
any stage and notify the authorized entities.
[CL-general-14] Decisions based on AI/ML made by a
...