Vehicle parameter data management method and device, electronic equipment and storage medium

Abstract

The invention provides a vehicle parameter data management method and device, electronic equipment and a storage medium. The method comprises the following steps: storing vehicle parameter data of a vehicle in an embedded database in a system; reading the vehicle parameter data from the embedded database in response to the power-on operation of the system, and caching the vehicle parameter data according to the read-write frequency and the priority; classifying the vehicle parameter data in the cache, and distributing the vehicle parameter data to a first function module according to the data category; synchronizing the vehicle parameter data in the cache to a micro-control unit, analyzing the vehicle parameter data by using the micro-control unit, and distributing the analyzed vehicle parameter data to a second function module corresponding to the micro-control unit; and in the system operation process, when it is judged that the vehicle parameter data needs to be updated, receiving an updating request sent by the first function module and / or the second function module, and updating the vehicle parameter data in the embedded database according to the updating request. The data transmission link can be simplified, and the data storage efficiency can be improved.

Description

Technical Field

[0001] The present application relates to the field of new energy vehicle technology, and in particular to a vehicle parameter data management method, device, electronic equipment and storage medium. Background Art

[0002] With the rapid development of intelligent assisted driving technology, the vehicle's electrical and electronic (E / E) architecture has become increasingly complex, and various vehicle controllers need to process large amounts of data from multiple sensors and other controllers. As a key link in supporting the normal operation of the electronic rearview mirror system, the vehicle parameter data management system is responsible for providing vehicle parameter data (referred to as vehicle parameter data) to other functional modules. The vehicle parameter data includes key information such as vehicle model, sensor specifications, and camera calibration parameters. The accuracy and real-time nature of these data are directly related to the performance and reliability of the electronic rearview mirror system.

[0003] Existing vehicle parameter data management methods have many deficiencies in data transmission and storage. On the one hand, when vehicle parameter data is transmitted between multiple modules, the link is relatively complex and susceptible to interference, resulting in low data transmission efficiency; on the other hand, the current method usually uses files to store and call vehicle parameter data, which is inefficient, and the storage structure is difficult to respond quickly when reading, writing or updating frequently. In addition, complex data transmission links and inefficient storage structures are prone to data loss or transmission delays, affecting the response speed and reliability of the electronic rearview mirror system. Summary of the invention

[0004] In view of this, an embodiment of the present application provides a vehicle parameter data management method, device, electronic device and storage medium to solve the problems of complex data transmission links and low storage efficiency in the prior art.

[0005] According to a first aspect of an embodiment of the present application, a vehicle parameter data management method is provided, comprising: storing the vehicle parameter data of a vehicle in an embedded database in the system to form an initialized vehicle parameter data set; in response to a power-on operation of the system, reading the vehicle parameter data from the embedded database, and caching the vehicle parameter data according to the read and write frequency and priority of the vehicle parameter data; classifying the vehicle parameter data in the cache, and distributing the vehicle parameter data to a corresponding first functional module according to the data category; synchronizing the vehicle parameter data in the cache to a microcontroller unit, parsing the vehicle parameter data using the microcontroller unit, and distributing the parsed vehicle parameter data to a second functional module corresponding to the microcontroller unit; during system operation, when it is determined that the vehicle parameter data needs to be updated, receiving an update request sent by the first functional module and / or the second functional module, and updating the vehicle parameter data in the embedded database according to the update request.

[0006] According to a second aspect of an embodiment of the present application, a vehicle parameter data management device is provided, comprising: a storage module, storing the vehicle parameter data of a vehicle in an embedded database in the system to form an initialized vehicle parameter data set; a reading module, reading the vehicle parameter data from the embedded database in response to the power-on operation of the system, and caching the vehicle parameter data according to the read and write frequency and priority of the vehicle parameter data; a distribution module, classifying the vehicle parameter data in the cache, and distributing the vehicle parameter data to the corresponding first functional module according to the data category; a parsing module, synchronizing the vehicle parameter data in the cache to a micro control unit, parsing the vehicle parameter data using the micro control unit, and distributing the parsed vehicle parameter data to the second functional module corresponding to the micro control unit; an update module, receiving an update request sent by the first functional module and / or the second functional module during system operation when it is determined that the vehicle parameter data needs to be updated, and updating the vehicle parameter data in the embedded database according to the update request.

[0007] According to a third aspect of an embodiment of the present application, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the steps of the above method are implemented when the processor executes the computer program.

[0008] According to a fourth aspect of an embodiment of the present application, a computer-readable storage medium is provided, which stores a computer program, and when the computer program is executed by a processor, the steps of the above method are implemented.

[0009] At least one of the above technical solutions adopted in the embodiments of the present application can achieve the following beneficial effects:

[0010] The vehicle parameter data of the vehicle is stored in an embedded database in the system to form an initialized vehicle parameter data set; in response to the power-on operation of the system, the vehicle parameter data is read from the embedded database, and cached according to the read and write frequency and priority of the vehicle parameter data; the vehicle parameter data in the cache is classified, and the vehicle parameter data is distributed to the corresponding first functional module according to the data category; the vehicle parameter data in the cache is synchronized to the micro control unit, the vehicle parameter data is parsed by the micro control unit, and the parsed vehicle parameter data is distributed to the second functional module corresponding to the micro control unit; during the operation of the system, when it is determined that the vehicle parameter data needs to be updated, an update request sent by the first functional module and / or the second functional module is received, and the vehicle parameter data in the embedded database is updated according to the update request. This application can simplify the data transmission link and improve the efficiency of data storage. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0012] Figure 1 It is a schematic diagram of the overall architecture of the vehicle parameter data management system involved in the actual scenario of the embodiment of the present application;

[0013] Figure 2 It is a schematic diagram of the overall implementation process of the vehicle parameter data management method provided in the embodiment of the present application;

[0014] Figure 3 It is a flowchart of the vehicle parameter data management method provided in the embodiment of the present application;

[0015] Figure 4 It is a structural diagram of a vehicle parameter data management device provided in an embodiment of the present application;

[0016] Figure 5 It is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0017] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0018] With the rapid development of intelligent assisted driving technology, the electronic and electrical (E / E) architecture of the whole vehicle has become more and more complex. As the core of the whole vehicle electronic system, the main responsibility of the controller is to process data streams from multiple sensors and other controllers to support the intelligent functions of the vehicle. For example, the electronic rearview mirror system (a technology that replaces traditional optical rearview mirrors) is an important intelligent driving assistance function. It uses a camera to collect and process image data of the external environment to display real-time video in the car.

[0019] In order for the electronic rearview mirror system to operate normally, the controller needs to obtain and manage various "vehicle parameter data", that is, vehicle parameter data. These vehicle parameter data are crucial to the performance of the electronic rearview mirror. Vehicle parameter data includes but is not limited to the following information:

[0020] Basic vehicle information (such as model, manufacturer, etc.) to determine the compatibility and suitability of a specific vehicle;

[0021] Sensor specifications (such as type, resolution, viewing angle, etc.), so that the system can be adaptively optimized according to the sensor characteristics;

[0022] Camera calibration parameters (such as installation position and lens calibration information) are used to ensure the accuracy of image correction and stitching.

[0023] In the related art, vehicle parameter data management is usually carried out through centralized or distributed storage and transmission. In this system, different vehicle parameter data are transmitted and shared between different modules through multiple data links. These data links can be buses, network connections or other protocols, and data is transmitted from the controller to each module that needs to use the data. Usually, the vehicle parameter data is stored as a file for the system to read and call in different states or operating modes.

[0024] Although the existing vehicle parameter data management methods can meet basic functional requirements, they still have some significant shortcomings in data transmission and storage. The specific problems are as follows:

[0025] 1. Complex transmission links: Vehicle parameter data is transmitted between different modules through multiple links, which makes the transmission process more complicated. The increase in links makes the transmission path susceptible to interference or delay, especially when multiple modules work in parallel. The increase in link load may lead to instability in data transmission.

[0026] 2. Low file storage efficiency: Current vehicle parameter data storage is mainly stored in the form of files. However, this file-based storage method is insufficient in terms of access speed and storage space utilization, especially when data needs to be read or updated frequently, the file processing efficiency is low, which increases the overall burden of the system.

[0027] 3. Data loss and delay risk: Due to the complexity of transmission links and storage methods, existing methods are prone to data loss or transmission delay. For electronic rearview mirror systems, this may result in the inability to provide key vehicle parameter data to subsequent processing modules in a timely manner, affecting the real-time response of the system and further affecting driving safety.

[0028] Therefore, the existing vehicle parameter data management methods in the application of intelligent driving systems expose problems such as complex data transmission links, low file storage efficiency, data loss and delay, which limits the real-time performance and reliability of the electronic rearview mirror system. Therefore, it is urgent to provide an efficient vehicle parameter data management method to simplify the data transmission link, optimize the data storage method, reduce data loss and transmission delay, and improve the overall performance of the electronic rearview mirror system.

[0029] In view of the problems existing in the above-mentioned related technologies, this application provides a vehicle parameter data management method based on database classification optimization storage strategy. The technical solution of this application mainly includes the following technical means:

[0030] 1. SPI (Serial Peripheral Interface) is used to realize the vehicle parameter data communication between SOC (System on Chip) and MCU (Microcontroller Unit), which simplifies the data transmission link and improves the transmission efficiency. In specific implementation, data is transmitted between SOC and MCU through the SPI bus to achieve efficient data transmission.

[0031] 2. Use lightweight database technology to store vehicle parameter data and quickly add, delete, modify and query operations, thereby improving data processing efficiency. When implementing, select a lightweight database suitable for the characteristics of vehicle parameter data, such as SQLite, to store and manage vehicle parameter data. SQLite is a lightweight embedded database with the advantages of low resource consumption, high speed, and ease of use. It is very suitable for processing data with high real-time requirements such as vehicle parameter data.

[0032] 3. The vehicle parameter data is divided into static data and dynamic data, which reduces the redundancy of data reading, writing and transmission and improves data management efficiency. In specific implementation, static data refers to data that does not change frequently, such as the vehicle's length, width and height, model, VIN code and other basic information, as well as the sensor's serial number, performance parameters, etc.; dynamic data refers to data that changes frequently, such as camera calibration related parameters. By distinguishing static data from dynamic data, the number of data reading, writing and transmission can be reduced, redundancy can be reduced, and data management efficiency can be improved.

[0033] Compared with the prior art, the technical solution of this application mainly solves the following technical problems:

[0034] 1) The data transmission link is complex and the transmission efficiency is low: The traditional vehicle parameter data transmission link is complex, which is prone to data loss or delay, affecting the performance of the electronic rearview mirror. This technical solution realizes the vehicle parameter data communication between SOC and MCU through SPI, simplifies the data transmission link, and improves the transmission efficiency.

[0035] 2) The problem of low efficiency of traditional file storage in processing vehicle parameter data: Traditional vehicle parameter data uses file storage. When processing vehicle parameter data, data reading and writing and adding, deleting, modifying and checking are cumbersome, occupy more resources, and are inefficient, and cannot meet the high real-time requirements of vehicle parameter data. This technical solution uses lightweight database technology to realize the storage and fast adding, deleting, modifying and checking of vehicle parameter data, thereby improving data processing efficiency.

[0036] 3) High data redundancy: In the existing vehicle parameter data management methods, there is a large amount of redundant data during data storage and transmission, which leads to resource waste and increases the burden on the system. This technical solution reduces the redundancy of data reading, writing and transmission and improves data management efficiency by dividing vehicle parameter data into static data and dynamic data.

[0037] Before describing the contents of the technical solution of the present application in detail, the architecture of the vehicle parameter data management system involved in the technical solution of the present application is first introduced in combination with the drawings and specific embodiments. Figure 1 Schematic diagram of the overall architecture of the vehicle data management system involved in the actual scenario of the embodiment of the present application. Figure 1 As shown, the vehicle parameter data management system may specifically include the following contents:

[0038] Based on the principle of modular design, this system constructs four core modules including vehicle parameter data storage and management, SOC side vehicle parameter data processing, MCU side vehicle parameter data processing and vehicle parameter data transmission. Each module is closely connected through standardized interfaces and communication protocols to form an efficient and reliable vehicle parameter data processing and transmission network, covering the entire life cycle from data generation to application. The vehicle parameter data management system can include the following core modules:

[0039] 1. Vehicle parameter data storage and management module

[0040] As the data center of the entire system, the vehicle parameter data storage and management module adopts lightweight database technologies such as SQLite, making full use of its small size, fast speed, and easy maintenance to achieve persistent storage and efficient management of vehicle parameter data. This module is not only responsible for the initial entry of static data (such as basic vehicle information, sensor specifications, etc.), but also supports real-time update and query of dynamic data (such as camera calibration parameters, real-time status of sensors, etc.). Through the rich API interface provided by SQLite, the module can flexibly perform data addition, deletion, modification and query operations to ensure the accuracy and timeliness of the data.

[0041] 2. SOC side vehicle parameter data processing module

[0042] SOC (system-on-chip) is the core processor of the vehicle control system, and the vehicle parameter data processing module on it is responsible for data integration, distribution and optimization. This module realizes efficient communication with other functional modules inside SOC through the COM (communication) component of Autosar AP (application platform). After receiving the data provided by the vehicle parameter data storage and management module, the vehicle parameter data processing module on the SOC side will perform necessary processing and conversion on the data according to the preset algorithms and logic, and then distribute the data to the required modules or systems in a publish / subscribe mode. In addition, this module is also responsible for receiving update requests from other modules, and writing the updated data back to the database for persistent storage to ensure the real-time and consistency of the data.

[0043] 3. MCU side vehicle parameter data processing module

[0044] MCU (microcontroller unit) is usually responsible for performing low-level control and data acquisition tasks in vehicle systems. The vehicle parameter data processing module on the MCU side serves as a bridge for data interaction between the MCU and the SOC. It is mainly responsible for receiving vehicle parameter data synchronization information from the SOC side, and distributing the data to other functional modules on the MCU side through the inter-process communication functional component of the Autosar CP (communication platform). At the same time, this module is also responsible for processing vehicle parameter data update requests issued by the functional modules on the MCU side, and transmitting the updated data back to the SOC side through the vehicle parameter data transmission module for storage. In this way, the vehicle parameter data processing module on the MCU side realizes the two-way synchronization and real-time update of vehicle parameter data between the MCU and the SOC.

[0045] 4. Vehicle parameter data transmission module

[0046] The vehicle parameter data transmission module is a key component connecting the SOC and MCU, and is responsible for achieving efficient data transmission and synchronization between the two. Considering the high requirements for data transmission speed and reliability in vehicle systems, this module adopts the SPI (Serial Peripheral Interface) communication protocol to ensure that the vehicle parameter data can be transmitted quickly and accurately between the SOC and MCU. At the same time, the module has an error detection and recovery mechanism, which can detect and correct errors in time during data transmission to ensure the integrity and security of data transmission. In addition, the vehicle parameter data transmission module is also responsible for processing synchronization signals and timeout logic to ensure that the data synchronization process between the SOC and MCU can proceed smoothly.

[0047] Based on the above-mentioned architecture of the vehicle parameter data management system, the overall implementation process of the vehicle parameter data management method of the present application is summarized. Figure 2 This is a schematic diagram of the overall implementation process of the vehicle parameter data management method provided in the embodiment of the present application. Figure 2 As shown, the overall implementation process of the vehicle parameter data management method may include the following main process steps:

[0048] 1. System power-on initialization: After the system is powered on, the vehicle parameter data storage and management module on the SOC side reads the vehicle parameter data from the embedded database and stores it in the cache area for subsequent data processing and distribution operations.

[0049] 2. Vehicle parameter data reading and processing: The vehicle parameter data processing module on the SOC side reads the vehicle parameter data from the cache area, parses and classifies the data for subsequent distribution operations.

[0050] 3. Data distribution on the SOC side: The data processing module on the SOC side distributes the classified vehicle parameter data to the corresponding modules through the preset communication components according to the requirements of each functional module. Specifically, the data is distributed to the camera calibration module, power-on self-test module and upgrade module, etc., to ensure that these modules can obtain the required vehicle parameter data when the system starts.

[0051] 4. Data synchronization to MCU side: The vehicle parameter data transmission module reads data from the SOC side and transmits the vehicle parameter data to the MCU side synchronously through the serial peripheral interface (SPI). The vehicle parameter data processing module on the MCU side receives and parses the synchronized data to ensure the integrity and real-time nature of the data.

[0052] 5. Data distribution on the MCU side: After the data analysis is completed, the data processing module on the MCU side will further distribute the data to the functional modules on the MCU side, including the power-on self-test module and upgrade module on the MCU side, to ensure that each module on the MCU side can call the latest vehicle parameter data.

[0053] 6. Update request judgment: During the system operation, determine whether there is a new vehicle parameter data update request. If there is an update request, the system re-acquires and updates the vehicle parameter data, repeating the data reading, distribution and synchronization process; if there is no update request, proceed to the next step.

[0054] 7. Data storage to database: In the absence of new update requests, the vehicle parameter data storage and management module on the SOC side writes the data in the cache area to the embedded database to complete the persistent storage of the vehicle parameter data and ensure that the data remains consistent after the system is shut down or restarted.

[0055] 8. System power off: After completing the above operations, the system enters the power off process, and this process of the vehicle parameter data management method ends.

[0056] The vehicle parameter data management method of the present application realizes efficient management and distribution of vehicle parameter data through the process of system power-on, data distribution, synchronization and update judgment, ensures that each module of the electronic rearview mirror system calls the latest vehicle parameter data in real time, and improves the reliability and real-time performance of the system.

[0057] The contents of the technical solution of the present application are described in detail below with reference to the accompanying drawings and specific embodiments.

[0058] Figure 3 Schematic diagram of the process of the vehicle parameter data management method provided in the embodiment of the present application. Figure 3 As shown, the vehicle parameter data management method may specifically include:

[0059] S301, storing the vehicle parameter data of the vehicle in an embedded database in the system to form an initialized vehicle parameter data set;

[0060] S302, in response to a power-on operation of the system, reading vehicle parameter data from an embedded database, and caching the vehicle parameter data according to a read and write frequency and priority;

[0061] S303, classifying the vehicle parameter data in the cache, and distributing the vehicle parameter data to the corresponding first functional module according to the data category;

[0062] S304, synchronizing the vehicle parameter data in the cache to the micro control unit, parsing the vehicle parameter data using the micro control unit, and distributing the parsed vehicle parameter data to the second functional module corresponding to the micro control unit;

[0063] S305: During the operation of the system, when it is determined that the vehicle parameter data needs to be updated, an update request sent by the first functional module and / or the second functional module is received, and the vehicle parameter data in the embedded database is updated according to the update request.

[0064] In some embodiments, the system is an electronic rearview mirror system, in which the vehicle parameter data of the vehicle is stored in an embedded database, including:

[0065] The static and dynamic data of the vehicle are entered into the embedded database of the electronic rearview mirror system by using the preset vehicle parameter data storage module;

[0066] During the data entry process, data verification and error processing are performed on the vehicle parameter data, and after the data entry is completed, data backup is generated and redundantly stored;

[0067] Among them, vehicle parameter data includes static data and dynamic data. Static data includes basic information of the vehicle and specification parameters of the sensor, and dynamic data includes calibration parameters of the camera.

[0068] In some examples, first, before the vehicle leaves the factory, technicians enter the static and dynamic data of the vehicle into the embedded database of the electronic rearview mirror system using the operating interface and automation tools provided by the vehicle parameter data storage and management module. Static data contains basic vehicle information and sensor specifications that do not change frequently, such as the length, width and height of the vehicle, vehicle model, VIN code (vehicle identification number), and the serial number and performance parameters of the sensor (such as resolution, viewing angle, etc.). These data remain basically unchanged after the vehicle leaves the factory and are stored as the basic data of the electronic rearview mirror system. Dynamic data includes parameter information that may need to be adjusted or updated, such as the calibration parameters of the camera, which are used to adjust the real-time position and viewing angle of the camera to meet the image requirements under different driving conditions.

[0069] During the data entry process, the system performs strict data verification and error handling. Specifically, after the data is entered, the system automatically checks the format of the data, the integrity of the content, and the logical consistency between the data, such as ensuring that the VIN code conforms to the standard format and the specifications of the sensor meet the preset standards. If the data entry error or incompleteness is detected, the system will immediately generate a prompt message and require the technician to recalibrate the data until the data passes the verification. Data verification ensures that the entered vehicle parameter data is accurate in format and content, providing a reliable data foundation for the stable operation of the subsequent system.

[0070] After the data verification is completed, the system automatically generates a data backup and stores the data redundantly. This step increases the reliability of data storage by establishing backup and redundant copies in the database, ensuring that even if the primary stored data is lost due to equipment failure or accident, it can be restored through the backup data. This redundant storage mechanism effectively improves the data security and system stability of the electronic rearview mirror system in long-term use, and reduces the risk of performance degradation caused by data loss.

[0071] In some embodiments, the vehicle parameter data is read from the embedded database and cached according to the read and write frequency and priority of the vehicle parameter data, including:

[0072] The vehicle parameter data is read from the embedded database, and priorities are established for each data category based on the importance and read and write frequency of the vehicle parameter data; corresponding cache and processing resources are allocated to vehicle parameter data of different data categories in descending order of priority, among which cache and processing resources are allocated preferentially to high-priority vehicle parameter data.

[0073] In some examples, after the system is powered on, the vehicle parameter data processing module on the SOC (system-on-chip) side first reads the vehicle parameter data from the embedded database. The data types read include various types of vehicle parameter data, such as basic vehicle information, camera calibration parameters, sensor performance data, etc. In order to ensure the real-time responsiveness of the system, the module sets a priority for each type of data based on the importance and read and write frequency of the vehicle parameter data.

[0074] The system has established a multi-level priority system based on the usage requirements and importance of data. High-priority data is processed first in frequent calls, while low-priority data is postponed when resources are insufficient. For example, dynamic data such as camera calibration parameters in the system are of high priority because they directly affect the image display effect of the electronic rearview mirror; static data such as the basic model of the vehicle are set to medium priority due to the low update frequency; performance parameters such as the operating temperature of the sensor are set to a lower priority.

[0075] In some examples, in order to improve data processing efficiency and system response speed, this system adopts a dual optimization strategy:

[0076] 1. Establish a data caching mechanism:

[0077] The system caches various priority data to reduce the need to frequently access the database. Through the caching mechanism, high-priority data that is frequently accessed is stored in the cache first, avoiding read delays each time the database is accessed, thereby effectively reducing the frequency of database access and CPU load. This caching mechanism ensures that the system can retrieve necessary data in real time during vehicle operation.

[0078] 2. Priority scheduling algorithm:

[0079] The system integrates a priority scheduling algorithm to allocate different data cache and processing resources according to the priority of the vehicle parameter data. In specific implementation, the vehicle parameter data processing module on the SOC side will call the communication component of the Autosar AP (application platform) to distribute the read vehicle parameter data to each functional module in a publish / subscribe mode to ensure that high-priority data is processed in each functional module in a timely manner. For example, when the camera calibration parameters need to be updated, the data will be given priority to cache and processing resources to ensure the real-time requirements of the system in image display and correction. For lower priority data (static data such as vehicle model), the system allocates resources appropriately according to resource conditions to avoid low-priority data occupying too many cache resources.

[0080] Through the above dual optimization strategy, the system significantly improves the distribution efficiency and reliability of vehicle parameter data, ensures the priority processing capability of key data in the electronic rearview mirror system, and optimizes the overall resource allocation and utilization efficiency while ensuring real-time performance.

[0081] In some embodiments, the vehicle parameter data in the cache is classified, and the vehicle parameter data is distributed to the corresponding first functional module according to the data category, including:

[0082] Classify the vehicle parameter data based on its attributes to obtain data categories corresponding to different vehicle parameter data, wherein the attributes of the vehicle parameter data include static attributes and dynamic attributes;

[0083] According to the data category, the communication component is used to distribute the vehicle parameter data to the corresponding first functional module in a publishing mode or a subscription mode, so that the first functional module receives the vehicle parameter data matching the function and makes a data call on the vehicle parameter data.

[0084] In some examples, first, the system divides the vehicle parameter data into two main categories: static data and dynamic data based on its attributes. Static data includes data that remains basically unchanged during the operation of the vehicle, such as basic information about the vehicle (such as model, length, width and height) and sensor specifications (such as resolution and type). Dynamic data includes data that may change over time or in the environment, such as camera calibration parameters and display screen dynamic adjustment parameters, which usually need to be updated more frequently to adapt to different driving situations.

[0085] After completing the initial classification, the system further refines the classification of each type of vehicle parameter data according to the purpose of the data to ensure that each functional module only receives data related to its function. Specifically, the system subdivides dynamic data into subcategories such as camera calibration parameters and display calibration parameters; while static data is further subdivided into basic parameters of sensors and basic parameters of vehicles. Through this refined classification strategy, the system avoids data redundancy and improves the efficiency of data transmission and processing.

[0086] The system uses the COM component of Autosar AP to implement the data publish / subscribe mode and distributes the refined and classified vehicle parameter data to the corresponding functional modules. In an exemplary operation:

[0087] The system distributes high-frequency updated dynamic data (such as camera calibration parameters) to the electronic rearview mirror and image processing module through the publishing mode to ensure that the display system obtains the latest calibration information of the camera in real time, thereby maintaining the clarity and accuracy of the image display under different driving conditions.

[0088] Static data (such as basic vehicle information) is distributed to modules related to vehicle information through a subscription model. Since these data are not easy to change, the subscription model reduces frequent data calls and reduces the occupation of system resources.

[0089] Through the above distribution strategy, the system can not only accurately meet the data requirements of each functional module, but also effectively reduce the resource consumption during data transmission. Compared with the method of directly distributing data without classification, this strategy significantly improves the system response speed and reduces the delay of data transmission, so that the electronic rearview mirror system can respond to various data requests more quickly and stably, thereby improving the overall operation efficiency of the system.

[0090] In some embodiments, synchronizing the vehicle parameter data in the cache to the micro control unit, parsing the vehicle parameter data using the micro control unit, and distributing the parsed vehicle parameter data to the second functional module corresponding to the micro control unit includes:

[0091] The vehicle parameter data is synchronized to the microcontroller unit through the serial peripheral interface communication link, so that the microcontroller unit can parse the vehicle parameter data and verify the integrity of the parsed vehicle parameter data;

[0092] The parsed vehicle parameter data is distributed to each second functional module in the micro control unit through the inter-process communication component, so that the second functional module calls the parsed vehicle parameter data.

[0093] In some examples, this embodiment synchronizes the vehicle parameter data to the microcontroller unit (MCU), and after parsing and verifying the vehicle parameter data using the MCU, distributes the parsed data to the functional modules corresponding to the MCU to ensure the accuracy of the data and the overall performance of the system. The specific implementation process is as follows:

[0094] When the system-on-chip (SOC) side completes the preliminary processing and distribution of the vehicle parameter data, the vehicle parameter data transmission module starts the serial peripheral interface (SPI) communication link and synchronously transmits the vehicle parameter data to the MCU side. This transmission process uses the SPI protocol to ensure that data is quickly and reliably transmitted between the SOC and the MCU.

[0095] After receiving the vehicle parameter data from the SOC, the vehicle parameter data processing module on the MCU side first parses the data and converts the embedded data structure into a format that is easy for each functional module to read. After the parsing is completed, the MCU side verifies the data integrity to ensure the accuracy and integrity of the data during transmission. Integrity verification includes checking the data format, content integrity, and parameter logic, such as checking whether the camera calibration parameters meet the preset calibration range, and whether the operating temperature and performance parameters of the sensor are within the specified range.

[0096] After data parsing and verification, the vehicle parameter data processing module on the MCU side distributes the parsed vehicle parameter data to other functional modules in the MCU through the inter-process communication component in Autosar CP (classic platform). The distribution process uses the inter-module communication interface to distribute various types of data (such as camera calibration parameters, sensor basic parameters, etc.) to the corresponding functional modules.

[0097] For example, in one example, the parsed camera calibration parameters are distributed to the image processing module on the MCU side to adjust the camera viewing angle in real time to ensure the display accuracy of the electronic rearview mirror; the basic sensor parameters are sent to the relevant environmental monitoring module for subsequent sensor status monitoring and fault diagnosis.

[0098] Through this data synchronization, analysis and distribution method, the MCU can ensure that each functional module obtains real-time and accurate vehicle parameter data, thereby providing stable and reliable operation support during system operation. This process effectively improves the data processing efficiency of the electronic rearview mirror system, reduces the delay in the transmission and analysis process, and provides a guarantee for the overall performance and response speed of the system.

[0099] In some embodiments, after synchronizing the vehicle parameter data to the microcontroller unit via the serial peripheral interface communication link, the method further includes:

[0100] Monitor the synchronization signal returned by the microcontroller unit. If no synchronization signal is heard within the preset time, periodically send vehicle parameter data to the microcontroller unit until the synchronization signal is heard or the preset timeout threshold is reached. If the timeout threshold is reached, a fault alarm is generated and the fault information is recorded.

[0101] In some examples, after the vehicle parameter data is synchronized to the microcontroller unit (MCU) through the serial peripheral interface (SPI) communication link, in order to ensure the accuracy of data synchronization and the real-time performance of the system, the system further sets up synchronization signal monitoring and timeout logic. The specific implementation steps are as follows:

[0102] When the SOC (system-on-chip) side sends the vehicle parameter data to the MCU side through the SPI communication link, the SOC will monitor the synchronization signal returned by the MCU to confirm whether the data is successfully received and processed. To prevent data delays or loss during transmission, the system sets a predetermined response time window to ensure the real-time and integrity of the data synchronization process.

[0103] For example, in one example, after the data is sent, if the SOC side does not hear the synchronization confirmation signal from the MCU side within the predetermined time, the SOC side will start the periodic retransmission mechanism and repeatedly send the vehicle parameter data at a fixed time interval until any of the following conditions is met:

[0104] 1) The synchronization signal returned by the MCU is successfully received, indicating that the data has been synchronized to the MCU and received correctly;

[0105] 2) The timeout threshold set by the system is reached.

[0106] If the SOC side still does not receive the synchronization signal from the MCU when the timeout threshold is reached, the system automatically generates a fault alarm for the vehicle parameter management function and records the relevant fault information. For example, the fault information includes but is not limited to the number of retransmissions, data transmission time, module number that did not receive the signal, and other detailed information, so that the system can quickly locate the cause of the problem in subsequent maintenance and support troubleshooting and repair operations.

[0107] By setting synchronization signal monitoring and timeout logic, this embodiment realizes the reliability guarantee of the data synchronization process. Even in the case of network transmission anomalies or data interference, the system can promptly identify data synchronization failures and generate fault alarms, effectively avoiding the impact of data loss or transmission delays on system functions, thereby improving the overall stability and safety of the electronic rearview mirror system.

[0108] In some embodiments, receiving an update request sent by the first functional module and / or the second functional module, and updating the vehicle parameter data in the embedded database according to the update request includes:

[0109] Receive an update request sent by the first functional module and / or the second functional module through a preset communication component, verify the update request, and after the update request is successfully verified, adjust the vehicle parameter data in the embedded database according to the update request, and persistently store the updated vehicle parameter data in the embedded database, so that the system can call the latest vehicle parameter data in subsequent operations.

[0110] In some examples, the system can dynamically update the vehicle parameter data in the embedded database according to the update request sent by the functional module to ensure that the system always calls the latest vehicle parameter (vehicle parameter) data, improving the accuracy and real-time performance of the electronic rearview mirror system. The specific implementation process is as follows:

[0111] During the operation of the system, some vehicle parameter data may need to be updated. For example, during the dynamic calibration or static calibration operation of the camera, the calibration parameters of the camera may change and need to be updated immediately. To this end, the system has a dynamic update function for vehicle parameter data, allowing real-time modification of relevant data in the database during operation.

[0112] When the functional module on the system-on-chip (SOC) side or the microcontroller unit (MCU) side detects that the vehicle parameter data needs to be updated, the update request is first sent to the vehicle parameter data storage and management module through the preset Autosar communication component.

[0113] The AUTOSAR communication component is a modular communication interface that complies with the AUTOSAR (AUTomotive Open System ARchitecture) standard and is used to standardize the communication between modules within the vehicle, thereby ensuring that requests can be efficiently transmitted between different modules.

[0114] After receiving the update request from the functional module, the vehicle parameter data storage and management module verifies the request content. The verification step includes checking the legality of the request, the correctness of the data format, and the rationality of the data update requirements. For example, the system verifies whether the calibration parameters are within the preset range, whether the permission of the requesting module allows the update of the data type, etc. This verification step ensures the security and accuracy of data updates and prevents illegal or erroneous data requests from causing inconsistent system data.

[0115] After the update request is verified, the vehicle parameter data storage and management module adjusts the vehicle parameter data in the embedded database according to the content of the request. Subsequently, the system stores the updated data persistently, that is, writes the new data to the embedded database and ensures that it can still be saved after power failure. Persistent storage is particularly important in this system because the vehicle parameter data, as the core data set of the electronic rearview mirror function, needs to be stable and traceable to support the continuous operation of the vehicle.

[0116] For example, in the scenario of updating camera calibration parameters, after the calibration data is persistently stored, other functional modules in the system (such as the image processing module) can instantly call the latest calibration data, thereby adjusting the camera's viewing angle in real time to ensure that the display of the electronic rearview mirror meets driving needs. This update mechanism not only improves the system's dynamic response capability, but also ensures that in an environment where multiple modules work together, all modules always have consistent and synchronized access to vehicle parameter data.

[0117] Through the above method flow, this embodiment realizes the real-time update and reliable storage of vehicle parameter data, ensuring that the electronic rearview mirror system always calls the latest data, thereby improving the real-time performance, reliability and flexibility of data management of the system.

[0118] According to the technical solution provided in the embodiments of the present application, the technical solution of the present application has at least the following advantages:

[0119] 1. Improve data transmission efficiency: This technical solution realizes vehicle parameter data communication between SOC (System on Chip) and MCU (Microcontroller Unit) through SPI (Serial Peripheral Interface), simplifies the data transmission link and improves the transmission efficiency, which can effectively avoid data loss or delay and improve the performance of the electronic rearview mirror.

[0120] 2. Optimize data storage methods: This technical solution uses lightweight database technology to store vehicle parameter data. Compared with traditional file storage methods, lightweight databases are more efficient in processing small-scale data with high real-time requirements. They can realize rapid addition, deletion, modification and query operations on vehicle parameter data and reduce data redundancy.

[0121] 3. Improve data management efficiency: This technical solution divides vehicle parameter data into static data and dynamic data. Static data, such as basic information of the vehicle, can be updated and read at a lower frequency, while dynamic data, such as vehicle speed, direction and other information, can be updated and read at a higher frequency. This hierarchical data management method can further improve data management efficiency.

[0122] 4. Reduce resource usage: Since lightweight databases usually have lower resource usage, this technical solution can reduce the system's resource usage and improve the system's stability and reliability compared to traditional database technology. At the same time, it can reduce data redundancy by establishing data caching mechanisms, priority scheduling algorithms, and detailed vehicle parameter data classification strategies, thereby further optimizing data transmission efficiency.

[0123] Therefore, to sum up, this technical solution has optimized the data transmission, storage and management methods. Compared with the existing technology, it has higher efficiency, lower latency and resource occupancy, and can effectively improve the efficiency and reliability of vehicle parameter data management.

[0124] The following is an embodiment of the device of the present application, which can be used to execute the embodiment of the method of the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the method of the present application.

[0125] Figure 4 Schematic diagram of the structure of the vehicle parameter data management device provided in the embodiment of the present application. Figure 4 As shown, the vehicle parameter data management device includes:

[0126] The storage module 401 stores the vehicle parameter data of the vehicle in the embedded database in the system to form an initialized vehicle parameter data set;

[0127] The reading module 402 reads the vehicle parameter data from the embedded database in response to the power-on operation of the system, and caches the vehicle parameter data according to the reading and writing frequency and priority of the vehicle parameter data;

[0128] The distribution module 403 classifies the vehicle parameter data in the cache and distributes the vehicle parameter data to the corresponding first functional module according to the data category;

[0129] The parsing module 404 synchronizes the vehicle parameter data in the cache to the micro control unit, parses the vehicle parameter data using the micro control unit, and distributes the parsed vehicle parameter data to the second functional module corresponding to the micro control unit;

[0130] The update module 405 receives an update request sent by the first function module and / or the second function module during system operation, and updates the vehicle parameter data in the embedded database according to the update request when it is determined that the vehicle parameter data needs to be updated.

[0131] In some embodiments, Figure 4 The storage module 401 uses a preset vehicle parameter data storage module to enter the static data and dynamic data of the vehicle into the embedded database of the electronic rearview mirror system; during the data entry process, data verification and error processing are performed on the vehicle parameter data, and after the data entry is completed, a data backup is generated and redundantly stored; wherein, the vehicle parameter data includes static data and dynamic data, the static data includes the basic information of the vehicle and the specification parameters of the sensor, and the dynamic data includes the calibration parameters of the camera.

[0132] In some embodiments, Figure 4 The reading module 402 reads the vehicle parameter data from the embedded database, and establishes a priority for each data category based on the importance and reading and writing frequency of the vehicle parameter data; in descending order of priority, corresponding cache and processing resources are allocated to vehicle parameter data of different data categories, among which cache and processing resources are preferentially allocated to high-priority vehicle parameter data.

[0133] In some embodiments, Figure 4 The distribution module 403 classifies the vehicle parameter data based on its attributes to obtain data categories corresponding to different vehicle parameter data, wherein the attributes of the vehicle parameter data include static attributes and dynamic attributes; according to the data category, the communication component is used to distribute the vehicle parameter data to the corresponding first functional module in a publishing mode or a subscription mode, so that the first functional module receives the vehicle parameter data matching the function and makes a data call on the vehicle parameter data.

[0134] In some embodiments, Figure 4 The parsing module 404 synchronizes the vehicle parameter data to the micro control unit through the serial peripheral interface communication link, so that the micro control unit parses the vehicle parameter data and verifies the integrity of the parsed vehicle parameter data; distributes the parsed vehicle parameter data to each second functional module in the micro control unit through the inter-process communication component, so that the second functional module calls the parsed vehicle parameter data.

[0135] In some embodiments, Figure 4The analysis module 404 monitors the synchronization signal returned by the micro control unit. If no synchronization signal is heard within a preset time, the vehicle parameter data is periodically sent to the micro control unit until the synchronization signal is heard or a preset timeout threshold is reached. If the timeout threshold is reached, a fault alarm is generated and the fault information is recorded.

[0136] In some embodiments, Figure 4 The update module 405 receives the update request sent by the first functional module and / or the second functional module through the preset communication component, verifies the update request, and after the update request is successfully verified, adjusts the vehicle parameter data in the embedded database according to the update request, and persistently stores the updated vehicle parameter data in the embedded database, so that the system can call the latest vehicle parameter data in subsequent operations.

[0137] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0138] Figure 5 Schematic diagram of the structure of the electronic device 5 provided in the embodiment of the present application. Figure 5 As shown, the electronic device 5 of this embodiment includes: a processor 501, a memory 502, and a computer program 503 stored in the memory 502 and executable on the processor 501. When the processor 501 executes the computer program 503, the steps in the above-mentioned method embodiments are implemented. Alternatively, when the processor 501 executes the computer program 503, the functions of the modules / units in the above-mentioned device embodiments are implemented.

[0139] Exemplarily, the computer program 503 may be divided into one or more modules / units, which are stored in the memory 502 and executed by the processor 501 to complete the present application. The one or more modules / units may be a series of computer program instruction segments capable of completing specific functions, which are used to describe the execution process of the computer program 503 in the electronic device 5.

[0140] The electronic device 5 may be a desktop computer, a notebook, a PDA, a cloud server, or other electronic device. The electronic device 5 may include, but is not limited to, a processor 501 and a memory 502. Those skilled in the art will appreciate that Figure 5 It is only an example of the electronic device 5 and does not constitute a limitation of the electronic device 5. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, the electronic device may also include input and output devices, network access devices, buses, etc.

[0141] The processor 501 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0142] The memory 502 may be an internal storage unit of the electronic device 5, for example, a hard disk or memory of the electronic device 5. The memory 502 may also be an external storage device of the electronic device 5, for example, a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the electronic device 5. Further, the memory 502 may also include both an internal storage unit of the electronic device 5 and an external storage device. The memory 502 is used to store computer programs and other programs and data required by the electronic device. The memory 502 may also be used to temporarily store data that has been output or is to be output.

[0143] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

[0144] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0145] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0146] In the embodiments provided in the present application, it should be understood that the disclosed devices / computer equipment and methods can be implemented in other ways. For example, the device / computer equipment embodiments described above are only schematic. For example, the division of modules or units is only a logical function division. There may be other division methods in actual implementation. Multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0147] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0148] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0149] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. The computer program may include computer program code, which may be in source code form, object code form, executable file or some intermediate form. Computer-readable media may include: any entity or device capable of carrying computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc.

[0150] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A vehicle parameter data management method, characterized in that: include: In the system, the vehicle parameter data of the vehicle is stored in an embedded database to form an initialized vehicle parameter data set; In response to a power-on operation of the system, the vehicle parameter data is read from the embedded database, and cached according to the read and write frequency and priority of the vehicle parameter data; Classify the vehicle parameter data in the cache, and distribute the vehicle parameter data to the corresponding first functional module according to the data category; Synchronize the vehicle parameter data in the cache to the micro control unit, parse the vehicle parameter data using the micro control unit, and distribute the parsed vehicle parameter data to the second functional module corresponding to the micro control unit; During the operation of the system, when it is determined that the vehicle parameter data needs to be updated, an update request sent by the first functional module and / or the second functional module is received, and the vehicle parameter data in the embedded database is updated according to the update request.

2. The method according to claim 1, characterized in that The system is an electronic rearview mirror system, in which the vehicle parameter data of the vehicle is stored in an embedded database, including: Using a preset vehicle parameter data storage module to input the static data and dynamic data of the vehicle into an embedded database of the electronic rearview mirror system; During the data entry process, data verification and error processing are performed on the vehicle parameter data, and after the data entry is completed, data backup is generated and redundantly stored; Among them, the vehicle parameter data includes static data and dynamic data, the static data includes basic information of the vehicle and specification parameters of the sensor, and the dynamic data includes calibration parameters of the camera.

3. The method according to claim 1, characterized in that The step of reading the vehicle parameter data from the embedded database and caching the vehicle parameter data according to the read and write frequency and priority of the vehicle parameter data includes: Reading vehicle parameter data from the embedded database and establishing priorities for each data category based on the importance and read / write frequency of the vehicle parameter data; In descending order of the priority, corresponding cache and processing resources are allocated to vehicle parameter data of different data categories, wherein the cache and processing resources are preferentially allocated to high-priority vehicle parameter data.

4. The method according to claim 1, characterized in that: The method of classifying the vehicle parameter data in the cache and distributing the vehicle parameter data to the corresponding first functional module according to the data category includes: Classifying based on the attributes of the vehicle parameter data to obtain data categories corresponding to different vehicle parameter data, wherein the attributes of the vehicle parameter data include static attributes and dynamic attributes; According to the data category, the vehicle parameter data is distributed to the corresponding first functional module using a communication component in a publishing mode or a subscription mode, so that the first functional module receives the vehicle parameter data matching the function and makes a data call on the vehicle parameter data.

5. The method according to claim 1, characterized in that The step of synchronizing the vehicle parameter data in the cache to the micro control unit, parsing the vehicle parameter data using the micro control unit, and distributing the parsed vehicle parameter data to the second functional module corresponding to the micro control unit includes: The vehicle parameter data is synchronized to the micro control unit through a serial peripheral interface communication link, so that the micro control unit parses the vehicle parameter data and verifies the integrity of the parsed vehicle parameter data; The parsed vehicle parameter data is distributed to each second functional module in the micro control unit through an inter-process communication component, so that the second functional module calls the parsed vehicle parameter data.

6. The method according to claim 5, characterized in that After synchronizing the vehicle parameter data to the micro control unit via the serial peripheral interface communication link, the method further includes: The synchronization signal returned by the microcontroller unit is monitored. If the synchronization signal is not heard within a preset time, the vehicle parameter data is periodically sent to the microcontroller unit until the synchronization signal is heard or a preset timeout threshold is reached. If the timeout threshold is reached, a fault alarm is generated and the fault information is recorded.

7. The method according to claim 1, characterized in that The receiving the update request sent by the first functional module and / or the second functional module, and updating the vehicle parameter data in the embedded database according to the update request, comprises: Receive an update request sent by the first functional module and / or the second functional module through a preset communication component, verify the update request, and after the update request is successfully verified, adjust the vehicle parameter data in the embedded database according to the update request, and persistently store the updated vehicle parameter data in the embedded database, so that the system can call the latest vehicle parameter data in subsequent operations.

8. A vehicle parameter data management device, characterized in that: include: A storage module stores the vehicle parameter data of the vehicle in the embedded database in the system to form an initialized vehicle parameter data set; A reading module, in response to a power-on operation of the system, reads the vehicle parameter data from the embedded database and caches the vehicle parameter data according to a read and write frequency and priority of the vehicle parameter data; A distribution module, which classifies the vehicle parameter data in the cache and distributes the vehicle parameter data to the corresponding first functional module according to the data category; A parsing module synchronizes the vehicle parameter data in the cache to the micro control unit, parses the vehicle parameter data using the micro control unit, and distributes the parsed vehicle parameter data to the second functional module corresponding to the micro control unit; The update module receives the update request sent by the first functional module and / or the second functional module during the system operation, and updates the vehicle parameter data in the embedded database according to the update request when it is determined that the vehicle parameter data needs to be updated.

9. An electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images