The gNB-DU initiates the procedure by sending a F1 SETUP REQUEST message including the appropriate data to the gNB-CU. The gNB-CU responds with a F1 SETUP RESPONSE message including the appropriate data.
The exchanged data shall be stored in respective node and used as long as there is an operational TNL association. When this procedure is finished, the F1 interface is operational and other F1 messages may be exchanged.
If the F1 SETUP REQUEST message contains the
gNB-DU Name IE, the gNB-CU may use this IE as a human readable name of the gNB-DU. If the F1 SETUP REQUEST message contains the
Extended gNB-DU Name IE, the gNB-CU may use this IE as a human readable name of the gNB-DU and shall ignore the
gNB-DU Name IE if included.
If the F1 SETUP RESPONSE message contains the
gNB-CU Name IE, the gNB-DU may use this IE as a human readable name of the gNB-CU. If the F1 SETUP RESPONSE message contains the
Extended gNB-CU Name IE, the gNB-DU may use this IE as a human readable name of the gNB-CU and shall ignore the
gNB-CU Name IE if included.
If the F1 SETUP REQUEST message contains the
gNB-DU Served Cells List IE, the gNB-CU shall take into account as specified in
TS 38.401.
For NG-RAN, the gNB-DU shall include the
gNB-DU System Information IE and the
TAI Slice Support List IE in the F1 SETUP REQUEST message.
The gNB-CU may include the
Cells to be Activated List IE in the F1 SETUP RESPONSE message. The
Cells to be Activated List IE includes a list of cells that the gNB-CU requests the gNB-DU to activate. The gNB-DU shall activate the cells included in the
Cells to be Activated List IE and reconfigure the physical cell identity for cells for which the
NR PCI IE is included.
If
Cells to be Activated List Item IE is included in the F1 SETUP RESPONSE message, and the information for the cell indicated by the
NR CGI IE includes the
IAB Info IAB-donor-CU IE, the gNB-DU shall, if supported, apply the
IAB STC Info IE therein to the indicated cell.
For NG-RAN, the gNB-CU shall include the
gNB-CU System Information IE in the F1 SETUP RESPONSE message.
For NG-RAN, the gNB-DU may include
Supported MBS FSA ID List IE in the
Served Cell Information IE in the F1 SETUP REQUEST message. The gNB-CU may use it according to
TS 38.300.
For NG-RAN, the gNB-DU may include the
RAN Area Code IE in the F1 SETUP REQUEST message. The gNB-CU may use it according to
TS 38.300.
For NG-RAN, the gNB-CU may include
Available PLMN List IE, and optionally also
Extended Available PLMN List IE in the F1 SETUP RESPONSE message, if the available PLMN(s) are different from what gNB-DU has provided in F1 SETUP REQUEST message, gNB-DU shall take this into account and only broadcast the PLMN(s) included in the received Available PLMN list(s).
For NG-RAN, the gNB-CU may include
Available SNPN ID List IE in the F1 SETUP RESPONSE message. If the available SNPN(s) are different from what gNB-DU has provided in F1 SETUP REQUEST message, gNB-DU shall take this into account and only broadcast the SNPN(s) included in the received Available SNPN ID list.
The
Latest RRC Version Enhanced IE shall be included in the F1 SETUP REQUEST message and in the F1 SETUP RESPONSE message.
If in F1 SETUP REQUEST message, the
Cell Direction IE is present, the gNB-CU should use it to understand whether the cell is for UL or DL only. If in F1 SETUP REQUEST message, the
Cell Direction IE is omitted in the
Served Cell Information IE it shall be interpreted as that the Cell Direction is Bi-directional.
If the
Intended TDD DL-UL Configuration IE is present in the F1 SETUP REQUEST message, the receiving gNB-CU shall use the received information for Cross Link Interference management and/or NR-DC power coordination. The gNB-CU may merge the Intended TDD DL-UL Configuration information received from two or more gNB-DUs. The gNB-CU shall consider the received Intended TDD DL-UL Configuration content valid until reception of an update of the IE for the same cell(s).
If the
Aggressor gNB Set ID IE is included in the
Served Cell Information IE in the F1 SETUP REQUEST message, the gNB-CU shall, if supported, take it into account.
If the
Victim gNB Set ID IE is included in the
Served Cell Information IE in the F1 SETUP REQUEST message, the gNB-CU shall, if supported, take it into account.
If the F1 SETUP REQUEST message contains the
Transport Layer Address Info IE, the gNB-CU shall, if supported, take into account for IPSec tunnel establishment.
If the
SFN Offset IE is contained in the
Served Cell Information IE in the F1 SETUP REQUEST message, the gNB-CU shall, if supported, use this information to deduce the SFN0 offset of the reported cell.
If the F1 SETUP RESPONSE message contains the
Transport Layer Address Info IE, the gNB-DU shall, if supported, take into account for IPSec tunnel establishment.
If the F1 SETUP RESPONSE message contains the
Uplink BH Non-UP Traffic Mapping IE, the gNB-DU shall, if supported, consider the information therein for mapping of non-UP uplink traffic.
If the
BAP Address IE is included in the F1 SETUP REQUEST, the receiving gNB-CU shall, if supported, consider the information therein for discovering the collocation of an IAB-DU and an IAB-MT.
If the F1 SETUP REQUEST message is received from an IAB-donor-DU, the gNB-CU shall, if supported, include the
BAP Address IE in the F1 SETUP RESPONSE message.
If the F1 SETUP RESPONSE message contains the
BAP Address IE, the gNB-DU shall, if supported, store the received BAP address and use it as specified in
TS 38.340.
If the
NR Cell PRACH Configuration IE is included in the
Served Cell Information IE contained in the F1 SETUP REQUEST message, the gNB-CU may store the information, and forward it to other RAN nodes for RACH optimisation.
If the
RedCap Broadcast Information IE is included in the
Served Cell Information IE in the F1 SETUP REQUEST message, the gNB-CU may use this information to determine a suitable target in case of subsequent outgoing mobility involving RedCap UEs.
If the
TAI NSAG Support List IE is included in the
Served Cell Information IE in the F1 SETUP REQUEST message, the gNB-CU shall, if supported, use this information as specified in
TS 23.501.
Not applicable.