The NONRTRIC project can be considered from a number of different viewpoints. This page presents some of these views:
NONRTRIC Controller Part:
Scope 1: A1 Adapter (Mediator, Endpoint) Southbound: Provide termination point for A1 interface(s) – REST endpoint for messages to/from Near-RealTime RIC Northbound: Provide a more generic interface for A1 operations – provide interface to R-APPs, without the need for A1 message generation, addressing, coordination, mediation, etc. O1 interfaces do not terminate in NONRTRIC function (but may terminate in same controller host/instance) |
NONRTRIC Services Part:
Scope 2: Coordinate/Host A1 Policy Management Services Map high level RAN goal/intent directives to finely-scoped A1 policies towards individual Near-RT RIC instances Informed by observed RAN context (provided over O1 via OAM functions), and other external context (via other SMO functions) Dynamically coordinate lifecycles of A1 policies in individual Near-RT RICs as contexts change |
Scope 3: Coordinate ML/AI Models – In RAN (“E2 nodes” & Near-RT RICs) and NONRTRIC Acts as model-training host May act as model-inference host (others: Near-RT RICs, “E2 nodes”) Dynamically coordinate ML/AI model lifecycle management (e.g. re-train, re-deploy, etc) Models are (always?) deployed over O1 interface |
Scope 4: Enrichment Data Coordinator Additional context that unavailable to Near-RT RICs (e.g. RAN data, SMO context, External context) Dynamically coordinate access and pass data to appropriate Near-RT RICs (e.g. for use in ML/AI model inference) |
Scope 5: R-APP Host & SMO Application Coordinator R-APPs may act as, or form part of, SMO-level applications R-APPs, via R-APP host function, may consumes many SMO-internal interfaces, and use many SMO-internal functions (O-RAN undefined) Dynamically coordinate R-APP lifecycle management |