Beruflich Dokumente
Kultur Dokumente
STATE
NUM. VALUE
T3402 Default 12 min. EMM DEREGISTERED
NOTE 1 EMM REGISTERED
ATTEMPTING TO-
ATTACH EMM
REGISTERED.
ATTEMPTING TO-
UPDATE
T3412 Default 54 min. EMM REGISTERED
NOTE 2
NOTE 5
T3417 5s EMM-
SERVICEREQUESTINITI
ATED
EMM REGISTERED
EMM-TRACKINGARE
AUPDATINGINITIATED
EMM
DEREGISTEREDINITIAT
ED
EMM-
SERVICEREQUESTINITI
ATED
T3420 15s EMM REGISTERED
INITIATED
EMM REGISTERED
EMM DEREGISTERED
INITIATED
EMM-TRACKINGAREA
UPDATING INITIATED
EMM-SERVICE
REQUEST INITIATED
T3421 15s EMM DEREGISTERED
INITIATED
T3423 NOTE 3 EMM REGISTERED
EMM DEREGISTERED
INITIATED
EMM-SERVICE
REQUEST INITIATED
EMM REGISTERED
T3442 NOTE 4 EMM REGISTERED
Note 1 The default value of this timer is used if the network does not indicate another value in an EMM signa
Note 2 The value of this timer is provided by the network operator during the attach and tracking area upda
The value of this timer may be provided by the network in the ATTACH ACCEPT message and TRACK
Note 3
identical to the value of T3412.
The value of this timer is provided by the network operator when a service request for CS fallback is
Note 4
available".
The default value of this timer is used if the network does not indicate a value in the TRACKING ARE
timer.
Note 5
(This Timer value is set in Attach Accept message as well).
Reception of
RRCConnectionSetup or
RRCConnectionReject
T300 Transmission of message, cell re-
RRCConnectionRequest selection and upon
abortion of connection
establishment by upper
layers
Reception of
RRCConnectionReestabl
ishment or
Transmission of
RRCConnectionReestabl
T301 RRCConnectionReestabilsh
ishmentReject message
mentRequest
as well as when the
selected cell becomes
unsuitable
Reception of
Upon entering
RRCConnectionReject
T302 RRC_CONNECTED and
while performing RRC
upon cell re-selection
connection establishment
Reception of
Criterion for successful
RRCConnectionReconfigur
completion of handover
ation message including
to EUTRA or cell change
the MobilityControl Info or
T304 order is met (the
reception of
criterion is specified in
MobilityFromEUTRAComm
the target RAT in case
and message including
of inter-RAT)
CellChangeOrder
Access barred while
Upon entering
performing RRCconnection
T305 RRC_CONNECTED and
establishment for mobile
upon cell re-selection
originating signalling
consecutive in-sync
Upon detecting physical
indications from lower
layer problems i.e. upon
layers, upon triggering
receiving N310
T310 the handover procedure
consecutive out-of-sync
and upon initiating the
indications from lower
connection re-
layers
Upon initiating the establishment
Selection of a suitable
RRCconnection
T311 E-UTRA cell or a cell
reestablishmentmprocedur
using another RAT.
e
Upon entering
Upon receiving t320 or
RRC_CONNECTED,
upon cell (re)selection to
when PLMN selection is
E-UTRA from another RAT
performed on request
with validity time
T320 by NAS, or upon cell
configured for dedicated
(re)selection to another
priorities (in which case
RAT (in which case the
the remaining validity time
timer is carried on to
is applied).
the other RAT).
network operator during the attach and tracking area updating procedures. (This Timer value is set in Attach Accept mess
y the network in the ATTACH ACCEPT message and TRACKING AREA UPDATE ACCEPT message. The default value of this t
network operator when a service request for CS fallback is rejected by the network with EMM cause #39 "CS domain temp
he network does not indicate a value in the TRACKING AREA UPDATE ACCEPT message and the UE does not have a stored
message as well).
At expiry
Go to RRC_IDLE
Enter RRC_IDLE
None
e.
EPT message and the UE does not have a stored value for this
LTE EPS mobility management timers - EMM timers
Lately many times I had to reach towards the EPS Mobility Management (EMM) timers, because it took me some time to google them here y
In the two tables you can easily find the times name it's default or suggested value, what is triggering it and what happens in case it will fi
T3402
T3410
T3411
T3412
T3416
T3417
T3417ext
T3418
T3418
T3420
T3421
T3423
T3430
T3440
T3442
TIMER NUM.
T3413
T3422
T3450
T3460
T3470
Mobile reachable
Management (EMM) timers, because it took me some time to google them here you go. Hope any one will find them as useful I did.
fault or suggested value, what is triggering it and what happens in case it will finally expire.
Default 12 min.
NOTE 1
15s
10s
Default 54 min.
NOTE 2
NOTE 5
30s
5s
10s
20s
20s
15s
15s
NOTE 3
15s
10s
NOTE 4
NOTE 1: The default value of this timer is used if the network does not indicate another value in an EMM
NOTE 2: The value of this timer is provided by the network operator during the attach and tracking area u
NOTE 3: The value of this timer may be provided by the network in the ATTACH ACCEPT message and TRA
NOTE 4: The value of this timer is provided by the network operator when a service request for CS fallbac
NOTE 5: The default value of this timer is used if the network does not indicate a value in the TRACKING
NOTE 2
6s
6s
6s
6s
NOTE 3
borted on the fifth expiry of the relevant timer. Exceptions are described in the corresponding procedure description.
ork dependent.
ork dependent. If ISR is activated, the default value of this timer is 4 minutes greater than T3423.
m here you go. Hope any one will find them as useful I did.
it will finally expire.
STATE
EMM-DEREGISTERED
EMM-REGISTERED
EMM-REGISTERED-INITIATED
EMM-DEREGISTERED. ATTEMPTING-TO-ATTACH
EMM-REGISTERED. ATTEMPTING-TO-UPDATE
EMM-REGISTERED
EMM-REGISTERED-INITIATED
EMM-REGISTERED
EMM-DEREGISTERED-INITIATED
EMM-TRACKING-AREA-UPDATING-INITIATED
EMM-SERVICE-REQUEST-INITIATED
EMM-SERVICE-REQUEST-INITIATED
EMM-SERVICE-REQUEST-INITIATED
EMM-REGISTERED-INITIATED
EMM-REGISTERED
EMM-TRACKING-AREA-UPDATING-INITIATED
EMM-DEREGISTERED-INITIATED
EMM-SERVICE-REQUEST-INITIATED
EMM-REGISTERED-INITIATED
EMM-REGISTERED
EMM-DEREGISTERED-INITIATED
EMM-TRACKING-AREA-UPDATING-INITIATED
EMM-SERVICE-REQUEST-INITIATED
EMM-DEREGISTERED-INITIATED
EMM-REGISTERED
EMM-TRACKING-AREA-UPDATING-INITIATED
EMM-REGISTERED-INITIATED
EMM-TRACKING-AREA-UPDATING-INITIATED
EMM-DEREGISTERED-INITIATED
EMM-SERVICE-REQUEST-INITIATED
EMM-REGISTERED
EMM-REGISTERED
is used if the network does not indicate another value in an EMM signalling procedure.
ded by the network operator during the attach and tracking area updating procedures.
provided by the network in the ATTACH ACCEPT message and TRACKING AREA UPDATE ACCEPT message. The default value o
ded by the network operator when a service request for CS fallback is rejected by the network with EMM cause #39 "CS doma
is used if the network does not indicate a value in the TRACKING AREA UPDATE ACCEPT message and the UE does not have a
EMM-REGISTERED
EMM-DEREGISTERED-INITIATED
EMM-COMMON-PROC-INIT
EMM-COMMON-PROC-INIT
EMM-COMMON-PROC-INIT
At attach failure due to lower layer failure, T3410 timeout or attach rejected with
other EMM cause values than those treated in subclause 5.5.1.2.5.
At tracking area updating failure due to lower layer failure, T3430 timeout or TAU
rejected with other EMM cause values than those treated in subclause 5.5.3.2.5.
EXTENDED SERVICE REQUEST sent in case e in subclause 5.6.1.1 and the CSFB
response was set to "CS fallback accepted by the UE"
ATTACH REJECT, DETACH REQUEST, TRACKING AREA UPDATE REJECT with any of
the EMM cause #11, #12, #13, #14 or #15
SERVICE REJECT received with any of the EMM cause #11, #12, #13 or #15
TRACKING AREA UPDATE ACCEPT received after the UE sent TRACKING AREA
UPDATE REQUEST in EMM-IDLE mode with no "active" flag
SERVICE REJECT received with EMM cause #39 "CS domain temporarily not
available"
EMM signalling procedure.
area updating procedures.
nd TRACKING AREA UPDATE ACCEPT message. The default value of this timer is identical to the value of T3412.
fallback is rejected by the network with EMM cause #39 "CS domain temporarily not available".
CKING AREA UPDATE ACCEPT message and the UE does not have a stored value for this timer.
The mobile reachable timer expires while the network is in EMM-IDLE mode
NORMAL STOP
he value of T3412.
e".
.
Initiation of the periodic TAU procedure if the UE is not attached for emergency bearer services.
Implicit detach from network if the UE is attached for emergency bearer services.
On first expiry, the UE should consider the network as false and follow item f of subclause 5.4.2.7, if the
services.
On first expiry, the UE will follow subclause 5.4.2.7 under “For items c, d, and e:”, if the UE is attached
On first expiry, the UE should consider the network as false and follow item f of subclause 5.4.2.7, if the
services.
On first expiry, the UE will follow subclause 5.4.2.7 under “For items c, d, and e:”, if the UE is attached
None
Network dependent