in the UE and stopped when layer 3 receives either RRC connection reject or RRC connection setup message. Therefore, T300 should be set long enough to cover all message 3 and message 4 transmissions. However, it should be noted that in case T300 is increased the terminal can transmit more preambles (not restricted by PREAMBLE_TRANSMISSION_COUNTER = preamble? Trans Max + 1 as described earlier) causing degradation of random access setup success rate. Example of T300 tuning and its impact on RRC connection setup success rate and random access setup success rate is shown in Figure 12.15. Message 5, Radio Resource Control Connection Setup Complete Message Transmission The UE does not have any uplink grant for RRC connection setup complete (message 5) message transmission SO before message 5 can be transmitted the UE needs to send scheduling request (SR) on physical uplink control channel (PUCCH) and wait for uplink capacity grant on PDCCH. Successful message 5 transmission (and reception by eNodeB) is impacted by PUCCH power control, PUSCH power control and PDCCH DCI decoding (to send the uplink capacity grant with high enough CCE aggregation level) and the resource allocation on PUSCH for the actual message 5 delivery (selected MCS and number of PRBs). Power control for both PUCCH and PUSCH must be set SO that high enough transmission power from the UE is possible when transmitting message 5 and scheduling request. Message 5 is the first message sent by the UE that is following the given power control strategy and uses dynamic PUSCH scheduling. The UE power for PUSCH is given by Eq. 12.3 according to [1] (assuming no simultaneous PUSCH and PUCCH transmission): PPUSCH PCMAX(i), (12.3) Olog10(MPUSCH(i)) + -PO_PUSCH(i)+a(j) . +f(i) LTE Small Cell Optimization where PCMAX is the configured UE transmit power defined in [2] in subframe i for serving cell c; i is the subframe number; For PUSCH (re)transmissions corresponding to the dynamic scheduling j equals 1; MPUSCH(i) is the bandwidth of the PUSCH resource assignment e