name: RLC
full_form: Radio Link Control
context: an AM RLC entity depending on the mode of data transfer that the RLC entity is configured to provide. A TM RLC entity is configured either as a transmitting TM RLC entity or a receiving TM RLC entity. The transmitting TM RLC entity receives RLC SDUs from upper layer and sends RLC PDUs to its peer receiving TM RLC entity via lower layers. The receiving TM RLC entity delivers RLC SDUs to upper layer and receives RLC PDUs from its peer transmitting TM RLC entity via lower layers. An UM RLC entity is configured either as a transmitting UM RLC entity or a receiving UM RLC entity. The transmitting UM RLC entity receives RLC SDUs from upper layer and sends RLC PDUs to its peer receiving UM RLC entity via lower layers. The receiving UM RLC entity delivers RLC SDUs to upper layer and receives RLC PDUs from its peer transmitting UM RLC entity via lower layers. An AM RLC entity consists of a transmitting side and a receiving side. The transmitting side of an AM RLC entity receives RLC SDUs from
description: Radio Link Control (RLC) is a protocol layer in the LTE radio interface that manages data transfer between the UE (User Equipment) and the eNodeB (evolved Node B). It provides three modes of operation: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). Each mode has distinct configurations for transmitting and receiving RLC entities, which handle RLC SDUs (Service Data Units) and PDUs (Protocol Data Units).
explanation: The text describes RLC as a protocol layer within the LTE radio interface responsible for managing data transfer. This clearly classifies it as a telecommunications protocol.
section_title: 4.2.1RLC entities
biotag_Context: O,B-Miscellaneous,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Organization,B-Protocol,O,O,O,O,O,O,O,B-Organization,B-Protocol,O,O,O,O,B-Organization,B-Protocol,O,O,O,B-Organization,B-Protocol,O,O,B-Protocol,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Organization,B-Protocol,O,O,O,O,O,O,B-Organization,B-Protocol,O,O,B-Protocol,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Organization,B-Protocol,O,O,O,O,O,B-Mode,B-Protocol,O,O,O,O,O,O,O,B-Mode,B-Protocol,O,O,O,O,B-Mode,B-Protocol,O,O,O,B-Mode,B-Protocol,O,O,B-Protocol,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Mode,B-Protocol,O,O,O,O,O,O,B-Mode,B-Protocol,O,O,B-Protocol,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Mode,B-Protocol,O,O,O,O,O,B-Miscellaneous,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,B-Protocol,O,O,B-Protocol,O,O
biotag_Description: B-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Parameter,I-Parameter,O,B-Mode,I-Mode,O,O,B-Mode,I-Mode,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O