Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 38.463  Word version:  16.3.0

Top   Top   Up   Prev   Next
1…   4…   8…   8.2…   8.2.5…   8.3…   8.3.2   8.3.3…   8.4…   9…

 

8.3  Bearer Context Management procedures

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

Reproduction of 3GPP TS 38.463, Figure 8.3.1.2-1: Bearer Context Setup procedure: Successful Operation.
Up
The gNB-CU-CP initiates the procedure by sending the BEARER CONTEXT SETUP REQUEST message to the gNB-CU-UP. If the gNB-CU-UP succeeds to establish the requested resources, it replies to the gNB-CU-CP with the BEARER CONTEXT SETUP RESPONSE message.
The gNB-CU-UP shall report to the gNB-CU-CP, in the BEARER CONTEXT SETUP RESPONSE message, the result for all the requested resources in the following way:
For E-UTRAN:
  • A list of DRBs which are successfully established shall be included in the DRB Setup List IE;
  • A list of DRBs which failed to be established shall be included in the DRB Failed List IE;
For NG-RAN:
  • A list of PDU Session Resources which are successfully established shall be included in the PDU Session Resource Setup List IE;
  • A list of PDU Session Resources which failed to be established shall be included in the PDU Session Resource Failed List IE;
  • For each established PDU Session Resource, a list of DRBs which are successfully established shall be included in the DRB Setup List IE;
  • For each established PDU Session Resource, a list of DRBs which failed to be established shall be included in the DRB Failed List IE;
  • For each established DRB, a list of QoS Flows which are successfully established shall be included in the Flow Setup List IE;
  • For each established DRB, a list of QoS Flows which failed to be established shall be included in the Flow Failed List IE;
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 Existing Allocated NG DL UP Transport Layer Information IE is contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP may re-use the indicated resources already allocated for this bearer context. If the gNB-CU-UP decides to re-use the indicated resources, it shall include the NG DL UP Unchanged IE in the BEARER CONTEXT SETUP RESPONSE message.
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 SETUP REQUEST message, the gNB-CU-UP shall store and use the information for the down link traffic policing for the Non-GBR QoS flows for the concerned UE as specified in TS 23.501.
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 SETUP 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 SETUP RESPONSE message.
If the DL UP Parameters IE is contained in the DRB To Setup List IE in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall configure the corresponding information.
For each PDU session for which the Security Indication IE is included in the PDU Session Resource To Setup List IE of the BEARER CONTEXT SETUP 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 of the BEARER CONTEXT SETUP RESPONSE message.
For each PDU session for which the Security Indication IE is included in the PDU Session Resource To Setup List IE of the BEARER CONTEXT SETUP 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 of the BEARER CONTEXT SETUP 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.
If the UE DL Maximum Integrity Protected Data Rate IE is contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall use this value when enforcing the maximum integrity protected data rate for the UE.
If the Bearer Context Status Change IE is contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall consider the UE RRC state and act as specified in TS 38.401.
For each requested DRB, if the PDCP Duplication IE is included in the PDCP Configuration IE contained in the BEARER CONTEXT SETUP REQUEST message, and one cell group is included in Cell Group Information IE, then the gNB-CU-UP shall include two UP Transport Layer Information IEs in the BEARER CONTEXT SETUP RESPONSE message to support packet duplication for intra-gNB-DU CA. The first UP Transport Layer Information IE of the two UP Transport Layer Information IEs is for the primary path.
For each requested DRB, if the Additional PDCP duplication Information IE is included in the PDCP Configuration IE contained in the BEARER CONTEXT SETUP REQUEST message, and one cell group is included in Cell Group Information IE, then the gNB-CU-UP shall include the same number of UP Transport Layer Information IEs indicated by the Additional PDCP duplication Information IE in the BEARER CONTEXT SETUP RESPONSE message to support packet duplication for intra-gNB-DU CA. If more than one cell group is included in the Cell Group Information IE, then the gNB-CU-UP shall consider that the request concerns for DC-based packet duplication where 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.
If the PDCP SN Status Information IE is contained within the DRB To Setup List IE in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall take it into account and act as specified in TS 38.401.
If the QoS Flow Mapping Indication IE is contained in the QoS Flows Information To Be Setup IE within the DRB To Setup List IE in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP may take it into account that only the uplink or downlink QoS flow is mapped to the DRB.
For each PDU Session Resource, if the Network Instance IE is included in the PDU Session Resource To Setup List IE in the BEARER CONTEXT SETUP 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 in the BEARER CONTEXT SETUP 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 in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, use it as the uplink termination point of the redundant tunnel for the user plane data of those QoS flows in this PDU session which need redundant transmission as described in TS 23.501, and it shall include the Redundant NG DL UP Transport Layer Information IE in the PDU Session Resource Setup List IE in the BEARER CONTEXT SETUP RESPONSE message.
For each PDU Session Resource, if the Redundant Common Network Instance IE is included in the PDU Session Resource To Setup List IE in the BEARER CONTEXT SETUP 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, if the Redundant QoS Flow Indicator IE is included in the QoS Flow QoS Parameters List IE in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, consider it for the redundant transmission.
For each PDU session, if the Redundant PDU Session Information IE is included in the PDU Session Resource To Setup List IE contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, set up the redundant user plane resources, as specified in TS 23.501 and include, if supported, the Used Redundant PDU Session Information IE in the PDU Session Resource Setup List IE in the BEARER CONTEXT SETUP RESPONSE message.
If UE Inactivity Timer IE or PDU session Inactivity Timer IE or DRB Inactivity Timer IE is contained in BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall take it into account when perform inactivity monitoring.
If the DRB QoS IE is contained within the DRB To Setup List IE in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, take it into account as specified in TS 28.552.
If the gNB-DU-ID IE is contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall store the information received.
If the RAN UE ID IE is contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall store the information received.
For each successfully established DRB, the gNB-CU-UP shall provide, in the respective UL UP Parameters IE of the BEARER CONTEXT SETUP RESPONSE, one UL UP Transport Layer Information Item per cell group entry contained in the respective Cell Group Information IE of the BEARER CONTEXT SETUP REQUEST message.
If the Trace Activation IE is included in the BEARER CONTEXT SETUP REQUEST message the gNB-CU-UP shall, if supported, initiate the requested trace function as described in TS 32.422. In particular, the gNB-CU-UP shall, if supported:
  • if the MDT Activation IE is set to "Immediate MDT Only", initiate the requested MDT session as described in TS 32.422 and the gNB-CU-UP shall ignore Interfaces To Trace IE, and Trace Depth IE;
  • if the MDT Activation IE is set to "Immediate MDT and Trace", initiate the requested trace session and MDT session as described in TS 32.422;
If the Management Based MDT PLMN List IE is contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, store the received information, and use this information to allow subsequent selection of the UE for management based MDT defined in TS 32.422.
For EN-DC, if the Subscriber Profile ID for RAT/Frequency priority IE is included in the BEARER CONTEXT SETUP 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 SETUP REQUEST, the gNB-CU-UP may use it to apply specific RRM policies as specified in TS 36.300.
If the TSC Traffic Characteristics IE is included in the BEARER CONTEXT SETUP 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 and the QoS Monitoring Request IE was included in the QoS Flow Level QoS Parameters IE contained in the BEARER CONTEXT SETUP 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.
For each requested DRB, if the QoS Mapping Information IE is contained in the DL UP Parameters IE in the BEARER CONTEXT SETUP 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.
If the BEARER CONTEXT SETUP REQUEST message contains the NPN Context Information IE the gNB-CU-UP shall, if supported, take it into account when allocating UP resources for the bearer context.
For each requested DRB, if the EHC Parameters IE is included in the PDCP Configuration IE, the gNB-CU-CP shall, if supported, also include ROHC Parameters IE in the PDCP Configuration IE in the BEARER CONTEXT SETUP REQUEST message, to enable the gNB-CU-UP to perform appropriate header compression.
If the EHC parameters IE is included in the PDCP Configuration IE contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP may take these parameters into account to perform appropriate header compression for the concerned DRB.
If the DAPS Request Information IE is included for a DRB to be setup in the BEARER CONTEXT SETUP 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 CHO Initiation IE is contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall consider that the request concerns conditional handover or conditional PSCell change and act as specified in TS 38.401.
If the MCG Offered GBR QoS Flow Information IE is contained in the QoS Flows Information To Be Setup IE within the DRB To Setup List IE in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP may take it into account when two cell groups are served by the gNB-CU-UP.
Up

8.3.1.3  Unsuccessful OperationWord‑p. 34
Reproduction of 3GPP TS 38.463, Figure 8.3.1.3-1: Bearer Context Setup procedure: Unsuccessful Operation.
Up
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.
Up

Up   Top   ToC