name: MT-SDT
full_form: Mobile Terminated SDT
context: The overall procedure for MT-SDT procedure with/without UE context relocation is illustrated in the figure 18.4-1. Figure 18.4-1: MT-SDT with/without UE context relocation 1. DL user data and/or DL NAS signalling are received at the Last Serving gNB for the UE in RRC_INACTIVE state. 2. The Last Serving gNB may send MT-SDT information to the neighbour gNBs within the RNA, via XnAP RAN PAGING message. 3. The gNB that receives MT-SDT information within the RNA, takes into account the MT-SDT information received in the XnAP RAN PAGING message to decide whether to trigger MT-SDT Paging. The gNB which ultimately reaches the UE via the Uu Paging becomes the Receiving gNB. NOTE 1: In case that the Receiving gNB decides not to trigger MT-SDT paging, the above step 3 and subsequent steps are the same as Figure 9.2.2.4.2 from step 3. 4/5. The UE may decide to initiate MT-SDT procedure and in this case sends an RRCResumeRequest message with an MT-SDT resume cause to the Receiving gNB. 6. The
description: Mobile Terminated SDT (MT-SDT) is a procedure used in the 5G core network for mobile terminated services, specifically for handling downlink user data and signaling when the UE is in RRC_INACTIVE state. It involves steps such as receiving MT-SDT information at the Last Serving gNB, sending this information to neighbor gNBs via XnAP RAN PAGING message, deciding whether to trigger MT-SDT Paging based on received information, and the UE initiating the MT-SDT procedure by sending an RRCResumeRequest message.
explanation: The context describes a sequence of network operations involving specific steps and messages exchanged between network components (gNBs and UE) for handling mobile terminated services. This matches the definition of a Procedure as it outlines a specific sequence of actions taken by network elements to achieve a particular goal.
section_title: 18.4MT-SDT with/without UE context relocation
biotag_Context: O,O,O,O,B-Procedure,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,B-Device,O,O,O,B-Connection,O,O,O,B-Connection,B-Protocol,O,O,O,O,O,O,O,B-Network Function,O,O,B-Device,O,O,O,O,O,O,O,B-Network Function,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,B-Network Function,O,O,B-Procedure,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,B-Procedure,O,O,B-Network Function,O,O,O,O,B-Device,O,O,B-Interface,B-Procedure,O,O,O,O,O,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,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O
biotag_Description: B-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,B-Procedure,B-Procedure,O,O,O,O,O,O,B-Device,O,O,B-Procedure,O,O,O,O,O,O