Data transmission method based on multiple operating systems of vehicle machine and computer equipment

Abstract

The application relates to a data transmission method based on a vehicle machine multi-operation system and a computer device. The main technical scheme comprises the following steps: a first system receives a touch event input by a user on an input device; the first system determines an operation object and path information corresponding to the touch event; when the operation object is an application program of a second system, the touch event is written into a device node file of the first system according to the path information; and the touch event is transmitted to a device node file of the second system through a preset interface protocol of a virtual machine monitor according to the device node file. The application can shorten the data transmission path, accelerate the data transmission speed, reduce the data copy times, quickly respond to the touch event, make the touch operation more smooth, and improve the user experience.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a data transmission method and computer device based on a vehicle-mounted multi-operating system. Background Technology

[0002] Currently, vehicle-mounted infotainment systems primarily employ a dual-system architecture, consisting of Linux and Android. These two systems run simultaneously on a hypervisor and transmit data via inter-process communication (IPC). This dual-system approach involves multiple data transfer modules and numerous data copying operations. When a user continuously taps the touchscreen, it triggers a large amount of data transmission. The dual-system cannot quickly complete this data transfer, leading to touchscreen lag and negatively impacting the user experience. Summary of the Invention

[0003] Based on this, this application provides a data transmission method and computer device based on multiple operating systems in a vehicle to solve the problem of touch screen lag caused by the inability of dual systems to quickly complete data transmission in a short period of time.

[0004] Firstly, a data transmission method based on a multi-operating system in a vehicle is provided. The multi-operating system includes a first system and a second system, which communicate with each other via a virtual machine monitor. The method includes:

[0005] The first system receives touch events input by the user on the input device;

[0006] The first system determines the operation object and path information corresponding to the touch event;

[0007] When the target of the operation is an application of the second system, the touch event is written to the device node file of the first system according to the path information;

[0008] Based on the device node file of the first system, touch events are transmitted to the device node file of the second system through the preset interface protocol of the virtual machine monitor.

[0009] According to one achievable method in an embodiment of this application, a first system is provided with a backend driver module and a first protocol interface, and a second system is provided with a frontend driver module and a second protocol interface; based on the device node file of the first system, touch events are transmitted to the device node file of the second system through a preset interface protocol of the virtual machine monitor, including:

[0010] The backend driver module obtains touch events from the device node file of the first system;

[0011] The preset interface protocol based on the virtual machine monitor transmits touch events to the front-end driver module through the first protocol interface and the second protocol interface.

[0012] The front-end driver module writes touch events into the device node file of the second system.

[0013] According to one achievable method in an embodiment of this application, a gesture service module is provided in the first system, and the path information includes device matching information; when the operation object is an application of the second system, the touch event is written to the device node file of the first system according to the path information, including:

[0014] When the target of the operation is an application of the second system, the gesture service module writes the touch event into the device node file of the first system according to the device matching information.

[0015] According to one achievable method in an embodiment of this application, the first system further includes a human-machine interface module and a transmission module; the first system determines the operation object corresponding to the touch event, including:

[0016] The human-machine interface module receives a unique identifier sent by the transmission module. The unique identifier is an identifier generated by the service being used to identify the service type.

[0017] The object to be operated on is determined by the unique identifier.

[0018] According to one achievable method in an embodiment of this application, the first system determines the path information corresponding to the touch event, including:

[0019] The human-machine interface module obtains the first device information from the touch event;

[0020] Based on the pre-stored device information and the first device information, determine the path information corresponding to the touch event.

[0021] According to one achievable method in an embodiment of this application, the method further includes:

[0022] When a new input device is connected to the first system, the human-machine interface module obtains the second device information of the new input device and saves the second device information;

[0023] The second device information is written into the newly added device node file via the gesture service module;

[0024] The new device node files are synchronized to the second system so that the device node files in the first system and the second system can be mapped to each other.

[0025] According to one possible implementation method in the embodiments of this application, the backend driver module set in the first system and the frontend driver module set in the second system realize data transmission by running on the virtual machine monitor layer.

[0026] According to one achievable method in an embodiment of this application, the method further includes:

[0027] When a touch event is detected in the device node file of the second system, the second system transmits the touch event to the application of the second system so that the application of the second system can respond to the touch event.

[0028] According to one achievable method in an embodiment of this application, the method further includes:

[0029] When the target of the operation is an application of the first system, the touch event is transmitted to the application of the first system so that the application of the first system can respond to the touch event.

[0030] Secondly, a data transmission device based on a vehicle infotainment system with multiple operating systems is provided, the device comprising:

[0031] A receiving module is used by the first system to receive touch events input by the user on the input device;

[0032] The determination module is used by the first system to determine the operation object and path information corresponding to the touch event;

[0033] The writing module is used to write the touch event into the device node file of the first system according to the path information when the operation object is an application of the second system;

[0034] The transmission module is used to transmit the data corresponding to the touch event to the device node file of the second system through a preset interface protocol of the virtual machine monitor, according to the device node file.

[0035] Thirdly, a computer device is provided, comprising:

[0036] At least one processor; and

[0037] A memory communicatively connected to the at least one processor; wherein,

[0038] The memory stores computer instructions that can be executed by the at least one processor to enable the at least one processor to perform the method involved in the first aspect above.

[0039] Fourthly, a computer-readable storage medium is provided, having stored thereon computer instructions, wherein the computer instructions are used to cause a computer to perform the methods involved in the first aspect above.

[0040] According to the technical content provided in the embodiments of this application, the first system receives touch events input by the user on the input device. The first system determines the operation object and path information corresponding to the touch event. When the operation object is an application of the second system, the touch event is written into the device node file of the first system according to the path information. According to the device node file, the touch event is transmitted to the device node file of the second system through the preset interface protocol of the virtual machine monitor. This can shorten the data transmission path, speed up the data transmission, reduce the number of data copies, and quickly respond to touch events, making the touch operation smoother and improving the user experience. Attached Figure Description

[0041] Figure 1 This is a schematic diagram of the structure of a vehicle infotainment system with multiple operating systems in one embodiment;

[0042] Figure 2 This is a flowchart illustrating a data transmission method based on multiple operating systems in a vehicle infotainment system in one embodiment.

[0043] Figure 3 This is a schematic diagram of the structure of the first system and the second system in one embodiment of this application;

[0044] Figure 4 This is a structural block diagram of a data transmission device based on a vehicle-mounted multi-operating system in one embodiment;

[0045] Figure 5 This is a schematic structural diagram of a computer device in one embodiment. Detailed Implementation

[0046] The present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the scope of the present application.

[0047] This application provides a data transmission method and computer device based on a multi-operating system in a vehicle. The data transmission method based on a multi-operating system in a vehicle provided by this application will be described first.

[0048] The touch control method based on multiple operating systems in in-vehicle systems provided in this application embodiment is applied to, for example... Figure 1The illustrated in-vehicle infotainment system features a multi-operating system comprising a first system 110, a second system 120, a virtual machine monitor 130, a processor 140, and a display system 150. The first system 110 interacts with the user through the display system 150, and the second system 120 communicates with the processor 140 via the virtual machine monitor 130. Under the coordination of the virtual machine monitor 130, the multiple operating systems can share virtualized hardware resources while maintaining their independence. The first and second systems can be either Android or Linux, respectively. The display system 150 can be a touch-screen LCD or a regular display with external buttons or a touchpad; no specific limitation is made here. In addition to connecting to the display system 150, the first system 110 can also connect to external USB devices, Bluetooth devices, or game controllers to assist the user in operating the first system 110.

[0049] Figure 2 This illustration shows a flowchart of a data transmission method based on a multi-operating system in a vehicle, according to an embodiment of this application. Figure 2 As shown, the method may include the following steps:

[0050] S210, the first system receives touch events input by the user on the input device.

[0051] Input devices can be the touchscreen of the display system 150, or USE devices or Bluetooth devices, such as a mouse.

[0052] Users can click on the location of the application that meets their needs on the input device. The display system 150 generates a touch event based on the user's input and sends it to the first system, triggering the first system to process the touch event.

[0053] S220, the first system determines the operation object and path information corresponding to the touch event.

[0054] After receiving a touch event, the first system determines the target of the touch event to identify the system that will respond to it. The target includes applications from both the first and second systems, ensuring that no single system can fail to respond to the touch event.

[0055] The path information includes device matching information, which includes the device nodes that transmit touch events. Each device node corresponds to a device node file. Each input device connected to the first system corresponds to a device node. When the first system is connected to one input device, the device node corresponding to that input device is directly determined as the path information. When the first system is connected to multiple input devices, the input device that generates the touch event must first be determined, and then the device node corresponding to that input device must be determined as the path information.

[0056] S230: When the target of the operation is an application of the second system, the touch event is written to the device node file of the first system according to the path information.

[0057] When the target of the operation is an application on the second system, the touch events need to be transmitted from the first system to the second system. Based on the device matching information contained in the path information, the touch events are written into the device node file of the first system.

[0058] S240, based on the device node file of the first system, transmits touch events to the device node file of the second system through the preset interface protocol of the virtual machine monitor.

[0059] The default interface protocol is the Virtio protocol. The Virtio protocol is a set of general-purpose I / O device virtualization programs. It is an abstraction of a set of general-purpose I / O devices in the virtual machine monitor, providing a communication framework and programming interface between upper-layer applications and various virtualization devices, reducing compatibility issues caused by cross-platform compatibility.

[0060] The Virtio protocol allows mapping of data between the device node files of the first system and the device node files of the second system. This means that the device node files of the first system can be directly used by the second system, reducing the need for intermediate modules, thereby reducing the number of data copies and enabling faster response to touch events.

[0061] As can be seen, in this embodiment, the first system receives touch events input by the user on the input device. The first system determines the operation object and path information corresponding to the touch event. When the operation object is an application of the second system, the touch event is written into the device node file of the first system according to the path information. According to the device node file, the touch event is transmitted to the device node file of the second system through the preset interface protocol of the virtual machine monitor. This can shorten the data transmission path, speed up the data transmission, reduce the number of data copies, and quickly respond to touch events, making the touch operation smoother and improving the user experience.

[0062] Before describing each step, the specific structures of the first system 110 and the second system 120 will be described first. For example... Figure 3As shown, the first system 110 includes a human-machine interface module 111, a gesture service module 112, a backend driver module 113, a first protocol interface 114, and a transmission module 115. The second system 120 includes a frontend driver module 121 and a second protocol interface 122.

[0063] The human-machine interface module 111 is used to determine the target of the touch event and the path information for transmitting the touch event. The gesture service module 112 is used to write the touch events transmitted from the human-machine interface module 111 into the device node file. The back-end driver module 113 is used to read the touch events from the device node file and transmit the touch events to the front-end driver module 121 through the first protocol interface 114 and the second protocol interface 122. The front-end driver module 121 then writes the touch events into the device node file of the second system. The transmission module 115 is used to transmit a unique identifier generated by the system when a certain service is used, which indicates what kind of service it is.

[0064] The steps in the above method flow are described in detail below. The following is a detailed description of step S220, namely, "the first system determines the operation object and path information corresponding to the touch event," in conjunction with an embodiment.

[0065] As one possible approach, the human-machine interface module receives a unique identifier sent by the transmission module. This unique identifier is an identifier generated by the service being used to identify the service type.

[0066] The object to be operated on is determined by the unique identifier.

[0067] Simultaneously with the HMI module receiving a touch event, the transmission module also sends the previously received unique identifier to the HMI module. The HMI module identifies the type of touch event based on the unique identifier and further determines the corresponding operation object. There are two possible outcomes: either the operation object belongs to an application in the first system, in which case the touch event is sent to the upper-layer application of the first system; or the operation object belongs to an application in the second system, in which case the touch event is sent to the upper-layer application of the second system. The first system, through the HMI module, centrally manages touch events and rationally allocates the corresponding operation objects, thereby improving the system's response speed to user requests.

[0068] As one possible approach, the human-machine interface module acquires the first device information from the touch event;

[0069] Based on the pre-stored device information and the first device information, determine the path information corresponding to the touch event.

[0070] The touch event includes first device information, which is the device information of the input device that has been connected to the system, including the device identifier of the input device that assists the user operating system interface in generating touch events.

[0071] When an input device connects to the first system, the first system acquires the device information of the input device and saves it as pre-stored device information. When the human-machine interface module acquires the device information in a touch event, it compares it with the pre-stored device information. If a matching pre-stored device information exists, the device node corresponding to that pre-stored device information is determined as the transmission path for the touch event. Determining the correct transmission path for the touch event enables fast and accurate data transmission.

[0072] As one possible approach, when a new input device is connected to the first system, the human-machine interface module obtains the second device information of the new input device and saves the second device information;

[0073] The second device information is written into the newly added device node file via the gesture service module;

[0074] The new device node files are synchronized to the second system so that the device node files in the first system and the second system can be mapped to each other.

[0075] A new input device is connected to the first system; that is, an input device is already connected to the first system. The newly connected input device can be temporarily not used or can be used immediately. The second device information is the device information of the newly connected input device.

[0076] When a new input device is connected to the first system, the human-machine interface module obtains and saves the second device information of the new input device, updating the pre-stored device information. At this time, the first system generates a device node file corresponding to the new input device. The gesture service module writes the second device information into the newly added device node file and creates an identical device node file in the second system, ensuring that the device node files in the first and second systems are synchronized and mutually mapped. When a touch event requires an application response in the second system, the synchronization of the device node files in the first and second systems facilitates the selection of transmission paths, enabling rapid transmission of touch events and improving the performance of touch event transmission.

[0077] The following describes in detail step S230, namely, "when the operation object is an application of the second system, the touch event is written into the device node file of the first system according to the path information," with reference to the embodiments.

[0078] As one possible approach, when the target of the operation is an application in the second system, the gesture service module writes the touch event into the device node file of the first system based on the device matching information.

[0079] Device matching information includes device nodes. The gesture service module determines the device node for transmitting touch events based on the device matching information and writes the touch events into the device node file corresponding to that device node. Since the first system can connect to multiple input devices, and each device node file has multiple corresponding files, transmitting touch events through the gesture service module based on the device matching information can avoid confusion during the transmission of touch events and improve the accuracy of touch event transmission.

[0080] The following describes in detail step S240, namely, "transmitting touch events to the device node file of the second system through a preset interface protocol of the virtual machine monitor according to the device node file of the first system", with reference to the embodiments.

[0081] As one possible approach, the backend driver module obtains touch events from the device node file of the first system;

[0082] Based on the virtual machine monitor's preset interface protocol, touch events are transmitted to the front-end driver module through the first protocol interface and the second protocol interface.

[0083] The front-end driver module writes touch events into the device node file of the second system.

[0084] Under the virtio protocol, corresponding modules need to be configured in different systems to coordinate data transmission. Therefore, a backend driver module is configured in the first system to read touch events from the device node file of the first system. A first protocol interface is configured in the first system, and a second protocol interface is configured in the second system to enable data transmission based on the virtual machine monitor under the virtio protocol. Both the first and second protocol interfaces are virito modules using the MMIO bus protocol. A frontend driver module is configured in the second system to write the received touch events to the corresponding device node file. The backend and frontend driver modules run at the virtual machine monitor layer and transmit data via shared memory using the virtio protocol. This allows for direct data transmission between the backend and frontend driver modules, reducing intermediate modules, minimizing data copying, and improving data transmission efficiency.

[0085] As one possible approach, when a touch event is detected in the device node file of the second system, the second system transmits the touch event to the application of the second system for the application to respond to the touch event.

[0086] When a touch event is detected in the device node file of the second system, the second system can detect it promptly. Upon detection, the touch event is transmitted to the application of the second system, which can process the transmitted data quickly and respond rapidly to the touch event.

[0087] As one possible approach, when the object of the operation is an application of the first system, the touch event is transmitted to the application of the first system so that the application of the first system can respond to the touch event.

[0088] When the target of the operation is an application of the first system, the first system directly responds to the touch event. When the target of the operation is an application of the second system, the first system sends the touch event to the second system for response. This combination of the two systems can expand the service scope to meet user needs and improve the user experience.

[0089] It should be understood that, although Figure 1 The steps in the flowchart are shown sequentially as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated in this application, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Furthermore, Figure 1 At least some of the steps in the process may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least some of the sub-steps or stages of other steps.

[0090] Figure 4 This application provides a schematic diagram of a data transmission device based on a multi-operating system in a vehicle, used to perform tasks such as... Figure 1 The method flow is shown below. Figure 4 As shown, the device may include: a receiving module 410, a determining module 420, a writing module 430, and a transmitting module 440, and may further include: a synchronization module. The main functions of each component module are as follows:

[0091] The receiving module 410 is used by the first system to receive touch events input by the user on the input device;

[0092] The determining module 420 is used by the first system to determine the operation object and path information corresponding to the touch event;

[0093] The writing module 430 is used to write the touch event into the device node file of the first system according to the path information when the operation object is an application of the second system.

[0094] The transmission module 440 is used to transmit the data corresponding to the touch event to the device node file of the second system through a preset interface protocol of the virtual machine monitor, according to the device node file.

[0095] As one possible approach, the first system is equipped with a backend driver module and a first protocol interface, and the second system is equipped with a frontend driver module and a second protocol interface; the transmission module 440 is specifically used by the backend driver module to obtain touch events from the device node file of the first system;

[0096] Based on the virtual machine monitor's preset interface protocol, touch events are transmitted to the front-end driver module through the first protocol interface and the second protocol interface.

[0097] The front-end driver module writes touch events into the device node file of the second system.

[0098] As one possible approach, the first system includes a gesture service module, and the path information includes device matching information; the writing module 430 is specifically used to write the touch event into the device node file of the first system according to the device matching information when the operation object is an application of the second system.

[0099] As one possible approach, the first system also includes a human-machine interface module and a transmission module; the determination module 420 is specifically used for the human-machine interface module to receive a unique identifier sent by the transmission module, the unique identifier being an identifier generated by the service being used to identify the service type;

[0100] The object to be operated on is determined by the unique identifier.

[0101] As one possible approach, module 420 is specifically used by the human-machine interface module to obtain the first device information in the touch event;

[0102] Based on the pre-stored device information and the first device information, determine the path information corresponding to the touch event.

[0103] As one possible approach, the device also includes a synchronization module, which, when a new input device is connected to the first system, enables the human-machine interface module to acquire and save the second device information of the new input device.

[0104] The second device information is written into the newly added device node file via the gesture service module;

[0105] The new device node files are synchronized to the second system so that the device node files in the first system and the second system can be mapped to each other.

[0106] As one possible implementation, the transmission module 440 is also used to transmit the touch event to the application of the second system when a touch event is detected in the device node file of the second system, so that the application of the second system can respond to the touch event.

[0107] As one possible implementation, the transmission module 440 is also used to transmit touch events to the application of the first system when the object of operation is an application of the first system, so that the application of the first system can respond to the touch events.

[0108] The same or similar parts among the above embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the device embodiments are basically similar to the method embodiments, so the description is relatively simple, and the relevant parts can be referred to the description of the method embodiments.

[0109] It should be noted that the embodiments of this application may involve the use of user data. In practical applications, user-specific personal data may be used in the scheme described herein within the scope permitted by applicable laws and regulations, provided that it complies with the applicable laws and regulations of the country (e.g., explicit consent from the user, actual notification to the user, explicit authorization from the user, etc.).

[0110] According to embodiments of this application, this application also provides a computer device and a computer-readable storage medium.

[0111] like Figure 5 The diagram shown is a block diagram of a computer device according to an embodiment of this application. The term "computer device" is intended to represent various forms of digital computers or mobile devices. The digital computer may include a desktop computer, a portable computer, a workbench, a personal digital assistant, a server, a mainframe computer, and other suitable computers. The mobile device may include a tablet computer, a smartphone, a wearable device, etc.

[0112] like Figure 5 As shown, device 500 includes a computing unit 501, a ROM 502, a RAM 503, a bus 504, and an input / output (I / O) interface 505. The computing unit 501, ROM 502, and RAM 503 are interconnected via the bus 504. The input / output (I / O) interface 505 is also connected to the bus 504.

[0113] The computing unit 501 can execute various processes in the method embodiments of this application according to computer instructions stored in the read-only memory (ROM) 502 or computer instructions loaded from the storage unit 508 into the random access memory (RAM) 503. The computing unit 501 can be various general-purpose and / or special-purpose processing components with processing and computing capabilities. The computing unit 501 can include, but is not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. In some embodiments, the methods provided in the embodiments of this application can be implemented as computer software programs, which are tangibly contained in a computer-readable storage medium, such as the storage unit 508.

[0114] RAM 503 can also store various programs and data required for the operation of device 500. Part or all of the computer program can be loaded and / or installed on device 500 via ROM 802 and / or communication unit 509.

[0115] The input unit 506, output unit 507, storage unit 508, and communication unit 509 in device 500 can be connected to I / O interface 505. The input unit 506 can be, for example, a keyboard, mouse, touchscreen, or microphone; the output unit 507 can be, for example, a display, speaker, or indicator light. Device 500 can exchange information and data with other devices through the communication unit 509.

[0116] It should be noted that the device may also include other components necessary for normal operation. It may also include only the components necessary for implementing the solution of this application, without necessarily including all the components shown in the figures.

[0117] Various implementations of the systems and techniques described herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SOCs), payload programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof.

[0118] The computer instructions used to implement the methods of this application may be written in any combination of one or more programming languages. These computer instructions may be provided to the computing unit 501 such that when executed by the computing unit 501, such as a processor, the computer instructions cause the execution of the steps involved in the embodiments of the methods of this application.

[0119] The computer-readable storage medium provided in this application can be a tangible medium that can contain or store computer instructions for performing the steps involved in the method embodiments of this application. The computer-readable storage medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, and other forms of storage media.

[0120] The specific embodiments described above do not constitute a limitation on the scope of protection of this application. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A data transmission method based on a multi-operating system in a vehicle, characterized in that, The multi-operating system includes a first system and a second system, wherein the first system and the second system communicate with each other through a virtual machine monitor; the method includes: The first system receives touch events input by a user on multiple input devices. The touch events include first device information, which includes the device identifier of the input device that generated the touch event. The first system determines the operation object corresponding to the touch event, and when there is pre-stored device information that is the same as the first device information, it uses the device node that transmits the touch event corresponding to the pre-stored device information as the path information of the touch event. The pre-stored device information is the device information of the input device that has been connected to the first system. Each device node corresponds to an input device connected to the first system, and each device node corresponds to a device node file of the first system. When the operation target is an application of the second system, the touch event is written to the device node file of the first system corresponding to the device node; Based on the device node file of the first system, the touch event is transmitted to the device node file of the second system through a preset interface protocol of the virtual machine monitor.

2. The method according to claim 1, characterized in that, The first system is equipped with a backend driver module and a first protocol interface, and the second system is equipped with a frontend driver module and a second protocol interface; the step of transmitting the touch event to the device node file of the second system through a preset interface protocol of the virtual machine monitor according to the device node file of the first system includes: The backend driver module obtains the touch event from the device node file of the first system; The preset interface protocol based on the virtual machine monitor transmits the touch event to the front-end driver module through the first protocol interface and the second protocol interface; The front-end driver module writes the touch event into the device node file of the second system.

3. The method according to claim 1, characterized in that, The first system also includes a human-machine interface module and a transmission module; the first system determines the operation object corresponding to the touch event, including: The human-machine interface module receives a unique identifier sent by the transmission module. The unique identifier is an identifier generated by the service being used to identify the service type. The operation object corresponding to the touch event is determined based on the unique identifier.

4. The method according to claim 3, characterized in that, The first system includes a gesture service module, and the method further includes: When a new input device is connected to the first system, the human-machine interface module obtains the second device information of the new input device and saves the second device information; The gesture service module writes the second device information into the newly added device node file. The newly added device node files are synchronized to the second system so that the device node files in the first system and the second system are mapped to each other.

5. The method according to any one of claims 1 to 4, characterized in that, The backend driver module in the first system and the frontend driver module in the second system achieve data transmission by running on the virtual machine monitor layer.

6. The method according to claim 1, characterized in that, The method further includes: When the touch event is detected in the device node file of the second system, the second system transmits the touch event to the application of the second system so that the application of the second system can respond to the touch event.

7. The method according to claim 1, characterized in that, The method further includes: When the target of the operation is an application of the first system, the touch event is transmitted to the application of the first system so that the application of the first system can respond to the touch event.

8. A computer device, comprising: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores computer instructions executable by the at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform the method of any one of claims 1-7.

Images