Ø The identification procedure is used by the network to request a particular UE to provide specific identification parameters, e.g. IMSI, IMEI etc…
Ø The network initiates the identification procedure by sending an IDENTITY REQUEST message to the UE. The type of the identity is requested in the IE Identity Type 2
Ø The MME can send an IDENTITY REQUEST message to an UE at any time while the UE is in EMM-CONNECTED mode and the UE shall be ready to respond to an IDENTITY REQUEST message at any time whilst in EMM-CONNECTED mode
Ø After receiving the IDENTITY REQUEST message the UE shall respond with an IDENTITY RESPONSE message to the network. The IDENTITY RESPONSE message shall contain the identification parameters as requested by the network
Ø If the network doesn’t receive IDENTITY RESPONSE message before the expiry of T3470, it shall retransmit the IDENTITY REQUEST message and reset/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
Reference: 3GPP TS 24.301
Example1: IDENTITY REQUEST – Identity Type: IMSI
 |
Example2: IDENTITY REQUEST – Identity Type: IMEI
|
Dear Swamy,
ReplyDeleteMay i know, what is the triggering reasons for MME to request the "Identity request"...
When MME looks up the Last UE Context and fails to find any (e.g.
Deletedue to failed integrity validation or no Old GUTI) then it sends an Identity Request to the UE.
The must communicate the IMEI or the IMSI ? Or must the both ?
ReplyDeleteThe UE must communicate the IMEI or the IMSI, One of them is enough for a successful authentication ? Or the need the IMEI + IMSI (Together) ?
ReplyDelete