Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Usage and event management BSSs can be created as applications on top of the DCAE environment as well as applications outside DCAE. These applications can collect customer events and perform mediation of the usage and events to downstream BSSs or OSSs (Operational Support Systems).  BSSs can also collect network events such as bill-impacting configuration changes, consumption or any new bill-impacting network product or service which can in turn be used for various purposes such as rating, balance management, and charge calculations. The following figure shows the DCAE architecture:



Figure 1. DCAE high-level architecture

A key subset of the DCAE architecture is the DCAE Platform.  The DCAE platform consists of the capabilities that help define how data is collected, moved, stored and analyzed within DCAE.

...

  1. The DCAE Controller is instantiated from an OpenECOMP Heat template.
  2. The DCAE Controller instantiates the rest of the DCAE components, including both infrastructure and service/application components.
  3. The DCAE Controller configures service/application components with static configurations, configuration policies fetched at run-time (for example data processing configurations or alert configurations), and any DMaap topics required for communication.

Figure 2. DCAE configuration flow (Control plane)


Figure 3 shows the DCAE data flow. This flow proceeds as follows:

  1. VNFs use REST calls to push measurement data to the DCAE VES collector.
  2. The VES collector validates, filters, and packages the received measurement data, and publishes the data to the "measurement data" topic of DMaaP.
  3. The analytics application receives measurement data from the DMaaP "measurement data" topic.
  4. The analytics application analyzes measurement data, and if alert conditions (defined by the alert policy that was installed by the DCAE Controller) are met, publishes an alert event to the DMaaP "event data" topic. 
  5. Other OpenECOMP components, for example the Policy or MSO subsystems, receive alert events from the DMaaP "event data" topic and react accordingly.

Figure 3. DCAE data flow (Data plane)