Mobility as a service interface
An interface system may include a communication interface. The interface system may include one or more processing units communicatively coupled with the communication interface. The interface system may include a memory having instructions stored thereon that, when executed, cause the one or more processing units to provide an application programming interface (API) that enables a managing authority system and a plurality of mobility entity systems to communicate with one another and the interface system via the communications interface. Each of the mobility entity systems may provide at least one mode of transportation. The instructions may further cause the one or more processing units to establish a communications link between the managing authority system and at least one of the plurality of mobility entity systems.
1. An interface system comprising:
a communication interface;
one or more processing units communicatively coupled with the communication interface; and
a memory having instructions stored thereon that, when executed, cause the one or more processing units to:
provide an application programming interface (API) that enables a managing authority system and a plurality of mobility entity systems to communicate with one another and the interface system via the communications interface, wherein each of the mobility entity systems provides at least one mode of transportation;
establish a communications link between the managing authority system and at least one of the plurality of mobility entity systems to enable planning for one or more journeys by one or more users dynamically, based on real-time data, wherein the real time data includes updates on locations of one or more vehicles and schedules for the one or more journeys;
receive a request through the communication link for a self-provision test against the API from the plurality of the mobility entity systems;
perform a procedure associated with the self-provision test for each of the plurality of mobility entity systems to check for a connection with the API;
grant tokens to the plurality of mobility entity systems based on a result of the self-provision test; and
authorize the plurality of mobility entity systems for usage of the API based on the tokens.
2. The interface system of claim 1 , wherein:
the API enables the managing authority system and the plurality of mobility entity systems to communicate with one another without need to program interfaces between each pair of systems.
3. The interface system of claim 1 , wherein the instructions further cause the one or more processing units to:
enable each of the plurality of mobility entity systems to self-certify with the API based on the self-provision test result.
4. The interface system of claim 3 , wherein the instructions further cause the one or more processing units to:
monitor API performance of each of the plurality of mobility entity systems based on data speed, scheduling prioritization, occurrence of errors.
5. The interface system of claim 1 , wherein the instructions further cause the one or more processing units to:
provide a transaction ledger configured to record events associated with one or more selected from a group comprising planning a journey for a traveler, providing a mobility service for the traveler, and paying for the mobility service.
6. The interface system of claim 5 , wherein the instructions further cause the one or more processing units to:
provide analytics of data in the transaction ledger; and
perform a fraud analysis of the transaction ledger.
7. The interface system of claim 1 , wherein the instructions further cause the one or more processing units to:
provide a managing authority the ability to upload one or more contracts and, for each of the one or more contracts:
select a contract type for the respective contract, and
activate the contract for use in the interface system;
provide a mobility entity the ability to choose a contract of the one or more contracts; and
provide the managing authority the ability to approve the mobility entity for a chosen contract.
8. A method of operating an interface system, comprising:
providing an application programming interface (API) that enables a managing authority system and a plurality of mobility entity systems to communicate with one another and the interface system via a communications interface of the interface system, wherein each of the mobility entity systems provides at least one mode of transportation;
establishing a communications link between the managing authority system and at least one of the plurality of mobility entity systems to enable planning for one or more journeys by one or more users dynamically, based on real-time data, wherein the real time data includes updates on locations of one or more vehicles and schedules for the one or more journeys;
receiving a request through the communication link for a self-provision test against the API from the plurality of the mobility entity systems;
performing a procedure associated with the self-provision test for each of the plurality of mobility entity systems to check for a connection with the API;
granting tokens to the plurality of mobility entity systems based on a result of the self-provision test; and
authorizing the plurality of mobility entity systems for usage of the API based on the tokens.
9. The method of operating an interface system of claim 8 , further comprising:
enabling each of the plurality of mobility entity systems to self-certify with the API based on the self-provision test result.
10. The method of operating an interface system of claim 8 , further comprising:
monitoring API performance of each of the plurality of mobility entity systems based on data speed, scheduling prioritization, occurrence of errors.
11. The method of operating an interface system of claim 8 , further comprising:
providing a transaction ledger configured to record events associated with one or more selected from a group comprising planning a journey for a traveler, providing a mobility service for the traveler, and paying for the mobility service.
12. The method of operating an interface system of claim 11 , further comprising:
providing analytics of data in the transaction ledger.
13. The method of operating an interface system of claim 11 , further comprising:
performing a fraud analysis of the transaction ledger.
14. The method of operating an interface system of claim 8 , further comprising:
providing a managing authority the ability to upload one or more contracts and, for each of the one or more contracts:
selecting a contract type for the respective contract, and
activating the contract for use in the interface system;
providing a mobility entity the ability to choose a contract of the one or more contracts; and
providing the managing authority the ability to approve the mobility entity for a chosen contract.
15. A non-transitory computer-readable medium having instructions stored thereon that, when executed by one or more processors of an interface system, cause the one or more processors to:
provide an application programming interface (API) that enables a managing authority system and a plurality of mobility entity systems to communicate with one another and the interface system via a communications interface of the interface system, wherein each of the mobility entity systems provides at least one mode of transportation;
establish a communications link between the managing authority system and at least one of the plurality of mobility entity systems to enable planning for one or more journeys by one or more users dynamically, based on real-time data, wherein the real time data includes updates on locations of one or more vehicles and schedules for the one or more journeys;
receive a request through the communication link for a self-provision test against the API from the plurality of the mobility entity systems;
perform a procedure associated with the self-provision test for each of the plurality of mobility entity systems to check for a connection with the API;
grant tokens to the plurality of mobility entity systems based on a result of the self-provision test; and
authorize the plurality of mobility entity systems for usage of the API based on the tokens.
16. The non-transitory computer-readable medium of claim 15 , wherein the instructions further cause the one or more processors to:
enable each of the plurality of mobility entity systems to self-certify with the API based on the self-provision test result.
17. The non-transitory computer-readable medium of claim 15 , wherein the instructions further cause the one or more processors to:
monitor API performance of each of the plurality of mobility entity systems based on data speed, scheduling prioritization, occurrence of errors.
18. The non-transitory computer-readable medium of claim 15 , wherein the instructions further cause the one or more processors to:
provide a transaction ledger configured to record events associated with one or more selected from a group comprising planning a journey for a traveler, providing a mobility service for the traveler, and paying for the mobility service.
19. The non-transitory computer-readable medium of claim 18 , wherein the instructions further cause the one or more processors to:
provide analytics of data in the transaction ledger; and
perform a fraud analysis of the transaction ledger.
20. The non-transitory computer-readable medium of claim 15 , wherein the instructions further cause the one or more processors to:
provide a managing authority the ability to upload one or more contracts and, for each of the one or more contracts:
select a contract type for the respective contract, and
activate the contract for use in the interface system;
provide a mobility entity the ability to choose a contract of the one or more contracts; and
provide the managing authority the ability to approve the mobility entity for a chosen contract.