Lookahead.org

Lookahead SmartCity BigData MobileIoT M2MCloud

Demo

Use a GPX file instead of the route plan to do the simulation.

Step 1. Select a GPX file (contains GPS track points) from local disk as an input to the mobile terminal. Click here to download a sample GPX file.

     
     

Step 2. Specify the geofence radius as the second input to the mobile terminal.
      (meter)

Step 3. Select the program to run.

Program Lookahead Type Use Case Description Setting
No lookahead Before introducing the lookahead strategy to the mobile-centric geofencing. This is the baseline version of location tracking with circular geofence. It is used to benchmark with the other demo programs. No lookahead request will be sent to Lookahead Server.
Regressive lookahead. No reference to route plan, historical trajectory, or geographic map. Neither route plan nor historical trajectory is in place. We still want to have a bare lookahead without the reference of surrounding roadmap. It should be statistically much better than the random guess and able to mitigate the penalty of prediction error. This is the most cost-effective option for the predictive location tracking. If you are satisfied with it alone, you can implement the simple algorithm (read the research paper) in mobile terminal or Location Server, and then be independent to the Lookahead Server! (1) The destination/next stop location will not be sent to Lookahead Server.
(2) A new mobile identity will be generated so the location cache specific to the mobile is empty.
Greedy lookahead by reference to historical trajectory In case the route plan is not available, the Lookahead Server can still perform the greedy lookahead if the mobile is on track of historical trajectory stored in location cache.
(1) A consumer user has a simple round trip between house and workplace in the daily life.
(2) An enterprise user has a regular path of transportation in the routine task.
The mobile trajectory is extended by appending its reverse path, so it becomes a round trip. The regressive lookahead will be performed on forward tracking; the greedy lookahead will be performed on backward tracking. (1) The destination/next stop location will not be sent to Lookahead Server.
(2) A new mobile identity will be generated so the location cache specific to the mobile is empty.