Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

Summary

Release K - Highlights

  • Still in progress

Release K - Tasks

Count of Epics (20 issues), User Stories, Tasks, and Issues:  (455 issues)
Relevant Epics:

  • In progress

Wiki: https://lf-o-ran-sc.atlassian.net/wiki/display/RICNR/

Tasks / Backlog / JIRA: https://jira.o-ran-sc.org/projects/NONRTRIC/issues

Weekly Meetings: Meetings

Gerrit / Source Code

Sonar / Test Coverage Reports

Docs

Testing

Release K - Studies


Release K - Demos

  • (in progress)

Release K - Container images

  • Still in progress

Release K Deployment Instructions

Latest Architecture (Release K)

  • Still in progress


NONRTRIC Components (Release K)

  • 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

NONRTRIC Control Panel (Release K)

Graphical user interface to interact with the Non-RT-RIC services.

With the OSC NONRTRIC Control Panel you can: 

  • View and Manage A1 policies in the RAN (near-RT-RICs)
  • Graphical A1 policy creation/editing is model-driven, based on policy type’s JSON schema
  • View and manage producers and jobs for the Information Coordination Service
  • Configure A1 Policy Management Service (add/remove near-rt-rics)
  • Interacts with the A1-Policy Management Service & Information Coordination Service (REST NBIs) via Service Exposure gateway

 Implementation & Documentation:

NONRTRIC (Spring Cloud) Service Gateway (Release K)

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.

Implementation & Documentation:

NONRTRIC (Kong) Service API Gateway (Release K)

Support Apps to use NONRTRIC, SMO and other App interfaces through a gateway

  • 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 – Oslo)

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

Repository and documentation about the service can be found at:

rApp Manager (Release K)

A service to support onboarding, instantiation and life-cycle management of composite rApps.

  • Preliminary composite rApp package
  • Demonstrate controlled LCM of composite rApps with & without µServices
    • ONAP ACM Models & Manager
    • Demonstrate extensible ACM ‘Participant’ approach as types of rApp constituents appear
  • Integration with DME for managing Data Inputs & Outputs
    • incl.: registration, discovery, access control (in&out)
  • Integration with SME for managing Service Inputs & Outputs
    • Incl.: gateway setup, registration, discovery, access control (in&out), service mesh config

Repository and documentation about the service can be found at:

Information Coordinator Service (ICS) (Release K)

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 K)

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 version implemented in Go - Supporting DMaaP mediation:

Service Manager (Release K)

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

Repository and documentation about the service can be found at:

CAPIF Service Registry (Release K)

Implementing a CAPIF service for Service registration, discovery, administration (SME)

Repository and documentation about the service can be found at:

NONRTRIC rApp catalog (Release K)

Register for NONRTRIC APPs (rApps)

  • 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:

A1 Policy Controller / Adapter (from ONAP CCSDK – Oslo)

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

  • Implemented as CCSDK OSGI Feature/Bundles
  • A1 REST southbound
  • RESTCONF Northbound
  • NETCONF YANG > RESTCONF adapter
  • Mapping logic / Provider
  • Can be included in an any controller based on ONAP CCSDK

Documentation about the adapter / controller can be found at:

A1 Interface Simulator (Release K)

Stateful extensible A1 test stub

  • Used to create multiple stateful A1 providers (simulated near-rt-rics)
  • Supports A1-Policy (A1-P) and A1-Enrichment Information (A1-EI)
  • Implemented as a Python application
  • Swagger-based northbound interface, so easy to change the A1 profile exposed (e.g. A1 version, A1 Policy Types, A1-EI consumers, etc)
  • All A1-AP versions supported

  • Call-out feature to add applications-specific A1-Policy behaviors (REST & Kafka call-outs supported)

Repository and documentation about the service can be found at:

RAN Performance Monitoring Functions (File-based PM) (Release K)

Functions to collect/parse/filter/store/forward file-based & event-based RAN PM data

  • End-to-end tool-chain to collection, parsing, filtering and delivery of file-based RAN PM observability data.
  • PM report data format defined by 3GPP (TS 32.432 and 3GPP TS 32.435)
  • High performance, fully scalable
  • Subscribers (e.g. rApps) can subscribe for chosen measurement types from specific resources in the network

Repository and documentation about the service can be found at:

RAN PM: PM Data File Collector

RAN PM: PM File Converter 

RAN PM: PM Producer

RAN PM: InfluxDB PM Logger

Authentication Support (JWT Token Fetch) (Release K)

A side-car utility service to takes care of authentication token fetching from Keycloak

  • Simplifies authentication in for services

Repository and documentation about the service can be found at:

Initial K8S Helm Chart LCM Manager (Release K)

Onboard, start, stop, and modify Non-RT-RIC App µServices as Helm Charts

A building block for coming releases as the rApp concept matures

  • Interfaces that accepts Non-RT-RIC App µServices Helm Charts
  • Support basic LCM operations
  • Onboard, Start, Stop, Modify, Monitor
  • Initial version co-developed with v. similar functions in ONAP
  • Limited functionality/integration for now

Repository and documentation about the service can be found at:

NONRTRIC Test Platform (Release K)

Information about the test platform can be found at:

Use Cases

  • Note: New rApps will replace with old use case implementations in this & next next releases







  • No labels