2 OCNADD Architecture

Oracle Communications Network Analytics Data Director (OCNADD) is a cloud native application. The application consists of different microservices with the following components running on separate namespaces in the cloud native environment:

OCNADD Architecture

Figure 2-1 OCNADD Architecture


OCNADD Architecture Diagram

OCNADD Centralized Deployment Architecture

Figure 2-2 OCNADD Centralized Deployment Architecture


OCNADD Centralized Deployment Architecture

Components of the OCNADD Architecture

OCNADD consists of:
  • Kubernetes cluster hosting Docker containers
  • Optional cloud native environment services to support operations of OCNADD
  • OCNADD Microservices:

    • Aggregation Service: This service collects data from various sources and provides it to the third-party consumer applications. It summarizes a large pool of data for analysis.

    • Consumer Adapter: This service allows the OCNADD to send data to third-party consumers. It ensures message durability in case Consumer Adapter or third-party consumer application fails.

    • Configuration Service: Third party consumers use this service to configure the OCNADD for data aggregation, filtering, and traffic load distribution rules through the console. It provides a subscription interface to all the other OCNADD services for the consumer feed. This service provides configuration recovery in case of other OCNADD services fail over or restart. It also maintains the configuration database for the OCNADD.

    • Alarm Service: This service maintains an alarm database to store the alarms generated by OCNADD microservices. It provides an interface, which can be used by other OCNADD services like the Dashboard service for alarms, to retrieve the raised alarms.

    • Health Monitoring Service: This service monitors the health of all the services that are managing the front-end and back-end engine for OCNADD. It generates health metrics and raises alerts if any of the registered device fails.

    • CNC Console: OCNADD uses the Oracle Communications Cloud Native Configuration Console interface to configure and monitor the message feeds.

    • UI Router Service: This is a gateway service that forwards all the Graphical User Interface (GUI) requests to other OCNADD services, such as Configuration service, Health Monitoring service, Alarm service, and so on.

    • Kafka Service: The OCNADD supports the external Kafka consumer applications using the external Kafka Feeds. This service enables the third-party consumer application to consume directly from the Data Director Kafka topic without the need for any egress adapter.
    • Admin Service: The Admin service provide functionality of Kafka management and dynamic deployment of OCNADD services like consumer adapter and correlation services.
    • Filter Service: This service adds filtering on both ingress and egress side, which OCNADD uses to perform data filtering on messages and send only the filtered messages to the next hop or feed.
    • Correlation Service: This service provides the capability to correlate messages within a network scenario, represented by a transaction, call, or session, and generate a summary record known as xDR.
    • Ingress Adapter Service: This service enables data processing from various third-party Network Functions (NFs). It receives data in HTTP/2 format with predefined custom headers from these NFs, then transforms the data into a format compatible with Data Director.
    • Storage Adapter Service: This service enables the persistence of xDR (eXtended Detail Records) records, along with PDUs (Protocol Data Units), in the OCNADD database.
    • Export Service: This service allows OCNADD to export xDR records to NFs or external file storage in CSV or PCAP format.