LTE: RRC Connection Reject

Direction: E-UTRAN => UE

Signalling Radio Bearer: SRB0
RLC Mode: TM
Logical Channel: CCCH
Transport Channel: DL-SCH

The RRC CONNECTION REJECT message is used to reject the RRC connection
establishment. This message includes the IE waitTime which can be in the range
from 0 to 16 seconds. Optionally, the NW can include the IE extendedWaitTime for
the purpose of Delay Tolerant access requests
Upon receiving the RRC CONNECTION REJECT message, the UE should start
timer T302, with the timer value set to waitTime. The UE is not allowed to send
another RRCConnectionRequest for mobile originating calls, mobile originating
signalling, mobile terminating access and mobile originating CS fallback on the
same cell on which RRC CONNECTION REJECT is received until the expiry of T302

The following differences are noted as compared to UMTS RRC CONNECTION

REJECT:

1. There is no RejectionCause in the case of LTE

2. RedirectionInfo which is used to redirect the UE to another frequency/RAT
is not present in the case of LTE
3. LTE requires the higher layers to initiate new RRC CONNECTION
REQUEST after receiving RRC CONNECTION REJECT, where as in the case of
UMTS, the procedure is repeated for N300 times
Example: RRC CONNECTION REJECT Message

15 comments:

1.

hi2friendsNovember 8, 2013 at 5:05 AM

 Hi Kumar,

There is Typo:

"LTE requires the higher layers to initiate new RRC CONNECTION REJECT after
receiving RRC CONNECTION REJECT, where as in the case of UMTS, the
procedure is repeated for N300 times"

Thanks,
Rajdeep

Reply

2.

KPNovember 8, 2013 at 5:40 AM

Thanks. Type corrected

Reply

3.

UnknownMay 8, 2014 at 10:50 PM

what are the reasons of the RRC rejections from the eNB??

Reply

Replies

1.

apvvp merit listSeptember 15, 2014 at 1:13 PM

how to reach rrc exam letter

Reply

4.

AnonymousSeptember 16, 2014 at 8:14 PM

Hi Pankaj,
eNodeB may send RRC Connection Reject in response to the UE’s RRC Connection
Request. This typically happens if the cell is congested and the necessary radio
resources for the connection setup cannot be provided and/or the eNodeB is
 overloaded. According to the 3GPP TS 36.331 , there is no reject cause value
specified for the RRC connection reject message in the LTE . However RRC
connection reject message provides the wait time parameter. The value of this wait
time is an integer number in the range of 1–16. Wait time defines how many seconds
the UE should wait after reception of RRC Connection Reject until a new RRC
connection request message is sent.

Reply

5.

UnknownDecember 1, 2015 at 9:34 AM

Hi Kumar,

How will MAC know whether it has received Setup or Reject?

Do we need to add CRI mac subheader in Reject message also?

Reply

Replies

1.

KPDecember 9, 2015 at 8:53 AM

Hi Shuaib,

The MAC will never know if this setup or reject. Only RRC will be able to
understand this. CRI subheader is part of contention resolution procedure
which is separate from receiving RRC Connection setup/reject. Some
networks transmit CRI along with setup/reject and some networks do it
separately (CRI first)

Reply

6.

hamoooo271087November 13, 2016 at 1:43 AM

Hello Kumar,

Do we have to check utilization counters like Resource blocks utilization or max

number of users in a manner similar to UMTS to check the cause of RRC rejection or
it wouldn't help

Thanks
 Reply

7.

UnknownDecember 8, 2016 at 3:16 AM

Hi Kumar,

ENB sending RRC connection reject if UE sending MMEC in rrc connection request
and MMEC does not match with any MME in pool.
Is it expected behavior?

Thanks

Reply

Replies

1.

KPDecember 8, 2016 at 10:08 AM

Hi,
You mean MMEC in S-TMSI? If yes, I think that the eNodeB shouldn't reject
the connection establishment procedure based on the fact that the MMEC
doesn't match with any of the MMEs in the pool. Frankly, I am not 100% sure.
Are you sure about the reason for rejection? In any case, please update the
progress here, I am interested to know this. In the meantime, I can spend time
in checking more about it.

Reply

8.

UnknownAugust 4, 2017 at 10:01 AM

Hi,
As I know UE even can send random number instead of s-TMSI and eNB still
accepting that, so undefined MMEC should not be a reason for rejecting the request.
on the other hand if MME grouping is used, then eNB will check the load balance of
each then forward the UE to it.

Reply

9.

AnonymousApril 26, 2020 at 5:14 PM

 How RRC can decide whether to accept or reject the connection? If it is based on cell
congestion control, looking for some references for that.

Reply

10.

AnonymousJune 7, 2020 at 8:20 AM

What if the UE sends a rrcConnectionRequest with an invalid TMSI? Would it

receive rrcConnectionReject and then attempt to perform imsi attach?

Reply

11.

সুদীপ্ত June 9, 2020 at 8:41 AM

Hi Kumaraswamy, how it is determined whether rrcconnectionrelease will contain

redirectedCarrierInfo or not?

Reply

12.

AnonymousJune 8, 2023 at 9:27 AM

71726

Reply

5G Timers | T300,T301,T302,T304,T310,T311,T312 timer

at UE
This page on 5G timers mentions UE timers such as T300, T301, T302, T304, T310, T311
and T312 timer used in 5G wireless system for various functions.

5G
Function at Start Stop at Expiry
Timers
T300 The Timer T300 starts at It stops at receptionof RRC • If timer expires, The
the transmission of RRC Connection Setup or RRC UE shall reset MAC,
Connection Request Connection Reject message, cell release MAC
selection configuration and re-
establish RLC for all
RBs which are
established,
 • It informs upper
layers about the failure
to establish RRC
connection, upon
which the procedure
ends.
It stops at reception of RRC
The Timer T301 starts at Connection Re-establishment or
The timer T301 goes
transmission of RRC RRC Connection Re-establishment
T301 to RRC_IDLE state
Connection Re- Reject message as well as when
upon expiry.
establishment request. the selected cell becomes
unsuitable due to some reasons.
At expiry, it (UE)
The Timer T302 starts at
informs upper layers
reception of RRC
It stops upon entering about barring
Connection Reject while
T302 RRC_CONNECTED and upon alleviation for mobile
performing RRC
cell selection. originating data or
Connection
mobile originating
Establishment.
access.
The timer T304 starts at At expiry, in case of
reception of RRC intra 5GRA handover,
It stops as per criterion for
Connection Re- it initiates RRC
T304 successful completion of handover
configuration message connection re-
within 5GRA, handover to 5GRA.
including the Mobility establishment
Control Info. message. procedure.
At expiry, IF security
The timer T310 starts
It stops upon receiving N311 is not activated "it
upon detecting physical
consecutive in-sync indications does to RRC_IDLE
layer problems for PCell
from lower layers for PCell, upon state"
T310 i.e. upon receiving N310
triggering the handover procedure ELSE "it initiates
consecutive out-of-sync
and upon initiating the connection connection
indications from lower
re-establishment procedure. establishment
layers.
procedure"
The timer T311 starts
At expiry the timer
upon initiating the RRC It stops upon selection of a
T311 enters in RRC_IDLE
Connection re- suitable 5GRA cell.
state.
establishment procedure.
• It stops upon receiving N311 At expiry, IF security
The timer T312 starts
consecutive in-sync indications is not activated "the
upon triggering a
from lower layers timer goes to
measurement report for
• upon triggering the handover RRC_IDLE state"
T312 measurement identity for
procedure ELSE "it initiates the
which T312 has been
• upon initiating connection re- connection re-
configured while T310
establishment procedure and establishment
timer is running.
• upon the expiry of T310 timer. procedure"