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.3  Bearer Context Modification Required (gNB-CU-UP initiated)Word‑p. 40

8.3.3.1  General

The purpose of the Bearer Context Modification Required procedure is to allow the gNB-CU-UP to modify a bearer context (e.g., due to local problems) and inform the gNB-CU-CP. The procedure uses UE-associated signalling.

8.3.3.2  Successful Operation

Reproduction of 3GPP TS 38.463, Figure 8.3.3.2-1: Bearer Context Modification Required procedure: Successful Operation.
Up
The gNB-CU-UP initiates the procedure by sending the BEARER CONTEXT MODIFICATION REQUIRED message to the gNB-CU-CP. The gNB-CU-CP replies with the BEARER CONTEXT MODIFICATION CONFIRM message.
If the S1 DL UP Transport Layer Information IE or the NG DL UP Transport Layer Information IE or the Redundant NG DL UP Transport Layer Information IE is contained in the BEARER CONTEXT MODIFICATION REQUIRED message, the gNB-CU-CP shall update the corresponding information.
If the gNB-CU-UP Cell Group Related Configuration IE is contained in the DRB To Modify List IE in the BEARER CONTEXT MODIFICATION REQUIRED message, the gNB-CU-CP shall try to change the cell group related configuration accordingly. If the gNB-CU-CP is not able to update the requested cell group related configuration, it shall include the Cell Group Information IE with the current cell group configuration in the DRB Modified List IE in the BEARER CONTEXT MODIFICATION CONFIRM message.
Up

8.3.3.3  Abnormal Conditions

Not applicable.

8.3.4  Bearer Context Release (gNB-CU-CP initiated)

8.3.4.1  General

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

8.3.4.2  Successful OperationWord‑p. 41
Reproduction of 3GPP TS 38.463, Figure 8.3.4.2-1: Bearer Context Release procedure: Successful Operation.
Up
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 and TS 28.552.
Up

8.3.4.3  Abnormal Conditions

Not applicable.

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

Reproduction of 3GPP TS 38.463, Figure 8.3.5.2-1: Bearer Context Release Requset procedure: Successful Operation.
Up
The gNB-CU-UP initiates the procedure by sending the BEARER CONTEXT RELEASE REQUEST message to the gNB-CU-CP.
If the DRB Status List IE is included in the BEARER CONTEXT RELEASE REQUEST message, the gNB-CU-CP shall act as specified in TS 38.401.
Interactions with Bearer Context Release procedure:
The Bearer Context Release (gNB-CU-CP initiated) procedure may be initiated upon reception of a BEARER CONTEXT RELEASE REQUEST message.
Interaction with Bearer Context Modification (gNB-CU-CP initiated) procedure:
If applicable, as specified in TS 38.401, the gNB-CU-UP may receive, after having performed the Bearer Context Release Request (gNB-CU-UP initiated) procedure, the BEARER CONTEXT MODIFICATION REQUEST message including the Data Forwarding Information Request IE within the DRBs To Modify List IE.
Up

8.3.5.3  Abnormal ConditionsWord‑p. 42
Not applicable.

8.3.6  Bearer Context Inactivity Notification

8.3.6.1  General

This procedure is initiated by the gNB-CU-UP to indicate the inactivity/resumption of activity related to the UE. The procedure uses UE-associated signalling.

8.3.6.2  Successful Operation

Reproduction of 3GPP TS 38.463, Figure 8.3.6.2-1: Bearer Context Inactivity Notification procedure: Successful Operation.
Up
The gNB-CU-UP initiates the procedure by sending the BEARER CONTEXT INACTIVITY NOTIFICATION message to the gNB-CU-CP.
If the Activity Notification Level was set to "DRB" during the Bearer Context establishment, the gNB-CU-UP shall include the DRB Activity List IE in the BEARER CONTEXT INACTIVITY NOTIFICATION message.
If the Activity Notification Level was set to "PDU Session" during the Bearer Context establishment, the gNB-CU-UP shall include the PDU Session Resource Activity List IE in the BEARER CONTEXT INACTIVITY NOTIFICATION message.
If the Activity Notification Level was set to "UE" during the Bearer Context establishment, the gNB-CU-UP shall include the UE Activity IE in the BEARER CONTEXT INACTIVITY NOTIFICATION message.
Up

8.3.6.3  Abnormal Conditions

Not applicable.

8.3.7  DL Data NotificationWord‑p. 43

8.3.7.1  General

This procedure is initiated by the gNB-CU-UP to indicate the detection of DL data arrival for the UE. The procedure uses UE-associated signalling.

8.3.7.2  Successful Operation

Reproduction of 3GPP TS 38.463, Figure 8.3.7.2-1: DL Data Notification procedure: Successful Operation.
Up
The gNB-CU-UP initiates the procedure by sending the DL DATA NOTIFICATION message to the gNB-CU-CP.
If the PPI IE is included in the DL DATA NOTIFICATION message, the gNB-CU-CP shall use it for paging policy differentiation.

8.3.7.3  Abnormal Conditions

Not applicable.

8.3.8  Data Usage Report

8.3.8.1  General

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

8.3.8.2  Successful Operation

Reproduction of 3GPP TS 38.463, Figure 8.3.8.2-1: Data Usage Report procedure: Successful Operation.
Up
The gNB-CU-UP initiates the procedure by sending the DATA USAGE REPORT message to the gNB-CU-CP.

8.3.8.3  Abnormal ConditionsWord‑p. 44
Not applicable.

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

Reproduction of 3GPP TS 38.463, Figure 8.3.9.2-1: gNB-CU-UP Counter Check procedure, successful operation.
Up
The gNB-CU-UP initiates the procedure by sending the gNB-CU-UP COUNTER CHECK REQUEST message to the gNB-CU-CP.
Upon reception of the gNB-CU-UP COUNTER CHECK REQUEST message, the gNB-CU-CP may perform the RRC counter check procedure as defined in TS 33.501.

8.3.9.3  Unsuccessful Operation

Not applicable.

8.3.9.4  Abnormal Conditions

Not applicable.

8.3.10  UL Data Notification

8.3.10.1  General

This procedure is initiated by the gNB-CU-UP to notify the gNB-CU-CP that an UL packet including a QFI value in the SDAP header not configured by the Flow Mapping Information IE is received for the first time at the default DRB. The procedure uses UE-associated signalling.

8.3.10.2  Successful OperationWord‑p. 45
Reproduction of 3GPP TS 38.463, Figure 8.3.10.2-1: UL Data Notification procedure: Successful Operation.
Up
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

Not applicable.

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.

8.3.11.2  Successful Operation

Reproduction of 3GPP TS 38.463, Figure 8.3.11.2-1: MR-DC Data Usage Report procedure: Successful Operation.
Up
The gNB-CU-UP initiates the procedure by sending the MR-DC DATA USAGE REPORT message to the gNB-CU-CP.

8.3.11.3  Abnormal Conditions

Not applicable.

8.3.12  Early Forwarding SN Transfer |R16|

8.3.12.1  General

The purpose of the Early Forwarding SN Transfer procedure is to transfer, from the source gNB-CU-UP to the source gNB-CU-CP, DL COUNT of the last PDCP SDU successfully delivered or transmitted to the UE, for the purpose of discarding early forwarded downlink PDCP SDUs during Conditional Handover or conditional PSCell change.
The procedure uses UE-associated signalling.

8.3.12.2  Successful OperationWord‑p. 46
Reproduction of 3GPP TS 38.463, Figure 8.3.12.2-1: Early Forwarding SN Transfer procedure: Successful Operation.
Up
The source gNB-CU-UP initiates the procedure by sending the EARLY FORWARDING SN TRANSFER message.
The DRBs Subject To Early Forwarding List IE included in the EARLY FORWARDING SN TRANSFER message contains the DRB ID(s) corresponding to the DRB(s) subject to early data forwarding during Conditional Handover or conditional PSCell change.
For each DRB in the DRBs Subject To Early Forwarding List IE, the value of the DL COUNT Value IE indicates the DL COUNT of the last PDCP SDU successfully delivered in-sequence to the UE, if RLC-AM, and successfully transmitted, if RLC-UM.
Up

8.3.12.3  Unsuccessful Operation

Not applicable.

8.3.12.4  Abnormal Conditions

If the source gNB-CU-CP receives this message for a UE for which no prepared Conditional Handover exists, the source gNB-CU-CP shall ignore the message.

8.3.13  GNB-CU-CP Measurement Results Information |R16|

8.3.13.1  General

This procedure is initiated by the gNB-CU-CP to inform the measurement results received from the UE to the gNB-CU-UP.
The procedure uses UE-associated signalling.

8.3.13.2  Successful Operation

Figure 8.3.13.2-1: GNB-CU-CP Measurement Results Information procedure. Successful operation.
The gNB-CU-CP initiates the procedure by sending a GNB-CU-CP MEASUREMENT RESULTS INFORMATION message.

8.3.13.3  Abnormal ConditionsWord‑p. 47
Not applicable.


Up   Top   ToC