Production line software breakpoint method, device and equipment based on OTA and storage medium
By dynamically calculating and automatically upgrading the software flashing package of the entire vehicle ECU in the vehicle's infotainment system controller, the problem of a large number of vehicle ECUs and frequent software changes has been solved. This has enabled an efficient and scalable OTA upgrade solution, improving vehicle off-line quality and circulation efficiency while reducing costs.
Patent Information
- Application Number
- CN202511200550.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-08-26
- Publication Date
- 2025-11-07
AI Technical Summary
Existing OTA upgrade solutions cannot cover the application scenarios within the production line where there are many ECUs and frequent software changes, resulting in poor vehicle quality, low turnover efficiency, high production line software flashing costs, poor scalability and flexibility, and the flashing of small-capacity controllers relies on manual work, wasting a lot of manpower.
By dynamically calculating the controllers that need software updates during vehicle assembly, the software flashing packages are imported into the reserved storage area of the vehicle controller. After the vehicle assembly is completed, the over-the-air (OTA) component in the vehicle controller calls these packages for upgrades. After verification, these packages are deleted at the PDI (Product Inspection) station before delivery.
It enables automated writing of high-capacity controllers, reduces reliance on manual labor, improves vehicle off-line quality and production line efficiency, reduces costs, and has scalability and flexibility, improving writing efficiency and speed.
Smart Images

Figure CN120909623A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of OTA upgrading, in particular to an OTA-based production line software breakpoint method, device, equipment and storage medium. BACKGROUND
[0002] The existing patent-CN118363622A-OTA upgrading method, device and vehicle-mounted remote control equipment discloses an OTA upgrading method, device and vehicle-mounted remote control equipment, the method comprising: an over the air (OTA) server of a TBOX responds to a first event of calling a flashing interface of an OTA component, stores first event header information corresponding to the first event to a first preset area of the memory; sends the first event to a micro control unit, so that the micro control unit performs a flashing operation of an OTA upgrade package on the to-be-upgraded controller based on the first event; in the case of receiving the flashing result corresponding to the first event returned by the micro control unit, obtaining the first event header information from the first preset area; based on the first event header information, return the flashing result to the OTA component. Wherein, by opening a special area (i.e. the first preset area) in the memory to store the first event header information, OTA parallel failure caused by the first event header information being overwritten can be avoided, and the success rate of OTA parallel upgrading is improved.
[0003] However, it has the following technical defects: the OTA component usage range does not cover the production line, and the application scenario is lacking.
[0004] And the existing technology needs to invest in power supply lines and a large number of equipment to realize production line software flashing; and the fixed area performs flashing, which is not flexible enough; small capacity controller flashing relies on manual completion, which wastes a lot of manpower cost.
[0005] The host factory can already solve the software breakpoint of large-capacity memory such as car controller and intelligent driving controller, but the number of small-capacity ECUs of the whole vehicle is large and the software changes frequently, and the inventory iteration is still a difficult problem that affects the vehicle flow and the quality of vehicle downlink. The existing scheme cannot solve this application scenario. SUMMARY
[0006] The main purpose of the present application is to provide an OTA-based production line software breakpoint method, device, equipment and storage medium, which aims to solve the technical problems in the prior art that the number of ECUs of the whole vehicle is large and the software changes frequently, the existing OTA upgrading scheme cannot cover the application scenario in the production line, resulting in poor vehicle downlink quality, low flow efficiency, high production line software flashing cost, poor expansibility and flexibility, small-capacity controller flashing relying on manual completion, and wasting a lot of manpower.
[0007] In a first aspect, the present application provides an OTA-based production line software breakpoint method, comprising the following steps: dynamically calculating a to-be-updated controller that needs software updating in vehicle assembly, and importing a software flashing package of the to-be-updated controller into a reserved storage area of a vehicle controller; after detecting that the vehicle assembly is completed, triggering an over-the-air (OTA) component in the vehicle controller to call the software flashing package in the reserved storage area to perform controller upgrading; performing verification on the software flashing package after flashing, and deleting the software flashing package in the reserved storage area through pre-delivery inspection (PDI) after verification passes.
[0008] Optionally, the step of dynamically calculating a to-be-updated controller that needs software updating in vehicle assembly, and importing a software flashing package of the to-be-updated controller into a reserved storage area of a vehicle controller comprises: dynamically calculating a to-be-updated controller that needs software updating in vehicle assembly through linkage between a manufacturing execution system (MES) and a software baseline management system (SBMS); importing the software flashing package of the to-be-updated controller into the reserved storage area of the vehicle controller through a single-piece flashing station.
[0009] Optionally, the step of dynamically calculating a to-be-updated controller that needs software updating in vehicle assembly through linkage between a manufacturing execution system (MES) and a software baseline management system (SBMS) comprises: comparing software of each controller in a vehicle through the manufacturing execution system (MES) and the software baseline management system (SBMS), and sending software difference information to a flashing control system; dynamically calculating a to-be-updated controller that needs software updating in vehicle assembly through the flashing control system.
[0010] Optionally, the step of importing the software flashing package of the to-be-updated controller into the reserved storage area of the vehicle controller through a single-piece flashing station comprises: receiving the software flashing package of the to-be-updated controller according to a preset flashing instruction through the single-piece flashing station, and importing the software flashing package into the reserved storage area of the vehicle controller.
[0011] Optionally, the step of, after detecting that the vehicle assembly is completed, triggering an over-the-air (OTA) component in the vehicle controller to call the software flashing package in the reserved storage area to perform controller upgrading comprises: after detecting that the vehicle assembly is completed and the vehicle is powered on, automatically triggering the over-the-air (OTA) component in the vehicle controller to call the software flashing package in the reserved storage area; According to the software flashing package, the upgrade flashing operation on the to-be-updated controller is completed.
[0012] Optionally, the software flashing package after flashing is checked, and the software flashing package in the reserved storage area is deleted by pre-delivery inspection (PDI) after the checking is passed. After detecting that the to-be-inspected vehicle arrives at the electrical inspection station, a current software version of the software flashing package after flashing of the to-be-inspected vehicle is obtained, and the current software version is checked with a version number of a corresponding latest software version. When the version number of the current software version is consistent with the version number of the latest software version, it is determined that the checking is passed. After detecting that the to-be-inspected vehicle arrives at the pre-delivery inspection (PDI) station, the software flashing package in the reserved storage area is deleted.
[0013] Optionally, after detecting that the to-be-inspected vehicle arrives at the pre-delivery inspection (PDI) station, the software flashing package in the reserved storage area is deleted.
[0014] After detecting that the to-be-inspected vehicle arrives at the pre-delivery inspection (PDI) station, a software package deletion instruction is received through the vehicle machine controller, and the software flashing package in the reserved storage area is deleted in response to the software package deletion instruction.
[0015] In a second aspect, to achieve the above object, the present application further provides an OTA-based production line software breakpoint device, which comprises: A dynamic calculation module is configured to dynamically calculate a to-be-updated controller that needs software updating in vehicle assembly, and to import a software flashing package of the to-be-updated controller into a reserved storage area of a vehicle machine controller. An upgrade module is configured to trigger an over-the-air (OTA) component in the vehicle machine controller to call the software flashing package in the reserved storage area to perform controller upgrade after detecting that the vehicle assembly is completed. A checking and deleting module is configured to check the software flashing package after flashing, and to delete the software flashing package in the reserved storage area by pre-delivery inspection (PDI) after the checking is passed.
[0016] In a third aspect, to achieve the above object, the present application further provides an OTA-based production line software breakpoint device, which comprises a memory, a processor, and an OTA-based production line software breakpoint program stored in the memory and capable of running on the processor, and the OTA-based production line software breakpoint program is configured to implement the steps of the OTA-based production line software breakpoint method as described above.
[0017] In a fourth aspect, to achieve the above object, the present application further provides a storage medium, wherein the storage medium stores an OTA-based production line software breakpoint program, and the OTA-based production line software breakpoint program, when executed by a processor, implements the steps of the OTA-based production line software breakpoint method as described above.
[0018] The OTA-based production line software breakpoint method provided by the present application can dynamically calculate a to-be-updated controller that needs software updating in vehicle assembly, import a software flashing package of the to-be-updated controller into a reserved storage area of a vehicle controller, trigger an over-the-air (OTA) component in the vehicle controller to call the software flashing package in the reserved storage area for controller upgrading after detecting that the vehicle assembly is completed, and check the software flashing package after flashing, and delete the software flashing package in the reserved storage area through pre-delivery inspection (PDI) after the check is passed, so that the software flashing of a large-capacity controller can be implemented without relying on manual flashing, the quality of vehicle off-line is improved, the production line turnover efficiency is improved, the production line software flashing cost is reduced, the OTA-based production line software breakpoint method has scalability and flexibility, the software flashing is stable and reliable, the downloading time is reduced, the software flashing efficiency is improved, and the implementation speed and efficiency of the OTA-based production line software breakpoint method are improved. BRIEF DESCRIPTION OF DRAWINGS
[0019] Figure 1 A device structure schematic diagram of a hardware running environment related to an embodiment of the present application; Figure 2 A flowchart of an OTA-based production line software breakpoint method first embodiment of the present application; Figure 3 A flowchart of an OTA-based production line software breakpoint method second embodiment of the present application; Figure 4 A flowchart of an OTA-based production line software breakpoint method third embodiment of the present application; Figure 5 A flowchart of an OTA-based production line software breakpoint method fourth embodiment of the present application; Figure 6 A functional module diagram of an OTA-based production line software breakpoint device first embodiment of the present application.
[0020] The implementation, functional features and advantages of the present application will be further described with reference to the embodiments and the accompanying drawings. DETAILED DESCRIPTION
[0021] It should be understood that the specific embodiments described herein are merely intended to explain the present application, and are not intended to limit the present application.
[0022] The solution of the embodiment of the present application is mainly: through dynamically calculating a to-be-updated controller needing software updating in vehicle assembly, a software flashing package of the to-be-updated controller is imported into a reserved storage area of a vehicle controller; after detecting that the vehicle assembly is completed, triggering an over-the-air (OTA) component in the vehicle controller to call the software flashing package in the reserved storage area to perform controller upgrading; verifying the software flashing package after flashing, and after verification, deleting the software flashing package in the reserved storage area through pre-delivery inspection (PDI), so that the flashing of a large-capacity controller can be realized, without relying on manual flashing, improving vehicle offline quality, improving production line circulation efficiency, reducing production line software flashing cost, having scalability and flexibility, stable and reliable flashing, reducing download time, improving flashing efficiency, improving the implementation speed and efficiency of the production line software breakpoint based on OTA, solving the technical problems in the prior art that the number of vehicle ECUs is large, software changes frequently, the existing OTA upgrading scheme cannot cover the application scenarios in the production line, resulting in poor vehicle offline quality, low circulation efficiency, high production line software flashing cost, poor scalability and flexibility, and manual completion of small-capacity controller flashing, wasting a large amount of manpower.
[0023] Reference Figure 1 , Figure 1 The device structure diagram of the hardware running environment involved in the embodiment of the present application is shown in the following table.
[0024] As shown in the following table, Figure 1 The device can include a processor 1001, such as a CPU, a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. The communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 can include a display screen (Display) and an input unit such as a keyboard (Keyboard). The optional user interface 1003 can also include a standard wired interface, a wireless interface. The network interface 1004 can optionally include a standard wired interface, a wireless interface (such as a Wi-Fi interface). The memory 1005 can be a high-speed RAM memory, or a stable memory (Non-Volatile Memory), such as a disk memory. The memory 1005 can also be an independent storage device from the aforementioned processor 1001.
[0025] Those skilled in the art can understand that Figure 1 The device structure shown in the table does not constitute a limitation on the device, and can include more or fewer components than the table, or combine certain components, or different component arrangements.
[0026] As shown in the following table, Figure 1As shown, the memory 1005 as a storage medium can include an operation device, a network communication module, a user interface module and an OTA-based production line software breakpoint program.
[0027] The device of the application calls the OTA-based production line software breakpoint program stored in the memory 1005 through the processor 1001, and performs the following operations: The software update controller to be updated in the whole vehicle assembly is dynamically calculated, and the software flashing package of the controller to be updated is imported into the reserved storage area of the vehicle controller. After detecting that the whole vehicle assembly is completed, the over-the-air download OTA component in the vehicle controller is triggered to call the software flashing package in the reserved storage area for controller upgrade. The software flashing package after flashing is verified, and after verification, the software flashing package in the reserved storage area is deleted through pre-delivery inspection PDI.
[0028] The device of the application calls the OTA-based production line software breakpoint program stored in the memory 1005 through the processor 1001, and performs the following operations: Through the linkage of the manufacturing execution system MES and the software baseline management system SBMS, the software update controller to be updated in the whole vehicle assembly is dynamically calculated. The software flashing package of the controller to be updated is imported into the reserved storage area of the vehicle controller through the single-piece flashing station.
[0029] The device of the application calls the OTA-based production line software breakpoint program stored in the memory 1005 through the processor 1001, and performs the following operations: Through the software comparison of each controller of the whole vehicle by the manufacturing execution system MES and the software baseline management system SBMS, the software difference information is sent to the flashing control system. The controller to be updated in each controller of the whole vehicle assembly is dynamically calculated by the flashing control system.
[0030] The device of the application calls the OTA-based production line software breakpoint program stored in the memory 1005 through the processor 1001, and performs the following operations: The software flashing package of the controller to be updated is received according to the preset flashing instruction through the single-piece flashing station, and the software flashing package is imported into the reserved storage area of the vehicle controller.
[0031] The device of the application calls the OTA-based production line software breakpoint program stored in the memory 1005 through the processor 1001, and performs the following operations: After detecting that the whole vehicle assembly is completed and the whole vehicle is powered on, the software flashing package in the reserved storage area is automatically triggered and called by an over-the-air (OTA) component in the vehicle controller; According to the software flashing package, an upgrade flashing operation on the to-be-updated controller is completed.
[0032] The device of the application calls the OTA-based production line software breakpoint program stored in the memory 1005 through the processor 1001, and further performs the following operations: After detecting that the to-be-inspected vehicle arrives at the electrical inspection station, the current software version of the software flashing package after flashing of the to-be-inspected vehicle is obtained, and the current software version is checked with the version number of the corresponding latest software version; When the version number of the current software version is consistent with the version number of the latest software version, it is determined that the check is passed; After detecting that the to-be-inspected vehicle arrives at the pre-delivery inspection (PDI) station, the software flashing package in the reserved storage area is deleted.
[0033] The device of the application calls the OTA-based production line software breakpoint program stored in the memory 1005 through the processor 1001, and further performs the following operations: After detecting that the to-be-inspected vehicle arrives at the pre-delivery inspection (PDI) station, the software flashing package in the reserved storage area is deleted.
[0034] The embodiment calculates the to-be-updated controller that needs software updating in the whole vehicle assembly through the above scheme, imports the software flashing package of the to-be-updated controller into the reserved storage area of the vehicle controller, triggers the over-the-air (OTA) component in the vehicle controller to call the software flashing package in the reserved storage area for controller upgrade after detecting that the whole vehicle assembly is completed, checks the software flashing package after flashing, deletes the software flashing package in the reserved storage area through the pre-delivery inspection (PDI) after the check is passed, can realize flashing of a large-capacity controller without relying on manual flashing, improves vehicle off-line quality, improves production line flow efficiency, reduces production line software flashing cost, has scalability and flexibility, is stable and reliable in flashing, reduces download time, improves flashing efficiency, improves the implementation speed and efficiency of the OTA-based production line software breakpoint, and has scalability and flexibility.
[0035] Based on the above hardware structure, the OTA-based production line software breakpoint method embodiment of the application is proposed.
[0036] Reference Figure 2 , Figure 2 The flowchart of the first embodiment of the OTA-based production line software breakpoint method of the application is shown.
[0037] In the first embodiment, the OTA-based production line software breakpoint method comprises the following steps: Step S10, dynamically calculating a to-be-updated controller needing software updating in vehicle assembly, and importing a software flashing package of the to-be-updated controller into a reserved storage area of a vehicle controller.
[0038] It should be noted that the to-be-updated controller needing software updating in the vehicle production line vehicle assembly process can be determined by dynamic calculation, and then the software flashing package of the to-be-updated controller needing updating is imported into the reserved storage area of the vehicle controller.
[0039] In specific implementation, the to-be-updated controller refers to a small-capacity electronic control unit (ECU) in a vehicle, such as a body control module (BCM), a vehicle lamp control unit, an air conditioning control unit, etc., which usually has a small storage space and frequent software updating requirements; the vehicle controller is an in-vehicle infotainment (IVI) controller, which usually has a large storage capacity and is used to process multimedia, navigation, voice interaction, etc. The vehicle controller is built-in with an OTA component for triggering software updating of other controllers, and a storage area is reserved for temporarily storing software flashing packages of other controllers.
[0040] Step S20, after detecting that the vehicle assembly is completed, triggering the over-the-air (OTA) component in the vehicle controller to call the software flashing package in the reserved storage area for controller upgrading.
[0041] It should be understood that after detecting that the vehicle needing upgrading is completed, the over-the-air (OTA) component of the vehicle controller can be triggered to call the software flashing package in the reserved storage area for controller upgrading.
[0042] Step S30, verifying the software flashing package after flashing, and deleting the software flashing package in the reserved storage area through pre-delivery inspection (PDI) after verification.
[0043] It can be understood that after verifying the software flashing package after flashing, the software flashing package in the reserved storage area can be deleted through pre-delivery inspection (PDI) after verification.
[0044] The embodiment calculates the to-be-updated controller needing software updating in vehicle assembly through dynamic calculation, imports the software flashing package of the to-be-updated controller into the reserved storage area of the vehicle controller, triggers the over-the-air (OTA) component in the vehicle controller to call the software flashing package in the reserved storage area for controller upgrading after detecting that the vehicle assembly is completed, checks the software flashing package after flashing, and deletes the software flashing package in the reserved storage area through pre-delivery inspection (PDI) after passing the check, so that the software flashing of a large-capacity controller can be implemented without relying on manual flashing, the vehicle offline quality is improved, the production line circulation efficiency is improved, the production line software flashing cost is reduced, the method has scalability and flexibility, the flashing is stable and reliable, the downloading time is reduced, the flashing efficiency is improved, and the implementation speed and efficiency of the production line software breakpoint based on OTA are improved.
[0045] Further, Figure 3 The flowchart of the second embodiment of the OTA-based production line software breakpoint method of the present application is shown in Figure 3 The second embodiment of the OTA-based production line software breakpoint method of the present application is proposed based on the first embodiment, and in the embodiment, the step S10 specifically includes the following steps. In step S11, the to-be-updated controller needing software updating in vehicle assembly is dynamically calculated through the linkage of the manufacturing execution system (MES) and the software baseline management system (SBMS).
[0046] It should be noted that the to-be-updated controller needing software updating in vehicle assembly can be dynamically calculated through the linkage of the manufacturing execution system (MES) and the software baseline management system (SBMS).
[0047] Further, the step S11 specifically includes the following steps. The software of each controller of the vehicle is compared through the manufacturing execution system (MES) and the software baseline management system (SBMS), and the software difference information is sent to the flashing control system. The to-be-updated controller needing software updating in vehicle assembly is dynamically calculated through the flashing control system.
[0048] It can be understood that the software of each controller of the vehicle is compared through the manufacturing execution system (MES) and the software baseline management system (SBMS), and the software difference information is sent to the flashing control system. The to-be-updated controller needing software updating in vehicle assembly can be dynamically calculated through the flashing control system.
[0049] Step S12, the software flashing package of the to-be-updated controller is imported into the reserved storage area of the car machine controller through the single-piece flashing station.
[0050] It should be understood that the software flashing package of the to-be-updated controller can be imported into the reserved storage area of the car machine controller through the single-piece flashing station.
[0051] Further, the step S12 specifically includes the following steps: The single-piece flashing station receives the software flashing package of the to-be-updated controller according to the preset flashing instruction, and imports the software flashing package into the reserved storage area of the car machine controller.
[0052] It can be understood that the single-piece flashing station of the car machine transmits the upgrade package to the car machine through the flashing control system, and after completing the software flashing of the car machine controller, the single-piece flashing station flashes the dynamically calculated to-be-updated controller to the designated storage area of the car machine through the preset instruction.
[0053] In specific implementation, before dynamic calculation, the single-piece flashing station and the electrical inspection system, the software management system, the manufacturing system, etc. can be imported, the flashing controller system is developed, the difference controller is dynamically calculated, the to-be-updated controller information and version are obtained, the controller system is developed, the to-be-updated controller task is issued to the single-piece flashing station, and after the car machine controller is upgraded, the single-piece flashing station transmits the to-be-updated controller software package to the designated memory of the car machine controller, that is, to the reserved storage area.
[0054] Through the above scheme, the to-be-updated controller needing software updating in the whole vehicle assembly is dynamically calculated through the linkage of the manufacturing execution system MES and the software baseline management system SBMS in the embodiment; the software flashing package of the to-be-updated controller is imported into the reserved storage area of the car machine controller through the single-piece flashing station, so that the flashing of the large-capacity controller can be realized, the artificial flashing is not needed, the vehicle off-line quality is improved, and the production line circulation efficiency is improved.
[0055] Further, Figure 4 The flowchart of the third embodiment of the OTA-based production line software breakpoint method of the application is shown in FIG. 6. Figure 4 The third embodiment of the OTA-based production line software breakpoint method of the application is proposed based on the first embodiment, and in the embodiment, the step S20 specifically includes the following steps: Step S21, after detecting that the whole vehicle assembly is completed and the whole vehicle is powered on, the software flashing package in the reserved storage area is automatically triggered and called through the over-the-air download (OTA) component in the car machine controller.
[0056] It should be noted that after detecting that the whole vehicle assembly is completed and detecting that the whole vehicle is powered on, the software flashing package in the reserved storage area can be automatically triggered and called by the over-the-air (OTA) component in the vehicle machine controller.
[0057] In a specific implementation, after the whole vehicle assembly is completed and the whole vehicle is powered on, the OTA component in the vehicle machine automatically triggers the stored flashing package upgrade operation.
[0058] Step S22, according to the software flashing package, the upgrade flashing operation of the to-be-updated controller is completed.
[0059] It can be understood that, according to the software flashing package, the upgrade flashing operation of the to-be-updated controller can be completed.
[0060] It should be noted that the OTA component in the embodiment has two modes, namely factory mode and user mode, which can be switched by external instructions. The OTA component defaults to factory mode and switches to user mode (i.e. traditional OTA component state) when it is put into storage after completing all detections. In factory mode, the OTA component can realize traditional online flashing. The OTA component in factory mode can receive the in-field upgrade task issued by the platform. The platform dynamically issues upgrade requirements according to the target version and the current vehicle software version.
[0061] In a specific implementation, the vehicle machine controller with the embedded OTA component completes software filling in the factory. The OTA component has about 5G (customizable development) memory. In the state that the vehicle machine controller has not been installed in the vehicle, the vehicle machine controller is flashed by single-piece flashing. After completing the upgrade of the vehicle machine controller itself, the software difference list issued by the platform is received, and the software package that needs to be upgraded for the vehicle model is imported into the memory of the OTA component in advance. After the vehicle machine controller completes assembly, the platform receives information and issues upgrade instructions to the OTA component through the industrial network after the vehicle machine controller meets the upgrade conditions on the production line. This process eliminates the process of downloading the upgrade package because the controller software package that needs to be upgraded has been imported in advance. The OTA component is embedded, and the flashing of the required controller of the whole vehicle is completed when the vehicle is still in the assembly and circulation process on the production line.
[0062] The embodiment can realize the flashing of large-capacity controllers without relying on manual flashing, improve the vehicle off-line quality, improve the production line circulation efficiency, and improve the implementation speed and efficiency of the production line software breakpoint based on OTA.
[0063] Further, Figure 5 A flowchart of a fourth embodiment of the OTA-based production line software breakpoint method of the present application is shown in FIG. 4. Figure 5 As shown in FIG. 4, the fourth embodiment of the OTA-based production line software breakpoint method of the present application is based on the first embodiment, and in this embodiment, the step S30 specifically includes the following steps: Step S31: After detecting that the vehicle to be inspected arrives at the electrical inspection station, the current software version of the software flashing package after flashing of the vehicle to be inspected is obtained, and the current software version is checked against the version number of the corresponding latest software version.
[0064] It should be noted that after detecting that the vehicle to be inspected arrives at the electrical inspection station, the current software version of the software flashing package after flashing of the vehicle to be inspected can be obtained. By comparing the current software version with the version number of the corresponding latest software version, the version number can be checked, i.e., it can be determined whether the current software version of the software flashing package is the latest version.
[0065] Step S32: When the version number of the current software version is consistent with the version number of the latest software version, it is determined that the check is passed.
[0066] It can be understood that when the version number of the current software version is consistent with the version number of the latest software version, it can be determined that the check is passed, i.e., at this time, the software flashing package is the latest software flashing package.
[0067] Step S33: After detecting that the vehicle to be inspected arrives at the pre-delivery inspection (PDI) station, the software flashing package in the reserved storage area is deleted.
[0068] It should be understood that after detecting that the vehicle to be inspected arrives at the pre-delivery inspection (PDI) station, the software flashing package in the reserved storage area can be deleted, thereby releasing the memory of the vehicle machine controller.
[0069] In a specific implementation, after the upgrade is completed, the whole vehicle is inspected to meet the warehouse entry standard, then the electrical inspection is performed, the OTA component is switched from the factory mode to the user mode, after the OTA component is switched to the user mode, the after-sales operation and maintenance personnel can issue an OTA upgrade task to the user vehicle according to the normal user upgrade demand, which is similar to the traditional OTA function.
[0070] It can be understood that the OTA component has higher flexibility in the factory mode, data transmission through the industrial network is safer, authentication is simplified, and the controller software package that needs to be flashed has been delivered to the OTA component in advance by flashing the single vehicle machine controller, reducing the time needed for downloading, maximizing the upgrade process, avoiding upgrade failure caused by additional software download, and additional time-consuming problems; The OTA component supports parallel flashing and can upgrade different controllers at the same time to improve upgrade efficiency. The platform can dynamically upgrade the parallel upgrade sequence according to the controller category that needs to be upgraded, and then the OTA component upgrades in the corresponding order according to the sequence issued by the platform. The OTA component is in the form of software, which is more flexible and has no device and station restrictions. As long as the vehicle state meets the requirements on the production line, software flashing can be started, which truly helps to realize the demand of controller software and hardware separation of the host factory, and the software version of all controllers is controlled by the host factory, reducing the investment of software switching iteration.
[0071] Further, the step S33 specifically includes the following steps: After detecting that the vehicle to be detected reaches the PDI station, the vehicle machine controller receives a software package deletion instruction, and in response to the software package deletion instruction, the software flashing package in the reserved storage area is deleted.
[0072] It can be understood that after the upgrade is completed, the vehicle reaches the electrical inspection station and is checked according to the latest software version. After the vehicle controller software package is upgraded, the vehicle reaches the PDI station, and the device sends a software package deletion instruction to the vehicle machine controller, and the vehicle machine controller deletes the stored flashing package to release the memory.
[0073] In specific implementation, after the whole vehicle assembly is completed and the vehicle completes the high voltage, the OTA component in the vehicle machine detects the high voltage and automatically executes the stored flashing package flashing. Taking 2 electrical inspection stations and 1 PDI station as an example, after the vehicle reaches the 2 electrical inspection stations, the software version is checked after the flashing is completed in the electrical inspection station combined with the latest software version. After the vehicle reaches the PDI station, a software package deletion instruction is sent to the vehicle machine controller, and the vehicle machine controller deletes the stored flashing package according to the software package deletion instruction.
[0074] It should be noted that this embodiment can solve the flashing problem of all high-capacity controllers, improving flashing efficiency. The single flashing station can be pre-stored, so the upgrade package of the controller to be flashed can be imported in advance, which is feasible. Through the OTA component, the flashing is stable and reliable. The flashing station is preset in advance, reducing download time and ensuring flashing reliability. By integrating existing resources to realize the flashing of the whole vehicle controller, it is possible to realize the flashing of small-capacity controllers with minimal investment, which reflects economic efficiency. Furthermore, the OTA component can dynamically determine the flashing order and adopt parallel flashing to improve flashing efficiency, which has scalability.
[0075] This embodiment, through the above-described scheme, dynamically calculates the controllers requiring software updates during vehicle assembly and imports their software flashing packages into the reserved storage area of the vehicle controller. Upon detection of completed vehicle assembly, the over-the-air (OTA) component within the vehicle controller is triggered to call the software flashing package in the reserved storage area to upgrade the controller. The flashed software flashing package is then verified; if successful, it is deleted from the reserved storage area via a pre-delivery inspection (PDI). This approach enables flashing of large-capacity controllers without manual intervention, improving vehicle off-line quality, increasing production line efficiency, reducing production line software flashing costs, and providing scalability, flexibility, stable and reliable flashing, reduced download time, and improved flashing efficiency. It also enhances the speed and efficiency of OTA-based production line software breakpoint implementation.
[0076] Accordingly, the present invention further provides a production line software breakpoint device based on OTA.
[0077] Reference Figure 6 , Figure 6 This is a functional block diagram of the first embodiment of the production line software breakpoint device based on OTA of the present invention.
[0078] In the first embodiment of the OTA-based production line software breakpoint device of the present invention, the OTA-based production line software breakpoint device includes: The dynamic calculation module 10 is used to dynamically calculate the controllers that need software updates during vehicle assembly and import the software flashing package of the controllers to be updated into the reserved storage area of the vehicle controller.
[0079] Upgrade module 20 is used to trigger the over-the-air (OTA) download component in the vehicle controller to call the software flashing package in the reserved storage area to upgrade the controller after detecting that the vehicle assembly is completed.
[0080] The verification and deletion module 30 is used to verify the software flashing package after it has been flashed. After the verification is passed, the software flashing package is deleted from the reserved storage area by the pre-delivery inspection (PDI).
[0081] The dynamic calculation module 10 is further configured to dynamically calculate, by linkage between a manufacturing execution system (MES) and a software baseline management system (SBMS), a to-be-updated controller needing software updating in vehicle assembly; and guide a software flashing package of the to-be-updated controller into a reserved storage area of a vehicle controller through a single-piece flashing station.
[0082] The dynamic calculation module 10 is further configured to compare software of each controller in vehicle assembly through the manufacturing execution system (MES) and the software baseline management system (SBMS), send software difference information to a flashing control system, and dynamically calculate, by the flashing control system, the to-be-updated controller needing software updating in each controller in vehicle assembly.
[0083] The dynamic calculation module 10 is further configured to guide, by the single-piece flashing station, the software flashing package of the to-be-updated controller into the reserved storage area of the vehicle controller according to a preset flashing instruction.
[0084] The upgrade module 20 is further configured to automatically trigger and call the software flashing package in the reserved storage area through an over-the-air (OTA) component in the vehicle controller after detecting that vehicle assembly is completed and the vehicle is powered on, and complete upgrade and flashing operation on the to-be-updated controller according to the software flashing package.
[0085] The verification and deletion module 30 is further configured to acquire a current software version of the software flashing package after flashing of a to-be-inspected vehicle after detecting that the to-be-inspected vehicle arrives at an electrical inspection station, verify the current software version with a version number of a latest software version, determine that verification is passed when the version number of the current software version is consistent with the version number of the latest software version, and delete the software flashing package in the reserved storage area after detecting that the to-be-inspected vehicle arrives at a pre-delivery inspection (PDI) station.
[0086] The verification and deletion module 30 is further configured to receive a software package deletion instruction through the vehicle controller after detecting that the to-be-inspected vehicle arrives at the pre-delivery inspection (PDI) station, and delete the software flashing package in the reserved storage area in response to the software package deletion instruction.
[0087] The steps of each functional module of the OTA-based production line software breakpoint device can refer to each embodiment of the OTA-based production line software breakpoint method of the present application, which will not be described here again.
[0088] In addition, an embodiment of the present application further provides a storage medium, and the storage medium stores an OTA-based production line software breakpoint program. When the OTA-based production line software breakpoint program is executed by a processor, the following operations are implemented: The software update controller to be updated in vehicle assembly is dynamically calculated, and a software flashing package of the software update controller is imported into a reserved storage area of a vehicle controller; After detecting that the vehicle assembly is completed, an over-the-air (OTA) component in the vehicle controller is triggered to call the software flashing package in the reserved storage area to perform controller upgrading; The software flashing package after flashing is verified, and the software flashing package in the reserved storage area is deleted through pre-delivery inspection (PDI) after verification.
[0089] Further, the OTA-based production line software breakpoint program executed by the processor further implements the following operations: The software update controller to be updated in vehicle assembly is dynamically calculated through linkage between a manufacturing execution system (MES) and a software baseline management system (SBMS); The software flashing package of the software update controller is imported into a reserved storage area of a vehicle controller through a single-piece flashing station.
[0090] Further, the OTA-based production line software breakpoint program executed by the processor further implements the following operations: Software of each controller in the vehicle is compared through a manufacturing execution system (MES) and a software baseline management system (SBMS), and software difference information is sent to a flashing control system; The software update controller to be updated in vehicle assembly is dynamically calculated through the flashing control system.
[0091] Further, the OTA-based production line software breakpoint program executed by the processor further implements the following operations: The software flashing package of the software update controller is imported into a reserved storage area of a vehicle controller through a single-piece flashing station according to a preset flashing instruction.
[0092] Further, the OTA-based production line software breakpoint program executed by the processor further implements the following operations: After detecting that the vehicle assembly is completed and the vehicle is powered on, the software flashing package in the reserved storage area is automatically triggered and called through an over-the-air (OTA) component in the vehicle controller; The software update controller to be updated is upgraded and flashed according to the software flashing package.
[0093] Further, the OTA-based production line software breakpoint program executed by the processor further implements the following operations: After detecting that the to-be-inspected vehicle arrives at the electrical inspection station, a current software version of the software flashing package after being flashed by the to-be-inspected vehicle is acquired, and the current software version is checked with a version number of a corresponding latest software version; When the version number of the current software version is consistent with the version number of the latest software version, it is determined that the checking is passed. After detecting that the to-be-inspected vehicle arrives at the pre-delivery inspection (PDI) station, the software flashing package in the reserved storage area is deleted.
[0094] Further, the OTA-based production line software breakpoint program further implements the following operations when executed by the processor: After detecting that the to-be-inspected vehicle arrives at the pre-delivery inspection (PDI) station, a software package deletion instruction is received through the vehicle machine controller, and the software flashing package in the reserved storage area is deleted in response to the software package deletion instruction.
[0095] Those skilled in the art can understand that all or part of the steps in the above-mentioned implementation methods can be completed by programs instructing related hardware, the programs are stored in a storage medium, and the programs include a plurality of instructions for causing an apparatus (which can be a single-chip microcomputer, a chip, etc.) or a processor to execute all or part of the steps of the methods described in the various embodiments of the present application. The foregoing storage medium is a computer-readable storage medium, including a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various media that can store program codes.
[0096] It should be noted that, in this document, the terms "comprising", "containing" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or apparatus that includes a series of elements not only includes those elements, but also includes other elements not explicitly listed or inherent to such a process, method, article or apparatus. Without more limitations, the element defined by the statement "comprising a" does not exclude the presence of another identical element in the process, method, article or apparatus that includes the element.
[0097] The above-mentioned serial numbers of the embodiments of the present application are only for description, and do not represent the advantages or disadvantages of the embodiments.
[0098] The above is only the preferred embodiments of the present application, and does not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation based on the content of the specification and drawings of the present application, or direct or indirect application in other related technical fields, is also included in the patent protection scope of the present application.
Claims
1. An OTA-based method for software breakpoint on a production line, characterized in that, The OTA-based production line software breakpoint method comprises: dynamically calculating a to-be-updated controller needing software updating in vehicle assembly, and importing a software flashing package of the to-be-updated controller into a reserved storage area of a vehicle controller; after detecting that the vehicle assembly is completed, triggering an over-the-air (OTA) component in the vehicle controller to call the software flashing package in the reserved storage area to perform controller upgrading; verifying the software flashing package after flashing, and deleting the software flashing package in the reserved storage area through pre-delivery inspection (PDI) after verification.
2. The OTA-based production line software breakpoint method of claim 1, wherein, The method comprises: linking a manufacturing execution system (MES) and a software baseline management system (SBMS) to dynamically calculate the to-be-updated controller needing software updating in vehicle assembly; importing the software flashing package of the to-be-updated controller into the reserved storage area of the vehicle controller through a single-piece flashing station.
3. The OTA-based production line software breakpoint method of claim 2, wherein, The method comprises: comparing software of each controller in a vehicle through the MES and the SBMS, and sending software difference information to a flashing control system; dynamically calculating the to-be-updated controller needing software updating in vehicle assembly through the flashing control system.
4. The OTA-based production line software breakpoint method of claim 2, wherein, The method comprises: receiving the software flashing package of the to-be-updated controller according to a preset flashing instruction through the single-piece flashing station, and importing the software flashing package into the reserved storage area of the vehicle controller.
5. The OTA-based production line software breakpoint method of claim 1, wherein, The method comprises: after detecting that the vehicle assembly is completed and the vehicle is powered on, automatically triggering the OTA component in the vehicle controller to call the software flashing package in the reserved storage area; performing upgrading and flashing operation on the to-be-updated controller according to the software flashing package.
6. The OTA-based production line software breakpoint method of claim 1, wherein, The method comprises: after detecting that the vehicle arrives at an electrical inspection station, obtaining a current software version of the software flashing package after flashing of the vehicle, and verifying the current software version with a version number of a corresponding latest software version; verifying pass when the version number of the current software version is consistent with the version number of the latest software version; after detecting that the vehicle arrives at a PDI station, deleting the software flashing package in the reserved storage area.
7. The OTA-based production line software breakpoint method of claim 6, wherein, The method comprises: after detecting that the vehicle arrives at the PDI station, deleting the software flashing package in the reserved storage area. After detecting that the vehicle to be tested arrives at a pre-delivery inspection (PDI) station, a software package deletion instruction is received by the vehicle controller, and in response to the software package deletion instruction, the software flashing package in the reserved storage area is deleted.
8. An OTA-based production line software breakpoint apparatus, comprising: The OTA-based production line software breakpoint device comprises: A dynamic calculation module is configured to dynamically calculate a controller to be updated in vehicle assembly, and to import a software flashing package of the controller to be updated into a reserved storage area of a vehicle controller. An upgrade module is configured to trigger an over-the-air (OTA) component in the vehicle controller to call the software flashing package in the reserved storage area to upgrade the controller after detecting that the vehicle assembly is completed. A verification and deletion module is configured to verify the software flashing package after flashing, and to delete the software flashing package in the reserved storage area through pre-delivery inspection (PDI) after verification.
9. An OTA-based line software breakpoint device, comprising: The OTA-based production line software breakpoint device comprises a memory, a processor, and an OTA-based production line software breakpoint program stored in the memory and executable on the processor, and the OTA-based production line software breakpoint program is configured to implement the steps of the OTA-based production line software breakpoint method according to any one of claims 1 to 7.
10. A storage medium, characterized by The storage medium stores an OTA-based production line software breakpoint program, and the OTA-based production line software breakpoint program implements the steps of the OTA-based production line software breakpoint method according to any one of claims 1 to 7 when executed by a processor.