Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 38.473  Word version:  16.3.1

Top   Top   Up   Prev   Next
1…   4…   8…   8.2…   8.2.4…   8.2.6…   8.3…   8.3.2…   8.3.4   8.3.5…   8.4…   8.5…   8.6…   8.10…   8.13…   9…   9.3…   9.4…

 

8.2.4  gNB-DU Configuration Update

8.2.4.1  General

The purpose of the gNB-DU Configuration Update procedure is to update application level configuration data needed for the gNB-DU and the gNB-CU to interoperate correctly on the F1 interface. This procedure does not affect existing UE-related contexts, if any. The procedure uses non-UE associated signalling.
Up

8.2.4.2  Successful Operation

Reproduction of 3GPP TS 38.473, Figure 8.2.4.2-1: gNB-DU Configuration Update procedure: Successful Operation
Up
The gNB-DU initiates the procedure by sending a GNB-DU CONFIGURATION UPDATE message to the gNB-CU including an appropriate set of updated configuration data that it has just taken into operational use. The gNB-CU responds with GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message to acknowledge that it successfully updated the configuration data. If an information element is not included in the GNB-DU CONFIGURATION UPDATE message, the gNB-CU shall interpret that the corresponding configuration data is not changed and shall continue to operate the F1-C interface with the existing related configuration data.
The updated configuration data shall be stored in both nodes and used as long as there is an operational TNL association or until any further update is performed.
If gNB-DU ID IE is contained in the GNB-DU CONFIGURATION UPDATE message for a newly established SCTP association, the gNB-CU will associate this association with the related gNB-DU.
If Served Cells To Add Item IE is contained in the GNB-DU CONFIGURATION UPDATE message, the gNB-CU shall add cell information according to the information in the Served Cell Information IE. For NG-RAN, the gNB-DU shall include the gNB-DU System Information IE.
If Served Cells To Modify Item IE is contained in the GNB-DU CONFIGURATION UPDATE message, the gNB-CU shall modify information of cell indicated by Old NR CGI IE according to the information in the Served Cell Information IE and overwrite the served cell information for the affected served cell. Further, if the gNB-DU System Information IE is present the gNB-CU shall store and replace any previous information received.
If Served Cells To Delete Item IE is contained in the GNB-DU CONFIGURATION UPDATE message, the gNB-CU shall delete information of cell indicated by Old NR CGI IE.
If Cells Status Item IE is contained in the GNB-DU CONFIGURATION UPDATE message, the gNB-CU shall update the information about the cells, as described in TS 38.401. If if the Switching Off Ongoing IE is present in the Cells Status Item IE, contained in the GNB-DU CONFIGURATION UPDATE message, and the corresponding Service State IE is set to "Out-of-Service", the gNB-CU shall ignore the Switching Off Ongoing IE.
If Cells to be Activated List Item IE is contained in the GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message, the gNB-DU shall activate the cell indicated by NR CGI 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 contained in the GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message and the indicated cells are already activated, the gNB-DU shall update the cell information received in Cells to be Activated List Item IE.
If Cells to be Activated List Item IE is included in the GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE 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.
If Cells to be Deactivated List Item IE is contained in the GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message, the gNB-DU shall deactivate all the cells with NR CGI listed in the IE.
If Dedicated SI Delivery Needed UE List IE is contained in the GNB-DU CONFIGURATION UPDATE message, the gNB-CU should take it into account when informing the UE of the updated system information via the dedicated RRC message.
For NG-RAN, the gNB-CU shall include the gNB-CU System Information IE in the GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message. The SIB type to Be Updated List IE shall contain the full list of SIBs to be broadcast.
For NG-RAN, the gNB-DU may include the RAN Area Code IE in the GNB-DU CONFIGURATION UPDATE message. The gNB-CU shall store and replace any previously provided RAN Area Code IE by the received RAN Area Code IE.
If Available PLMN List IE, and optionally also Extended Available PLMN List IE, is contained in GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message, the gNB-DU shall overwrite the whole available PLMN list and update the corresponding system information.
If Available SNPN ID List IE is contained in GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message, the gNB-DU shall overwrite the whole available SNPN ID list and update the corresponding system information.
If in GNB-DU CONFIGURATION UPDATE 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 GNB-DU CONFIGURATION UPDATE 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 GNB-DU CONFIGURATION UPDATE message includes gNB-DU TNL Association To Remove List IE, and the Endpoint IP address IE and the Port Number IE for both TNL endpoints of the TNL association(s) are included in the gNB-DU TNL Association To Remove List IE, the gNB-CU shall, if supported, consider that the TNL association(s) indicated by both received TNL endpoints will be removed by the gNB-DU. If the Endpoint IP address IE, or the Endpoint IP address IE and the Port Number IE for one or both of the TNL endpoints is included in the gNB-DU TNL Association To Remove List IE in GNB-DU CONFIGURATION UPDATE message, the gNB-CU shall, if supported, consider that the TNL association(s) indicated by the received endpoint IP address(es) will be removed by the gNB-DU.
If the Intended TDD DL-UL Configuration IE is present in the GNB-DU CONFIGURATION UPDATE 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 IE 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 GNB-DU CONFIGURATION UPDATE 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 GNB-DU CONFIGURATION UPDATE message, the gNB-CU shall, if supported, take it into account.
If the GNB-DU CONFIGURATION UPDATE message includes Transport Layer Address Info IE, the gNB-CU shall, if supported, take into account for IPSec tunnel establishment.
If the GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message includes Transport Layer Address Info IE, the gNB-DU shall, if supported, take into account for IPSec tunnel establishment.
If the GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE 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.
Up

8.2.4.3  Unsuccessful OperationWord‑p. 30
Reproduction of 3GPP TS 38.473, Figure 8.2.4.3-1: gNB-DU Configuration Update procedure: Unsuccessful Operation
Up
If the gNB-CU cannot accept the update, it shall respond with a GNB-DU CONFIGURATION UPDATE FAILURE message and appropriate cause value.
If the GNB-DU CONFIGURATION UPDATE FAILURE message includes the Time To Wait IE, the gNB-DU shall wait at least for the indicated time before reinitiating the GNB-DU CONFIGURATION UPDATE message towards the same gNB-CU.

8.2.4.4  Abnormal Conditions

Not applicable.

8.2.5  gNB-CU Configuration Update

8.2.5.1  General

The purpose of the gNB-CU Configuration Update procedure is to update application level configuration data needed for the gNB-DU and gNB-CU to interoperate correctly on the F1 interface. This procedure does not affect existing UE-related contexts, if any. The procedure uses non-UE associated signalling.

8.2.5.2  Successful Operation

Reproduction of 3GPP TS 38.473, Figure 8.2.5.2-1: gNB-CU Configuration Update procedure: Successful Operation
Up
The gNB-CU initiates the procedure by sending a GNB-CU CONFIGURATION UPDATE message including the appropriate updated configuration data to the gNB-DU. The gNB-DU responds with a GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE message to acknowledge that it successfully updated the configuration data. If an information element is not included in the GNB-CU CONFIGURATION UPDATE message, the gNB-DU shall interpret that the corresponding configuration data is not changed and shall continue to operate the F1-C interface with the existing related configuration data.
The updated configuration data shall be stored in the respective node and used as long as there is an operational TNL association or until any further update is performed.
If Cells to be Activated List Item IE is contained in the GNB-CU CONFIGURATION UPDATE message, the gNB-DU shall activate the cell indicated by NR CGI IE and reconfigure the physical cell identity for which the NR PCI IE is included.
If Cells to be Deactivated List Item IE is contained in the GNB-CU CONFIGURATION UPDATE message, the gNB-DU shall deactivate the cell indicated by NR CGI IE.
If Cells to be Activated List Item IE is contained in the GNB-CU CONFIGURATION UPDATE message and the indicated cells are already activated, the gNB-DU shall update the cell information received in Cells to be Activated List Item IE.
If Cells to be Activated List Item IE is included in the GNB-CU CONFIGURATION UPDATE 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.
If the gNB-CU System Information IE is contained in the gNB-CU CONFIGURATION UPDATE message, the gNB-DU shall include the Dedicated SI Delivery Needed UE List IE in the GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE message for UEs that are unable to receive system information from broadcast.
If Dedicated SI Delivery Needed UE List IE is contained in the GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE message, the gNB-CU should take it into account when informing the UE of the updated system information via the dedicated RRC message.
If the gNB-CU TNL Association To Add List IE is contained in the gNB-CU CONFIGURATION UPDATE message, the gNB-DU shall, if supported, use it to establish the TNL association(s) with the gNB-CU. The gNB-DU shall report to the gNB-CU, in the gNB-CU CONFIGURATION UPDATE ACKNOWLEDGE message, the successful establishment of the TNL association(s) with the gNB-CU as follows:
  • A list of TNL address(es) with which the gNB-DU successfully established the TNL association shall be included in the gNB-CU TNL Association Setup List IE;
  • A list of TNL address(es) with which the gNB-DU failed to establish the TNL association shall be included in the gNB-CU TNL Association Failed To Setup List IE.
If the GNB-CU CONFIGURATION UPDATE message includes gNB-CU TNL Association To Remove List IE, and the Endpoint IP address IE and the Port Number IE for both TNL endpoints of the TNL association(s) are included in the gNB-CU TNL Association To Remove List IE, the gNB-DU shall, if supported, initiate removal of the TNL association(s) indicated by both received TNL endpoints towards the gNB-CU. If the Endpoint IP address IE, or the Endpoint IP address IE and the Port Number IE for one or both of the TNL endpoints is included in the gNB-CU TNL Association To Remove List IE, the gNB-DU shall, if supported, initiate removal of the TNL association(s) indicated by the received endpoint IP address(es).
If the gNB-CU TNL Association To Update List IE is contained in the gNB-CU CONFIGURATION UPDATE message the gNB-DU shall, if supported, overwrite the previously stored information for the related TNL Association(s).
If in the gNB-CU CONFIGURATION UPDATE message the TNL Association usage IE is included in the gNB-CU TNL Association To Add List IE or the gNB-CU TNL Association To Update List IE, the gNB-DU node shall, if supported, use it as described in TS 38.472.
For NG-RAN, the gNB-CU shall include the gNB-CU System Information IE in the GNB-CU CONFIGURATION UPDATE message. The SIB type to Be Updated List IE shall contain the full list of SIBs to be broadcast.
If Protected E-UTRA Resources List IE is contained in the GNB-CU CONFIGURATION UPDATE message, the gNB-DU shall protect the corresponding resource of the cells indicated by E-UTRA Cells List IE for spectrum sharing between E-UTRA and NR.
If the GNB-CU CONFIGURATION UPDATE message contains the Protected E-UTRA Resource Indication IE, the receiving gNB-DU should forward it to lower layers and use it for cell-level resource coordination. The gNB-DU shall consider the received Protected E-UTRA Resource Indication IE when expressing its desired resource allocation during gNB-DU Resource Coordination procedure. The gNB-DU shall consider the received Protected E-UTRA Resource Indication IE content valid until reception of a new update of the IE for the same gNB-DU.
If Available PLMN List IE, and optionally also Extended Available PLMN List IE, is contained in GNB-CU CONFIGURATION UPDATE message, the gNB-DU shall overwrite the whole available PLMN list and update the corresponding system information.
If Available SNPN ID List IE is contained in GNB-CU CONFIGURATION UPDATE message, the gNB-DU shall overwrite the whole available SNPN ID list and update the corresponding system information.
If Cells Failed to be Activated Item IE is contained in the GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE message, the gNB-CU shall consider that the indicated cells are out-of-service as defined in TS 38.401.
If the Neighbour Cell Information List IE is present in the GNB-CU CONFIGURATION UPDATE message, the receiving gNB-DU shall use the received information for Cross Link Interference management and/or NR-DC power coordination. The gNB-DU shall consider the received Neighbour Cell Information List IE content valid until reception of an update of the IE for the same cell(s). If the Intended TDD DL-UL Configuration NR IE is absent from the Neighbour Cell Information List IE, whereas the corresponding NR CGI IE is present, the receiving gNB-DU shall remove the previously stored Neighbour Cell Information IE corresponding to the NR CGI.
If the GNB-CU CONFIGURATION UPDATE message includes Transport Layer Address Info IE, the gNB-DU shall, if supported, take into account for IPSec tunnel establishment.
If the GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE message includes Transport Layer Address Info IE, the gNB-CU shall, if supported, take into account for IPSec tunnel establishment.
If the GNB-CU CONFIGURATION UPDATE 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 IAB Barred IE is included in the GNB-CU CONFIGURATION UPDATE message, the gNB-DU shall, if supported, consider it as an indication of whether the cell allows IAB-node access or not.
Up

8.2.5.3  Unsuccessful OperationWord‑p. 32
Reproduction of 3GPP TS 38.473, Figure 8.2.5.3-1: gNB-CU Configuration Update: Unsuccessful Operation
Up
If the gNB-DU cannot accept the update, it shall respond with a GNB-CU CONFIGURATION UPDATE FAILURE message and appropriate cause value.
If the GNB-CU CONFIGURATION UPDATE FAILURE message includes the Time To Wait IE, the gNB-CU shall wait at least for the indicated time before reinitiating the GNB-CU CONFIGURATION UPDATE message towards the same gNB-DU.

8.2.5.4  Abnormal Conditions

Not applicable.

Up   Top   ToC