Versions Compared

Key

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

...

NONRTRIC gateway code can be found here.found at:

More information on the Spring Cloud Gateway can be found in the documentation here.

...

  • 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 Adaptor to connect direct to near-RT-RICs)

Documentation about the service can be found at:

https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric/en/cherry/

...

  • Maintains a registry of:
    • A1-EI Data Types / schemas
    • A1-EI Producers
    • A1-EI Consumers
    • A1-EI Jobs
  • A1-EI Query API (e.g. per producer, per consumer, per types)
  • Query status of A1-EI jobs
  • Monitors all near-RT-RICs and recovers from inconsistencies
  • After EI-type/Producer/Consumer/Job is successfully registered delivery/flow can happen directly between A1-EI Producers (in SMO/NONRTRIC domain) and A1-EI consumers (near-RT-RICs in RAN domain)
  • Being extended to coordinate non-A1 Enrichment Information exchange between NONRTRIC Apps

Documentation about the service can be found at:

https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric/en/cherry/

...

  • 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
  • OSC Dawn will continue to support both a dedicated A1-controller persona (NONRTRIC) and an SDNC/SDNR persona (IT/DEP, OAM/SMO)

Documentation about the adaptor can be found at:

https://docs.o-ran-sc.org/projects/o-ran-sc-nonrtric/en/cherry/

...

  • Used to create multiple stateful A1 providers (simulated near-rt-rics)
  • Supports A1-Policy and A1-EnrichmentInformation
  • 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-E1 consumers, etc)
  • All A1-AP versions supported

Documentation about the simulator can be found at:

https://docs.o-ran-sc.org/projects/o-ran-sc-sim-a1-interface/en/latest/index.html

...

Code for the use case can be found here.found at: