name: MO-LR
full_form: Mobile Originated Location Request
context: Figure 7.3.2-1 shows the sequence of operations for an MO-LR service, starting at the point where an LCS Client in the UE or the user has requested some location service (e.g., retrieval of the UE's location or transfer of the UE's location to a third party). Figure 7.3.2-1: UE Positioning Operations to support an MO-LR 1. The UE sends a NAS level MO-LR location service request message to the MME. The MO-LR location service request message may carry an LPP PDU to instigate one or more LPP procedures to transfer capabilities, request assistance data and/or transfer location information (e.g. location measurements). 2. The MME sends a location request to the E-SMLC and includes any LPP PDU received in step 1. 3. The E-SMLC may obtain location related information from the UE and/or from the serving eNode B. In the former case or if an immediate response is needed to any LPP procedure instigated by the UE in step 1 (e.g., a request for assistance data), the E-SMLC instigates one or more
description: The Mobile Originated Location Request (MO-LR) is a procedure initiated by the User Equipment (UE) to request location services, such as retrieving its own location or transferring its location to a third party. This procedure involves a sequence of operations between the UE, Mobility Management Entity (MME), and Evolved Serving Mobile Location Centre (E-SMLC) to facilitate location-related information exchange.
explanation: The context describes MO-LR as a service support in 3GPP TS 36.305, specifically highlighting the sequence of operations for an MO-LR service. This indicates that MO-LR is a procedure involving multiple steps and interactions between different network components to achieve a specific goal, which is to provide location services.
section_title: 7.3.2	MO-LR Service Support
biotag_Context: O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,B-Service,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,B-Protocol,I-Protocol,O,O,O,O,B-Procedure,O,O,B-Device,O,O,B-Protocol,O,B-Procedure,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,B-Protocol,B-Connection,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,B-Protocol,B-Connection,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,B-Protocol,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: O,B-Procedure,I-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,O,O,B-Device,I-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,B-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O