name: GUTI REALLOCATION COMPLETE
full_form: GUTI Reallocation Complete Message
context: Upon receipt of the GUTI REALLOCATION COMMAND message, the UE shall:
  -	store the GUTI;
  -	store the TAI list, if provided;
  -	store the DCN-ID, if provided;
  -	in WB-S1 mode, if the UE supports RACS and the GUTI REALLOCATION COMMAND message includes:
  a)	a UE radio capability ID deletion indication IE set to "Network-assigned UE radio capability IDs deletion requested", delete any network-assigned UE radio capability IDs associated with the registered PLMN stored at the UE, then the UE shall, after the completion of the ongoing GUTI reallocation procedure, initiate a tracking area updating procedure as specified in clauseÂ 5.5.3. If the UE has an applicable manufacturer-assigned UE radio capability ID for the current UE radio configuration, the UE shall include the UE radio capability ID availability IE set to "UE radio capability ID available" in the TRACKING AREA UPDATE REQUEST message; or
  b)	a UE radio capability ID IE, store the UE radio capability ID as specified in annexÂ C; and
  -	send a GUTI REALLOCATION COMPLETE message to the MME.
  The UE considers the new GUTI as valid and the old GUTI as invalid. If the UE receives a new TAI list in the GUTI REALLOCATION COMMAND message, the UE shall consider the new TAI list as valid and the old TAI list as invalid; otherwise, the UE shall consider the old TAI list as valid.
  If the GUTI REALLOCATION COMMAND message contains the DCN-ID IE, then the UE shall store the included DCN-ID value together with the PLMN code of the registered PLMN in a DCN-ID list in a non-volatile memory in the ME as specified in annexÂ C.
description: The GUTI REALLOCATION COMPLETE message is sent by the UE to the MME upon completion of the GUTI reallocation procedure.
explanation: Categorized as a Message because it conveys information between network entities.
biotag_Context: O,O,O,O,B-Message,I-Message,I-Message,O,O,B-Device,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,B-Mode,O,O,O,B-Device,O,B-Network Function,O,O,B-Message,I-Message,I-Message,O,O,O,O,B-Device,O,O,B-Parameter,O,O,B-Message,O,O,O,B-Device,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Device,O,O,B-Parameter,O,O,O,B-Device,O,O,O,B-Device,O,O,O,B-Device,O,O,B-Parameter,O,B-Message,O,O,O,O,O,B-Parameter,O,O,O,B-Message,I-Message,I-Message,I-Message,O,O,O,O,B-Device,O,O,B-Parameter,O,O,O,B-Device,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,B-Message,I-Message,I-Message,O,O,O,O,O,B-Device,O,O,O,B-Parameter,O,O,O,O,O,B-Parameter,O,O,O,O,B-Device,O,O,O,B-Parameter,O,O,O,B-Message,I-Message,I-Message,O,O,B-Device,O,O,O,O,B-Parameter,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,B-Device,O,O,O,O,B-Parameter,O,O,O,O,O,B-Message,I-Message,I-Message,O,O,O,B-Parameter,O,O,O,B-Device,O,O,O,O,B-Parameter,O,O,O,O,B-Network,O,O,O,O,B-Network,O,O,B-Parameter,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O
biotag_Description: O,B-Message,I-Message,I-Message,O,O,O,O,O,B-Device,O,O,B-Network Function,O,O,O,O,B-Parameter,O,O