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