Versions Compared

Key

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

...

  • Data is collected from the network using appropriate interfaces and is published to DMaaP. Such data can be performance (PM) counters, KPIs, alarms, etc.
  • Network data is consumed by SON algorithmic-logic micro-services that may be either part of DCAE, thereby managed by the DCAE controller, or part of other analytics frameworks that have access to DMaaP.
  • SON analytical logic analyses the network data. Such logic may be implemented within a single micro-services, or may leverage communication between multiple micro-services. The result of the SON logic is published to DMaaP for consumption by other ONAP components – primarily the ONAP Policy platform.
  • The Policy platform will obtain and assess the SON algorithmic output, in order to make a decision on what actions will need to be performed to network elements towards achieving the optimization goal. Such actions may be decided exclusively by Policy, or may be recommended by the SON algorithm as part of its output.
  • The Policy platform will convey its decision to the radio SDN controller, which will further apply the action(s) to the appropriate network element(s).

Comment (Oskar M.) There is no radio SDN controller in the ONAP architecture. Could re-use execution framework requirement stated below: initiate radio access network change using SO and / or controllers.

  • Upon applying the action, the SON logic will analyze post-action network data to determine (in conjunction with Policy) whether subsequent actions need to be applied in order to achieve the optimization objective.

...

This ONAP use case enables automated lifecycle management of large scale disaggregated 5G radio access networks and E2E network slices.  It also enables the deployment and life cycle management of hybrid 5G networks (a combination of PNFs and VNFs)

...

Comment (Oskar M.) I think this description is related to the other sub cases (A and B)?