name: T3247
full_form: Timer T3247
context: If the authentication response (RES or SRES) is not valid, the network response depends upon the type of identity used by the mobile station in the first message, that is: - the TMSI was used; or - the IMSI was used. If the TMSI has been used, the network may decide to initiate the identification procedure. If the IMSI given by the mobile station then differs from the one the network had associated with the TMSI, the authentication should be restarted with the correct parameters. If the IMSI provided by the MS is the expected one (i.e. authentication has really failed), the network should send an AUTHENTICATION REJECT message to the mobile station. If the IMSI has been used, or the network decides not to try the identification procedure, an AUTHENTICATION REJECT message should be transferred to the mobile station. After having sent this message, all MM connections in progress (if any) are released and the network should initiate the RR connection release procedure described in subclause 3.5.of 3GPP TS 44.018 [84] (A/Gb mode only), 3GPP TS 25.331 [23c] (UTRAN Iu mode only), or in 3GPP TS 44.118 [111] (GERAN Iu mode only). Upon receipt of an AUTHENTICATION REJECT message, a) if the message has been successfully integrity checked by the lower layers, the mobile station shall set the update status in the SIM/USIM to U3 ROAMING NOT ALLOWED, delete from the SIM/USIM the stored TMSI, LAI and ciphering key sequence number. The SIM/USIM shall be considered as invalid until switching off or the SIM/USIM is removed. If the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. If the MS maintains a counter for "SIM/USIM considered invalid for GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. b) if the message is received without integrity protection, then the MS shall start timer T3247 with a random value uniformly drawn from the range between 30 minutes and 60 minutes, if the timer is not running (see subclause 4.1.1.6A). Additionally, the MS shall: - if the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services" events and the counter has a value less than an MS implementation-specific maximum value, proceed as specified in subclause 4.1.1.6A, list item 1.a) for the case a LOCATION UPDATING REJECT message is received without integrity protection. Additionally, if the MS maintains a counter for "SIM/USIM considered invalid for GPRS services", then the MS shall increment this counter; and - otherwise proceed as specified under list item a) above for the case that the message has been successfully checked by the lower layers. List item b) above is also applicable, if the message is received in A/Gb mode. If the AUTHENTICATION REJECT message is received in the state IMSI DETACH INITIATED the mobile station shall follow subclause 4.3.4.3. If the AUTHENTICATION REJECT message is received in any other state the mobile station shall abort any MM specific, MM connection establishment or call re-establishment procedure, stop any of the timers T3210, T3230, T3214 or T3216 (if they were running), release all MM connections (if any), start timer T3240 and enter the state WAIT FOR NETWORK COMMAND, expecting the release of the RR connection. If the RR connection is not released within a given time controlled by the timer T3240, the mobile station shall abort the RR connection. In both cases, either after a RR connection release triggered from the network side or after a RR connection abort requested by the MS-side, the MS enters state MM IDLE, substate NO IMSI.
description: A timer used by the mobile station to wait for a random period before taking action.
explanation: Categorized as a Timer because it is a specific time interval used by the mobile station.
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,B-Parameter,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,I-Message,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,I-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Interface,I-Interface,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Specification,I-Specification,I-Specification,O,O,O,O,B-Specification,I-Specification,I-Specification,O,O,B-Mode,I-Mode,O,O,O,B-Organization,B-Specification,O,O,O,B-Mode,I-Mode,O,O,O,O,O,B-Message,I-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,B-Parameter,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Technology,O,O,O,B-Parameter,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Technology,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,I-Message,O,O,O,O,O,O,B-State,I-State,I-State,O,O,O,O,O,O,O,O,O,B-Message,I-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Interface,I-Interface,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Parameter,O,O,B-Network Function,O,O,B-Miscellaneous,O
biotag_Description: O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O