Data interaction methods and systems between the speedometer and the vehicle's infotainment system
By classifying and prioritizing vehicle data on the vehicle-mounted system side, and adopting a highly adaptable encapsulation and transmission strategy, the problem of diverse data transmission needs between smart speedometers and vehicle-mounted systems is solved, achieving efficient compatibility in data transmission.
Patent Information
- Application Number
- CN202611336004.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-31
- Publication Date
- 2026-11-17
AI Technical Summary
In existing technologies, cellular network synchronization and Bluetooth Low Energy technologies cannot simultaneously meet the diverse needs of smart speedometers and vehicle systems for various types of data, such as low latency, high bandwidth, and low power consumption.
By classifying vehicle data by type on the vehicle-mounted system, determining target priorities based on business type, and adopting highly adaptable encapsulation and transmission strategies, targeted encapsulation and transmission can be achieved.
It can accommodate the transmission needs of different types of data on the same communication link, ensure the real-time performance of critical signals, and make full use of available bandwidth to transmit large volumes of resource data.
Smart Images

Figure CN123123846A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of vehicle testing technology, and in particular to a method and system for data interaction between a speedometer and a vehicle-mounted system. Background Technology
[0002] Smart speedometers, as small intelligent display terminals installed in vehicles to display vehicle operating status and interactive effects, need to acquire various types of data in real time from the vehicle's infotainment system, including vehicle speed, gear position, music status, album art, theme resources, facial expression trigger commands, and firmware upgrade data. Different types of data have different transmission requirements; for example, driving-related data requires low-latency synchronization, while emotional interactive content data requires high bandwidth support. Current technologies typically use cellular network synchronization and Bluetooth Low Energy (BLE) technology to connect the speedometer to the vehicle's infotainment system. However, cellular network synchronization relies on multi-hop links, resulting in significant latency. BLE direct connection solutions have limited effective throughput, making it difficult to support large data sets such as album art and firmware packages, and their concurrency scheduling capabilities are insufficient. Therefore, existing connection and communication methods cannot simultaneously meet the diverse needs of various data types, such as low latency, high bandwidth, and low power consumption. Summary of the Invention
[0003] This invention provides a data interaction method and system between a codebook and a vehicle-mounted system, which addresses the technical problem in related technologies where the current communication method cannot meet the diverse needs corresponding to multiple data types due to the large number of service types of vehicle-mounted system data.
[0004] In a first aspect, embodiments of the present invention provide a data interaction method between a code reader and a vehicle infotainment system, applied to a vehicle infotainment system, the method comprising: If a communication channel has been established with the target code table, acquire the vehicle data to be transmitted to the target code table; A target priority is determined based on the service type of the vehicle data, and the target priority is associated with a preset target encapsulation strategy and a target transmission strategy. The vehicle data is encapsulated according to the target encapsulation strategy and the preset message format, and the encapsulated message is used as the target message. According to the target transmission strategy, the target message is transmitted to the target code table.
[0005] Secondly, embodiments of the present invention provide a data interaction method between a codebook and a vehicle-mounted system, applied to a target codebook, the method comprising: If a communication channel has been established with the vehicle's infotainment system, the target message from the vehicle's infotainment system will be received. Parse the target message and display the vehicle data included in the target message.
[0006] Thirdly, embodiments of the present invention provide a data interaction system, the system comprising: The vehicle-mounted unit (V2U) is used to acquire vehicle data to be transmitted to the target code table when a communication channel has been established with the target code table; determine the target priority based on the service type of the vehicle data, wherein the target priority is associated with a preset target encapsulation strategy and a target transmission strategy; encapsulate the vehicle data according to the target encapsulation strategy and a preset message format, and use the encapsulated message as the target message; and transmit the target message to the target code table according to the target transmission strategy. The target code table is used to receive target messages from the vehicle's infotainment system when a communication channel has been established; to parse the target messages and display the vehicle data included in the target messages.
[0007] This invention provides a data interaction method between a vehicle code table and a vehicle-mounted system. Applied to a vehicle-mounted system, the method involves acquiring vehicle data to be transmitted to a target code table after a communication channel has been established. A target priority is determined based on the service type of the vehicle data, and this target priority is associated with a preset target encapsulation strategy and a target transmission strategy. The vehicle data is encapsulated according to the target encapsulation strategy and a preset message format, and the encapsulated message is used as the target message. The target message is then transmitted to the target code table according to the target transmission strategy. By pre-classifying the vehicle data by type and matching the corresponding target encapsulation strategy and target transmission strategy according to the characteristics of each type of vehicle data, the method allows for targeted encapsulation and transmission of different types of vehicle data according to highly adaptable paths and protocols. This addresses, to some extent, the technical problem in related technologies where the current communication method cannot meet the diverse needs of multiple data types due to the large number of service types in vehicle-mounted system data. Attached Figure Description
[0008] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0009] Figure 1 This invention illustrates the concept of a data interaction system provided by some embodiments of the present invention; Figure 2 The flowchart of the data interaction method between the code table and the vehicle system provided in some embodiments of the present invention is shown; Figure 3 The interactive timing of establishing a communication channel between the vehicle-mounted system and the target code table is shown in some embodiments of the present invention; Figure 4The field arrangement of a preset message format provided by some embodiments of the present invention is illustrated; Figure 5 This illustrates a concept for prioritizing objectives provided by some embodiments of the present invention; Figure 6 The flowchart of the data interaction method between the codebook and the vehicle system provided in some other embodiments of the present invention is shown; Figure 7 This invention illustrates the concept of a data interaction system provided by some embodiments of the present invention; Figure 8 This invention illustrates a transmission concept for transmitting vehicle data to a target code table, as provided in some embodiments of the present invention. Figure 9 The present invention illustrates the transmission process of third-class vehicle data provided in some embodiments; Figure 10 The present invention illustrates the transmission process of fourth type vehicle data provided by some embodiments of the present invention. Detailed Implementation
[0010] As described in the background section, smart speedometers, as small intelligent display terminals installed in vehicles to display vehicle operating status and interactive effects, need to acquire various types of data in real time from the vehicle's infotainment system, including vehicle speed, gear position, music status, album art, theme resources, facial expression trigger commands, and firmware upgrade data. Different types of vehicle data have different transmission requirements; for example, driving-related data requires low-latency synchronization, while emotional interactive content data requires high bandwidth support. Existing technologies typically use cellular network synchronization and Bluetooth Low Energy (BLE) technology to connect the speedometer to the vehicle's infotainment system. However, cellular network synchronization relies on multi-hop links, resulting in significant latency. BLE direct connection solutions have limited effective throughput, making it difficult to support large data sets such as album art and firmware packages, and their concurrency scheduling capabilities are insufficient. Therefore, existing connection and communication methods cannot simultaneously meet the diverse needs of various data types, such as low latency, high bandwidth, and low power consumption.
[0011] This invention provides a data interaction method between a vehicle code table and a vehicle-mounted system. Applied to a vehicle-mounted system, the method involves acquiring vehicle data to be transmitted to a target code table after a communication channel has been established. A target priority is determined based on the service type of the vehicle data, and this target priority is associated with a preset target encapsulation strategy and a target transmission strategy. The vehicle data is encapsulated according to the target encapsulation strategy and a preset message format, and the encapsulated message is used as the target message. The target message is then transmitted to the target code table according to the target transmission strategy. By pre-classifying the vehicle data by type and matching the corresponding target encapsulation strategy and target transmission strategy according to the characteristics of each type of vehicle data, the method allows for targeted encapsulation and transmission of different types of vehicle data according to highly adaptable paths and protocols. This addresses, to some extent, the technical problem in related technologies where the current communication method cannot meet the diverse needs of multiple data types due to the large number of service types in vehicle-mounted system data.
[0012] The technical solution of the present invention and how the technical solution of the present invention solves the above-mentioned technical problems will be described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of the present invention will now be described with reference to the accompanying drawings.
[0013] Before understanding the data interaction method between the codebook and the vehicle system provided in the embodiments of the present invention, it is necessary to understand that, Figure 1 The present invention illustrates the concept of a data interaction system provided by some embodiments thereof. Figure 1 As shown, the data interaction system includes an application layer, a signal layer, an access layer, and a terminal layer. The application layer, signal layer, and access layer are all located on the vehicle's infotainment system side, while the terminal layer is located on the vehicle's speedometer side.
[0014] Specifically, the signal layer resides within the vehicle infotainment system (e.g., Android), including the CarService module responsible for receiving vehicle signal callbacks. The CarService module receives various raw basic signals from the vehicle bus, such as sensor readings, switch statuses, and control command feedback. These contact signals are identified by the CommandHelper module according to service type and routed to the corresponding Consumer modules. Consumer modules are processing units categorized by service, covering energy consumption, driving, vehicle control, system, and entertainment categories. For example, energy consumption modules handle charging status, battery percentage, remaining range, mileage, and fuel / electricity consumption; driving modules handle vehicle speed, gear position, intelligent driving status, navigation speed limits, and navigation start / stop; vehicle control modules handle door, window, sunroof, door locks, child locks, air conditioning, fragrance, seats, ambient lighting, and temperature; system modules are responsible for time synchronization updates; and entertainment modules aggregate the status of applications such as music, video, radio, karaoke, and games. Each consumer module can transform the basic signals under its jurisdiction into structured vehicle data that can be transmitted and displayed through internal logic operations and format conversion, and then write the vehicle data into the access layer through an interface (e.g., by calling Native methods through FunctionControl).
[0015] The access layer includes a Bluetooth Low Energy (BLE) configuration module, a hotspot management module, a JNI module, a communication module, and a state machine. The BLE configuration module enables Bluetooth communication between the vehicle's infotainment system and the terminal-side codebook, implemented by the Bluetooth Low Energy Configuration Manager (BleProvisionManager) and its interface (BleProvisionProvider). The hotspot management module reads hotspot information (Service Set Identifier, SSID) and password from the vehicle's infotainment system configuration (e.g., Soft AP) and configures the hotspot information as configuration content in the format "Wireless Network Name|Password|5G," which can be implemented by the Hotspot Manager (HotspotManager). The JNI module enables data transmission between Java and other programming languages. The communication module sends encapsulated vehicle data to the terminal-side codebook, typically including the Transfer Control Protocol (TCP), and can be implemented by related plugins (e.g., NativeSmallSocket). The state machine is used to monitor whether the state of the target code table is normal during the data transmission process between the vehicle's infotainment system and the target code table.
[0016] The application layer runs on the vehicle's infotainment system, providing users with entry points for adding and removing speedometers, theme settings, brightness settings, emoji on / off, wallpaper component configuration, firmware upgrades, and connection status display. The application layer does not directly handle the underlying binary protocol; instead, it indirectly calls the access layer through business modules (such as FunctionControl, ThemeCmd, and ExpressionCmd).
[0017] The terminal layer is the smart speedometer end, which includes a communication driver (WiFi client) module, a protocol parsing module, a user interface (UI) rendering module, and an upgrade / reset module. The communication driver module receives vehicle data from the access layer's communication module. The protocol parsing module parses the vehicle data. The UI rendering module renders resources such as energy consumption, compass, clock, vehicle speed, music, interactive emoticons, and wallpaper themes. The upgrade / reset module performs version maintenance using various upgrade technologies, such as local offline upgrades (SD Card Upgrade) and remote wireless upgrades (Over-The-Air Technology, OTA).
[0018] In an embodiment of the present invention, Figure 2 The flowchart illustrates the data interaction method between the codebook and the vehicle-mounted system provided in some embodiments of the present invention. For example... Figure 2 The data interaction method between the codebook and the vehicle infotainment system provided in the illustrated embodiment of the present invention can be executed by the vehicle infotainment system. The vehicle infotainment system can be an in-vehicle infotainment and cockpit domain control system installed in the vehicle, belonging to the cockpit domain. It can interact and coordinate with the powertrain domain (including the vehicle control unit, VCU), chassis domain, and autonomous driving domain via in-vehicle Ethernet and Controller Area Network (CAN) bus. The vehicle infotainment system typically includes, for example,... Figure 1 The diagram shows the application layer, signal layer, and access layer. Specifically, as shown... Figure 2 The data interaction method between the speedometer and the vehicle's infotainment system shown includes steps 210 to 240.
[0019] Step 210: If a communication channel has been established with the target code table, acquire the vehicle data to be transmitted to the target code table.
[0020] In this embodiment of the invention, the target codebook can be a codebook installed in the vehicle and capable of data interaction with the vehicle's infotainment system. The communication channel refers to the logical path established between the vehicle's access layer and the target codebook for data transmission, which can be implemented using a hotspot module in the access layer, a BLE module, or other wireless transmission media. The establishment of a communication channel between the target codebook and the vehicle's infotainment system indicates that the vehicle's infotainment system is aware that the target codebook has receiving capabilities, and subsequent vehicle data can be pushed to the other end. Vehicle data refers to the vehicle's operating status or interactive data displayed on the target codebook, such as vehicle speed, gear position, battery level, range, energy consumption, intelligent driving status, navigation speed limit, time, weather, music status, album art, theme resources, facial animation trigger commands, and firmware upgrade data, among other types of data, typically obtained after preliminary conversion by various consumer modules in the signal layer.
[0021] Step 220: Determine the target priority based on the service type of the vehicle data. The target priority is associated with a preset target encapsulation strategy and target transmission strategy.
[0022] In this embodiment of the invention, the target priority is used to index the pre-configured target encapsulation strategy and target transmission strategy, reflecting the importance of vehicle data in this transmission process. The target encapsulation strategy may include processing rules for vehicle data when encapsulating it into packets, such as data organization methods, compression, fragmentation, and format conversion. The target transmission strategy may include the scheduling priority of data during transmission. Since different types of vehicle data have significantly different requirements for transmission latency, bandwidth usage, and reliability—for example, driving signals such as vehicle speed and gear position require extremely low latency, multimedia data such as album art and theme resources require high bandwidth, while firmware upgrade data focuses more on transmission integrity—a clear mapping relationship needs to be established between the service type of vehicle data and the transmission strategy. The target priority serves as the index identifier for this mapping relationship, enabling subsequent encapsulation and transmission stages to execute differentiated processing logic based on priority levels.
[0023] Step 230: Encapsulate the vehicle data according to the target encapsulation strategy and the preset message format, and use the encapsulated message as the target message.
[0024] In this embodiment of the invention, the preset message format is a binary protocol structure, typically including a message header, a content field, and a checksum field. The message header usually includes basic information such as message length. The content field typically carries the data payload processed by the target encapsulation strategy. The checksum field is used by the target code table to verify the integrity and correctness of the message. Based on the target encapsulation strategy corresponding to the target priority, the compression degree of vehicle data of different service types varies in the content field. For example, high-frequency driving signals use a fixed-length field to reduce parsing overhead, while multimedia resources use fragmented encapsulation to adapt to the transmission window.
[0025] Step 240: Transmit the target message to the target code table according to the target transmission strategy.
[0026] In this embodiment of the invention, the target transmission strategy may include the scheduling priority of the target message during the transmission of the target message to the target code table through the communication channel. The high-priority target message can occupy the transmission bandwidth first to ensure that driving safety data can still be delivered in a timely manner during channel congestion or large data transmission. The low-priority command is sent in the idle time slot and can tolerate a large transmission delay.
[0027] In this embodiment of the invention, vehicle data is pre-classified by type, and corresponding target encapsulation and target transmission strategies are matched according to the characteristics of each type of vehicle data. This allows each type of vehicle data to be encapsulated and transmitted in a targeted manner according to highly adaptable paths and protocols. Through the above-mentioned mechanism of differentiated encapsulation by type and hierarchical scheduling by priority, the vehicle-mounted system can take into account the transmission needs of different types of data on the same communication link, which not only ensures the real-time performance of key signals, but also makes full use of available bandwidth to transmit large-volume resource data.
[0028] In this embodiment of the invention, before obtaining the vehicle data to be transmitted to the target code table in step 210, the method further includes establishing a communication channel between the vehicle unit and the target code table. Figure 3 The following are some embodiments of the present invention illustrating the interaction timing of establishing a communication channel between the vehicle-mounted system and the target code table. Figure 3 As shown, the process of establishing a communication channel between the vehicle's infotainment system and the target code table typically includes the following steps: First, in response to an add request, the system scans for Bluetooth devices within the target range of the vehicle's infotainment system, including the target code table. If the target code table exists within the target range, a network configuration channel is established between the vehicle's infotainment system and the target code table. The vehicle's hotspot information is transmitted to the target code table through the network configuration channel, enabling the target code table to initiate a hotspot access request based on the hotspot information. In response to the hotspot access request from the target code table, the system accesses the target code table. Second, the system listens for and receives communication connection requests from the target code table through a preset communication port, and in response to the communication connection requests, establishes a communication channel with the target code table.
[0029] Specifically, in the first stage, after the user triggers the addition of a device in the application layer of the vehicle's infotainment system, the state machine on the vehicle's side records that the system has entered a pairing state and instructs the BLE network configuration module of the access layer to start the scanning and connection process, scanning for Bluetooth devices within the target range of the vehicle's infotainment system. These Bluetooth devices include the target code table. If the target code table exists within the target range, a network configuration channel is established between the target code table and the target code table. During the network configuration process, the hotspot module of the vehicle's access layer sends the SSID, password, and frequency band information of the vehicle's hotspot to the code table via the network configuration channel using credentials. After receiving the credentials, the code table saves them and initiates a hotspot access request, attempting to connect to the vehicle's hotspot. This stage solves the problem of the code table not being able to manually input the hotspot password, while also preventing the hotspot password from being exposed in plaintext to the user's operation process. In response to the hotspot access request from the target code table, the target code table is connected to the vehicle's hotspot management network. The second stage is the communication stage. After the codebook connects to the vehicle's hotspot, it actively connects to the communication module of the vehicle's access layer and sends a communication connection request to the vehicle. The vehicle listens for and receives the communication connection request from the target codebook through a preset communication port, and responds to the request to establish a communication channel with the target codebook. Specifically, the vehicle side sets a connection status callback through the native layer of the JNI module, and then starts listening on TCP port 8099 on all available network interfaces of the communication module to receive access from the target codebook. Regarding connection parameters, the vehicle side is configured with relevant attributes to keep active (e.g., TCP keepalive) to maintain the validity of long connections, disables the Nagle algorithm to reduce the transmission latency of small data packets, and sets the communication module to non-blocking mode to improve concurrent processing capabilities. In the current transmission, the vehicle side acts as the server, and the target codebook acts as the client initiating the connection. The vehicle side maintains only one active connection at a time, meaning it communicates with only one codebook (i.e., the target codebook) at any given time. The state machine updates the connection status between the vehicle and the target codebook from "pairing" to "paired".
[0030] In this embodiment of the invention, after the target code table establishes a communication channel with the vehicle's infotainment system, the native layer of the JNI module notifies the Java layer of the JNI module of the target code table's identification information (e.g., IP address) and connection port via a callback. This allows the Java layer to notify the state machine via a specific port value when it detects a connection anomaly or heartbeat timeout. For example, port 9999 indicates a disconnected communication socket, and port 8888 indicates that the target code table has entered an upgrade state. The Unified State Manager in the state machine abstracts the connection process into five states: idle, pairing, paired, abnormal, and upgrading. It then drives the transitions between these states based on events such as pairing start, Bluetooth scan timeout, hotspot switch switching, socket establishment or failure, firmware upgrade (OTA) trigger, upgrade completion, and device removal.
[0031] In this embodiment of the invention, the vehicle-mounted system and the target codebook use a lightweight binary command protocol for data transmission in the communication channel. Figure 4 The present invention illustrates the field arrangement of a preset message format provided in some embodiments, such as... Figure 4As shown, the preset message format includes at least a message header and a content field payload, and may also include a CRC16 checksum. The content field payload carries the vehicle data, and the payload is interpreted as the corresponding data structure according to the type field. A two-byte cyclic redundancy check value is appended to the end of the message as a checksum, and the checksum covers the message header and content field. The current maximum message length is 1024 bytes, of which the message header occupies a fixed 8 bytes, the checksum field occupies 2 bytes, and therefore the content field is approximately 1014 bytes at most. Compared to general text-based protocols such as Hypertext Transfer Protocol and JavaScript Object Notation, this binary message structure significantly compresses header overhead and field name redundancy, making it particularly suitable for the rapid transmission of high-frequency small data packets such as vehicle speed, gear position, time, and battery level. Within the fixed 8 bytes occupied by the message header, the message header includes at least a length field and a type field, and may also include a sequence number field seq and a reserved field reserve. The length field occupies 2 bytes and is used to indicate the length of the target message, including the message header itself, the content field, and the checksum. The sequence number field occupies 2 bytes and represents the number of the vehicle data in the current communication session. The sequence number for ordinary commands can start from zero and increment sequentially, while periodic data can use a fixed periodic sequence number. The type field occupies 2 bytes and indicates the service of the vehicle data. The command words in the type field are defined by a unified enumeration set, covering different service types such as theme switching, emoticon playback, emoticon reporting, vehicle status, backlight setting, file transfer, power off, album art, device information, WiFi and Bluetooth configuration reset, heartbeat, factory reset notification, and factory testing. Different service types are distinguished by command words, eliminating the need to repeatedly transmit text fields in each payload, thus effectively reducing redundancy overhead. A reserved field occupies 2 bytes for future expansion.
[0032] In this embodiment of the invention, after transmitting the target message to the target code table according to the target transmission strategy, the method further includes: if the target message includes a response indication, creating a waiting object based on the sequence number field in the target message, and storing the waiting object in a waiting response queue, wherein the response indication is used to instruct the target code table to send a response signal after receiving the target message; and deleting the waiting object from the waiting response queue in response to the response signal sent by the target code table. Specifically, for commands requiring a response, the vehicle system constructs a waiting object carrying a sequence number, adds it to the waiting response queue, and waits for a synchronization signal after the command is sent; after the target code table replies with a response, the vehicle system matches the corresponding command from the waiting response queue according to the sequence number and releases the wait, completing a reliable interaction. On this basis, if the waiting time exceeds a preset threshold, the command is determined to have timed out, and the receiving loop performs timeout cleanup to avoid queue backlog. For periodic vehicle status reporting, heartbeat maintenance, and expression playback, which do not require blocking and waiting for results, a no-response sending function can be used to send the data directly without waiting for a reply, thereby effectively reducing waiting overhead and improving overall transmission efficiency.
[0033] In an embodiment of the present invention, Figure 5 This illustrates a target priority partitioning concept provided by some embodiments of the present invention. Step 220: Determine the target priority based on the service type of the vehicle data. The target priority is associated with a preset target encapsulation strategy and a target transmission strategy. A specific implementation may include: Figure 5 As shown, the target priority does not rely solely on the vehicle data service content itself, but is expressed through multiple dimensions such as the service content, triggering method, cycle frequency, fragmentation status, and expression level of the vehicle data. Based on the relevance of vehicle data to real-time performance, safety, and user experience, vehicle data involving high real-time events can be classified as P0 (first priority), vehicle data involving high-frequency vehicle state change events as P1 (second priority), vehicle data for medium-real-time display events as P2 (third priority), and vehicle data for low-real-time events with large data volumes as P3 (fourth priority). The urgency of the first priority is higher than the second priority, the second priority is higher than the third priority, and the third priority is higher than the fourth priority. Vehicle data of different priorities are further classified according to the following... Figure 4The binary message shown is encapsulated and sent to the target code table via the special port 8099. The target code table parses and renders the received target message. Specifically, the first priority vehicle data may include event-driven emoticon services such as speeding reminders, rapid acceleration or deceleration, intelligent driving status changes, parking processes, fatigue or distracted driving reminders, and seat belt status, as well as necessary driving status change services. This type of vehicle data is triggered by events from the signal layer's consumer module or monitor, calling the underlying interface (e.g., FunctionControl.playAnimation) via emoticon playback instructions, encapsulating it into an animation playback type target message (Animation_play_cmd) and sending it directly. The target message carries information such as playback status, loop count, session identifier, forced playback flag, and animation name. The signal layer's native layer also has a built-in multi-level emoticon priority and playback status management mechanism to determine whether a new emoticon is sent directly, discarded, interrupts the current playback, or restores the previous state. The second priority vehicle data covers services such as vehicle speed, gear, battery level, remaining range, navigation speed limit, intelligent driving status, and time. Vehicle data for this type of service is aggregated in the vehicle snapshot field (vehicle_data_cmd) and transmitted as a whole via the target message at a period of approximately 100 milliseconds. Compared to sending each field individually, using a complete snapshot reduces the complexity of receiver state synchronization and maintains consistency of displayed data even with minor network fluctuations. Third-priority vehicle data includes weather conditions, day / night status, ambient temperature, heading angle, music playback status, and music session identifiers. This type of vehicle data can be either included in the aforementioned vehicle data snapshot (vehicle_data_cmd) for unified transmission or updated by the media session monitoring module when the status changes. When the album art changes, the vehicle's infotainment system first updates the music session identifier, then prepares the album art data. The codebook requests data fragments in blocks based on the session identifier and data offset. Fourth-priority vehicle data includes service data such as album art, resource files, theme resources, and firmware upgrade packages. This type of data is transmitted in fragments via target messages of file transfer type (Music_cover_cmd or file_transfer_cmd). The music cover uses a request-response transmission mechanism. The codebook sends a request carrying a music session identifier, data offset, and expected block size. The vehicle's infotainment system returns approximately 1,000 bytes of data each time. Resources and firmware files are managed using a file transfer state machine. The states include start transfer, data transfer, end transfer, abort, verification, query, continue, wait, and verification failure. Each data block is approximately 992 bytes and carries fields such as session identifier, total file size, data offset, data length, file checksum, and block sequence number.
[0034] In this embodiment of the invention, in addition to the static classification described above, vehicle data can be dynamically scheduled based on target priority according to vehicle speed, gear position, charging status, hotspot status, and upgrade status. For example, in high-speed or driving conditions, vehicle snapshot and emoticon event services are prioritized, reducing resource / OTA fragmentation frequency; in parked or charging conditions, the proportion of third-priority vehicle data and OTA fragmentation transmission is allowed to be increased; in upgrade status, the system enters the upgrading state via a state machine and returns to the pairing / connection recovery process after the upgrade is completed. This strategy can avoid long-term link occupation during large file transfers and ensure low-latency synchronization of vehicle speed, gear position, and alarm animations.
[0035] In this embodiment of the invention, step 230, which involves encapsulating the vehicle data according to the target encapsulation strategy and the preset message format, and using the encapsulated message as the target message, includes the following specific implementation: if the target priority of the vehicle data is a first priority, the vehicle data is encapsulated in the content field; if the target priority of the vehicle data is a second priority, multiple pieces of vehicle data generated in the first transmission period are merged and encapsulated in the content field; if the target priority of the vehicle data is a third priority, when a change in the vehicle data relative to the previous encapsulation value is detected, the vehicle data is encapsulated in the content field; if the target priority of the vehicle data is a fourth priority, the vehicle data is divided into multiple sub-data packets, and each sub-data packet is encapsulated in the content field of multiple messages.
[0036] In this embodiment of the invention, for vehicle data of the first priority, the vehicle data can be directly and completely encapsulated in the content field without additional processing. For vehicle data of the second priority, to avoid the frequent interaction overhead caused by single transmission, multiple vehicle data generated within the first transmission cycle (e.g., the 100ms mentioned above) are merged and encapsulated in the same content field to achieve batch transmission. For data of the third priority, encapsulation is only performed when a change in the current vehicle data compared to the previous encapsulation value is detected, in order to reduce redundant transmission. For data of the fourth priority, due to its large data volume, it needs to be divided into multiple sub-data packets, which are then encapsulated in the content fields of multiple messages and transmitted sequentially in fragment form. Through the above classification and encapsulation strategy, different types of data can adopt encapsulation methods adapted to their characteristics, thereby optimizing transmission efficiency while ensuring effectiveness.
[0037] In an embodiment of the present invention, step 240, which involves transmitting the target message to the target code table according to the target transmission strategy, includes the following specific implementation: if the target priority of the vehicle data is a first priority or a third priority, the target message is transmitted to the target code table after it is generated; if the target priority of the vehicle data is a second priority, the target message is periodically transmitted to the target code table according to a preset first transmission period; if the target priority of the vehicle data is a fourth priority, the target message is periodically transmitted to the target code table according to a second transmission period.
[0038] In this embodiment of the invention, for vehicle data with a target priority of first or third priority, a trigger-based transmission strategy can be adopted. Once the target message is encapsulated, it is immediately transmitted to the target code table without waiting for any period or condition. The difference lies in the triggering conditions during the encapsulation stage: first-priority vehicle data is encapsulated in real-time based on an event, and sent immediately after encapsulation; third-priority vehicle data is encapsulated only when a change in the current data compared to the previous encapsulation value is detected, and also sent immediately after encapsulation. Both maintain consistency in transmission scheduling, aiming for timely response after state or event changes. For vehicle data with a target priority of second priority, the encapsulated target message is periodically transmitted to the target code table according to a preset first transmission period, achieving continuous synchronization of driving status data through fixed-period snapshots. For vehicle data with a target priority of fourth priority, the target message containing each sub-data packet is transmitted to the target code table in batches according to a preset second transmission period, avoiding excessive link resource consumption by large amounts of data at once, which could affect the normal transmission of other types of data.
[0039] In this embodiment of the invention, by employing the target transmission strategy of matching targets based on target priority, the differentiated requirements of different types of data regarding real-time performance, continuity, and resource consumption can be accommodated within the same communication link. Accordingly, based on the aforementioned static layering, the target priority corresponding to services can be dynamically scheduled and adjusted according to vehicle speed, gear position, charging status, hotspot status, and upgrade status. For example, during high-speed or driving conditions, priority can be given to ensuring the timely delivery of vehicle snapshots and event emoticons, while appropriately reducing the transmission frequency of resources and firmware fragments, further optimizing the utilization efficiency of the communication link.
[0040] In an embodiment of the present invention, Figure 6 The flowchart illustrates the data interaction method between the codebook and the vehicle-mounted system provided in other embodiments of the present invention. For example... Figure 6 The data interaction method between the codebook and the vehicle-mounted system provided in the embodiment of the present invention can be executed by the target codebook. Specifically, as shown... Figure 6 The data interaction method between the speedometer and the vehicle's infotainment system shown includes steps 610 to 620.
[0041] Step 610: If a communication channel has been established with the vehicle's infotainment system, receive the target message from the vehicle's infotainment system.
[0042] In this embodiment of the invention, provided that a communication channel is successfully established with the vehicle's infotainment system, the target code table continuously listens for and receives target messages from the vehicle's infotainment system through the communication port within the target code table.
[0043] Step 620: Parse the target message and display the vehicle data included in the target message.
[0044] In this embodiment of the invention, the target code table parses the received target message, extracts the payload from the message, reconstructs the vehicle data according to the preset message format and type field definitions, and displays the parsed data on the code table's display interface, allowing users to view the vehicle's operating status and related interactive information in real time. In this embodiment, the target code table first obtains hotspot information broadcast by the vehicle's infotainment system via Bluetooth or manually. Upon receiving the hotspot information, the target code table also sequentially initiates a hotspot access request and a TCP-based communication connection request to establish a communication channel. If the target message includes a response indication, the target code table sends a response signal upon receiving the target message. After receiving the command, the target code table immediately returns a corresponding response signal to the vehicle's infotainment system to inform it that the command has been successfully received. This allows the vehicle's infotainment system to match and clear the waiting queue based on the response signal, ensuring a closed loop of reliable communication. In the above process, the target code table also needs to perform differentiated interface rendering and interactive feedback for various types of data such as vehicle speed, gear, battery level, music album, and facial animation effects, based on the business type of vehicle data and the corresponding display strategy, to ensure that users have a smooth and clear cockpit display experience.
[0045] In an embodiment of the present invention, Figure 7 The present invention illustrates the concept of a data interaction system provided by some embodiments thereof. Figure 7 As shown, the data interaction system 700 provided in this embodiment of the invention includes a vehicle-mounted system 710 and a target code table 720.
[0046] The vehicle-mounted unit 710 is used to acquire vehicle data to be transmitted to the target code table when a communication channel has been established with the target code table; determine the target priority according to the service type of the vehicle data, wherein the target priority is associated with a preset target encapsulation strategy and a target transmission strategy; encapsulate the vehicle data according to the target encapsulation strategy and a preset message format, and use the encapsulated message as the target message; and transmit the target message to the target code table according to the target transmission strategy. The target code table 720 is used to receive target messages from the vehicle's infotainment system when a communication channel has been established with the system; to parse the target messages and display the vehicle data included in the target messages.
[0047] It should be noted that the embodiments of the data interaction system between the odometer and the vehicle-mounted system in this specification and the embodiments of the data interaction method between the odometer and the vehicle-mounted system in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the corresponding embodiments of the data interaction method between the odometer and the vehicle-mounted system mentioned above, and the repeated parts will not be described again.
[0048] In this embodiment of the invention, examples are given to better understand the method provided.
[0049] Figure 8 This illustrates a transmission concept for vehicle data transmission to a target code table, provided by some embodiments of the present invention. For example... Figure 8 As shown, for vehicle data including emoticons in the first priority category, when the vehicle speed is updated, the signal layer calculates the acceleration corresponding to the speed change through the vehicle bus at intervals of at least 1 second. If the acceleration is greater than or equal to 0.2 times the gravitational acceleration, a rapid acceleration emoticon is triggered; if it is less than or equal to negative 0.2 times the gravitational acceleration, a rapid deceleration emoticon is triggered. When the vehicle system is in a matched state and the speeding condition is triggered, a speeding reminder emoticon is sent. When the gear is switched to reverse or forward and the seat belt is not fastened, a seat belt reminder can be triggered. Changes in the status of intelligent driving, automatic parking, surround view system, fatigue driving, distracted driving, as well as changes in the status of doors, windows, sunroof, door locks, child locks, sentry mode, air conditioning, fragrance, seats, ambient lighting, music, video, radio, karaoke, games, etc., can also be triggered by the corresponding function processing module. Emoticon sending is uniformly processed by the playback command module (ExpressionCmd.sendEmoji, not shown in the figure) of the access layer. This module first determines whether the current theme allows the playback of emoticons, i.e., whether the current theme is an emoticon theme or the emoticon switch is enabled. Then, it calls a thread (NativeplayAnimation) in the thread pool to generate an animation session identifier (ID), recording information such as the priority, status, whether it is always displayed, and start time of the new emoticon. This ID is then sent to the target code table via the emoticon session module (ANIMATION_PLAY_CMD) in the access layer. After playback ends in the target code table, it reports via ANIMATION_REPORT_CMD, allowing the vehicle's infotainment system to clear the current playback status or restore interrupted always-displayed emoticons. Through this mechanism, driving behavior, vehicle status, and vehicle application status can be converted into lightweight emoticon commands recognizable by the code table, while prioritizing and using session mechanisms to prevent low-priority emoticons from overwriting critical reminders.
[0050] like Figure 8As shown, for the full vehicle data structure corresponding to the second priority, the vehicle's signal layer obtains the raw signals through the vehicle CAN bus, cockpit service, and CarService signal callback module. After receiving the raw signals from the vehicle service module (CarService), the consumer modules in the Java layer of the access layer do not immediately construct independent network messages. Instead, they call the Native layer of the access layer through ports (e.g., FunctionControl.updateVehicleDataField, updateVehicleFloatDataField, or updateVehicleStrDataField) to update the global vehicle data snapshot by field name. The Native layer adds a mutex lock to the field updates, setting the data update flag only when the field value changes, avoiding data inconsistency caused by concurrent writes. The vehicle-side clock maintains a global vehicle data structure (vehicle_data_cmd) to carry the comprehensive vehicle status that the current clock needs to display. This structure includes fields such as charging status, battery percentage, remaining mileage, gear, power type, current mileage, current energy / fuel consumption, steering angle, date, time, vehicle speed, navigation speed limit, intelligent driving status, rapid acceleration status, music session identifier (ID), music playback status, weather, day / night status, and outside temperature. The access layer's socket module (Native SmallSocket) automatically starts a vehicle data periodic transmission thread during initialization. This thread acquires a snapshot of the current vehicle data approximately every 100ms and sends it to the codebook end via a command using the vehicle data structure (vehicle_data_cmd). The advantage of using a complete snapshot is that the receiving end does not need to rely on the independent incremental order of each field; even if a periodic message is lost, the complete status can still be obtained in the next period. Furthermore, multiple theme interfaces share the same vehicle status, reducing the complexity of codebook end subscription and aggregation.
[0051] For vehicle data related to music album covers corresponding to the third priority, Figure 9This paper illustrates the transmission flow of third-type vehicle data provided by some embodiments of the present invention. When the media session cover changes, the vehicle-mounted unit scales the cover and converts it into vehicle data in RGB565 format, generates a new music session identifier (ID), and temporarily stores the cover data in the Native layer of the access layer. When the target code table needs cover data, it sends a music cover request (MUSIC_COVER_REQUEST), which includes the music session identifier (ID), data offset, and expected chunk size (chunk_size). After verifying the session identifier (ID), the vehicle-mounted unit copies up to approximately 1000 bytes from the specified offset position and constructs a music cover response command (MUSIC_COVER_RESPONSE) to return to the target code table; if there is currently no cover data, it returns a no-cover command (MUSIC_COVER_NOEXIST). This method, where the receiving end actively requests the cover data based on the offset, avoids link congestion caused by transmitting a large cover at once and also facilitates re-requesting missing segments in abnormal situations.
[0052] For vehicle data in the resource files or firmware files corresponding to the fourth priority, Figure 10 The transmission process of fourth type vehicle data provided by some embodiments of the present invention is illustrated. For example... Figure 10 As shown, for resource files or firmware files, the vehicle-mounted system establishes a file transfer session via the file transfer command (FILE_TRANSFER_CMD). When the session starts, the vehicle-mounted system calculates the checksum of the entire file and sends a transfer start command (TRANSFER_START) to inform the system of the file type, session ID, file size, and checksum. Once the code reader is ready, it replies with a transfer ready confirmation (TRANSFER_READY), and the vehicle-mounted system sends the first data block. Afterwards, the code reader continues sending the next data block via a transfer continue command (TRANSFER_CONTINUE) carrying the fragment sequence number (index). Each data block contains the file type, transfer status, session ID, total file size, data offset, data length, CRC16 checksum of the entire file, fragment sequence number, and the current block data. If the code reader returns a transfer wait indication (TRANSFER_WAIT), the vehicle-mounted system continues after a delay; if it returns a transfer success, transfer failure, or checksum failure, the vehicle-mounted system closes the session and clears the transfer status. This mechanism ensures that large files with low real-time requirements can be transferred under controlled conditions and that resources are released promptly in the event of a link interruption. Firmware data can be used as a file transfer type. Figure 7The file transfer command (FILE_TRANSFER_CMD) shown indicates that the file is being transferred in chunks. After the target code table receives the complete upgrade package, it implements the firmware upgrade using a two-level bootloader. The first-level bootloader is responsible for hardware initialization and boot mode selection during the startup phase, while the second-level bootloader is responsible for upgrade package parsing, partition writing, integrity verification, and failure rollback. After the upgrade is complete, the system automatically restarts and re-enters the connection process. By using over-the-air (OTA) firmware as a chunked transmission of large files with low real-time requirements, the system can expand its upgrade capabilities without changing the real-time vehicle data channel.
[0053] In this embodiment of the invention, during the data interaction between the vehicle-mounted system and the code table, the connection status on the vehicle-mounted system side is maintained by the state machine of the access layer. The state machine includes five states: idle, pairing, paired, abnormal, and upgrading. Specifically, after the SmallSocket service in the access layer starts, the heartbeat thread runs immediately, sending a heartbeat packet approximately every second and maintaining a send count and a reply count. When the difference between the send count and the reply count exceeds a preset threshold, the current socket connection is determined to be abnormal. If the abnormality occurs during file transfer, the vehicle-mounted system first closes the file transfer session and clears the transfer status, then closes the socket of the target code table, calls back the connection disconnection event to the upper layer, and uses a specific port number to identify the socket disconnection event. In addition to the heartbeat mechanism, the TCP connection itself is also configured with keepalive parameters, enabling keepalive detection and setting the idle detection time, detection interval, and detection count, while disabling the Nagle algorithm to reduce small packet latency. The receiving thread employs a non-blocking socket combined with select timeout polling to continuously check connection validity during periods of no data. If transmission fails, it handles connection closure for various network errors. The state machine's driving state machine transitions according to the following rules: when the device is not paired or the user actively removes the device, it enters an idle state and rejects new socket client connections; when the pairing process begins, it enters a pairing state; after a successful socket connection, it enters a paired state; if a socket connection fails, the hotspot closes, the device loses power, or the connection is reset, it enters an abnormal state; after a firmware upgrade is triggered, it enters an upgrade state. Through this state machine, the system can clearly distinguish between different scenarios such as user-initiated removal, hotspot anomalies, Bluetooth anomalies, socket anomalies, and upgrades, avoiding state confusion caused by simple reconnection logic and ensuring that the system can make correct and predictable state responses under various operating conditions.
[0054] In this embodiment of the invention, a local area network TCP direct connection is established through the vehicle's hotspot, enabling the vehicle's infotainment system and the target vehicle speedometer to communicate without relying on cloud or cellular network relays. The vehicle's infotainment system directly issues periodic vehicle data snapshots and event-based emoticon commands, effectively meeting the real-time synchronization requirements of driving-related information such as vehicle speed, gear position, overspeed warnings, rapid acceleration, and rapid deceleration, significantly reducing the transmission latency of high-frequency vehicle control data. At the protocol level, compared to general text protocols such as Hypertext Transfer Protocol and JavaScript object representation, a lightweight message structure with an eight-byte binary header and a two-byte cyclic redundancy check is adopted. The payload structure is directly distinguished by the type field in the message, avoiding repeated transmission of field names and redundant protocol headers, greatly increasing the payload ratio, and is especially suitable for the rapid transmission of high-frequency small data packets such as vehicle speed, battery level, time, and gear position. To address the differentiated transmission needs of various data types, vehicle snapshots, facial expression events, music album art, resource files, and firmware upgrades are all subject to layered scheduling using different command words, triggering methods, periodic frequencies, and fragmentation states. High-real-time vehicle data and event commands can be rapidly distributed, while large file data is transmitted in a controlled manner through fragmentation, effectively preventing resource files or firmware upgrade data from occupying link resources for extended periods. Regarding connection stability, the vehicle-mounted system employs application-layer heartbeats, TCP keep-alive detection, non-blocking socket detection, and a unified state machine to manage connection states. When the heartbeat difference exceeds a threshold or a socket connection error occurs, the system promptly closes the abnormal connection, releases the file transmission state, and notifies the upper layer to enter an abnormal disconnection state, preventing residual sockets or transmission sessions from interfering with subsequent reconnections. In terms of network configuration, the code reader does not require users to manually enter the wireless network name and password. Instead, it obtains the vehicle-mounted hotspot credentials through a low-power Bluetooth configuration process. Hotspot information is read by the vehicle-mounted system service or soft access point configuration. After network configuration is complete, the code reader can connect to the vehicle-mounted hotspot to establish a high-speed data channel, balancing low interaction costs with high bandwidth transmission. In terms of interactive experience, changes in vehicle speed, navigation speed limits, intelligent driving and parking status, door / window, air conditioning, and seat status, and media playback status can all trigger corresponding emoji commands. These emoji commands carry session identifiers, loop counts, forced playback flags, priority, and status cache information, reducing issues such as repeated playback and low-priority animations overriding key reminders, making the speedometer interaction more closely aligned with the vehicle's real-time status. Furthermore, it supports complete lifecycle management of the speedometer firmware. The firmware version is obtained via device information commands, and an upgrade process is initiated when a low version is detected. The firmware upgrade package is sent via a fragmented file transfer command. The speedometer, combined with a two-level bootloader and upgrade image mechanism, completes the writing, verification, and rollback, which is beneficial for subsequent feature expansion, bug fixing, and mass production maintenance.Furthermore, this invention possesses excellent scalability. The command word enumeration, payload structure, and reserved fields in the message header provide ample room for expansion of new themes, emoticons, resource types, factory tests, equipment information, and status reporting. The Java layer, through the layered encapsulation of modules such as functional processing modules, control interfaces, theme commands, and emoticon commands, also facilitates the rapid integration of subsequent additions of vehicle signals and interactive services.
[0055] In an exemplary embodiment, the vehicle may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the data interaction method between the code table and the vehicle-mounted system provided in any of the above method embodiments.
[0056] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory including instructions, which can be executed by a processor of a device to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc. When the instructions in this non-transitory computer-readable storage medium are executed by a processor of an electronic device, the electronic device is able to execute the data interaction method between the code table and the vehicle-mounted system provided in any of the above-described method embodiments.
[0057] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the data interaction method between the code table and the vehicle system provided in any of the above method embodiments.
[0058] The above description does not provide detailed technical specifications regarding the structure of each layer. However, those skilled in the art should understand that layers and regions of desired shapes can be formed using various technical means. Furthermore, to form the same structure, those skilled in the art can also design methods that are not entirely identical to those described above. Additionally, although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be advantageously combined.
[0059] Although preferred embodiments of the invention have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including both the preferred embodiments and all changes and modifications falling within the scope of the invention.
[0060] Obviously, those skilled in the art can make various modifications and variations to this invention without departing from its spirit and scope. Therefore, if these modifications and variations fall within the scope of the claims of this invention and their equivalents, this invention also intends to include these modifications and variations.
Claims
1. A code table and vehicle machine data interaction method, characterized in that, Applied to in-vehicle infotainment systems, the method includes: If a communication channel has been established with the target code table, acquire the vehicle data to be transmitted to the target code table; A target priority is determined based on the service type of the vehicle data, and the target priority is associated with a preset target encapsulation strategy and a target transmission strategy. The vehicle data is encapsulated according to the target encapsulation strategy and the preset message format, and the encapsulated message is used as the target message. According to the target transmission strategy, the target message is transmitted to the target code table.
2. The method of claim 1, wherein, Before acquiring the vehicle data to be transmitted to the target code table, the method further includes: In response to an add request, scan for Bluetooth devices within the target range of the vehicle's infotainment system, the Bluetooth devices including the target code table; If the target code table exists within the target range, establish a distribution network channel with the target code table; The hotspot information of the vehicle's infotainment system is transmitted to the target code table through the distribution network channel, so that the target code table initiates a hotspot access request based on the hotspot information. In response to the hotspot access request from the target code table, access the target code table; The system listens for and receives communication connection requests from the target code table through a preset communication port, and responds to the communication connection requests to establish a communication channel with the target code table.
3. The method of claim 1, wherein, The preset message format includes at least a message header and a content field. The message header includes at least a length field and a type field. The content field is used to carry the vehicle data. The length field is used to indicate the length of the target message. The type field is used to indicate the service type of the vehicle data.
4. The method of claim 3, wherein, The message header also includes a sequence number field, which is used to indicate the number of the vehicle data in the current communication session; After transmitting the target message to the target code table according to the target transmission strategy, the method further includes: If the target message includes a response indication, a waiting object is created based on the sequence number field in the target message, and the waiting object is stored in the waiting response queue. The response indication is used to instruct the target code table to send a response signal after receiving the target message. In response to the response signal sent by the target code table, the waiting object is removed from the waiting response queue.
5. The method of claim 3, wherein, The step of encapsulating the vehicle data according to the target encapsulation strategy and the preset message format, and using the encapsulated message as the target message, includes: If the target priority of the vehicle data is the first priority, the vehicle data will be encapsulated in the content field; If the target priority of the vehicle data is the second priority, multiple pieces of vehicle data generated in the first transmission cycle are merged and encapsulated in the content field; If the target priority of the vehicle data is the third priority, when a change in the vehicle data relative to the previous encapsulation value is detected, the vehicle data is encapsulated in the content field; If the target priority of the vehicle data is the fourth priority, the vehicle data is divided into multiple sub-data packets, and each sub-data packet is encapsulated in the content field of multiple messages.
6. The method of claim 3, wherein, The step of transmitting the target message to the target code table according to the target transmission strategy includes: If the target priority of the vehicle data is the first priority or the third priority, it is transmitted to the target code table after the target message is generated; If the target priority of the vehicle data is the second priority, the target message is periodically transmitted to the target code table according to the preset first transmission cycle; If the target priority of the vehicle data is the fourth priority, the target message is periodically transmitted to the target code table according to the second transmission cycle.
7. The method according to any one of claims 1 to 6, wherein The method further includes: During the data transmission between the vehicle's infotainment system and the target code table, the status of the target code table is monitored by the vehicle's state machine to ensure it is functioning correctly.
8. A method for data interaction between a speedometer and a vehicle-mounted system, characterized in that, Applied to a target code table, the method includes: If a communication channel has been established with the vehicle's infotainment system, the target message from the vehicle's infotainment system will be received. Parse the target message and display the vehicle data included in the target message.
9. The method as described in claim 8, characterized in that, The method further includes: Upon receiving hotspot information, a hotspot access request and a communication connection request are initiated sequentially based on the hotspot information. If the target message includes a response indication, a response signal is sent upon receiving the target message.
10. A data interaction system, characterized in that, The system includes: The vehicle-mounted unit (V2U) is used to acquire vehicle data to be transmitted to the target code table when a communication channel has been established with the target code table; determine the target priority based on the service type of the vehicle data, wherein the target priority is associated with a preset target encapsulation strategy and a target transmission strategy; encapsulate the vehicle data according to the target encapsulation strategy and a preset message format, and use the encapsulated message as the target message; and transmit the target message to the target code table according to the target transmission strategy. The target code table is used to receive target messages from the vehicle's infotainment system when a communication channel has been established; to parse the target messages and display the vehicle data included in the target messages.
