Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Agenda

  1. Testing status for Jakarta release - Testing is on track and target is to close test cases by Thursday 4/28
  2. Requirements for Kohn release - RAN-Sim changes
  3. A1 Policy schema for ANR

Notes

ItemWhoNotes



Kohn release reqs

Discussed reqs in following table. Will create JIRA as needed after discussion converges. Need to determine feasibility of work for SON-Handler MS and Policy.

View file
nameONAP_SON_UseCase_Kohn_Req.xlsx
height250

A1 - based action

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:

  1. Implement A1 instance in SDN-R. Leverage past work in A1, including work for Slicing use case, and OSC.
  2. A1-policy trigger will be based on Control Loop msg sent from SON-Handler MS via Policy over DMaaP.
  3. 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.
  4. 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.

4/26: Discussed control loop message formats for PCI and ANR and ANR policy schema. They are using same Policy name but different Control-Loop name and

different Action. See sample messages in file. Changes to ANR message format and control loop policy has impact on SON-Handler MS and Policy.

View file
nameSON_ANR_PCI_sample_clmsg_sample A1policy.txt
height250

RAN-Sim

3/8 Further discussion on including netopeer in RAN-Sim. See slides 2-6 in ppt attached here.

View file
nameONAP_RANSim_Enhancement.pptx
height250

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.

View file
nameNearRT-implementation.pptx
height250

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 )


...