1 Introduction
This chapter provides information about installing Oracle Communications Network Analytics Data Director (OCNADD) and its microservices on the supported platforms.
Caution:
User, computer and applications, and character encoding settings may cause an issue when copy-pasting commands or any content from PDF. PDF reader version also affects the copy-pasting functionality. It is recommended to verify the pasted content especially when hyphens or any special characters are part of copied content.1.1 Overview
With the emergence of 5G networks, Communication Service Providers (CSPs) now have access to vast amounts of data. Oracle Communications Network Analytics Data Director (OCNADD) serves as a specialized Network Data Broker (NDB) within the 5G Network Architecture. It collects network traffic data from various sources such as 5G network functions (NFs), non-5G NFs, and third-party producers. OCNADD then performs a range of rule-based operations to help CSPs maximize the value of this data. These operations include data aggregation, data filtering, data replication, data governance, and secure data transmission for subscribed third-party consumers.
By efficiently collecting and utilizing data, OCNADD provides CSPs with the following advantages:
- Enhanced service quality
- Ease of scalability
- Simplified monitoring and troubleshooting
- Identification of new revenue and network monetization opportunities
- Reduced network downtime
As an NDB, OCNADD sits between the 5G infrastructure and third-party tools or consumer applications. Its primary function is to ensure data security, low latency, and redundancy while efficiently collecting and processing data. By correlating and transforming acquired data based on configurable data feed settings, OCNADD enables CSPs to generate comprehensive dashboards and Key Performance Indicators (KPIs). These insights provide a deep understanding of all functions within the 5G Network Architecture, allowing CSPs to improve service quality, reduce downtime, support network scalability, and minimize losses.
In the event of network failures, OCNADD data is used for monitoring and troubleshooting. Additionally, OCNADD offers a user-friendly GUI that supports the creation, editing, and deletion of data feeds. For more information about OCNADD architecture and features, see the Oracle Communications Network Analytics Data Director User Guide.
Deployment Overview
OCNADD deployment models help customers optimize or reduce the Data Director footprint based on the third-party consumer’s capability to consume data directly from the Kafka cluster. Users can deploy different Data Director models by configuring the applicable custom values.
The OCNADD deployment consists of the following groups:
OCNADD Management Group:
The OCNADD Management Group serves as the central hub for configuration management, health monitoring, and alarm handling across all OCNADD services. It is also responsible for managing export and tracing for critical transactions within Data Director, ensuring comprehensive visibility and control.
OCNADD Worker Group:
The OCNADD Worker Group is a logical entity divided into two sub-groups:
- OCNADD Relay Agent Group: Responsible for receiving data from source Network Functions (NFs) and performing essential operations, including data aggregation, non-transaction-based filtering, message sequencing, and metadata enrichment.
- OCNADD Mediation Group: Receives processed data from the associated Relay Agent and applies further processing, including transaction-based filtering, correlation, storing XDRs in supported formats to centralized data stores, and forwarding data to third-party probes.
Both the Relay Agent Group and the Mediation Group can be linked to a worker group, which is configurable through Helm charts. Within this worker group, the Mediation service can be associated with a specific Relay Agent. To establish this association, update the Mediation values file with the namespace and cluster details of the Relay Agent using Helm charts.
For more details, refer to the OCNADD Deployment Models section to understand the available deployment models and determine the required resources before proceeding with installation.
1.2 References
For more information on OCNADD, refer to the following documents:
- Oracle Communications Network Analytics Suite Release Notes
- Oracle Communications Network Analytics Suite Licensing Information User Manual
- Oracle Communications Network Analytics Automated Testing Suite Guide
- Oracle Communications Network Analytics Suite Security Guide
- Oracle Communications Network Analytics Data Director User Guide
- Oracle Communications Network Analytics Data Director Outbound Interface Specification Guide
- Oracle Communications Network Analytics Data Director Benchmarking Guide
- Oracle Communications Network Analytics Data Director Diameter User Guide
- Oracle Communications Network Analytics Data Director vCollector Installation Guide
- Oracle Communications Network Analytics Data Director Troubleshooting Guide
- Oracle Communications Cloud Native Core, cnDBTier Installation,Upgrade, and Fault Recovery Guide
- Oracle Communications Cloud Native Configuration Console Installation, Upgrade, and Fault Recovery Guide
- Oracle Communications Cloud Native Core, OCI Deployment Guide
- Oracle Communication Certificate Manager Installation, Upgrade and Fault Recovery Guide
- Oracle Communication Certificate Manager User Guide
1.3 Oracle Error Correction Policy
The table below outlines the key details for the current and past releases, their General Availability (GA) dates, and the end dates for the Error Correction Grace Period.
Table 1-1 Oracle Error Correction Policy
| Release Number | General Availability (GA) Date | Error Correction Grace Period End Date |
|---|---|---|
| 25.2.200 | December 2025 | December 2026 |
| 25.2.100 | September 2025 | September 2026 |
| 25.1.200 | July 2025 | July 2026 |
| 25.1.100 | February 2025 | February 2026 |
Note:
- For the latest patch releases, see their corresponding Oracle Communications Cloud Native Core Release Notes.
- For a release, Sev1 and Critical Patch Unit (CPU) patches are supported for 12 months. For more information, see the Oracle Communications Cloud Native Core and Network Analytics Error Correction Policy.
1.4 Oracle Open Source Support Policies
Oracle Communications Cloud Native Core uses open source technology governed by the Oracle Open Source Support Policies. For more information, see Oracle Open Source Support Policies.