|
TECHNICAL SPECIFICATION
LTE;
5G;
Management and orchestration;
Management services for communication service assurance;
Stage 2 and stage 3
(3GPP TS 28.536 version 17.2.0 Release 17)
---------------------- Page: 1 ----------------------
3GPP TS 28.536 version 17.2.0 Release 17 1 ETSI TS 128 536 V17.2.0 (2022-05)
Reference
RTS/TSGS-0528536vh20
Keywords
5G,LTE
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
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:
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
If you find errors in the present document, please send your comment to one of the following services:
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
---------------------- Page: 2 ----------------------
3GPP TS 28.536 version 17.2.0 Release 17 2 ETSI TS 128 536 V17.2.0 (2022-05)
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.
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 .
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.536 version 17.2.0 Release 17 3 ETSI TS 128 536 V17.2.0 (2022-05)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 5
Introduction . 6
1 Scope . 7
2 References . 7
3 Definitions of terms, symbols and abbreviations . 8
3.1 Terms . 8
3.2 Symbols . 8
3.3 Abbreviations . 8
4 Communication service assurance service . 8
4.1 Stage 2 . 8
4.1.1 Void . 8
4.1.2 Model . 8
4.1.2.1 Imported and associated information entities . 8
4.1.2.1.1 Imported information entities and local labels . 8
4.1.2.1.2 Associated information entities and local labels . 9
4.1.2.2 Class diagram . 9
4.1.2.2.1 Relationships . 9
4.1.2.2.2 Inheritance . 10
4.1.2.3 Class definitions . 10
4.1.2.3.1 AssuranceClosedControlLoop . 10
4.1.2.3.2 AssuranceGoal . 11
4.1.2.3.3 Void . 12
4.1.2.3.4 Void . 12
4.1.2.3.5 AssuranceTarget <> . 12
4.1.2.3.6 AssuranceScope <> . 12
4.1.2.4 Attribute definitions . 13
4.1.2.4.1 Attribute properties . 13
4.1.2.4.2 Constraints . 16
4.1.2.4.3 Notifications . 16
4.1.2.5 Common notifications . 17
4.1.2.5.1 Alarm notifications . 17
4.1.2.5.2 Configuration notifications . 17
4.1.3 Procedures. 18
4.1.3.1 SLS Assurance Procedure . 18
4.2 Stage 3 . 19
4.2.1 Solution Set (SS) for JSON/YAML . 19
Annex A (informative): Control loop deployed in different layers . 20
A.1 Introduction . 20
A.2 Control loop in communication service layer . 20
A.3 Control loop in network slice layer . 20
A.4 Control loop in network slice subnet layer . 21
A.5 Control loop in NF layer . 21
Annex B (normative): OpenAPI definition of the COSLA NRM . 22
B.1 General . 22
B.2 Solution Set (SS) definitions . 22
B.2.1 OpenAPI document "coslaNrm.yml" . 22
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 28.536 version 17.2.0 Release 17 4 ETSI TS 128 536 V17.2.0 (2022-05)
Annex C (normative): AssuranceClosedControlLoop state management . 25
Annex D (informative): Appendix with UML code for model diagrams . 27
D.1 UML code for Figure 4.1.2.2.1.1 . 27
D.2 UML code for Figure 4.1.2.2.2.1 . 27
Annex E (informative): Change history . 28
History . 29
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 28.536 version 17.2.0 Release 17 5 ETSI TS 128 536 V17.2.0 (2022-05)
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.
In the present document, modal verbs have the following meanings:
shall indicates a mandatory requirement to do something
shall not indicates an interdiction (prohibition) to do something
The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in
Technical Reports.
The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided
insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced,
non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a
referenced document.
should indicates a recommendation to do something
should not indicates a recommendation not to do something
may indicates permission to do something
need not indicates permission not to do something
The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions
"might not" or "shall not" are used instead, depending upon the meaning intended.
can indicates that something is possible
cannot indicates that something is impossible
The constructions "can" and "cannot" are not substitutes for "may" and "need not".
will indicates that something is certain or expected to happen as a result of action taken by an agency
the behaviour of which is outside the scope of the present document
will not indicates that something is certain or expected not to happen as a result of action taken by an
agency the behaviour of which is outside the scope of the present document
might indicates a likelihood that something will happen as a result of action taken by some agency the
behaviour of which is outside the scope of the present document
ETSI
---------------------- Page: 6 ----------------------
3GPP TS 28.536 version 17.2.0 Release 17 6 ETSI TS 128 536 V17.2.0 (2022-05)
might not indicates a likelihood that something will not happen as a result of action taken by some agency
the behaviour of which is outside the scope of the present document
In addition:
is (or any other verb in the indicative mood) indicates a statement of fact
is not (or any other negative verb in the indicative mood) indicates a statement of fact
The constructions "is" and "is not" do not indicate requirements.
Introduction
The present document describes closed control loop assurance solution enabling a service provider or an operator to
continuously deliver the requested level of communication service quality to the customer and is part of a TS-family
covering the 3rd Generation Partnership Project Technical Specification Group Services and System Aspects
Management and orchestration of networks, as identified below:
TS 28.535: Management Services for Communication Service Assurance; Requirements
TS 28.536: Management Services for Communication Service Assurance; Stage 2 and stage 3
The solution described builds upon the management services specifications as identified below:
TS 28.530: Management and orchestration; Concepts, use cases and requirements
TS 28.533: Management and orchestration; Architecture framework
TS 28.532: Management and orchestration; Generic management services.
TS 28.540: Management and orchestration; 5G Network Resource Model (NRM); Stage 1
TS 28.541: Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3
TS 28.531: Management and orchestration; Provisioning
TS 28.545: Management and orchestration; Fault Supervision (FS)
TS 28.550: Management and orchestration; Performance assurance
TS 28.552: Management and orchestration; 5G performance measurements
TS 28.554: Management and orchestration; 5G End to end Key Performance Indicators (KPI)
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 28.536 version 17.2.0 Release 17 7 ETSI TS 128 536 V17.2.0 (2022-05)
1 Scope
The present document describes the management services for communication service assurance and specifies stage 2
and stage 3 for closed control loop communication service assurance solution that adjusts and optimizes the services
provided by NG-RAN and 5GC.
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] Void
[3] 3GPP TS 28.550: "Management and orchestration; Performance assurance".
[4] Void
[5] 3GPP TS 28.622: "Telecommunication management; Generic Network Resource Model (NRM)
Integration Reference Point (IRP); Information Service (IS)".
[6] 3GPP TS 28.541: "Management and orchestration; 5G Network Resource Model (NRM); Stage 2
and stage 3".
[7] 3GPP TS 28.532: "Management and orchestration; Generic management services".
[8] 3GPP TS 32.302: "Telecommunication management; Configuration Management (CM);
Notification Integration Reference Point (IRP); Information Service (IS)".
[9] 3GPP TS 28.531: "Management and orchestration; Provisioning".
[10] 3GPP TS 32.160: "Management and orchestration; Management service template".
[11] 3GPP TS 29.520: "5G System; Network Data Analytics Services; Stage 3".
[12] 3GPP TS 28.552: "Management and orchestration; 5G performance measurements".
[13] 3GPP TS 28.554: "Management and orchestration; 5G end to end Key Performance Indicators
(KPI)".
[14] 3GPP TS 28.625: "State Management Data Definition Integration Reference Point (IRP);
Information Service (IS)".
[15] ITU-T Recommendation X.731: "Information technology - Open Systems Interconnection -
Systems Management: State management function".
[16] Void
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 28.536 version 17.2.0 Release 17 8 ETSI TS 128 536 V17.2.0 (2022-05)
3 Definitions of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in 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 TR 21.905 [1].
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in 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
TR 21.905 [1].
COSLA Closed control loop SLS Assurance
CSC Communication Service Customer
CSP Communication Service Provider
IOC Information Object Class
IS Information Service
JSON JavaScript Object Notation
YAML YAML Ain't Markup Language
MDAS Management Data Analytics Service
MDT Minimization of Drive Tests
MnS Management Service
NF Network Function
NRM Network Resource Model
NSSI NetworkSlice Subnet Instance
NWDAF NetWork Data Analytics Function
QoE Quality of Experience
SLA Service Level agreement
SLS Service Level Specification
4 Communication service assurance service
4.1 Stage 2
4.1.1 Void
4.1.2 Model
4.1.2.1 Imported and associated information entities
4.1.2.1.1 Imported information entities and local labels
ETSI
---------------------- Page: 9 ----------------------
3GPP TS 28.536 version 17.2.0 Release 17 9 ETSI TS 128 536 V17.2.0 (2022-05)
Label reference Local label
Top
TS 28.622 [5], IOC, Top
4.1.2.1.2 Associated information entities and local labels
Label reference Local label
SubNetwork
TS 28.622 [5], IOC, SubNetwork
NetworkSlice
TS 28.541 [6], IOC, NetWorkSlice
NetworkSliceSubnet
TS 28.541 [6], IOC, NetWorkSliceSubnet
ManagedElement
TS 28.622 [5], IOC, ManagedElement
serviceProfileId
TS 28.541 [6], attribute, serviceProfileId
sliceProfileId
TS 28.541 [6], attribute, sliceProfileId
taiList
TS 28.541 [6], attribute, taiList
4.1.2.2 Class diagram
4.1.2.2.1 Relationships
This clause depicts the set of classes that encapsulates the information relevant for this MnS. This clause provides an
overview of the relationships between relevant classes in UML.
Figure 4.1.2.2.1.1: Assurance management NRM fragment
ETSI
---------------------- Page: 10 ----------------------
3GPP TS 28.536 version 17.2.0 Release 17 10 ETSI TS 128 536 V17.2.0 (2022-05)
4.1.2.2.2 Inheritance
Figure 4.1.2.2.2.1: Assurance management inheritance relationships
4.1.2.3 Class definitions
4.1.2.3.1 AssuranceClosedControlLoop
4.1.2.3.1.1 Definition
This class represents the information for controlling and monitoring an assurance closed control loop associated with a
NetworkSlice or NetworkSliceSubnet. It can be name-contained by SubNetwork or ManagedElement.
To express the assurance closed control loop goals, the MnS consumer needs to request the MnS producer to create an
AssuranceClosedControlLoop on the MnS producer. The MnS producer may trigger to create the
AssuranceClosedControlLoop as well, for example, when an instance of NetworkSlice or
NetworkSliceSubnet is created, MnS producer may create an instance of
AssuranceClosedControlLoop associated to the instance of NetworkSlice or NetworkSliceSubnet
to assure the target described in ServiceProfile or SliceProfile. For the deletion of the assurance closed
control loop, the MnS consumer needs to request the MnS producer to delete the AssuranceClosedControlLoop
to free up resources on the MnS producer. MnS producer also can trigger to delete AssuranceClosedControlLoop
to free up resources by itself.
For temporary deactivation of the assurance closed control loop, the MnS consumer can modify the value of the
administrative state attribute to “LOCKED”. The MnS producer may disable the assurance closed control loop, for
example in conflict situations, by setting the operational state attribute to “disabled”. When a closed control loop is
enabled by the MnS producer, the operational state is set again to “enabled”. For the activation of an assurance closed
control loop, the MnS consumer can modify the value of the administrative state attribute to “UNLOCKED”.
An AssuranceClosedControlLoop can name-contain multiple instances of AssuranceGoal which represents
the assurance goal and corresponding observed or predicted goal fulfilment information (see clause 4.1.2.3.2). The
AssuranceGoal may optionally include an assurance scope in terms of location (see clause 4.1.2.3.2).
The attribute “controlLoopLifeCyclePhase” is used to keep track of the lifecycle of an
AssuranceClosedControlLoop
4.1.2.3.1.2 Attributes
The AssuranceClosedControlLoop IOC includes attributes inherited from Top IOC (defined TS 28.622[5]) and
the following attributes:
Attribute name S isReadable isWritable isInvariant isNotifyable
operationalState
M T F F T
administrativeState
M T T F T
controlLoopLifeCyclePhase
M T T F T
4.1.2.3.1.3 Constraints
No constraints have been defined for this document.
ETSI
---------------------- Page: 11 ----------------------
3GPP TS 28.536 version 17.2.0 Release 17 11 ETSI TS 128 536 V17.2.0 (2022-05)
4.1.2.3.1.4 Notifications
The common notifications defined in clause 4.1.2.5 are valid for this IOC, without exceptions or additions.
4.1.2.3.2 AssuranceGoal
4.1.2.3.2.1 Definition
This IOC represents assurance goal and corresponding observed or predicted goal fulfilment information.
To express a new assurance goal for the assurance closed control loop, the MnS consumer needs to request the MnS
producer to create an instance of AssuranceGoal. MnS producer can also trigger the creation of an instance of
AssuranceGoal. For example, when a new instance NetworkSLice or NetworkSliceSubnet is created on
the MnS producer and the corresponding SLS needs to be assured, a new instance of AssuranceGoal needs to be
created and associated to the new instance NetworkSLice or NetworkSliceSubnet by configuring the attribute
“networkSliceRef” or “networkSliceSubnetRef” and corresponding attribute “serviceProfileId”
and “sliceProfileId“.
The attribute “assuranceTargetList” defines a list of assurance targets (the subset of attributes (typically
characteristics attributes) from an SLS, i.e. a ServiceProfile or a SliceProfile, that are subject to assurance
requirements.) that should be assured by the AssuranceClosedControlLoop. The attribute
“assuranceTargetList” is configured by MnS producer based on the specified ServiceProfile or
SliceProfile.
To obtain the observed predicted status of the the goal fulfilment information, the MnS consumer can query the attribute
“AssuranceGoalStatusObserved” and “AssuranceGoalStatusPredicted”from MnS producer. The
attribute “AssuranceGoalStatusObserved” and “AssuranceGoalStatusPredicted” is configured
by MnS producer at the end of an observation period. The observation period is assigned by MnS consumer through
requsting the MnS producer to set attribute “observationTime”. The status of the goal fuilfilment is considered
FULFILLED if all the constituent target are FULFILLED.
NOTE: Multiple instances of AssuranceGoal can be created for a single instance of NetworkSlice or
NetworkSliceSubnet.
4.1.2.3.2.2 Attributes
The AssuranceGoal IOC includes attributes inherited from Top IOC (defined TS 28.622[5]) and the following
attributes:
Attribute name S isReadable isWritab
...