...
Need to add names ..
Agenda
- Kohn release - RAN Simulator updateupdates
Notes
Item | Who | Notes | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Kohn release reqs | 5/3: Here are links to the main SON Use case REQ for Kohn release .. CCSDK REQ to cover A1 support in SDNR and also RAN-Sim work (which does not have a JIRA home) It is clear that the SON-Handler MS has to send a modified message for the ANR A1-based message. That will have some minor code impact to SON-Handler. Currently, Policy has two control loops for the SON use case which are both forwarded from Policy to SDNR. As of Jakarta, both were O1-based actions in SDNR. 5/31 - Discussed A1 flow. See A1 section 6/21 - Presented SON Use Kohn in Architecture Sub-Committee. Got Approval. See JIRA and slides below
6/28: Created
| |||||||||||||||||||||||||||||||||
A1 support in SDN-R and Policy | 3/30 Good discussion on including A1-based action. Vishal Varvate is interested in contributing. He will work with John Keeney .
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.
5/3 Discussed message format for A1-based action. DMaaP message for ANR based needs to change to send payload aligned with A1 policy. Requirement on SON Handler MS
5/16: Discussed the problem statement using slides above. esp. Option 1 and 2 in slide xx. 5/31: See updated slides. Good discussion for A1-based flow which meets following guidelines:
6/21. Presented Use Case in Architecture Committee. Consensus is to make changes in Policy PEF to have
John K also showed diagrams for options about message from Policy to SDN-R. Ahila showed design used in Slicing use case. Need to add details and get recording (which went to cloud) . | |||||||||||||||||||||||||||||||||
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.
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
5/3 RAN App will have code to take an A1 message with (poor) HO KPI for a cell relation, and take action to blacklist that cell relation. 5/31 Slides update for A1 support topic also shows that RAN App can have direct netconf to CU/DU Honeycomb device. We understand that RAN App is only an abstraction of xApp (which will have E2 interface to CU/DU which is not netconf). 6/21 - Plan is to focus on using websocket from RAN App to RAN Sim Controller. 6/28 -
|
...