Scope 2: Coordinate/Host A1 Policy Management Services - Map high level RAN goal/intent directives to finely-scoped A1 policies towards individual nearNear-RealTimeRIC 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 nearNear-RealTimeRICs RT RICs as contexts change
|
Scope 3: Coordinate ML/AI Models – In RAN (“E2 nodes” & nearNear-RealTimeRICsRT RICs) and NONRTRIC - Acts as model-training host
- May act as model-inference host (others: nearNear-RealTimeRICsRT 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 nearNear-RealTimeRICs RT RICs (e.g. RAN data, SMO context, External context)
- Dynamically coordinate access and pass data to appropriate nearNear-RealTimeRICs 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
|