WO2016022837A1

WO2016022837A1 - Systems and methods for enhanced navigation, route, and destination suggestions

Info

Publication number: WO2016022837A1
Application number: PCT/US2015/044070
Authority: WO
Inventors: Randall MARX; Kevin HIBBARD
Original assignee: International Development Group Limited
Priority date: 2014-08-06
Filing date: 2015-08-06
Publication date: 2016-02-11

Abstract

In one embodiment, a method for hands-free advertising and pay-per-patronage revenue includes providing an application resident in a mobile device. The method further includes receiving at the application an information request from a user in a vehicle and contacting a suggestion clearinghouse with the information request from the application. The method further includes processing the information request at the suggestion clearinghouse and returning information to the user, the information including a destination. The method further includes detecting the user in the vehicle went to the destination and billing a company associated with the destination on the basis of the detecting.

Description

SYSTEMS AND METHODS FOR ENHANCED NAVIGATION, ROUTE, AND DESTINATION

SUGGESTIONS

TECHNICAL FIELD

The embodiments described herein relate to systems and methods for allowing the user to access enhanced navigation, route, and destination suggestions based on suggestions and route collection and processing.

BACKGROUND

With the introduction of smart phones and other mobile computing devices, users have rapid access to information, content, and the ability to purchase products. People in various contexts, whether commuting via car, motorcycle, or other vehicles, may not have the ability to fully access their smart phone or mobile computing device; however, they still may desire to interact with the device, access information, receive traffic updates, receive destination suggestions, or otherwise utilize their smart phone or mobile computing device.

Some innovations have occurred in relation to smart phones and mobile computing devices in vehicles such as Bluetooth® connectivity for voice features and other systems. This allows the smart phones or other mobile computing devices some opportunity to interface with the vehicle. Bluetooth® integration typically involves the speakers of the vehicle as well as a microphone for receiving sounds from the user.

SUMMARY

In one embodiment, a method for hands-free advertising and pay-per-patronage revenue includes providing an application resident in a mobile device. The method further includes receiving at the application an information request from a user in a vehicle and contacting a suggestion clearinghouse with the information request from the application. The method further includes processing the information request at the suggestion clearinghouse and returning information to the user, the information including a destination. The method further includes detecting the user in the vehicle went to the destination and billing a company associated with the destination on the basis of the detecting. Optionally, the information request is a destination. Alternatively, the information request is a product. In one alternative, the information request is a keyword representative of a destination selected from a group of keywords. In another alternative, the group of keywords includes gas station, service station, grocery store, and liquor store. In yet another alternative, the group of keywords includes electronics store, bank, and clothing store. Optionally, the application is an app and the mobile device is a smart phone. In one alternative, the method further includes receiving from the company an advertisement at the suggestion clearinghouse, wherein the information returned to the user is the advertisement. In one alternative, the method further includes providing an audio request from the application resident in the device to the user, wherein the information request is responsive to the audio request. In one alternative, the method further includes triggering the audio request from the user based on detecting the user is in a vehicle. In another alternative, the method further includes linking the mobile device to an NFC chip in the vehicle, wherein the linking causes the application resident in a mobile device to provide the audio request. Optionally, detecting the user is in a vehicle is based on GPS feedback from the mobile device. Alternatively, detecting the user is in a vehicle is based on accelerometer feedback from the mobile device. Optionally, the NFC chip is located in a charging pad.

In another embodiment, a method for hands-free assistance includes providing an application resident in a mobile device and receiving at the application an information request from a user in a vehicle. The method further includes providing, to the user through audio communication from the mobile device, route information based on the information request. Optionally, the route information includes predicted travel time as compared to average travel time. Alternatively, the route information includes information concerning accidents or delays along a route related to the information request. In one alternative, the information request is a destination. Optionally, the method further includes providing an audio request from the application resident in the device to the user, wherein the information request is responsive to the audio request. Alternatively, the method further includes triggering the audio request from the user based on detecting the user is in a vehicle. Optionally, the method further includes linking the mobile device to an NFC chip in the vehicle, wherein the linking causes the application resident in a mobile device to provide the audio request. Alternatively, detecting the user is in a vehicle is based on GPS feedback from the mobile device. Optionally, detecting the user is in a vehicle is based on accelerometer feedback from the mobile device. In one alternative, the NFC chip is located in a charging pad.

In one embodiment, a system for hands-free assistance includes an application on a mobile device, the application configured to receive, at the application, an information request from a user in a vehicle; and provide, to the user through audio communication from the mobile device, route information based on the information request. Optionally, the application further is configured to provide an audio request from the application resident in the device to the user, wherein the information request is responsive to the audio request. Alternatively, the application further is configured to trigger the audio request from the user based on detecting the user is in a vehicle. In one configuration, the application further is configured to link the mobile device to an NFC chip in the vehicle, wherein the linking causes the application resident in a mobile device to provide the audio request. Optionally, detecting the user is in a vehicle is based on GPS feedback from the mobile device. Alternatively, detecting the user is in a vehicle is based on accelerometer feedback from the mobile device. Optionally, the NFC chip is located in a charging pad.

In one embodiment, a system for hands-free assistance includes an application on a mobile device, the application configured to receive at the application an information request from a user in a vehicle and contact a suggestion clearinghouse with the information request from the application. The application further is configured to process the information request at the suggestion clearinghouse and return information to the user, the information including a destination. The application further is configured to detect the user in the vehicle went to the destination and bill a company associated with the destination on the basis of the detecting.

In one embodiment, a computer-readable non-transitory storage medium that contains instructions, which, when executed by one or more processors, results in performing operations including receiving, at the application, an information request from a user in a vehicle; and provide, to the user through audio communication from the mobile device, route information based on the information request. In one embodiment, a computer-readable non-transitory storage medium that contains instructions, which, when executed by one or more processors, results in performing operations including receiving at the application an information request from a user in a vehicle and contact a suggestion clearinghouse with the information request from the application, process the information request at the suggestion clearinghouse, and return information to the user, the information including a destination; and detect the user in the vehicle went to the destination and bill a company associated with the destination on the basis of the detecting.

BRIEF DESCRIPTION OF THE DRAWINGS

Fig. 1 shows one embodiment of a system diagram for enhanced navigation, route, and destination suggestions via a suggestion clearinghouse and route collector;

Fig. 2 shows one embodiment of a vehicle-based view of a system for enhanced navigation, route, and destination suggestions via a suggestion clearinghouse and route collector;

Fig. 3a shows one embodiment of a vehicle interaction flow chart for controlling vehicle settings;

Fig. 3b shows one embodiment of a vehicle interaction flow chart for monitoring driver efficiency;

Fig. 3c shows one embodiment of a vehicle interaction flow chart for monitoring driver performance;

Fig. 3d shows one embodiment of a vehicle interaction flow chart for monitoring vehicle performance;

Fig. 4a shows one embodiment of a flow chart for executing pre-travel communications;

Fig. 4b shows one embodiment of a flow chart for executing pre-travel communications including advertisements;

Fig. 5a shows one embodiment of a flow chart for executing startup communications; and Fig. 5b shows one embodiment of a flow chart for determining what content to return to the user.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Embodiments of systems and methods for enhanced navigation, route, and destination suggestions via a suggestion clearinghouse and route collector are described herein ("mobile suggestions system" or "MSS"). In various embodiments, a module resident in a mobile device or vehicle-based computing system receives and provides various information to and from the user. Embodiments of mobile suggestion systems are described herein as being implemented in mobile devices that interconnect with a vehicle's Bluetooth® and CAN bus system. However, the various embodiments may function in a vehicle-based computing system or a mobile device that is not interconnected with the vehicle's Bluetooth® and/or CAN bus system. Embodiments of the MSS may have four primary modes of operation. These modes include, but are not limited to, 1) pre-travel; 2) startup; 3) in-transit; and 4) event responsive. Note that the categories of operation are for the sake of convenience of description, and the operation may include different configurations of modes of operation.

Essentially, the MSS constantly monitors routes the user travels. Most users travel similar or identical routes frequently. Based on routes recorded, the MSS may create a database of destinations to which the user commonly travels. In pre-travel mode, the system may predict where the user will travel to at a certain time of the day and indicate to the user if travel times are greater than normal due to construction, traffic, or other occurrences. In startup mode, the MSS may inquire with the user concerning the desired destination or errand. It then may deliver information concerning driving conditions to that destination. Alternatively, it may deliver targeted suggestions or advertisements for fulfilling that destination. The MSS alternatively, based on the location of the user, the day of the week, and the time of day, may provide alternative route or traffic information, for instance when the user is headed to work. During in- transit mode, the MSS functions in a similar fashion to startup mode. The MSS may receive destination or errand inquiries from the user and provide targeted suggestions based on these inquiries. The MSS also may provide en route detour information and driving instructions in order to fulfill the errand request. Further, the MSS may provide suggestions from time to time based on profile information extracted from various sources concerning the user and also based on previous activities of the user. In event responsive mode, the MSS may provide notifications of events occurring that may affect the user's route. Events include accidents, amber alerts, and other emergencies. The MSS may notify the user of such events and provide rerouting information and adjust travel times. Further, in event responsive mode, the MSS may interact with the vehicle to obtain information concerning vehicle operation and provide suggestions based on vehicle operation. For instance, the vehicle may provide a low fuel signal to the MSS system which may trigger a route adjustment to the nearest fueling station.

The MSS may function and receive profits on a pay-per- visit or pay-per-patronage system. In such a system, when the suggestion clearinghouse provides an advertisement or a destination suggestion to a user, the MSS may track if and when the user goes to the location for which the advertisement was advertising. Only if the user goes to that location, which is tracked by the MSS, is the advertiser billed. For instance, a grocery store may sign up for pay-per- patronage advertising. If a user searches for grocery stores, the MSS may present an advertisement (audio based) for a particular store. If the user then goes to the store, the MSS may track this occurrence and accordingly bill the store for the fulfilled advertisement.

In some embodiments, the MSS may provide keyword-based interaction.

In some embodiments, the MSS includes a clearinghouse. The clearinghouse provides for enhanced opportunity of advertisers and providers to reach consumers in their vehicles. When the user accesses information concerning services or products that are part of an errand, the MSS may provide targeted results based on sales or special offers, the user's profile or habits, and fees paid by the advertiser.

Fig. 1 shows one embodiment of a MSS system 100. A driver in a vehicle 120 may operate a mobile computing device 130 such as a smart phone. Other types of devices may qualify as mobile computing devices 130, including laptops, tablets, smart phones, and computing systems installed in the vehicle. The mobile computing device 130 may communicate with the user through the microphone and audio output of the mobile computing device 130. Alternatively, the mobile computing device 130 may connect with a car's Bluetooth® and other systems 115 and utilize the speaker and microphone of the vehicle to communicate with the user. Additionally, the mobile computing device may connect to the CAN bus of the vehicle. This connection may occur according to a variety of methods. The mobile computing device 130 includes various software modules which enable the operation of the MSS. The mobile computing device 130 may communicate over a network 140 with suggestion clearinghouse 150 and a profile collector 160. In some embodiments, suggestion clearinghouse 150 and profile collection 160 may be unified. In many embodiments, network 140 includes the Internet and a mobile phone network; however, other network configurations are possible.

Fig. 2 shows one embodiment of a vehicle-based view of the implementation of the MSS. Mobile computing device 240 may be placed by the user in the vehicle when traveling (or in some embodiments may remain in the users' pocket or purse). The MSS may function solely by interaction with mobile computing device 240. In other embodiments, however, the mobile computing device 240 may be connected via a Bluetooth® system to the vehicle, such that the user may utilize Bluetooth® buttons 220 to communicate with the MSS system. Additionally, the vehicle may include a special MSS button 225 for activating the MSS during hands-free operation. The vehicle's Bluetooth® buttons 220 and/or the MSS button 225 and the accompanying system may be programmed to accept commands from the MSS software modules running on the mobile computing device 240. In this way, the user may interact with the MSS in a hands-free manner. Additionally, the mobile computing device 240 may additionally interact with the CAN bus of the vehicle and may allow the MSS to control and interact with radio, displays, and other car systems 230. In this way, the MSS may enable the user to control the radio, displays, and other car systems 230 and receive small amounts of visual data on the radio, displays, and other car systems 230. Additionally, the system may include an NFC communication chip located in an area where the user may place the mobile computing device 240. In the embodiment shown in Fig. 2, an NFC chip is located in a mobile charging pad 220. This may provide for additional data transfer between the vehicle systems and the mobile device 240. The mobile device 240 may include a flexible operating system such as the iPhone's iOS® or the Android® operating system, or any other operating system that allows the installation of customized code or applications. Smart phone 240 may include an application or app designed to work with the charging pad 220 and button 225. The application then may communicate with a remote decoder server via a data network provided by the smart phone 240. In some configurations, the smart phone 240 may use the Bluetooth® system of the vehicle. In either configuration, the user may be prompted to issue voice commands via the Bluetooth® system.

The operations of the MSS system may be easily explained in terms of use cases. The following use cases may be implemented as part of the MSS alone or together, including one or more of the provided use cases and modules or software code to implement such use cases.

Vehicle Interaction

In the vehicle interaction use case, a mobile device implementing code for activating the MSS may include instructions for interacting with the vehicle. Various aspects of the vehicle may be monitored. Aspects include, but are not limited to, the fuel efficiency of the vehicle, the amount of gas in the vehicle, the need for vehicle maintenance (like oil changes), the driver settings, such as seat and mirror positioning, and the performance of the driver. The mobile device may interact with the vehicle via a variety of short range communication protocols including, but not limited to, Bluetooth® and NFC. A wide variety of communications systems may be used in all of the embodiments described herein including, but not limited to, Bluetooth®, Bluetooth Low Energy®, and Near Field Communication protocols, as well as ANT+, Cellular, IEEE 802.15.4, IEEE 802.22, ISA 100a, Infrared, ISM band, RFID, 6L0WPAM, UWB, Wi-Fi, Wireless HART, WirelessHD, Wireless USB, ZigBee®, and Zee- Wave®, as well as many other communications protocols. Due to the particular configuration of the system, it is thought that Bluetooth®, Bluetooth LE®, and NFC present the most natural technical fit (since many devices already incorporate these technologies), although other short range communication systems are possible. In the vehicle interaction embodiment, it is thought that the Bluetooth® or NFC protocols are well suited. In particular, a charging pad including an NFC chip may be utilized. When the user enters the vehicle and places their mobile device 240 on the charging pad 220 as shown in Fig. 2, the vehicle interaction protocols may begin to activate.

In Fig. 3a in step 302, a mobile communication device is placed in range of a short range communication sensor. In step 304, the sensor detects the device, in many embodiments via NFC. The mobile computing device, in step 306, includes a record of the seat, climate control, and mirror configurations of the vehicle and communicates the settings via short range communication to the vehicle CAN bus. In step 308, the CAN bus configures the vehicle accordingly. This may be driven by microprocessors and software modules in the vehicle itself or in the mobile device. In step 310, the CAN bus and mobile device monitor can communicate any adjustments that the user makes to the vehicle seat, climate control, and mirror configurations and saves those configurations for future implementation through steps 302 - 306.

In Fig. 3b in step 302, a mobile communication device is placed in range of a short range communication sensor. In step 304, the sensor detects the device, in many embodiments via NFC. In step 312, the CAN Bus of the vehicle may periodically or constantly transmit fuel efficiency information. In optional step 314, this information may be matched with driving route information. In many cases when this information is for routes consistently driven by the user, the MSS may report to the user areas of the route where the driver did not drive in an efficient manner. In step 316, efficiency information is reported to the user. This may be via email, web page, or voice interaction in the vehicle. The MSS may provide tips to the user for driving more efficiently.

In Fig. 3c in step 302, a mobile communication device is placed in range of a short range communication sensor. In step 304, the sensor detects the device, in many embodiments via NFC. In step 318, the CAN Bus of the vehicle may periodically or constantly transmit driver performance information to the MSS of the mobile device. The mobile device may store this locally or in a remote server. This information may include acceleration and deceleration, as well as turning speed and radius. In optional step 320, this information may be correlated with route information in order to provide to the user more specific feedback concerning the driving of particular routes. In step 322, the user is provided with feedback concerning their driving performance. This may be via email, web page, or voice interaction in the vehicle. The MSS may provide tips to the user for driving more efficiently. Based on acceleration and deceleration, the MSS may determine when the user is driving too aggressively and notify the user of areas of a route where accident danger may be higher due to this driving style.

In Fig. 3d in step 302, a mobile communication device is placed in range of a short range communication sensor. In step 304, the sensor detects the device, in many embodiments via NFC. In step 324, the CAN Bus of the vehicle may periodically or constantly transmit information concerning fuel supply and/or maintenance to the MSS modules executing in the mobile device. In step 326, when the fuel is low or there is a need for maintenance, the MSS may notify the user with a sound-based language communication (e.g., "fuel level low"). In optional step 328, the MSS may inquire with the user whether the user desires gas station location or maintenance operations reservations. In step 330, the MSS may interrogate a clearinghouse that may provide targeted advertisements for nearby gas or service stations. In step 332, these advertisements or suggestions may be provided to the user; and the MSS may offer to provide and subsequently provide driving instructions to the gas or service station. Alternatively, the MSS may inquire as to whether the user desires to call the service station utilizing the Bluetooth® communication system and thereby allow the user to make maintenance reservations.

In alternative embodiments, the MSS may further interact with the CAN bus and record information concerning radio station utilization by the user. The MSS may monitor which stations the user listens to more often and may automatically adjust presets accordingly. Alternatively, the MSS may make suggestions to the user for new presets or stations based on what stations are listened to frequently or related stations that the user may like. In the case of satellite radio, with the large number of stations available, the user may not be aware of a large number of stations available. The system may sense when the user is stopped at a light or otherwise not operating the vehicle, based on GPS and accelerometer detection from the MSS, and inquire concerning preset changes during this period. This inquiry may be voice-based through the Bluetooth® or other communication system of the vehicle. Such setting configuration may occur for any of the systems described herein. Route and Destination Storage and Communication

The MSS constantly collects data concerning user actions in the vehicle. Based on this connection, the MSS may communicate with a profile server and build a profile of common destinations of the user. Locations at which the user spends typically day-long shifts multiple times per week may be determined to be work. The MSS may record routes typically driven by the user to a variety of destinations. The MSS also may record when these routes typically are driven. During in-transit operation, the MSS may anticipate the route that will likely be taken by the user. If, based on navigation, traffic, and other information known by the MSS, the MSS determines that an alternate route would be more efficient, the MSS may notify the user and make alternative navigation suggestions. The MSS may correlate commonly-driven routes and destinations with location information. For instance, if a user frequently drives a certain route to a grocery store, this route and the location of the grocery store may be defined as the primary grocery store for the user automatically. This may hold true for work and leisure locations, shopping locations, and the locations of friends and relatives.

Pre-travel

In pre-travel mode, the MSS may predict what action the user is likely to take based on previous routes recorded and the times those routes were driven. For instance, in Fig. 4a in step 410, a mobile device including an application for the MSS may receive an indication from a profile server that a particular route typically is driven at a time in the near future. In step 420, the profile server provides information concerning travel conditions to the mobile device and whether the route is likely to take any longer to drive. In step 430, the mobile device notifies the user via any of a variety of protocols and indications concerning any change in typical travel time. In Fig. 4b in step 440, a mobile device including an application for the MSS may receive an indication from a profile server that a particular route is typically driven at a time in the near future. In step 450, it is determined that this route includes an advertising opportunity. An advertising opportunity may include times when the user typically does a particular type of shopping, such as grocery shopping. In step 450, a clearinghouse is interrogated by the mobile device for special sales or offers. Note that the separate clearinghouse and profile server structure is purely exemplary, and the two may be combined. In step 460, those sales or offers are presented to the user. These sales or offers may be presented via audio suggestion when the user leaves for an errand in a vehicle or may be merely messages indicated on the mobile device, or a variety of different contact means.

Startup

In startup mode, the MSS follows a protocol as shown in Fig. 5a. In step 510, it is determined that the user is beginning to travel in a vehicle. This step may include the user placing their mobile device in a charging pad including an NFC chip in many embodiments. In such a configuration, the mobile device, including software modules for executing the MSS, detects the NFC chip and forms a communication link with the vehicle. The detection of the NFC chip in the charging pad may trigger the startup mode. Alternatively, this linking may include Bluetooth® linking to the vehicle. Alternatively, the mobile device may solely detect to begin startup mode, based on Bluetooth® linking. Alternatively, location detection systems of the mobile device include, but are not limited to, GPS receivers, accelerometers, WiFi, and other communications network protocols. In step 520, the MSS requests destination information from the user. In many embodiments, this is the form of an audio question. This may be accomplished via the speakers of the vehicle through a Bluetooth® system or the speakers of the mobile device. In step 530, the MSS receives a destination or command from the user. This may be accomplished using the microphone of the vehicle through a Bluetooth® system or the microphone of the mobile device. In step 540, the MSS analyzes the destination or command provided by the user. In step 550, the MSS returns and communicates content to the user. The content may take many forms, based on the destination or command provided by the user.

Fig. 5b shows a flow chart for determining what content to return to the user. In step 555, it is determined that the user indicated their destination was work. In step 560, the MSS returns estimated travel time and the difference in travel time as compared to normal travel time. In step 565, the MSS returns the availability of alternative directions from the user's normal route as recorded related to the profile for the user. In many configurations, these alternatives are only provided if the alternative route of travel estimated time is less than the user's normal route. In step 570, it is determined that the user desires to visit a commercial enterprise. From step 570, the flow may proceed to steps 560 and 565 in order for the user to receive optimal route information. Alternatively, the flow may proceed to step 575. In step 575, the software module executing on the mobile device accesses the suggestion clearinghouse via a mobile data network and retrieves advertising, fulfillment suggestions, and coupons. For instance, the system may verbally suggest restaurants in the area or offer to provide a voice interface for accessing reservation options through a service such as Open Table®. For instance, in the case of wine, the system may provide information, through audio communication, concerning discounts at wine stores on the user's route. Alternatively, the system may provide audio information concerning a discount or may send a QR code coupon to the user's mobile device.

In step 580, it is determined that the user needs emergency services. In step 585, the MSS provides a verbal indication to the user questioning whether they want driving directions or whether they want to call the emergency services.

In-transit

In-transit interaction with the MSS functions in essentially the similar fashion as startup. The user may issue voice commands concerning desired information or destinations. One additional feature of the MSS in-transit is that the MSS may locate services along the route that the user is known to be traveling or merely nearby.

Event Responsive

The MSS may include the option for the user to put the system in a standby mode or completely deactivate the MSS. In standby mode, the user may not be interacting with the system, and the MSS may not be providing any information to the user. Even in standby mode, the MSS may be actively determining what route the user is likely traveling based on the user's profile information or routes commonly travelled. In either standby mode or when the user is in the process of utilizing the MSS from in-transit mode or from startup mode, the MSS may receive notifications concerning events along the user's likely route of travel. In one configuration, these events are accidents, amber alerts, or emergencies. In both standby and in- transit modes, or from start-up mode, the MSS may notify the user of these events and provide the opportunity to receive alternative routing information.

Suggestion Clearinghouse

Many embodiments of the MSS may include a suggestion clearinghouse. The suggestion clearinghouse may be a server or group of servers with which the software modules resident on the user's mobile device may communicate. The suggestion clearinghouse may work on a variety of configurations. In one configuration, the suggestion clearinghouse may conduct location-based searches near a user' s route responsive to the destination provided by the user. In another configuration, businesses may be provided a geographically limited right to have their business suggested when the user provides certain keyword destinations. Since the MSS system tracks where the user goes, it is easily determined whether the user utilizes the ad. Upon utilization, the owner of the MSS system or suggestion clearinghouse may receive a payment (a return revenue or pay per actual visit, similar to pay-per-click, but the suggestion clearinghouse gets paid when the user actually visits the business as determined by the MSS's tracking) for the presentation of the suggestion. If more than one company desires to have their business associated with a particular keyword, then various systems for resolution are possible, including random presentation of those bidding for a keyword, semi-random presentation of those bidding for a keyword where those businesses that are preferred over all or those that are preferred according to a user's profile are presented more often, return revenue bidding where companies that bid the highest in relation to the amount they will pay if a customer goes there, or other protocols.

In many situations, while a user is operating a vehicle, he or she may not be able to properly utilize a smart phone due to safety and legal (hands-free laws) constraints. The user may be unable to effectively operate their smart phone. Various embodiments of systems and methods described herein may be implemented fully or partially in software and/or firmware. This software and/or firmware may take the form of instructions contained in or on a non- transitory computer-readable storage medium. Those instructions then may be read and executed by one or more processors to enable performance of the operations described herein. The instructions may be in any suitable form such as, but not limited to, source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. Such a computer- readable medium may include any tangible non-transitory medium for storing information in a form readable by one or more computers such as, but not limited to, read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; a flash memory, etc.

Embodiments of systems and methods described herein may be implemented in a variety of systems including, but not limited to, smartphones, tablets, laptops, and combinations of computing devices and cloud computing resources. For instance, portions of the operations may occur in one device, and other operations may occur at a remote location, such as a remote server or servers. For instance, the collection of the data may occur at a smartphone, and the data analysis may occur at a server or in a cloud computing resource. Any single computing device or combination of computing devices may execute the methods described.

Although the foregoing description is directed to certain embodiments, it is noted that other variations and modifications will be apparent to those skilled in the art, and may be made without departing from the spirit or scope of the disclosure. Moreover, features described in connection with one embodiment may be used in conjunction with other embodiments, even if not explicitly stated above.

Claims

WHAT IS CLAIMED IS:

1. A method for hands-free advertising and pay-per-patronage revenue, the method comprising:

providing an application resident in a mobile device;

receiving at the application an information request from a user in a vehicle; contacting a suggestion clearinghouse with the information request from the application;

processing the information request at the suggestion clearinghouse;

returning information to the user, the information including a destination; detecting the user in the vehicle went to the destination; and

billing a company associated with the destination on the basis of the detecting.

2. The method of claim 1, wherein the information request is a destination.

3. The method of claim 1, wherein the information request is a product.

4. The method of claim 1, wherein the information request is a keyword representative of a destination selected from a group of keywords.

5. The method of claim 4, wherein the group of keywords includes gas station, service station, grocery store, and liquor store.

6. The method of claim 5, wherein the group of keywords includes electronics store, bank, and clothing store.

7. The method of claim 1, wherein the application is an app and the mobile device is a smart phone.

8. The method of claim 1, further comprising:

receiving from the company an advertisement at the suggestion clearinghouse, wherein the information returned to the user is the advertisement.

9. The method of claim 1, further comprising:

providing an audio request from the application resident in the device to the user, wherein the information request is responsive to the audio request.

10. The method of claim 9, further comprising:

triggering the audio request from the application resident in the device to the user, based on detecting the user is in a vehicle.

11. The method of claim 10, further comprising:

linking the mobile device to an NFC chip in the vehicle, wherein the linking causes the application resident in a mobile device to provide the audio request.

12. The method of claim 10, wherein detecting the user is in a vehicle is based on GPS feedback from the mobile device.

13. The method of claim 10, wherein detecting the user is in a vehicle is based on accelerometer feedback from the mobile device.

14. The method of claim 11, wherein the NFC chip is located in a charging pad.

15. A method for hands-free assistance, comprising:

providing an application resident in a mobile device;

receiving at the application an information request from a user in a vehicle; and providing, to the user through audio communication from the mobile device, route information based on the information request.

16. The method of claim 15, wherein the route information includes predicted travel time as compared to average travel time.

17. The method of claim 15, wherein the route information includes information concerning accidents or delays along a route related to the information request.

18. The method of claim 15, wherein the information request is a destination.

19. The method of claim 15, further comprising:

20. The method of claim 19, further comprising:

21. The method of claim 20, further comprising:

22. The method of claim 20, wherein detecting the user is in a vehicle is based on GPS feedback from the mobile device.

23. The method of claim 20, wherein detecting the user is in a vehicle is based on accelerometer feedback from the mobile device.

24. The method of claim 21, wherein the NFC chip is located in a charging pad.

25. A system for hands-free assistance, comprising:

an application on a mobile device, the application configured to: receive, at the application, an information request from a user in a vehicle; and provide, to the user through audio communication from the mobile device, route information based on the information request.

26. The system of claim 25, wherein the application further is configured to:

provide an audio request from the application resident in the device to the user, wherein the information request is responsive to the audio request.

27. The system of claim 25, wherein the application further is configured to:

trigger the audio request from the application resident in the device to the user, based on detecting the user is in a vehicle.

28. The system of claim 27, wherein the application further is configured to:

link the mobile device to an NFC chip in the vehicle, wherein the linking causes the application resident in a mobile device to provide the audio request.

29. The system of claim 28, wherein detecting the user is in a vehicle is based on GPS feedback from the mobile device.

30. The system of claim 28, wherein detecting the user is in a vehicle is based on accelerometer feedback from the mobile device.

31. The system of claim 30, wherein the NFC chip is located in a charging pad.

32. A system for hands-free assistance, comprising:

an application on a mobile device, the application configured to:

receive at the application an information request from a user in a vehicle; contact a suggestion clearinghouse with the information request from the application;

process the information request at the suggestion clearinghouse;

return information to the user, the information including a destination; detect the user in the vehicle went to the destination; and

bill a company associated with the destination on the basis of the detecting.

33. A computer-readable non-transitory storage medium that contains instructions which, when executed by one or more processors, result in performing operations comprising:

receive at the application an information request from a user in a vehicle; contact a suggestion clearinghouse with the information request from the application; process the information request at the suggestion clearinghouse;

return information to the user, the information including a destination;

detect the user in the vehicle went to the destination; and

bill a company associated with the destination on the basis of the detecting.