Backtracker Status Report

Reading Time: 4 minutes

About Backtracker

As mentioned in the previous article our main project at the moment is Backtracker. The project aims to be a anti theft system. More in detail means that if you loose your mobile device it would be possible to gain it. This goal we achieve with a lot of information that we receive from the mobile device.


The problem until now was that our developing platform is not stable enough to be able to develop constantly on our project. This fact wouldn’t be that big problem, because we need only to transfer somehow the data from the device to our server. The bigger problem was that we aren’t sure how to implement the data reasoning. This problem should be now fixed by the use of structured semantic data such as RDF/OWL files. The well structured data as backend gives as the possibility to visualize and classify the data for different clients. For example on a desktop client we could visualize more data as on a mobile device. If you want to track our lost mobile device in real time it’s also useful to visualize other information as if you are at the home and want to see what the theft is doing with our device. On the other hand the server could easily extend the information received from the stolen device.

Listing 1: Description of the mobile device in RDF.

       - The RDF file about a mobile device. The IMSI identifies the
       - mobile device uniquely! Please feel free to add informations or
       - delete informations in your mobile device file.
    <bt:MobileDevice rdf:ID="IMEI_12345678901234">
        <bt:owner rdf:resource="" />
        <bt:manufacturer>OpenMoko, Inc</bt:manufacturer>
        <bt:cpu rdf:parseType="Resource">
            <bt:model>Samsung 2442B</bt:model>
                <bt:speed>400 MHZ</bt:speed>
            <bt:display rdf:parseType="Resource">
                <bt:colorDepth>24 Bit</bt:colorDepth>
            <bt:ram>128 SDRAM</bt:ram>
            <bt:internStorage>256 MB</bt:internStorage>
                    <rdf:li rdf:parseType="Resource">
                        <bt:currentFlashCard rdf:parseType="Resource">
                            <bt:capacity>8 GB</bt:capacity>
                <rdf:li rdf:parseType="Resource">
                    <bt:gsm rdf:parseType="Resource">
                        <bt:chip>Calypso D751992AZHH</bt:chip>
                <rdf:li rdf:parseType="Resource">
                    <bt:bluetooth rdf:parseType="Resource">
                <rdf:li rdf:parseType="Resource">
                    <!-- offline/local/online -->
                    <bt:wlan rdf:parseType="Resource">
                        <bt:chip>Atheros chipset AR6001 Flash version</bt:chip>
                        <bt:type>802.11 b/g</bt:type>
                <rdf:li rdf:parseType="Resource">
                    <!-- offline/local/online -->
                    <bt:usb rdf:parseType="Resource">
                <rdf:li rdf:parseType="Resource">
                    <bt:gps rdf:parseType="Resource">
                        <bt:chip>u-blox ANTARIS 4</bt:chip>
                    <rdf:li rdf:parseType="Resource">
                        <bt:accelerometer rdf:parseType="Resource">
            <bt:lastKnown rdf:parseType="Resource">
                <bt:imsi rdf:resource="sim_1234567890123456.rdf" />
                <bt:position rdf:parseType="Resource">
                    <geo:Point rdf:parseType="Resource">
Backtracker ControlUnit Mainscreen
Backtracker ControlUnit

Maybe it’s good to mention that the real time tracking works very well with a Server/Client infrastructure. The server is needed to have a reachable point at every time, because we don’t know when the stolen device is able to transfer the data, so the client hasn’t to be switch on 24/7. If the server receives the GPS coordinates from a mobile device and a client is connected the server saves the data and forwards it to the client. The client you could see at the left.

The Backtracker Ontology

As you can see in the listing 1 we use a own ontology to describe the device. Unfortunately the ontology is not specified until now. If our team has more time we would specify the language.