Commercial vehicle all-in-one controller software and hardware separation automatic flashing method, device, equipment and storage medium
By using an automatic flashing method that separates the hardware and software of the all-in-one controller for commercial vehicles, the problem of redundant parts caused by hardware and software binding is solved, achieving efficient parts management and full lifecycle traceability of production data, thereby improving supply chain response efficiency and mass production consistency.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- DONGFENG LIUZHOU MOTOR
- Filing Date
- 2026-03-04
- Publication Date
- 2026-06-30
AI Technical Summary
The all-in-one controller for commercial vehicles results in redundant parts due to the binding of software and hardware, leading to high warehousing and management costs, long production and inventory cycles, and difficulties in after-sales parts reserves. Furthermore, the software supply method is difficult to adapt to the needs of mixed production lines for multiple vehicle models.
An automatic flashing method with separate hardware and software for commercial vehicle all-in-one controllers is adopted. By obtaining the vehicle quota list, querying the software version number comparison library, obtaining the software package file, and performing the flashing operation using an automatic flashing device, a hardware and software matching information table is established to achieve data traceability.
It eliminated redundant parts, improved supply chain response efficiency, reduced warehouse management complexity, ensured mass production consistency, and enabled full lifecycle traceability of production data.
Smart Images
Figure CN122308893A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of automotive manufacturing technology, and in particular to an automatic flashing method, apparatus, equipment, and storage medium for a multi-functional controller for commercial vehicles with separate hardware and software. Background Technology
[0002] With the accelerated transformation of commercial vehicles towards new energy, building a resilient and controllable supply chain system has become a core requirement for industry development. Optimizing resource allocation around core assemblies such as motors, steering, braking, and power distribution to achieve a production model that is cost-controllable, technologically advanced, and agile in delivery has become a key path to enhance the competitiveness of vehicle manufacturing.
[0003] Currently, commercial vehicle all-in-one controllers generally adopt a hardware and software-bound management and control model. Due to differences in the built-in software versions, the same hardware needs to correspond to multiple part numbers, resulting in an exponential increase in the variety of parts as the software is combined. This leads to high warehousing and management costs, long production and inventory cycles, and difficulties in after-sales parts reserves. Furthermore, the supply method of software being delivered along with hardware is difficult to adapt to the rapid switching needs in multi-model mixed-line production scenarios, which seriously restricts production efficiency and supply chain response speed.
[0004] The above content is only used to help understand the technical solution of the present invention and does not represent an admission that the above content is prior art. Summary of the Invention
[0005] The main objective of this invention is to provide an automatic flashing method, apparatus, device, and storage medium for the software and hardware separation of a commercial vehicle all-in-one controller. The aim is to solve the technical problem of how to eliminate the redundancy of parts caused by the software and hardware binding of the commercial vehicle all-in-one controller and realize the automatic flashing and data traceability control of the software and hardware decoupling at the production line level.
[0006] To achieve the above objectives, the present invention provides an automatic flashing method for a commercial vehicle all-in-one controller with separate hardware and software, the method comprising the following steps:
[0007] Obtain the loading quota list, wherein the loading quota list includes hardware drawing numbers and software drawing numbers; The software version number is obtained by querying a preset software version number and software version number lookup database based on the software version number. The corresponding software package file is retrieved from the preset software package storage path according to the software version number; The software package file is sent to the automatic flashing device so that the automatic flashing device performs a flashing operation on the all-in-one controller according to the software package file.
[0008] In one embodiment, the step of querying a preset software drawing number and software version number lookup database based on the software drawing number to obtain the software version number corresponding to the software drawing number includes: The module identification information is obtained by parsing the software drawing number; Based on the module identification information, a matching candidate record is retrieved from the software drawing number and software version number lookup database; Filter the candidate records to select target records that are exactly the same as the software drawing number; Extract the version number field stored in the target record as the software version number corresponding to the software drawing number.
[0009] In one embodiment, the step of retrieving the corresponding software package file from a preset software package storage path based on the software version number includes: Generate a file retrieval request based on the software version number; Send the file retrieval request to the file management system; Receive the software package file corresponding to the software version number returned by the file management system.
[0010] In one embodiment, the step of obtaining the loading quota list includes: Send a quota query request to the manufacturing execution system, the quota query request carrying the vehicle's unique identification code; Receive the initial loading quota returned by the manufacturing execution system; The initial loading quota is analyzed to obtain the hardware and software drawing numbers corresponding to the all-in-one controller; The hardware drawing number and the software drawing number are combined to generate a loading quota list.
[0011] In one embodiment, the method further includes, after: Create a blank data table structure; Write the hardware drawing number into the hardware identifier field of the blank data table structure; Write the software drawing number and the software version number into the software identifier field of the blank data table structure; The completed blank data table structure is saved as a hardware / software matching information table.
[0012] In one embodiment, the step of saving the completed blank data table structure as the hardware / software matching information table includes: Convert the file format of the blank data table structure into a preset data format; Save the converted blank data table structure as a local temporary file; Upload the local temporary file to the data platform; Receive the storage completion confirmation information returned by the data platform; The storage completion confirmation information confirms that the hardware and software matching information table has been saved.
[0013] In one embodiment, the step of sending the software package file to an automatic flashing device, so that the automatic flashing device performs a flashing operation on the all-in-one controller according to the software package file, includes: Establish a communication connection with the automatic writing device; Write the storage path information of the software package file into the flash boot command; Send the flashing start command to the automatic flashing device; Receive confirmation information of completion of the writing process returned by the automatic writing device.
[0014] Furthermore, to achieve the above objectives, the present invention also proposes an automatic flashing device for a commercial vehicle all-in-one controller with separate hardware and software, the device comprising: The quota acquisition module is used to acquire the loading quota list, wherein the loading quota list includes hardware drawing numbers and software drawing numbers; The version query module is used to query a preset software drawing number and software version number lookup database based on the software drawing number to obtain the software version number corresponding to the software drawing number; The file acquisition module is used to acquire the corresponding software package file from the preset software package storage path according to the software version number; The flashing control module is used to send the software package file to the automatic flashing device, so that the automatic flashing device performs a flashing operation on the all-in-one controller according to the software package file.
[0015] Furthermore, to achieve the above objectives, the present invention also proposes an automatic flashing device for the hardware and software separation of a commercial vehicle all-in-one controller. The device includes: a memory, a processor, and an automatic flashing program for the hardware and software separation of a commercial vehicle all-in-one controller stored in the memory and executable on the processor. The automatic flashing program for the hardware and software separation of a commercial vehicle all-in-one controller is configured to implement the steps of the automatic flashing method for the hardware and software separation of a commercial vehicle all-in-one controller as described above.
[0016] Furthermore, to achieve the above objectives, the present invention also proposes a storage medium storing an automatic flashing program for the hardware and software separation of a commercial vehicle all-in-one controller. When the automatic flashing program for the hardware and software separation of a commercial vehicle all-in-one controller is executed by a processor, it implements the steps of the automatic flashing method for the hardware and software separation of a commercial vehicle all-in-one controller as described above.
[0017] In addition, to achieve the above objectives, this application also provides a computer program product, which includes a computer program that, when executed by a processor, implements the steps of the automatic flashing method for separating the hardware and software of a commercial vehicle all-in-one controller as described above.
[0018] One or more technical solutions proposed in this application have at least the following technical effects: It achieves decoupled control of hardware and software in the all-in-one controller, eliminates redundancy of parts by mapping software drawing number and software version number, realizes accurate matching of software version and unattended writing by relying on the production line automatic writing system, and establishes a data traceability system covering the entire production life cycle, thereby improving supply chain response efficiency, reducing warehouse management complexity and ensuring mass production consistency. Attached Figure Description
[0019] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.
[0020] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0021] Figure 1 This is a flowchart illustrating an embodiment of the automatic flashing method for separating the hardware and software of a multi-in-one controller for commercial vehicles in this application. Figure 2 This is a flowchart illustrating Embodiment 2 of the automatic flashing method for the software and hardware separation of the commercial vehicle all-in-one controller in this application. Figure 3 This is a schematic diagram of the module structure of the automatic flashing device for the software and hardware separation of the commercial vehicle all-in-one controller according to an embodiment of this application; Figure 4 This is a schematic diagram of the device structure of the hardware operating environment involved in the automatic flashing method for the software and hardware separation of the commercial vehicle all-in-one controller in the embodiments of this application.
[0022] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation
[0023] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.
[0024] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.
[0025] It should be noted that the executing entity in this embodiment can be a computing service device with data processing, network communication, and program execution functions, such as a tablet computer, personal computer, or mobile phone, or an electronic device capable of performing the above functions, such as an automatic flashing device with separate hardware and software for a commercial vehicle all-in-one controller. The following description uses an automatic flashing device with separate hardware and software for a commercial vehicle all-in-one controller as an example to illustrate this embodiment and the subsequent embodiments.
[0026] Based on this, this application provides an automatic flashing method for a commercial vehicle all-in-one controller with separate hardware and software, referring to... Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the automatic flashing method for the hardware and software separation of the commercial vehicle all-in-one controller of this application.
[0027] In this embodiment, the automatic flashing method for the hardware and software separation of the commercial vehicle all-in-one controller includes steps S10 to S40: Step S10: Obtain the loading quota list, which includes hardware drawing numbers and software drawing numbers; It should be noted that the vehicle assembly quota list is a detailed list of component configuration information used to guide the vehicle assembly process. In this embodiment, the list specifically specifies the hardware specifications and software configuration required for the all-in-one controller, serving as a bridge between engineering design and manufacturing. It should also be noted that the hardware drawing number is a unique identifier for the physical hardware structure of the all-in-one controller. In this embodiment, the hardware drawing number represents the physical entity identity of the controller and is managed separately from the software drawing number to achieve hardware standardization. Furthermore, the software drawing number is a number used to identify the software configuration of each functional module within the all-in-one controller. In this embodiment, the software drawing number corresponds to the software combination of the motor control unit, DC-DC conversion unit, high-voltage power distribution unit, electric air conditioning control unit, or electric power steering unit.
[0028] Understandably, step S10 retrieves the loading quota list, which includes hardware and software drawing number configuration information, from the manufacturing execution layer's production information management platform. This list serves as the data foundation for subsequent software version matching and flashing operations. This step enables access to the production data source, ensuring that subsequent operations are based on accurate engineering configurations.
[0029] In one feasible implementation, step S10 includes steps A11 to A14: Step A11: Send a quota query request to the manufacturing execution system, the quota query request carrying the vehicle's unique identification code; It should be noted that the Manufacturing Execution Layer (MAIL) production information management platform refers to a production information management architecture oriented towards the workshop execution layer of manufacturing enterprises. In this embodiment, this architecture is responsible for storing and managing all quota data required for vehicle assembly and providing real-time data support to the production control end. It should also be noted that the unique vehicle identifier (UDI) is a 17-character code used to uniquely identify a vehicle. In this embodiment, this UDI serves as a query index for accurately locating the assembly configuration information of a specific vehicle, such as the unique identification code for vehicle 241261_16_01. Furthermore, a quota query request is an instruction message used to request specific vehicle assembly data from the MAIL production information management platform. In this embodiment, the request carries the UDI as a search condition to obtain the corresponding vehicle configuration information.
[0030] Understandably, step A11 initiates a data query request carrying the vehicle's unique identification code to the manufacturing execution layer's production information management platform in order to obtain the corresponding vehicle's assembly configuration data. This step establishes a data interaction channel with the manufacturing execution layer's production information management platform and initiates the data acquisition process.
[0031] Step A12: Receive the initial loading quota returned by the manufacturing execution system; It should be noted that the initial assembly quota refers to the set of original assembly data returned from the manufacturing execution layer production information management platform. In this embodiment, this data contains information on all the components required for vehicle assembly, and it needs to be parsed and extracted to obtain the specific configuration related to the all-in-one controller.
[0032] Understandably, step A12 involves receiving the initial loading quota data packet returned by the manufacturing execution layer's production information management platform, completing the data acquisition operation. This step enables the receipt of raw assembly data, providing input for subsequent data parsing.
[0033] Step A13: Parse the initial loading quota to obtain the hardware and software drawing numbers corresponding to the all-in-one controller; Understandably, the received initial assembly quota is structured and parsed to extract the hardware and software drawing numbers related to the all-in-one controller. This step enables precise extraction from full assembly data to specific controller configuration information.
[0034] Step A14: Combine the hardware drawing number and the software drawing number to generate the loading quota list.
[0035] Understandably, step A14 combines the parsed hardware and software drawing numbers according to a preset format to generate a standardized loading quota list. This step achieves standardized data encapsulation, forming a configuration document that can be directly used in subsequent processes.
[0036] Step S20: Query the preset software drawing number and software version number lookup database according to the software drawing number to obtain the software version number corresponding to the software drawing number; In this embodiment, the reference database records the correspondence between software drawing numbers and specific binary file version numbers for each module of the Huichuan third-generation controller. For example, the software drawing number 2142212A066A0 for the electric power steering unit corresponds to the version number 2_03114760_EPS_V0.01.bin. It should be noted that the software version number is an encoding used to uniquely identify the specific version characteristics of a software package file. In this embodiment, this version number not only identifies the software but also implicitly contains the naming rules of the software package file, used to locate the specific file in the storage path.
[0037] Understandably, step S20 retrieves matching records from a pre-defined lookup database based on the obtained software drawing number and extracts the corresponding software version number. This step achieves the crucial transformation from logical configuration identifier to physical software identity, establishing a mapping relationship between software drawing numbers and executable software packages.
[0038] Step S30: Obtain the corresponding software package file from the preset software package storage path according to the software version number; It should be noted that the software package storage path refers to the server directory address used to store the software package files of each module of the all-in-one controller. In this embodiment, this path is hierarchically stored and managed according to software version numbers to ensure that different versions of software package files can be accurately addressed. It should also be noted that a software package file refers to a binary file containing the executable program code of the all-in-one controller. In this embodiment, the file is named with a version number, such as 2_03114760_EPS_V0.01.bin, and contains the control program for the electric power steering unit.
[0039] Understandably, step S30 retrieves the corresponding software package file from the preset storage path based on the determined software version number, serving as the data carrier for the flashing operation. This step achieves the retrieval from the version identifier to the physical software file, providing a program data source for controller flashing.
[0040] In one feasible implementation, step S30 includes steps A21 to A23: Step A21: Generate a file retrieval request based on the software version number; It should be noted that a file retrieval request refers to a query command used to find a specific software package file in the software package file management terminal. In this embodiment, the request carries the software version number as a search keyword to locate the target file.
[0041] Understandably, step A21 generates a standardized file retrieval request based on the software version number, and this request includes the version identification information of the target file. This step constructs the retrieval instruction, providing query conditions for file location.
[0042] Step A22: Send the file retrieval request to the file management system; It should be noted that the software package file management terminal refers to a storage platform used for centralized storage and management of software package files. In this embodiment, the platform is responsible for maintaining version control, path management, and file distribution of software packages, ensuring the availability and integrity of the software packages required for production.
[0043] Understandably, step A22 sends the generated file retrieval request to the software package file management terminal, initiating the software package file query process. This step establishes data interaction with the software package file management terminal and starts the file retrieval process.
[0044] Step A23: Receive the software package file corresponding to the software version number returned by the file management system.
[0045] As is understandable, step A23 involves receiving the software package file returned by the software package file management terminal, matching the software version number, thus completing the file acquisition operation. This step achieves the reception of the target software file, preparing for subsequent transfer to the flashing tool.
[0046] Step S40: Send the software package file to the automatic flashing device so that the automatic flashing device performs a flashing operation on the all-in-one controller according to the software package file.
[0047] It should be noted that the flashing fixture refers to a specialized tooling device installed on the production line for burning software programs to the all-in-one controller. In this embodiment, the fixture establishes a connection with the all-in-one controller through a communication interface to perform the program writing operation.
[0048] Understandably, step S40 transfers the acquired software package file to the flashing tool, triggering the tool to perform a program flashing operation on the all-in-one controller. This step realizes the physical writing of software from the storage end to the controller hardware, completing the coupling and assembly of software and hardware.
[0049] In one feasible implementation, step S40 includes steps A31 to A34: Step A31: Establish a communication connection with the automatic writing device; Understandably, step A31 establishes a data communication connection with the flashing tool to ensure smooth command and file transfer. This step initializes the communication link, establishing a physical channel for subsequent data transmission.
[0050] Step A32: Write the storage path information of the package file into the flashing startup command; It should be noted that the flashing start command is a control command used to trigger the flashing tool to perform the software burning operation. In this embodiment, the command contains the storage path information of the software package file, guiding the tool to locate and read the target file.
[0051] Understandably, step A32 writes the storage path information of the software package file into the data field of the flashing startup command. This step populates the command parameters, providing file location information for the flashing tool.
[0052] Step A33: Send the flashing start command to the automatic flashing device; Understandably, step A33 sends a flashing start command carrying file path information to the flashing tool, triggering the tool to start the flashing process. This step realizes the issuance of control commands and starts the actual program burning process.
[0053] Step A34: Receive confirmation information that the flashing process is complete from the automatic flashing device.
[0054] It should be noted that the flashing completion confirmation information refers to the status feedback signal returned by the flashing fixture after completing the software flashing. In this embodiment, this information indicates the success or failure status of the flashing operation and is used to confirm the completion of the production process.
[0055] Understandably, step A34 receives the brushing completion confirmation information returned by the brushing fixture after the brushing operation is completed, confirming the result of the process. This step achieves closed-loop confirmation of the operation and identifies the completion status of the brushing process.
[0056] Furthermore, this solution also includes steps A41 to A44: Step A41: Create a blank data table structure; It should be noted that a blank data table structure refers to a database table or file template with predefined field formats but no data. In this embodiment, the structure includes preset columns such as hardware identifier fields and software identifier fields, used to standardize the storage of hardware and software matching information.
[0057] Understandably, step A41 creates a blank data table structure with preset field formats and initializes the data storage container. This step prepares the data carrier and establishes a standardized format for recording assembly information.
[0058] Step A42: Write the hardware drawing number into the hardware identifier field of the blank data table structure; It should be noted that the hardware identification field refers to the column in the blank data table structure used to store hardware drawing number information. In this embodiment, this field is used to record the identity of the physical hardware of the all-in-one controller.
[0059] Understandably, step A42 writes the hardware drawing number data into the hardware identifier field of the blank data table structure. This step records the hardware identification information and establishes traceability data at the hardware level.
[0060] Step A43: Write the software drawing number and software version number into the software identifier field of the blank data table structure; It should be noted that the software identifier field refers to the column in the blank data table structure used to store software drawing number and software version number information. In this embodiment, this field is used to record the software configuration information running inside the controller.
[0061] Understandably, step A43 writes the software drawing number and corresponding software version number into the software identifier field of the blank data table structure. This step records the software configuration information and establishes traceability data at the software level.
[0062] Step A44: Save the completed blank data table structure as a hardware / software matching information table.
[0063] It should be noted that the storage completion confirmation message refers to the response signal returned by the cloud-based traceability data storage terminal after successfully receiving and saving the data. In this embodiment, this message indicates that the data upload was successful and confirms that the traceability data has been securely archived.
[0064] Understandably, receiving the storage completion confirmation message from the cloud-based traceability data storage terminal involves listening for and receiving the confirmation response returned by the cloud-based traceability data storage terminal after successfully storing the file. This step confirms the upload result and verifies the integrity of the data transmission.
[0065] Further, step A44 includes: Convert blank data table structure files to a preset data format; Save the converted blank data table structure as a local temporary file; Upload local temporary files to the data platform; Receive the storage completion confirmation information returned by the data platform; The storage completion confirmation message confirms that the hardware and software matching information table has been saved.
[0066] Understandably, confirming the storage completion information and verifying the hardware / software matching information table has been saved is based on the received confirmation information to determine that the data archiving operation is complete and the saving process ends. This step achieves a closed loop in the process, confirming that the traceability data has been successfully stored.
[0067] By executing the above steps, decoupled management and automatic matching of hardware and software information for the all-in-one controller are achieved, eliminating the redundancy of parts caused by hardware and software binding in the traditional model. By establishing a hardware and software matching information table and uploading it to the cloud traceability data storage terminal, a data traceability system covering the entire production process is constructed, realizing end-to-end digital control from engineering configuration to production execution and data archiving, effectively supporting the requirements of production consistency and after-sales traceability.
[0068] This embodiment provides an automated flashing method for a commercial vehicle all-in-one controller with separated hardware and software. By constructing a bill of materials architecture with separated hardware and software, it achieves decoupled management of hardware generalization and software configuration, eliminating redundancy in parts caused by software version differences. Relying on the automatic mapping mechanism between software drawing numbers and software version numbers, it achieves accurate matching and automatic acquisition of software versions, avoiding errors in manual selection. Through the linkage of automated flashing equipment, it completes the unattended burning of software programs to the controller hardware, ensuring the consistency and accuracy of flashing. By establishing a hardware and software matching information table and implementing full lifecycle data archiving, it constructs a complete traceability chain from engineering configuration to production execution, realizing closed-loop management of production data and after-sales traceability capabilities.
[0069] Based on the first embodiment of this application, in the second embodiment of this application, the content that is the same as or similar to that in the first embodiment described above can be referred to the above description, and will not be repeated hereafter. Based on this, please refer to... Figure 2 Step S20 includes steps S201 to S204: Step S201: Parse the software drawing number to obtain module identification information; It should be noted that module identification information refers to the feature code extracted from the software drawing number, used to identify the category of internal functional modules of the all-in-one controller. In this embodiment, module identification information is used to distinguish different functional modules such as motor control unit, DC-DC conversion unit, high-voltage power distribution unit, electric air conditioning control unit, or electric power steering unit. For example, it can identify the specific software configuration corresponding to which functional module from the software drawing number of the Huichuan third-generation controller.
[0070] Understandably, step S201 performs structured parsing of the software drawing number to extract the module identification information contained therein. This step enables the identification of specific functional module categories from composite drawing numbers, establishing search conditions for accurately retrieving the corresponding software version of that module from the database.
[0071] Step S202: Search for matching candidate records in the software drawing number and software version number lookup database based on the module identification information; It should be noted that candidate records refer to the set of data records that match the module identification information obtained after preliminary searching in the software drawing number and software version number lookup database. In this embodiment, candidate records include multiple software drawing numbers and their corresponding version number information for different configuration variations under the same functional module, serving as the data basis for further precise filtering.
[0072] Understandably, step S202 performs a preliminary search in a pre-defined software drawing number and software version number lookup database based on the parsed module identifier information to obtain a set of candidate records for that module category. This step initially limits the data range, narrowing the search space for subsequent precise matching.
[0073] Step S203: Select the target record from the candidate records that is completely consistent with the software drawing number; It should be noted that a target record refers to a single data record in the candidate record set that perfectly matches the queried software part number after precise filtering. In this embodiment, the target record is a software part number entry that uniquely corresponds to a specific vehicle configuration requirement, such as precisely matching the specific module software part number 2142212A066A0 required by vehicle 241261_16_01.
[0074] Understandably, step S203 performs an exact match filter in the candidate record set to find the target record that is completely consistent with the current software drawing number. This step enables the location of the unique and correct software configuration entry from multiple candidate configurations of the same module, ensuring the accuracy of version matching.
[0075] Step S204: Extract the version number field stored in the target record as the software version number corresponding to the software drawing number.
[0076] It should be noted that the version number field refers to a specific data column in the target record that stores software version number information. In this embodiment, the version number field stores a specific software file version identifier, such as 2_03114760_EPS_V0.01.bin, which is used to retrieve the corresponding software package file from the storage path later.
[0077] Understandably, step S204 reads the data content stored in the version number field from the target record and outputs this data content as the software version number corresponding to the software drawing number. This step realizes the extraction from the database record to the specific software version identifier, completing the mapping conversion from software drawing number to software version number.
[0078] This embodiment provides an automatic flashing method for the hardware and software separation of a commercial vehicle all-in-one controller. By extracting module identification information from the software drawing number through structured parsing, it achieves accurate classification and identification of heterogeneous functional modules within the all-in-one controller, laying the foundation for differentiated software management. Relying on the hierarchical retrieval mechanism of module identification information, it first locates the candidate record set and then performs precise matching, effectively improving the retrieval efficiency in a large-scale comparison database. The precise screening of target records ensures a one-to-one correspondence between the software version and the vehicle configuration requirements, eliminating the risk of errors from manual matching. Finally, the version number field is extracted to complete the mapping conversion, establishing a reliable association channel from logical configuration identifier to physical software identity, supporting the automatic and accurate processing of subsequent software package files.
[0079] It should be noted that the above examples are only for understanding this application and do not constitute a limitation on the automatic flashing method of separating the hardware and software of the commercial vehicle all-in-one controller in this application. Any simple modifications based on this technical concept are within the protection scope of this application.
[0080] This application also provides an automatic flashing device for a commercial vehicle all-in-one controller with separate hardware and software. Please refer to [link / reference]. Figure 3 The automatic flashing device for commercial vehicle all-in-one controllers with separate hardware and software includes: The quota acquisition module 10 is used to acquire the loading quota list, which includes hardware drawing numbers and software drawing numbers; The version query module 20 is used to query a preset software drawing number and software version number lookup database based on the software drawing number to obtain the software version number corresponding to the software drawing number. The file acquisition module 30 is used to acquire the corresponding software package file from the preset software package storage path according to the software version number; The flashing control module 40 is used to send the software package file to the automatic flashing device so that the automatic flashing device can perform a flashing operation on the all-in-one controller according to the software package file.
[0081] The automatic flashing device for commercial vehicle all-in-one controllers with hardware and software separation provided in this application adopts the automatic flashing method for commercial vehicle all-in-one controllers with hardware and software separation in the above embodiments. It can solve the technical problem of how to eliminate the redundancy of parts caused by hardware and software binding in commercial vehicle all-in-one controllers and realize the automatic flashing and data traceability control of hardware and software decoupling at the production line level. Compared with the prior art, the beneficial effects of the automatic flashing device for commercial vehicle all-in-one controllers with hardware and software separation provided in this application are the same as the beneficial effects of the automatic flashing method for commercial vehicle all-in-one controllers with hardware and software separation provided in the above embodiments. Moreover, other technical features in the automatic flashing device for commercial vehicle all-in-one controllers with hardware and software separation are the same as the features disclosed in the methods of the above embodiments, and will not be repeated here.
[0082] In one embodiment, the version query module 20 is also used to parse the software drawing number to obtain module identification information; Based on the module identification information, search for matching candidate records in the software drawing number and software version number lookup database; Filter the candidate records to find the target record that is exactly the same as the software drawing number; Extract the version number field stored in the target record as the software version number corresponding to the software drawing number.
[0083] In one embodiment, the file acquisition module 30 is further configured to generate a file retrieval request based on the software version number; Send the file retrieval request to the file management system; Receive the software package file corresponding to the software version number returned by the file management system.
[0084] In one embodiment, the quota acquisition module 10 is further configured to send a quota query request to the manufacturing execution system, the quota query request carrying a unique vehicle identification code; Receive the initial loading quota returned by the manufacturing execution system; The hardware and software drawing numbers corresponding to the all-in-one controller are obtained by analyzing the initial loading quota. Combine hardware drawing numbers and software drawing numbers to generate a loading quota list.
[0085] In one embodiment, the write control module 40 is also used to create a blank data table structure; Write the hardware drawing number into the hardware identifier field of the blank data table structure; Write the software drawing number and software version number into the software identifier field of the blank data table structure; Save the completed blank data table structure as a hardware / software matching information table.
[0086] In one embodiment, the write control module 40 is also used to convert the file format of the blank data table structure into a preset data format; Save the converted blank data table structure as a local temporary file; Upload local temporary files to the data platform; Receive the storage completion confirmation information returned by the data platform; The storage completion confirmation message confirms that the hardware and software matching information table has been saved.
[0087] In one embodiment, the write control module 40 is also used to establish a communication connection with the automatic write device; Write the storage path information of the package file into the flash boot command; Send the flashing start command to the automatic flashing device; Receive confirmation information that the automatic flashing device has completed the flashing process.
[0088] This application provides an automatic flashing device for a commercial vehicle all-in-one controller with separate hardware and software. The automatic flashing device for a commercial vehicle all-in-one controller with separate hardware and software includes: at least one processor; and a memory communicatively connected to at least one processor; wherein the memory stores instructions that can be executed by at least one processor, and the instructions are executed by at least one processor to enable at least one processor to execute the automatic flashing method for a commercial vehicle all-in-one controller with separate hardware and software in the above embodiment 1.
[0089] The following is for reference. Figure 4 This document illustrates a schematic diagram of an automatic flashing device suitable for implementing the hardware and software separation of a commercial vehicle all-in-one controller according to embodiments of this application. The automatic flashing device for commercial vehicle all-in-one controllers in this application can include, but is not limited to, mobile terminals such as mobile phones, laptops, digital radio receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), and in-vehicle terminals (e.g., in-vehicle navigation terminals), as well as fixed terminals such as digital TVs and desktop computers. Figure 4 The illustrated automatic flashing device for commercial vehicle all-in-one controllers with separate hardware and software is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.
[0090] like Figure 4As shown, the automatic flashing device for the hardware and software separation of the commercial vehicle all-in-one controller may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to the program stored in ROM (Read Only Memory) 1002 or the program loaded from storage device 1003 into RAM (Random Access Memory) 1004. RAM 1004 also stores various programs and data required for the operation of the automatic flashing device for the commercial vehicle all-in-one controller. The processing unit 1001, ROM 1002, and RAM 1004 are interconnected via bus 1005. Input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to I / O interface 1006: input devices 1007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1009. Communication device 1009 allows the automatic flashing device for commercial vehicle all-in-one controllers with separate hardware and software to wirelessly or wiredly communicate with other devices to exchange data. Although the figure shows an automatic flashing device for commercial vehicle all-in-one controllers with separate hardware and software having various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or have alternatively.
[0091] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from ROM 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.
[0092] The automatic flashing device for commercial vehicle all-in-one controllers with hardware and software separation provided in this application adopts the automatic flashing method for commercial vehicle all-in-one controllers with hardware and software separation in the above embodiments. It can solve the technical problem of how to eliminate the redundancy of parts caused by hardware and software binding in commercial vehicle all-in-one controllers and realize the automatic flashing and data traceability control of hardware and software decoupling at the production line level. Compared with the prior art, the beneficial effects of the automatic flashing device for commercial vehicle all-in-one controllers with hardware and software separation provided in this application are the same as the beneficial effects of the automatic flashing method for commercial vehicle all-in-one controllers with hardware and software separation provided in the above embodiments. Moreover, other technical features in the automatic flashing device for commercial vehicle all-in-one controllers with hardware and software separation are the same as the features disclosed in the method of the previous embodiment, and will not be repeated here.
[0093] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.
[0094] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
[0095] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, which are used to execute the automatic flashing method for separating the hardware and software of the commercial vehicle all-in-one controller in the above embodiments.
[0096] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, RAM (Random Access Memory), ROM (Read Only Memory), EPROM (Erasable Programmable Read Only Memory or Flash Memory), optical fibers, CD-ROM (CD-Read Only Memory), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.
[0097] The aforementioned computer-readable storage medium may be included in an automatic flashing device that separates the hardware and software of a commercial vehicle all-in-one controller; or it may exist independently and not be assembled into an automatic flashing device that separates the hardware and software of a commercial vehicle all-in-one controller.
[0098] The aforementioned computer-readable storage medium carries one or more programs. When these programs are executed by an automatic flashing device for the commercial vehicle all-in-one controller with separate hardware and software, the automatic flashing device for the commercial vehicle all-in-one controller performs the following actions: obtains a vehicle installation quota list, wherein the vehicle installation quota list includes hardware drawing numbers and software drawing numbers; queries a preset software drawing number and software version number lookup database based on the software drawing number to obtain the software version number corresponding to the software drawing number; obtains the corresponding software package file from a preset software package storage path based on the software version number; and sends the software package file to the automatic flashing device, so that the automatic flashing device performs a flashing operation on the all-in-one controller based on the software package file, thereby constructing a hardware and software separated bill of materials architecture.
[0099] Computer program code for performing the operations of this application can be written in one or more programming languages or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, and C++, as well as conventional procedural programming languages such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including LAN (Local Area Network) or WAN (Wide Area Network)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0100] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.
[0101] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.
[0102] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described automatic flashing method for separating the hardware and software of a commercial vehicle all-in-one controller. This solves the technical problem of how to eliminate component redundancy caused by hardware and software bonding in commercial vehicle all-in-one controllers and achieve production line-level hardware and software decoupling for automatic flashing and data traceability control. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the automatic flashing method for separating the hardware and software of a commercial vehicle all-in-one controller provided in the above embodiments, and will not be elaborated upon here.
[0103] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the above-described automatic flashing method for separating the hardware and software of a commercial vehicle all-in-one controller.
[0104] The computer program product provided in this application can solve the technical problem of how to eliminate the redundancy of parts caused by the hardware and software binding of commercial vehicle all-in-one controllers and realize automatic flashing and data traceability control of hardware and software decoupling at the production line level. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as the beneficial effects of the automatic flashing method for hardware and software separation of commercial vehicle all-in-one controllers provided in the above embodiments, and will not be repeated here.
[0105] The above description is only a part of the embodiments of this application and does not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included in the patent protection scope of this application.
Claims
1. An automatic flashing method for a commercial vehicle all-in-one controller with separate hardware and software, characterized in that, The method includes: Obtain the loading quota list, wherein the loading quota list includes hardware drawing numbers and software drawing numbers; The software version number is obtained by querying a preset software version number and software version number lookup database based on the software version number. The corresponding software package file is retrieved from the preset software package storage path according to the software version number; The software package file is sent to the automatic flashing device so that the automatic flashing device performs a flashing operation on the all-in-one controller according to the software package file.
2. The method as described in claim 1, characterized in that, The step of querying a preset software drawing number and software version number lookup database based on the software drawing number to obtain the software version number corresponding to the software drawing number includes: The module identification information is obtained by parsing the software drawing number; Based on the module identification information, a matching candidate record is retrieved from the software drawing number and software version number lookup database; Filter the candidate records to select target records that are exactly the same as the software drawing number; Extract the version number field stored in the target record as the software version number corresponding to the software drawing number.
3. The method as described in claim 1, characterized in that, The step of retrieving the corresponding software package file from the preset software package storage path according to the software version number includes: Generate a file retrieval request based on the software version number; Send the file retrieval request to the file management system; Receive the software package file corresponding to the software version number returned by the file management system.
4. The method as described in claim 1, characterized in that, The steps for obtaining the loading quota list include: Send a quota query request to the manufacturing execution system, the quota query request carrying the vehicle's unique identification code; Receive the initial loading quota returned by the manufacturing execution system; The initial loading quota is analyzed to obtain the hardware and software drawing numbers corresponding to the all-in-one controller; The hardware drawing number and the software drawing number are combined to generate a loading quota list.
5. The method as described in claim 1, characterized in that, Following the method, the method also includes: Create a blank data table structure; Write the hardware drawing number into the hardware identifier field of the blank data table structure; Write the software drawing number and the software version number into the software identifier field of the blank data table structure; The completed blank data table structure is saved as a hardware / software matching information table.
6. The method as described in claim 5, characterized in that, The step of saving the completed blank data table structure as the hardware / software matching information table includes: Convert the file format of the blank data table structure into a preset data format; Save the converted blank data table structure as a local temporary file; Upload the local temporary file to the data platform; Receive the storage completion confirmation information returned by the data platform; The storage completion confirmation information confirms that the hardware and software matching information table has been saved.
7. The method as described in claim 1, characterized in that, The step of sending the software package file to the automatic flashing device, so that the automatic flashing device performs a flashing operation on the all-in-one controller according to the software package file, includes: Establish a communication connection with the automatic writing device; Write the storage path information of the software package file into the flash boot command; Send the flashing start command to the automatic flashing device; Receive confirmation information of completion of the writing process returned by the automatic writing device.
8. An automatic flashing device for a commercial vehicle all-in-one controller with separate hardware and software, characterized in that, The device includes: The quota acquisition module is used to acquire the loading quota list, wherein the loading quota list includes hardware drawing numbers and software drawing numbers; The version query module is used to query a preset software drawing number and software version number lookup database based on the software drawing number to obtain the software version number corresponding to the software drawing number; The file acquisition module is used to acquire the corresponding software package file from the preset software package storage path according to the software version number; The flashing control module is used to send the software package file to the automatic flashing device, so that the automatic flashing device performs a flashing operation on the all-in-one controller according to the software package file.
9. An automatic flashing device for a commercial vehicle all-in-one controller with separate hardware and software, characterized in that, The device includes: a memory, a processor, and an automatic flashing program for a commercial vehicle all-in-one controller with separate hardware and software, stored on the memory and executable on the processor. The automatic flashing program for a commercial vehicle all-in-one controller with separate hardware and software is configured to implement the steps of the automatic flashing method for a commercial vehicle all-in-one controller with separate hardware and software as described in any one of claims 1 to 7.
10. A storage medium, characterized in that, The storage medium stores an automatic flashing program for the hardware and software separation of a commercial vehicle all-in-one controller. When the processor executes the automatic flashing program for the hardware and software separation of a commercial vehicle all-in-one controller, it implements the steps of the automatic flashing method for the hardware and software separation of a commercial vehicle all-in-one controller as described in any one of claims 1 to 7.