spec: clarify "Next Pseudonymous IMSI SMS is Lost"
Explicitly state that we send a lost next pseudonymous IMSI again.
This commit is contained in:
parent
04ff01ef63
commit
fcf7811bc0
|
@ -386,6 +386,7 @@ with the new pseudonymous IMSI arrives with a delay.
|
|||
When Insert Subscriber Data Result arrives, a subscriber specific
|
||||
Next_Pseudo_IMSI_Timer starts.
|
||||
|
||||
[[next-pseudo-imsi-timer-expires]]
|
||||
==== Next_Pseudo_IMSI_Timer Expires
|
||||
|
||||
If the subscriber has only one pseudonymous IMSI allocated, and the amount of
|
||||
|
@ -446,7 +447,9 @@ Padding at the end, should be filled with 1111 as in the TBCD specification.
|
|||
If the SMS with the next pseudonymous IMSI does not arrive, the SIM/USIM will start
|
||||
the next Location Updating Procedure with the old pseudonymous IMSI. Because
|
||||
the HLR/HSS has both the old and the new pseudonymous IMSI allocated at this point,
|
||||
the subscriber is not locked out of the network.
|
||||
the subscriber is not locked out of the network. The HLR/HSS does not deallocate
|
||||
the new pseudonymous IMSI that did not arrive, but instead send it again
|
||||
(<<next-pseudo-imsi-timer-expires>>).
|
||||
|
||||
=== Next Pseudonymous IMSI SMS Arrives Out of Order
|
||||
|
||||
|
|
Loading…
Reference in New Issue