mirror of
https://gitlab.eurecom.fr/oai/openairinterface5g.git
synced 2026-07-13 04:30:28 +00:00
Fixes for multiplexing pattern 3 operations in FR2 The standard (section 13 of 38.213) defines 3 SSB and CORESET 0 multiplexing patterns, which differ based on how the two channels are respectively positioned in time and frequency. For MUX pattern 3, SSB and CORESET 0 are transmitted in the same slot/symbols but on different frequencies. With CORESET 0 being directly above or below in frequency of SSBs, this means it does not start from symbol 0. This configuration is important for more than 8 SSBs (FR2) to accommodate SIB1 in the available DL slots (SIB1 in the same slot as its relative SSB), but it is impractical for anything else. So for any other channel except SSB, it is necessary to use a different common CORESET than CSET0 (namely commonControlResourceSet). This MR attempts to fix an issue in case the CORSET being smaller than 48 PRBs, triggering 2 symbol CORESET configuration, but the BWP being larger than 48 PRBs so not taking into account the 2 symbol CORESET when configuring other channels, e.g. PDSCH. Reviewed-By: Luis Pereira <lpereira@allbesmart.pt>
Configuration files: naming style guide
The configuration files should have the following name format:
<type>[.<sa|nsa>][.band<num>.[u<num>.]<num>prb].<sdr>[.<opt>].conf
Where:
[]means this field is optional<type>: one ofgnb,enb,gnb-cu,gnb-du,nrue,lteue, etc.<sa|nsa>: in the case of 5G, notes whether this is SA or NSA<num>forband/u/prb: numerical value. Note that band/PRB are only applicable in some cases. The numerologyuis only to be set for 5G if it differs fromu1.<sdr>: what SDR board/split this is tailored for:- e.g.,
usrpb210,usrpn310,rfsim,aw2s - if there is no SDR (e.g., for a CU), use the south-bound split, e.g.,
f1,if4p5, etc. - for the L2simulator, write
l2sim
- e.g.,
<opt>: optional specifiers. If there are multiple, concatenated using a dash (-). Examples:2x2prs(positioning reference signal)ddsuu(specific TDD pattern)tm2: Transmission Mode 2 in 4Goaiue: specifies usage with OAI UE and not COTS UE
Examples:
- standard monolithic gNB, 2x2 configuration, with SDAP:
gnb.sa.band78.162prb.usrpn310.2x2-sdap.conf - gNB-CU:
gnb-cu.sa.f1.conf - monolithic gNB, L2sim:
gnb.sa.band77.106prb.l2sim.conf - monolithic eNB:
enb.band7.25prb.usrpb200.conf - RCC (4G eNB with IF4.5 split):
enb-rcc.band7.25prb.tm1.if4p5.conf
Notes:
- there is no need for TDD/FDD, this is encoded in the band number
- there is no need for FR1/FR2, this is encoded in the band number