name: MM IDLE state
full_form: Mobility Management IDLE State
context: The IMSI detach procedure may be invoked by a mobile station if the mobile station is deactivated or if the Subscriber Identity Module (see 3GPP TS 42.017 [7] and 3GPP TS 31.102 [112]) is detached from the mobile station or as part of the eCall inactivity procedure defined in subclause 4.4.7. In A/Gb mode and GERAN Iu mode, the network indicates whether the IMSI detach/attach procedures are required by using the ATT flag which is broadcast in the L3-RR SYSTEM INFORMATION TYPE 3 message on the BCCH (see 3GPP TS 44.018 [84] subclause 10.5.2.11). The mobile station shall use the value of the ATT flag that was broadcast when the mobile station was in the MM IDLE state. In UTRAN Iu mode, the network indicates whether the IMSI detach/attach procedures are required by using the ATT flag which is included in the CS domain specific system information element (see subclause 10.5.1.12.2). The mobile station shall use the latest received value of the ATT flag. If a RR connection exists and the ATT flag indicates that the IMSI detach/attach procedures are not required, the MM sublayer will release locally any ongoing MM connections before releasing the RR connection. If an MM specific procedure is active, the release of the RR connection may be delayed until the MM specific procedure is complete. The IMSI detach procedure causes the mobile station to be indicated as inactive in the network. The mobile station is allowed to initiate the IMSI detach procedure even if the timer T3246 is running. The network proceeds with the IMSI detach procedure even if NAS level mobility management congestion control is active.
description: This is a state of the mobility management sublayer where the mobile station is idle, not actively engaged in any MM procedures.
explanation: Classified as a Protocol because it defines states and transitions within the mobility management context.
biotag_Context: O,B-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,I-Device,I-Device,O,B-Organization,B-Specification,O,O,O,B-Organization,B-Specification,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Mode,I-Mode,O,B-Network,B-Interface,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,I-Message,I-Message,I-Message,I-Message,O,O,B-Connection,O,B-Specification,I-Specification,I-Specification,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-State,I-State,O,O,B-Network,B-Interface,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Mode,O,O,O,O,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,O,O,B-Parameter,O,O,O,O,O,O,B-Network Function,I-Network Function,O,O,O,O,O,B-Interface,I-Interface,O,O,O,B-Network Function,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,I-Procedure,I-Procedure,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,B-Procedure,I-Procedure,I-Procedure,O,O,B-Protocol,O,O,O,O,O,O,O
biotag_Description: O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O