Content for  TS 37.483  Word version:  18.2.0

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.

The gNB-CU-CP initiates the procedure by sending the BEARER CONTEXT MODIFICATION REQUEST message to the gNB-CU-UP. If the gNB-CU-UP succeeds to modify the bearer context, it replies to the gNB-CU-CP with the BEARER CONTEXT MODIFICATION RESPONSE message. The gNB-CU-UP shall report to the gNB-CU-CP, in the BEARER CONTEXT MODIFICATION RESPONSE message, the result for all the requested resources in the following way: When the gNB-CU-UP reports the unsuccessful establishment of a PDU Session Resource, DRB or QoS Flow the cause value should be precise enough to enable the gNB-CU-CP to know the reason for the unsuccessful establishment. If the Security Information IE is contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall update the corresponding information. If the UE DL Aggregate Maximum Bit Rate IE is contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall update the corresponding information. If the UE DL Maximum Integrity Protected Data Rate IE is contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall update the corresponding information. If the Bearer Context Status Change IE is contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall consider the UE RRC state and act as specified in TS 38.401. If the Bearer Context Status Change IE is set to "ResumeforSDT", the gNB-CU-UP shall consider that DRBs configured with SDT are resumed only and the other DRBs remain suspended. If SDT Continue ROHC IE is contained in the BEARER CONTEXT MODIFICATION REQUEST message and the value is set to "true", the gNB-CU-UP shall, if supported, continue the ROHC for the SDT bearers for the UE. If the Data Forwarding Information Request IE, PDU Session Data Forwarding Information Request IE or the DRB Data Forwarding Information Request IE are included in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall include the requested forwarding information in the Data Forwarding Information Response IE, PDU Session Data Forwarding Information Response IE or the DRB Data Forwarding Information Response IE in the BEARER CONTEXT MODIFICATION RESPONSE message. If the PDU Session Data Forwarding Information IE is included in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, consider that data forwarding is applicable for the indicated QoS flows for the concerned PDU session. If the Secondary PDU Session Data Forwarding Information IE is included in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, consider that data forwarding is applicable for the indicated QoS flows for the concerned PDU session. If the PDCP Configuration IE is contained in the DRB To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall update the corresponding information, except for the PDCP SN UL Size IE, the PDCP SN DL Size IE and the RLC mode IE which shall be ignored. If the E-UTRAN QoS IE is contained in the DRB To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall update the corresponding information. If the PDCP SN Status Request IE is contained in the DRB To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall act as specified in TS 38.401 and include the UL COUNT Value IE and the DL COUNT Value IE in the BEARER CONTEXT MODIFICATION RESPONSE message. If the PDCP SN Status Information IE is contained in the DRB To Setup List IE or the DRB To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall take it into account and act as specified in TS 38.401. If the DL UP Parameters IE is contained in the DRB To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall update the corresponding information. If the Indirect Path Indication IE is contained in the DL UP Parameters IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, act as specified in TS 38.401. If the PDCP COUNT Reset IE is contained within the DRB To Modify List IE for a DRB of the PDU Session Resource To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, reset the PDCP COUNT value for this DRB (i.e. its HFN and PDCP-SN to value "0"). If the Cell Group To Add IE or the Cell Group To Modify IE or the Cell Group To Remove IE is contained in the DRB To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall add or modify or remove the corresponding cell group. If the PDU Session Resource DL Aggregate Maximum Bit Rate IE is contained in the PDU Session Resource To Setup List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall replace the information in the UE context and use it when enforcing downlink traffic policing for the non GBR QoS flows for the concerned UE, as specified in TS 23.501. If the PDU Session Resource DL Aggregate Maximum Bit Rate IE is contained in the PDU Session Resource To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall update the corresponding information. If the SDAP Configuration IE is contained in the DRB To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall update the corresponding information. If the Flow Mapping Information IE is contained in the DRB To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall update the corresponding information. For each requested DRB, if the PDCP Duplication IE or Additional PDCP duplication Information IE is included in the PDCP Configuration IE contained in the BEARER CONTEXT MODIFICATION REQUEST message, then the gNB-CU-CP shall include two or more UP Transport Layer Information IEs in the BEARER CONTEXT MODIFICATION REQUEST message, and the gNB-CU-UP shall, if supported, also include two or more UP Transport Layer Information IEs in the BEARER CONTEXT MODIFICATION RESPONSE message to support packet duplication. If only one cell group is included in the Cell Group Information IE for the concerned DRB, then the gNB-CU-UP shall consider that the first UP Transport Layer Information IE of these UP Transport Layer Information IEs is for the primary path. If more than one cell group is included in the Cell Group Information IE, then the gNB-CU-UP shall consider that the number of duplication tunnels for each cell group is indicated by the Number of tunnels IE, and that the first UP Transport Layer Information IE for each cell group is for the primary path or the split secondary path. For a certain DRB which was allocated with two or more GTP-U tunnels, if such DRB is modified and given one GTP-U tunnel via the Bearer Context Modification (gNB-CU-CP initiated) procedure, i.e. only one UP Transport Layer Information per Cell Group ID is present in DL UP Parameters IE for the concerned DRB, then the gNB-CU-UP shall consider that PDCP duplication is deconfigured for this DRB. If such Bearer Context Modification (gNB-CU-CP initiated) procedure occurs, the Duplication Activation IE shall not be included for the concerned DRB. If the New UL TNL Information Required IE is contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall include the new UP Transport Layer Information in the BEARER CONTEXT MODIFICATION RESPONSE message. For each PDU session for which the Security Indication IE is included in the PDU Session Resource To Setup List IE or the Security Indication Modify IE is included in the PDU Session Resource To Modify List IE of the BEARER CONTEXT MODIFICATION REQUEST message, and the Integrity Protection Indication IE or Confidentiality Protection Indication IE is set to "preferred", then the gNB-CU-UP should, if supported, perform user plane integrity protection or ciphering, respectively, for the concerned PDU session and shall notify whether it performed the user plane integrity protection or ciphering by including the Integrity Protection Result IE or Confidentiality Protection Result IE, respectively, in the PDU Session Resource Setup List IE or the PDU Session Resource Modified List IE of the BEARER CONTEXT MODIFICATION RESPONSE message. For each PDU session for which the Security Indication IE is included in the PDU Session Resource To Setup List IE or the Security Indication Modify IE is included in the PDU Session Resource To Modify List IE of the BEARER CONTEXT MODIFICATION REQUEST message, and the Integrity Protection Indication IE or Confidentiality Protection Indication IE is set to "required", then the gNB-CU-UP shall perform user plane integrity protection or ciphering, respectively, for the concerned PDU Session. If the gNB-CU-UP cannot perform the user plane integrity protection or ciphering, it shall reject the setup of the PDU Session Resources with an appropriate cause value. For each PDU session for which the Security Indication IE is included in the PDU Session Resource To Setup List IE or the Security Indication Modify IE is included in the PDU Session Resource To Modify List IE of the BEARER CONTEXT MODIFICATION REQUEST message:

• if the Integrity Protection Indication IE is set to "not needed", then the gNB-CU-UP shall not perform user plane integrity protection for the concerned PDU session;
• if the Confidentiality Protection Indication IE is set to "not needed", then the gNB-CU-UP shall not perform user plane ciphering for the concerned PDU session.

For E-UTRAN:

• For each DRB for which the Security Indication IE is included in the DRB To Setup List IE of the BEARER CONTEXT MODIFICATION REQUEST message, and the Integrity Protection Indication IE is set to "preferred", then the gNB-CU-UP should, if supported, perform user plane integrity protection for the concerned DRB and notify whether it performed the user plane integrity protection by including the Integrity Protection Result IE in the DRB Setup List IE of the BEARER CONTEXT MODIFICATION RESPONSE message.
• For each DRB for which the Security Indication IE is included in the DRB To Setup List IE of the BEARER CONTEXT MODIFICATION REQUEST message, and the Integrity Protection Indication IE is set to "required", then the gNB-CU-UP shall, if supported, perform user plane integrity protection for the concerned DRB. If the gNB-CU-UP cannot perform the user plane integrity protection, it shall reject the setup of the DRB with an appropriate cause value.
• For each DRB for which the Security Indication IE is included in the DRB To Setup List IE of the BEARER CONTEXT MODIFICATION REQUEST message and the Integrity Protection Indication IE is set to "not needed", then the gNB-CU-UP shall not perform user plane integrity protection for the concerned DRB.

For each PDU Session Resource, if the Network Instance IE is included in the PDU Session Resource To Setup List IE or the PDU Session Resource To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message and the Common Network Instance IE is not included, the gNB-CU-UP shall, if supported, use it when selecting transport network resource as specified in TS 23.501. For each PDU session, if the Common Network Instance IE is included in the PDU Session Resource To Setup List IE or the PDU Session Resource To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, use it when selecting transport network resource as specified in TS 23.501. For each PDU session, if the Redundant NG UL UP Transport Layer Information IE is included in the PDU Session Resource To Setup List IE or the PDU Session Resource To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, include the Redundant NG DL UP Transport Layer Information IE in the PDU Session Resource Setup List IE or the PDU Session Resource Modified List IE in the BEARER CONTEXT MODIFICATION RESPONSE message. If the Redundant Common Network Instance IE is included in the PDU Session Resource To Setup List IE or the PDU Session Resource To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, use it when selecting transport network resource for the redundant transmission as specified in TS 23.501. For each PDU session for which the Redundant QoS Flow Indicator IE is included in QoS Flows Information To Be Setup IE contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if support, shall store and use it as specified in TS 23.501. For each PDU session, if the Redundant QoS Flow Indicator IE is set to false for all QoS flows, the gNB-CU-UP shall, if supported, stop the redundant transmission and release the redundant tunnel for the concerned PDU session as specified in TS 23.501. For each PDU session, if the Data Forwarding to E-UTRAN Information List IE is included in the PDU Session Resource To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, use it for inter-system data forwarding from 5GS to EPS as specified in TS 38.300. If the Special Triggering Purpose IE is included in PDU Session Resource To Setup Modification List IE contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP may store the bearer context information and consider that the setup of the DRB or the PDU session for which the IE is included is for the purpose of indirect data forwarding. If the Special Triggering Purpose IE is included in PDU Session Resource To Modify List IE contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP may store the bearer context information and consider that the setup of the DRB for which the IE is included is for the purpose of indirect data forwarding. If the QoS Flow Mapping Indication IE is contained in the QoS Flow QoS Parameters List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, replace any previously received value and take it into account that only the uplink or downlink QoS flow is mapped to the DRB. If the Data Discard Required IE is contained in the BEARER CONTEXT MODIFICATION REQUEST message and the value is set to "Required", the gNB-CU-UP shall consider that a RAN Paging Failure occurred for that UE. The gNB-CU-UP shall discard the user plane data for that UE and consider that the bearer context is still suspended. If UE Inactivity Timer IE or PDU session Inactivity Timer IE or DRB Inactivity Timer IE is contained in BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall take it into account when perform inactivity monitoring. If the S-NSSAI IE is contained in the PDU Session Resource To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall store the corresponding information and replace any existing information. If the DRB QoS IE is contained within the DRB To Setup List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, take it into account for each DRB, as specified in TS 28.552. If the DRB QoS IE is contained within the DRB To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, replace any previously received value and take it into account for each DRB, as specifed in TS 28.552. If the gNB-DU-ID IE is contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall store and replace any previous information received. If the RAN UE ID IE is contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall store and replace any previous information received. If the gNB-CU-UP receives a BEARER CONTEXT MODIFICATION REQUEST message including Activity Notification Level IE and its value does not match the current bearer context, the gNB-CU-UP shall ignore the Activity Notification Level IE and also the requested modification of inactivity timer. For each successfully established DRB, the gNB-CU-UP shall provide, in the respective UL UP Parameters IE of the BEARER CONTEXT MODIFICATION RESPONSE, one UL UP Transport Layer Information Item per cell group entry contained in the respective Cell Group Information IE of the BEARER CONTEXT MODIFICATION REQUEST message. If the Old QoS Flow List - UL End Marker expected IE is included in the PDU Session Resource To Modify List IE of the BEARER CONTEXT MODIFICATION REQUEST message for a DRB to be modified, the gNB-CU-UP shall consider that the source NG-RAN node has initiated QoS flow re-mapping and has not yet received SDAP end markers, as described in TS 38.300. The gNB-CU-UP shall consider that the Old QoS Flow List - UL End Marker expected IE only contains UL QoS flow information for QoS flows for which no SDAP end marker has been yet received on the source side. For EN-DC, if the Subscriber Profile ID for RAT/Frequency priority IE is included in the BEARER CONTEXT MODIFICATION REQUEST, the gNB-CU-UP may use it to apply specific RRM policies as specified in TS 36.300. If the Additional RRM Policy Index IE is included in the BEARER CONTEXT MODIFICATION REQUEST, the gNB-CU-UP may use it to apply specific RRM policies as specified in TS 36.300. If there is at least one DRB removed by the gNB-CU-UP, the gNB-CU-UP shall, if supported, include the Retainability Measurements Information IE in the BEARER CONTEXT MODIFICATION RESPONSE message, providing information on the removed DRB(s) for retainability measurements in the gNB-CU-CP, as described in TS 32.425 and TS 28.552. If the TSC Traffic Characteristics IE is included in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, take into account the corresponding information received in the TSC Traffic Characteristics IE. For each QoS flow whose DRB has been successfully established or modified and the QoS Monitoring Request IE was included in the QoS Flow Level QoS Parameters IE contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall store this information, and, if supported, perform delay measurement and QoS monitoring, as specified in TS 23.501. If the QoS Monitoring Reporting Frequency IE was included in the QoS Flow Level QoS Parameters IE contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall store this information, and, if supported, use it for RAN part delay reporting. For each QoS flow whose DRB has been successfully established or modified in the gNB-CU-UP, if the ECN Marking or Congestion Information Reporting Request IE is included in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, use it accordingly for the specific QoS flow. If the ECN Marking or Congestion Information Reporting Status IE is included in the Flow Setup List IE contained in the PDU Session Resource Setup List IE or the PDU Session Resource Modified List IE of the BEARER CONTEXT MODIFICATION RESPONSE message, the gNB-CU-CP shall, if supported, use it to deduce if ECN marking at NG-RAN or ECN marking at UPF or congestion information reporting is active or not active. For each requested DRB, if the QoS Mapping Information IE is contained in the DL UP Parameters IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall use it to set DSCP and/or flow label fields in the downlink IP packets which are transmitted through the GTP tunnels indicated by the UP Transport Layer Information IE. The Diffserv code point (DSCP) marking is performed as specified in TS 38.474. If the Early Forwarding COUNT Request IE is contained in the DRB To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall act as specified in TS 38.401 and include the requested FIRST DL COUNT Value IE or DISCARD DL COUNT Value IE in the BEARER CONTEXT MODIFICATION RESPONSE message. If the Early Forwarding COUNT Information IE is contained in the DRB To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall take it into account and act as specified in TS 38.401. If the Ignore Mapping Rule Indication IE is contained within the DRB To Setup List IE for a DRB in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, ignore the QoS flow mapping information indicated by the QoS Flows Information To Be Setup IE for the concerned DRB. If the DAPS Request Information IE is included for a DRB to be modified in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall consider that the request concerns a DAPS handover for that DRB and, if admitted, act as specified in TS 38.300. If the Early Data Forwarding Indicator IE set to "stop" is contained in the DRB To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported and if already initiated, stop the early data forwarding for the concerned DRB. If the DRB Data forwarding information IE containing the DL Data Forwarding IE is included together in the DRB To Modify List IE, the gNB-CU-UP shall consider that the stop is only for the early data forwarding initiated toward that forwarding TNL. If the MDT Polluted Measurement Indicator IE is included in the BEARER CONTEXT MODIFICATION REQUEST, the gNB-CU-UP shall take this information into account as specified in TS 38.401. If the UE Slice Maximum Bit Rate List IE is contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, store and replace the previously provided UE Slice Maximum Bit Rate List by the received UE Slice Maximum Bit Rate List in the UE context, and use the received UE Slice Maximum Bit Rate List for the downlink traffic policing for each concerned slice as specified in TS 23.501. If the SCG Activation Status IE is contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall take it into account when handling DL data transfer as specified in TS 37.340. If the UDC parameters IE is included in the PDCP Configuration IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, take these parameters into account to perform appropriate uplink data compression for the concerned DRB. If the Data Forwarding Source IP Address IE is included in the DRB To Setup Modification List E-UTRAN IE or in the QoS Flow Level QoS Parameters IE within the PDU Session Resource To Setup Modification List IE and the PDU Session Resource To Modify List IE contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, store this information in the UE context and use it as part of its ACL functionality configuration actions, if such ACL functionality is deployed. If the Data Forwarding Source IP Address IE is included in the DRB Setup Modification List E-UTRAN IE or in the Flow Setup List IE within the PDU Session Resource Setup Modification List IE and the PDU Session Resource Modified List IE of the BEARER CONTEXT MODIFICATION RESPONSE message, the gNB-CU-CP shall, if supported, store this information in the UE context and use it as part of its ACL functionality configuration actions, if such ACL functionality is deployed. If the Management Based MDT PLMN Modification List IE is contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, overwrite any previously stored Management Based MDT PLMN List information in the UE context and use the received information to determine subsequent selection of the UE for management based MDT defined in TS 32.422. If the Inactivity Information Request IE is contained in the BEARER CONTEXT MODIFICATION REQUEST, the gNB-CU-UP shall, if supported, include the UE Inactivity Information IE in the BEARER CONTEXT MODIFICATION RESPONSE message. If the PDU Set QoS Parameters IE is contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, store it and use the information as specified in TS 23.501. For a QoS flow established with PDU Set QoS parameters, if the PDU Set based Handling Indicator IE is included in the PDU Session Data Forwarding Information IE within the BEARER CONTEXT MODIFICATION REQUEST message and the value of the PDU Set based Handling Indicator IE is set to "supported", the gNB-CU-UP shall, if supported, include the PDU Set Information Container in the data to be forwarded. For each PDU session, if the User Plane Failure Indication IE is included in the PDU Session Resource To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, allocate the new NG-U DL endpoint address for the concerned GTP-U tunnel as specified in TS 23.527. Interactions with DL Data Notification procedure: If the MT-SDT Information Request IE is included in the BEARER CONTEXT MODIFICATION REQUEST message and the value is set to 'true', the gNB-CU-UP shall, if supported, store it and report the MT-SDT Information IE in the DL DATA NOTIFICATION message as specified in TS 38.401. If the SDT Data Size Threshold IE is included in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, store it and act as specified in TS 38.401. Interaction with the Bearer Context Modification (gNB-CU-CP initiated) If the BEARER CONTEXT MODIFICATION REQUEST message includes for a DRB in the DRB To Modify List IE the PDCP SN Status Request IE set to "requested" and if the gNB-CU-UP has not yet received a SDAP end marker packet for a QoS flow which has been previously re-configured to another DRB by means of a gNB-CU-CP initiated Bearer Context Modification procedure, the gNB-CU-UP shall includes the QoS Flow Identifier of that QoS flow in the Old QoS Flow List - UL End Marker expected IE in the PDU Session Resource Modified List IE in the BEARER CONTEXT MODIFICATION RESPONSE message.

If the gNB-CU-UP cannot successfully perform any of the requested bearer context modifications, or cannot handle SCG with the indicated activated or deactivated status, it shall respond with a BEARER CONTEXT MODIFICATION FAILURE message and appropriate cause value. If the gNB-CU-UP receives a BEARER CONTEXT MODIFICATION REQUEST message containing the Security Indication Modify IE in the PDU Session Resource To Modify List IE for a PDU session that may result in the change of security status that has been applied but the DRBs that have been established for that PDU session are not requested to be released via the DRB To Remove List IEs as specified in TS 38.331, then the gNB-CU-UP shall respond with a BEARER CONTEXT MODIFICATION FAILURE message and appropriate cause value. If the gNB-CU-UP receives a BEARER CONTEXT MODIFICATION REQUEST message containing the PDCP COUNT Reset IE in the DRB To Modify List IE of the PDU Session Resource To Modify List IE but if the Security Information IE is not present, then the gNB-CU-UP shall respond with a BEARER CONTEXT MODIFICATION FAILURE message and appropriate cause value.

If the gNB-CU-UP receives a BEARER CONTEXT MODIFICATION REQUEST message containing a E-UTRAN QoS IE in the DRB To Setup List or the DRB To Modify List IE for a GBR QoS DRB but where the GBR QoS Information IE is not present, the gNB-CU-UP shall report the addition or the modification of the corresponding DRB as failed in the DRB Failed List IE or the DRB Failed To Modify List IE of the BEARER CONTEXT MODIFICATION RESPONSE message with an appropriate cause value. If the gNB-CU-UP receives a BEARER CONTEXT MODIFICATION REQUEST message containing a QoS Flow Level QoS Parameters IE in the PDU Session Resource To Setup List IE or the PDU Session Resource To Modify 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 addition or the modification of the corresponding QoS Flow as failed in the corresponding Flow Failed List IE of the BEARER CONTEXT MODIFICATION RESPONSE message with an appropriate cause value.