Hi Team,
I’m trying to build an understanding of the Aerial cuBB architecture, and I’m facing some issues bring the system up.
While I try to bring the system up, could I possibly get some E2E logs of a sample scenario having below procedures:
- Multi-Cell Setup/Start
- UE attach
- multi-cell UE scheduling
- UL/DL data transfer.
While I believe a set of logs having these procedures would be enough to get a hang of the system architecture, code-flow mapping and even bring the system up directly or indirectly – any available logs that might catalyze the purpose shall suffice.
If possible, please also share the corresponding scenario configurations for a clearer understanding of the scenario.
A prompt response shall be appreciated.
Thanks,
Anubhav Aggarwal
Hi @anubhav.aggarwal,
You can find information about running cuBB tests here and here.
This section also explains the overall software architecture of cuBB.
While I try to bring the system up, could I possibly get some E2E logs of a sample scenario having below procedures:
1. Multi-Cell Setup/Start
2. UE attach
3. multi-cell UE scheduling
4. UL/DL data transfer.
These procedures are mainly related to upper layer stacks and not L1. However, you can monitor some of the related information in phy log as well. For example, when you run a cuBB test, you can see UL/DL data throughput on the console. You can also observe CRC status (UL) and ACK/NACK information (DL) for each cell and UE (with a RNTI value). If you capture a FAPI log, you can see scheduled UEs on each cell with the corresponding L1 configuration (PRB, MCS, code rate information, etc.)
Can you provide more information about your use case so that we can help better?
Thank you.