name: HDLC
full_form: High level Data Link Control
context: - Storage of Cell Broadcast Messages. The BMC stores the Cell Broadcast messages received over the CBC-RNC interface for scheduled transmission. - Traffic volume monitoring and radio resource request for CBS. At the UTRAN side, the BMC calculates the required transmission rate for Cell Broadcast Service based on the messages received over the CBC-RNC interface, and requests for appropriate CTCH/FACH resources from RRC. - Scheduling of BMC messages. The BMC receives scheduling information together with each Cell Broadcast message over the CBC-RNC-interface. Based on this scheduling information, at the UTRAN side, BMC generates schedule messages and schedules BMC message sequences accordingly. At the UE side, BMC evaluates the schedule messages and indicates scheduling parameters to RRC, which are used by RRC to configure the lower layers for CBS discontinuous reception. - Transmission of BMC messages to UE. This function transmits the BMC messages (Scheduling and Cell Broadcast
description: High-Level Data Link Control (HDLC) is a protocol used in telecommunications networks, specifically defined by ISO/IEC 13239. In the context of this TS, HDLC is utilized with specific parameters such as Unbalanced operation, Normal response mode, and Class options supported. It also involves XID negotiation, start/stop transmission with basic transparency, and operates in half-duplex mode (Two Way Alternate - TWA).
explanation: HDLC is classified under the Protocol category because it outlines rules for data transmission over a link, adhering to specific standards and configurations as described in the context. The detailed breakdown of its definition within the provided paragraph further emphasizes its role as a protocol governing data link control.
section_title: Annex A (informative):
  HDLC description
biotag_Context: O,O,O,B-Service,I-Service,O,O,B-Network Function,O,O,B-Service,I-Service,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,B-Network Function,O,O,O,O,O,O,B-Service,I-Service,I-Service,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,O,O,B-Service,I-Service,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,B-Network Function,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Device,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Service,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Service,I-Service
biotag_Description: O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,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,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O