Identical EARFCN assignment for E-UTRA bands 106 and 107

[kuehnhammer]

Context

3GPP TS 36.101 V18.4.0 (2023-12) defines the EARFCN for band 106 in table 5.7.3-1 as:

... and for band 107 in table 5.7.3H-1 as:

Problem description

The bands share identical EARFCNs in range 70656 - 70705. If both bands are defined, the eNB cannot determine the intended band from a provided DL EARFCN in this range.

Suggested solution

Is this by design? If so, how should an LTE-based 5G-BC capable eNodeB handle the situation?

** Edit: corrected UE to eNodeB **

[jordijoangimenez]

Hi @kuehnhammer, I'm not sure if this is a problem as the UE will calculate the exact frequency given FDL_low as FDL = FDL_low + 0.1(NDL – NDL_ini), means 612 up to 652 for Band 107; and 470 up to 698. So is the combination of both FDL_low and NDL which uniquely determine the frequency

@haudiobe. What I would suggest is that we include in ETSI TS 103 720 how the UE derives the exact frequency and what the required signaling is to be provided by the TX.

[kuehnhammer]

Agreed on the frequency, but how can an eNB know which band to signal in SIB1 based on the configured EARFCN?

[jordijoangimenez]

I see your point. I'm not sure how the EARFCN is delivered to the eNBs. The MME should be responsible of managing the SIBs but the SIBs convey information to the UE, not to configure the eNB. The information to the eNB shoudl be carried over M2/M3?

What I think may be needed is a kind of T2-MI (https://dvb.org/wp-content/uploads/2019/12/a136_dvb-t2-modulator-interface.pdf) interface or at least we could describe in ETSI 103 720 how this is done based on the signaling between MME and eNB or how the control plane info from the BM-SC is used to configure the eNBs participating in an MBSFN Service Area.