name: TB
full_form: Transport Block
context: Currently the Iub and Iur interfaces need to be terminated in the DRNC. The consequences for the DCH Frame Protocol are shown in figure 2: Figure 2: ATM-based DRNC DCH FP stack in R99/Rel-4 The functions of the CPS and SSSAR layer are shown in figure 3 (based on [2]). As can be seen in figure 3, a large FP frame will be segmented by the SSCS layer, and then multiplexed in ATM cells by the CPS layer. When receiving an FP frame, the reverse will take place: demultiplexing in CPS layer and re-assembly of the FP frame in the SSCS layer. Figure 3: Example of CPS/SSCS functionality In the DRNS, a complete FP frame will have to be re-assembled before it can be forwarded on the next interface. Especially in the case of low/average speeds on both Iub and Iur this will generate considerable additional delay. E.g. if both Iub and Iur are a 2Mbps interface, for a 384kbps transport channel with a 40ms TTI, an additional minimum delay of 7.68ms will be inserted. Note this figure does not include any
description: Transport Block (TB) refers to a parameter in the context of downlink signalling parameters. It defines the size of data blocks transmitted over the air interface. The standard specifies various TB size tables for different transmission time intervals (TTIs), modulation schemes, and UE capabilities. These tables contain exponentially distributed TB sizes for a certain number of timeslot resources.
explanation: The context describes Transport Block as a parameter related to downlink signalling, specifying data block sizes for transmission over the air interface. The mention of various tables defined by the standard for different scenarios (e.g., TTI, modulation schemes, UE capabilities) further supports its classification as a Parameter.
section_title: 12.2	Downlink signalling parameters
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,B-Protocol,I-Protocol,O,O,O,O,O,O,O,O,B-Network Function,B-Connection,B-Protocol,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,B-Protocol,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Specification,O,O,O,B-Network Function,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,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,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: B-Parameter,I-Parameter,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-Parameter,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O