Versions Compared

Key

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

DRAFT

Table of Contents
maxLevel3

Summary

Tasks / Backlog / JIRA

Wiki: https://wiki.o-ran-sc.org/display/RICNR

Latest Architecture: (See below)

Components: Release J Components

Release J -

Headline Goals
  • Continue working on rApp manager service
    • Aim to have a fully functional service, and several sample rApps
  • Continue working on Service Manager service
    • Aim to have a first-release stable Service Exposure Manager function
    • Aim for O-RAN R1-SME spec compliance
  • Consider which older functions to deprecate. (Resource prioritization)
    • Invite community participation & help
  • Improvements in Function Test environments
    • Support latest releases, and expand set of use cases tested
  • Continue improvements for A1-

    Highlights

    • Major improvements in new rApp Manager
      • Includes several sample/starter rApps
      • Fully functional rApp repository & life-cycle manager
    • Major improvements in new Service Manager
    • Improvements in Function Test environments
      • Supports latest releases, and expand set of use cases tested
    • Continued improvements for A1-Policy functions (ONAP CCSDK)
      • Investigate emerging Added new O-RAN R1-A1 specifications & Introduce new compliant A1-Policy-Management northbound API (A1-PMS-v3 NBI
      • Full alignment with OSC Near-RT-A1-Mediator
      Maintain
      • )
      • Added tracing support for all northbound (R1) and southbound (A1) interfaces
    • Maintained & support existing NONRTRIC functions & service - best effort Assist with (See below)
    • Updates to OSC Integrated SMO deployment scripts & charts
    • Improvements in stability, 3PP vulnerability, test coverage & quality
    • Continued engagement with O-RAN Alliance working groups for standardization alignment

    Release J - Tasks

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

    • Jira Legacy
      serverSystem Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
      keyNONRTRIC-571
    • Jira Legacy
      serverSystem Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
      keyNONRTRIC-648
    • Jira Legacy
      serverSystem Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
      keyNONRTRIC-670
    • Jira Legacy
      serverSystem Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
      keyNONRTRIC-725
    • Jira Legacy
      serverSystem Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
      keyNONRTRIC-753
    • Jira Legacy
      serverSystem Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
      keyNONRTRIC-788
    • Jira Legacy
      serverSystem Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
      keyNONRTRIC-799
    • Jira Legacy
      serverSystem Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
      keyNONRTRIC-818
    • Jira Legacy
      serverSystem Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
      keyNONRTRIC-825
    • Jira Legacy
      serverSystem Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
      keyNONRTRIC-846
    • Jira Legacy
      serverSystem Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
      keyNONRTRIC-896
    • Jira Legacy
      serverSystem Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
      keyNONRTRIC-970944
    • Jira Legacy
      serverSystem Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
      keyNONRTRIC-971970
    • Jira Legacy
      serverSystem Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
      keyNONRTRIC-972971
    • Jira Legacy
      serverSystem Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
      keyNONRTRIC-973972
    • Jira Legacy
      serverSystem Jira
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId3122c0e4-6090-3a7d-9725-8b5a32a8eaeb
      keyNONRTRIC-973

    Wiki: https://jira.lf-o-ran-sc.org/projects/NONRTRIC/issues atlassian.net/wiki/display/RICNR/

    Latest Architecture: Release J Architecture

    Components: Release J Components

    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 J - Studies

    Child pages (Children Display)
    alltrue
    depth1
    pageRICNR:Release J: Technical spikes

    Release J - Demos

    • ToDo(in progress)

    Release J - Container images

    Release J - Deployment Instructions

    ToDo

    Latest Architecture (Release J)
    Anchor
    ArchitectureReleaseJ
    ArchitectureReleaseJ

    ...


    Image Added

    Image Removed

    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

    ...

    Information Coordinator Service (ICS) (Release J)

    ...

    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.) 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 Java (Spring) Go - Supporting filtered DMaaP and Kafka mediation:

    ...

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

    CAPIF Service Registry (Release J)

    ...

    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:

    A1 Policy Controller / Adapter (from ONAP CCSDK –

    ...

    New Delhi)

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

    ...

    Information about the test platform can be found at:

    Use Cases

    "Helloworld" O-RU Fronthaul Recovery use case

    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:

    Repository and documentation about the service 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:

    Repository and documentation about the service 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

    ...