System and method for providing navigation data to a vehicle

Through the navigation API, communication between the portable device and the vehicle main unit is solved, and the problem of difficulty and high cost of updating embedded navigation systems is realized, real-time update of navigation data and personalized services are realized.

CN113029184BActive Publication Date: 2024-11-26GOOGLE LLC
View PDF 20 Cites 0 Cited by

Patent Information

Application Number
CN202110178390.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2013-09-26
Filing Date
2014-09-25
Publication Date
2024-11-26
Estimated Expiration
2034-09-25

AI Technical Summary

Technical Problem

The existing embedded vehicle navigation system is difficult to update and is expensive to update, making it impossible to effectively utilize navigation data on portable devices.

Method used

By providing a navigation API, portable devices allow communication with the vehicle's main unit, receive and convert navigation data, real-time updates and personalized services of navigation data are realized.

Benefits of technology

It realizes efficient transmission of navigation data on portable devices and updates of vehicle navigation systems, reduces costs, and improves the real-time and personalized service capabilities of navigation data.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113029184B_ABST
    Figure CN113029184B_ABST
Patent Text Reader

Abstract

The present disclosure relates to systems and methods for providing navigation data to a vehicle. An instruction set implements an application programming interface (API) for providing navigation data from a portable device to a head unit of a vehicle. When called by a paired application executed on the portable device, the API is configured to obtain navigation data for navigating a user between a source point and a destination point, wherein the portable device receives the navigation data from a navigation server via a long-range communication link. The API is further configured to provide the navigation data to the paired application for transmission to the head unit via a short-range communication link.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Description of the case

[0002] This application is a divisional application of Chinese invention patent application No. 201480053510.3, filed on September 25, 2014. Technical Field

[0003] The present application relates generally to providing digital navigation data via a user interface and, more particularly, to providing navigation data to a head unit of a vehicle. Background Art

[0004] The background description provided herein is for the purpose of generally presenting the context of the present disclosure. The work of the presently named "inventor", to the extent described in this background section and aspects of the invention content that may not have been prior art at the time of filing the application, is neither explicitly nor implicitly identified as prior art to the present disclosure.

[0005] Today, many automobile manufacturers offer navigation systems embedded in the vehicle's head unit or "deck." These embedded vehicle navigation systems typically store a collection of static maps and perform path planning and navigation operations locally in the head unit. As maps and algorithms implemented in the navigation system become outdated, updates are often difficult to perform, even if supported. Although some embedded vehicle navigation systems now include a dedicated cellular link for accessing a network server, the link typically requires an expensive subscription.

[0006] In order to utilize applications running on smartphones and other portable devices, some automobile manufacturers now provide application programming interfaces (APIs) for accessing the audio and visual components of the vehicle's head unit. These APIs provide manufacturer-specific solutions for accessing the head unit. As a result, applications using these APIs are often developed for a unique make or model of vehicle. Summary of the invention

[0007] In general, an API allows an application running on a portable device to receive navigation data, which can include turn-by-turn directions, route overviews, audio instructions, map images, etc., from a navigation server via a wireless communication network. An application ("companion application") that calls the API can then provide the navigation data to the vehicle's head unit using any desired communication scheme, such as a communication scheme defined by the head unit manufacturer. In an example embodiment, the API communicates with a navigation server via a navigation service native to the portable device's operating system. The portable device and the head unit can communicate via a wired or wireless short-range communication link. The companion application can receive navigation data according to a predefined format exposed by the API and convert the navigation data into a format supported by the head unit. Thus, the manufacturer of the head unit or the manufacturer of the vehicle can use the API to develop a companion application that obtains navigation data and converts the data into a desired format. More generally, the companion application can call the API to support a wide variety of communication and processing schemes.

[0008] Using the technology of the present disclosure, an API allows a navigation service application executed on a portable device such as a smart phone to efficiently provide a digital map image to a second application (a "paired application") executed on the portable device, which calls the API. The paired application can then provide the digital map image to the main unit of the vehicle using any desired communication scheme, such as a communication scheme defined by the main unit manufacturer. The navigation service application can receive navigation data as a sequence of steps defining a route from a starting point to a destination and map data for presenting a digital map of a geographic area between the starting point and the destination. For example, the map data can be provided in the format of a vector map, and the navigation service application can interpret and present the map data to generate a bitmap. In order to preserve bandwidth and battery power, the navigation service application can present a map image as only illustrating the steps of the navigation route guidance, which are typically maneuvers for transferring between road segments (e.g., "turn right to the main road", "go straight for 2.4 miles"), without continuously providing updated digital map images to the main unit. More specifically, rather than re-rendering digital maps to reflect the vehicle's progress along the route in real time, the navigation service application can generate digital map images for only "interesting" portions of the route, such as intersections where the vehicle must maneuver to stay on the route. The navigation service application can generate these digital maps based on the orientation of the vehicle at each step, so that the vehicle can appear to always be facing the direction of travel on the digital map. The companion application can receive digital map images from the navigation service application according to a predefined format exposed with the API and convert the digital map images into a format supported by the head unit.

[0009] Further, an application ("pairing application") running on a portable device such as a smart phone that calls the API receives partial user input from the car's head unit, such as the address or first few letters of the name of a business. The pairing application receives the partial input from the head unit using any desired communication scheme, such as a communication scheme defined by the head unit manufacturer. For example, the portable device can receive the partial user input via a short-range communication link such as USB. The pairing application then calls the API to allow the pairing application to forward the partial user input received via the head unit to the navigation service. The navigation service then generates suggestion inputs locally or by requesting suggestions from a suggestion server via a long-range communication link such as a cellular link. The suggestions can include the names or addresses of one or more geographic locations consistent with the suggestion inputs. If desired, the suggestions can be personalized for the user of the portable device. The navigation service can provide these suggestions to the head unit in the form of a string of alphanumeric characters, an audio notification, etc. In some cases, the navigation service converts the suggestions into a format recognized by the head unit. In such an embodiment, the navigation service includes: (i) a navigation service application native to the operating system of the portable device and (ii) an API that a paired application can call to receive the suggestions, convert the suggestions into the format recognized by the main unit, and provide the suggestions to the main unit.

[0010] To allow a driver of a vehicle to safely invoke navigation functions on a portable device (e.g., a smartphone), an application ("pairing application") of the present disclosure that calls an API receives the driver's indication of which vehicle controls to activate and activates and executes navigation functions based on these indications and a mapping that can be established for an individual user of the portable device. The pairing application receives the indications from the head unit using any desired communication scheme, such as a communication scheme defined by the head unit manufacturer. The pairing application then calls the API to allow the pairing application to forward the indications received via the head unit to the navigation service. The driver can press a hardware, touch screen, or other button disposed on or connected to the head unit of the car, and the head unit can forward these events to the portable device. In an example scenario, the user first establishes a mapping between vehicle controls and navigation functions by invoking an interactive dialog on the portable device that activates various vehicle controls so that the head unit can report these activation events to the portable device and select the desired navigation function for each activation event. During navigation, the user can, for example, press a "volume up" key on the steering wheel, and after the head unit reports the key event to the portable device, the portable device can provide the next navigation instructions to the head unit. Because the buttons can be configured on the portable device using software, almost any vehicle can be easily configured and modified for use with the navigation software running on the portable device.

[0011] More particularly, an example implementation of the technology of the present disclosure is a computer-readable medium storing instructions executable on one or more processors. The instructions implement an API for providing navigation data from a portable device to a head unit installed in a vehicle. When called by a paired application executed on the portable device, the API is configured to obtain navigation data for navigating a user between a source point and a destination, wherein the portable device receives the navigation data from a navigation server via a first communication link. The API is further configured to provide the navigation data to the paired application for transmission to the head unit via a second communication link.

[0012] Another example implementation of these techniques is a computer-readable medium storing another set of instructions executable on one or more processors. The instructions implement another API for providing navigation data from a portable device to a main unit installed in a vehicle. When called by a paired application executed on the portable device, the API is configured to receive navigation data from a navigation application executed on the portable device independently of the paired application. The navigation service application receives the navigation data from a navigation server via a first communication link, and the paired application communicates with the main unit via a second communication link. The API is further configured to provide the navigation data to the paired application for transmission to the main unit.

[0013] Yet another example implementation of the technology of the present disclosure is a computer-implemented method for providing navigation data from a portable device to a head unit of a vehicle. The method includes providing instructions that implement a navigation service, the instructions being executed on the portable device to receive navigation data from a navigation server via a long-range communication link. The navigation data describes multiple steps for navigating between a source point and a destination. The method also includes providing instructions that implement a navigation API that a paired application calls to: (i) provide the destination selected via the head unit to the navigation service and (ii) receive the navigation data from the navigation server, wherein the paired application provides the navigation data to the head unit via a short-range communication link.

[0014] Another embodiment of these technologies is a non-transient computer-readable medium storing instructions for implementing a navigation service application. When executed by one or more processors, the instructions cause the one or more processors to receive navigation data for navigating a user between a source point and a destination via a long-range communication link. The received navigation data conforms to a first format. The instructions further cause the one or more processors to convert the navigation data into a second format defined only for communicating navigation data between the navigation service application and a main unit of a vehicle, and cause the navigation data in the second format to be transmitted to the main unit of the vehicle via a short-range communication link. The instructions for implementing the navigation service do not cause instructions dedicated to the main unit to be called to convert the navigation data or cause the navigation data to be transmitted.

[0015] Another embodiment of the techniques is a computer-implemented method for providing navigation data to a head unit installed in a vehicle. The method includes receiving, by one or more processors, an indication of a current position and a current orientation of the vehicle and receiving map data from a network device via a first link for generating a digital map of a geographic area including the current position. The method further includes generating, by the one or more processors, a digital map image using the map data, including orienting the digital map according to the current orientation, and providing, by the one or more processors, the digital map image to the head unit via a second communication link.

[0016] Another embodiment of the techniques is a portable device comprising one or more processors, a first network interface for communicating with a network device via a long-range communication link, a second network interface for communicating with a head unit of a vehicle via a short-range communication link, and a non-transitory computer-readable memory storing instructions that, when executed by the one or more processors, enable the portable device to determine a current location and a current orientation of the vehicle, receive map data via the long-range communication link for generating a digital map of a geographic area including the current location, generate a digital map image based on the determined vehicle orientation using the map data, and provide the digital map image to the head unit via the short-range communication link.

[0017] Yet another embodiment of these techniques is a method in a computing device for providing navigation data to a head unit of a vehicle, wherein the head unit includes a display device. The method includes receiving, by one or more processors, navigation data specifying a sequence of steps for traveling between a source point and a destination point, wherein each of the steps specifies a respective maneuver at a corresponding geographic location. The method also includes presenting, using the one or more processors, for each of the steps, a digital map image of a geographic area including the geographic location corresponding to the step to generate a sequence of digital map images. Further, the method includes providing, by the one or more processors, the sequence of digital map images to the head unit of the vehicle.

[0018] Yet another embodiment is an apparatus for providing navigation data to a head unit of a vehicle, wherein the head unit includes a display device. The apparatus for providing navigation data includes: (i) means for receiving navigation data specifying a sequence of steps for traveling between an origin and a destination, wherein each of the steps specifies a respective maneuver at a corresponding geographic location, (ii) means for presenting, for each of the steps, a digital map image of a geographic area including the geographic location corresponding to the step to generate a sequence of digital map images, and (iii) means for providing the sequence of digital map images to the head unit of the vehicle.

[0019] Another embodiment of the technology of the present disclosure is a method in a portable device for providing input suggestions for requesting navigation data via a head unit of a vehicle. The method includes receiving a portion of a user input provided to the head unit via a short-range communication link, such that the portion of the user input includes an alphanumeric character sequence. The method further includes generating, by one or more processors, a suggestion input corresponding to the portion of the user input, wherein the suggestion input includes the alphanumeric character sequence and one or more additional characters, and wherein the suggestion input corresponds to a set of one or more geographic locations. The method also includes providing, by the one or more processors, the suggestion input to the head unit via the short-range communication link.

[0020] Another embodiment of the disclosed technology is a portable device comprising one or more processors, a first network interface for communicating with a head unit of a vehicle via a first communication link, a second network interface for communicating with a suggestion server via a second communication link, and a non-transitory computer-readable medium storing instructions. When executed by the one or more processors, the instructions cause the portable device to: (i) receive a portion of a user input provided to the head unit via the first communication link, (ii) cause the portion of the user input to be transmitted to the suggestion server, (iii) generate a suggestion input based on the suggestion set, and (iv) cause the suggestion input to be transmitted to the head unit.

[0021] Yet another embodiment of the disclosed technology is a non-transitory computer-readable medium storing instructions that implement an application programming interface (API) for use by a software application executing on a portable device. The API, when called by the software application, is configured to: (i) receive a portion of user input from an external device operating independently of the portable device via a first communication link, (ii) provide the portion of user input to a suggestion server via a second communication link, (iii) receive suggestion input corresponding to a set of one or more geographic locations from the suggestion server, and (iv) provide the suggestion input to the external device.

[0022] More particularly, one embodiment of the disclosed technology is a method in a portable device for controlling a navigation service application executed on the portable device based on user input received via a head unit of a vehicle. The method is executed by one or more processors and includes: (i) receiving a mapping between controls of the head unit and functions of the navigation software application, (ii) receiving an indication via a communication link between the portable device and the head unit that one of the controls has been activated, (iii) selecting a function from among the functions of the navigation software application based on the received mapping and the received indication, and (iv) executing the selected function of the navigation software application.

[0023] Another embodiment of the technology disclosed herein is a portable device comprising one or more processors, a short-range network interface for communicating with a main unit of a vehicle via a short-range communication link, and a non-transitory computer-readable medium storing instructions executable by the one or more processors, wherein the main unit includes a plurality of controls. The instructions implement a navigation service application that supports a plurality of user-selectable functions. The instructions are also configured to: (i) receive an indication via the short-range network interface that one of the controls on the main unit has been activated, (ii) select a function from among the plurality of user-selectable functions based on the received indication, and (iii) execute the selected function.

[0024] Yet another embodiment of the disclosed technology is a non-transitory computer-readable medium storing instructions that, when executed by one or more processors of a portable device, are configured to: (i) receive a mapping between a plurality of controls on a head unit of a vehicle and a plurality of navigation functions supported by the portable device, (ii) receive an indication that one of the controls is activated on the head unit, (iii) select a navigation function from among the plurality of navigation functions based on the received mapping and the received indication, (iv) execute the navigation function, and (v) provide a result of executing the navigation function to the head unit. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 illustrates an example environment in which the techniques of the present disclosure can be used to transfer navigation data from a portable device to a head unit of a vehicle;

[0026] Figure 2 is able to Figure 1 A block diagram of an example portable device and an example main unit operating in a system of FIG.

[0027] Figure 3 yes Figure 1 A block diagram of an example communication system for operation of a portable device;

[0028] Figure 4 It is a graphic Figure 2 A message sequence chart illustrating an example information exchange between components shown in to provide navigation data to a master unit in response to user input provided via the master unit;

[0029] Figure 5 is a flow chart of an example method for receiving navigation data from a navigation server and providing the navigation data to a head unit of a vehicle, the method being capable of Figure 2 The API is implemented in

[0030] Figure 6 It is a graphic Figure 2 An example information exchange between the components shown in the figure provides a message sequence diagram of a digital map image in response to manipulation of the master unit;

[0031] Figure 7 are example images that can be displayed on the main unit using the techniques of this disclosure;

[0032] Figure 8 is a flow chart of an example method for generating a digital map image for a maneuver and providing the digital map image to a vehicle head unit of a vehicle, the method being capable of Figure 2 The API is implemented in

[0033] Fig. 9 It is a graphic Figure 2 A message sequence diagram of an example information exchange between components shown in to map the hardware controls of the head unit to navigation functions on the portable device;

[0034] Fig.10 It is a graphic Figure 2 A message sequence chart showing an example information exchange between components shown in to provide user input received via the head unit to a navigation application on a portable device;

[0035] Fig.11 is a flow chart of an example method for processing user input received via a vehicle's head unit in a navigation application for a portable device, the method being capable of Figure 2 to be implemented in portable devices;

[0036] Fig.12 It is a graphic Figure 2 A message sequence diagram of an exemplary information exchange between the components shown in to provide input suggestions to the master unit; and

[0037] Fig.13 is a flow chart of an example method for providing input suggestions for requesting navigation data via a head unit of a vehicle, the method being capable of Figure 2 can be implemented in portable devices. DETAILED DESCRIPTION

[0038] Overview

[0039] On the portable device, the navigation service exposes a navigation API to allow applications to receive navigation data from the navigation service. The application provides navigation data to the vehicle's main unit or another external output system using any desired communication scheme, such as a communication scheme defined by the manufacturer of the main unit. The navigation API can also allow the application to forward user input received via the main unit to the navigation service. Therefore, in a sense, the API provides a two-way interface between the application and the navigation service. Depending on the vehicle, the main unit can include relatively simple components for displaying alphanumeric characters and playing audio or relatively robust components for displaying digital images and even animations, receiving touch screen input, receiving and processing voice commands, etc. For example, a portable device that can be a smart phone can communicate with the main unit via a short-range communication link, such as a short-range communication link that supports the Bluetooth protocol.

[0040] As discussed in more detail below, the portable device in an example embodiment supports a navigation service application (or simply "navigation application") that communicates with a navigation server via a cellular network or another wireless communication network. The navigation service application can be native to the operating system of the portable device. Using the API, a programmer can develop a "paired" application that runs on the portable device and communicates with the navigation service on the one hand and communicates with the main unit using a communication scheme supported by the main unit on the other hand. As an alternative, the API can implement functionality for communicating directly with a navigation server. As another alternative, the API can communicate with a navigation service application that generates navigation data locally on the portable device without sending a request to the navigation server.

[0041] In any case, the car manufacturer can develop a companion application that communicates with the car's head unit using any desired communication scheme, including proprietary communication schemes not shared with other car manufacturers. In general, the navigation API of the present disclosure allows developers to easily and efficiently export navigation data from portable devices and retrofit existing vehicles for vehicles.

[0042] Depending on the implementation, the navigation API can include one or several functions, classes, etc. Further, the navigation API can use various data structures, message formats, constants, enumeration lists, etc., and the developer can then have appropriate definitions. Still further, the navigation API can provide a mechanism for specifying callback functions or otherwise configuring event reporting, messaging, etc. from the navigation service application to the paired application.

[0043] In an example scenario, the paired application receives user input from the main unit and calls the navigation API to provide the user input to the navigation service. For example, the user input can include the name or address of the destination. The navigation service application generates or receives from the navigation server a route that guides the driver from the current location to the destination. As an example, the route can include a sequence of steps, each step describing a road segment (e.g., the name or number of the road, the distance, the travel time, the speed limit) and the maneuver used to access the next road segment (e.g., turn left, merge right, go straight). For example, the paired application retrieves the route from the navigation service application via the navigation API, converts the navigation data into a format supported by the main unit, and provides the navigation data to the main unit via a single message or a sequence of messages.

[0044] In addition, the navigation API in some embodiments provides a sequence of digital map graphics to the main unit to illustrate the steps of the route and / or the progress of the vehicle. As discussed above, the navigation service application can receive a description of the route from the current to the specified end point of the portable device. When the portable device moves along the route to the end point, the navigation service application can request map data for the geographical area where the portable device is currently located. Using the map data, the portable device can present a digital map image and for each step, its illustration, such as the geographical area corresponding to the step, the manipulation for transitioning to the step, etc. Further, the inertial measurement unit (IMU) of the portable device and / or the vehicle can determine the current orientation of the vehicle and orient each digital map image to match the current orientation of the vehicle. Still further, the navigation API can also provide personalized digital map images (using the information received by the navigation service application from the personalization server). To further personalize the digital map image, the main unit can also specify the screen size, style selection, etc., so that the specific digital map matches the performance of the main unit and matches the design of the car as needed.

[0045] According to some embodiments, the paired application also maps vehicle controls such as hardware buttons on the main unit or on the steering wheel to navigation functions of the navigation service application. More specifically, the user can specify the mapping on the portable device so that the main unit can simply report the key events to the navigation service application. For example, the paired application can map the volume down button on the steering wheel to the next step navigation function for requesting the description of the next step in the route. When the user presses the volume down button on the steering wheel, the main unit transmits a message reporting the event to the paired application. The paired application then determines that the volume down button has been mapped to the next step function, calls the navigation API to call the function and receive the description of the next step, and provides the description of the next step to the main unit. Because the hardware buttons can be configured on the portable device using software, most buttons in many different types of vehicles and main units (even knobs or slider controls in some cases) can be simply configured to cooperate with the navigation API of the present disclosure.

[0046] Further, the navigation API in some embodiments supports an auto-complete feature that reduces the interaction time with the vehicle controls by generating geographic suggestions based on partial user input via the main unit. For example, when the driver begins typing a location using the touch screen of the main unit of the car, the portable device generates location suggestions and transmits the suggestions to the main unit for display. More specifically, the main unit reports partial user input (e.g., one or more key events) to a paired application, which calls the navigation API to provide the partial user input to the navigation service application, which in turn contacts the suggestion server. Once one or more suggestions arrive, the navigation service application provides the suggestions to the paired application for forwarding to the main unit. If the user configures the navigation service application to access the user's profile when providing suggestions, the suggestions can also be personalized. Thus, for example, when the driver enters the first letter of the destination (e.g., "M"), the main unit displays suggested locations that the user has recently visited that begin with that letter.

[0047] Example environment and system architecture

[0048] Reference Figure 1 , an example environment 1 capable of implementing the techniques outlined above includes a portable device 10 and a vehicle 12 having a main unit 14. The portable device 10 may be a smart phone, a tablet computer, a wearable computer, etc. The portable device 10 communicates with the main unit 14 of the vehicle 12 via a communication link 16, which may be wired (e.g., Universal Serial Bus (USB)) or wireless (e.g., Bluetooth, Wi-Fi Direct). The portable device 10 may also communicate with various content providers, servers, etc. via a wireless communication network such as a fourth or third generation cellular network (4G or 3G, respectively).

[0049] In operation, the portable device 10 provides navigation-related information to the main unit 14, which may include digital map images, text, and audio. The main unit 14 displays the information via a display 18. The display 18 in some embodiments is a touch screen and includes a software keyboard for entering text input, which may include the name or address of the destination, the starting point, etc. Another type of display 18 can be a relatively sophisticated screen, such as one equipped with a non-touch input device such as a rotary controller or a separate touch pad. In general, the display 18 does not need to be able to display both text and images. The main unit in another vehicle can include, for example, a simple display that can only display one or a few lines of alphanumeric characters.

[0050] The main unit 14 can include hardware input controls, such as buttons, knobs, etc. These controls can be located on the main unit 14 or elsewhere in the vehicle 12. For example, Figure 1 The vehicle 12 in the embodiment includes a navigation control 20 on the head unit 14 and a steering wheel control 22 communicatively coupled to the head unit 14. The controls 20 and 22 can be mapped to various navigation control functions on the portable device 10, as described in detail below. The controls 20 and 22 in some embodiments can also be used to enter alphanumeric characters.

[0051] The vehicle 12 can also include audio input and output components, such as, for example, a microphone 24 and a speaker 26. Similar to the hardware controls 20 and 22, the microphone 24 and the speaker 26 can be located directly on the head unit 14 or elsewhere in the vehicle 12.

[0052] Reference Figure 2 An example implementation of a portable device 10 and a main unit 14 is illustrated. As discussed above, the main unit 14 includes a display 18, hardware controls 20, 22, an audio input unit 24, and an audio output unit 26. The main unit 14 can also include a processor 25, one or more sensor sets 28, and one or more short-range communication units 30B.

[0053] The combination of sensors 28 can include, for example, a global positioning system (GPS) module for determining the current location of the vehicle in which the main unit 14 is installed, an inertial measurement unit (IMU) for measuring speed, acceleration, and current orientation of the vehicle, a barometer for determining the altitude of the vehicle, etc. Figure 2 The sensor set 28 is depicted as being internal to the main unit 14, but it should be noted that the sensors 28 need not be an integral component of the main unit 14. Rather, the vehicle can include any number of sensors in various locations, and the main unit 14 can receive data from these sensors during operation.

[0054] The short-range communication unit 30B allows the main unit 14 to communicate with the portable device 10. The short-range communication unit 30B may support wired or wireless communication, such as USB, Bluetooth, Wi-Fi Direct, Near Field Communication (NFC), and the like.

[0055] Depending on the implementation, the processor 25 can be a general purpose processor that executes instructions stored on a computer readable memory (not shown) or an application specific integrated circuit (ASIC) that implements the functions of the main unit 14. In any case, the processor 25 can be operable to format messages from the main unit 14 to the portable device 10, receive and process messages from the portable device 10, display a map image via the display 18, play audio messages via the audio output 26, etc.

[0056] Similarly, the portable device 10 can include a short-range communication unit 30A for communicating with the main unit 14. Similar to the unit 3B, the short-range communication unit 30A can support one or more communication schemes, such as USB, Bluetooth, Wi-Fi Direct, etc. The portable device 10 also includes one or more processors or CPUs 34, a GPS module 36, a memory 38, and a cellular communication unit 50 for transmitting and receiving data via a 3G cellular network, a 4G cellular network, or any other appropriate network. For example, the portable device 10 can also include additional components, such as a graphics processing unit (GPU). In general, the portable device 10 can include additional sensors (e.g., accelerometers, gyroscopes), or conversely, the portable device 10 can rely on sensor data provided by the main unit 14. In one embodiment, to improve the accuracy of real-time navigation, the portable device 10 relies on positioning data provided by the main unit 14 rather than the output of the GPS module 36.

[0057] The memory 38 can store, for example, contacts 40 and other personal data of the user. Figure 2 As shown in , the memory can also store instructions for an operating system 42, a paired application 44 that calls a navigation API 46 during operation, and a navigation service application 48. The software components 42, 44, and 48 can include assembly instructions and / or instructions in any suitable programming language that can be translated at runtime. In any case, the software components 42, 44, and 48 are executed on one or more processors 34.

[0058] In some embodiments of the portable device 10, the companion application 44 and the navigation service application 48 can be executed as separate processes or tasks. The applications 44 and 48 can communicate using an inter-process communication (IPC) scheme provided by the operating system 42. In one embodiment, the navigation service application 48 is provided as a service on the operating system 42 or otherwise as a native component. In another embodiment, the navigation service application 48 is an application that is compatible with the operating system 42 but is provided separately from the operating system 42, possibly by a different software provider.

[0059] Still further, in other embodiments of the portable device 10, the functionality of the navigation services application 48 can be provided as a static library of functions accessible via the navigation API 46. In other words, some or all of the functionality of the navigation services application 48 can be performed as part of the companion application 44. More generally, the navigation API 46 provides the companion application 44 with access to the navigation services of the portable device 10, using any suitable software architecture and communication scheme, including those currently known in the art.

[0060] The navigation API 46 can generally be provided in different versions for different operating systems. For example, the manufacturer of the portable device 10 can adopt a software development kit (SDK), including for Android TM Platform Navigation API 46, for iOS TM Platform SDK, etc.

[0061] As indicated above, a developer with knowledge of the messaging schemes supported by the head unit 14 or with sufficient access rights to the head unit 14 to extend its functionality is able to develop a companion application 44 and access the navigation services of the portable device 10 via the navigation API 46. In other words, the navigation services application 48 is able to provide navigation data to an external device (in this case, the head unit 14) without making any modifications to the functionality of the navigation services application 48 to match the requirements of the external device.

[0062] To further clarify, Figure 3 An example communication system is shown in which the portable device 10 is operable to obtain navigation data in response to a user request submitted via the head unit 14. Figure 3 The portable device 10 and the main unit 14 are illustrated in a simplified manner.

[0063] The portable device 10 has access to a wide area communications network 52, such as the Internet via a long-range wireless communications link (eg, a cellular link). Figure 2 , the portable device 10 is able to access the communication network 52 via the cellular communication unit 50. Figure 3In an example configuration, the portable device 10 has access to a navigation server 54 that provides navigation data and map data, a suggestion server 56 that generates suggestions based on portions of user input, and a personalization server 58 that provides personalized data based on the user's past interactions with the navigation server 54 and other factors.

[0064] In some embodiments, the pairing server 60 formats the navigation data for direct use by the head unit 12. In particular, the portable device 10 can establish a communication path for the navigation data between the head unit 14 and the pairing server 60 so that the pairing server 60 and / or the navigation server 54 can provide the navigation data directly to the head unit 14.

[0065] More generally, the portable device 10 can communicate with any number of suitable servers. Figure 3 In another embodiment of the communication network depicted in , the navigation server 54 provides route guidance and other navigation data, while a separate map server provides map data (e.g., in a vector graphics format), traffic data provides road condition updates along the route, and a weather data server provides weather data and / or alerts, etc.

[0066] Provides navigation data to the vehicle's head unit

[0067] According to an example scenario, a driver requests navigation information by pressing an appropriate button on the head unit of the user's vehicle and entering a destination. The head unit provides the request to a portable device, which in turn requests and receives navigation data from a navigation server. The portable device then provides the navigation data to the head unit for display and / or audio playback.

[0068] To further clarify, Figure 4 A message sequence diagram (400) depicting the scenario is shown in FIG. Each vertical line schematically represents the timeline of the corresponding component, with the time plotted at the lower part of the page occurring after the event plotted at the upper part of the page. The flow of information between components is represented by arrows. Arrows in different situations can represent messages propagating between different physical devices, messages propagating between tasks running on the same device, function calls from one software layer to another, callback functions called in response to triggering events, etc. Furthermore, a single arrow in some cases can represent a sequence of function calls and / or messages.

[0069] The user submits input (402) to the main unit 14 including a destination (D), such as "233 South Wacker Dr." The user can also specify an origin (O), or the main unit 14 can automatically associate the current location with the origin. Depending on the hardware and software available in the main unit 14, the user can submit the input 402 using buttons, knobs, voice, touch screen, etc. The main unit 14 processes the user input and transmits a navigation request event 404 to the paired application 44 running on the portable device 12. If desired, the navigation request event 404 can be a message conforming to a proprietary communication protocol dedicated to communication between the main unit 14 and devices external to the main unit 14. Review Figure 1 and 2 , the head unit 14 is able to transmit the navigation request event 404 via the short-range communication link 16 .

[0070] The companion application 44 receives the navigation request event 404 and calls the navigation API 46. More specifically, the navigation request event 404 generates a navigation request 405 according to the format of the API 46. As part of generating the navigation request 405, the companion application 44 can call a function for specifying an end point, a function for specifying a preferred manner of reporting navigation events (e.g., upcoming turns, en route progress confirmations), a function for configuring the use of sensors (e.g., using GPS readings from the head unit 14 or portable device 10, using readings from the IMU of the vehicle 12), etc. Each of these functions can have a syntax and a list of parameters specific to the navigation API 46. Additionally or alternatively, for calling functions with API-specific prototypes, the companion application 44 can populate data structures exposed by the navigation 46.

[0071] In a sense, the companion application 44 translates a request to direct a user to a certain destination from the format of the head unit 14 into the format of the navigation API 46 and more generally into a format usable by the navigation service on the portable device 10. The navigation service thereby does not need to support multiple protocols for communicating with the head units of various automobile manufacturers.

[0072] Before forwarding the request from the paired application 44 to the navigation service application 48, the navigation API 46 in some embodiments performs authentication of the paired application 44. More specifically, the navigation API 46 determines whether the paired application 44 is authenticated to request navigation data from the navigation service of the portable device 10. For example, the navigation API 46 can receive an authentication key and request that the paired application 44 be authenticated by the authentication server (at Figure 1-3 ) to verify the authentication key.

[0073] Next, the navigation API 46 notifies the navigation service application 48 of the request via a navigation request message 406. To this end, any suitable IPC scheme can be used (or, if components 46 and 48 operate within the same task, an in-process communication scheme or any suitable notification mechanism).

[0074] The navigation service application 48 then formats the navigation request 408 and sends it via a long-range wireless communication link and ultimately via a reference such as Figure 3 The wireless communication network of the network 52 in question is transmitted to the navigation server 54. In general, the navigation request 408 can be similar to the request that the navigation service application 48 transmits to the navigation server 54 when the user directly invokes the navigation function via the portable device 10. In other words, the portable device 10 and the main unit 14 in some embodiments can be presented to the navigation server 54 as a single node. In some embodiments, the navigation request 408 conforms to a proprietary protocol defined by the operator of the navigation server 54 (so as to more efficiently form communications between the navigation server 54 and the client device and reduce the probability of unauthorized access).

[0075] In response to the navigation request 408, the navigation server 54 provides route guidance 410. Figure 4 In the example of FIG. 4 , the route guidance 410 includes a description of a series of N steps S1, S2, ..., S N The description of each step can indicate the road segment and the maneuver used to transition to the next road segment. The route guidance 410 can also include an estimated time of arrival, the time and / or distance to the destination, the time and / or distance to the next road segment (for each step), a description of current traffic conditions, etc. The navigation server 54 transmits the route guidance 410 to the navigation service application 48 via a remote communication link in the form of a message or a sequence of messages. For ease of illustration, Figure 4 Route directions 410 are depicted as being transmitted as a single message to the navigation application 48 only at the beginning of the navigation session. However, navigation service 48 and navigation server 54 according to other embodiments can exchange additional information, such as route updates and corrections, later during the navigation session as portable device 10 progresses toward a destination.

[0076] Continue to refer to Figure 4 , the navigation service application 48 receives the route guidance 410 and provides the first step S1 to the companion application 44 in the form of a message 412, which may be a callback function previously set by the companion application 44, for example. The navigation service application 48 is typically capable of forwarding data to the companion application via the navigation API 46.

[0077] In a typical scenario, the message 412 includes text consisting of alphanumeric characters. However, in some cases the navigation service application 48 can generate an audio notification based on the description of the steps and provide the audio notification to the companion application 44 in a digital format (e.g., MAV, MP3). Alternatively, the conversion from text to audio can be implemented in the companion application 44. Further, the description of the steps of the navigation route guidance can include a digital map image, as shown below. Figure 6-8 Let’s discuss this in more detail.

[0078] In any case, the paired application 44 converts the received description of the first step S1 into a format supported by the head unit 14 and transmits the navigation data message 415A to the head unit via the short-range communication link. The head unit 14 can provide the first information to the driver in any suitable manner (e.g., display, audio playback).

[0079] exist Figure 4 4. The driver in the example scenario of FIG. 4 presses a key on the steering wheel (or activates another control) to request a description of the next step in route guidance. After the master input detects the data event 416, the master unit 14 transmits a next step trigger notification 418 to the paired application 44, which in turn calls the navigation API 46 to submit a request 419 for the next step. The navigation API 46 transmits the next step request message 410 to the navigation service application 48. Similar to the description 412 discussed above, the navigation application 48 provides the description of the next step (422) to the paired application 44 for format conversion and forwarding to the master unit 14 in the form of a navigation data message 415B. For example, the scenario can continue in this manner until the user reaches the end point or cancels the navigation session.

[0080] In another embodiment, the head unit 14 automatically generates the next step trigger message 418 after analyzing the current position of the vehicle 12. In another embodiment, the navigation application 48 automatically generates the description 422 of the next step in response to detecting that the portable device 10 is close to the driver's necessary maneuver to stay on the route. In yet another embodiment, the navigation application 48 immediately provides all the steps of the route guidance to the head unit 14 after receiving the route guidance 410 from the navigation server 54, provided that the head unit 14 is capable of storing the entire sequence of steps.

[0081] Now refer to Figure 5 , the example method 500 implements some of the functionality of a navigation API (eg, navigation API 46). For example, the method 500 can be a set of instructions stored on a computer-readable memory and executable on one or more processors of the portable device 10.

[0082] The method begins at box 502, where an identifier of a destination is received from a paired application. For example, the identifier can include a full address (e.g., "233 South Wacker Drive, Chicago, IL, USA") or a geospatial search term (e.g., "Sears Tower in Chicago"). Next, at box 504, the identifier of the destination is provided to a software component via which a navigation service of the portable device can be accessed. For example, the identifier can be provided to the navigation service application 48 discussed above.

[0083] At block 506, navigation data is received from the navigation service application 48 or otherwise originates from the navigation service of the portable device. At block 508, the navigation data is provided to the companion application for transmission to the head unit 14 via the short range communication link. After block 508, the method is complete.

[0084] In some embodiments, the navigation service application communicates directly with the main unit without using a paired application. More specifically, the navigation service application and the main unit can exchange messages that conform to a data format defined specifically for communicating navigation data and related information between the main unit of the navigation service application vehicle. The data format can be an open format shared with several vehicle manufacturers. Since it is not necessary to transmit navigation data to the main unit in a format dedicated to the main unit or vehicle, the navigation service application can simply convert the navigation data into messages that conform to an open format and transmit these messages via a short-range communication link. The navigation service application in this case does not have to execute instructions dedicated to the main unit (e.g., calling an API provided by the manufacturer of the vehicle and / or the main unit). In addition, except for optional personalization, the navigation service application does not have to understand any specific parameters of the main unit to transmit navigation data to the main unit. The navigation service application can be native to the operating system of the portable device.

[0085] Providing digital map images to the vehicle's head unit

[0086] As discussed above, the navigation service application 48 receives the requested route guidance as a series of steps describing the route. Each step includes one or more maneuvers (e.g., "turn left on Main Street," "continue through the intersection," "enter Route 66"). In some embodiments, the main unit 14 also receives a digital map image for the maneuvers. The digital map image can be oriented to match the current orientation of the vehicle so that the top of the map corresponds to the direction the vehicle is currently facing rather than true north. Further, the digital map image can be personalized to include one or more locations associated with the user's account, such as a business or another point of interest (PO) that the user has previously visited. Still further, the digital map image can be personalized to match the style of the main unit.

[0087] As an alternative to these techniques, the portable device 10 can continuously export images to the main unit 14 as the digital map is re-rendered according to the new position of the portable device 10. In other words, the graphical content presented on the portable device 10 can be "mirrored" to the portable device 10. However, the mirroring method requires a large amount of bandwidth, rapidly drains the battery on the portable device 10, and requires the main unit 14 to be able to display a rapid succession of images.

[0088] according to Figure 6 In the example scenario 600, when the user activates a control to indicate that she wants to see and / or hear instructions for the next step of the route, an input event 602 is generated. For example, input 602 can correspond to input event 416, and Figure 6 The technique shown in Figure 4 to achieve it in the context of.

[0089] In response to the input event 602, the head unit 14 transmits a next step trigger event (604) to the companion application 44 via the short-range communication link. The companion application 44 then calls the navigation API 46, which may include converting the next step trigger event 604 into a data structure and / or function call recognized by the navigation API 46. The navigation API 46 notifies the navigation application 48 via a next step request message 606.

[0090] In this example scenario, a description of the next step is provided to the pairing application 44 (see Figure 4 4), the navigation services application 48 makes a query (personalization request 608) to the personalization server 58 regarding the user's preferences, receives personalization data 610 in response, and generates a digital map image for manipulation for display via the head unit 14. Generally speaking, the navigation services application 48 does not have to contact the personalization server, and the navigation services application 48 in some embodiments generates a digital map image without personalization.

[0091] When generating digital map graphics, for example, the navigation service application 48 can operate on a set of map elements defined in a vector graphics format. In general, a vector graphics format is a mathematical description based on geometric shapes. The navigation service application 48 can receive map data specifying various map elements for various geographic areas, such as roads, buildings, water bodies, parks, etc. The map data can also include alphanumeric labels and, in some cases, rasterized images (i.e., images defined in a bitmap format). The navigation service application 48 can interpret the vector-based definitions of map elements to generate a raster image in a standard format (e.g., JPEG) in a desired orientation.

[0092] The personalized data 610 can include information such as an indication of which places along the route should be displayed more prominently to the user (e.g., coffee shops), an indication of which places the user has visited previously, an indication of the user's familiarity with a portion of the route (e.g., so as to provide less route guidance for frequently visited portions of the route and more route guidance for portions of the route with which the user is not as familiar), etc. The navigation service application 48 can generate a digital map image in view of the personalized data 610.

[0093] Still further, given the parameters of the head unit 602, the navigation service application 48 can adjust the visual attributes of the map image, such as the color scheme, line thickness, fonts used in labels, etc. Thus, the companion application 44 can call upon the functionality of the navigation API 46 to specify the size, resolution, preferred color scheme, etc. of the screen available at the head unit 14. In this manner, the companion application 44 can configure the navigation application 48 to generate a map image that matches the overall style of the vehicle interior.

[0094] As also noted above, the navigation service application 48 can generate each map image with an orientation that matches the direction the vehicle is currently facing. In one example embodiment, the companion application 44 receives an indication of the current orientation from the head unit 14 and provides the indication to the navigation service application 48 via the navigation API 46. Alternatively, the navigation service application 48 and / or the navigation API 46 can use sensors in the portable device 10. The map images generated by the navigation service application 48 for display via the head unit 14 can be in any suitable format, such as BMP, JPEG, etc.

[0095] The navigation service application 48 provides the next step data along with the map image to the companion application 55 (message 612 of next step with map image), which in turn provides the data to the head unit 14 (message 614 of navigation data with map data).

[0096] Transfer to Figure 7, illustrates an example viewport 700 on the display of the main unit 14. The viewport 700 displays a digital map 702, a step description area 704, and a detailed digital map area 706. The main unit 14 can use the above reference Figure 6 The requests and received data are discussed to generate viewport 700.

[0097] like Figure 7 As shown in FIG. 7 , a digital map 702 is augmented with one or more locations associated with a user account, such as restaurants frequented by the user, etc. Including familiar landmarks in a digital map generally allows a user to better visualize and understand maneuvers presented on a detailed digital map.

[0098] For clarification, see Figure 8 An example method 800 for providing navigation data with a digital map image to a head unit of a vehicle is discussed. The method 800 can be implemented as a computer-executable set of instructions stored in a computer-readable memory and executed on one or more processors. As an example, the method 800 can be implemented in the navigation API 46, but in general, the method 800 can be implemented in a portable device or any suitable computing device.

[0099] The method begins at box 802, where navigation data for a specified operation is received from a navigation server. Next, at box 804, an indication of the current location of the vehicle 12 is received. In some embodiments, the orientation of the vehicle 12 is also received at box 804. At box 806, a digital map is generated for a geographic area including the location where the maneuver occurs. The digital map image can be oriented according to the current orientation of the vehicle 12, and as discussed above, the digital map image can be personalized in some cases. At box 808, the digital map is provided to the head unit 14 of the vehicle 12 via a communication link. The method is completed after box 810.

[0100] Configure and map vehicle controls

[0101] In some cases, the navigation service on the portable device 10 can be used to map existing vehicle controls in the vehicle 12, such as navigation buttons and steering wheel buttons, to the navigation functions of the navigation service application 48. The user configures the mapping on the portable device 10 so that the main unit 14 can simply report the key events to the navigation service application 48. For example, many vehicles have buttons on the steering wheel, radio, main unit 14, etc. for increasing the volume, decreasing the volume, next track, previous track, etc. The paired application 44 can support configuration features that enable users to map vehicle controls to various navigation functions. Once the mapping is completed, the navigation service application 48 performs various actions in response to the user activating the vehicle control, such as providing the next step in the route, returning to the previous step in the route, etc. Because the buttons can be configured on the portable device 10 using software, the main unit 14 can be easily configured or even modified.

[0102] Fig. 9 It is a graphic Figure 2 900 is a message sequence diagram illustrating an example information exchange between components to map hardware controls of the head unit 14 to navigation functions on the portable device 10.

[0103] When the user activates a button such as the navigation button 20 and / or the steering wheel button 22 (see Figure 1 ), the paired application 46 receives a control activation event 902. For example, the control activation event 902 can indicate that the user pressed a "next track" button on the steering wheel. At the same time, the paired application 46 can present a user interface screen on the portable device 10, through which the user can select various navigation functions and specify mappings. The user selects a navigation function (e.g., next step) via the paired application 46. Optionally, the paired application 46 obtains parameters and other information about the navigation function via the navigation API 48 ( Fig. 9 Message 904).

[0104] Once the companion application 46 receives both the indication of which vehicle control has been activated and the indication of which navigation has been selected, the companion application 46 creates a mapping between the vehicle control and the navigation function (action 906) and saves the mapping in the persistent memory of the portable device 10 (action 908). In a similar manner, the companion application 46 can receive mappings for multiple navigation functions and multiple vehicle controls. If desired, more than one vehicle control can be mapped to the same navigation function.

[0105] Next, Fig.10 Message sequence diagram 1000 diagram Figure 2 2 and 3. Example information exchanges between components shown in FIG. 4 are provided to provide user input received via the head unit 14 to the navigation service application 48.

[0106] like Fig.10 As shown in FIG. 1 , a user activates a vehicle control (1002), such as a "next track" button on a steering wheel that is mapped to a "next step" navigation function. The head unit 20 reports the key press event in a control activation event (1004) via the short-range communication link. The paired application 44 receives the control activation event 1004, identifies the navigation function using the previously saved configuration information, and invokes the identified navigation function (navigation function selection 10005) via the navigation API 46. Continuing with the above example, the paired application 44 identifies and invokes the "next step" navigation function.

[0107] Continue to refer to Fig.10 , the navigation API 46 forwards the selection to the navigation service application 48 (Event 1006), which performs the function (Event 1008) and provides the result of performing the selected navigation function to the companion application 44 (Event 1010) to be forwarded to the head unit 20 (Event 1012).

[0108] Thus, the vehicle controls are mapped to navigation functions using the configuration functionality of the companion application. In some embodiments, the companion application 44 automatically maps one or more vehicle controls to navigation functions of the portable device 10 according to a predetermined set of rules. For example, the companion application can automatically map a "volume up" or "next track" steering wheel button to a navigation function that presents the next step in a route, a "volume down" or "previous track" steering wheel button to a navigation function that presents the previous step, and so on.

[0109] As another alternative, the mapping between vehicle controls and navigation functions can be implemented and stored in the router of the head unit 14. To do this, the head unit 14 can request the navigation service application 48 to list the available navigation functions via the paired application 44 (which in turn calls the navigation API 46). Alternatively, the head unit 14 can simply assume the availability of certain functions on the portable device 10. According to this embodiment, the head unit 14 reports the selection of the navigation function to the paired application 44, rather than the "raw" key event.

[0110] For clarification, see Fig.11 An example method is discussed for processing an indication of user input from an external input device installed in the vehicle 12. The method can be implemented as a set of computer-executable instructions executable on one or more processors of the portable device 10 and stored in a computer-readable memory, for example.

[0111] The method begins at frame 1102, where a mapping between a set of controls on an external input device and a plurality of navigation functions of a navigation service is received. Next, at frame 1104, an indication that one of these controls has been activated is received. At frame 1106, an appropriate navigation function is selected from the set of navigation functions based on the received mapping and the received indication. At frame 1108, the selected navigation function is called. In at least some embodiments, the output of the navigation function is provided to the external input device. The method is completed after frame 1108.

[0112] Using a suggestion server to handle partial user input

[0113] In some embodiments, the navigation service of the portable device 10 also supports an "autocomplete" feature to provide suggestions based on user input that is only partially completed. This feature reduces the time that the user must interact with the vehicle controls while driving. Thus, for example, when the user initiates an input corresponding to the first letter of the destination (e.g., "M"), the main unit 14 displays or notifies a suggested location starting with that letter. The autocomplete function also allows the main unit 14 to utilize the remote communication capabilities of the portable device 10 and the user account associated with the portable device 10. In this way, without requiring the main unit 14 to have a subscription to a remote wireless service or the main unit 14 to save various user accounts, the suggestions can be personalized for the user. Therefore, the user can rent a car, borrow a car from a friend, etc. and still obtain personalized navigation data, personalized map images, and personalized suggestions.

[0114] Fig.12 It is a graphic Figure 2 1200 to provide input suggestions to the main unit 14. Depending on the scenario, the main unit 14 receives a partial input (event 1201), which may include as little as one letter or multiple letters depending on the scenario. In some embodiments of the main unit 14, software executing on the main unit 14 presents a dialog to request an endpoint via a display or to request user input via an audio component.

[0115] The head unit 14 transmits the partial input event 1202 to the companion application 44 via the short-range communication link. The companion application 44 then calls the navigation API 46 to structure the partial input so as to conform to a format supported by the navigation service application 48. The navigation API 46 then transmits the partial input message 1204 to the navigation application 48, which in turn transmits a suggestion request 1206 to the suggestion server 56 via the long-range communication link. Once the suggestion server 56 responds with one or several suggestions 1208, the navigation application 48 provides the suggestion to the companion application 44 (suggestion event 1209), and the companion application transmits the suggestion to the head unit 14 (suggested text message 1210). In particular, the companion application 44 can convert the received suggestion into a format supported by the head unit 14. The format can specify text, audio, etc.

[0116] In some embodiments, the navigation application 48 and / or suggestion server 56 personalizes the suggestions based on the user account and / or the location history of the portable device 10 .

[0117] This process continues and / or repeats as the main unit 14 continues to receive input. For example, the main unit 14 can transmit the first partial input (the first letter of the destination) to the pairing application 44, the second partial input (the first two letters of the destination) to the pairing application 44, and so on until the destination has been determined or fully input by the user.

[0118] In some embodiments, the portable device 10 has a sufficient cache of suggestions stored in the memory 38 and the automatic suggestion function is used when the portable device 10 cannot communicate with the suggestion server 56. The navigation service application 48 in this case receives the partial input and generates suggestion output based on the suggestions stored in the cache.

[0119] Still further, in some embodiments, the navigation application 48 generates the suggestion before any input is received by the head unit 14. For example, an account associated with the portable device 10 can include a location history indicating that the user typically drives home when the vehicle 12 is at Sydney Airport. Thus, the navigation application 48 can suggest the user's home location in response to the user initiating a navigation function via the head unit 14.

[0120] For clarification, see Fig.13 An example method for providing input suggestions via the main unit 14 is discussed. The method can be implemented as a set of computer-executable instructions and stored in a computer-readable memory. In an example embodiment, Fig.13 The method is implemented in Navigation API 46. More generally, Fig.13 The method can be implemented in a portable device or in any suitable computing device.

[0121] The method begins at block 1302, where a portion of the user input is received from the main unit 14 via a first communication link. Next, at block 1304, the portion of the user input is provided to a suggestion server via a second communication link. At block 1306, a suggestion input corresponding to the portion of the user input is received from the suggestion server via the second communication link. At block 1308, the suggestion input is provided to the main unit 14 via the first communication link. The method is complete after block 1308.

[0122] Additional considerations

[0123] The following additional considerations apply to the foregoing discussion. In this specification, multiple instances may implement components, operations or structures described as single instances. Although the individual operations in one or more methods are illustrated and described as separate operations, one or more of the individual operations may be performed simultaneously, and the operations are not required to be performed in the order shown. The structures and functions presented as separate components in the example configuration may be implemented as combined structures or components. Similarly, the structures and functions presented as single components may be implemented as separate components. These and other variations, modifications, additions and improvements fall within the scope of the subject matter of the present disclosure.

[0124] In addition, some embodiments are described herein as including logical or several components, modules or mechanisms. A module may constitute a software module (e.g., a code stored on a computer-readable medium) or a hardware module. A hardware module is a tangible unit that can perform certain operations and can be configured or arranged in a certain manner. In an example embodiment, one or more computer systems (e.g., independent client or server computer systems) or one or more hardware modules of a computer system (e.g., a processor or a processor group) may be configured by software (e.g., an application or an application portion) as a hardware module that operates to perform certain operations as described herein.

[0125] A hardware module may include dedicated circuitry or logic that is permanently configured to perform certain operations (e.g., a dedicated processor such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC)). A hardware module may also include programmable logic or circuitry (e.g., contained within a general purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. It should be appreciated that the decision to implement a hardware module in dedicated and permanently configured circuitry or in temporarily configured circuitry may be influenced by cost and time considerations.

[0126] Therefore, the term hardware should be understood to include tangible entities, which are entities that are physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or perform certain operations described herein. Considering embodiments in which hardware modules are temporarily configured (e.g., programmed), each of the hardware modules need not be configured or instantiated at any time stage. For example, in the case where the hardware modules include a general-purpose processor configured using software, the general-purpose processor can be configured as different hardware modules at different times. The software can configure the processor accordingly, for example, to constitute a specific hardware module at one time stage and to constitute different hardware modules at different time stages.

[0127] Hardware and software modules can provide information to other hardware and / or software modules and receive information from them. Therefore, the hardware modules can be considered to be coupled in a communication mode. In the case of multiple coexistence in such hardware or software modules, the communication connecting the software or hardware modules can be achieved by signal transmission (for example, by appropriate circuits and buses). In the embodiment where multiple hardware modules or software are configured or instantiated at different times, the communication between such hardware or software modules can be achieved, for example, by storing and retrieving information in a storage structure accessible to multiple hardware or software modules. For example, a hardware or software module can perform an operation and store the output of the operation in a storage device coupled in a communication mode with it. Another hardware or software module can then access a storage device at a later time to retrieve and process the stored output. Hardware and software modules can also initiate communication with input or output devices, and can operate resources (for example, the collection of information).

[0128] The various operations of the example methods described herein may be performed at least in part by one or more processors, which are temporarily configured (e.g., by software) or permanently configured to perform related operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented modules that operate to perform one or more operations or functions. The modules referred to herein may include processor-implemented modules in some example embodiments.

[0129] Similarly, the methods or routines described herein may be implemented at least in part by a processor. For example, at least some of the operations of the method may be performed by one or more processors or a hardware module implemented by the processor. The execution of certain operations may be assigned to one or more processors that are not only located in a single machine but also arranged on several machines. In some example embodiments, a processor or multiple processors may be located in a single location (e.g., in a home environment, an office environment, or as a server cluster), and in other embodiments, multiple processors may be distributed in several locations.

[0130] The one or more processors may also be operable to support execution of the related operations in a "cloud computing" environment or as SaaS. For example, as noted above, at least some of the operations may be performed by a computer group (as an example of a machine including a processor), which may be accessed via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., APIs).

[0131] The execution of certain operations may be assigned to one or more processors that reside not only in a single machine but also on multiple machines. In some example embodiments, one or more processors or processor-implemented modules may be located in a single geographic location (e.g., in a home environment, in an office environment, or in a server farm). In other example embodiments, one or more processors or processor-implemented modules may be distributed across multiple geographic locations.

[0132] Some parts of this specification are based on algorithms or symbolic representations of operations on data stored in machine memory (e.g., computer memory) as bits or binary digital signals. These algorithms or symbolic representations are examples of techniques used by those skilled in the art of data processing to communicate their work content to other technicians in the field. As used herein, an "algorithm" or "routine" is a self-consistent sequence of operations or similar processing that results in an expected result. In this regard, algorithms, routines, and operations involve physical manipulation of physical quantities. Typically, but not necessarily, such quantities can take the form of electronic, electromagnetic, or optical signals that can be stored, accessed, transferred, combined, compared, or otherwise manipulated by a machine. Often for convenience, mainly for public reasons, such signals are referred to using words such as "data", "content", "bit", "value", "element", "symbol", "character", "item", "number", "digit", etc. However, these words are only for ease of annotation and will be associated with appropriate physical quantities.

[0133] Unless otherwise specifically noted, discussions herein using words such as "process," "compute," "calculate," "determine," "present," "display," etc. may refer to the actions or procedures of a machine (e.g., a computer) that operates on or transforms data represented as physical (e.g., electronic, electromagnetic, or optical) quantities within one or more memories (e.g., volatile memory, non-volatile memory, or a combination thereof), registers, or other machine components that receive, store, transmit, or display information.

[0134] As used herein, any reference to "one embodiment" or "an embodiment" means that a particular element, feature, structure, or characteristic described in conjunction with the embodiment is included in at least one embodiment. The phrase "in one embodiment" appearing in various places in this specification does not necessarily all refer to the same embodiment.

[0135] Some embodiments may be described using the expressions "coupled" and "connected," along with their derivatives. For example, some embodiments may be described using the term "coupled" to indicate that two or more elements are in direct physical or electrical contact. However, the term "coupled" may also mean that two or more elements are not in direct contact with each other, but still cooperate or interact with each other. Embodiments are not limited in this respect.

[0136] As used herein, the terms "include," "have," or any other variation thereof are intended to cover non-exclusive inclusion. For example, a program, method, article, or apparatus that includes a list of elements is not necessarily limited to only those elements, but may include other elements not expressly listed or inherent to such program, method, article, or apparatus. Furthermore, unless expressly stated otherwise, "or" means inclusive rather than exclusive. For example, any of the following satisfies condition A or B: A is true (or exists) and B is false (or does not exist); A is false (or does not exist) and B is true (or exists); and both A and B are true (or exist).

[0137] In addition, the use of "a" and "an" is used to describe elements and components of the embodiments described herein. This is done only for convenience and to give a general meaning to the description. The description should be interpreted to include one or at least one, and the singular also includes the plural unless it is obvious that there is another meaning.

[0138] After reading this disclosure, those skilled in the art will appreciate the structural and functional designs of alternatives to the navigation API through the principles disclosed herein. Therefore, although specific embodiments and applications have been illustrated and described, it should be understood that the disclosed embodiments are not limited to the explicit configurations and components disclosed herein. Various modifications, changes and variations that are obvious to those skilled in the art may be made in the arrangement, operation and details of the methods and devices disclosed herein without departing from the spirit and scope defined in the appended claims.

Claims

1. A method for controlling a navigation service application via a head unit of a vehicle, the method comprising: Creating mappings between a plurality of controls of a main unit and a plurality of functions of a navigation service application executed on the portable device using a companion application executed by one or more processors on the portable device to utilize the plurality of controls on the main unit as external input devices of the portable device, wherein the companion application and the navigation service application are executed as separate tasks on an operating system of the portable device, comprising: receiving, at the paired application via a communication link between the portable device and the main unit, a corresponding control activation event for each of a plurality of controls activated at the main unit, and receiving, at the pairing application via a user interface of the portable device, a selection of a respective function of each of the plurality of controls; After creating the mapping, receiving, by the pairing application via the communication link between the portable device and the main unit, an indication that one of the plurality of controls has been activated; Selecting, by the companion application, a function from among the plurality of functions of the navigation service application according to the created mapping and the received indication, comprises: transmitting an indication of the selected function from the companion application to the navigation service application; and The selected function of the navigation service application is executed by the navigation service application.

2. The method according to claim 1, further comprising: obtaining, by the one or more processors, navigation data specifying a sequence of instructions for traveling between a source point and a destination point, wherein each of the instructions describes a respective maneuver at a corresponding geographic location; and Wherein executing the selected function comprises providing a next instruction in the sequence of instructions.

3. The method according to claim 2, wherein: Receiving the indication that one of the plurality of controls has been activated includes receiving an indication that a next track button has been activated, wherein providing the next instruction is in response to receiving the indication that the next track button has been activated.

4. The method according to claim 2, wherein: Providing the next instruction includes transmitting the next instruction to the master unit via the communication link.

5. The method according to claim 2, wherein: The communication link between the portable device and the main unit is a short range communication link, and wherein obtaining the navigation data comprises receiving the navigation data from a navigation server via a long range communication link.

6. The method of claim 1 , wherein creating the mapping comprises: For each of the control start events received for the corresponding control, generating a corresponding data record to indicate the correspondence between the control and the selected function; as well as Each data record is stored in a memory of the portable device.

7. The method according to claim 1, wherein: The plurality of functions of the navigation service application include one or more of: (i) starting navigation, (ii) canceling navigation, (iii) providing a next instruction, and (iv) providing a previous instruction.

8. A portable device comprising: one or more processors; User interface; a short-range network interface for communicating with a main unit of the vehicle via a short-range communication link, wherein the main unit includes a plurality of controls; A non-transitory computer-readable medium storing thereon: (i) first instructions implementing a navigation service application executable on the one or more processors, wherein the navigation service application supports a plurality of user-selectable functions, and (iii) second instructions implementing a companion application, wherein the companion application is executed on the one or more processors as a task separate from the navigation service application, wherein the companion application is configured to: receiving, via the short-range network interface, a control activation event indicating a control activated at the main unit, and receiving, via the user interface, a selection of a corresponding function of the navigation service application to create a mapping between the control and the function; After creating the mapping, receiving, via the short range network interface, an indication that one of the plurality of controls on the main unit has been activated; selecting a function from among the plurality of user-selectable functions based on the received indication in accordance with the mapping; and communicating an indication of the selected function to the navigation service application; The navigation service application is configured to execute the selected function in response to the instruction.

9. The portable device according to claim 8, further comprising: a remote network interface for communicating with a navigation server via a remote communication link; wherein the navigation service application, when executed on the one or more processors, causes the portable device to receive, via the remote network interface, navigation data specifying a sequence of instructions for traveling between a source point and a destination point, wherein each of the instructions describes a respective operation at a corresponding geographic location; and Therein, the selected function provides the next instruction in the sequence of instructions.

10. The portable device according to claim 9, wherein: The second instruction further causes the portable device to provide the next instruction to the main unit via the short range network interface.

11. The portable device according to claim 9, wherein: The second instructions cause the portable device to provide the next instructions in response to receiving the indication that a next track button was activated.

12. The portable device according to claim 8, wherein: The map is stored in the computer-readable medium.

13. The portable device according to claim 12, in, To generate the mapping, the instructions further cause the portable device to: for each of the indications that the plurality of controls are activated, receiving a corresponding control identifier, And generating a corresponding data record to indicate the correspondence between the control identifier and the selected function.

14. A non-transitory computer readable medium storing thereon instructions which, when executed by one or more processors of a portable device, cause the portable device to: creating, using the pairing application, a mapping between a plurality of controls on a head unit of a vehicle and a plurality of navigation functions supported by the portable device using: (i) an indication of a plurality of controls activated at the head unit received via a communication link between the portable device and the head unit, and (ii) a corresponding one of the plurality of navigation functions selected via a user interface of the portable device to utilize the plurality of controls on the head unit as an external input device for the portable device; After creating the mapping, receiving, by the pairing application, an indication that one of the plurality of controls is activated on the primary unit; selecting, by the companion application, a navigation function from among the plurality of navigation functions according to the received mapping and the received indication; providing an indication of the selected navigation function to a navigation service application executed as a separate task from the companion application; Using the navigation service application to perform the navigation function; as well as A result of performing the navigation function is provided from the navigation service application to the main unit via the companion application.

15. The computer-readable medium of claim 14, wherein: To create the mapping, the instructions further cause the portable device to: for each of the indications that the plurality of controls are activated, receiving a corresponding control identifier, And generating a corresponding data record to indicate the correspondence between the control identifier and the selected function.

16. The computer-readable medium of claim 14, wherein: The instructions cause the portable device to: In a first case, receiving a first indication that a first control among the plurality of controls is activated on the main unit, obtaining navigation data in response to the first indication, wherein the navigation data specifies a sequence of instructions for traveling between a source point to a destination point, In a second case, receiving a second indication that a second control among the plurality of controls is activated on the master unit, and A next instruction in the sequence of instructions is provided to the master unit.

17. The computer-readable medium of claim 16, wherein: The second of the plurality of controls is one of: (i) a next track button or (ii) a volume up button.

18. The computer-readable medium of claim 16, wherein: The instructions cause the portable device to receive the navigation data from a navigation server via a long-range communication link, wherein the portable device communicates with the head unit via a short-range communication link.

19. The computer-readable medium of claim 14, wherein: The plurality of navigation functions of the navigation service application include one or more of the following: (i) starting navigation, (ii) canceling navigation, (iii) providing a next instruction, and (iv) providing a previous instruction.

20. The computer-readable medium of claim 14, wherein: The instructions implement an application programming interface (API) called by the companion application, the companion application being configured to communicate with the navigation service application.

Citation Information

Patent Citations

  • Method and system for guidance based on wireless communication network

    CN101203040A

  • A method of generating improved map data for use in navigation devices, map data and navigation device therefor

    CN101517366A

  • Portable navigation device

    CN101563583A

  • Information processing device, information processing method and information processing program

    CN101630228A

  • Operating system providing consistent operations across multiple input devices

    CN101978364A