Provisioning Console for the Database
("GyEIRdbConsole")

• Features
• User interface
• Primary and Slave modes
• Configuration
• Version history

• Loads EIR database and IoT lists into the memory to be accessible by the 2G/3G, 4G and 5G EIR modules and the Telnet Server
• Provides local access to the database of GyEIR and to the IoT lists
• Can export and import to and from text and binary format files, as well
• User can insert or delete ranges into or from any IMEI list in the databases
• Provides an interface to query individual IMEI which IMEI list contains it
• Applied rule can be queried for a given IMSI
• Saves automatically the database on every change (primary mode)
• Loads automatically the database from back ups (slave mode)
• Creates a full back up weekly

Details of the user interface

• GyEIRdb.dll block
  • Status button
    Pressing this button a new window appears and show status info of IMEI lists and IMSI rules.
    
    The status window contains the following information:
    • IMSI prefix count (max / used): Number of maximum and defined IMSI prefixes in GyEIRdb.ini/[IMSIPref Rules]
    • IMEI list entry counts (max / used): Display, how many entries can be and how many entries are actually used by the GyEIR database for each IMEI lists (the maximum number of entries is defined by GyEIRdb.ini/[Advanced]/dwMaxIMEIListEntryCount) .
    • INI file in use: Shows which INI file is used by the GyEIR database.
    • Total allocated memory: Indicates the size of the allocated memory for the main EIR database
    
    
  • IMSI rules for the IMEI' lists
    • Reload all rules: Reloads entries from [IMSIPref Rules] section of GyEIRdb.ini
    • Show all rules: Actually loaded rules will be shown in a new window.
    
    
  • IMEI' lists of the IMSI rules
    • List # (0..9): Here the order of the IMEI list should be typed where the range defined below will be inserted to or deleted from
    • IMEI' start: The first element of the IMEI range
    • IMEI' end: The last element of the range
    • Insert range: Above range will be inserted into the IMEI list defined by the List # (0..9) field
    • Delete range: Given range will be deleted from the IMEI list

    • Show list: Ranges will be shown that are in the given IMEI list
    • Drop list: IMEI range will be dropped from the given IMEI list

    • Save list: The whole IMEI list will be saved into a binary file named GyEIR_IMEIList-N.eir where N refers to the order of the IMEI list. The filename will be completed by the timestamp of the saving (timestamp is in GMT (UTC) format).
      "GyEIR_IMEIList-9 (2009.01.14. 16'01'45).eir" - It contains IMEI ranges which were in the 9th IMEIList at 2009.01.14 16'01:45.
    • Load list: Load ranges into the IMEI list from a binary file. Timestamp should be removed from the filename before loading. The whole list will be reloaded and before loading the actual ranges will be dropped!

    • Export list: Ranges will be saved into a text (csv) file. The filename will be completed by the timestamp of the saving (timestamp is in GMT (UTC) format).
      "GyEIR_IMEIList-9 (2009.01.14. 16'01'45).csv" - It contains IMEI ranges which were in the 9th IMEIList at 2009.01.14 16'01:45.
    • Import list: IMEI ranges will be imported from a text (csv) file. Timestamp should be removed from the filename before loading. More IMEI ranges can be added and deleted, as well, in this way.
  
  
• GyEIRdb2.dll block
  • Status button
    Pressing this button a new window appears and show status info of IoT IMSI and IMEI lists.
    
    The status window contains the following information:
    • IMSI list entry counts (max / used): Number of maximum and actually defined IoT IMSI's in the IoT database (the maximum number of entries is defined by GyEIRdb2.ini/[Advanced]/dwMaxIoTstuffIMSIlistEntryCount entry).
    • IMEI' list entry counts (max / used): Number of maximum and actually defined IoT IMEI's in the IoT database (the maximum number of entries is defined by GyEIRdb2.ini/[Advanced]/dwMaxIoTstuffIMEIlistEntryCount entry).
    • INI file in use: Shows which INI file is used by the IoT database.
    • Total allocated memory: Indicates the size of the allocated memory for the IoT database
    
    
  • IoT IMSI<--->IMEI' lists:
    • IMSI-list / IMEI'-list The radio buttons determine that for which IoT list the following controls are valid
    • IMSI / IMEI': IMSI or IMEI' input field
    • ID string: Defines the ID string value for the IMSI or IMEI' above
    • Insert: Above values will be inserted into the IMSI or IMEI' list
    • Delete: Given values will be removed from the IMSI or IMEI' list

    • Show list: The last 20 IMSI's or IMEI's will be shown
    • Drop list: IMSI or IMEI' list will be dropped

    • Save list: The whole IMSI or IMEI' list will be saved into a binary file named GyEIR_IoTlist-IMSI.eir or GyEIR_IoTlist-IMEI'.eir. The timestamp is appended to the file name (timestamp is in GMT (UTC) format).
      Example: "GyEIR_IoTlist-IMSI (2009.01.14. 16'01'45).eir" - It contains list of IMSI's which were in the IoT IMSI list at 2009.01.14 16'01:45.
    • Load list: Load IMSI's or IMEI's into the corresponding IoT list from a binary file. Timestamp should be removed from the filename before loading! The current list will be dropped before loading a saved list!

    • Export list: Selected IoT list will be saved into a text (csv) file. The timestamp is appended to the file name (timestamp is in GMT (UTC) format).
      "GyEIR_IoTlist-IMSI (2009.01.14. 16'01'45).csv" - It contains list of IMSI's which were in the IoT IMSI list at 2009.01.14 16'01:45.
    • Import list: An IoT list will be imported from a text (csv) file. Timestamp should be removed from the filename before loading.
  
  
• Query block
  • IMSI:
    • applied rule: Shows rules belonging to the given IMSI
    • IoT ID string: Indicates IoT ID string for the given IMSI (when it is defined)
  • IMEI':
    • member of #: Gives back which IMEI list contains the typed IMEI number
    • IoT ID string: Indicates IoT ID string for the given IMEI' (when it is defined)
  • {IMEI',IMSI} answer: Displays the applied rule for the IMEI and IMSI above ('W', 'B', 'G' or 'U')
  
  
• Status
  • In this field the result of the operations will be shown.
  
  
• *PRIMARY GyEIR* or *SLAVE GyEIR*: Primary/Slave indication (For details see the Primary and Slave modes section!)
  
• Exit Shuts down the program.

Primary mode

• Mode can be set by INI/[Advanced]/bModePrimary = True
• All controls on the GUI are active.
• The console backs up the EIR database after every change (AutoSave function). These back ups are tranferred by the "File transfer client" module to the other server where the Console is running in the slave mode.

Slave mode

• Mode can be set by INI/[Advanced]/bModePrimary = False
• Only "Show ranges", "Export ranges" and "Query" controls are active on the GUI.
• Back ups are received from the primary server by the "File transfer server" module and stored in the local back up folder
• The module scans the back up folder for database back ups and when finds a new one then loads the information from it (AutoLoad function) providing that both EIR sites has the same IMEI and IoT database.

Version history

v1.10
• (n) Handles GyEIRDb2.dll for IoT devices