Page Comparison

...

• controller : Optional A1 Controller configuration, e.g. an SDNC instance (with A1-Adapter)
  • name : for use later in the configuration
  • baseUrl : the URL of the A1 controller (e.g. SDNC + A1 Adapter)
  • userName & password : to configure security parameters to access to the controller
  • The A1 Policy Management service can entirely by-pass the A1-Controller (SDNC + A1 Adapter) if desired - it is optional to access the near-RT-RIC through an A1-Controller.
    In the configuration the "controller" property is optional in the "ric" objects (below)
    If all configured rics bypass the A1-Controller (do not have "controller" values) then the "controller" object at the top of the configuration can be omitted.
    If all configured rics bypass the A1-Controller there is no need to start an A1-Controller.
    There is no functional gain in accessing the near-RT-RIC through an A1-Controller.
• ric : One entry for each near-RT-RIC, which includes:
  • name : a friendly name to refer to the near-RT-RIC
  • baseUrl : The base URL of the A1 interface endpoint in the near-RT-RIC.
  • managedElementIds : A optional list of identifiers that near-RT-RIC is using. An application can query the A1 Policy Management Service to retrieve "RIC" instance associated with these identiefiers. (e.g. cells, sectors, locations, etc.) .
  • controller : An optional reference to the controller to use, or excluded if the near-RT-RIC can be accessed directly from this A1 Policy Management Service.
  • customAdapterClass:
    • An optional java class name to be used for the southbound interface towards the near-RT-RIC. If this is not given the PMS will automatically discover the A1-P API version supported by the near-RT-RIC.
This parameter can be used for explicitly defining a class to be used. See the example below using the "customAdapterClass" property. The class used has to be in the class path of the built container.
This means that the A1-PMS can be extended to support any protocol towards the near-RT-RIC without changing its implementation.
On how to implement such an adapter class, see the source code and the actual class referred to in the configuration example below.
• DMaaP configuration: Optional. Used if the A1 Policy Management Service is configured to send/receive API calls over a DMaaP topic:
  • streams_subscribes : Information on the DMaaP topic to receive API requests
  • streams_publishes : Information on the DMaaP topic to publish API responses
  • Note: Support for accessing the service using DMaaP is deprecated, and will be removed in future versions.

For details about the syntax of the file, there is an example in source code repository /config/application_configuration.json (london). This file is also included in the docker container /opt/app/policy-agent/data/application_configuration.json_example.

...