Stupidcaterpillar

3G UE Protocol timers, counters, other parameters and default configurations

Posted on: September 8, 2010

Timers for UE

Timer

Start

Stop

At expiry

T300 Transmission of RRC CONNECTION REQUEST Reception of RRC CONNECTION SETUP Retransmit RRC CONNECTION REQUEST if V300 =< N300, else go to Idle mode
T302 Transmission of CELL UPDATE/URA UPDATE Reception of CELL UPDATE CONFIRM/URA UPDATE CONFIRM Retransmit CELL UPDATE/URA UPDATE if V302 =< N302, else, go to Idle mode
T304 Transmission of UE CAPABILITY INFORMATION Reception of UE CAPABILITY INFORMATION CONFIRM Retransmit UE CAPABILITY INFORMATION if V304 =< N304, else initiate a cell update procedure
T305 Entering CELL_FACH or URA_PCH or CELL_PCH state. Reception of CELL UDPATE CONFIRM/URA UPDATE CONFIRM. Entering another state. Transmit CELL UPDATE if T307 is not activated and the UE detects “in service area”. Otherwise, if T307 is not active, start T307.
T307 When the timer T305 has expired and the UE detects “out of service area”. When the UE detects “in service area”. Transit to idle mode
T308 Transmission of RRC CONNECTION RELEASE COMPLETE Not stopped Transmit RRC CONNECTION RELEASE COMPLETE if V308 <=N308, else go to idle mode.
T309 Upon reception of CELL CHANGE ORDER FROM UTRAN message Successful response to a connection establishment request in the new cell. Resume the connection to UTRAN
T310 Transmission of PUSCH CAPACITY REQUEST Reception of PHYSICAL SHARED CHANNEL ALLOCATION Transmit PUSCH CAPACITY REQUEST if V310 =< N310, else procedure stops.
T311 Reception of PHYSICAL SHARED CHANNEL ALLOCATION message with the CHOICE “PUSCH allocation” set to “PUSCH allocation pending”. Reception of PHYSICAL SHARED CHANNEL ALLOCATION message with CHOICE “PUSCH allocation” set to “PUSCH allocation assignment”. UE may initiate a PUSCH capacity request procedure.
T312 When the UE starts to establish dedicated CH When the UE detects N312 “in sync” indication from L1. The criteria for physical channel establishment failure is fulfilled
T313 When the UE detects consecutive N313 “out of sync” indication from L1. When the UE detects consecutive N315 “in sync” indication from L1. The criteria for Radio Link failure is fulfilled
T314 When the criteria for radio link failure are fulfilled.

The timer is started if radio bearer(s) that are associated with T314 exist of if only RRC connection exists.

When the Cell Update procedure has been completed. See subclause 8.3.1.13
T315 When the criteria for radio link failure are fulfilled.

The timer is started only if radio bearer(s) that are associated with T315 exist.

When the Cell Update procedure has been completed. See subclause 8.3.1.14
T316 When the UE detects “out of service area” in URA_PCH or CELL_PCH state When the UE detects “in service area”. Initiate cell update procedure if in service area is detected. Otherwise start timer T317, transit to CELL_FACH state and initiate cell update procedure when the UE detects “in service area”.
T317 When the T316 expires or when in CELL_FACH state, the UE detects “out of service area”. When the UE detects “in service area”. Transit to idle mode

Counters for UE

Counter Reset Incremented When reaching max value
V300 When initiating the procedure RRC connection establishment Upon expiry of T300. When V300 > N300, the UE enters idle mode.
V302 When initiating the procedure Cell update or URA update Upon expiry of T302 When V302 > N302 the UE enters idle mode.
V304 When sending the first UE CAPABILITY INFORMATION message. Upon expiry of T304 When V304 > N304 the UE initiates the Cell update procedure
V308 When sending the first RRC CONNECTION RELEASE COMPLETE message in a RRC connection release procedure. Upon expiry of T308 When V308 > N308 the UE stops re-transmitting the RRC CONNECTION RELEASE COMPLETE message.
V310 When sending the first PUSCH CAPACITY REQUEST message in a PUSCH capacity request procedure Upon expiry of T310 When V310 > N310 the UE stops re-transmitting the PUSCH CAPACITY REQUEST message.

UE constants and parameters

Constant Usage
N300 Maximum number of retransmissions of the RRC CONNECTION REQUEST message
N302 Maximum number of retransmissions of the CELL UPDATE / URA UPDATE message
N304 Maximum number of retransmissions of the UE CAPABILITY INFORMATION message
N308 Maximum number of retransmissions of the RRC CONNECTION RELEASE COMPLETE message
N310 Maximum number of retransmission of the PUSCH CAPACITY REQUEST message
N312 Maximum number of “in sync” received from L1.
N313 Maximum number of successive “out of sync” received from L1.
N315 Maximum number of successive “in sync” received from L1 during T313 is activated.
About these ads

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


  • aamadmi: Great Job done ! for a one stop source for references of relevant timers.
  • Idriss: Hi, it is very interessent, but i need know if the measuse is tooken for a special code or for the best signal code of a node B??
  • J: Hello, I'm trying to find a bit more information regarding GMM cause 98 however I don't quite understand the, "see annex.H subclause H.6.2". I would

Categories

Follow

Get every new post delivered to your Inbox.