ETSI GS ZSM 002 V1.1.1 (2019-08)

Zero-touch network and Service Management (ZSM); Reference Architecture

DGS/ZSM-02ed111_Arch

General Information

• Status: Published
• Publication Date: 12-Aug-2019
• Technical Committee: ZSM - Zero-touch network and Service Management
• Current Stage: 12 - Completion
• Due Date: 10-Sep-2019
• Completion Date: 13-Aug-2019

Standards Content (Sample)

GROUP SPECIFICATION
Zero-touch network and Service Management (ZSM);
Reference Architecture
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.

2 ETSI GS ZSM 002 V1.1.1 (2019-08)

Reference
DGS/ZSM-002ed111_Arch
Keywords
architecture, management, network, service

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

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture 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 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
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 2019.
All rights reserved.
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.
ETSI
3 ETSI GS ZSM 002 V1.1.1 (2019-08)
Contents
Intellectual Property Rights . 7
Foreword . 7
Modal verbs terminology . 7
1 Scope . 8
2 References . 8
2.1 Normative references . 8
2.2 Informative references . 8
3 Definition of terms, symbols, abbreviations and conventions . 9
3.1 Terms . 9
3.2 Symbols . 10
3.3 Abbreviations . 10
3.4 Conventions . 11
4 Architecture principles . 12
4.1 Introduction . 12
4.2 The principles . 12
4.2.1 Principle 01: Modularity . 12
4.2.2 Principle 02: Extensibility . 12
4.2.3 Principle 03: Scalability . 12
4.2.4 Principle 04: Model-driven, open interfaces . 12
4.2.5 Principle 05: Closed-loop management automation . 13
4.2.6 Principle 06: Support for stateless management functions . 13
4.2.7 Principle 07: Resilience . 13
4.2.8 Principle 08: Separation of concerns in management . 13
4.2.9 Principle 09: Service composability . 13
4.2.10 Principle 10: Intent-based interfaces . 13
4.2.11 Principle 11: Functional abstraction . 13
4.2.12 Principle 12: Simplicity . 13
4.2.13 Principle 13: Designed for automation . 14
5 Architecture requirements . 14
5.1 Introduction . 14
5.2 Non-functional requirements . 14
5.2.1 General non-functional requirements. 14
5.2.2 Non-functional requirements for cross-domain data services . 14
5.2.3 Non-functional requirements for cross-domain service integration . 15
5.3 Functional requirements . 15
5.3.1 General functional requirements . 15
5.3.2 Functional requirements for data collection . 16
5.3.3 Functional requirements for cross-domain data services . 16
5.3.4 Functional requirements for cross-domain service integration and access . 17
5.3.5 Functional requirements for lawful intercept . 17
5.4 Security requirements . 17
6 Reference architecture . 18
6.1 General architecture overview . 18
6.1.1 Introduction. 18
6.1.2 Architectural building blocks . 18
6.1.2.1 Management services . 18
6.1.2.2 Management functions . 19
6.1.2.3 Management domains . 19
6.1.2.4 The end-to-end (E2E) service management domain . 20
6.1.2.5 Integration fabric . 20
6.1.2.6 Data services . 20
6.2 Architecture diagram . 21
6.3 Integration fabric . 22
ETSI
4 ETSI GS ZSM 002 V1.1.1 (2019-08)
6.3.1 Overview . 22
6.3.2 Provided management services . 22
6.3.2.1 Management services registration service . 22
6.3.2.2 Management services discovery service . 23
6.3.2.3 Management communication service . 23
6.3.2.4 Management service invocation routing service . 24
6.3.2.5 Management capability exposure configuration service . 24
6.3.3 Cross-domain integration fabric . 25
6.3.4 Domain integration fabric . 25
6.4 Data services . 26
6.4.1 Overview . 26
6.4.2 Provided management services . 26
6.4.2.1 Data store management service . 26
6.4.2.2 Data persistence services . 27
6.4.2.3 Data processing service . 27
6.4.3 Cross-domain data services. 28
6.4.4 Domain data services . 28
6.5 Management domain . 29
6.5.1 Overview . 29
6.5.2 Domain data collection . 29
6.5.2.1 Description . 29
6.5.2.2 Provided management services . 29
6.5.2.2.1 Event notification services. 29
6.5.2.2.2 Performance measurements streaming service . 30
6.5.2.2.3 Performance measurements collection service . 30
6.5.2.2.4 Log collection service . 31
6.5.3 Domain analytics . 31
6.5.3.1 Description . 31
6.5.3.2 Provided management services . 32
6.5.3.2.1 Analytics services . 32
6.5.3.2.2 Domain condition detection service . 33
6.5.3.2.3 Data optimization services. 33
6.5.4 Domain intelligence . 34
6.5.4.1 Description . 34
6.5.4.2 Provided management services . 34
6.5.4.2.1 AI model management service . 34
6.5.4.2.2 Deployed AI model assessment service . 35
6.5.4.2.3 AI training data management service . 35
6.5.4.2.4 Knowledge base service . 35
6.5.4.2.5 Health issue reporting service . 36
6.5.5 Domain orchestration . 36
6.5.5.1 Description . 36
6.5.5.2 Provided management services . 37
6.5.5.2.1 Domain orchestration service . 37
6.5.5.2.2 Feasibility check service . 38
6.5.5.2.3 Managed services catalogue management service . 38
6.5.5.2.4 Testing service . 38
6.5.5.2.5 Domain inventory information service . 39
6.5.5.2.6 Domain inventory management service . 39
6.5.5.2.7 Domain topology information service . 39
6.5.6 Domain control . 40
6.5.6.1 Description . 40
6.5.6.2 Provided management services . 40
6.5.6.2.1 Resource configuration management service . 40
6.5.6.2.2 Resource lifecycle management services . 40
6.5.6.2.3 Configuration data generation service . 41
6.5.7 Supporting services . 41
6.5.7.1 Description . 41
6.5.7.2 Provided management services . 42
6.5.7.2.1 Policy management service . 42
6.6 E2E service management domain . 42
6.6.1 Overview . 42
ETSI
5 ETSI GS ZSM 002 V1.1.1 (2019-08)
6.6.2 E2E service data collection . 43
6.6.2.1 Description . 43
6.6.2.2 Provided management services . 43
6.6.2.2.1 E2E performance data reporting service . 43
6.6.3 E2E service analytics . 43
6.6.3.1 Description . 43
6.6.3.2 Provided management services . 43
6.6.3.2.1 Analytics services . 43
6.6.3.2.2 E2E service quality management service . 45
6.6.3.2.3 E2E service condition detection service . 45
6.6.4 E2E service intelligence . 46
6.6.4.1 Description . 46
6.6.4.2 Provided management services . 46
6.6.4.2.1 AI model management service . 46
6.6.4.2.2 Deployed AI model assessment service . 47
6.6.4.2.3 AI training data management service . 47
6.6.4.2.4 E2E service health issue reporting service . 47
6.6.5 E2E service orchestration . 48
6.6.5.1 Description . 48
6.6.5.2 Provided management services . 48
6.6.5.2.1 E2E service orchestration service . 48
6.6.5.2.2 Feasibility check service . 49
6.6.5.2.3 Managed services catalogue management service . 50
6.6.5.2.4 E2E testing service . 50
6.6.5.2.5 E2E services inventory information service . 50
6.6.5.2.6 E2E services inventory management service . 51
6.6.5.2.7 E2E services topology information service . 51
6.6.6 Supporting services . 51
6.6.6.1 Description . 51
6.6.6.2 Provided management services . 52
6.6.6.2.1 E2E policy management service . 52
7 Operational considerations (informative) . 52
7.1 Support for closed-loop operation . 52
8 Security considerations. 53
8.1 General . 53
8.2 Data security . 53
8.3 Data privacy . 53
8.4 System security . 53
Annex A (informative): Architecture options . 55
A.1 Integration with legacy management systems . 55
A.1.1 Overview . 55
A.1.2 Option 1: Legacy management domain integration using domain control services at management
domain level . 55
A.1.3 Option 2: Legacy management domain integration using a ZSM adapter . 56
A.2 Examples of valid ZSM architecture deployments . 56
A.2.1 Overview . 56
A.2.2 Example 1: Multiple recursive levels of domain hierarchies . 56
Annex B (informative): Service consumption patterns . 58
B.1 General . 58
B.2 Service registration and discovery. 58
B.3 Synchronous interactions (request-response) . 58
B.4 Asynchronous communication (publish/subscribe) via the integration fabric . 59
B.5 Asynchronous communication (publish/subscribe) with subscription managed by the service
producer . 60
ETSI
6 ETSI GS ZSM 002 V1.1.1 (2019-08)
Annex C (informative): Support for closed-loop operation . 62
Annex D (informative): Automated discovery and consumption of management capabilities
exposed from a management domain . 65
Annex E (informative): Realization of selected scenarios in the ZSM framework reference
architecture. 66
E.1 Introduction . 66
E.2 Example of services discovery with a new management domain . 66
E.2.1 Objective . 66
E.2.2 Steps . 66
E.3 Example of a customer-facing service deployment . 67
E.3.1 Objective . 67
E.3.2 Steps . 67
E.4 Example of closed-loop operation in management domain . 68
E.4.1 Objective . 68
E.4.2 Steps . 69
Annex F (informative): Change history . 71
History . 80

ETSI
7 ETSI GS ZSM 002 V1.1.1 (2019-08)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if 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 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) 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.
Foreword
This Group Specification (GS) has been produced by ETSI Industry Specification Group (ISG) Zero touch network and
Service Management (ZSM).
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
8 ETSI GS ZSM 002 V1.1.1 (2019-08)
1 Scope
The present document defines and describes the reference architecture for the end-to-end Zero-touch network and
Service Management (ZSM) framework based on a set of user scenarios and requirements documented in ETSI
GS ZSM 001 [i.9].
The reference architecture employs a set of architectural principles, described further in the present document, and a
service-centric architectural model to define at a high level a set of management services for zero-touch network and
service management. It also defines means of management service integration, communication, interoperation, and
organization. Procedures and detailed information models are beyond the scope of the present document.
The reference architecture also defines normative provisions for externally visible management services, defined as part
of the reference architecture, as well as recommendations for their organization. It is assumed that the architectural
patterns introduced in the present document can be used not only for the ZSM framework, but also for architecture and
design of individual management services.
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.
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 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 GR ZSM 005: "Zero-touch network and Service Management (ZSM); Means of
Automation".
[i.2] Boyd, J.R.: "The Essence of Winning and Losing", June 1995.
[i.3] Kephart, J. and D. Chess: "The Vision of Autonomic Computing", IEEE Computer, vol. 36, no. 1,
pp. 41-50, DOI 10.1109/MC.2003.1160055, January 2003.
[i.4] Miller, D.E.: "A new approach to model reference adaptive control", IEEE Transactions on
Automatic Control, Volume: 48, Issue: 5, May 2003.
[i.5] EU General Data Protection Regulation (GDPR).
NOTE: Available from https://eugdpr.org/.
ETSI
9 ETSI GS ZSM 002 V1.1.1 (2019-08)
[i.6] Telemanagement Forum Open Digital Architecture Project.
NOTE: Available from https://www.tmforum.org/collaboration/open-digital-architecture-oda-project/.
[i.7] ETSI TS 128 533: "5G; Management and orchestration;Architecture framework
(3GPP TS 28.533)".
NOTE: Available at https://www.etsi.org/deliver/etsi_ts/128500_128599/128533/.
[i.8] ETSI GS ZSM 007: "Zero-touch network and Service Management (ZSM); Terminology for
concepts in ZSM".
[i.9] ETSI GS ZSM 001: "Zero-touch network and Service Management (ZSM); Requirements based
on documented scenarios".
3 Definition of terms, symbols, abbreviations and
conventions
3.1 Terms
For the purposes of the present document, the terms given in ETSI GS ZSM 007 [i.8] and the following apply:
NOTE: If the same term is defined in both ETSI GS ZSM 007 [i.8] and in the present document, the definition in
the present document takes precedence.
cross-domain data services: services that allow to share data with authorized consumers across management domains
external visibility: property of a ZSM service that indicates whether the scope of the service consumption spans
outside the management domain
NOTE: Conventions for external visibility are defined in clause 3.4.
integration fabric: management function that plays both the roles of service consumer and service producer and which
facilitates the interoperation and communication between management functions
key performance indicator: measurement of a specific aspect of the performance of a service that can be used in a
service level objective
managed entity: managed resource or managed service
NOTE: Examples of managed entities are infrastructure resources, such as virtual network functions (VNF),
physical network functions (PNF), and services such as cloud services, NFV network services, CFSs,
RFSs.
managed resource: resource that is managed by one or more ZSM services
managed service: service that is managed by one or more ZSM services
management domain: scope of management that federates together management services, that enables their exposure
towards external service consumers and that is delineated by a business, administrative, technological or other boundary
management function: logical entity playing the roles of service consumer and/or service producer
NOTE: The implementation details of a management function are not covered in the present document.
management service: See "ZSM service".
service capability: specific part of a ZSM service
NOTE: Examples of service capabilities are defined in the sub-clauses "Provided management services" of
clauses 6.3, 6.4, 6.5 and 6.6 of the present document.
service consumer: role of an entity consuming one or more ZSM services
ETSI
10 ETSI GS ZSM 002 V1.1.1 (2019-08)
service end-point: interface through which service capabilities are offered and consumed
service level agreement: part of a business agreement between a service provider and a customer, specifying the
committed service quality and quantity in terms of service level specifications, and the associated consequences in case
the service level objectives are not met
service level objective: element in a service level specification that is defined in terms of parameters, and related
metrics, thresholds and tolerances associated with the parameters
service level specification: specification of the minimum acceptable standard of service
service producer: role of an entity offering one or more ZSM services
ZSM framework consumer: entity outside the ZSM framework that uses one or several of the management
capabilities offered by the ZSM framework
NOTE 1: ZSM framework consumers may be non-human entities (e.g. digital store fronts, web portals, BSS
components, other ZSM framework instances) or human users.
NOTE 2: ZSM services offer machine-consumable interfaces. They may also allow interfacing with human users
using e.g. a GUI, web portal or application.
ZSM service: set of offered management capabilities
NOTE: In the present document, the terms "ZSM service" and "management service" are used interchangeably.
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI GS ZSM 007 [i.8] and the following apply:
NOTE: If the same abbreviation is defined in both ETSI GS ZSM 007 [i.8] and in the present document, the
definition in the present document takes precedence.
rd
3GPP 3 Generation Partnership Project
AI Artificial Intelligence
BSS Business Support System
CDS Cross-domain Data Services
CFS Customer Facing Service
CPU Central Processing Unit
CRUD Create-Read-Update-Delete
CRUDL Create-Read-Update-Delete-List
E2E End-to-End
EP End-Point
ETSI European Telecommunications Standards Institute
FM Fault Management
GDPR General Data Protection Regulation
GR Group Report
GS Group Specification
GUI Graphical User Interface
IEEE Institute of Electrical and Electronics Engineers
IF Integration Fabric
IP Internet Protocol
IPR Intellectual Property Right
ISG Industry Specification Group
KPI Key Performance Indicator
LI Lawful Intercept
MANO MANagement and Orchestration
MAPE-K Monitor-Analyse-Plan-Execute plus Knowledge
ETSI
11 ETSI GS ZSM 002 V1.1.1 (2019-08)
MD Management Domain
ML Machine Learning
MRACL Model-Reference Adaptive Control Loop
NBI North Bound Interface
NFV Network Functions Virtualization
NIST National Institute of Standards and Technology
OODA Observe, Orient, Decide, Act
PM Performance Management
PNF Physical Network Function
RFS Resource Facing Service
SBI South Bound Interface
SDN Software-Defined Network
SLA Service Level Agreement
SLO Service Level Objective
SLS Service Level Specification
SON Self-Organizing Networks
TS Technical Specification
VIM Virtualized Infrastructure Manager
VLAN Virtualized Local Area Network
VNF Virtualized Network Function
XaaS X-as-a-Service
ZSM Zero-touch network and Service Management
3.4 Conventions
The present document defines ZSM services in a table that provides the name of the service, information about the
visibility of that service outside the management domain where the service producer is located, information on the
capabilities of that service and whether or not the capabilities are mandatory to provide.
The table format is reproduced below.
Table 3.4-1: Service definition template
Service name Name of the service
External visibility MANDATORY/CONDITIONAL (define condition)/OPTIONAL
Service capabilities
First capability (M/C/O) Capability description.
Next capability2 (M/C/O) …
NOTE: (if needed, e.g. to define conditions.)

The external visibility (or "ExtVis" in short) defines whether the service:
• shall always (i.e. without condition) be visible to consumers that are external to the management domain in
which the producer resides (external visibility set to MANDATORY);
• shall be visible to external consumers if certain conditions are met and may be visible to external consumers
otherwise (external visibility set to CONDITIONAL); or
• may be visible to external consumers (external visibility set to OPTIONAL).
If the external visibility is defined as CONDITIONAL, a condition is defined either in the "External visibility" row or in
the "NOTE" row. ZSM services that are defined with optional external visibility are not required to be supported in
ZSM.
The external visibility of data services and integration fabric services is documented separately as it depends on the
scope. Hence, the "external visibility" row is not contained in tables that define a data service or an integration fabric
service.
ETSI
12 ETSI GS ZSM 002 V1.1.1 (2019-08)
The capabilities offered by the service are defined under "Service capabilities". A capability can be mandatory (M)
which means it shall be offered if the service is offered, conditional (C) which means it shall be offered under certain
conditions if the service is offered or optional (O) which means it may be of
...