ETSI GS ZSM 003 V1.1.1 (2021-06)

Zero-touch network and Service Management (ZSM); End-to-end management and orchestration of network slicing

DGS/ZSM-003ed111_Slicing

General Information

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

Standards Content (Sample)

GROUP SPECIFICATION
Zero-touch network and Service Management (ZSM);
End-to-end management and orchestration of network slicing
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 003 V1.1.1 (2021-06)

Reference
DGS/ZSM-003ed111_Slicing
Keywords
network management, orchestration, service,
slicing
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
3 ETSI GS ZSM 003 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 . 7
3 Definition of terms, symbols and abbreviations . 8
3.1 Terms . 8
3.2 Symbols . 8
3.3 Abbreviations . 8
4 Concept of E2E network slicing management and orchestration . 10
4.1 Roles in network slicing . 10
4.2 Communication service provided by network slice . 10
4.3 Typical scenarios of using network slicing . 10
4.3.1 Overview . 10
4.3.2 Using "Network Slices as NOP internals" . 11
4.3.3 Adopting "Network Slices as a Service" model . 12
5 E2E network slicing management and orchestration Architecture . 14
5.1 Network slicing management architecture . 14
6 E2E network slicing management and orchestration solutions . 16
6.1 E2E network slice management . 16
6.1.1 Requirements for Network Slice . 16
6.1.2 Actions in LCM of network slicing . 16
6.2 Providing communication service in the scenario of network slice as NOP internals . 17
6.2.1 Overall Description . 17
6.2.2 E2E communication service provisioning . 18
6.2.2.1 Overall Description . 18
6.2.2.2 Solution of E2E communication service provisioning . 18
6.2.2.2.1 Solution of E2E communication service allocation . 18
6.2.2.2.2 Solution of E2E communication service modification . 22
6.2.2.2.3 Solution of E2E communication service deallocation . 24
6.2.2.2.4 Solution of E2E communication service activation . 28
6.2.2.2.5 Solution of E2E communication service deactivation . 32
6.2.2.2.6 Solution of E2E network slice instance feasibility check . 35
6.2.2.3 Coordination with transport network for supporting of network slicing provisioning . 39
6.2.3 E2E network slicing performance management . 39
6.2.3.1 Overall Description . 39
6.2.3.2 Solution of E2E network slice performance file-based reporting . 40
6.2.3.3 Solution of E2E network slice performance data streaming reporting . 42
6.2.3.4 Solution of E2E network slice performance assurance . 44
6.2.4 E2E network slicing fault management . 45
6.2.4.1 Overall Description . 45
6.2.4.2 Example of E2E network slice fault notification . 45
6.2.4.3 Example of getting E2E network slice alarm list . 46
6.3 Providing communication service in the scenario of network slice as a service (NsaaS) . 47
6.3.1 Overall Description . 47
6.3.2 End-to-end network slicing provisioning . 48
6.3.2.1 Introduction . 48
6.3.2.2 Solution of E2E network slicing provisioning . 48
6.3.2.2.1 Solution of E2E network slice allocation with new network slice instance . 48
6.3.2.2.2 Solution of E2E network slice modification . 50
6.3.2.2.3 Solution of E2E network slice deallocation . 52
ETSI
4 ETSI GS ZSM 003 V1.1.1 (2021-06)
6.3.3 E2E network slicing performance management . 53
6.3.3.1 Overall Description . 53
6.3.3.2 Solution of E2E network slice performance reporting . 53
6.4 Topology service for E2E network slicing services . 53
7 Management exposure to vertical consumers . 54
7.1 Network slice SLA/SLS . 54
7.1.1 Network slice SLA/SLS in GSMA and 3GPP . 54
7.1.2 Network slice SLA in ZSM . 55
7.1.3 Network slice management models . 56
7.2 Management exposure to vertical consumers in NOP Internal scenario . 57
7.3 Management exposure to vertical consumers in NSaaS scenario . 57
Annex A (informative): Available output from standard groups and open source groups on
network slicing management . 59
A.1 Telecommunication . 59
A.1.1 3GPP TSG SA2 . 59
A.1.2 3GPP TSG SA3 . 59
A.1.3 3GPP TSG SA5 . 59
A.1.4 NGMN . 60
A.1.5 GSMA . 60
A.1.6 ETSI NFV EVE012 . 60
A.1.7 IETF . 61
Annex B (informative): Deployment scenario . 63
B.1 Deployment scenario to support network slicing using NFV. 63
B.2 Providing media streaming service by deployment of an E2E network slicing . 64
Annex C (informative): Sequences of Network Slice Management by ZSM . 66
C.0 Introduction . 66
C.1 Sequence of network slice instance Creation . 66
C.1.1 Basic Sequence of network slice instance Creation . 66
C.1.2 Domain Level Sequence of network slice instance Creation . 67
C.1.3 Domain Level Sequence of network slice instance Creation with resource adjustment . 68
C.1.4 Patterns of interaction between E2E Service Management Domain and Management Domains . 70
C.2 Sequence of network slice instance Auto Healing . 70
C.3 Sequence of network slice instance Termination . 72
C.3.1 Basic Sequence of network slice instance Termination. 72
C.3.2 Domain-Level Sequence of network slice instance Termination . 73
C.3.3 Domain-Level Sequence of network slice instance Termination with resource adjustment . 74
C.4 Sequence of Switching Network Slice . 75
Annex D (informative): Recommendation on the cooperation with the standard groups and
open source groups . 78
D.1 Coordination between ZSM and other groups. 78
Annex E (informative): Network slice subnet and Management Domain . 81
Annex F (informative): MnS mapping relations . 83
F.1 MnS mapping table between ETSI GS ZSM 002 and 3GPP SA5 . 83
Annex G (informative): Change History . 84
History . 87

ETSI
5 ETSI GS ZSM 003 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).
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 003 V1.1.1 (2021-06)
1 Scope
The present document specifies the E2E network slicing management solutions and related management interfaces. The
E2E network slicing including provisioning, performance assurance and fault management of an E2E slice instance
across multiple management 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 TS 123 501 (V15.2.0): "5G; System Architecture for the 5G System (3GPP TS 23.501
version 15.2.0 Release 15)".
[2] ETSI TS 123 502 (V15.2.0): "5G; Procedures for the 5G System (3GPP TS 23.502 version 15.2.0
Release 15)".
[3] ETSI TS 123 503 (V15.2.0): "5G; Policy and Charging Control Framework for the 5G System;
Stage 2 (3GPP TS 23.503 version 15.2.0 Release 15)".
[4] ETSI TS 128 530 (V15.0.0): "5G; Management and orchestration; Concepts, use cases and
requirements (3GPP TS 28.530 version 15.0.0 Release 15)".
[5] ETSI TS 128 531 (V15.0.0): "5G; Management and orchestration; Provisioning (3GPP TS 28.531
version 15.0.0 Release 15)".
[6] ETSI TS 128 550 (V16.7.0): "5G; Management and orchestration; Performance assurance (3GPP
TS 28.550 version 16.7.0 Release 16)".
[7] ETSI TS 128 541 (V15.0.1): "5G; Management and orchestration; 5G Network Resource Model
(NRM); Stage 2 and stage 3 (3GPP TS 28.541 version 15.0.1 Release 15)".
[8] ETSI TS 128 552 (V15.0.0): "5G; Management and orchestration; 5G performance measurements
(3GPP TS 28.552 version 15.0.0 Release 15)".
[9] ETSI TS 128 554 (V15.0.1): "5G; Management and orchestration; 5G end to end Key Performance
Indicators (KPI) (3GPP TS 28.554 version 15.0.1 Release 15)".
[10] ETSI GS NFV-IFA 013: "Network Functions Virtualisation (NFV) Release 3; Management and
Orchestration; Os-Ma-nfvo reference point - Interface and Information Model Specification".
[11] ETSI GS ZSM 007: "Zero-touch network and Service Management (ZSM); Terminology for
concepts in ZSM".
[12] ETSI GS ZSM 002: "Zero-touch network and Service Management (ZSM); Reference
Architecture".
[13] ETSI TS 128 532 (V15.0.1): "5G; Management and orchestration; Generic management services
(3GPP TS 28.532 version 15.0.1 Release 15)".
ETSI
7 ETSI GS ZSM 003 V1.1.1 (2021-06)
[14] ETSI TS 128 545 (V15.0.0): "5G; Management and orchestration; Fault Supervision (FS) (3GPP
TS 28.545 version 15.0.0 Release 15)".
[15] ETSI TS 128 526 (V16.0.0): "LTE; Telecommunication management; Life Cycle Management
(LCM) for mobile networks that include virtualized network functions; Procedures (3GPP
TS 28.526 version 16.0.0 Release 16)".
[16] GSMA PRD NG.116 v1.0 (2019-05): "Generic Network Slice Template", v1.0.
[17] ETSI GS ZSM 001: "Zero-touch network and Service Management (ZSM); Requirements based
on documented scenarios".
[18] ETSI TS 133 501 (V16.4.0): "5G; Security architecture and procedures for 5G System (3GPP
TS 33.501 version 16.4.0 Release 16)".
[19] ETSI TS 128 622 (V16.7.1): "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 version 16.7.1 Release 16)".
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] 3GPP TR 33.811 (V0.4.0) (2018-01): "Study on security aspects of 5G network slicing
management".
[i.2] GSMA: "5G Network Slicing Report: From Vertical Industry Requirements to Network Slice
Characteristics".
[i.3] ETSI GR NFV-EVE 012: "Network Functions Virtualisation (NFV) Release 3; Evolution and
Ecosystem; Report on Network Slicing Support with ETSI NFV Architecture Framework".
[i.4] TMF641: "Service Ordering API REST Specification".
[i.5] TMF638: "Service Inventory Management API REST Specification".
[i.6] TMF633: "Service Catalog Management API REST Specification".
[i.7] TMF628: "Performance Management API REST Specification".
[i.8] TMF642: "Alarm Management API REST Specification".
[i.9] IETF RFC 8453: "Framework for Abstraction and Control of TE Networks (ACTN)".
[i.10] IETF RFC 8632: "A YANG Data Model for Alarm Management", S. Vallin et al.
[i.11] draft-ietf-teas-yang-te work in progress: "A YANG Data Model for Traffic Engineering Tunnels
and Interfaces", T. Saad et al.
[i.12] draft-ietf-teas-actn-pm-telemetry-autonomics work in progress: "YANG models for VN/TE
Performance Monitoring Telemetry and Scaling Intent Autonomics", Y. Lee et al.
[i.13] IETF RFC 8795: "YANG Data Model for TE Topologies".
[i.14] draft-ietf-teas-enhanced-vpn work in progress: "A framework for Enhanced Virtual Private
Networks (VPN+) Service", J. Dong et al.
ETSI
8 ETSI GS ZSM 003 V1.1.1 (2021-06)
[i.15] draft-ietf-teas-ietf-network-slices-03: "Framework for IETF Network Slices".
[i.16] IETF RFC 8466: "A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service
Delivery".
[i.17] NGMN Alliance: "Description of Network Slicing Concept", September 2016.
[i.18] NGMN Alliance: "5G E2E Architectural framework v2.0", February 2018.
[i.19] IETF RFC 8299: "YANG Data Model for L3VPN Service Delivery".
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 [11] and the following apply:
E2E network slicing: set of management and orchestration activities that allow the deployment and operation of
network slices across multiple management domains
network slice: logical network that provides specific network capabilities and network characteristics, supporting
various service properties for network slice customers
network slice subnet: representation of a set of network functions and the associated resources (e.g. compute, storage
and networking resources) supporting network slice
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI GS ZSM 007 [11] and the following apply:
AAA Authentication-Authorisation-Accounting
ACTN Abstraction and Control of TE Networks
AI Artificial Intelligence
AMF Access and Mobility Management Function
AN Access Network
API Application Programming Interface
AS Access Stratum
BBF Broadband Forum
CMI Customer Network Controller - Multi-Domain Service Coordinator Interface
CN Core Network
CSC Communication Service Customer
CSM Communication Service Management
CSP Communication Service Provider
DCN Data Center Network
DL DownLink
DN Distinguished Name
DRB Data Radio Bearer
DSL Domain Specific Language
EVR Evaluation Result
GSM Global System for Mobile communications
GSMA GSM Association
GST Generic network Slice Template
IOC Information Object Class
KPI Key Performance Indicator
ETSI
9 ETSI GS ZSM 003 V1.1.1 (2021-06)
LCM Life Cycle Management
MD Management Domain
MDSC Multi-Domain Service Coordinator
MEF Metro Ethernet Forum
MNO Mobile Network Operator
MnS Management Service
MOI Managed Object Instance
MPI Main Path Interface
MPLS Multiprotocol Label Switching
NBI Northbound Interface
NEST NEtwork Slice Type
NF Network Function
NFVI NFV Infrastructure
NFVO NFV Orchestrator
NG Next Generation
NGMN Next Generation Mobile Networks
NG-RAN NG Radio Access Network
NOP Network Operator
NRM Network Resource Model
NSC Network Slice Controller
NSDT Network Slice Design Team
NSE Network Slice Endpoints
NSI Network Slice Instance
NSM Network Service Management
NSRE Network Slice Realization Endpoints
NSS Network Slice Subnet
NSSAI Network Slice Selection Assistance Information
NSSI Network Slice Subnet Instance
OAM Operation, Administration and Maintenance
PDU Protocol Data Unit
PLMN Public Land Mobile Network
PM Performance Management
PNC Provisioning Network Controller
PNF Physical Network Function
PRB Physical Resource Block
PRD Permanent Reference Document
PSA PDU session anchor
RAN Radio Access Network
RRM Radio Resource Management
SBI SouthBound Interface
Serv-Orch Service Orchestration service
SLA Service Level Agreement
SLS Service-Level Specification
SMF Session Management Function
S-NSSAI Single Network Slice Selection Assistance Information
TEAS Traffic Engineering and Architecture Signaling
TM Telecom Management
TN Transport Network
T-NSSMF Transport Network Slice Subnet Management Function
TSG Technical Specification Group
UE User Equipment
UL UpLink
UPF User Plane Function
VLAN Virtual Local Area Network
VN Virtualised Network
VNF Virtualised Network Function
VPN Virtual Private Network
WAN Wide Area Network
YANG Yet Another Next Generation
ETSI
10 ETSI GS ZSM 003 V1.1.1 (2021-06)
4 Concept of E2E network slicing management and
orchestration
4.1 Roles in network slicing
In the context of 5G networks, responsibilities regarding network management operations have been defined and
assigned to different roles, see clause 4.8 of ETSI TS 128 530 [4]. The ZSM Framework Consumer plays the role of
Communication Service Customer (CSC) and uses communication services provided by Communication Service
Provider (CSP). The communication provider in turn uses the network provided by the role network operator.
4.2 Communication service provided by network slice
The following diagram shows the relation between communication service instance, network slice instance and network
slice subnet instance.
Figure 4.2-1: A variety of communication services provided by multiple network slices
A vertical may have multiple communication services and one or more communication services may be supported by
one network slice instance as shown in ETSI TS 128 530 [4], clause 4.1.3.
NOTE: The concepts of "vertical" and "vertical customer" are used interchangeably throughout the present
document.
4.3 Typical scenarios of using network slicing
4.3.1 Overview
There are two scenarios for using network slicing, as specified in clauses 4.1.6 and 4.1.7 of ETSI TS 128 530 [4]:
• Network Slices as NOP internals.
ETSI
11 ETSI GS ZSM 003 V1.1.1 (2021-06)
• Network Slice as a Service (NSaaS).
4.3.2 Using "Network Slices as NOP internals"
In the "Network Slices as NOP internals" scenario, one entity takes both CSP and NOP roles and provides
communication services to vertical customers, which take the role of CSCs. The network slice instances are not visible
to the verticals. The entity decides whether the network slices instances or the network is used to support the
communication services (e.g. for internal network resource utilization consideration, etc.). This scenario allows the
vertical consumer to use the communication service and optionally allows the vertical to monitor the network status of
the network that supports the communication service.
Figure 4.3.2-1 quoted from 3GPP (see ETSI TS 128 530 [4]) illustrates an example of how network slices can be
utilized to deliver communication services based on the 3GPP defined roles.
CSC
Entity takes
both CSP and
CSP
NOP roles offer
CS
NOP
Management
NSI
view
Network
NF NF DN
view
Network Slice
a)
Figure 4.3.2-1: 3GPP example of Network Slice as NOP internals
Figure 4.3.2-2 illustrates an example of how network slices from business view can be utilized to deliver
communication services in ZSM.
A network slice consists ofa group of NFs. The business entity X (e.g. MNO) takes the role of both NOP and CSP and
delivers communication services to vertical customers. Only the communication service is exposed to the vertical
customer. The vertical should be able to monitor the communication service status (e.g. administrative status,
operational status, etc.) and performance data via the exposed interfaces.
ETSI
12 ETSI GS ZSM 003 V1.1.1 (2021-06)

Figure 4.3.2-2: ZSM example of Network Slice as NOP internals
4.3.3 Adopting "Network Slices as a Service" model
In the "Network Slice as a Service" scenario, a network slice can be offered to vertical as a service. This scenario allows
a vertical customer to use the network slice and optionally allows the vertical to manage the network slice instance via
management exposure interface. In addition, verticals can offer their own services (e.g. communication services) that
rely on the new network slice.
Figure 4.3.3-1 quoted from 3GPP (see [4]) illustrates an example of how network slices can be utilized to deliver
communication services, including Network Slice as a Service reusing the 3GPP defined roles.
NS
NS
Figure 4.3.3-1: 3GPP examples of Network Slice as a Service being utilized
to deliver communication services to customers
ETSI
13 ETSI GS ZSM 003 V1.1.1 (2021-06)
Figure 4.3.3-2 illustrates an example of how network slices from a business view can be utilized to deliver
communication services in ZSM.
In this example, CSP uses the network slice offered by NOP and its own network functions to deliver communication
services to vertical customers (CSC). CSP and NOP corresponds to different business entities in this example.

NOTE 1: Network slice shown on the left side of Figure 4.3.3-2 is a managed object instance created by NOP of
Business Entity X. It is offered as a network slice as a service to Business Entity Y as a network slice shown
on the right side of the same figure. CSP of Business Entity Y uses Distinguished Name to refer to and access
the network slice created in the NOP.
NOTE 2: Depending on the use case, the business entity Y could represent a vertical customer or another MNO.

Figure 4.3.3-2: ZSM example of Network Slice as a Service being utilized
to deliver communication services to customers
In another example, as shown in Figure 4.3.3-3, CSP of Business Entity Y may use the network slice offered by NOP of
Business Entity X and additional network functions to build a new network slice.
ETSI
14 ETSI GS ZSM 003 V1.1.1 (2021-06)

Figure 4.3.3-3: ZSM example of Network Slice as a Service being utilized to build a new network slice
5 E2E network slicing management and orchestration
Architecture
5.1 Network slicing management architecture
Figure 5.1-1 describes an example of ZSM architecture deployment for network slicing management. In this scenario,
the management domains for E2E Service, AN, CN and TN exist. The deployment is according to the architecture
defined in ETSI GS ZSM 002 [12].
ETSI
15 ETSI GS ZSM 003 V1.1.1 (2021-06)

Figure 5.1-1: ZSM architecture deployment example for network slicing management
NOTE: This is one possible example shows how to deploy management domains.
The components of E2E network slicing architecture are described as follows:
• E2E Service MD (E2E Service Management Domain) is a provider of the E2E network slicing related
management services based on Management Functions. E2E Service MD is also a consumer of the
management services provided by AN MD, CN MD and TN MD.
• AN MD (Access Network Management Domain) is a provider of the AN slice subnet-related management
services based on Management Functions.
• CN MD (Core Network Management Domain) is a provider of the CN slice subnet-related management
services based on Management Functions.
• TN MD (Transport Network Management Domain) is a provider of the TN slice subnet-related management
services based on Management Functions.
A network slice instance is composed of one E2E network slice subnet. One E2E network slice subnet is composed of
one or more network slice subnets as shown in ETSI TS 128 541 [7], clause 6.2.1.
ETSI
16 ETSI GS ZSM 003 V1.1.1 (2021-06)
6 E2E network slicing management and orchestration
solutions
6.1 E2E network slice management
6.1.1 Requirements for Network Slice
GSMA has provided information that capturing service requirements for a network slice. In GSMA PRD NG.116 [16],
a Generic network Slice Template (GST) is defined as a set of attributes that can characterize a type of network
slice/service. The value of each attribute is assigned to express a set of requirements to support a network slice
customer's use case. The NEtwork Slice Type (NEST) is a GST filled with values. The NEST can be used as an input to
the network slice preparation as depicted in Figure 6.1.1-1.
Different NESTs allow describing different types of network slices. For the network slices based on standardized
service types, e.g. eMBB, uRLLC and mIoT, the network operator may have a set of the readymade, standardized
NESTs. For the network slices addressing specific use cases, the network operator can create additional NESTs.
GST
CSC
CSC Use Case
NSC Use Case Network Slice Preparation
NEST
NEST
Requirements
Figure 6.1.1-1: GST and NEST in context of the network slice lifecycle
GST attributes can be classified into two main categories:
• Character attributes - characterize a network slice. They can be further split into:
- performance-related attributes, which specify the Key Performance Indicators (KPIs) supported by the
network slice;
- functionality-related attributes, which specify the functionality provided by the network slice;
- control and management-related attributes, which specify what control and management capabilities are
handed over to the vertical in order to operate the network slice.
• Scalability attributes - provide information about the scalability of the network slice.
6.1.2 Actions in LCM of network slicing
This clause describes the actions in the Life Cycle Management (LCM) of an E2E network slice instance, which is an
overview of the E2E network slicing management and orchestration solutions.
As shown in ETSI TS 128 530 [4], Figure 4.3.1.1, the management of network slice instance contains four phases:
Preparation, Commissioning, Operation and Decommissioning.
ETSI
17 ETSI GS ZSM 003 V1.1.1 (2021-06)

Figure 6.1.2-1: Lifecycle of network slice instance
During the Preparation phase, a capability check from the network environment is necessary.
During the Commissioning, Operation and Decommissioning phases, the following actions are necessary for the
network slice instance provisioning:
• Creation
For network slice instance allocation, the provider may create a new network slice instance or using an
existing network slice instance to satisfy the request.
• Activation
• Modification
• De-activation
• Termination
For network slice instance deallocation, the provider may terminate the network slice instance.
During the Operation phase, the following actions are necessary for fault and performance management:
• Supervision
• Reporting
6.2 Providing communication service in the scenario of network
slice as NOP internals
6.2.1 Overall Description
In the scenario of network slice as NOP internals, the operator plays CSP and NOP roles simultaneously to provide
communication services and network services.
The communication services provided by the operator may include such as eMBB, mIoT and critical communication.
ETSI
18 ETSI GS ZSM 003 V1.1.1 (2021-06)

Figure 6.2.1-1: High-level model of roles for network slice
as NOP internals based on ETSI TS 128 530 [4]
In the "Network Slices as NOP internals" scenario, see clause 4.1.7 of ETSI TS 128 530 [4], the provisioning of the
network is provided by E2E service management domain. For example, in the case of operator A operating the E2E
service management domain, operator A provides communication services to vertical consumers to satisfy
service-related requirements whilst the one or more network slice instances internally deployed by operator A are not
visible to the vertical consumers.
Furthermore, as a consumer, E2E service management domain consumes the provisioning management service for
network slice subnet instance provided by respective management domains, for example, AN management domain, CN
management domain and TN management domain managed by vendors.
Optionally, the operator provides the management services to some vertical consumers who have requirements of
acquiring some of the capabilities of service management. The E2E management services exposed by the operator may
include capabilities such as monitoring of E2E service status, provisioning of E2E service.
6.2.2 E2E communication service provisioning
6.2.2.1 Overall Description
The management services (operations, notifications and information model) provided by E2E service management
domain, management services provided by CN management domain and AN management domain should refer to ETSI
TS 128 531 [5]. This clause provides the possible procedures for E2E network slicing management according to the
example ZSM architecture deployment for network slicing in Figure 5.1-1.
6.2.2.2 Solution of E2E communication service provisioning
6.2.2.2.1 Solution of E2E communication service allocation
Figure 6.2.2.2.1-1 illustrates one of the possible solutions of allocating network with E2E network slice for
communication services in the scenario of network slice as NOP internals. In the scenario of network slice as NOP
internals, ZSM Framework Consumer (e.g. vertical customer) decides to deploy a service.
NOTE: The sequence in this clause assumes a network structure consisting of AN/CN/TN MD.
ETSI
19 ETSI GS ZSM 003 V1.1.1 (2021-06)
ZSM framework
E2E Service MD AN MD TN MD
CN MD
consumer
(1) E2E service orchestration service
(2) Decide to use network slice
to fulfill the request
(3a) Feasibility check service
(3b) Response for feasibility check
(3c) Feasibility check service
(3d) Response for feasibility check
(3e) Feasibility check service
(3f) Response for feasibility check
(4) Decide to continue slice allocation
(5a) Domain orchestration service (NSSI allocation )
(5b) Domain orchestration service (NSSI allocation )
(5c) Domain orchestration service (NSSI allocation )
(6a) NSSI allocation >
(6b) NSSI allocation >
(6c) NSSI allocation>
(7a) Response for NSSI allocation
(7b) Response for NSSI allocation
(7c) Response for NSSI allocation
(8) NSI activation procedure (in case of NSI
allocation with activation)
(9) E2E service orchestration service

Figure 6.2.2.2.1-1: Allocating network with E2E network slice for communication services
1) E2E Service MD (E2E Service Management Domain) which includes the function of NSM (network service
management) and CSM (communication service management), as communication service providers, acquires
the service requirements on receiving the request from ZSM Framework Consumer by utilizing E2E service
orchestration service in clause 6.6.5.2.1, ETSI GS ZSM 002 [12] (the service may be implemented by TM
Forum Open API, see API operation of Create Service in TMF638 [i.5]).
2) The E2E Service MD may decide to use network slice to fulfil the service-related requirements.
ETSI
20 ETSI GS ZSM 003 V1.1.1 (2021-06)
3a) The E2E Service MD derives the requirements for AN from the requirements received in step 1. Then, it sends
a request to AN MD by utilizing feasibility check service in clause 6.5.5.2.2 of ETSI GS ZSM 002 [12] to
check the feasibility of required resources and, if yes, reserves them. The feasibility check and reservation
shall be processed in the same transaction
...