name: CB
full_form: Cell Broadcast
context: handling the HARQ protocol. There shall be one HARQ process per HS-DSCH per TTI for single stream transmission, two HARQ processes per HS-DSCH per TTI for dual stream transmission, three HARQ processes per HS-DSCH per TTI for three stream transmission (FDD only) and four HARQ processes per HS-DSCH per TTI for four stream transmission (FDD only). There shall be one HARQ entity per HS-DSCH (FDD only). The HARQ functional entity handles all the tasks that are required for hybrid ARQ. It is for example responsible for generating ACKs or NACKs. The detailed configuration of the hybrid ARQ protocol is provided by RRC over the MAC-Control SAP.In 1.28 Mcps TDD multi-frequency HS-DSCH cell, multiple HARQ processes are assigned for HS-DSCH operaton on every carrier independently, namely HARQ sub-entity; only one HARQ process is allowed to receive HS-DSCH in one TTI for each carrier. The maximum number of HARQ process per HS-DSCH per TTI on which an HS-DSCH transmission can be received is one. -
description: Cell Broadcast (CB) is a service that allows messages to be broadcast from the Cell Broadcast Centre to User Equipment (UE). It involves the transmission of user data, known as CB messages, which can be repeated at specified intervals. The service includes features such as CB repetition period, Number of Broadcast Requested, DRX Schedule Period, Reserved CB Capacity, CTCH Block Set, and CBS schedule period, all of which are used to manage and control the broadcast of CB messages.
explanation: The context describes Cell Broadcast (CB) in terms of its functionality, features, and parameters. It outlines how CB messages are transmitted, repeated, and managed within the network. Based on this description, CB is classified as a Service, as it provides a specific telecommunications offering that enables the broadcast of messages to UE.
section_title: 3.1	Definitions
biotag_Context: O,O,B-Protocol,O,O,O,O,O,B-Protocol,O,O,B-Connection,O,B-Parameter,O,O,O,O,O,B-Protocol,O,O,B-Connection,O,B-Parameter,O,O,O,O,O,B-Protocol,O,O,B-Connection,O,B-Parameter,O,O,O,O,O,O,O,O,B-Protocol,O,O,B-Connection,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,B-Connection,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,B-Protocol,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Technology,O,B-Connection,O,O,B-Protocol,O,O,O,O,B-Connection,O,O,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,O,O,O,B-Connection,O,O,B-Parameter,O,O,O,O,O,O,O,B-Protocol,O,O,B-Connection,O,B-Parameter,O,O,O,B-Connection,O,O,O,O,O,O,O
biotag_Description: B-Service,I-Service,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,I-Network Function,I-Network Function,O,B-Device,I-Device,O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O,B-Service,O,B-Procedure,O,O,O,B-Miscellaneous,O,B-Connection,O,O,O,B-Service,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O