name: RB
full_form: Radio Bearer
context: In the steady state phase each cell gets a cell sync burst plan which defines when cell sync bursts shall be transmitted and when cell sync bursts should be received. In this phase, the normal traffic is supported, i.e. the regular cell synchronisation monitoring and update is done in parallel to ongoing UE connections. The following procedures have to be considered: - Cell Sync Burst Instruction: Establishing a synchronisation schedule - Cell Sync Bursts Measurement Report - Synchronisation Adjustment procedure Cell Sync Burst Instruction: Defining the schedule consists of defining the transmission parameters and defining the receiving parameters. I.e. it is defined at which radio frames the cell shall transmit a sync burst and at which radio frames the cell shall receive sync bursts. Information elements required: - Time slot: This defines a PRACH timeslot to use - For all SFN where the cell transmits a sync burst: - Cell Sync Burst Code - Cell Sync Burst Code Shift - Tx Power (for
description: A Radio Bearer (RB) is a logical channel that carries specific types of data or services over the radio interface between the User Equipment (UE) and the Universal Terrestrial Radio Access Network (UTRAN). In the context of Multimedia Broadcast Multicast Service (MBMS), an MBMS RB is used to transmit multimedia content from a single source to multiple recipients. The release of an MBMS RB can be initiated explicitly through signaling or implicitly based on the absence of the RB in the MBMS SERVICE INFORMATION flow.
explanation: The context describes the Radio Bearer (RB) as a mechanism for transmitting specific data or services over the radio interface, specifically highlighting its role in MBMS transmissions. This indicates that RB is related to data transmission paths, which aligns with the Channel category.
section_title: 5.2.6	MBMS Radio Bearer Release in the UE
biotag_Context: 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,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,I-Message,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,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-Connection,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: O,B-Connection,I-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,I-Device,O,O,O,B-Network,I-Network,I-Network,I-Network,I-Network,O,O,O,O,O,B-Service,I-Service,I-Service,I-Service,O,O,B-Service,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Service,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,B-Service,O,O,O