name: LARF
full_form: Location Acquisition Requesting Function
context: Upon the receipt of a location acquisition request over LI_XLA, the LARF shall first check that the UE is registered at the MME/AMF. If it is registered the LARF will check the UE context at the MME/AMF to see if the current location for the UE is known. The LARF/MME/AMF shall override any user consent, privacy and paging restrictions concerned with location acquisition that may apply to the target UE. The LARF/MME/AMF shall ensure that overriding these restrictions does not result in additional detectability issues. If delivery via the LI_HI2 is required, the LARF will send the acquisition response as either an AMFLocationUpdate (in case of the 5GC) or an MMELocationUpdate (in case of the EPC) xIRI record to the MDF2 via LI_X2_LA. Full details are given in clause 7.3.5.6. If delivery via the LI_HILA is required, the LARF returns the acquisition response as part of the LI_XLA response, which the LAF then transforms into a LI_HILA response given as a LocationResponseDetails structure
description: The Location Acquisition Requesting Function (LARF) manages location acquisition requests within the network. Its responsibilities include checking User Equipment (UE) registration, retrieving UE context information, and overriding user consent and privacy restrictions when required. The LARF also handles the delivery of location acquisition responses through various interfaces.
explanation: The text describes LARF as a function that controls and manages the process of acquiring location information from UEs within the network. It performs tasks like checking registration status, retrieving UE context, and managing response delivery. These functions are characteristic of a Network Function, which is responsible for specific network operations.
section_title: 7.3.5.4.1	General description
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Device,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,O,O,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,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,O,O,O,O,O,O,O,B-Network Function,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,O
biotag_Description: O,B-Network Function,I-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,I-Device,O,O,O,B-Device,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,O