|
TECHNICAL SPECIFICATION
LTE;
5G;
Management and orchestration;
Management service template
(3GPP TS 32.160 version 16.6.0 Release 16)
---------------------- Page: 1 ----------------------
3GPP TS 32.160 version 16.6.0 Release 16 1 ETSI TS 132 160 V16.6.0 (2023-01)
Reference
RTS/TSGS-0532160vg60
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 2023.
All rights reserved.
ETSI
---------------------- Page: 2 ----------------------
3GPP TS 32.160 version 16.6.0 Release 16 2 ETSI TS 132 160 V16.6.0 (2023-01)
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 32.160 version 16.6.0 Release 16 3 ETSI TS 132 160 V16.6.0 (2023-01)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 6
1 Scope . 8
2 References . 8
3 Definitions of terms, symbols and abbreviations . 9
3.1 Terms . 9
3.2 Symbols . 9
3.3 Abbreviations . 9
4 Management service template (stage 1) . 9
4.1 General . 9
4.2 Template for high-level requirement specifications . 9
4.3 Template for Management service specific requirement specifications . 10
5 Management service template (stage 2) . 11
5.1 General . 11
5.1.1 General . 11
5.1.2 Management service components . 11
5.2 Template for NRM . 11
5.3 Template for Management service operations and notifications . 17
6 NRM Stage 3 definition rules . 22
6.1 Mappings from stage 2 artefacts to stage 3 JSON schema . 22
6.1.1 Usage of JSON schema . 22
6.1.2 Concrete NRM classes . 22
6.1.3 Abstract classes . 23
6.1.4 Name containment . 23
6.1.5 Recursive name containment . 25
6.1.6 Inheritance . 25
6.1.7 NRM class naming attribute "id" . 26
6.1.8 NRM class attributes . 26
6.1.9 Vendor specific extensions . 26
6.1.10 Attribute support qualifier . 27
6.1.11 Attribute properties . 27
6.1.11.1 Introduction . 27
6.1.11.2 Attribute property "multiplicity" . 27
6.1.11.3 Attribute property "isUnique" . 27
6.1.11.4 Attribute property "isOrdered" . 27
6.1.11.5 Attribute property "defaultValue" . 28
6.1.11.6 Attribute property "isNullable" . 28
6.1.11.7 Attribute property "isInvariant". 28
6.1.11.8 Attribute property "isReadable" and "isWritable" . 28
6.1.11.9 Attribute property "isNotifyable" . 28
6.1.11.10 Attribute property "allowedValues" . 28
6.2 Stage 3 YANG style and example . 29
6.2.1 General Modeling Rules . 29
6.2.1.1 Modeling Resources . 29
6.2.1.2 Unique YANG Module names . 29
6.2.1.3 Unique YANG Namespace . 29
6.2.1.4 Unique YANG Module Prefixes . 29
6.2.1.5 Use YANG Version 1.1 . 29
6.2.1.6 YANG Constructs Not to be Used – Not needed . 29
6.2.1.7 Reuse Standards from Other Standard Organizations . 30
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 32.160 version 16.6.0 Release 16 4 ETSI TS 132 160 V16.6.0 (2023-01)
6.2.1.8 Vendor Specific Model Changes . 30
6.2.1.9 Model Correctness, checking . 30
6.2.1.10 YANG modules in technical specifications . 30
6.2.1.11 Module header statements . 30
6.2.1.12 Provide description and reference statements . 31
6.2.1.13 YANG module revisions . 31
6.2.1.14 Don’t use YANG statements with their default meaning . 31
6.2.1.15 Formatting YANG modules/submodules . 31
6.2.2 InformationObjectClass – abstract . 32
6.2.2.1 Introduction . 32
6.2.2.2 YANG mapping . 32
6.2.3 Naming attribute . 32
6.2.3.1 Introduction . 32
6.2.3.2 Yang mapping . 32
6.2.4 InformationObjectClass – concrete . 32
6.2.4.0 Introduction . 32
6.2.4.1 YANG mapping . 32
6.2.5 Generalization relationship - inheritance from another class . 33
6.2.5.1 Introduction . 33
6.2.5.2 YANG mapping . 33
6.2.6 Name containment . 33
6.2.6.1 Introduction . 33
6.2.6.2 YANG mapping . 34
6.2.7 Recursive containment - reference based solution . 34
6.2.8 Multi-root management tree . 36
6.2.9 Alternative containment . 36
6.2.10 Attribute – simple, single value . 36
6.2.10.1 Introduction . 36
6.2.10.2 YANG Mapping . 36
6.2.11 Attribute – simple, multivalue . 36
6.2.11.1 Introduction . 36
6.2.11.2 YANG mapping . 37
6.2.12 Attribute, structured . 37
6.2.12.0 Introduction . 37
6.2.12.1 YANG Mapping . 37
6.2.13 defaultValue . 38
6.2.13.1 Introduction . 38
6.2.13.2 YANG mapping . 38
6.2.14 multiplicity and cardinality . 38
6.2.14.0 Introduction . 38
6.2.14.1 YANG mapping . 38
6.2.15 isNullable . 39
6.2.15.0 Introduction . 39
6.2.15.1 YANG mapping . 39
6.2.16 dataType . 39
6.2.16.0 Introduction . 39
6.2.16.1 YANG mapping . 39
6.2.17 enumeration . 39
6.2.17.0 Introduction . 39
6.2.17.1 YANG mapping . 39
6.2.18 choice . 39
6.2.18.0 Introduction . 39
6.2.18.1 YANG mapping . 40
6.2.19 isInvariant on attribute . 40
6.2.19.1 YANG mapping . 40
6.2.20 isReadable/isWritable . 40
6.2.20.1 YANG mapping . 40
6.2.21 isOrdered . 40
6.2.21.1 YANG mapping . 40
6.2.22 isUnique . 40
6.2.22.1 YANG mapping . 40
6.2.23 allowedValues . 41
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 32.160 version 16.6.0 Release 16 5 ETSI TS 132 160 V16.6.0 (2023-01)
6.2.23.1 YANG mapping . 41
6.2.24 Xor constraint . 41
6.2.24.1 YANG mapping . 41
6.2.25 ProxyClass . 41
6.2.25.1 YANG mapping . 41
6.2.26 SupportQualifier . 41
6.2.26.1 Introduction . 41
6.2.26.2 YANG mapping . 41
6.2.27 isNotifyable. 42
6.2.27.1 Introduction . 42
6.2.27.2 YANG mapping . 42
Annex A (informative): Change history . 43
History . 44
ETSI
---------------------- Page: 6 ----------------------
3GPP TS 32.160 version 16.6.0 Release 16 6 ETSI TS 132 160 V16.6.0 (2023-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.
In the present document, certain 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" shall not to be used as 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: 7 ----------------------
3GPP TS 32.160 version 16.6.0 Release 16 7 ETSI TS 132 160 V16.6.0 (20
...