https://projects.osmocom.org/https://projects.osmocom.org/favicon.ico?16647414092017-10-06T02:52:54ZOpen Source Mobile CommunicationsOsmoHLR - Feature #2541: have IMEI in HLR DBhttps://projects.osmocom.org/issues/2541?journal_id=55652017-10-06T02:52:54Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-7 priority-1 priority-lowest" href="/issues/2542">Feature #2542</a>: have subscriber create-on-demand</i> added</li></ul> OsmoHLR - Feature #2541: have IMEI in HLR DBhttps://projects.osmocom.org/issues/2541?journal_id=89692018-04-19T19:41:30Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-3 priority-1 priority-lowest closed" href="/issues/3189">Feature #3189</a>: make retrieval of IMEI configurable</i> added</li></ul> OsmoHLR - Feature #2541: have IMEI in HLR DBhttps://projects.osmocom.org/issues/2541?journal_id=118632018-10-02T15:39:48Zlaforge
<ul><li><strong>Assignee</strong> set to <i>4368</i></li></ul> OsmoHLR - Feature #2541: have IMEI in HLR DBhttps://projects.osmocom.org/issues/2541?journal_id=119372018-10-03T10:28:33Zlaforge
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Urgent</i></li></ul> OsmoHLR - Feature #2541: have IMEI in HLR DBhttps://projects.osmocom.org/issues/2541?journal_id=119422018-10-03T10:29:21Zlaforge
<ul><li><strong>Priority</strong> changed from <i>Urgent</i> to <i>Normal</i></li></ul> OsmoHLR - Feature #2541: have IMEI in HLR DBhttps://projects.osmocom.org/issues/2541?journal_id=119972018-10-04T12:00:57Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>I guess I could resolve this one pretty quickly; but this would also qualify for newcomers to familarize with the layers.<br />needs:</p>
<ul>
<li>MSC+VLR vty config for <a class="issue tracker-2 status-3 priority-1 priority-lowest closed" title="Feature: make retrieval of IMEI configurable (Resolved)" href="https://projects.osmocom.org/issues/3189">#3189</a> -- all ID Request code already exists, just needs a flag flipped by VTY.</li>
<li>extend GSUP to add IMEISV</li>
<li>adjust HLR to store IMEISV -- db column already exists.</li>
</ul> OsmoHLR - Feature #2541: have IMEI in HLR DBhttps://projects.osmocom.org/issues/2541?journal_id=120002018-10-04T12:20:34Zlaforge
<ul></ul><p>Please keep in mind we do want to keep things in line with the 3GPP<br />procedures on the MSC/VLR<->HLR/EIR interface!</p>
<p>Simply adding the IMEI to an UpdateLocation request is not going to cu<br />it. Rather, the VLR needs to invoke the CheckIMEI procedure towards the<br />EIR, and OsmoHLR then has to implement the EIR functionality in this<br />context.</p>
<p>So on the protocol level the transactions look like 3GPP. Whether or<br />not the HLR then dynamically creates a "EIR entry" and acknowledges all<br />CheckIMEI is an implementation detail that doesn't affect the<br />transactions/procedures "on the wire".</p> OsmoHLR - Feature #2541: have IMEI in HLR DBhttps://projects.osmocom.org/issues/2541?journal_id=125712018-11-13T10:57:16Zosmith
<ul><li><strong>Assignee</strong> changed from <i>4368</i> to <i>osmith</i></li></ul> OsmoHLR - Feature #2541: have IMEI in HLR DBhttps://projects.osmocom.org/issues/2541?journal_id=125752018-11-13T15:20:09Zlaforge
<ul></ul><p>Some context:</p>
<ul>
<li>Normally, a HLR doesn't store IMEI information, rather the EIR (Equipment Identity Register) does</li>
<li>The VLR in the MSC will explicitly issue a CHECK_IMEI procedure, which will send a MAP request<br />to the EIR and ask if this IMEI is permitted or not</li>
<li>The EIR will respond to the VLR</li>
</ul>
<p>The purpose of this procedure as per 3GPP specs is to have a blacklist/whitelist of IMEIS that<br />is pre-populated using out-of-band sources. It is <strong>not</strong> to dynamically store information about IMEIS.</p>
<p>While we use GSUP and not MAP, we still want to have the same abstract trasactions, procedures<br />and message flows. This means, we have to implement whatever the MAP CHECK IMEI procedure normally<br />does, but then OsmoHLR can, optionally, if enabled by VTY, store the received IMEI information in<br />some table. So rather than a policy check, it would be used for dynamically storing the IMEI/IMSI<br />mappings as they appear over time.</p>
<p>Please note that the CHECK IMEI procedure in the VLR is an optional procedure, so it must be<br />enabled in the VLR. I'm not sure if all required code exists and we simply commented it out,<br />or if it's already enable-able by VTY, ...</p> OsmoHLR - Feature #2541: have IMEI in HLR DBhttps://projects.osmocom.org/issues/2541?journal_id=129402018-12-13T11:05:26Zosmith
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul> OsmoHLR - Feature #2541: have IMEI in HLR DBhttps://projects.osmocom.org/issues/2541?journal_id=129432018-12-13T12:45:56Zosmith
<ul></ul><blockquote>
<p>Please note that the CHECK IMEI procedure in the VLR is an optional procedure, so it must be<br />enabled in the VLR. I'm not sure if all required code exists and we simply commented it out,<br />or if it's already enable-able by VTY, ...</p>
</blockquote>
<p>Reading <a class="issue tracker-2 status-3 priority-1 priority-lowest closed" title="Feature: make retrieval of IMEI configurable (Resolved)" href="https://projects.osmocom.org/issues/3189">#3189</a>, it seems that CHECK_IMEI is already implemented in the VLR (in osmo-msc), but can not be set in the VTY config yet. So I'm looking at this first.</p> OsmoHLR - Feature #2541: have IMEI in HLR DBhttps://projects.osmocom.org/issues/2541?journal_id=129442018-12-13T15:23:48Zmsuraev
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-1 priority-1 priority-lowest" href="/issues/3732">Feature #3732</a>: Support tacdb query in HLR</i> added</li></ul> OsmoHLR - Feature #2541: have IMEI in HLR DBhttps://projects.osmocom.org/issues/2541?journal_id=129512018-12-14T14:17:25Zosmith
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-3 priority-2 priority-default closed" href="/issues/3733">Feature #3733</a>: Send IMEI from MSC to HLR</i> added</li></ul> OsmoHLR - Feature #2541: have IMEI in HLR DBhttps://projects.osmocom.org/issues/2541?journal_id=130432019-01-09T14:29:08Zosmith
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>30</i></li></ul><p>In HLR, we have a column for IMEISV. However, since we decided to use the Check IMEI mechanism, we only send the IMEI from the MSC/VLR to the HLR/EIR. Not the IMEISV.</p>
<p>For testing purposes I'm just saving the IMEI in the IMEISV column right now, but that will probably lead to confusion in the future. I'm wondering what the best way to continue is here. I came up with these options:</p>
<p>a) Keep using the IMEISV column with the IMEI<br />b) Update the DB format and add a new IMEI column<br />c) Update the DB format, add a new IMEI column and delete the IMEISV column</p>
<p><a class="user active" href="https://projects.osmocom.org/users/7">laforge</a>, <a class="user active" href="https://projects.osmocom.org/users/91">neels</a>: recommendations?</p> OsmoHLR - Feature #2541: have IMEI in HLR DBhttps://projects.osmocom.org/issues/2541?journal_id=130452019-01-10T10:30:37Zlaforge
<ul></ul><p>Hi Oliver,</p>
<p>On Wed, Jan 09, 2019 at 02:29:09PM +0000, osmith [REDMINE] wrote:</p>
<blockquote>
<p>a) Keep using the IMEISV column with the IMEI<br />b) Update the DB format and add a new IMEI column<br />c) Update the DB format, add a new IMEI column and delete the IMEISV column</p>
<p><a class="user active" href="https://projects.osmocom.org/users/7">laforge</a>, <a class="user active" href="https://projects.osmocom.org/users/91">neels</a>: recommendations?</p>
</blockquote>
<p>I'm all for option 'b'.</p> OsmoHLR - Feature #2541: have IMEI in HLR DBhttps://projects.osmocom.org/issues/2541?journal_id=130542019-01-11T15:37:11Zosmith
<ul><li><strong>% Done</strong> changed from <i>30</i> to <i>80</i></li></ul><blockquote>
<p>I'm all for option 'b'.</p>
</blockquote>
<p>Implemented, patches submitted:<br /><a class="external" href="https://gerrit.osmocom.org/#/q/topic:send-imei-to-hlr+(status:open+OR+status:merged)">https://gerrit.osmocom.org/#/q/topic:send-imei-to-hlr+(status:open+OR+status:merged)</a></p>
<p>(CI failures are due to a dependency in libosmocore.)</p> OsmoHLR - Feature #2541: have IMEI in HLR DBhttps://projects.osmocom.org/issues/2541?journal_id=131272019-01-24T15:39:56Zosmith
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>80</i> to <i>100</i></li></ul>