name: HARQ-ACK
full_form: Hybrid Automatic Repeat reQuest Acknowledgement
context: in clauses 9.1.3.1 and 9.1.3.2. If a UE would report unicast HARQ-ACK information and multicast HARQ-ACK information with same priority index in a slot, the UE multiplexes the unicast HARQ-ACK information and the multicast HARQ-ACK information following the procedures in this clause and in clauses 9.1.2, 9.1.3, and 9.1.4. If, for unicast and multicast HARQ-ACK information of same priority value, a UE - is provided - either pdsch-HARQ-ACK-Codebook = dynamic or pdsch-HARQ-ACK-Codebook-r16 for unicast HARQ-ACK information and pdsch-HARQ-ACK-Codebook = semi-static for multicast HARQ-ACK information, - or pdsch-HARQ-ACK-Codebook = semi-static for unicast HARQ-ACK information and pdsch-HARQ-ACK-Codebook = dynamic for multicast HARQ-ACK information, and - would multiplex the unicast and multicast HARQ-ACK information in a same PUCCH or PUSCH the UE - appends the HARQ-ACK codebooks for the multicast HARQ-ACK information to the HARQ-ACK codebooks for the unicast HARQ-ACK information - if , the
description: Hybrid Automatic Repeat reQuest Acknowledgement (HARQ-ACK) is a protocol used in telecommunications, specifically in the context of 5G networks, to manage and acknowledge data transmission. It involves procedures for multiplexing unicast and multicast HARQ-ACK information, as outlined in clauses 9.1.2, 9.1.3, and 9.1.4 of 3GPP TS 38.213.
explanation: The text explicitly states that HARQ-ACK is a 'protocol' used in 5G networks to manage data transmission. It outlines specific procedures and codebooks related to HARQ-ACK, further solidifying its classification as a protocol governing communication rules.
section_title: 18Multicast Broadcast Services
biotag_Context: O,O,O,O,O,O,O,B-Device,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,B-Device,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,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,B-Connection,O,B-Connection,O,B-Device,O,O,O,B-Protocol,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,O,O,B-Protocol,O,O,O,O,O
biotag_Description: B-Protocol,I-Protocol,I-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Organization,B-Specification,O