name: TFRI
full_form: Transport Format and Resource Indicator
context: an indication of an HS-SCCH order, start receiving the HS-PDSCHs indicated by this consistent control information. - If the CRC of the HS-SCCH is OK: - If the âchannelization-code-set informationâ and âmodulation scheme informationâ correspond to an HS-SCCH order as defined in [2] subclause 4.6C.3, - if the TFRI value corresponds to an HS-SCCH order and the order mapping is as per subclause 4.6C.3.2.1, the UE shall process the HS-SCCH orders as described in subclause 6B. If NT-HS-DPCCH_Enabled is TRUE, the UE shall not transmit the associated HARQ-ACK information acknowledging the HS-SCCH order. - if the TFRI value corresponds to an HS-SCCH order and the order mapping is as per subclause 4.6C.3.2.2, the UE shall process the HS-SCCH order as described in [5]. - else, discard the information received on this HS-SCCH - Else, the transport block size information shall be derived from the signalled TFRI value as defined in [9]. If the 'Hybrid-ARQ process information' is not included in the
description: The Transport Format and Resource Indicator (TFRI) is a parameter used to indicate the transport format and resource allocation for High-Speed Downlink Shared Channel (HS-DSCH) transmissions. It provides information about the channelization code set, modulation scheme, and transport block size, which are essential for the User Equipment (UE) to correctly receive and process HS-DSCH data.
explanation: The context describes TFRI as a parameter that specifies transmission characteristics for HS-DSCH, making it directly involved in configuring and controlling the communication process. This classification aligns with the definition of a 'Parameter' as a value that sets or modifies a system's behavior.
section_title: 6A.1.1A	UE procedure for receiving HS-DSCH and HS-SCCH in CELL_FACH state
biotag_Context: O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,B-Protocol,O,O,O,B-Connection,O,O,O,O,B-Parameter,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: O,B-Parameter,I-Parameter,I-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,I-Connection,I-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,I-Device,O,O,O,O,O,O,B-Connection,O