Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A Android-IMSI-Catcher-Detector
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 162
    • Issues 162
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • CellularPrivacy
  • Android-IMSI-Catcher-Detector
  • Issues
  • #253
Closed
Open
Issue created Jan 01, 2015 by Administrator@rootContributor

DBe Consistency Check

Created by: E3V3A

This is the DBe Consistency Check detection specifications, as referenced by detection item 1 in the Detection List of #230. This detection is used to filter out bad data and corrupt BTS tower info when importing the external BTS DB from OCID and MLS etc. The table in this part of the database is called DBe_import.

The way it works is that the DBe is imported (from OCID), then all the BTS data in that table is checked for a few criteria, some of which are part of the settings. Depending on the detailed items checked for, DBe_import is updating the new table column called _rej_cause_ with an integer [0,5]. Please refer to issue #215 (closed) for the current DB structure.

IFF (rej_cause>0) we reject the BTS as bad and show it as in RED in the Map Viewer.

Here is the flowchart for this test.

dbe_consistency_check

I see there's a small mistake there. Should be only one Import DBe process...

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Assignee
Assign to
Time tracking