Project

General

Profile

Actions

Feature #2541

closed

have IMEI in HLR DB

Added by neels over 6 years ago. Updated about 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
Start date:
10/06/2017
Due date:
% Done:

100%

Spec Reference:

Description

Especially for communal operators that allow 3rd party SIM cards to camp on the network and that deal with "random"
IMSIs showing up to get signed on to the network, it is important to be able to query the subscriber database for
the IMEI.

The IMEI is often the only identification of an MS that is readily available if we haven't given out a SIM card,
and hence the least ambiguous way to associate a random LU to a real-life person waiting to get authorized.

We should transport the IMEI (IMEISV) via GSUP to the HLR and store it in the HLR database, if the VLR is configured
to retrieve the IMEI / IMEISV from the subscriber.

The database scheme as well as the GSUP protocol need to be expanded for this to work.

Note that this use case also depends on the ability to record LU attempts of unknown subscribers,
i.e. a "subscriber create-on-demand" feature like in the old OsmoNITB.


Related issues

Related to OsmoHLR - Feature #2542: have subscriber create-on-demandStalledosmith10/06/2017

Actions
Related to OsmoMSC - Feature #3189: make retrieval of IMEI configurableResolvedosmith04/19/2018

Actions
Related to OsmoHLR - Feature #3732: Support tacdb query in HLRNew12/13/2018

Actions
Related to Cellular Network Infrastructure - Feature #3733: Send IMEI from MSC to HLRResolvedosmith12/14/2018

Actions
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)