Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Management

NRM IRP

Network Resource Model Integration Reference Point

Management →

NRM IRP is a set of 3GPP specifications that defines the Network Resource Model data models for management interfaces, without specifying operations or notifications.

Introduced
Rel-8
Where
Management
Specifications
2 specs
NRM IRP Description Purpose What changed Neighbours Specifications

Description

NRM IRP (Network Resource Model Integration Reference Point) is a collective term for a series of 3GPP specifications that define Network Resource Models (NRMs) as part of the Integration Reference Point (IRP) framework. These specifications are published in 3GPP TS 32.101 and related documents (e.g., 32.103, 32.150). An NRM IRP describes the information model for a particular set of network resources, such as eNodeB, gNodeB, cells, and their attributes, relationships, and containment. However, NRM IRPs do not define any operations or notifications; they are purely informational models that are used by other IRPs (e.g., Basic CM IRP) to implement management operations.

The IRP framework is a cornerstone of 3GPP management architecture, enabling standardized, multi-vendor network management. It consists of several types of IRPs: NRM IRPs (information models), Solution Set (SS) IRPs (protocol-specific implementations, e.g., CORBA, XML, SOAP), and others. NRM IRPs are technology-agnostic and define the semantics of managed objects. For example, the Generic NRM IRP (specified in 28.621, 28.622, 28.623) defines generic classes like ManagedElement, SubNetwork, and their attributes. Specific NRM IRPs, such as the E-UTRAN NRM IRP, extend these to define technology-specific resources.

NRM IRPs are used by management systems (e.g., Element Managers, Network Managers) to understand the structure of network resources. They are typically implemented using a protocol such as NETCONF/YANG or RESTful APIs in modern networks, but the IRP framework itself is protocol-independent. The NRM IRP specifications are maintained across releases, with updates to reflect new technologies (e.g., 5G NR) and management requirements.

In practice, an NRM IRP provides a UML model or a set of class definitions that describe the managed objects. For instance, the Generic NRM IRP defines a ManagedElement class with attributes like userLabel, vendorName, and swVersion. These models are then used by the Basic CM IRP to perform CRUD (Create, Read, Update, Delete) operations on the actual network elements. Without NRM IRPs, management systems would not have a standardized way to interpret the data exposed by network elements.

The evolution of NRM IRPs reflects the changing landscape of mobile networks. Early releases focused on 2G/3G resources, while later releases added LTE and 5G NR resources. The specifications are continuously updated to support new features like network slicing, edge computing, and energy efficiency. Despite the rise of YANG models in 3GPP (e.g., TS 28.541), NRM IRPs remain relevant as they provide the conceptual foundation for these models.

Purpose & Motivation

NRM IRPs exist to provide a standardized, technology-independent information model for managing network resources in multi-vendor environments. Before the IRP framework, each vendor had its own proprietary management interfaces, making it difficult for operators to integrate and manage equipment from different suppliers. The IRP framework, introduced in Release 8, solved this by defining common models and protocols for network management.

NRM IRPs specifically address the need for a clear, consistent representation of network resources. They allow management systems to discover, configure, and monitor network elements without needing to understand vendor-specific details. This reduces integration costs and enables automation. The separation of information models (NRM IRPs) from solution sets (SS IRPs) ensures that the same model can be implemented over different protocols, future-proofing the management architecture.

Over time, NRM IRPs have evolved to cover new radio technologies and network architectures. They are essential for the efficient operation of large, heterogeneous networks, and they continue to be a key part of 3GPP's management specifications, even as the industry moves towards model-driven management with YANG.

What changed in its specifications

The latest release-to-release comparison of specifications that define NRM IRP. Each summary describes the whole specification, not only this term.

TS 32.103Rel-15 → Rel-16

Rel-16 updated TS 32.103 normative references, removing 5G management specs and adding non-3GPP management specs, for 5G network slicing performance assurance.

Full comparison in TS 32.103 →
TS 32.150Rel-9 → Rel-10

Rel-10 added definitions for Managed Object and Managed Object Class and instance, and refined Solution Set definition text.

Full comparison in TS 32.150 →

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-8 Initial

Initial definition: '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: In some NRM IRP titles, for historic reasons, they are named "…network resources IRP"). An example of an NRM IRP is the Generic NRM IRP (32.621 [11], 32.622 [12], 32.623 [13], etc.).'

Definition unchanged from Rel-8; the term carried over without modification.

Reference to TS 32.101 changed from [1] to [3], and example specification numbers updated to 32.621 [95], 32.622 [96], 32.623 [97]. The core definition remained the same.

Example specification numbers updated: 32.621 [95], 32.622 [96], 32.626 [97]. No change to the core definition.

Definition unchanged from Rel-11; the term carried over without modification.

Example specification numbers updated: 32.621 [94], 32.622 [95], 32.626 [96]. No change to the core definition.

Example specification numbers changed to 28.621 [10], 28.622 [11], 28.623 [12], reflecting the renumbering of NRM IRP specifications from 32.xxx to 28.xxx. The core definition remained the same.

Definition unchanged from Rel-14; the term carried over without modification.

Definition unchanged from Rel-15; the term carried over without modification.

Minor formatting change: 'Network Resource Model' expanded in the text, and the note about historic naming was slightly rephrased. The core definition remained the same.

Definition unchanged from Rel-17; the term carried over without modification.

Definition unchanged from Rel-18; the term carried over without modification.

Defining Specifications

3GPP specifications that define or reference NRM IRP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 32.103 vj00 3GPP Management IRP Overview Rel-19 read
TS 32.150 vj00 IRP Concept and Definitions Rel-19 read