name: TEBS
full_form: Total E-DCH Buffer Status
context: and CLTD modes is defined as follows: The serving grant SG and SINR difference SD parameters are calculated and signaled by the Node B to the UE for each TTI. The SG parameter defines the E-DPDCH power relative to the DPCCH as for the legacy power-based approach. An illustration of the transmit power level and the SG and SD parameters for the SINR-based scheduling of a SIMO or CLTD transmission is given in Figure 5.7.3.1-2. Figure 5.7.3.1-2: SINR-based scheduling using SG and SD parameters for the SIMO and CLTD transmission modes E-TFC selection is done using the legacy procedure, but the SD parameter is applied to decrease the SG grant prior to passing it to the E-TFC. However, the actual transmit power is not affected by SD. The SD is selected so that the combination of the SG and SD allows the UE to estimate the post-receiver SINR level at the Node B and select the E-TFC that would provide the maximum throughput at the required BLER performance. The mechanism considering 2-loop
description: The Total E-DCH Buffer Status (TEBS) is a parameter used in the MAC-i/is segmentation entity to indicate the amount of data available for transmission. It includes control PDUs, RLC PDUs outside the RLC Tx window, and excludes RLC PDUs that have been transmitted but not negatively acknowledged by the peer entity. The TEBS field has a length of 5 bits and its values are defined in Table 9.2.5.3.2-1.
explanation: TEBS is classified as a Parameter because it is used to convey specific information about the buffer status, which is a configuration setting used in the MAC-i/is segmentation entity. The context highlights how TEBS is calculated and what it includes, indicating its role as a parameter in the telecommunications process.
section_title: 9.2.5.3.2	Scheduling Information
biotag_Context: O,B-Technology,O,O,O,O,O,O,O,O,B-Network Function,O,B-Measurement,O,B-Network Function,O,O,O,O,O,O,O,B-Network Function,I-Network Function,O,O,B-Device,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,B-Network Function,O,O,O,O,O,O,O,B-Miscellaneous,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,B-Network Function,O,O,O,B-Miscellaneous,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,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,B-Network Function,O,O,O,O,O,O,O,O,B-Network Function,O,B-Network Function,O,O,B-Device,O,O,O,O,B-Measurement,O,O,O,B-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Measurement,O,O,O,O,O
biotag_Description: O,B-Parameter,I-Parameter,I-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,B-Protocol,O,O,O,B-Protocol,O,O,O,O,B-Protocol,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,O,O,O,O