Customizable secure touch for vehicle displays

Abstract

The invention relates to a customizable secure touch for a vehicle display. Systems / techniques are provided that facilitate customizable secure touch control of vehicle operations. In various embodiments, a system may implement generating a virtual icon representing a hardware-based component of a vehicle on a display. In various aspects, the system may receive touch input to activate a virtual icon and operate associated hardware-based components of the vehicle through a complex touch mode that ensures that touch activation and touch coordinates meet safety regulations and requirements. In various examples, a system may enable layout of virtual icons, visual representations, and customization of indicia based on user preferences through an interface on a vehicle display.

Description

Technical Field

[0001] The subject disclosure generally relates to soft buttons on a vehicle touch display to facilitate customizable safe touch control of vehicle operations. Background Art

[0002] For many years, physical buttons in vehicles have been a common interface for controlling various functions and features. However, they have various problems and disadvantages. Physical buttons are fixed in position and used for specific functions. Unlike soft buttons or touch screens, they cannot be easily reconfigured or customized to adapt to changing user needs or preferences. The presence of many physical buttons may detract from the interior aesthetics of the vehicle, making it look less modern and stylish, especially in luxury or high-end car designs. In compact vehicles or vehicles with a minimalist design philosophy, there may not be enough room to accommodate all the necessary physical buttons without sacrificing comfort or aesthetics. Physical buttons may take up valuable dashboard space, potentially limiting the size and placement of screens for infotainment and navigation systems. In addition, physical buttons are an aging design because vehicles with too many physical buttons may look outdated and less attractive to consumers who expect modern, user-friendly features. As vehicles become more advanced and feature-rich, dashboards may become cluttered with various physical buttons for different functions. This may make the interior of the vehicle look complicated and confusing. New drivers or those who are not familiar with a particular vehicle may find it challenging to locate and use all of the physical buttons, especially if they are not intuitively labeled or logically grouped. Additionally, physical buttons wear out over time. Frequent use may cause buttons to become less responsive or even malfunction, requiring maintenance or replacement.

[0003] Soft buttons in vehicle displays have generally replaced physical buttons in vehicles, however, display soft buttons also exhibit various disadvantages. Soft buttons on vehicle displays are generally limited to functions and features that have been pre-programmed into the system by the car manufacturer. This means that users may not be able to access certain functions they expect, even if the hardware is able to support them. A large number of physical buttons or switches are still required to operate various vehicle functions that are not supported by display soft buttons. The use of both touch displays and physical buttons may make it challenging and confusing for drivers to locate features. In addition, some vehicle displays have a fixed user interface design with predefined soft buttons that cannot be customized or rearranged by the user. This lack of flexibility may be frustrating for drivers who want to prioritize certain functions or features. In addition, soft buttons may have labels or icons that are not particularly clear or intuitive, causing user confusion and the need to experiment to figure out their functions. There is a need in the art to mitigate or overcome some of the disadvantages of physical buttons and soft buttons in displays to control vehicle functions. Summary of the invention

[0004] The following presents a summary of the invention to provide a basic understanding of one or more embodiments of the invention. The summary of the invention is not intended to identify key or important elements, or to delineate any scope of a particular embodiment or any scope of the claims. Its sole purpose is to present concepts in a simplified form as a prelude to a more detailed description that is presented later. In one or more embodiments described herein, an apparatus, system, computer-implemented method, device, or computer program product that facilitates customizable safety touch control of vehicle operations is described.

[0005] According to an embodiment, a system includes a processor that executes computer-executable components stored in a non-transitory computer-readable memory, the computer-executable components including: a virtualization component that generates a virtual icon representing a hardware-based component of a vehicle; a display component that displays the virtual icon on a touch display; and an interface component that receives input associated with activation of the virtual icon to implement a function of the associated hardware-based component.

[0006] According to an embodiment, a computer-implemented method includes: using a virtualization component to enable a user to generate a virtual icon representing a hardware-based component of a vehicle; using a display component to display the virtual icon on a touch display; and using an interface component to receive input associated with activation of the virtual icon to implement the functionality of the associated hardware-based component.

[0007] According to yet another embodiment, a computer program product includes a non-transitory computer-readable memory containing program instructions executable by a processor to cause the processor to: use a virtualization component to enable a user to generate a virtual icon representing a hardware-based component of a vehicle; use a display component to display the virtual icon on a touch display; and use an interface component to receive input associated with activation of the virtual icon to implement functionality of the associated hardware-based component.

[0008] According to one or more embodiments, the above system may be implemented as a computer-implemented method or a computer program product. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 A block diagram of an example non-limiting system that facilitates customizable safe touch control of vehicle operations according to one or more embodiments described herein is shown.

[0010] Figure 2 A block diagram of an example non-limiting system that facilitates customizable safe touch control of vehicle operations according to one or more embodiments described herein is shown.

[0011] Figure 3 A block diagram of an example non-limiting system that facilitates customizable safe touch control of vehicle operations according to one or more embodiments described herein is shown.

[0012] Figure 4 Shown is a magnified view of an example GUI displayed on a vehicle touch screen according to one or more embodiments described herein.

[0013] Figure 5 Shown is a magnified view of an example GUI displayed on a vehicle touch screen according to one or more embodiments described herein.

[0014] Figure 6 Shown is a magnified view of an example GUI displayed on a vehicle touch screen according to one or more embodiments described herein.

[0015] Figure 7 A flow chart illustrating an example non-limiting computer-implemented method for facilitating customizable safe touch control of vehicle operations according to one or more embodiments described herein.

[0016] Figure 8 A flow chart illustrating an example non-limiting computer-implemented method for facilitating customizable safe touch control of vehicle operations according to one or more embodiments described herein.

[0017] Fig. 9 A flow chart illustrating an example non-limiting computer-implemented method for facilitating customizable safe touch control of vehicle operations according to one or more embodiments described herein.

[0018] Fig.10 A block diagram is shown of an example non-limiting operating environment in which one or more embodiments described herein may be facilitated.

[0019] Fig.11 An example networking environment is shown that is operable to perform various embodiments described herein. DETAILED DESCRIPTION

[0020] The following detailed description is merely illustrative and is not intended to limit the embodiments or the application / use of the embodiments. In addition, there is no intention to be bound by any express or implied information presented in the preceding background or summary sections or detailed description sections.

[0021] One or more embodiments are now described with reference to the accompanying drawings, wherein the same reference numerals are used to refer to the same elements throughout. In the following description, for the purpose of explanation, many specific details are set forth in order to provide a more thorough understanding of one or more embodiments. However, it is apparent that in various circumstances, one or more embodiments may be practiced without these specific details.

[0022] Soft buttons in vehicles refer to digital touch-sensitive icons displayed on a screen or interface within the vehicle. They can vary in design and functionality and include controls for audio, climate, navigation, phone calls, vehicle settings, and infotainment features. Physical buttons in vehicles are still typically used for key functions of vehicle operation and include basic controls such as turning lights on and off, emergency hazard lights, opening and closing windows, activating windshield wipers, and engaging the handbrake.

[0023] Unfortunately, existing techniques for controlling vehicle operation using soft and physical buttons can be unreliable, unsafe, and limited for a variety of reasons.

[0024] First, physical buttons in vehicles often have an overwhelming layout, consisting of an excessive number of physical buttons on the dashboard that can overwhelm the driver, making it challenging to quickly locate and use necessary controls. Poor placement or poor ergonomics of physical buttons can lead to distraction and safety risks while driving. For example, the driver may fumble to find and use the various physical buttons, taking their hands off the steering wheel. This may also cause the driver to lose focus on the road for an extended period of time. In addition, the numerous physical buttons present in a small space may make it challenging for the driver to accurately press the intended button without taking their eyes off the road. This may lead to the accidental activation of the wrong function. In addition, in modern vehicles equipped with more advanced features, new users may have difficulty understanding the functions and their placement, resulting in delays in accessing essential controls.

[0025] Secondly, physical buttons cannot be customized because they have fixed positions and functions, making it difficult to adjust their layout or functionality based on driver preferences. In addition, physical buttons require dedicated space on the dashboard or center console, thereby consuming valuable space on the dashboard and limiting design flexibility, and potentially hindering the integration of newer technologies or more fashionable design elements. Without completely redesigning the control panel, physical buttons may not be able to adapt to such new advances and features. In addition, soft buttons in vehicles also lack customization (e.g., icon visuals, icon labels, layout). This lack of customization may also lead to driver distraction, as new drivers may find it challenging to find and select various functions.

[0026] Third, soft buttons used in vehicles currently have limited functionality for operating vehicle controls. Soft button functionality is primarily used for basic control operations (e.g., climate control, phone calls, navigation, settings, radio, infotainment features). Soft button functionality has not been expanded to further control essential driving functions and operations (e.g., turn signals, window activation, gear shifting, windshield wipers).

[0027] In addition, soft buttons and physical buttons are usually activated with a touch or a press to activate the expected vehicle function. However, this method may prove to be unsafe in various situations. For example, a touch activation of a soft button may lead to unexpected activation of a vehicle function (e.g., mistakenly pressing a touch display, accidentally touching a touch display). As another example, an unintentional press of a physical button may activate a key vehicle function (e.g., accidentally flashing a high beam, opening a window, unlocking a door, activating a turn signal, turning on a cruise control). This accidental activation may cause safety risks in various situations. For example, accidentally turning off the headlights while driving at night may hinder visibility and risk an accident. Unintentional activation of high beams or windshield wipers may also temporarily impair visibility, thereby causing a dangerous situation. As another example, mistakenly turning on hazard lights or activating turn signals while driving may confuse other drivers on the road and potentially cause an accident. If the vehicle continues to drive in a straight line instead of turning as indicated by the signal, the driver who attempts to merge or overtake the vehicle may cause a collision. If the driver believes that the vehicle will stop or slow down due to the hazard lights being turned on, misleading signals may also cause unnecessary manipulation or rear-end collisions. Unexpected lane changes may also be caused by unintentional signals and may result in side-swipe accidents.

[0028] Therefore, a system or technique that can address one or more of these technical problems may be desirable.

[0029] Various embodiments described herein may address one or more of these technical issues. One or more embodiments described herein may include a system, computer-implemented method, apparatus, or computer program product that may facilitate customizable safety touch control of vehicle operations. That is, the inventors have recognized that various shortcomings associated with prior art for operating vehicle functions may be improved through customizable safety touch control of vehicle operations.

[0030] In various embodiments, the virtualization component can realize the generation of virtual icons representing hardware-based components of the vehicle on the display component. In various aspects, the interface component can receive touch input to activate the virtual icon and operate the associated hardware-based components of the vehicle. In various aspects, the interface component can realize the customization of the virtual icon based on user preferences (e.g., customized icon vision, layout or marking). In various embodiments, the compliance component can ensure that the touch activation and touch coordinates meet the regulations and requirements. For example, the compliance component can require double touch input on the interface component to activate the vehicle function and prevent unintentional activation (e.g., unintentional shifting, window operation, door unlocking). In various aspects, the vehicle can be equipped with a vehicle microphone. More specifically, the vehicle can use such a microphone in the vehicle to realize voice recognition for voice generation of virtual icons. Therefore, only the driver or authorized passenger can generate virtual icons for vehicle control through voice recognition.

[0031] It should be understood that the drawings and description herein provide non-limiting examples of various embodiments and are not necessarily drawn to scale.

[0032] Figure 1 A block diagram of an example non-limiting system 100 is shown that facilitates customizable safe touch control of vehicle operations according to one or more embodiments described herein.

[0033] In various aspects, the vehicle can be any suitable vehicle or automobile (e.g., it can be a car, truck, van, motorcycle, airplane, boat, helicopter). In various cases, the vehicle can have or otherwise present any suitable type of propulsion system (e.g., it can be an electric vehicle, it can be a gasoline-powered or diesel-powered vehicle, it can be a hybrid vehicle). In some cases, the vehicle can be driven on any suitable road, street, lane or highway at any suitable speed. In other cases, the vehicle can be stopped at an intersection, traffic light, stop sign, crosswalk or traffic jam while driving. In other cases, the vehicle can be parked instead of driving (e.g., it can be parked in a parking lot, on the side of the road or in a driveway). In any case, the vehicle can include, have or otherwise be equipped or equipped with system 100. In other words, system 100 can be on the vehicle.

[0034] In various embodiments, the system 100 may include a processor 102 (e.g., a computer processing unit, a microprocessor) and a non-transitory computer-readable memory 104 operatively or operatively or communicatively connected or coupled to the processor 102. The non-transitory computer-readable memory 104 may store computer-executable instructions that, when executed by the processor 102, may cause the processor 102 or other components of the system 100 (e.g., a virtualization component 106, a display component 108, an interface component 110) to perform one or more actions. In various embodiments, the non-transitory computer-readable memory 104 may store computer-executable components (e.g., a virtualization component 106, a display component 108, an interface component 110), and the processor 102 may execute the computer-executable components.

[0035] In various embodiments, the system 100 can include a virtualization component 106. In various aspects, as described herein, the virtualization component 106 can generate virtual icons representing hardware-based components of a vehicle. For example, the virtualization component 106 can generate virtual icons representing exterior or interior vehicle lights (e.g., turn signals, hazard lights, headlights, dome lights, fog lights).

[0036] The virtualization component 106 can facilitate the use of machine-executable instructions to perform and control one or more operations of the vehicle when the virtual icon is activated. In this regard, embodiments of the system 100 and other systems described herein may include one or more machine-executable components embodied within one or more machines (e.g., embodied in one or more computer-readable storage media associated with one or more machines). When executed by one or more machines (e.g., processors, computers, computing devices, virtual machines, etc.), such components can cause one or more machines to perform the described operations.

[0037] In various embodiments, the system 100 can include a display component 108. In various aspects, as described herein, the display component 108 can display the generated virtual icon on the vehicle display. For example, the display component 108 can display a virtual icon representing an exterior or interior vehicle light on the vehicle display.

[0038] The display assembly 108 may include suitable hardware for registering input events in response to touch (e.g., by a finger, stylus, gloved hand, pen, etc.). The type of display assembly 108 may vary, and may include, but is not limited to, a resistive touch screen, a surface capacitive touch screen, a projected capacitive touch screen, a surface acoustic wave touch screen, and an infrared touch screen. In various embodiments, the display assembly 108 may be positioned on the dashboard of the vehicle, such as on or within the center stack (centerstack) or center console of the dashboard. However, the position of the display assembly 108 in the vehicle may vary. The display assembly 108 may also include one or more display screens (e.g., displays on the steering wheel and dashboard) located in multiple locations of the vehicle. The multiple displays of the display assembly 108 may enable interaction with virtual icons to be limited to the driver. For example, virtual icons representing key vehicle functions (e.g., shifting, turn signals, seat positions) may be specifically displayed on the steering wheel display to prevent activation by another passenger, while virtual icons representing other functions (e.g., window and sunroof operation, interior vehicle lights, door locking and unlocking) may be displayed on the central dashboard display. Regardless of the location or number of displays, the driver can customize the layout and arrangement of the virtual icons based on preference.

[0039] In various embodiments, the system 100 may include an interface component 110. In various aspects, as described herein, the interface component 110 may receive input associated with activation of a virtual icon to implement the functionality of an associated hardware-based component. For example, a virtual icon representing vehicle light operation may receive touch input from a driver to activate and implement functionality to operate the vehicle light (e.g., turn on the left turn signal, turn off the hazard lights, switch the headlights to low beam).

[0040] The interface component 110 may be displayed on the display component 108 to facilitate docking with a graphical user interface (GUI) rendered on the display. The interface component 110 may be one or more interactive GUIs that facilitate access to or control of various functions and applications of the vehicle. In this regard, the GUI may present one or more selectable graphical elements or virtual icons that may correspond to controls for functions, applications, functions of applications, interactive data, etc. for the vehicle, respectively, wherein the corresponding functions are activated via touch selection or interaction with the graphical elements or virtual icons displayed on the display component 108. For example, one or more GUIs displayed on the display component 108 may include selectable buttons or bars corresponding to vehicle operating functions, vehicle navigation applications, media applications, phone applications, reversing camera functions, car settings functions, parking assist functions, etc. In some embodiments, selecting a button or bar corresponding to an application or function may result in the generation of a new window or GUI including additional selectable icons or widgets associated with the selected application. For example, the selection of a light virtual icon may result in the generation of a new GUI or window including additional buttons or widgets for various vehicle lights and light settings (e.g., turn signals, hazard lights, fog lights, headlights, low beams, high beams). The type and appearance of the selectable graphical elements can vary. For example, the selectable graphical elements can include icons, symbols, widgets, windows, tabs, text, images, etc.

[0041] In various aspects, based on input received via user interaction with a GUI displayed on the display component 108, the virtualization component 106 can issue or send control commands to control or execute vehicle functions or applications. For example, the driver can touch a virtual icon associated with a hardware-based component of the vehicle on the selection interface component 110 (e.g., a virtual icon associated with actuating a window of the vehicle). Upon touch input of the interface component 110, the virtual icon can be activated. Thus, the virtualization component 106 can activate or operate the associated hardware-based component of the vehicle function represented by the activated virtual icon (e.g., opening the driver's seat window, closing the sunroof, further raising the passenger seat window).

[0042] In various aspects, the interface component 110 may allow for customized configuration of the generated virtual icons (e.g., virtual icon functions, graphics, markings, layouts) based on the user's preferences. The interface component 110 may provide various GUI configurations to display virtual icons on the display component 108. The GUI may include various configurations to display a home screen containing the generated virtual icons created by the user and a virtual icon that creates a new icon when activated. The user may start generating a new virtual icon by touching and activating a virtual icon that can create a new icon. The user may then select the vehicle function that the new virtual icon will operate from a batch of functions that have not yet been generated as virtual icons. The batch of vehicle functions may be displayed in any suitable interface configuration (e.g., as a grid layout, a slide with navigation arrows, a list view, an interactive layout with a slider). This may be displayed in a new GUI or window or in an existing window. In addition, the user may select the icon symbol to be displayed on the virtual icon given a batch of images, or may upload a separate image (e.g., may be uploaded via USB connection, Bluetooth, wireless screen mirroring, mobile application integration, cloud storage integration) to be used as an icon visual. The batch of images can be displayed in any suitable interface configuration (e.g., as a grid layout, a slideshow with navigation arrows, a list view, an interactive layout with a slider), and can be displayed in a new GUI or window or within an existing window. In addition, the user can change the label of the new virtual icon from the original vehicle function label selected by the user (e.g., changing the label of the icon from light to lighting). The GUI may include any suitable configuration for allowing text editing of the virtual icon label (e.g., a keyboard display after selecting an edit button). Thus, after selecting the function, visual, and label of the new virtual icon, the new virtual icon will now be displayed in the main screen interface where the virtual icons are displayed.

[0043] The interface component 110 may include a GUI configuration for enabling editing or customizing a home screen of the displayed generated virtual icons. For example, the layout and order of the virtual icons on the vehicle display may be changed based on the user's preferences or the frequency of use of the virtual icons (e.g., if the user frequently uses a virtual icon for operating windshield wipers, the user may move the virtual icon closer or enlarge the size of the virtual icon on the vehicle display). The GUI configuration for display customization may also enable the user to change the icon visuals and labels of the virtual icons that have been created any number of times. Such customization may enable flexibility in vehicle operation to accommodate the user's changing needs or driving behavior.

[0044] Figure 2A block diagram of an example non-limiting system 200 that can facilitate customizable safety touch control of vehicle operation according to one or more embodiments described herein is shown. As shown, in some cases, system 200 can include the same components as system 100 and can also include a compliance component 202.

[0045] In various embodiments, the interface component 110 can engage the compliance component 202 to ensure that the activation, touch coordinates, and generated visuals of the virtual icons used to operate the vehicle functions meet or satisfy safety requirements and regulations. In various aspects, the touch activation of the virtual icons on the display component 108 can meet the ISO-26262 of ASIL-B level by utilizing complex touch patterns. The complex touch pattern can consist of a double touch input on the interface component 110 to activate the virtual icon to operate the associated vehicle function. The two-touch activation can mitigate the possibility of accidental or unauthorized activation of the vehicle function by providing an additional confirmation layer via the second touch input. For example, the double touch input can be implemented by requiring a first touch of the virtual icon, followed by a second touch of the virtual icon. As another example, the double touch input may include a first touch of the virtual icon, followed by a slide from a first position to a second position. In addition, another double touch input may include a slide from a first position to a second position. The interface component 110 can be configured to require a single touch or a double touch input to select various buttons on the display that do not activate any vehicle function (e.g., select an image to be used as an icon visual during icon generation, scroll to view additional icons or list options). Utilizing dual touch inputs to activate soft buttons on the display assembly 108 may allow for safe operation of necessary and critical vehicle operations that conventional systems using single touch input activation cannot provide.

[0046] In various instances, the compliance component 202 can implement a time limit between two touch inputs to further enhance safety and avoid unintentional or accidental touches on the display component 108. For example, the compliance component can implement a time constraint so that the second touch input must occur after a defined amount of time from the first touch input. Thus, rapid activation of various vehicle functions can be prevented to maintain control and safe operation of the vehicle. Rapid touch input of a virtual icon may result in inadvertent activation of a vehicle function (e.g., accidental activation of high beams, cruise control, or vehicle windows). In addition, a time constraint can be imposed on the second touch input to ensure that the second touch occurs before a certain amount of time after the first touch. Such a time limit can mitigate accidental activation by ensuring that the two touches occur intentionally by the user and that activation does not occur due to stray or unintended presses. If the second touch does not occur within a suitable determined time frame after the first touch, the interface component 110 can reset the virtual icon activation (e.g., return to the main menu, ignore the first touch).

[0047] In addition, the compliance component 202 can limit the activation or display of certain virtual icons while the vehicle is in motion to prevent dangerous driving conditions (e.g., limiting the opening of a trunk or hood while the vehicle is in motion). For example, virtual icons that may cause visual obstruction to the driver if activated can be disabled until the vehicle is placed in a parking space (e.g., trunk, hood). As another example, virtual icons that may cause safety hazards if activated can be disabled while the vehicle is in motion (e.g., open fuel door, open charging port). In various instances, the temporary disabling of such virtual icons can mitigate the possibility of accidental activation or opening of the vehicle's fuel door or charging port, thereby preventing the possibility of fuel spilling, allowing fuel vapor to escape, or exposing live electrical components, as such instances may cause fire hazards, electrical chocks, or damage to the vehicle.

[0048] In various embodiments, the compliance component 202 can ensure that the touch coordinates of the generated virtual icon meet the ISO-26262 regulations. The display component 108 must be developed according to ISO-26262 to at least ASIL-A level. An integrity mechanism can be implemented to confirm that the touch coordinates are accurate and correct when sent from the interface component 110 to the display component 108 for evaluation. For example, a graphics engine can be used to generate graphics on the display component 108. Then, the frame buffer can prepare the graphics to be displayed, and engage the graphics monitor to read out the frame buffer to ensure the accuracy and correctness of the graphics, so as to operate the appropriate associated hardware-based components of the vehicle. Once the integrity of the graphics has been checked, the display component 108 can display the physical graphics. The compliance component 202 can implement an integrity mechanism (e.g., cyclic redundancy check (CRC), Kalman filtering, singular value decomposition (SVD), machine learning) to ensure that the touch coordinates are accurate when the touch input is sent to the virtualization component 106 to operate the vehicle function. For example, a cyclic redundancy check (CRC) can be used as an integrity mechanism.

[0049] Figure 3 A block diagram of an example non-limiting system 300 that can facilitate speech generation of customizable safe touch control of vehicle operations according to one or more embodiments described herein is shown. As shown, in some cases, system 300 can include the same components as system 200, and can also include a set of vehicle microphones 302, an inference component 304, and a deep learning neural network 306.

[0050] In various aspects, the set of vehicle microphones 302 can include any suitable number of any suitable type of microphones (e.g., sound capture devices). In various examples, the set of vehicle microphones 302 can be integrated into a vehicle. For example, such one or more microphones can be integrated into any suitable interior vehicle surface (e.g., dashboard, steering wheel, door, vehicle ceiling) to capture or otherwise record sounds or noises occurring within the vehicle. The audio recorded by the vehicle microphones 302 can include any suitable number of audio clips that can represent noises occurring within the vehicle.

[0051] In various embodiments, the system 300 can include an inference component 304. In various examples, as described herein, the inference component 304 can detect and recognize passenger and driver speech, as well as any suitable speech activation phrases or phrasing to initiate generation of a new virtual icon.

[0052] In various embodiments, the inference component 304 may electronically store, electronically maintain, electronically control, or otherwise electronically access the deep learning neural network 306. In various aspects, the deep learning neural network 306 may have or otherwise exhibit any suitable internal architecture. For example, the deep learning neural network 306 may have an input layer, one or more hidden layers, and an output layer. In various instances, any such layers may be coupled together by any suitable interneuron connections or interlayer connections (e.g., forward connections, skip connections, or recurrent connections). In addition, in various cases, any such layer may be a neural network layer of any suitable type with any suitable learnable or trainable internal parameters. For example, any of such an input layer, one or more hidden layers, or an output layer may be a convolutional layer, whose learnable or trainable parameters may be a convolution kernel. As another example, any of such an input layer, one or more hidden layers, or an output layer may be a dense layer, whose learnable or trainable parameters may be a weight matrix or a bias value. As yet another example, any of such an input layer, one or more hidden layers, or an output layer may be a batch normalization layer, whose learnable or trainable parameters may be a shift factor or a scale factor. Furthermore, in various cases, any such layer may be any suitable type of neural network layer with any suitable fixed or non-trainable internal parameters. For example, any of such input layers, one or more hidden layers, or output layers may be a non-linear layer, a padding layer, a pooling layer, or a cascade layer.

[0053] In various aspects, voice recognition through inference component 304 can be utilized to ensure authorized generation of virtual icons for vehicle operations. Voice recognition and authorization can prevent other occupants of the vehicle from generating virtual icons and interfering with the driver's operation of the vehicle (e.g., a child in the vehicle attempts to change custom settings with voice and confuses the driver with the virtual icons). Voice recognition can mitigate this and prevent driver confusion when trying to locate various vehicle functions.

[0054] In addition, interface component 110 can also use inference component 304 to identify the current driver of the vehicle, and automatically change the customized settings and display of preferences based on the identified driver. Inference component 304 can use any suitable method (e.g., voice recognition, remote control key, facial recognition, smart phone application) to identify the vehicle driver. In any case, interface component 110 can create profiles for different drivers of the vehicle, and can display the confirmation or selection of the identified driver to the current driver. Once the driver has confirmed or selected the correct user profile on display component 108, interface component 110 can be engaged to display the user's customized preset on display component 108. For example, a vehicle can be shared between multiple people. Voice recognition of the current driver can be used to determine the appropriate customized display to be displayed on display component 108 before the driver starts driving the vehicle (e.g., if a couple shares a vehicle, when voice recognition identifies a partner as a driver, the screen can display the layout and virtual icons of the partner's preference settings).

[0055] In various instances, the inference component 304 can use a deep learning neural network 306 to learn the driver's behavior or preferred vehicle settings (e.g., driving mode, seat positioning, climate control, radio presets). Therefore, the inference component 304 can engage the virtualization component 106 to automatically adjust various vehicle operations (e.g., automatically adjust climate control settings, seat positioning, radio presets) when the current driver is determined. In addition, in addition to the vehicle microphone 302, the inference component 304 can also use any suitable vehicle sensor to detect various internal or external vehicle conditions. Therefore, the inference component 304 can mask or display certain virtual icons based on the determination of the vehicle condition. For example, if rain is detected on the windshield of the vehicle, a virtual icon representing the operation of the windshield wipers can be displayed on the display component 108. On the contrary, if rain is not detected on the windshield of the vehicle, a virtual icon representing the operation of the windshield wipers can be masked or hidden on the display to avoid displaying a large number of virtual icons and alleviate the driver's confusion when navigating vehicle operations. In various examples, the inference component 304 can also engage the interface component 110 to display corresponding portions of the vehicle's owner's manual when warning of various vehicle conditions. For example, if the engine light is illuminated on the vehicle, the interface component 110 can display portions of the owner's manual that instruct the driver how to handle such warnings and conditions. As another example, if low tire pressure is detected, a portion of the owner's manual that describes how to change a tire on the vehicle or how to refill tire air can be displayed.

[0056] Figure 4 Shown is a magnified view of an example GUI that may be displayed on a display assembly according to one or more embodiments described herein.

[0057] In various embodiments, Figure 4 An example GUI that can display new virtual icons and facilitate the generation of new virtual icons is depicted in . In this example, the display component 108 displays a create icon 402 and two previously generated virtual icons, a window icon 404 and a shift icon 406. In various aspects, the create icon 402 can enable a user to create a new virtual icon for operating a vehicle function when a double touch input is activated.

[0058] In various embodiments, the window icon 404 can, for example, when touch activated, generate a new GUI or window that displays various control settings for actuating one or more windows of the vehicle (e.g., a sliding function for selecting the degree to which a window is opened or closed, opening the sunroof, closing the sunroof, locking the windows).

[0059] In various aspects, the gear shift icon 406 can display the vehicle's gear shift (e.g., park, reverse, drive, neutral, overdrive, low gear, manual transmission gear) in a new GUI or window, for example, when the icon is touched to activate. The user can then use a double touch input to change the vehicle's gear.

[0060] In this example, when the user activates create icon 402, a scrollable window 408 (e.g., with a scroll function to view all list items) can be displayed to list vehicle functions that do not yet have a virtual icon. Accordingly, the user can select the desired function, in this example, vehicle lights, and an icon visual selection window 410 can be displayed to allow the user to select a preferred image from a batch of images 412 to represent the new virtual icon. The icon visual selection window 410 can also include an upload picture option 414 to allow the user to use an image that is not available in the batch of images 412 to represent the virtual icon.

[0061] Figure 5 Shown is a magnified view of an example GUI that may be displayed on a display assembly according to one or more embodiments described herein.

[0062] In various embodiments, Figure 5 An example GUI that can display the generated virtual icon is depicted in FIG. In this example, the display component 108 can display the newly generated icon 502 using a visual selected from the batch of images 412 to operate the vehicle lights. In addition, in this example, the GUI can be other virtual icons that can operate other vehicle functions.

[0063] In various aspects, the virtualization component 106 can create an icon that can, for example, display and allow operation of windshield wiper settings and states (e.g., front windshield wiper speed, rear windshield wiper speed, spray washing fluid on the front windshield, spray washing fluid on the rear windshield, single swipe, auto-sensing mode) in a new GUI or window when the icon is activated by touch. The user can then use dual touch input to change the settings or modes of the vehicle windshield wipers.

[0064] In various examples, the virtualization component 106 can create icons that can, for example, display vehicle access points (e.g., trunk, hood, fuel door, charging port) and allow opening or closing of vehicle access points (e.g., trunk release or lock, hood release or lock, fuel door release or lock, open or close charging port) in a new GUI or window when the icon is activated by touch. The user can then use dual touch input to open, close, or lock such vehicle access points.

[0065] In various embodiments, the virtualization component 106 can create an icon that can display and operate the door locking function (e.g., child lock, lock door, unlock door, automatic lock or unlock) in a new GUI or window, for example, when the icon is activated by touch. The user can then use dual touch input to lock, unlock, or control the door locking mechanism.

[0066] In various aspects, the virtualization component 106 can create an icon that can display and control the vehicle's driving mode (e.g., sport mode, economy mode, comfort mode, all-terrain mode, traction mode, electric or hybrid mode) in a new GUI or window, such as when the icon is activated by touch. The user can then use dual touch input to change the vehicle's driving mode.

[0067] In various aspects, the virtualization component 106 can create an icon that can display and control the seat adjustments of the vehicle seat (e.g., height, tilt angle, horizontal position, lumbar support, headrest height, headrest tilt, seat cushion tilt) in a new GUI or window, for example, when the icon is activated by touch. The user can then use dual touch input to change the seat adjustments of the vehicle seat.

[0068] Figure 6 Shown is a magnified view of an example GUI that may be displayed on a display assembly according to one or more embodiments described herein.

[0069] In various embodiments, Figure 6 , an example GUI that can display lighting settings after selecting a newly generated icon 502 for operating vehicle lights is depicted. In this example, a complex touch pattern that can be used to activate vehicle functions is displayed. For example, a first touch input and a second touch input can be used to operate a turn signal of a vehicle. The first touch input 602 can select a left turn signal, and the second touch input 604 can select the left turn signal again to confirm the activation of the left turn signal of the vehicle. As another example, a first touch input followed by a swipe from a first position to a second position can be used to operate the headlights of a vehicle. The first touch input 606 can select a headlight label or icon, and a swipe from the first position to the second position 608 can select a low beam or high beam setting for the headlights (e.g., swiping from the center to the left to select low beam, swiping from the center to the right to select high beam). As yet another example, a swipe from the first position to the second position can be used to dim the top lights in a vehicle. The user can slide the marker from a first position 610 (e.g., a current dimming level) to a second position 612 (e.g., a desired dimming level).

[0070] Figure 7A flow chart illustrating an example non-limiting computer-implemented method 700 that can facilitate customizable safety touch control of vehicle operations according to one or more embodiments described herein. In various circumstances, the system 100 can facilitate the computer-implemented method 700 .

[0071] In various embodiments, action 702 may include receiving, by the interface component (eg, via 110 ), input (eg, voice input, touch input) for generating a new virtual icon.

[0072] In various cases, act 704 may include receiving, by the interface component (eg, via 110 ), a user selection of a desired vehicle function for the new virtual icon.

[0073] In various aspects, act 706 can include receiving, by the interface component (eg, via 110 ), a user selection of a desired icon graphic for the new virtual icon.

[0074] In various aspects, act 708 can include receiving, by the interface component (eg, via 110 ), a user selection or entry input of a desired label for the new virtual icon.

[0075] In various aspects, act 710 can include receiving, by the interface component (eg, via 110 ), a user selection of a desired location for a new virtual icon on the home screen.

[0076] In various aspects, act 712 may include engaging, by an interface component (eg, via 110 ) a virtualization component (eg, 106 ) to generate and implement functionality of a new virtual icon.

[0077] For example, a user may select the create icon 402 on the display component 108 and select the function of operating the vehicle windshield wipers. The user may then select a preferred graphic to represent the virtual icon. In addition, the user may then change or maintain the label of the new virtual icon (e.g., selecting wipers as a label, changing the label to windshield wipers). The user may also select a desired position on the home screen of the virtual icon based on user preferences (e.g., selecting the leftmost position on the dashboard display due to frequent use of the vehicle windshield wipers). After the customization of the new virtual icon has been selected, the virtualization component may be engaged to implement the function of the new virtual icon to implement the operation of the vehicle windshield wipers when activated according to the user's double touch input.

[0078] Figure 8 A flow chart illustrating an example non-limiting computer-implemented method 800 that can facilitate customizable safety touch control of vehicle operations according to one or more embodiments described herein. In various circumstances, the system 100 can facilitate the computer-implemented method 800 .

[0079] In various embodiments, action 802 may include receiving, by the interface component (eg, via 110 ), a first touch input to activate functionality of the virtual icon.

[0080] In various cases, action 804 can include determining, by the compliance component (e.g., via 202), whether the interface component (e.g., 110) has received the second touch input within the determined time frame. If no (e.g., if the interface component 110 has not received the second touch input within the determined time frame), the computer-implemented method 800 can proceed to action 802. If yes (e.g., if the interface component 110 has received the second touch input within the determined time frame), the computer-implemented method 800 can proceed to action 806.

[0081] In various aspects, act 806 can include engaging, by the compliance component (eg, via 202 ), the virtualization component (eg, 110 ) to operate and execute the functionality of the activated virtual icon.

[0082] For example, the user may accidentally touch the display assembly 108 as a first touch input (e.g., mistakenly extending an arm to make contact with the display). The user may then not touch the display assembly 108 for a given time because the first touch input was unintentional and the user does not want to change or operate any vehicle settings. After the determined time frame from the activation of the second touch input has passed, the interface assembly 110 may ignore the first touch input and be ready to receive another first touch input to activate a vehicle function.

[0083] Fig. 9 A flow chart illustrating an example non-limiting computer-implemented method 900 that can facilitate customizable safety touch control of vehicle operations according to one or more embodiments described herein. In various circumstances, the system 100 can facilitate the computer-implemented method 900 .

[0084] In various embodiments, act 902 may include engaging, by an inference component (eg, 304 ), a vehicle microphone (eg, 302 ) to record speech requesting generation of a new virtual icon.

[0085] In various aspects, act 904 can include using a deep learning neural network (e.g., 306) by an inference component (e.g., 304) to determine the identity of the recorded speech.

[0086] In various cases, action 906 may include determining, by the compliance component (e.g., via 202), whether the recorded voice matches the voice of the vehicle driver. If no (e.g., if the recorded voice does not match the voice of the vehicle driver), the computer-implemented method 900 may proceed to action 902. If yes (e.g., the recorded voice matches the voice of the vehicle driver), the computer-implemented method 900 may proceed to action 908.

[0087] In various embodiments, act 908 may include engaging, by a compliance component (eg, 202 ) a virtualization component (eg, 106 ) to generate a virtual icon.

[0088] For example, a child in the back seat may attempt to voice-generate a new virtual icon for operating a gear shift. The deep learning neural network 306 may utilize the recorded child's voice to identify the speaker's voice (e.g., not the current driver of the vehicle, the current driver of the vehicle). Based on determining that the child's voice does not match the voice of the current driver of the vehicle, the compliance component 202 may ignore the request to generate a new virtual icon.

[0089] Although the disclosure herein mainly describes various embodiments as implementing a deep learning neural network (e.g., 602), this is merely a non-limiting example. In various aspects, the teachings described herein can be implemented via any suitable machine learning model that exhibits any suitable artificial intelligence architecture (e.g., support vector machine, naive Bayes, linear regression, logistic regression, decision tree, random forest, reinforcement learning) or quantum computing architecture.

[0090] In various cases, the machine learning algorithm or model can be implemented in any suitable manner to facilitate any suitable aspect described herein. In order to facilitate some of the above-mentioned machine learning aspects of various embodiments, consider the following discussion of artificial intelligence (AI). Various embodiments described herein can use artificial intelligence to facilitate the automation of one or more features or functions. Components can use various AI-based schemes to perform various embodiments / examples disclosed herein. In order to provide or assist in many determinations described herein (e.g., determination, detection, inference, calculation, prediction, prediction, estimation, derivation, forecast, detection, calculation), the components described herein can check all or a subset of the data to which they are authorized to access, and can provide reasoning about the state of the system or environment or determine the state of the system or environment from a set of observations captured via events or data. For example, determination can be used to identify a specific context or action, or a probability distribution of a state can be generated. Determination can be probabilistic; that is, a probability distribution of a state of interest is calculated based on consideration of data and events. Determination can also refer to a technique for composing a higher-level event from a set of events or data.

[0091] Such determination can result in constructing new events or actions from a set of observed events or stored event data, whether or not the events are closely related in time, and whether the events and data come from one or more event and data sources. The components disclosed herein can employ various classification (explicit training (e.g., via training data) and implicit training (e.g., via observed behavior, preferences, historical information, receiving external information, etc.)) schemes or systems (e.g., support vector machines, neural networks, expert systems, Bayesian belief networks, fuzzy logic, data fusion engines, etc.), in combination with performing automatic or determined actions related to the claimed subject matter. Therefore, the classification scheme or system can be used to automatically learn and perform multiple functions, actions, or determinations.

[0092] The classifier can take the input attribute vector z = (z1, z2, z3, z4, z n ) is mapped to the confidence that the input belongs to a class, as represented by f(z)=confidence(class). This classification can use probabilistic or statistical analysis (e.g., taking into account analytical utility and cost) to determine the actions to be automatically performed. A support vector machine (SVM) may be an example of a classifier that can be used. SVM operates by finding a hyper-surface in the space of possible inputs, where the hyper-surface attempts to separate triggering criteria from non-triggering events. Intuitively, this makes the classification correct for test data that is close to but not identical to the training data. Other directed and undirected model classification schemes include, for example, naive Bayes, Bayesian networks, decision trees, neural networks, fuzzy logic models, or probabilistic classification models that provide different independence patterns, any of which can be used. Classification as used herein also includes statistical regression for developing priority models.

[0093] The disclosure herein describes non-limiting embodiments. For ease of description or explanation, various portions of the disclosure herein utilize the terms "each," "each," or "all" when discussing various examples. Such usage of the terms "each," "each," or "all" is non-limiting. In other words, when the disclosure herein provides a description of "each," "each," or "all" applied to a particular object or component, it should be understood that this is a non-limiting example, and it should be further understood that in various other examples, such descriptions may apply to less than "each," "each," or "all" in the particular object or component.

[0094] To provide additional context for the various embodiments described herein, Fig.10The following discussion is intended to provide a brief, general description of a suitable computing environment 1000 in which various embodiments described herein may be implemented. Although the embodiments have been described above in the general context of computer-executable instructions that may be executed on one or more computers, those skilled in the art will recognize that the embodiments may also be implemented in combination with other program modules or as a combination of hardware and software.

[0095] Generally, program modules include routines, programs, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In addition, those skilled in the art will appreciate that the present invention can be practiced with other computer system configurations, including single-processor or multi-processor computer systems, minicomputers, mainframe computers, Internet of Things (IoT) devices, distributed computing systems, and personal computers, handheld computing devices, microprocessor-based or programmable consumer electronics, etc., each of which can be operably coupled to one or more associated devices.

[0096] The illustrated embodiments of the embodiments herein can also be practiced in distributed computing environments, where certain tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

[0097] Computing devices typically include various media, which may include computer-readable storage media, machine-readable storage media, or communication media, the two terms being used differently from each other herein as follows. Computer-readable storage media or machine-readable storage media can be any available storage media that can be accessed by a computer, and include both volatile and non-volatile media, removable and non-removable media. By way of example and not limitation, computer-readable storage media or machine-readable storage media can be implemented in conjunction with any method or technology for storing information such as computer-readable or machine-readable instructions, program modules, structured data, or unstructured data.

[0098] Computer-readable storage media may include, but are not limited to, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD), Blu-ray disk (BD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, solid-state drives or other solid-state storage devices, or other tangible or non-transitory media that may be used to store the desired information. In this regard, the terms "tangible" or "non-transitory" as applied to storage, memory, or computer-readable media herein should be understood as excluding only propagating transitory signals per se as modifiers, and not disclaiming all standard storage, memory, or computer-readable media that are not merely propagating transitory signals per se.

[0099] Computer readable storage media may include, but are not limited to, quantum memories or other tangible or non-transitory media that can be used to store the desired information. In this regard, the terms "tangible" or "non-transitory" as applied to storage devices, memories, or computer readable media herein should be understood as excluding only propagating transitory signals per se as modifiers, and not disclaiming the right to all standard storage devices, memories, or computer readable media that are not merely propagating transitory signals per se.

[0100] Computer-readable storage media may be accessed by one or more local or remote computing devices, eg, via access requests, queries, or other data retrieval protocols, for various operations regarding the information stored by the media.

[0101] Communication media typically embodies computer readable instructions, data structures, program modules, or other structured or unstructured data in a data signal such as a modulated data signal (e.g., a carrier wave or other transport mechanism), and includes any information delivery or transmission media. The term "modulated data signal" or signal refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in one or more signals. By way of example, and not limitation, communication media includes wired media (e.g., a wired network or direct-wired connection) and wireless media (e.g., acoustic, RF, infrared, and other wireless media).

[0102] Reference again Fig.10 , an example environment 1000 for implementing various embodiments of aspects described herein includes a computer 1002, which includes a processing unit 1004, a system memory 1006, and a system bus 1008. The system bus 1008 couples system components including, but not limited to, the system memory 1006 to the processing unit 1004. The processing unit 1004 can be any of a variety of commercially available processors. Dual microprocessors and other multi-processor architectures can also be used as the processing unit 1004.

[0103] The system bus 1008 may be any of several types of bus structures that may further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures. The system memory 1006 includes ROM 1010 and RAM 1012. A basic input / output system (BIOS) containing the basic routines that help to transfer information between elements within the computer 1002, such as during startup, may be stored in a nonvolatile memory such as a ROM, an erasable programmable read-only memory (EPROM), an EEPROM, or the like. The RAM 1012 may also include a high-speed RAM such as a static RAM for caching data.

[0104] The computer 1002 also includes an internal hard disk drive (HDD) 1014 (e.g., EIDE, SATA), one or more external storage devices 1016 (e.g., a magnetic floppy disk drive (FDD) 1016, a memory stick or flash drive reader, a memory card reader, etc.), and a drive 1020, such as a solid state drive, an optical drive, which can read or write from a disk 1022 such as a CD-ROM disk, a DVD, a BD, etc. Alternatively, in the case of a solid state drive, the disk 1022 will not be included (unless it is separate). Although the internal HDD 1014 is shown as being located within the computer 1002, the internal HDD 1014 can also be configured for external use in a suitable chassis (not shown). In addition, although not shown in the environment 1000, a solid state drive (SSD) can be used in addition to or instead of the HDD 1014. The HDD 1014, external storage device 1016, and drive 1020 can be connected to the system bus 1008 via a HDD interface 1024, an external storage interface 1026, and a drive interface 1028, respectively. The interface 1024 for external drive implementations may include at least one or both of Universal Serial Bus (USB) and Institute of Electrical and Electronics Engineers (IEEE) 1394 interface technologies. Other external drive connection technologies are within the contemplation of the embodiments described herein.

[0105] The drives and their associated computer-readable storage media provide non-volatile storage of data, data structures, computer-executable instructions, etc. For the computer 1002, the drives and storage media accommodate the storage of any data in a suitable digital format. Although the above description of computer-readable storage media relates to corresponding types of storage devices, it should be understood by those skilled in the art that other types of computer-readable storage media (whether currently existing or developed in the future) can also be used in the example operating environment, and further, any such storage media can contain computer-executable instructions for performing the methods described herein.

[0106] A number of program modules may be stored in the drives and RAM 1012, including an operating system 1030, one or more application programs 1032, other program modules 1034, and program data 1036. All or portions of the operating system, applications, modules, or data may also be cached in RAM 1012. The systems and methods described herein may be implemented using various commercially available operating systems or combinations of operating systems.

[0107] Computer 1002 may optionally include emulation technology. For example, a hypervisor (not shown) or other intermediary may emulate the hardware environment of operating system 1030, and the emulated hardware may optionally communicate with the operating system 1030. Fig.10 The hardware shown is different. In such an embodiment, the operating system 1030 may include one of multiple virtual machines (VMs) hosted at the computer 1002. In addition, the operating system 1030 may provide a runtime environment for the application 1032, such as a Java runtime environment or a .NET framework. The runtime environment is a consistent execution environment that allows the application 1032 to run on any operating system that includes a runtime environment. Similarly, the operating system 1030 may support containers, and the application 1032 may be in the form of a container, which is a lightweight, independent, executable software package that includes, for example, code, runtime, system tools, system libraries, and settings for the application.

[0108] In addition, the computer 1002 may be implemented with a security module, such as a trusted processing module (TPM). For example, in the case of a TPM, the boot component hashes the next boot component in time and waits for the result to match the security value before loading the next boot component. This process may occur at any layer in the code execution stack of the computer 1002, for example, at the application execution level or at the operating system (OS) kernel level, thereby achieving security of code execution at any level.

[0109] A user may enter commands and information into the computer 1002 through one or more wired / wireless input devices, such as a keyboard 1038, a touch screen 1040, and a pointing device such as a mouse 1042. Other input devices (not shown) may include a microphone, an infrared (IR) remote control, a radio frequency (RF) remote control or other remote control, a joystick, a virtual reality controller or headset, a game controller, a stylus, an image input device (e.g., a camera), a gesture sensor input device, a visual motion sensor input device, an emotion or facial detection device, a biometric input device (e.g., a fingerprint or iris scanner), and the like. These and other input devices are typically connected to the processing unit 1004 through an input device interface 1044, which may be coupled to the system bus 1008, but may be connected through other interfaces, such as a parallel port, an IEEE 1394 serial port, a game port, a USB port, an IR port, a fingerprint scanner, or the like. Interfaces, etc.

[0110] A monitor 1046 or other type of display device may also be connected to the system bus 1008 via an interface, such as a video adapter 1048. In addition to the monitor 1046, computers typically include other peripheral output devices (not shown), such as speakers, printers, and the like.

[0111] The computer 1002 can operate in a networked environment using logical connections via wired or wireless communications to one or more remote computers, such as remote computer 1050. The remote computer 1050 can be a workstation, server computer, router, personal computer, portable computer, microprocessor-based entertainment device, peer device, or other public network node, and typically includes many or all of the elements described relative to the computer 1002, but for the sake of simplicity, only the memory / storage device 1052 is shown. The depicted logical connections include wired / wireless connections to a local area network (LAN) 1054 or a larger network, such as a wide area network (WAN) 1056. Such LAN and WAN networking environments are common in offices and companies, and facilitate enterprise-wide computer networks, such as intranets, all of which can be connected to a global communication network, such as the Internet.

[0112] The computer 1002 can operate in a networked environment using logical connections via GPRS, GSM, 5G, LTE, 6G protocols based on wireless communications.

[0113] When used in a LAN networking environment, the computer 1002 can be connected to a local network 1054 through a wired or wireless communication network interface or adapter 1058. The adapter 1058 can facilitate wired or wireless communication to the LAN 1054, which can also include a wireless access point (AP) disposed thereon for communicating with the adapter 1058 in a wireless mode.

[0114] When used in a WAN networking environment, the computer 1002 may include a modem 1060 or may be connected to a communication server on the WAN 1056 via other means for establishing communications on the WAN 1056 (e.g., through the Internet). The modem 1060, which may be internal or external and a wired or wireless device, may be connected to the system bus 1008 via the input device interface 1044. In a networked environment, program modules depicted relative to the computer 1002, or portions thereof, may be stored in the remote memory / storage device 1052. It should be appreciated that the network connections shown are examples and other means of establishing a communications link between the computers may be used.

[0115] When used in a LAN or WAN networking environment, in addition to or in lieu of the external storage device 1016 described above, the computer 1002 may also access a cloud storage system or other network-based storage system, such as, but not limited to, a network virtual machine that provides one or more aspects of storage or processing of information. Typically, the connection between the computer 1002 and the cloud storage system may be established over the LAN 1054 or WAN 1056, for example, via an adapter 1058 or a modem 1060, respectively. When the computer 1002 is connected to the associated cloud storage system, the external storage interface 1026 may manage the storage provided by the cloud storage system with the aid of the adapter 1058 or the modem 1060, as with other types of external storage. For example, the external storage interface 1026 may be configured to provide access to cloud storage sources as if those sources were physically connected to the computer 1002.

[0116] The computer 1002 may be operable to communicate with any wireless device or entity operatively arranged in wireless communication, such as a printer, scanner, desktop or portable computer, portable data assistant, communication satellite, any device or location associated with a wirelessly detectable tag (e.g., a kiosk, newsstand, store shelf, etc.), and telephone. This may include Wireless Fidelity (Wi-Fi) and Wireless technology. Therefore, the communication can be a predefined structure like a conventional network, or simply an ad hoc communication between at least two devices.

[0117] Fig.111 is a schematic block diagram of an example computing environment 1100 with which the disclosed subject matter can interact. The example computing environment 1100 includes one or more clients 4110. The client 4110 can be hardware or software (e.g., a thread, a process, a computing device). The example computing environment 1100 also includes one or more servers 1130. The server 1130 can also be hardware or software (e.g., a thread, a process, a computing device). For example, the server 1130 can accommodate threads to perform transformations by adopting one or more embodiments as described herein. One possible communication between the client 4110 and the server 1130 can be in the form of data packets suitable for transmission between two or more computer processes. The example computing environment 1100 includes a communication framework 1150, which can be used to facilitate communication between the client 4110 and the server 1130. The client 4110 is operably connected to one or more client data repositories 1120, which can be used to store information local to the client 4110. Similarly, server 1130 may be operably connected to one or more server data repositories 1140 , which may be used to store information local to server 1130 .

[0118] The present invention may be a system, method, apparatus or computer program product at any possible level of technical detail integration. The computer program product may include a computer-readable storage medium (or multiple media) having computer-readable program instructions thereon for causing a processor to perform various aspects of the present invention. The computer-readable storage medium may be a tangible device that can retain and store instructions used by an instruction execution device. The computer-readable storage medium may be, for example, but not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of computer-readable storage media may also include the following: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a static random access memory (SRAM), a portable compact disk read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanical encoding device (e.g., a punched card or a raised structure in a groove on which instructions are recorded), and any suitable combination of the foregoing. As used herein, computer-readable storage media should not be interpreted as transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., light pulses passing through fiber optic cables), or electrical signals transmitted through wires.

[0119] The computer-readable program instructions described herein can be downloaded to the corresponding calculation / processing equipment from the computer-readable storage medium, or downloaded to an external computer or external storage device via a network (for example, the Internet, a local area network, a wide area network or a wireless network). The network can include copper transmission cables, optical transmission optical fibers, wireless transmissions, routers, firewalls, switches, gateway computers or edge servers. The network adapter card or the network interface in each calculation / processing equipment receive computer-readable program instructions from the network, and forward computer-readable program instructions to be stored in the computer-readable storage medium in the corresponding calculation / processing equipment. The computer-readable program instructions for performing the operation of the present invention can be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-related instructions, microcodes, firmware instructions, state setting data, configuration data of integrated circuits, or source code or object code written in any combination of one or more programming languages, and the programming languages ​​include object-oriented programming languages ​​such as Smalltalk, C++, etc., and process programming languages ​​such as "C" programming languages ​​or similar programming languages. Computer readable program instructions can be executed entirely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on a remote computer, or completely on a remote computer or server. In the latter case, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (e.g., using an Internet service provider through the Internet). In some embodiments, electronic circuits including, for example, programmable logic circuits, field programmable gate arrays (FPGAs), or programmable logic arrays (PLAs) can execute computer readable program instructions to personalize the electronic circuits by utilizing the state information of the computer readable program instructions to perform aspects of the present invention.

[0120] Here, various aspects of the present invention are described with reference to the flowchart or block diagram of the method, device (system) and computer program product according to an embodiment of the present invention. It should be understood that each frame of the flowchart diagram or block diagram and the combination of frames in the flowchart diagram or block diagram can be implemented by computer-readable program instructions. These computer-readable program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device create a component for implementing the function / action specified in one or more frames of the flowchart or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium, which can indicate that the computer, programmable data processing device or other equipment works in a specific way, so that the computer-readable storage medium in which the instructions are stored includes an article, which includes instructions for implementing various aspects of the function / action specified in one or more frames of the flowchart or block diagram. The computer-readable program instructions can also be loaded onto a computer, other programmable data processing devices or other devices, so that a series of operating actions are performed on a computer, other programmable devices or other devices to produce a computer-implemented process, so that the instructions executed on a computer, other programmable devices or other devices implement the function / action specified in one or more frames of the flowchart or block diagram.

[0121] The flow charts and block diagrams in the accompanying drawings illustrate the architecture, functions and operations of possible implementations of the system, method and computer program product according to various embodiments of the present invention. In this regard, each frame in the flow chart or block diagram may represent a module, segment or instruction portion, which includes one or more executable instructions for implementing a specified logical function. In some alternative embodiments, the function indicated in the frame may not occur in the order indicated in the figure. For example, the two frames shown in succession can actually be performed substantially simultaneously, or these frames can sometimes be performed in reverse order, depending on the functions involved. It should also be noted that each frame of the block diagram or flow chart illustration and the combination of frames in the block diagram or flow chart illustration can be implemented by a system based on dedicated hardware that performs a specified function or action or performs a combination of dedicated hardware and computer instructions.

[0122] Although the subject matter has been described above in the general context of computer executable instructions of a computer program product running on one or more computers, it will be appreciated by those skilled in the art that the present disclosure may also be combined with other program modules or may be implemented in combination with other program modules. Typically, a program module includes routines, programs, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In addition, it will be appreciated by those skilled in the art that the computer-implemented method of the present invention may be practiced with other computer system configurations, including single-processor or multi-processor computer systems, small computing devices, large computers, and computers, handheld computing devices (e.g., PDAs, phones), microprocessor-based or programmable consumer or industrial electronics, etc. The illustrated aspects may also be practiced in a distributed computing environment, where tasks are performed by a remote processing device linked by a communication network. However, some (if not all) aspects of the present disclosure may be practiced on a stand-alone computer. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

[0123] As used in this application, the terms "component", "system", "platform", "interface", etc. may refer to or may include computer-related entities or entities related to an operating machine having one or more specific functions. The entities disclosed herein may be hardware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to, a process, a processor, an object, an executable file, an execution thread, a program, or a computer running on a processor. As an illustration, both an application running on a server and the server may be components. One or more components may reside within a process or an execution thread, and a component may be located on one computer or distributed between two or more computers. In another example, a corresponding component may be executed from various computer-readable media having various data structures stored thereon. Components may communicate via local or remote processes, such as according to signals having one or more data packets (e.g., data from a component interacting with another component in a local system, a distributed system, or interacting with other systems across a network such as the Internet via a signal). As another example, a component may be a device having a specific function provided by a mechanical part operated by an electrical or electronic circuit, which is operated by a software or firmware application executed by a processor. In this case, the processor may be internal or external to the device and may execute at least a portion of a software or firmware application. As yet another example, the component may be a device that provides a specific functionality through an electronic component without mechanical parts, where the electronic component may include a processor or other components to execute software or firmware that at least partially imparts the functionality of the electronic component. In one aspect, the component may emulate the electronic component via, for example, a virtual machine within a cloud computing system.

[0124] In addition, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless otherwise specified or clear from the context, "X employs A or B" is intended to mean any natural inclusive arrangement. That is, if X employs A; X employs B; or X employs both A and B, then "X employs A or B" is satisfied under any of the foregoing instances. As used herein, the term "and / or" is intended to have the same meaning as "or". In addition, the articles "one" and "an" used in this specification and the drawings should generally be interpreted as meaning "one or more", unless otherwise specified or clearly pointed to the singular form from the context. As used herein, the term "example" or "exemplary" is used to mean used as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited to these examples. In addition, any aspect or design described herein as "example" or "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to exclude equivalent exemplary structures and techniques known to those of ordinary skill in the art.

[0125] When used in this specification, the term "processor" may refer to substantially any computing processing unit or device, including but not limited to: a single-core processor; a single processor with software multi-threaded execution capability; a multi-core processor; a multi-core processor with software multi-threaded execution capability; a multi-core processor with hardware multi-threading technology; a parallel platform; and a parallel platform with distributed shared memory. In addition, the processor may refer to an integrated circuit, an application-specific integrated circuit (ASIC), a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic controller (PLC), a complex programmable logic device (CPLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. In addition, the processor may utilize nanoscale architectures, such as, but not limited to, transistors, switches, and gates based on molecules and quantum dots, in order to optimize space usage or enhance the performance of user devices. The processor may also be implemented as a combination of computing processing units. In the present disclosure, terms such as "repository", "storage device", "data repository", "data storage device", "data database", and substantially any other information storage component related to the operation and function of the component are used to refer to a "memory component", an entity embodied in a "memory", or a component including a memory. It should be understood that the memory or memory components described herein may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. As an illustration and not limitation, non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable ROM (EEPROM), flash memory, or non-volatile random access memory (RAM) (e.g., ferroelectric RAM (FeRAM)). Volatile memory may include RAM, which may, for example, act as an external cache memory. As an illustration and not limitation, RAM is available in many forms, such as synchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), direct Rambus RAM (DRRAM), direct Rambus dynamic RAM (DRDRAM), and Rambus dynamic RAM (RDRAM). In addition, the disclosed memory components or computer-implemented methods of the systems herein are intended to include, but are not limited to, including these and any other suitable types of memory.

[0126] What has been described above merely includes examples of systems and computer-implemented methods. Of course, for purposes of describing the present disclosure, it is not possible to describe every conceivable combination of components or computer-implemented methods, but many further combinations and permutations of the present disclosure are possible. In addition, to the extent that the terms "including," "having," "having," and the like are used in the detailed description, claims, appendices, and drawings, these terms are intended to be inclusive in a manner similar to the term "comprising," as if "including" is interpreted when used as a transitional word in a claim.

[0127] The description of various embodiments has been presented for the purpose of illustration, but is not intended to be exhaustive or limited to the disclosed embodiments. Many modifications and variations will be apparent without departing from the scope and spirit of the described embodiments. The terminology used herein is selected to best explain the principles of the embodiments, practical applications or technical improvements over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

[0128] Various non-limiting aspects of the various embodiments described herein are presented in the following clauses.

[0129] Clause 1: A system comprising: a processor that executes computer-executable components stored in a non-transitory computer-readable memory, the computer-executable components comprising: a virtualization component that generates a virtual icon representing a hardware-based component of a vehicle; a display component that displays the virtual icon on a touch display; and an interface component that receives input associated with activation of the virtual icon to implement functionality of the associated hardware-based component.

[0130] Clause 2: A system as described in any preceding clause, wherein the compliance component ensures that the generated virtual icon touch coordinates meet ISO-26262 to at least ASIL-A level.

[0131] Clause 3: A system as described in any preceding clause, wherein the compliance component ensures that touch activation of the virtual icon meets ISO-26262 at ASIL-B level.

[0132] Clause 4: A system according to any preceding clause, wherein the display component requires dual touch input to activate the functionality of the virtualization component, and wherein the dual touch event includes one of the following complex touch patterns: two presses of a soft button, one press of a soft button and a slide from a first position to a second position, or a slide from a first position to a second position.

[0133] Clause 5: A system according to any preceding clause, wherein the virtualization component generates virtual icons for operating interior or exterior vehicle lights and lighting.

[0134] Clause 6: A system according to any preceding clause, wherein the virtualization component generates a virtual icon for actuating a window or sunroof of the vehicle.

[0135] Clause 7: A system according to any preceding clause, wherein the virtualization component generates a virtual icon for adjusting a seat position.

[0136] Clause 8: A system according to any preceding clause, wherein the virtualization component generates a virtual icon for operating a vehicle door locking mechanism.

[0137] Clause 9: A system according to any preceding clause, wherein the virtualization component generates a virtual icon for controlling vehicle windshield wiper settings.

[0138] Clause 10: The system of any preceding clause, wherein the virtualization component generates a virtual icon for releasing or latching at least one of the following vehicle access points: a trunk, a hood, a charge port, or a fuel door.

[0139] Clause 11: A system according to any preceding clause, wherein the virtualization component generates a virtual icon for operating a vehicle gear selection or a driving performance mode.

[0140] Clause 12: The system of any preceding clause, wherein the virtualization component enables speech-based generation of the virtual icon.

[0141] In various cases, any suitable combination or combinations of clauses 1-12 may be implemented.

[0142] Clause 13: A computer-implemented method comprising: using a virtualization component to enable a user to generate a virtual icon representing a hardware-based component of a vehicle; using a display component to display the virtual icon on a touch display; and using an interface component to receive input associated with activation of the virtual icon to implement functionality of the associated hardware-based component.

[0143] Clause 14: A computer-implemented method according to any of the preceding clauses, further comprising requiring a double touch to activate a function of the virtualized component, and wherein the double touch event comprises one of the following complex touch patterns: two presses of a soft button, one press of a soft button and a slide from a first position to a second position, or a slide from a first position to a second position.

[0144] Clause 15: The computer-implemented method of any preceding clause, further comprising engaging the virtualization component to enable a user to generate virtual icons for operating interior or exterior vehicle lights and lighting.

[0145] Clause 16: The computer-implemented method of any preceding clause, further comprising engaging the virtualization component to enable a user to generate a virtual icon for actuating a window or sunroof of the vehicle.

[0146] Clause 17: The computer-implemented method of any preceding clause, further comprising engaging the virtualization component to enable a user to generate a virtual icon for operating a vehicle door locking mechanism.

[0147] Clause 18: The computer-implemented method of any preceding clause, further comprising engaging the virtualization component to enable a user to generate a virtual icon for controlling vehicle windshield wiper settings.

[0148] In various cases, any suitable combination or combinations of clauses 13-18 may be implemented.

[0149] Clause 19: A computer program product comprising a non-transitory computer-readable memory containing program instructions executable by a processor to cause the processor to: use a virtualization component to enable a user to generate a virtual icon representing a hardware-based component of a vehicle; use a display component to display the virtual icon on a touch display; and use an interface component to receive input associated with activation of the virtual icon to implement functionality of the associated hardware-based component.

[0150] Clause 20: A computer program product according to any preceding clause, wherein the program instructions are further executable to cause the processor to: engage the virtualization component to enable a user to generate a virtual icon for operating interior or exterior vehicle lights and lighting.

[0151] In various cases, any suitable combination or combinations of clauses 19-20 may be implemented.

[0152] In various cases, any suitable combination or combinations of clauses 1-20 may be implemented.

Claims

1. A system comprising: a processor that executes computer-executable components stored in a non-transitory computer-readable memory, the computer-executable components comprising: a virtualization component that generates virtual icons representing hardware-based components of the vehicle; a display component that displays the virtual icon on a vehicle display; and An interface component receives input associated with activation of the virtual icon to implement functionality of an associated hardware-based component.

2. The system according to claim 1, wherein: The compliance component ensures that the generated virtual icon touch coordinates meet ISO-26262 to at least ASIL-A level.

3. The system according to claim 1, wherein: The compliance component ensures that touch activation of the virtual icon meets ISO-26262 at ASIL-B level.

4. The system according to claim 3, wherein: The display component requires a dual touch input to activate a function of the virtualization component, and wherein the dual touch input comprises one of the following complex touch patterns: two presses of a soft button, one press of a soft button and a slide from a first position to a second position, or a slide from a first position to a second position.

5. The system according to claim 1, wherein: The virtualization component generates virtual icons for operating interior or exterior vehicle lights and lighting.

6. The system according to claim 1, wherein: The virtualization component generates a virtual icon for actuating a window or sunroof of the vehicle.

7. The system according to claim 1, wherein: The virtualization component generates a virtual icon for adjusting a seat position.

8. The system according to claim 1, wherein: The virtualization component generates a virtual icon for operating a door locking mechanism.

9. The system according to claim 1, wherein: The virtualization component generates a virtual icon for controlling vehicle windshield wiper settings.

10. The system according to claim 1, wherein: The virtualization component generates a virtual icon for releasing or latching at least one of the following vehicle access points: a trunk, a hood, a charging port, or a fuel door.

11. The system according to claim 1, wherein: The virtualization component generates a virtual icon for operating a vehicle gear selection or a driving performance mode.

12. The system of claim 1, wherein: The virtualization component enables speech-based generation of virtual icons.

13. A computer-implemented method comprising: using a virtualized component to enable a user to generate a virtual icon representing a hardware-based component of a vehicle; Displaying the virtual icon on the touch display using a display component; as well as An interface component is used to receive input associated with activation of the virtual icon to implement functionality of an associated hardware-based component.

14. The computer-implemented method of claim 11, further comprising requiring a double touch to activate a function of the virtualized component, and wherein: The double touch event includes one of the following complex touch patterns: two presses of a soft button, one press of a soft button and a slide from a first position to a second position, or a slide from a first position to a second position.

15. The computer-implemented method of claim 11, further comprising engaging the virtualization component to enable a user to generate virtual icons for operating interior or exterior vehicle lights and lighting. 16 . The computer-implemented method of claim 11 , further comprising engaging the virtualization component to enable a user to generate a virtual icon for actuating a window or sunroof of the vehicle. 17 . The computer-implemented method of claim 11 , further comprising engaging the virtualization component to enable a user to generate a virtual icon for operating a vehicle door locking mechanism.

18. The computer-implemented method of claim 11, further comprising engaging the virtualization component to enable a user to generate a virtual icon for controlling vehicle windshield wiper settings.

19. A computer program product comprising a non-transitory computer readable memory containing program instructions executable by a processor to cause the processor to: using a virtualized component to enable a user to generate a virtual icon representing a hardware-based component of a vehicle; displaying the virtual icon on a touch display using a display component; and An interface component is used to receive input associated with activation of the virtual icon to implement functionality of an associated hardware-based component.

20. The computer program product of claim 19, wherein: The program instructions are further executable to cause the processor to perform the following operations: The virtualization component is engaged to enable a user to generate virtual icons for operating interior or exterior vehicle lights and lighting.

Images