MOBILE GEOGRAPHIC APPLICATION IN AUTOMOTIVE ENVIRONMENT

The integration of wearable devices with vehicle head units through a communication protocol manages focus and sensor data to address conflicts, improving safety and usability by ensuring accurate navigation and reducing distractions.

DE112016002580B4Active Publication Date: 2024-11-21GOOGLE LLC
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
DE112016002580
Authority / Receiving Office
DE · DE
Patent Type
Patents
Current Assignee / Owner
Priority Date
2015-06-23
Filing Date
2016-06-22
Publication Date
2024-11-21
Estimated Expiration
2036-06-22

AI Technical Summary

Technical Problem

Existing vehicle systems lack efficient integration of wearable devices with head units, leading to conflicts in navigation, audio, and video focus, as well as inconsistent sensor data, which can distract drivers and compromise safety.

Method used

A communication protocol allowing wearable devices to interact with vehicle components independently of make or model, managing focus and sensor data to ensure safe and efficient operation, including negotiation of video, audio, and navigation focus, and combining sensor outputs to improve accuracy.

Benefits of technology

Enhances safety and usability by preventing driver confusion, ensuring accurate navigation, and improving sensor data integration, thereby reducing distractions and enhancing the overall driving experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

Method for providing geographical information to head units (18) of vehicles, the method comprising: determining, by one or more processors (102) on a portable device (12), a user context regarding a geographic location; the detection, by one or more processors, that the portable device has been communicatively coupled with a head unit of a vehicle, the head unit being equipped with a display device; the transfer to the head unit without an explicit user command, a request that the head unit accept data from the portable device for output via the display device; and in response to receiving a notification that the request has been approved, causing one or more processors to display information regarding the geographic location via the display device without explicit user input on the portable device; where determining the user context with respect to the geographic location involves recognizing that information regarding a business at the geographic location is provided via a user interface of the portable device; the procedure also includes: automatically determining the probability that a user wants to navigate to the geographic location; instigating, when the probability exceeds a threshold, the automatic selection of a geographic location as a destination for navigation instructions, or instigating, when the probability is not above a threshold, the provision of business information relating to a business at the geographic location via the display device of the head unit.
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0001] This disclosure relates to geographic software applications and, more particularly, to using geographic applications in an automotive environment. BACKGROUND

[0002] The background description provided herein is for the purpose of generally setting forth the context of the disclosure. The work of the inventors identified in the present disclosure, to the extent described in this general background section, as well as aspects of the description that might not otherwise be considered prior art at the time of filing, are neither expressly nor by implication admitted as prior art to the present disclosure.

[0003] Many vehicles today are equipped with head units that include displays, touchscreens, speakers, microphones, and / or other components for receiving user input and providing output. Some of these head units also include wired and / or wireless connections to communicate with other electronic devices in the vehicle. US 2009 / 0005070 A1 describes a method for synchronization between mobile devices and vehicles, wherein a mobile device receives position information from a vehicle and includes at least one motion sensor whose data is used to update a position estimate of the mobile device. US 2014 / 0068010 A1 describes networking of vehicle head units with mobile devices, wherein user preferences can be transferred between different vehicles via the networking of a mobile device.EP 1 909 069 A1 describes a method for entering a destination into a vehicle navigation system. An electronic device is coupled to the vehicle navigation system, on which at least one location and an appointment planner module are stored. A location stored on the electronic device or in the vehicle navigation system is selected as a destination for route guidance based on at least one stored appointment. DE 10 2007 024 061 A1 describes a method and a device for suggesting a destination for a navigation system, wherein destinations are derived from the observed and recorded past behavior of a user.US 2014 / 0365124A1 describes a method for a mobile device connected to an interactive communication system of a vehicle, in which a search term is received via the vehicle's audio system, a search is performed on the mobile device for at least one location associated with the search term, and a map is generated that displays the determined location. This map is then shown on a display screen of the vehicle's communication system. US 2014 / 0279723 A1 describes a mobile device with a route prediction engine that can formulate predictions about current or future destinations or routes for the device user based on stored user-specific data. SUMMARY

[0004] This disclosure provides a method according to claim 1, a portable device according to claim 7, and a server according to claim 13. Further embodiments of the respective subject matter are presented in the dependent claims. Generally speaking, the techniques described below allow a user device, such as a smartphone, to securely and efficiently cooperate with various components in an automotive environment. The portable user device may provide video, audio, and sensor data to a vehicle's head unit for display and / or playback via user interface ("UI") devices incorporated in the vehicle.Furthermore, the portable user device may receive sensor data, environmental data, and other data relating to the current state of the vehicle, user commands, and other information from the head unit to improve the quality of information provided to the user.

[0005] One aspect of these techniques is a communication protocol that allows the portable device to access various components of the vehicle, such as one or more displays, audio speakers, speed sensors, or temperature sensors, for example, using a messaging scheme that is independent of the make or model of the vehicle. To this end, the portable device and the head unit can exchange messages that refer to components of the vehicle and describe them in a flexible format as devices at a hardware level. In this way, the portable device can implement much of the logic for interacting with vehicle components, and conversely, the head unit does not need to support complex logic for describing and presenting vehicle components to the portable device.Furthermore, the wearable device can interact with different vehicles with different configurations and software capabilities. Even further, the wearable device can implement discovery services to identify components available on the vehicle, rather than relying on preconfigured settings.

[0006] Another aspect of these techniques is navigation focus management, or the essentially exclusive use of video, audio, tactile, and other output components of the head unit for the purpose of providing navigation instructions. If both the head unit and the portable device are capable of providing navigation instructions, the head unit and the portable device, when connected, may effectively compete for the head unit's output components. To avoid driver confusion, the portable device or the head unit may transmit a message to the other device requesting navigation focus. The other device may approve or deny the request. In one example implementation, the focus assignment policy is implemented in the head unit in accordance with the vehicle manufacturer's requirements.

[0007] Yet another aspect of these techniques is video focus management, or the essentially exclusive use of one or more of the head unit's displays. The wearable device and the unit may exchange messages to determine whether the video output from the wearable device ("projected UI") or from a component operating within the head unit ("native UI") should be displayed via the head unit. The projected UI may include various screen windows generated by software applications running on the wearable device, which may include mapping applications, call applications, music applications, etc. The native UI may include sensor measurements, such as speed and fuel level, as well as a video feed from the rear camera and safety messages (e.g., "seat belt not fastened").Video focus management can be based on user commands, safety factors such as when the head unit acquires video focus to display video from the rear camera, negotiations between the wearable device and the head unit, etc.

[0008] Yet another aspect of these techniques is the management of audio focus, or the substantially exclusive use of one or more of the vehicle's embedded audio output components. The portable device and the head unit may manage audio focus independently of the video focus and / or navigation focus. To support scenarios such as playing a text-to-speech (TTS) notification while the head unit is streaming audio from the portable device, or playing a navigation instruction received from the portable device while the head unit is playing FM radio, the portable device and the head unit may exchange messages to negotiate audio focus assignment. In some cases, the messages indicate not only requests to receive or release focus, but also "push away" conditions, audio types, etc.The portable device and head unit can support multiple simultaneous audio channels for different types of audio data.

[0009] The techniques of this disclosure further allow the wearable device and the head unit, each of which may include a plurality of sensors of varying capability and accuracy, to combine some of the sensor outputs to improve positioning, wheel speed measurements, compass readings, etc. In some scenarios, the wearable device and the sensor may implement heuristic techniques to detect a mismatch in estimating similar parameters, such as speed, based on different sensor measurements. For example, the wearable device may report a small amount of movement based on its sensor measurements, while the head unit may access transmission information from the vehicle and report that the vehicle has stopped. The wearable device and / or the head unit may determine that the user is likely moving the wearable device within the vehicle and adjust the sensor measurements accordingly.

[0010] Furthermore, according to the techniques of this disclosure, the portable device can generate a simulated route for testing various system functions including the portable device and the head unit, and provide the simulated route to the head unit. The head unit, in turn, can provide the parameters of the simulated route to other components of the vehicle, generate various sensor measurements, and provide the sensor measurements to other portable devices. Thus, the portable device can generate a simulated attitude of the vehicle and cause the head unit to provide the simulated attitude to components that the portable device cannot directly access and that may be affected by the simulated attitude. For example, the vehicle's headlights can be automatically turned on based in part on the current attitude of the vehicle.

[0011] Another aspect of these techniques is security features, such as locking the wearable device when the wearable device is connected to the head unit. When implemented, when the wearable device provides the projected UI to the head unit, it prevents the user from accessing other functionalities of the wearable device without unplugging the wearable device. Thus, the user cannot access a text messaging application, which would make driving unsafe, without losing access to the projected UI and, in some cases, without interrupting the music stream or other ongoing interactions between the wearable device and the head unit.

[0012] Another aspect of these techniques is the wearable device's ability to selectively exclude features of the projected and / or native UI based on environmental conditions. The head unit notifies the wearable device of at least some of these environmental conditions, such as the current speed of the vehicle, and various events, such as windshield wiper activation. Based on certain notifications received by the head unit, the wearable device may determine that certain UI features are unsafe, unlikely to be used, or simply obsolete. More generally, the wearable device may adapt its output and / or the output of the head unit based on various environmental conditions. In one example scenario, the wearable device disables the display of a keyboard in response to detecting that the vehicle is moving.In another example scenario, the wearable device detects that the vehicle is moving at a certain speed and that it's likely raining because the windshield wipers are running. The wearable device limits the list of geographic search results to one page, even though a multi-page results list is available, to prevent the user from scrolling or browsing through the list while driving.

[0013] Yet another aspect of these techniques is altering the visual representation of a digital map with respect to the connection between the portable device on which the digital map is rendered and the head unit on which the digital map is displayed. The head unit can report various vehicle- or head unit-specific parameters when the portable device connects to the head unit, and the portable device can determine, for example, which colors to use and whether to display certain geographic features. The portable device can render the digital map by applying different styles, or sets of visual attributes, to the same map feature geometry to create different visualizations of the same geographic area.Thus, using transparent color schemes defined by a specific style, the wearable device can effectively hide geographic features that are typically less relevant in an automotive context, such as public transit data. As a further aspect, a specific style can specify thicker lines for roads when the digital map is used in an automotive context. The wearable device can automatically switch between different styles when the user connects the wearable device to the head unit, or vice versa when the user unplugs the wearable device from the head unit.

[0014] Another aspect of these techniques is continuity between the execution of certain tasks performed on the portable device and the execution of related tasks on a vehicle's head unit when the portable device detects a new connection to the head unit. For example, when a user explicitly or implicitly selects a specific geographic location via their portable device and later connects the portable device to the head unit, the portable device automatically triggers the display of driving instructions or other information related to the geographic location via the head unit. To this end, the portable device may request control of the display device embedded in the head unit. Depending on the implementation and / or configuration of the head unit, the portable device may acquire control automatically or upon acknowledging the transfer of control via the head unit.

[0015] At least some of the techniques discussed above can be used with self-driving vehicles. For example, a user can pair their wearable device with the head unit of a self-driving vehicle to use the wearable device as a source of multimedia content or navigation instructions that the vehicle can follow autonomously. Character list • Fig. 1 is a block diagram of an example system in which a portable user device is configured to communicate with a head unit of a vehicle and in which the portable user device is configured to receive map data, navigation data, and other types of geospatial data over a communications network; • Fig. 2 is a block diagram of an exemplary portable user device used in the system of Fig. 1 can be in operation; • Fig. 3 is a block diagram of an exemplary head unit used in the system of Fig. 1 can be in operation; • Fig. Figure 4 is a block diagram of an exemplary set of channels over which the portable device and the head unit of Fig. 1 be able to exchange data; • Fig. 5A is a block diagram of an example message that the portable device of Fig. 1 can send to a vehicle to request service discovery; • Fig. Figure 5B is a block diagram of an example message that the vehicle sends in response to the message from Fig. 5 can send; • Fig. 5C is a block diagram of an exemplary data unit describing a service of any type included in the message from Fig. 5B may be included; • Fig. Figure 5D is a block diagram of an exemplary data unit describing a media sink service included in the data unit of Fig. 5C may be included; • Fig. 5E is a block diagram of an exemplary data unit describing a video configuration included in the data unit of Fig. 5D may be included; • Fig. 6A is a message flow diagram of an example scenario in which the head unit displays native navigation instructions and rejects a request from the portable device for navigation focus; • Fig. Figure 6B is a message flow diagram of an example scenario in which the head unit approves a request for navigation focus from the portable device and displays projected navigation instructions. • Fig. 7A is a message flow diagram of an example scenario in which the head unit switches between displaying the native UI and the projected UI in response to user commands; • Fig. 7B is a message flow diagram of an example scenario in which the head unit switches between displaying the native UI and the projected UI in response to a safety-critical event; • Fig. 7C is a message flow diagram of an example scenario in which the head unit switches between displaying the native UI and the projected UI in response to a request from the wearable device; • Fig. Figure 8 is a block diagram of an exemplary set of audio channels comprising the portable device and the head unit of Fig. 1 can create; • Fig. Figure 9A is a message flow diagram of an example scenario in which the head unit acquires audio focus in response to a user command. • Fig. 9B is a message flow diagram of an example scenario in which the portable device requests and receives audio focus for streaming music from the head unit in response to a user command; • Fig. 9C is a message flow diagram of an example scenario in which the head unit acquires audio focus in response to a user command and then passes audio focus to the portable device for streaming music in response to another user command; • Fig. 9D is a message flow diagram of an example scenario in which the portable device provides audio navigation instruction to the head unit during radio playback on the head unit; • Fig. 9E is a message flow diagram of an example scenario in which the head unit generates an audio notification while the portable device streams music to the head unit; • Fig. 9F is a message flow diagram of an example scenario in which the head unit rejects a request from the portable device for audio focus for security reasons; • Fig. 9G is a message flow diagram of an example scenario in which the portable device applies speech recognition to audio received from the head unit; • Fig. 10 is a flowchart of an example method for determining appropriate conditions for combining a sensor output from a portable device with a sensor output from a head unit; • Fig. 11 is a message flow diagram of an example scenario in which a portable device provides a simulated route to a head unit of a vehicle and receives feedback based on the output of the vehicle components; • Fig. 12 is a message flow diagram of an example scenario in which a portable device locks out its user interface when projecting a user interface onto a vehicle head unit; • Fig. 13 is a message flow diagram of an example scenario in which a portable device projects the presentation and / or selection of content via the head unit of a vehicle in response to environmental factors reported by the head unit; • Fig. 14 is a block diagram of an exemplary memory module of the portable device of Fig. 1, in which map stylization data describes different visual styles for automotive and non-automotive environments. • Fig. 15A is a message flow diagram of an example scenario in which the portable device detects a communicative pairing with a head unit of a vehicle, determines a geographic context related to a geographic location, and automatically requests focus for projecting navigation instructions to the geographic location. • Fig. 15B is a message flow diagram of an example scenario in which the portable device or a network server selects a geographic location for use in projected navigation directions based on previous user activity; • Fig. 15C is a message flow diagram of an example scenario in which a portable device receives a suggested geographic location from a network server and uses the geographic location in projecting navigation instructions via a head unit; • Fig. 15D is a message flow diagram of an example scenario in which a portable device or a network server selects a geographic location from one portable device for use in projecting navigation directions based on previous activities of another portable device; and • Fig. 16 is a flowchart of an example method for providing geographic information to vehicle head units. DETAILED DESCRIPTION OF THE DRAWINGS Example architecture of hardware and software

[0016] Referring first to Fig. 1, an exemplary communications system 10 in which some or all of the techniques outlined above may be implemented includes a portable user device (or simply "portable device") 12 that may be communicatively coupled to a vehicle subsystem 14 of a vehicle (not shown). The vehicle subsystem 14 may include a head unit 18 and a plurality of vehicle sensors 20. The portable user device 12 is configured to communicate with a network server 40 over a communications network 30, which may be a wide area network such as the Internet. The network server 40 may be connected to several databases, including a map database 42 and a geospatial database 44.

[0017] The portable user device 12 may be any portable computing device, such as a smartphone, a tablet computer, a wearable computer, etc. An exemplary implementation of the portable user device 12 is described with reference to Fig. 2. The portable user device 12 communicates with the head unit 18 via a communications link 16, which may be wired (e.g., Universal Serial Bus (USB)) or wireless (e.g., Bluetooth). The portable user device 12 may also communicate with various content providers, servers, etc., via a wireless communications network, such as a fourth- or third-generation (4G or 3G) cellular network.

[0018] In operation, the portable user device 12 provides the head unit 18 with information regarding navigation, which may include digital map images, text, and audio. The head unit 18 may display this information via a display, such as a touchscreen. Furthermore, the head unit 18 may include various hardware input control elements, such as buttons, knobs, etc. An exemplary implementation of the head unit 18 is described with reference to Fig. 3 discussed.

[0019] The head unit 18 may receive data from a set of vehicle sensors 20 during operation. The set of vehicle sensors 20 may include, for example, a global positioning system (GPS) module to determine the current position of the vehicle in which the head unit 18 is installed, an inertial measurement unit (IMU) to measure the speed, acceleration, and current orientation of the vehicle, a barometer to determine the altitude of the vehicle, etc. Although Fig. 1 illustrates the set of sensors 20 as coupled to the head unit 18, it should be noted that the sensors 20 may also be integral components of the head unit 18.

[0020] In some implementations, the communications link 16 operates as a component of an automotive interconnect layer 60, which can be viewed as a service that provides a communications protocol for one or more components of the portable user device 12 to communicate with one or more components of the head unit 18. More generally, the automotive interconnect layer 60 supports various functions that enable interactions between the portable user device 12 and the head unit 18. As discussed in more detail below, the automotive interconnect layer 60 may include one or more software components of the portable device 12 and one or more components of the head unit 18.

[0021] The network server 40 can be implemented as a single device or as a group of servers (e.g., as a set of front-end servers and a set of back-end servers). Furthermore, depending on the implementation, the network server 40 can be implemented as a single network node with all the databases in the group of databases (e.g., as in Fig. 1) or as separate network nodes associated with each of the databases in the group of databases. The network server 40 may include processing hardware, such as one or more processors configured to execute instructions stored, for example, in non-transitory, computer-readable memory. The network server 40 may also include a network interface using which the network server 40 may communicate with remote hosts, such as the portable device 12 and the database 42 and 44. The network interface may support various communication protocols for wired and / or wireless communication types.

[0022] In the example configuration of Fig. 1, the portable user device 12 communicates with the network server 40 to access map data provided by the map database 42 and spatial data provided by the geospatial database 44. The databases 42 and 44 may be implemented in any suitable manner, such as as relational databases on dedicated storage devices, dedicated groups of storage devices, or, for example, on the network server 40. The map database 42 may store descriptions of geometry and location information for various natural geographical features (e.g., rivers, mountains, forests) as well as artificial geographical features (e.g., roads, buildings, parks). The map data may include, among other data, vector graphic data, raster image data, and text data. The geospatial database 44 may store information regarding various points of interest (e.g., monuments, museums, landmark buildings), businesses (e.g.,Store locations (restaurants, hotels, shops), train and bus stations, municipal boundaries, and other geographic units. Descriptions of geographic units can contain any number of search terms, based on which the data can be indexed or otherwise organized for quick search and retrieval.

[0023] The portable device 12 can operate in an online mode in which the portable device 12 has a sufficiently reliable network connection to the network server 40 with a sufficiently high capacity. In the online mode, the user device 12 requests map data, geospatial search results, other geographic data, as well as non-geographic data such as music streams from the network server 40. If the portable device 12 cannot establish a network connection to the network server 40, for example, due to poor network coverage, or if the user of the portable device 12 has explicitly deactivated the network connection, the portable device 12 can operate in an offline mode. The portable device 12 can store street data, geospatial data, and other data offline in the cache, which can be implemented, for example, in the non-volatile memory of the portable device 12.

[0024] In general, the exemplary communication system 10 may include processing hardware of any suitable type configured to implement the techniques of this disclosure. The processing hardware may include one or more processors on one or more computing devices, one or more servers, a distributed network, etc.

[0025] Now referring to Fig. 2, a portable user device 100 may operate within the communication system 10 (e.g., as the portable user device 12) or in another suitable computing environment. The portable user device 100 includes one or more processors 102, such as, for example, a central processing unit (CPU). The portable user device 100 also includes a memory 116 readable by the one or more processors 102. The memory 116 may include one or more non-volatile memory modules, such as a flash memory, hard drive, optical drive, etc., and / or one or more volatile memory modules, such as a random access memory (RAM) module. In some implementations, the one or more processors 102 also include a graphics processing unit (GPU) to render graphics content more accurately and efficiently.Furthermore, the portable user device 100 may include one or more long-range communication interfaces 104 supporting, for example, a concept such as 802.11 (Wi-Fi®) or a suitable telephony protocol, and one or more short-range communication interfaces 106 supporting, for example, a concept such as Bluetooth®, Wi-Fi Direct®, or USB.

[0026] The portable user device 100 further includes various input and output devices, such as a touchscreen 108, a microphone 110, and speakers 112. In addition, the portable user device 100 includes one or more sensors 114, which may include a GPS sensor, an accelerometer, a gyro sensor, a temperature sensor, a proximity sensor, etc. In some implementations, the portable user device 100 may determine its current location by using the communication interface(s) 104 and 106 to discover Wi-Fi hotspots with known locations and to perform triangulation. The components 102-114 may be interconnected, for example, via a digital bus.

[0027] The memory 116 stores a variety of software components or modules, including a mobile platform 120, a protocol transmitter 122, automotive application programming interfaces (APIs) 124, and software applications, including automotive applications (apps) 126. The software modules may include compiled instructions and / or instructions in any suitable programming language that are interpreted at runtime. The software modules 120-126 execute on the one or more processors 102.

[0028] The mobile platform 120 may include an operating system (OS) that controls the portable user device 100. As such, the mobile platform 120 includes various drivers that support the functions of the operating system. For example, the mobile platform 120 includes a virtual display driver that defines how information or data (e.g., text, images, alphanumeric characters, etc.) is displayed by the portable user device 100 (e.g., via the touchscreen 108). As another example, the mobile platform 120 includes a media encoder and a driver for a media player. The media encoder operates to encode and / or decode media signals (e.g., video, audio, etc.), while the media player driver defines how these media signals are played or delivered by the portable user device 100 (e.g., via the speaker(s) 112).As yet another example, the mobile platform 120 includes a Wi-Fi Direct / USB driver that defines how communication schemes, such as Wi-Fi Direct or USB, are processed by the portable user device 100 (e.g., via the communication interface(s) 104 and 106). As a further example, the mobile platform 120 includes an input feed driver that defines how user input is received or acquired by the portable user device 100 (e.g., via a virtual keyboard on the touchscreen 108). Additionally, the mobile platform 120 includes a car mode driver that defines how the portable user device 100 can be enabled for in-car use, such as making calls, using navigation, listening to music, etc., while the vehicle is being driven.

[0029] The protocol transmitter 122 may, for example, be implemented as part of the automotive link layer 60 of Fig. 1. The protocol transmitter 122 may include a communication protocol for exchanging sensor data, user commands, device-to-device commands, audio commands, audio streams, video streams, and other data with another device, such as the head unit 18 of Fig. 1. The protocol transmitter 122 can be plugged into the interfaces of the mobile platform 120, such as video, audio, networking, input, etc. Some of these features of the communication protocol are discussed in more detail below.

[0030] The portable device 100 may communicate with a head unit of a vehicle via the short-range communication interface(s) 106. The portable user device 100 and the head unit may support one or more protocols via the general-purpose protocol supported by the short-range communication interface(s) 106 and the corresponding short-range communication interface of the head unit (such as Bluetooth®, Wi-Fi Direct®, or USB). As a more specific example, the protocol transmitter 122 and the protocol receiver 230 (see Fig. 3 below) support a protocol discussed in more detail below, which occupies a layer above Android Open Accessory Protocol (AOAP), which in turn occupies a layer above USB. In such an implementation, the portable device 100 operates as a USB accessory, and the head unit operates as a USB host.

[0031] The automotive APIs 124 may receive and transmit data via the protocol transmitter 122. These APIs define a standardized interface for developers to create software applications that use a vehicle's head unit to interact with the driver. More specifically, the automotive APIs 124 allow the portable user device 100 to access various parameters, functions, or services of a vehicle. In particular, with reference to Fig. 1, the automotive APIs 124 allow the portable user device 100 to access data or information collected by the set of vehicle sensors 20. As in Fig. 2, the example set of automotive APIs 124 includes a fuel query interface that allows the device 100 to receive information regarding the current fuel level of the vehicle and, in some implementations, more robust information such as fuel efficiency, past fuel consumption, etc.The automotive APIs 124 further include a speed query interface for obtaining information regarding the current speed of the vehicle, a windshield wiper interface for determining whether the windshield wipers are currently active (and, in some implementations, at what speed), an engine speed (RPM) query interface for obtaining data regarding the vehicle's RPM measurements, a tire query interface for determining the condition of the tires, and a radio query interface for determining the status of the radio component embedded in the vehicle. More generally, the set of automotive APIs 124 may include any suitable functions for obtaining current and / or historical data from the vehicle.

[0032] In general, the automotive APIs 124 may be implemented for use with any suitable programming language, including those that are currently in the art. Furthermore, the automotive APIs 124 may be provided in different versions for different respective operating systems.

[0033] The automotive applications 126 may provide applications that can operate in an automotive environment and, in some cases, other environments. For example, the automotive applications 126 may include a geographic / mapping application 126A that may use data stored offline or retrieved from an online database (e.g., the database 42 of Fig. 1) processes received map data and generates interactive digital maps for display via the touchscreen 108 and / or the head unit of a vehicle. The geographic / mapping application 126a may also receive and process spatial queries, such as requests to find nearby restaurants or gas stations, obtain and display navigation directions, etc. Other examples of the automotive applications 126 may include a calling application for making and / or receiving phone calls via the remote communication interface 104, a voice input application that allows users to enter voice commands to control the device 100, and a music application that allows users to listen to music using the device 100. The music application may stream music in an online mode or store audio files (not shown) in the memory 116.

[0034] Next, Fig. 3 an exemplary head unit 200 which may be used, for example, as the head unit 18 of Fig. 1. The head unit 200 includes one or more processors 202, a memory 216, which are generally similar to the processor(s) 102 and the memory 116 of Fig. 2. The head unit 200 can communicate with a portable device, such as the portable device 100, via the one or more near-field communication interfaces 204, which can be wired and / or wireless. Similar to the near-field communication interface(s) 106, the near-field communication interface(s) 204 can support Bluetooth®, Wi-Fi Direct®, USB, or another suitable communication protocol.

[0035] The head unit 200 may also include a touchscreen 206, which is typically larger and has a higher density than the touchscreen 108 of the portable device 100. The touchscreen 206 may serve as a main console display of the head unit 200. In other implementations, the head unit 200 may include a display that does not receive input from the touchscreen and receives input via buttons, knobs, and other input devices. Further, in some implementations, the head unit 200 may include a plurality of display devices. Similarly, the head unit 200 may include a microphone 208, which may be a high-quality microphone that may be housed within the head unit housing or elsewhere in the vehicle.

[0036] Further, the head unit 200 may have access to sensors 212, which may include a GPS location sensor, a position beacon, a mechanical speed sensor, a compass heading sensor such as a gyroscope, an accelerometer, a thermometer, etc. Further, the head unit 200 may have access to indicators 214, such as a windshield wiper status indicator, a vehicle transmission indicator, a window closure indicator, etc. In general, the head unit 200 may include or have access to any suitable number of components that report measurements, settings, configurations, and parameters of the vehicle.

[0037] The memory 216 also stores a variety of software modules, including a head unit OS 220, an OS adaptation layer 222, and a native human-machine interface (HMI) 224. Each of the modules 220-224 may, for example, be implemented using software instructions executable on the one or more processors 202.

[0038] The OS adaptation level 222 includes a protocol receiver 230 that uses the same protocol as the protocol transmitter 122 of Fig. 2. In this way, the head unit 200 can communicate with the portable device 100 or another computing device that implements the protocol transmitter 122. The protocol receiver 230 and the protocol transmitter 122 can be implemented as parts of the automotive link layer 60 of Fig. 1 can be operated.

[0039] The native HMI 224 includes functions for accessing various vehicle functions. For example, the native HMI 224 can support functions for accessing the home screen, which displays basic vehicle information (e.g., transmission, speed, fuel level), activating the AM / FM radio, and making a phone call. Some of these HMI 224 functions, such as the phone function, access the protocol receiver 230 to establish a communication link with the portable device.

[0040] In general, the portable device 100 and the head unit 200 may exchange some types of data over separate channels. In an example set of channels 300, shown in Fig. 4, the automotive applications 126 provide outputs to the head unit 200 via the video and audio output channels 302. The protocol transmitter 122 and the protocol receiver 230 may exchange messages via a control channel 304. Vehicle data, user input events, microphone audio, and other data from the head unit OS 220 may pass to the portable device 100 via channels 306.

[0041] More specifically, control channel 305 may be a bidirectional channel that supports call setup messages, which supports the establishment of other channels, such as channels 302 and 306, etc. Video output channel 302A may be a device-to-device channel that supports H.264 video from portable device 100 to head unit 200 for display via the main console display. Audio output channel 302B may be a device-to-device channel that transmits audio from portable device 100 to head unit 200 for output via the vehicle speakers. The audio may be AAC at 44k / 48k, AAC or PCM for 16k, etc.

[0042] The vehicle data channel 306A may transmit vehicle-related data such as GPS data, wheel speed, and other data from the head unit 200 to the portable device 100. The input event channel 306B may be a device-to-device channel that transmits input events from input devices in the vehicle, such as touchscreen(s), buttons, dials, etc., to the portable device 100. The microphone audio channel 306C may be a device-to-device channel that transmits audio captured by the vehicle microphone to the portable device 100.

[0043] The set of channels 300 may also, in some implementations, include channels over which the portable device 100 and the head unit 200 may exchange information about such other services as FM radio, HVAC, etc. II. Communication protocol for accessing vehicle components

[0044] Generally speaking, applications running on wearable devices such as wearable device 12 (or 100) can operate in feature-rich application frameworks, be easily upgradeable, have better connectivity than typical embedded services, support user profiles, etc. On the other hand, the head unit 18 (or 200) illustrated above typically has a larger, well-positioned, higher-quality video display, as well as high-fidelity audio and a larger battery. In some implementations, head unit 18 has a main console display, as well as additional displays and multiple speakers. In addition, head unit 18 or 200 has access to high-quality sensor data, such as sensors 212.

[0045] To allow both the portable device 12 and the head unit 18 to benefit from the capabilities of the other device, the automotive interconnect layer 60 supports messages according to which the vehicle components are presented to the portable device 12 as a collection of low-level hardware devices. The automotive interconnect layer 60 can discover and access these vehicle components accordingly, as if these components were peripheral to the portable device 12. For convenience, these vehicle components are sometimes referred to as components of the head unit 200 because of the ability of the head unit 200 to access these components. However, it will be understood that some of these components may be physically located elsewhere in the vehicle and external to the head unit 200.

[0046] The automotive connectivity layer 60 can establish a variety of services for component-specific communication. As used herein, a service is an endpoint for communication between the portable device and the head unit. The automotive connectivity layer 60 can discover each component of the head unit 200 separately and associate each discovered component with a unique endpoint.

[0047] In general, vehicles today have a wide variety of input types: dials, pushbuttons, buttons, dials, touchpads, touchscreens, etc. Some vehicles have multiple instances of certain input devices. For example, a vehicle may have dials in the front and rear seats. A vehicle may also have many types of sensors, such as a GPS unit, a wheel speed sensor, a compass, an interior temperature sensor, and an outside temperature sensor.

[0048] Referring to Fig. 3, the head unit 200 can list (or have listed) its hardware. In the example configuration of Fig. 3, the automotive interconnect layer 60 may list its single touchscreen 206 as Display #0. In another configuration, the automotive interconnect layer 60 lists a plurality of display devices, each with its own resolution, color depth, and physical location. The automotive interconnect layer 60 may discover each of the displays separately and generate respective addresses for those displays. The head unit 200 may then generate descriptions of these display services in accordance with the automotive interconnect layer 60 protocol.

[0049] For example, referring to Fig. 5A, the portable device 100, for example, sends a message 400 including a service discovery request to the head unit 200 via the control channel 304 (see Fig. 4) send. As in Fig. As illustrated in Figure 5A, message 400 may include several icons of various sizes, one or more of which the head unit 200 may display as a selectable control via its main console display. When the user presses or otherwise activates the icon, the head unit 200 may, for example, transition from projected mode to native display mode. The message 400 may also include text to be displayed to the user via the main console to alert the user that the portable device 100 is in communication with the head unit 200.

[0050] In response to message 400, head unit 200 may determine which components are available, list the components, and generate descriptions of those components that conform to the general format of messages 5B and 5C. In effect, message 400 advertises the services available at head unit 200.

[0051] A message 420 from Fig. 5B includes descriptions of service endpoints, each of which is considered a Fig. 5C. In general, message 420 may describe any number of different types of services. In addition to service descriptions, message 420 may indicate the vehicle's make, model, year of manufacture, identification, driver position (left or right), head unit hardware type and software versions, etc.

[0052] The data unit 440 may specify a substantially unique identifier for the service and include a description of the service. The description may, in turn, include an indication of the service type (e.g., sensor source service, media sink service, input source service, media source service) and a description consistent with the corresponding structure. One such exemplary structure describing a media sink service is described in Fig. 5D illustrated.

[0053] A data unit 460 of Fig. 5D includes an indication of an available codec type, an audio type, a description of an audio configuration, and / or a description of a video configuration, etc. As a further example, the video configuration contained in data unit 460 conforms to the format of a data unit 480 describing a video configuration, illustrated in Fig. 5E. The data unit 480 may include an indication of a codec resolution, a frame rate, an image width limit, etc.

[0054] More generally, messages that the portable device 100 and the head unit 200 can exchange may contain numerous nested data units. The formats of the Fig. 5A-E provide a high level of flexibility and compatibility. Furthermore, because the head unit 200 can describe many types of components in this way and provide detailed parameters for each component, the portable device 100 can implement extensive software logic for interacting with these components. Accordingly, the head unit 200 does not need to support complex, component-specific software to simplify interactions between these components and the head unit 100. III. Managing navigation focus between a portable device and a head unit

[0055] In some implementations of system 10, both portable user device 12 and head unit 18 are capable of generating turn-by-turn navigation instructions at the same time. As discussed above, portable user device 12 can generate navigation instructions in an online mode, using data received from network server 40, or an offline mode, using cached data. Head unit 18 can implement an onboard navigation system, for example, using road data stored in memory of head unit 18.

[0056] When not in communication with the vehicle subsystem 14, the portable user device 12 may generate navigation instructions for display and / or audio playback via a user interface of the user device 12, while the head unit 18 may generate “competing” navigation instructions using the user interface elements embedded in the vehicle, such as the Fig. 3 and / or speakers 212. In this case, the portable user device 12 and the head unit 18 compete for the driver's attention. When the user connects the portable user device 12 to the head unit 18, the units 12 and 18 may compete for the resources of the head unit 18. More specifically, the portable user device 12 may attempt to display information via the head unit 18 while the head unit 18 attempts to display its own "native" visual output.

[0057] To avoid providing duplicate or conflicting navigation instructions when the portable user device 12 is connected to the head unit 18, the automotive connection layer 60 implements a navigation focus negotiation technique, which involves substantially exclusive use of one or more user video and / or audio output devices of the head unit 18 for the purpose of providing navigation instructions. To this end, the portable device 12 and the head unit 18 may exchange messages to establish the navigation focus, as described with reference to Fig. 6A and Fig. 6B discussed.

[0058] In general, illustrate Fig. 6A and Fig. 6B exemplary message exchange between a user 502, a head unit 504 and a portable device 506. The head unit 504 may, for example, be connected to the head unit 200 of Fig. 3 and / or the head unit 18 of Fig. 1. The portable device 506 may, for example, correspond to the portable device 100 of Fig. 2 and / or the portable device 12 of Fig. 1 correspond.

[0059] In Fig. 6A, while the head unit 504 and the portable device 506 are not connected to each other, the head unit 504 displays, for example, native navigation instructions generated by the onboard navigation system of the vehicle, while the portable device 506 displays navigation instructions generated by a geographic application running on the portable device 506, such as the application 126A of Fig. 2, were generated.

[0060] The user then plugs the portable device 506 into the head unit 504 or wirelessly connects them. The portable device 506 can automatically request navigation focus by sending a navigation focus request message to the head unit 504. According to one implementation, the portable device 506 generates the navigation focus request message in response to determining that (i) a navigation session is in progress and (ii) that the portable device 506 is now connected to the head unit 504.

[0061] For example, the head unit 504 may play a dialog via its main display console to determine whether the user prefers native navigation or portable device navigation. Additionally or alternatively, the head unit 504 may request a selection from the user, for example, by generating an audio announcement. If the user selects portable device navigation, the head unit 504 may accept the request, deactivate the native navigation, and begin displaying the projected navigation from portable device 506. In the scenario of Fig. 6A, however, the user selects native navigation, and the head unit 504 rejects the request from the portable device 506. The head unit 504 then proceeds to display the native navigation instructions.

[0062] In the scenario of Fig. 6B, the head unit 504 does not display navigation instructions at the time the user connects the portable device 506 to the head unit 504. Accordingly, the head unit 504 approves the navigation focus request and begins displaying projected navigation instructions.

[0063] In another implementation, the head unit 504 may implement a policy to automatically prioritize either the head unit 504 or the portable device 506 and automatically reject navigation focus requests according to the policy. The head unit 504 may not display a dialog in these cases. For example, the head unit 504 may be configured to unconditionally accept the navigation focus request once the user connects the portable device 506 to the head unit 504.

[0064] In general, the head unit 504 and / or the portable device 506 may implement any suitable policy and / or user dialogs to prevent the head unit 504 and the portable device 506 from competing for the same audio, visual, tactile, etc. resources of the head unit 504 to present navigation instructions. IV. Managing video focus between a portable device and a head unit

[0065] In addition to navigation instructions, the native visual output of the head unit 18 (or 300) may include vehicle data such as speed, transmission, fuel levels, temperatures, etc., video inputs from the rear ("backup") camera, various announcements such as "Seat belt not fastened!" or "Check tire pressure," and other information. The native visual output of the head unit 18 may be referred to as the "native UI."

[0066] The visual output of the portable device 12 provided to the vehicle subsystem 14 for display via the one or more screens of the head unit 18 may be referred to as a "projected UI." In addition to the navigation instructions discussed above, the projected UI may include various geographic information related to navigation (e.g., "gas station in 5 miles"), user interface controls of the geographic application 126A, controls for selecting music stations via the music application running on the portable device 12, UI controls for making and receiving phone calls, and / or other suitable information.

[0067] To provide a safe and intuitive user interface to the driver and / or passenger of a vehicle, the automotive interconnect layer 60 may implement a technique for negotiating the video focus or substantially exclusive use of the one or more video output devices of the head unit 18 for the purpose of providing visual outputs.

[0068] To assign video focus, the portable user device 12 and the head unit 18 may exchange messages to request video focus, allow or deny a request for video focus, notify the other device of a loss of focus, or otherwise negotiate and / or enforce the video focus assignment. In some implementations, the automotive interconnect layer 60 may ensure that the video focus is mutually exclusive. In other words, either the portable user device 12 or the head unit 18 may provide visual output to the driver via the video resource(s) of the head unit 18, but not both.

[0069] According to one implementation, head unit 18 implements policy decisions regarding the allocation of video focus. Automotive link layer 60 may support messages by which portable user device 12 requests video focus, and head unit 18 may deny or allow the request depending on the policy, which may be specific to the automaker.

[0070] Some example scenarios in which a head unit and a wearable device manage video focus are described with reference to Fig. 7A - 7C. In these scenarios, a head unit 604 can, for example, be connected to the head unit 200 of Fig. 3 and / or the head unit 18 of Fig. 1. The portable device 606 may, for example, correspond to the portable device 100 of Fig. 2 and / or the portable device 12 of Fig. 1 correspond.

[0071] First referring to Fig. 7A, at the beginning of scenario 600, portable device 606 displays a projected UI, which may include, for example, an interactive menu of the geographic application. User 602 presses a button or otherwise manipulates a control on head unit 604 to switch the display to the native UI of head unit 604. For example, the user may press the hardware button for the air conditioning on head unit 604, and head unit 604 may provide a native UI for climate control. In this case, head unit 604 switches to the native UI display without negotiating video focus with portable device 606 and forcibly notifies portable device 606 of the loss of video focus. Portable device 606 stops sending the projected UI to head unit 604 upon receiving the command.At a later time, user 602 operates the same or a different control on the selected projected UI, and head unit 604 notifies portable device 606 that portable device 606 now has video focus. In response, portable device 606 continues transmitting the projected UI via head unit 604.

[0072] Thus, in scenario 600, the head unit 604 acquires and releases video focus in response to a user action with respect to the head unit 604. In some situations, the head unit 604 may also acquire video focus for security reasons.

[0073] For example, with reference to Fig. 7B, at the beginning of scenario 650, the portable device 606 may display the projected UI via the head unit 604. The head unit 604 then detects that a safety-critical UI needs to be displayed. For example, the user 602 may have shifted the transmission into REVERSE. The head unit 604 switches the display to the native UI to display the rear camera. The head unit 604 also notifies the portable device 606 of the loss of video focus. Upon receiving this notification, the portable device 606 stops transmitting the projected UI to the head unit 604.

[0074] The head unit 604 then completes the display of the safety-critical UI. For example, the user 602 may have shifted the transmission into DRIVE mode. The head unit 604 notifies the portable device 606 that the portable device 606 has regained video focus. In response to this notification, the portable device 606 proceeds to transmit the projected UI to the head unit 604.

[0075] Furthermore, in some situations, the head unit 604 may switch between displaying the native UI and the projected UI in response to a request from the portable device 606. For example, a music streaming application may be running on the portable device 606 while the head unit 604 and the portable device 606 are connected. The music streaming application may stream audio through the head unit 604 and not request video focus until the end of the playlist is reached. As another example, a navigation application may similarly run without requesting video focus until the next step in the step-by-step instructions is reached.

[0076] As a more specific example, the head unit 604 shows at the beginning of the example scenario 700 of Fig. 7C displays the native UI, such as climate control and vehicle status. User 602 connects portable device 606 to head unit 604. Portable device 606 plays a navigation application.

[0077] When the vehicle approaches an upcoming event in the navigation directions generated by the navigation application on the portable device 606 (e.g., a turn), the portable device 606 begins broadcasting the projected UI and requests video focus. The head unit 604 confirms that the native UI is not currently displaying safety-critical information, such as input from the rear camera, and determines that the video focus request should be allowed. The head unit 604 then switches to the projected UI to display the information from the portable device 606 regarding the upcoming event. Managing audio focus

[0078] Referring to Fig. 1, the portable device 12 and the vehicle subsystem 14 may both implement complex audio management techniques. For example, the portable device 12 may support a plurality of parallel software applications, and each of these software applications may output one or more audio streams. The portable device 12 may implement various audio policies to coordinate audio between these applications and streams, such as automatically "pushing away" or lowering the volume of a notification stream when another application requests audio focus over the media stream.

[0079] The vehicle subsystem 14 also supports a variety of audio streams. These streams may include, for example, cabin audio (speakers directed at the entire cabin) and driver audio (directional speakers directed at the driver's head). Each of these audio streams may be directed to different speakers and / or have different audio processing and / or trigger the implementation of different audio policies. For example, the vehicle subsystem 14 may also push cabin audio away when the driver is playing audio.

[0080] To coordinate audio between the two complex audio systems of the portable device 12 and the vehicle subsystem 14, the automotive interconnect layer 60 may implement a technique for negotiating the allocation of audio focus. The audio focus may involve the substantially exclusive use of one or more audio output devices accessible to the head unit 18 for the purpose of providing audio output. As discussed above, a vehicle may generally include a plurality of speakers, which may be installed in the head unit 18 or elsewhere within the vehicle. The automotive interconnect layer 60 may manage the audio focus independently of the video focus or navigation focus. More specifically, the automotive interconnect layer 60 allows, as in Fig. 9A-G illustrates the portable device 12 and the head unit 18 exchanging audio focus messages.

[0081] In an example implementation, the automotive interconnect layer 60 operates on audio sources, which can correspond to logical endpoints that can generate and send audio data to audio streams. The automotive interconnect layer 60 also operates on audio sinks, which can correspond to logical endpoints that can receive audio content from an audio stream. An example audio sink is the location of in-vehicle speakers. Furthermore, the automotive interconnect layer 60 can operate on audio streams, which can correspond to the aforementioned combinations of an audio source and an audio sink.

[0082] As used herein, output audio streams refer to streams sent from the portable device 12 to the head unit 18, and input audio streams are those sent from the head unit 18 to the portable device 12. Fig. Figure 8 illustrates an exemplary set of audio channels that may be used on the portable device 12 and the head unit 18 of Fig. 1-powered automotive connection layer 60. In an example implementation, a set of signals 750 includes an audio input stream for a microphone, a bidirectional audio stream for incoming Bluetooth audio calls, and four audio output streams: a UI stream for user interface feedback data, a guidance stream for driver guidance, a voice stream for conversational speech, and a media stream for cabin media.

[0083] The portable device 12 and the head unit 18 can exchange messages to coordinate the allocation of audio focus for each logical audio stream shared by the portable device 12 and the head unit 18. In this manner, the portable device 12 and the head unit 18 can coordinate multiple audio streams. Either the portable device 12 or the head unit 18 can operate as a "master," configured to receive audio focus requests from the other and accept or reject these requests based on configuration, environmental factors, policies, etc.

[0084] Fig. 9A illustrates an example scenario 800 in which the head unit acquires audio focus in response to a user command. Fig. 9B illustrates an example scenario 820 in which the portable device requests and receives audio focus for streaming music from the head unit in response to a user command. Fig. 9C illustrates an example scenario 840 in which the head unit acquires audio focus in response to a user command and then passes audio focus to the portable device for streaming music in response to another user command. Fig. 9D illustrates an example scenario 860 in which the portable device provides audio navigation instruction to the head unit during radio playback on the head unit. Fig. 9E illustrates an example scenario 880 in which the head unit generates an audio notification while the portable device streams music to the head unit. Fig. 9F illustrates an example scenario 900 in which the head unit rejects a request from the portable device for audio focus for security reasons. Fig. 9G illustrates an example scenario 920 in which the portable device applies speech recognition to audio received from the head unit. VI. Detecting and correcting sensor errors in the automotive environment

[0085] In System 10 of Fig. 1, interconnected devices and / or subsystems such as wearable device 12 and vehicle subsystem 14 may generate inaccurate sensor data in some situations. For example, vehicle subsystem 14 may provide erroneous accuracy information (such as setting the accuracy field to 0). As another example, wearable device 12 may generate inaccurate compass data due to the presence of a nearby magnetic object. As yet another example, vehicle subsystem 14 may output a wheel speed that is 5% inaccurate due to tire pressure.

[0086] The automotive interconnect layer 60 may employ heuristic techniques to detect and sometimes correct sensor faults using sensor outputs from the wearable device 12 and the vehicle subsystem 14. In isolation, both the wearable device 12 and the vehicle subsystem 14 may have difficulty detecting sensor faults. The automotive interconnect layer 60 supports messages that allow the wearable device 12 and the vehicle subsystem 14 to jointly determine sensor faults.

[0087] In some implementations, the automotive connectivity layer 60 collects raw sensor data measurements from the portable device 12 and / or the vehicle subsystem 14 and provides these raw data measurements to the portable device 12. The portable device 12 post-processes sensor measurements from local and external (vehicle) sensors in a navigation correction stage. In an example implementation, the geographic mapping application 126A (see Fig. 2) The navigation correction stage. In a further implementation, the functionality is implemented in the head unit 18. For convenience, this functionality may be discussed with continued reference to the automotive interconnect layer 60, which includes components on the portable device 12 and / or the head unit 18, such as one or more software modules.

[0088] In an example scenario, the automotive connectivity layer 60 detects a 5% deviation in wheel speed by comparing sensor measurements relayed from the vehicle sensors through the head unit 18 to the GPS measurements of the portable device 12, or, in some cases, combined GPS measurements from the vehicle sensors and the portable device 12. The automotive connectivity layer 60 then establishes a feedback loop to correct this deviation, thus making the wheel speed more accurate.

[0089] In another example, the portable device 12 receives inaccurate GPS data from the vehicle subsystem 14 and uses the GPS accuracy of the portable device 12 as an average for the GPS accuracy of the car. As yet another example, the portable device 12 may determine that its heading can be ignored if the GPS heading from the vehicle subsystem 14 provides different values. In this case, the portable device 12 may determine that the user is likely moving the portable device 12 within the vehicle.

[0090] More specifically, the automotive connection layer 60 checks whether the heading direction of the compass on the portable device 12 changes over a certain period of time substantially synchronously with the heading direction of the compass on the vehicle containing the vehicle subsystem 14. If the compass changes at the same time, the automotive connection layer 60 determines an estimate that the portable device is stationary within the car. This determination can help the system combine sensor measurements. Otherwise, if the heading direction does not change at the same time, the user may be moving the portable device within the car and the sensor fusion is likely to produce unreliable results. An example method 910 for determining conditions for combining a sensor output from the portable device 12 with a sensor output from a head unit 18 is described in Fig. 10 illustrates.

[0091] As another example, if the accelerometer of the wearable device 12 indicates that the wearable device 12 is moving, but sensor measurements from the vehicle indicate that the vehicle is stationary, the wearable device is likely moving relative to the vehicle. VII. Simulated routes

[0092] When the portable device 12 has access to the map data 42 via the network server 40 (or, in some cases, when a large amount of offline map data is stored), it may access an enriched road graph (which may include a data structure specifying connections between road segments, lengths of road segments, various restrictions related to road segments, speed limits, lane restrictions, etc.). Using this road graph, the portable device 12 may generate a simulated route that may include a series of maneuvers such as, for example, turns and lane changes at corresponding geographic locations.

[0093] To determine whether the vehicle is responding to the route as expected, the portable device 12 may provide the simulated route to the head unit 18, which in turn may provide the parameters of the simulated route to the vehicle components, such as sensors. Fig. In the example scenario 920 illustrated in Figure 11, the software stack of a portable device 922 may generate a simulated route and, via a head unit 924, cause various vehicle components 926 to respond to the generated route. Portable device 922 may correspond to portable device 12 and / or 100, and head unit 922 may correspond to head unit 18 and / or 200. Head unit 18, in some cases, accesses components and software modules distributed across various components of the vehicle and / or portable device 12.

[0094] As an example, a particular vehicle may be configured to automatically turn on its headlights based on a sun position calculation combined with the vehicle's current position. In this case, the portable device 12 provides the vehicle with a simulated position so that the vehicle's response can be tested.

[0095] With continued reference to Fig. 11, the portable device 922 may provide a simulated route as a series of a plurality of maneuvers and locations, or, in another implementation, the portable device 922 may provide location (and maneuver) information individually. Furthermore, the head unit 922 may provide feedback, such as sensor measurements, status indicators for the various vehicle components 926, etc., either individually, as in Fig. 11, or as a single data collection. VIII. Preventing the user from activating phone functions

[0096] In a Fig. In the example scenario 940 illustrated in Figure 12, a user 942 connects a portable device 943 to a head unit 948, and an automotive connection 946 of the portable device 943 begins transmitting a projected UI to the head unit 948. The automotive connection 946 may, for example, correspond to the automotive connection layer 60 discussed above. The automotive connection 946 also locks out the native UI of the portable device 943. In other words, the automotive connection 946 prevents the user from accessing the display 944 of the portable device 943 without disconnecting the portable device 943 from the head unit 948. The display 944 may be blank during the lockout stage or display an indicator, such as a text message: "Disconnect the device to access the menu."

[0097] Thus, if the driver wishes to access a banking application on the portable device 943 while the portable device 943 is connected to the head unit 948, the driver is effectively prevented from doing so. In this way, the automotive connection 946 can reduce distractions. After the user 942 disconnects the portable device 943 from the head unit 948, the user can again access the user interface of the portable device 943 via the display 944.

[0098] It is noted that when the display 944 is locked out, the portable device 943 may continue to project the UI via the head unit 948. The projected UI may provide the user 942 with access to some of the features of the portable device 943, such as, for example, the automotive applications 126 of Fig. 2. IX. Blocking features with regard to vehicle data

[0099] Furthermore, in some implementations, the head unit 18 may provide environmental data to the portable device 12, and the portable device 12 may determine which UI features should be enabled, disabled, or modified in response to those environmental conditions. The UI features that the portable device 12 may thus modify may be native to the head unit 18 or to the portable device 12. In an example implementation, the portable device 12 implements the policy according to which UI features are locked out, reactivated, or modified and sends appropriate commands to the head unit 18.

[0100] Fig. 13 illustrates an example scenario 960 in which a portable device 962 (which may correspond to portable device 12 and / or 100) is paired with a head unit 964 (which may correspond to head unit 18 and / or 200). The portable device 962 initially provides the projected UI with a default level of detail. The head unit 964 then reports changes in the environmental data, such as an indication that the windshield wipers are now running, to the portable device 962. The head unit 964 also reports that the vehicle is moving at a speed of 60 miles per hour.

[0101] The portable device 962 may observe these signals and determine that the geographic search results generated by a geographic application, such as application 126A, and provided by the projected UI should be reduced to one page. The driver can then view these search results without scrolling or browsing through the list. Thus, in this scenario, the portable device 962 effectively disables the scrolling / list browsing functionality.

[0102] As another example, vehicle 964 may display a keyboard as part of its native UI. Portable device 962 may determine, when head unit 964 reports that the vehicle has no passengers (e.g., based on the weight measured by the passenger seat), that the keyboard should be disabled whenever the vehicle is moving. To this end, portable device 962 may send an appropriate command to head unit 96. Stylizing map data in accordance with vehicle data

[0103] When displaying geographical or navigational information to a driver of a vehicle, it is often desirable to ensure that the driver can easily view, read, and understand the information at a glance. When the portable device 12 is connected to the vehicle subsystem 14 (see Fig. 1), the portable device 12 can adapt the display of map data, geographic search results, and other geographic data for display within the vehicle environment. More specifically, the portable device 12 can modify the visual presentation of a digital map with respect to the connection between the portable device 12, on which the digital map is rendered, and the head unit 18, on which the digital map is displayed.

[0104] In some implementations, the portable device 12 customizes the digital map rendered for in-vehicle display by applying certain "styles," or sets of visual attributes, such as color, transparency, line thickness, etc., to map a feature geometry. The portable device 12 may apply a style based on the general automotive context, which may be the same across all types of vehicles, and / or a vehicle-specific automotive context. A vehicle-specific automotive context may depend on the car's make, model, and year, as well as more specific parameters such as interior color.

[0105] Fig. 14 is a block diagram of an exemplary memory 1000, which may correspond, for example, to the memory 116 of the portable device 100. In the memory 1000, map stylization data is used to describe different visual styles for automotive and non-automotive environments. Similar to the Fig. 2, the memory 1000 may store various software components or modules, such as a mobile platform, a protocol transmitter, automotive APIs, and automotive applications.

[0106] The memory 1000 also includes a map feature geography module 1002, which stores map data, and a map feature style data module 1004, which stores map style data. The map data includes descriptions of geometry for various map features, such as buildings, parks, bodies of water, label text, textures, various forms of metadata, etc. Some of these map features may be defined in a vector graphics format or other suitable scalable format. In some cases, the map data may also include raster images, for example, in a bitmap format. The map style data includes various style parameters for rendering the map data. For example, each style parameter may describe a respective color, number of keystrokes, width for each of the keystrokes, transparency level, etc.

[0107] With reference to Fig. 1, the portable user device 12 may request map data and map style data for rendering a digital map of a geographic region from the network server 40. The map database 42 may provide the map data along with the map style data. The portable user device 12 may store the received map data in module 1002 and the received map style data in module 1004. The portable user device 12 may then display the digital map of the geographic region and render the digital map with appropriate style parameters.

[0108] When the portable user device 12 is connected to the vehicle (such as the head unit 18), the digital map displayed on the device 12 may be rendered in a manner appropriate for the vehicle environment. The portable user device 12 may render the digital map by applying different styles or sets of visual attributes to create different visualizations of the same geographic area. For example, the portable user device 12 may hide certain geographic features in the result that are typically less relevant in an automotive context to provide an enhanced user experience. The portable device 12 may automatically switch between different styles when the user connects the portable device 12 to the vehicle, or vice versa when the user unplugs the portable device 12 from the vehicle.

[0109] In an example scenario, the user might view a map on the portable device 12 with certain map features present, such as bus stop icons. When the user connects the portable device 12 to the vehicle, the bus stop icons may be less relevant to the user who is now driving the vehicle. As such, the portable device 12 might apply appropriate styling, such as changing the transparency level of the bus stop icons, to remove the bus stop icons from the map view. This helps to improve the user experience by simplifying the map and removing potential clutter.

[0110] In another example scenario, when the user connects the portable device 12 to the vehicle, the portable device 12 may apply styles to emphasize certain map features. For example, thicker lines may be applied to roads to make the road appear more visible. As another example, some driving-related map elements, such as street signs or gas stations, may be bolded to emphasize the importance or relevance of these elements to the user driving the vehicle.

[0111] In yet another example scenario, the portable device 12 may render the map differently when the vehicle is moving. In other words, relevant map features may be visualized according to the vehicle's speed. For example, some less important map features, such as trees, buildings, parks, etc., may be given less detail or removed altogether, while other, more important map features, such as landmarks, may be given greater detail or highlighted. Thus, the driver can better see and understand the environment surrounding the vehicle while the vehicle is moving. XI. Use of user intent signals for order continuity

[0112] If a user explicitly or implicitly selects a specific geographic location via their wearable device and later connects the wearable device to a car's head unit, the wearable device may automatically trigger the display of driving instructions or other information associated with the geographic location via the head unit. In particular, the wearable device may request control of the display device embedded in the head unit, and depending on the head unit's implementation and / or configuration, the wearable device may obtain control automatically or upon user confirmation via the head unit.

[0113] A software module executing on the portable device can determine a context regarding the geographic location based on the currently active application (e.g., a mapping application displaying the geographic location on a digital map, a web browser displaying a listing for a business at the geographic location, a news application in which a read message includes a street address) and / or past user activity (e.g., internet searches, geographic queries, requests for navigation directions). In some implementations, the software module executing on the portable device queries a network server to determine whether to project navigation data, a business date, or other information onto the head unit display.In some cases, the determination may be based on a calculation of the likelihood that the user will request navigation instructions, business data, a digital map, etc.

[0114] Thus, a user can simply connect the wearable device to the head unit and automatically see selected geographic data on the head unit without explicitly selecting an input from the wearable device via the head unit and navigating through menus to select the desired function. In this respect, the software running on the wearable device can provide continuity of the user experience when a wearable device is connected to a head unit.

[0115] In an example scenario, user Alice launches a navigation application on her smartphone and initiates a request for the nearest cinema. She then plugs her smartphone into her car's head unit. The head unit displays a dialog asking Alice to confirm that she wants to request navigation directions to the cinema. Upon Alice's confirmation, the smartphone begins projecting navigation directions via the head unit. It should be noted that in this example scenario, Alice did not have to explicitly activate the mode on the head unit to receive or project data from the smartphone, nor did she have to navigate through menus and explicitly activate this mode on her smartphone. Furthermore, Alice did not have to launch or reactivate the mapping / navigation application, reselect the cinema, and issue a command to project navigation directions to the cinema via the head unit.

[0116] For further clarity, Fig. 15A shows an exemplary message sequence 1100 between a portable device 1102 and a head unit 1104. The head unit 1104 may, for example, be connected to the head unit 200 of Fig. 3 and / or the head unit 18 of Fig. 1 and the portable device 1102 can communicate with the portable device 100 of Fig. 2 and / or the portable device 12 of Fig. 1 correspond.

[0117] According to the scenario of Fig. 15A, for example, the user selects a particular geographical location via an interactive mapping application (e.g., the mapping application 126A of Fig. 2) or by viewing information regarding the geographic location in a web browser (event 1110). As a more specific example, the user may view the business hours for a particular geolocated business in a browser window on the portable device 1102. When the user pairs the portable device 1102 with the head unit 1104 (event 1112), the browser window is active and in the foreground. A software component executing on the portable device 1102, such as the log sender 122 or the geographic / mapping application 126A (see Fig. 2) may detect the pairing (event 1114), for example, by monitoring operating system events. The software component may then automatically determine that focus should be requested from head unit 1104 (event 1116) and request focus by sending one or more messages (event 1118). In some implementations, the software component may not even prompt the user to confirm requesting focus, or may rely on prior authorization from the user. The geographic / mapping application 126A in this scenario may be running in the background, waiting for events related to pairing a portable device 1002 with a vehicle head unit.

[0118] The head unit 1104 may display a confirmation dialog (1120) and, upon receiving the confirmation, may provide an appropriate indication to the portable device 1102 (event 1122). In response, the protocol sender 122, the geographic / mapping application 126A, or another software component may automatically select the geographic location previously selected at state 1110 for use with the head unit 1104 (event 1124). For example, the mapping application executing on the portable device 1102 may generate and project navigation data for driving to the geographic location (events 1126, 1128). As another example, a software component executing on the portable device 1102 may project business hours or other information related to a business entity at the geographic location.

[0119] Thus, instead of explicitly selecting information or a task to be projected via the head unit, the user can simply confirm that an automatically selected geographic location and the corresponding task (e.g., navigation, checking business hours, dialing a phone number) are correct. In other words, a software component executing on the portable device 1102 and / or a network server can, in some cases, predict user needs (at least in part) based on current user activity on the portable device.

[0120] Furthermore, in addition to current activity, the software component and / or the network server can anticipate user needs based on the user's past activities and even the activities of other users. To modify the above example, Alice can use a web browser on her smartphone to view show times at the nearest cinema. According to the settings previously entered by Alice, her smartphone and / or a network server generates a record indicating a link between Alice, the cinema-related website, and the time of her visit to the website. One hour later, Alice can get into her car and connect her smartphone to the head unit. Software running on her smartphone and / or the network server generates an indication that Alice is likely to drive to the cinema.Accordingly, your smartphone automatically requests focus and begins to project navigation instructions.

[0121] Fig. Figure 15B illustrates an exemplary message sequence 1200 between a portable device 1102 and a head unit 1104. Similar to the episode involving Alice and the website, the scenario of Fig. 15B illustrates activities on the portable device 1102 between selecting a geographic location and pairing with the head unit 1104. Specifically, at one time, the user may configure the portable device 1102 to obtain a geographic context, such as selecting a particular geographic location via a web browser, email application, messaging application, geographic / mapping application, etc. (event 1202). At a later time, the user may view information related to a geographic location using a web browser application, messaging / email application, geographic / mapping application, etc. (event 1204).

[0122] The geographic location indication may be stored in the memory of portable device 1102 or on a network server, depending on the implementation or scenario (event 1206). In at least some of these implementations, the time the information was viewed is stored along with the geographic location indication. The user can then move the application through which they viewed geographic location information to the background or even close the application entirely.

[0123] At a later time, the user may pair the portable device 1102 with the head unit 1104, and the portable device 1102 may automatically determine a geographic context regarding a geographic location, negotiate focus, and project information for a geographic location via the head unit, similar to the scenario of Fig. 15A (events 1210). In this case, however, portable device 1102 may determine the geographic context based on the information stored when processing event 1106. Thus, even though the application used to establish the geographic context may no longer be active, portable device 1102 may nevertheless automatically suggest projecting navigation directions via the head unit based on the user's past activities.

[0124] Fig. 15C illustrates a message sequence 1300, which is generally similar to sequences 1100 and 1200, except that a user intent server 1004 determines a proposed geographic location for use in projected data about a head unit using an indication of current and / or past user activity. The user intent server 1004 may be implemented, for example, as a component of the network server 40 of Fig. 1 or operate as a separate server.

[0125] In the scenario of Fig. 15C, the portable device 1002 transmits an indication of a geographic location to the user intent server 1006 (event 1302), upon detecting pairing of the head unit 1004 (event 1304), requests a suggested geographic location from the user intent server 1006, and receives a suggested geographic location (event 1306). The request corresponding to event 1304 may include an indication that the portable device 1002 is now paired with the head unit 1004. The user intent server 1004 may select a suggested geographic location based on a single event (e.g., that the user is currently viewing information about a geolocated business in a browser window), a single instance of recent activity (e.g., that the user has requested a geographic location), or a plurality of instances (e.g., that the user frequently travels to a particular geographic location).Furthermore, user intent server 1004 may estimate the relevance of certain geographic locations with respect to time. For example, the user may drive to a particular location at a particular time of day. As discussed above, for example, the user may configure portable device 1102 and / or user intent server 1006 to use this user-specific data in generating suggestions by explicitly activating certain controls or by installing certain applications or plug-ins.

[0126] Now referring to Fig. 15D, an exemplary message sequence 1400 corresponds to a scenario in which the user intent server 1006 determines a geographic location associated with information projected from the portable device 1002 via the head unit 1004 based on relevant activities on a peer portable device 1008.

[0127] Returning to Alice, in an example scenario, her friend Bob launches an application for making restaurant reservations and looks up the hours a particular cafe is open. Bob has previously determined that certain information be shared with Alice. When Alice and Bob enter a car, Alice's smartphone, using an appropriate proximity sensing or location-sharing technique, determines that Bob is also in the car (assuming Alice and Bob have configured their respective smartphones for this purpose). Alice's smartphone queries a network server, which determines a geographic location for projecting navigation directions based not only on Alice's profile but also on information Bob shares with Alice.In this scenario, Alice's smartphone can then automatically request navigation directions or business information for the cafe and project the information via the head unit.

[0128] As in Fig. 15D illustrates that the portable peer device 1008 shares a geographic location indication with the user intent server 1006 (event 1410). At a later time, the portable device 1002 paired with the head unit 1004 detects the presence of the portable peer device 1008 (event 1412) and requests the user intent server 1006 to provide a suggested geographic location in light of the detected presence of the portable peer device 1008 (event 1414). The user intent server 1006 then selects the geographic location received as part of event 1410 and provides that location, or other relevant information, to the portable device 1002 (event 1416) for projecting the corresponding navigation instructions via the head unit 1004.

[0129] More generally, the user intent server 1006 may select geographic locations for one or more users based on one or more such signals as phone calls, web pages visited, search results, the current state of the application, etc., provided those users chose to share this information.

[0130] Fig. 16 illustrates an example method 1500 for providing geographic information to vehicle head units, which may be implemented in the protocol transmitter 122, the geographic / mapping application 126A, or another software component running on the portable user device. The method 1500 may be implemented as a set of instructions executable on one or more processors and stored on a non-transitory computer-readable medium, such as flash memory or a hard disk.

[0131] The method 1500 begins at block 1502, where a user context related to a geographic location is determined. As discussed above, the context may be determined based on current activity on a portable device, one or more past activities on the portable device, one or more activities on a peer device, etc.

[0132] Next, a communicative coupling of the portable device with the head unit of a vehicle is detected (block 1504). In response, focus is automatically requested from the head unit (1506). The focus request may be sent without an explicit user command. However, according to some implementations, the user previously configures the portable device to automatically request focus in certain situations.

[0133] At block 1508, navigation instructions to the geographic location are projected from the wearable device via the head unit. In some scenarios, the user may explicitly confirm that the head unit should grant focus to the wearable device via the head unit's input component. Additional considerations

[0134] The following additional considerations apply to the preceding discussion. Throughout this specification, plural instances may implement components, operations, or structures described as a single instance. Although individual operations of one or more methods have been illustrated and described as separate operations, one or more of the individual operations may be performed concurrently, and nothing requires that the operations be performed in the illustrated order. In general, structures and functionality represented as separate components in exemplary configurations may be implemented as a combined structure or component. Likewise, structures and functionality represented as a single component may be implemented as separate components.These and other variations, modifications, additions and improvements are within the scope of the present invention.

[0135] Certain implementations are described herein as including logic or a number of components, modules, or mechanisms. Modules may constitute either software modules (e.g., code embodied in a machine-readable medium or a transmission signal) or hardware modules. A hardware module is a tangible entity capable of performing particular operations and that can be configured or arranged in a particular manner. In example implementations, one or more computer systems (e.g., a stand-alone, client, or server computer system) or one or more hardware modules of a computer system (e.g., a processor or a group of processors) may be configured by software (e.g., an application or a portion of an application) as a hardware module that operates to perform particular operations, as described herein.

[0136] Unless explicitly stated otherwise, descriptions using words such as "process", "calculate", "compute", "determine", "represent", "display" or the like may refer to actions or processes of a machine (e.g., a computer) that manipulate or transform data represented as physical (e.g., electronic, magnetic, or optical) quantities in one or more memories (e.g., volatile memories, non-volatile memories, or a combination thereof), registers, or other machine components that receive, store, transmit, or display information.

[0137] As used herein, reference to "an implementation" or "an embodiment" means that a particular element, feature, structure, or characteristic described in connection with the implementation is included in at least one implementation. The use of the phrase "in an implementation" in various places in the specification does not necessarily always refer to the same embodiment.

[0138] Some implementations may be described using the terms "coupled" and "connected," along with their derivatives. For example, some implementations 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" can also mean that two or more elements are not in direct contact with each other, but still operate or interact with each other. Implementations are not limited in this context.

[0139] As used herein, the terms "comprises," "comprising," "includes," "contains," "has," "comprising," and other variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, article, or device comprising a list of elements is not necessarily limited to only those elements, but may include other elements not expressly listed or inherent in such process, method, article, or device. Furthermore, unless otherwise noted, "or" refers to an inclusive rather than an exclusive or. For example, a condition A or B is satisfied by one of the following: A is true (or present) and B is false (or absent), A is false (or absent) and B is true (or present), and both A and B are true (or present).

[0140] Additionally, "a," "an," or "another" is used to describe elements and components of the implementations herein. This is done solely for convenience and to convey a general idea of ​​various implementations. The description should be read as including one or at least one, and the singular includes the plural unless clearly intended otherwise.

[0141] Upon reading this disclosure, those of ordinary skill in the art will recognize still further alternative structural and functional designs for facilitating interactions between a portable device and a vehicle head unit through the principles disclosed herein. Thus, it is to be understood that although particular implementations and applications have been illustrated and described, the disclosed implementations are not limited to the precise construction and components disclosed herein. Various modifications, alterations, and changes that will be apparent to those of ordinary skill in the art may be made in the arrangement, operation, and details of the method and apparatus disclosed herein without departing from the spirit and scope of the appended claims.

Claims

[1] A method for providing geographical information to head units (18) of vehicles, the method comprising: determining, by one or more processors (102) on a portable device (12), a user context regarding a geographical location; detecting, by one or more processors, that the portable device has been communicatively coupled to a head unit of a vehicle, the head unit being equipped with a display device; transmitting to the head unit, without an explicit user command, a request that the head unit accept data from the portable device for output via the display device; and in response to receiving an indication that the request has been approved, causing, by one or more processors, the display of information regarding the geographic location via the display device, without explicit user input on the portable device; wherein determining the user context regarding the geographic location includes detecting that information regarding a business at the geographic location is provided via a user interface of the portable device; the method further comprising: automatically determining a probability that a user will want to navigate to the geographic location; causing, if the probability is above a threshold, a geographical location to be automatically selected as a destination for navigation instructions, or causing, if the probability is not greater than a threshold, business information relating to a business at the geographical location to be provided via the head unit display device. [2] The method of claim 1, including determining user context with respect to geographical location during a session in which a user interacts with a software application executing on the portable device, wherein the session was deactivated prior to detecting that the portable device has been communicatively coupled to the head unit. [3] The method of claim 1, wherein causing information regarding the geographic location to be displayed via the display device causes the geographic location to be automatically selected as a destination for the navigation instructions. [4] The method of claim 1, wherein determining the user context with respect to a geographical location includes: providing a digital map via a user interface on the portable device and receiving a selection of the geographic location via the user interface. [5] The method of claim 1, wherein determining the user context regarding the geographic location includes receiving a search request regarding the geographic location via an application executing on the portable device. [6] The method of claim 1, further comprising: transmitting the user context regarding the geographical location to a network server; and receiving a selection of geographic location information from the network server. [7] Portable device comprising: one or more processors (102); an interface (106) configured to couple the portable device to a head unit (18) of a vehicle; a non-transitory computer-readable memory (116) having stored thereon instructions that, when executed by the one or more processors, cause the portable device to: to determine a user context regarding a geographical location, to detect that the portable device has been communicatively coupled with the head unit of a vehicle, the head unit being equipped with a display device, to transmit to the head unit, without an explicit user command, a request that the head unit accept data from the portable device for output via the display device and in response to receiving an indication that the request has been approved, cause information regarding the geographic location to be displayed via the display device without explicit user input on the portable device; wherein, to determine the user context regarding the geographic location, the instructions cause the portable device to recognize that information regarding a business at the geographic location is provided via a user interface of the portable device; and to determine the user context regarding the geographical location, the instructions further cause the portable device to: automatically determine a probability that a user will want to navigate to the geographic location; to initiate it if the probability is above a threshold that a geographical location will be selected as a destination for navigation instructions or to initiate it if the probability is not above a threshold that business information relating to a business at the geographical location will be provided via the head unit display device. [8] The portable device of claim 7, wherein the instructions further cause the computing device to: to determine the user context with respect to geographical location during a session in which a user interacts with a software application executing on the portable device, wherein the session was deactivated prior to detecting that the portable device has been communicatively paired with the head unit. [9] The portable device of claim 7, wherein to cause the geographical location information to be displayed via the display device, the instructions further cause the portable device to: to have the geographical location automatically selected as a destination for navigation instructions. [10] The portable device of claim 7, further comprising a user interface; wherein, to determine the user context with respect to a geographical location, the instructions further cause the portable device to: provide a digital map via the user interface and to receive a selection of the geographical location via the user interface. [11] The portable device of claim 7, wherein, to determine the user context regarding the geographical location, the instructions cause the portable device to receive a search request regarding the geographical location via an application executing on the portable device. [12] The portable device of claim 7, wherein the instructions further cause the portable device to: to transmit the user context regarding the geographical location to a network server; and to receive a selection of geographical location information from the network server. [13] Server (40) operated in a communications network (30), the server comprising: a network interface to communicate with remote hosts and processing hardware configured to: to receive from a portable device (12), at a first time, via the network interface an indication of a geographical location selected on the portable device, to store in a non-volatile computer-readable memory the reference to a geographical location and the first time, subsequent to storing the indication and the first time, to receive a request for a proposed geographical location from the portable device for use with a head unit of a vehicle at a second time, to determine, based at least on the difference between the first time and the second time, whether the stored geographical location should be suggested and provide the portable device with a suggestion including an indication of the stored geographical location via the network interface in response to that the stored geographical location should be suggested; where the reference to the geographical location selected on the portable device corresponds to a one-time selection of the geographical location via a web browser and wherein the processing hardware is configured to determine that the geographic location should be suggested if the geographic location corresponds to a geolocated business; and to determine a user context regarding the geographical location, the processing hardware is further configured to: automatically determine a probability that a user will want to navigate to the geographic location; if the probability is above a threshold, to provide a suggestion that a geographical location will be selected as a destination for navigation instructions or, if the probability is not above a threshold, to provide a suggestion that business information relating to a business at the geographical location be provided via the head unit display device. [14] The server of claim 13, wherein the processing hardware is further configured to: to determine whether the stored geographic location should be suggested with regard to a time at which the request for a suggested geographic location was received. [15] The server of claim 14, wherein the processing hardware is configured to suggest the stored geographic location to the portable device at a particular time of day. [16] The server of claim 13, wherein the processing hardware is configured to determine that the geographic location should be suggested in response to determining that the geographic location indication has been received from the portable device a plurality of times.

Citation Information

Patent Citations

  • Method and device for adaptive target determination in navigation systems

    DE102007024061A1

  • Method for operating a navigation system and method for creating a database with potential destinations and navigation device

    DE102008005796A1

  • Intelligent destination setting for navigation systems

    EP1909069A1

  • Synchronizing mobile and vehicle devices

    US20090005070A1

  • Systems, methods and articles for a server providing communications and services involving automobile head units

    US20140068010A1