Automobile instrument internal communication method and system

Abstract

The invention relates to an automobile instrument internal communication method and system, and the method comprises the following steps: after connection is established between an instrument MPU (Microprogrammed Control Unit) and an MCU (Microprogrammed Control Unit) through a heartbeat mechanism and a handshake process, required data are mutually sent in a whole-packet and circulating manner, and meanwhile, the heartbeat connection and the circulating handshake process are kept; the instrument MPU circularly sends a connection request to the vehicle-mounted information entertainment system, and after connection is established, required data are mutually sent in a whole-packet and circular mode; the interior of the instrument MPU adopts a circulating and whole-packet data sending mode for communication. According to the automobile instrument internal communication method provided by the invention, in the instrument internal communication process, the data is sent in a whole-packet and circulating manner, the data needing to be sent are summarized into one data packet, the whole data packet is sent in a circulating manner, and when the data is sent abnormally, the abnormally sent data can be updated in time by sending the data packet next time, so that the data transmission efficiency is improved. And data disorder and loss are avoided to a certain extent, and the possibility of instrument display errors is reduced.

Description

Technical Field

[0001] The present application relates to the field of automotive instruments, and in particular to an internal communication method and system for automotive instruments. Background Art

[0002] With the development of intelligent cockpits in vehicles, instrument cluster software has become more complex. The content required to be displayed has expanded from basic data such as speed, RPM, and mileage to include assisted driving data such as autonomous driving and ADAS. This shift requires higher security and reliability for instrument cluster software to ensure that it provides rich data without compromising driving safety.

[0003] Due to the instability of the communication process, communication software can malfunction, leading to data transmission anomalies. Current data communication technologies often rely on single data transmission. Each communication sends a single piece of data for the instrument display, and the process of transmitting all the required instrument data over multiple communications constitutes a communication cycle. If a data transmission error occurs during a communication, the instrument module corresponding to that data immediately displays the anomaly. However, the transmission process for the abnormal data cannot be restarted until the end of a communication cycle. This delay in timely processing can lead to instrument display errors, which in turn affects the driver's judgment and reduces driving safety. Summary of the Invention

[0004] In response to the above-mentioned problems existing in the current technology, the present application provides a method and system for internal communication of an automobile instrument, which solves the problem of untimely processing of abnormal data transmission in the internal communication of the instrument.

[0005] To achieve the above objectives, in a first aspect, the present application provides a method for internal communication of an automobile instrument, the method comprising:

[0006] After the instrument MPU and MCU establish a connection through the heartbeat mechanism and handshake process, they send the required data to each other in a whole packet and cyclic manner, while retaining the heartbeat connection and cyclic handshake process.

[0007] The instrument MPU sends a connection request to the in-vehicle infotainment system in a loop. After the connection is established, the required data is sent to each other in a whole packet and in a loop.

[0008] The instrument MPU communicates internally by sending data in a cyclic and complete packet manner.

[0009] Furthermore, in one embodiment, the instrument MPU cyclically sends a heartbeat and three-way handshake request to the MCU, including:

[0010] The instrument MPU sends heartbeat requests in a loop, and the MCU receives and responds to each request. The instrument MPU and MCU implement the handshake process in a loop, and the connection is successful after the three-way handshake is successfully completed.

[0011] Furthermore, in one embodiment, if the preset heartbeat response time is reached and the instrument MPU does not receive the MCU's response to the heartbeat request, or if the preset handshake request response time is reached and the instrument MPU or MCU does not receive the other party's response to the handshake request, it is considered that the connection is disconnected and the connection needs to be re-established.

[0012] Furthermore, in one embodiment, the instrument MPU cyclically sends a connection request to the in-vehicle infotainment system, including:

[0013] The instrument MPU sends connection requests in a loop, and the in-vehicle infotainment system receives and responds to each request. After the instrument MPU receives a response from the in-vehicle infotainment system, the connection between the instrument MPU and the in-vehicle infotainment system is successfully established.

[0014] If the preset connection request response time is reached and the instrument MPU does not receive a response to the connection request from the vehicle infotainment system, it is considered that the connection is disconnected and needs to be re-established.

[0015] Furthermore, in one embodiment, the instrument MPU and MCU send whole packets of data to each other in a loop, including: the MCU sends graphic display and audio playback data, and the instrument MPU sends function setting data.

[0016] The instrument MPU and the in-vehicle infotainment system send whole packets of data to each other in a loop, including: the in-vehicle infotainment system sends graphic display and audio playback data, and the instrument MPU sends control messages.

[0017] Furthermore, in one embodiment, the meter MPU includes a meter middleware module, a UI module, and an audio control module.

[0018] The UI module and audio control module respectively send connection requests to the instrument middleware module in a loop. The instrument middleware module receives and responds to each request. After the connection is established, the UI module and audio control module respectively send data subscription requests in a loop. The instrument middleware module marks the subscription data corresponding to each module, packages the subscription data separately, and sends the data packets to the corresponding modules in a loop.

[0019] Furthermore, in one embodiment, establishing the connection includes:

[0020] After the UI module and the audio control module respectively receive responses to the connection request from the instrument middleware module, the two modules respectively establish connections with the instrument middleware module successfully.

[0021] If the preset connection request response time is reached and the UI module or the audio control module does not receive a response to the connection request from the instrument middleware module, it is considered that the corresponding module connection is disconnected and needs to be re-established.

[0022] Furthermore, in one embodiment, before sending the data, the method further includes: compressing all the data in the data packet.

[0023] In a second aspect, based on the above-mentioned automobile instrument internal communication method, the present application provides an automobile instrument internal communication system, the system comprising:

[0024] The instrument MPU module is used to cyclically send connection establishment requests to the MCU and the in-vehicle infotainment system. After the connection is established, it is also used to send the required data to the MCU and the in-vehicle infotainment system in a complete and cyclic manner. It is also used to display graphics and play audio.

[0025] The MCU module is used to respond to the heartbeat and multiple handshake requests of the instrument MPU. It is also used to send the required data to the instrument MPU in a complete and cyclic manner after establishing a connection.

[0026] The in-vehicle infotainment system module is used to respond to the connection request from the instrument MPU; it is also used to send the required data to the instrument MPU in a complete and cyclic manner after the connection is established.

[0027] Furthermore, in one embodiment, the instrument MPU module includes:

[0028] The UI module is used to send connection requests to the instrument middleware module in a loop; after establishing a connection, it is also used to send data subscription requests to the instrument middleware module in a whole package and loop manner; and it is also used to display graphics.

[0029] The audio control module is used to send connection requests to the instrument middleware module in a loop; after establishing a connection, it is also used to send data subscription requests to the instrument middleware module in a whole packet and loop manner; and it is also used to play audio.

[0030] The instrument middleware module is used to respond to connection requests from the UI module and the audio control module. After the connection is established, it is also used to mark the subscription data of the UI module and the audio control module, and send the required data to the two modules in a complete and cyclic manner.

[0031] The beneficial effects of the technical solutions provided in the embodiments of the present application include:

[0032] This application sends data in a whole package and cyclic manner during the internal communication process of the instrument. The data to be sent is summarized into a data packet, and the entire data packet is sent cyclically. When data sending is abnormal, the abnormal sending data can be updated in time by sending the data packet next time, which can avoid data confusion and loss to a certain extent and reduce the possibility of instrument display errors. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 This is a flow chart of the internal communication method of the automobile instrument in an embodiment of the present application.

[0034] Figure 2 For this application Figure 1 Single-cycle communication flow chart of step S1 in FIG.

[0035] Figure 3 For this application Figure 1 Single-cycle communication flow chart of step S2 in FIG.

[0036] Figure 4 For this application Figure 1 The UI module single-cycle communication flow chart of step S3.

[0037] Figure 5 For this application Figure 1 The audio control module single cycle communication flow chart of step S3.

[0038] Figure 6 This is a block diagram of the internal communication system of the automobile instrument according to an embodiment of the present application.

[0039] Figure 7 This is a detailed block diagram of the internal communication system of the automobile instrument according to an embodiment of the present application. DETAILED DESCRIPTION

[0040] In order to enable those skilled in the art to better understand the present invention, the following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0041] In order to make the objectives, technical solutions and advantages of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0042] In a first aspect, an embodiment of the present application provides an internal communication method for an automobile instrument.

[0043] In one embodiment, see Figure 1 As shown, the above method includes:

[0044] In step S1, after the instrument MPU (Micro Processor Unit) and MCU (Micro Control Unit) establish a connection through the heartbeat mechanism and handshake process, they send required data to each other in a whole packet and cyclic manner, while retaining the heartbeat connection and cyclic handshake process.

[0045] Step S2: The instrument MPU cyclically sends a connection request to the vehicle infotainment system. After the connection is established, the required data is sent to each other in a whole packet and cyclic manner.

[0046] Step S3: The instrument MPU communicates internally by sending data in a cyclic manner and in whole packets.

[0047] The internal communication method of the automobile instrument provided by the present application sends data in a whole-packet and cyclic manner during the internal communication process of the instrument, aggregates the data to be sent into a data packet, and sends the entire data packet cyclically. When data sending is abnormal, the abnormally sent data can be updated in time by sending the data packet next time, thereby avoiding data confusion and loss to a certain extent and reducing the possibility of instrument display errors.

[0048] Generally, instrument processors are divided into MCU and MPU. The MPU is a multi-core chip that uses virtualization technology to divide 2 cores to run the Linux system of the instrument MPU and 4 cores to run the Android system of the in-vehicle infotainment system.

[0049] Furthermore, in one embodiment, the functions of the meter can be divided into three independently running operating systems:

[0050] System 1: The MCU is responsible for processing the vehicle body CAN (Controller Area Network) bus data, and sends the data to the instrument MPU through the serial port after logical processing, running the RTOS (Real-time Operating System) system.

[0051] System 2: The instrument MPU is mainly responsible for graphics display and sound playback, and runs an embedded Linux system internally.

[0052] System 3: The in-vehicle infotainment system communicates with the instrument panel MPU through inter-core communication. It is mainly responsible for sending information from the in-vehicle infotainment system to the instrument panel for graphic display and audio playback, and runs the Android system.

[0053] Furthermore, in one embodiment, corresponding to the steps in the above embodiment, the internal communication method of the automobile instrument may include three communication paths:

[0054] Path 1: MCU communicates with the instrument MPU through the serial port.

[0055] Path 2: The in-vehicle infotainment system communicates with the instrument MPU through inter-core communication.

[0056] Path 3: Communication within the cluster MPU. The cluster MPU includes the cluster middleware (Cluster Middleware) module, the UI (User Interface) module, and the audio control (Audio Control) module. Sockets are used for communication between the cluster middleware module and the UI module, and between the cluster middleware module and the audio control module. The cluster middleware module communicates with the MCU outside the cluster MPU and the in-vehicle infotainment system.

[0057] Furthermore, in one embodiment, the above step S1 includes:

[0058] The instrument MPU sends heartbeat requests in a loop, and the MCU receives and responds to each request; the instrument MPU and MCU implement the handshake process in a loop, and the connection is successful after a three-way handshake is successfully completed; the MCU sends graphic display and audio playback data to the instrument MPU, and the instrument MPU sends function setting data to the MCU.

[0059] See also Figure 2 As shown, a specific embodiment of successfully establishing a connection in step S1 is provided, including the following steps:

[0060] S11. The instrument MPU sends a heartbeat request to the MCU.

[0061] S12. After receiving the heartbeat request, the MCU sends a heartbeat response to the instrument MPU. After the instrument MPU receives the heartbeat response, a heartbeat interaction is completed.

[0062] S13. The instrument MPU sends a first handshake request to the MCU to implement the first handshake.

[0063] S14. After receiving the first handshake request, the MCU sends a response to the first handshake request and a second handshake request to the instrument MPU to implement the second handshake.

[0064] S15. After receiving the response to the first handshake request and the second handshake request, the instrument MPU sends a response to the second handshake request to the MCU, completing the three-way handshake process.

[0065] S16. MCU sends graphic display and audio playback data to the instrument MPU.

[0066] S17. The instrument MPU sends function setting data to the MCU.

[0067] Based on this embodiment, if the preset heartbeat response time is reached and the instrument MPU does not receive the MCU's response to the heartbeat request, or if the preset handshake request response time is reached and the instrument MPU or MCU does not receive the other party's response to the handshake request, it is considered that the connection is disconnected and the connection needs to be re-established.

[0068] Based on this embodiment, the instrument MPU sends heartbeat requests in a loop. If the instrument MPU does not detect a heartbeat response from the MCU for a long time, or the MCU detects a missing heartbeat, it means that a communication failure has occurred, and the failure can be eliminated by restarting. Due to the cyclic sending of heartbeat requests, even if the MCU does not work normally for a period of time, as long as it resumes normal operation, it can receive the heartbeat request sent by the instrument MPU and enter the handshake process in time; similarly, after the instrument MPU malfunctions and then resumes normal operation, no matter what state the MCU is in, the instrument MPU will send a heartbeat request to trigger the handshake process and improve the efficiency of restoring the connection. Similarly, the handshake process can be seen in a loop. When the heartbeat process is completed, it will enter the handshake process in time. In addition, the entire packet of data is sent cyclically between the MCU and the instrument MPU. When a certain content data is disordered during transmission, the subsequent data will be able to be corrected quickly.

[0069] Furthermore, in one embodiment, the above step S2 includes:

[0070] The instrument MPU sends connection requests in a loop, and the in-vehicle infotainment system receives and responds to each request. After the instrument MPU receives a response from the in-vehicle infotainment system, the instrument MPU and the in-vehicle infotainment system are successfully connected. If the preset connection request response time is reached and the instrument MPU does not receive a response from the in-vehicle infotainment system to the connection request, it is considered that the connection is disconnected and needs to be re-established.

[0071] Based on this embodiment, step S2 also includes: the vehicle infotainment system sends graphic display and audio playback data to the instrument MPU, and the instrument MPU sends a control message to the vehicle infotainment system. Figure 3 As shown, the steps include:

[0072] S21. The instrument MPU sends a connection request to the in-vehicle infotainment system.

[0073] S22. After receiving the connection request, the in-vehicle infotainment system sends an online response to the instrument MPU. After the instrument MPU receives the online response, the connection is successfully established.

[0074] S23. The instrument MPU sends control information to the in-vehicle infotainment system.

[0075] S24. The in-vehicle infotainment system sends graphic display and audio playback data to the instrument MPU.

[0076] Based on this embodiment, by cyclically sending connection requests, when the instrument MPU and the in-vehicle infotainment system malfunction and cause the connection to be interrupted, as long as the faulty party resumes work, the connection can be restored in time and data sending can be started; and because the entire package of data is sent cyclically, when the data sending is disordered, the connection can be restored in time, the data can be updated in time, and the instrument display can be normal.

[0077] Furthermore, in one embodiment, in the above step S3, the instrument MPU includes an instrument middleware module, a UI module and an audio control module. The UI module and the audio control module respectively send connection requests to the instrument middleware module in a loop. The instrument middleware module receives and responds to each request. After the connection is established, the UI module and the audio control module respectively send data subscription requests in a loop. The instrument middleware module marks the subscription data corresponding to each module, packages the subscription data separately, and sends the data packets to the corresponding modules in a loop.

[0078] See also Figure 4 As shown, a specific embodiment of successfully establishing a connection between the UI module and the instrument middleware module in step S3 is provided, including the following steps:

[0079] S311. The UI module sends a connection request to the instrument middleware module.

[0080] S312: After receiving the connection request, the instrument middleware module sends an online response to the UI module. After receiving the online response, the UI module establishes a successful connection.

[0081] S313. The UI module sends a data subscription request to the instrument middleware module.

[0082] S314 , after receiving the data subscription request, the instrument middleware module marks the corresponding subscription data, packages the subscription data, and cyclically sends the subscription data packet to the UI module.

[0083] See also Figure 5 As shown, a specific embodiment of successfully establishing a connection between the audio control module and the instrument middleware module in step S3 is provided, including the following steps:

[0084] S321. The audio control module sends a connection request to the instrument middleware module.

[0085] S322: After receiving the connection request, the instrument middleware module sends an online response to the audio control module. After receiving the online response, the audio control module establishes a successful connection.

[0086] S323: The audio control module sends a data subscription request to the instrument middleware module.

[0087] S324 , after receiving the data subscription request, the meter middleware module marks the corresponding subscription data, packages the subscription data, and cyclically sends the subscription data packet to the audio control module.

[0088] Based on this embodiment, after the UI module and the audio control module respectively receive the response of the instrument middleware module to the connection request, the two modules respectively establish a connection with the instrument middleware module successfully; if the preset connection request response time is reached and the UI module or the audio control module does not receive a response to the connection request from the instrument middleware module, it is deemed that the connection between the corresponding module and the instrument middleware module is disconnected and the connection needs to be re-established.

[0089] Based on this embodiment, by cyclically sending connection requests, the connection can be restored in time when a failure occurs in the instrument intermediate module, UI module and audio control module inside the instrument MPU, or when a module restarts and causes a connection interruption; and because the entire package of data is sent cyclically, it can ensure that the abnormally sent data is restored to a normal state, so that the instrument can be displayed normally.

[0090] Furthermore, in one embodiment, before sending data, the system also includes compressing all data within the data packet, allocating only the maximum number of bits required to store the data, ensuring that each transmitted data occupies the minimum data bandwidth, thereby saving CPU load and memory. This transmitted data includes graphic display and audio playback data sent by the MCU, function setting data sent by the instrument cluster MPU; graphic display and audio playback data sent by the in-vehicle infotainment system, control messages sent by the instrument cluster MPU; data subscription requests sent by the UI module and audio control module, and subscription data sent by the instrument cluster middleware module; all of this data is sent in complete packets.

[0091] In a second aspect, based on the above-mentioned embodiment of the automobile instrument internal communication method, the present application provides an embodiment of an automobile instrument internal communication system.

[0092] See also Figure 6 As shown, the above system includes an instrument MPU module, an MCU module, and an in-vehicle infotainment system module, among which:

[0093] The instrument MPU module is used to cyclically send connection establishment requests to the MCU and the in-vehicle infotainment system. After the connection is established, it is also used to send the required data to the MCU and the in-vehicle infotainment system in a complete and cyclic manner. It is also used to display graphics and play audio.

[0094] The MCU module is used to respond to the heartbeat and multiple handshake requests of the instrument MPU. It is also used to send the required data to the instrument MPU in a complete and cyclic manner after establishing a connection.

[0095] The in-vehicle infotainment system module is used to respond to the connection request from the instrument MPU; it is also used to send the required data to the instrument MPU in a complete and cyclic manner after the connection is established.

[0096] Further, in one embodiment, see Figure 7 As shown, the instrument MPU module includes a UI module, an audio control module, and an instrument middleware module. The instrument middleware module is used to communicate with the MCU module and the in-vehicle infotainment system module externally, and is used to communicate with the UI module and the audio control module internally. Specifically:

[0097] The UI module is used to send connection requests to the instrument middleware module in a loop; after establishing a connection, it is also used to send data subscription requests to the instrument middleware module in a whole package and loop manner; and it is also used to display graphics.

[0098] The audio control module is used to send connection requests to the instrument middleware module in a loop; after establishing a connection, it is also used to send data subscription requests to the instrument middleware module in a whole packet and loop manner; and it is also used to play audio.

[0099] The instrument middleware module is used to respond to connection requests from the UI module and the audio control module. After the connection is established, it is also used to mark the subscription data of the UI module and the audio control module, and send the required data to the two modules in a complete and cyclic manner.

[0100] It should be noted that the serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0101] The terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices. The terms "first", "second" and "third" are used to distinguish different objects, etc., and do not represent a sequence, nor do they limit the "first", "second" and "third" to different types.

[0102] In the description of the embodiments of this application, the words "exemplary," "for example," or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary," "for example," or "for example" in the embodiments of this application should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary," "for example," or "for example" is intended to present the relevant concepts in a concrete manner.

[0103] In the description of the embodiments of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in the text is merely a description of the association relationship of associated objects, indicating that three relationships may exist, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, "multiple times" means twice or more than twice.

[0104] In some processes described in the embodiments of the present application, multiple operations or steps are included that appear in a specific order. However, it should be understood that these operations or steps may not be performed in the order in which they appear in the embodiments of the present application or may be performed in parallel. The sequence numbers of the operations are only used to distinguish between different operations, and the sequence numbers themselves do not represent any order of execution. In addition, these processes may include more or fewer operations, and these operations or steps may be performed in sequence or in parallel, and these operations or steps may be combined.

[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 the necessary general hardware platform, of course, it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this 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 software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes a number of instructions for enabling a terminal device to execute the methods described in each embodiment of the present application.

[0106] The above are only preferred embodiments of the present application and do not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A method for internal communication of automobile instruments, characterized in that: The method comprises: After the instrument MPU and MCU establish a connection through the heartbeat mechanism and handshake process, they send the required data to each other in a whole packet and cyclic manner, while retaining the heartbeat connection and cyclic handshake process; The instrument panel MPU sends a connection request to the vehicle infotainment system in a loop. After the connection is established, the required data is sent to each other in a whole packet and in a loop. The instrument MPU communicates internally by sending data in a cyclic manner and in whole packets.

2. The method for internal communication of automobile instruments according to claim 1, characterized in that: The instrument MPU sends a heartbeat and three-way handshake request to the MCU in a loop, including: The instrument MPU sends heartbeat requests in a loop, and the MCU receives and responds to each request; the instrument MPU and MCU implement the handshake process in a loop, and the connection is successful after the three-way handshake is successfully completed.

3. The method for internal communication of automobile instruments as claimed in claim 2, characterized in that: If the preset heartbeat response time is reached and the instrument MPU does not receive the MCU's response to the heartbeat request, or if the preset handshake request response time is reached and the instrument MPU or MCU does not receive the other party's response to the handshake request, the connection is considered disconnected and needs to be reestablished.

4. The method for internal communication of automobile instruments according to claim 1, characterized in that: The instrument MPU cyclically sends a connection request to the in-vehicle infotainment system, including: The instrument MPU sends connection requests cyclically, and the in-vehicle infotainment system receives and responds to each request. After the instrument MPU receives a response from the in-vehicle infotainment system, the instrument MPU and the in-vehicle infotainment system are successfully connected. If the preset connection request response time is reached and the instrument MPU does not receive a response to the connection request from the vehicle infotainment system, it is considered that the connection is disconnected and needs to be re-established.

5. The method for internal communication of automobile instruments as claimed in claim 1, characterized in that: The instrument MPU and MCU send whole packets of data to each other in a loop, including: MCU sends graphic display and audio playback data, and the instrument MPU sends function setting data; The instrument MPU and the in-vehicle infotainment system send whole packets of data to each other in a loop, including: the in-vehicle infotainment system sends graphic display and audio playback data, and the instrument MPU sends control messages.

6. The method for internal communication of automobile instruments as claimed in claim 1, characterized in that: The instrument MPU includes an instrument middleware module, a UI module and an audio control module; The UI module and the audio control module respectively send connection requests to the instrument middleware module in a loop. The instrument middleware module receives and responds to each request. After the connection is established, the UI module and the audio control module respectively send data subscription requests in a loop. The instrument middleware module marks the subscription data corresponding to each module, packages the subscription data separately, and sends the data packets to the corresponding modules in a loop.

7. The method for internal communication of automobile instruments as claimed in claim 6, characterized in that: The establishing of the connection comprises: After the UI module and the audio control module receive responses to the connection request from the instrument middleware module, the two modules successfully establish connections with the instrument middleware module; If the preset connection request response time is reached and the UI module or the audio control module does not receive a response to the connection request from the instrument middleware module, it is considered that the corresponding module connection is disconnected and needs to be re-established.

8. The method for internal communication of automobile instruments as claimed in claim 1, characterized in that: Before sending the data, the process also includes: compressing all the data in the data packet.

9. A communication system based on the internal communication method of automobile instrument according to any one of claims 1 to 8, characterized in that: The system comprises: The instrument panel MPU module is used to send connection establishment requests to the MCU and the in-vehicle infotainment system in a loop. It is also used to send the required data to the MCU and the in-vehicle infotainment system in a whole packet and loop after the connection is established. It is also used to display graphics and play audio. The MCU module is used to respond to the heartbeat and multiple handshake requests of the instrument MPU; it is also used to send the required data to the instrument MPU in a whole packet and cyclic manner after the connection is established; The in-vehicle infotainment system module is used to respond to the connection request of the instrument MPU; it is also used to send the required data to the instrument MPU in a whole packet and cyclic manner after the connection is established.

10. The communication system according to claim 9, characterized in that The instrument MPU module includes: The UI module is used to send connection requests to the instrument middleware module in a loop; after establishing the connection, it is also used to send data subscription requests to the instrument middleware module in a whole packet and loop manner; it is also used to display graphics; The audio control module is used to send a connection request to the instrument middleware module in a loop; after the connection is established, it sends a data subscription request to the instrument middleware module in a whole packet and in a loop; it is also used to play audio; The instrument middleware module is used to respond to the connection requests of the UI module and the audio control module; it is also used to mark the subscription data of the UI module and the audio control module after the connection is established, and send the required data to the two modules in a whole package and loop manner.

Images