name: SERVICE REJECT
full_form: Service Reject Message
context: The following abnormal cases can be identified:
  a)	Lower layer failure
  If a lower layer failure occurs before a SERVICE REJECT message has been sent to the UE or the service request procedure has been completed by the network, the network enters/stays in EMM-IDLE.
  b)	Protocol error
  If the SERVICE REQUEST, EXTENDED SERVICE REQUEST or the CONTROL PLANE SERVICE REQUEST message is received with a protocol error, the network shall return a SERVICE REJECT message with one of the following EMM cause values:
  #96:	invalid mandatory information;
  #99:	information element non-existent or not implemented;
  #100:	conditional IE error; or
  #111:	protocol error, unspecified.
  The network stays in the current EMM mode.
  c)	More than one SERVICE REQUEST, EXTENDED SERVICE REQUEST or CONTROL PLANE SERVICE REQUEST received before the procedure has been completed (i.e., before SERVICE REJECT message has been sent or service request procedure has been completed)
  -	If one or more of the information elements in the SERVICE REQUEST message, CONTROL PLANE SERVICE REQUEST or EXTENDED SERVICE REQUEST for packet services differs from the ones received within the previous SERVICE REQUEST, CONTROL PLANE SERVICE REQUEST or EXTENDED SERVICE REQUEST message for packet services, the previously initiated service request procedure shall be aborted and the new service request procedure shall be progressed;
  NOTE:	The network actions are implementation dependent for the case that more than one EXTENDED SERVICE REQUEST messages for CS fallback or 1xCS fallback are received and their information elements differ.
  -	If the information elements do not differ, then the network shall continue with the previous service request procedure and shall not treat any further this SERVICE REQUEST, EXTENDED SERVICE REQUEST or CONTROL PLANE SERVICE REQUEST message.
  d)	ATTACH REQUEST received before a SERVICE REJECT message has been sent or the service request procedure has been completed
  If an ATTACH REQUEST message is received and the service request procedure has not been completed or a SERVICE REJECT message has not been sent, the network may initiate the EMM common procedures, e.g. the EMM authentication procedure. The network may e.g. after a successful EMM authentication procedure execution, abort the service request procedure, delete the EMM context, EPS bearer contexts, if any, and progress the new ATTACH REQUEST.
  e)	TRACKING AREA UPDATE REQUEST message received before the service request procedure has been completed or a SERVICE REJECT message has been sent
  If a TRACKING AREA UPDATE REQUEST message is received and the service request procedure has not been completed or a SERVICE REJECT message has not been sent, the network may initiate the EMM common procedures, e.g. the EMM authentication procedure. The network may e.g. after a successful EMM authentication procedure execution, abort the service request procedure and progress the tracking area updating procedure.
  f)	Default or dedicated bearer set up failure
  If the lower layers indicate a failure to set up a radio or S1 bearer, the MME shall locally deactivate the EPS bearer as described in clauseÂ 6.4.4.6.
description: A message sent by the network to the UE in response to a service request, indicating that the service cannot be provided.
explanation: Categorized as a Message because it is used for communication between the network and the UE.
biotag_Context: 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-Device,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-Message,I-Message,I-Message,I-Message,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,I-Message,O,O,O,O,O,O,B-Protocol,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,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Message,I-Message,I-Message,O,B-Message,I-Message,I-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,B-Message,I-Message,O,B-Message,I-Message,I-Message,I-Message,O,B-Message,I-Message,I-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,I-Message,I-Message,I-Message,O,B-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,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,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,I-Message,I-Message,O,B-Message,I-Message,I-Message,I-Message,O,O,B-Message,I-Message,O,O,O,B-Message,I-Message,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-Message,I-Message,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,B-Network,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,B-Message,I-Message,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,B-Message,I-Message,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,B-Protocol,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,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,B-Network Function,O,O,O,O,B-Network,O,O,O,O,O,O
biotag_Description: O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O