name: NI-LR
full_form: Network Induced Location Request
context: Figure 7.3.1-1 shows the sequence of operations for an NI-LR or MT-LR location service, starting at the point where the MME initiates the service in the E-SMLC. Figure 7.3.1-1: UE Positioning Operations to support an MT-LR or NI-LR 1. The MME sends a location request to the E-SMLC for a target UE and may include associated QoS. 2. The E-SMLC may obtain location related information from the UE and/or from the serving eNode B. In the former case, the E-SMLC instigates one or more LPP procedures to transfer UE positioning capabilities, provide assistance data to the UE and/or obtain location information from the UE. The UE may also instigate one or more LPP procedures after the first LPP message is received from the E-SMLC (e.g., to request assistance data from the E-SMLC). 3. If the E-SMLC needs location related information for the UE from the eNode B, the E-SMLC instigates one or more LPPa procedures. Step 3 is not necessarily serialised with step 2; if the E-SMLC and eNode B have the
description: Network Induced Location Request (NI-LR) is a procedure initiated by the Mobility Management Entity (MME) to request location information of a target User Equipment (UE). The procedure involves the MME sending a location request to the Evolved Serving Mobile Location Centre (E-SMLC), which may then obtain location-related information from the UE and/or the serving eNode B through LPP or LPPa procedures.
explanation: The context describes a sequence of operations for NI-LR, including the initiation by MME, the involvement of E-SMLC, and the potential use of LPP/LPPa procedures to obtain location information. This indicates that NI-LR is a specific procedure within the network, hence classified as a Procedure.
section_title: 7.3.1	NI-LR and MT-LR Service Support
biotag_Context: O,O,O,O,O,O,O,O,O,B-Procedure,O,B-Procedure,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Protocol,I-Protocol,O,O,O,O,B-Procedure,O,B-Procedure,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,B-Device,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,O,O,O,O,O,O,B-Protocol,O,O,O,B-Device,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,B-Protocol,O,O,O,O,B-Protocol,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-Device,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
biotag_Description: B-Procedure,I-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,O,O,B-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,B-Device,I-Device,O,O,O,O,O,B-Network Function,O,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,O,O,B-Protocol,O,O,O