SYSTEM AND METHOD FOR GEO-AWARE TRANSPORTATION BILLING VERIFICATION

• US 20180137487A1
• Filed: 03/30/2017
• Published: 05/17/2018
• Est. Priority Date: 11/11/2016
• Status: Active Grant

• Current Assignee: Operr Technologies, Inc.
• Original Assignee: Kevin Sunlin Wang
• Inventors: WANG, KEVIN SUNLIN
• Granted Patent: US 10,504,079 B2
• Time in Patent Office: Days
• CPC Class Codes: G06Q 10/08 Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
• CPC Class Codes: G06Q 20/0855 involving a third party
• CPC Class Codes: G06Q 20/14 specially adapted for billing systems
• CPC Class Codes: G06Q 20/3224 Transactions dependent on location of M-devices
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions

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.

Claims

1. A computer-implemented system for providing automated computer verification for a transportation service, said system comprising:

a computing system comprising one or more databases residing on one or more servers in connection with a communication network;

a vendor module configured to transmit a service request for providing a service for a passenger, said service request including at least one of a pickup time, a pickup location, a drop off time, or a drop off location;

a service provider module configured to receive said service request from said vendor module, assign said service request to a driver, and transmit said service request to said driver;

a driver module configured to receive said service request, generate a billing request, and transmit said billing request to said service provider module; and

a non-transitory computer-readable storage medium capable of storing instructions to instruct one or more processors to;

receive, by said service provider module, said service request from said vendor module through one of a plurality of computing devices;

transmit, by said service provider module, said service request to said driver module;

generate, by said driver module, said billing request;

compare said service request with said billing request;

identify whether said driver or said passenger is within a field of acceptability at a time said billing request is generated, said field of acceptability based on one or more predetermined rules characterized by at least one of (i) a predetermined distance from said pick up location (ii) a predetermined distance from said drop off location, (iii) a predetermined time relative to said pick up time, or (iv) a predetermined time relative to said drop off time; and

confirm completion of said service request contingent on said driver or said passenger identified as being within said field of acceptability.

3. The system according to claim 1, wherein said one or more processors are further configured to:

determine, prior to generating said billing request, at least one of (a) an actual pick up geolocation, (b) an actual drop off geolocation, (c) an actual pickup time, or (d) an actual drop off time; and

include in said billing request at least one of (e) said actual pick up geolocation, (f) said actual drop off geolocation, (g) said actual pickup time, or (h) said actual drop off time.

4. The system according to claim 1, wherein said one or more processors are configured to:

establish said field of acceptability based on said one or more predetermined rules, said field of acceptability relating to time and one of geolocation or location.

5. The system according to claim 1, wherein said billing request comprises at least one or more pickup locations, pickup times, drop off locations, or drop off times.

7. The system according to claim 1, said system further comprising:

a passenger module configured to at least transmit information from said passenger confirming completion of said service request by said driver;

wherein said information includes at least one of a signature, a PIN, a passcode, a fingerprint, other biometric data, or any other means for confirming said billing request from said passenger.

8. The system according to claim 7, wherein said information includes at least a timestamp or location data and is provided at one of a start of said service, an end of said service, or any other time relevant to said service.

9. The system according to claim 1, wherein said instruction to compare includes a comparison between one or more of (a) said pickup location and an actual pickup location, (b) said drop off location and an actual drop of location, (c) said pickup time and an actual pickup time, or (d) said drop off time and an actual drop off time to determine whether said driver is within said field of acceptability.

12. The system according to claim 1, wherein said one or more processors are further configured to:

identify a pickup intent of said driver for said passenger or a drop off intent of said driver for said passenger;

prompt said driver to confirm said pickup intent or said drop off intent;

identify whether said driver or said passenger is within said field of acceptability; and

alert said driver as to whether said driver or said passenger is within said field of acceptability;

wherein said pickup intent or said drop off intent is based on a predetermined speed of said driver while being within a predetermined distance of said pickup location or said drop-off location.

14. The system according to claim 12, wherein upon confirmation of said pickup intent or said drop off intent, said one or more processors are configured to alert said driver of failing to be within said field of acceptability.

15. The system according to claim 12, wherein said one or more processors are further configured to:

adjust said billing request to match said service request upon confirmation of completion of said service request;

or

issue a conditional rejection of said billing request based on said driver failing to be within said field of acceptability.

16. The system according to claim 1, wherein said one or more processors are further configured to:

prompt said driver to submit said billing relevant data through at least one of said plurality of computing devices upon failing to be within said field of acceptability;

mine said billing relevant data for a timestamp or a geolocation; and

update said one or more databases with said billing relevant data dynamically;

wherein said billing relevant data includes one or more reasons for failing to be within said field of acceptability while attempting to complete said service request, said one or more reasons including at least one of text data, audio data, image data, or video data.

17. The system according to claim 16, wherein said one or more processors are further configured to:

receive one or more verifications of said billing relevant data from one or more additional users having firsthand experience with said billing relevant data through at least one of said plurality of computing devices;

wherein said firsthand experience is identified as said one or more additional users determined to physically be or have been within a predetermined distance to said one or more actual geolocations relating to said billing relevant data based on said billing relevant data.

18. The system according to claim 16, wherein said one or more processors are further configured to:

adjust said billing request to match said service request responsive to said billing relevant data reaching a predetermined number of positive ratings within a predetermined period of time; and

update said field of acceptability dynamically.

19. The system according to claim 1, wherein said one or more processors are further configured to:

reject said billing request responsive to said billing relevant data failing to receive a predetermined number of positive ratings within a predetermined time.

20. The system according to claim 1, wherein said one or more processors are further configured to:

collect crowdsourced billing relevant data from one or more additional users having firsthand experience with said billing relevant data through one or more of said plurality of computing devices.

21. The system according to claim 20, wherein said one or more processors are further configured to:

update said one or more databases dynamically based on said billing relevant data and said crowdsourced billing relevant data.

22. The system according to claim 1, wherein said field of acceptability is characterized as at least one of:

a preliminary field of acceptability, a permanent field of acceptability, or a temporary field of acceptability; and

wherein only one of said preliminary field of acceptability, said permanent field of acceptability, or said temporary field of acceptability is active at a time.

23. The system according to claim 22, wherein said one or more processors are further configured to:

characterize said field of acceptability as said preliminary field of acceptability for said service request based on one or more predetermined default parameters.

24. The system according to claim 22, wherein said one or more processors are configured to:

collect said billing relevant data through said one or more user engagement panels; and

recharacterize said preliminary field of acceptability as said permanent field of acceptability based on said predetermined rules in accordance with said billing relevant data;

wherein said permanent field of acceptability is characterized as fully active; and

wherein said preliminary field of acceptability and said temporary field of acceptability are characterized as not active.

25. The system according to claim 22, wherein said one or more processors are configured to:

characterize said field of acceptability as said temporary field of acceptability based on a predetermined number of drivers completing services outside said permanent field of acceptability for said location; and

recharacterize said temporary field of acceptability as a new permanent field of acceptability based on said predetermined number of drivers completing said services within said temporary field of acceptability.

26. The system according to claim 22, wherein said one or more processors are further configured to:

characterize said permanent field of acceptability as semi-active based on a predetermined number of drivers completing services outside said permanent field of acceptability for said location;

wherein said permanent field of acceptability remains semi-active until;

(a) said temporary field of acceptability transforms to said new permanent field of acceptability;

or (b) upon at least one said driver completing said services within said semi-active field of acceptability.

27. The system according to claim 22, wherein said one or more processors are further configured to:

modify dynamically characterization of said field of acceptability from (a) said preliminary field of acceptability to said permanent field of acceptability, (b) said permanent field of acceptability to said temporary field of acceptability, or (c) said temporary field of acceptability to said permanent field of acceptability, in accordance with one of (d) aggregate billing relevant data received from a plurality of remote computing devices within a predetermined distance to said designated pickup location or said designated drop off location, (e) a predetermined first number of drivers completing service requests outside of said permanent field of acceptability, or (f) a predetermined second number of drivers completing service requests within said temporary field of acceptability.

28. The system according to claim 1, wherein said one or more processors are further configured to:

identify an absence of said passenger from said pickup location upon said passenger failing to confirm said service request within a predetermined period of time.

29. The system according to claim 28, wherein said one or more processors are further configured to:

track a length of time said driver waits for said passenger at said pickup location;

receive evidence from said driver of attempts to contact said passenger; and

transmit said evidence to said service provider module with at least a portion of said billing request verifying said absence of said passenger.

31. The system according to claim 1, wherein said one or more processors are further configured to:

aggregate billing relevant data received from said plurality of computing devices located within said predetermined distance from said designated pickup location or said predetermined distance from said designated drop off location;

store said aggregated billing relevant data in said one or more databases; and

update said predetermined rules dynamically in accordance with said aggregated billing relevant data.

32. The system according to claim 31, wherein said aggregated billing relevant data includes at least one of (a) a plurality of GPS data corresponding to one or more geolocations, or (b) a plurality of time data corresponding to one or more times or days of transmission of said aggregated billing relevant data.

33. The system according to claim 32, wherein said one or more processors are further configured to:

utilize said plurality of GPS data to continuously identify whether each of said plurality of computing devices is within said predetermined distance from said pickup location or said predetermined distance to said drop off location;

wherein said aggregated billing relevant data is performed continuously.

34. The system according to claim 33, wherein said aggregated billing relevant data includes information relating to at least one of:

traffic density, population density, a construction obstacle, a road closure, a lane closure, a weather condition, parking restrictions, road rules, constructions sites, temporary road blocks, special security events, parades, rallies, or protests.

35. The system according to claim 1, said system further comprising:

a geo-aware camera configured to enable said driver to capture data for submission to said system as billing relevant data indicative of a reason for failing to be within said field of acceptability;

wherein said plurality of computing devices are configured to enable one or more users to rate said billing relevant data with a positive rating or a negative rating.

2. (canceled)

6. (canceled)

10-11. -11. (canceled)

13. (canceled)

30. (canceled)

36. A method for establishing and updating a field of acceptability in geo-aware transportation computer verification, said method comprising the steps of:

establishing one or more fields of acceptability based on predetermined rules characterized by at least one of (1) a predetermined distance from a pick-up location (ii) a predetermined distance from a drop-off location, (iii) a predetermined time relative to a pick-up time, or (iv) a predetermined time relative to a drop-off time;

receiving a service request for a passenger from a vendor module, said service request including a pick-up time, a pick-up location, a drop-off time, or a drop-off location;

sending said service request to a service provider module;

assigning said service request to a driver through said service provider module;

confirming a driver'"'"'s completion of said service request through said passenger module;

receiving a billing request from a driver module;

comparing said service request to said billing request to determine whether said driver is within said field of acceptability;

adjusting said billing request automatically to match said service request responsive to said driver being within said field of acceptability;

aggregating billing relevant data received from said plurality of computing devices located within said predetermined distance from said designated pickup location or said designated drop off location;

updating said predetermined rules dynamically in accordance with said aggregated billing relevant data;

updating said field of acceptability dynamically in accordance with at least said predetermined rules; and

issue a notification in response to said comparing, said notification (i) indicating an acceptance of said billing request if said driver or said passenger is identified as being within said field of acceptability, or (ii) indicating a conditional rejection of said billing request if said driver or said passenger is identified as not being within said field of acceptability.