name: MT-LR
full_form: Mobile Terminated Location Request
context: and is the size of the bitmap . Note: For the purpose of calculating TPRS,i, only the PRS resources fully or partially covered by the MG are considered. When PRS-RSRP measurements are configured for DL-AoD, except for deferred MT-LR as defined in clause 4.1a.5 [TS 23.273], the time starts from the first MG instance aligned with DL PRS resources in the assistance data after both the NR-DL-AoD-RequestLocationInformation message and NR-DL-AoD-ProvideAssistanceData message from LMF via LPP [34] are delivered to the physical layer of UE. For deferred MT-LR with other event than âPeriodic Locationâ as defined in clause 4.1a.5.1 [TS 23.273], the time starts from the first MG instance aligned with a DL PRS resource(s) in the assistance data after the associated event(s) occurs. For deferred MT-LR with event âPeriodic Locationâ as defined in clause 4.1a.5.1 [TS 23.273], the UE shall perform the PRS-RSRP measurement in each reporting period and activate the location report at the time when the
description: The Mobile Terminated Location Request (MT-LR) is a procedure used in the context of location services, specifically for calculating the Time-To-First-Positioning-Result-Success (TPRS). It involves the UE performing PRS-RSRP measurements and reporting location information to the network. The MT-LR can be deferred based on specific events or periodic locations.
explanation: The context provided highlights the procedural aspects of MT-LR, detailing when and how it is triggered, and what actions the UE takes in response. This includes the calculation of TPRS, the alignment with DL PRS resources, and the reporting of location information. The emphasis on specific events, timing, and measurement procedures indicates that MT-LR is a procedure rather than a protocol, network function, or any other entity type.
section_title: 16.2.1.3	Minimum conformance requirements
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,B-Technology,O,O,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,B-Technology,O,O,O,B-Connection,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,B-Protocol,O,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,O,O,O,O,O,B-Technology,O,O,O,O,B-Connection,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,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
biotag_Description: O,B-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,B-Device,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O