You are here



The mobile probe stores data in a mongoDB database in json format.

For this purpose a mongoDB to mPlane reference implemenation proxy has been created.
The proxy is not specific to the mobile proxy and, therefore, it can be configureed to extract data from any mongoDB schema. 

Repository Description:

The repository consists of a MongoDB database and a node.js interface. The Mobile Probe sends HTTP requests from the device to the server with the aggregated measurements. The node.js script is in turn responsible for receiving, parsing and storing the incoming data to the database. Each measurement is inserted with fields such as timestamp, the device's unique ID and IP address. In this way, the repository can handle concurrent reports from multiple devices. As can be seen in the provided sample below, a report contains the required performance metrics from the different layers that the probe is monitoring.

        "timestamp":"2015-03-31 13:19:57.608",

        "timestamp":"2015-03-31 13:19:58.050",
        "timestamp":"2015-03-31 13:19:58.851",
          "Cpu Tot: ":1,
        "timestamp":"2015-03-31 14:54:55.716",
        "LogCat":"I/AwesomePlayer( 1854): setDataSource_l(URL suppressed)",
        "timestamp":"2015-03-31 14:54:56.546",
        "LogCat":"I/AwesomePlayer( 1854): Could not offload audio decode, try pcm offload",
        "timestamp":"2015-03-31 22:09:40.809",


mPlane proxy interface

The proxy can be found here: is external)

The proxy Interface is written in python and it sits on top of MongoDB. It exports the collections of mongoDB as capabilities using the Reference Implementation. Afterwards, the mPlane clients can pull the requested data. 

The mongoDB proxy can be used by any component that has data stored in a mongoDB database. For details on how to install and run the probe visit the github help file: is external)



Copy files from the mPlane interface (from the components GitHub) into protocol-ri/: - mobile_probe_settings.json The registry.json file, copy it into protocol-ri/mplane/components/. - The Python interface, copy it into protocol-ri/mplane/components/. - supervisor.conf , component.conf and client.conf The configuration files, copy them into protocol-ri/conf/.


The mongoDB proxy can be used by any component that has data stored in a mongoDB database. The configuration is given at a json file of the following format.

            "cpuload":"HW.Cpu Tot: ",

The settings above will pull data from db mplane and collection mobileMeasurements. The field "devicID" will be used as the source field when making a query for a specific device. Furthermore, the timestamp field is "date"

The measurements dictionary contains information about the offered capabilities and the association of the return values between the mongoDB database and the mPlane reference implemenation. For instance, the mongoDB entryHW.wifi_RSSI will be returned as the mPlane's RI snr field.

The settings above will generate three capabilities.

query (mobile_probe_hardware) 
query (mobile_probe_videoLog) 
query (mobile_probe_cellInfo)

Launching the data extractor

After installing the RI, in a terminal window start supervisor:

cd ~/protocol-ri
python3 -m scripts/mpsup --config ./conf/supervisor.conf


cd ~/protocol-ri 
python3 -m mplane.supervisor --config ./conf/supervisor.conf

In another terminal start the mobile probe as a component:

cd ~/protocol-ri 
python3 -m scripts/mpcom --config ./conf/component.conf 

The expected output for this example should be:

Capability registration outcome:
mobile_probe_hardware: Ok
mobile_probe_videoLog: Ok
mobile_probe_cellInfo: Ok

Checking for Specifications...



Retreiving data

You need to have mongoDB setup and running on your machine. You should also have the settings.json configured in order to access and translate the mongoDB field into the mPlanes RI entries (see above).

Start a client to test the component:

mpcli --config ./conf/client.conf

The expected output should be:

mPlane client shell (rev 20.1.2015, sdk branch)
Type help or ? to list commands. ^D to exit.

Now check that the mongoDB capabilities is registered:

|mplane| listcap
Capability mobile_probe_cellInfo (token cd6b5fa2dc4ddfd3d7c4f16898bf1b60)
Capability mobile_probe_hardware (token f3a12891623783d20d4f63f01e86104d)
Capability mobile_probe_videoLog (token 57a0a9484788520090bf3e1c97aa6df8)

And run a test capability. In this example we ask for any mongoDB hardware entries for mobile
device with IMEI 352605059221028 between 2013-09-20 and 2015-5-5:

|mplane| runcap mobile_probe_hardware
|when| = 2013-09-20 ... 2015-5-5
source.device = 352605059221028

If everything works ok the data should be pulled from the mongoDB database and transformed into an mPlane result:

|mplane| listmeas
Result  mobile_probe_hardware-0 (token 6ed23ada2c8921f7cf9de917402a4283): 
2015-03-31 11:19:58.851000 ... 2015-03-31 11:20:04.377000

You can now access the measurments:

|mplane| showmeas 6ed23ada2c8921f7cf9de917402a4283
result: query
    label       : mobile_probe_hardware-0
    token       : 6ed23ada2c8921f7cf9de917402a4283
    when        : 2015-03-31 11:19:58.851000 ... 2015-03-31 11:20:04.377000
    registry    :
    parameters  ( 1): 
                           source.device: 352605059221028
    metadata    ( 1): 
                          System_version: 1.0
    resultvalues( 2):
          result 0:
                                     cpuload: 1.0
                                     memload: 20908.0
                                         snr: -37.0
          result 1:
                                     cpuload: 0.6805555820465088
                                     memload: 44084.0
                                         snr: -39.0