Reference Data Model

Description

The Reference Data Model (RDM) in 3GPP is a comprehensive, technology-neutral information framework that defines the managed objects, their attributes, relationships, and behaviors for telecommunications network management. It serves as the canonical blueprint for all 3GPP-defined Management Data (MD) across various network domains, including 5G Core, NG-RAN, and IMS. The RDM is specified using a Unified Modeling Language (UML) class diagram methodology, which is then translated into concrete implementations such as YANG data models for NETCONF/YANG-based management or Structure of Management Information (SMI) for SNMP. The model is organized hierarchically, starting from high-level network functions and services down to physical and logical components like gNBs, AMFs, slices, and PDU sessions. Each managed object class in the RDM has defined attributes (e.g., administrative state, operational state), notifications (for fault and performance events), and actions (operations that can be invoked). The RDM covers key management areas: Fault Management (alarms, fault supervision), Configuration Management (provisioning, software management), Performance Management (counters, measurements), and Inventory Management. For example, the RDM for a gNB would define objects representing its cells, carrier frequencies, beamforming configurations, and associated KPIs. Management systems, such as Network Management Systems (NMS) or Element Management Systems (EMS), interact with network elements using protocols like NETCONF, which carry instantiations of the RDM's YANG-derived data. This ensures that a manager from vendor A can configure and monitor a network element from vendor B because both adhere to the same RDM definitions. The RDM is continuously extended to support new 3GPP features like network slicing, edge computing, and non-terrestrial networks, ensuring management capabilities evolve with the network architecture.

Purpose & Motivation

The RDM was created to solve critical interoperability and integration challenges in multi-vendor telecommunications networks. Before its standardization, each equipment vendor used proprietary data models for their network element management, forcing operators to develop complex, vendor-specific integrations for their OSS/BSS systems. This resulted in high operational costs, long deployment cycles for new services, and vendor lock-in. The 3GPP RDM, initiated in Release 10, provided a common language for management information, enabling true multi-vendor plug-and-play operation. It allows operators to automate network lifecycle management—from provisioning and commissioning to assurance and optimization—using standardized interfaces and data structures. This is especially vital for modern networks like 5G, which are software-driven, cloud-native, and support dynamic features such as network slicing that require rapid, programmable configuration changes across domains. The RDM also facilitates the adoption of modern, model-driven management paradigms like Software-Defined Networking (SDN) and Network Function Virtualization (NFV), where the data model is the central contract between the controller and the network elements. By providing a single source of truth for management semantics, the RDM reduces errors, accelerates service deployment, and forms the backbone for autonomous networks and intent-based management in future releases.

Key Features

• Technology-neutral UML-based hierarchical model defining managed objects and their relationships
• Covers Fault, Configuration, Performance, and Inventory (FCPI) management areas
• Enables multi-vendor interoperability for network management interfaces
• Serves as the source for deriving concrete implementation data models (e.g., YANG, SMI)
• Extensible to support new network functions and services like network slicing
• Facilitates automated, model-driven network management and orchestration

Evolution Across Releases

Defining Specifications