Repository Access Function

Description

The Repository Access Function (RAF) is a component within the 3GPP Telecommunications Management Network (TMN) and later Network Management (NM) framework, defined in the Management and Orchestration (MANO) related specifications. It acts as a standardized interface and functional block that provides access to a repository or database storing management-related information. This information can include Network Resource Models (NRM), performance measurement (PM) data, fault management (FM) records, configuration management (CM) data, and other operational data necessary for the administration of the network. The RAF essentially abstracts the underlying data storage, offering a consistent access method for other management functions like the Network Management (NM), Domain Management (DM), or Element Management (EM) systems.

Architecturally, the RAF is often positioned as part of the Management Data Repository (MDR) or an integrated function within an Operations Support System (OSS). It works by exposing northbound interfaces, typically based on protocols like CORBA, SNMP, or more recently, RESTful APIs as defined in 3GPP specifications (e.g., for the Network Resource Model - NRM). Key components include the interface definitions (Irp), the data models (Information Service - IS), and the actual repository storage backend. When a management system needs to retrieve historical performance data or a specific configuration snapshot, it sends a request to the RAF. The RAF then queries its repository, applies any necessary filtering or aggregation, and returns the results in a standardized format.

Its role is critical for network automation, assurance, and analytics. By centralizing management data access, the RAF prevents siloed data storage across different network elements or management domains. It supports functions like performance trend analysis, root cause analysis for faults, audit trails for configuration changes, and compliance reporting. Specifications such as TS 32.808 detail the requirements and solutions for the RAF, ensuring that different vendors' management systems can interoperate with a shared repository, facilitating multi-vendor network management.

Purpose & Motivation

The RAF was created to address the growing complexity of managing multi-vendor, multi-technology cellular networks. Early network management often involved proprietary element managers directly accessing network elements, leading to data silos, inconsistent interfaces, and difficulties in performing cross-domain analysis. The RAF, as part of the 3GPP's standardized management architecture, provides a unified point of access to consolidated management data.

This solves several key problems: it decouples data storage from data consumers (allowing different OSS applications to use the same data), it standardizes the way management information is retrieved (improving interoperability), and it enables efficient data sharing for complex operations like service assurance and capacity planning. Historically, its development was motivated by the need for more automated, efficient OSS systems as networks evolved from 2G/3G to 4G and 5G, where the volume and variety of management data increased exponentially. The RAF provides the foundational data layer for modern, data-driven network operations.

Key Features

• Provides standardized access to a management data repository (MDR)
• Stores and retrieves Network Resource Model (NRM), Performance Measurement (PM), and Fault Management (FM) data
• Defines northbound interfaces (e.g., CORBA, RESTful) for OSS integration
• Supports data filtering, aggregation, and historical querying
• Enables centralized data storage for multi-vendor network management
• Facilitates network automation and analytics by serving as a consistent data source

Evolution Across Releases

Defining Specifications