Latest Architecture (Release J)

Anchor

...

ArchitectureReleaseJ

...

ArchitectureReleaseJ

DRAFT

Image RemovedImage Added

NONRTRIC Components (Release J)

Anchor

...

ComponentsReleaseJ

...

ComponentsReleaseJ

DRAFT

• Non-RT-RIC Control Panel

• Non-RT-RIC (Spring Cloud) Service Gateway

• Non-RT-RIC (Kong) Service Exposure Prototyping

• A1 Policy Management Service

• rApp Manager

• Information Coordinator Service

• DMaaP/Kafka Information Producer Adapters

• Service Manager

• NONRTRIC CAPIF Core (Service Registry)

• Initial Non-RT-RIC App Catalogue

• A1 Policy Controller / Adapter

• A1 Interface Simulator

• RAN PM functions

• Initial K8S Helm Chart LCM Manager

• Authentication Support (JWT Token Fetch)

• Test Framework

• "Helloworld" O-RU Fronthaul Recovery use case

• "Helloworld" O-DU Slice Assurance use case

• "Healthcheck" use case

...

• Support dynamic registration and exposure of service interfaces to Non-RT-RIC applications (& NONRTRIC Control panel)
• Extends a static gateway function specifically for NONRTRIC Control panel
• Initial version based on Kong gateway function
• Initial exposure candidates include A1 (NONRTRIC) services & O1 (OAM/SMO) services

A1 Policy Management Service (from ONAP CCSDK

...

– New-Delhi)

A1 Policy Controller Service above A1 Adapter that provides:

• Unified REST API for managing A1 Policies in all near-RT-RICs
  • Implements O-RAN R1-AP specification for A1-Policy Management
• 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

...

• https://gerrit.o-ran-sc.org/r/admin/repos/nonrtric/plt/rappmanager
• https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-plt-rappmanager
• Release J: rApp Manager

Information Coordinator Service (ICS) (Release J)

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.

Image Removed

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

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.

Image Added

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:

• https://gerrit.o-ran-sc.org/r/admin/repos/nonrtric/plt/informationcoordinatorservice
• https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-plt-informationcoordinatorservice

DMaaP/Kafka Information Producer Adapters (Release J)

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 mediationRepository and documentation about the service can be found at:

• https://gerrit.o-ran-sc.org/r/admin/repos/nonrtric/plt/informationcoordinatorservicedmaapadapter
• Release J - Run in Docker
• https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-plt-informationcoordinatorservice

DMaaP/Kafka Information Producer Adapters (Release J)

Configurable mediators to take information from DMaaP (& Kafka) and present it as a coordinated Information Producer

...

• dmaapadapter
• Includes additional support for PM data filtering/delivery

A version implemented in Java (Spring) Go - Supporting filtered DMaaP and Kafka mediation:

• https://gerrit.o-ran-sc.org/r/admin/repos/nonrtric/plt/dmaapadapterdmaapmediatorproducer
• Release J - Run in Docker
• https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-plt-dmaapadapter
• Includes additional support for PM data filtering/delivery
• dmaapmediatorproducer

Service Manager (Release J)

Provides a solution to register & Discover services. Includes automatic Service Exposure Gateway for registered services.

Repository and documentation about the service can be found atA version implemented in Go - Supporting DMaaP mediation:

• https://gerrit.o-ran-sc.org/r/admin/repos/nonrtric/plt/dmaapmediatorproducerRelease J - Run in Dockersme
• https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-plt-dmaapmediatorproducer-plt-sme
• https://gerrit.o-ran-sc.org/r/gitweb?p=nonrtric/plt/sme.git;a=blob;f=servicemanager/README.md
• Service Manager

CAPIF Service Registry (Release J)

...

• https://gerrit.o-ran-sc.org/r/admin/repos/nonrtric/plt/sme
• https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-plt-sme
• https://gerrit.o-ran-sc.org/r/gitweb?p=nonrtric/plt/sme.git;a=blobtree;f=README.md capifcore
• CAPIF Study

NONRTRIC rApp catalog (Release J)

...

• rApps can be registered / queried
• This function will be merged into our new rApp Manager function in coming releases.

Repository and documentation about the service can be found at:

• https://gerrit.o-ran-sc.org/r/admin/repos/nonrtric/plt/rappcatalogue
• https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric-plt-rappcatalogue

A1 Policy Controller / Adapter (from ONAP CCSDK –

...

New Delhi)

Optional mediation point for A1 Policy interface termination in SMO/NONRTRIC

...

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'

Note: A new rApp will replace with old implementation in the next release

Information about the use case can be found at:

...

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'

Note: A new rApp will replace with old implementation in the next release

Information about the use case can be found at:

...

A very simplified rApp use case to check if A1 Policy connection to a near-rt-ric exists & is healthy. Not intended to to be 'real-world'

Note: A new rApp will replace with old implementation in the next release

• https://gerrit.o-ran-sc.org/r/q/project:nonrtric/rapp/healthcheck
• https://gerrit.o-ran-sc.org/r/gitweb?p=nonrtric/rapp/healthcheck.git;a=blob;f=README.md

...