Calibration data processing method, electronic device, and storage medium
Patent Information
- Application Number
- CN202610915821.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-06-24
- Publication Date
- 2026-09-11
AI Technical Summary
[0003]现有技术中，将控制器的标定数据在编译阶段统一加载至控制器标定数据空间，这种加载方法容易超出控制器的标定数据空间，造成集成软件报错
本申请提供的一种标定数据的处理方法、电子设备及存储介质，通过先根据各标定数据的长度、控制器的标定区域的总容量以及非功能板块的总容量，确定可加载目标功能板块，实现了在标定数据加载之前对标定数据进行管理，有效避免软件集成错误，提高了开发效率；并且在目标功能板块运行过程中根据标定数据在加载之前的初始值、加载之后的最新值、标定数据调度周期最大值以及标定数据的属性信息确定标定数据的优化类型，可以实现在运行过程中对标定数据的监控以及优化，并且标定数据的优化类型是基于标定数据的初始值、最新值以及标定数据的属性信息量化得到的结果，避免现有技术中依赖主观判断导致的易误删关键参数或遗漏冗余参数的问题，使得标定数据的优化的依据更准确。
Smart Images
Figure CN122734601A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of calibration data processing technology, and more specifically, to a calibration data processing method, electronic device, and storage medium. Background Technology
[0002] The functional complexity and software scale of new energy vehicle controllers are growing exponentially. Throughout the vehicle development process, various controllers, such as vehicle controllers, motor controllers, and battery management systems, need to handle a large amount of calibration data to support multi-dimensional functional verification and performance optimization. Therefore, effective management of calibration data is essential.
[0003] In existing technologies, the controller calibration data is loaded into the controller calibration data space during the compilation phase. This loading method is prone to exceeding the controller's calibration data space, causing errors in the integrated software. Furthermore, during the calibration data execution phase, the optimization of the calibration data relies on experience-based judgment, which can easily lead to problems such as accidentally deleting key parameters or omitting highly redundant parameters. Summary of the Invention
[0004] The purpose of this application is to address the shortcomings of the prior art by providing a method, electronic device, and storage medium for processing calibration data, thereby enabling the management, monitoring, early warning, and optimization of calibration data processing.
[0005] To achieve the above objectives, the technical solutions adopted in the embodiments of this application are as follows: In a first aspect, embodiments of this application provide a method for processing calibration data, the method comprising: Obtain the calibration data of each sub-functional module corresponding to each functional module in the controller, the total capacity of the calibration area of the controller, and the total capacity of the non-functional modules; The length of each calibration data is determined, and based on the length of each calibration data, the total capacity of the calibration area of the controller, and the total capacity of the non-functional modules, the loadable target functional module is determined, and the calibration data of the target functional module is loaded. During the operation of the target functional module, the initial value of the calibration data of the target functional module before loading, the latest value after loading, and the maximum value of the calibration data scheduling cycle are obtained. Based on the initial value, the latest value, the maximum value of the calibration data scheduling cycle, and the attribute information of the calibration data, the optimization type of the calibration data is determined, and the calibration data is processed according to the optimization type.
[0006] Optionally, before obtaining the calibration data of each sub-functional module corresponding to each functional module in the controller, the total capacity of the calibration area of the controller, and the total capacity of non-functional modules, the method further includes: The functional modules are divided into multiple sub-functional modules corresponding to the functional modules; Based on the type of calibration data in each functional module, determine the calibration data for each sub-functional module.
[0007] Optionally, determining the loadable target functional module based on the length of each calibration data, the total capacity of the controller's calibration area, and the total capacity of the non-functional modules includes: Based on the length of each calibration data, the total capacity of the calibration area of the controller, and the total capacity of the non-functional modules, determine the total space utilization rate of all functional modules; Based on the total space utilization rate and the multiple warning thresholds, determine whether the integration conditions are met; If so, the utilization rate of each functional module is determined based on the length of each calibration data and the total usage capacity of each functional module; Based on the usage rate of each functional module and the alarm threshold corresponding to each functional module, the target functional modules that can be loaded are determined.
[0008] Optionally, determining whether the integration conditions are met based on the total space utilization rate and the multiple warning thresholds includes: If the total space utilization rate is less than or equal to the first warning threshold among the multiple warning thresholds, then the integration condition is determined to be met. If the total space utilization rate is greater than the first warning threshold and less than the second warning threshold among the plurality of warning thresholds, then a warning message is output and the calibration data is evaluated and optimized, and the integration conditions are determined based on the evaluation and optimization results. If the total space utilization rate is greater than or equal to the second warning threshold, then it is determined that the integration conditions are not met.
[0009] Optionally, determining the total space utilization of all functional modules based on the length of each calibration data, the total capacity of the controller's calibration area, and the total capacity of the non-functional modules includes: Subtract the total capacity of the non-functional modules from the total capacity of the calibration area of the controller to obtain the total capacity of all functional modules; The amount of calibration data used in each functional module is determined based on the length of each calibration data in each sub-functional module of each functional module. The total space utilization rate of all functional modules is obtained by dividing the sum of the calibration data usage of all functional modules by the total capacity of all functional modules.
[0010] Optionally, determining the utilization rate of each functional module based on the length of each calibration data and the total usage capacity of each functional module includes: The amount of calibration data used in the functional module is determined based on the data length of each calibration data in each sub-functional module of the functional module. The usage rate of a functional module is obtained by dividing the amount of calibration data used by the total amount of data used by the functional module.
[0011] Optionally, determining the optimization type of the calibration data based on the initial value, the latest value, the maximum value of the calibration data scheduling cycle, and the attribute information of the calibration data includes: The change in the calibration data is determined based on the initial value and the latest value; Based on the change value of the calibration data, the maximum value of the calibration data scheduling cycle, and the data type size, calibration data scheduling cycle, maximum value of the calibration data type, and function activation enable value in the attribute information, determine the optimization requirement value of the calibration data; The optimization type of the calibration data is determined based on the optimization requirement value.
[0012] Optionally, determining the optimization requirement value of the calibration data based on the change value of the calibration data, the maximum value of the calibration data scheduling cycle, and the data type size, calibration data scheduling cycle, maximum value of the calibration data type, and function activation enable value in the attribute information includes: Through formula Calculate the optimized requirement value, where, , , These are the preset weighting coefficients. For data type size, To calibrate the data scheduling cycle, To determine the maximum value of a data type, To calibrate the maximum value of the data scheduling cycle, For the change data of the calibration data, This is the enable value for activating the function.
[0013] Secondly, embodiments of this application also provide a calibration data processing apparatus, the apparatus comprising: The acquisition module is used to acquire the calibration data of each sub-functional module corresponding to each functional module in the controller, the total capacity of the calibration area of the controller, and the total capacity of the non-functional modules. The determination module is used to determine the length of each calibration data, and based on the length of each calibration data, the total capacity of the calibration area of the controller, and the total capacity of the non-functional modules, determine the loadable target functional module, and load the calibration data of the target functional module; The determination module is used to obtain the initial value of the calibration data of the target functional module before loading, the latest value after loading, and the maximum value of the calibration data scheduling cycle during the operation of the target functional module, and determine the optimization type of the calibration data based on the initial value, the latest value, the maximum value of the calibration data scheduling cycle, and the attribute information of the calibration data, and process the calibration data according to the optimization type.
[0014] Optionally, the determining module is specifically used for: The functional modules are divided into multiple sub-functional modules corresponding to the functional modules; Based on the type of calibration data in each functional module, determine the calibration data for each sub-functional module.
[0015] Optionally, the determining module is specifically used for: Based on the length of each calibration data, the total capacity of the calibration area of the controller, and the total capacity of the non-functional modules, determine the total space utilization rate of all functional modules; Based on the total space utilization rate and the multiple warning thresholds, determine whether the integration conditions are met; If so, the utilization rate of each functional module is determined based on the length of each calibration data and the total usage capacity of each functional module; Based on the usage rate of each functional module and the alarm threshold corresponding to each functional module, the target functional modules that can be loaded are determined.
[0016] Optionally, the determining module is specifically used for: If the total space utilization rate is less than or equal to the first warning threshold among the multiple warning thresholds, then the integration condition is determined to be met. If the total space utilization rate is greater than the first warning threshold and less than the second warning threshold among the plurality of warning thresholds, then a warning message is output and the calibration data is evaluated and optimized, and the integration conditions are determined based on the evaluation and optimization results. If the total space utilization rate is greater than or equal to the second warning threshold, then it is determined that the integration conditions are not met.
[0017] Optionally, the determining module is specifically used for: Subtract the total capacity of the non-functional modules from the total capacity of the calibration area of the controller to obtain the total capacity of all functional modules; The amount of calibration data used in each functional module is determined based on the length of each calibration data in each sub-functional module of each functional module. The total space utilization rate of all functional modules is obtained by dividing the sum of the calibration data usage of all functional modules by the total capacity of all functional modules.
[0018] Optionally, the determining module is specifically used for: The amount of calibration data used in the functional module is determined based on the data length of each calibration data in each sub-functional module of the functional module. The usage rate of a functional module is obtained by dividing the amount of calibration data used by the total amount of data used by the functional module.
[0019] Optionally, the determining module is specifically used for: The change in the calibration data is determined based on the initial value and the latest value; Based on the change value of the calibration data, the maximum value of the calibration data scheduling cycle, and the data type size, calibration data scheduling cycle, maximum value of the calibration data type, and function activation enable value in the attribute information, determine the optimization requirement value of the calibration data; The optimization type of the calibration data is determined based on the optimization requirement value.
[0020] Optionally, the determining module is specifically used for: Through formula Calculate the optimized requirement value, where, , , These are the preset weighting coefficients. For data type size, To calibrate the data scheduling cycle, To determine the maximum value of a data type, To calibrate the maximum value of the data scheduling cycle, For the change data of the calibration data, This is the enable value for activating the function.
[0021] Thirdly, embodiments of this application also provide an electronic device, including: a processor, a memory, and a bus. The memory stores program instructions executable by the processor. When an application program runs, the processor communicates with the memory via the bus, and the processor executes the program instructions to perform the steps of the calibration data processing method described in the first aspect.
[0022] Fourthly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which is read and executes the steps of the calibration data processing method described in the first aspect.
[0023] The beneficial effects of this application are: This application provides a calibration data processing method, electronic device, and storage medium. By first determining the loadable target functional module based on the length of each calibration data, the total capacity of the controller's calibration area, and the total capacity of non-functional modules, the calibration data can be managed before loading, effectively avoiding software integration errors and improving development efficiency. Furthermore, during the operation of the target functional module, the optimization type of the calibration data is determined based on the initial value of the calibration data before loading, the latest value after loading, the maximum value of the calibration data scheduling cycle, and the attribute information of the calibration data. This enables monitoring and optimization of the calibration data during operation. Moreover, the optimization type of the calibration data is a result quantified based on the initial value, latest value, and attribute information of the calibration data, avoiding the problems of accidental deletion of key parameters or omission of redundant parameters caused by subjective judgment in the prior art, making the basis for calibration data optimization more accurate. Attached Figure Description
[0024] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.
[0025] Figure 1 A flowchart illustrating a calibration data processing method provided in an embodiment of this application; Figure 2 A flowchart illustrating another calibration data processing method provided in this application embodiment; Figure 3 A flowchart illustrating another calibration data processing method provided in this application embodiment; Figure 4 A flowchart illustrating another method for processing calibration data provided in this application embodiment; Figure 5 A schematic diagram of an apparatus for processing calibration data provided in an embodiment of this application; Figure 6 This is a structural block diagram of an electronic device provided in an embodiment of this application. Detailed Implementation
[0026] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the accompanying drawings in this application are for illustrative and descriptive purposes only and are not intended to limit the scope of protection of this application. Furthermore, it should be understood that the schematic drawings are not drawn to scale. The flowcharts used in this application illustrate operations implemented according to some embodiments of this application. It should be understood that the operations in the flowcharts may not be implemented in sequence, and steps without logical contextual relationships may be reversed or implemented simultaneously. In addition, those skilled in the art, guided by the content of this application, may add one or more other operations to the flowcharts, or remove one or more operations from the flowcharts.
[0027] Furthermore, the described embodiments are merely some, not all, of the embodiments of this application. The components of the embodiments of this application described and illustrated herein can typically be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.
[0028] It should be noted that the term "comprising" will be used in the embodiments of this application to indicate the presence of the features declared thereafter, but does not exclude the addition of other features.
[0029] Optionally, the calibration data processing method provided in this application embodiment can be applied to an electronic device, such as a mobile phone, tablet computer, laptop computer, PDA, desktop computer, or other terminal device with computing power and display function, or it can be a server. Specifically, it can be applied to applications in terminal devices, such as mobile phone applications (APP) and computer application systems.
[0030] Figure 1 A flowchart illustrating a calibration data processing method provided in this application embodiment, wherein the execution subject of the method is the aforementioned electronic device, and the method includes: S101. Obtain the calibration data of each sub-functional module corresponding to each functional module in the controller, the total capacity of the calibration area of the controller, and the total capacity of the non-functional modules.
[0031] Within each sub-functional module, the calibration data is of the same type. The length of each calibration data is a storage size in bytes, which can be determined by the calibration data type and the array dimension.
[0032] The controller is an embedded electronic control unit applicable to new energy vehicles. It can be a vehicle controller, battery management system, or motor controller, among others. The controller's internal memory is divided into multiple physically isolated logical regions. The calibration region is a fixed address space pre-allocated in non-volatile or volatile memory. This space is fixed during chip selection and hardware design. The total capacity of the controller's calibration region can, for example, use... This indicates that the total capacity of the calibrated area is the global calibrated resource availability.
[0033] The calibration area of the controller may include multiple functional modules and non-functional modules. Functional modules may be, for example, the various functional modules within the controller; exemplarily, functional modules may include a powertrain functional module, a thermal management functional module, an environmental adaptability functional module, etc. Each functional module has corresponding storage space for storing its calibration data and other data. Each functional module is divided into multiple sub-functional modules, and each sub-functional module includes at least one set of calibration data. For example, functional module A may include sub-functional module 1, sub-functional module 2, and sub-functional module 3.
[0034] The storage space of non-functional modules is the storage space occupied by calibration data in other areas besides the calibration data of the application layer. These non-functional modules may include, for example, modules for underlying calibration data and modules for device abstract calibration data.
[0035] S102. Based on the length of each calibration data, the total capacity of the controller's calibration area, and the total capacity of the non-functional modules, determine the target functional module that can be loaded, and load the calibration data of the target functional module.
[0036] Optionally, based on the length of each calibration data, the total capacity of the controller's calibration area, and the total capacity of non-functional modules, a preset method can be used to determine the total space utilization rate of all functional modules in the controller's calibration area and the utilization rate of each functional module. Then, based on the determined total space utilization rate and utilization rate of each functional module, a preset method can be used to determine the loadable target functional module. For example, when the total space utilization rate of all functional modules meets the requirements for reasonable spatial distribution, and the utilization rate of the functional module meets the requirements for reasonableness, then this functional module can be used as the target functional module, and the calibration data of this target functional module can be loaded into the software. The loadable target functional module can be one or more.
[0037] Optionally, for unloadable functional modules, the calibration data of the unloadable functional modules can be optimized until the optimized calibration data meets the loading conditions, then the functional module can be loaded.
[0038] S103. During the operation of the target functional module, obtain the initial value of the calibration data of the target functional module before loading, the latest value after loading, and the maximum value of the calibration data scheduling cycle. Based on the initial value, the latest value, the maximum value of the calibration data scheduling cycle, and the attribute information of the calibration data, determine the optimization type of the calibration data.
[0039] Optionally, the calibration data has an initial value before loading. During operation after loading, the value of the calibration data may or may not change. During the operation of the target function module, the latest value of the calibration data after loading can be obtained periodically. This latest value may refer to the value of the calibration data collected at the last moment within that period.
[0040] The attribute information of the calibration data may include data such as data type size, calibration data scheduling cycle, maximum value of calibration data type, and function activation enable value.
[0041] Optionally, after the calibration data of each target functional module is loaded into the software, the latest value of the calibration data can be periodically monitored when the software is running. The latest value of the calibration data in each period and the maximum value of the calibration data scheduling period are collected. The optimization type of the calibration data is determined based on the initial value, latest value, maximum value of the calibration data scheduling period and attribute information of the calibration data. The optimization type of the calibration data may include: immediate optimization, keeping monitoring and recommending optimization, and keeping monitoring without optimization.
[0042] In this embodiment, the target functional module to be loaded is first determined based on the length of each calibration data, the total capacity of the controller's calibration area, and the total capacity of the non-functional modules. This enables management of the calibration data before loading, effectively avoiding software integration errors and improving development efficiency. Furthermore, during the operation of the target functional module, the optimization type of the calibration data is determined based on the initial value of the calibration data before loading, the latest value after loading, the maximum value of the calibration data scheduling cycle, and the attribute information of the calibration data. This allows for monitoring and optimization of the calibration data during operation. Moreover, the optimization type of the calibration data is a result quantified based on the initial value, the latest value, and the attribute information of the calibration data, avoiding the problem of easily deleting key parameters or omitting redundant parameters due to subjective judgment in the prior art, making the basis for the optimization of the calibration data more accurate.
[0043] Figure 2 A flowchart illustrating another calibration data processing method provided in this application embodiment is shown below. Figure 2As shown, before obtaining the calibration data of each sub-functional block corresponding to each functional block in the controller, the total capacity of the controller's calibration area, and the total capacity of non-functional blocks in S101 above, the following may be included: S201. Divide the functional blocks to obtain multiple sub-functional blocks corresponding to the functional blocks.
[0044] This functional module can be any functional module within the controller. For example, this functional module could be functional module B. Each functional module can be divided into multiple sub-functional modules, such as dividing functional module B into sub-functional modules B1, B2, and B3. Each sub-functional module is used to store calibration data.
[0045] S202. Determine the calibration data for each sub-functional module based on the type of calibration data in each functional module.
[0046] Optionally, the calibration data type is the same for each sub-functional block. Each calibration data in each sub-functional block includes online calibration enable parameters and calibration value parameters. When the online calibration enable parameter is enabled, the value of the calibration value parameter is written into the calibration data, and the calibration enable parameter and calibration value parameter are stored in a memory area independent of the calibration data. For example, the online calibration enable parameter for calibration data x can be represented by Cv_x_EN_FLAG, and the calibration value parameter can be represented by Cv_x_VALUE. When calibration data x needs to be calibrated, Cv_x_EN_FLAG must be set to 1 before the value of Cv_x_VALUE can be written to calibration data x; otherwise, the value of calibration data x is provided by the original provider.
[0047] For example, the types of calibration data may include data type 1, data type 2, and data type 3. Then, the calibration data belonging to data type 1 can be stored in sub-functional module 1, and the calibration data in sub-functional module 1 will contain each calibration data of data type 1 and the data length of each calibration data. Similarly, the calibration data belonging to data type 2 can be stored in sub-functional module 2, and the calibration data in sub-functional module 2 will contain each calibration data of data type 2 and the data length of each calibration data. Likewise, the calibration data belonging to data type 3 can be stored in sub-functional module 3, and the calibration data in sub-functional module 3 will contain each calibration data of data type 3 and the data length of each calibration data. Alternatively, the calibration data belonging to data type 1 can also be stored in sub-functional module 2, and the calibration data in sub-functional module 2 will contain each calibration data of data type 1 and the data length of each calibration data.
[0048] In this embodiment, during the controller development process, the calibration data in each functional module is subdivided according to the type of calibration data to obtain the calibration data of each sub-functional module, which can realize semantic grouping management of calibration data and ensure the rationality of resource allocation.
[0049] Figure 3 A flowchart illustrating another calibration data processing method provided in this application embodiment is shown below. Figure 3 As shown, in S102 above, the target functional module that can be loaded is determined based on the length of each calibration data, the total capacity of the controller's calibration area, and the total capacity of the non-functional modules. This may include: S301. Determine the total space utilization rate of all functional modules based on the length of each calibration data, the total capacity of the controller's calibration area, and the total capacity of non-functional modules.
[0050] Optionally, the total capacity of the controller's calibration area is the total capacity of the calibration area pre-allocated to all functional modules in the controller, and the total capacity of non-functional modules is the total capacity occupied by non-functional modules of functional modules excluded from the application layer. The total space utilization rate of all functional modules in the calibration area is determined based on the data length of each calibration data in each sub-functional module. This total space utilization rate is a normalized indicator, and its value reflects the actual capacity utilization efficiency of all functional modules on the controller's calibration resources. This total utilization rate is configured as the triggering basis for subsequent resource reallocation, function addition and deletion decisions, or security compliance judgments.
[0051] S302. Determine whether the integration conditions are met based on the total space utilization rate and multiple warning thresholds.
[0052] The multiple warning thresholds may include a first warning threshold and a second warning threshold, with different warning thresholds corresponding to constraints of different dimensions. The total space utilization rate obtained in S301 is compared step by step with the set of multiple warning thresholds, and an integrated access decision is executed according to preset logical judgment rules.
[0053] If the integration conditions are met, proceed to step S303 below; if the integration conditions are not met, proceed to step S305 below.
[0054] S303. Determine the utilization rate of each functional module based on the length of each calibration data and the total usage capacity of each functional module.
[0055] The total capacity of each functional module can be planned based on the total capacity of all functional modules, with different weightings for different functional modules. For example, the total capacity of all functional modules is... If the weighting of functional module 1 is 0.4, then the total usage capacity of functional module 1 is... The weighting of functional module 2 is 0.2, therefore the total usage capacity of functional module 2 is... The weighting of functional module 3 is 0.4, therefore the total usage capacity of functional module 3 is... .
[0056] The utilization rate of each functional module refers to the space occupied by all calibration data in that functional module.
[0057] S304. Based on the usage rate of each functional module and the alarm threshold of each functional module, determine the target functional modules that can be loaded.
[0058] Alarm thresholds for different functional modules can be different or the same. The alarm thresholds for each functional module can be determined based on the weighting of each module and the total alarm threshold, such as... , where i is the identifier of the functional module, and the total alarm threshold is the first alarm threshold among the aforementioned multiple alarm thresholds.
[0059] For example, if the total alarm threshold is 70%, the weight ratio of functional module 1 is 0.4, then the alarm threshold of functional module 1 is 28%; the weight ratio of functional module 2 is 0.2, then the alarm threshold of functional module 2 is 14%; and the weight ratio of functional module 3 is 0.4, then the alarm threshold of functional module 3 is 28%.
[0060] Specifically, the usage rate of each functional module can be compared with the alarm threshold of that functional module. If the usage rate of a functional module is greater than the alarm threshold of that functional module, then that functional module is not a loadable target functional module; if the usage rate of a functional module is less than or equal to the alarm threshold of that functional module, then that functional module can be used as a loadable target functional module.
[0061] S305. Optimize the calibration data of each functional module.
[0062] Optionally, after optimizing the calibration data of each functional module, step S301 can be re-executed based on the optimized calibration data of each functional module.
[0063] In this embodiment, multi-level early warnings are provided for calibration data, which can achieve differentiated protection for different security levels.
[0064] Optionally, determining whether the integration conditions are met in step S302 above, based on the total space utilization rate and multiple warning thresholds, may include: If the total space utilization rate is less than or equal to the first warning threshold among multiple warning thresholds, then the integration condition is met; if the total space utilization rate is greater than the first warning threshold but less than the second warning threshold among multiple warning thresholds, then a warning message is output and the calibration data is evaluated and optimized; if the total space utilization rate is greater than or equal to the second warning threshold, then integration is prohibited and the calibration data is optimized. The first warning threshold is less than the second warning threshold, for example, if the first warning threshold is 70% and the second warning threshold is 85%. =0.85.
[0065] Figure 4 A flowchart illustrating another calibration data processing method provided in this application embodiment is shown below. Figure 4 As shown, in S301 above, determining the total space utilization of all functional modules based on the length of each calibration data, the total capacity of the controller's calibration area, and the total capacity of non-functional modules can include: S401. Subtract the total capacity of non-functional modules from the total capacity of the controller's calibration area to obtain the total capacity of all functional modules.
[0066] It can be done through formula The total capacity of all functional modules is calculated, where, The total capacity of the controller's calibration area. This represents the total capacity of the non-functional modules. This represents the total capacity of all functional modules.
[0067] S402. Determine the amount of calibration data used in each functional module based on the data length of each calibration data in each sub-functional module within each functional module.
[0068] Specifically, it can be done through formulas The calibration data usage of each functional module was calculated, among which, Let m be the data length of the y-th calibration data in functional block i, and m be the total number of calibration data in functional block i. This refers to the amount of calibration data used for functional module i.
[0069] S403. Sum the usage of calibration data for all functional modules and divide by the total capacity of all functional modules to obtain the total space utilization rate of all functional modules.
[0070] Specifically, it can be done through formulas The total space utilization rate of all functional modules was calculated, where, , Let be the calibration data usage for functional module i, and n be the total number of functional modules. The sum of the calibration data usage for all functional modules. P represents the total capacity of all functional modules, and P represents the total space utilization rate of all functional modules.
[0071] Optionally, determining the utilization rate of each functional module in S303 above, based on the length of each calibration data and the total usage capacity of each functional module, may include: Specifically, the calibration data usage of a functional module can be determined based on the data length of each calibration data in each sub-functional module within that functional module. The calibration data usage of a functional module is as described above. The usage rate of a functional module is obtained by dividing the calibration data usage of that functional module by the total usage of that functional module.
[0072] Optionally, determining the optimization type of the calibration data in S103 above based on the initial value, the latest value, the maximum value of the calibration data scheduling cycle, and the attribute information of the calibration data may include: Alternatively, the change in calibration data can be determined first based on the initial and latest values. Specifically, if the absolute value of the change between the initial value and the latest value of the calibration data is greater than a preset change threshold, then the change value of the calibration data... A value of 0 indicates that the latest value has changed relative to the initial value. If the absolute value of the change between the initial value and the latest value of the calibration data is less than or equal to a preset change threshold, then the change value of the calibration data is considered to be 0. A value of 1 indicates that the latest value has not changed or has changed only slightly compared to the initial value.
[0073] Based on the changes in the calibration data, the maximum value of the calibration data scheduling cycle, and the data type size, calibration data scheduling cycle, maximum value of the calibration data type, and function activation enable value in the attribute information, determine the optimization requirement value of the calibration data; determine the optimization type of the calibration data based on the optimization requirement value.
[0074] Optionally, if the optimization requirement value of the calibration data is greater than the first requirement threshold, it means that the calibration data needs to be optimized immediately, for example, the calibration data can be deleted; if the optimization requirement value of the calibration data is less than or equal to the first requirement threshold and greater than the second requirement threshold, the calibration data will be monitored and optimization will be recommended; if the optimization requirement value of the calibration data is less than or equal to the second requirement threshold, the calibration data will be monitored or no optimization is required. The first requirement threshold is greater than the second requirement threshold. For example, the first requirement threshold is 0.8 and the second requirement threshold is 0.6.
[0075] Optionally, determining the optimization requirements for the calibration data based on the changes in the calibration data, the maximum value of the calibration data scheduling cycle, and the data type size, calibration data scheduling cycle, maximum value of the calibration data type, and function activation / enabling value in the attribute information may include: Through formula Calculate the optimized requirement value, where, , , These are the preset weighting coefficients. For data type size, To calibrate the data scheduling cycle, To determine the maximum value of a data type, To calibrate the maximum value of the data scheduling cycle, To calibrate the change value of the data, This is the enable value for activating the function. The required values for the calibration data.
[0076] Among them, the change data of the calibration data This characterizes whether the value of the calibration data changes within a certain time window compared to the initial value at the start of the run; if it changes, then... =0; if there is no change, then The value is 1. ,in, To calibrate the value of the k-th test within the time window, m is the total number of detections within the time window. These are the initial values for the calibration data. To avoid errors caused by comparing floating-point numbers for equality, a threshold for relative change is used. .
[0077] This embodiment monitors the calibration data in real time and determines the optimization requirements of the calibration data based on the monitored data, thereby providing a quantitative basis for the optimization of the calibration data and making the optimization of the calibration data more accurate.
[0078] Figure 5 A schematic diagram of an apparatus for processing calibration data provided in an embodiment of this application is shown below. Figure 5 As shown, the device includes: The acquisition module 501 is used to acquire the calibration data of each sub-functional block corresponding to each functional block in the controller, the total capacity of the calibration area of the controller, and the total capacity of the non-functional blocks. The determination module 502 is used to determine the length of each calibration data, and based on the length of each calibration data, the total capacity of the calibration area of the controller, and the total capacity of the non-functional modules, determine the loadable target functional module, and load the calibration data of the target functional module; The determination module 502 is used to obtain the initial value of the calibration data of the target functional module before loading, the latest value after loading, and the maximum value of the calibration data scheduling cycle during the operation of the target functional module, and determine the optimization type of the calibration data based on the initial value, the latest value, the maximum value of the calibration data scheduling cycle, and the attribute information of the calibration data, and process the calibration data according to the optimization type.
[0079] Optionally, the determining module 502 is specifically used for: The functional modules are divided into multiple sub-functional modules corresponding to the functional modules; Based on the type of calibration data in each functional module, determine the calibration data for each sub-functional module.
[0080] Optionally, the determining module 502 is specifically used for: Based on the length of each calibration data, the total capacity of the calibration area of the controller, and the total capacity of the non-functional modules, determine the total space utilization rate of all functional modules; Based on the total space utilization rate and the multiple warning thresholds, determine whether the integration conditions are met; If so, the utilization rate of each functional module is determined based on the length of each calibration data and the total usage capacity of each functional module; Based on the usage rate of each functional module and the alarm threshold corresponding to each functional module, the target functional modules that can be loaded are determined.
[0081] Optionally, the determining module 502 is specifically used for: If the total space utilization rate is less than or equal to the first warning threshold among the multiple warning thresholds, then the integration condition is determined to be met. If the total space utilization rate is greater than the first warning threshold and less than the second warning threshold among the plurality of warning thresholds, then a warning message is output and the calibration data is evaluated and optimized, and the integration conditions are determined based on the evaluation and optimization results. If the total space utilization rate is greater than or equal to the second warning threshold, then it is determined that the integration conditions are not met.
[0082] Optionally, the determining module 502 is specifically used for: Subtract the total capacity of the non-functional modules from the total capacity of the calibration area of the controller to obtain the total capacity of all functional modules; The amount of calibration data used in each functional module is determined based on the length of each calibration data in each sub-functional module of each functional module. The total space utilization rate of all functional modules is obtained by dividing the sum of the calibration data usage of all functional modules by the total capacity of all functional modules.
[0083] Optionally, the determining module 502 is specifically used for: The amount of calibration data used in the functional module is determined based on the data length of each calibration data in each sub-functional module of the functional module. The usage rate of a functional module is obtained by dividing the amount of calibration data used by the total amount of data used by the functional module.
[0084] Optionally, the determining module 502 is specifically used for: The change in the calibration data is determined based on the initial value and the latest value; Based on the change value of the calibration data, the maximum value of the calibration data scheduling cycle, and the data type size, calibration data scheduling cycle, maximum value of the calibration data type, and function activation enable value in the attribute information, determine the optimization requirement value of the calibration data; The optimization type of the calibration data is determined based on the optimization requirement value.
[0085] Optionally, the determining module 502 is specifically used for: Through formula Calculate the optimized requirement value, where, , , These are the preset weighting coefficients. For data type size, To calibrate the data scheduling cycle, To determine the maximum value of a data type, To calibrate the maximum value of the data scheduling cycle, For the change data of the calibration data, This is the enable value for activating the function.
[0086] Figure 6 This is a structural block diagram of an electronic device 600 provided in an embodiment of this application. (See diagram below.) Figure 6 As shown, the electronic device may include: a processor 601 and a memory 602.
[0087] Optionally, a bus 603 may also be included, wherein the memory 602 is used to store machine-readable instructions executable by the processor 601. When the electronic device 600 is running, the processor 601 and the memory 602 communicate via the bus 603, and the processor 601 executes the machine-readable instructions to perform the method steps in the above method embodiments.
[0088] This application also provides a computer-readable storage medium storing a computer program, which, when run by a processor, executes the method steps described in the above-described calibration data processing method embodiments.
[0089] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems and devices described above can be referred to the corresponding processes in the method embodiments, and will not be repeated here. In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. Furthermore, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed mutual coupling or direct coupling or communication connection can be through some communication interfaces; the indirect coupling or communication connection of devices or modules can be electrical, mechanical, or other forms.
[0090] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. If the functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes: USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, optical disks, and other media capable of storing program code.
[0091] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.
Claims
1. A method for processing calibration data, characterized in that, The method includes: Obtain the calibration data of each sub-functional module corresponding to each functional module in the controller, the total capacity of the calibration area of the controller, and the total capacity of the non-functional modules; The length of each calibration data is determined, and based on the length of each calibration data, the total capacity of the calibration area of the controller, and the total capacity of the non-functional modules, the loadable target functional module is determined, and the calibration data of the target functional module is loaded. During the operation of the target functional module, the initial value of the calibration data of the target functional module before loading, the latest value after loading, and the maximum value of the calibration data scheduling cycle are obtained. Based on the initial value, the latest value, the maximum value of the calibration data scheduling cycle, and the attribute information of the calibration data, the optimization type of the calibration data is determined, and the calibration data is processed according to the optimization type.
2. The method for processing calibration data according to claim 1, characterized in that, Before acquiring the calibration data of each sub-functional module corresponding to each functional module in the controller, the total capacity of the calibration area of the controller, and the total capacity of non-functional modules, the process further includes: The functional modules are divided into multiple sub-functional modules corresponding to the functional modules; Based on the type of calibration data in each functional module, determine the calibration data for each sub-functional module.
3. The method for processing calibration data according to claim 1, characterized in that, The step of determining the loadable target functional module based on the length of each calibration data, the total capacity of the controller's calibration area, and the total capacity of the non-functional modules includes: Based on the length of each calibration data, the total capacity of the calibration area of the controller, and the total capacity of the non-functional modules, determine the total space utilization rate of all functional modules; Based on the total space utilization rate and multiple warning thresholds, determine whether the integration conditions are met; If so, the utilization rate of each functional module is determined based on the length of each calibration data and the total usage capacity of each functional module; Based on the usage rate of each functional module and the alarm threshold corresponding to each functional module, the target functional modules that can be loaded are determined.
4. The method according to claim 3, characterized in that, The step of determining whether the integration conditions are met based on the total space utilization rate and the multiple warning thresholds includes: If the total space utilization rate is less than or equal to the first warning threshold among the multiple warning thresholds, then the integration condition is determined to be met. If the total space utilization rate is greater than the first warning threshold and less than the second warning threshold among the plurality of warning thresholds, then a warning message is output and the calibration data is evaluated and optimized, and the integration conditions are determined based on the evaluation and optimization results. If the total space utilization rate is greater than or equal to the second warning threshold, then it is determined that the integration conditions are not met.
5. The method for processing calibration data according to claim 3, characterized in that, The determination of the total space utilization rate of all functional modules based on the length of each calibration data, the total capacity of the controller's calibration area, and the total capacity of the non-functional modules includes: Subtract the total capacity of the non-functional modules from the total capacity of the calibration area of the controller to obtain the total capacity of all functional modules; The amount of calibration data used in each functional module is determined based on the length of each calibration data in each sub-functional module of each functional module. The total space utilization rate of all functional modules is obtained by dividing the sum of the calibration data usage of all functional modules by the total capacity of all functional modules.
6. The method for processing calibration data according to claim 3, characterized in that, The step of determining the utilization rate of each functional module based on the length of each calibration data and the total usage capacity of each functional module includes: The amount of calibration data used in the functional module is determined based on the data length of each calibration data in each sub-functional module of the functional module. The usage rate of a functional module is obtained by dividing the amount of calibration data used by the total amount of data used by the functional module.
7. The method for processing calibration data according to claim 1, characterized in that, The step of determining the optimization type of the calibration data based on the initial value, the latest value, the maximum value of the calibration data scheduling cycle, and the attribute information of the calibration data includes: The change in the calibration data is determined based on the initial value and the latest value; Based on the change value of the calibration data, the maximum value of the calibration data scheduling cycle, and the data type size, calibration data scheduling cycle, maximum value of the calibration data type, and function activation enable value in the attribute information, determine the optimization requirement value of the calibration data; The optimization type of the calibration data is determined based on the optimization requirement value.
8. The method for processing calibration data according to claim 6, characterized in that, The step of determining the optimization requirement value of the calibration data based on the change value of the calibration data, the maximum value of the calibration data scheduling cycle, and the data type size, calibration data scheduling cycle, maximum value of the calibration data type, and function activation enable value in the attribute information includes: Through formula Calculate the optimized requirement value, where, , , These are the preset weighting coefficients. For data type size, To calibrate the data scheduling cycle, To determine the maximum value of a data type, To calibrate the maximum value of the data scheduling cycle, For the change data of the calibration data, This is the enable value for activating the function.
9. An electronic device, characterized in that, The device includes a memory and a processor, wherein the memory stores a computer program executable by the processor, and the processor executes the computer program to implement the steps of the calibration data processing method according to any one of claims 1-8.
10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, performs the steps of the calibration data processing method as described in any one of claims 1-8.