name: SR
full_form: Scheduling Request
context: for new transmission. The MAC entity may be configured with zero, one, or more SR configurations. An SR configuration consists of a set of PUCCH resources for SR across different BWPs and cells. For a logical channel, at most one PUCCH resource for SR is configured per BWP. Each SR configuration corresponds to one or more logical channels. Each logical channel may be mapped to zero or one SR configuration, which is configured by RRC. The SR configuration of the LCH that triggered the BSR (subclause 5.4.5) (if such a configuration exists) is considered as corresponding SR configuration for the triggered SR. For BSR triggered by retxBSR-Timer expiry, the corresponding SR configuration for the triggered SR is that of the highest priority LCH (if such a configuration exists) that has data available for transmission at the time the BSR is triggered. RRC configures the following parameters for the scheduling request procedure: - sr-ProhibitTimer (per SR configuration); - sr-TransMax (per SR
description: The Scheduling Request (SR) procedure is a process in the MAC layer that allows the UE to request resources for uplink transmission. It involves the exchange of control information between the UE and the eNodeB, including the configuration of PUCCH resources for SR across different BWPs and cells.
explanation: The context describes the SR procedure as a specific process in the MAC layer, involving the configuration of parameters such as sr-ProhibitTimer and sr-TransMax, and the exchange of control information between the UE and the eNodeB. This indicates that SR is a sequence of network operations, which corresponds to the 'Procedure' entity type.
section_title: 7.1.1.3.3Correct handling of MAC control information / Scheduling requests
biotag_Context: O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,B-Procedure,O,O,O,O,O,O,B-Connection,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,B-Procedure,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,B-Procedure,O,O,O,B-Connection,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,B-Procedure,O,O,O,O,B-Procedure,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,B-Procedure
biotag_Description: O,B-Procedure,I-Procedure,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,B-Connection,O,O,B-Procedure,O,O,O,O,O