Most Probable Path & Destination Prediction API (MPP&DP API)

Overview - What is MPP&DP

Use-case examples with route/destination prediction

API specification

Considerations and recommendations

  1. Only one prediction model per moving object (vehicle) or per driver.
  2. If driver-based prediction is required, the customer must specify all of trips when generating the prediction model.
  3. The interval to execute the prediction per moving object (vehicle) or per driver should be carefully considered and should be long enough, e.g. more than 60 seconds. The prediction itself is relatively costly operation among multiple CVI components.
  4. Older prediction models remain on the server side as cache data when a new prediction model per moving object (vehicle) or per driver is created, therefore the customer must clear the cache by calling the API.

Architecture overview

component_diagram

How to use: Steps to enable and execute MPP&DP

Summarized steps

  1. Model generation

    1.1. Gather car probe data.
    1.2. Optional step. Configure parameters of prediction model generation.
    1.3. Create prediction model per moving object (vehicle).
    1.4. Optional step. Query Origin/Destination (O/D) patterns per moving object (vehicle).
    
  2. Prediction

    2.1 Execute prediction per moving object (vehicle)
    

Detailed steps by sequence diagram

sequence_diagram