name: SDT
full_form: Small Data Transmission
context: The procedure for the case where the UE has CG-SDT resource configurations but decides to perform RACH based small data transmission in RRC Inactive or to perform RACH procedure to transit to RRC Connected (see TS 38.321 [30] clause 5.27) is shown in Figure 8.18.3-1. Figure 8.18.3-1: RA-SDT or non-SDT with CG-SDT configuration. 1. The UE in RRC Inactive sends RRCResumeRequest message. If the UE decides to perform RACH based SDT procedure, it also sends UL SDT data and/or UL SDT signalling. 2. The gNB-DU buffers the UL SDT data and/or UL SDT signalling. 3. The gNB-DU sends the INITIAL UL RRC MESSAGE TRANSFER message to the gNB-CU-CP, including a new gNB-DU UE F1AP ID, and in case of RACH based SDT access, the gNB-DU provides an indication of SDT access and may also the SDT assistance information. 4. If UE context is successfully retrieved as specified in TS 38.300 [2], the gNB-CU-CP sends the UE CONTEXT SETUP REQUEST message with the stored (or retrieved from the last serving gNB) F1 UL
description: The Small Data Transmission (SDT) procedure enables user equipment (UE) to transmit small amounts of data in RRC Inactive or Connected mode. It involves the UE sending an RRCResumeRequest message, followed by UL SDT data and/or signaling. These are buffered by the gNB-DU and forwarded to the gNB-CU-CP for processing.
explanation: The text describes a specific sequence of actions (RRCResumeRequest, data transmission, buffering, forwarding) performed by different network entities (UE, gNB-DU, gNB-CU-CP). This structured process defines a well-defined operation within the telecommunications system, classifying SDT as a Procedure.
section_title: 8.18.3RA-SDT or non-SDT with CG-SDT configuration
biotag_Context: O,O,O,O,O,O,O,B-Device,O,B-Procedure,O,O,O,O,O,O,B-Connection,O,O,O,O,O,B-Protocol,O,O,O,O,B-Connection,O,O,O,O,B-Protocol,O,O,B-Specification,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,B-Procedure,O,O,O,B-Device,O,B-Protocol,O,O,O,O,O,O,B-Device,O,O,O,B-Connection,O,B-Procedure,O,O,O,O,B-Connection,B-Procedure,O,O,B-Connection,B-Procedure,O,O,O,B-Network Function,O,O,B-Connection,B-Procedure,O,O,B-Connection,B-Procedure,O,O,O,B-Network Function,O,O,O,B-Connection,B-Protocol,O,O,O,O,O,O,O,O,O,B-Network Function,B-Device,B-Protocol,O,O,O,O,O,B-Connection,O,B-Procedure,O,O,B-Network Function,O,O,O,O,B-Procedure,O,O,O,O,O,B-Procedure,O,O,O,O,B-Device,O,O,O,O,O,O,O,B-Specification,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Interface,B-Connection
biotag_Description: O,B-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,B-Connection,B-Procedure,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O