name: NIDD
full_form: Non-IP Data Delivery
context: There are several different events in which the information is sent to the DF2 if this is required. Details are described in the following clause. The events for interception are configurable (if they are sent to DF2) in the MME, SGSN, SCEF or the HSS and can be suppressed in the DF2. The network procedures for which the events are generated are defined in TS 23.060 [10] and TS 23.401 [22]. The following events are applicable to the MME: - IoT UE Attach for NIDD using SCEF; - IoT UE Detach for NIDD for using SCEF; - IoT UE Tracking Area Update for NIDD using SCEF; - IoT UE requested non-IP PDN connectivity; - IoT UE Requested non-IP PDN disconnection; - SCEF requested non-IP PDN disconnection - Start of interception with attached IoT UE with active non-IP PDN connection. The following events are applicable to the SGSN: - IoT UE Attach for NIDD using SCEF; - IoT UE Detach for NIDD using SCEF; - IoT UE Routing Area Update for NIDD using SCEF; - IoT UE requested non-IP PDP context
description: Non-IP Data Delivery (NIDD) is a telecommunications service that enables the delivery of data without using IP protocols. It is specifically designed for IoT devices and allows them to communicate with the network without establishing an IP connection.
explanation: The text describes NIDD as a 'telecommunications service' designed for a specific purpose (data delivery for IoT devices). This aligns with the definition of a Service in telecommunications, which refers to a functional offering provided to users.
section_title: 23.3.3	Structure of the events
biotag_Context: 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,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,O,B-Specification,O,O,O,O,O,O,O,O,O,O,O,B-Technology,B-Device,O,O,B-Procedure,O,O,O,B-Technology,B-Device,B-Message,O,B-Procedure,O,O,O,O,B-Technology,B-Device,B-Procedure,I-Procedure,I-Procedure,O,B-Procedure,O,O,O,B-Technology,B-Device,O,O,B-Network,O,O,B-Technology,B-Device,O,O,B-Network,O,O,B-Network Function,O,O,B-Network,O,O,O,O,O,O,O,B-Technology,B-Device,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,B-Technology,B-Device,O,O,B-Procedure,O,O,O,B-Technology,B-Device,B-Message,O,B-Procedure,O,O,O,B-Technology,B-Device,B-Procedure,I-Procedure,I-Procedure,O,B-Procedure,O,O,O,B-Technology,B-Device,O,O,B-Protocol,O
biotag_Description: 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,B-Technology,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O