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

Glossary term · Management

Data Definition IRP

Data Definition Integration Reference Point

Management →

Data Definition IRP is a set of 3GPP specifications that defines commonly used data definitions for integration reference points to promote reuse and consistency in network management.

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

Description

The Data Definition Integration Reference Point (IRP) is a category of 3GPP specifications that provide standardized data definitions for use in network management. Introduced in Release 8, these specifications are part of the wider IRP framework, which defines interfaces for managing network elements. The Data Definition IRP specifically focuses on defining data types, attributes, and relationships that are common across multiple management interfaces. By publishing these definitions separately, 3GPP enables other IRPs, such as Interface IRPs and Network Resource Model (NRM) IRPs, to import and reuse them, ensuring consistency and reducing duplication across specifications. The concept is described in TS 32.103 and TS 32.150, which outline the principles and provide examples.

The IRP framework itself is a cornerstone of 3GPP network management. It consists of a set of specifications that define how a network management system (NMS) can interact with network elements (NEs) for operations, administration, maintenance, and provisioning (OAM&P). An IRP typically includes a requirements specification, an information service specification, and a solution set specification (e.g., CORBA, XML, or SOAP). The Data Definition IRP is a specialized type that does not define a complete interface but rather a set of reusable data definitions. These definitions are often expressed in UML or XML schema and can be imported into other IRP specifications. For example, the State Management IRP, which defines how to manage the state of network resources, is cited as an example of a Data Definition IRP. It provides definitions for states like 'enabled', 'disabled', and 'standby', which are used by many other IRPs.

The operation of Data Definition IRPs is indirect: they do not have their own protocol or interface but are used at specification time to build other IRPs. When an Interface IRP or NRM IRP is developed, it can import the data definitions from a Data Definition IRP, ensuring that the same data types and semantics are used consistently. This import mechanism is typically realized through the use of UML packages or XML namespaces. For network operators, this means that when they implement management interfaces based on these IRPs, the data models are aligned, simplifying integration and reducing the need for custom mappings. It also facilitates the development of management tools that can work across multiple vendors and technologies.

The evolution of the Data Definition IRP shows several changes in the referenced specifications over the releases. In Rel-8, the example State Management IRP was cited with references to TS 32.671, 32.672, and 32.673. In Rel-12, the reference to 32.673 was replaced with 32.676, and in Rel-13, the numbering of the references changed slightly. A more significant change occurred in Rel-14, where the example references were updated to TS 28.624, 28.625, and 28.626. This reflects the reorganization of 3GPP specifications for 5G management, where many IRPs were renumbered under the 28 series. The definition text itself remained largely the same, emphasizing the role of Data Definition IRPs in publishing common data definitions. The stability of the definition underscores the enduring nature of the concept, even as the specific specifications evolve.

In the context of 5G and beyond, the Data Definition IRP concept continues to be relevant. With the introduction of service-based management architectures and model-driven management, the need for standardized data definitions is greater than ever. The 3GPP management framework for 5G, known as the Management Data Analytics (MDA) and the Network Resource Model (NRM) for 5G, relies heavily on reusable data definitions. The Data Definition IRP provides a mechanism to define these once and reuse them across multiple management interfaces, such as the N2, N3, and N6 interfaces, as well as the management services. This promotes interoperability and reduces the complexity of managing multi-vendor, multi-technology networks. As networks become more dynamic and automated, the role of Data Definition IRPs in ensuring semantic consistency will only grow.

Purpose & Motivation

The Data Definition IRP exists to solve the problem of data model fragmentation in network management specifications. Before its introduction, each management interface specification would define its own data types and attributes, leading to inconsistencies and duplication. For example, a 'state' attribute might be defined differently in two different IRPs, causing confusion and integration challenges for network operators and vendors. By creating a separate class of specifications dedicated to common data definitions, 3GPP ensures that fundamental concepts are defined once and reused everywhere. This reduces the effort required to develop and implement management interfaces and improves interoperability between different network elements and management systems.

Another motivation was to facilitate the evolution of network management towards more model-driven and service-oriented architectures. As networks grew more complex with the introduction of LTE and later 5G, the number of managed objects and their attributes exploded. Without a centralized repository of data definitions, the specifications would become unwieldy and prone to errors. The Data Definition IRP provides a modular approach, where common definitions can be maintained and updated independently of the interfaces that use them. This modularity also allows for faster development of new IRPs, as they can leverage existing definitions rather than reinventing them.

Historically, the concept was introduced in Release 8, a time when 3GPP was actively enhancing its management framework to support new technologies like HSPA and LTE. The IRP approach itself had been in use since earlier releases, but the formalization of Data Definition IRPs as a distinct category marked a maturation of the framework. Over the releases, the specific specifications referenced as examples have changed, reflecting the ongoing reorganization and expansion of 3GPP's management specifications. The shift from 32-series to 28-series references in Rel-14 aligns with the creation of a dedicated series for 5G management, showing how the concept adapts to new generations. Today, Data Definition IRPs are essential for the efficient and consistent management of complex, multi-vendor networks.

What changed in its specifications

The latest release-to-release comparison of specifications that define Data Definition 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 introduced: '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. An example of a Data Definition IRP is the State Management IRP (32.671 [14], 32.672 [15], 32.673 [16], etc).' This established the concept and provided an example.

Definition carried over unchanged from Rel-8, with the same wording and references.

Definition carried over unchanged from Rel-9, but the reference numbers in the example were updated to [109], [110], [111].

Definition carried over unchanged from Rel-10, with no changes to the wording or references.

Definition carried over unchanged from Rel-11, but the example reference to 32.673 was replaced with 32.676.

Definition carried over unchanged from Rel-12, with minor changes to reference numbers (e.g., 32.671 [102], 32.672 [103], 32.676 [103]).

Wording changed: the example references were updated to '28.624 [4], 28.625 [5], 28.626 [6]', reflecting the reorganization of 3GPP management specifications under the 28 series. The core definition remained the same.

Definition carried over unchanged from Rel-14, with the same wording and references.

Definition carried over unchanged from Rel-15, with no changes.

Definition carried over unchanged from Rel-16, with the same wording and references.

Definition carried over unchanged from Rel-17, with no changes.

Definition carried over unchanged from Rel-18, with the same wording and references.

Defining Specifications

3GPP specifications that define or reference Data Definition 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