System and method for processing vehicle requests

• US 9,870,656 B2
• Filed: 12/07/2016
• Issued: 01/16/2018
• Est. Priority Date: 12/08/2015
• Status: Active Grant

• Current Assignee: Smartcar, Inc.
• Original Assignee: Smartcar, Inc.
• Inventors: Katta, Sanketh Suresh, Katta, Sahas Suresh
• Primary Examiner(s): Black, Thomas G
• Assistant Examiner(s): Lewandroski, Sara J
• Application Number:
  US15/372,257
• Publication Number:
  US 20170161973A1
• Time in Patent Office: 405 Days
• CPC Class Codes: G06Q 40/08 Insurance
• CPC Class Codes: G07C 5/008 communicating information to a remotely located station transmission systems for measured values G08C
• CPC Class Codes: G07C 5/0825 using optical means
• CPC Class Codes: G07C 5/085 using electronic data carriers

Abstract

A method and system for processing requests for vehicular data, including receiving a vehicle request for a vehicle parameter from a client system (e.g., third party application); verifying client access to the vehicle parameter; determining one or more parameter values for the requested vehicle parameter; and transmitting the one or more parameter values to the client system.

Claims

1. A method for processing requests for vehicular data, the method comprising:

receiving a first value for a first vehicle parameter from a first vehicle resource, the first value sampled by a first vehicle at a first time;

storing the first value;

prior to receiving a vehicle request comprising a system access token from a third party application;

receiving a system access request from the third party application; and

in response to verifying the system access request, transmitting the system access token to the third party application;

receiving the vehicle request for the first vehicle parameter from the third party application;

prior to transmitting a first resource query for the first vehicle parameter to the first vehicle resource;

transmitting a resource access request to the first vehicle resource; and

in response to verification of the resource access request by the first vehicle resource, receiving a resource access token from the first vehicle resource;

in response to verifying the vehicle request, transmitting the first resource query for the first vehicle parameter to the first vehicle resource, wherein verifying the vehicle request comprises;

mapping the vehicle request to a user identifier stored in association with a client identifier identifying the third party application; and

verifying the system access token from the vehicle request based on the client identifier, wherein the first resource query comprises the resource access token stored in association with the user identifier, the resource access token granting access to the first vehicle resource;

in response to acceptance of the first resource query by the first vehicle resource, receiving a second value for the first vehicle parameter from the first vehicle resource, the second value sampled at the first vehicle at a second time after the first time;

in response to rejection of the first resource query by the first vehicle resource, retrieving the first value; and

transmitting at least one of the first value and the second value to the third party application.

2. The method of claim 1, wherein the first vehicle resource is a first original equipment manufacturer (OEM) platform, wherein the resource access token is a first OEM access token granting access to the first OEM platform, and wherein the user identifier is stored in association with the first OEM access token.

3. The method of claim 2, wherein the user identifier is further associated with a second OEM access token granting access to a second OEM platform, wherein the first OEM access token is associated with a first permission level granting access to the first vehicle parameter at the first OEM platform, and wherein the second OEM access token is associated with a second permission level granting access to a second vehicle parameter at the second OEM platform.

4. The method of claim 1, further comprising:

associating the user identifier with a variable limit rule from a plurality of request rules stored at a remote system in association with a plurality of user identifiers;

associating the vehicle request with the variable limit rule; and

transmitting a rejection of the vehicle request to the third party application in response to determining that the vehicle request fails to satisfy the variable limit rule, wherein transmitting the first resource query is further in response to determining that the vehicle request satisfies the variable limit rule.

5. The method of claim 1, wherein receiving the vehicle request comprises receiving the vehicle request for a second vehicle parameter associated with a second vehicle, the method further comprising:

in response to verifying the vehicle request, transmitting a second resource query for the second vehicle parameter to a second vehicle resource;

in response to acceptance of the second resource query by the second vehicle resource;

receiving a value for the second vehicle parameter from the second vehicle resource; and

transmitting the value for the second parameter to the third party application.

6. The method of claim 5, further comprising:

translating the vehicle request into the first resource query based on a first subset of communication protocol rules associated with the first vehicle resource; and

translating the vehicle request into the second resource query based on a second subset of communication protocol rules associated with the second vehicle resource.

7. The method of claim 6, wherein the first vehicle resource is the first vehicle, wherein the second vehicle resource is an original equipment manufacturer platform associated with the second vehicle.

8. The method of claim 1, further comprising:

determining a timestamp of a historical resource query transmitted for the first vehicle parameter to the first vehicle resource; and

determining a request receipt timestamp of the vehicle request, wherein verifying the vehicle request is based on the timestamp within a threshold duration of the request receipt timestamp.

9. The method of claim 1, further comprising:

receiving a second vehicle request comprising a vehicle command to operate the first vehicle;

generating control instructions for the first vehicle based on the vehicle command; and

transmitting the control instructions to the first vehicle for execution, thereby transforming the first vehicle to a different state.

10. The method of claim 1, further comprising querying the vehicle resource for a state-of-charge of the first vehicle, wherein transmitting the first resource query is further in response to the state-of-charge exceeding a threshold.

11. The method of claim 1, wherein the first vehicle parameter is an odometer reading, and, wherein transmitting to the third party application comprises transmitting the at least one of the first and the second value for the odometer reading to the third party application.

12. A method for processing requests for vehicular data, the method comprising:

receiving a first value for a first vehicle parameter from a first vehicle resource, the first value sampled by a first vehicle at a first time;

storing the first value;

receiving a vehicle request for the first vehicle parameter from a third party application;

querying the vehicle resource for a state-of-charge of the first vehicle;

in response to verifying the vehicle request and the state-of-charge exceeding a threshold, transmitting a first resource query for the first vehicle parameter to the first vehicle resource;

in response to acceptance of the first resource query by the first vehicle resource, receiving a second value for the first vehicle parameter from the first vehicle resource, the second value sampled at the first vehicle at a second time after the first time;

in response to rejection of the first resource query by the first vehicle resource, retrieving the first value; and

transmitting at least one of the first value and the second value to the third party application.