You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Near-RT RIC Application Requirements

General Requirements:

Upon being loaded will declare to the Near-RT RIC Platform what data it consumes and what data it publishes.

TS xApp Requirements:

When loaded, the TS xApp will declare to the Near-RT RIC Platform that it consumes “QoE Based Traffic Steering” Policy, UePerf data, and PredictedQoE data. It produces nothing.

QP xApp Requirements:

When loaded will declare to the Near-RT RIC Platform that it consumes UeRf, UePerf, and CellPerf data. It produces PredictedQoE data.

Near-RT RIC Platform Requirements

Upon a new xApp instance being loaded, the Platform will catalog the data types consumed and produced, and use this information in the routing of data from xApp to xApp. Particularly, the Platform will be responsible for ensuring that the PredictedQoE data produced by the QP xApp is made available to the TS xApp.

SMO/Non-RT RIC Platform Requirements

Because ONAP does not support xApps as separately managed objects in the Frankfurt release, xApp deployment in Release B will be handled as if the TS and QP xApps were software modules of the Near-RT RIC itself.

  • No labels