Revision fcf7811b
Added by osmith about 4 years ago
| docs/imsi-pseudo-spec.adoc | ||
|---|---|---|
| 386 | 386 |
When Insert Subscriber Data Result arrives, a subscriber specific |
| 387 | 387 |
Next_Pseudo_IMSI_Timer starts. |
| 388 | 388 |
|
| 389 |
[[next-pseudo-imsi-timer-expires]] |
|
| 389 | 390 |
==== Next_Pseudo_IMSI_Timer Expires |
| 390 | 391 |
|
| 391 | 392 |
If the subscriber has only one pseudonymous IMSI allocated, and the amount of |
| ... | ... | |
| 446 | 447 |
If the SMS with the next pseudonymous IMSI does not arrive, the SIM/USIM will start |
| 447 | 448 |
the next Location Updating Procedure with the old pseudonymous IMSI. Because |
| 448 | 449 |
the HLR/HSS has both the old and the new pseudonymous IMSI allocated at this point, |
| 449 |
the subscriber is not locked out of the network. |
|
| 450 |
the subscriber is not locked out of the network. The HLR/HSS does not deallocate |
|
| 451 |
the new pseudonymous IMSI that did not arrive, but instead send it again |
|
| 452 |
(<<next-pseudo-imsi-timer-expires>>). |
|
| 450 | 453 |
|
| 451 | 454 |
=== Next Pseudonymous IMSI SMS Arrives Out of Order |
| 452 | 455 |
|
Also available in: Unified diff
spec: clarify "Next Pseudonymous IMSI SMS is Lost"
Explicitly state that we send a lost next pseudonymous IMSI again.