FIG. 3 is a flow diagram illustrating one implementation of a method 300 for performing a scheduling request procedure by an eNB 160. The eNB 160 may transmit one or more RRC messages to the UE 102 to configure, for the UE 102, one or more of PUCCH Cell Groups, the PUCCH SCell, and SR. The RRC layer of the eNB 160 may assume or consider that the RRC layer of the UE 102 configures RRC layer and/or lower layers (e.g., PHY layer, MAC layer, RLC layer, PDCP layer) of the UE 102 according to RRC configurations which may be configured by the RRC messages, broadcasted system information, and so on. For example, the eNB 160 may 302 transmit a RRC message including a first parameter (e.g., dsr-TransMax) related to a maximum number of scheduling request transmission for a secondary cell. The eNB 160 may 304 receive a scheduling request on a Physical Uplink Control Channel (PUCCH) on the secondary cell, wherein a scheduling request procedure is performed based on the first parameter.
A sr-ProhibitTimer IE, the schedulingRequestConfig IE, schedulingRequestConfig-v1020 IE, PhysicalConfigDedicated IE, a PhysicalConfigDedicatedPSCell-r12 IE, physicalConfigDedicatedSCell-r10 IE, etc may be transmitted from the eNB 160 to the UE 102 by using a RRC connection reconfiguration message, a RRC connection reestablishment message, a RRC connection setup message, etc. eNB 160 may configure UE 102 with dsr-TransMax for the PUCCH SCell. Configuring dsr-TranMax for the PUCCH SCell independently of the PCell may provide benefits of flexibility of configuration of upper limit of the number of SR transmission.
