NONRTRIC (Spring Cloud) Service Gateway (Release I)
Enable Apps and the Control Panel to use A1 Services
A basic API gateway using spring cloud gateway which then exposes two Non-RT-RIC functions: A1 Policy Management Service & Information Coordinator Service.
Can add predicates through code or yaml (preferred) and in Non-RT-RIC.
A1 Policy Management Service (from ONAP CCSDK – Montreal)
A1 Policy Controller Service above A1 Adapter that provides:
Unified REST API for managing A1 Policies in all near-RT-RICs
Operations:
Query A1 Policy Types in near-RT-RICs
Create/Query/Update/Delete A1 Policy Instances in near-RT-RICs
Query Status for A1 Policy Instances
Maintains (persistent) cache of RAN’s A1 Policy information
Support RAN-wide view of A1 Policy information
Streamline A1 traffic
Enable (optional) re-synchronization after inconsistencies / near-RT-RIC restarts
Added support for multiple near-RT-RICs (& multi-version support)
Converged ONAP & O-RAN-SC A1 Adapter/Controller functions in ONAP SDNC/CCSDK
(Optionally deploy without A1 Adapter to connect direct to near-RT-RICs)
Support for different Southbound connectors per near-RT-RIC - e.g. different A1 versions, different near-RT-RIC version, different A1 adapter/controllers supports different or proprietary A1 controllers/EMSs
Repository and documentation about the service can be found at:
A service that coordinates Information Jobs, producers and consumers. Also acts as an A1 Enrichment Information Controller.
ICS is a data subscription service which decouples data producers from data consumers. A data consumer can create a data subscription (Information Job) without any knowledge of its data producers (one subscription may involve several data producers). A data producer has the ability to produce one or several types of data (Information Type). One type of data can be produced by zero to many producers.
A data consumer can be an R-App using R1 APIs, or a near-RT RIC using the A1-EI API (where the subscribed data is more specifically called "Enrichment Information"). A data consumer can have several active data subscriptions (Information Job). One Information Job consists of the type of data to produce and additional parameters, which may be different for different data types. These parameters is not defined or limited by this service and may for instance include:
Parameters related to delivery (Kafka stream, callback URL etc.). These are different for different delivery protocols.
Filtering information (scope, filter or other discriminators).
Periodicity
Other info used for aggregation
Repository and documentation about the service can be found at:
DMaaP/Kafka Information Producer Adapters (Release I)
Configurable mediators to take information from DMaaP (& Kafka) and present it as a coordinated Information Producer
Two alternative implementations to allow Information Consumers to consume DMaaP or Kafka events as coordinated Information Jobs. These configurable adapters/mediators act producers of Information Coordinator Service (ICS) jobs by polling topics in DMaaP Message Router (MR) or Kafka and pushing the messages to a consumer.
Note: DMaaP is now deprecated in ONAP, but this function is intended a generic data job/stream → DME producer adapter function.
A version implemented in Java (Spring) - Supporting filtered DMaaP and Kafka mediation:
A very simplified closed-loop rApp use case to re-establish front-haul connections between O-DUs and O-RUs if they fail. Not intended to to be 'real-world'
A very simplified closed-loop rApp use case to re-prioritize a RAN slice's radio resource allocation priority if sufficient throughput cannot be maintained. Not intended to to be 'real-world'
