Relative Distinguished Name

Description

A Relative Distinguished Name (RDN) is a fundamental building block from the X.500 directory services standard, adopted extensively within 3GPP management specifications for structuring and identifying managed objects. In the context of 3GPP, every managed resource—such as a network function, a hardware component, or a logical entity like a network slice—is represented as a Management Object (MO) instance within a hierarchical Management Information Tree (MIT). Each MO instance is uniquely addressed by its Distinguished Name (DN), which is a sequence of RDNs concatenated from the root of the tree down to the specific MO. An RDN itself is an attribute-value assertion, typically a single key-value pair (e.g., `ManagedElementId=Gnb123`), that uniquely identifies an MO among its siblings under the same parent MO. For example, the full DN of a gNB cell might be: `DN=SubNetwork=CountryA, ManagedElement=Gnb123, GNBDUFunction=1, NRCellDU=Cell456`. Here, `NRCellDU=Cell456` is the RDN that uniquely identifies this cell within its parent `GNBDUFunction`. The hierarchical structure enforced by RDNs allows for logical grouping and efficient navigation. All 3GPP management interfaces, such as the Itf-N (northbound interface) or the management services defined for 5G, use DNs composed of RDNs as the primary reference to target specific resources for operations like create, read, update, delete, and notify. The syntax and allowed attributes for RDNs are defined in the 3GPP Management Data (MD) specifications, particularly TS 32.300, which provides the naming framework. This rigorous naming convention is critical for ensuring unambiguous communication between management systems (e.g., NMS, OSS) and network elements or between network functions in a service-based architecture, enabling precise configuration, fault correlation, and inventory tracking across a complex, multi-vendor network.

Purpose & Motivation

The adoption of the RDN/DN concept from X.500 into 3GPP management (starting in Release 8) addressed the critical need for a standardized, hierarchical, and unambiguous naming scheme for all managed objects in a telecommunications network. Prior approaches were often ad-hoc or vendor-specific, leading to inconsistencies in how network resources were identified across different management interfaces and systems. This made automated management, multi-vendor integration, and large-scale orchestration extremely difficult. The RDN-based hierarchical naming provides a natural way to model the real-world containment relationships of network resources (e.g., a network contains sub-networks, which contain managed elements, which contain functions). This structure is not just for identification; it enables powerful management operations like scoping (applying an operation to all objects under a parent) and inheritance of properties. It solves the problem of uniquely identifying millions of managed object instances in a global network while maintaining human-readable and machine-parsable names. This is essential for functions like fault management, where an alarm must precisely indicate the failing component, or configuration management, where a slice profile must be applied to a specific set of network functions. The RDN framework underpins the entire 3GPP Management Architecture, making it possible to implement automated, model-driven operations and is a prerequisite for advanced concepts like closed-loop automation and intent-based management in 5G and beyond.

Key Features

• A key-value pair (e.g., `AttributeName=Value`) that uniquely identifies an object among its siblings
• Fundamental component for constructing the hierarchical Distinguished Name (DN) of a managed object
• Enables logical modeling of containment relationships in the Management Information Tree (MIT)
• Provides unambiguous addressing for all management operations (CRUD, notifications)
• Defined by 3GPP standards to ensure consistency across all management interfaces
• Supports scoping and filtering in management service requests

Evolution Across Releases

Defining Specifications