System and method for geo-aware transportation billing verification
First Claim
1. A system for providing automated computer verification for a transportation service, the system comprising:
- a server in communication with a plurality of driver computing devices associated with a plurality of drivers via a network, wherein the server includes at least one non-transitory computer-readable storage medium with computer-readable instructions stored thereon, and a processor instructed to execute the computer-readable instructions to;
receive service request data related to one or more service requests for one or more passengers, wherein the one or more service requests are associated with at least one of a pickup location or a pickup time-location, and at least one of a dropoff location or a dropoff time-location;
receive, from the plurality of driver computing devices, real-time driver data comprising at least one of a real-time location data set or a real-time time-location data set associated with the plurality of drivers, wherein the real-time driver data is periodically transmitted from one or more location identifiers associated with the plurality of driver computing devices during performance of the one or more service requests;
identify a particular portion of the real-time driver data which does not match at least a corresponding one of the designated pickup location, the designated dropoff location, the designated pickup time-location, or the designated dropoff time-location of the one or more service requests;
transmit one or more rejections, to the plurality of driver computing devices, associated with the corresponding one of the designated pickup location, the designated dropoff location, the designated pickup time-location, or the designated dropoff time-location of the one or more service requests, each rejection indicating that a respective driver is not within a first field of acceptability associated with the corresponding one of the designated pickup location, the designated dropoff location, the designated pickup time-location, or the designated dropoff time-location, wherein the first field of acceptability is based on one or more predetermined rules and includes corresponding aggregate data comprising at least one of (i) one or more location data sets corresponding to the designated pickup location or the designated dropoff location, or (ii) one or more time-location data sets corresponding to at least one of the designated pickup time-location or the designated dropoff time-location, and wherein each rejection prompts the respective driver to;
submit respective service request completion relevant data justifying the respective driver not being within the first field of acceptability;
store the respective service request completion relevant data on the server;
responsive to transmitting a predetermined number of rejections within a predetermined period of time, adjust the first field of acceptability to a second field of acceptability comprising at least the particular portion of the driver data.
1 Assignment
0 Petitions
Accused Products
Abstract
A geo-aware transportation verification system and is disclosed. A processor receives a billing request for payment, including an actual geolocation and an actual time and date. The processor compares a service request to a billing request to determine whether a driver is within a field of acceptability. There are at least three types of fields of acceptability for assisting billing verification, where one may be active at a time. The processor automatically adjusts the billing request to match the service request if the driver is within a field of acceptability for geolocation and time. The processor conditionally rejects a billing request if the driver is not within the field of acceptability and provides a user engagement panel on which the user is allowed to submit billing relevant data for further verification. The field of acceptability is updated dynamically based on collected data.
57 Citations
29 Claims
-
1. A system for providing automated computer verification for a transportation service, the system comprising:
a server in communication with a plurality of driver computing devices associated with a plurality of drivers via a network, wherein the server includes at least one non-transitory computer-readable storage medium with computer-readable instructions stored thereon, and a processor instructed to execute the computer-readable instructions to; receive service request data related to one or more service requests for one or more passengers, wherein the one or more service requests are associated with at least one of a pickup location or a pickup time-location, and at least one of a dropoff location or a dropoff time-location; receive, from the plurality of driver computing devices, real-time driver data comprising at least one of a real-time location data set or a real-time time-location data set associated with the plurality of drivers, wherein the real-time driver data is periodically transmitted from one or more location identifiers associated with the plurality of driver computing devices during performance of the one or more service requests; identify a particular portion of the real-time driver data which does not match at least a corresponding one of the designated pickup location, the designated dropoff location, the designated pickup time-location, or the designated dropoff time-location of the one or more service requests; transmit one or more rejections, to the plurality of driver computing devices, associated with the corresponding one of the designated pickup location, the designated dropoff location, the designated pickup time-location, or the designated dropoff time-location of the one or more service requests, each rejection indicating that a respective driver is not within a first field of acceptability associated with the corresponding one of the designated pickup location, the designated dropoff location, the designated pickup time-location, or the designated dropoff time-location, wherein the first field of acceptability is based on one or more predetermined rules and includes corresponding aggregate data comprising at least one of (i) one or more location data sets corresponding to the designated pickup location or the designated dropoff location, or (ii) one or more time-location data sets corresponding to at least one of the designated pickup time-location or the designated dropoff time-location, and wherein each rejection prompts the respective driver to; submit respective service request completion relevant data justifying the respective driver not being within the first field of acceptability; store the respective service request completion relevant data on the server; responsive to transmitting a predetermined number of rejections within a predetermined period of time, adjust the first field of acceptability to a second field of acceptability comprising at least the particular portion of the driver data. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11)
-
12. A system for providing automated computer verification for a transportation service, the system comprising:
a server in communication with a plurality of driver computing devices associated with a plurality of drivers via a network, wherein the server includes at least one non-transitory computer-readable storage medium with computer-readable instructions stored thereon, and a processor instructed to execute the computer-readable instructions to; receive service request data related to a service request for a passenger, the service request data including at least one of a designated pickup location or a designated pickup time-location, and at least one of a designated dropoff location or a designated dropoff time-location for the passenger; receive, from a first computing device of the plurality of driver computing devices that is associated with a driver, real-time driver data comprising at least one of a real-time location data set or a real-time time-location data set associated with the driver, wherein the real-time driver data is periodically transmitted from one or more location identifiers associated with the first computing device during performance of the service request; identify a particular portion of the real-time driver data which does not match at least a corresponding one of the designated pickup location, the designated dropoff location, the designated pickup time-location, or the designated dropoff time-location of the service request; transmit a rejection to the first computing device for not being within a first field of acceptability, wherein the first field of acceptability is based on one or more predetermined rules, and includes corresponding aggregate data comprising at least one of (i) one or more location data sets corresponding to at least one of the designated pickup location or the designated dropoff location, or (ii) one or more time-location data sets corresponding to at least one of the designated pickup time-location or the designated dropoff time-location, and wherein the rejection prompts the driver to submit service request completion relevant data justifying the driver not being within the first field of acceptability; store the service request completion relevant data on the server; transmit for display at least a portion of the service request completion relevant data, via one or more additional computing devices, to one or more additional users having firsthand experience; responsive to receiving, from the one or more additional users, via the one or more additional computing devices, one or more verifications of the service request completion relevant data comprising one or more ratings; adjust the first field of acceptability to a second field of acceptability comprising at least the particular portion of the driver data in response to the one or more ratings reaching a predetermined number of positive ratings within a predetermined period of time. - View Dependent Claims (13, 14, 15)
-
16. A method for providing automated computer verification for a transportation service, the method comprising:
-
receiving service request data related to one or more service requests for one or more passengers, wherein the one or more service requests are associated with at least one of a pickup location or a pickup time-location, and at least one of a dropoff location or a dropoff time-location; receiving, from a plurality of driver computing devices associated with a plurality of drivers, real-time driver data comprising at least one of a real-time location data set or a real-time time-location data set associated with the plurality of drivers, wherein the real-time driver data is periodically transmitted from one or more location identifiers associated with the plurality of driver computing devices during performance of the one or more service requests; identifying, by a server computing system, a particular portion of the real-time driver data which does not match at least a corresponding one of the designated pickup location, the designated dropoff location, the designated pickup time-location, or the designated dropoff time-location of the one or more service requests; transmitting one or more rejections, to the plurality of driver computing devices, associated with the corresponding one of the designated pickup location, the designated dropoff location, the designated pickup time-location, or the designated dropoff time-location of the one or more service requests, each rejection indicating that a respective driver is not within a first field of acceptability associated with the corresponding one of the designated pickup location, the designated dropoff location, the designated pickup time-location, or the designated dropoff time-location, wherein the first field of acceptability is based on one or more predetermined rules and includes corresponding aggregate data comprising at least one of (i) one or more location data sets corresponding to the designated pickup location or the designated dropoff location, or (ii) one or more time-location data sets corresponding to at least one of the designated pickup time-location or the designated dropoff time-location, and wherein each rejection prompts the respective driver to; submitting respective service request completion relevant data justifying the respective driver not being within the first field of acceptability; storing the respective service request completion relevant data on a server; responsive to transmitting a predetermined number of rejections within a predetermined period of time, adjusting the first field of acceptability to a second field of acceptability comprising at least the particular portion of the driver data. - View Dependent Claims (17, 18, 19, 20, 21, 22, 23, 24, 25)
-
-
26. A method for providing automated computer verification for a transportation service, the method comprising:
-
receiving service request data related to a service request for a passenger, the service request data including at least one of a designated pickup location or a designated pickup time-location, and at least one of a designated dropoff location or a designated dropoff time-location for the passenger; receiving, from a first computing device associated with a particular driver, real-time driver data comprising at least one of a real-time location data set or a real-time time-location data set associated with the particular driver, wherein the real-time driver data is periodically transmitted from one or more location identifiers associated with the first computing device during performance of the service request; identifying, by a server computing system, a particular portion of the real-time driver data which does not match at least a corresponding one of the designated pickup location, the designated dropoff location, the designated pickup time-location, or the designated dropoff time-location of the service request; transmitting a rejection to the first computing device for not being within a first field of acceptability, wherein the first field of acceptability is based on one or more predetermined rules, and includes corresponding aggregate data comprising at least one of (i) one or more location data sets corresponding to at least one of the designated pickup location or the designated dropoff location, or (ii) one or more time-location data sets corresponding to at least one of the designated pickup time-location or the designated dropoff time-location, and wherein the rejection prompts the particular driver to submit service request completion relevant data justifying the particular driver not being within the first field of acceptability; storing the service request completion relevant data on a server; transmitting for display at least a portion of the service request completion relevant data, via one or more additional computing devices, to one or more additional users having firsthand experience; responsive to receiving, from the one or more additional users, via the one or more additional computing devices, one or more verifications of the service request completion relevant data comprising one or more ratings; adjusting the first field of acceptability to a second field of acceptability comprising at least the particular portion of the driver data in response to the one or more ratings reaching a predetermined number of positive ratings within a predetermined period of time. - View Dependent Claims (27, 28, 29)
-
Specification