Software deployment method and device based on vehicle, electronic equipment and medium

Abstract

The invention provides a vehicle-based software deployment method and device, electronic equipment and a medium, and the method comprises the steps that a software configuration list of a target vehicle is called, the software configuration list comprises a plurality of configuration items, and each configuration item comprises a software identifier and a processing identifier; for each configuration item in the software configuration list, executing the following deployment processing: searching an actual processing unit corresponding to the software identifier of the configuration item in the software deployment list of the target vehicle, and if the actual processing unit corresponding to the configuration item is different from a preset processing unit, executing the deployment processing; and if not, replacing a processing identifier indicating a preset processing unit with a processing identifier corresponding to a software identifier corresponding to the configuration item in a software deployment list so as to execute software deployment for the target vehicle based on the software deployment list. Through the vehicle software deployment method and device, automatic verification and correction of the mapping relation between the software component and the processing unit are achieved, and the accuracy and execution efficiency of vehicle software deployment are improved.

Description

Technical Field

[0001] The present application relates to the technical field of automotive software development, and in particular to a vehicle-based software deployment method, device, electronic device, and medium. Background Art

[0002] PREEvision, a core modeling tool for vehicle electrical and electronic architecture design, relies on the correct mapping of software components (SWCs) and processing units for communication modeling. SWC interfaces (Ports) must be wired across processing units to enable SOME / IP service communication, and the SWCs to which these ports belong must be deployed on different processing units. The current deployment process relies on manual operations—users must drag and drop SWCs one by one to the target processing unit according to a mapping table and confirm the mapping relationships one by one. For example, deploying 100 SWCs requires 100 repeated drag-and-drop operations, which leads to two problems: first, manual dragging can easily lead to mismatches, causing communication link disruptions or signal conflicts; second, repeated manual operations are time-consuming in large-scale projects and make it difficult to ensure consistency between the mapping table and the model. Summary of the Invention

[0003] In view of this, the purpose of this application is to provide a vehicle-based software deployment method, device, electronic device and medium, aiming to realize automatic verification and correction of the mapping relationship between software components and processing units, and improve the accuracy and execution efficiency of vehicle software deployment.

[0004] In a first aspect, the present application provides a vehicle-based software deployment method, the method comprising: calling a software configuration list of a target vehicle, the software configuration list comprising multiple configuration items, each configuration item comprising a software identifier and a processing identifier, for indicating that there is a preset mapping relationship between a software component corresponding to the software identifier in the same configuration item and a processing unit corresponding to the processing identifier; for each configuration item in the software configuration list, performing the following deployment processing: searching the software deployment list of the target vehicle for an actual processing unit corresponding to the software identifier of the configuration item, and identifying whether the actual processing unit is consistent with a preset processing unit corresponding to the software identifier of the configuration item in the software configuration list; if the actual processing unit corresponding to the configuration item is different from the preset processing unit, replacing the processing identifier indicating the preset processing unit with the processing identifier corresponding to the software identifier of the configuration item in the software deployment list, so as to perform software deployment for the target vehicle based on the software deployment list.

[0005] In one possible implementation, the deployment processing performed on each configuration item in the software configuration list includes: (A) extracting the software identifier and processing identifier of the i-th configuration item in the software configuration list, where the initial value of i is 2; (B) verifying whether the software identifier and processing unit identifier of the i-th configuration item both exist in the software deployment list; (C) if both exist, searching for the actual processing unit identifier corresponding to the software identifier of the i-th configuration item in the software deployment list; (D) verifying whether the actual processing unit identifier is consistent with the processing unit identifier of the i-th configuration item; (E) if not consistent, updating the actual processing unit identifier corresponding to the software component identifier of the i-th row in the software deployment list to the processing unit identifier of the i-th row, setting i=i+1, and returning to step (A); (F) if consistent, setting i=i+1, and returning to step (A).

[0006] In a possible implementation, before step (A), the method further includes: scanning the i-th row in the software deployment list to determine whether the i-th row is empty; wherein, if the i-th row is not empty, extracting the software component identifier and processing unit identifier of the i-th row.

[0007] In one possible implementation, step (B) includes: (B1) searching for the software component identifier of the i-th configuration item in the software deployment list; (B2) if the software component identifier of the i-th configuration item does not exist, determining it as an exception, recording the line number of the i-th row and the first exception type in the exception record, setting i=i+1, and returning to step (A); (B3) if the software component identifier of the i-th configuration item exists, searching for the processing unit identifier of the i-th configuration item in the software deployment list; (B4) if the processing unit identifier of the i-th configuration item does not exist, determining it as an exception, recording the line number of the i-th row and the second exception type in the exception record, setting i=i+1, and returning to step (A); (B5) if the processing unit identifier of the i-th configuration item exists, determining that both the software component identifier of the i-th configuration item and the processing unit identifier of the i-th configuration item exist.

[0008] In a possible implementation, the step of calling the vehicle's software deployment list also includes: providing an interactive interface; receiving a self-test instruction triggered by a user on the interactive interface; and loading the software deployment list in response to the self-test instruction.

[0009] In a possible implementation, the method further includes: receiving a user's request to view the exception record in an interactive interface; and displaying a details window in response to the viewing request, wherein a plurality of lines of exception records are displayed in the details window, each line including a line number and a corresponding exception type recorded in the software deployment list.

[0010] In a second aspect, the present application provides a vehicle-based software deployment device, which includes: a calling module for calling a software configuration list of a target vehicle, wherein the software configuration list includes multiple configuration items, each configuration item includes a software identifier and a processing identifier, which is used to indicate that there is a preset mapping relationship between the software component corresponding to the software identifier in the same configuration item and the processing unit corresponding to the processing identifier; a deployment module for performing the following deployment processing for each configuration item in the software configuration list: searching the software deployment list of the target vehicle for the actual processing unit corresponding to the software identifier of the configuration item, and identifying whether the actual processing unit is consistent with the preset processing unit corresponding to the software identifier of the configuration item in the software configuration list; if the actual processing unit corresponding to the configuration item is different from the preset processing unit, then replacing the processing identifier indicating the preset processing unit with the processing identifier corresponding to the software identifier of the configuration item in the software deployment list, so as to perform software deployment for the target vehicle based on the software deployment list.

[0011] In one possible embodiment, the deployment module is further configured to: (A) extract the software identifier and processing identifier of the i-th configuration item in the software configuration list, where the initial value of i is 2; (B) verify whether the software identifier and processing unit identifier of the i-th configuration item both exist in the software deployment list; (C) if both exist, search for the actual processing unit identifier corresponding to the software identifier of the i-th configuration item in the software deployment list; (D) verify whether the actual processing unit identifier is consistent with the processing unit identifier of the i-th configuration item; (E) if not consistent, update the actual processing unit identifier corresponding to the software component identifier of the i-th row in the software deployment list to the processing unit identifier of the i-th row, set i=i+1, and return to step (A); (F) if consistent, set i=i+1, and return to step (A).

[0012] In a third aspect, the present application also provides an electronic device comprising: a processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor. When the electronic device is running, the processor and the memory communicate through the bus, and when the machine-readable instructions are executed by the processor, the steps of the above method are performed.

[0013] In a fourth aspect, the present application further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above method are executed.

[0014] The present application provides a vehicle-based software deployment method, device, electronic device, and medium, wherein the method includes: calling the software configuration list of the target vehicle, the software configuration list including multiple configuration items, each configuration item including a software identifier and a processing identifier; for each configuration item in the software configuration list, performing the following deployment processing: searching the software deployment list of the target vehicle for the actual processing unit corresponding to the software identifier of the configuration item; if the actual processing unit corresponding to the configuration item is different from the preset processing unit, then replacing the processing identifier corresponding to the software identifier corresponding to the configuration item with the processing identifier indicating the preset processing unit in the software deployment list, so as to execute software deployment for the target vehicle based on the software deployment list. Through the present application, automatic verification and correction of the mapping relationship between software components and processing units is achieved, thereby improving the accuracy and execution efficiency of vehicle software deployment.

[0015] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, preferred embodiments are given below and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other relevant drawings can be obtained based on these drawings without creative work.

[0017] Figure 1 A flowchart of vehicle-based software deployment provided in an embodiment of the present application;

[0018] Figure 2 A flowchart of the software deployment method provided in an embodiment of the present application;

[0019] Figure 3 A schematic diagram of the structure of a vehicle-based software deployment device provided in an embodiment of the present application;

[0020] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0021] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. The components of the embodiments of the present application generally described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application for which protection is claimed, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, each other embodiment obtained by those skilled in the art without making creative work falls within the scope of protection of the present application.

[0022] First, the application scenarios to which this application is applicable are introduced. This application can be applied to automotive software development.

[0023] PREEvision is a widely used computer modeling tool in the field of electronic and electrical architecture design. It supports cross-core SOME / IP service communication based on software component (SWC) interfaces (ports). In this tool, communication modeling requires two prerequisites: 1. Connections between SWC ports exist; 2. The SWCs belonging to the connected ports must be deployed on different processing units. Therefore, mapping the SWCs to the processing units is a prerequisite for establishing communication links. Currently, SWC deployment in PREEvision relies primarily on manual operations: users must manually drag and drop SWCs to target processing units (or vice versa) according to a mapping table, completing deployment and confirming the mapping relationships one by one. For example, 100 SWCs require 100 repeated drag-and-drop operations. Manual configuration is prone to the following issues: 1. Accuracy: Drag-and-drop errors can lead to mismatches, causing communication link disruptions or signal conflicts; 2. Inefficiency: Repeated operations are time-consuming in large-scale projects, and it is difficult to ensure consistency between the mapping table and the model; 3. Poor maintainability: Manual adjustments can easily introduce new errors during subsequent architectural changes. Existing technical solutions are highly dependent on manual intervention and are unable to meet the requirements of the automotive electronics field for high reliability, high efficiency and traceability of complex systems. There is an urgent need to optimize the deployment process through automation technology.

[0024] Based on this, the embodiments of the present application provide a vehicle-based software deployment method, device, electronic device and medium, which realize automatic verification and correction of the mapping relationship between software components and processing units, and improve the accuracy and execution efficiency of vehicle software deployment.

[0025] See also Figure 1 , Figure 1 This is a flow chart of a vehicle-based software deployment method provided in an embodiment of the present application. Figure 1 As shown in , the vehicle-based software deployment method provided by the embodiment of the present application includes:

[0026] S101. Call the software configuration list of the target vehicle.

[0027] Specifically, the software configuration list includes multiple configuration items, each configuration item includes a software identifier and a processing identifier, which is used to indicate that a preset mapping relationship exists between the software component corresponding to the software identifier and the processing unit corresponding to the processing identifier in the same configuration item.

[0028] The software configuration list refers to a predefined standard mapping relationship table between vehicle software components and processing units. Each configuration item specifies the target processing unit (uniquely identified by the processing identifier) ​​to which a specific software component (uniquely identified by the software identifier) ​​should be deployed. The software configuration list serves as a deployment baseline, defining the expected state of the software architecture. One software identifier uniquely corresponds to one software component (such as SWC1, SWC2), which is used to distinguish different functional modules or code units, and accurately associate the software component with its target / actual processing unit in the configuration list and deployment list. One processing identifier uniquely corresponds to one processing unit (such as ECU_A, SoC_B), representing the hardware execution node in the vehicle, and is used to clarify the deployment location of the software component and ensure that the communication link complies with the electronic and electrical architecture specifications.

[0029] In a preferred example of the present application, a self-test button can be set on PREEvision. Upon receiving a self-test instruction triggered by the user on the interactive interface, the software deployment list is loaded in response to the self-test instruction to automatically complete subsequent self-test and deployment work.

[0030] S102. For each configuration item in the software configuration list, perform the following deployment processing: search the software deployment list of the target vehicle for the actual processing unit corresponding to the software identifier of the configuration item, and identify whether the actual processing unit is consistent with the preset processing unit corresponding to the software identifier of the configuration item in the software configuration list; if the actual processing unit corresponding to the configuration item is different from the preset processing unit, replace the processing identifier indicating the preset processing unit with the processing identifier corresponding to the software identifier of the configuration item in the software deployment list, so as to perform software deployment on the target vehicle based on the software deployment list.

[0031] Here, the software deployment list refers to a record of the vehicle's current actual software deployment status. It stores the processing unit identifiers to which software identifiers are actually bound. It is used to reflect the real-time status of the system and may deviate from the software configuration list (such as due to human mismatching or version inconsistency). The actual processing unit refers to the processing unit to which the software components recorded in the software deployment list are actually bound. It may be inconsistent with the actual processing unit bound in the software configuration list due to human error or version iteration.

[0032] Specifically, if Figure 2 As shown in , the embodiment of the present application provides specific steps for executing the deployment process for each configuration item in the software configuration list.

[0033] S201. Extract the software identifier and processing identifier of the i-th configuration item in the software configuration list, where the initial value of i is 2.

[0034] Here, a configuration item refers to a row of data in the software configuration list, which represents the mapping rule from an independent software component to a processing unit. The initial value of i is 2, which means that the first row of the software configuration list is the table header (column name). The data starts from the second row and traverses all configuration items through a loop (i=i+1) to ensure full verification.

[0035] Among them, the following steps are also included before step S201.

[0036] S2011. Scan the i-th row in the software deployment list to determine whether the i-th row is empty.

[0037] S2012: If the i-th row is not empty, execute step S201.

[0038] S2013: If the i-th row is empty, the process ends.

[0039] return Figure 2 S202: Verify whether the software identifier and processing unit identifier of the i-th configuration item both exist in the software deployment list.

[0040] Wherein, step S202 specifically also includes the following steps.

[0041] S2021. Search the software deployment list to see whether the software component identifier of the i-th configuration item exists.

[0042] S2022. If the software component identifier of the i-th configuration item does not exist, it is determined to be an exception, and the line number of the i-th line and the first exception type are recorded in the exception record, and i=i+1 is set, and the process returns to step (A).

[0043] Here, the exception record refers to error information found during the storage verification process, including the line number of the exception in the software deployment list and the corresponding exception type. The first exception type refers to the software identifier not existing in the software deployment list.

[0044] S2023. If the software component identifier of the i-th configuration item exists, search the software deployment list to see whether the processing unit identifier of the i-th configuration item exists.

[0045] S2024. If the processing unit identifier of the i-th configuration item does not exist, it is determined to be an exception, and the row number of the i-th row and the second exception type are recorded in the exception record, and i=i+1 is set, and the process returns to step (A).

[0046] Here, the second exception type refers to the fact that the processing unit identifier does not exist in the software deployment list.

[0047] S2025: If the processing unit identifier of the i-th configuration item exists, determine that both the software component identifier of the i-th configuration item and the processing unit identifier of the i-th configuration item exist.

[0048] return Figure 2 , S203, if both exist, search for the actual processing unit identifier corresponding to the software identifier of the i-th configuration item in the software deployment list.

[0049] S204: Verify whether the actual processing unit identifier is consistent with the processing unit identifier of the i-th configuration item.

[0050] S205 , if inconsistent, then update the actual processing unit identifier corresponding to the software component identifier in the i-th row in the software deployment list to the processing unit identifier in the i-th row, set i=i+1, and return to step S201 .

[0051] S206. If they are consistent, set i=i+1 and return to step S201.

[0052] Finally, the user can click on the exception record on the PREEvision interactive interface to generate a viewing request for the exception record. In response to the viewing request, PREEvision displays a details window, which displays multiple lines of exception records. Each line includes the line number recorded in the software deployment list and the corresponding exception type.

[0053] Based on the same inventive concept, the embodiments of the present application also provide a vehicle-based software deployment device corresponding to the vehicle-based software deployment method. Since the principle of solving the problem by the device in the embodiments of the present application is similar to the above-mentioned vehicle-based software deployment method in the embodiments of the present application, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be repeated.

[0054] See also Figure 3 , Figure 3 A schematic diagram of a vehicle-based software deployment device provided in an embodiment of the present application is shown in FIG. Figure 3 As shown in FIG, the vehicle-based software deployment apparatus 400 includes:

[0055] The calling module 401 is used to call the software configuration list of the target vehicle. The software configuration list includes multiple configuration items. Each configuration item includes a software identifier and a processing identifier, which is used to indicate that there is a preset mapping relationship between the software component corresponding to the software identifier in the same configuration item and the processing unit corresponding to the processing identifier.

[0056] The deployment module 402 is used to perform the following deployment processing for each configuration item in the software configuration list: searching the software deployment list of the target vehicle for the actual processing unit corresponding to the software identifier of the configuration item, and identifying whether the actual processing unit is consistent with the preset processing unit corresponding to the software identifier of the configuration item in the software configuration list; if the actual processing unit corresponding to the configuration item is different from the preset processing unit, replacing the processing identifier indicating the preset processing unit with the processing identifier corresponding to the software identifier of the configuration item in the software deployment list, so as to perform software deployment on the target vehicle based on the software deployment list.

[0057] See also Figure 4 , Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Figure 4 As shown in FIG, the electronic device 500 includes a processor 510, a memory 520 and a bus 530.

[0058] The memory 520 stores machine-readable instructions executable by the processor 510. When the electronic device 500 is running, the processor 510 communicates with the memory 520 through the bus 530. When the machine-readable instructions are executed by the processor 510, the steps of the vehicle-based software deployment method in the above embodiment can be executed. The specific implementation method can be found in the method embodiment and will not be repeated here.

[0059] An embodiment of the present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the vehicle-based software deployment method in the above-mentioned method embodiment can be executed. The specific implementation method can be found in the method embodiment and will not be repeated here.

[0060] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0061] 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 schematic. For example, the division of the units is merely a logical function division. There may be other division methods in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed may be through some communication interface, indirect coupling or communication connection of devices or units, which may be electrical, mechanical or other forms.

[0062] The units described as separate components may or may not be physically separate, and 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 these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0063] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0064] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0065] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present application, which are used to illustrate the technical solutions of the present application, rather than to limit them. The scope of protection of the present application is not limited thereto. Although the present application has been described in detail with reference to the above-mentioned embodiments, those skilled in the art should understand that any person skilled in the art can modify or easily conceive of changes to the technical solutions described in the above-mentioned embodiments within the technical scope disclosed in the present application, or perform equivalent replacements for some of the technical features thereof. These modifications, changes, or replacements do not deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A vehicle-based software deployment method, characterized in that: The method comprises: Recalling a software configuration list of a target vehicle, the software configuration list including a plurality of configuration items, each configuration item including a software identifier and a processing identifier, for indicating that a preset mapping relationship exists between a software component corresponding to the software identifier and a processing unit corresponding to the processing identifier in the same configuration item; For each configuration item in the software configuration list, the following deployment processing is performed: the actual processing unit corresponding to the software identifier of the configuration item is searched in the software deployment list of the target vehicle, and it is identified whether the actual processing unit is consistent with the preset processing unit corresponding to the software identifier of the configuration item in the software configuration list; if the actual processing unit corresponding to the configuration item is different from the preset processing unit, the processing identifier corresponding to the software identifier of the configuration item in the software deployment list is replaced with the processing identifier indicating the preset processing unit, so as to perform software deployment for the target vehicle based on the software deployment list.

2. The method according to claim 1, characterized in that The deployment process performed for each configuration item in the software configuration list includes: (A) extracting the software identifier and processing identifier of the i-th configuration item in the software configuration list, where the initial value of i is 2; (B) verifying whether the software identifier and the processing unit identifier of the configuration item i are both present in the software deployment list; (C) If both exist, searching for the actual processing unit identifier corresponding to the software identifier of the i-th configuration item in the software deployment list; (D) verifying whether the actual processing unit identifier is consistent with the processing unit identifier of the i-th configuration item; (E) If they are inconsistent, then the actual processing unit identifier corresponding to the software component identifier in the i-th row in the software deployment list is updated to the processing unit identifier in the i-th row, and i=i+1, and return to step (A); (F) If they are consistent, set i=i+1 and return to step (A).

3. The method according to claim 2, characterized in that Before step (A), the method further comprises: Scan the i-th row in the software deployment list to determine whether the i-th row is empty; If the i-th row is not empty, the software component identifier and the processing unit identifier of the i-th row are extracted.

4. The method according to claim 2, characterized in that Step (B) comprises: (B1) searching the software deployment list for the software component identifier of the configuration item i; (B2) If the software component identifier of the i-th configuration item does not exist, it is determined to be an exception, and the line number of the i-th line and the first exception type are recorded in the exception record, and i=i+1 is set, and the process returns to step (A); (B3) if the software component identifier of the i-th configuration item exists, searching the software deployment list for the processing unit identifier of the i-th configuration item; (B4) If the processing unit identifier of the i-th configuration item does not exist, it is determined to be an exception, and the row number of the i-th row and the second exception type are recorded in the exception record, and i=i+1 is set, and the process returns to step (A); (B5) If the processing unit identifier of the i-th configuration item exists, it is determined that both the software component identifier of the i-th configuration item and the processing unit identifier of the i-th configuration item exist.

5. The method according to claim 1, characterized in that Before the step of calling the vehicle's software deployment list, the following steps are also included: Provide an interactive interface; Receiving a self-test instruction triggered by a user on the interactive interface; In response to the self-check instruction, the software deployment checklist is loaded.

6. The method according to claim 4, characterized in that Also includes: Receiving a user's request to view the abnormal record on the interactive interface; In response to the viewing request, a detail window is displayed, wherein a plurality of lines of exception records are displayed in the detail window, each line including a line number recorded in the software deployment list and a corresponding exception type.

7. A vehicle-based software deployment device, characterized in that: The device comprises: a calling module, configured to call a software configuration list of a target vehicle, wherein the software configuration list includes a plurality of configuration items, each configuration item including a software identifier and a processing identifier, and indicating that a preset mapping relationship exists between a software component corresponding to the software identifier and a processing unit corresponding to the processing identifier in the same configuration item; A deployment module is used to perform the following deployment processing for each configuration item in the software configuration list: searching the software deployment list of the target vehicle for an actual processing unit corresponding to the software identifier of the configuration item, and identifying whether the actual processing unit is consistent with the preset processing unit corresponding to the software identifier of the configuration item in the software configuration list; if the actual processing unit corresponding to the configuration item is different from the preset processing unit, replacing the processing identifier indicating the preset processing unit with the processing identifier corresponding to the software identifier of the configuration item in the software deployment list, so as to perform software deployment for the target vehicle based on the software deployment list.

8. The device according to claim 7, characterized in that The deployment module is further configured to: (A) extracting the software identifier and processing identifier of the i-th configuration item in the software configuration list, where the initial value of i is 2; (B) verifying whether the software identifier and the processing unit identifier of the configuration item i are both present in the software deployment list; (C) If both exist, searching for the actual processing unit identifier corresponding to the software identifier of the i-th configuration item in the software deployment list; (D) verifying whether the actual processing unit identifier is consistent with the processing unit identifier of the i-th configuration item; (E) If they are inconsistent, then the actual processing unit identifier corresponding to the software component identifier in the i-th row in the software deployment list is updated to the processing unit identifier in the i-th row, and i=i+1, and return to step (A); (F) If they are consistent, set i=i+1 and return to step (A).

9. An electronic device, characterized in that: include: A processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor and the memory communicate via the bus, and the processor executes the machine-readable instructions to perform the steps of any one of the methods described in claims 1 to 6.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are executed.

Images