name: TFRC
full_form: Transport Format Resource Combination
context: CHANNEL SETUP REQUEST message. Where more than one FPACH is defined, the FPACH that Node B should use is defined by the UpPCH signature (SYNC_UL) code that the UE used. The FPACH number = N mod M where N denotes the signature number (0..7) and M denotes the number of FPACHs that are defined in a cell. The FPACH number is in ascending order by Common Physical Channel ID IE contained in the COMMON TRANSPORT CHANNEL SETUP REQUEST message. If the FPACH IE contains the UARFCN IE, the FPACH shall be set up on the secondary frequency indicated by the UARFCN IE. When the FPACH is set up on the secondary frequency of a multi-frequency cell, if the PRACH LCR IE contains the UARFCN IE, the RACH IE included in the PRACH LCR IE shall be ignored; otherwise all IEs included in the PRACH LCR IE shall be ignored. [1.28Mcps TDD - PLCCH]: If the COMMON TRANSPORT CHANNEL SETUP REQUEST message contains the PLCCH IE, the Node B shall configure and activate the indicated PLCCH according to the COMMON
description: Transport Format Resource Combination (TFRC) refers to a parameter used in the configuration and management of High-Speed Downlink Shared Channel (HS-DSCH) transmissions within the Universal Terrestrial Radio Access Network (UTRAN). It is involved in the selection process for MAC-ehs, which is identical to that of MAC-hs. TFRC plays a role in determining transmission formats and resource allocation for HS-DSCH operations.
explanation: The context describes TFRC as a parameter used in configuring and managing HS-DSCH transmissions, specifically mentioning its role in selection processes and resource allocation. This clearly indicates that TFRC is a configurable element within the system, fitting the definition of a 'Parameter'.
section_title: 4.2.4.5	MAC-e entity â UTRAN Side
biotag_Context: O,O,O,O,O,O,O,O,B-Connection,O,O,O,B-Connection,O,B-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,B-Connection,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-Connection,O,O,O,O,O,O,O,O,B-Connection,B-Parameter,B-Message,O,O,O,O,O,O,O,O,O,O,O,B-Connection,B-Message,O,O,B-Parameter,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,B-Parameter,B-Message,O,O,B-Parameter,O,O,B-Connection,B-Message,O,O,O,B-Connection,B-Parameter,B-Message,O,O,O,O,O,O,O,O,O,B-Connection,B-Parameter,B-Message,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,B-Network Function,I-Network Function,O,O,O,O,O,O,B-Connection,O,O,O,O
biotag_Description: B-Parameter,I-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,I-Connection,I-Connection,O,O,O,O,B-Network,I-Network,I-Network,I-Network,I-Network,O,O,O,O,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,B-Connection,O