Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MaaS Use Case – Multimodal request – Deeplink with the mobility service – Need the tracking of usage in the MaaS platform #28

Open
levenes-mbc opened this issue May 13, 2022 · 0 comments

Comments

@levenes-mbc
Copy link

Here after is the MaaS use case to explain the different step in a booking session with a carpooling trip. This to show the need to have information exchanged between the MaaS and Service provider.

  1. The user check the availability to go to a specific place B from his home which does not provide a large public transport offer.

  2. The trip calculator in the MaaS platform shows all the possibilities for the trip. For the example, we have the following results :

    • A- Trip with his personal car to a toll parking then take a carpooling trip with mobility service provider 1 (Cost estimation for parking, Cost estimation for carpooling). A journey ID is given by the mobility service provider 1.
    • B- Trip with his personal car to a toll parking then take a carpooling trip with mobility service provider 2 (Cost estimation for parking, Cost estimation for carpooling). A journey ID is given by the mobility service provider 2.
    • C- Trip with his personal car to a toll parking then take a train to the final destination (Train ticket cost + Cost estimation for parking)
    • D- Trip with his personal car from end to end.
  3. The user chooses the multimodal trip B, this is memorized in the MaaS platform with a technical ID to ensure the uniqueness.

  4. Click on the trip and follow the deeplink to the application of the mobility service provider 2 with the transmission of the technical ID of MaaS to ensure the tracking of the usage.

  5. Deferred processing of the carpooling transaction in the process of the carpooling service provider.

  6. Asynchronous update of the transaction form the MaaS (Hash of MaaS ID and Journey ID) to allow the user to continue.

  7. Re open to the shopping cart of the MaaS platform to finalize the transaction for another element (tool parking)

  8. This allow the user manage his multimodal trip and to see all his consumption on different services (history of all centralized on the MaaS).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant