name: WAIT FOR RR CONNECTION (LOCATION UPDATING)
full_form: Wait for RR Connection (Location Updating)
context: 0 NULL The mobile station is inactive (e.g. power down). Important parameters are stored. Only manual action by the user may transfer the MM sublayer to another state. 3 LOCATION UPDATING INITIATED A location updating procedure has been started and the MM awaits a response from the network. The timer T3210 is running. 5 WAIT FOR OUTGOING MM CONNECTION The MM connection establishment has been started, and the MM awaits a response from the network. The timer T3230 is running. 6 MM CONNECTION ACTIVE The MM sublayer has a RR connection to its peer entity on the network side. One or more MM connections are active. 7 IMSI DETACH INITIATED The IMSI detach procedure has been started. The timer T3220 is running. 8 PROCESS CM SERVICE PROMPT The MM sublayer has a RR connection to its peer entity on the network side. The Mobile Station has received a CM SERVICE PROMPT message but has not yet responded $(CCBS)$. 9 WAIT FOR NETWORK COMMAND The MM sublayer has a RR connection to its peer entity in the network, but no MM connection is established. The mobile station is passive, awaiting further commands from the network. The timer T3240 may be running. 10 LOCATION UPDATE REJECTED A location updating procedure has been rejected and RR connection release is awaited. The timer T3240 is running. Figure 4.1a/3GPP TS 24.008: Overview mobility management protocol/MS Side Additions to Figure 4.1a/3GPP TS 24.008 13. WAIT FOR RR CONNECTION (LOCATION UPDATING) The MM sublayer has requested RR connection establishment for starting the location updating procedure. 14. WAIT FOR RR CONNECTION (MM CONNECTION) The MM sublayer has requested RR connection establishment for dedicated mode for starting the MM connection establishment. 15. WAIT FOR RR CONNECTION (IMSI DETACH) The MM sublayer has requested RR connection establishment for starting the IMSI detach procedure. 17. WAIT FOR REESTABLISH A lower layer failure has occurred and re-establishment may be performed from the disturbed CM layer entities. 18. WAIT FOR RR ACTIVE The MM sublayer has requested activation of the RR sublayer. 19. MM IDLE There is no MM procedure running and no RR connection exists except that a local MM context may exist when the RR sublayer is in Group Receive mode. This is a compound state, and the actual behaviour of the mobile station to Connection Management requests is determined by the actual substate as described hereafter. 20. WAIT FOR ADDITIONAL OUTGOING MM CONNECTION. The MM connection establishment for an additional MM connection has been started, and the MM awaits response from the network. 21. MM CONNECTION ACTIVE (GROUP TRANSMIT MODE) (Only applicable for mobile stations supporting VGCS talking:) The MM sublayer has a RR connection on the VGCS channel to its peer entity on the network side. Only one MM connection is active. 22. WAIT FOR RR CONNECTION (GROUP TRANSMIT MODE) (Only applicable for mobile stations supporting VGCS talking:) The MM sublayer has requested to perform an uplink access on the VGCS channel. 23. LOCATION UPDATING PENDING (Only applicable for GPRS MS operation modes A and B; not shown in figure 4.1a) A location updating has been started using the combined GPRS attach procedure or the combined GPRS routing area updating procedure. 24. IMSI DETACH PENDING (Only applicable for GPRS MS operation modes A and B; not shown in figure 4.1a) An IMSI detach for non-GPRS services has been started using the combined GPRS detach procedure at not switching off. 25. RR CONNECTION RELEASE NOT ALLOWED (Only applicable for mobile stations supporting RRLP procedures (see 3GPP TS 44.031 [23b]) or LCS procedures over RRC (see 3GPP TS 25.331 [23c])). All MM connections are released by their CM entities, but the RR connection is maintained by the network due to an ongoing RRLP procedure or LCS procedure over RRC.
description: The MM sublayer has requested RR connection establishment for starting the location updating procedure.
explanation: Classified as a State because it represents an ongoing process.
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,B-Network Function,I-Network Function,O,O,O,O,B-State,I-State,I-State,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-State,I-State,I-State,I-State,I-State,O,B-Network Function,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-State,I-State,I-State,O,B-Network Function,I-Network Function,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Interface,I-Interface,O,O,O,B-State,I-State,I-State,O,B-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,B-Parameter,O,O,O,B-State,I-State,I-State,I-State,O,B-Network Function,I-Network Function,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,B-Device,I-Device,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,B-State,I-State,I-State,I-State,O,B-Network Function,I-Network Function,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,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-State,I-State,I-State,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,O,O,O,O,O,O,O,O,B-Specification,I-Specification,O,B-State,I-State,I-State,I-State,I-State,I-State,O,B-Network Function,I-Network Function,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-State,I-State,I-State,I-State,O,O,O,B-Network Function,I-Network Function,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-State,I-State,I-State,I-State,I-State,I-State,O,B-Network Function,I-Network Function,O,O,B-Network Function,O,O,O,O,O,B-Parameter,O,O,O,B-State,I-State,I-State,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Network Function,O,O,B-Network Function,I-Network Function,O,O,O,O,O,B-Network Function,O,O,B-State,I-State,O,O,O,B-Network Function,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Network Function,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Measurement,I-Measurement,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-State,I-State,I-State,O,O,O,O,O,O,O,O,O,B-Service,O,O,B-Network Function,I-Network Function,O,O,B-Network Function,O,O,O,B-Service,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-State,I-State,I-State,I-State,O,O,O,O,O,O,O,O,O,B-Service,O,O,B-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,B-Service,O,O,O,O,O,O,O,O,B-Technology,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,B-Technology,O,O,O,O,O,B-Parameter,O,O,O,O,O,B-Technology,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,B-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Organization,B-Specification,O,O,O,B-Service,O,O,B-Protocol,O,B-Specification,I-Specification,I-Specification,O,O,B-Interface,I-Interface,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,B-Service,O,O,O
biotag_Description: O,B-Network Function,I-Network Function,O,O,B-Network Function,O,O,O,O,O,O,O,O