Cross-domain touch data transmission method and device, electronic equipment and storage medium

Through the cross-domain transmission method on the smart cockpit chip, using shared memory and notification message mechanism, the touch data of the central control display screen is transmitted to the panoramic monitor processor, which solves the data transmission problem between the AP domain and the CP domain, and realizes the user Effective issuance of touch commands and interface response.

CN118939456APending Publication Date: 2024-11-12ECARX (HUBEI) TECHCO LTD

Patent Information

Application Number
CN202411425944.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-10-14
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

The prior art cannot realize the transmission of the central control display touch data received by the AP domain in the smart cockpit chip to the AVM service layer of the CP domain, resulting in the inability of user touch instructions to the AVM processing program.

Method used

By implementing a cross-domain touch data transmission method on the smart cockpit chip, using shared memory to cache the touch data of the central control display screen and send a notification message, ensuring that the touch data is transmitted from the first system domain to the second system when the preset conditions are met. and then processed by the Panoramic Monitor handler.

Benefits of technology

It realizes the issuance of user touch instructions, improves the response speed and user experience of AVM interface, and meets the business needs of real-time and computing power.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118939456A_ABST
    Figure CN118939456A_ABST
Patent Text Reader

Abstract

The invention discloses a cross-domain touch data transmission method and device, electronic equipment and a storage medium, the method is applied to an intelligent cabin chip running multiple system domains, and the method comprises the steps that a first system domain caches touch data of a target area based on a central control display screen to a shared memory; the first system domain sends a notification message to the second system domain; the second system domain obtains the touch data from the shared memory in response to the notification message; and reporting the touch data to a panoramic monitor processing program for processing. Therefore, under the condition that the central control display screen and the panoramic monitor processing program are controlled by different system domains of the intelligent cabin chip, after the first system domain obtains the touch data, the touch data are transmitted to the second system domain through the shared memory, and then the touch data are transmitted to the panoramic monitor processing program through the shared memory. And the second system domain reports the touch data to a panoramic monitor processing program for analysis processing, so that the issuing of a user touch instruction is realized.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of vehicles, and in particular to a cross-domain touch data transmission method, device, electronic device and storage medium. Background Art

[0002] The smart cockpit chip contains two independent CPU (Central Processing Unit) units, namely the AP (Adaptive Platform) domain and the CP (Classic Platform) domain. The AP domain is used to run the Android OS (Operating System) and is suitable for businesses with high computing power requirements. The CP domain is used to run the Linux OS and is suitable for businesses with high real-time requirements.

[0003] Therefore, according to different business needs, the business on the smart cockpit chip can be assigned to the AP domain or CP domain for operation. Among them, the central control display is usually operated by the AP domain, and the AVM (Around View Monitor) is one of the most important functions of the car computer. Its response time needs to be shortened as much as possible, so it is deployed in the CP domain with higher real-time performance. The CP domain then displays the AVM screen on the central control display in the AP domain.

[0004] However, in some scenarios, after the AVM screen is displayed, the user needs to issue instructions on the AVM interface by touching the central control display screen. However, the existing technology cannot transmit the touch data of the central control display screen received by the AP domain to the AVM business layer of the CP domain, resulting in the user's touch instructions being unable to be issued to the AVM for implementation. Summary of the invention

[0005] The purpose of the embodiments of the present application is to provide a cross-domain touch data transmission method, device, electronic device and storage medium, which can solve the problem that it is currently impossible to transmit the touch data of the central control display screen received by the AP domain to the AVM business layer of the CP domain, resulting in the user's touch instructions being unable to be issued to the AVM for implementation.

[0006] In a first aspect, an embodiment of the present application provides a cross-domain touch data transmission method, which is applied to a smart cockpit chip running multiple system domains, including: The first system domain caches the touch data of the target area based on the central control display screen into the shared memory; the target area is a display area of ​​the panoramic monitor processing program of the second system domain other than the first system domain among the multiple system domains; The first system domain sends a notification message to the second system domain; The second system domain obtains the touch data from the shared memory in response to the notification message; and reports the touch data to the panoramic monitor processing program for processing.

[0007] Optionally, the first system domain sending a notification message to a second system domain other than the first system domain among the multiple system domains includes: In a case where the touch data meets a preset transmission condition, a notification message is sent to a second system domain other than the first system domain among the multiple system domains.

[0008] Optionally, the preset transmission condition includes: The caching time of the touch data exceeds a preset time threshold; and / or, The touch data cached in the shared memory exceeds a preset data amount threshold.

[0009] Optionally, the first system domain caches the touch data of the target area based on the central control display screen into a shared memory, including: Acquire touch data of a target area based on the central control display screen through the central control display screen touch driver of the first system domain, and upload the touch data to the first core driver of the first system domain; The first core driver sends the touch data to the touch screen service driver of the first system domain; The touch screen service driver caches the touch data into a shared memory.

[0010] Optionally, acquiring touch data of a target area based on a central control display screen through a central control display screen touch driver of the first system domain, and uploading the touch data to a first core driver of the first system domain includes: The central control display screen touch driver of the first system domain receives the touch protocol data of the target area uploaded by the central control display screen through the integrated circuit bus; Parsing and encapsulating the touch protocol data to obtain an input event data packet as touch data; The touch data is uploaded to a first core driver of the first system domain.

[0011] Optionally, the first system domain further includes a first communication module, and the first system domain sends a notification message to a second system domain other than the first system domain among the multiple system domains, including: The touch screen service driver of the first system domain notifies the first communication module to send the notification message; The first communication module sends the notification message to a second system domain other than the first system domain among the multiple system domains through a full-duplex message channel based on a remote system domain communication protocol.

[0012] Optionally, after uploading the touch data to the first core driver of the first system domain, the method further includes: The first core driver sends the touch data to a first event processing driver of the first system domain; The first event processing driver forwards the touch data to a user space.

[0013] Optionally, the second system domain obtains the touch data from the shared memory in response to the notification message; and reports the touch data to the panoramic monitor processing program for processing, including: The virtual touch driver of the second system domain obtains the touch data from the shared memory in response to the notification message; and reports the touch data to the second core driver of the second system domain; The second core driver reports the touch data to the panoramic monitor processing program for processing.

[0014] Optionally, the second core driver reports the touch data to the panoramic monitor processing program for processing, including: The second core driver reports the touch data to a second event processing driver in the second system domain; The second event processing driver reports the touch data to an input event parsing driver input into the second system domain; The input event parsing driver parses the touch data by calling a function to obtain parsed data, and reports the parsed data to the panoramic monitor processing program; The panoramic monitor processing program processes the parsed data.

[0015] Optionally, the second system domain further includes a second communication module, and the virtual touch driver of the second system domain obtains the touch data from the shared memory in response to the notification message, including: The second communication module receives the notification message through a full-duplex message channel; and sends a data acquisition notification to the virtual touch driver of the second system domain; The virtual touch driver acquires the touch data from the shared memory in response to the data acquisition notification.

[0016] In a second aspect, an embodiment of the present application provides a touch data transmission device, which is applied to a smart cockpit chip running multiple system domains, including: A first system domain, used to cache touch data of a target area based on a central control display screen to a shared memory; send a notification message to a second system domain other than the first system domain among multiple system domains; the target area is a display area of ​​a panoramic monitor processing program of the second system domain; The second system domain is used to obtain the touch data from the shared memory in response to the notification message; and report the touch data to the panoramic monitor processing program for processing.

[0017] In a third aspect, an embodiment of the present application provides an electronic device, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the second aspect are implemented.

[0018] In a fourth aspect, an embodiment of the present application provides a readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, the steps of the method described in the second aspect are implemented.

[0019] In a fifth aspect, an embodiment of the present application provides a chip, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the second aspect.

[0020] In a sixth aspect, an embodiment of the present application provides a computer program product, which is stored in a storage medium and is executed by at least one processor to implement the method described in the second aspect.

[0021] In the solution provided in the embodiment of the present application, the cross-domain touch data transmission method is applied to a smart cockpit chip running multiple system domains, including: the first system domain caches the touch data of the target area based on the central control display screen to the shared memory; the target area is the display area of ​​the panoramic monitor handler of the second system domain other than the first system domain in the multiple system domains; the first system domain sends a notification message to the second system domain; the second system domain responds to the notification message and obtains the touch data from the shared memory; and the touch data is reported to the panoramic monitor handler for processing.

[0022] In this way, when the central control display screen and the panoramic monitor processor are controlled by different system domains of the smart cockpit chip, after the central control display screen collects the user's touch data on the panoramic monitor processor, it can transmit the touch data to the first system domain. After obtaining the touch data, the first system domain transmits the touch data to the second system domain through shared memory. Then, the second system domain reports the touch data to the panoramic monitor processor, and the panoramic monitor processor parses and processes the touch data, thereby realizing the issuance of user touch commands.

[0023] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1 is a flow chart of a cross-domain touch data transmission method according to an exemplary embodiment; Figure 2 is a schematic diagram of a software architecture of a cross-domain touch data transmission method according to an exemplary embodiment; Figure 3 is a block diagram of a cross-domain touch data transmission device according to an exemplary embodiment; Figure 4 is a block diagram of an electronic device according to an exemplary embodiment; Figure 5 The figure is a schematic diagram showing the hardware structure of an electronic device according to an exemplary embodiment. DETAILED DESCRIPTION

[0025] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments in the present application belong to the scope of protection of this application.

[0026] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0027] The cross-domain touch data transmission method provided by the embodiment of the present application is described in detail below through specific embodiments and application scenarios in conjunction with the accompanying drawings.

[0028] Figure 1 The present invention is a flowchart of a cross-domain touch data transmission method according to an exemplary embodiment. The touch data transmission method is applied to a smart cockpit chip running multiple system domains, and includes the following steps: Step S11: the first system domain caches the touch data of the target area based on the central control display screen into the shared memory; the target area is the display area of ​​the panoramic monitor processing program of the second system domain except the first system domain among the multiple system domains.

[0029] Multiple independent system domains can be run in the smart cockpit chip, and each system domain can be supported by different CPU units. For example, the system domains running in the smart cockpit chip can be AP domains and CP domains. The AP domain is used to run the Android OS, which is suitable for businesses with high computing power requirements. The CP domain is used to run the Linux OS, which is suitable for businesses with high real-time requirements.

[0030] According to different business needs, the business on the smart cockpit chip can be assigned to the AP domain or CP domain for operation. In this application, the first system domain is the AP domain, and the second system domain other than the first system domain in multiple system domains is the CP domain. Therefore, the central control display screen is usually run by the first system domain, and the panoramic monitor (AVM) processor is deployed in the second system domain with higher real-time performance. The second system domain needs to display the AVM screen on the central control display screen controlled by the first system domain.

[0031] In some scenarios, after the AVM screen is displayed on the central control display screen, the user issues instructions on the AVM interface by touching the central control display screen. However, in the related technology, it is impossible to transmit the touch data of the central control display screen received by the first system domain to the AVM business layer of the second system domain, resulting in the user's touch instructions being unable to be issued to the AVM processing program for implementation.

[0032] Based on this, the present application proposes a cross-domain touch data transmission method to solve the problems existing in the related technology, realize the transmission of touch data between the first system domain and the second system domain, and send the user's touch instructions to the AVM processing program.

[0033] Specifically, first, after the user performs a touch operation in the target area of ​​the central control display screen, the central control display screen generates touch data based on the user's touch operation, and then reports the touch data to the first system domain.

[0034] Among them, the target area is the display area of ​​the panoramic monitor processor of the second system domain. The touch data includes the user's operation type and operation location. For example, the user may enter text in the text input area through touch operation in the target area, or click on certain controls, etc. These touch operations will be recognized and collected by the central control display as touch data.

[0035] Then, the first system domain caches the touch data to a shared memory, which is a memory space accessible to both the first system domain and the second system domain. In this way, after the first system domain caches the touch data to the shared memory, it is convenient for the second system domain to obtain the touch data from the shared memory.

[0036] The shared memory may be LPDDR (Low Power Double Data Rate SDRAM) or other devices with data storage function, which is not specifically limited in the present application.

[0037] Step S12: The first system domain sends a notification message to the second system domain.

[0038] In this step, after the first system domain caches the touch data in the shared memory, it may send a notification message to the second system domain, where the notification message is used to prompt the second system domain to obtain the touch data from the shared memory to achieve cross-domain transmission of the touch data.

[0039] In one implementation, the first system domain sends a notification message to the second system domain, including: When the touch data meets the preset transmission condition, a notification message is sent to the second system domain.

[0040] That is to say, before the first system domain notifies the second system domain to obtain touch data from the shared memory, it needs to first determine whether the touch data meets the preset transmission conditions, so as to avoid the second system domain reading touch data from the shared memory when the data transmission of the first system domain has not been completed, resulting in data reading failure.

[0041] In one implementation, the preset transmission condition includes: The touch data cache time exceeds a preset time threshold; and / or, The touch data cached in the shared memory exceeds the preset data volume threshold.

[0042] That is to say, after the first system domain caches the touch data to the shared memory, it can monitor the storage status of the touch data in the shared memory. If the cache time of the touch data in the shared memory exceeds the preset time threshold, or if the touch data cached in the shared memory exceeds the preset data volume threshold, a notification message can be sent to the second system domain to enable the second system domain to obtain the touch data from the shared memory.

[0043] Among them, the preset time threshold and the preset data volume threshold are both set to smaller values. In this way, the touch data transmission rate between the first system domain and the second system domain can be accelerated to avoid the AVM handler responding too slowly. For example, the preset time threshold can be set to 50 milliseconds.

[0044] In one implementation, the first system domain caches the touch data of the target area based on the central control display screen to the shared memory, including: Acquire touch data of a target area based on the central control display screen through the central control display screen touch driver of the first system domain, and upload the touch data to the first core driver of the first system domain; The first core driver sends the touch data to the touch screen service driver of the first system domain; The touch screen service driver caches touch data in shared memory.

[0045] That is to say, the software architecture in the first system domain includes at least the central control display screen touch driver (touchscreendriver), the first core driver and the touch screen service driver (virtual TP service driver). Among them, the first core driver is the core driver (inputcore) of the input subsystem of the Linux kernel layer of the first system domain.

[0046] Specifically, the central control display screen touch driver is a touch driver program for the central control display screen, which can communicate with the central control display screen, obtain touch data collected by the central control display screen for the panoramic monitor processing program, and then upload the touch data to the input core of the input subsystem of the Linux kernel layer of the first system domain, that is, the first core driver.

[0047] The first core driver can distribute the touch data and send the touch data to the touch screen service driver; the touch screen service driver, as the touch screen core service driver of the Linux kernel layer of the first system domain, is responsible for receiving and sharing the touch data, caching the touch data to the shared memory, and sending a notification message to the second system domain when the touch data meets the preset transmission conditions.

[0048] Furthermore, the touch screen service driver can also distribute the touch data to the AVM service program (AVM Service) of the native service layer of the first system domain, and the AVM Service can interact with the AVM startup program of the first system domain through the AVMAdapt API (Adapt Application Programming Interface) of the framework layer of the first system domain. Among them, the AVM startup program of the first system domain is mainly used to start the AVM application, and the data processing of the AVM application is mainly performed by the AVM processing program of the second system domain.

[0049] In one implementation, the touch data of the target area based on the central control display screen is acquired through the central control display screen touch driver of the first system domain, and the touch data is uploaded to the first core driver of the first system domain, including: The central control display screen touch driver of the first system domain receives the touch protocol data of the target area uploaded by the central control display screen through the integrated circuit bus; Parse and encapsulate the touch protocol data to obtain an input event data packet as touch data; The touch data is uploaded to a first core driver of the first system domain.

[0050] That is to say, the central control display touch driver module communicates with the central control display through I2C (Inter-Integrated Circuit, integrated circuit bus). I2C is a communication protocol that can realize communication between the first system domain and other peripheral modules such as the central control display. In this way, the central control display touch driver module can receive the touch protocol data uploaded by the central control display.

[0051] Then, the central control display screen touch driver module parses the touch protocol data and encapsulates it into an input event data packet as touch data; then, the touch data can be uploaded to the first core driver.

[0052] In one implementation, the first system domain further includes a first communication module, and the first system domain sends a notification message to the second system domain, including: The touch screen service driver of the first system domain notifies the first communication module to send a notification message; The first communication module sends a notification message to the second system domain through a full-duplex message channel based on a remote system domain communication protocol.

[0053] The first communication module may be a communication module based on the rpmsg (remote processor messaging) protocol. The rpmsg protocol may implement communication through a full-duplex message channel. For example, the full-duplex message channel may be a Mailbox hardware channel.

[0054] That is, when the touch data meets the preset transmission conditions, the touch screen service driver triggers the first communication module, and the first communication module sends a notification message to the second system domain through the Mailbox, and the notification message is used to prompt the second system domain to obtain the touch data from the shared memory and process it.

[0055] In one implementation, after uploading the touch data to the first core driver of the first system domain, the cross-domain touch data transmission method further includes: The first core driver sends the touch data to the first event processing driver of the first system domain; The first event processing driver forwards the touch data to the user space.

[0056] For example, after the touch data is forwarded to the user space, it can first be managed by the first system domain input HAL (Hardware Abstraction Layer). The input HAL is the Android HAL of the Native layer of the first system domain. It can provide a unified interface for the upper-level Android applications to call the touch data, and at the same time can shield the details of the underlying implementation, that is, the upper-level applications do not need to know how the lower-level hardware collects touch data.

[0057] Step S13: the second system domain obtains touch data from the shared memory in response to the notification message; and reports the touch data to the panoramic monitor processing program for processing.

[0058] In this step, after receiving the notification message sent by the first system domain, the second system domain can respond to the notification message, obtain touch data from the shared memory, and then report the touch data to the AVM handler, which processes the touch data and responds to the user's touch instructions.

[0059] Moreover, in the present application, by setting the second system domain, the transmission of touch data can be turned on and off according to business needs, thereby effectively saving system resources.

[0060] In one implementation, the second system domain obtains touch data from the shared memory in response to the notification message; and reports the touch data to the panoramic monitor processing program for processing, including: The virtual touch driver of the second system domain obtains touch data from the shared memory in response to the notification message; and reports the touch data to the second core driver of the second system domain; The second core driver reports the touch data to the panoramic monitor processing program for processing.

[0061] That is to say, the software architecture in the second system domain includes at least a virtual touch driver and a second core driver, wherein the second core driver is an input core of an input subsystem of a Linux kernel layer in the second system domain.

[0062] Specifically, the virtual touch driver (virtual TP drive) in the second system domain can obtain touch data from the shared memory after receiving the notification message sent by the first system domain, thereby realizing the transmission of touch data from the first system domain to the second system domain.

[0063] Then, the virtual touch driver can report the touch data to the second core driver, and the second core driver reports the touch data to the AVM processing program for further processing and analysis. After receiving the touch data, the AVM processing program can process the touch data and respond to the user's touch operation.

[0064] In one implementation, the second core driver reports the touch data to the panoramic monitor processing program for processing, including: The second core driver reports the touch data to the second event processing driver of the second system domain; The second event processing driver reports the touch data to the input event parsing driver of the second system domain; The input event parsing driver parses the touch data by calling a function to obtain parsed data, and reports the parsed data to the panoramic monitor processing program; The panoramic view monitor processing program processes the parsed data.

[0065] That is to say, in the process that the second core driver reports the touch data to the AVM processing program, the touch data will pass through the second event processing driver, the input event parsing driver and other modules in sequence.

[0066] Among them, the second event processing driver is the input evdev driver of the Linux kernel layer of the second system domain, and the input event parsing driver is an event parsing driver based on libinput. Libinput is a library function of Linux standard inputevent parsing. The functions included in libinput can be used to read and parse the received touch data to obtain parsed data.

[0067] Furthermore, the AVM handler can process the parsed data and respond to the user's touch operations.

[0068] In one implementation, the second system domain further includes a second communication module, and the virtual touch driver of the second system domain obtains touch data from the shared memory in response to the notification message, including: The second communication module receives the notification message through the full-duplex message channel; sends a data acquisition notification to the virtual touch driver of the second system domain; The virtual touch driver obtains the touch data from the shared memory in response to the data acquisition notification.

[0069] The second communication module may be a communication module based on the rpmsg protocol. Thus, after receiving the notification message sent by the first system domain through the Mailbox, the second communication module may send a data acquisition notification to the virtual touch driver, where the data acquisition notification is used to prompt the virtual touch driver to acquire touch data. Then, the virtual touch driver can obtain the touch data from the shared memory and further forward the touch data.

[0070] In one embodiment, Figure 2 As shown, it is a software architecture diagram of a cross-domain touch data transmission method provided by the present application. Among them, the smart cockpit chip can adopt E04 chip, which can be used to run the first system domain and the second system domain, and the first system domain and the second system domain are AP domain and CP domain respectively.

[0071] The AP domain includes: the AVM startup program of the application (APP) layer; the AVM Adapt API of the framework (FWK) layer; the input HAL and AVM Service of the native service (Native) layer; the first event processing driver (inputevdev), virtual TP service Drive, the first core driver (input core), the first communication module (rpmsg module), and the touchscreen driver of the kernel layer; The CP domain includes: the second communication module (rpmsg module) of the kernel layer, the virtual TP drive, the second core driver (input core), the second event processing driver (input evdev); the input event parsing driver (libinput) of the core implementation layer (Runtime); and the AVM handler of the APP layer. In addition, the hardware layer (Hardware) of the E04 chip also includes shared memory (LPDDR) and message channel (Mailbox).

[0072] exist Figure 2 In the software architecture shown, when the user performs a touch operation on the AVM interface displayed on the vehicle's central control display screen, the AVM handler in the CP domain responds to the touch operation. In this process, the transmission flow of touch data is as follows: The central control display screen sends the collected touch protocol data to the touchscreen driver via I2C; The touchscreen driver parses the touch protocol data, encapsulates it into input event data packets, and sends it to the input core of the AP domain as touch data; The input core of the AP domain distributes the touch data to the virtual TP service driver; The virtual TP service driver caches touch data to LPDDR; When the amount of touch data exceeds the preset data amount threshold or the cache time of touch data in LPDDR exceeds 50ms, the rpmsg module in the AP domain sends a notification message to the rpmsg module in the CP domain through the Mailbox; After receiving the notification message, the rpmsg module in the CP domain notifies the virtual TP drive; The virtual TP drive takes the touch data from LPDDR and reports it to the input core of the CP domain; The input core of the CP domain reports the touch data to the input evdev, libinput and AVM processing program of the CP domain in sequence, and then the AVM processing program performs corresponding business processing according to the touch data.

[0073] Therefore, in the above process, the touch data is diverted through the virtual TP service driver in the AP domain, and the virtual TP drive in the CP domain uses the driver design of the standard input subsystem, which reduces the workload of AVM business development. Moreover, there is no need to modify the driver of the central control display itself, and it is independent of the touch hardware and driver, thus realizing a platform design.

[0074] From the above, it can be seen that the technical solution provided by the embodiment of the present application, when the central control display screen and the panoramic monitor are controlled by different system domains of the smart cockpit chip, after the central control display screen collects the user's touch data of the panoramic monitor processor, the touch data can be transmitted to the first system domain. After obtaining the touch data, the first system domain transmits the touch data to the second system domain through shared memory. Then, the second system domain reports the touch data to the panoramic monitor processor, and the panoramic monitor processor parses and processes the touch data, thereby realizing the issuance of user touch commands.

[0075] The touch data transmission method provided in the embodiment of the present application can be executed by a touch data transmission device. In the embodiment of the present application, a method in which a touch data transmission device executes terminal access is taken as an example to illustrate the device of the touch data transmission method provided in the embodiment of the present application.

[0076] Figure 31 is a block diagram of a cross-domain touch data transmission device according to an exemplary embodiment, which is applied to a smart cockpit chip running multiple system domains, including a first system domain 210 and a second system domain 220, wherein: The first system domain 210 is used to cache the touch data of the target area based on the central control display screen to the shared memory; the target area is the display area of ​​the panoramic monitor processing program of the second system domain other than the first system domain among the multiple system domains; and send a notification message to the second system domain 220; The second system domain 220 is used to obtain touch data from the shared memory in response to the notification message; and report the touch data to the panoramic monitor processing program 223 for processing.

[0077] In one implementation, the first system domain 210 is specifically used for: When the touch data meets a preset transmission condition, a notification message is sent to the second system domain 220 .

[0078] In one implementation, the preset transmission condition includes: The caching time of the touch data exceeds a preset time threshold; and / or, The touch data cached in the shared memory exceeds a preset data amount threshold.

[0079] In one implementation, the first system domain 210 includes a central control display screen touch driver 211, a first core driver 212 and a touch screen service driver 213: The central control display screen touch driver 211 is used to obtain touch data of a target area based on the central control display screen, and upload the touch data to the first core driver 212; The first core driver 212 is used to send the touch data to the touch screen service driver 213; The touch screen service driver 213 is used to cache the touch data into a shared memory.

[0080] In one implementation, the central control display screen touch driver 211 is specifically used for: Receive the touch protocol data of the target area uploaded by the central control display screen through the integrated circuit bus; Parsing and encapsulating the touch protocol data to obtain an input event data packet as touch data; The touch data is uploaded to the first core driver 212 .

[0081] In one implementation, the first system domain further includes a first communication module 214, wherein: The touch screen service driver 213 is specifically used to notify the first communication module 214 to send the notification message; The first communication module is used to send the notification message to the second system domain 220 through a full-duplex message channel based on a remote system domain communication protocol.

[0082] In one implementation, the first system domain 210 further includes a first event processing driver, wherein: The first core driver 212 is further configured to send the touch data to the first event processing driver; The first event processing driver is used to forward the touch data to a user space.

[0083] In one implementation, the second system domain 220 further includes a virtual touch driver 221 and a second core driver 222, wherein: The virtual touch driver 221 is used to obtain the touch data from the shared memory in response to the notification message; and report the touch data to the second core driver 222; The second core driver 222 is used to report the touch data to the panoramic monitor processing program 223 for processing.

[0084] In one implementation, the second system domain 220 further includes a second event processing driver and an input event parsing driver, wherein: The second core driver 222 is specifically configured to report the touch data to the second event processing driver; The second event processing driver is used to report the touch data to the input event parsing driver; The input event parsing driver is used to parse the touch data by calling a function to obtain parsed data, and report the parsed data to the panoramic monitor processing program 223; The panoramic monitor processing program 223 is used to process the parsed data.

[0085] In one implementation, the second system domain 220 further includes a second communication module 224, wherein: The second communication module 224 is used to receive the notification message through a full-duplex message channel; and send a data acquisition notification to the virtual touch driver 221; The virtual touch driver 221 is specifically configured to obtain the touch data from the shared memory in response to the data acquisition notification.

[0086] From the above, it can be seen that the technical solution provided by the embodiment of the present application, when the central control display screen and the panoramic monitor are controlled by different system domains of the smart cockpit chip, after the central control display screen collects the user's touch data of the panoramic monitor processor, the touch data can be transmitted to the first system domain. After obtaining the touch data, the first system domain transmits the touch data to the second system domain through shared memory. Then, the second system domain reports the touch data to the panoramic monitor processor, and the panoramic monitor processor parses and processes the touch data, thereby realizing the issuance of user touch commands.

[0087] The touch data transmission method provided in the embodiment of the present application can be executed by a terminal access terminal. In the embodiment of the present application, a method for executing terminal access by a terminal access terminal is taken as an example to illustrate the device of the touch data transmission method provided in the embodiment of the present application.

[0088] The touch data transmission device in the embodiment of the present application can be an electronic device, or a component in the electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or it can be other devices other than a terminal. Exemplarily, the electronic device can be a mobile phone, a tablet computer, a laptop computer, a PDA, a vehicle-mounted electronic device, a mobile Internet device (Mobile Internet Device, MID), an augmented reality (augmented reality, AR) / virtual reality (virtual reality, VR) device, a robot, a wearable device, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a netbook or a personal digital assistant (personal digital assistant, PDA), etc. It can also be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.

[0089] The touch data transmission device provided in the embodiment of the present application can realize Figures 1 to 3 To avoid repetition, the various processes implemented by the method embodiment are not described here.

[0090] Alternatively, if Figure 4As shown, an embodiment of the present application further provides an electronic device 500, including a processor 501 and a memory 502, wherein the memory 502 stores a program or instruction that can be executed on the processor 501, and when the program or instruction is executed by the processor 501, each step of the above-mentioned touch data transmission method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0091] It should be noted that the electronic devices in the embodiments of the present application include the mobile electronic devices and non-mobile electronic devices mentioned above.

[0092] Figure 5 A schematic diagram of the hardware structure of an electronic device to implement an embodiment of the present application.

[0093] The electronic device 1000 includes but is not limited to: a radio frequency unit 1001, a network module 1002, an audio output unit 1003, an input unit 1004, a sensor 1005, a display unit 1006, a user input unit 1007, an interface unit 1008, a memory 1009, and a processor 1010 and other components.

[0094] Those skilled in the art will appreciate that the electronic device 1000 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 1010 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Figure 5 The electronic device structure shown in the figure does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0095] From the above, it can be seen that the technical solution provided by the embodiment of the present application, when the central control display screen and the panoramic monitor are controlled by different system domains of the smart cockpit chip, after the central control display screen collects the user's touch data of the panoramic monitor processor, the touch data can be transmitted to the first system domain. After obtaining the touch data, the first system domain transmits the touch data to the second system domain through shared memory. Then, the second system domain reports the touch data to the panoramic monitor processor, and the panoramic monitor processor parses and processes the touch data, thereby realizing the issuance of user touch commands.

[0096] It should be understood that in the embodiment of the present application, the input unit 1004 may include a graphics processor (GPU) 10041 and a microphone 10042, and the graphics processor 10041 processes the image data of the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the image capture mode. The display unit 1006 may include a display panel 10061, and the display panel 10061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1007 includes a touch panel 10071 and at least one of other input devices 10072. The touch panel 10071 is also called a touch screen. The touch panel 10071 may include two parts: a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, a physical keyboard, function keys (such as a volume control key, a switch key, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0097] The memory 1009 can be used to store software programs and various data. The memory 1009 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 1009 may include a volatile memory or a non-volatile memory, or the memory 1009 may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM) and a direct memory bus random access memory (DRRAM). The memory 109 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0098] The processor 1010 may include one or more processing units; optionally, the processor 1010 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 1010.

[0099] The embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the above-mentioned touch data transmission method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0100] The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk.

[0101] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned touch data transmission method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0102] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0103] An embodiment of the present application provides a computer program product, which is stored in a storage medium. The program product is executed by at least one processor to implement the various processes of the above-mentioned touch data transmission method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0104] It should be noted that, in this article, the term "comprises", "includes" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "including one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the method and device in the embodiment of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0105] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for enabling a terminal (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0106] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. A cross-domain touch data transmission method, characterized in that: Applied to smart cockpit chips running multiple system domains, including: The first system domain caches the touch data of the target area based on the central control display screen into the shared memory; the target area is a display area of ​​the panoramic monitor processing program of the second system domain other than the first system domain among the multiple system domains; The first system domain sends a notification message to the second system domain; The second system domain obtains the touch data from the shared memory in response to the notification message; and reports the touch data to the panoramic monitor processing program for processing.

2. The cross-domain touch data transmission method according to claim 1, characterized in that: The first system domain sending a notification message to the second system domain includes: When the touch data meets a preset transmission condition, a notification message is sent to the second system domain.

3. The cross-domain touch data transmission method according to claim 2, characterized in that: The preset transmission conditions include: The caching time of the touch data exceeds a preset time threshold; and / or, The touch data cached in the shared memory exceeds a preset data amount threshold.

4. The cross-domain touch data transmission method according to claim 1, characterized in that: The first system domain caches the touch data of the target area based on the central control display screen into the shared memory, including: Acquire touch data of a target area based on the central control display screen through the central control display screen touch driver of the first system domain, and upload the touch data to the first core driver of the first system domain; The first core driver sends the touch data to the touch screen service driver of the first system domain; The touch screen service driver caches the touch data into a shared memory.

5. The cross-domain touch data transmission method according to claim 4, characterized in that: The acquiring touch data of a target area based on the central control display screen through the central control display screen touch driver of the first system domain, and uploading the touch data to the first core driver of the first system domain includes: The central control display screen touch driver of the first system domain receives the touch protocol data of the target area uploaded by the central control display screen through the integrated circuit bus; Parsing and encapsulating the touch protocol data to obtain an input event data packet as touch data; The touch data is uploaded to a first core driver of the first system domain.

6. The cross-domain touch data transmission method according to claim 4, characterized in that: The first system domain further includes a first communication module, and the first system domain sends a notification message to the second system domain, including: The touch screen service driver of the first system domain notifies the first communication module to send the notification message; The first communication module sends the notification message to the second system domain through a full-duplex message channel based on a remote system domain communication protocol.

7. The cross-domain touch data transmission method according to claim 4, characterized in that: After uploading the touch data to the first core driver of the first system domain, the method further includes: The first core driver sends the touch data to a first event processing driver of the first system domain; The first event processing driver forwards the touch data to a user space.

8. The cross-domain touch data transmission method according to claim 1, characterized in that: The second system domain obtains the touch data from the shared memory in response to the notification message; Reporting the touch data to the panoramic monitor processing program for processing includes: The virtual touch driver of the second system domain obtains the touch data from the shared memory in response to the notification message; and reports the touch data to the second core driver of the second system domain; The second core driver reports the touch data to the panoramic monitor processing program for processing.

9. The cross-domain touch data transmission method according to claim 8, characterized in that: The second core driver reports the touch data to the panoramic monitor processing program for processing, including: The second core driver reports the touch data to a second event processing driver in the second system domain; The second event processing driver reports the touch data to an input event parsing driver input into the second system domain; The input event parsing driver parses the touch data by calling a function to obtain parsed data, and reports the parsed data to the panoramic monitor processing program; The panoramic monitor processing program processes the parsed data.

10. The cross-domain touch data transmission method according to claim 8, characterized in that: The second system domain further includes a second communication module, and the virtual touch driver of the second system domain obtains the touch data from the shared memory in response to the notification message, including: The second communication module receives the notification message through a full-duplex message channel; and sends a data acquisition notification to the virtual touch driver of the second system domain; The virtual touch driver acquires the touch data from the shared memory in response to the data acquisition notification.

11. A cross-domain touch data transmission device, characterized in that: Applied to smart cockpit chips running multiple system domains, including: A first system domain, used to cache touch data of a target area based on a central control display screen to a shared memory; send a notification message to a second system domain other than the first system domain among multiple system domains; the target area is a display area of ​​a panoramic monitor processing program of the second system domain; The second system domain is used to obtain the touch data from the shared memory in response to the notification message; and report the touch data to the panoramic monitor processing program for processing.

12. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the cross-domain touch data transmission method according to any one of claims 1 to 10.

13. A readable storage medium, characterized in that: The readable storage medium stores a program or an instruction, and when the program or the instruction is executed by the processor, the steps of the cross-domain touch data transmission method according to any one of claims 1 to 10 are implemented.

Citation Information

Patent Citations

  • Cross-domain communication method, system and device for intelligent cabin and storage medium

    CN112929343A

  • Touch screen control method and system supporting multiple operating systems and chip

    CN115145645A

  • Data transmission method and device under virtualization management, equipment and medium

    CN116248772A

  • Cross-domain audio processing method and device, electronic equipment and storage medium

    CN116540973A

  • Quick display method, system and equipment for panoramic looking-around system and medium

    CN117201872A

Cited By

  • Cross-system touch screen data processing method, system and equipment based on HAB mechanism

    CN120743136A