Method and apparatus for transmitting screen data

Abstract

The present invention relates to the field of computer technology, and discloses a method and device for transmitting screen data. The method includes: obtaining the screen type in a configuration file; based on the screen type, determining a target data acquisition route for the screen data from a plurality of preset transmission routes, and determining an interrupt number corresponding to the target screen type; sending the screen data to each application in a target message queue according to the screen data type and the screen type; wherein, the screen types and screen data types of the applications in the target message queue are the same.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and particularly to a method and device for transmitting screen data. Background Art

[0002] Most of the human-machine interaction screens in the current smart cockpit systems adopt touch technology to implement user input operations. To collect touch data, the prior art usually relies on software interfaces to directly access the I 2 C (Inter-Integrated Circuit) bus of the screen terminal. The I 2 C bus is a serial communication bus used to connect low-speed peripheral devices and is widely used in various electronic devices, including the screen module of the smart cockpit. Through this direct access method, the system can obtain real-time touch information of users, such as click positions, sliding trajectories, etc., and then trigger corresponding application functions.

[0003] However, the screen module of the smart cockpit not only includes a touch function module but also integrates multiple subsystems such as backlight services and temperature monitoring. These subsystems also need to communicate with the main controller through the I 2 C bus to implement their respective functions. Therefore, in actual operation, multiple functional modules will compete for the access right to the I 2 C bus at the same time, which may cause the touch data to be interfered by the services of other functional modules during the transmission process, resulting in incorrect judgments of application screen click events.

[0004] Therefore, how to improve the accuracy of triggering application screen click events becomes a problem to be solved. Summary of the Invention

[0005] In view of this, the present invention provides a method and device for transmitting screen data.

[0006] In a first aspect, the present invention provides a method for transmitting screen data, the method including: obtaining a target screen type in a configuration file; determining an acquisition route of screen data corresponding to the target screen type and determining an interrupt number corresponding to the target screen type from a plurality of preset transmission routes; sending screen data to each application in a target message queue according to the screen data type and the target screen type; wherein, the target screen types and screen data types of each application in the target message queue are the same.

[0007] The screen data transmission method provided in this embodiment configures the acquisition route of screen data corresponding to the screen type for each screen. When an interrupt reported by the interrupt number is obtained, the acquisition route of screen data is determined through the transmission route corresponding to the screen type, and according to the target screen data and the screen type, the screen data is sent to each application in the target message queue, so as to avoid the interference of touch data by the services of other functional modules during the transmission process, which may cause incorrect judgments of application screen click events, thereby improving the accuracy of application triggering of screen click events.

[0008] In a possible implementation manner, determining the acquisition route of screen data corresponding to the target screen type and determining the interrupt number corresponding to the target screen type from a preset plurality of transmission routes includes: matching the configuration files of each intelligent cockpit hardware in the vehicle based on the target screen type; wherein, the file content of the configuration file includes: screen type, iic bus, device address of the screen, and interrupt number; determining the target configuration file of the intelligent cockpit hardware with the target screen type from multiple screen types; determining the target screen interrupt number, target iic bus, and device address of the target screen based on the target configuration file; and determining the target data acquisition route of the screen data based on the target screen type, target iic bus, and device address of the target screen.

[0009] The screen data transmission method provided in this embodiment can accurately identify the intelligent cockpit hardware that generates screen data through the precise matching of the target screen type and the configuration file, thereby avoiding misoperations and confusion in data transmission. Moreover, once the target configuration file is determined, the transmission route can be quickly determined based on the information (such as interrupt number, iiC bus, device address of the screen, etc.) in the configuration file, thus realizing the efficient transmission of screen data.

[0010] In a possible implementation manner, sending the screen data to each application in the target message queue according to the screen data type and the target screen type includes: obtaining the special character corresponding to the screen data type from the target screen type; and transmitting the screen data to each application in the target message queue based on the special character.

[0011] The screen data transmission method provided in this embodiment can quickly identify the type of screen data by extracting the special character from the target screen type. Once the data type is identified, the system can directly transmit the screen data to the corresponding target transmission route according to the preset transmission route rules, improving the efficiency of data processing.

[0012] In a possible implementation, the method further includes: obtaining the registration information of each application; wherein the registration information includes the screen type and screen data type corresponding to the application; dividing target applications with the same screen type and screen data type into the same message queue.

[0013] For the screen data transmission method provided in this embodiment, when other applications are registering, each application is classified according to the registration information of each application, and applications with the same screen type and screen data type are assigned to the same message queue, so that the screen-reported data can be sent to all applications in the same queue simultaneously.

[0014] In a possible implementation, the method further includes: obtaining pulse information; detecting whether the pulse information conforms to a preset pulse; if the pulse information conforms to the preset pulse, removing the target application corresponding to the pulse information from the target message queue.

[0015] For the screen data transmission method provided in this embodiment, by obtaining the pulse information and quickly detecting it, the system can quickly determine whether the pulse conforms to the preset conditions. Once a pulse that conforms to the preset conditions is detected, the system can immediately remove the corresponding target application from the target message queue, realizing the timely response and processing of events.

[0016] In a second aspect, the present invention provides a screen data transmission device, which includes: an obtaining module for obtaining the screen type in the configuration file; a determining module for determining the obtaining route of the screen data corresponding to the screen type from a preset plurality of transmission routes and determining the interrupt number corresponding to the screen type; a sending module for sending the screen data to each application in the target message queue according to the screen data type and the screen type; wherein the screen type and screen data type of each application in the target message queue are the same.

[0017] In a third aspect, the present invention provides a computer device, including: a memory and a processor, which are communicatively connected to each other. The memory stores computer instructions, and the processor executes the computer instructions to execute the screen data transmission method according to the first aspect or any corresponding implementation manner thereof.

[0018] In a fourth aspect, the present invention provides a vehicle, including: a memory and a processor, which are communicatively connected to each other. The memory stores computer instructions, and the processor executes the computer instructions to execute the screen data transmission method according to the first aspect or any corresponding implementation manner thereof.

[0019] Fifth aspect, the present invention provides a computer-readable storage medium, on which computer instructions are stored, and the computer instructions are used to cause a computer to execute the screen data transmission method according to the first aspect or any corresponding embodiment thereof.

[0020] Sixth aspect, the present invention provides a computer program product, including computer instructions, and the computer instructions are used to cause a computer to execute the screen data transmission method according to the first aspect or any corresponding embodiment thereof. Description of the Drawings

[0021] In order to more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the following will briefly introduce the drawings required for the description of the specific embodiments or the prior art. Obviously, the drawings in the following description are some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0022] Figure 1 is a flowchart of the screen data transmission method according to an embodiment of the present invention;

[0023] Figure 2 is a schematic diagram of the screen data transmission method according to an embodiment of the present invention;

[0024] Figure 3 is a structural block diagram of the screen data transmission device according to an embodiment of the present invention;

[0025] Figure 4 is a schematic diagram of the hardware structure of the computer device according to an embodiment of the present invention. Detailed Embodiments

[0026] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the drawings in the embodiments of the present invention. Obviously, the described embodiments are some, but not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the protection scope of the present invention.

[0027] Based on the related art, it is known that the screen module of the intelligent cockpit not only includes a touch function module, but also integrates multiple subsystems such as a backlight service and temperature monitoring. These subsystems also need to communicate with the main controller through the I 2 C bus to achieve their respective functions. Therefore, in actual operation, multiple functional modules will simultaneously compete for the I 2The access right of the C bus may cause the touch data to be interfered by the services of other functional modules during the transmission process, resulting in an incorrect judgment of the screen click event by the application.

[0028] Based on this, for the screen data transmission method provided by the present invention, a corresponding target data acquisition route is configured for each screen type of the screen. When the target interrupt number corresponding to the screen data is obtained, the acquisition route of the screen data is determined through the transmission route corresponding to the screen type, and the screen data type is determined. According to the screen data type and the screen type, the screen data is sent to each application in the target message queue, so as to avoid the touch data being interfered by the services of other functional modules during the transmission process, resulting in an incorrect judgment of the screen click event by the application, thereby improving the accuracy of the application's trigger of the screen click event.

[0029] According to an embodiment of the present invention, an embodiment of a screen data transmission method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order than here.

[0030] In this embodiment, a screen data transmission method is provided, which can be used in computer devices such as computers and servers. Figure 1 It is a flowchart of the screen data transmission method according to an embodiment of the present invention, as Figure 1 shown, and the process includes the following steps:

[0031] Step S101, obtain the target screen type in the configuration file.

[0032] Screen data may refer to digital information carrying certain information of the screen transmitted from the screen end to the host end. The screen type may be an instrument screen, a central control entertainment screen, a screen in the co-pilot position, a vehicle control screen, a head-up display, a rear seat screen, etc., and no specific limitation is made here.

[0033] Step S102, determine the acquisition route of the screen data corresponding to the target screen type from a preset multiple transmission routes, and determine the interrupt number corresponding to the target screen type.

[0034] The data acquisition route of the screen data may be the process of the screen data to the host, that is, the process from the generation of the screen data to the soc system. The screen data type refers to data such as touch, temperature, and fault codes, and different types of screen data may require different data processing methods.

[0035] Step S103: Send the screen data to each application in the target message queue according to the screen data type and the target screen type. Among them, the target screen types of the applications in the target message queue are the same as the screen data type.

[0036] The target message queue is used to store screen data waiting to be processed or distributed. Each element in the queue is usually associated with a specific screen type, screen data, and application. The screen types and screen data of the applications in the target message queue are the same. Specifically, according to the determined screen type and screen data type, the screen data is sent to the target message queue, and each application in the queue matches this screen type. For example: The obtained light sensor data is transmitted to the application that needs this data through inter-process communication in the system, and this data makes corresponding processing on the in-vehicle screen according to the magnitude of the light sensor value, increasing or decreasing the brightness.

[0037] In a possible implementation, a message middleware (such as RabbitMQ, Kafka, etc.) can be used to implement the distribution of screen data. The screen data can be sent to the target application through a network protocol (such as TCP / IP, UDP, etc.).

[0038] In this embodiment, for each screen, a corresponding target data acquisition route is configured according to the screen type. When an interrupt reported by the interrupt number is obtained, the target acquisition route of the screen data is determined through the transmission route corresponding to the screen type, and the target screen data type is determined. According to the target screen data and the screen type, the screen data is sent to each application in the target message queue, so as to avoid the interference of touch data by the services of other functional modules during the transmission process, which may cause incorrect judgments of the application on the screen click event, thereby improving the accuracy of the application triggered by the screen click event.

[0039] In a possible implementation, the above step S102 includes:

[0040] Step a1: Based on the target screen type, match the configuration files of each intelligent cockpit hardware in the vehicle. Among them, the content of the configuration file includes: screen type, IIC bus, device address of the screen, and interrupt number.

[0041] The configuration file can be a file containing the detailed information of the intelligent cockpit hardware, such as the screen type, communication bus (such as IIC bus), device address, and interrupt number, etc. Specifically, traverse the configuration files of each intelligent cockpit hardware in the vehicle to find the configuration items that match the target screen type. For example: There are three screen devices in the vehicle intelligent cockpit system, and each device has a configuration file. Configuration file 1 contains the screen type "02", the screen type is the center console screen, the IIC bus is "IIC1", the device address is "0x3C", and the interrupt number is "150". Configuration files 2 and 3 contain other screen types and hardware information respectively. When the target screen type is "02", the system traverses all configuration files and finds configuration file 1 that matches "02".

[0042] In a possible implementation, the intelligent cockpit system starts, and sets the startup instance of this method in the early stage of the startup of the intelligent cockpit system. The early stage requires that the applications that need screen data have not started yet. Pass the configuration file that matches the intelligent cockpit hardware to the system in the form of startup parameters. The content of the configuration file includes the screen type, which can be distinguished by numbers or letters. For example, the number 1 represents the instrument screen, the number 2 represents the center console entertainment screen, the number 3 represents the screen in the co-pilot position, the number 4 represents the vehicle control screen, the number 5 represents the head-up display, the number 6 represents the rear seat screen, etc.; the content of the configuration file also includes the iic bus used by the screen, such as iic1, iic2, etc. Most screens use the iic protocol to communicate with the cockpit main controller; the device address of each screen, and the device address requirement is that there cannot be the same device address on the same iic bus; the interrupt number. This method requires that all data at the screen end be reported in the form of screen end interrupts. The interrupt number is unique for each screen for the intelligent cockpit host and is stored in the host memory.

[0043] Step a2, determine the target configuration file of the intelligent cockpit hardware with the target screen type from multiple screen types.

[0044] From all the configuration files, select the screen type that matches the target screen type and the configuration file corresponding to the screen type as the target configuration file. For example: In configuration file 1 found in step a1, the screen type "02" matches the target screen type, so configuration file 1 is determined as the target configuration file.

[0045] Step a3, based on the target configuration file, determine the target screen interrupt number, target iic bus, and device address of the target screen.

[0046] Extract the target interrupt number, target IIC bus, and device address of the target screen from the target configuration file. For example: Extract from target configuration file 1 that the target screen interrupt is 150, the target IIC bus is "IIC1", and the device address of the target screen is "0x3C".

[0047] Step a4, based on the target screen type, target iic bus, and device address of the target screen, determine the acquisition route of the target screen data.

[0048] According to the target screen type, target IIC bus, and device address of the target screen, determine which communication path (i.e., the target acquisition route) the screen data should be transmitted to the soc through.

[0049] In this embodiment, by matching the target screen type with the interrupt number in the configuration file, it is possible to accurately identify which screen the screen data is generated from, thus avoiding misoperations and confusion in data transmission. And once the target configuration file is determined, the data acquisition route can be quickly determined based on the information in the configuration file (such as screen type, iiC bus, device address of the screen, etc.), thereby achieving efficient transmission of screen data.

[0050] In a possible implementation, the above step S102 includes:

[0051] Step b1, obtain the special character corresponding to the screen data type from the target screen type.

[0052] The special character can be a character or symbol embedded when the screen sends data, used to identify the data type or transmission characteristics. These special characters are composed of numbers, and their positions and combinations are defined according to the protocol between the screen and the host. Analyze the target screen data and extract the special character corresponding to the data type from it. These special characters may be used to distinguish different types of data (such as temperature, brightness, etc.). Specifically, a parser can be written to extract special characters according to the custom protocol between the screen end and the host end. Regular expressions or string operation functions can be used to find and extract special characters. For example: The target data is "0x311234", where the first byte "31" is the special character, used to identify that the data type is touch data. The system analyzes the target data and extracts the special character "0x31".

[0053] Step b2, based on the special character, transmit the screen data to each application in the target message queue.

[0054] Based on the extracted special characters, select the transmission route that matches the target data type and screen type from multiple preset transmission routes. Specifically, the special characters can be matched with the identifiers or attributes of the transmission routes. For example: among the multiple preset transmission routes, there is one designed specifically for touch data transmission, and its identifier or attribute may contain information that matches the special character "0x31". The system matches the special character "0x31" with the identifier or attribute of the transmission route and finds the transmission route that matches the touch data type. Finally, the system determines that the target transmission route is the one designed specifically for touch data transmission.

[0055] In this embodiment, by extracting special characters from the target screen data, the system can quickly identify the type of the screen data. Once the data type is identified, the system can directly route the screen data to the corresponding target transmission route according to the preset transmission route rules, improving the efficiency of data processing.

[0056] In a possible implementation manner, the above method further includes:

[0057] Step c1, obtain the registration information of each application; wherein, the registration information includes the screen type and screen data type corresponding to the application.

[0058] When other applications register, other applications call the provided registration interface to complete the registration. The information attached to the registration information includes the screen type, the special character (screen data type) representing the type in the data reported by the screen that needs to be concerned about. For example, 0x31 is in a separate position in the data reported by the screen. The data with this special character needs to be concerned about. Only this information needs to be attached to the registration information. The registration information also includes the callback function for the registered application to process the concerned type of data, and the chanel ID established by the registered application through the qnx system. This ID needs to be passed to the system for communication between the screen and the registered application.

[0059] Step c2, divide the target applications with the same screen type and screen data type into the same message queue.

[0060] The system divides the target applications into different message queues according to the data type and screen type. Each message queue contains target applications with the same data type and screen type.

[0061] As an example, there are two types of screen data: touch data and light sensor data. Touch data is usually used to generate responses when clicking on the screen, while light sensor data may be used for backlight services.

[0062] In this embodiment, when other applications are registered, the applications are classified according to the registration information of each application, and the applications with the same screen type and screen data type are assigned to a message queue, so that the data reported by the screen can be sent to all applications in the same queue simultaneously.

[0063] In a possible implementation manner, the method further includes:

[0064] Step d1: Obtain pulse information; detect whether the pulse information conforms to a preset pulse.

[0065] The pulse information can indicate the occurrence of a certain specific condition or action. This signal is used to trigger a system response or execute a specific task.

[0066] Step d2: If the pulse information conforms to the preset pulse, remove the target application corresponding to the pulse information from the target message queue.

[0067] As an example, this method has a monitoring function for registered applications. This method will connect to the chanel ID created by the client, which is passed to the system during registration and obtains a coid. When this coid is disconnected, the qnx kernel can send a system pulse to the system. If this system receives a system pulse with the value of _PULSE_CODE_COIDDEATH, it means that the connection of an application has been disconnected, where pulse.value.sival_int is the coid that has just been disconnected. The corresponding client information can be searched in the queue according to this coid. If it is found, it means that this client has exited, and then it is removed from the queue storing registered users.

[0068] The method for transmitting screen data provided in this embodiment can quickly detect the obtained pulse information. The system can quickly determine whether the pulse conforms to the preset condition. Once a pulse that conforms to the preset condition is detected, the system can immediately remove the corresponding target application from the target message queue, realizing timely response and processing of events.

[0069] Reference Figure 2 , Figure 2 is a schematic diagram of the method for transmitting screen data according to the embodiment of the present invention;

[0070] Applications 1, 2,..., n are registered. This method has the detection of abnormal events for registered applications. This method will connect to the channel ID created by the client, which is passed to the system by the application during registration and obtains a coid. When this coid is disconnected, the QNX kernel can send a system pulse to the system. If this system receives a system pulse with the value of _PULSE_CODE_COIDDEATH, it means that the connection of an application has been disconnected. Among them, pulse.value.sival_int is the coid that has just been disconnected. The corresponding client information can be searched in the queue according to this coid. If it is found, it means that this client has exited, and then it will be removed from the queue storing registered users. The screen reports data through interrupts. When an interrupt is detected, the data reported by the screen is read, the special character representing the data type in the data is extracted, the registration type of the previous application is queried. If there is a matching registration type, the data will be saved in the data storage area created for each screen, and all applications registered for this data type will be notified to read the data from the data buffer.

[0071] In this embodiment, a screen data transmission device is further provided. This device is used to implement the above-mentioned embodiment and preferred implementation manners, and those that have been described will not be repeated here. As used below, the term "module" can be a combination of software and / or hardware that can achieve a predetermined function. Although the device described in the following embodiments is preferably implemented in software, implementation in hardware, or a combination of software and hardware is also possible and contemplated.

[0072] This embodiment provides a screen data transmission device, as Figure 3 shown, including: an acquisition module 301, configured to acquire the screen type in the configuration file; a determination module 302, configured to determine the target data acquisition route of the screen data and determine the interrupt number corresponding to the target screen type from a plurality of preset transmission routes based on the screen type; a sending module 303, configured to send the screen data to each application in the target message queue according to the screen data type and the target screen type; wherein, the screen types and screen data types of each application in the target message queue are the same.

[0073] The further function descriptions of the above-mentioned modules and units are the same as those in the corresponding embodiments above, and will not be repeated here.

[0074] The transmission device of the screen data in this embodiment is presented in the form of functional units. Here, the functional units refer to ASIC (Application Specific Integrated Circuit) circuits, processors and memories that execute one or more software or fixed programs, and / or other devices that can provide the above functions.

[0075] An embodiment of the present invention further provides a computer device having the above Figure 3 shown screen data transmission device.

[0076] Please refer to Figure 4 , Figure 4 which is a schematic structural diagram of a computer device provided by an alternative embodiment of the present invention. As shown in Figure 4 , the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including a high-speed interface and a low-speed interface. Each component communicates with each other using different buses and can be installed on a common motherboard or installed in other ways as needed. The processor can process instructions executed within the computer device, including instructions stored in the memory or on the memory to display graphical information of the GUI on an external input / output device (such as a display device coupled to the interface). In some alternative embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (such as a server array, a set of blade servers, or a multi-processor system). Figure 4 In

[0077] one processor 10 is taken as an example.

[0078] The memory 20 stores instructions executable by at least one processor 10, so that at least one processor 10 executes the method shown in the above embodiment.

[0079] The memory 20 may include a program storage area and a data storage area. Among them, the program storage area can store an operating system and application programs required for at least one function; the data storage area can store data created according to the use of the computer device and the like. In addition, the memory 20 may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, a flash memory device, or other non-transitory solid-state storage devices. In some alternative embodiments, the memory 20 may optionally include a memory remotely provided with respect to the processor 10, and these remote memories can be connected to the computer device through a network. Examples of the above-mentioned network include but are not limited to the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0080] The memory 20 may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as flash memory, a hard disk, or a solid-state drive; the memory 20 may further include a combination of the above types of memory.

[0081] The computer device further includes a communication interface 30 for the computer device to communicate with other devices or a communication network.

[0082] An embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or be implemented as computer code that can be recorded on a storage medium, or be implemented as computer code originally stored in a remote storage medium or a non-transitory machine-readable storage medium and downloaded through a network and to be stored in a local storage medium, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only memory, a random access memory, a flash memory, a hard disk, or a solid-state drive, etc.; further, the storage medium may also include a combination of the above types of memory. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code, and when the software or computer code is accessed and executed by the computer, the processor, or the hardware, the method shown in the above embodiment is implemented.

[0083] A part of the present invention can be applied as a computer program product, such as computer program instructions, which, when executed by a computer, can call or provide the methods and / or technical solutions according to the present invention through the operations of the computer. Those skilled in the art should understand that the forms in which computer program instructions exist in a computer-readable medium include but are not limited to source files, executable files, installation package files, etc. Correspondingly, the ways in which computer program instructions are executed by a computer include but are not limited to: the computer directly executes the instructions, or the computer compiles the instructions and then executes the corresponding compiled program, or the computer reads and executes the instructions, or the computer reads and installs the instructions and then executes the corresponding installed program. Herein, the computer-readable medium can be any available computer-readable storage medium or communication medium accessible to the computer.

[0084] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art can make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations all fall within the scope defined by the appended claims.

Claims

1. A method for transmitting screen data, characterized in that: The method comprises: Get the target screen type in the configuration file; Determine a route for acquiring screen data corresponding to the target screen type from a plurality of preset transmission routes, and determine an interrupt number corresponding to the target screen type; Sending the screen data to each application in the target message queue according to the screen data type and the target screen type; wherein the target screen type and the screen data type of each application in the target message queue are the same; Determining a route for acquiring screen data corresponding to a target screen type from a plurality of preset transmission routes, and determining an interrupt number corresponding to the target screen type, including: Based on the target screen type, match the configuration file of each smart cockpit hardware in the vehicle; wherein the file content of the configuration file includes: screen type, iic bus, device address and interrupt number of the screen; determining a target profile of smart cockpit hardware having the target screen type from a plurality of screen types; Based on the target configuration file, determine the target screen interrupt number, the target iic bus and the device address of the target screen; Based on the target screen type, the target iic bus and the device address of the target screen, a target acquisition route of the screen data is determined.

2. The screen data transmission method according to claim 1, characterized in that: According to the screen data type and target screen type, the screen data is sent to each application in the target message queue, including: Acquire special characters corresponding to the screen data type from the target screen type; Based on the special characters, the screen data is transmitted to each application in the target message queue.

3. The screen data transmission method according to claim 1, characterized in that: The method further comprises: Acquire registration information of each application; wherein the registration information includes the screen type and screen data type corresponding to the application; Target applications with the same screen type and screen data type are grouped into the same message queue.

4. The screen data transmission method according to claim 3, characterized in that: The method further comprises: Get pulse information; Detecting whether the pulse information conforms to a preset pulse; If the pulse information matches the preset pulse, the target application corresponding to the pulse information is removed from the target message queue.

5. A screen data transmission device, characterized in that: The device comprises: The acquisition module is used to obtain the target screen type in the configuration file; A determination module, used to determine the acquisition route of the screen data corresponding to the target screen type from a plurality of preset transmission routes, and to determine the interrupt number corresponding to the screen type; A sending module, used for sending the screen data to each application in the target message queue according to the screen data type and the target screen type; wherein the screen type and the screen data type of each application in the target message queue are the same; The determination module is further used to match the configuration file of each smart cockpit hardware in the vehicle based on the target screen type; wherein the file content of the configuration file includes: screen type, iic bus, device address and interrupt number of the screen; determine the target configuration file of the smart cockpit hardware with the target screen type from multiple screen types; based on the target configuration file, determine the target screen interrupt number, target iic bus and device address of the target screen; based on the target screen type, target iic bus and device address of the target screen, determine the target acquisition route of the screen data.

6. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the screen data transmission method according to any one of claims 1 to 4 by executing the computer instructions.

7. A vehicle, characterized in that: It comprises a memory and a processor, the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the screen data transmission method according to any one of claims 1 to 4 by executing the computer instructions.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the screen data transmission method according to any one of claims 1 to 4.

9. A computer program product, characterized in that The method comprises computer instructions, wherein the computer instructions are used to cause a computer to execute the screen data transmission method according to any one of claims 1 to 4.

Images