The purpose of the gNB-CU-CP Configuration Update procedure is to update application level configuration data needed for the gNB-CU-CP and the gNB-CU-UP to interoperate correctly on the E1 interface. This procedure does not affect existing UE-related contexts, if any. The procedure uses non-UE associated signalling.
The gNB-CU-CP initiates the procedure by sending a GNB-CU-CP CONFIGURATION UPDATE message to the gNB-CU-UP including an appropriate set of updated configuration data that it has just taken into operational use. The gNB-CU-UP responds with GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE message to acknowledge that it successfully updated the configuration data. If an information element is not included in the GNB-CU-CP CONFIGURATION UPDATE message, the gNB-CU-UP shall interpret that the corresponding configuration data is not changed and shall continue to operate 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 the
gNB-CU-CP Name IE is included in the GNB-CU-CP CONFIGURATION UPDATE message, the
gNB-CU-UP may store it or update this IE value if already stored, and use it as a human readable name of the gNB-CU-CP. If the
Extended gNB-CU-CP Name IE is included in the GNB-CU-CP CONFIGURATION UPDATE message, the
gNB-CU-UP may store it or update this IE value if already stored, and use it as a human readable name of the gNB-CU-CP and shall ignore the
gNB-CU-CP Name IE if also included.
If the
gNB-CU-CP TNLA To Add List IE is contained in the gNB-CU-CP CONFIGURATION UPDATE message, the gNB-CU-UP shall, if supported, use it to establish the TNL association(s) with the gNB-CU-CP. The gNB-CU-UP shall report to the gNB-CU-CP, in the gNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE message, the successful establishment of the TNL association(s) with the gNB-CU-CP as follows:
-
A list of TNL address(es) with which the gNB-CU-UP successfully established the TNL association shall be included in the gNB-CU-CP TNLA Setup List IE;
-
A list of TNL address(es) with which the gNB-CU-UP failed to establish the TNL association shall be included in the gNB-CU-CP TNLA Failed To Setup List IE.
If the
GNB-CU-CP CONFIGURATION UPDATE message includes gNB-CU-CP TNLA 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-CP TNLA To Remove List IE, the gNB-CU-UP shall, if supported, initiate removal of the TNL association(s) indicated by both received TNL endpoints towards the gNB-CU-CP. 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-CP TNLA To Remove List IE, the gNB-CU-UP shall, if supported, initiate removal of the TNL association(s) indicated by the received endpoint IP address(es).
If the
gNB-CU-CP TNLA To Update List IE is contained in the gNB-CU-CP CONFIGURATION UPDATE message the gNB-CU-UP shall, if supported, overwrite the previously stored information for the related TNL association.
If the
TNLA Usage IE is included in the
gNB-CU-CP TNLA To Add List IE or the
gNB-CU-CP TNLA To Update List IE in the gNB-CU-CP CONFIGURATION UPDATE message, the gNB-CU-UP shall, if supported, use it as described in
TS 37.482.
If the GNB-CU-CP CONFIGURATION UPDATE message includes the
Transport Network Layer Address Info IE, the
gNB-CU-UP shall, if supported, take this IE into account for IPSec tunnel establishment.
If the GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE message includes the
Transport Network Layer Address Info IE, the
gNB-CU-CP shall, if supported, take this IE into account for IPSec tunnel establishment.
If the gNB-CU-UP cannot accept the update, it shall respond with a GNB-CU-CP CONFIGURATION UPDATE FAILURE message and appropriate cause value.
If the GNB-CU-CP CONFIGURATION UPDATE FAILURE message includes the
Time To Wait IE, the gNB-CU-CP shall wait at least for the indicated time before reinitiating the GNB-CU-CP CONFIGURATION UPDATE message towards the same gNB-CU-UP.
Not applicable.