name: ARQ
full_form: Automatic Repeat Request
context: For RLC AM, ARQ can be conducted hop-by-hop along access and backhaul links (Figure 8.2.1-1b, c, d, e and 8.2.1-2). It is also possible to support ARQ end-to-end between UE and IAB-donor (Figure 8.2.1-1a). Since RLC segmentation is a just-in-time process it is always conducted in a hop-by-hop manner. The figures show example protocol stacks and do not preclude other possibilities. The study includes hop-by-hop and end-to-end RLC ARQ. The type of multi-hop RLC ARQ and adaptation-layer placement have the following interdependence: - End-to-end ARQ: Adaptation layer is integrated with MAC layer or placed above MAC layer; - Hop-by-hop ARQ: No interdependence. Table 8.2.3-1 summarizes observations for end-to-end and hop-by-hop ARQ. Table 8.2.3-1: Observations for end-to-end and hop-by-hop ARQ The issue of end to end reliability in hop-by-hop RLC ARQ case could be addressed by specifying, e.g., the following mechanisms: - Modification of PDCP protocol/procedures. This mechanism would not be
description: Automatic Repeat Request (ARQ) is a protocol used for error control in data transmission. It ensures reliable communication by automatically retransmitting erroneous or lost packets.
explanation: The description explicitly states that ARQ is a protocol designed to manage errors and ensure reliability in data transmission, aligning with the definition of a protocol.
section_title: 8.2.3Multi-hop RLC ARQ
biotag_Context: O,B-Protocol,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,B-Protocol,O,O,B-Device,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,B-Protocol,O,O,O,O,O,B-Protocol,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,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,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,B-Protocol,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O
biotag_Description: B-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O