4 IRP Framework

32.1033GPPIntegration Reference Point (IRP) overview and usage guideRelease 17Telecommunication managementTS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

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 model-driven development, protocol and technology neutral modelling methods as well as protocol specific solution sets to achieve its goals.

IRP Framework and Methodology related 3GPP specifications:

– 32.150 [2]: Integration Reference Point (IRP) Concept and definitions

– 32.153 [15]: IRP technology specific templates, rules and guidelines

– 32.154 [16]: Backward and Forward Compatibility Concept and definitions

– 32.155 [17]: Requirements template

– 32.156 [18]: Fixed Mobile Convergence (FMC) Model repertoire

– 32.157 [19]: IRP Information Service (IS) template

4.2 IRP Framework Highlights

4.2.1 IRP Concept

IRP specifications are specified using a 3-level approach: Requirements, IS-level and SS-level.

Figure 4.2-1: The IRP 3-level specifications approach combined with the three IRP categories

Requirements-level:

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.

IS-level:

The "IS-level" provides the technology independent specification of an IRP.

SS-level:

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.

4.2.2 Relationships between IRPs

There are three categories of IRP specifications:

– Interface IRPs

– NRM IRPs

– Data Definition IRPs

Each category is partitioned into Requirements, IS-level and SS-level specifications.

Relationships between various kinds of IRPs:

– Some Interface IRPs and NRM IRPs are used together. Such Interface IRPs operate on entities modelled by NRM IRPs. For example, operations defined in Basic CM IRP are used together with E- UTRAN NRM IRP to support E-UTRAN configuration management function.

– Interface IRPs are network/radio technology independent and can operate on entities modelled by NRM IRPs of different network technologies. For example, operations defined in Basic CM IRP are used together with E- UTRAN NRM IRP or UTRAN NRM IRP to support E- UTRAN or UTRAN configuration management functions.

– Interface IRPs are Converged Management ready (e.g. support management of fixed and/or mobile) and can operate on modelled mobile and/or fixed network entities.

– A Data Definition IRP provides common data definitions, referenced by specifications of Interface IRPs and NRM IRPs.

Figure 4.2-2: Relationship Interface IRP vs NRM IRP

4.2.3 IRP Development Principles

NRM IRP Extendibility – Enabling Technology, Organizational & Vendor-specific NRM extensions via

Rule-based NRM Extensions (e.g. Sub-classing)
vsDataContainer

Interface IRP Flexibility – Enabling: wide applicability, phased introduction capabilities & broad industry adoption (not just for wireless) via

Flexible use of qualifiers "mandatory", "optional", "conditional" for operation, notifications and/or parameters
NRM/Technology-neutrality & avoiding competing procedures

4.2.4 IRP Specification Structure

32-series IRPs follow a uniform specification structure:

– xx1: xyz IRP Requirements

– xx2: xyz IRP IS

– xx3: xyz IRP CORBA SS (merged into xx6 after R9)

– xx4: xyz IRP CMIP SS (retired after R6)

– xx5: xyz IRP XML Definitions (applicable for NRM’s & notification emitting IRPs – merged into xx6 after R9)

– xx6: xyz IRP SS (since Rel-10, containing all technology specific Solution Set definitions)

xx7: xyz IRP SOAP SS (merged into xx6 after R9)

28-series IRPs (supporting FMC) consisting of 3-specification sets, structured as follows:

– 28.3xx: Interface IRP specifications.

– 28.611-28.616 EPC and non-3GPP access interworking system NRM IRP

– 28.620-28.649: Common/Generic NRM IRPs.

– 28.650-28.699: Access Network related NRM IRPs.

– 28.700-28.729: CN-related NRM IRPs.

– 28.730-28.749: Transport-related NRM IRPs.

– 28.750-28.769: Service-related NRM IRPs.

– 28.770-28.799: reserved for future topic NRM IRPs.

4.2.5 Void

4.3 IRP related High-level Requirements & Architecture Specifications

The IRP Framework has been developed in response to management requirements documented in the following specifications:

– 32.101 [3]: Principles and high level requirements

– 32.102 [20]: Architecture

– 32.107 [21]: Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM)

– 32.111-1 [22]: 3G fault management requirements

– 32.140 [23], SuM requirements

– 32.141 [24]: SuM architecture

– 32.300 [25]: Name convention for Managed Objects

– 32.401 [26]: PM Concept and requirements

– 32.500 [27]: SON Concepts and requirements

– 32.511 [28]: ANR management Concepts and requirements

– 32.521 [29]: Self-optimization Concepts and requirements

– 32.541 [30]: Self-healing Concepts and requirements

– 32.551 [31]: Energy Saving Management (ESM) Concepts and requirements

– 32.600 [32]: CM Concept and high-level requirements

4.4 Converged Management and IRPs

As outlined in previous sections, 3GPP Interface IRPs are network-technology-independent, and therefore can be utilized for the management of various network technologies.

To further ease converged management (the common management of multiple network technologies) and to address the need for OPEX reduction, 3GPP together with other industry organizations (i.e. NGMN and TM Forum) developed jointly the following specifications:

– Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) (published in 3GPP as TS 32.107 [21])

– Defining conceptually the federated network information model and the relationships between participating models (see also section 5.5 of TS 32.101 [3]).

– FMC FNIM Umbrella Information Model (UIM) (published in 3GPP as TS 28.620 [34])

– Providing abstract definitions of information objects applicable across Domain/Technology-specific Concrete Models.

– Fixed Mobile Convergence (FMC) Model repertoire (published in 3GPP as TS 32.156 [18])

– Defining meta definitions for models supporting converged management.

– Fixed Mobile Convergence (FMC) 3GPP / TM Forum Concrete Model Relationships and Use Cases

– Proposing the specific structure of model and realisation of that structure across 3GPP and TM Forum by taking advantage of current TM Forum transport-oriented model work (SID, MTNM/MTOSI) as well as current 3GPP SA5 mobile-oriented model work (NRM IRPs etc.).

Based on above, 3GPP has applied definitions provided by these specifications by creating the 28-series variants of the 3GPP NRM IRPs to support converged management.