Versions Compared

Version Old Version 1 New Version Current
Changes made by

N.K. Shankaranarayanan

N.K. Shankaranarayanan

Saved on

Key

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

...


Recording:  video1081010987.mp4

Agenda

  1. Kohn release timeline - M3 target is Sept 1.
  2. Control Loop message format - Reviewed control loop message in JIRA. We have consensus to share format with Policy team
  3. RAN-Sim update - Ongoing progress. No issues.
  4. Rutgers lab info - Shared info about Rutgers Lab used for integration testing. See Open Wireless Lab - NO LONGER AVAILABLE for info about access

Notes

ItemWhoNotes
Control Loop message format

Converged on a modified Control Loop message format for PCI and ANR messages. Changes made to designate them as SONO1 and SONA1 messages.
The message format is tracked in trh Policy JIRA

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPOLICY-4108

There is impact on SONH-MS, SDN-R, RAN-Sim also.

8/23 - Reviewed control loop message in JIRA. We have consensus to share format with Policy team

 A1-Simulator (A1 Terminator) → RAN App

8/9: 

A1-Termination code is in OSC repo

https://gerrit.o-ran-sc.org/r/gitweb?p=sim%2Fa1-interface.git;a=shortlog;h=refs%2Fheads%2Fmaster

Payload of A1 Policy msg will have HO_KPI is numeric form.

RAN App is programmed / configured with a poorHOKPI_threshold (e.g, 20). If HO_KPI < threshold, then the cell relation needs to be marked as isHOAllowed=false.

7/19:

Halil Cakal discussed the previous email message to converge on the Kafka message format between the A1 Terminator and RAN App

  • Confirmed details of Kafka message format
  • A1 Terminator will own the Kafka topics and mapping to policy_id
  • Assume pre-configured knowledge of existence of ANR RAN App so that it does not need to be discovered during initial bootstrap (this would require an interface between A1 Terminator and RANSim Controller which keeps a catalog of RAN Apps)
  • Default timeout value of 30 seconds (configurable) for response from RAN App to A1 Term. It might take longer to have Policy processed in RAN-Sim. Can be adjusted during testing.
  • Halil will send email with items agreed.


-- from 7/12 last week --

  • Need configurable lookup table (Map) for
    • A1 Policy Type  :-:  Topics (req & resp)
  • Need 2 topics: request and response
    • RANSIM will query A1-SIM (adapter) to request lookup table - per A1 Policy Type
    • Each message A1-Sim → RanSIM will have a requestID Key - which must be included in the reply RanSIM → A1-SIM to correlate requests & responses.
      • Default timeout 30 sec waiting for response.
  • Need Near-RT-RIC ID in each message A1 Sim → RanSIM   
    • Can be ignored by RANSIM - as RANSIM acts as 1 near-RT-RIC, so 1:1:1 mapping A1-SIM :  RANSIM : nearRTRIC
  • Next week will demo a real A1 Policy Type (prefer the actual use case type) with full end-to-end sequence
    • (request) curl/postman → A1(REST) → A1-SIM → kafkaAdapter → kafka broker → RANSIM(stub) 
    • (response) RANSIM(stub) → kafka broker → kafka adapter → A1-SIM → A1(REST) → curl/postman
RAN App → RAN-Sim Controller → Honeycomb RAN NF (CU)

8/9 See comments in

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyINT-2129
 

netconf editmsg to change nrcellrelation/isHOAllowed property has been added to the the JIRA. This is aligned with the O-RAN yang model.

RAN App output will use this format as the payload in the websocket msg.


...