Vehicle user experience enhancement

A vehicle comprises a processor programmed to: responsive to detecting a predefined event, transition a plurality of vehicle systems from a normal mode of operation to a quiet mode of operation, the transition including to adjust vehicle exhaust setting to a quiet mode, engage active noise cancellation, close vehicle windows, and adjust vehicle suspension to a predefined suspension mode.

TECHNICAL FIELD

The present disclosure generally relates to a system for enhancing vehicle user experience. More specifically, the present disclosure relates to a system for enhancing vehicle user experience by adjusting vehicle features.

BACKGROUND

Many modern vehicles are provided with advanced features to enhance user/occupant experience. For instance, an active exhaust system may turn up the exhaust sound in a sport mode and turn down the volume in a quite mode. Similarly, an adaptive suspension may adjust the response of suspension between stiff configuration for better handling and soft configuration for ride comfort.

SUMMARY

In one or more illustrative embodiment, a vehicle comprises a processor programmed to responsive to detecting a predefined event, transition a plurality of vehicle systems from a normal mode of operation to a quiet mode of operation, the transition including to adjust vehicle exhaust setting to a quiet mode, engage active noise cancellation, close vehicle windows, and adjust vehicle suspension to a predefined suspension mode.

In one or more illustrative embodiment, a method for a vehicle comprises detecting a predefined event; and transitioning a plurality of vehicle systems from a normal mode of operation to a quiet mode of operation by adjusting vehicle exhaust setting to a quiet mode, engaging active noise cancellation, closing vehicle windows, and adjusting vehicle suspension to a predefined suspension mode.

In one or more illustrative embodiment, a vehicle comprises a processor programmed to responsive to detecting a conversation involving at least one vehicle user, transition a plurality of vehicle systems from a normal mode of operation to a quiet mode of operation, the transition including to adjust vehicle exhaust setting to a quiet mode, engage active noise cancellation, close vehicle windows, and switch vehicle sound enhancement to a conducive mode.

DETAILED DESCRIPTION

The present disclosure, among other things, proposes a vehicle user experience enhancement system. More specifically, the present disclosure proposes a system configured to automatically adjust vehicle features such as exhaust and/or suspension settings responsive to a vehicle event to enhance the vehicle user experience. The vehicle event may include a phone call, a conversation among vehicle users, a user gesture, an evasive driving condition, an emergency situation, and/or vehicle entering a specific location. Further aspects of the disclosure are discussed in detail herein.

Referring toFIG. 1, an example block topology of a vehicle system100of one embodiment of the present disclosure is illustrated. Vehicle102may include various types of automobile, crossover utility vehicle (CUV), sport utility vehicle (SUV), truck, recreational vehicle (RV), boat, plane, or other mobile machine for transporting people or goods. In many cases, the vehicle102may be powered by an internal combustion engine. As another possibility, the vehicle102may be a hybrid electric vehicle (HEV) powered by both an internal combustion engine and one or move electric motors, such as a series hybrid electric vehicle (SHEV), a parallel hybrid electric vehicle (PHEV), or a parallel/series hybrid vehicle (PSHEV), a boat, a plane or other mobile machine for transporting people or goods. As an example, the system100may include the SYNC system manufactured by The Ford Motor Company of Dearborn, Mich. It should be noted that the illustrated system100is merely an example, and more, fewer, and/or differently located elements may be used.

As illustrated inFIG. 1, a computing platform104may include one or more processors112configured to perform instructions, commands, and other routines in support of the processes described herein. For instance, the computing platform104may be configured to execute instructions of vehicle applications108to provide features such as navigation, satellite radio decoding, and vehicle setting adjustments. Such instructions and other data may be maintained in a non-volatile manner using a variety of types of computer-readable storage medium106. The computer-readable medium106(also referred to as a processor-readable medium or storage) includes any non-transitory medium (e.g., tangible medium) that participates in providing instructions or other data that may be read by the processor112of the computing platform104. Computer-executable instructions may be compiled or interpreted from computer programs created using a variety of programming languages and/or technologies, including, without limitation, and either alone or in combination, Java, C, C++, C #, Objective C, Fortran, Pascal, Java Script, Python, Perl, and PL/SQL.

The computing platform104may be provided with various features allowing the vehicle occupants/users to interface with the computing platform104. For example, the computing platform104may receive input from human-machine interface (HMI) controls136configured to provide for occupant interaction with the vehicle102. As an example, the computing platform104may interface with one or more motion sensors138, buttons (not shown) or other HMI controls configured to invoke functions on the computing platform104(e.g., steering wheel audio buttons, a push-to-talk button, instrument panel controls, etc.).

The computing platform104may also drive or otherwise communicate with one or more displays116configured to provide visual output to vehicle occupants by way of a video controller114. The computing platform104may further drive or otherwise communicate with one or more cabin cameras118configured to provide visual input to the computing platform by way of the video controller114. In some cases, the display116may be a touch screen further configured to receive user touch input via the video controller114, while in other cases the display116may be a display only, without touch input capabilities. The computing platform104may also drive or otherwise communicate with one or more speakers122and microphones124configured to provide audio output and input to and from vehicle occupants by way of an audio controller120. The speaker112and microphone124may enable various features such as active noise cancellation and vehicle exhaust sound enhancement by the computing platform104.

The computing platform104may also be provided with navigation and route planning features through a navigation controller128configured to calculate navigation routes responsive to user input via e.g. the HMI controls136, and output planned routes and instructions via the speaker122and the display116. Location data that is needed for navigation may be collected from a global positioning system (GPS) controller126configured to communicate with GPS satellites and calculate the location of the vehicle102. Map data used for route planning may be stored in the storage106as a part of the vehicle data110. Alternatively, map data may be live streamed from the cloud with or without being stored in the storage106. Navigation software may be stored in the storage116as a part of the vehicle applications108.

The computing platform104may be configured to communicate with a mobile device140of the vehicle occupants via a wireless connection162. The mobile device140may be any of various types of portable computing device, such as cellular phones, tablet computers, smart watches, laptop computers, portable music players, or other device capable of communication with the computing platform104. In many examples, the computing platform104may include a wireless transceiver134in communication with a WiFi controller130, a Bluetooth controller132, and other controllers such as a Zigbee transceiver, an IrDA transceiver, an RFID transceiver (not shown), configured to communicate with a compatible wireless transceiver160of the mobile device140.

The mobile device140may be provided with communication capability via the wireless transceiver in communication with a WiFi controller150, a Bluetooth controller154and other controllers configured to communicate with a compatible wireless transceiver134of the computing platform104. The mobile device140may be further provided with capability to communicate with the wireless network190via a wireless connection194.

The mobile device140may be provided with a processor148configured to perform instructions, commands, and other routines in support of the processes such as navigation, calling, wireless communication, and multi-media processing. For instance, the mobile device140may be provided with location and navigation functions via a navigation controller158and a GPS controller156controlled by application as a part of a mobile application144stored in a non-volatile storage142. Map data used for navigation purposes may be stored in the storage142as a part of mobile data146. Alternatively, the mobile device140may be configured to download live map and traffic data from a remote server via a communication network190through a wireless connection194. For instance, the communication network190may be a cellular network. The mobile device140may be provided with various features allowing the vehicle occupants/users to interface with the mobile device140. For example, the mobile device140may receive input from human-machine interface (HMI) controls152configured to provide for occupant interaction with the mobile device140as well as the vehicle102.

The computing platform104may be further configured to communicate with various electronic control units (ECUs) via one or more in-vehicle network170. The in-vehicle network170may include, but is not limited to, one or more of a controller area network (CAN), an Ethernet network, and a media oriented system transport (MOST), as some examples.

The vehicle102may include multiple ECUs172configured to control and operate various functions of the vehicle102. As a few non-limiting examples, the ECUs172may include a telematics control unit (TCU)174configured to control telecommunications of the vehicles102. In many cases, the TCU174may include a modem (not shown) configured to communicate between the vehicle102and the communication network190. The ECUs172may further include a powertrain control module (PCM)176configured to control the powertrain of the vehicle102such as engine tuning and exhaust mode; and a body control module (BCM)178configured to operate various exterior and interior body functions of the vehicle102such as doors, windows and suspension modes.

The ECUs172may further include a body sensor module (BSM) configured to control and operate various sensors of the vehicle102. For instance, the BSM180may drive or otherwise communicate with one or more exterior microphones184, camera184, and radar186configured to provide audio, video and proximity input to the BSM180as well as the computing platform104. BSM180may further drive or otherwise communicate with one or more beacons188configured to enable the vehicle102to communicate with other vehicles. As an example, the beacon188may support dedicated short range communication (DSRC) technology to enable direct communication between multiple vehicles. The ECUs172may further include electronic stability controls (ESC)188configured to monitor the operation of the vehicle102and controls safety features such as anti-lock brakes (ABS) and traction controls.

Referring toFIG. 2, a flow diagram for a process200of a general embodiment of the present disclosure is illustrated. At operation202, computing platform104detects a predefined event. A few non-limiting examples of the predefined event may include an incoming/outgoing phone call; a conversation between vehicle occupants; a user gesture demanding quietness; an evasive driving situation; horns or sirens of outside vehicles; an outside image or sound; and/or a location detected by various sensors and inputs in communication with the computing platform104.

At operation204, the computing platform104checks whether all predefined vehicle settings are in predefined preference for the specific event detected at operation202. Vehicle settings may include vehicle exhaust mode; exhaust sound enhancement; active noise cancellation; suspension mode; windows setting; and/or convertible top (for convertible vehicles). Each setting may have a predefined preference for a specific event. For instance, in an event of an incoming phone call, the predefined configuration for the exhaust mode may be a quite mode for enhanced user experience. If at operation204, the computing platform all predefined vehicle settings are in predefined configurations, the process proceeds to operation206and no setting is changed. Otherwise, the process proceeds to operation208, and the computing platform104records current status/configuration for all settings for restoration purposes which will be discussed below. The recorded status/configuration may be stored in the storage106as a part of vehicle data110. Alternatively, the recorded status/configuration may be stored in ECU corresponding to the particular feature setting. In case that some settings are in predefined preference and some others are not, the computing platform104may only record those settings that are not in predefined preference.

At operation210, the computing platform104changes settings from current configurations to predefined configurations. Taking the above incoming phone call situation for instance, the computing platform104may switch the exhaust to the quietest mode, turn on active noise cancellation and switch the suspension to the most comfortable settings through various components and ECUs of the vehicle102to provide the best user experience for a phone call.

At operation212, the computing platform104detects the predefined event has passed and the process proceeds to operation214and the computing platform104restores settings to the previously recorded configurations loading the configurations from the storage106. Still using the above phone call example, the computing platform104may detect the phone call has ended and load the configurations previously stored in the storage at operation208to restore the exhaust mode, active noise cancellation and suspension to the previously configurations prior to receiving the incoming phone call.

The operations of process200may be applied to various situations. Referring toFIG. 3, a flow diagram for a process300of a phone call embodiment of the present disclosure is illustrated. At operation302, the computing platform104detects a phone call event while the vehicle102is being operated by a user. The phone call event may include an incoming or outgoing call by the mobile device140connected to the computing platform104via the wireless connection162using the Bluetooth controller132or other technologies. Alternatively, the phone call event may be initiated via the TCU174of the vehicle102without the mobile device140.

Responsive to detecting the phone call event, at operation304, the computing platform104determines whether the user experience enhancement feature is enabled. If the answer is a no, the process proceeds to operation306and no further action is performed. Otherwise, if the user experience enhancement feature is enabled, the process proceeds to operation308and the computing platform104determines whether the exhaust setting is at the predefined preference for phone calls. For instance, a predefined preference may be the quietest exhaust mode for the best phone call experience. If the computing platform104determines the current exhaust setting is not at the predefined preference, the process proceeds to operation310and the computing platform104set the exhaust to the preference setting after recording the current setting. The current exhaust setting may be recorded and stored in the storage106as a part of vehicle date110for further restoration purposes.

The computing platform104further checks whether the active noise cancellation is enabled at operation312. The active noise cancellation setting is correlated with vehicle sound enhancement sometimes. If the computing platform104determines that the active noise cancellation is not enabled, the process proceeds to operation314and the computing platform104turns on the active noise cancellation feature of the vehicle102. In addition, in case that the sound enhancement feature is available, the computing platform104may further records the current sound enhancement setting in the storage106and set to the most conducive mode if that is not the current case.

The computing platform104further checks whether the suspension setting is at the predefined preference at operation316. If that is not the case, the process proceeds to operation318and the computing platform318sets the suspension to the most comfortable mode which is the predefined preference after recording the current suspension setting.

The computing platform104further checks whether all windows (including the sun/moon roof if available) of the vehicle102are closed via the BCM178at operation320. If not all windows are closed, the process proceeds to operation322. The computing platform104records the current setting/status for all windows and close all windows for optimized phone call user experience.

In case that the vehicle102is convertible, the computing platform104further checks whether the convertible top is closed at operation324. If not, the computing platform104puts up the convertible top via the BCM178if the conditions allow. For instance, the convertible top may be closed if the vehicle102is operating within the speed limit allowing to close the top safely.

Depending on specific configurations of the vehicle102, more or less settings may be adjusted. At operation328, if the computing platform104determines that the phone call event has passed, the process proceeds to operation330and the computing platform104loads the recorded settings from the storage106to restore to the previous settings before the detection of the phone call event. The passing of the phone call event may be determined by the user hanging up the phone. Additionally or alternatively, a grace time period (e.g. 10 seconds after the hang up) may be used to confirm that the user is not making another phone call.

The operations of process200may be further applied to other situations such as a conversation between vehicle users. The computing platform104may be configured to enhance user experience responsive to detecting a conversation between the vehicle users via the microphone124by way of the audio controller120. Additionally or alternatively, the computing platform104may detect conversations between vehicle users using the mobile device140connected via the wireless connection162. Responsive to detecting the conversation, the computing platform may perform operations similar to process300to enhance the user conversation experience. For instance, the computing platform104may be configured to perform operations including set the exhaust to the quietest mode, turn on active noise cancellation, set sound enhancement to the most conducive mode, set suspensions to the most comfortable mode, close windows and/or put up convertible top. Responsive to the passing of the conversation, the computing platform104may revert all settings to previously recorded configurations. Similar to the phone call event example, a grace time period may be used to determine the passing of the conversation.

The operations of process200may be further applied to other situations such as detecting a gesture or motion made by a vehicle user instructing to enter quiet mode. The computing platform104may be configured to set the vehicle102to a preconfigured mode (e.g. quiet mode) responsive to detecting a user gesture or motion input via the motion sensor138or the cabin camera118. Referring toFIG. 4, an example vehicle dashboard diagram400of the present disclosure is illustrated. Among other things, the motion sensor138is provided near the infotainment display116above the center console of the vehicle102. Additionally, the cabin camera118may be provided near the rear-view mirror facing inward to capture images of the vehicle cabin. It is noted that the locations of the motion sensor136and the cabin camera118are merely examples and other appropriated locations may be used. The computing platform104may be configured to detect a hand gesture or motion402made by the vehicle user to trigger the process200. As illustrated inFIG. 4, the hand gesture or motion402may be an up and down motion previously configured into the computing platform104. For instance, a downward hand motion may indicate quiet mode and an upward hand motion may indicate restore from quiet mode to previously mode. Additionally or alternatively, the computing platform104may detect the user gesture or motion402using the cabin camera118with image processing software stored in the storage106as a part of vehicle applications108. Responsive to detecting the user gesture or motion402indicating quiet mode, the computing platform may perform the process similar to operations308-326to adjust the vehicle into a quiet mode to enhance user experience. To terminate the quiet mode, the vehicle user may perform a preconfigured gesture402, and the computing platform may restore the vehicle settings to the previous configuration in response. Alternatively, the trigger and restore feature of the computing platform104may be performed by voice commands using the microphone124by way of the audio controller120in addition to or instead of the gesture or motion detection.

The operations of process200may be further applied to other situations such as evasive driving. Referring toFIG. 5, a flow diagram for process500of the evasive driving embodiment of the present disclosure is illustrated. At operation502, the computing platform104detects an evasive driving event via the ESC188connected via the in-vehicle network170. For instance, the evasive driving may be detected via ESC188through evasive operations including engaging traction controls, antilock brakes, and/or stability controls.

Responsive to detecting the evasive driving, the computing platform104verifies whether the user is intentionally doing some special driving such as race track or autocross and has manually defeated the user experience enhancement settings at operation506. If that is the case, the process proceeds to operation506, and the computing platform104deactivates the user experience enhancement system and allows the user to continue the special driving. However, if the answer for operation504is a no, the process proceeds to operation508and the computing platform104performs user experience enhancement by recording current settings and change the settings to predefined preference. This operation is similar to operations308-326illustrated inFIG. 3, with a few differences. Instead of turning all setting to the quietest and comfortable mode, in this case, more concentration and control is desired to improve the user's chance to safely maneuver the vehicle102. For instance, the computing platform104may set the exhaust to the quietest mode, set active noise cancellation and sound enhancement to the most conducive mode helping the user concentrate, set the suspensions to the most controlled settings (e.g. firmest suspension setting), close all windows and put up convertible top (if applicable).

At operation510, responsive to detecting the evasive driving has passed, the computing platform104reverts settings to previously recorded configuration. Similarly, a time period may be used to determine the evasive driving has passed. For instance, the computing platform104may determine the evasive driving condition has passed 30 seconds after disengaging traction control or ABS by the ESC.

The operations of process200may be further applied to emergencies which may include various situations. For instance, the emergency situation may include emergency vehicles are nearby by detecting flash light and/or siren using the exterior camera184and/or microphone by way of the BSM180. The computing platform may further detect the emergency vehicle using the beacon188. For instance, the computing platform104may detect flash light from an emergency behind or near the vehicle102, indicating the vehicle102should stop or yield. In response, the computing platform104may perform operations similar to operation508inFIG. 5and adjust the vehicle102to help the user concentrate. After the emergency vehicle has passed, the computing platform104may revert to the previous configuration.

In addition, the emergency situation may further include detecting objects including human and animals using various sensors managed by the BSM180. For instance, the computing platform104may detect the vehicle102is approaching an animal (e.g. a deer) at high speed via the radar186, the camera184and/or the microphone182, and enable the user experience enhancement feature to help the user concentrate similar to the emergency vehicle case.