ETSI GS ZSM 008 V1.1.1 (2022-07)

Zero-touch network and Service Management (ZSM); Cross-domain E2E service lifecycle management

DGS/ZSM-008ed111_CrossDomE2eS

General Information

• Status: Not Published
• Technical Committee: ZSM - Zero-touch network and Service Management
• Current Stage: 12 - Completion
• Due Date: 26-Jul-2022
• Completion Date: 08-Jul-2022

Standards Content (Sample)

GROUP SPECIFICATION
Zero-touch network and Service Management (ZSM);
Cross-domain E2E service lifecycle management
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 008 V1.1.1 (2022-07)

Reference
DGS/ZSM-008ed111_CrossDomE2eS
Keywords
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
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure Program:
https://www.etsi.org/standards/coordinated-vulnerability-disclosure
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
rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
and/or governmental
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 2022.
All rights reserved.
ETSI
3 ETSI GS ZSM 008 V1.1.1 (2022-07)
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 . 8
3 Definition of terms, symbols and abbreviations . 10
3.1 Terms . 10
3.2 Symbols . 10
3.3 Abbreviations . 10
4 Overview of cross-domain E2E service lifecycle management . 11
5 Cross-domain E2E service lifecycle management processes . 14
5.1 Overview . 14
5.2 Service onboarding . 14
5.2.1 Overview . 14
5.2.2 Process: Service onboarding . 14
5.2.2.1 Description . 14
5.2.2.2 Procedure flow . 15
5.2.2.3 Related management services . 17
5.3 Service fulfilment . 17
5.3.1 Overview . 17
5.3.2 Process: Service instantiation . 17
5.3.2.1 Description . 17
5.3.2.2 Procedure flow . 18
5.3.2.3 Related management services . 20
5.3.3 Process: Service activation . 21
5.3.3.1 Description . 21
5.3.3.2 Procedure flow . 22
5.3.3.3 Related management services . 23
5.3.4 Process: Service configuration . 23
5.3.4.1 Description . 23
5.3.4.2 Procedure flow . 24
5.3.4.3 Related management services . 25
5.3.5 Process: Service deactivation . 25
5.3.5.1 Description . 25
5.3.5.2 Procedure flow . 26
5.3.5.3 Related management services . 27
5.3.6 Process: Service decommissioning . 27
5.3.6.1 Description . 27
5.3.6.2 Procedure flow . 28
5.3.6.3 Related management services . 29
5.3.7 Process: Update E2E inventory / topology . 30
5.3.7.1 Description . 30
5.3.7.2 Procedure flow . 31
5.3.7.3 Related management services . 33
5.4 Service assurance . 34
5.4.1 Overview . 34
5.4.2 Process: Service assurance set-up . 34
5.4.2.1 Description . 34
5.4.2.2 Procedure flows . 35
5.4.2.2.1 Producer-initiated set-up of information collection related to domain service instance . 35
5.4.2.2.2 Consumer-initiated set-up of collecting "E2E-service specific" information related to domain
service instances . 37
ETSI
4 ETSI GS ZSM 008 V1.1.1 (2022-07)
5.4.2.3 Related management services . 39
5.4.3 Process: Service quality management . 39
5.4.3.1 Description . 39
5.4.3.2 Procedure flows . 40
5.4.3.2.1 Main service quality management flow . 40
5.4.3.2.2 Auxiliary process to collect additional domain performance data . 43
5.4.3.3 Related management services . 46
5.4.4 Process: Service problem management . 47
5.4.4.1 Description . 47
5.4.4.2 Procedure flow . 48
5.4.4.3 Related management services . 50
5.4.5 Process: Service assurance tear-down. 51
5.4.5.1 Description . 51
5.4.5.2 Procedure flows . 52
5.4.5.2.1 Producer-initiated tear-down of information collection related to domain service instances . 52
5.4.5.2.2 Consumer-initiated tear-down of collecting "E2E-service specific" information related to
domain service instances . 54
5.4.5.3 Related management services . 55
6 Management domain support for cross-domain E2E service lifecycle management . 56
6.1 Overview . 56
6.2 3GPP Core domain and 3GPP RAN domain . 56
6.3 Fixed access domain . 63
6.4 Transport domain . 67
6.4.1 Overview . 67
6.4.2 Optical transport domain with IETF-based NBI . 67
6.4.3 Optical transport domain with TAPI as NBI . 71
6.4.4 Transport domain based on Layer 2 / Layer 3 VPNs . 79
6.4.5 Transport slices . 83
6.5 Cloud domain . 87
7 Gaps and commonalities . 91
Annex A (normative): Management services . 95
A.1 Overview . 95
A.2 Additional services . 95
A.2.1 E2E services topology management service. 95
A.3 Additional service capabilities . 95
A.3.1 Domain inventory information service . 95
A.3.2 Domain topology information service . 96
A.3.3 Managed services catalogue management service . 96
Annex B (informative): Further northbound interfaces . 97
B.1 Domain northbound interfaces specified by TMF Open API. 97
Annex C (informative): Change History . 100
History . 105

ETSI
5 ETSI GS ZSM 008 V1.1.1 (2022-07)
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).
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
6 ETSI GS ZSM 008 V1.1.1 (2022-07)
1 Scope
The present document investigates the management of End to End (E2E) services across Management Domains (MDs).
It defines the management processes during the lifecycle of E2E services (covering onboarding processes, fulfilment
processes and assurance processes) and describes the interactions between E2E service management domain and
management domains during these processes.
Furthermore, it maps the management services used in the management processes to the northbound interfaces of
selected technology domains and references the underlying specifications of these interfaces. These mappings enable
the automation of lifecycle management across domains.
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 002: "Zero-touch network and Service Management (ZSM); Reference
Architecture".
[2] ETSI GS ZSM 007: "Zero-touch network and Service Management (ZSM); Terminology for
concepts in ZSM".
[3] ETSI GS NFV-IFA 013: "Network Functions Virtualisation (NFV) Release 3; Management and
Orchestration; Os-Ma-nfvo reference point - Interface and Information Model Specification".
[4] ETSI GS NFV-IFA 031: "Network Functions Virtualisation (NFV) Release 3; Management and
Orchestration; Requirements and interfaces specification for management of NFV-MANO".
[5] ETSI GS NFV-SOL 005: "Network Functions Virtualisation (NFV) Release 3; Protocols and Data
Models; RESTful protocols specification for the Os-Ma-nfvo Reference Point".
[6] ETSI TS 128 532: "5G; Management and orchestration; Generic management services (3GPP
TS 28.532 Release 16)".
[7] ETSI TS 128 531: "5G; Management and orchestration; Provisioning (3GPP TS 28.531
Release 16)".
[8] ETSI TS 128 541: "5G; Management and orchestration; 5G Network Resource Model (NRM);
Stage 2 and stage 3 (3GPP TS 28.541 Release 17)".
[9] ETSI TS 128 632: "Universal Mobile Telecommunications System (UMTS); LTE;
Telecommunication management; Inventory Management (IM) Network Resource Model (NRM)
Integration Reference Point (IRP); Information Service (IS) (3GPP TS 28.632 Release 16)".
[10] ETSI TS 128 552: "5G; Management and orchestration; 5G performance measurements (3GPP
TS 28.552 Release 16)".
[11] ETSI TS 128 554: "5G; Management and orchestration; 5G end to end Key Performance
Indicators (KPI) (3GPP TS 28.554 Release 16)".
ETSI
7 ETSI GS ZSM 008 V1.1.1 (2022-07)
[12] ETSI TS 128 622: "Universal Mobile Telecommunications System (UMTS); LTE; 5G;
Telecommunication management; Generic Network Resource Model (NRM) Integration
Reference Point (IRP); Information Service (IS) (3GPP TS 28.622 Release 16)".
[13] ETSI TS 128 658: "Universal Mobile Telecommunications System (UMTS); LTE;
Telecommunication management; Evolved Universal Terrestrial Radio Access Network
(E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); Information
Service (IS) (3GPP TS 28.658 Release 16)".
[14] ETSI TS 128 708: "Universal Mobile Telecommunications System (UMTS); LTE;
Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM)
Integration Reference Point (IRP); Information Service (IS) (3GPP TS 28.708 Release 16)".
[15] ETSI TS 132 425: "LTE; Telecommunication management; Performance Management (PM);
Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN)
(3GPP TS 32.425 Release 16)".
[16] ETSI TS 132 426: "LTE; Telecommunication management; Performance Management (PM);
Performance measurements Evolved Packet Core (EPC) network (3GPP TS 32.426 Release 16)".
[17] ETSI TS 128 527: "LTE; Telecommunication management; Life Cycle Management (LCM) for
mobile networks that include virtualized network functions; Stage 2 (3GPP TS 28.527
Release 16)".
[18] BBF TR-384: "Cloud Central Office Reference Architectural Framework", Technical Report,
Broadband Forum, January 2018.
[19] BBF TR-411: "Definition of interfaces between CloudCO Functional Modules", Technical Report,
Broadband Forum, April 2021.
[20] BBF TR-454: "YANG Modules for Network Map & Equipment Inventory", Technical Report,
Broadband Forum, July 2021.
[21] TMF628 (Version 2.0.1): "Performance Management API REST Specification", TM Forum
Specification.
[22] TMF633 (Version 4.0.0): "Service Catalog Management API REST Specification", TM Forum
Specification.
[23] TMF638 (Version 4.0.1): "Service Inventory Management API User Guide", TM Forum
Specification.
[24] TMF639 (Version 4.0.1): "Resource Inventory Management API User Guide", TM Forum
Specification.
[25] TMF640 (Version 4.0.1): "Service Activation and Configuration API User Guide", TM Forum
Specification.
[26] TMF641 (Version 4.1.0): "Service Ordering Management API User Guide", TM Forum
Specification.
[27] TMF642 (Version 4.0.1): "Alarm Management API User Guide", TM Forum Specification.
[28] TMF645 (Version 4.0.1): "Service Qualification Management API User Guide", TM Forum
Specification.
[29] TMF653 (Version 4.1.0): "Service Test Management API User Guide", TM Forum Specification.
[30] TMF657 (Version 4.0.1): "Service Quality Management API User Guide", TM Forum
Specification.
[31] TMF664 (Version 4.0.1): "Resource Function Activation and Configuration API User Guide", TM
Forum Specification.
ETSI
8 ETSI GS ZSM 008 V1.1.1 (2022-07)
[32] ONF TR-547: "TAPI Reference Implementation Agreement", Version 1.1.
NOTE: Available at https://opennetworking.org/wp-content/uploads/2021/12/TR-547-
TAPI_ReferenceImplementationAgreement_v1.1.pdf.
[33] ONF TR-548: "TAPI Reference Implementation Agreement for Streaming", Version 1.1.
NOTE: Available at https://opennetworking.org/wp-content/uploads/2021/12/TR-548-
TAPI_ReferenceImplementationAgreement-Streaming_v1.1.pdf.
[34] ONF Transport API SDK Version 2.1.3.
NOTE: Available at https://github.com/OpenNetworkingFoundation/TAPI/releases/tag/v2.1.3.
[35] IETF RFC 6020: "YANG - A Data Modeling Language for the Network Configuration Protocol
(NETCONF)".
[36] IETF RFC 6241: "Network Configuration Protocol (NETCONF)".
[37] IETF RFC 7950: "The YANG 1.1 Data Modeling Language".
[38] IETF RFC 8040: "RESTCONF Protocol".
[39] IETF RFC 8299: "YANG Data Model for L3VPN Service Delivery".
[40] IETF RFC 8345: "A YANG Data Model for Network Topologies".
[41] IETF RFC 8346: "A YANG Data Model for Layer 3 Topologies".
[42] IETF RFC 8466: "A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service
Delivery".
[43] IETF RFC 8639: "Subscription to YANG Notifications".
[44] IETF RFC 8641: "Subscription to YANG Notifications for Datastore Updates".
[45] IETF RFC 8650: "Dynamic Subscription to YANG Events and Datastores over RESTCONF".
[46] IETF RFC 8795: "YANG Data Model for Traffic Engineering (TE) Topologies".
[47] IETF RFC 8944: "A YANG Data Model for Layer 2 Network Topologies".
[48] IETF RFC 9094: "A YANG Data Model for Wavelength Switched Optical Networks (WSONs)".
[49] IETF RFC 9182: "A YANG Network Data Model for Layer 3 VPNs".
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-1: "Zero-touch network and Service Management (ZSM); Closed-loop
automation; Part 1: Enablers".
[i.2] ETSI TS 123 288: "5G; Architecture enhancements for 5G System (5GS) to support network data
analytics services (3GPP TS 23.288 Release 16)".
ETSI
9 ETSI GS ZSM 008 V1.1.1 (2022-07)
[i.3] 3GPP TS 28.104: "3rd Generation Partnership Project; Technical Specification Group Services
and System Aspects; Management and orchestration; Management Data Analytics (MDA)",
Release 17.
[i.4] draft-openconfig-rtgwg-gnmi-spec: Shakir, R. et al.: "gRPC Network Management Interface
(gNMI)", Internet draft, Version 01, expired, March 2018.
NOTE: Available at https://datatracker.ietf.org/doc/html/draft-openconfig-rtgwg-gnmi-spec-01. ®
[i.5] "gRPC : A high performance, open source universal RPC framework", Invoked 2021-12-10.
NOTE: Available at http://grpc.io.
[i.6] draft-ietf-teas-ietf-network-slices: "Framework for IETF Network Slices", Internet draft,
Version 10, work in progress.
NOTE: Available at https://datatracker.ietf.org/doc/draft-ietf-teas-ietf-network-slices/.
[i.7] draft-ietf-teas-ietf-network-slice-nbi-yang: "IETF Network Slice Service YANG Model", Internet
draft, Version 01, work in progress.
NOTE: Available at https://datatracker.ietf.org/doc/draft-ietf-teas-ietf-network-slice-nbi-yang/.
[i.8] draft-ietf-teas-yang-te: "A YANG Data Model for Traffic Engineering Tunnels, Label Switched
Paths and Interfaces", Internet draft, Version 29, work in progress.
NOTE: Available at https://datatracker.ietf.org/doc/draft-ietf-teas-yang-te/.
[i.9] draft-ietf-teas-yang-path-computation: "YANG Data Model for requesting Path Computation",
Internet draft, Version 18, work in progress.
NOTE: Available at https://datatracker.ietf.org/doc/draft-ietf-teas-yang-path-computation/.
[i.10] draft-ietf-ccamp-otn-tunnel-model: "YANG data model for tunnels in OTN TE Networks",
Internet draft, Version 16, work in progress.
NOTE: Available at https://datatracker.ietf.org/doc/draft-ietf-ccamp-otn-tunnel-model/.
[i.11] draft-ietf-ccamp-wson-tunnel-model: "A Yang Data Model for WSON Tunnel", Internet draft,
Version 06, work in progress.
NOTE: Available at https://datatracker.ietf.org/doc/draft-ietf-ccamp-wson-tunnel-model/.
[i.12] draft-ietf-ccamp-client-signal-yang: "A YANG Data Model for Transport Network Client
Signals", Internet draft, Version 06, work in progress.
NOTE: Available at https://datatracker.ietf.org/doc/draft-ietf-ccamp-client-signal-yang/.
[i.13] draft-ietf-ccamp-otn-topo-yang: "A YANG Data Model for Optical Transport Network Topology",
Internet draft, Version 14, work in progress.
NOTE: Available at https://datatracker.ietf.org/doc/draft-ietf-ccamp-otn-topo-yang/.
[i.14] draft-ietf-ccamp-eth-client-te-topo-yang: "A YANG Data Model for Ethernet TE Topology",
Internet draft, Version 02, work in progress.
NOTE: Available at https://datatracker.ietf.org/doc/draft-ietf-ccamp-eth-client-te-topo-yang/.
[i.15] draft-ietf-opsawg-l2nm: " A Layer 2 VPN Network YANG Model ", Internet draft, Version 15,
work in progress.
NOTE: Available at https://datatracker.ietf.org/doc/draft-ietf-opsawg-l2nm/.
[i.16] draft-ietf-opsawg-sap: "A Network YANG Model for Service Attachment Points (SAPs)", Internet
draft, Version 04, work in progress.
NOTE: Available at https://datatracker.ietf.org/doc/draft-ietf-opsawg-sap/.
ETSI
10 ETSI GS ZSM 008 V1.1.1 (2022-07)
[i.17] draft-ietf-opsawg-yang-vpn-service-pm: "A YANG Model for Network and VPN Service
Performance Monitoring", Internet draft, Version 07, work in progress.
NOTE: Available at https://datatracker.ietf.org/doc/draft-ietf-opsawg-yang-vpn-service-pm/.
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 [2] and the following apply:
domain service: service that is managed by a management domain
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI GS ZSM 007 [2] and the following apply:
th
5G 5 Generation
API Application Programming Interface
BBF Broadband Forum
CCAMP Common Control and Measurement Plane
CCO Cloud Central Office
CCO DO Cloud Central Office Domain Orchestrator
CloudCO Cloud Central Office
CRUD Create, Read, Update, Delete
CRUD-N CRUD plus Notify
E2E End-to-End
E-UTRAN Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network
EPC Evolved Packet Core
ETSI European Telecommunications Standards Institute
FM Fault Management
gNMI gRPC Network Management Interface
gRPC Google Remote Procedure Call
IETF Internet Engineering Task Force
IFA InterFaces and Architecture
IOC Information Object Class
KPI Key Performance Indicator
L2 Layer 2
L2NM Layer 2 Network Model
L2SM Layer 2 Service Model
L2VPN Layer 2 VPN
L3 Layer 3
L3NM Layer 3 Network Model
L3SM Layer 3 Service Model
L3VPN Layer 3 VPN
LCM LifeCycle Management
LTE Long-Term Evolution
MD Management Domain
MDA Management Data Analytics
MDAS Management Data Analytics Service
MnF Management Function
MnS Management Service
MOI Managed Object Instance
ETSI
11 ETSI GS ZSM 008 V1.1.1 (2022-07)
n/a not applicable
NBI NorthBound Interface
NFV Network Functions Virtualisation
NFVO NFV Orchestrator
NRM Network Resource Model
NSC Network Slice Controller
NWDAF Network Data Analytics Function
ONF Open Networking Foundation
OTN Optical Transport Network
PM Performance Management
SDK Software Development Kit
SOL SOLutions
TAPI Transport Application Programming Interfaces
TEAS Traffic Engineering Architecture and Signaling
TMF TM Forum
TR Technical Report
UC Use Case
VNF Virtualised Network Function
VPN Virtual Private Network
WG Working group
XML eXtensible Markup Language
YANG Yet Another Next Generation
4 Overview of cross-domain E2E service lifecycle
management
The E2E service lifecycle is managed using different processes.
Roughly, the processes can be divided into:
• onboarding processes that ingest a service model that was created during an out-of-scope service design phase
into the ZSM framework;
• fulfilment processes that bring up a service instance based on an onboarded service model, configure the
service instance, activate it for use and finally terminate it;
• assurance processes that ensure a service is free of faults (service problem management) and meets its SLSs
(service quality management).
Onboarding and fulfilment processes are typically finite and are executed per request. Assurance processes typically
execute continuously once set up, ideally in closed loops. ETSI GS ZSM 009-1 [i.1] defines enablers for closed loops.
The present document focuses on the cross-domain aspects of these management processes and what management
services can be used to implement those processes.
Figure 4-1 illustrates the management processes during the E2E service lifecycle. Furthermore, the figure indicates as
example the groups of management services introduced in ETSI GS ZSM 002 [1] that can be used to implement the
processes. Apart from the processes that start the lifecycle of a service instance (service instantiation and assurance
set-up) and end it (service decommissioning and assurance tear-down), the figure depicts sets of processes with no
particular order. The processes are further detailed in clause 5.
ETSI
12 ETSI GS ZSM 008 V1.1.1 (2022-07)

Figure 4-1: Management processes during the lifecycle of E2E services
Each management process during the E2E service lifecycle requires that the E2E service management domain
consumes management services from the management domains. For example, a fulfilment process might use
Orchestration services for service configuration, and Data Collection services to validate if the service quality
requirements are met initially. As another example, an assurance process might be realized as a closed loop using Data
Collection services, Data Analytics Services, Intelligence services together with Orchestration services to improve the
configuration in order to maintain the desired service quality.
A large set of these management services depends on the technology used in the underlying management domain. The
E2E service management domain needs to be able to consume the various management services from the management
domains via the endpoints that make up the northbound interface of the domain.
Figure 4-2 illustrates the set of technology domains considered in the present document. In deployments, there may be
additional technology domains. Clause 6 documents the northbound interfaces of management domains based on
different technologies.
In the present document, the NBIs of the E2E service management domain are defined in terms of ZSM management
services (see ETSI GS ZSM 002 [1] with extensions defined in Annex A of the present document). The technology
mapping of these NBIs is out of scope of the present document.
ETSI
13 ETSI GS ZSM 008 V1.1.1 (2022-07)

NOTE 1: NBIs depicted in figure 4-2 are neither mandatory nor exhaustive ones, but examples to be utilized.
NOTE 2: The cross-domain integration fabric is not depicted in figure 4-2 for simplicity.

Figure 4-2: Domain NBIs consumed during the management of the lifecycle of E2E services
Clause 7 documents gaps and commonalities between the different technology domains with respect to their northbound
interfaces.
ETSI
14 ETSI GS ZSM 008 V1.1.1 (2022-07)
5 Cross-domain E2E service lifecycle management
processes
5.1 Overview
Clause 5 introduces typical lifecycle management processes that the E2E service management domain performs to
manage E2E services throughout their lifespan and during which it interacts with the underlying management domains
that manage resources and domain services which are needed for the E2E service.
In deployments, processes may be combined or split.
For each process, a description, a process flow and a list of related management services are provided. The description
explains the overall purpose and task of the process. The procedure flow provides a graphical and a textual
representation of the individual steps of the process. For simplicity's sake, only requests are shown in the flows and
responses and acknowledgements are omitted. Furthermore, for the unsuccessful execution of the procedures, only error
conditions are defined, but no detailed error flows are specified. The list of related management services includes
management services that are produced or consumed by the E2E service management domain and therefore represent a
cross-domain integration point. Management services that are invoked internally by the management domain or E2E
service management domain (i.e. where producer and consumer are in the same domain) are not listed as these do not
require cross-domain integration or coordination.
In the following, the term "domain service" is used as shorthand for "a service that is managed by a management
domain".
The processes are split into three categories: Service onboarding, Service fulfilment and Service assurance, as depicted
in figure 4-1.
5.2 Service onboarding
5.2.1 Overview
The following sub-clauses introduce typical onboarding processes, i.e. processes that the E2E service management
domain performs to obtain E2E service models from service design (which is out of scope of the present document) and
that prepare the E2E service management domain and the management domains for the instantiation of such services.
5.2.2 Process: Service onboarding
5.2.2.1 Description
The "Service onboarding" process imports a new service model into the service catalogue of the E2E service
management domain, following the service design phase that is outside the scope of the present document. The E2E
service model is introduced in clause 6.6.5.2.3 of ETSI GS ZSM 002 [1].
Onboarding may optionally include the importing of a service template that allows to parameterize the service model
when a subsequent service instance creation is requested. A service template contains a customer-facing part and a
resource-facing part. The customer facing part, called the service offer descriptor, defines a set of parameters with their
allowed values or value ranges which can be used by the ZSM framework consumers to configure the characteristics of
the service they request to instantiate. The resource-facing part defines how to map the parameters in the service offer
descriptor to the realization of the service.
ETSI
15 ETSI GS ZSM 008 V1.1.1 (2022-07)
5.2.2.2 Procedure flow
Figure 5.2.2.2-1: Service onboarding
PRECONDITIONS:
• None.
The procedure, as illustrated in figure 5.2.2.2-1, consists of the following steps:
1. The ZSM framework consumer requests the creation of a service model and its import into the service
catalogue managed by the E2E service management domain by consuming the "Manage service models"
capability of the "Managed services catalogue management service".
2. Optionally, the ZSM framework consumer also requests the creation of a related service template and its
import into the service catalogue, consuming the same service.
ETSI
16 ETSI GS ZSM 008 V1.1.1 (2022-07)
3. The E2E service management domain validates the service model and, if it has been provided, the service
template.
4. The E2E service management domain determines the domain services that are necessary to provide the E2E
service.
5. To determine the missing domain service models (if any), the E2E service management domain queries from
the involved management domains the service catalogue entries of those domain service models that are
needed as components of the E2E service, using the "Manage service models" capability of the "Managed
services catalogue management service".
If domain service models are missing that are needed by the E2E service, steps 6 to 8 are performed:
6. Optionally, in special cases if the E2E service management domain is able to provide certain domain service
models to the management domains, it onboards them into the relevant management domains, using the
"Manage service models" capability of the "Managed services catalogue management service".
7. Optionally, if management domains support being informed about the need to provide certain domain services
that are currently missing, the E2E service management domain informs them using the "Request missing
service catalogue entry" capability of the "Managed services catalogue management service".
NOTE: Thi
...