name: CE
full_form: Control Element
context: (highest priority listed first): - MAC CE for C-RNTI, or data from UL-CCCH; - MAC CE for (Enhanced) BFR, or MAC CE for Configured Grant Confirmation, or MAC CE for Multiple Entry Configured Grant Confirmation; - MAC CE for Sidelink Configured Grant Confirmation; - MAC CE for LBT failure; - MAC CE for SL LBT failure according to clause 5.31.2; - MAC CE for Timing Advance Report; - MAC CE for Delay Status Report; - MAC CE for SL-BSR prioritized according to clause 5.22.1.6; - MAC CE for (Extended) BSR, with exception of BSR included for padding; - MAC CE for (Enhanced) Single Entry PHR, or MAC CE for (Enhanced) Multiple Entry PHR or MAC CE for Single Entry PHR with assumed PUSCH, or MAC CE for Multiple Entry PHR with assumed PUSCH; - MAC CE for Positioning Measurement Gap Activation/Deactivation Request; - MAC CE for the number of Desired Guard Symbols; - MAC CE for Case-6 Timing Request; - MAC CE for (Extended) Pre-emptive BSR; - MAC CE for SL-BSR, with exception of SL-BSR prioritized
description: A Control Element (CE) is a type of message used in the Medium Access Control (MAC) layer to control and manage various aspects of communication in a wireless network. In this context, MAC CE refers to specific types of control elements used for different purposes such as resource allocation, configured grant confirmation, sidelink configured grant confirmation, LBT failure, timing advance report, delay status report, SL-BSR prioritization, (Extended) BSR, PHR, positioning measurement gap activation/deactivation request, desired guard symbols, case-6 timing request, and (Extended) Pre-emptive BSR.
explanation: The context describes CEs as messages used in the MAC layer for controlling communication aspects like resource allocation and grant confirmations. This clearly classifies them as messages.
section_title: 5.4.3.1.3Allocation of resources
biotag_Context: O,O,O,O,O,B-Protocol,B-Message,O,O,O,O,O,O,O,B-Protocol,B-Message,O,O,O,O,B-Protocol,B-Message,O,O,O,O,O,B-Protocol,B-Message,O,O,O,O,O,O,O,B-Protocol,B-Message,O,B-Technology,O,O,O,O,B-Protocol,B-Message,O,B-Technology,O,O,B-Protocol,B-Message,O,B-Technology,B-Technology,O,O,O,O,O,O,B-Protocol,B-Message,O,B-Parameter,I-Parameter,O,O,B-Protocol,B-Message,O,O,O,O,O,B-Protocol,B-Message,O,O,O,O,O,O,O,O,B-Protocol,B-Message,O,O,O,O,O,O,B-Message,O,O,O,O,B-Protocol,B-Message,O,O,O,O,O,O,B-Protocol,B-Message,O,O,O,O,B-Procedure,O,B-Protocol,B-Message,O,O,O,B-Procedure,O,O,O,O,B-Protocol,B-Message,O,O,O,B-Procedure,O,O,O,O,B-Protocol,B-Message,O,O,O,O,O,O,O,B-Protocol,B-Message,O,O,O,O,O,O,O,O,B-Protocol,B-Message,O,O,O,O,O,B-Protocol,B-Message,O,O,O,O,O,B-Protocol,B-Message,O,O,O,O,O,O,O
biotag_Description: O,B-Message,I-Message,O,O,O,O,O,O,O,O,O,B-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,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,O,O,O,O,O