GyEIR

The ‘Equipment Identity Register’ function,
implemented by
TSP-Lab and Aitia International Inc.

Table of contents

• How does GyEIR work?

• Software components

The "GyEIRdb.dll" contains:

• an IMSI-prefix list (maximum 100 elements) in which every single entry contains one or more rules;
• maximum 10 IMEI ranges.

The "GyEIRdb2.dll" contains:

• List of IMSI's with a 20-character long identifier;
• List of IMEI's with a 20-character long identifier.
• Note: Alphanumeric and underscore characters are allowed to be used in identifiers

EIR logic

Step 1 (checking IoT database)

• EIR checks whether the IMSI of incoming CheckIMEI reuqest is in the IoT IMSI list
  • If NO then goes to "Step 2"
  • If YES then
    • Checks the IMEI whether it is in the IoT IMEI' list and compare the ID strings.
      • When they are the same then goes to "Step 2"
      • When they are not the same then the answer will be "BlackListed"

Step 2 (checking IMEI lists)

• EIR selects which rule should be applied based on the IMSI from the incoming CheckIMEI (the first fitting IMSI prefix or the default ("*") )
• Checks the corresponding IMEI list(s) to select the status belonging to the IMEI and answers it as the status ("WhiteListed"/"BlackListed"/"GreyListed"/"UnknownEquipment")
• When the IMEI is not found then the default status of the rule will be answered