-
Notifications
You must be signed in to change notification settings - Fork 3
Description
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.
-
The user check the availability to go to a specific place B from his home which does not provide a large public transport offer.
-
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.
-
The user chooses the multimodal trip B, this is memorized in the MaaS platform with a technical ID to ensure the uniqueness.
-
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.
-
Deferred processing of the carpooling transaction in the process of the carpooling service provider.
-
Asynchronous update of the transaction form the MaaS (Hash of MaaS ID and Journey ID) to allow the user to continue.
-
Re open to the shopping cart of the MaaS platform to finalize the transaction for another element (tool parking)
-
This allow the user manage his multimodal trip and to see all his consumption on different services (history of all centralized on the MaaS).