Systems and methods for providing navigation data to a vehicle

• US 10,288,442 B2
• Filed: 07/19/2018
• Issued: 05/14/2019
• Est. Priority Date: 09/26/2013
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google LLC (Alphabet Inc.)
• Inventors: Foster, Andrew, Pelly, Nicholas J.
• Primary Examiner(s): Whittington, Jess
• Application Number:
  US16/039,631
• Publication Number:
  US 20180321057A1
• Time in Patent Office: 299 Days
• CPC Class Codes: G01C 21/3626 Details of the output of route guidance instructions traffic control systems for road vehicles involving transmission of navigation instructions to the vehicle G08G1/0968
• CPC Class Codes: G01C 21/3676 Overview of the route on the road map

Abstract

In a method for exchanging navigation data between a portable device and a head unit of a vehicle, implemented in a portable device that includes one or more processors executing a navigation service application and a companion application, the navigation service application sends a destination to a navigation server, and receives first navigation data from the navigation server. The first navigation data describes at least one of a plurality of steps for navigating between a source and the destination. A companion application invokes a navigation application programming interface (API) of the navigation service application, at by using a syntax and a list of parameters specific to the navigation API to obtain, from the navigation service application, the first navigation data, and sends the first navigation data to the head unit to cause the head unit to display navigation information indicating at least the one of the plurality of navigation steps.

Claims

1. A method for exchanging navigation data between a portable device and a head unit of a vehicle, the method being implemented in a portable device that includes one or more processors executing (i) a navigation service application configured to receive navigation data from a navigation server and (ii) a companion application that executes on the portable device separately from the navigation service application, the method comprising:

sending, by the navigation service application, a destination to the navigation server via a long-range communication link;

receiving, by the navigation service application, first navigation data from the navigation server via the long-range communication link, wherein the first navigation data describes at least one of a plurality of steps for navigating between a source and the destination;

invoking, by the companion application, a navigation application programming interface (API) of the navigation service application, wherein invoking the navigation API includes using a syntax and a list of parameters specific to the navigation API to obtain, from the navigation service application, the first navigation data; and

sending, by the companion application, the first navigation data to the head unit via a short-range communication link to cause the head unit to display navigation information indicating at least the one of the plurality of steps for navigating between the source and the destination.

2. The method of claim 1, further comprising, prior to sending the destination to the navigation server via the long-range communication link:

receiving, by the companion application and via the short-range communication link, the destination, the destination having been selected via the head unit; and

invoking, by the companion application, the navigation API by using the syntax and the list of parameters specific to the navigation API to provide the destination to the navigation service application.

3. The method of claim 1, wherein the navigation API communicates with the navigation service application using an IPC scheme.

4. The method of claim 1, wherein the syntax and the list of parameters specific to the navigation API defines a set of one or more data structures for exchanging data between the navigation API and the companion application.

5. The method of claim 1, wherein the first navigation data describes a sequence of steps, and wherein invoking the navigation API includes using the syntax and the list of parameters specific to the navigation API to receive from the navigation service application, in response to providing each of a plurality of next step requests to the navigation service application, a next one in the sequence of steps for transmission to the head unit.

6. The method of claim 1, wherein invoking the navigation API includes using the syntax and the list of parameters specific to the navigation API to provide authentication information to the navigation service application.

7. The method of claim 1, wherein:

the first navigation data received from the navigation server conforms to a first format; and

the navigation API, when invoked by the companion application, converts the first navigation data to a second format defined only for communicating navigation data between the navigation service application and the head unit.

8. The method of claim 7, wherein the second format is an open format compatible with a plurality of vehicle makes.

9. The method of claim 7, wherein the second format is a format specific to a manufacturer of the vehicle.

10. The method of claim 1, wherein the companion application communicates with the head unit according to a proprietary communication protocol defined by a manufacturer of the head unit.

11. The method of claim 1, wherein the companion application communicates with the head unit according to a first proprietary communication scheme defined by a manufacturer of the head unit, and wherein the navigation service application communicates with the navigation server according to a second proprietary communication scheme defined by an operator of the navigation server.

12. A portable device that includes one or more processors, wherein the portable device is configured, when the one or more processors execute (i) a navigation service application configured to receive navigation data from a navigation server and (ii) a companion application that executes on the portable device separately from the navigation service application, to execute a method comprising:

sending, by the navigation service application, a destination to the navigation server via a long-range communication link;

receiving, by the navigation service application, first navigation data from the navigation server via the long-range communication link, wherein the first navigation data describes at least one of a plurality of steps for navigating between a source and the destination;

invoking, by the companion application, a navigation application programming interface (API) of the navigation service application, wherein invoking the navigation API includes using a syntax and a list of parameters specific to the navigation API to obtain, from the navigation service application, the first navigation data; and

sending, by the companion application, the first navigation data to a head unit of a vehicle via a short-range communication link to cause the head unit to display navigation information indicating at least the one of the plurality of steps for navigating between the source and the destination.

13. The portable device of claim 12, wherein the method further comprises, prior to sending the destination to the navigation server via the long-range communication link:

receiving, by the companion application and via the short-range communication link, the destination, the destination having been selected via the head unit; and

invoking, by the companion application, the navigation API by using the syntax and the list of parameters specific to the navigation API to provide the destination to the navigation service application.

14. The portable device of claim 12, wherein the syntax and the list of parameters specific to the navigation API defines a set of one or more data structures for exchanging data between the navigation API and the companion application.

15. The portable device of claim 12, wherein the first navigation data describes a sequence of steps, and wherein invoking the navigation API includes using the syntax and the list of parameters specific to the navigation API to receive from the navigation service application, in response to providing each of a plurality of next step requests to the navigation service application, a next one in the sequence of steps for transmission to the head unit.

16. The portable device of claim 12, wherein invoking the navigation API includes using the syntax and the list of parameters specific to the navigation API to provide authentication information to the navigation service application.

17. A non-transitory computer-readable medium storing thereon a plurality of instructions that implement a navigation service application configured to, when installed on a portable device on which a companion application that executes separately from the navigation service application is also installed, execute a method comprising:

sending a destination to a navigation server via a long-range communication link;

receiving first navigation data from the navigation server via the long-range communication link, wherein the first navigation data describes at least one of a plurality of steps for navigating between a source and the destination; and

when the companion application invokes a navigation application programming interface (API) of the navigation service application using a syntax and a list of parameters specific to the navigation API, providing the first navigation data to the companion application,

wherein the companion application is configured to send the first navigation data to a head unit of a vehicle via a short-range communication link to cause the head unit to display navigation information indicating at least the one of the plurality of steps for navigating between the source and the destination.

18. The non-transitory computer-readable medium of claim 17, wherein the syntax and the list of parameters specific to the navigation API defines a set of one or more data structures for exchanging data between the navigation API and the companion application.

19. The non-transitory computer-readable medium of claim 17, wherein the first navigation data describes a sequence of steps, and wherein the companion application is configured to invoke the navigation API at least by using the syntax and the list of parameters specific to the navigation API to receive from the navigation service application, in response to providing each of a plurality of next step requests to the navigation service application, a next one in the sequence of steps for transmission to the head unit.

20. The non-transitory computer-readable medium of claim 17, wherein the companion application is configured to invoke the navigation API at least by using the syntax and the list of parameters specific to the navigation API to provide authentication information to the navigation service application.