Actions
Feature #1976
closedVLR / 3G: periodic LU expiry by T3212
Start date:
03/09/2017
Due date:
% Done:
0%
Resolution:
Spec Reference:
Description
pre-VLR code had T3212 subscriber expiry if it missed a periodic LU.
libvlr has stubs ready, but it is not yet enforced nor fully implemented.
Add T3212 expiry with an msc_vlr_test_periodic_lu unit test (using fake time).
Related issues
Updated by neels about 7 years ago
- Related to Support #1922: comprehensive test of MSC subscriber connection and request handling added
Updated by neels about 6 years ago
Some pointers and related things to balance out in a nice (TM) implementation:
- We so far don't, but we should have a mechanism to cache unused auth tuples for a subscriber even past IMSI Detach.
(An idea to optimise lookups and iterate less subscribers for <insert action here> would be to keep inactive subscribers for which we merely cache auth tuples in a separate llist.)
- TS 23.012 2.4.2 "Implicit IMSI detach" describes periodic location updating timer
- TS 23.012 3.7.3 Extended periodic LAU Signalling (the possibility to send extended timers during Location Updating Accept)
- TS 23.012 4.3.2.1 "Process Detach_IMSI_VLR"
- Are we required to notify the HLR of an IMSI Detach? (not sure, so far we don't)
Updated by neels about 6 years ago
might be interesting as well:
- 23.018 8.3 Messages on the D interface (VLR-HLR)
- 24.008 4.3.4 IMSI detach procedure
Updated by stsp almost 6 years ago
Initial implementation proposal at https://gerrit.osmocom.org/#/c/osmo-msc/+/9211
Updated by stsp almost 6 years ago
Can we close this ticket now? Some of neels' points remain unaddressed, but wouldn't it be more appropriate to file separate issues for these?
Actions
