Project

General

Profile

Actions

Feature #1974

open

VLR: high water mark on subscriber storage

Added by neels over 4 years ago. Updated over 2 years ago.

Status:
New
Priority:
Low
Assignee:
Osmocom CNI Developers
Category:
-
Target version:
-
Start date:
03/08/2017
Due date:
% Done:

0%

Resolution:
Spec Reference:

Description

In libvlr, we (will) keep every subscriber in RAM as long as it still has valid auth tuples (3GPP TS 33.102 Annex C.2.3).
Most subscribers will still have auth tuples left upon detaching, so we would store all subscribers.

Implement a configurable way of limiting the number of subscribers kept in RAM, e.g. a fixed max size.
If this is reached, discard those subscribers that have been inactive for the longest time first.


Related issues

Related to OsmoMSC - Feature #1973: VLR: efficient subscriber lookupNewOsmocom CNI Developers03/08/2017

Actions
Actions #1

Updated by neels over 4 years ago

  • Related to Feature #1973: VLR: efficient subscriber lookup added
Actions #2

Updated by neels over 4 years ago

Before the VLR, there were VTY commands to mark a subscriber to be kept in ram, i.e. to not drop it from in-ram structures because we no longer use it, in order to allow continuously querying it from the vty. When we implement subscriber removal, we may also need such mechanisms again.

Actions #3

Updated by laforge almost 4 years ago

  • Project changed from OpenBSC to OsmoMSC
Actions #4

Updated by laforge over 2 years ago

  • Priority changed from Normal to Low
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)