3/30 Good discussion on including A1-based action. Vishal Varvate is interested in contributing. He will work with John Keeney . We discussed following plan:
Implement A1 instance in SDN-R. Leverage past work in A1, including work for Slicing use case, and OSC.
A1-policy trigger will be based on Control Loop msg sent from SON-Handler MS via Policy over DMaaP.
RAN-Sim needs enhancement to have xApp abstraction to receive A1 message and update CU/DU state and send VES msg. If A1 policy message is about ANR/HO state, it can trigger xApp to make change to CU property. This chain replaces a direct O1 action for current ANR action.
RAN-Sim update can leverage work for Slicing. The target for RAN-SIm work is to align with OSC and also plan to move to netopeer due to Honeycomb being archived. Possible approach is to add a netopeer-based server for near-rt-roc and xApp abstraction. Implementation of E2 to CU/DU can be abstracted. Details TBD.
4/19 Vishal needs info on A1 policy schema for ANR use case. Discussed details. Shankar to follow up.
RAN-Sim
3/8 Further discussion on including netopeer in RAN-Sim. See slides 2-6 in ppt attached here.
3/30
Vishal presented slides below. We had a good discussion. Option 2 gives a little more flexibility for future use. John said they are willing to help with the A1 termination. Netconf option instead of Websocket to RAN-Sim controller will need some integration work in RAN-Sim controller. Vishal will work with Niranjana on that. Also sent a request to present in the ONAP/OSC Harmonization call today 3/30.
4/19
Discussed change in terminology to avoid confusion. We are not implementing Near-RT RIC and xApp using OSC near-rt-ric.
Decision to change terminology to better capture the nature of the RAN-Sim enhancement.
Plan is to implement
A1-Termination
RAN App. (The App function is an abstraction which works with RAN-Sim, and does not implement E2 like an xApp on near-rt-ric )