Bearer resource modification request

38.463 3GPP E1 Application Protocol (E1AP) NG-RAN Release 16 TS

8.3.1 Bearer Context Setup

8.3.1.1 General

The purpose of the Bearer Context Setup procedure is to allow the gNB-CU-CP to establish a bearer context in the gNB-CU-UP. The procedure uses UE-associated signalling.

8.3.1.2 Successful Operation

Figure 8.3.1.3-1: Bearer Context Setup procedure: Unsuccessful Operation.

If the gNB-CU-UP cannot establish the requested bearer context, or cannot even establish one bearer it shall consider the procedure as failed and respond with a BEARER CONTEXT SETUP FAILURE message and appropriate cause value.

8.3.1.4 Abnormal Conditions

If the gNB-CU-UP receives a BEARER CONTEXT SETUP REQUEST message containing a E-UTRAN QoS IE in the DRB To Setup List IE for a GBR QoS DRB but where the GBR QoS Information IE is not present, the gNB-CU-UP shall report the establishment of the corresponding DRB as failed in the DRB Failed List IE of the BEARER CONTEXT SETUP RESPONSE message with an appropriate cause value.

If the gNB-CU-UP receives a BEARER CONTEXT SETUP REQUEST message containing a QoS Flow Level QoS Parameters IE in the PDU Session Resource To Setup List IE for a GBR QoS Flow but where the GBR QoS Flow Information IE is not present, the gNB-CU-UP shall report the establishment of the corresponding QoS Flow as failed in the corresponding Flow Failed List IE of the BEARER CONTEXT SETUP RESPONSE message with an appropriate cause value.

8.3.2 Bearer Context Modification (gNB-CU-CP initiated)

8.3.2.1 General

The purpose of the Bearer Context Modification procedure is to allow the gNB-CU-CP to modify a bearer context in the gNB-CU-UP. The procedure uses UE-associated signalling.

8.3.2.2 Successful Operation

Figure 8.3.4.2-1: Bearer Context Release procedure: Successful Operation.

The gNB-CU-CP initiates the procedure by sending the BEARER CONTEXT RELEASE COMMAND message to the gNB-CU-UP. The gNB-CU-UP replies with the BEARER CONTEXT RELEASE COMPLETE message.

Upon reception of the BEARER CONTEXT RELEASE COMMAND message, the gNB-CU-UP shall release all related signalling and user data transport resources and reply with the BEARER CONTEXT RELEASE COMPLETE message.

The gNB-CU-UP shall, if supported, include the Retainability Measurements Information IE in the BEARER CONTEXT RELEASE COMPLETE message, providing information on the removed DRB(s) for retainability measurements in the gNB-CU-CP, as described in TS 32.425 [26] and TS 28.552 [22].

8.3.4.3 Abnormal Conditions

8.3.5 Bearer Context Release Request (gNB-CU-UP initiated)

8.3.5.1 General

The purpose of the Bearer Context Release Request procedure is to allow the gNB-CU-UP to request the gNB-CU-CP to release an UE-associated logical E1 connection. The procedure uses UE-associated signalling.

8.3.5.2 Successful Operation

Figure 8.3.8.2-1: Data Usage Report procedure: Successful Operation.

The gNB-CU-UP initiates the procedure by sending the DATA USAGE REPORT message to the gNB-CU-CP.

8.3.8.3 Abnormal Conditions

8.3.9 gNB-CU-UP Counter Check

8.3.9.1 General

This procedure is initiated by the gNB-CU-UP to request the gNB-CU-CP to execute a counter check procedure to verify the value of the PDCP COUNTs associated with DRBs established in the gNB-CU-UP.

The procedure uses UE-associated signalling.

8.3.9.2 Successful Operation

Figure 8.3.10.2-1: UL Data Notification procedure: Successful Operation.

The gNB-CU-UP initiates the procedure by sending the UL DATA NOTIFICATION message to the gNB-CU-CP.

8.3.10.3 Abnormal Conditions

8.3.11 MR-DC Data Usage Report

8.3.11.1 General

This procedure is initiated by the gNB-CU-UP to report data volume served at the gNB-CU-UP, where the UE is connected to the 5GC. The procedure uses UE-associated signalling.