Intelligent cabin controller virtualization general touch screen control method and intelligent cabin controller

Abstract

The invention discloses an intelligent cabin controller virtualization general touch screen control method and an intelligent cabin controller, and the method comprises the steps: in a QNX host system, receiving and analyzing original input data from physical touch hardware through a standard touch screen driver, and generating a standardized touch event containing coordinate information; transmitting the standardized touch event to a touch event dispatcher running on the QNX host system; the touch event dispatcher reads coordinate information of the touch event and compares the coordinate information with a preset distribution configuration rule; the distribution configuration rule defines a coordinate range of one or more regions on the screen and a corresponding target operating system. Multiple sets of complete inputs are replaced by one central distributor, repeated occupation of system resources is reduced, the equipment utilization rate is improved, the data transmission efficiency is improved, the overall safety of the system is high, and the system has extremely high portability and expansibility.

Description

Technical Field

[0001] This invention relates to the field of automotive vehicle control technology, and in particular to a virtualized universal touchscreen control method for an intelligent cockpit controller and an intelligent cockpit controller. Background Technology

[0002] With the rapid development of automotive intelligence, intelligent cockpit systems are evolving towards greater integration and complexity. Modern intelligent cockpit controllers typically need to run multiple operating systems with different functions and real-time requirements simultaneously. For example, the instrument panel system needs to run the highly secure and real-time-compliant QNX operating system to display key vehicle information, while the infotainment system is better suited to running the ecosystem-rich Android operating system to provide navigation, audio-visual, and other functions.

[0003] To integrate these heterogeneous operating systems on a single hardware platform, virtualization technology (especially Type-1 hypervisors) has been widely adopted. The QNX Hypervisor, as a mature embedded system virtualization solution, allows multiple guest operating systems, such as QNX and Android, to run simultaneously on a single system-on-a-chip (SoC), achieving hardware resource sharing and isolation, and reducing system cost and complexity.

[0004] However, this architecture also brings new Human-Computer Interaction (HMI) challenges. One core issue is how to efficiently, accurately, and seamlessly distribute input from a single physical touchscreen to operating systems running on different virtual machines. Traditional solutions have the following drawbacks: Software redundancy: Configuring a separate touchscreen driver and input processing module for each virtual machine leads to a waste of system resources and increases memory usage and CPU overhead.

[0005] Coordination complexity: The lack of a global coordinator requires complex cross-virtual machine communication mechanisms to determine which system should respond when a touch event occurs, increasing the complexity and latency of the system design.

[0006] User experience fragmentation: If the dispatch logic is inaccurate, touch events may be dispatched incorrectly (for example, intending to operate an Android application but triggering a QNX system control), or users may need to perform cumbersome manual switching (such as switching with a physical button), resulting in a fragmented and inconsistent user experience.

[0007] Lack of versatility: Existing solutions are often tightly coupled with specific hardware or software versions, making it difficult to adapt to cockpit platforms with different screen sizes, resolutions, or operating system versions, resulting in poor portability and versatility. Summary of the Invention

[0008] In order to overcome the above-mentioned problems in the prior art, the present invention proposes a virtualized universal touch screen control method for intelligent cockpit controllers and an intelligent cockpit controller.

[0009] The technical solution adopted by this invention to solve its technical problem is: a virtualized universal touchscreen control method for intelligent cockpit controllers, comprising the following steps: Step 1, Touch Event Acquisition: In the QNX host system, raw input data from the physical touch hardware is received and parsed through the standard touch screen driver to generate standardized touch events containing coordinate information; Step 2, Event delivery to the dispatcher: The standardized touch events obtained in Step 1 are delivered to a touch event dispatcher running on a QNX host system; Step 3, Coordinate Range Judgment and Routing Decision: The touch event dispatcher reads the coordinate information of the touch event and compares it with the preset dispatch configuration rules; In step 3, the distribution configuration rules define the coordinate range of one or more areas on the screen and their corresponding target operating systems. The target operating systems include at least one QNX host system and at least one Guest OS system.

[0010] The above-mentioned intelligent cockpit controller virtualization universal touch screen control method, wherein the standardized touch event generated in step 1 includes absolute coordinates, touch state, and timestamp.

[0011] The above-mentioned intelligent cockpit controller virtualization universal touchscreen control method, wherein the Guest OS system is one or more of Android, Linux, and QNX systems.

[0012] The above-mentioned intelligent cockpit controller virtualization universal touch screen control method, step 3 specifically involves: determining the target operating system corresponding to the triggering event based on coordinate information; if the coordinates belong to the QNX region, then entering the QNX system branch, entering coordinate mapping, converting absolute coordinates to relative coordinates, injecting coordinate data and touch state into the QNX event queue, and the event being processed by QNX's own input system and application; If the coordinates belong to the Guest OS system, they enter the QNX Hypervisor virtual machine. Through coordinate mapping, the absolute coordinates are converted into relative coordinates. The coordinate data and touch state enter the Hypervisor virtual data transmission channel to send events to the virtual Guest OS system. The touch screen driver of the virtual Guest OS system receives the data and then transmits the data and events to the Guest OS system application framework to complete the interactive response.

[0013] The above-mentioned intelligent cockpit controller virtualization universal touch screen control method converts absolute coordinates to relative coordinates by subtracting the starting coordinates of the corresponding target system area from the absolute coordinate value.

[0014] A smart cockpit controller is used to implement the above-described smart cockpit controller virtualization universal touchscreen control method, including a hardware layer, a virtualization layer, and a virtual machine layer, wherein the hardware layer includes a processor, memory, and a physical touchscreen; The virtualization layer uses QNX Hypervisor to abstract and partition hardware resources; The virtual machine layer includes at least one privileged virtual machine running the QNX operating system and at least one guest virtual machine running the Guset OS; The privileged virtual machine running the QNX operating system integrates a touch control function module, which is used to collect touch events and distribute the collected touch events to the corresponding target operating system.

[0015] The aforementioned intelligent cockpit controller includes a touch control module comprising: The touchscreen driver module is used to acquire the raw input from the physical touchscreen. The touch event standardization module is used to convert raw input into standardized events; The touch event dispatcher module has a built-in dispatch rule configuration unit and a routing logic execution unit, which are used to make dispatch decisions based on the coordinate range; The coordinate mapping module is used to remap the received coordinates for use by the HMI program; The QNX local event injection interface is used to distribute events to this system. The Guest OS virtual machine event forwarding interface is used to forward events to the Guest OS system via the Hypervisor.

[0016] The beneficial effects of this invention are: 1. High efficiency and low overhead: By replacing multiple complete inputs with a central distributor, the repeated occupation of system resources is reduced, CPU and memory overhead is reduced, event processing efficiency is improved, and the QNX system and Android system can share the same touch controller, thereby improving device utilization and data transmission efficiency.

[0017] 2. Precise distribution and seamless experience: Routing is based on precise coordinate ranges, avoiding accidental operations. Users can directly operate the corresponding system in different screen areas without manual switching, achieving a seamless integrated interactive experience.

[0018] 3. Strong Isolation and Security: The event distribution logic runs in a privileged virtual machine (QNX host). The client system does not need to, and does not directly access, the physical touch hardware, which meets the requirements of functional safety isolation and enhances the overall system security. The Android system uses virtual devices, which are independent of physical circuits, reducing system coupling, improving Android system compatibility, and increasing development efficiency.

[0019] 4. High versatility and configurability: The method is not dependent on any specific application. Distribution rules (such as the mapping relationship between coordinate range and system) can be flexibly defined through configuration files, making it easy to adapt to different screen layouts, resolutions and new guest operating systems. It has strong portability and scalability. Attached Figure Description

[0020] Figure 1 This is a schematic diagram of the system architecture of the present invention; Figure 2 This is a schematic diagram of the system functional architecture in the existing technology; Figure 3 This is a schematic diagram of the touchscreen area allocation in an embodiment of the present invention; Figure 4 This is a flowchart of the touch event distribution process of the present invention. Detailed Implementation

[0021] To enable those skilled in the art to better understand the technical solution of the present invention, the present invention will be described in detail below with reference to the accompanying drawings and specific embodiments.

[0022] This invention provides a hypervisor-based virtualized universal touchscreen control method for intelligent cockpit controllers. The controller hardware platform is equipped with a QNX Hypervisor, on which at least one QNX host system and a Guest OS run. The Guest OS can be Android, Linux, or QNX, among other systems. The system architecture of this invention is as follows: Figure 1 As shown, the system functional architecture of the prior art is as follows: Figure 2 As shown, by Figure 2 It can be seen that the Guest OS cannot respond to touch events on a touchscreen controlled by the Host OS (QNX), and the Host OS also cannot respond to touch events on a touchscreen controlled by the Guest OS. Therefore, the only way to control the touchscreen is to add a touchscreen to the hardware architecture. Figure 1 It can be seen that the Guest OS and Host OS can use the same touchscreen and respond to corresponding touch events.

[0023] This embodiment of the intelligent cockpit controller includes a hardware layer, a virtualization layer, and a virtual machine layer. The hardware layer includes a processor, memory, and a physical touchscreen. The virtualization layer uses the QNX Hypervisor to abstract and partition hardware resources. The virtual machine layer includes at least one privileged virtual machine running the QNX operating system and at least one guest virtual machine running the Guset OS. The privileged virtual machine running the QNX operating system integrates a touch control function module, which is used to collect touch events and distribute the collected touch events to the corresponding target operating system.

[0024] The touch control function module includes: The touchscreen driver module is used to acquire the raw input from the physical touchscreen. The touch event standardization module is used to convert raw input into standardized events; The touch event dispatcher module has a built-in dispatch rule configuration unit and a routing logic execution unit, which are used to make dispatch decisions based on the coordinate range; The coordinate mapping module is used to remap the received coordinates for use by the HMI program; The QNX local event injection interface is used to distribute events to this system. The Guest OS virtual machine event forwarding interface is used to forward events to the Guest OS system via the Hypervisor.

[0025] The working principle adopted in this embodiment is: touch event acquisition. In the QNX host system, the raw input data from the physical touch hardware is received and parsed through the standard touch screen driver to generate standardized touch events containing information such as absolute coordinates (X, Y), touch state (such as press, move, release), and timestamp.

[0026] The event is passed to the dispatcher. The standardized touch event is passed to a touch event dispatcher running on the QNX host system. This dispatcher, as the core control module of the system, maintains the global touch distribution strategy.

[0027] Coordinate range determination and routing decision. The touch event dispatcher reads the coordinate information of touch events and compares it with preset dispatch configuration rules. These rules define the coordinate range of one or more areas on the screen and their corresponding target operating systems.

[0028] For example, the rules can be configured as follows: touch events on the left side of the screen (coordinate range [0, 0] to [959, 1080]) are assigned to the QNX system (responsible for instrument display); touch events on the right side of the screen (coordinate range [960, 0] to [1920, 1080]) are assigned to the Android system (responsible for infotainment). The screen is divided into two main areas by a clear vertical dotted line (e.g., at X=960), with each area's coordinate range and corresponding operating system clearly marked. This division method can be flexibly adjusted by modifying the distributor's configuration file according to the actual vehicle model and screen layout. See the screen area diagram. Figure 3 As shown.

[0029] The screen resolution and coordinate area division in this invention are not limited to the division in the example, and can be configured according to the specific display requirements.

[0030] Event distribution. Based on the decision result of the coordinate range, the touch event distributor distributes touch events to the target system through different channels: If the target system is the QNX host system itself, the dispatcher directly injects the event into the local input event processing queue, maps the received coordinates, and then the QNX system's window manager and application process it.

[0031] If the target system is an Android client system, the dispatcher first maps the received touch coordinates into single-screen coordinates, and then encapsulates the standardized touch events into a format recognizable by the Android system through the virtualization interrupt and virtual data transmission channel provided by the QNX Hypervisor (e.g., simulating a virtual virtio-input8), and sends them to the Android virtual machine.

[0032] Target system processing. After receiving a touch event, the QNX or Android system performs subsequent processing through its own input subsystem, window manager, and application framework to ultimately complete the user interaction.

[0033] The distribution and execution process of touch events is as follows: Figure 4 As shown, the steps of the touch event dispatch method are as follows: 1. Start: The process begins.

[0034] 2. Touch event acquisition: The physical touch screen driver detects user touch and acquires raw coordinate data.

[0035] 3. Event Standardization: Convert raw data into standardized touch events that include absolute coordinates (X, Y), touch state (press / move / release), and timestamps.

[0036] 4. Deliver to Distributor: Send the standardized event to the touch event distributor running on the QNX host system.

[0037] 5. Coordinate range determination: The dispatcher reads the event coordinates and compares them with the preset dispatch rules (such as coordinate range).

[0038] If the coordinates belong to the QNX region, then proceed to the QNX system processing branch; the steps are as follows: a) Enter coordinate mapping and convert absolute coordinates to relative coordinates. The conversion method is: subtract the starting coordinate of the QNX region from the absolute coordinate value; b) Coordinate data and touch status are injected into the QNX event queue, and the events are processed by QNX's own input system and application. c) The QNX system processing flow ends.

[0039] If the coordinates belong to the Android region, then enter the QNX Hypervisor virtual machine. The steps are as follows: a) Coordinate mapping: Convert absolute coordinates to relative coordinates. The conversion method is to subtract the starting coordinates of the Android region from the absolute coordinate value. b) Coordinate data and touch status enter the Hypervisor virtual data transmission channel (such as virtio-input8) and send the event to the virtual Android system; c) The touchscreen driver of the virtualized Android system receives data and then transmits the data and events to the Android application framework to complete the interactive response; d) The virtualization Android system processing flow ends.

[0040] Specifically, after the system starts, the QNX Hypervisor runs first and creates two virtual machines: VM0 (privileged virtual machine, running QNX 7.1 system) and VM1 (guest virtual machine, running Android 10 system).

[0041] In the QNX system, deploy and run the touch event dispatcher of this invention. The configuration file loaded by the dispatcher is defined as follows: zone_android = { x_start: 960, y_start: 0, x_end: 1920, y_end: 1080} zone_qnx = { x_start: 0, y_start: 0, x_end: 959, y_end: 1080} When the user touches the screen at coordinates (1200, 500): When the physical touch driver generates an interrupt, the driver in the QNX system reads the coordinate data and generates a normalized event {type: TOUCH_DOWN, x: 1200, y: 500, ...}. This event is then sent to the touch event dispatcher.

[0042] The dispatcher determines that the coordinates (1200, 500) fall within the area defined by zone_android.

[0043] The dispatcher calls coordinate mapping to map the touch coordinates (1200, 500) to (240, 500). The calculation method is as follows: X coordinate 1200-960 = 240; Y coordinate 500-0 = 500. The mapped data and touch state enter the virtio-input8 virtual data transmission channel of the QNX Hypervisor virtual machine, and the touch coordinates and touch state are encapsulated in the touch screen. When the Android virtual machine receives a virtual device interrupt, it reads the event data, which is then processed by its internal Input subsystem and finally dispatched to the foreground navigation application to complete a touch operation.

[0044] In this embodiment, the deployment location, coordinate determination rules, communication mechanism, and operating system of the distributor are not singular but can be varied according to specific circumstances. For example: 1. Replacement of distributor deployment location: Original solution: The distributor runs as a service or driver on the QNX host system (privileged virtual machine).

[0045] Alternative solution: Integrate the dispatcher into the QNX Hypervisor. As a service provided by the Hypervisor itself, it directly intercepts and handles physical interruptions, achieving higher efficiency and stronger isolation.

[0046] 2. Replacement of coordinate determination rules: Original solution: Simple rectangular area division (such as left half screen, right half screen).

[0047] Alternative Solution 1: Non-rectangular complex regions. Rules can be defined as regions such as circles or polygons.

[0048] Alternative Solution Two: Dynamically Variable and Configurable Regions. Distribution rules are not statically configured but can be dynamically changed based on system status. For example: When the Android system launches a full-screen application, the rule is temporarily adjusted to "all full-screen touch events are distributed to Android".

[0049] When the vehicle is reversing, the touch control of a specific area is automatically handed over to the QNX system to display the reversing image interface.

[0050] 3. Replacement of cross-virtual machine communication mechanisms: Original solution: Pass events to the Android virtual machine through the Hypervisor's virtual data transmission channel, such as virtio-input8.

[0051] Alternative Solution 1: Use shared memory and virtual interrupts. QNX writes events to a memory region shared by both VMs, and then notifies the Android system to read them via virtual interrupts.

[0052] Alternative Option 2: Use the dedicated messaging mechanism or IPC (Inter-Process Communication) channel provided by the Hypervisor (such as the channel of QNX Hypervisor).

[0053] 4. Supported operating system replacement: Original solution: QNX (host) and Android (client).

[0054] Alternative: This method is also applicable to any other heterogeneous operating system combination that requires a shared touchscreen. For example: QNX + Linux (for digital dashboards and infotainment systems), QNX + AGL (Automotive GradeLinux), Hypervisor + multiple OSes of the same type.

[0055] The above embodiments are merely exemplary embodiments of the present invention and are not intended to limit the present invention. Those skilled in the art can make various modifications or equivalent substitutions to the present invention within its scope and spirit, and such modifications or equivalent substitutions should also be considered to fall within the scope of protection of the present invention.

Claims

1. A virtualized universal touchscreen control method for an intelligent cockpit controller, characterized in that, Includes the following steps: Step 1, Touch Event Acquisition: In the QNX host system, raw input data from the physical touch hardware is received and parsed through the standard touch screen driver to generate standardized touch events containing coordinate information; Step 2, Event delivery to the dispatcher: The standardized touch events obtained in Step 1 are delivered to a touch event dispatcher running on a QNX host system; Step 3, Coordinate Range Judgment and Routing Decision: The touch event dispatcher reads the coordinate information of the touch event and compares it with the preset dispatch configuration rules; In step 3, the distribution configuration rules define the coordinate range of one or more areas on the screen and their corresponding target operating systems. The target operating systems include at least one QNX host system and at least one Guest OS system.

2. The virtualized universal touchscreen control method for an intelligent cockpit controller according to claim 1, characterized in that, The standardized touch event generated in step 1 includes absolute coordinates, touch state, and timestamp.

3. The virtualized universal touchscreen control method for an intelligent cockpit controller according to claim 1, characterized in that, The Guest OS system is one or more of the following: Android, Linux, and QNX.

4. The virtualized universal touchscreen control method for an intelligent cockpit controller according to claim 2, characterized in that, Step 3 specifically involves: determining the target operating system corresponding to the triggering event based on the coordinate information; if the coordinates belong to the QNX region, then entering the QNX system branch, entering coordinate mapping, converting absolute coordinates to relative coordinates, and injecting the coordinate data and touch state into the QNX event queue; the event is processed by QNX's own input system and application. If the coordinates belong to the Guest OS system, they enter the QNX Hypervisor virtual machine. Through coordinate mapping, the absolute coordinates are converted into relative coordinates. The coordinate data and touch state enter the Hypervisor virtual data transmission channel to send events to the virtual Guest OS system. The touch screen driver of the virtual Guest OS system receives the data and then transmits the data and events to the Guest OS system application framework to complete the interactive response.

5. The virtualized universal touchscreen control method for an intelligent cockpit controller according to claim 4, characterized in that, The specific method for converting absolute coordinates to relative coordinates is to subtract the starting coordinates of the corresponding target system region from the absolute coordinate value.

6. An intelligent cockpit controller, characterized in that, A method for implementing a virtualized universal touchscreen control method for an intelligent cockpit controller as described in any one of claims 1-5 includes a hardware layer, a virtualization layer, and a virtual machine layer, wherein the hardware layer includes a processor, memory, and a physical touchscreen; The virtualization layer uses QNX Hypervisor to abstract and partition hardware resources; The virtual machine layer includes at least one privileged virtual machine running the QNX operating system and at least one guest virtual machine running the Guset OS; The privileged virtual machine running the QNX operating system integrates a touch control function module, which is used to collect touch events and distribute the collected touch events to the corresponding target operating system.

7. The intelligent cockpit controller according to claim 6, characterized in that, The touch control function module includes: The touchscreen driver module is used to acquire the raw input from the physical touchscreen. The touch event standardization module is used to convert raw input into standardized events; The touch event dispatcher module has a built-in dispatch rule configuration unit and a routing logic execution unit, which are used to make dispatch decisions based on the coordinate range; The coordinate mapping module is used to remap the received coordinates for use by the HMI program; The QNX local event injection interface is used to distribute events to this system. The Guest OS virtual machine event forwarding interface is used to forward events to the Guest OS system via the Hypervisor.

Images