Section: 4.5.3.1 Release of associated RR connection
Content: If all MM connections are released by their CM entities, and no RRLP procedure (see 3GPP TS 44.031[ None ]  [23b]) and no LCS procedure over RRC (see 3GPP TS 25.331[ None ]  [23c]) is ongoing, the mobile station shall set timer T3240 and enter the state WAIT FOR NETWORK COMMAND, expecting the release of the RR connection. If all MM connections are released by their CM entities and an RRLP procedure or LCS procedure over RRC is ongoing, the MS shall start the timer T3241 and enter the state RR CONNECTION RELEASE NOT ALLOWED. If the MS is expecting the release of the RR connection in MM state WAIT FOR NETWORK COMMAND and an RRLP procedure or LCS procedure over RRC is started, the MS shall stop the timer T3240, start the timer T3241 and enter the state RR CONNECTION RELEASE NOT ALLOWED. If the MS is in MM state RR CONNECTION RELEASE NOT ALLOWED and the ongoing RRLP procedure or LCS procedure over RRC is finished, the MS shall stop the timer T3241, reset and start the timer T3240 and shall enter the state WAIT FOR NETWORK COMMAND. If the MS receives the "Extended wait time" for CS domain from the lower layers when no location updating or CM service request procedure is ongoing, the MS shall ignore the "Extended wait time". In the network, if the last MM connection is released by its user, the MM sublayer may decide to release the RR connection. The RR connection may be maintained by the network, e.g. in order to establish another MM connection. If the RR connection is not released within a given time controlled by the timer T3240 or T3241, 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 shall return to MM IDLE state; the service state depending upon the current update status as specified in subclause 4.2.3. If the UE determines a service state in which a Location Update procedure is required, the UE shall reset the location update attempt counter and immediately start the Location Updating procedure as specified in subclause 4.4.4.