search

edwinvandenbelt / images

0 stars 0 forks source link

TOMP API images #1

Open edwinvandenbelt opened 5 years ago

edwinvandenbelt commented 5 years ago

image

edwinvandenbelt commented 5 years ago

image

edwinvandenbelt commented 5 years ago

image

edwinvandenbelt commented 5 years ago

image

edwinvandenbelt commented 5 years ago

image

edwinvandenbelt commented 5 years ago

image

edwinvandenbelt commented 5 years ago

image

edwinvandenbelt commented 5 years ago

image

edwinvandenbelt commented 4 years ago

image Postponed confirmed class Booking { state { availibility_checked { availability-request -> pending; } pending { asset-request -> confirmed; asset-postponed-request -> postponedconfirmed; cancel-request -> released; expired -> expired; } postponedconfirmed { commit -> confirmed; deny -> cancelled; } confirmed { cancel-booking -> cancelled; } } }

edwinvandenbelt commented 4 years ago

image

edwinvandenbelt commented 4 years ago

FMS image title simple flow TOMP API - FMS - trip exec

note over User, MP, FMS, Taxi around 10 minutes before start of leg end note

loop until found a taxi or none available FMS->Taxi: I've got a ride for you alt accepts Taxi->FMS: accept

FMS->MP: COMMIT MP->User: inform the trip can be done

Taxi->FMS: ETA FMS->MP: ETA MP->User: ETA

Taxi->FMS: start ride FMS->MP: start ride

Taxi->FMS: end ride FMS->MP: end ride else denies Taxi->FMS: denies note over FMS FMS can find another taxi? end note end alt end loop

FMS->MP: DENY note over MP MP can find another alternative? end note MP->User: inform

edwinvandenbelt commented 4 years ago

FMS 2 image title simple flow TOMP API - FMS

note over User, MP, FMS Planning phase end note

User->+MP: request trip from A to B note over MP do some trip planning, find possible legs look for TOs that can fulfill these legs. Hei, there's FMS! end note MP->+FMS: request transport for found legs FMS->-MP: possibilities, postponed commit condition with ultimate-response-time = start time - 10 minutes note over MP construct the best option(s) to get user from A to B, with knowledge of the personal aspects end note MP->+FMS: provide ids for legs FMS->-MP: legs with id MP->-User: present best options note over User user selects an option to book end note User->+MP: book this option MP->+FMS: book legs FMS->-MP: ok, all in pending state MP->+FMS: commit all legs FMS->-MP: ok, all in CONDITIONAL_CONFIRMED state MP->-User: ok

edwinvandenbelt commented 4 years ago

AlocCars - planning/booking image title simple flow TOMP API - AlocCars

note over User, MP, AlocCars Planning phase end note

User->+MP: request trip from A to B note over MP do some trip planning, find possible legs look for TOs that can fulfill these legs. Hei, there's AlocCars! end note alt provide license driver upfront MP->+AlocCars: request transport for found legs, providing driver license AlocCars->-MP: possibilities, postponed commit condition else provide on booking MP->+AlocCars: request transport for found legs AlocCars->-MP: possibilities, postponed commit condition, require-booking-data-condition[driver-license] end alt note over MP construct the best option(s) to get user from A to B, with knowledge of the personal aspects end note MP->+AlocCars: provide ids for legs AlocCars->-MP: legs with id MP->-User: present best options note over User user selects an option to book end note User->+MP: book this option MP->+AlocCars: book legs, provide driver license in case of require-booking-data AlocCars->-MP: ok, all in pending state MP->+AlocCars: commit all legs AlocCars->-MP: ok, all in CONDITIONAL_CONFIRMED state MP->-User: ok

edwinvandenbelt commented 4 years ago

AlocCars image title simple flow TOMP API - AlocCars - trip execution

note over User, MP, AlocCars Trip execution end note

User->+MP: get access for car MP->+AlocCars: /legs/{id}/events PREPARE AlocCars->-MP: return digibox code MP->-User: provide access code

User->+MP: /legs/{id}/events SET_IN_USE; the car is opened and the leg starts MP->+AlocCars: /legs/{id}/events SET_IN_USE AlocCars->-MP: ok MP->-User: ok

User->MP: /legs/{id}/events FINISH; the car is closed and the leg ends MP->AlocCars: /legs/{id}/events FINISH AlocCars->-MP: ok MP->-User: ok

edwinvandenbelt commented 4 years ago

Publibike image title simple flow TOMP API - Publibike - planning & booking

note over User, MP no trip planning possible. Get TOs around A end note alt no bluetooth swipe User->+MP: request trip from A MP->+Publibike: request transport for asset at A, directly provide ids Publibike->-MP: possibilities MP->-User: present best options else bluetooth swipe note over User the app will do a bluetooth swipe, use every bluetooth device idin the request end note User->+MP: request trip from A with found assets MP->+Publibike: request transport for asset at A, directly provide ids Publibike->-MP: possibilities MP->-User: present best options end note over User user selects an option to book end note User->+MP: book this option MP->+Publibike: book legs Publibike->-MP: ok, all in pending state MP->+Publibike: commit all legs Publibike->-MP: ok, all in CONFIRMED state, provide information to open bike MP->-User: ok, provide information to open bike (deep link?)

edwinvandenbelt commented 4 years ago

image title simple flow TOMP API - Publibike - trip execution

alt custom app note over User MP app is using custom app (deeplink) to open asset end note User->+MP: /legs/{id}/SET_IN_USE MP->+Publibike: /legs/{id}/SET_IN_USE Publibike->-MP: ok MP->-User: ok else internet connected User->+MP: /legs/{id}/SET_IN_USE MP->+Publibike: /legs/{id}/SET_IN_USE note over Publibike bike is remotely opened end note Publibike->-MP: ok MP->User: ok else bluetooth operated note over User MP app is using bluetooth to open asset end note User->+MP: /legs/{id}/SET_IN_USE MP->+Publibike: /legs/{id}/SET_IN_USE Publibike->-MP: ok MP->-User: ok end alt