Vehicle software file flashing method, vehicle manufacturing system and storage medium

Abstract

The application discloses a kind of vehicle software file's flashing method, comprising: in response to the target software list obtained after being successfully matched with the production system of vehicle, the target software file acquisition request sent by EOL tool received, target software file is sent to EOL tool, so that EOL tool can be written to vehicle with target software file;Production system generates broadcast file after successfully matching target software list with OTA system.The vehicle software file flashing method of the application, after OTA system and production system successfully match to obtain target software list, the target software file acquisition request of EOL tool can be received, and target software file is sent to EOL tool, so that EOL tool can be written to vehicle with target software file according to the flashing information in broadcast file sent by production system.The introduction of OTA system makes the flashing of vehicle software can be maintained by OTA system uniformly, saves part of labor cost, improves the accuracy of data, improves user experience.

Description

Vehicle software flashing methods, vehicle manufacturing systems and storage media Technical Field

[0001] This application relates to the technical field of vehicle manufacturing, and in particular to a method for flashing vehicle software files, a vehicle manufacturing system, and a computer-readable storage medium. Background Technology

[0002] Currently, in the vehicle manufacturing process, the management of the software list information during the flashing of software files required for vehicle hardware is done manually. Software information management engineers manually select from the released software information and choose which to use at different stages of the subsequent vehicle manufacturing process. If the vehicle needs to be flashed with a new software version, the software information must be manually replaced. However, this process is cumbersome, not only lacking in accuracy but also detrimental to subsequent update processes. Summary of the Invention

[0003] This application provides a method for flashing vehicle software files, a vehicle manufacturing system, and a computer-readable storage medium.

[0004] The method for flashing vehicle software files in this application is used in an OTA system, and the method includes:

[0005] In response to a target software file retrieval request received from an EOL tool after successfully matching the target software list with the vehicle's production system, the target software file is sent to the EOL tool so that the EOL tool can flash the target software file to the vehicle. The production system generates a broadcast file after successfully matching the target software list with the OTA system. The broadcast file includes the target software list and flashing information for the target software file. The target software file retrieval request is generated based on the broadcast file.

[0006] Thus, in the vehicle software flashing method proposed in this application, after the OTA system and the production system successfully match and obtain the target software list, the OTA system can receive the target software file acquisition request from the EOL tool and send the target software file to the EOL tool. The EOL tool then flashes the target software file to the vehicle according to the flashing information in the broadcast file sent by the production system and reports the flashing completion information to both the production system and the OTA system. The production system, OTA system, and EOL tool form a complete closed loop. The introduction of the OTA system allows vehicle software flashing to be uniformly maintained by the OTA system, saving some labor costs, improving data accuracy, and enhancing the user experience.

[0007] The method further includes, before sending the target software file to the EOL tool:

[0008] Receive and store the software files released by the vehicle's R&D system after R&D is completed.

[0009] In this way, the OTA system can receive software files released by the R&D system so as to match the software file versions with the production system.

[0010] The method further includes:

[0011] In response to the target software list acquisition request automatically triggered by the production system at a preset workstation, target software list matching is performed according to the target software list acquisition request.

[0012] In this way, the production system can automatically trigger a request to the OTA system to obtain the target software list at the preset workstation, perform target software list matching, and obtain the target software list for subsequent software flashing.

[0013] The step of responding to a target software list acquisition request automatically triggered by the production system at a preset workstation, and performing target software list matching based on the target software list acquisition request, includes:

[0014] Based on the production information and vehicle configuration information in the target software file request, the target software list is obtained by matching the software files released by the R&D system with the software files used for the target vehicle hardware according to preset rules.

[0015] In this way, the OTA system can match and generate a target software list based on the target software file request. The production system receives and stores the target software list in order to generate a broadcast file for obtaining the target software file.

[0016] The method further includes:

[0017] If the target vehicle is a first-category vehicle, and some of the target vehicle's hardware matches the target software file, it is confirmed that it has been successfully matched with the production system.

[0018] If the target vehicle is a second-category vehicle, and the software files are obtained after matching all the hardware of the target vehicle, then it is confirmed that the vehicle has been successfully matched with the production system.

[0019] Therefore, the OTA system needs to execute different matching rules according to the vehicle category to obtain a list of target software for the vehicle, so that the target software files can be flashed for different types of vehicles in the future.

[0020] The method for flashing vehicle software files in this application, used in EOL tools, includes:

[0021] After the vehicle's production system and OTA system successfully match and obtain the target software list, a broadcast file sent by the production system is received. The broadcast file includes the target software list and the flashing information of the target software files.

[0022] Based on the broadcast file, a target software file acquisition request is sent to the OTA system;

[0023] The system receives the target software file returned by the OTA system and flashes the target software file to the vehicle according to the flashing information.

[0024] In this way, the EOL tool can receive broadcast files sent by the production system, send a request to obtain the target software file, and complete the flashing process of the target software file according to the flashing information in the broadcast file, saving some labor costs and improving the accuracy of the data.

[0025] The method includes:

[0026] After the vehicle completes the flashing of the target software file, it reports the completion information to the production system, and the production system reports the completion information to the OTA system.

[0027] In this way, after the target software file of the vehicle is flashed, the EOL tool can report the completion information to the production system and the OTA system, so that the flashing process of the vehicle software file forms a complete closed loop structure, reducing manpower, improving data accuracy, and enhancing the user experience.

[0028] The method for flashing vehicle software files in this application, used in OTA systems, includes:

[0029] In response to a target software file retrieval request sent by the production system after successfully matching the target software list with the vehicle's production system;

[0030] The software file is sent to the vehicle to flash the software file to the vehicle. After the production system successfully matches the target software list with the OTA system, it generates a broadcast file. The broadcast file includes the target software list and the flashing information of the target software file. The target software file acquisition request is generated based on the broadcast file.

[0031] In this way, the OTA system can directly interact with the production system and send software files to the vehicle to complete the software flashing process. Direct data flashing in the OTA system allows for unified management of data sources in the production process and the market, improving data accuracy.

[0032] The method for flashing vehicle software files in this application, used in EOL tools, includes:

[0033] After the vehicle's production system and OTA system successfully match and obtain the target software list, the system receives a broadcast file sent by the production system. The broadcast file includes the target software list and the flashing information of the target software file. The OTA system then sends the target software file to the CDN server according to the target software list.

[0034] Based on the broadcast file, a request to obtain the target software file is sent to the CDN server.

[0035] The system receives the target software file returned by the CDN server and flashes the target software file to the vehicle according to the flashing information.

[0036] In this way, a CDN server is introduced to store the target software files, allowing the EOL tool to directly request and retrieve them. This reduces the server load on the OTA system and improves system stability.

[0037] The vehicle manufacturing system of this application includes a production system, an OTA system, and an EOL tool. The production system is used to generate a broadcast file after successfully matching with the OTA system to obtain a target software list. The broadcast file includes the target software list and the flashing information of the target software file.

[0038] The production system is also used to send the broadcast file to the EOL tool;

[0039] The EOL tool is used to send a target software file acquisition request to the OTA system based on the broadcast file;

[0040] The OTA system is used to return the target software file to the EOL tool according to the target software file acquisition request;

[0041] The EOL tool is also used to flash the target software file to the vehicle according to the flashing information.

[0042] The vehicle manufacturing system of this application includes a production system and an OTA system. The production system is used to generate a broadcast file after successfully matching with the OTA system to obtain a target software list. The broadcast file includes the target software list and the flashing information of the target software file.

[0043] The production system is also used to generate a target software file acquisition request based on the broadcast file, and send the target software file acquisition request to the OTA system;

[0044] The OTA system is used to send the target software file to the vehicle according to the target software file acquisition request, and to flash the target software file to the vehicle according to the flashing information.

[0045] The vehicle manufacturing system of this application includes a production system, an OTA system, a CDN server, and an EOL tool. The production system is used to generate a broadcast file after successfully matching the target software list with the OTA system. The broadcast file includes the target software list and the flashing information of the target software file.

[0046] The production system is also used to send the broadcast file to the EOL tool;

[0047] The OTA system is used to send the target software files to the CDN server according to the target software list;

[0048] The EOL tool is used to send a target software file retrieval request to the CDN server based on the broadcast file;

[0049] The CDN server is used to return the target software file to the EOL tool according to the target software file acquisition request;

[0050] The EOL tool is also used to flash the target software file to the vehicle according to the flashing information.

[0051] The computer-readable storage medium of this application stores a computer program that, when executed by one or more processors, implements the above-described method for flashing vehicle software files.

[0052] Additional aspects and advantages of embodiments of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of embodiments of this application. Attached Figure Description

[0053] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the description of the embodiments taken in conjunction with the following drawings, wherein:

[0054] Figure 1 is a schematic diagram of the method for flashing vehicle software files in this application;

[0055] Figure 2 is a flowchart illustrating the method for flashing the vehicle software files in this application;

[0056] Figure 3 is a data flow timing diagram of the vehicle software file flashing method of this application;

[0057] Figure 4 is a flowchart illustrating the method for flashing the vehicle software files in this application;

[0058] Figure 5 is a flowchart illustrating the method for flashing the vehicle software files in this application.

[0059] Figure 6 is a data flow timing diagram of the vehicle software file flashing method of this application;

[0060] Figure 7 is a flowchart illustrating the method for flashing the vehicle software files in this application;

[0061] Figure 8 is a flowchart illustrating the method for flashing the vehicle software files in this application;

[0062] Figure 9 is a flowchart illustrating the method for flashing the vehicle software files in this application;

[0063] Figure 10 is a data flow timing diagram of the vehicle software file flashing method of this application;

[0064] Figure 11 is a flowchart illustrating the method for flashing the vehicle software files in this application;

[0065] Figure 12 is a flowchart illustrating the method for flashing the vehicle software files in this application;

[0066] Figure 13 is a data flow timing diagram of the vehicle software file flashing method of this application;

[0067] Figure 14 is a flowchart illustrating the method for flashing the vehicle software files in this application;

[0068] Figure 15 is a data flow timing diagram of the vehicle software file flashing method of this application;

[0069] Figure 16 is a data flow timing diagram of the vehicle software file flashing method of this application. Detailed Implementation

[0070] The embodiments of this application are described in detail below. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the embodiments of this application, and should not be construed as limiting the embodiments of this application.

[0071] Currently, in the vehicle manufacturing process, the management of software inventory information during the flashing of software files required for vehicle hardware is done manually. This process is cumbersome, inaccurate, and detrimental to subsequent software updates. Furthermore, this primarily manual software data management model leads to inconsistencies in software data management methods and data sources between the production line and the market, making it impossible to uniformly manage vehicle software versions.

[0072] Based on the aforementioned potential problems, please refer to Figure 1. This application provides a vehicle manufacturing system 100, including a production system 101, an OTA system 102, and an EOL tool 103. The production system 101 generates a broadcast file after successfully matching with the OTA system 102 to obtain a target software list. The broadcast file includes the target software list and flashing information for the target software file. The production system 101 also sends the broadcast file to the EOL tool 103. The EOL tool 103 sends a target software file retrieval request to the OTA system 102 based on the broadcast file. The OTA system 102 returns the target software file to the EOL tool 103 based on the target software file retrieval request. The EOL tool 103 also flashes the target software file to the vehicle based on the flashing information.

[0073] Referring to Figure 2, this application also provides a method for flashing vehicle software files. The vehicle manufacturing method of this application can be implemented by the vehicle manufacturing system 100 of this application. Taking the OTA system 102 as the executing entity, the flashing method includes:

[0074] 001: In response to the target software file acquisition request received from the EOL tool 103 after successfully matching the target software list with the vehicle's production system 101, the target software file is sent to the EOL tool 103 so that the EOL tool 103 can flash the target software file to the vehicle.

[0075] In some implementations, the OTA system 102 is used to send the target software file to the EOL tool 103 in response to a target software file acquisition request received after successfully matching the target software list with the vehicle's production system 101, so that the EOL tool 103 can flash the target software file to the vehicle.

[0076] Specifically, in the vehicle software flashing method of this application, the production system 101 can control the start of the vehicle manufacturing process. The OTA system 102 stores and manages software information. The EOL tool 103 completes the software flashing process. By introducing the OTA (Over-the-Air) system 102 and the EOL (End-of-life) tool 103 to establish a connection, the OTA system 102 can provide the EOL tool 103 with a method for flashing and packaging software.

[0077] As shown in Figure 3, after the vehicle manufacturing process begins on the production system 101, the production system 101 first interacts with the OTA system 102. The software information required by the production system 101 is matched with the software information stored and managed in the OTA system 102 to obtain a target software list. The target software list provides all software files that can be used for the target vehicle hardware. The vehicle hardware included in different models is different, and the target software list may change as the software version is updated.

[0078] Once the production system 101 and the OTA system 102 successfully match and obtain the target software list, the production system 101 generates a broadcast file and sends it to the EOL tool 103. The broadcast file includes the target software list and the flashing information for the target software files.

[0079] After receiving the broadcast file, the EOL tool 103 immediately sends a target software file retrieval request to the OTA system 102, interacting with the OTA system 102. Based on the received target software file retrieval request, the OTA system 102 selects the target software file from the target software list and sends the selected target software file back to the EOL tool 103. Finally, the EOL tool 103 can then flash the received target software file to the vehicle according to the flashing information in the broadcast file sent by the production system 101.

[0080] The introduction of OTA system 102, leveraging the closed-loop structure formed by "production system 101 - OTA system 102 - EOL tool 103," supports real-time filtering of the latest available target software list based on the target software file retrieval requests sent by different vehicles through EOL tool 103 and the vehicle's configuration information. Vehicle software flashing can then be uniformly maintained by OTA system 102, saving some labor costs and improving data accuracy. Furthermore, OTA system 102's management of vehicle software files allows for "one file per vehicle," enhancing the user experience.

[0081] In summary, in the vehicle software file flashing method proposed in this application, after the OTA system and the production system successfully match to obtain the target software list, the OTA system can receive the target software file acquisition request from the EOL tool and send the target software file to the EOL tool. The EOL tool then flashes the target software file to the vehicle based on the flashing information in the broadcast file sent by the production system. The production system, OTA system, and EOL tool form a complete closed loop. The introduction of the OTA system allows vehicle software flashing to be uniformly maintained by the OTA system, saving some labor costs, improving data accuracy, and enhancing the user experience.

[0082] In some embodiments, the vehicle manufacturing system 100 also includes a research and development system 104. As shown in Figure 1, the research and development system 104 is used to manage all software information during the research and development phase, maintain the software versions released at different nodes in the vehicle manufacturing process, and send the approved software versions to the OTA system 102.

[0083] Referring to Figure 4, in some embodiments, the method further includes the following step before step 001:

[0084] 002: Receive and store the software files released by the vehicle's R&D system after R&D is completed.

[0085] In some implementations, the OTA system 102 is used to receive and store software files released by the vehicle's R&D system 104 after R&D is completed.

[0086] Specifically, the R&D system 104 manages all software information during the R&D phase and maintains the software versions released at different stages of the vehicle manufacturing process. As shown in Figure 3, the R&D system 104 sends the approved software version to the OTA system 102, and the OTA system 102 stores the received software version.

[0087] Understandably, during the collaborative work at each stage of the vehicle manufacturing system 100, the OTA system 102 needs to manage all software versions released by the R&D system 104. Users can manually configure the software file version available for use by the production system 101 in the OTA system 102. In particular, if there is no user configuration record in the OTA system 102, the latest version of the software file can be used by default to complete the vehicle manufacturing process.

[0088] In this way, the OTA system can receive software files released by the R&D system so as to match the software file versions with the production system.

[0089] Please refer to Figure 5. In some embodiments, the method further includes:

[0090] 003: In response to the target software list retrieval request automatically triggered by the production system at the preset workstation, perform target software list matching based on the target software list retrieval request.

[0091] In some implementations, the OTA system 102 is used to respond to a target software list acquisition request automatically triggered by the production system 101 at a preset workstation, and to perform target software list matching based on the target software list acquisition request.

[0092] Specifically, after the OTA system 102 receives the software file released by the R&D system, the user can set a trigger command at a preset workstation in the production system 101, as shown in Figure 3, to send a target software list acquisition request to the OTA system 102. The target software list acquisition request is used to obtain information including the software required for vehicle manufacturing, such as production information and vehicle configuration information. The preset workstation needs to ensure certain conditions are met: during the vehicle manufacturing process, after the vehicle identification code is generated, until the production line reaches the EOL tool 103, the production system 101 must have sufficient time to use the target software list provided by the OTA system 102 to produce the broadcast file.

[0093] The interaction process of production system 101 obtaining the target software list from OTA system 102 is shown in Figure 6. A target software list retrieval request is set at a preset workstation in production system 101. When the production line reaches this preset workstation, the target software list retrieval request is triggered, requesting matching from OTA system 102 to ultimately obtain the target software list. The matching process follows certain requirements; that is, the software information on the target software list must match the hardware information used in vehicle manufacturing.

[0094] In this way, the production system can automatically trigger a request to the OTA system to obtain the target software list at the preset workstation, perform target software list matching, and obtain the target software list for subsequent software flashing.

[0095] Specifically, including the interaction process between the production system 101 and the OTA system 102, all interaction processes of the vehicle software file flashing method of this application are completed through cloud-to-cloud docking. A protocol-adaptive framework can be built, using protocols such as HTTPS as the interaction protocol, and transmitting interaction data through API interfaces (Application Programming Interfaces).

[0096] Please refer to Figure 7. In some embodiments, step 03 includes:

[0097] 0031: Based on the production information and vehicle configuration information in the target software file request, match the software files used for the target vehicle hardware in the software files released by the R&D system according to preset rules to obtain the target software list.

[0098] In some implementations, the OTA system 102 is used to match the software files for the target vehicle hardware in the software files released by the R&D system 104 according to preset rules based on the production information and vehicle configuration information in the target software file request, so as to obtain a target software list.

[0099] Specifically, the target software file request sent by the production system 101 to the OTA system 102 contains software production information and vehicle configuration information. The production information includes the vehicle chassis number, material number, order number, and the planned start time for vehicle welding. The vehicle configuration information refers to the hardware information to be installed on the vehicle, including component assembly numbers and part numbers. The production system 101 encapsulates the above information into a lightweight data exchange format JSON message (JavaScript Object Notation), namely the target software file request, and sends it to the OTA system 102.

[0100] The OTA system 102 matches the vehicle hardware with the software files released by the R&D system 104. The matching rules include: the start time of the vehicle's welding plan is greater than or equal to the release time of the software; the part number in the vehicle's hardware information matches the corresponding hardware number in the software; and the configuration information of the vehicle's part number matches the configuration information of the software. All of the above matching rules must be met simultaneously for the hardware and software to be considered successfully matched.

[0101] After successful matching, the software files usable for the target vehicle hardware form a target software list. The target software list includes the production information of the aforementioned software and vehicle configuration information. Production information includes the vehicle chassis number, material number, order number, and the planned start time for vehicle welding. Vehicle configuration information refers to the hardware information installed on the vehicle, including the component assembly number and part number, information about the corresponding electronic control unit, software part number, software version number, and the storage address of the software files. Finally, the OTA system 102 encapsulates the above information into a JSON message, as shown in Figure 6, and combines it to generate the target software list.

[0102] In addition, Figure 6 shows that the target software list of the vehicle is returned to the production system 101 via communication protocols such as HTTPS, so that the production system 101 can store the target software list and generate a broadcast file for obtaining the target software files.

[0103] In this way, the OTA system can match and generate a target software list based on the target software file request. The production system receives and stores the target software list in order to generate a broadcast file for obtaining the target software file.

[0104] Please refer to Figure 8. In some embodiments, step 03 includes:

[0105] 0032: If the target vehicle is a Class I vehicle, and some of the target vehicle's hardware matches the target software file, confirm successful matching with the production system;

[0106] 0033: If the target vehicle is a Category 2 vehicle, and the software files are obtained after matching all the hardware of the target vehicle, confirm that the matching with the production system is successful.

[0107] In some implementations, the OTA system 102 is used to confirm successful matching with the production system 101 if the target vehicle is a first-category vehicle and the target software file is matched with some of the target vehicle's hardware, and to confirm successful matching with the production system 101 if the target vehicle is a second-category vehicle and the software file is matched with all of the target vehicle's hardware.

[0108] Specifically, the OTA system 102 can match all the software information installed in the vehicle with the hardware information and vehicle configuration information of the production system 101.

[0109] For different vehicle categories of the target vehicle requiring matching, the OTA system 102 will adopt different matching rules. For non-mass-produced Category 1 vehicles, i.e., prototype vehicles, the OTA system 102 will perform fuzzy matching. During the fuzzy matching process, if a hardware component of the target vehicle matches the software in the target software file, the hardware is considered to have successfully matched; if the hardware does not match the software, it is skipped, and the matching process continues with subsequent hardware. The matching process will not be interrupted by a hardware component of the target vehicle failing to match the software in the target software file. Once all hardware matching processes are completed, it can be determined that the matching with the production system 101 has been successful, and the vehicle target software list can be obtained.

[0110] For the second category of vehicles, namely mass-produced vehicles, the OTA system 102 requires precise matching. Precise matching requires that all hardware of the target vehicle be matched with the software in the target software file in order to be considered a successful match. During the precise matching process, if any hardware fails to match the software, the matching process will terminate, and the vehicle's target software list cannot be obtained.

[0111] Therefore, the OTA system needs to execute different matching rules according to the vehicle category to obtain a list of target software for the vehicle, so that the target software files can be flashed for different types of vehicles in the future.

[0112] Please refer to Figure 9. Using the EOL tool 103 as the execution subject, the vehicle software file flashing method of this application includes:

[0113] 004: After the vehicle's production system and OTA system successfully match and obtain the target software list, receive the broadcast file sent by the production system 101;

[0114] 005: Based on the broadcast file, send a request to the OTA system to obtain the target software file;

[0115] 006: Receive the target software file returned by the OTA system and flash the target software file to the vehicle according to the flashing information.

[0116] In some implementations, the EOL tool 103 is used to receive a broadcast file sent by the production system 101 after the vehicle's production system 101 and OTA system 102 have successfully matched and obtained the target software list, and to send a target software file acquisition request to the OTA system 102 according to the broadcast file, and to receive the target software file returned by the OTA system 102, and to flash the target software file to the vehicle according to the flashing information.

[0117] The vehicle software file flashing method in this embodiment differs from the flashing method using the OTA system 102 as the execution subject only in the execution subject; the principle is basically the same. Please refer to the explanations of the relevant parts in the above embodiment, which will not be repeated here.

[0118] Specifically, the target software file acquisition request can be in URL (Uniform Resource Locator) format, as shown in Figure 10, which illustrates the data transmission process between the EOL tool 103 and the OTA system 102. The EOL tool 103 completes the download and storage of the software file.

[0119] In this way, the EOL tool can receive broadcast files sent by the production system, send a request to obtain the target software file, and complete the flashing process of the target software file according to the flashing information in the broadcast file, saving some labor costs and improving the accuracy of the data.

[0120] Please refer to Figure 11. In some embodiments, the method includes:

[0121] 007: After the vehicle completes the target software file flashing, the completion information is reported to the production system 101, and the production system 101 reports the completion information to the OTA system 102.

[0122] In some implementations, the EOL tool 103 is used to report completion information to the production system 101 after the vehicle has completed the target software file flashing, and the production system 101 is used to report the completion information to the OTA system 102.

[0123] Specifically, as shown in Figure 3, after the EOL tool 103 completes the flashing of the vehicle's target software file, it can report the completion information to the production system 101. After receiving the completion information, the production system 101 reports the completion information to the OTA system 102. This ultimately forms a complete closed-loop structure of "production system - OTA system - EOL tool" as shown in Figure 1.

[0124] In this way, after the target software file of the vehicle is flashed, the EOL tool can report the completion information to the production system and the OTA system, so that the flashing process of the vehicle software file forms a complete closed loop structure, reducing manpower, improving data accuracy, and enhancing the user experience.

[0125] Understandably, the flashing method using EOL tool 103 as the execution subject includes all the implementation methods of the flashing method using OTA system 102 as the execution subject described above. The corresponding parts can be referred to the explanation of the aforementioned implementation methods, and will not be repeated here.

[0126] This application also provides a vehicle manufacturing system 200. Specifically, the vehicle manufacturing system 200 includes a production system 201 and an OTA system 202. The production system 201, after successfully matching a target software list with the OTA system 202, generates a broadcast file, generates a target software file retrieval request based on the broadcast file, and sends the target software file retrieval request to the OTA system 202. The OTA system 202 is used to send the target software file to the vehicle according to the target software file retrieval request, and flash the target software file to the vehicle according to flashing information. The broadcast file includes a target software list and flashing information for the target software file, and the target software file retrieval request is generated based on the broadcast file.

[0127] Referring to Figure 12, this application also provides a method for flashing vehicle software files. The vehicle manufacturing method of this application can be implemented by the vehicle manufacturing system 200 of this application. Taking the OTA system 202 as the executing entity, the flashing method includes:

[0128] 011: Response to a target software file retrieval request sent by the production system after successfully matching the target software list with the vehicle's production system;

[0129] 012: Send the software file to the vehicle to flash the software file to the vehicle.

[0130] In some implementations, the OTA system 202 is used to respond to a target software file acquisition request received from the production system 201 after successfully matching the target software list with the vehicle's production system 201, and to send the software file to the vehicle to flash the software file to the vehicle.

[0131] Specifically, the vehicle software file flashing method of this embodiment is basically the same as the flashing method based on the vehicle manufacturing system 100 with the OTA system 102 as the execution subject. The production system 201 and OTA system 202 in the vehicle manufacturing system 200 are basically the same as the corresponding structures in the vehicle manufacturing system 100. The specific functions will not be described in detail.

[0132] In the flashing method based on the vehicle manufacturing system 100, the EOL tool 103 still uses traditional electrical inspection tools, meaning the vehicle can only complete the production process and leave the production line after the vehicle software files are flashed. To improve the efficiency of flashing the vehicle software files, in this embodiment, the "OTA Client" in the vehicle's OTA system can be used instead of the EOL tool to complete the flashing. This allows for unified management of data sources in the production process and the market, and unifies the software flashing technology, improving data accuracy.

[0133] As shown in Figure 13, during the actual process of flashing vehicle software files in the vehicle manufacturing system 200, when the OTA system 202 receives the target software file acquisition request sent by the production system 201, the "OTA Client" flashes the software file information required by the vehicle hardware in the target software list to the vehicle.

[0134] In this way, the OTA system can directly interact with the production system and send software files to the vehicle to complete the software flashing process. Direct data flashing in the OTA system allows for unified management of data sources in the production process and the market, improving data accuracy.

[0135] This application also provides a vehicle manufacturing system 300. Specifically, the vehicle manufacturing system 300 includes a production system 301, an OTA system 302, a CDN server 303, and an EOL tool 304. The production system 301, after successfully matching with the OTA system 302 to obtain a target software list, generates a broadcast file and sends the broadcast file to the EOL tool 304. The OTA system 302 sends the target software file to the CDN server 303 according to the target software list. The CDN server 303 returns the target software file to the EOL tool 304 according to the target software file retrieval request. The EOL tool 304, based on the broadcast file, sends a target software file retrieval request to the CDN server 303 and flashes the target software file to the vehicle according to the flashing information. The broadcast file includes the target software list and the flashing information for the target software file.

[0136] Referring to Figure 14, this application also provides a method for flashing vehicle software files. The vehicle manufacturing method of this application can be implemented by the vehicle manufacturing system 300 of this application. Taking the OTA system 302 as the executing entity, the flashing method includes:

[0137] 021: After the vehicle's production system and OTA system successfully match and obtain the target software list, receive the broadcast file sent by the production system;

[0138] 022: Based on the broadcast file, send a request to the CDN server to obtain the target software file;

[0139] 023: Receive the target software file returned by the CDN server and flash the target software file to the vehicle according to the flashing information.

[0140] In some implementations, the OTA system 302 is used to receive a broadcast file sent by the production system 301 after the vehicle production system 301 and the OTA system 302 successfully match and obtain the target software list, and send a target software file acquisition request to the CDN server 303 according to the broadcast file, and receive the target software file returned by the CDN server 303, and flash the target software file to the vehicle according to the flashing information.

[0141] Specifically, the vehicle software file flashing method of this embodiment is basically the same as the flashing method based on the vehicle manufacturing system 100 with the OTA system 102 as the execution subject. The production system 201, OTA system 302, and EOL tool 304 in the vehicle manufacturing system 200 are basically the same as their corresponding structures in the vehicle manufacturing system 100. The specific functions will not be described in detail.

[0142] In the flashing method based on the vehicle manufacturing system 100, a closed loop exists consisting of "production system 101 - OTA system 102 - EOL tool 103". The OTA system 102 needs to manage all software versions at each stage of the software file flashing process, resulting in a significant workload. To reduce the load on the OTA system, a CDN server 303 (Content Delivery Network), as shown in Figure 15, is introduced into the vehicle manufacturing system 300 to provide storage space for the software files of the production system 301. Furthermore, the OTA system 302 only needs to send the target software file to the CDN server 303 and receive the push result information returned by the CDN server 303. The push result information could be, for example, whether the CDN server 303 successfully or failed to push the target software file. The OTA system 302 does not need to store the target software file, thus reducing its load.

[0143] As shown in Figure 16, during the actual process of flashing vehicle software files in the vehicle manufacturing system 300, the production system 301 and the OTA system 302 successfully match and obtain the target software list. The OTA system 302 then sends the target software files to the CDN server 303 in advance based on this list. At this time, the EOL tool 304 does not need to send a target software file retrieval request to the OTA system 302, but can instead send a request to the CDN server 303 to directly download the software files from the CDN server 303, and finally flash the target software files to the vehicle.

[0144] In this way, a CDN server is introduced to store the target software files, allowing the EOL tool to directly request and retrieve them. This reduces the server load on the OTA system and improves system stability.

[0145] In addition to HTTPS, the production system can also use MQTT, HTTP, MQ message queues, etc. as the interaction protocol when requesting the target software list from the OTA system.

[0146] When the production system requests the target software list from the OTA system, the information transmission process can use XML files, text files (TXT), etc., instead of JSON message format.

[0147] This application also provides a computer-readable storage medium storing a computer program that, when executed by one or more processors, implements the above-described method for flashing vehicle software files.

[0148] In the description of this specification, the terms "above," "specifically," "particularly," "furthermore," etc., refer to specific features, structures, materials, or characteristics described in connection with embodiments or examples that are included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0149] Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing a particular logical function or process, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0150] Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of this application.

Claims

1. A method for flashing vehicle software files, used in an OTA system, characterized in that, The method includes: in response to a target software file retrieval request received from an EOL tool after successfully matching a target software list with the vehicle's production system, sending a target software file to the EOL tool so that the EOL tool can flash the target software file to the vehicle; wherein, after successfully matching the target software list with the OTA system, the production system generates a broadcast file, the broadcast file including the target software list and flashing information for the target software file, and the target software file retrieval request is generated based on the broadcast file; the OTA system, in response to a target software list retrieval request automatically triggered by the production system at a preset workstation, including production information and vehicle configuration information, matches the target software list according to the target software list retrieval request, and sends the target software list to the production system, the production system generates the broadcast file.

2. The method according to claim 1, characterized in that, The method further includes, before sending the target software file to the EOL tool, receiving and storing the software file released by the vehicle's R&D system after R&D is completed.

3. The method according to claim 1, characterized in that, The step of responding to the target software list acquisition request automatically triggered by the production system at a preset workstation and matching the target software list according to the target software list acquisition request includes: matching software files for the target vehicle hardware in the software files released by the R&D system according to preset rules based on the production information and vehicle configuration information in the target software file request to obtain the target software list.

4. The method according to claim 3, characterized in that, The method further includes: if the target vehicle is a first-category vehicle, and the target software file is matched with some of the target vehicle's hardware, then the matching with the production system is confirmed to be successful; if the target vehicle is a second-category vehicle, and the software file is matched with all of the target vehicle's hardware, then the matching with the production system is confirmed to be successful.

5. A method for flashing vehicle software files, used in an EOL (End-of-Life) tool, characterized in that, include: After the vehicle's production system and OTA system successfully match and obtain the target software list, a broadcast file sent by the production system is received. The broadcast file includes the target software list and the flashing information of the target software files. According to the broadcast file, a target software file retrieval request is sent to the OTA system; the target software file returned by the OTA system is received, and the target software file is flashed to the vehicle according to the flashing information; when the production system is at a preset workstation, it automatically triggers a target software list retrieval request including production information and vehicle configuration information to the OTA system; the OTA system matches the target software list according to the target software list retrieval request, and after sending the target software list to the production system, the production system generates the broadcast file.

6. The method according to claim 5, characterized in that, The method includes: after the vehicle completes the flashing of the target software file, reporting completion information to the production system, and the production system reporting the completion information to the OTA system.

7. A method for flashing vehicle software files, used in an OTA system, characterized in that, The method for performing any one of claims 1-4 includes: in response to a target software file acquisition request received from a production system after successfully matching a target software list with a vehicle's production system, sending a software file to the vehicle to flash the software file to the vehicle, wherein the production system generates a broadcast file after successfully matching the target software list with an OTA system, the broadcast file including the target software list and flashing information of the target software file, and the target software file acquisition request is generated based on the broadcast file; the OTA system, in response to the target software list acquisition request automatically triggered by the production system at a preset workstation, including production information and vehicle configuration information, matching the target software list according to the target software list acquisition request, and sending the target software list to the production system, the production system generates the broadcast file.

8. A method for flashing vehicle software files, used in an EOL tool, characterized in that, include: After the vehicle's production system and OTA system successfully match and obtain the target software list, the system receives a broadcast file sent by the production system. The broadcast file includes the target software list and the flashing information of the target software file. The OTA system then sends the target software file to the CDN server according to the target software list. According to the broadcast file, a target software file retrieval request is sent to the CDN server; the target software file returned by the CDN server is received, and the target software file is flashed to the vehicle according to the flashing information; The OTA system responds to the target software list acquisition request, which is automatically triggered by the production system at a preset workstation and includes production information and vehicle configuration information. The system matches the target software list according to the target software list acquisition request and sends the target list to the production system. The production system then generates the broadcast file.

9. A vehicle manufacturing system, characterized in that, The vehicle manufacturing system includes a production system, an OTA system, and an EOL tool. The production system, after successfully matching the target software list with the OTA system, generates a broadcast file, which includes the target software list and flashing information for the target software files. The production system also sends the broadcast file to the EOL tool. The EOL tool sends a target software file retrieval request to the OTA system based on the broadcast file. The OTA system returns the target software files to the EOL tool based on the retrieval request. The EOL tool also flashes the target software files to the vehicle based on the flashing information. The OTA system, responding to the target software list retrieval request automatically triggered by the production system at a preset workstation, which includes production information and vehicle configuration information, matches the target software list according to the retrieval request and sends the target list to the production system. The production system then generates the broadcast file.

10. A vehicle manufacturing system, characterized in that, For performing the method as described in any one of claims 1-4, the vehicle manufacturing system includes a production system and an OTA system. The production system is configured to generate a broadcast file after successfully matching a target software list with the OTA system. The broadcast file includes the target software list and flashing information for the target software file. The production system is further configured to generate a target software file retrieval request based on the broadcast file and send the target software file retrieval request to the OTA system. The OTA system is configured to send the target software file to the vehicle based on the target software file retrieval request and flash the target software file to the vehicle based on the flashing information. In response to the target software list retrieval request, which is automatically triggered by the production system at a preset workstation and includes production information and vehicle configuration information, the OTA system matches the target software list based on the target software list retrieval request and sends the target software list to the production system. After this, the production system generates the broadcast file.

11. A vehicle manufacturing system, characterized in that, The vehicle manufacturing system includes a production system, an OTA system, a CDN server, and an EOL tool. The production system generates a broadcast file after successfully matching the target software list with the OTA system. The broadcast file includes the target software list and flashing information for the target software files. The production system also sends the broadcast file to the EOL tool. The OTA system sends the target software files to the CDN server according to the target software list. The EOL tool is used to send a target software file retrieval request to the CDN server based on the broadcast file; The CDN server is used to return the target software file to the EOL tool according to the target software file acquisition request; the EOL tool is also used to flash the target software file to the vehicle according to the flashing information; the OTA system responds to the target software list acquisition request, which is automatically triggered by the production system at a preset workstation and includes production information and vehicle configuration information, matches the target software list according to the target software list acquisition request, and sends the target list to the production system, after which the production system generates the broadcast file.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by one or more processors, implements the method as described in any one of claims 1-8.

Images