From 197db6a65f8173e4e2f0515211bb71e6aa309032 Mon Sep 17 00:00:00 2001 From: Teodora Date: Wed, 4 Dec 2024 16:57:30 +0100 Subject: [PATCH] Correction on PRACH offset in FHI README - this should have been done in the commit ID b334feb9 --- doc/ORAN_FHI7.2_Tutorial.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/ORAN_FHI7.2_Tutorial.md b/doc/ORAN_FHI7.2_Tutorial.md index 015c5b6ad1..b55b354a85 100644 --- a/doc/ORAN_FHI7.2_Tutorial.md +++ b/doc/ORAN_FHI7.2_Tutorial.md @@ -929,7 +929,9 @@ Layer mapping (eAxC offsets) happens as follows: - For PUSCH/PDSCH, the layers are mapped to `[0,1,...,Nrx-1]/[0,1,...,Ntx-1]` where `Nrx/Ntx` is the respective RX/TX number of antennas. - For PRACH, the layers are mapped to `[No,No+1,...No+Nrx-1]` where `No` is the - `fhi_72.fh_config.[0].prach_config.eAxC_offset`. Please be aware that the following equation must be fullfilled: `No >= max(Nrx,Ntx)`. + `fhi_72.fh_config.[0].prach_config.eAxC_offset`. xran assumes PRACH offset `No >= max(Nrx,Ntx)`. + However, we made a workaround that xran supports PRACH eAxC IDs same as PUSCH eAxC IDs. This is achieved with `is_prach` and `filter_id` parameters in the patch. + Please note that this approach only applies to the RUs that support this functionality, e.g. LITEON RU. **Note**