Vehicle part software full life cycle management method, device, equipment and medium

Abstract

The invention discloses a vehicle part software full-life-cycle management method, device, equipment and medium, and relates to the technical field of vehicle software full-life-cycle management, the method comprises the steps that a part design file is published in the development and design link of a vehicle, and the part design file comprises vehicle software and hardware detailed information; transmitting the part design file to a downstream link, and extracting software and hardware version information and part information in the vehicle software and hardware detailed information; preparing materials for vehicle production based on the part information, and checking software and hardware version information of the parts according to the order information; and obtaining software and hardware version information of the parts, and comparing the software and hardware version information with software version information flashed in the corresponding controller of the vehicle to check whether the flashed software in the controller is correct or not. According to the method, the effectiveness, normalization and accuracy of software full-life-cycle management can be improved.

Description

Technical Field

[0001] The present application relates to the technical field of automobile software full life cycle management, and specifically to a vehicle component software full life cycle management method, device, equipment and medium. Background Art

[0002] With the continuous advancement of vehicle electrification, intelligence and networking, the core position of controllers in the vehicle system has become increasingly prominent, and its share has increased significantly year by year. In this process, the concept of "software-defined cars" has become increasingly important, highlighting the dominant role of software in car design, function realization and value creation. Therefore, effective management of software throughout its life cycle is of vital importance to improving the vehicle's user experience and after-sales service quality.

[0003] However, the current management has problems such as the inability to manage software version information throughout the entire life cycle, the inability to transmit software and hardware version information to the production end and the terminal, and the inability of customers to update the software in a timely manner. Therefore, in the design and development, production and manufacturing, and after-sales service of the vehicle, how to effectively manage the controller software and hardware, ensure the consistency of software from R&D design to production and manufacturing, and quickly and accurately check and flash the software to ensure that the terminal customers' software is quickly and accurately updated has become an urgent problem to be solved. Summary of the invention

[0004] The present application provides a vehicle component software full life cycle management method, device, equipment and medium, which can improve the effectiveness, standardization and accuracy of software full life cycle management.

[0005] In a first aspect, an embodiment of the present application provides a vehicle component software full life cycle management method, the vehicle component software full life cycle management method comprising:

[0006] Release component design files during the vehicle development and design phase, where the component design files contain detailed information on the vehicle's software and hardware;

[0007] Deliver the component design file to the downstream link, and extract the software and hardware version information and component information from the vehicle software and hardware detailed information;

[0008] Prepare materials for vehicle production based on the parts information, and verify the software and hardware version information of the parts according to the order information;

[0009] Obtain the software and hardware version information of the components, and compare it with the software version information flashed inside the corresponding controller of the vehicle to verify whether the software flashed inside the controller is correct.

[0010] In conjunction with the first aspect, in one implementation, the publishing of component design files in the vehicle development and design phase specifically includes:

[0011] Release component design documents during vehicle development and design;

[0012] Link the parts information to the corresponding vehicle model.

[0013] In combination with the first aspect, in one implementation, the transmitting the component design file to the downstream link and extracting the software and hardware version information and component information in the vehicle software and hardware detailed information specifically includes:

[0014] Automatically transfer the released component design files to downstream links, including procurement, manufacturing and after-sales service;

[0015] Identify component design files and extract software and hardware version information and component information from vehicle hardware and software details.

[0016] In combination with the first aspect, in one implementation, the preparing materials for vehicle production based on the component information and verifying the software and hardware version information of the component according to the order information specifically includes:

[0017] When there is a production demand for a vehicle model, the purchasing department sends the parts information to the supplier for the supply of the vehicle in preparation for production, or prepares the materials for vehicle production on its own;

[0018] When the supplier has completed delivery or the purchasing department has completed material preparation, before the vehicle enters final assembly production, the software and hardware version information of the parts will be verified based on the vehicle production order information.

[0019] In combination with the first aspect, in one implementation, the obtaining of the software and hardware version information of the component and comparing it with the software version information flashed inside the corresponding controller of the vehicle to verify whether the software flashed inside the controller is correct specifically includes:

[0020] When the vehicle is assembled, the software and hardware version information bound to the parts is obtained to form the software and hardware version information library of the current vehicle, and it is bound to the vehicle identification code;

[0021] Read the software version information inside the vehicle controller and compare it with the software version information in the software and hardware version information library to verify whether the software flashed inside the controller is correct.

[0022] In combination with the first aspect, in one implementation, verifying whether the software flashed inside the controller is correct specifically includes:

[0023] If the software version information read from the vehicle controller is consistent with the software version information in the software and hardware version information library, it means that the software flashed inside the vehicle controller is correct;

[0024] If the software version information read from the vehicle controller is inconsistent with the software version information in the software and hardware version information library, it indicates that the software flashed inside the vehicle controller is wrong, and the vehicle controller needs to be re-flashed.

[0025] In combination with the first aspect, in one implementation, the vehicle component software full life cycle management method further includes:

[0026] When a vehicle enters the market, if the software version of the vehicle controller changes, the hardware version information is checked through the vehicle identification code to confirm whether the new software is compatible with the hardware:

[0027] If compatible, the corresponding software will be updated through OTA or offline service, and the update record will be saved;

[0028] If incompatible, no processing will be performed.

[0029] In a second aspect, an embodiment of the present application provides a vehicle component software full life cycle management device, the vehicle component software full life cycle management device comprising:

[0030] A publishing module, which is used to publish component design files during the vehicle development and design phase, wherein the component design files contain detailed information about the vehicle's software and hardware;

[0031] A transfer module, which is used to transfer the component design file to the downstream link and extract the software and hardware version information and component information from the vehicle software and hardware detailed information;

[0032] A verification module, which is used to prepare materials for vehicle production based on the parts information and verify the software and hardware version information of the parts according to the order information;

[0033] The determination module is used to obtain the software and hardware version information of the components and compare it with the software version information flashed inside the corresponding controller of the vehicle to verify whether the software flashed inside the controller is correct.

[0034] In the third aspect, an embodiment of the present application provides a vehicle component software full life cycle management device, the vehicle component software full life cycle management device comprising a processor, a memory, and a vehicle component software full life cycle management program stored in the memory and executable by the processor, wherein when the vehicle component software full life cycle management program is executed by the processor, the steps of the above-mentioned vehicle component software full life cycle management method are implemented.

[0035] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a vehicle component software full life cycle management program is stored. When the vehicle component software full life cycle management program is executed by a processor, the steps of the above-mentioned vehicle component software full life cycle management method are implemented.

[0036] The beneficial effects brought by the technical solution provided by the embodiments of the present application include:

[0037] It systematically solves the management and transmission problems of controller software from design and development to production and manufacturing and even after-sales service. It effectively manages the controller hardware and software in each link of vehicle design and development, production and manufacturing, and after-sales service, ensuring the consistency of software from research and development to production and manufacturing, and quickly and accurately checking and flashing software to ensure fast and accurate software updates for end customers. At the same time, it can also start from the actual needs of the enterprise and comprehensively consider the concerns of each link to improve the effectiveness, standardization and accuracy of software management throughout the entire life cycle. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 A flowchart of the vehicle component software full life cycle management method for this application;

[0039] Figure 2 This is a functional module diagram of the vehicle parts software full life cycle management device of this application;

[0040] Figure 3 This is a schematic diagram of the hardware structure of the vehicle parts software full life cycle management equipment for this application. DETAILED DESCRIPTION

[0041] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution 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 part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0042] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below in conjunction with the accompanying drawings.

[0043] On the first aspect, the embodiments of the present application provide a method for the full life cycle management of vehicle component software to solve the management and transmission problems of controller software from design and development to production and manufacturing, and even to after-sales service. In addition, it can also start from the actual needs of the enterprise and comprehensively consider the concerns of various links to improve the effectiveness, standardization and accuracy of software full life cycle management, and the solution is more flexible.

[0044] In one embodiment, referring to Figure 1 , Figure 1 This is a flow chart of the vehicle component software full life cycle management method for this application. Figure 1 As shown in the figure, the vehicle component software full life cycle management method includes:

[0045] S1: Release component design files during the vehicle development and design phase, where the component design files contain detailed information on vehicle software and hardware;

[0046] S2: delivering the component design file to the downstream link, and extracting the software and hardware version information and component information from the vehicle software and hardware detailed information;

[0047] S3: preparing materials for vehicle production based on the parts information, and verifying the software and hardware version information of the parts according to the order information;

[0048] S4: Obtain the software and hardware version information of the components, and compare it with the software version information flashed inside the corresponding controller of the vehicle to verify whether the software flashed inside the controller is correct.

[0049] Furthermore, in one embodiment, the release of component design files in the vehicle development and design phase specifically includes:

[0050] S101: Release component design documents during vehicle development and design;

[0051] S102: The component information is transferred to the corresponding vehicle model.

[0052] Specifically, the component design files are released, which include detailed information on the vehicle's software and hardware. During the vehicle development and design phase, R&D engineers release the component design files, which include detailed information on the vehicle's software and hardware, and then link the component information to the corresponding vehicle model.

[0053] Furthermore, in one embodiment, the component design file is transmitted to a downstream link, and the software and hardware version information and component information in the vehicle software and hardware detailed information are extracted, specifically including:

[0054] S201: automatically delivering the released component design files to downstream links, including procurement, manufacturing and production, and after-sales service;

[0055] S202: Identify component design files, and extract software and hardware version information and component information from vehicle software and hardware detailed information.

[0056] Specifically, the released component design files are automatically transmitted to the downstream links in the system, and the system automatically identifies and extracts software and hardware version information and component information.

[0057] Furthermore, in one embodiment, preparing materials for vehicle production based on the component information and verifying the software and hardware version information of the components according to the order information specifically includes:

[0058] S301: When there is a production demand for a vehicle model, the purchasing department sends the parts information to the supplier for the supply of the vehicle for production preparation, or prepares the materials for the vehicle production preparation by itself;

[0059] S302: When the supplier has completed the delivery or the purchasing department has completed the material preparation, before the vehicle enters the final assembly production, the software and hardware version information of the parts is verified according to the vehicle production order information.

[0060] Specifically, when there is production demand for a vehicle model, the purchasing department will send the received parts information to the supplier for supply in preparation for vehicle production, or prepare the materials for vehicle production on its own. When the supplier has completed the supply or the purchasing department has completed the material preparation, before the vehicle enters final assembly production, the software and hardware version information of the parts will be verified according to the vehicle production order information to ensure that the parts loaded on the vehicle are the required parts.

[0061] Furthermore, in one embodiment, the software and hardware version information of the components is obtained and compared with the software version information flashed inside the corresponding controller of the vehicle to verify whether the software flashed inside the controller is correct, specifically including:

[0062] S401: When the vehicle is being assembled, the software and hardware version information bound to the components is obtained to form a software and hardware version information library of the current vehicle, and the information is bound to the vehicle identification code;

[0063] S402: Read the software version information inside the vehicle controller and compare it with the software version information in the software and hardware version information library to verify whether the software flashed inside the controller is correct.

[0064] Specifically, when the vehicle is assembled, the software and hardware version information library of the current vehicle is first formed by recording the software and hardware version information pasted on the parts and components, and bound to the vehicle identification code. Then, the software version information inside the vehicle controller is read through the corresponding equipment, and the read software version information is compared with the software version information in the software and hardware version information library to verify whether the software flashed inside the controller is correct.

[0065] Specifically, verify whether the software flashed inside the controller is correct, including:

[0066] If the software version information read from the vehicle controller is consistent with the software version information in the software and hardware version information library, it means that the software flashed inside the vehicle controller is correct;

[0067] If the software version information read from the vehicle controller is inconsistent with the software version information in the software and hardware version information library, it indicates that the software flashed inside the vehicle controller is wrong, and the vehicle controller needs to be re-flashed.

[0068] The above operations can ensure the consistency of software from R&D design to production and manufacturing, and reduce user complaints caused by software version errors.

[0069] Furthermore, in one embodiment, the vehicle component software full life cycle management method further includes:

[0070] When a vehicle enters the market, if the software version of the vehicle controller changes, the hardware version information is checked through the vehicle identification code to confirm whether the new software is compatible with the hardware:

[0071] If compatible, the corresponding software will be updated through OTA or offline service, and the update record will be saved;

[0072] If incompatible, no processing will be performed.

[0073] Specifically, after a vehicle enters the market, when the software version of a controller under the model changes, the hardware version information is first checked through the vehicle identification code to confirm whether the new software is compatible with the hardware. If compatible, the corresponding software is updated through OTA (Over-the-Air Technology) or offline service, and the update record is saved. If incompatible, no processing is performed.

[0074] First, after completing the software development test, the R&D designers will release the software together with the component design files; the component design files will be automatically sent to the procurement, production and after-sales service links along with the vehicle model files; in the production and manufacturing link, the hardware and software information of the components will be checked by the equipment. If the information is wrong, the software will be automatically triggered to flash the latest software officially released in the system to the controller. In the after-sales service link, the software and hardware version information will be compared in real time through remote management technology. When the software and hardware version information does not match the latest data, the software can be updated through OTA or offline active service according to the actual situation.

[0075] The vehicle component software full life cycle management method of the embodiment of the present application systematically solves the management and transmission problems of the controller software from design and development to production and manufacturing and even after-sales service. In each link of the design and development, production and manufacturing and after-sales service of the whole vehicle, it effectively manages the controller hardware and software to ensure the consistency of the software from research and development to production and manufacturing, and quickly and accurately checks and flashes the software to ensure that the end customer's software is updated quickly and accurately. At the same time, it can also start from the actual needs of the enterprise and comprehensively consider the concerns of each link to improve the effectiveness, standardization and accuracy of the software full life cycle management.

[0076] In a second aspect, an embodiment of the present application also provides a vehicle component software full life cycle management device.

[0077] In one embodiment, referring to Figure 2 , Figure 2 This is a functional module diagram of the vehicle parts software full life cycle management device of this application. Figure 2 As shown, the vehicle component software full life cycle management device includes: a release module, a delivery module, a verification module, and a determination module.

[0078] The release module is used to release component design files during the development and design phase of the vehicle, and the component design files contain detailed information on the vehicle's software and hardware; the delivery module is used to deliver the component design files to downstream links, and extract the software and hardware version information and component information from the vehicle's software and hardware detailed information; the verification module is used to prepare materials for vehicle production based on the component information, and verify the component's software and hardware version information based on the order information; the determination module is used to obtain the component's software and hardware version information, and compare it with the software version information flashed inside the corresponding controller of the vehicle to verify whether the software flashed inside the controller is correct.

[0079] In this application, the release of component design documents is carried out during the vehicle development and design phase, specifically including:

[0080] Release component design documents during vehicle development and design;

[0081] Link the parts information to the corresponding vehicle model.

[0082] In this application, the component design file is transmitted to the downstream link, and the software and hardware version information and component information in the vehicle software and hardware detailed information are extracted, specifically including:

[0083] Automatically transfer the released component design files to downstream links, including procurement, manufacturing and after-sales service;

[0084] Identify component design files and extract software and hardware version information and component information from vehicle hardware and software details.

[0085] In this application, the preparation of vehicle production is carried out based on the component information, and the software and hardware version information of the components is verified according to the order information, specifically including:

[0086] When there is a production demand for a vehicle model, the purchasing department sends the parts information to the supplier for the supply of the vehicle in preparation for production, or prepares the materials for vehicle production on its own;

[0087] When the supplier has completed delivery or the purchasing department has completed material preparation, before the vehicle enters final assembly production, the software and hardware version information of the parts will be verified based on the vehicle production order information.

[0088] In this application, the software and hardware version information of the components is obtained and compared with the software version information flashed inside the corresponding controller of the vehicle to verify whether the software flashed inside the controller is correct, including:

[0089] When the vehicle is assembled, the software and hardware version information bound to the parts is obtained to form the software and hardware version information library of the current vehicle, and it is bound to the vehicle identification code;

[0090] Read the software version information inside the vehicle controller and compare it with the software version information in the software and hardware version information library to verify whether the software flashed inside the controller is correct.

[0091] In this application, the software flashed inside the controller is verified to be correct, including:

[0092] If the software version information read from the vehicle controller is consistent with the software version information in the software and hardware version information library, it means that the software flashed inside the vehicle controller is correct;

[0093] If the software version information read from the vehicle controller is inconsistent with the software version information in the software and hardware version information library, it indicates that the software flashed inside the vehicle controller is wrong, and the vehicle controller needs to be re-flashed.

[0094] In this application, the vehicle component software full life cycle management method also includes:

[0095] When a vehicle enters the market, if the software version of the vehicle controller changes, the hardware version information is checked through the vehicle identification code to confirm whether the new software is compatible with the hardware:

[0096] If compatible, the corresponding software will be updated through OTA or offline service, and the update record will be saved;

[0097] If incompatible, no processing will be performed.

[0098] On the third aspect, an embodiment of the present application provides a vehicle component software full life cycle management device, which can be a personal computer (PC), a laptop computer, a server, or other device with data processing capabilities.

[0099] Reference Figure 3 , Figure 3 The hardware structure diagram of the vehicle component software full life cycle management device involved in the embodiment of the present application is shown in FIG. In the embodiment of the present application, the vehicle component software full life cycle management device may include a processor, a memory, a communication interface, and a communication bus.

[0100] The communication bus may be of any type and is used to interconnect the processor, the memory, and the communication interface.

[0101] The communication interface includes input / output (I / O) interface, physical interface and logical interface, etc., which are used to realize the interconnection of devices inside the vehicle component software full life cycle management device, and the interface used to realize the interconnection between the vehicle component software full life cycle management device and other devices (such as other computing devices or user devices). The physical interface can be an Ethernet interface, a fiber optic interface, an ATM interface, etc.; the user device can be a display, a keyboard, etc.

[0102] The memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical storage, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.

[0103] The processor may be a general-purpose processor, which may call the vehicle component software life cycle management program stored in the memory and execute the vehicle component software life cycle management method provided in the embodiment of the present application. For example, the general-purpose processor may be a central processing unit (CPU). The method executed when the vehicle component software life cycle management program is called may refer to the various embodiments of the vehicle component software life cycle management method of the present application, which will not be repeated here.

[0104] Those skilled in the art will understand that Figure 3 The hardware structure shown in the figure does not constitute a limitation on the present application, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0105] In a fourth aspect, an embodiment of the present application also provides a computer-readable storage medium.

[0106] The computer-readable storage medium of the present application stores a vehicle component software full life cycle management program, wherein when the vehicle component software full life cycle management program is executed by a processor, the steps of the vehicle component software full life cycle management method as described above are implemented.

[0107] Among them, the method implemented when the vehicle component software full life cycle management program is executed can refer to the various embodiments of the vehicle component software full life cycle management method of the present application, and will not be repeated here.

[0108] The terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices. The terms "first", "second" and "third" are used to distinguish different objects, etc., and do not represent a sequence, nor do they limit "first", "second" and "third" to different types.

[0109] In the description of the embodiments of the present application, "exemplary", "for example" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary", "for example" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary", "for example" or "for example" is intended to present related concepts in a specific way.

[0110] In the description of the embodiments of the present application, unless otherwise specified, “ / ” means or, for example, A / B can mean A or B; the “and / or” in the text is merely a description of the association relationship of associated objects, indicating that three relationships may exist, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, “multiple” refers to two or more than two.

[0111] In some processes described in the embodiments of the present application, multiple operations or steps that appear in a specific order are included, but it should be understood that these operations or steps may not be executed in the order in which they appear in the embodiments of the present application or in parallel, and the sequence number of the operation is only used to distinguish the different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed in sequence or in parallel, and these operations or steps may be combined.

[0112] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, disk, CD) as described above, and includes a number of instructions for a terminal device to execute the methods described in each embodiment of the present application.

[0113] The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A vehicle component software full life cycle management method, characterized in that: The vehicle component software full life cycle management method includes: Release component design files during the vehicle development and design phase, where the component design files contain detailed information on the vehicle's software and hardware; Deliver the component design file to the downstream link, and extract the software and hardware version information and component information from the vehicle software and hardware detailed information; Prepare materials for vehicle production based on the parts information, and verify the software and hardware version information of the parts according to the order information; Obtain the software and hardware version information of the components, and compare it with the software version information flashed inside the corresponding controller of the vehicle to verify whether the software flashed inside the controller is correct.

2. A vehicle component software full life cycle management method as claimed in claim 1, characterized in that: The release of component design documents during the vehicle development and design phase specifically includes: Release component design documents during vehicle development and design; Link the parts information to the corresponding vehicle model.

3. A vehicle component software full life cycle management method as claimed in claim 1, characterized in that: The transmitting of the component design file to the downstream link and the extraction of software and hardware version information and component information in the vehicle software and hardware detailed information specifically include: Automatically transfer the released component design files to downstream links, including procurement, manufacturing and after-sales service; Identify component design files and extract software and hardware version information and component information from vehicle hardware and software details.

4. A vehicle component software full life cycle management method as claimed in claim 1, characterized in that: The preparing materials for vehicle production based on the parts information and verifying the software and hardware version information of the parts according to the order information specifically includes: When there is a production demand for a vehicle model, the purchasing department sends the parts information to the supplier for the supply of the vehicle in preparation for production, or prepares the materials for vehicle production on its own; When the supplier has completed delivery or the purchasing department has completed material preparation, before the vehicle enters final assembly production, the software and hardware version information of the parts will be verified based on the vehicle production order information.

5. A vehicle component software full life cycle management method as claimed in claim 1, characterized in that: The acquisition of the software and hardware version information of the components and comparison with the software version information flashed inside the corresponding controller of the vehicle to verify whether the software flashed inside the controller is correct specifically includes: When the vehicle is assembled, the software and hardware version information bound to the parts is obtained to form the software and hardware version information library of the current vehicle, and it is bound to the vehicle identification code; Read the software version information inside the vehicle controller and compare it with the software version information in the software and hardware version information library to verify whether the software flashed inside the controller is correct.

6. A vehicle component software full life cycle management method as claimed in claim 5, characterized in that: The verification of whether the software written in the controller is correct specifically includes: If the software version information read from the vehicle controller is consistent with the software version information in the software and hardware version information library, it means that the software flashed inside the vehicle controller is correct; If the software version information read from the vehicle controller is inconsistent with the software version information in the software and hardware version information library, it indicates that the software flashed inside the vehicle controller is wrong, and the vehicle controller needs to be re-flashed.

7. A vehicle component software full life cycle management method as claimed in claim 5, characterized in that: The vehicle component software full life cycle management method also includes: When a vehicle enters the market, if the software version of the vehicle controller changes, the hardware version information is checked through the vehicle identification code to confirm whether the new software is compatible with the hardware: If compatible, the corresponding software will be updated through OTA or offline service, and the update record will be saved; If incompatible, no processing will be performed.

8. A vehicle component software full life cycle management device, characterized in that: The vehicle component software full life cycle management device comprises: A publishing module, which is used to publish component design files during the vehicle development and design phase, wherein the component design files contain detailed information about the vehicle's software and hardware; A transfer module, which is used to transfer the component design file to the downstream link and extract the software and hardware version information and component information from the vehicle software and hardware detailed information; A verification module, which is used to prepare materials for vehicle production based on the parts information and verify the software and hardware version information of the parts according to the order information; The determination module is used to obtain the software and hardware version information of the components and compare it with the software version information flashed inside the corresponding controller of the vehicle to verify whether the software flashed inside the controller is correct.

9. A vehicle component software full life cycle management device, characterized in that: The vehicle component software full life cycle management device includes a processor, a memory, and a vehicle component software full life cycle management program stored in the memory and executable by the processor, wherein when the vehicle component software full life cycle management program is executed by the processor, the steps of the vehicle component software full life cycle management method as described in any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a vehicle component software full life cycle management program, wherein the vehicle component software full life cycle management program, when executed by the processor, implements the steps of the vehicle component software full life cycle management method as described in any one of claims 1 to 7.

Images