Revision e9b57f5d
Added by osmith about 4 years ago
| docs/imsi-pseudo-spec.adoc | ||
|---|---|---|
| 356 | 356 |
==== Update Location Request |
| 357 | 357 |
|
| 358 | 358 |
When Update Location Request arrives, the HLR/HSS does not look up the subscriber |
| 359 |
by the IMSI, but by the pseudonymous IMSI instead. Unless the subscriber has
|
|
| 360 |
two pseudonymous IMSI allocated and used the new pseudonymous IMSI in the
|
|
| 361 |
Update Location Request, this is followed by the existing logic to continue
|
|
| 362 |
with Insert Subscriber Data Request.
|
|
| 359 |
by the IMSI, but by the pseudonymous IMSI instead. If the subscriber has two
|
|
| 360 |
pseudonymous IMSI allocated and used the new pseudonymous IMSI in the Update
|
|
| 361 |
Location Request, <<ul-new-pseudo-imsi>> applies. Otherwise, the HLR continues
|
|
| 362 |
with the existing Insert Subscriber Data Request logic.
|
|
| 363 | 363 |
|
| 364 |
[[ul-new-pseudo-imsi]] |
|
| 364 | 365 |
===== Update Location Request With New Pseudonymous IMSI |
| 365 | 366 |
|
| 366 | 367 |
If the subscriber has two pseudonymous IMSIs allocated, and the newer entry was |
Also available in: Unified diff
spec: UL Request: clarify sentence