Page Comparison

NONRTRIC Controller Part

Scope 1: A1 Controller (Mediator, Endpoint)

Southbound:
- Implement A1 spec. from O-RAN Alliance WG2
- Very restricted A1-like functions for Release A
Base Controller: Release A: Selected SDNC
Base Controller: Release B+: Studies ongoing, to be confirmed
Northbound:
- Release A: Very similar to southbound
  - Thin “shim” in SDNC to demonstrate the concept
- Release B+: Studies ongoing, to be confirmed
O1 interfaces:
- Defined in OAM project with SDN-R, VES collectors, etc
- Release A: Out of scope
- Release B+: O1 Observability
  - Coordinate with OAM project to leverage additional ONAP functions
    e.g.: DMAAP, RuntimeDB (ConfigDB), A&AI, DCAE, Policy Framework, SDN-R, SDC, CLAMP, Portal, etc.

Scope 2: Coordinate/Host A1 Policy Management Services

Intent Mapping:
- Release A: Out of scope
- Release B+: Studies ongoing, to be confirmed
  - Domain-specific mappings could be performed by domain-specific R-APPs? (TBC)
Policy Lifecycle Management
- Release A: Out of scope
- Release B+: Track & maintain multiple policy instances/types in multiple Near-RT RICs
Multiple Near-RT RIC instances
- Release A: Out of scope / hard-coded
- Release B+: A&AI, RuntimeDB to keep track of multiple Near-RT RICs (TBC)
- Release C+: A&AI, RuntimeDB, DCAE, VES to map Near-RT RICs to mobile UEs (TBC)
O1 Observability
- Release A: Out of scope
- Release B+: Coordinate with OAM project to leverage additional ONAP functions
- Release C+: Leverage DCAE & PM function coordination for custom O1 observability (TBC)

Scope 3: Coordinate ML/AI Models – In RAN (“E2 nodes” & Near-RT RICs) and NONRTRIC

Release A: Out of scope
Release B+: Studies initiated, to be confirmed
- Hope to leverage planned ONAP functionality

Scope 4: Enrichment Data Coordinator

Scope 5: R-APP Host & SMO Application Coordinator

...

Please see the relevant discussions for the current release under the NONRTRIC Development Guide section.