Versions Compared

Old Version 5

changes.mady.by.user John Keeney

Saved on

compared with

New Version Current

changes.mady.by.user John Keeney

Saved on

Key

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

Table of Contents
maxLevel3

Summary

key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

Release H - Highlights

  • Consolidated & Improved RAN PM data exposure in new repo for RAN PM functions
    • Adds 4 new services for RAN PM processing
    • Lots of work on deployment scripts/charts, testing, CI, and documentation
  • (R1) Service Exposure & Management (SME)
    • CAPIF Aligned Service Registry & Discovery
    • Continued

Primary Goals for Non-RealTime RAN Intelligent Controller (Non-RT-RIC) - Release H

  • R1 Service Exposure & Management
    • Continuing work of Service execution platform extensions (K8s, Istio, Keycloak, OPA, Gateway) to enable and enforce service isolation & exposure
    • First version of 3GPP CAPIF-aligned Service Registration & Discovery service available. Will continue integration with related work on rApp management & Service exposure enforcement.
    • Controlled access & exposure of service to/from rApps
  • (R1) R1 Data Management & Exposure
    • Aligning with emerging proposals for R1-DME where possible
    • R1 DME Data Catalog support in NONRTRIC ICS 
    • R1 Data delivery & filtering (Kafka & REST)
      • Investigating approaches for access to stored data
    • Continuing prototyping with PM data exposure, filtering & access control
      • Additional support for stored data access (S3/Minio & InfluxDB) .
    (DME)
    • Small updates to Information Coordination Service – studying alignment with R1 proposals
    • File-based PM data → Kafka/InfluxDB/Minio
      • Including parsing, filtering & delivery
      • ref. PM Data exposure above
  • rApp Management
    • Started work on a new rApp Manager functions – more in next release
    • LCM for rApps:
    rApp Manager
    • Building on ONAP “Automation Composition” model & platform to implement rApp use cases
      • Added a 'KServe Participant’
        • Inference Services in rApps
        • Now supports KServe-based AI/ML rApps
      • Added an ‘A1 Policy Participant’
    • Overlap with Service Exposure work to examine role Overlap with Service Exposure work to examine role of an rApp Manager to support controlled access to and exposure & LCM of µService and non-µService parts of an rApp
    • Hope to start work on supporting ASD-based rApps
    • Support KServe App components
    • of Services
    • Overlap with Data Exposure work to examine role of an rApp Manager to support controlled access to and exposure of Data types
  • Continued A1-Policy & A1-Enrichment-Information evolution (& R1-A1)
    • Sample use cases (rApps)
      • Requirements Drivers for rApp/R1 development
      • High degree of cross-project integration activity
    • Testing, Maintenance & Housekeeping
      • Function Test & Integration Test environment,
      • Support integration, deployment & configuration of SMO/Non-RT-RIC related functions & usecases in OSC Integration env.
      • Project coordination, Documentation, Delivery, Reporting, Cross-project alignment, Community demos, O-RAN Standardization support, etc.
      • A1-Policy work in ONAP (continues in ONAP London) - candidate for R1-A1(P)
        • Numerous updates to improve security
        • Improved support fine-grained policy-based access control
        • Removed DMaaP NBI
      • A1-EI management as part of DME - candidate for how to include A1-EI in R1-DME
        • ref. DME work above
    • Demonstrated ASD-based CNF LCM
      • ONAP SO CNFM in standalone mode
    • Sample use cases (rApps)
      • Requirements Drivers for rApp/R1 development
    • Testing, Maintenance & Housekeeping
      • 3PP update – esp. Springboot 3 & JDK 17
      • Function Test & Integration Test environment,
        • Lots of new test cases, and new ONAP L & OSC H test profiles
      • Continue integration, deployment & configuration of SMO/Non-RT-RIC related functions & usecases in OSC Integration environment.
      • Project coordination, Documentation, Delivery, Reporting, Cross-project alignment, Community demos, O-RAN Standardization support, etc.

Release H - Tasks

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

  • Jira
    serverORAN Jira

H Release - Highlights:

Count of Epics (20 issues), User Stories, Tasks, and Issues:  (455 issues)
Relevant Epics (Draft/Incomplete. Mostly in progress):

Jira
serverORAN Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns
serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
keyNONRTRIC-
829
855
  • Jira
    serverORAN JiracolumnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
    keyNONRTRIC-826846
  • Jira
    serverORAN Jira
    serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
    keyNONRTRIC-846
  • Jira
    issuekey,
    serverORAN JiracolumnIds
    serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
    keyNONRTRIC-842

  • Jira
    serverORAN Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
    keyNONRTRIC-

    825

    829

  • Jira
    serverORAN Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
    keyNONRTRIC-818826
  • Jira
    serverORAN Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
    keyNONRTRIC-788825
  • Jira
    serverORAN Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
    keyNONRTRIC-818
  • Jira
    serverORAN Jira
    serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
    keyNONRTRIC-753799
  • Jira
    serverORAN Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
    keyNONRTRIC-725788
  • Jira
    serverORAN Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
    keyNONRTRIC-670781
  • Jira
    serverORAN Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
    keyNONRTRIC-781753
  • Jira
    serverORAN Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
    keyNONRTRIC-842725
  • Jira
    serverORAN Jira
    serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
    keyNONRTRIC-696
  • Jira
    serverORAN Jira
    columnIdsissuekey,summary,issuetype,columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
    keyNONRTRIC-696670
  • Jira
    serverORAN Jira
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
    keyNONRTRIC-648

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

    Latest Architecture: Release H Architecture

    Components: Release H 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

    :

    Weekly Meetings:

    Demos:

    Release H - Studies

    Children Display
    alltrue
    depth1
    pageRICNR:Release H: Technical spikes

    Release H - Demos:


    • H-Release: Demonstration: "LCM of ASD-based CNFs using ONAP CNFM function in Standalone mode"
      See Video (HD), Video (SD) and Slides for more information

    • H-Release: Demonstration: "CAPIF for Service Registration & Service Discovery"
      See Video (HD), Video (SD) and Slides for more information

    Release H

    release:

    - Container images

    Release H

    release:

    - Deployment

    Instruction

    Instructions

    Latest Architecture (Release H)
    Anchor
    ArchitectureReleaseH
    ArchitectureReleaseH


    NONRTRIC

    ...

    Components (Release H)
    Anchor
    ComponentsReleaseH
    ComponentsReleaseH

    1. Non-RT-RIC Control Panel

    2. Non-RT-RIC (Spring Cloud) Service Gateway
    3. Non-RT-RIC (Kong) Service Exposure Prototyping
    4. A1 Policy Management Service
    5. Information Coordinator Service
    6. DMaaP/Kafka Information Producer Adapters
    7. NONRTRIC CAPIF Core (Service Registry)
    8. Initial Non-RT-RIC App Catalogue
    9. A1 Policy Controller / Adapter
    10. A1 Interface Simulator
    11. RAN PM functions
    12. Initial K8S Helm Chart LCM Manager
    13. Authentication Support (JWT Token Fetch)
    14. Test Framework
    15. "Helloworld" O-RU Fronthaul Recovery use case
    16. "Helloworld" O-DU Slice Assurance use case
    17. "Healthcheck" use case

    ...

    NONRTRIC (Spring Cloud) Service Gateway (Release H)

    ...

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

    ...

    London)

    A1 Policy Controller Service above A1 Adapter that provides:

    • Unified REST & DMaaP APIs 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)
    • Unified REST & DMaaP NBI
    • 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

    ...

    ...

    APIs provided by the ICS service

    A1-EI

    This API is between Near-RT RIC and the Non-RT RIC. The Near-RT RIC is a data consumer, which creates Information Jobs to subscribe for data. In this context, the information is referred to as 'Enrichment Information', EI.

    Data producer API

    This API is provided by the Non-RT RIC platform and is intended to be part of the O-RAN R1 interface. The API is for use by different kinds of data producers and provides support for:

    • Registry of supported information types and which parameters needed to setup a subscription.
    • Registry of existing data producers.
    • Callback API provided by producers to setup subscriptions.
    Data consumer API

    This API is provided by the Non-RT RIC platform and is intended to be part of the O-RAN R1 interface. The API is for use by different kinds of data consumers and provides support for:

    • Querying of available types of data to consume.
    • Management of data subscription jobs
    • Optional callback API provided by consumers to get notification on added and removed information types.
    Service status

    This API provides a means to monitor the health of this service.

    DMaaP/Kafka Information Producer Adapters (Release H)

    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.

    NONRTRIC CAPIF Core (Service Registry) (Release H)

    ...

    DMaaP/Kafka Information Producer Adapters (Release H)

    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.

    CAPIF Service Registry (Release H)

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

    Repository and documentation about the service can be found at:

    NONRTRIC rApp catalog (Release H)

    Register for NONRTRIC APPs (rApps)

    • rApps can be registered / queried

    Repository and documentation about the service can be found at:

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

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

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

    NONRTRIC rApp catalog (Release H)

    Register for NONRTRIC APPs (rApps)

    RAN Performance Monitoring Functions (File-based PM)

    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 networkrApps can be registered / queried

    Repository and documentation about the service can be found at:

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

    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

    ...

    RAN PM: PM Data File Collector

    RAN PM: PM File Converter 

    A1 Interface Simulator (Release H)

    Stateful 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 PM: PM Producer

    RAN PM: InfluxDB PM Logger

    Authentication Support (JWT Token Fetch) (Release H)

    ...

    Initial K8S Helm Chart LCM Manager (Release H)

    ...

    NONRTRIC Test Platform (Release H)

    ...

    Use Cases (Release H)

    "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'

    Information about the use case can be found at:

    Repository and documentation about the service can be found at:

    "Helloworld" O-DU Slice Assurance use case

    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'

    Information about the use case can be found at:

    Repository and documentation about the service can be found at:

    "Healthcheck" use case

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

    ...