Integration of internal add-on modules into the driver user interface

Abstract

System (100), which includes: a display (116) that is integrated into a vehicle (102); a wireless transmitter-receiver (112); and a processor that is coupled with the display (116) and the transmitter-receiver (112), programmed to do so, to maintain a list of wireless, factory-installed in-vehicle components, to scan for wireless vehicle-internal auxiliary components within the vehicle (102) using the wireless transmitter-receiver (112), to create a user interface (300) that lists both the factory-installed wireless in-vehicle components and the wireless in-vehicle add-on components, and to provide the list for display (116), the processor is further programmed to: to receive a user input to the display (116) requesting a change in the state of one of the vehicle's internal components, and to use the wireless transmitter-receiver (112) to update the status of one of the vehicle's internal components, characterized in that the change of state is one of a vehicle-internal intelligence shading component rolling down or a vehicle-internal intelligence shading component rolling up.

Description

TECHNICAL FIELD

[0001] Aspects of the disclosure generally relate to the integration of internal add-on modules for the user interface of a head unit or other vehicle interface. BACKGROUND

[0002] Sales of personal devices such as smartphones and wearable devices continue to grow. As a result, users are increasingly using personal devices to interact with vehicles. Smartphones can already be used in some vehicle models to access a wide range of vehicle information, start the vehicle, and open windows and doors. Some wearable devices are capable of providing real-time navigation information to the driver. Manufacturers of such devices are implementing frameworks to enable more seamless integration of their brand of personal devices into the driving experience.

[0003] Bluetooth technology can be incorporated into various user devices to enable communication between them. BLE (Bluetooth Low Energy) is another wireless technology designed to facilitate data communication between devices. Compared to Bluetooth, BLE enables communication of smaller amounts of data with reduced energy consumption.

[0004] BLE devices can assume the roles of either a central device or a peripheral device. Central devices wirelessly scan for announcements from peripheral devices, while peripheral devices make the announcements. Once the peripheral device connects to the central device, the peripheral device can cancel the announcement, preventing other central devices from wirelessly identifying or connecting to it until the existing connection is terminated.

[0005] BLE devices transmit data using concepts known as services and characteristics. Services are collections of characteristics. A central device can connect to or access one or more of the characteristics of a peripheral device's service. Characteristics encapsulate a single value or data type with one or more bytes of data and zero or more descriptors describing the characteristic's value. The descriptors can include information such as human-readable descriptions, a range for the characteristic's value, or a unit of measurement for the characteristic's value. A Service Discovery Protocol (SDP) can enable a device to discover services offered by other devices and their associated parameters. The services can be identified by universally unique identifiers (UUIDs).

[0006] DE 10 2014 111 294 A1 discloses a method for using an integrated wireless image capture system in a vehicle according to the preamble of claim 1. US 2008 / 0 140 868 A1 discloses peripheral devices and data processing systems that can be configured to interact based on sensor data. SUMMARY

[0007] According to the invention, a system according to claim 1 is provided. Furthermore, the invention provides a method according to claim 6. Advantageous developments of the invention are the subject of the dependent claims. BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1A illustrates an example system including a vehicle with a network of in-vehicle components configured to interact with a vehicle computing system; Fig. 1B illustrates an example vehicle computing system equipped with a wireless transceiver configured to facilitate detection of and communication with in-vehicle components; Fig. 2A and Fig. 2B illustrate an exemplary removable in-vehicle accessory component; Fig. 3 illustrates an exemplary user interface for selecting applications for use on a display of the vehicle computing system; Fig. 4A illustrates an exemplary user interface of the vehicle component interface application illustrating in-vehicle components detected by the vehicle computing system; Fig. 4B illustrates an example user interface for controlling a factory-installed in-vehicle component; Fig. 4C illustrates an example user interface for controlling an in-vehicle auxiliary component; Fig. 5 illustrates an exemplary process for scanning for in-vehicle components by the vehicle computing system; and Fig. 6 illustrates an example process for displaying the user interface for controlling the in-vehicle components. DETAILED DESCRIPTION

[0008] As required, detailed embodiments of the present invention are disclosed herein; however, it is to be understood that the disclosed embodiments are merely exemplary of the invention that may be embodied in various and alternative forms. The figures are not necessarily to scale; some features may be exaggerated or minimized to show details of particular components. Therefore, specific details of structure and function disclosed herein are not to be interpreted as limiting, but merely as a representative basis for teaching those skilled in the art to variously employ the present invention.

[0009] Traditional vehicle interior components, such as reading lights or speakers, can be upgraded to incorporate a communication interface such as BLE. Because BLE has a relatively small processor footprint, processors in the internal components are able to integrate the functionality of the communication interface without requiring additional or more powerful processors. These enhanced vehicle interior components can also be referred to as in-vehicle components.

[0010] In-vehicle components may include components that are integrated into the vehicle at the factory. For example, factory-installed in-vehicle components may include skylights, speakers, and built-in headrest screens. Additionally, in-vehicle components may include aftermarket components that can be added to or removed from the vehicle by the vehicle occupants. These removable in-vehicle components may include, for example, car seats with integrated vibration or music functions or window shades with remotely controlled up / down functions. Because in-vehicle components can be installed or removed, the in-vehicle components available within the vehicle may change over time.

[0011] A vehicle computing system may include a communication interface such as a BLE. Using the communication interface, the vehicle computing system may be configured to discover, identify, and interact with the in-vehicle components located within the vehicle. The vehicle computing system may perform the discovery of the in-vehicle components periodically. For example, the vehicle computing system may also perform the discovery in response to a user command to re-identify the in-vehicle components or after another trigger condition such as a vehicle occupant entering the vehicle, after the key is turned, or after the initialization of the vehicle computing system itself.

[0012] The vehicle computing system may further provide a user interface in which the configuration of the in-vehicle components can be reviewed and adjusted. Accordingly, using information announced by the in-vehicle modules, the vehicle computing system may be able to provide a dynamic user interface describing the currently available in-vehicle modules and services. Furthermore, by using connectivity such as BLE, which does not require access to the vehicle bus, the development of the in-vehicle components can be performed independently of the development of the vehicle systems and without the validation required for components that access the vehicle bus.

[0013] Fig. 1A illustrates an example system 100 including a vehicle 102 having a network of in-vehicle components 106 configured to interact with a vehicle computing system 110. The system 100 may be configured to enable users, such as vehicle occupants, to use the vehicle computing system 110 to seamlessly interact with the in-vehicle components 106 within the vehicle 102 or with any other vehicle 102 enabled for the framework.

[0014] The vehicle 102 may include various types of automobiles, crossover utility vehicles (CUVs), sport utility vehicles (SUVs), trucks, camper vans, boats, aircraft, or other mobile machines for transporting people or goods. In many cases, the vehicle 102 may be powered by an internal combustion engine. Alternatively, the vehicle 102 may be a hybrid electric vehicle (HEV) powered by both an internal combustion engine and one or more electric motors, such as a series hybrid electric vehicle (SHEV), a parallel hybrid electric vehicle (PHEV), or a parallel / series hybrid electric vehicle (PSHEV). Since the type and configuration of the vehicle 102 may vary, the capabilities of the vehicle 102 may vary accordingly.Likewise, for example, the vehicles 102 may have different performance capabilities in terms of passenger capacity, traction power and capacity, and storage volume.

[0015] Personal devices 104-A, 104-B, and 104-C (collectively, 104) may include users' mobile devices and / or wearable devices. The mobile devices may be various types of portable computing devices such as mobile phones, tablet computers, smart watches, laptop computers, portable music players, or other devices capable of networked communication with other mobile devices. The wearable devices may include, as non-limiting examples, smart watches, smart glasses, fitness bands, control rings, or other personal mobility or accessory devices designed to be worn and communicate with the user's mobile device.

[0016] The in-vehicle components 106-A through 106-N (collectively 106) may include various elements of the vehicle 102 with user-configurable settings. These in-vehicle components 106 may include, for example, in-vehicle skylight components 106-A through 106-D, in-vehicle climate control components 106-E and 106-F, in-vehicle seat control components 106-G through 106-J, and in-vehicle speaker components 106-K through 106-N. Other examples of in-vehicle components 106 are also possible, such as entertainment screens for the rear row of seats or automated window shades. In many cases, the in-vehicle component 106 may display controls such as buttons, dials, and touchscreens that can be used by the user to configure the particular settings of the in-vehicle component 106.It is also possible that the controls of the in-vehicle component 106 allow the user to adjust a brightness level of a lighting control, adjust a temperature of a climate control, adjust a volume and audio source for a speaker, and adjust a seating position.

[0017] The interior of the vehicle 102 may be divided into a plurality of zones 108, where each zone 108 may be associated with a seating position within the interior of the vehicle 102. For example, the front row of the illustrated vehicle 102 may include a first zone 108-A associated with the driver's seating position and a second zone 108-B associated with a passenger's seating position. The second row of the illustrated vehicle 102 may include a third zone 108-C associated with a driver-side rear seating position and a fourth zone 108-D associated with a passenger-side rear seating position. Variations in the number and arrangement of the zones 108 are also possible. For example, an alternative second row may include an additional fifth zone 108 of a second-row middle seating position (not shown).Four vehicle occupants are shown inside the example vehicle 102, three of whom are using personal devices 104. A driver located in zone 108-A is not using a personal device 104. A passenger located in zone 108-B is using personal device 104-A. A rear driver-side vehicle occupant located in zone 108-C is using personal device 104-B. A rear passenger-side vehicle occupant located in zone 108-D is using personal device 104-C.

[0018] Each of the various in-vehicle components 106 present within the vehicle 102 may be associated with one or more of the zones 108. For example, the in-vehicle components 106 may be associated with the zone 108 in which the respective in-vehicle component 106 is located and / or with the one (or more) of the zones 108 controlled by the respective in-vehicle component 106. For example, the in-vehicle light component 106-C, which is accessible by the passenger, may be associated with the second zone 108B, while the in-vehicle light component 106-D, which is accessible from the rear passenger side thereof, may be associated with the fourth zone 108D. It should be noted that the illustrated portion of the vehicle 102 in Fig. 1A is merely an example and that more or fewer and / or differently arranged in-vehicle components 106 and zones 108 may be used.

[0019] The vehicle computing system 110 may be configured to provide telematics services to the vehicle 102. These services may include, as some non-limiting examples, navigation, route guidance, vehicle maintenance status, local business locator, accident reporting, and hands-free calling. In one example, the vehicle computing system 110 may include the SYNC system manufactured by The Ford Motor Company, Dearborn, MI.

[0020] With reference to Fig. 1B, the vehicle computing system 110 may interface with a wireless transceiver 112 configured to communicate with the in-vehicle components 106 disposed within the vehicle 102. In one example, the wireless transceiver 112 may support communication via Bluetooth and / or BLE.

[0021] The vehicle computing system 110 may also receive input from human-machine interface (HMI) controls 114 configured to provide for the interaction of the vehicle occupants with the vehicle 102. For example, the vehicle computing system 110 may interface with one or more buttons or other HMI controls 114 configured to activate functions on the vehicle computing system 110 (e.g., steering wheel audio buttons, a talk button, an instrument panel control, etc.). The vehicle computing system 110 may also drive or otherwise communicate with one or more displays 116 configured to provide visual output to the vehicle occupants. In some cases, the display 116 may be a touchscreen further configured to receive user touch input (e.g.,Operation as an HMI controller 114), while in other cases the display 116 may only be an output device without also having input capabilities.

[0022] The vehicle computing system 110 may be further configured to communicate with other components of the vehicle 102 via one or more in-vehicle networks. The in-vehicle networks may include, for example, one or more of a Vehicle Controller Area Network (CAN), an Ethernet Network, and a Media Oriented System Transfer (MOST). The in-vehicle networks may enable the vehicle computing system 110 to communicate with other vehicle systems, such as a vehicle modem (which may not be present in some configurations), a Global Positioning System (GPS) module configured to provide current vehicle location and heading information, and various other vehicle controls.

[0023] Each in-vehicle component 106 may also be equipped with a wireless transceiver 118. The wireless transceiver 118 may be configured to facilitate communication with the in-vehicle computing system 110. In one example, the wireless transceiver 118 may comprise a wireless device such as a Bluetooth Low Energy transceiver. In one example, the wireless transceiver 112 of the in-vehicle computing system 110 may communicate data with the wireless transceiver 118 of the in-vehicle component 106 via a wireless connection 120. The wireless connections 120 may be a BLE connection, but other types of local wireless connections 120 may also be used.

[0024] The vehicle component interface application 122 may be an application installed in the vehicle computing system 110. The vehicle component interface application 122 may be configured to facilitate vehicle occupant access to features of the in-vehicle components 106 enabled for networked configuration via the wireless transceiver 118. In some cases, the vehicle component interface application 122 may be configured to identify the available in-vehicle components 106 and maintain an in-vehicle component list 124 of the available in-vehicle components 106. In one example, the in-vehicle component list 124 may include a list of factory-installed wireless in-vehicle components 106 as well as a list of wireless in-vehicle add-on components 106 detected by the vehicle component interface application 122.The vehicle component interface application 122 may also be configured to identify the available features and current settings of the identified in-vehicle components 106. The vehicle component interface application 122 may be further configured to display a user interface describing the available features of the in-vehicle components 106 on the in-vehicle component list 124, receive user input, and provide commands to the in-vehicle components 106 based on the user input to enable the user to control the features of the in-vehicle components 106. Thus, the system 100 may be configured to enable vehicle occupants to seamlessly interact with the in-vehicle components 106 within the vehicle 102.

[0025] The vehicle component interface application 122, executed by the vehicle computing system 110, may be configured to scan and update the in-vehicle component list 124 of available in-vehicle components 106. For example, the scanning may be performed periodically, in response to a user request to refresh, or upon activation of the vehicle component interface application 122. In examples where the scanning is performed automatically, the correct feature set is continuously refreshed, and the user interface of the vehicle component interface application 122 is updated to reflect changes in the installed or removed in-vehicle components 106.

[0026] The Fig. 2A and Fig. 2B illustrate a removable in-vehicle accessory component 106. As in Fig. As shown in Figure 2A, the removable in-vehicle component 106 is a smart shade for attachment to a window of the vehicle 102. The in-vehicle smart shade component 106 may include a motor 202 for raising and lowering the shade, semi-rigid connected side rods 204 for stretching the shade material to open and folding it to close, and expandable anchors 206 for holding the shade in place. The in-vehicle smart shade component 106 may further include a controller 208 programmed to command the motor 202 to open and close.

[0027] As shown in the block diagram of the Fig. 2B, the smart shade may further include other components such as an ultraviolet or other light sensor 210 configured to monitor light conditions and provide light intensity information to the controller 208. The controller 208 may utilize the control logic 212 to enable the controller to automatically open and close the shade. For example, the control logic 212 may include a first light threshold above which the controller 208 commands the motor 202 to close the shade and a second light threshold below which the controller 208 commands the motor 202 to open the shade. The controller 208 may also be programmed to command the motor 202 according to user input to the smart shade controls 214.In one example, the controls 214 may include open and close buttons that, when selected, send signals to the controller 208 to command the shade to raise or lower. The control logic 212 may accordingly receive the signals from the controls 214 and command the motor 202 to raise or lower the shade. The controller 208 may also be programmed to receive wireless commands from the wireless transceiver 118 to control the shade, as well as to command the wireless transceiver 118 to broadcast information regarding the available functions and the current status of the smart shade (e.g., open, closed, etc.).

[0028] Fig. 3 illustrates an exemplary user interface 300 for selecting applications for use on a head unit display 116 of the vehicle computing system 110. The head unit display 116 may be driven, for example, by a video connection to the vehicle computing system 110 of the vehicle 102. The user interface 300 may include a category list 302 of one or more screen contents to be displayed in the main screen area 304 of the head unit display 116.For example, the category list 302 may include an audio screen from which the configuration of the audio settings of the vehicle 102 may be performed, a climate control screen from which the climate control settings of the vehicle 102 may be configured, a phone screen from which call services may be used, a navigation screen from which maps and route guidance may be performed, an application screen from which installed applications may be activated, and a settings screen from which the backlight or other general settings of the head unit display 116 may be accessed.The user interface 300 may also include a general information area 306 from which time, current temperature, and other information remain visible to the user regardless of the specific screen or application active in the main screen area 304.

[0029] As shown, the application screen is depicted as selected from the category list 302, and the main screen area 304 is depicted as displaying a list of available applications that can be activated. These applications may include, for example, an application item for finding new applications 308-A, an internet radio item 308-B, a satellite radio item 308-C, a streaming radio item 308-D, an icon 308-E for selecting the vehicle component interface application 122, a map item 308-F, a news icon 308-G, and a weather icon 308-G. To activate the vehicle component interface application 122 to control the in-vehicle components 106, the user may select the icon 308-E from the user interface 300.

[0030] Fig. 4A illustrates an exemplary user interface 400-A of the vehicle component interface application 122, illustrating the in-vehicle components 106 detected by the personal device 104. As shown, the user interface 400-A of the vehicle component interface application 122 may be presented on the display 116 of the vehicle computing system 110 and may include a list 402 configured to display selectable list items 404-A through 404-D (collectively 404) indicating the identified in-vehicle components 106. Each of the selectable list items 404 may display a family of detected in-vehicle components 106 available for configuration by the user. Thus, the selectable list entries 404 may be based on the in-vehicle components 106 maintained by the vehicle computing system 110 on the in-vehicle component list 124.The user interface 400-A may also include a title label 406 to indicate to the user that the user interface 400-A displays a menu of the in-vehicle components 106 as detected by the vehicle component interface application 122.

[0031] As illustrated, the list 402 of the vehicle component interface application 122 includes an entry 404-A for an in-vehicle shading component 106 (e.g., one as described above with reference to the Fig. 2A and Fig. 2B), an entry 404-B for an in-vehicle lighting component 106, an entry 404-C for an in-vehicle seating component 106, and an entry 404-D for an in-vehicle climate control component 106. In particular, the list 402 may include a unified list of both factory-installed in-vehicle components 106 and in-vehicle add-on components 106. The list 402 may also operate as a menu such that a user of the user interface 400-A is able to scroll through the list items of the list control 402 (e.g., using up and down arrow keys and a selection button to activate a selected menu item). In some cases, the list control 402 may also be presented on a touchscreen such that the user can touch the list control 402 to select and activate a menu item.As another example, user interface 400-A may support voice command selection of menu items. For example, to activate the options of the in-vehicle lighting component 106, the user may speak the voice command "LIGHT." It should be noted that the illustrated entries 404 are merely examples, and that multiple or different in-vehicle components 106 may be available.

[0032] Fig. 4B illustrates an exemplary user interface 400-B for controlling a factory-installed in-vehicle component 106. User interface 400-B may be provided to the display 116 of the vehicle computing system 110. In one example, user interface 400-B may display functions of an in-vehicle lighting component 106 in response to user input to entry 404-B in user interface 400-A. User interface 400-B may also include title labels 406 to indicate to the user that user interface 400-B displays functions of the selected in-vehicle lighting component 106.

[0033] As shown, user interface 400-B may include a list 408 configured to display selectable controls 410-A through 410-C (collectively 410) based on the characteristics of the identified in-vehicle components 106. Each of the selectable controls 410 may report a function of the reported in-vehicle component 106 that is available for configuration by the user. User interface 400-B may also include a title label 308 to alert the user that user interface 400-B is displaying a menu of functions of the reported in-vehicle component 106. In some cases, when title label 308 is selected, user interface 400-B may reference user interface 300 to allow the user to return to the list of currently active in-vehicle components 106.

[0034] As illustrated, list 408 includes a control 410-A for turning the light of in-vehicle component 106 on and off, a control 410-B for specifying an intensity of in-vehicle light component 106, and a control 410-C for specifying a color of the light of in-vehicle component 106. List 408 may also provide scrolling in cases where there are multiple controls 410 visually represented simultaneously in display 116. In some cases, control 410 may be displayed on a touchscreen so that the user can touch controls 410 to make adjustments to the functions of in-vehicle component 106. As another example, user interface 400-B may support voice commands. For example, to turn on the light, the user may speak the voice command "LIGHT ON" or simply "ON."It should be noted that the illustrated controls 410 are merely examples, and multiple or different functions or layouts of the functions of the in-vehicle component 106 may be utilized.

[0035] It should be noted that while the controls 410 of the user interface 400-B include a toggle switch to turn the light on and off and two dials used to adjust the intensity and ambient color based on the characteristics, the actual physical in-vehicle component 106 may include a different user interface 400-B. For example, the in-vehicle component 106 may include a simpler user interface, such as a single mechanical or proximity switch to turn the light on and off, so that the vehicle occupant is not dependent on the use of the vehicle computing system 110 to utilize the basic functions of the in-vehicle component 106.

[0036] In some examples, user interface 400-B may further include a zone interface 412 to enable a user of display 116 to switch among in-vehicle components 106 within different zones 108. As one option, zone interface 412 may include a control 414-A for selecting a driver-side rear zone 108-C and a control 414-B for selecting a passenger-side rear zone 108-D (collectively, controls 414). Accordingly, in response to selecting one of controls 414, user interface 400-B may display the controls 410 of the corresponding in-vehicle component 106 for the selected zone 108. For example, if the lighting control is currently displayed in zone 108-C and the user selects control 414-B to display the corresponding control for zone 108-D, user interface 400-B may display the lighting control functions for zone 108-D.

[0037] Fig. 4C illustrates an example user interface 400-C for controlling an in-vehicle add-on component 106. As with user interface 400-B, user interface 400-C may also be provided to the display 116 of the vehicle computing system 110. In one example, user interface 400-B may display functions of an in-vehicle shading component 106 in response to user input to entry 404-A in user interface 400-A. User interface 400-C may also include title label 406 to indicate to the user that user interface 400-C displays functions of the selected in-vehicle shading component 106. Thus, vehicle component interface application 122 may provide a consistent user interface across the factory-installed and in-vehicle add-on components 106.

[0038] As illustrated, list 408 includes a controller 410-A for turning the shade of in-vehicle component 106 on and off and a controller 410-B for specifying a position of the shade (e.g., how high or low the shade should be positioned). In response to user input to controller 410-A or controller 410-B, vehicle computing system 110 may wirelessly command in-vehicle shade component 106. In one example, if the user selects to adjust the shade position using controller 410-B, vehicle computing system 110 may utilize wireless transceiver 112 to send a wireless command directed to wireless transceiver 118 of in-vehicle shade component 106.The controller 208 of the in-vehicle shading component 106 can accordingly receive the command and utilize the control logic 212 to instruct the motor 202 to raise or lower the shade to the desired position. In particular, these operations can be performed without requiring the vehicle computing system 110 or the in-vehicle shading component 106 to communicate with each other via the vehicle bus.

[0039] Fig. 5 illustrates an example process 500 for scanning for in-vehicle components 106 by the vehicle computing system 110. In one example, the process 500 may be performed by the vehicle computing system 110 executing the vehicle component interface application 122.

[0040] In operation 502, the vehicle computing system 110 performs the scanning. In one example, a scanning service of the vehicle component interface application 122 executed by the vehicle computing system 110 may utilize the wireless transceiver 112 to scan for BLE advertisements. Triggering the scanning may, in one example, be performed periodically. In some other examples, the vehicle computing system 110 may perform the discovery in response to a user command to re-identify in-vehicle components 106, or after another trigger condition, such as an occupant entering the vehicle 102, turning the key of the vehicle 102, or initializing the vehicle computing system 110 and / or the vehicle component interface application 122. At 504, the vehicle computing system 110 determines whether any BLE modules are present. If this is the case, control continues with operation 506.Otherwise, control continues with operation 512.

[0041] At 506, the vehicle computing system 110 determines whether the detected BLE modules are in-vehicle components 106. In one example, if a module is found, the vehicle component interface application 122 determines the service UUID of the in-vehicle component 106 to determine whether the service UUID indicates an in-vehicle component 106. For example, the vehicle component interface application 122 may identify whether the service UUID is within an identifier range associated with being an in-vehicle component 106. If the module is an in-vehicle component 106, control continues with operation 508. Otherwise, control continues with operation 502.

[0042] The vehicle computing system 110 determines whether the detected in-vehicle component 106 was previously detected at 508. For example, the vehicle computing system 110 may maintain the in-vehicle component list 124, which indicates the currently active in-vehicle components 106 and which, in one example, may be used to generate the list 402 of the vehicle component interface application 122 of the user interface 400-A. The vehicle computing system 110 may compare a service identifier, address, or other information of the detected in-vehicle component 106 with the service identifiers, addresses, or other information of the previously detected in-vehicle components 106 of the in-vehicle component list 124 to determine whether the in-vehicle component 106 was previously detected. If the in-vehicle component 106 was previously detected, control continues with operation 502.Otherwise, control continues with operation 510.

[0043] In operation 510, the vehicle computing system 110 adds the newly detected in-vehicle component 106 to the in-vehicle component list 124. In one example, the vehicle component interface application 122 may add information from the advertisement to the in-vehicle component list 124, such as the service identifier of the in-vehicle component 106, an address at which the in-vehicle component 106 can be accessed, and / or other information related to the in-vehicle component 106, such as timeout information from the advertisement. After operation 510, control returns to operation 502 to perform the scanning.

[0044] In the operations of element 512, the vehicle computing system 110 determines whether any in-vehicle components 106 should be removed from the in-vehicle component list 124. In one example, the vehicle component interface application 122 may determine whether any timeouts of the in-vehicle components 106 located on the in-vehicle component list 124 have expired. In another example, the vehicle component interface application 122 may determine whether any previously detected in-vehicle components 106 are no longer located during the scan. If so, control continues with operation 620 to remove those in-vehicle components 106 from the in-vehicle component list 124. If not, control returns to operation 502 to perform the scan.

[0045] Thus, using process 500, vehicle computing system 110 may wirelessly maintain in-vehicle component list 124 of available in-vehicle components 106 without having to access the vehicle bus.

[0046] Fig. 6 illustrates an example process 600 for displaying the user interface 400 for controlling the in-vehicle components 106. In one example, the process 600 may be performed by the in-vehicle component 106 and the vehicle computing system 110 in communication via a wireless connection.

[0047] In operation 602, the vehicle computing system 110 receives a notification to activate the user interface 400. In one example, the vehicle computing system 110 may receive a notification that the user has selected the in-vehicle component icon 308-E from the user interface 300. At 604, the vehicle computing system 110 generates the user interface 400. The generated user interface 400 may include a list 402 of controls 404 based on the detection of the in-vehicle component list 124 performed in process 500.

[0048] The vehicle computing system 110 determines at 606 whether there is a user interaction with the vehicle component interface application 122. In one example, the vehicle component interface application 122 may receive input to a user interface 400 provided to the display 116 to adjust the state of the in-vehicle component 106. In some examples, the user may provide user input to one or more controllers 410, as described above with reference to the Fig. 4B and Fig. 4C. If an interaction is received, control continues with operation 608. Otherwise, control continues with operation 610.

[0049] At 608, the vehicle computing system 110 updates the control values ​​of the in-vehicle component 106. In one example, the vehicle component interface application 122 uses the wireless transceiver 112 to send a message to the in-vehicle component 106 to update the state of the in-vehicle component 106. For example, in response to the user selecting from the user interface 400 that the in-vehicle smart shade component 106 be rolled down, the vehicle component interface application 122 may instruct the wireless transceiver 112 to send a message directed to the wireless transceiver 118 of the in-vehicle smart shade component 106 requesting that the shade be rolled up or down. After operation 608, control continues with operation 606.

[0050] In the operations of 610, the in-vehicle component 106 determines whether there is an update to the state of the in-vehicle component 106. In one example, the user may adjust a control value of the in-vehicle component 106 using the controls of the in-vehicle component 106 (e.g., a user may use a control on the in-vehicle shading component 106 to command the shading to roll down). In another example, the in-vehicle component 106 may adjust its own state (e.g., the in-vehicle intelligence shading component 106 may roll down based on the detection of increased light conditions). This interaction causes the in-vehicle component 106 to broadcast a message or announce that a change in the state of the in-vehicle component 106 has occurred.If a control value of the in-vehicle component 106 has changed, control continues with operation 612. Otherwise, control continues with operation 606.

[0051] In operation 612, the vehicle computing system 110 receives control state values ​​from the in-vehicle component 106. In one example, the vehicle component interface application 122 may detect the current state of the controls from the in-vehicle component 106 due to the in-vehicle component 106 using BLE to announce a change in state or notifying the vehicle computing system 110 of the change in state.

[0052] At 614, the vehicle computing system 110 refreshes the user interface 400. In one example, the vehicle component interface application 122 may report the changed state of the controls (e.g., on, off, volume level, shade up / down, etc.) based on the state of the controls received at operation 612. After operation 614, control continues with operation 606.

[0053] Computing devices described herein, such as personal devices 104, in-vehicle components 106, vehicle computing system 110, and controller 208, generally include computer-executable instructions, which instructions may be executed by one or more computing devices such as those listed above. Computer-executable instructions, such as the instructions of vehicle component interface application 122 or control logic 212, may be composed of or interpreted by computer programs generated using a variety of programming languages ​​and / or technologies, including, without limitation, and either alone or in combination, Java™, C, C++, C#, Visual Basic, Java Script, Perl, etc. Generally, a processor (e.g., a microprocessor) receives instructions, e.g., from memory, a computer-readable medium, etc.and executes those instructions, thereby performing one or more processes, including one or more of the processes described herein. Such instructions and other data may be stored and transmitted using a variety of computer-readable media.

[0054] With respect to the processes, systems, methods, heuristics, etc. described herein, it is to be understood that although the steps of such processes, etc., are described as occurring according to a certain ordered sequence, such processes may also be implemented such that the described steps are performed in a different order than described herein. It is further to be understood that certain steps could be performed concurrently, that other steps could be added, or that certain steps described herein could be omitted. In other words, the descriptions of the processes herein are for the purpose of illustrating certain embodiments and should in no way be construed to limit the claims.

[0055] While exemplary embodiments have been described above, these embodiments are not intended to describe all possible forms of the invention. Rather, the terms used in the description are for the purpose of description rather than limitation, and it is understood that various changes may be made without departing from the spirit and scope of the invention. In addition, the features of the various implementing embodiments may be combined to form further embodiments of the invention.

[0056] It further describes: A. System that includes: a display integrated into a vehicle; a wireless transmitter-receiver; and a processor coupled to the display and the transmitter-receiver, programmed to to maintain a list of wireless, factory-installed in-vehicle components, to scan for wireless in-vehicle additional components within the vehicle using the wireless transceiver, to create a user interface that lists both the factory-installed wireless in-vehicle components and the wireless in-vehicle add-on components, and to make the list available for display. B. The system of A, wherein the processor is further programmed to: receive a user input to the display requesting a change in the state of one of the vehicle's internal components, and to use the wireless transceiver to update the status of one of the vehicle's internal components. C. The system of B, wherein the change of state is one of rolling down an on-vehicle intelligence shading component or rolling up an on-vehicle intelligence shading component. D. The system of claim 1, wherein the processor is further programmed to: to receive a notification of a change in status from one of the vehicle's internal components; and to update the status of one of the vehicle's internal components in the list responding to the message. E. The system of D, wherein the change in state is an automatic change based on input to one of the in-vehicle components from a light sensor of the in-vehicle component. F. The system of D, wherein the change in state is in response to input received at a user interface controller of one of the in-vehicle components. G. The system of A, wherein the display is a head unit of the vehicle and the processor is a telematics control unit processor. H. Procedure which includes: Maintaining an on-vehicle component list, including factory-installed components and additional components added after a vehicle has been assembled; Scanning for additional in-vehicle components within the vehicle using a wireless transceiver; Removing a first wireless in-vehicle accessory component from the list in response to a failure to locate the first in-vehicle component during scanning; and Add a second wireless in-vehicle accessory to the list located during scanning. I. Method according to H, which further comprises: Generating a user interface list that includes both the factory-installed components and the additional components; and Providing the user interface list for a display. J. The method of I, wherein the display is a head unit of the vehicle. K. Method according to I, which further comprises: Receiving a user input to the display requesting a change in the state of one of the vehicle's internal components; and Using the wireless transceiver to update the status of one of the vehicle's internal components. L. The method of K, wherein the change in state is one of rolling down an in-vehicle window shading component or rolling up an in-vehicle window shading component. M. Method according to I, which further comprises: Receiving a notification of a change in the state of one of the vehicle's internal components; and Updating the state of one of the in-vehicle components in the user interface in response to the message. N. The method of M, wherein the change in state is one of the following: an automatic change based on input to one of the in-vehicle components from a sensor of the in-vehicle component or in response to input received at a user interface controller of the one of the in-vehicle components. O. A computer program product embodied in non-transitory computer-readable memory with instructions for programming a processor of a vehicle in communication with a wireless transceiver to control a display, including instructions for: Maintaining a list of installed in-vehicle components, Scanning for current in-vehicle components inside the vehicle using the wireless transceiver, Updating the list based on scanning and Send to display a generated user interface list of the current in-vehicle components. P. Computer program product according to O, which further includes instructions for maintaining in the list identifiers of the factory-installed components and of the additional components added after assembly of the vehicle. Q. The computer program product of O, further comprising instructions for removing a wireless in-vehicle add-on component from the list in response to failure to locate the wireless in-vehicle component during scanning. R. The computer program product of O, further comprising instructions for adding a wireless in-vehicle add-on component to the list located during scanning.

Claims

[1] System (100) which includes: a display (116) integrated into a vehicle (102); a wireless transmitter-receiver (112); and a processor coupled to the display (116) and the transmitter-receiver (112), programmed to maintain a list of wireless, factory-installed in-vehicle components, to scan for wireless in-vehicle additional components within the vehicle (102) using the wireless transceiver (112), generate a user interface (300) that lists both the factory-installed wireless in-vehicle components and the wireless in-vehicle add-on components, and to provide the list for display (116), wherein the processor is further programmed to: receive a user input to the display (116) requesting a change in the state of one of the in-vehicle components, and to use the wireless transceiver (112) to update the status of one of the in-vehicle components, characterized by that the change in state is one of rolling down an in-vehicle intelligence shading component or rolling up an in-vehicle intelligence shading component. [2] The system (100) of claim 1, wherein the processor is further programmed to: to receive a notification of a change in status from one of the vehicle's internal components; and to update the status of one of the vehicle's internal components in the list responding to the message. [3] The system (100) of claim 2, wherein the change in state is an automatic change based on input to one of the in-vehicle components from a light sensor (210) of the in-vehicle component. [4] The system (100) of claim 2, wherein the change in state is in response to the input received at a user interface controller of one of the in-vehicle components. [5] The system (100) of claim 1, wherein the display (116) is a head unit of the vehicle (102) and the processor is a telematics control unit processor. [6] Procedure which includes: Maintaining an in-vehicle component list (124) by a processor of the vehicle (102) in a memory, including factory-installed components and additional components added after assembly of a vehicle (102); scanning for in-vehicle auxiliary components within the vehicle (102) using a wireless transceiver (112) controlled by the processor; removing, by the processor, a first wireless in-vehicle add-on component from the component list (124) in response to a failure to locate the first in-vehicle component during scanning; adding, by the processor, a second wireless in-vehicle add-on component to the component list (124) located during the scanning; Generate a user interface list that includes both the factory-installed components and the additional components; Providing the user interface list for a display (116); Receiving a user input to the display (116) requesting a change in the state of one of the in-vehicle components; Using the wireless transceiver (112) to update the status of one of the vehicle's internal components, characterized by that the change in state is one of rolling down an in-vehicle window shading component or rolling up an in-vehicle window shading component. [7] The method of claim 6, wherein the display (116) is a head unit of the vehicle (102). [8] The method of claim 6, further comprising: Receiving a notification of a change in the state of one of the vehicle's internal components; and Updating the state of the one of the in-vehicle components in the user interface (300) in response to the message. [9] The method of claim 8, wherein the change in state is one of the following: an automatic change based on input to one of the in-vehicle components from a sensor of the in-vehicle component or in response to input received at a user interface controller of the one of the in-vehicle components.

Images