School of Specs 24.501v20.0.0

3GPP 24.501 v20.0.0 — the document's own text

5.4.3.5 Abnormal cases in the UE

Taught in 4. Inside TS 24.501, the document at the centre (CT1 — the group that writes what your phone says, overview).

The following abnormal cases can be identified:

  • Transmission failure of the IDENTITY RESPONSE message (if the identification procedure is triggered by a registration procedure).

The UE shall re-initiate the registration procedure.

  • Requested identity is not available

If the UE cannot encode the requested identity in the IDENTITY RESPONSE message, e.g. because no valid USIM is available, then it shall encode the identity type as "No identity".

NOTE: If the Identity type IE in the IDENTITY REQUEST message is set to "SUCI" and a valid USIM is available, and if the UE cannot encode the requested identity in the IDENTITY RESPONSE message, e.g. because the information required for the SUCI calculation is not correctly configured in the USIM (see 3GPP TS 31.102 [22]), then the UE behavior is implementation specific.