Baseband behavior on IMSI change » History » Version 9
osmith, 04/01/2020 07:39 AM
| 1 | 1 | neels | h1. Baseband behavior on IMSI change |
|---|---|---|---|
| 2 | |||
| 3 | 4 | neels | h1. With "Proactive SIM" REFRESH command |
| 4 | |||
| 5 | 5 | neels | According to ETSI TS 101 267 / 3GPP TS 11.14 section 6.4.7.1 "EF IMSI changing procedure", after changing EF-IMSI, |
| 6 | valid REFRESH qualifiers are |
||
| 7 | 1 | neels | |
| 8 | 5 | neels | * "SIM Initialization and File Change Notification" |
| 9 | * "SIM Initialization and Full File Change Notification" |
||
| 10 | * "SIM Reset" |
||
| 11 | 1 | neels | |
| 12 | 8 | neels | h2. 1 "SIM Initialization and Full File Change Notification" |
| 13 | 1 | neels | |
| 14 | 8 | neels | h3. 1.1 ATT == 1 (Channel Description: Attach = yes) |
| 15 | |||
| 16 | 6 | neels | * Samsung Galaxy phone displays "Refreshing SIM" (notification bubble on display, probably annoying to the user) |
| 17 | 5 | neels | * immediate IMSI Detach |
| 18 | 6 | neels | * some seconds delay of being detached: Samsung Galaxy S4m = 15s; NOKIA 1100 = 8s |
| 19 | 5 | neels | * Location Updating (IMSI Attach) with previous TMSI (!) |
| 20 | * MSC has forgotten the TMSI due to IMSI detach (OsmoMSC peculiarity, usually an MSC should still have the TMSI) |
||
| 21 | 1 | neels | * Identity Request & Response yields new IMSI |
| 22 | |||
| 23 | 8 | neels | h3. 1.2 ATT == 0 (Channel Description: Attach = no) |
| 24 | 1 | neels | |
| 25 | 8 | neels | h4. 1.2.1 ATT == 0, Nokia 1100 |
| 26 | 1 | neels | |
| 27 | 7 | neels | * omits IMSI Detach |
| 28 | * Nokia 1100 sends Location Updating (Periodic) immediately = changes identity at MSC immediately |
||
| 29 | |||
| 30 | 8 | neels | h4. 1.2.2 ATT == 0, Samsung Galaxy S4m |
| 31 | 7 | neels | |
| 32 | 1 | neels | * omits IMSI Detach |
| 33 | * does not send Location Updating = stays on previous TMSI = keeps old identity |
||
| 34 | * even after periodic LU period expired, still uses previous TMSI = still keeps old identity |
||
| 35 | (due to omitted IMSI Detach, OsmoMSC still knows the TMSI; if we implement that OsmoMSC forgets the TMSI, the periodic LU should ask for the IMSI and change identity) |
||
| 36 | 8 | neels | |
| 37 | h2. 2 "SIM Reset" |
||
| 38 | |||
| 39 | TODO |
||
| 40 | |||
| 41 | h2. 3 "SIM Initialization and File Change Notification" |
||
| 42 | |||
| 43 | TODO |
||
| 44 | |||
| 45 | 1 | neels | h1. Phones Keep the TMSI |
| 46 | |||
| 47 | Even though the IMSI has changed, the Baseband uses the last TMSI, and hence looks as if it remained completely unchanged, keeps using the previous identity. |
||
| 48 | After a power cycle, it also uses the last TMSI. |
||
| 49 | 5 | neels | |
| 50 | 2 | neels | When the MSC has forgotten the last TMSI (e.g. due to IMSI Detach), the Identity Request is answered with the new IMSI, and the phone has thus switched to the new identity. |
| 51 | 1 | neels | |
| 52 | * Needs to make sure the MSC forgets the TMSI. |
||
| 53 | 9 | osmith | * -Investigate whether we can make the SIM forget the TMSI.- implemented |
| 54 | 6 | neels | |
| 55 | h1. Without "Proactive SIM" REFRESH command |
||
| 56 | |||
| 57 | Just for your info, we should not omit the REFRESH. |
||
| 58 | |||
| 59 | | phone | directly when writing new IMSI to SIM file | on CM Service Request | after periodical LU period | after flight mode / phone restart | on Identity Request | |
||
| 60 | | Nokia | no reaction | uses previous TMSI | uses previous TMSI | uses previous TMSI | returns new IMSI | |
||
| 61 | | Samsung Galaxy S4m | no reaction | uses previous TMSI | uses previous TMSI | uses previous TMSI | returns new IMSI | |
