name: FDR
full_form: False transmit format Detection Ratio. A false Transport Format detection occurs when the receiver detects a different TF to that which was transmitted, and the decoded transport block(s) for this incorrect TF passes the CRC check(s).
context: Assuming that all the parameters (Itest, G, a, FTMA, â¦) related to dividing IMD contributions between 3GPP TMA and BS would have been agreed, how could one then formulate IMD requirements for the 3GPP TMA so that equation (*)(or equivalent) holds for each of the elected IMD scenarios? The following 3 options may be considered: 1) Attempt to standardise the TMA RX filter responses and LNA IIP3 in 3GPP (the filter response would have to be separated in one part before the LNA and one part after the LNA). Then and the LHS of equation (*) are known for all elected IMD scenarios and BS system vendors can check the validity of equation (*) throughout this process. For testing the TMA vendors would then need to provide data related to RX filter responses and the LNA IIP3. However, it should be noted that standardising details of the receiver implementation (like RX filters, IIP3) is typically not done in 3GPP as this may restrict the design freedom of the implementation. Furthermore, each
description: The False Transport Format Detection Ratio (FDR) measures the likelihood of a receiver incorrectly identifying a transport format, despite passing the Cyclic Redundancy Check (CRC), which can lead to significant degradation in service quality. FDR is an essential metric for evaluating the performance and reliability of transport format detection mechanisms in telecommunications systems.
explanation: The context explicitly defines FDR as a ratio used to evaluate the probability of false transport format detection, highlighting its importance in assessing service quality degradation. This classification as a Measurement is based on the provided definition within the context, which emphasizes its role in quantifying and evaluating performance.
section_title: 15.3.1.2	Assumption
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,O,O,B-Measurement,O,O,B-Organization,B-Miscellaneous,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Measurement,O,O,O,B-Organization,B-Miscellaneous,O,O,O,O,O,O,O,O,O,O,O,B-Measurement,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,B-Device,O,O,O,B-Device,O,O,B-Organization,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,B-Measurement,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,B-Organization,O,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: O,O,B-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,O,B-Measurement,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O