Method and apparatus for processing configuration of device power supply domain in vehicle
By acquiring the target parameter data of the device to be evaluated in the vehicle, and using the migration threshold rule base and power supply domain configuration table, the power supply domain configuration is automatically corrected, which solves the problem of inefficient consistency verification caused by reliance on human experience in the existing technology, and realizes efficient power supply domain data correction and consistency verification.
Patent Information
- Application Number
- CN202611247969.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-17
- Publication Date
- 2026-11-17
AI Technical Summary
In existing technologies, 48V device migration verification relies on manual experience, resulting in low efficiency in power supply domain configuration consistency verification and an inability to quickly correct problematic devices.
By acquiring the target parameter data of the equipment to be evaluated in the vehicle, using the migration threshold rule base and power supply domain configuration table, the current and theoretical power supply domain data are determined, and correction suggestions are generated based on the difference risk data to automatically correct the power supply domain configuration.
It improves the efficiency and consistency of power supply domain configuration correction, avoids errors from manual judgment, and ensures that correction actions have clear basis and traceability.
Smart Images

Figure CN123104555A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of vehicle technology, and in particular to a method and apparatus for processing the power supply domain configuration of equipment in a vehicle. Background Technology
[0002] With the rapid development of intelligent electric vehicle technology, the current 12V power supply system is limited by power bottlenecks, complex wiring harness layout, carpet bulging issues, and difficulties in vias. It is no longer able to meet the needs of high-power chassis actuators, thermal management equipment, high-power comfort equipment, and intelligent power distribution systems. Therefore, upgrading to 48V can significantly reduce the weight of the wiring harness, improve power transmission efficiency, and enable more flexible intelligent power distribution management.
[0003] Currently, in the industry, the verification of 48V device migration mainly relies on manual experience, which requires manually calculating the appropriate power supply domain based on the device's master data and comparing it with the power supply domain configuration.
[0004] However, the above method is prone to human error, which can lead to low consistency verification efficiency and make it difficult to quickly correct the power domain configuration of devices with consistency problems. Summary of the Invention
[0005] This application provides a method and apparatus for processing the power supply domain configuration of equipment in a vehicle, so as to improve the efficiency of correcting the power supply domain configuration of equipment.
[0006] In a first aspect, embodiments of this application provide a method for configuring the power supply domain of devices in a vehicle, including:
[0007] Obtain target parameter data for the equipment to be evaluated in the vehicle;
[0008] Based on the target parameter data, the current power supply domain data and theoretical power supply domain data of the device to be evaluated are determined;
[0009] Based on the theoretical power supply domain data and the current power supply domain data, the power supply domain data of the device to be evaluated is corrected.
[0010] In one or more embodiments, determining the current power supply domain data and theoretical power supply domain data of the device to be evaluated based on the target parameter data includes:
[0011] Based on the target parameter data and the migration threshold rule base, the theoretical power supply domain data suitable for the device to be evaluated is determined. The migration threshold rule base is determined based on power thresholds and / or security levels.
[0012] Based on the device identifier to be evaluated and the power supply domain configuration table in the target parameter data, the current power supply domain data of the device to be evaluated is determined. The power supply domain configuration table records different device identifiers and the power supply domain data to which each device identifier belongs.
[0013] In one or more embodiments, the step of correcting the power supply domain data of the device to be evaluated based on the theoretical power supply domain data and the current power supply domain data includes:
[0014] Based on the theoretical power supply domain data and the current power supply domain data, determine the difference risk data of the device to be evaluated;
[0015] Based on the aforementioned differential risk data, the power supply domain data of the device to be evaluated is corrected.
[0016] In one or more embodiments, determining the difference risk data of the device to be evaluated based on the theoretical power supply domain data and the current power supply domain data includes:
[0017] By comparing the theoretical power supply domain data and the current power supply domain data, a list of target difference objects is obtained;
[0018] Based on the target difference object list and the preset risk assessment strategy, the difference risk data of the equipment to be assessed is obtained. The risk assessment strategy is determined based on the first impact of equipment failure on vehicle safety and the second impact of equipment power on the carrying capacity of the power supply network.
[0019] In one or more embodiments, the step of correcting the power supply domain data of the device to be evaluated based on the differential risk data includes:
[0020] Based on the target risk level indicated by the differential risk data, a target correction recommendation is determined in the risk level strategy, which records different risk levels and the correction recommendation corresponding to each risk level.
[0021] Based on the target correction suggestion, modify the current power supply domain data corresponding to the device to be evaluated in the power supply domain configuration table. The power supply domain configuration table records different device identifiers and the power supply domain data to which each device identifier belongs.
[0022] In one or more embodiments, determining a target correction recommendation in a risk level strategy based on the target risk level indicated by the differential risk data includes:
[0023] If the target risk level indicates high risk, then the first correction suggestion is determined as the target correction suggestion. The first correction suggestion is used to indicate that the correction process is of the highest priority and the correction must be performed immediately.
[0024] If the target risk level indicates risk, then the second correction suggestion is determined as the target correction suggestion. The second correction suggestion is used to indicate that the correction process is of high priority and it is recommended to correct it in the next iteration.
[0025] If the target risk level indicates low risk, then the third revision suggestion will be determined as the target revision suggestion. The third revision suggestion is used to indicate that the revision process is of regular priority and is recommended to be included in the planning of subsequent versions.
[0026] In one or more embodiments, the target parameter data includes: device identifier, power parameters, security level, and device type;
[0027] The corresponding power supply domain data includes: power supply domain, migration priority level, and associated DC-DC conversion scheme.
[0028] Secondly, embodiments of this application provide a processing apparatus for configuring the power supply domain of devices in a vehicle, comprising:
[0029] The acquisition module is used to acquire target parameter data of the equipment to be evaluated in the vehicle.
[0030] The determination module is used to determine the current power supply domain data and theoretical power supply domain data of the device to be evaluated based on the target parameter data.
[0031] The processing module is used to correct the power supply domain data of the device to be evaluated based on the theoretical power supply domain data and the current power supply domain data.
[0032] In one or more embodiments, the determining module determines the current power supply domain data and theoretical power supply domain data of the device to be evaluated based on the target parameter data, specifically for:
[0033] Based on the target parameter data and the migration threshold rule base, the theoretical power supply domain data suitable for the device to be evaluated is determined. The migration threshold rule base is determined based on power thresholds and / or security levels.
[0034] Based on the device identifier to be evaluated and the power supply domain configuration table in the target parameter data, the current power supply domain data of the device to be evaluated is determined. The power supply domain configuration table records different device identifiers and the power supply domain data to which each device identifier belongs.
[0035] In one or more embodiments, the processing module corrects the power supply domain data of the device to be evaluated based on the theoretical power supply domain data and the current power supply domain data, specifically for:
[0036] Based on the theoretical power supply domain data and the current power supply domain data, determine the difference risk data of the device to be evaluated;
[0037] Based on the aforementioned differential risk data, the power supply domain data of the device to be evaluated is corrected.
[0038] In one or more embodiments, the processing module determines the difference risk data of the device to be evaluated based on the theoretical power supply domain data and the current power supply domain data, specifically for:
[0039] By comparing the theoretical power supply domain data and the current power supply domain data, a list of target difference objects is obtained;
[0040] Based on the target difference object list and the preset risk assessment strategy, the difference risk data of the equipment to be assessed is obtained. The risk assessment strategy is determined based on the first impact of equipment failure on vehicle safety and the second impact of equipment power on the carrying capacity of the power supply network.
[0041] In one or more embodiments, the processing module corrects the power supply domain data of the device to be evaluated based on the difference risk data, specifically for:
[0042] Based on the target risk level indicated by the differential risk data, a target correction recommendation is determined in the risk level strategy, which records different risk levels and the correction recommendation corresponding to each risk level.
[0043] Based on the target correction suggestion, modify the current power supply domain data corresponding to the device to be evaluated in the power supply domain configuration table. The power supply domain configuration table records different device identifiers and the power supply domain data to which each device identifier belongs.
[0044] In one or more embodiments, the processing module determines a target correction suggestion in the risk level strategy based on the target risk level indicated by the differential risk data, specifically for:
[0045] If the target risk level indicates high risk, then the first correction suggestion is determined as the target correction suggestion. The first correction suggestion is used to indicate that the correction process is of the highest priority and the correction must be performed immediately.
[0046] If the target risk level indicates risk, then the second correction suggestion is determined as the target correction suggestion. The second correction suggestion is used to indicate that the correction process is of high priority and it is recommended to correct it in the next iteration.
[0047] If the target risk level indicates low risk, then the third revision suggestion will be determined as the target revision suggestion. The third revision suggestion is used to indicate that the revision process is of regular priority and is recommended to be included in the planning of subsequent versions.
[0048] In one or more embodiments, the target parameter data includes: device identifier, power parameters, security level, and device type;
[0049] The corresponding power supply domain data includes: power supply domain, migration priority level, and associated DC-DC conversion scheme.
[0050] Thirdly, embodiments of this application provide an electronic device, including: a memory and a processor;
[0051] The memory stores computer-executed instructions;
[0052] The processor executes computer execution instructions stored in the memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above.
[0053] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect and / or various possible implementations of the first aspect.
[0054] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the first aspect and / or various possible implementations of the first aspect.
[0055] This application provides a method and apparatus for processing the power supply domain configuration of equipment in a vehicle. The method acquires target parameter data of the equipment to be evaluated in the vehicle; determines the current power supply domain data and theoretical power supply domain data of the equipment to be evaluated based on the target parameter data; and corrects the power supply domain data of the equipment to be evaluated based on the theoretical power supply domain data and the current power supply domain data. This technical solution establishes a standardized data foundation at the single-device granularity for all subsequent judgment operations by acquiring the target parameter data of the equipment to be evaluated in the vehicle. Then, by determining the current power supply domain data and theoretical power supply domain data based on the same set of target parameter data, both the actual current configuration and the expected baseline configuration of the equipment originate from the same initial input, ensuring the reliability of the data source for comparison. Furthermore, by correcting the power supply domain data of the equipment to be evaluated based on the theoretical power supply domain data and the current power supply domain data, the theoretical calculation results are used as the correction benchmark to directly drive the update of the current configuration. This provides a clear and traceable basis for the correction action rather than relying on manual experience judgment, thereby improving the verification and correction of the consistency of the power supply domain data. Attached Figure Description
[0056] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.
[0057] Figure 1 This is a schematic diagram of the structure of a processing system for configuring the power supply domain of devices in a vehicle, provided in an embodiment of this application.
[0058] Figure 2 A flowchart illustrating the processing method for configuring the power supply domain of devices in a vehicle according to embodiments of this application. Figure 1 ;
[0059] Figure 3 A flowchart illustrating the processing method for configuring the power supply domain of devices in a vehicle according to embodiments of this application. Figure 2 ;
[0060] Figure 4 A flowchart illustrating the processing method for configuring the power supply domain of devices in a vehicle according to embodiments of this application. Figure 3 ;
[0061] Figure 5 A flowchart illustrating the processing method for configuring the power supply domain of devices in a vehicle according to embodiments of this application. Figure 4 ;
[0062] Figure 6 A flowchart illustrating the processing method for configuring the power supply domain of devices in a vehicle according to embodiments of this application. Figure 5 ;
[0063] Figure 7 A schematic diagram of the structure of a processing device configured in the power supply domain of a vehicle according to an embodiment of this application;
[0064] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.
[0065] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation
[0066] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.
[0067] The 48V power supply system has evolved from a simple local high-power supply to a crucial infrastructure for the entire vehicle's electronic and electrical architecture. Given the persistent power bottlenecks, complex wiring harness layouts, carpet bulges, and difficulties with vias in 12V systems, upgrading to 48V can simultaneously improve wiring harness weight reduction, power capacity, intelligent power distribution, and the responsiveness of high-power actuators.
[0068] With the gradual introduction of centralized intelligent power distribution (Zone Control Unit, ZCU), battery management system (BMS) / on-board charger (OBC), distributed DC-DC converter (DCDC), thermal management, high-power chassis, and high-power comfort equipment, it is necessary to solidify the system architecture, migration threshold, control strategy, safety closed loop, and continuous evolution mechanism into implementable forms. Only after the migration threshold and mapping model have been verified for consistency can they support mass production configuration and after-sales service.
[0069] The current solutions rely primarily on manual experience or partially automated tools for verifying the migration of 48V devices, which has significant shortcomings, such as:
[0070] 1) Manual verification: Engineers need to manually compare the device master data, threshold rules and power supply domain configuration table, and rely on experience to judge the rationality of the migration results;
[0071] This process is inefficient and prone to configuration errors due to human error.
[0072] 2) Partial automation tools: Some systems use scripts or simple rule engines to compare certain fields;
[0073] However, the lack of systematic analysis of migration range, power supply domain mapping, and risk level makes it impossible to cover all equipment or incremental change scenarios.
[0074] 3) Lack of version management: The existing solution does not establish a mechanism to associate the difference list with version assets, which makes it difficult to trace the disconnect between migration results and configuration templates, and the correction suggestions lack a closed-loop verification path.
[0075] Accordingly, in response to the technical problems existing in the prior art, the technical concept of this application is as follows: If the inherent attributes of the device to be evaluated can be used as a unified input, the theoretical power supply domain data of the device to be evaluated can be directly derived at the theoretical level; secondly, based on the identifier of the device to be evaluated, the current power supply domain data can be directly determined; then comparing the two, and using the comparison result to directly drive the synchronous processing of the power supply domain data, can achieve rapid synchronous processing of inconsistent power supply domain data of the device to be evaluated, and avoid the occurrence of human inaccuracies.
[0076] Based on the above technical concept. Figure 1 This is a schematic diagram of the structure of the processing system for the power supply domain configuration of the equipment in the vehicle provided in the embodiments of this application, as shown below. Figure 1 As shown, the processing system configured in the power supply domain of the vehicle includes:
[0077] The database includes a low-voltage equipment database, a migration threshold rule base, a power supply domain configuration table, a consistency recalculation controller, a difference risk classifier, a power supply template reference library, a DC-DC configuration reference library, and a difference list and regression results.
[0078] Accordingly, one implementation could be as follows: read the device master data from the low-voltage device database, read the threshold rules from the migration threshold rule library, and read the power supply domain configuration table; recalculate the migration interval and power supply domain mapping results; compare the consistency between the current results and the target configuration; perform risk classification on the difference objects; then generate correction suggestions and perform regression verification; and finally archive the difference list and regression results.
[0079] It should be understood that the above embodiments are only a brief introduction to this solution, and the implementation details of this solution will be described in detail in the following embodiments.
[0080] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.
[0081] It should be understood that this method is applied to electronic devices.
[0082] Figure 2 A flowchart illustrating the processing method for configuring the power supply domain of devices in a vehicle according to embodiments of this application. Figure 1 ,like Figure 2 As shown, the method includes:
[0083] Step 21: Obtain the target parameter data of the equipment to be evaluated in the vehicle;
[0084] In this step, the identifier of the device to be evaluated can be read as the primary key for retrieval through the device master data platform or the configuration management database of the vehicle's electronic and electrical architecture. Based on the preset joint acquisition rules, key attributes such as power parameters, safety level and equipment type are extracted in parallel or in stages from different data sources and recorded as the target parameter data of the device to be evaluated.
[0085] In other words, the target parameter data includes: device identification, power parameters, safety level, and device type.
[0086] For example, different data sources can be BOM systems, diagnostic databases, functional safety documents; safety levels can be ASIL levels; power parameters can be continuous power, peak power, etc.; and device types can be actuators, sensors, controllers, etc.
[0087] Step 22: Based on the target parameter data, determine the current power supply domain data and theoretical power supply domain data of the equipment to be evaluated;
[0088] In this step, based on the target parameter data, two different power supply domain data describing the power supply status of the same device to be evaluated are obtained: Channel 1 is the theoretical calculation channel, which receives parameters (such as power parameters, safety level, and device type) from the target parameter data as input; Channel 2 is the current status query channel, which receives the device identifier from the target parameter data as input.
[0089] These two types of power supply domain data can be generated by calling different internal processing logics and information carriers respectively. For possible implementations, please refer to the embodiments of steps 31 and 32 below.
[0090] It should be understood that the execution order of the two paths is not important; they can be executed sequentially or in parallel. The two sets of data output will be uniformly converged into the input buffer of the consistency comparator to await subsequent comparison processing.
[0091] Optionally, the corresponding power supply domain data includes: power supply domain, migration priority level, and associated DC-DC conversion scheme.
[0092] Step 23: Correct the power supply domain data of the equipment to be evaluated based on the theoretical power supply domain data and the current power supply domain data.
[0093] In this step, the current power supply domain data and the theoretical power supply domain data of the device to be evaluated are read and compared. Based on the comparison results, the power supply domain data is synchronized, i.e., consistency verification is performed.
[0094] Optionally, you can determine whether the current power supply domain data is NULL:
[0095] If NULL, the device to be evaluated is directly marked as having a configuration missing difference, and subsequent consistency comparisons are skipped, and the process proceeds directly to risk classification. If not NULL, the theoretical power supply domain value is compared with the current power supply domain value. If the two are equal (e.g., both are 48V or both are 12V), the device to be evaluated is determined to be consistent, and no difference record is generated.
[0096] All equipment in the vehicle can be judged using a consistent method based on the equipment being evaluated.
[0097] Furthermore, if it is determined that there is a difference in the equipment to be evaluated, the equipment identifier, theoretical power supply threshold, current power supply threshold, equipment type, and security level of the equipment to be evaluated are combined into a difference record and written into the target difference object list.
[0098] After traversing the complete dataset to be compared, a complete list of target discrepancies is obtained. Subsequently, a risk classifier thread is started to calculate the risk level of each discrepancy record in the list, generating discrepancy risk data. The discrepancy risk data output by the risk classifier includes the device identifier and the corresponding risk level field.
[0099] The method for processing the power supply domain configuration of equipment in a vehicle provided in this application involves: acquiring target parameter data of the equipment to be evaluated in the vehicle; determining the current power supply domain data and theoretical power supply domain data of the equipment to be evaluated based on the target parameter data; and correcting the power supply domain data of the equipment to be evaluated based on the theoretical power supply domain data and the current power supply domain data. This technical solution establishes a standardized data foundation at the single-device granularity for all subsequent judgment operations by acquiring the target parameter data of the equipment to be evaluated in the vehicle; then, by determining the current power supply domain data and theoretical power supply domain data based on the same set of target parameter data, both the actual current configuration and the expected baseline configuration of the equipment originate from the same initial input, ensuring the reliability of the data source for comparison; and finally, by correcting the power supply domain data of the equipment to be evaluated based on the theoretical power supply domain data and the current power supply domain data, the theoretical calculation results are used as the correction benchmark to directly drive the update of the current configuration, giving the correction action a clear and traceable basis rather than relying on manual experience judgment, thereby improving the verification and synchronization of power supply domain data consistency.
[0100] Based on the above embodiments, Figure 3 A flowchart illustrating the processing method for configuring the power supply domain of devices in a vehicle according to embodiments of this application. Figure 2 ,like Figure 3 As shown, step 22 may include:
[0101] Step 31: Based on the target parameter data and the migration threshold rule base, determine the theoretical power supply domain data that the device to be evaluated is compatible with;
[0102] The migration threshold rule base is determined based on power thresholds and / or security levels;
[0103] In this step, the level calculation unit set in the electronic device loads a migration threshold rule base. This migration threshold rule base is stored in memory in the form of a lookup table, and its primary key is composed of a power range identifier and a security level identifier.
[0104] Based on the power parameter and safety level fields in the target parameter data, the level recalculator first determines which preset power range the device's power parameter value falls into (e.g., less than 100W, 100W to 500W, greater than 500W), and obtains the power range identifier; at the same time, it directly reads the safety level identifier of the device to be evaluated. The level recalculator combines the power range identifier and the safety level identifier into a lookup key and performs an accurate match in the migration threshold rule base lookup table.
[0105] If the migration threshold rule base returns a migration determination result of 48V, the level calculation unit will output a theoretical power supply domain value of 48V; if the returned result is 12V, the output will be 12V.
[0106] For example, a device with a continuous power of 600W and a safety level of ASIL C has a power of more than 500W. The combination key is more than 500W + ASIL C. The result found in the migration threshold rule base is 48V. Therefore, the theoretical power supply domain of the device to be evaluated is determined to be 48V.
[0107] Step 32: Based on the device identifier and power supply domain configuration table in the target parameter data, determine the current power supply domain data of the device to be evaluated;
[0108] The power supply domain configuration table contains different device identifiers and the power supply domain data to which each device identifier belongs.
[0109] In this step, the field of the device identifier to be evaluated is extracted from the target parameter data, and the query operation is performed in the power supply domain configuration table using the device identifier to be evaluated as the query primary key.
[0110] The power supply domain configuration table is a relational data table containing: a device identifier primary key column, a power supply domain column, a DC-DC scheme column, and a version validity range column. The query condition is set to the device identifier being equal to the identifier of the device being queried. If the query result set is not empty, the value of the power supply domain column (12V or 48V) is read from the result set as the current power supply domain data for that device.
[0111] If the query result set is empty, meaning there is no configuration record for the device identifier in the configuration table, or if a record exists but its version validity period does not cover the current time, the system determines that the current power supply domain data for the device is missing. The system sets the current power supply domain data to NULL and records a configuration missing event in the log, along with the device identifier and query timestamp. The system then encapsulates the retrieved current power supply domain value or NULL value along with the device identifier and outputs it to the corresponding field in the data container to be compared.
[0112] It should be understood that the above examples, which are based on current power supply domain data and theoretical power supply domain data, are only examples of the power supply domain. In reality, they may also include migration priority levels and associated DC-DC conversion schemes, etc.
[0113] The method for configuring the power supply domain of equipment in a vehicle provided in this application determines the theoretical power supply domain data suitable for the device to be evaluated based on target parameter data and a migration threshold rule base. The migration threshold rule base is determined based on power thresholds and / or safety levels. Based on the device identifier and power supply domain configuration table in the target parameter data, the current power supply domain data of the device to be evaluated is determined. The power supply domain configuration table records different device identifiers and the power supply domain data to which each device identifier belongs. This technical solution, by inputting the target parameter data of the device to be evaluated into the migration threshold rule base, can independently calculate the theoretical power supply domain affiliation of the device to be evaluated, independent of any existing configuration template, providing an objective benchmark reference unaffected by the current configuration table status for subsequent verification. Simultaneously, by querying the power supply domain configuration table using the device identifier as a unique index, the actual recorded and effective power supply domain data of the device to be evaluated in the current engineering template can be accurately obtained, ultimately ensuring the accuracy of the source of the current and theoretical power supply domain data of the device to be evaluated.
[0114] Based on the above embodiments, Figure 4 A flowchart illustrating the processing method for configuring the power supply domain of devices in a vehicle according to embodiments of this application. Figure 3 ,like Figure 4 As shown, step 23 may include:
[0115] Step 41: Based on the theoretical power supply domain data and the current power supply domain data, determine the difference risk data of the equipment to be evaluated;
[0116] In this step, for the device to be evaluated, its corresponding theoretical power supply domain data and current power supply domain data are compared. If the theoretical power supply domain value is equal to the current power supply domain value, it is determined that there is no difference in the device to be evaluated; if the two are not equal, it is determined that there is a difference in the power supply domain configuration of the device to be evaluated.
[0117] For equipment identified as having discrepancies, discrepancy risk data is generated based on the equipment identifier, theoretical power supply threshold, current power supply threshold, equipment type, and security level.
[0118] Optionally, one possible implementation of step 41 could be:
[0119] Step 1: Compare the theoretical power supply domain data with the current power supply domain data to obtain a list of target discrepancies.
[0120] In this implementation, the theoretical power supply domain value and the current power supply domain value of the device to be evaluated are read, and the theoretical power supply domain value and the current power supply domain value are compared as equivalent.
[0121] If the two are equal, no list record will be generated, and the processing flow for the device to be evaluated will be terminated; if the two are not equal, a new difference object record will be created, the device identifier of the device to be evaluated will be filled into the object number field, the theoretical power supply domain value will be filled into the theoretical affiliation field, the current power supply domain value will be filled into the current affiliation field, and the record will be appended to the target difference object list.
[0122] It should be understood that: based on the specific content of the power supply domain data, comparisons can be made separately, and the number of comparison items is the same as the number of data items in the power supply domain data. Here, only the power supply domain value is used as an example.
[0123] Step 2: Based on the target difference object list and the preset risk assessment strategy, obtain the difference risk data of the equipment to be assessed;
[0124] The risk assessment strategy is determined based on the primary impact of equipment failure on vehicle safety and the secondary impact of equipment power on the carrying capacity of the power supply network.
[0125] In this implementation, records about the device to be evaluated are read from the target difference object list: if the list is empty, the difference risk data is empty and no subsequent steps are performed; if the list contains a difference record about the device to be evaluated, the device identifier of the device to be evaluated is extracted from the record, and the safety level and power parameters (e.g., continuous power value) of the device to be evaluated are extracted from the obtained target parameter data.
[0126] The safety level is used as the first dimension to input into the risk assessment strategy to determine the first level of impact (high, medium, or low) of the failure on vehicle safety; the power parameter is used as the second dimension to input into the risk assessment strategy, and combined with the remaining capacity of the current power supply network, the second level of impact (high, medium, or low) of the power of the device on the carrying capacity of the power supply network is determined.
[0127] Furthermore, the first and second impact levels can be used as row and column coordinates to locate the corresponding risk level cell in the preset two-dimensional risk assessment matrix, read the risk level value (high risk, medium risk, or low risk) in the cell, and associate the device identifier with the risk level value as the differential risk data of the device to be assessed.
[0128] Optionally, the weighting ratio of safety impact to power supply impact can be dynamically adjusted during the risk assessment process. For example, during the prototype development phase, the weight of the first level of impact can be set to 80% and the weight of the second level of impact to 20%, while during the mass production phase, the weighting can be adjusted to 60% for the first level of impact and 40% for the second level of impact to adapt to the priority requirements of different development stages.
[0129] Optionally, when archiving the list of difference objects (i.e., the difference list) and the correction results, the difference records can be bound to the current vehicle configuration version and stored in a versioned baseline library. For example, the corrected power supply domain configuration table and synchronization processing logs need to be associated with this version number. In subsequent version iterations, historical baseline library data can be called through the version management interface to ensure the traceability of configuration changes.
[0130] Step 42: Correct the power supply domain data of the equipment to be evaluated based on the difference risk data.
[0131] In this step, the theoretical power supply domain value from the obtained differential risk data is taken, and the configuration template and other data in the current power supply domain associated with the device to be evaluated are updated.
[0132] For example, using the device identifier of the device to be evaluated as the query condition, the configuration record row corresponding to the device to be evaluated is located in the power supply domain configuration table, and the power supply domain field value in the record row is modified to the theoretical power supply domain value.
[0133] Simultaneously, based on changes in the theoretical power supply domain value, the reference field of the DC-DC conversion scheme associated with the device is updated in a coordinated manner: if the theoretical power supply domain value is 48V, the DC-DC scheme reference is pointed to the 48V dedicated conversion scheme; if the theoretical power supply domain value is 12V, the DC-DC scheme reference is pointed to the original 12V scheme or the 48V scheme reference is removed.
[0134] After updating the configuration table, the updated configuration record is compared with the original configuration record before the correction, generating a synchronization processing log. This log includes the device identifier, the power supply domain value before the correction, the power supply domain value after the correction, the operation timestamp, and the execution status. The corrected configuration record and the synchronization processing log are then written into the baseline library and stored as versioned assets.
[0135] After processing all discrepancy records in the discrepancy risk data, a summary report of the synchronization processing results is output to the external system. The report lists the number of devices that have been synchronized and the comparison information of each device before and after the correction.
[0136] Optionally, one possible implementation of step 42 could be:
[0137] Step 1: Based on the target risk level indicated by the differential risk data, determine the target revision recommendations in the risk level strategy;
[0138] The risk level strategy includes different risk levels and corresponding correction suggestions for each risk level.
[0139] In this implementation, the target risk level string (high risk, medium risk, or low risk) corresponding to the device to be evaluated is extracted from the differential risk data. This risk level string is then used as the query key to access the pre-loaded risk level strategy table in memory.
[0140] The risk level strategy table is a key-value pair structure with different pre-defined mapping records. Then, based on the queried mapping results, the corresponding correction suggestions are determined as target correction suggestions. The target correction suggestions contain two fields: a description of the suggested action and a processing priority indicator.
[0141] Accordingly, step 1 includes any of the following:
[0142] Item 1: If the target risk level indicates high risk, the first revision recommendation will be determined as the target revision recommendation. The first revision recommendation is used to indicate that the revision process is of the highest priority and must be implemented immediately.
[0143] In this implementation, when the target risk level extracted from the differential risk data is high risk, the risk level strategy table is queried with high risk as the key, the record corresponding to the key high risk is matched, and the first correction suggestion bound to the record is determined as the target correction suggestion.
[0144] The first correction suggestion contains a priority flag with the highest priority. Upon reading this suggestion, the synchronization interface of the configuration management tool is immediately invoked to update the power supply domain configuration template of the device under evaluation. This forces the current power supply domain value of the device under evaluation to be overwritten with the theoretical power supply domain value, and simultaneously updates the associated DC-DC conversion scheme references. After the update is complete, the execution log of this correction operation is recorded.
[0145] Item 2: If the target risk level indicates risk, then the second revision suggestion will be determined as the target revision suggestion. The second revision suggestion is used to indicate that the revision process is of high priority and it is recommended to make the revision in the next iteration.
[0146] In this implementation, when the target risk level extracted from the differential risk data is medium risk, the risk level strategy table is queried with medium risk as the key, the record corresponding to the medium risk key is matched, and the second correction suggestion bound to the record is determined as the target correction suggestion.
[0147] The second revision suggestion contains a priority flag, which has a high priority value. This second revision suggestion is written to the recent iteration partition of the pending revision list, and the device identifier, theoretical power supply domain value, and current power supply domain value of the device to be evaluated are associated and recorded in the revision suggestion entry for the version release management tool to read and process during subsequent iteration planning.
[0148] Item 3: If the target risk level indicates low risk, then the third revision recommendation will be determined as the target revision recommendation. The third revision recommendation is used to indicate that the revision process is of regular priority and it is recommended to include it in the planning of subsequent versions.
[0149] In this implementation, when the target risk level extracted from the differential risk data is low risk, the risk level strategy table is queried with low risk as the key, the record corresponding to the key low risk is matched, and the third correction suggestion bound to the record is determined as the target correction suggestion.
[0150] This third revision suggestion contains a priority flag, the value of which is a regular priority. This third revision suggestion should be added to the version planning section of the pending revision list, and the device identifier and difference details of the device to be evaluated should be recorded in the revision suggestion entry for unified review and processing during subsequent major version initiation.
[0151] Furthermore, when generating target correction suggestions, the device number can be bound to the target correction suggestion and recorded in the synchronization processing log. For example, when a configuration difference of the front-end fan is detected, the generated correction suggestion must be clearly marked with the device number FAN-001, and the original power supply domain value, the corrected power supply domain value, and the operation timestamp of the device must be recorded in the operation log to ensure that each correction operation can be traced back to the specific device.
[0152] Step 2: Based on the target correction suggestions, modify the current power supply domain data corresponding to the device to be evaluated in the power supply domain configuration table;
[0153] The power supply domain configuration table contains different device identifiers and the power supply domain data to which each device identifier belongs.
[0154] In this implementation, the corresponding execution path is selected based on the priority indicated by the target modification suggestion:
[0155] If the priority is the highest, immediately call the forced update interface of the power supply domain configuration management module. Using the device identifier of the device to be evaluated as the update condition, modify the power supply domain field value of the device in the power supply domain configuration table to the theoretical power supply domain value, and at the same time update the associated DC-DC conversion scheme reference field to the scheme number that matches the theoretical power supply domain.
[0156] After the update operation is completed, the updated record in the configuration table is read and compared with the theoretical power supply domain value for confirmation. If the two comparisons match, the correction is considered successful; if they do not match, the system throws an exception and records the reason for the failure.
[0157] The final result of the correction (success or failure), the correction timestamp, and the current software version number are associated to generate a correction result record. The write-back interface of the master data platform is called to send the correction result record and the updated configuration data back to the master data platform, ensuring that the power supply domain configuration of the device in the master data platform is consistent with the corrected configuration.
[0158] If the priority is high or normal, a forced update is not executed immediately. Instead, the correction suggestion, device identifier, and difference details are written to the corresponding partition of the pending correction list for manual or automatic triggering during subsequent version iterations. A status tracking field is added to the pending correction list for this entry. The initial status is "pending," and after the actual correction is executed, the operator or automated script updates the status to "processed," and the processing result is synchronously written back to the master data platform.
[0159] The method for processing the power supply domain configuration of equipment in a vehicle provided in this application determines the difference risk data of the equipment to be evaluated based on theoretical power supply domain data and current power supply domain data; and corrects the power supply domain data of the equipment to be evaluated based on the difference risk data. This technical solution first accurately locates the power supply domain configuration deviation of the equipment to be evaluated by comparing theoretical power supply domain data with current power supply domain data, avoiding omissions and inefficiencies caused by manual sampling or overall traversal; then, by generating difference risk data, the deviation is associated with and bound to the equipment's own attribute information, providing a data foundation for tiered handling; finally, by performing synchronous processing based on the difference risk data, the correction action is directly applied to the power supply domain configuration of the equipment, realizing the process from problem discovery to correction execution, thereby fundamentally eliminating the potential configuration inconsistency caused by the disconnect between master data, threshold rules, and mapping tables.
[0160] Based on the above embodiments, Figure 5 A flowchart illustrating the processing method for configuring the power supply domain of devices in a vehicle according to embodiments of this application. Figure 4 ,like Figure 5 As shown, the method may include:
[0161] Step 51: Read the device master data, threshold rules, and power supply domain configuration table;
[0162] Step 52: Recalculate the migration interval and power supply domain mapping results;
[0163] Step 53: Compare the consistency between the current result and the target configuration;
[0164] Step 54: Perform risk classification on the discrepancies;
[0165] Step 55: Generate correction suggestions and perform regression validation;
[0166] Step 56: Archive the discrepancy list and regression results.
[0167] Based on the above embodiments, Figure 6 A flowchart illustrating the processing method for configuring the power supply domain of devices in a vehicle according to embodiments of this application. Figure 5 ,like Figure 6 As shown, the method may include:
[0168] Interactive components: baseline library, consistency recalculator, risk analyzer, and reporter;
[0169] Step 61: The baseline library provides master data and threshold rules to the consistency recalculator;
[0170] Step 62: The consistency recalculator outputs the discrepancy objects and consistency results to the risk analyzer;
[0171] Step 63: The risk analyzer submits risk classification and correction recommendations to the reporter;
[0172] Step 64: The reporter writes back the regression status to the baseline library.
[0173] The method for processing the power supply domain configuration of equipment in a vehicle provided in this application provides a consistency and regression verification path for the migration threshold and the power supply domain mapping model, enabling the correctness of the rules to form an independent verification conclusion; and since the object boundary, parameter boundary, state migration and recording results have been clearly defined in this application, it can directly enter the detailed design, verification, calibration and after-sales traceability process.
[0174] Figure 7 This is a schematic diagram of the structure of the processing device configured in the power supply domain of the vehicle provided in the embodiments of this application, as shown below. Figure 7 As shown, the processing unit configured in the power supply domain of the vehicle includes:
[0175] Module 71 is used to acquire target parameter data of the device to be evaluated in the vehicle;
[0176] The determination module 72 is used to determine the current power supply domain data and theoretical power supply domain data of the device to be evaluated based on the target parameter data.
[0177] The processing module 73 is used to correct the power supply domain data of the device to be evaluated based on the theoretical power supply domain data and the current power supply domain data.
[0178] In one or more embodiments, the determining module 72 determines the current power supply domain data and theoretical power supply domain data of the device to be evaluated based on the target parameter data, specifically for:
[0179] Based on the target parameter data and the migration threshold rule base, the theoretical power supply domain data for the device to be evaluated is determined. The migration threshold rule base is determined based on power thresholds and / or safety levels.
[0180] Based on the device identifier and power supply domain configuration table in the target parameter data, the current power supply domain data of the device to be evaluated is determined. The power supply domain configuration table records different device identifiers and the power supply domain data to which each device identifier belongs.
[0181] In one or more embodiments, the processing module 73 performs correction processing on the power supply domain data of the device to be evaluated based on theoretical power supply domain data and current power supply domain data, specifically for:
[0182] Based on theoretical power supply domain data and current power supply domain data, determine the difference risk data of the equipment to be evaluated;
[0183] Based on the differential risk data, the power supply domain data of the equipment to be evaluated is corrected.
[0184] In one or more embodiments, the processing module 73 determines the difference risk data of the device to be evaluated based on the theoretical power supply domain data and the current power supply domain data, specifically for:
[0185] By comparing theoretical power supply domain data with current power supply domain data, a list of target discrepancies is obtained.
[0186] Based on the target difference object list and the preset risk assessment strategy, the difference risk data of the equipment to be assessed are obtained. The risk assessment strategy is determined based on the primary impact of equipment failure on vehicle safety and the secondary impact of equipment power on the carrying capacity of the power supply network.
[0187] In one or more embodiments, the processing module 73 corrects the power supply domain data of the device to be evaluated based on the difference risk data, specifically for:
[0188] Based on the target risk level indicated by the differential risk data, target modification recommendations are determined in the risk level strategy. The risk level strategy records different risk levels and the modification recommendations corresponding to each risk level.
[0189] Based on the target correction recommendations, modify the current power supply domain data corresponding to the device to be evaluated in the power supply domain configuration table. The power supply domain configuration table records different device identifiers and the power supply domain data to which each device identifier belongs.
[0190] In one or more embodiments, the processing module 73 determines a target correction suggestion in the risk level strategy based on the target risk level indicated by the differential risk data, specifically for:
[0191] If the target risk level indicates high risk, the first revision recommendation will be determined as the target revision recommendation. The first revision recommendation is used to indicate that the revision is of the highest priority and must be implemented immediately.
[0192] If the target risk level indicates risk, then the second revision recommendation will be determined as the target revision recommendation. The second revision recommendation is used to indicate that the revision process is of high priority and it is recommended to make the revision in the most recent iteration.
[0193] If the target risk level indicates low risk, then the third revision recommendation will be determined as the target revision recommendation. The third revision recommendation is used to indicate that the revision process is of regular priority and should be included in the planning of subsequent versions.
[0194] In one or more embodiments, the target parameter data includes: device identifier, power parameters, security level, and device type;
[0195] The corresponding power supply domain data includes: power supply domain, migration priority level, and associated DC-DC conversion scheme.
[0196] It should be noted that the division of the various modules in the above device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical element, or they can be physically separated. Furthermore, these modules can be implemented entirely in software through processing element calls, or entirely in hardware. Alternatively, some modules can be implemented through processing element calls in software, while others can be implemented in hardware. Moreover, these modules can be integrated together or implemented independently. The processing element here can be an integrated circuit with signal processing capabilities. During implementation, each step of the above method or each of the above modules can be completed through the integrated logic circuits in the hardware of the processor element or through software instructions.
[0197] As can be seen from the above, the processing device for the power supply domain configuration of the vehicle provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.
[0198] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 8 As shown, the electronic device provided in this embodiment includes at least one processor 81 and a memory 82.
[0199] Optionally, the electronic device also includes a communication component 83.
[0200] The processor 81, memory 82, and communication component 83 are connected via bus 84.
[0201] In a specific implementation, at least one processor 81 executes computer execution instructions stored in memory 82, causing at least one processor 81 to perform the above-described method.
[0202] The specific implementation process of processor 81 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.
[0203] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.
[0204] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.
[0205] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.
[0206] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.
[0207] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.
[0208] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.
[0209] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.
[0210] The division of units is merely a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.
[0211] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0212] In addition, the functional units in the various embodiments of the present invention 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.
[0213] If a function is implemented as 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 technical solution of this invention, or the part that contributes to the prior art, or a 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 of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0214] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.
[0215] Finally, it should be noted that other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein, and is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.
Claims
1. A method for configuring the power supply domain of equipment in a vehicle, characterized in that, include: Obtain target parameter data for the equipment to be evaluated in the vehicle; Based on the target parameter data, the current power supply domain data and theoretical power supply domain data of the device to be evaluated are determined; Based on the theoretical power supply domain data and the current power supply domain data, the power supply domain data of the device to be evaluated is corrected.
2. The method according to claim 1, characterized in that, The step of determining the current power supply domain data and theoretical power supply domain data of the device to be evaluated based on the target parameter data includes: Based on the target parameter data and the migration threshold rule base, the theoretical power supply domain data suitable for the device to be evaluated is determined. The migration threshold rule base is determined based on power thresholds and / or security levels. Based on the device identifier to be evaluated and the power supply domain configuration table in the target parameter data, the current power supply domain data of the device to be evaluated is determined. The power supply domain configuration table records different device identifiers and the power supply domain data to which each device identifier belongs.
3. The method according to claim 1 or 2, characterized in that, The step of correcting the power supply domain data of the device to be evaluated based on the theoretical power supply domain data and the current power supply domain data includes: Based on the theoretical power supply domain data and the current power supply domain data, determine the difference risk data of the device to be evaluated; Based on the aforementioned differential risk data, the power supply domain data of the device to be evaluated is corrected.
4. The method according to claim 3, characterized in that, The step of determining the difference risk data of the device to be evaluated based on the theoretical power supply domain data and the current power supply domain data includes: By comparing the theoretical power supply domain data and the current power supply domain data, a list of target difference objects is obtained; Based on the target difference object list and the preset risk assessment strategy, the difference risk data of the equipment to be assessed is obtained. The risk assessment strategy is determined based on the first impact of equipment failure on vehicle safety and the second impact of equipment power on the carrying capacity of the power supply network.
5. The method according to claim 3, characterized in that, The step of correcting the power supply domain data of the device to be evaluated based on the difference risk data includes: Based on the target risk level indicated by the differential risk data, a target correction recommendation is determined in the risk level strategy, which records different risk levels and the correction recommendation corresponding to each risk level. Based on the target correction suggestion, modify the current power supply domain data corresponding to the device to be evaluated in the power supply domain configuration table. The power supply domain configuration table records different device identifiers and the power supply domain data to which each device identifier belongs.
6. The method according to claim 5, characterized in that, The step of determining target correction recommendations in the risk level strategy based on the target risk level indicated by the differential risk data includes: If the target risk level indicates high risk, then the first correction suggestion is determined as the target correction suggestion. The first correction suggestion is used to indicate that the correction process is of the highest priority and the correction must be performed immediately. If the target risk level indicates risk, then the second correction suggestion is determined as the target correction suggestion. The second correction suggestion is used to indicate that the correction process is of high priority and it is recommended to correct it in the next iteration. If the target risk level indicates low risk, then the third revision suggestion will be determined as the target revision suggestion. The third revision suggestion is used to indicate that the revision process is of regular priority and is recommended to be included in the planning of subsequent versions.
7. The method according to claim 1 or 2, characterized in that, The target parameter data includes: device identifier, power parameters, security level, and device type; The corresponding power supply domain data includes: power supply domain, migration priority level, and associated DC-DC conversion scheme.
8. A processing apparatus for configuring the power supply domain of equipment in a vehicle, characterized in that, include: The acquisition module is used to acquire target parameter data of the equipment to be evaluated in the vehicle. The determination module is used to determine the current power supply domain data and theoretical power supply domain data of the device to be evaluated based on the target parameter data. The processing module is used to correct the power supply domain data of the device to be evaluated based on the theoretical power supply domain data and the current power supply domain data.
9. An electronic device, characterized in that, include: Memory, processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1-7.
10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-7.
