/
Discussion End-to-End Integration

Discussion End-to-End Integration

Owned by bimo fransiscus asisi
Last updated: Apr 30, 2025

Description

INT Project propose end-to-end integration effort. It can be viewed as an effort to have end-to-end call flow with a use case from TIFG with below details:

  • Topic:

    • End-to-End Integration Use Case Proposal

  • Use Case :

    • Network Energy Saving with Carrier and Cell switch off/on using Non-RT RIC (O-RAN.TIFG.E2E-Test.0-R003-v06.00)

  • Test Description:

    • As the load in capacity cell decreases, the carrier/cell switch off decision is made.

    • Appropriate operations to switch off capacity cell need to be taken in AIMLFW, SMO/Non-RT RIC/rApp and Near RT RIC.

  • System Architecture:

image-20250430-112242.png

 

CallFlow:

  1. Viavi RICTEST runs and expose O1 PM

  2. ES rApp sends DRB.UEThp, RRU.PrbTot, PEE.AvgPower to ML rApp for traffic load prediction

  3. ML rApp sends the DRB.UEThp predict result

  4. ES rApp controls cell on/off

  5. ES rApp sends A1 policy

  6. Handover(HO) xApp retrieves UEID and identify neighbor cells and select cell based on highest RSRP

  7. ES rApp turns off RAN

 

Overlay Architecture refer to Decouple SMO

image-20250416-065749.png

 

Topic

  • Interfaces

    • O1

      • Define O1 PM Procedure and details in E2E call

        • Problem: Plan to use Viavi TeraVM RICTest for O1 Node integration but PM file-based is not available.

        • Action Items:

          • Figure out approach to use for O1 PM.

          • Have Viavi permission to share NETCONF capabilities. Link:

 

Feedback

Project

PTL

Comment/Requirement

Project

PTL

Comment/Requirement

AIMLFW

@subhas.mondal

In context of AIMLFW, I feel we could enhance it by adding below steps after the step 1 from the flow:

  1. Model Training: The ES rApp should first request AIMLFW to train a model using O1 PM data (e.g., DRB.UEThp, RRU.PrbTot, PEE.AvgPower) for traffic load prediction.

  2. Model Discovery: The ES rApp should leverage AIMLFW’s model management service to discover and retrieve the trained model.

  3. Model Deployment: The ES rApp should request AIMLFW to deploy the trained model as an rApp. (This capability currently does not exist but needs to be introduced).

SMO/Non-Realtime RIC

@John Keeney (Ericsson EST)

  • We expect to have a working integrated SMO/NONRTRIC/OAM install available in it/dep in coming days (early Apr) - incorporating a working version of the previous it/dep/smo-install (ONAP & OAM & nonrtric), nontric, ranpm, teiv - with common infrastructure integrated to all charts. Still examining how to integrate AIMLFW, Nephio & other smo project’s function (Tacker etc). This hould provide integated functionality for smo/nonrtric/oam - including rApp platform function.

  • PM → AIMLFW & rApps: File-based or Streamed?

    • Some old work on streamed PM: PM Streaming - but not yet implemented completely

    • File-based solution could use existing NONRTRIC RAN-PM solution - will be already included in SMO deployment

    • Could possibly use NONRTRIC DMaapAdapter to present events as DME job - but would probably needs some work. And a collector would be needed too (if not using VES collector)

    • Could possibly translate existing data format to file-based? Seems to be interval-based periodic data, so should be possible? 

  • 2 existing rApps needs to be updated to nonrtric-rAppManager format.

  • Need to confirm A1-Policy Type supported in xApp. Need a sample A1Policy instance to help define the A1-Policy logic in rApp.

  • Note: O1-CM - Should be possible to use NCMP to perform RestConf operation via SDNC/ODL

 

 

OAM

@Martin Skorupski

Flows
[1] We assume that this point includes the following messages:
- 1.1 VES StndDefined FileReady
- 1.2 The DataFileCollecter gets the PM Data (NonRtRic Project) in a 3GPP xml file format
- 1.3 The data will be stored in InfluxDB and will be also on Kafka

[7] There are several ways to turn a cell ON/OFF. How about using the administrativeState of the NrCellDU object class: https://forge.3gpp.org/rep/sa5/MnS/-/blob/Tag_Rel18_SA107/yang-models/_3gpp-nr-nrm-nrcelldu.yang?ref_type=tags#L107

Interface specs
- 3GPP xml format for PM data (link to be provided)
- NETCONF: 3gpp-nr-nrm-nrcelldu@2024-05-24.yang
- VES stndDefined plus OpenAPI/TS28532_FileDataReportingMnS.yaml · Rel-18 · SA5 – Management & Orchestration and Charging / Management and Orchestration APIs · GitLab

RICPLT

@abdulwahid.w

 

RIC APP

@Sunil Singh

 

ODU High

@Ankit Barve

 

ODU LOW

@Farias Luis

 

SIM

@Alex Stancu

SIM project can provide O1 interface simulation, that can be used for the dev environment, before we do the final integration with Viavi RIC Test.

There is also the E2 interface simulator in SIM project which could be leveraged, if needed.

Reference