4.1 Introduction

32.1503GPPIntegration Reference Point (IRP) Concept and definitionsRelease 17Telecommunication managementTS

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).

Figure 4.1: IRP components (with example Solution Sets; for definition of valid 3GPP Solution Sets, see Annex C in TS 32.101 [1])

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.

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.