Versions Compared

Key

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

Architecture for London Release

...

:



A1 Policy components (subset of 'Non-RealTime RIC'):

  • A1 Policy Management Service (In ONAP CCSDK/SDNC)
  • SDNC A1 Adapter (In ONAP CCSDK/SDNC)
  • Near-RT RIC / A1 Simulator (in O-RAN Source Community (OSC)) (Wiki)
  • A1 Policy Management GUI / NONRTRIC Dashboard (in O-RAN Source Community (OSC)) (Wiki)

Source code & Documentation

...

  • london' branch)

...

...

  • Jira
    serverONAP Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyREQ-1391

  • Jira
    serverONAP Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCCSDK-3809

ONAP A1 Policy Management Service (ONAP

...

CCSDK)

The Policy Management Service is a micro service which maintains a transient repository of:

  • All A1 policies instances in the network. Each policy is targeted to a near-RT-RIC instance and is owned by a 'service' (R-APP or the NONRTRIC Dashboard).
  • All near-RT-RICs in the network. This information can be maintained using the ONAP CDS database (which is using the Cloudify Consul database) or using a plain text file.
  • All Policy types supported by each near-RT-RIC.

The service provides :

  • Unified REST API for managing A1 Policies in all near-RT-RICs.A DMaaP API for A1 Policy management (Deprecated).
  • Synchronized view of A1 Policy instances for each R-APPrAPP
  • Synchronized view of A1 Policy instances in each near-RT-RIC
  • Synchronized view of A1 Policy types supported by each near-RT-RIC
  • Lookup service to find the near-RT-RIC to control resources in the RAN as defined in  O1 (e.g. which near-RT-RIC should be accessed to control a certain CU or DU, which in turn controls a certain cell).
  • Monitors all near-RT-RICs and maintains data consistency  – e.g. recovery from near-RT-RIC restarts
  • Support for different Southbound APIs  to the near-RT-RICs (different versions of the A1-P and other similar APIs).
  • HTTPS can be configured to use a supplied certificate/private key and to validate peers towards a list of trusted CAs/certs.
  • HTTP proxy support for tunneling HTTP/HTTPS connections.
  • Fine-grained access-control

The REST API can be found at

ONAP A1 Adapter (part of ONAP CCSDK/SDNC):

...

  • Used to create multiple stateful A1 providers (simulated near-RT-RICs)
  • Implemented as a Java Springboot application
  • Swagger-based northbound interface, so easy to change the A1 profile exposed
  • Supports plugable type-specific behaviors
  • Please refer to the OSC A1 Simulator Documentation (Latest)