name: DETACH REQUEST
full_form: Detach Request Message
context: The following abnormal cases can be identified:
  a)        Lower layer failure
  Upon detection of a lower layer failure before the IDENTITY RESPONSE is received, the network shall abort any ongoing EMM procedure.
  b)        Expiry of timer T3470
  The identification procedure is supervised by the network by the timer T3470. The network shall, on the first expiry of the timer T3470, retransmit the IDENTITY REQUEST message and reset and restart the timer T3470. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3470, the network shall abort the identification procedure and any ongoing EMM procedure.
  c)        Collision of an identification procedure with an attach procedure
  If the network receives an ATTACH REQUEST message before the ongoing identification procedure has been completed and no attach procedure is pending on the network (i.e. no ATTACH ACCEPT/REJECT message has still to be sent as an answer to an ATTACH REQUEST message), the network shall proceed with the attach procedure.
  d)        Collision of an identification procedure with an attach procedure when the identification procedure has been caused by an attach procedure
  If the network receives an ATTACH REQUEST message before the ongoing identification procedure has been completed and an attach procedure is pending (i.e. an ATTACH ACCEPT/REJECT message has to be sent as an answer to an earlier ATTACH REQUEST message), then:
  -        If one or more of the information elements in the ATTACH REQUEST message differ from the ones received within the previous ATTACH REQUEST message, the network shall proceed with the new attach procedure; or
  -        If the information elements do not differ, then the network shall not treat any further this new ATTACH REQUEST.
  e)        Collision of an identification procedure with a UE initiated detach procedure
  Detach containing cause "switch off" within the Detach type IE:
  If the network receives a DETACH REQUEST message before the ongoing identification procedure has been completed, the network shall abort the identification procedure and shall progress the detach procedure.
  Detach containing other causes than "switch off" within the Detach type IE:
  If the network receives a DETACH REQUEST message before the ongoing identification procedure has been completed, the network shall complete the identification procedure and shall respond to the detach procedure as described in clauseÂ 5.5.2.
  f)        Collision of an identification procedure with a tracking area updating procedure
  If the network receives a TRACKING AREA UPDATE REQUEST message before the ongoing identification procedure has been completed, the network shall progress both procedures.
  g)        Collision of an identification procedure with a service request procedure
  If the network receives an EXTENDED SERVICE REQUEST message for CS fallback or 1xCS fallback before the ongoing identification procedure has been completed, the network shall progress both procedures.
  h)        Lower layers indication of non-delivered NAS PDU due to handover
  If the IDENTITY REQUEST message could not be delivered due to an intra MME handover and the target TA is included in the TAI list, then upon successful completion of the intra MME handover the MME shall retransmit the IDENTITY REQUEST message. If a failure of the handover procedure is reported by the lower layer and the S1 signalling connection exists, the MME shall retransmit the IDENTITY REQUEST message.
description: The DETACH REQUEST message is sent by the UE to initiate a detach procedure, which may collide with ongoing identification procedures.
explanation: Categorized as a Message because it initiates communication between network entities.
biotag_Context: 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,O,O,B-Protocol,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,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,B-Protocol,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,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,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,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,O,O,O,O,O,O,O,B-Message,I-Message,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,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-Device,O,O,O,B-Message,O,O,O,O,O,O,B-Message,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,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,B-Message,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,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,I-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,B-Message,I-Message,I-Message,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,O,B-Protocol,B-Connection,O,O,O,O,O,B-Message,I-Message,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Parameter,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,B-Message,I-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O,B-Network Function,O,O,O,B-Message,I-Message,O
biotag_Description: O,B-Message,I-Message,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O