5gsd / aicdm Goto Github PK

Why does this require root, the previous version did not need this?

This is the app Data Flow Diagram, showing how data flows from data collectors to the database and then on to the various components, for analysis, tests and display.

This thread is for developer commitments (only)!

If you are available to help contributing to the NG AICD development, please add a short comment below and what parts of the app you think you could or would like to contribute to.

Here is a short (incomplete) list of app areas to which we need contributors.

Alpha Milestone

Functionality:

• fix app permissions requests

• fix and separate SignalStrengths and PhoneState listener functions

• app background Services (main controller, RfApi, GPS)

  • To ensure the correct life-cycle of services started and stopped with the controller/settings activity.

• Create data bundle handler for the collector services (to push data from listeners to DB handler)

• Create the main analyzer loop thread, that iterate through all Detection Tests

• Create DTn test template

  • consists of SQL query
  • score calculator
  • instant attack detection (flag or BROADCAST?)
  • time-stamp and dt (delta-t) for the time it takes to process the detection

• Create run test/submit function to be used in analyzer loop:

  • RunDT(Int n);
  • Returns: (String error, Int score, Boolean isAttack, Real TS, Real dt)
  • IF (error=="ok"){...} else {Log.e(TAG, ":DT%n: FAILED with Error: " + error, n);}

SQL:

NOTE: This will be based on raw (Sqlite3) SQL queries only.
No external libraries or pre-fabricated Java plug-ins.

• Create a DB handler (insert), receiving the collector bundles and populate the DB tables with it. (one way)
• Create a DB handler (select), that performs the queries and gets the result score from it. (two way)

UI:

• app controller/settings activity (cleanup of: saving settings, buttons, text)

• app detailed info activity (from AIMSICD) showing:

• add DB viewer (from AIMSICD) for:

  • 1. EventLog
  • 2. SmsData, BtsLoc, DBi_phy
  • 3. and some additional VIEWS: TBA

Beta Milestone

MAP:

• add map activity from AIMSICD to be accessible from Setting Activity:

  • add map only, no points

  • add map points from DBi_ext (import) from local camera (bounding box), no logic, just points

  • add BTS point color-codes using DBe_ext

  • add long press on map, to add that location to the BtsLoc DB table.

  • add long press pop-up to select:

    • Delete: to delete the point
    • Move: to move the point to new location
    • Sector Count: 0,1,2,3,4: to give a visible estimate of the number of sectors

This is the current Database design structure (ER diagram).

UPDATES:

1. DBe_import will be renamed to DBe_ext for externally imported or created data.
2. The EvenLog fields: LAC, CID, PSC, gpsd_* will be replaced by Dbi_vol.id.
3. The SmsData fields: rat, lac, cid, gpsd_* will be replaced by Dbi_vol.id.
4. The defaultlocation table, will be renamed DefLoc.

Here we propose show an idea of how we see the files and directories are organized and connected.

Eventually, there will also be a one-line description of each.
If you have suggestions for new items or a different structure, please post them below.

NOTE:

1. This post will be regularly updated and eventually added to our Wiki.
2. This is WIP, and may not yet reflect whats found in the repo.

/collectors/
	RfApi.java
	GPS.java
/defend/
/detect/
	DT1.java	-- 
	DT2.java	--
	...
	DTn.java	-- Empty Template
/map/
	AddBts
/services/
	./main/Analyzer.java
	./sms/
	./sim/
	./ss7/
/ui/
	./activities/
	./drawer/
	./fragments/
	./widget/
/utils/
	./anneal/
	Logger

Main
Settings

This thread is for proposing new FAQ's.

Please focus on specific questions pertaining to development.
(Avoid general general about what it does and what's LTE etc.)

As this issue progress, they will be added to our Wiki.

Q: What detection methods do you plan to use?

A: The detection methods will essentially be the same as previous project,
but with the greatest difference that they will actually work and be much
easier to implement and understand. The reason for this is that each
detection test (DT-n) will be made as a separate "module" and thus
free-standing. That way it is very easy to implement and test and will
not affect other modules. In addition, it allows us to work in parallel
on several tests and can implement pretty much any method we want. We
are open also for new ideas, not already covered. To be able to make
this happen we have changed the DB structure. Here you can find:

Detection Tests
DB Structure

Q: How are the detections performed?

A: The collector services continuously populate the DB with network measurements.
These measurements are then queried directly by SQL statements inside each test
module, called DT-1, DT-2 to DT-n. Where n is the number of each test.
The results of each query is then used in the analyzer loop and given a detection
score. When the sum of all scores reach a threshold a detection flag raised. That
is, one of the colored antenna symbols are shown as an alert.

Q: How can I help implement a new detection?

A: You first check that the detection doesn't already exist in our
Detection Table list.
If it does exists, you check it's status and related issues and join
the discussion from there, if you have something important to add.
If it does not exists, you first create a new issue
labeled Detection: <what it does>. Here you try to describe in as much
detail you can, how the test works and how it helps detect fake base
stations. You can be as technical as you like, but try to be pedagogic
to allow other programmer understand how it work. Then, unless the test
is of trivial nature (which is very unlikely) we want you to accompany
the issue OP with a picture of a flow-chart describing the test you
propose. Once, we are all confident it will work..

You clone the repo, and under the /detect/ directory, you copy the file
called DT-n_template.java to DT-n.java. Then you go to the analyzer and
add your new test to the test loop, labeled ADD NEW Detection Tests HERE.
Of course you need to check and make sure the n you choose doesn't already
exist in our Detection Table. Once you feel this is working, you make
sure you have thoroughly documented the detection, and preferably accompanied
it with a flow chart picture. Once you got this, you make a PR with your new
code and wait for our wetting and test team to accept or reject the new test.