name: LNA
full_form: Low Noise Amplifier
context: In MR-DC, when a UE performs successful random access attempts which are only known by the SN (e.g., beam failure recovery, UL synchronization issue, scheduling request failure, no PUCCH resource available), the SN may inform the MN about the occurrences of successful random access procedures in the SN via a RACH indication. The MN may then retrieve the RA Report from the UE(s) based on the RACH indication received from the SN. A UE while being in EN-DC and NGEN-DC can collect E-UTRA RA Reports and NR RA Reports upon performing RACH in MN and SN respectively. When a E-UTRAN node retrieves the E-UTRA RA Report, it can also request UE to include the NR RA Report. If available, the UE then includes the NR RA Report in a container along with a list of PSCells associated to the NR RA Report within the E-UTRA RA Report. The retrieiving E-UTRAN node may then forward it to the corresponding SNs serving the PSCells indicated within the E-UTRA RA Report. In case of NGEN-DC, in case there is no
description: A Low Noise Amplifier (LNA) is a type of amplifier used in telecommunications systems to amplify weak signals while minimizing noise. In the context of 3GPP TS 25.818, LNAs are discussed as part of the receiver implementation, particularly regarding Intermodulation Distortion (IMD) requirements for Multi-Antenna (TMA) terminals. The LNA's Input IP3 (IIP3) is a key parameter used to define IMD requirements.
explanation: The text explicitly mentions the LNA within the framework of 3GPP TS 25.818, a standard for telecommunications technology. It discusses the LNA's role in signal amplification and its impact on IMD performance in TMA receivers, clearly classifying it as a technological component within the telecommunications domain.
section_title: 7.4.2	Feasibility of defining IMD requirements for the 3GPP TMA
biotag_Context: O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,B-Connection,O,O,O,O,O,O,B-Connection,O,O,O,B-Message,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,B-Connection,O,O,B-Network Function,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,B-Device,O,O,O,B-Technology,O,B-Technology,O,O,B-Technology,B-Procedure,O,O,B-Network,B-Procedure,O,O,O,B-Connection,O,B-Network Function,O,B-Message,O,O,O,B-Network,O,O,O,B-Technology,B-Procedure,O,O,O,O,O,B-Device,O,O,O,B-Network,B-Procedure,O,O,O,O,B-Device,O,O,O,B-Network,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,B-Procedure,O,O,O,B-Technology,B-Procedure,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,B-Procedure,O,O,O,O,O,O,O,O,O,O
biotag_Description: O,B-Device,I-Device,I-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Organization,B-Specification,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-Measurement,O