A software version verification method, system, and electronic device based on EOL (End of Hour)
By using an EOL-based software version verification method, virtual sub-orders are used for pre-verification of sub-assembly and verification of the finished vehicle. This solves the problem of incorrect or missed software updates in controllers supplied by multiple vendors, improves production efficiency and vehicle quality, and achieves supply chain flexibility and cost optimization.
Patent Information
- Application Number
- CN202611232514.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-14
- Publication Date
- 2026-11-17
AI Technical Summary
In the scenario of platform-integrated controllers with mixed hardware supply from multiple suppliers, the existing vehicle end-of-line (EOL) testing process cannot effectively avoid software errors, missed checks, and EOL station overload issues, resulting in low production efficiency and increased vehicle quality risks.
By using an EOL-based software version verification method, the controller production files are obtained through virtual sub-orders for pre-verification during sub-assembly, and secondary verification is performed at the vehicle off-line workstation, forming a closed-loop quality control system to ensure software version consistency.
This enabled mixed-line production of integrated controllers from different suppliers, reducing the risk of software errors in the vehicle, improving production efficiency and vehicle delivery quality, and ensuring supply chain flexibility and purchasing power.
Smart Images

Figure CN123114497A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of intelligent automotive manufacturing technology, specifically to a software version verification method, system, and electronic device based on EOL (End of Hour). Background Technology
[0002] The all-in-one integrated controller for new energy commercial vehicles integrates the core functions of the vehicle's three electric systems, such as electric drive control and charging and power distribution management, and is a key component of the vehicle's electronic control system. In the traditional manufacturing supply chain system, the all-in-one integrated controller adopts a "one factory, one number" exclusive matching model. Different component suppliers such as Huichuan, CRRC, and Invt each have their own independent part numbers. The controller's hardware mechanical structure, electrical interface, underlying software driver code, CAN bus communication protocol, and program flashing encryption algorithm are deeply bound. The hardware and software of controllers from different manufacturers correspond one-to-one and cannot be used interchangeably.
[0003] This traditional supporting model suffers from multiple supply chain and manufacturing defects: First, vehicle manufacturers have limited procurement channels for parts, lack competitive options with suppliers, have weak bargaining power, and consequently, high parts procurement costs. Second, R&D teams must develop software adaptations, bench tests, and vehicle verification for each supplier's differentiated hardware, requiring simultaneous maintenance of multiple software and hardware adaptation solutions, significantly increasing R&D manpower, testing equipment, and testing cycle costs. Third, the controller components from different suppliers are not interchangeable, resulting in extremely poor supply chain resilience. Insufficient capacity or delivery delays from a single supplier can directly cause the vehicle assembly line to shut down, compromising production stability.
[0004] The platformization and unification of controller hardware have given rise to new process contradictions: To reduce component procurement costs, broaden supplier competition channels, and enhance the resilience of the supply chain, the vehicle R&D and procurement system has implemented a platform-based upgrade strategy for multi-integrated controllers. This strategy unifies the mechanical dimensions, electrical interfaces, and power hardware parameters of controllers from all qualified suppliers, enabling seamless cross-line supply and cross-assembly of integrated controller hardware from different manufacturers, with complete hardware interoperability.
[0005] While standardized hardware platform solutions address the supply chain shortcomings of traditional supporting models, they also create a core technological contradiction at the manufacturing process level: a conflict between "uniform hardware specifications" and "differentiated underlying software systems." Even if the external hardware structure and electrical interfaces of the controller are standardized, there are significant differences in the underlying driver architecture, CAN bus communication protocol, program flashing encryption algorithm, and control logic of each functional module developed by different suppliers. If the vehicle assembly line uses a unified software flashing program to flash mixed-supplier controllers in batches without distinguishing the underlying software adaptation requirements of different suppliers, software errors, missed program flashing, and communication protocol incompatibility will directly occur. The controller will malfunction after power-on, which can easily lead to major safety hazards such as loss of control of vehicle power output, short circuits in charging and distribution, and fires.
[0006] The existing EOL (End-of-Life) testing process for complete vehicles has significant bottlenecks: The vehicle EOL (End-of-Life) testing station is responsible for flashing the programs, configuring parameters, and verifying the overall functionality of all electronic control controllers in the vehicle. It is the core station for quality control of the electronic control system before the vehicle leaves the production line. With the continuous improvement of the integration level of multi-in-one integrated controllers for new energy commercial vehicles, the number of built-in functional modules such as MCU main controller, DC-DC converter, and OPCU on-board charger is constantly expanding, and the size of the controller software package and the total amount of flashing data packages are increasing exponentially.
[0007] The existing manufacturing process centralizes the entire software flashing process for the all-in-one integrated controller to the vehicle's End-of-Life (EOL) station. After the vehicle is put into production, the flashing of all controllers is performed simultaneously. This increases the cycle time of the EOL station per vehicle from 4.5 minutes to 7.5 minutes, making the EOL station a core bottleneck in the vehicle assembly line. This significantly limits the daily production capacity of the entire vehicle, reduces production line efficiency, and simultaneously increases the overall manufacturing costs of equipment, labor, and space. Furthermore, the existing EOL station can only perform a single software flashing and verification after vehicle assembly. Defects in the controller's incoming software and mismatches in the flashing program can only be identified after vehicle assembly. This results in a large workload for disassembling and reworking faulty controllers, high repair costs, and significant difficulty in tracing faults throughout the entire process.
[0008] Currently, the industry lacks standardized process solutions that can adapt to multi-supplier hardware mixed supply platform integrated controllers, can divert EOL station writing load, and achieve closed-loop control of software matching throughout the entire process. It is impossible to simultaneously meet the multiple production needs of supply chain cost reduction, production line cycle optimization, and vehicle electronic control quality. New software filling and offline verification methods are urgently needed to solve the above technical deficiencies. Summary of the Invention
[0009] To overcome the above-mentioned deficiencies, this invention proposes a software version verification method, system, and electronic device based on EOL, which solves the problems of incorrect or missed software updates and EOL workstation cycle overload in scenarios with unified hardware and mixed supply from multiple vendors.
[0010] To achieve the above-mentioned objectives, the present invention adopts the following technical solution: In a first aspect, the present invention provides a software version verification method based on EOL, comprising: Based on the supplier code of the integrated controller, retrieve the pre-configured virtual sub-orders from the preset mapping relationship; The controller production file is obtained using the virtual sub-order, the integrated controller is flashed with software through the filling terminal, and the pre-verification of dispensing is completed based on the standard software information in the virtual sub-order. After the pre-assembly verification is qualified, the integrated controller is assembled into the vehicle, and the standard order of the vehicle bound to the vehicle is obtained at the vehicle off-line station according to the vehicle VIN code; Based on the preset software standard information in the standard vehicle order, the software of the integrated controller is verified for offline testing.
[0011] Optionally, obtaining the pre-configured virtual sub-order from the preset mapping relationship based on the supplier code of the integrated controller includes: Read the vendor code stored in the integrated controller and upload it to the EOL system; Based on the supplier code mapping relationship, match the virtual sub-order that uniquely corresponds to the supplier code.
[0012] Optionally, the step of obtaining the controller production file using the virtual sub-order, performing software flashing on the integrated controller, and completing pre-verification of the repackaging based on the standard software information in the virtual sub-order includes: Based on the virtual sub-order, the upstream data dictionary is retrieved to obtain the controller production file bound to the virtual sub-order, and the controller production file is sent to the local cache of the filling terminal to instruct the filling terminal to load the controller production file and perform software flashing on the integrated controller; Receive the software data inside the integrated controller after the filling terminal has been written; The software data is compared with the standard software information in the virtual sub-order to complete the pre-verification of the packaging.
[0013] Optionally, comparing the software data with the standard software information within the virtual sub-order to complete the pre-verification of the repackaging process includes: The received software version number and module configuration parameters are compared field by field with the standard software information in the virtual sub-order. If the comparison is completely consistent, the pre-verification of dispensing is deemed qualified; if there is a difference in the comparison, the filling terminal is instructed to trigger a local alarm and perform a rewrite operation.
[0014] Optionally, the step of obtaining the standard vehicle order bound to the vehicle based on the vehicle's VIN code at the vehicle off-line workstation; and performing off-line verification of the integrated controller's software based on the preset software standard information in the standard vehicle order, includes: After the integrated controller is assembled into the vehicle and transferred to the EOL (End of Production) workstation, the software data inside the integrated controller is read through the EOL device, and the software data uploaded by the EOL device is received. Based on the current vehicle's VIN code, retrieve the standard order for the complete vehicle that is linked to that VIN code; The received software data is compared with the preset software standard information in the standard vehicle order for consistency, and the offline processing is performed based on the comparison result.
[0015] Optionally, the step of performing offline processing based on the comparison results includes: When the software data matches the preset software standard information, the system outputs a "passed" flag and releases the vehicle. When a discrepancy is found, a fault alarm is triggered, and the EOL device automatically initiates a secondary write process.
[0016] Optionally, after automatically initiating the secondary write process through the EOL device, the method further includes: The software data of the integrated controller is reread through the EOL device, and the uploaded reread software data is received. The reread software data is compared again with the preset software standard information in the standard vehicle order; If the comparison fails again, the vehicle's off-line clearance will be locked, and a manual re-inspection work order will be generated.
[0017] Optionally, the controller production files include: MCU main control software package, DC-DC converter software package, and OPCU on-board charger software package.
[0018] Secondly, the present invention provides a software version verification system based on EOL, comprising: The mapping relationship acquisition module is used to obtain pre-configured virtual sub-orders from the preset mapping relationship based on the supplier code of the integrated controller; The pre-verification module is used to obtain the controller production file using the virtual sub-order, perform software flashing on the integrated controller through the filling terminal, and complete the pre-verification of dispensing based on the standard software information in the virtual sub-order. The order acquisition module is used to assemble the integrated controller into the vehicle after the pre-verification of the sub-assembly is qualified, and to obtain the standard order of the vehicle bound to the vehicle based on the vehicle VIN code at the vehicle off-line station. The offline verification module is used to perform offline verification on the software of the integrated controller based on the preset software standard information in the standard vehicle order.
[0019] Thirdly, the present invention provides an electronic device, the electronic device comprising: At least one processor; and a memory communicatively connected to said at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor to enable the at least one processor to perform the method described in any one of the first aspects.
[0020] Compared with the prior art, the present invention has the following beneficial effects: This invention provides a software version verification method, system, and electronic device based on EOL (End of Hour). By reading the supplier code permanently stored in the underlying layer of the integrated controller, it obtains pre-configured virtual sub-orders from a preset mapping relationship. Using these virtual sub-orders, it retrieves the corresponding supplier's controller production files for software flashing, achieving a process path of "hardware unification and software decoupling." This mechanism allows integrated controllers from different suppliers to be produced on the same production line, with dedicated software packages matched on demand. It completely breaks the limitations of the traditional "one factory, one number" dedicated model, enhances the purchasing party's bargaining power and supply chain flexibility, and provides reliable technical support for the implementation of multi-supplier platform strategies.
[0021] This invention moves the time-consuming full software flashing process to the sub-assembly area. The EOL (End-of-Life) workstation is only responsible for verifying the consistency of software data based on the standard vehicle order, and no longer undertakes the full flashing task. This layered architecture of "sub-assembly pre-filling + EOL collaborative verification" effectively avoids the problem of extended EOL cycle time caused by the increased functions of the integrated controller, ensuring that the EOL workstation cycle time remains at the original level and significantly improving the efficiency of vehicle production.
[0022] This invention performs pre-verification of the controller's software version immediately after the software is flashed in the sub-assembly area, based on the standard software information in the virtual sub-order, to ensure the correct software version before assembly. At the vehicle off-line station, the standard vehicle order is retrieved again based on the vehicle's VIN code, and off-line verification is performed based on the preset standard software information in the order. This two-level verification forms a closed-loop quality control system, completely eliminating quality risks caused by supplier software errors, flashing omissions, etc., thus ensuring the quality of the delivered vehicle. Attached Figure Description
[0023] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the accompanying drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. In all the drawings, similar elements or parts are generally identified by similar reference numerals. In the drawings, the elements or parts are not necessarily drawn to scale.
[0024] Figure 1 This is a flowchart of a software version verification method based on EOL provided by the present invention; Figure 2 A schematic diagram of the system layered architecture and data interaction flow corresponding to the EOL-based software version verification method provided by this invention; Figure 3 This is a schematic diagram of the pre-filling process in the dispensing area provided by the present invention; Figure 4 This is a flowchart of the EOL station final inspection and verification process provided by the present invention; Figure 5 A block diagram of the software version verification system architecture based on EOL provided by the present invention; Figure 6 This is an internal structural diagram of the electronic device provided by the present invention. Detailed Implementation
[0025] The embodiments of the technical solution of the present invention will now be described in detail with reference to the accompanying drawings. These embodiments are only used to more clearly illustrate the technical solution of the present invention and are therefore merely examples, and should not be construed as limiting the scope of protection of the present invention.
[0026] It should be noted that, unless otherwise stated, the technical or scientific terms used in this application should have the ordinary meaning as understood by one of ordinary skill in the art to which this invention pertains.
[0027] This invention provides a software version verification method, system, and electronic device based on EOL. The embodiments of this invention will be described below with reference to the accompanying drawings.
[0028] Example 1: As Figure 1 As shown, Embodiment 1 of the present invention provides a software version verification method based on EOL (End of Online Count). The overall process includes preliminary system configuration and setup, pre-filling in the packaging area, and EOL offline verification. Specifically, it includes the following steps: S101 retrieves the pre-configured virtual sub-order from the preset mapping relationship based on the supplier code of the integrated controller; S102 uses the virtual sub-order to obtain the controller production file, performs software flashing on the integrated controller through the filling terminal, and completes the pre-verification of dispensing based on the standard software information in the virtual sub-order; After the pre-assembly verification is qualified, S103 will assemble the integrated controller into the vehicle and obtain the standard order of the vehicle bound to the vehicle based on the vehicle VIN code at the vehicle off-line station. S104 performs offline verification on the software of the integrated controller based on the preset software standard information in the standard vehicle order.
[0029] In one embodiment, prior to performing the above steps, system configuration and setup need to be implemented, specifically including: The upstream system deploys a comprehensive data dictionary, recording the complete software production files for the all-in-one integrated controllers (MCU, DC-DC converter, and OPC) from three suppliers: Supplier A (CRRC), Supplier B (Inovance), and Supplier C (Invt). The controller production files include at least one of the following: MCU main control software package, DC-DC converter software package, and OPC on-board charger software package. A supplier code mapping relationship is configured in the EOL system backend. This mapping relationship pre-binds the supplier code to a virtual sub-order and the controller production file: Supplier A's built-in controller feature code LA901 is bound to Supplier A's virtual sub-order and complete production file; Supplier B's feature code LA902 is bound to Supplier B's virtual sub-order and complete production file; and Supplier C's feature code LA903 is bound to Supplier C's virtual sub-order and complete production file. After the vehicle sales order is issued, the EOL system generates an independent standard vehicle order based on each vehicle's unique VIN code. The order pre-stores the standard software version and module configuration parameters corresponding to the controller for that vehicle model.
[0030] like Figure 2 This invention demonstrates the system layered architecture and data interaction flow corresponding to the entire method. The system layers are divided from top to bottom into the upstream system layer, the EOL system service layer, the sub-assembly operation layer, and the final vehicle assembly EOL verification layer. The upstream system internally deploys a global data dictionary, storing complete production files for all supplier controllers. The data dictionary pushes association relationships to the EOL system / order service through a preset supplier code mapping logic. After receiving the mapping data, the EOL system / order service generates corresponding virtual sub-orders based on the supplier codes and issues the virtual sub-orders and dedicated production files to the downstream sub-assembly area filling equipment. After the sub-assembly area filling equipment completes the controller pre-filling operation, qualified controllers are transferred to the final assembly line. After the complete vehicle arrives at the EOL station, it connects to the EOL station equipment via the OBD interface to complete the final version verification. All data in the entire chain is uniformly scheduled and stored by the EOL system.
[0031] Step S101 above: Obtain the pre-configured virtual sub-order from the preset mapping relationship according to the supplier code of the integrated controller.
[0032] The supplier delivers a standardized hardware all-in-one integrated controller to the chassis assembly station. The operator retrieves a portable filling terminal and connects it to the controller's hardware communication interface via a dedicated wiring harness. The filling terminal and controller are powered on synchronously, establishing a real-time CAN bus communication channel. The filling terminal reads the supplier code stored in the integrated controller's underlying memory, for example, the signature LA902 (Inovance), and uploads this supplier code to the EOL system. The EOL system, based on its internally pre-set supplier code mapping relationship, matches a virtual sub-order uniquely corresponding to that supplier code—that is, Inovance's virtual sub-order.
[0033] Step S102 above: Obtain the controller production file using the virtual sub-order, perform software flashing on the integrated controller through the filling terminal, and complete the pre-verification of dispensing based on the standard software information in the virtual sub-order.
[0034] The EOL system retrieves the upstream global data dictionary based on the matched virtual sub-order to obtain the controller production file (Inovance MCU, DC-DC, OPCU software package) bound to the virtual sub-order. This controller production file is then sent to the local cache of the filling terminal, instructing the terminal to load the file and sequentially write software and configure parameters for the integrated controller according to its functional modules. Subsequently, the filling terminal loads the locally cached Inovance-specific production file and writes programs to the integrated controller module by module via the CAN bus, sequentially completing the software flashing and parameter configuration of the main control unit, DC-DC converter unit, and on-board charger unit.
[0035] After the entire flashing process is complete, the filling terminal rereads the complete software version number and module configuration parameters inside the integrated controller and sends this data back to the EOL system. The EOL system compares the received software version number and module configuration parameters with the standard software information in the virtual sub-order field by field. If the comparison is completely consistent, the pre-verification of the dispensing is deemed qualified, the integrated controller is marked as qualified, and a qualified transfer label is printed. If there is a discrepancy, the filling terminal is instructed to trigger an audible and visual alarm. The operator clears the original program of the controller and performs a re-flashing operation. If the error persists after two repetitions, the controller is isolated and returned to the supplier's incoming material inspection station.
[0036] like Figure 3The operator connects the integrated controller to the portable filling terminal and powers it on. The filling terminal reads the supplier code built into the controller and uploads it to the EOL system. The EOL system matches the unique corresponding virtual sub-order, retrieves the corresponding supplier's production file from the upstream data dictionary, and sends it to the local cache of the filling terminal. The filling terminal loads the cache file and performs a full-module software flashing of the integrated controller. After the flashing is completed, the filling terminal reads the controller software version and configuration parameters and sends them back to the EOL system. The system compares the data field by field with the standard information of the virtual sub-order. If the comparison is successful, the controller is transferred to final assembly. If the comparison is abnormal, the terminal alarms locally and re-executes the flashing operation.
[0037] Step S103 above: After the pre-verification of the sub-assembly is qualified, the integrated controller is assembled into the vehicle, and the standard order of the vehicle bound to the vehicle is obtained at the vehicle off-line station according to the vehicle VIN code.
[0038] The multi-in-one integrated controller, with a certified label, is transferred to the chassis assembly station, securely installed to its pre-set mounting point on the frame, and enters the final vehicle assembly line after wiring harness connection. After the vehicle completes all assembly processes for the cab, powertrain, and chassis, it is transferred to the EOL (End-of-Life) station. After the integrated controller is assembled into the vehicle and transferred to the EOL station, the EOL equipment reads the software data inside the integrated controller and receives software data uploaded by the EOL equipment. Specifically, the EOL testing equipment plug is inserted into the vehicle's OBD diagnostic interface, activating the vehicle's CAN bus electronic control communication network. The EOL equipment sends data reading messages to the integrated controller, extracts the software version numbers and hardware configuration parameters of each module stored internally, and uploads all read data to the EOL system server. The EOL system retrieves the standard vehicle order bound to the VIN code read by the current vehicle's OBD system.
[0039] Step S104 above: Based on the preset software standard information in the standard vehicle order, perform offline verification on the software of the integrated controller.
[0040] The EOL system will compare the received software data with the preset software standard information in the standard vehicle order and perform offline processing based on the comparison results.
[0041] The process of taking the system offline based on the comparison results includes two scenarios: When all software versions and configuration parameters are consistent, the vehicle is marked off the production line and released. The vehicle is then transferred to the finished vehicle storage area to await delivery. When any module software version or configuration parameter mismatch is found, a fault alarm is triggered, and a secondary write process is automatically initiated via the EOL device. The system automatically retrieves the virtual sub-order software file from the controller supplier and initiates a secondary software write to the vehicle's all-in-one integrated controller via the OBD interface.
[0042] After the secondary write process is completed, further verification steps are included: rereading the integrated controller's software data through the EOL device and receiving the uploaded reread software data; comparing the reread software data with the preset software standard information in the vehicle's standard order; if they match again, the vehicle is deemed qualified and released; if they do not match again, the vehicle's off-line access is locked, and a manual re-inspection work order containing the vehicle's VIN, fault code, sub-assembly station number, and EOL station number is generated and pushed to the maintenance team. Technicians disassemble the controller to check the incoming hardware and the root cause of the fault in the sub-assembly and write process. Only after completing the repair and re-inspection can the vehicle be released.
[0043] like Figure 4 The demonstration showcases the complete verification and judgment logic of the EOL (End of Service) station after a vehicle rolls off the production line: Upon arrival at the EOL station, the equipment connects to the vehicle's OBD interface to establish CAN bus communication; the EOL equipment reads the internal software version number and configuration parameters of the multi-in-one integrated controller and uploads them to the EOL system; the EOL system retrieves the bound standard vehicle order based on the vehicle's VIN and compares the actual read software data with the standard software information in the order item by item; if the comparison matches, a PASS output is generated for vehicle rollout; if the comparison does not match, a FAIL alarm is triggered, and the system automatically initiates a secondary write process. If the secondary write verification still fails, the rollout permission is locked, and a manual re-inspection work order is generated.
[0044] Example 2: Multi-vehicle platform compatibility expansion implementation method When a company adds two new vehicle models, namely new energy light trucks and new energy heavy trucks, or adds a fourth controller supplier, there is no need to modify the hardware structure of the filling terminal and EOL off-line equipment. Only the production files of the new supplier's MCU, DCDC, and OPCU software need to be entered into the upstream data dictionary, and the feature code and virtual sub-order and production file binding relationship need to be added to the supplier code mapping table of the EOL system. When the vehicle order is issued, the EOL system automatically matches the corresponding vehicle model and the corresponding supplier virtual sub-order according to the vehicle model VIN. The original process execution flow of the filling area and EOL station remains completely unchanged, realizing rapid adaptation and expansion.
[0045] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.
[0046] Example 3: Based on the same technical concept, Example 3 of this invention also provides a software version verification system based on EOL, such as... Figure 2 As shown, it includes: a mapping relationship acquisition module 210, a pre-verification module 220, an order acquisition module 230, and an offline verification module 240, wherein: The mapping relationship acquisition module 210 is used to obtain pre-configured virtual sub-orders from the preset mapping relationship based on the supplier code of the integrated controller; The pre-verification module 220 is used to obtain the controller production file using the virtual sub-order, perform software flashing on the integrated controller through the filling terminal, and complete the pre-verification of the dispensing based on the standard software information in the virtual sub-order. The order acquisition module 230 is used to assemble the integrated controller into the vehicle after the pre-verification of the sub-assembly is qualified, and to obtain the standard order of the vehicle bound to the vehicle based on the vehicle VIN code at the vehicle off-line station. The offline verification module 240 is used to perform offline verification on the software of the integrated controller based on the preset software standard information in the standard vehicle order.
[0047] Example 4: In one embodiment, Example 4 of the present invention also provides an electronic device; the electronic device may be a terminal, and its internal structure diagram may be as follows. Figure 3 As shown. The electronic device includes a processor, memory, communication interface, display screen, and input device connected via a system bus. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements the EOL-based software version verification method described in any one of steps S101 to S104. The display screen can be a liquid crystal display (LCD) or an electronic ink display. The input device can be a touch layer covering the display screen, buttons, a trackball, or a touchpad mounted on the device's casing, or an external keyboard, touchpad, or mouse.
[0048] Those skilled in the art will understand that Figure 3 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.
[0049] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0050] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.
[0051] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.
[0052] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.
[0053] The above are merely embodiments of the present invention and are not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention are included within the scope of the claims of the present invention pending approval.
Claims
1. An EOL-based software version checking method, characterized by, include: Based on the supplier code of the integrated controller, retrieve the pre-configured virtual sub-orders from the preset mapping relationship; The controller production file is obtained using the virtual sub-order, the integrated controller is flashed with software through the filling terminal, and the pre-verification of dispensing is completed based on the standard software information in the virtual sub-order. After the pre-verification of the sub-assembly is qualified, the integrated controller is assembled into the vehicle, and the standard order of the vehicle bound to the vehicle is obtained at the vehicle off-line station according to the vehicle VIN code; Based on the preset software standard information in the standard vehicle order, the software of the integrated controller is subjected to offline verification.
2. The method of claim 1, wherein, The step of retrieving the pre-configured virtual sub-order from the preset mapping relationship based on the supplier code of the integrated controller includes: Read the vendor code stored in the integrated controller and upload it to the EOL system; Based on the supplier code mapping relationship, match the virtual sub-order that uniquely corresponds to the supplier code.
3. The method of claim 2, wherein, The process of obtaining controller production files using the virtual sub-order, flashing the integrated controller with software, and completing pre-verification of the repackaging based on the standard software information in the virtual sub-order includes: Based on the virtual sub-order, the upstream data dictionary is retrieved to obtain the controller production file bound to the virtual sub-order, and the controller production file is sent to the local cache of the filling terminal to instruct the filling terminal to load the controller production file and perform software flashing on the integrated controller; Receive the software data inside the integrated controller after the filling terminal has been written; The software data is compared with the standard software information in the virtual sub-order to complete the pre-verification of the packaging.
4. The method according to claim 3, characterized in that, The step of comparing the software data with the standard software information in the virtual sub-order to complete the pre-verification of the repackaging process includes: The received software version number and module configuration parameters are compared field by field with the standard software information in the virtual sub-order. If the comparison is completely consistent, the pre-verification of dispensing is deemed qualified; if there is a difference in the comparison, the filling terminal is instructed to trigger a local alarm and perform a rewrite operation.
5. The method according to claim 1, characterized in that, The standard order for the complete vehicle bound to the complete vehicle is obtained at the vehicle off-line workstation based on the vehicle's VIN code; Based on the preset software standard information in the standard vehicle order, the software of the integrated controller is subjected to offline verification, including: After the integrated controller is assembled into the vehicle and transferred to the EOL (End of Production) workstation, the software data inside the integrated controller is read through the EOL device, and the software data uploaded by the EOL device is received. Based on the current vehicle's VIN code, retrieve the standard order for the complete vehicle that is linked to that VIN code; The received software data is compared with the preset software standard information in the standard vehicle order for consistency, and the offline processing is performed based on the comparison result.
6. The method according to claim 5, characterized in that, The step of taking the device offline based on the comparison results includes: When the software data matches the preset software standard information, the system outputs a "passed" flag and releases the vehicle. When a discrepancy is found, a fault alarm is triggered, and the EOL device automatically initiates a secondary write process.
7. The method according to claim 6, characterized in that, After the automatic initiation of the secondary write process via the EOL device, the process further includes: The software data of the integrated controller is reread through the EOL device, and the uploaded reread software data is received. The reread software data is compared again with the preset software standard information in the standard vehicle order; If the comparison fails again, the vehicle's off-line clearance will be locked, and a manual re-inspection work order will be generated.
8. The method according to claim 3, characterized in that, The controller production files include: MCU main control software package, DC-DC converter software package, and OPCU on-board charger software package.
9. A software version verification system based on EOL, characterized in that, include: The mapping relationship acquisition module is used to obtain pre-configured virtual sub-orders from the preset mapping relationship based on the supplier code of the integrated controller; The pre-verification module is used to obtain the controller production file using the virtual sub-order, perform software flashing on the integrated controller through the filling terminal, and complete the pre-verification of dispensing based on the standard software information in the virtual sub-order. The order acquisition module is used to assemble the integrated controller into the vehicle after the pre-verification of the sub-assembly is qualified, and to obtain the standard order of the vehicle bound to the vehicle based on the vehicle VIN code at the vehicle off-line station. The offline verification module is used to perform offline verification on the software of the integrated controller based on the preset software standard information in the standard vehicle order.
10. An electronic device, characterized in that, The electronic device includes: At least one processor; and a memory communicatively connected to said at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-8.
