name: MT-SDT
full_form: Mobile Terminated Small Data Transmission
context: subsequent CPAC configuration with CPA execution condition(s) maintained after SCG release can be used for the subsequent CPA execution. - Upon inter-SN subsequent CPAC execution, the UE uses the first unused sk-Counter value for S-KgNB generation, based on the per-SN pre-configured sk-Counter value list. - Upon PCell change, PSCell change or SCG release, if the subsequent CPAC configuration is maintained, the UE also maintains the unused sk-Counter values. MN initiated subsequent CPAC The subsequent CPAC procedure is initiated by the MN for inter-SN subsequent CPAC configuration and inter-SN subsequent CPAC execution. Figure 10.20-1: Inter-SN subsequent CPAC - MN initiated Figure 10.20-1 shows an example signalling flow for the inter-SN subsequent CPAC initiated by the MN: 1/2/3/4. The MN initiates the inter-SN subsequent CPAC by requesting the candidate SN(s) to allocate resources for the UE by means of the SN Addition procedure, indicating that the request is for subsequent CPAC.
description: Mobile Terminated Small Data Transmission (MT-SDT) is a procedure related to handling small data transmissions in mobile networks, specifically when the data transmission is initiated by the network towards the user equipment. This procedure involves interactions with other processes such as DL Data Notification and is governed by specific rules for including or excluding PDU Set information based on certain conditions.
explanation: MT-SDT is classified under Procedure because it describes a sequence of operations related to handling small data transmissions in mobile networks, involving the interaction between network components like gNB-CU-UP and the inclusion/exclusion of specific information (PDU Set) under certain conditions. The context highlights its role within the BEARER CONTEXT MODIFICATION REQUEST message and DL Data Notification procedure.
section_title: 8.3.2.2	Successful Operation
biotag_Context: O,B-Procedure,O,O,B-Procedure,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,B-Procedure,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,B-Network Function,O,O,O,O,B-Procedure,O,O,O,O,B-Device,O,O,O,O,O,O,B-Network Function,O,O,B-Procedure,O,O,B-Procedure,O,O,O,O,O,B-Network Function,O,O,O,B-Procedure,O,O,O,O,B-Procedure,O,O,O,O,O,B-Procedure,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O
biotag_Description: B-Procedure,I-Procedure,I-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O