|
TECHNICAL SPECIFICATION
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
LTE;
Telecommunication management;
Integration Reference Point (IRP) Concept and definitions
(3GPP TS 32.150 version 14.1.0 Release 14)
---------------------- Page: 1 ----------------------
3GPP TS 32.150 version 14.1.0 Release 14 1 ETSI TS 132 150 V14.1.0 (2017-04)
Reference
RTS/TSGS-0532150ve10
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:
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 only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
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:
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.
© European Telecommunications Standards Institute 2017.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3GPP TS 32.150 version 14.1.0 Release 14 2 ETSI TS 132 150 V14.1.0 (2017-04)
Intellectual Property Rights
IPRs essential or potentially essential to the present document 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.
Foreword
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, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 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.150 version 14.1.0 Release 14 3 ETSI TS 132 150 V14.1.0 (2017-04)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 4
Introduction . 4
1 Scope . 5
2 References . 5
3 Definitions and abbreviations . 6
3.1 Definitions . 6
3.2 Abbreviations . 7
4 Integration Reference Points (IRPs) . 8
4.1 Introduction . 8
4.1.1 General . 8
4.1.2 IRP Specifications Approach . 9
4.2 Integration levels . 10
4.2.1 Application integration . 10
4.3 Application of IRPs . 11
4.4 Defining the IRPs . 12
4.5 Void . 12
4.6 Mandatory, Optional and Conditional qualifiers . 13
4.7 System context for Interface IRPs . 15
4.8 Object instance visibility . 16
Annex A (informative): Void . 17
Annex B (normative): Void . 18
Annex C (informative): Void . 19
Annex D (informative): Void . 20
Annex E (normative): Void . 21
Annex F (informative): Void . 22
Annex G (normative): IOC Properties and Inheritance . 23
G.1 Property . 23
G.2 Inheritance . 24
Annex H (normative): Interface Properties and Inheritance . 25
H.1 Property . 25
H.2 Inheritance . 25
Annex I (normative): Entity (Interface, IOC and Attribute) Import . 26
Annex K (informative): Change history . 27
History . 28
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 32.150 version 14.1.0 Release 14 4 ETSI TS 132 150 V14.1.0 (2017-04)
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:
TS 32.150: Integration Reference Point (IRP) Concept and definitions
TS 32.151: Integration Reference Point (IRP) Information Service (IS) template
TS 32.152: Integration Reference Point (IRP) Information Service (IS) Unified Modelling Language (UML)
repertoire
TS 32.153 Integration Reference Point (IRP) technology specific templates
TS 32.154 Backward and Forward Compatibility (BFC); Concept and definitions
TS 32.155 Telecommunication management; Requirements template
TS 32.156 Telecommunication management; Fixed Mobile Convergence (FMC) Model Repertoire
TS 32.157 Telecommunication management; Integration Reference Point (IRP) Information Service (IS) template
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 32.150 version 14.1.0 Release 14 5 ETSI TS 132 150 V14.1.0 (2017-04)
1 Scope
The present document provides the overall concept for all Integration Reference Point (IRP) specifications.
Relevant IRP overview and high-level definitions are already provided in 3GPP TS 32.101 [1] and TS 32.102 [2].
IRP specifications are intended to be applicable to any management interface (see definition of Integration Reference
Point in subclause 3.1).
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.151: "Telecommunication management; Integration Reference Point (IRP)
Information Service (IS) template".
[4] Void.
[5] ITU-T Recommendation M.3020 (05/2009): "TMN Interface Specification Methodology".
[6] OMG IDL Style Guide, ab/98-06-03, June 17, 1998.
[7] 3GPP TS 32.111-2: "Telecommunication management; Fault Management; Part 2: Alarm
Integration Reference Point: Information Service (IS)".
[8] 3GPP TS 32.601: "Telecommunication management; Configuration Management (CM); Basic CM
Integration Reference Point (IRP); Requirements".
[9] 3GPP TS 32.602: "Telecommunication management; Configuration Management (CM); Basic CM
Integration Reference Point (IRP): Information Service (IS)".
[10] 3GPP TS 32.606: "Telecommunication management; Configuration Management (CM); Basic CM
Integration Reference Point (IRP); Solution Set (SS) definitions".
[11] 3GPP TS 28.621: "Telecommunication management; Generic Network Resource Model (NRM)
Integration Reference Point (IRP); Requirements".
[12] 3GPP TS 28.622: "Telecommunication management; Generic Network Resource Model (NRM)
Integration Reference Point (IRP) ; Information Service (IS)".
[13] 3GPP TS 28.623: "Telecommunication management; Generic Network Resource Model (NRM)
Integration Reference Point (IRP) ; Solution Set (SS) definitions".
[14] 3GPP TS 28.624: "Telecommunication management; State Management Data Definition
Integration Reference Point (IRP) ; Requirements".
[15] 3GPP TS 28.625: "Telecommunication management; State Management Data Definition
Integration Reference Point (IRP) ; Information Service (IS)".
ETSI
---------------------- Page: 6 ----------------------
3GPP TS 32.150 version 14.1.0 Release 14 6 ETSI TS 132 150 V14.1.0 (2017-04)
[16] 3GPP TS 28.626: "Telecommunication management; State Management Data Definition
Integration Reference Point (IRP); Solution Set (SS) definitions".
[17] 3GPP TS 32.107 Fixed Mobile Convergence (FMC) Federated Network Information Model
(FNIM)
[18] 3GPP TS 32.156 Fixed Mobile Convergence (FMC) Model Repertoire
[19] 3GPP TS 32.157 Integration Reference Point (IRP) Information Service (IS) template
[20] 3GPP TS 28.620 Fixed Mobile Convergence (FMC) Federated Network Information Model
(FNIM) Umbrella Information Model (UIM)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2],
3GPP TS 32.151 [3] , 3GPP TS 32.107 [17], 3GPP TS 32.157 [19], 3GPP TS 28.620 [20] and the following apply:
Data Definition IRP: 3GPP publishes IRP specifications relating to commonly used data definitions that can be
imported for use by Interface IRP and/or NRM IRP. This term represents all such specifications.
NOTE 1: An example of a Data Definition IRP is the State Management IRP (32.671 [14], 32.672 [15], 32.676
[16]).
Information Object Class (IOC): information that can be passed/used in management interfaces and is modelled using
the stereotype "Class" in the UML meta-model. For a formal definition of Information Object Class and its structure of
specification, see 3GPP TS 32.151[3].
Integration Reference Point (IRP): An architectural concept that is described by a set of specifications for definition
of a certain aspect of a management interface, comprising a Requirements specification, an Information Service
specification, and one or more Solution Set specifications.
Interface IRP: 3GPP publishes a number of IRP specifications each of which is related to a set of operations and
notifications for a specific telecom management domain such as alarm management, configuration management, etc.
Interface IRPs also contain definitions of SupportIOCs. This term represents all such specifications.
NOTE 2: An example of an Interface IRP is the Basic CM IRP (the set of TSs 32.601 [8], 32.602 [9], 32.606 [10]).
IRPAgent: Encapsulation of a well-defined subset of network (element) functions. It interacts with IRPManagers using
one or more IRPs. From the IRPManager's perspective, the IRPAgent behaviour is only visible via the IRP(s).
Information Service (IS): description of the information related to the entities (either network resources or support
objects) to be managed and the way that the information may be managed for a certain functional area (e.g. the Alarm
IRP Information Service in the fault management area). Information Services are defined for all IRPs.
IRPManager: Modeling of a user of IRPAgent(s) which interacts directly with the IRPAgent(s) using IRP(s).
Since the IRPManager represents an IRPAgent user, it gives a clear picture of what the IRPAgent is supposed to do.
From the IRPAgent perspective, the IRPManager behaviour is only visible via the IRP.
Managed Object Class (MOC): information that can be passed/used in management interfaces in a similar way to
IOC.
NOTE 3: See subclause 7.3.4.3 of [5] on Guidelines for definitions of Managed Object.
Network Resource Model (NRM): description of Information Object Classes representing the manageable aspects of
network resources.
NOTE 4: Examples of network resources are RNC and NodeB.
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 32.150 version 14.1.0 Release 14 7 ETSI TS 132 150 V14.1.0 (2017-04)
NRM IRP: 3GPP publishes a number of IRP specifications each of which is related to a particular NRM (Network
Resource Model) as defined in 3GPP TS 32.101 [1]. NRM IRPs do not define any operations or notifications. This term
represents all such specifications.
NOTE 5: In some NRM IRP titles, for historic reasons, they are named "…network resources IRP").
NOTE 6: An example of an NRM IRP is the Generic NRM IRP (32.621 [11], 32.622 [12], 32.626 [13]).
Solution Set (SS): mapping of the IRP Information Service (IS) defined entities (that are technology-agnostic) to
technology specific termed entities.
NOTE7: SS does not contain specification of the entities' semantics which can be found in the corresponding
IS.One IS can be mapped to one or several SSs.
NOTE 8: Examples of an IS defined entity and technology specific termed entity are IOC and MOC respectively.
SupportIOC: representation of a particular capability, introduced to model a management service.
NOTE 9: As an example of SupportIOC, in the Alarm IRP Information Service [59] there are the AlarmInformation
and AlarmList IOCs.
NOTE 10: See Annex [F] of [18] for information about the difference between IOC and SupportIOC.
Yyy IRP: For a specific Interface IRP such as the Basic CM IRP, when the letters Yyy are replaced by the specific key
words naming that IRP (in the given example the Yyy is replaced by “Basic CM”), this term represents all
specifications that are part of that Interface IRP.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2],
3GPP TS 32.151 [3] and the following apply:
CORBA Common Object Request Broker Architecture
EM Element Manager
GDMO Guidelines for the Definition of Managed Objects
GUI Graphical User Interface
IDL Interface Definition Language
IOC Information Object Class
IRP Integration Reference Point
IS Information Service
MOC Managed Object Class
NE Network Element
NM Network Manager
NRM Network Resource Model
OMG Object Management Group
ORB Object Request Broker
PSA Product Specific Application
SMP System Management Processes
SNM Sub-Network Manager
SS Solution Set
TMF TeleManagement Forum
TOM Telecom Operations Map
UML Unified Modelling Language
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 32.150 version 14.1.0 Release 14 8 ETSI TS 132 150 V14.1.0 (2017-04)
4 Integration Reference Points (IRPs)
4.1 Introduction
For the purpose of management interface development 3GPP has developed an interface concept known as Integration
Reference Point (IRP) to promote the wider adoption of standardized management interfaces in telecommunication
networks. The IRP concept and associated methodology employs protocol and technology neutral modelling methods as
well as protocol specific solution sets to achieve its goals.
4.1.1 General
The three cornerstones of the IRP concept are:
- Top-down, process-driven modelling approach: The purpose of each IRP is automation of one specific task,
related to TMF TOM. This allows taking a "one step at a time" approach with a focus on the most important
tasks.
- Technology-independent modelling: To create from the requirements an interface technology independent
model. This is specified in the IRP Information Service.
- Standards-based technology-dependent modelling: To create one or more interface technology dependent
models from the technology independent model. This is specified in the IRP Solution Set(s).
IRP REQUIREMENTS
<<<>>> IRP INFO RMATION SERVICE
AAllarar mmIIRR PPOOpperer atatii oonsns
IRP Inform ation Service
sseelleeccttAlAlaarrmmIIRRPVePVerrssiioonn (())
acackknnowowlleeddgg eAeAllaarrmmss(())
unaunacckknn owowlledgeedgeAAll ararmmss(())
ususee ggeettAAllaarmrmLLiisstt()()
gegettAA lalarrmmCCoouu nntt(()) iimmppll ememenentt
SySysstteemm
ususee
imimppllee mmeenntt
AcActtoorr <<<>>>
AAllaarr mmIIRRPPNNoo titifificcaatiti oonn
nonottiiff yy(())
+
IRP SOLUTION SETS
SNSNMPMP
JAXMLVA
CMSOAIPP
COCORBRBAA
Figure 4.1: IRP components (with example Solution Sets; for definition of valid 3GPP Solution Sets,
see Annex C in TS 32.101 [1])
ETSI
---------------------- Page: 9 ----------------------
3GPP TS 32.150 version 14.1.0 Release 14 9 ETSI TS 132 150 V14.1.0 (2017-04)
4.1.2 IRP Specifications Approach
As highlighted in the previous subclause, IRP specifications are specified using a 3-level approach: Requirements, IS-
level and SS-level.
Furthermore, there are three categories of IRP specifications (see formal and more detailed definitions in subclause 3.1):
- Interface IRPs
- NRM IRPs
- Data Definition IRPs.
Each category is partitioned into Requirements, IS-level and SS-level specifications.
Requirements / Use Cases
Data
Interface IRP’s NRM IRP’s Relative stable
Definition IRP’s
over long
period of time
Information Service Definitions (UML)
• Notification IRP • Generic NRM
•Alarm IRP •CoreNW NRM
•
State Mgmt IRP
•BulkCM IRP •UMTS NRM’s
Changes only with
•etc
• KernelCM IRP • CDMA NRM’s
respect to addition
•BasicCM IRP • Inventory NRM
and extensions
•etc •etc
Changes with
new/better
Solution Set Definitions (CORBA, SOAP, XML, CMIP)
Technologies
Solution Set Definitions (other/future e.g. JAVA , SNMP)
Figure 4.2: The IRP 3-Level Specifications Approach combined with the three IRP categories.
Level 1:
The "Requirements-level" intends to provide conceptual and use cases definitions for a specific management
interface aspect as well as defining subsequent requirements for this IRP.
Level 2:
The "IS-level" provides the technology independent specification of an IRP.
Level 3:
The "SS-level" finally provides the mapping of IS definitions into one or more technology-specific Solution
Sets. This concept provides support for multiple interface technologies as applicable on a vendor and/or network
type basis and also enables accommodation of future interface technologies - without the need to redefine
requirements and IS-level definitions.
Usage of terms:
The term IOC and SupportIOC are used in IS-level specification. The term MOC is used in SS-level
specifications and it corresponds to IOC or SupportIOC defined in IS-level specification. This term MOC is a
term defined by ITU-T M.series Recommendations. See subclause 7.3.4.3 of [5] on Guidelines for definitions of
Managed Object, for information.
ETSI
---------------------- Page: 10 ----------------------
3GPP TS 32.150 version 14.1.0 Release 14 10 ETSI TS 132 150 V14.1.0 (2017-04)
4.2 Integration levels
Virtually all types of telecom/datacom networks comprise many different technologies purchased from several different
vendors. This implies that the corresponding management solution need to be built by integrating product-specific
applications from different vendors with a number of generic applications that each provide some aspect of
multi-vendor and/or multi-technology support. A complete management solution is thus composed of several
independent applications.
The following levels of integration are defined:
- Screen Integration: Each application provides its own specific Graphical User Interface (GUI) that need to be
accessible from a single, unified screen (a common desktop). A seamless integration between the various GUIs
is then required. Screen Integration is not specified in the present document.
- Application Integration: Applications need to interwork, on a machine-machine basis, in order to automate
various end-to-end processes of a communication provider.
4.2.1 Application integration
Interfaces related to application integration can be divided in the following three categories:
1) High-level generic interfaces: between generic applications on the network and service management layers.
The same approach and concepts apply for these as the next category.
2) High-level (technology-independent to the extent possible) interfaces: between product-specific and generic
applications are needed in order to automate and streamline frequently occurring tasks applicable to several types
of network elements. A top-down approach shall be taken when defining these interfaces, where the main input
is:
a) business processes of a communication provider; and
b) the types of generic applications that are used to implement the process support.
3) Detailed (product-specific) interfaces: between product-specific applications and the corresponding network
elements are of course also needed. These interfaces are defined using the traditional bottom-up approach, where
the actual network infrastructure is modelled. This is the traditional TMN approach to element management. The
management information in these interfaces is not further discussed in the present document, as it is internal to a
specific development organization and does not need to be open. In fact, by publishing the management
information in these interfaces, too much of the internal design may be revealed and it may become impossible
to later enhance the systems that are using the interfaces. The management services (operations and
notifications) and protocol shall however be open and standardized as long as they are independent of the NRM
describing the managed NEs/NRs.
ETSI
---------------------- Page: 11 ----------------------
3GPP TS 32.150 version 14.1.0 Release 14 11 ETSI TS 132 150 V14.1.0 (2017-04)
4.3 Application of IRPs
When providing integrated management solutions for multi-vendor networks, there is a strong requirement that the NEs
and the management solutions that go together with them are systems integratable.
It should be noted that these IRPs could be provided by an IRPAgent on any management interface.
These IRPs are introduced to ensure interoperability, for example between Product-Specific Applications (PSA) and the
Network and System Management Processes (SMP) of the Network Manager (NM) - see figure 4.3 from TS 32.101 [1].
These IRPs are considered to cover the most basic needs of task automation.
Network Manager
Network & System Management Processes
Network Network Network
Network Network Data
Planning & Inventory Maintenance
Provisioning Management
Development Management & Restoration
IRP (alternative 2)
IRP (alternative 1)
Service CM IRPs
Common IRPs
FM IRPs
PM IRPs
IRPs (Bulk, Inventory, (Notification, File
(Alarm ,Test.)
Xfer, Log…)
State ….)
EEElllemememenenent Mt Mt Maaannnaaagergerger
PSPSPSPSAAAA
PSAPSAPSAPSA
EEElllemememenenenttt Man Man Manaaagegegerrr
PSAPSAPSAPSA
PSAPSAPSAPSA
NENENE
PSA = Product Specific Application
NENENE
NE = Network Element
Figure 4.3: Examples of IRPs for application integration
Taking one of the above mentioned IRPs as an example, the Network and System Management Processes have similar
need to receive notifications from various PSAs. The corresponding service is formalize
...