A1 Termination

(Describe use of A1 Termination module, and how it is adapted for SON Use Case with Kafka dispatcher)

Ran-App

To support A1 interface in SON use case we have added RAN-App( ANR use case). RAN-App simulates the xApp behavior and to simulate the xApp E2 interface functionality we are using NETCONF protocol. Currently we have developed RAN-App for the ANR use case.

RAN App receives the ANR A1 policy data from the A1 Terminator and performs the business logic over it and triggers the Neighbor change  request towards the requested gNodeB node.

RAN-App uses Netconf protocol to interact with the gNodeB for triggering the ANR configuration.

We will add the sample payload which RAN-App will receive from the A1 Terminator and the sample output which RAN App will  send towards the CU/DU.

Enhancements to Ran-Sim Controller

RAN-Simulator is enhanced to support the RAN-App functionality. RAN-App crates a WebSocket connection with the RAN Simulator for interacting with the database and to interact with the CU/DU. RAN-App asks RAN-Simulator for the CU/DU existing configuration which in-turn RAN Simulator fetch it from MariaDB and gives back to the RAN-App.

Same way RAN-App sends the newly generated config payload towards the RAN simulator and RAN simulator in turn sends it towards the requested CU/DU using the NETCONF.