ETSI TS 132 612 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);
Bulk CM Integration Reference Point (IRP):
Information Service (IS)
(3GPP TS 32.612 version 15.1.0 Release 15)

3GPP TS 32.612 version 15.1.0 Release 15 1 ETSI TS 132 612 V15.1.0 (2019-10)

Reference
RTS/TSGS-0532612vf10
Keywords
GSM,LTE,UMTS
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 - 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
3GPP TS 32.612 version 15.1.0 Release 15 2 ETSI TS 132 612 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
3GPP TS 32.612 version 15.1.0 Release 15 3 ETSI TS 132 612 V15.1.0 (2019-10)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 7
Introduction . 7
1 Scope . 8
2 References . 8
3 Definitions and abbreviations . 9
3.1 Definitions . 9
3.2 Abbreviations . 11
4 System Overview . 12
4.1 System Context . 12
4.2 Compliance rules . 13
4.3 Scope of Bulk CM Management Specification . 14
5 Modelling approach . 14
6 Information Object Classes . . 14
6.1 Information entities imported and local label . 14
6.2 Class diagram . 15
6.2.1 Attributes and relations . 15
6.2.2 Inheritance . 15
6.3 Information object classes definitio n . 16
6.3.1 SimpleUploadBulkCMIRP . 16
6.3.1.1 Definition . 16
6.3.1.2 Attributes . 16
6.3.1.3 Notifications . 16
6.3.2 ControlledUploadBulkCMIRP . 16
6.3.2.1 Definition . 16
6.3.2.2 Attributes . 16
6.3.2.3 Notifications . 16
6.3.3 BulkCMIRP . 16
6.3.3.1 Definition . 16
6.3.3.2 Attributes . 16
6.3.3.3 Notifications . 16
6.4 Void . 17
7 Interface Definition . 18
7.1 Class Diagram . 19
7.1.1 Operations and Notifications for Simple Upload . 19
7.1.2 Operations and Notifications for Controlled Upload . 19
7.1.3 Main Operations and Notifications for Controlled Upload & Provisioning . 20
7.1.4 Suboperations for Controlled Upload & Provisioning (of clause 10) . 20
7.2 Generic rules . 20
7.3 Interface BulkCMSession . 21
7.3.1 Operation startSession (M) . 21
7.3.1.1 Definition . 21
7.3.1.2 Input parameters . 21
7.3.1.3 Output parameters . 21
7.3.1.4 Pre-condition . 21
7.3.1.5 Post-condition . 21
7.3.1.6 Exceptions . 21
7.3.1.6.1 operationFailed . 21
7.3.2 Operation endSession (M) . 22
ETSI
3GPP TS 32.612 version 15.1.0 Release 15 4 ETSI TS 132 612 V15.1.0 (2019-10)
7.3.2.1 Definition . 22
7.3.2.2 Input parameters . 22
7.3.2.3 Output parameters . 22
7.3.2.4 Pre-condition . 22
7.3.2.5 Post-condition . 22
7.3.2.6 Exceptions . 22
7.3.2.6.1 operationFailed . 22
7.3.3 Operation abortSessionOperation (M) . 23
7.3.3.1 Definition . 23
7.3.3.2 Input parameters . 23
7.3.3.3 Output parameters . 23
7.3.3.4 Pre-condition . 23
7.3.3.5 Post-condition . 23
7.3.3.6 Exceptions . 23
7.3.3.6.1 operationFailed . 23
7.3.4 Operation getSessionIds (M) . 24
7.3.4.1 Definition . 24
7.3.4.2 Input parameters . 24
7.3.4.3 Output parameters . 24
7.3.4.4 Pre-condition . 24
7.3.4.5 Post-condition . 24
7.3.5 Operation getSessionStatus (M) . 25
7.3.5.1 Definition . 25
7.3.5.2 Input parameters . 25
7.3.5.3 Output parameters . 25
7.3.5.4 Pre-condition . 25
7.3.5.5 Post-condition . 25
7.3.5.6 Exceptions . 26
7.3.5.6.1 operationFailed . 26
7.3.6 Operation getSessionLog (M) . 26
7.3.6.1 Definition . 26
7.3.6.2 Input parameters . 26
7.3.6.3 Output parameters . 26
7.3.6.4 Pre-condition . 26
7.3.6.5 Post-condition . 26
7.3.6.6 Exceptions . 27
7.3.6.6.1 operationFailed . 27
7.4 Interface BulkCMPassive . 28
7.4.1 Operation upload (M) . 28
7.4.1.1 Definition . 28
7.4.1.2 Input parameters . 28
7.4.1.3 Output parameters . 29
7.4.1.4 Pre-condition . 29
7.4.1.5 Post-condition . 29
7.4.1.6 Exceptions . 29
7.4.1.6.1 operationFailed . 29
7.5 Interface BulkCMActive . 30
7.5.1 Operation download (M) . 30
7.5.1.1 Definition . 30
7.5.1.2 Input parameters . 30
7.5.1.3 Output parameters . 30
7.5.1.4 Pre-condition . 30
7.5.1.5 Post-condition . 30
7.5.1.6 Exceptions . 31
7.5.1.6.1 operationFailed . 31
7.5.2 Operation validate (O) . 32
7.5.2.1 Definition . 32
7.5.2.2 Input parameters . 32
7.5.2.3 Output parameters . 32
7.5.2.4 Pre-condition . 32
7.5.2.5 Post-condition . 32
7.5.2.6 Exceptions . 33
ETSI
3GPP TS 32.612 version 15.1.0 Release 15 5 ETSI TS 132 612 V15.1.0 (2019-10)
7.5.2.6.1 operationFailed . 33
7.5.3 Operation preactivate (O) . 34
7.5.3.1 Definition . 34
7.5.3.2 Input parameters . 34
7.5.3.3 Output parameters . 35
7.5.3.3 Pre-condition . 35
7.5.3.5 Post-condition . 35
7.5.3.6 Exceptions . 35
7.5.3.6.1 operationFailed . 35
7.5.4 Operation activate (M) . 36
7.5.4.1 Definition . 36
7.5.4.2 Input parameters . 37
7.5.4.3 Output parameters . 37
7.5.4.4 Pre-condition . 37
7.5.4.5 Post-condition . 37
7.5.4.6 Exceptions . 37
7.5.4.6.1 operationFailed . 37
7.5.5 Operation fallback (M) . 38
7.5.5.1 Definition . 38
7.5.5.2 Input parameters . 38
7.5.5.3 Output parameters . 38
7.5.5.4 Pre-condition . 38
7.5.5.5 Post-condition . 38
7.5.5.6 Exceptions . 39
7.5.5.6.1 operationFailed . 39
7.5.6 Validation and Checking Functions . 40
7.5.6.1 Download Checks . 40
7.5.6.2 Validate Checks . 40
7.5.6.3 Preactivation Checks . 40
7.5.6.4 Activate Checks . 40
7.6 Interface BulkCMIRPNotification_1 . 41
7.6.1 Notification notifySessionStateChanged (M) . 41
7.6.1.1 Definition . 41
7.6.1.2 Input Parameters . 41
7.6.1.3 Triggering events . 42
7.7 Interface BulkCMIRPNotification_2 . 42
7.7.1 Notification notifyGetSessionLogEnded (M) . 42
7.7.1.1 Definition . 42
7.7.1.2 Input parameters . 42
7.7.1.3 Triggering event . 42
8 Void . 44
9 State Machine . 44
9.1 State Machine Overview . 44
9.2 State Machine Description . 45
9.2.1 Upload Phase . 47
9.2.2 Download Phase . 48
9.2.3 Validation Phase . 48
9.2.4 Preactivation Phase . 50
9.2.5 Activation Phase . 51
9.2.6 Fallback Phase . 52
9.3 State Machine Pre and Post Conditions Tables . 53
10 Bulk Configuration Data File . 56
10.1 Bulk Configuration Data Management Actions – Sub-operations . 56
10.1.1 bulkCmCreateMo (Create MO Sub-operation) (M) . 56
10.1.2 bulkCmDeleteMo (Delete MO Sub-operation) (M) . 57
10.1.3 bulkCmChangeMo (Change MO Sub-operation) (M) . 57
10.2 Rules for ordering Management Actions (Sub-operations) in Configuration Data Files . 57
10.2.1 Download files . 57
10.2.2 Upload files . 58
ETSI
3GPP TS 32.612 version 15.1.0 Release 15 6 ETSI TS 132 612 V15.1.0 (2019-10)
Annex A (informative): Scenarios . 59
Annex B (informative): Bulk CM Application and Operation Principles . 65
B.1 Key characteristics . 65
Annex C (informative): Change history . 66
History . 68

ETSI
3GPP TS 32.612 version 15.1.0 Release 15 7 ETSI TS 132 612 V15.1.0 (2019-10)
Foreword
rd
This Technical Specification (TS) 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.611: "Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Requirements".
32.612: "Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Information
Service (IS)".
32.616: "Configuration Management (CM); Bulk 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 Element (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. The CM actions are
initiated either as a 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
3GPP TS 32.612 version 15.1.0 Release 15 8 ETSI TS 132 612 V15.1.0 (2019-10)
1 Scope
The present document (Bulk Configuration Management IRP: Information Service) defines a number of Integration
Reference Point (IRP) through which an 'IRPAgent' (typically an Element Manager or Network Element) can
communicate bulk Configuration Management related information to one or several 'IRPManagers' (typically Network
Managers).
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.622: "Telecommunication management; Configuration Management (CM); Generic
network resources Integration Reference Point (IRP): Network Resource Model (NRM)".
[5] 3GPP TS 32.642: "Telecommunication management; Configuration Management (CM); UTRAN
network resources Integration Reference Point (IRP): Network Resource Model (NRM)".
[6] 3GPP TS 32.652: "Telecommunication management; Configuration Management (CM); GERAN
network resources Integration Reference Point (IRP): Network Resource Model (NRM)".
[7] 3GPP TS 32.300: "Telecommunication management; Configuration Management (CM); Name
convention for Managed Objects".
[8] 3GPP TS 32.600: "Telecommunication management; Configuration Management (CM); Concept
and high-level requirements".
[9] 3GPP TS 32.312: "Telecommunication management; Generic Integration Reference Point (IRP)
management; Information Service (IS)".
[10] 3GPP TS 32.632: "Telecommunication management; Configuration Management (CM); Core
Network Resources Integration Reference Point (IRP): Network Resource Model (NRM)".
[11] 3GPP TS 32.692 "Inventory Management (IM) network resource Integration Reference Point
(IRP): Network Resource Model (NRM)".
[12] Void
[13] 3GPP TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept
and definitions".
[14] 3GPP TS 32.712: "Telecommunication management; Configuration Management (CM); Transport
Network (TN) Network Resource Model (NRM) Integration Reference Point (IRP): Information
Service (IS)".
[15] Void
ETSI
3GPP TS 32.612 version 15.1.0 Release 15 9 ETSI TS 132 612 V15.1.0 (2019-10)
[16] Void
[17] Void
[18] Void
[19] Void
[20] Void
[21] Void
[22] Void
[23] 3GPP TS 28.622: "Telecommunication management; Generic Network Resource Model (NRM)
Integration Reference Point (IRP); Information Service (IS)".
[24] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [24], 3GPP TS 32.101
[1], 3GPP TS 32.102 [2] and 3GPP TS 32.600 [8] 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 [24], 3GPP TS 32.101 [1], 3GPP TS
32.102 [2] and 3GPP TS 32.600 [8].
Association: Association 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). However, all (non-containment) associations are
modelled. by means of reference attributes of the participating MOs.
Element Manager (EM): provides a package of end-user functions for management of a set of closely related types of
Network Elements (NEs).
NOTE 3: These functions can be divided into two main categories:
- Element Management Functions for management of NEs on an individual basis. These are basically the same
functions as supported by the corresponding local terminals.
- Sub-Network Management Functions that are related to a network model for a set of NEs constituting a clearly
defined sub-network, which may include relations between the NEs. This model enables additional functions on
the sub-network level (typically in the areas of network topology presentation, alarm correlation, service impact
analysis and circuit provisioning).
Integration Reference Point (IRP): See 3GPP TS 32.150 [6].
IRP Information Service (IS): See 3GPP TS 32.101 [1].
IRP Network Resource Model (NRM): See 3GPP TS 32.101 [1].
IRP Solution Set (SS): See 3GPP TS 32.101 [1].
ETSI
3GPP TS 32.612 version 15.1.0 Release 15 10 ETSI TS 132 612 V15.1.0 (2019-10)
Managed Element (ME): An instance of the Managed Object Class G3ManagedElement/ManagedElement.
Managed Object (MO): software object that encapsulates the manageable characteristics and behaviour of a particular
network resource.
NOTE 4: 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 (the term "attribute " is taken from
TMN and corresponds to a "property " according to CIM). Furthermore, a MO class can have operations
that represent the behaviour relevant for that class (the term "operation " is taken from TMN and
corresponds to a "method " according to CIM). An MO class may support notifications that provide
information about an event occurrence within a network resource.
Managed Object Class (MOC): a description of all the common characteristics for a number of MOs, such as their
attributes, operations, notifications and behaviour.
Managed Object Instance (MOI): an instance of a MOC, which is the same as a MO as described above.
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 5: a MIB consist 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 (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 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
Management Information Model (MIM): Also referred to as NRM – see the definition below. There is a slight
difference between the meaning of MIM and NRM – the term MIM is generic and can be used to denote any type of
management model, while NRM denotes the model of the actual managed telecommunications network resources .
Name space: A name space is a collection of names.
NOTE 6: The IRP name convention [7] 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 shall be 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 3GPP TS 28.622 [23].
Network Resource Model (NRM): See definition in 3GPP TS 28.622 [23].
Operator: is either a human being controlling and managing the network; or a company running a network (the 3G
network operator).
...