Question about using real USRP devices with the project

[LoganCome]

• I noticed that the current setup uses ZMQ to emulate gNB. I was wondering if it's possible to use real USRP devices, such as the USRP B210, instead of the emulation.
• If the project does support real USRP devices, are there any specific configuration changes that need to be made to accommodate them?

[pgawlowicz]

The RIC part is independent of the deployment type (i.e, emulation over zmq or real wireless transmission using USRP).
The provided tutorial is focused on ZMQ-based setup, as it makes it easy for everyone to replicate.

You can check our tutorial showing how to run the setup over a USRP here. Then you need to update gnb's config to enable E2 agent.

[s21sm]

It is possible with real USRP and with commercial UE. Here is my xapp output for real setup. I recommend using always the updated version. I am wondering how to control some parameter of gNB using xapp>>RIC agent.

[pgawlowicz]

We will soon publish an example showing how to control gNB parameters using E2SM-RC module.

[s21sm]

@pgawlowicz Thanks. In the Flexric, it is possible to access the saved database [xApp]: DB filename = /tmp/xapp_db_1714648640282017 I am wondering if there is any such type of implementation in oran-sc-ric? database is very important for creating further decision making logic.

[pgawlowicz]

We are running a container with a database, check here: https://github.com/srsran/oran-sc-ric/blob/main/docker-compose.yml#L4
Also, if you sniff traffic on the RIC interface in Wireshark, you can see that some services are accessing it.

You will need to check the ORAN-SC-RIC resources on how to access it from your xapp.

[s21sm]

@pgawlowicz Could you please give some hints how to access / save the data in a database as it is in Flexric?

$ redis-cli -h 10.0.2.12 -p 6379
10.0.2.12:6379> keys *
1) "{e2Manager},GNB:00F110:0000000000000000000110011011"
2) "{e2Manager},GNB"
3) "{e2Manager},RAN:gnb_001_001_0000019b"
4) "{e2Manager},GENERAL"
5) "{e2Manager},E2TAddresses"
6) "{e2Manager},GNB:00F110:0000000000000110011011"
7) "{e2Manager},E2TInstance:10.0.2.10:38000"
8) "{e2Manager},RAN:gnb_001_001_00019b"
10.0.2.12:6379> 

[pgawlowicz]

Not sure if the python API for accessing the database is implemented in the Python xApp Framework (https://github.com/o-ran-sc/ric-plt-xapp-frame-py)

[LoganCome]

It is possible with real USRP and with commercial UE. Here is my xapp output for real setup. I recommend using always the updated version. I am wondering how to control some parameter of gNB using xapp>>RIC agent.

@s21sm Congratulations! Congratulations on your success in implementing the project on a real USRP and with a commercial UE. I'm also trying to deploy it, but I'm encountering the error shown in the image. Could you share your experience? Specially, could you help us on which configuration files/parameters need to be modified to achieve deployment on real devices?

1. The figure is the error output in app and containers:
   
   
   

2. The gNB log file
   gnb.log

3. Contents of gNB configure file
   gnb_rf_x410_tdd_n78_20mhz.txt