Versions Compared

Old Version 1

changes.mady.by.user N.K. Shankaranarayanan

Saved on

compared with

New Version Current

changes.mady.by.user N.K. Shankaranarayanan

Saved on

Key

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

...


Recording:  0719_son_usecasecall_video1295099740.mp4

Agenda

  1. Continue demo of discussion on the details of the Kafka message between A1-Simulator (A1 Terminator) → RANSIM-Controller Kafka messaging for A1 operationsand RAN App

Notes

Unfortunately N.K. Shankaranarayanan could not join so we could not use the usual bridge - used different bridge (ONAP OSC Alignment meeting bridge)
ItemWhoNotes
 A1-Simulator (A1 Terminator) → RANSIM Controller RAN App Kafka messaging

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 -- showed current snapshot of A1-SIM → RANSIM (kafka)

  • 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

...