ETSI TS 132 662 V15.1.0 (2019-10)

Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Configuration Management (CM); Kernel CM Information Service (IS) (3GPP TS 32.662 version 15.1.0 Release 15)

RTS/TSGS-0532662vf10

General Information

• Status: Published
• Publication Date: 08-Oct-2019
• Technical Committee: 3GPP SA 5 - Telecom Management
• Current Stage: 12 - Completion
• Completion Date: 09-Oct-2019

Standards Content (Sample)

ETSI TS 132 662 V15.1.0 (2019-10)






TECHNICAL SPECIFICATION
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
LTE;
Telecommunication management;
Configuration Management (CM);
Kernel CM Information Service (IS)
(3GPP TS 32.662 version 15.1.0 Release 15)

---------------------- Page: 1 ----------------------
3GPP TS 32.662 version 15.1.0 Release 15 1 ETSI TS 132 662 V15.1.0 (2019-10)



Reference
RTS/TSGS-0532662vf10
Keywords
GSM,LTE,UMTS
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 2019.
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 32.662 version 15.1.0 Release 15 2 ETSI TS 132 662 V15.1.0 (2019-10)
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 32.662 version 15.1.0 Release 15 3 ETSI TS 132 662 V15.1.0 (2019-10)
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 . 7
3.1 Definitions . 7
3.2 Abbreviations . 8
4 System overview . 8
4.1 System Context . 8
4.2 Compliance rules . 9
5 Modelling approach . 9
6 Information Object Classes (IOCs) . 10
6.1 Imported Information entities and local labels . 10
6.2 Class diagram . 10
6.2.1 Attributes and relationships . 10
6.2.2 Inheritance . 10
6.3 Information Object Class Definitions . 11
6.3.1 KernelCmIRP . 11
6.3.1.1 Definition . 11
6.3.2 ManagedEntity . 11
6.3.2.1 Definition . 11
6.4 Information relationship definitions . 11
6.4.1 containment (M) . 11
6.4.1.1 Definition . 11
6.4.1.2 Role . 11
6.4.1.3 Constraint . 11
7 Interface Definition . 12
7.1 Class diagram . 12
7.2 Generic rules . 12
7.3 Interface KernelCmIRPOperations. 13
7.3.1 Operation getNRMIRPVersion (M) . 13
7.3.1.1 Definition . 13
7.3.1.2 Input parameters . 13
7.3.1.3 Output parameters . 13
7.3.1.4 Pre-condition . 13
7.3.1.5 Post-condition . 13
7.3.1.6 Exceptions . 14
7.4 Interface KernelCmIRPNotifications_1 . 15
7.4.1 notifyObjectCreation (O) . 15
7.4.1.1 Definition . 15
7.4.1.2 Input Parameters . 15
7.4.1.3 Triggering Event . 16
7.4.1.3.1 From-state . 16
7.4.1.3.2 To-state . 16
7.5 Interface KernelCmIRPNotifications_2 . 16
7.5.1 notifyObjectDeletion (O) . 16
7.5.1.1 Definition . 16
7.5.1.2 Input Parameters . 16
ETSI

---------------------- Page: 4 ----------------------
3GPP TS 32.662 version 15.1.0 Release 15 4 ETSI TS 132 662 V15.1.0 (2019-10)
7.5.1.3 Triggering Event . 16
7.5.1.3.1 From-state . 16
7.5.1.3.2 To-state . 17
7.6 Interface KernelCmIRPNotifications_3 . 17
7.6.1 notifyAttributeValueChange (O) . 17
7.6.6.1 Definition . 17
7.6.6.2 Input Parameters . 17
7.6.6.3 Triggering Event . 17
7.6.6.3.1 From-state . 17
7.6.6.3.2 To-state . 18
7.7 Interface KernelCmIRPNotifications_4 . 19
7.7.1 notifyCMSynchronizationRecommended (O) . 19
7.7.1.1 Definition . 19
7.7.1.2 Input Parameters . 20
7.7.1.3 Triggering Event . 20
7.7.1.3.1 From-state . 20
7.7.1.3.2 To-state . 20
7.8 Interface KernelCmIRPNotifications_5 . 21
7.8.1 notifyStateChange (O) . 21
7.8.1.1 Definition . 21
7.8.1.2 Input parameters . 21
7.8.1.3 Triggering Event . 21
7.8.1.3.1 From-state . 21
7.8.1.3.2 To-state . 21
Annex A (normative): Notification/Event Types . 22
Annex B (informative): Change history . 23
History . 24

ETSI

---------------------- Page: 5 ----------------------
3GPP TS 32.662 version 15.1.0 Release 15 5 ETSI TS 132 662 V15.1.0 (2019-10)
Foreword
rd
This Technical Specification has been produced by the 3 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
rd
The present document is part of a TS-family covering the 3 Generation Partnership Project; Technical Specification
Group Services and System Aspects; Telecommunication management; as identified below:
32.661 Configuration Management (CM); Kernel CM Requirements
32.662 Configuration Management (CM); Kernel CM Information Service (IS)
32.666: Configuration Management (CM); Kernel CM Integration Reference Point (IRP); Solution Set (SS)
definitions
Configuration Management (CM), in general, provides the operator with the ability to assure correct and effective
operation of the 3G network as it evolves. CM actions have the objective to control and monitor the actual configuration
on the Network Elements (NEs) and network resources , and they may be initiated by the operator or by functions in the
Operations Systems (OSs) or NEs.
CM actions may be requested as part of an implementation programme (e.g. additions and deletions), as part of an
optimisation programme (e.g. modifications), and to maintain the overall Quality of Service (QoS). The CM actions are
initiated either as single actions on single NEs of the 3G network, or as part of a complex procedure involving actions
on many resources/objects in one or several NEs.
ETSI

---------------------- Page: 6 ----------------------
3GPP TS 32.662 version 15.1.0 Release 15 6 ETSI TS 132 662 V15.1.0 (2019-10)
1 Scope
The present document defines Integration Reference Point (IRP) through which an 'IRPAgent' (typically an Element
Manager or Network Element) can communicate Configuration Management related information to one or several
'IRPManagers' (typically Network Managers).
The function of this Kernel CM IRP Information Service is to define an interface that provides the essential CM
services. While it is not expected that the Kernel CM IRP alone will provide adequate CM capability, The Kernel CM
IRP is expected to provide the common supporting capability required for other IRPs such as the Basic CM IRP or the
Bulk CM IRP, each of which require the Kernel CM IRP.
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 TS 32.101: "Telecommunication management; Principles and high level requirements".
[2] 3GPP TS 32.102: "Telecommunication management; Architecture".
[3] 3GPP TS 32.302: "Telecommunication management; Configuration Management (CM);
Notification Integration Reference Point (IRP): Information Service (IS)".
[4] 3GPP TS 32.312: "Telecommunication management; Generic Integration Reference Point (IRP)
management; Information Service (IS)".
[5] Void.
[6] 3GPP TS 32.672: "Telecommunication management; Configuration Management (CM); State
Management Integration Reference Point (IRP): Information Service (IS)".
[7] ITU-T Recommendation X.710 (1997): "Information technology - Open Systems Interconnection -
Common Management Information Service".
[8] ITU-T Recommendation X.721 (1992): "Information technology - Open Systems Interconnection -
Structure of Management Information: Definition of management information".
[9] ITU-T Recommendation X.730 (1992): "Information technology - Open Systems Interconnection -
Systems Management: Object Management Function".
[10] ITU-T Recommendation X.733 (1992): "Information technology - Open Systems
Interconnection - Systems Management: Alarm reporting function".
[11] - [12] Void.
[13] 3GPP TS 32.300: "Telecommunication management; Configuration Management (CM); Name
convention for Managed Objects".
[14] 3GPP TS 32.600: "Telecommunication management; Configuration Management (CM); Concept
and high-level requirements".
[15] ITU-T Recommendation X.720: "Information technology - Open Systems Interconnection -
Structure of management information: Management information model".
ETSI

---------------------- Page: 7 ----------------------
3GPP TS 32.662 version 15.1.0 Release 15 7 ETSI TS 132 662 V15.1.0 (2019-10)
[16] Void.
[17] Void.
[18] Void.
[19] 3GPP TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept
and definitions".
[20] 3GPP TS 32.311: "Telecommunication management; Generic Integration Reference Point (IRP)
management: Requirements.
[21] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[22] 3GPP TS 28.622: "Telecommunication management; Generic Network Resource Model (NRM)
Integration Reference Point (IRP); Information Service (IS)".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [21], 3GPP TS 32.101
[1], 3GPP TS 32.102 [2] and 3GPP TS 32.600 [14] 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 [21], 3GPP TS 32.101 [1], 3GPP TS
32.102 [2] and 3GPP 32.600 [14].
association: In general it is used to model relationships between Managed Objects.
NOTE 1: Associations can be implemented in several ways, such as:
1) name bindings,
2) reference attributes, and
3) association objects.
NOTE 2: This IRP stipulates that containment associations shall be expressed through name bindings, but it does
not stipulate the implementation for other types of associations as a general rule. These are specified as
separate entities in the object models (UML diagrams). Currently however, all (non-containment)
associations are modelled by means of reference attributes of the participating MOs.

Managed Object (MO): software object that encapsulates the manageable characteristics and behaviour of a particular
network resource.
NOTE 3: The MO is instance of a MO class defined in a MIM/NRM. An MO class has attributes that provide
information used to characterize the objects that belong to the class. Furthermore, an MO class can have
operations that represent the behaviour relevant for that class. An MO class may support notifications that
provide information about an event occurrence within a network resource.
Management Information Base (MIB): A MIB is an instance of an NRM and has some values on the defined
attributes and associations specific for that instance.
NOTE 4: an MIB consists of:
1) a Name space (describing the MO containment hierarchy in the MIB through Distinguished Names),
2) a number of Managed Objects with their attributes, and
3) a number of Associations between these MOs. Also note that TMN (ITU-T Recommendation X.710 [7])
defines a concept of a Management Information Tree (also known as a Naming Tree) that corresponds to the
name space (containment hierarchy) portion of this MIB definition. Figure 3.1 depicts the relationships
ETSI

---------------------- Page: 8 ----------------------
3GPP TS 32.662 version 15.1.0 Release 15 8 ETSI TS 132 662 V15.1.0 (2019-10)
between a Name space and a number of participating MOs (the shown association is of a non-containment
type).
Namespace (containment hierarhy)
MIB
MO
Association

Figure 3.1: Relationships between a Name space and a number of participating MOs

Name space: A name space is a collection of names.
NOTE 5: The IRP name convention (see TS 32.300 [13]) restricts the name space to a hierarchical containment
structure, including its simplest form - the one-level, flat name space.
All Managed Objects in a MIB are included in the corresponding name space and the MIB/name space
shall only support a strict hierarchical containment structure (with one root object). A Managed Object
that contains another is said to be the superior (parent); the contained Managed Object is referred to as the
subordinate (child). The parent of all MOs in a single name space is called a Local Root. The ultimate
parent of all MOs of all managed systems is called the Global Root.
Network resource: See definition in TS 28.622 [22].
Network Resource Model (NRM): See definition in TS 28.622 [22].


3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [21] 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 [21].

DN Distinguished Name (see TS 32.300 [13])

MO Managed Object
MOC Managed Object Class
MOI Managed Object Instance
PM Performance Management
RDN Relative Distinguished Name (see TS 32.300 [13])
SS Solution Set
VSE Vendor Specific Extensions
4 System overview
4.1 System Context
The general definition of the System Context for the present IRP is found in 3GPP TS 32.150 [19] subclause 4.7.
In addition, the set of related IRP(s) relevant to the present IRP is shown in the two diagrams below.
ETSI

---------------------- Page: 9 ----------------------
3GPP TS 32.662 version 15.1.0 Release 15 9 ETSI TS 132 662 V15.1.0 (2019-10)

IRPManager IRPAgent
NEs
NM EM
Itf-N
Notification IRP
Kernel CM IRP

Figure 4.1: System Context A

IRPManager IRPAgent
NM NE
Notification IRP
Itf-N
Kernel CM IRP

Figure 4.2: System Context B
4.2 Compliance rules
For general definitions of compliance rules related to qualifiers (Mandatory/Optional/Conditional) for operations,
notifications and parameters (of operations and notifications) please refer to TS 32.150 [19].
An IRPAgent that incorporates vendor-specific extensions shall support normal communication with a 3GPP
SA5-compliant IRPManager with respect to all Mandatory and Optional managed object classes, attributes,
associations, operations, parameters and notifications without requiring the IRPManager to have any knowledge of the
extensions.
Given that
- rules for vendor-specific extensions remain to be fully specified, and
- many scenarios under which IRPManager and IRPAgent interwork may exist,
it is recognised that the IRPManager, even though it is not required to have knowledge of vendor-specific
extensions, may be required to be implemented with an awareness that extensions can exist and behave accordingly.
5 Modelling approach
See 3GPP TS 32.150 [19].
ETSI

---------------------- Page: 10 ----------------------
3GPP TS 32.662 version 15.1.0 Release 15 10 ETSI TS 132 662 V15.1.0 (2019-10)
6 Information Object Classes (IOCs)
6.1 Imported Information entities and local labels
Label reference Local label
32.312 [4], SupportIOC, ManagedGenericIRP ManagedGenericIRP
6.2 Class diagram
This sub-clause introduces the set of Support Information Object Classes (SupportIOCs) that encapsulate information
within the IRPAgent. The intent is to identify the information required for the KernelCMIRP Agent implementation
of its operations and notification emission. This sub-clause provides the overview of all SupportI
...