Method for ensuring an action on a member of a vehicle after a user presses a touch screen

Abstract

The present invention relates to a method and device for ensuring that an action has been carried out on a member of a vehicle after a user has pressed a touch screen of a display system of the vehicle. A first device of the display system transmits (21) a control datum. A second control device verifies (23) the consistency of the control datum. If the consistency of the control datum is verified, the second device transmits (24), to the first device, a datum representative of a confirmation of the execution of the action on the member of the vehicle, and the first device determines a rendering of the fourth datum which is displayed on the touch screen. Otherwise, the second device transmits (25), to the first device, a datum representative of an error notification and the first device determines a rendering of the fifth datum which is displayed on the touch screen.

Description

DESCRIPTION Title: Method for securing an action on a vehicle component following a user's touchscreen input technical field

[0001] The present invention claims priority from French application 2404343 filed on April 25, 2024, the content of which (text, drawings, and claims) is incorporated herein by reference. The present invention relates to securing actions on vehicle components following user touch of a touchscreen. Technological background

[0002] In the automotive field, it is common practice to use a solution combining physical buttons and indicator lights to implement critical safety-related functions in vehicle systems. Activating a button triggers a function (or action) of a vehicle component, and an indicator light illuminates as soon as that function (or action) is executed.

[0003] The solution combining physical buttons and indicator lights ensures that critical functions, such as activating emergency signals or setting safety functions, are reliably performed with tangible and direct user input because the physical nature combined with immediate visual feedback provides a clear and intuitive interface.

[0004] However, the solution combining physical buttons and indicator lights no longer meets the requirements and limitations of the new interfaces implemented in current vehicles because the cost of implementing this solution is high and its integration is often complex in increasingly confined spaces. Indeed, the production of physical buttons, especially when combined with indicator lights, involves significant material and assembly costs. Each The button requires additional mechanical components, wiring, and circuits for the indicator light, significantly increasing the overall manufacturing costs of the vehicle.

[0005] Furthermore, integrating physical buttons into a vehicle's design requires space allocation and electrical integration, which complicates dashboard layout and wiring diagrams. This complexity increases the effort and costs involved in vehicle assembly and design.

[0006] Furthermore, the use of physical buttons imposes design and ergonomic limitations because the buttons have fixed positions and sizes. Physical buttons are assigned specific positions on the dashboard or center console, which can limit the ergonomic optimization of the control devices and the aesthetic appeal of the vehicle's interior.

[0007] Implementing critical functions via physical buttons also limits the adaptability of these functions because, as vehicle features evolve, updating or adding new safety features can become difficult. Physical controls cannot be easily reconfigured or updated without significant hardware modifications, making it challenging to adapt to new safety technologies or user preferences.

[0008] Implementing critical functions with physical buttons also presents wear and tear and environmental impact issues. Over time, physical buttons can wear down, leading to potential failures or the need for replacement. This degradation can affect the reliability of safety-critical functions and increase maintenance costs. Furthermore, the production and disposal of the physical components used in buttons and indicator lights contribute to the environmental footprint of vehicle manufacturing. Reducing these components can be a step toward more sustainable vehicle design and production.

[0009] To overcome the drawbacks of solutions combining physical buttons and indicator lights, solutions based on touch interfaces and software can be used to secure critical functions. These solutions, based on touch interfaces and software, allow for more flexible, adaptable, and less expensive control of critical functions in vehicle embedded systems.

[0010] However, the implementation of these solutions based on touch interfaces and software poses some problems.

[0011] One of these challenges is ensuring the reliability and responsiveness of these solutions. Software commands must match or exceed the reliability of physical buttons, a significant challenge given the inherent robustness of mechanical interfaces. Furthermore, it is crucial to guarantee that touch interactions are as immediate and responsive as physical buttons. Delays or lags could lead to dangerous situations or user frustration.

[0012] Another challenge is providing clear and concise feedback. It's not easy to replicate the tactile feedback of a physical button press in a touchscreen environment. Furthermore, while software interfaces can use visual and audible signals to confirm actions on vehicle components, the design of these signals must be carefully crafted to be as intuitive as the feedback from physical buttons.

[0013] Users accustomed to physical buttons with indicator light feedback may need time to adapt to touch interfaces, especially for critical safety functions. Ensuring an intuitive design and clear guidance is important for a smooth transition and user acceptance of these touch interfaces.

[0014] Furthermore, software-based systems must undergo rigorous testing to meet safety standards and certifications, such as compliance with Automotive Safety Integrity Levels (ASILs). Touchscreen-based solutions may require complex and resource-intensive implementations to meet any of these ASIL levels. Indeed, detecting and managing software errors to maintain a given safety level can be challenging.

[0015] Another challenge in implementing touchscreen and software-based solutions is managing the available space on a touchscreen used to execute commands. Allocating dedicated space on a touchscreen for commands related to critical functions, while also balancing other needs such as infotainment, requires careful design and prioritization.

[0016] Another challenge in implementing touch-based solutions and software concerns protection against malfunctions and tampering. Software systems introduce vulnerabilities to potential problems, bugs, or security flaws. Implementing robust security measures to protect against these risks is also a crucial consideration.

[0017] The transition to touchscreen and software-based solutions for securing critical functions represents a significant shift in vehicle user interface design. While offering potential advantages in terms of flexibility and cost, it is crucial to address the various challenges outlined above related to reliability, user experience, safety compliance, and the integration of these solutions. Summary of the present invention

[0018] One object of the present invention is to solve at least one of the problems of the technological background described above.

[0019] According to a first aspect, the present invention relates to a method of ensuring that an action on a component of a vehicle has been performed following a user's press on a touch screen of a vehicle display system, the method comprising the following steps: - transmission, by a first device of the display system and intended for a second device of the display system, of a first control data comprising a first data representative of information defining a region of interest on the touch screen corresponding to the user's press and associated with the action on the vehicle's component, a second data representing a description of the press on the region of interest associated with the action on the vehicle's component and a third data representing a value of a counter associated with the region of interest and incremented with each new press on the region of interest, the counter associated with each region of interest being present on the first device and another counter synchronized to said counter of the first device being present on the second device; - emission, by the second device, of a second command data to the vehicle component that must perform the action indicated by the user's press on the region of interest; - verification, by the second device, of the consistency of the first command data by verifying that the first, second and third data are received and taken into account by the second device, that the second data describes a press which triggers the action associated with the region of interest defined by the information represented by the first data and that the value of the counter represented by the third data is equal to a current value associated with the defined region of interest; - if the consistency of the first command data is verified, the second device emits a fourth data point to the first device, representing confirmation of the execution of the action on the vehicle component; and the first device determines a rendering of the fourth data point, which is displayed on the touch screen; - if the consistency of the first command data is not verified, the second device emits a fifth data representing an error notification to the first device; and the first device determines a rendering of the fifth data which is displayed on the touch screen.

[0020] The method uses touch interactions to launch commands related to the implementation of critical functions. In particular, the method uses regions of interest that are synchronized on a touchscreen interface and associated with a incremental counter mechanism for each region of interest to ensure the reliability and responsiveness of these commands.

[0021] The synchronized counter mechanism ensures that every command data is verified from launch to execution, thereby improving the reliability and safety of critical functions.

[0022] The process offers a cost-effective, flexible, and user-friendly alternative without compromising the critical safety and feedback aspects necessary for vehicle operation. This process addresses the need for tactile feedback, clear user confirmation, and rigorous safety standards.

[0023] The process verifies end-to-end security for touch commands, solely within the software domain. This process ensures that commands are not only sent but also received and executed as intended, thus providing a robust mechanism for detecting and compensating for any failures in real time.

[0024] By eliminating the need for additional hardware for safety verification, the method presents a solution for achieving ASIL A compliance for touch interactions. This software-centric approach minimizes material costs and simplifies the manufacturing process, thus offering significant economic advantages. By achieving ASIL A compliance for touch controls in infotainment systems, the invention establishes a new standard for safety in vehicle controls. It addresses the challenge of maintaining stringent safety standards in increasingly software-driven automotive environments.

[0025] The process enables more intuitive and engaging user interactions with vehicle safety systems, leveraging touch interfaces and dynamic feedback to enhance the overall driving experience.

[0026] The process recognizes the vulnerabilities and variability inherent in software systems, particularly in the management of critical functions. It compensates for these potential weaknesses by improving the ability to reliably detect and execute touch commands.

[0027] The process allows for adaptability to updates, accommodating new safety features or user preferences without physical modifications to the vehicle's interior design. The software-centric approach ensures the system can easily adapt to new technologies and user interaction paradigms, such as augmented reality displays or advanced haptic feedback, keeping vehicles at the forefront of technological advancements.

[0028] According to one variant, the rendering of the fourth data point is a rendering of a haptic effect implemented by a vehicle accessory.

[0029] According to one variant, the rendering of the fifth data point is a rendering of a haptic effect implemented by a vehicle accessory.

[0030] According to one variant, the fifth piece of data is also representative of a cause of error.

[0031] According to a second aspect, the present invention relates to a security device that ensures an action on a vehicle component has been performed following a user's press on a touch screen of a vehicle display system, the system comprising a memory associated with a processor configured for the implementation of the steps of the process according to the first aspect of the present invention.

[0032] According to a third aspect, the present invention relates to an on-board display system for a vehicle comprising a device according to the second aspect of the present invention.

[0033] According to a fourth aspect, the present invention relates to a vehicle comprising a display system according to the third aspect of the present invention.

[0034] According to one variant, the display system is a vehicle infotainment system.

[0035] The process integrates seamlessly with existing infotainment systems, using the screen as the primary interface for the data entry and feedback. This integration facilitates a unified user experience and simplifies the implementation of critical functions, thus avoiding the complexity and costs associated with integrating separate security modules.

[0036] Current infotainment systems, increasingly reliant on touchscreens, struggle to support safety-related controls without compromising flexibility and user experience. This method offers a solution that seamlessly integrates these controls, preserving the overall functionality and aesthetic appeal of the infotainment system.

[0037] The process ensures the reliability of touch controls for safety-critical functions in the variable and software-intensive environment of infotainment systems.

[0038] By focusing on an end-to-end software-only solution with the touchscreen, the process bypasses the inherent weaknesses of infotainment systems, thereby improving security without incurring significant costs.

[0039] According to a fifth aspect, the present invention relates to a computer program which includes instructions adapted for carrying out the steps of the process according to the first aspect of the present invention, in particular when the computer program is executed by at least one processor.

[0040] Such a computer program can use any programming language, and be in the form of source code, object code, or an intermediate form between source code and object code, such as in a partially compiled form, or in any other desirable form.

[0041] According to a sixth aspect, the present invention relates to a computer-readable recording medium on which is recorded a computer program comprising instructions for carrying out the steps of the process according to the first aspect of the present invention.

[0042] On the one hand, the recording medium can be any entity or device capable of storing the program. For example, the medium may include a storage means, such as ROM, RAM, a CD-ROM, or a ROM memory of the microelectronic circuit type, or a magnetic recording device or a hard drive.

[0043] On the other hand, this recording medium can also be a transmissible medium such as an electrical or optical signal, such a signal being able to be transmitted via an electrical or optical cable, by conventional or radio frequency, by self-directing laser beam, or by other means. The computer program according to the present invention can, in particular, be downloaded from a network such as the Internet.

[0044] Alternatively, the recording medium may be an integrated circuit in which the computer program is incorporated, the integrated circuit being adapted to execute or to be used in the execution of the process in question. Brief description of the figures

[0045] Other features and advantages of the present invention will become apparent from the description of the specific and non-limiting embodiments of the present invention below, with reference to the attached Figures 1 to 4, in which:

[0046] [Fig. 1] schematically illustrates part of the passenger compartment of an electric vehicle, according to an example.

[0047] [Fig. 2] schematically illustrates a display system 1 of a vehicle (not shown) according to a particular and non-limiting embodiment of the present invention.

[0048] [Fig. 3] illustrates a flowchart of the different steps of a process for ensuring that an action on a component of a vehicle has been carried out following a user's press on a touch screen of a vehicle display system, according to a particular and non-limiting embodiment of the present invention.

[0049] [Fig. 4] illustrates a security device that an action on a vehicle component has been performed following a user's press on a touch screen of a vehicle display system, according to a particular and non-limiting embodiment of the present invention. Description of examples of achievements

[0050] A method and a device for ensuring that an action on a vehicle component has been performed following a user's press on a touch screen of a vehicle display device will now be described in what follows with joint reference to Figures 1 to 4. The same elements are identified with the same reference signs throughout the description that follows.

[0051] The terms "first," "second" (or "firsts," "seconds"), etc., are used in this document by arbitrary convention to identify and distinguish different elements (such as operations, means, etc.) implemented in the embodiments described below. Such elements may be distinct or correspond to a single element, depending on the embodiment.

[0052] According to a particular and non-limiting embodiment of the present invention, a first device of a vehicle display system transmits to a second device of the display system a first control signal comprising a first data point representing information defining a region of interest on a vehicle touchscreen corresponding to a touch by a vehicle user and associated with an action on a vehicle component, a second data point representing a description of the touch on the region of interest associated with the action on the vehicle component, and a third data point representing a value of a counter associated with the region of interest and incremented with each subsequent touch on the region of interest. The counter associated with each region of interest is present on the first device, and another counter synchronized with said counter of the first device is present on the second device.The second device sends a second command signal to the vehicle component that will perform the action indicated by the user's press on the region of interest. The second device verifies the consistency of the first command signal by checking that the first, second, and third signals are received and processed by the second device, and that the second signal describes a press that triggers the action associated with the defined region of interest. The information represented by the first data point and the counter value represented by the third data point must be equal to a current value associated with the defined region of interest. If the consistency of the first command data point is verified, the second device sends a fourth data point to the first device, representing confirmation that the action on the vehicle component has been executed, and the first device determines a rendering of this fourth data point, which is displayed on the touchscreen. If the consistency of the first command data point is not verified, the second device sends a fifth data point to the first device, representing an error notification, and the first device determines a rendering of this fifth data point, which is displayed on the touchscreen.

[0053] Figure 1 schematically illustrates a part of the passenger compartment of a vehicle, according to a particular and non-limiting embodiment of the present invention.

[0054] The vehicle corresponds, for example, to a land vehicle, for example a car, a truck, a bus, a utility vehicle.

[0055] The vehicle includes a display system comprising one or more screens, for example a screen 101 with a touch interface 102 integrated into the dashboard 11 and a computer configured to control the display of content(s) on the touch screen 101. The computer corresponds, for example, to the computer of the infotainment system, known as the IVI computer (from the English "In-Vehicle Infotainment" or in French "Infodivertissement étoilé") of the vehicle.

[0056] The 101 touch screen corresponds for example to an LCD type screen (from the English "Liquid Crystal Display" or in French "Affichage à cristals liquide"), for example of type TFT (from the English "Thin-Film Transistor" or in French "Transistor en film mince"), or OLED (from the English "Organic Light-Emitting Diode" or in French "Diode électroluminescente organique").

[0057] The 101 touchscreen is configured to display content for the driver and passengers of the vehicle. The 101 touchscreen is also configured to allow the driver and / or passengers to interact with one or more on-board vehicle systems via a human-machine interface. (HMI) displayed on touch screen 101. For example, touch screen 101 is configured to interact with the I VI system.

[0058] In a particular embodiment, the vehicle incorporates one or more embedded systems, each controlled by one or more computers. These computers, along with computer I-VI, form, for example, a multiplexed architecture for providing various services essential for the proper functioning of the vehicle and for assisting the driver and / or passengers in controlling the vehicle through the control of the embedded system(s).Computers communicate and exchange data with each other via one or more computer buses, for example a CAN data bus (from the English "Controller Area Network" or in French "Réseau de contrôlers"), CAN FD (from the English "Controller Area Network Flexible Data-Rate" or in French "Réseau de contrôlers à débit de données flexible"), FlexRay (according to the ISO 17458 standard), LIN (from the English "Local Interconnect Network" or in French "Réseau interconnecté local") or Ethernet (according to the ISO / IEC 802-3 standard).

[0059] Figure 2 schematically illustrates a display system 1 of the vehicle of figure 1 according to a particular and non-limiting embodiment of the present invention.

[0060] The display system 1 comprises a first device 10 and a second device 11.

[0061] For example, the first device 10 could be a vehicle display device.

[0062] According to one particular embodiment of the present invention, the display system may be an on-board infotainment system of the vehicle of Figure 1 and the second device 11 may be a central processing unit which manages this infotainment system (IV), including the execution of touch commands and communication with the vehicle's safety systems.

[0063] The first device 10 includes a microcontroller 103 and the touch screen 101 configured to interact with the touch interface 102.

[0064] The touch interface 102 is configured to define at least one region of interest on the touchscreen 101 and to associate a counter with each defined region of interest. Each region of interest is also associated with an action on a vehicle component. This action implements a critical function that is secured by the method described in relation to Figure 3. Each counter is initialized to a value, for example, 0. The touch interface 102 is also configured to increment a counter associated with a region of interest as soon as a user touches that region of interest.

[0065] The touch interface 102 is also configured to detect a touch on a region of interest and to provide the microcontroller 103 with information defining a region of interest on the touch screen 101 following a user touch on that region of interest and to provide a value of the incremented counter associated with that region of interest.

[0066] The microcontroller 103 is configured to send a first command data C1 to the first microcontroller 111. The first command data includes a first data D1 representing information defining a region of interest on the touch screen following a user press on this region of interest, a second data D2 representing a description of the press on the region of interest associated with the action on the vehicle component and a third data D3 representing a value of a counter associated with the region of interest and incremented with each new press on the region of interest.

[0067] The second device 11 is also configured to implement, in software form, a mechanism for verifying the execution of commands via a synchronized counter mechanism for each region of interest, thus ensuring end-to-end security compliance.

[0068] The second device 11 includes a first microcontroller 111, a first control unit 112, a second control unit 113, a security unit 114 and a second microcontroller 115.

[0069] The first microcontroller 111 and the microcontroller 103 are configured to exchange data with each other via a communication channel, for example, of the CAN type.

[0070] The first microcontroller 111 is configured to provide the first command data C1 to the securing unit 114.

[0071] The security unit 114 is configured to receive the first command data C1 and to send a second command data C2 to a vehicle component, defining an action on the vehicle component.

[0072] The first microcontroller 111 is also configured to provide the first data D1 to the first driver unit 112 and to provide the second data D2 to the second driver unit 113.

[0073] The first control unit 112 is configured to check if the first data D1 is received by the first microcontroller 111 and to provide the first received data D1 to the security unit 114.

[0074] The second control unit 113 is configured to check if the second data D2 is received by the first microcontroller 111 and to provide the second received data D2 to the security unit 114.

[0075] The security unit 114 is also configured to check the consistency of the first command data C1 by verifying that the first (D1), second (D2) and third (D3) data are received and taken into account by the second device 11, that the second data D2 describes a press which triggers the action associated with the region of interest defined by the information represented by the first data D1 and that the counter value represented by the third data D3 is equal to a current value associated with the defined region of interest.

[0076] The first microcontroller 111 is also configured to send a fourth data D4 and a fifth data D5 to the microcontroller 103. The fourth data D4 represents a confirmation of the execution of the action on the vehicle component and the fifth data D5 represents an error notification and, alternatively, a cause of a verification error.

[0077] The microcontroller 103 is also configured to determine a rendering of the fourth (D4) and fifth (D5) data and to drive the display of the rendering on the touch screen 101.

[0078] Figure 3 illustrates a flowchart of the different steps of a process for securing that an action on a component of a vehicle has been carried out following a user's press on a touch screen of a vehicle display system, according to a particular and non-limiting embodiment of the present invention.

[0079] In step 21, the first device 10 transmits to the second device 11 the first control data C1, comprising the first data point D1 representing information defining a region of interest on the touchscreen 101 corresponding to the user's touch and associated with the action on the vehicle component; the second data point D2 representing a description of the touch on the region of interest associated with the action on the vehicle component; and the third data point D3 representing a value of a counter associated with the region of interest and incremented with each new touch on the region of interest. The counter associated with each region of interest is present on the first device 10, and another counter synchronized to said counter of the first device 10 is present on the second device 11. Thus, when the counter of the first device 10 is incremented, the counter of the second device 11 is also incremented.The counter synchronization mechanism ensures that the order data to be checked corresponds to the last order issued by the user.

[0080] In a step 22, the second device 11 emits the second command data C2 to the vehicle organ that must perform the action indicated by the user's press on the region of interest.

[0081] In a step 23, the second device 11 checks the consistency of the first control data C1 by verifying that the first (D1), second (D2) and third (D3) data are received and taken into account by the second device 11, that the second data D2 describes a press which triggers the action associated with the region of interest defined by the information represented by the first data D1 and that the value of the counter represented by the third data D3 is equal to a current value associated with the defined region of interest.

[0082] If the consistency of the first command data C1 is verified, in step 24, the second device 11 transmits to the first device 10, the fourth data D4 representing a confirmation of the execution of the action on the vehicle organ and the first device 10 determines a rendering of the fourth data D4 which is displayed on the touch screen 101.

[0083] If the consistency of the first command data C1 is not verified, the second device 11 sends to the first device 10, a fifth data D5 representing an error notification and the first device 10 determines a rendering of the fifth data D5 which is displayed on the touch screen 101.

[0084] According to a particular and non-limiting embodiment of the present invention, the rendering of the fourth data D4 is a rendering of a haptic effect implemented by an accessory of the vehicle.

[0085] According to a particular and non-limiting embodiment of the present invention, the rendering of the fifth data D5 is a rendering of a haptic effect implemented by an accessory of the vehicle.

[0086] According to a particular and non-limiting embodiment of the present invention, the fifth data point D5 is further representative of a cause of the error.

[0087] According to one variant, the data exchanges between the first microcontroller 111, the first control unit 112, the second control unit 113, the security unit 114 and the second microcontroller 115 can rely on redundant processing paths within the second device 11, thus improving error detection and providing failover options in case of failure of the main path.

[0088] According to one variant, the definition of regions of interest can adapt according to a context of the display system or user preferences, coupled with dynamic feedback mechanisms (visual, auditory and haptic) which can adjust according to the urgency or importance of the first command data.

[0089] This variant strikes an optimal balance between display system flexibility, user experience, and security. By allowing regions of interest to adapt to different contexts and providing multimodal feedback to the user, this variant addresses the main challenges related to interaction. User Y1 with safety-related controls. It makes touch controls more intuitive and reliable, without compromising the safety standards required for ASIL A compliance.

[0090] This variant's emphasis on dynamic adaptation and comprehensive feedback mechanisms aligns well with current trends toward more interactive and user-centric vehicle infotainment systems. It provides a solid framework for future enhancements, including the potential integration of more advanced predictive features based on artificial intelligence, making it a future-proof solution in the evolution of vehicle control systems.

[0091] Figure 4 schematically illustrates a device 3 configured for controlling a display system of an electric vehicle, for example, the electric vehicle 10, and / or for controlling functions implemented by a navigation system associated with a warning system and a route planning module of the electric vehicle 10, according to specific and non-limiting embodiments of the present invention. The device 3 corresponds, for example, to a device embedded in the electric vehicle 10, for example, a computer.

[0092] Device 3 is, for example, configured to carry out steps 22 to 25 of the process described opposite Figure 3. Examples of such a device 3 include, but are not limited to, embedded electronic equipment such as a vehicle's on-board computer or an electronic control unit such as an ECU (Electronic Control Unit). The elements of device 3, individually or in combination, can be integrated into a single integrated circuit, into several integrated circuits, and / or into discrete components. Device 3 can be implemented as electronic circuits or software (or computer) modules, or a combination of electronic circuits and software modules.

[0093] Device 3 includes one (or more) processor(s) 30 configured to execute instructions for carrying out the steps of the process and / or for executing instructions from the software embedded in Device 3. The processor 30 may include integrated memory, an input / output interface, and various circuits known to those skilled in the art. Device 3 further includes less a memory 31 corresponding for example to volatile and / or non-volatile memory and / or includes a memory storage device which may include volatile and / or non-volatile memory, such as EEPROM, ROM, PROM, RAM, DRAM, SRAM, flash, magnetic or optical disk.

[0094] The computer code of the embedded software(s) including the instructions to be loaded and executed by the processor is for example stored in the memory 31.

[0095] According to various particular and non-limiting embodiments, the device 3 is coupled in communication with other similar devices or systems and / or with communication devices, for example a TCU (from the English “Telematic Control Unit” or in French “Telematic Control Unit”), for example via a communication bus or through dedicated input / output ports.

[0096] According to a specific and non-limiting embodiment, device 3 includes a block 32 of interface elements for communicating with external devices. The interface elements of block 32 include one or more of the following interfaces: - radio frequency RF interface, for example of the Wi-Fi® type (according to IEEE 802.11), for example in the 2.4 or 5 GHz frequency bands, or of the Bluetooth® type (according to IEEE 802.15.1), in the 2.4 GHz frequency band, or of the Sigfox type using UBN (Ultra Narrow Band) radio technology, or LoRa in the 868 MHz frequency band, LTE (Long-Term Evolution), LTE-Advanced; - USB interface (from the English "Universal Serial Bus" or "Universal Serial Bus" in French); - HDMI interface (from the English "High Definition Multimedia Interface", or "High Definition Multimedia Interface" in French); - LIN interface (from the English "Local Interconnect Network", or in French "Réseau interconnecté local").

[0097] According to another particular and non-limiting embodiment, the device 3 includes a communication interface 33 which enables communication with other devices (such as other computers in the embedded system) via a communication channel 330. The communication interface 33 corresponds, for example, to a transmitter configured to transmit and receive information and / or data via the communication channel 330. The communication interface 33 corresponds, for example, to a CAN-type wired network.

[0098] According to a particular and non-limiting embodiment, the device 3 can provide output signals to one or more external devices, such as a display screen 340, touch or not, one or more speakers 350 and / or other peripherals 360 (projection system) via output interfaces 34, 35 and 36 respectively. According to a variant, one or more of the external devices is integrated into the device 3.

[0099] Of course, the present invention is not limited to the embodiments described above but extends to a method for verifying that an action on a vehicle component has been performed following a user's touchscreen on a vehicle display system. This method would include secondary steps without falling outside the scope of the present invention. The same would apply to a device configured to implement such a method.

[0100] The present invention also relates to a display system comprising device 3 of figure 4.

[0101] The present invention also relates to a vehicle, for example an automobile or more generally an autonomous land-powered vehicle, comprising the display system 1.

Claims

CLAIMS 1. A method for ensuring that an action on a vehicle component has been performed following a user's touchscreen input on a vehicle display system, the method comprising the following steps: - emission (21), by a first device of the display system and to a second device of the display system, of a first control data comprising a first data representing information defining a region of interest on the touch screen corresponding to the user's press and associated with the action on the vehicle's component, a second data representing a description of the press on the region of interest associated with the action on the vehicle's component and a third data representing a value of a counter associated with the region of interest and incremented with each new press on the region of interest, the counter associated with each region of interest being present on the first device and another counter synchronized with said counter of the first device being present on the second device; - emission (22), by the second device, of a second command data to the vehicle component that must perform the action indicated by the user's press on the region of interest; - verification (23), by the second device, of the consistency of the first command data by verifying that the first, second and third data are received and taken into account by the second device, that the second data describes a press which triggers the action associated with the region of interest defined by the information represented by the first data and that the value of the counter represented by the third data is equal to a current value associated with the defined region of interest; - if the consistency of the first command data is verified, emission (24), by the second device to the first device, of a fourth data representing a confirmation of the execution of the action on the vehicle component; and the first device determines a rendering of the fourth data which is displayed on the touch screen; - if the consistency of the first command data is not verified, emission (25), by the second device to the first device, of a fifth data representing an error notification; and the first device determines a rendering of the fifth data which is displayed on the touch screen.

2. Method according to claim 1, wherein the rendering of the fourth data is a rendering of a haptic effect implemented by an accessory of the vehicle.

3. Method according to claim 1, wherein the rendering of the fifth data is a rendering of a haptic effect implemented by a vehicle accessory.

4. A method according to claim 1, wherein the fifth piece of data is further representative of a cause of error.

5. A security device that ensures an action on a vehicle component has been performed following a user's press on a touch screen of a vehicle display system, said device (3) comprising a memory (31) associated with at least one processor (30) configured to carry out the steps of the method according to any one of claims 1 to 4.

6. Computer program comprising instructions for implementing the method according to any one of claims 1 to 4, when these instructions are executed by a processor.

7. Computer-readable recording medium on which is recorded a computer program comprising instructions for carrying out the steps of the process according to any one of claims 1 to 4.

8. Vehicle on-board display system comprising a device according to claim 5.

9. Vehicle comprising a display system according to claim 8.

10. Vehicle according to claim 9, wherein the display system is a vehicle infotainment system.

Images