ETSI TS 128 530 V15.3.0 (2020-01)

5G; Management and orchestration; Concepts, use cases and requirements (3GPP TS 28.530 version 15.3.0 Release 15)

RTS/TSGS-0528530vf30

General Information

• Status: Published
• Publication Date: 14-Jan-2020
• Technical Committee: 3GPP SA 5 - Telecom Management
• Current Stage: 12 - Completion
• Completion Date: 15-Jan-2020

Standards Content (Sample)

ETSI TS 128 530 V15.3.0 (2020-01)






TECHNICAL SPECIFICATION
5G;
Management and orchestration;
Concepts, use cases and requirements
(3GPP TS 28.530 version 15.3.0 Release 15)

---------------------- Page: 1 ----------------------
3GPP TS 28.530 version 15.3.0 Release 15 1 ETSI TS 128 530 V15.3.0 (2020-01)



Reference
RTS/TSGS-0528530vf30
Keywords
5G
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 2020.
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

---------------------- Page: 2 ----------------------
3GPP TS 28.530 version 15.3.0 Release 15 2 ETSI TS 128 530 V15.3.0 (2020-01)
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.
Legal Notice
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp.
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: 3 ----------------------
3GPP TS 28.530 version 15.3.0 Release 15 3 ETSI TS 128 530 V15.3.0 (2020-01)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 5
Introduction . 5
1 Scope . 6
2 References . 6
3 Definitions and abbreviations . 6
3.1 Definitions . 6
3.2 Abbreviations . 7
4 Concepts and background . 7
4.1 General concepts . 7
4.1.1 Management of 5G networks and network slicing . 7
4.1.2 Types of communication services . 8
4.1.3 Communication services using network slice instances . 8
4.1.4 Communication services requirements . 9
4.1.5 NSI Lifecycle and relationship to service instances . 10
4.1.6 Network Slice as a Service (NSaaS) . 10
4.1.7 Network Slices as NOP internals . 11
4.1.8 Network slice delivery concepts . 12
4.2 Principles . 12
4.2.1 General Principles . 12
4.2.2 Principles of network slicing management framework . 12
4.3 Management aspects of network slicing . 13
4.3.1 Introduction. 13
4.3.2 Preparation . 14
4.3.3 Commissioning . 14
4.3.4 Operation . 14
4.3.5 Decommissioning . 14
4.4 Managed network slice concepts . 14
4.4.1 General . 14
4.5 Network slice subnet concepts . 15
4.6 Slice profile concepts . 15
4.7 Coordination with management systems of non-3GPP parts . 16
4.8 Roles related to 5G networks and network slicing management . 16
5 Business level requirements . 17
5.1 Requirements . 17
5.1.1 General requirements . 17
5.1.2 Network slicing management . 18
5.1.3 CM requirements . 20
5.2 Actor roles . 20
5.3 Telecommunication resources . 20
5.4 High-level use cases . 21
5.4.1 Network slicing supporting communication services . 21
5.4.2 Provisioning of a network slice instance. 22
5.4.3 Provisioning of a network slice subnet instance . 23
5.4.4 Performance management of a Network Slice Instance (NSI). 23
5.4.5 Performance management of a Network Slice Subnet Instance (NSSI) . 24
5.4.6 Report fault management data of a network slice instance . 24
5.4.7 Report fault management data of a network slice subnet instance. 25
5.4.8 Multiple operator support for network slicing . 25
5.4.9 Manage network slice with agreed performance . 26
ETSI

---------------------- Page: 4 ----------------------
3GPP TS 28.530 version 15.3.0 Release 15 4 ETSI TS 128 530 V15.3.0 (2020-01)
5.4.10 Communication services using network with or without slicing . 26
5.4.11 Exposure of network slice management data for network slice as a service case . 27
5.4.12 Exposure of network slice management capability . 27
5.4.13 To modify the network slice instance due to changed demand . 28
5.4.14 Management data analytics for 5G networks . 28
5.4.15 Capacity management of Network Slice Instances (NSIs) and Network Slice Subnet Instances
(NSSIs) . 29
Annex A (informative): Change history . 30
History . 31

ETSI

---------------------- Page: 5 ----------------------
3GPP TS 28.530 version 15.3.0 Release 15 5 ETSI TS 128 530 V15.3.0 (2020-01)
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
Introduction
Network slicing is a key feature for 5G. Network slicing is a paradigm where logical networks/partitions are created,
with appropriate isolation, resources and optimized topology to serve a purpose or service category (e.g. use case/traffic
category, or for MNO internal reasons) or customers (logical system created "on demand").
ETSI

---------------------- Page: 6 ----------------------
3GPP TS 28.530 version 15.3.0 Release 15 6 ETSI TS 128 530 V15.3.0 (2020-01)
1 Scope
The present document specifies the concepts, use cases and requirements for management of network slicing in mobile
networks. The 3GPP management system directly manages only the parts of the network that consist of network
functions specified in 3GPP (e.g. 5G RAN, 5G CN and IMS). For the network functions specified by other SDOs, the
management impact of network slicing is addressed as required. For example, regarding the Transport Network (TN) part
supporting connectivity within and between CN and RAN parts, 3GPP management system may provide link
requirements (e.g. topology, QOS parameters) to the TN management system.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.261 "Service requirements for next generation new services and markets".
[3] 3GPP TS 23.501: " System Architecture for the 5G system".
[4] 3GPP TS 38.401 "NG-RAN; Architecture description".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following
apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP
TR 21.905 [1].
network slice: Defined in 3gpp TS 23.501 v1.4.0 [3].
network slice instance: Defined in 3GPP TS 23.501 V1.4.0 [3].
network slice subnet: a representation of the management aspects of a set of Managed Functions and the required
resources (e.g. compute, storage and networking resources).
network slice subnet instance: an instance of Network Slice Subnet representing the management aspects of a set of
Managed Function instances and the used resources (e.g. compute, storage and networking resources).
Service Level Specification: a set of service level requirements associated with a Service Level Agreement to be
satisfied by a network slice instance
NOTE: Network Slice Subnet Information Object Class describes the structure (i.e. contained components and
connectivity between them) and configuration of a network slice subnet, as well as network capability.
ETSI

---------------------- Page: 7 ----------------------
3GPP TS 28.530 version 15.3.0 Release 15 7 ETSI TS 128 530 V15.3.0 (2020-01)
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
3GPP TR 21.905 [1].
CSC Communication Service Customer
CSP Communication Service Provider
DN Data Network
MNO Mobile Network Operator
NOP Network Operator
NSaaS Network Slice as a Service
NSaasC Network Slice as a Service Customer
NSaaSP Network Slice as a Service Provider
NSC Network Slice Customer
NSI Network Slice Instance
NSP Network Slice Provider
NSS Network Slice Subnet
NSSI Network Slice Subnet Instance
SLA Service Level Agreement
SLS Service Level Specification
TN Transport Network
4 Concepts and background
4.1 General concepts
4.1.1 Management of 5G networks and network slicing
5G system consists of 5G Access Network (AN), 5G Core Network and UE, see TS 23.501 [3].
5G system is expected to be able to provide optimized support for a variety of different communication services,
different traffic loads, and different end user communities, see clause 4 of TS 22.261 [2]. For example, the
communication services using network slicing may include:
- V2X services
The 5G system aims to enhance its capability to meet KPIs that emerging V2X applications require. For these
advanced applications, the requirements, such as data rate, reliability, latency, communication range and speed,
are made more stringent, see clause 4 of TS 22.261 [2].
- 5G seamless eMBB service with FMC
As one of the key technologies to enable network slicing, fixed mobile convergence (FMC) which includes
wireless-to-the-everything (WTTx) and fibre-to-the-everything (FTTx), is expected to provide native support for
network slicing. For optimization and resource efficiency, the 5G system will select the most appropriate 3GPP
or non-3GPP access technology for a communication service, potentially allowing multiple access technologies
to be used simultaneously for one or more services active on a UE, see clause 6.3 of TS 22.261 [2].
- massive IoT connections
Support for massive Internet of Things (mIoT) brings many new requirements in addition to MBB
enhancements, see clause 4 of TS 22.261 [2]. Communication services with massive IoT connections such as
smart households, smart grid, smart agriculture and smart meter will require the support of a large number and
high density IoT devices to be efficient and cost effective, see TS 23.501 [3]. Operators can use one or more
network slice instances to provide these communication services, which require similar network characteristics,
to different vertical industries.
The next generation 3GPP management system is expected to support the management of 3GPP 5G system and 3GPP
legacy systems.
ETSI

---------------------- Page: 8 ----------------------
3GPP TS 28.530 version 15.3.0 Release 15 8 ETSI TS 128 530 V15.3.0 (2020-01)
3GPP management system directly manages 3GPP managed network components (e.g. 5G RAN, 5G CN). For non-
3GPP domains (e.g. DCN, TN), 3GPP management system needs to coordinate with the corresponding management
systems of the non-3GPP domains.
4.1.2 Types of communication services
Communication services offered by Communication Service Providers (CSPs) to Communication Service Customers
(CSCs) are of various categories, among which:
- Business to consumer (B2C) services, e.g. mobile web browsing, 5G voice, Rich Communication Services, etc.
- Business to business (B2B) services, e.g. Internet access, LAN interconnection, etc.
- Business to household (B2H) services, e.g. Internet access, MBMS, VOIP, VPN, etc.
- Business to business to everything (B2B2X) services: e.g. services offered to other CSPs (e.g. international
roaming, RAN sharing, etc.) offering themselves communication services to their own customers. B2B2X
service type includes B2B2 applied recursively, i.e. B2B2B, B2B2B2B, etc.
NOTE: How to derive different network slice related requirements from different categories of communication
services is not in the scope of the present document.
A communication service offered by CSPs can include a bundle of specific B2C, B2B, B2H or B2B2X type of services.
Taking as an example the B2C type of services, a bundle could include: data (for mobile web browsing), voice (through
5G voice), and messaging (via Rich Communication Services). In this case, each one of the individual B2C may be
fulfilled by different PDU connectivity services provided via corresponding PDU sessions.
4.1.3 Communication services using network slice instances
As an example, a variety of communication services instances provided by multiple NSI(s) are illustrated in the figure
4.1.3.1. Figure 4.1.3.1 is only for illustrative purposes to highlight the combination and relationship of Communication
Services to Network Slices without depicting any UE. An actual network slice deployment offering communication
services to UEs will need to comply with the 5G system architecture defined in TS 23.501 [3] and TS 38.401 [4].

ETSI

---------------------- Page: 9 ----------------------
3GPP TS 28.530 version 15.3.0 Release 15 9 ETSI TS 128 530 V15.3.0 (2020-01)
Communication
Communication Communication Communication
Services
Service Instance 1 Service Instance 2 Service Instance 3
NSI A NSI B NSI C
NSSI C
NSSI B
NSSI A
Core Network
NSSI CN-1 NSSI CN-2 NSSI CN-3
TN supporting
connectivity
Access Network
NSSI AN-1 NSSI AN-2

Figure 4.1.3.1: A variety of communication services instances provided by multiple NSIs
Figure 4.1.3.1 illustrates the relationship between instances of Communication Services, instances of Network Slices,
and instances of Network Slice Subnets:
- NSSI AN-1 and NSSI AN-2 each contain distinct sets of instances of AN NFs. NSSI CN-1, NSSI CN-2 and
NSSI CN-3 each contain distinct sets of instances of CN NFs. The TN supporting connectivity facilitates the
communication between CN and AN NFs. NSSI A combines NSSI AN-1 with NSSI CN-1 and corresponding
TN connectivity. NSSI B combines NSSI AN-2 and NSSI CN-2 and corresponding TN connectivity. NSSI C
combines NSSI AN-2 with NSSI CN-3 and corresponding TN connectivity. The NSSI AN-2 is shared between
NSSI B and NSSI C, while NSSI AN-1 is dedicated to NSSI A.
- NOP offers NSSI A as a Network Slice instance NSI A, in this relationship NSI A represents NSSI A with
associated Service Level Specification (SLS). NOP also offers NSSI B as NSI B and NSSI C as NSI C. The SLS
of NSI A satisfies the service requirements of Communication Service Instance 1 and Communication Service
Instance 2. The SLS of NSI B satisfies the service requirements of Communication Service Instance 2. The SLS
of NSI C satisfies the service requirements of Communication Service Instance 3.
- The Communication Service Instance 1 is supported by NSI A. The Communication Service Instance 2 may be
supported by either NSI A or NSI B. The Communication Service Instance 3 is supported by NSI C.
4.1.4 Communication services requirements
eMBB service type aims at supporting high data rates and high traffic densities as outlined in TS 22.261 [2], Table 7.1-1
"Performance requirements for high data rate and traffic density scenarios". URLLC service type aims at supporting the
requirements in TS 22.261 [2], Table 7.2.2-1 "Performance requirements for low-latency and high-reliability services."
related to high reliability and low latency scenarios. mIoT service type aims at supporting a large number and high
density of IoT devices efficiently and cost effectively, see TS 23.501 [3].
Depending on the service type (eMBB, URLLC, mIoT), different service types may include different network slice
related requirements, for example:
- Area traffic capacity requirement
- Charging requirement
ETSI

---------------------- Page: 10 ----------------------
3GPP TS 28.530 version 15.3.0 Release 15 10 ETSI TS 128 530 V15.3.0 (2020-01)
- Coverage area requirement
- Degree of isolation requirement
- End-to-end latency requirement
- Mobility requirement
- Overall user density requirement
- Priority requirement
- Service availability requirement
- Service reliability requirement
- UE speed requirement
4.1.5 NSI Lifecycle and relationship to service instances
An NSI may support multiple service instances if it satisfies their service level requirements or has been modified to
support these requirements. When a service instance is to be supported, it may trigger an operation phase of the NSI
lifecycle for activation or modification(s) of an existing NSI, or it may trigger a commissioning phase of the NSI
lifecycle for creation of a new NSI. When a service instance no longer needs to be supported by an NSI, it may trigger
an operation phase of the NSI lifecycle for de-activation or modification(s) of an existing NSI, or it may trigger a
decommissioning phase of the NSI lifecycle for termination of an existing NSI.
4.1.6 Network Slice as a Service (NSaaS)
Network Slice as a Service (NSaaS) can be offered by a CSP to its CSC in the form of a service. This service allows
CSC to use the network slice instance as the end user or optionally allows CSC to manage the network slice instance as
manager via management interface exposed by the CSP. In turn, these CSC can play the role of CSP and offer their own
services (e.g. communication services) on top of the network slice instance obtained from the CSP. For example, a
network slice customer can also play the role of NOP and could build their own network containing the network slice
obtained from the CSP as a "building block". In this model, both CSP offering NSaaS and CSC consuming NSaaS have
the knowledge of the existence of network slice instances. Depending on service offering, CSP offering NSaaS may
impose limits on the NSaaS management capabilities exposure to the CSC, and the CSC can manage the network slice
instance according to NSaaS management capabilities exposed and agreed upon limited level of management by the
CSP.
The NSaaS offered by the CSP could be characterized by certain properties (capabilities to satisfy service level
requirements), e.g.
- radio access technology,
- bandwidth,
- end-to-end latency,
- reliability,
- guaranteed / non-guaranteed QoS,
- security level, etc.
Figure 4.1.6.1 illustrates some examples on how network slices can be utilized to deliver communication services,
including Network Slice as a Service. For simplicity this figure omits the details of how NFs are being managed and
does not show their groupings into NSSI:
a) A Network Slice as a Service is provided to CSC-A by CSP-A. Unlike the communication service delivered to
end customers, in NSaaS, the offered service is the actual network slice.
b) CSC-A can use the network slice obtained from CSP-A to support own Communication Services or may add
additional network functions to the obtained NSaaS and offer the resulting combination as a new network slice to
CSP-B. In this case, CSC-A plays the role of NOP-B and builds his own network. The Network Slice obtained
ETSI

---------------------- Page: 11 ----------------------
...