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

Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP); Solution Set (SS) definitions (3GPP TS 32.616 version 15.1.0 Release 15)

RTS/TSGS-0532616vf10

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)

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);
Solution Set (SS) definitions
(3GPP TS 32.616 version 15.1.0 Release 15)

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

Reference
RTS/TSGS-0532616vf10
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
3GPP TS 32.616 version 15.1.0 Release 15 2 ETSI TS 132 616 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.616 version 15.1.0 Release 15 3 ETSI TS 132 616 V15.1.0 (2019-10)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 6
Introduction . 6
1 Scope . 7
2 References . 7
3 Definitions and abbreviations . 10
3.1 Definitions . 10
3.2 Abbreviations . 11
4 Solution Set (SS) definitions . 11
Annex A (normative): CORBA Solution Set . 12
A.1 Architectural features . 12
A.1.1 Syntax for Distinguished Names . 12
A.1.2 BulkCMIRPNotifications Interface . 12
A.1.2.1 Method push (M) . 12
A.2 Mapping . 13
A.2.1 General mappings . 13
A.2.2 Operation and Notification mapping . 13
A.2.3 Operation parameter mapping . 15
A.2.4 Notification parameter mapping . 19
A.2.5 Two modes of operations . 23
A.2.6 Mapping from IS State Names to SS equivalents . 24
A.2.7 Package Mapping . 24
A.3 Solution Set definitions . 25
A.3.1 IDL definition structure . 25
A.3.2 IDL specification "BulkCmIRPConstDefs.idl" . 26
A.3.3 IDL specification "BulkCMIRPSystem.idl" . 29
A.3.4 IDL specification "BulkCMIRPNotifications.idl" . 37
Annex B (normative): XML Definitions . 39
B.1 Architectural Features . 39
B.1.1 Syntax for Distinguished Names . 39
B.2 Structure and content of configuration data XML files . 39
B.2.1 Global structure . 39
B.2.2 XML elements fileHeader and fileFooter . 41
B.2.2.1 XML element fileHeader . 41
B.2.2.2 XML element fileFooter . 41
B.2.3 XML element configData. 42
B.2.4 NRM-specific XML elements . 43
B.2.4.1 NRM-specific XML schemas . 43
B.2.4.2 Generic mapping rules . 43
B.2.5 XML attribute specification modifier . 46
B.2.6 XML elements VsDataContainer, vsData and vsDataFormatVersion . 50
B.3 Structure and content of session log XML files . 51
B.3.1 Global structure . 51
B.3.2 XML elements fileHeader and fileFooter . 52
B.3.3 XML element activity . 52
ETSI
3GPP TS 32.616 version 15.1.0 Release 15 4 ETSI TS 132 616 V15.1.0 (2019-10)
B.4 Solution Set definitions . 54
B.4.1 XML definition structure . 54
B.4.2 Graphical Representation . 55
B.4.3 XML Schema “configData.xsd” . 56
B.4.4 Example XML Schema “NNRncHandOver.1.1.xsd” . 59
B.4.5 XML Schema “sessionLog.xsd” . 60
B.4.6 XML Schema “bulkCMIRPNotif.xsd” . 62
Annex C (normative): SOAP Solution Set . 64
C.1 Architectural features . 64
C.1.1 Syntax for Distinguished Names . 64
C.1.2 Supported W3C specifications . 64
C.1.3 Prefixes and namespaces . 64
C.1.4 Filter language . 64
C.2 Mapping . 65
C.2.1 Operation and notification mapping . 65
C.2.2 Operation parameter mapping . 66
C.2.2.1 Operation startSession . 66
C.2.2.1.1 Input parameters . 66
C.2.2.1.2 Output parameters . 66
C.2.2.1.3 Fault definition . 66
C.2.2.2 Operation endSession . 66
C.2.2.2.1 Input parameters . 66
C.2.2.2.2 Output parameters . 67
C.2.2.2.3 Fault definition . 67
C.2.2.3 Operation abortSessionOperation . 67
C.2.2.3.1 Input parameters . 67
C.2.2.3.2 Output parameters . 67
C.2.2.3.3 Fault definition . 67
C.2.2.4 Operation getSessionIds . 68
C.2.2.4.1 Input parameters . 68
C.2.2.4.2 Output parameters . 68
C.2.2.4.3 Fault definition . 68
C.2.2.5 Operation getSessionStatus . 68
C.2.2.5.1 Input parameters . 68
C.2.2.5.2 Output parameters . 68
C.2.2.5.3 Fault definition . 69
C.2.2.6 Operation getSessionLog . 69
C.2.2.6.1 Input parameters . 69
C.2.2.6.2 Output parameters . 69
C.2.2.6.3 Fault definition . 69
C.2.2.7 Operation upload . 70
C.2.2.7.1 Input parameters . 70
C.2.2.7.2 Output parameters . 70
C.2.2.7.3 Fault definition . 70
C.2.2.8 Operation download . 70
C.2.2.8.1 Input parameters . 70
C.2.2.8.2 Output parameters . 71
C.2.2.8.3 Fault definition . 71
C.2.2.9 Operation validate . 71
C.2.2.9.1 Input parameters . 71
C.2.2.9.2 Output parameters . 71
C.2.2.9.3 Fault definition . 71
C.2.2.10 Operation preactivate . 72
C.2.2.10.1 Input parameters . 72
C.2.2.10.2 Output parameters . 72
C.2.2.10.3 Fault definition . 72
C.2.2.11 Operation activate . 72
C.2.2.11.1 Input parameters . 72
C.2.2.11.2 Output parameters . 73
ETSI
3GPP TS 32.616 version 15.1.0 Release 15 5 ETSI TS 132 616 V15.1.0 (2019-10)
C.2.2.11.3 Fault definition . 73
C.2.2.12 Operation fallback . 73
C.2.2.12.1 Input parameters . 73
C.2.2.12.2 Output parameters . 73
C.2.2.12.3 Fault definition . 73
C.3 Solution Set definitions . 74
C.3.1 WSDL definition structure . 74
C.3.2 Graphical Representation . 74
C.3.3 WSDL specification “BulkCMIRPSystem.wsdl” . 75
Annex D (informative): Change history . 85
History . 86

ETSI
3GPP TS 32.616 version 15.1.0 Release 15 6 ETSI TS 132 616 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.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 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 action on a NE of the 3G network or as part of a complex procedure involving actions on
many NEs.
ETSI
3GPP TS 32.616 version 15.1.0 Release 15 7 ETSI TS 132 616 V15.1.0 (2019-10)
1 Scope
The present document specifies the Solution Sets for the IRP whose semantics are specified in Bulk CM IRP:
Information Service (3GPP TS 32.612 [9]).
This Solution Set specification is related to 3GPP TS 32.612 [9].
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.150: "Telecommunication management; Integration Reference Point (IRP) Concept
and definitions".
[4] 3GPP TS 32.300: "Telecommunication management; Configuration Management (CM); Name
convention for Managed Objects".
[5] 3GPP TS 32.306: "Telecommunication management; Configuration Management (CM);
Notification Integration Reference Point (IRP): Solution Set (SS) definitions".
[6] 3GPP TS 32.312: "Telecommunication management; Generic Integration Reference Point (IRP)
management; Information Service (IS)".
[7] 3GPP TS 32.316: "Telecommunication management; Generic Integration Reference Point (IRP)
management: Solution Set (SS) definitions".
[8] 3GPP TS 32.611: " Technical Specification Group Services and System Aspects;
Telecommunication management; Configuration Management (CM); Bulk CM Integration
Reference Point (IRP): Requirements ".
[9] 3GPP TS 32.612: "Telecommunication management; Configuration Management (CM); Bulk CM
Integration Reference Point (IRP); Information Service (IS)".
[10] 3GPP TS 32.622: "Telecommunication management; Configuration Management (CM); Generic
network resources Integration Reference Point (IRP): Network Resource Model (NRM)".
[11] 3GPP TS 32.626: "Telecommunication management; Configuration Management (CM); Generic
network resources Integration Reference Point (IRP): Solution Set (SS) definitions".
[12] 3GPP TS 32.632: "Telecommunication management; Configuration Management (CM); CN
network resources Integration Reference Point (IRP): Network Resource Model (NRM)".
[13] 3GPP TS 32.636: "Telecommunication management; Configuration Management (CM); Core
network resources Integration Reference Point (IRP): Solution Set (SS) definitions".
[14] 3GPP TS 32.642: "Telecommunication management; Configuration Management (CM); UTRAN
network resources Integration Reference Point (IRP): Network Resource Model (NRM)".
ETSI
3GPP TS 32.616 version 15.1.0 Release 15 8 ETSI TS 132 616 V15.1.0 (2019-10)
[15] 3GPP TS 32.646: "Telecommunication management; Configuration Management (CM); UTRAN
network resources Integration Reference Point (IRP): Solution Set (SS) definitions".
[16] 3GPP TS 32.652: "Telecommunication management; Configuration Management (CM); GERAN
network resources Integration Reference Point (IRP): Network Resource Model (NRM)".
[17] 3GPP TS 32.656: "Telecommunication management; Configuration Management (CM); GERAN
network resources Integration Reference Point (IRP): Solution Set (SS) definitions".
[18] 3GPP TS 32.692 "Inventory Management (IM) network resources Integration Reference Point
(IRP): Network Resource Model (NRM)".
[19] 3GPP TS 32.696: "Telecommunication management; Inventory Management (IM) Network
Resource Model (NRM); Integration Reference Point (IRP): Solution Set (SS) definitions".
[20] 3GPP TS 32.716: "Telecommunication management; Configuration Management (CM); Transport
Network (TN) interface Network Resource Model (NRM) Integration Reference Point (IRP):
Solution Set (SS) definitions".
[21] 3GPP TS 32.736: "IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration
Reference Point (IRP): Solution Set (SS) definitions".
[22] 3GPP TS 32.742: "Telecommunication management; Configuration Management (CM);
Signalling Transport Network (STN) Interface Network Resource Model (NRM) Integration
Reference Point (IRP): Information Service (IS)".
[23] 3GPP TS 32.746: "Telecommunication management; Configuration Management (CM);
Signalling Transport Network (STN) Interface Network Resource Model (NRM) Integration
Reference Point (IRP): Solution Set (SS) definitions".
[24] 3GPP TS 32.756: " Telecommunication management; Evolved Packet Core (EPC) Network
Resource Model (NRM) Integration Reference Point (IRP): Solution Set (SS) definitions".
[25] 3GPP TS 32.766: "Telecommunication management; Evolved Universal Terrestrial Radio Access
Network (E UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP):
Solution Set (SS) definitions".
[26] OMG Notification Service, Version 1.0.
[27] W3C REC-xml-20001006: "Extensible Markup Language (XML) 1.0 (Second Edition)".
[28] W3C REC-xmlschema-0-20010502: "XML Schema Part 0: Primer".
[29] W3C REC-xmlschema-1-20010502: "XML Schema Part 1: Structures".
[30] W3C REC-xmlschema-2-20010502: "XML Schema Part 2: Datatypes".
[31] W3C REC-xml-names-19990114: "Namespaces in XML".
[32] W3C SOAP 1.1 specification (http://www.w3.org/TR/2000/NOTE-SOAP-20000508/)
[33] W3C XPath 1.0 specification (http://www.w3.org/TR/1999/REC-xpath-19991116)
[34] W3C WSDL 1.1 specification (http://www.w3.org/TR/2001/NOTE-wsdl-20010315)
[35] W3C SOAP 1.2 specification (http://www.w3.org/TR/soap12-part1/)
[36] 3GPP TS 32.172: "Telecommunication management; Subscription Management (SuM) Network
Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)".
[37] 3GPP TS 32.176: "Telecommunication management; Subscription Management (SuM) Network
Resource Model (NRM) Integration Reference Point (IRP): Solution Set (SS) definitions".
[38] 3GPP TS 32.522: "Telecommunication management; Self-Organizing Networks (SON) Policy
Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)".
ETSI
3GPP TS 32.616 version 15.1.0 Release 15 9 ETSI TS 132 616 V15.1.0 (2019-10)
[39] 3GPP TS 32.526: "Telecommunication management; Self-Organizing Networks (SON) Policy
Network Resource Model (NRM) Integration Reference Point (IRP): Solution Set (SS)
definitions".
[40] 3GPP TS 32.712: "Telecommunication management; Configuration Management (CM); Transport
Network (TN) Network Resource Model (NRM) Integration Reference Point (IRP): Information
Service (IS)".
[41] 3GPP TS 32.722: "Telecommunication management; Configuration Management (CM); Repeater
network resources Integration Reference Point (IRP); information Service (IS)".
[42] 3GPP TS 32.726: "Telecommunication management; Configuration Management (CM); Repeater
network resources Integration Reference Point (IRP): Solution Set (SS) definitions".
[43] 3GPP TS 32.732: "Telecommunication management; IP Multimedia Subsystem (IMS) Network
Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)".
[44] 3GPP TS 32.752: "Telecommunication management; Evolved Packet Core (EPC) Network
Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)".
[45] 3GPP TS 32.762: "Telecommunication management; Evolved Universal Terrestrial Radio Access
Network (E UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP):
Information Service (IS)".
[46] 3GPP TS 32.772: "Telecommunication management; Home Node B (HNB) Subsystem (HNS);
Network Resource Model (NRM); Integration Reference Point (IRP): Information Service (IS)".
[47] 3GPP TS 32.776: "Telecommunication management; Home Node B (HNB) Subsystem (HNS);
Network Resource Model (NRM); Integration Reference Point (IRP): Solution Set (SS)
definitions".
[48] 3GPP TS 32.782: "Telecommunication management; Home enhanced Node B (HeNB) Subsystem
(HeNS); Network Resource Model (NRM); Integration Reference Point (IRP): Information
Service (IS)".
[49] 3GPP TS 32.786: "Telecommunication management; Home enhanced Node B (HeNB) Subsystem
(HeNS); Network Resource Model (NRM); Integration Reference Point (IRP): Solution Set (SS)
definitions".
[50] 3GPP TS 32.796: "Telecommunication management; Generic Radio Access Network (RAN)
Network Resource Model (NRM) Integration Reference Point (IRP): Solution Set (SS)
definitions".
[51] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
ETSI
3GPP TS 32.616 version 15.1.0 Release 15 10 ETSI TS 132 616 V15.1.0 (2019-10)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms given in 3GPP TR 21.905 [51] , TS 32.101 [1], TS 32.102 [2], TS
32.150 [3], TS 32.172 [36], TS 32.522 [38], TS 32.611 [8], TS 32.612 [9], TS 32.622 [10], TS 32.632 [12], TS 32.642
[14], TS 32.652 [16], TS 32.692 [18], TS 32.712 [40], 32.722 [41], TS 32.732 [43], TS 32.742 [22], TS 32.752 [44], TS
32.762 [45], TS 32.772 [46] and TS 32.782 [48] and the following apply:

IRP document version number string (or "IRPVersion"): See 3GPP TS 32.312 [6].
XML file: a file containing an XML document.
XML document: see [27]; in the scope of this specification, an XML document is composed of the succession of an
optional XML declaration followed by a root XML element.
XML declaration: see [27]; it specifies the version of XML and the character encoding being used.
XML element: see [27]; an XML element has a type, is identified by a name, may have a set of XML attribute
specifications and is either composed of the succession of an XML start-tag followed by the XML content of the XML
element followed by an XML end-tag, or composed simply of an XML empty-element tag; each XML element may
contain other XML elements.
empty XML element: see [27]; an XML element having an empty XML content; an empty XML element still possibly
has a set of XML attribute specifications; an empty XML element is either composed of the succession of an XML
start-tag directly followed by an XML end-tag, or composed simply of an XML empty-element tag.
XML content (of an XML element): empty if the XML element is simply composed of an XML empty-element tag;
otherwise the part, possibly empty, of the XML element between its XML start-tag and its XML end-tag.
XML start-tag: see [27]; the beginning of a non-empty XML element is marked by an XML start-tag containing the
name and the set of XML attribute specifications of the XML element.
XML end-tag: see [27]; the end of a non-empty XML element is marked by an XML end-tag containing the name of
the XML element.
XML empty-element tag: see [27]; an empty XML element is composed simply of an empty-element tag containing
the name and the set of XML attribute specifications of the XML element.
XML attribute specification: see [27]; an XML attribute specification has a name and a value.
DTD: see [27]; a DTD defines structure and content constraints to be respected by an XML document to be valid with
regard to this DTD.
XML schema: see [28], [29] and [30]; more powerful than a DTD, an XML schema defines structure and content
constraints to be respected by an XML document to conform with this XML schema; through the use of XML
namespaces several XML schemas can be used together by a single XML document; an XML schema is itself also an
XML document that shall conform with the XML schema for XML schemas.
XML namespace: see [31]; in the scope of this specification, enables qualifying element and attribute names used in
XML documents by associating them with namespaces identified by different XML schemas.
XML complex type: see [28], [29] and [30]; defined in an XML schema; cannot be directly used in an XML document;
can be the concrete type or the derivation base type for an XML element type or for another XML complex type;
ultimately defines constraints for an XML element on its XML attribute specifications and/or its XML content.
XML element type: see [28], [29] and [30]; declared by an XML schema; can be directly used in an XML document;
as the concrete type of an XML element, directly or indirectly defines constraints on its XML attribute specifications
and/or its XML content; can also be the concrete type or the derivation base type for another XML element type.
ETSI
3GPP TS 32.616 version 15.1.0 Release 15 11 ETSI TS 132 616 V15.1.0 (2019-10)
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [51] 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 [51].].
CM Configuration Management
DN Distinguished Name
MO Managed Object
MOC Managed Object Class
RDN Relative Distinguished Name
SS Solution Set
WSDL Web Service Description Language
4 Solution Set (SS) definitions
This specification defines the following 3GPP Bulk CM IRP Solution Set Definitions:
Annex A provides the CORBA Solution Set.
Annex B provides the XML Definitions.
Annex C provides the SOAP Solution Set.
ETSI
3GPP TS 32.616 version 15.1.0 Release 15 12 ETSI TS 132 616 V15.1.0 (2019-10)
Annex A (normative):
CORBA Solution Set
This annex specifies the CORBA Solution Set for the IRP whose semantics are specified in 3GPP TS 32.612 [9].
A.1 Architectural features
The overall architectural feature of Bulk CM IRP is specified in 3GPP TS 32.612 [9].
This clause specifies features that are specific to the CORBA SS.
A.1.1 Syntax for Distinguished Names
The syntax of a Distinguished Name is defined in 3GPP TS 32.300 [4].
A.1.2 BulkCMIRPNotifications Interface
OMG CORBA Notification push operation is used to realise the notification of BulkCMIRPNotifications. All the
notifications in this interface are implemented using this push_structured_event method.
A.1.2.1 Method push (M)
module CosNotifyComm {
…
Interface SequencePushConsumer : NotifyPublish {
void push_structured_events(
in CosNotification::EventBatch notifications)
raises( CosEventComm::Disconnected);
…
}; // SequencePushConsumer
…
}; // CosNotifyComm
NOTE 1: The push_structured_events method takes an input parameter of type EventBatch as defined in the OMG
CosNotification module (OMG Notification Service [26]). This data type is the same as a sequence of
Structured Events. Upon invocation, this parameter will contain a sequence of Structured Events being
delivered to IRPManager by IRPAgent to which it is connected.
NOTE 2: The maximum number of events that will be transmitted within a single invocation of this operation is
controlled by IRPAgent wide configuration parameter.
NOTE 3: The amount of time the supplier (IRPAgent) of a sequence of Structured Events will accumulate
individual events into the sequence before invoking this operation is controlled by IRPAgent wide
configuration parameter as well.
NOTE 4: IRPAgent may push EventBatch with only one Structured Event.
ETSI
3GPP TS 32.616 version 15.1.0 Release 15 13 ETSI TS 132 616 V15.1.0 (2019-10)
A.2 Mapping
A.2.1 General mappings
All MOs are arranged in a containment structure, according to the containment relations defined in the NRM. This
structure is held internally by the IRPAgent. Externally, the MO containment structure is defined by the semantics in
the distinguished name syntax. The distinguished name (DN) for a MO contains the distinguished name of the parent
plus the Relative DN for the MO itself.
Associations as defined in the NRM (UML) are in this document mapped to attributes in the MIB. The names of the
roles for an association in the NRM are used for defining attribute names in the MIB. When the cardinality for a role is
0.1 or 1.1 the datatype for the attribute is defined as a MO reference. The value of a MO reference contains the
distinguished name of the referred MO. When the cardinality for a role allows more than one referred MO instances,
the attribute will contain a sequence of MO references (i.e., DNs).
A.2.2 Operation and Notification mapping
The IS part of Bulk CM: IRP defines semantics of operations and notifications visible across the Bulk Configuration
IRP. The table below indicates mapping of these operations and notifications to their equivalents defined in this
document.
There are 3 qualifications for each row of the following mapping table.
The 3 qualifications correspond to the three IS-defined packages: Controlled Upload & Provisioning, Controlled Upload
and Simple Upload.
Not all operations/notifications specified in the following table are required for all 3 packages.
An ‘-‘ indicates that the subject operation or notification is not allowed by that corresponding package.
ETSI
3GPP TS 32.616 version 15.1.0 Release 15 14 ETSI TS 132 616 V15.1.0 (2019-10)
Table A.2.2: Mapping from IM Notification/Operation to SS equivalents
IS Operation/ notification SS Method Qualifier
startSession start_session M,M,-
endSession end_session M,M,-
upload upload M,M,M
download download M,-,-
activate activate M,-,-
getSessionStatus get_session_status M,M,-
getSessionIds get_session_ids M,M,-
getSessionLog get_session_log M,M,-
fallback fallback M,-,-
abortSessionOperation abort_session_operation M,M,-
getIRPVersion get_bulk_cm_irp_versions M,-,-
get_controlled_upload_bulk_cm_irp_versions -,M,-
get_simple_upload_bulk_cm_irp_versions -,-,M
notifySessionStateChanged push_structured_event M,M,M
Note that OMG Notification Service OMG Notification Service
[26] defines this method.
See clause A.1.2.
notifyGetSessionLogEnded push_structured_event M,M,-
Note that OMG Notification Service OMG Notification Service
[26] defines this method.
See clause A.1.2.
preactivate preactivate O,-,-
validate validate O,-,-
getOperationProfile get_bulk_cm_irp_operation_profile O,-,-
get_controlled_upload_bulk_cm_irp_operation_profile -,O,-
get_simple_upload_bulk_cm_irp_operation_profile -,-,O
getNotificationProfile get_bulk_cm_irp_notification_profile O,
...