Feature #3733
closedSend IMEI from MSC to HLR
100%
Description
We want to store the IMEI in HLR (see OS#2541). But first, we need to send it from the MSC to the HLR.
laforge wrote:
Some context:
- Normally, a HLR doesn't store IMEI information, rather the EIR (Equipment Identity Register) does
- The VLR in the MSC will explicitly issue a CHECK_IMEI procedure, which will send a MAP request
to the EIR and ask if this IMEI is permitted or not- The EIR will respond to the VLR
The purpose of this procedure as per 3GPP specs is to have a blacklist/whitelist of IMEIS that
is pre-populated using out-of-band sources. It is not to dynamically store information about IMEIS.While we use GSUP and not MAP, we still want to have the same abstract trasactions, procedures
and message flows. This means, we have to implement whatever the MAP CHECK IMEI procedure normally
does, but then OsmoHLR can, optionally, if enabled by VTY, store the received IMEI information in
some table. So rather than a policy check, it would be used for dynamically storing the IMEI/IMSI
mappings as they appear over time.
So far, the VLR/MSC is able to query the IMEI from the MS.
This issue is about implementing and using the CHECK_IMEI related messages in GSUP, based on the MAP spec 29.002 (see 25.6 IMEI Handling Macros).
The EIR (Equipment Identity Register) part that would usually report if a device is stolen or not, will be implemened in osmo-hlr and always accept all incoming IMEIs.
Checklist
- libosmocore changes merge to master
- hlr changes merge to master
- submit msc changes to gerrit
- msc changes merged to master
- update wireshark GSUP protocol
- update GSUP documentation
Related issues