A1 Termination
on top of existing OSC A1 simulator codebase a module named A1 Terminator has added, it does interaction with the A1-PMS and the RAN-App. It acts a gateway between the RAN-Simulator and the SDNR.
A1-PMS sends the A1 policy to the A1 Terminator ,which in turn using Kafka dispatcher module A1 terminator sends the A1 policy payload on the configured Kafka topic and RAN-App will consume the A1 policy from the same topic.
Once RAN-App finishes its processing it publish response back on the Response topic ,which in turn A1 terminator receives it and process it.
To start the A1 terminator please use below commands.
Build and start the simulator containers: STD_1.1.3 and OSC_2.1.0, using: ./build_and_start.sh duplicate-check|ignore-duplicate Build and start the simulator container version STD_2.0.0, using two alternatives: ext-srv or kafka-srv. However, both can not be used at the same time to start A1 sim. In order to start with ext-srv: In order to start with kafka-srv: |
|---|
We will add the A1 ANR policy payload which A1 terminator receives it from the A1-PMS and will add the sample output which A1 Terminator will be pushing.
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.
Sample Input Payload for Ran-App:
| {"action":"UpdatePolicy","payload":{"PNFName":"cucpserver2","PLMNID":"ran-1","CellID":"15549","neighbours":[{"PNFName":"cucpserver2","PLMNID":"ran-1","CellID":"14427","ho-kpi1":100},{"PNFName":"cucpserver2","PLMNID":"ran-1","CellID":"15548","ho-kpi1":90}]},"policy_type_id":"ANR","policy_id":"pi3"} |
|---|
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.