name: MAC-hs
full_form: Medium Access Control-high speed
context: when the DL user plane of this RL is considered synchronised.] [TDD â The Node B shall transmit special bursts on the DL DPCH as per TS 25.224 [11], until the DL user plane is considered synchronised]. When the DL user plane is considered synchronised and the Node B does not receive a valid DL DATA FRAME in a TTI, it assumes that there is no data to be transmitted in that TTI for this transport channel, and shall act as one of the following cases: - [TDD â If the Node B receives no valid DL DATA FRAMEs for any transport channel assigned to a UE it shall assume DTX and transmit special bursts as per TS 25.224 [11]]. - If the Node B is aware of a TFI value corresponding to zero bits for this transport channel, this TFI is assumed. If the TFS contains both a TFI corresponding to "TB length equal to 0 bits" and a TFI corresponding to "number of TB equal to 0", the Node B shall assume the TFI corresponding to "number of TB equal to 0". When combining the TFI's of the different transport
description: The Medium Access Control-high speed (MAC-hs) protocol is a specific format used in the High-Speed Downlink Shared Channel (HS-DSCH) for transmitting data. It consists of a MAC-hs header and one or more MAC-hs Service Data Units (SDUs), where each SDU equals a MAC-d PDU. The MAC-hs header is variable in size, and multiple MAC-hs SDUs in the same Transmission Time Interval (TTI) belong to the same reordering queue.
explanation: MAC-hs is classified as a Protocol because it defines the rules and structure for data transmission within the HS-DSCH.  The description outlines its components (header, SDUs) and how they function together to ensure organized data transfer.
section_title: 9.1.4	MAC PDU (HS-DSCH)
biotag_Context: O,O,B-Connection,O,O,O,O,B-Connection,O,O,O,O,O,O,B-Network Function,I-Network Function,O,O,O,O,O,O,B-Connection,B-Connection,O,O,B-Specification,O,O,O,O,B-Connection,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,B-Network Function,I-Network Function,O,O,O,O,O,B-Connection,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,O,O,O,O,O,O,O,B-Network Function,I-Network Function,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,B-Technology,O,O,O,O,O,O,B-Specification,O,O,O,O,O,B-Network Function,I-Network Function,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,B-Parameter,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,B-Parameter,O,O,O,O,B-Network Function,I-Network Function,O,O,O,B-Parameter,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: O,B-Protocol,I-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,B-Connection,I-Connection,I-Connection,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Parameter,O,O,B-Protocol,O,O,B-Protocol,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,B-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O