CN116156485A - Vehicle software file refreshing method, vehicle manufacturing system and storage medium - Google Patents
Vehicle software file refreshing method, vehicle manufacturing system and storage medium Download PDFInfo
- Publication number
- CN116156485A CN116156485A CN202310199475.7A CN202310199475A CN116156485A CN 116156485 A CN116156485 A CN 116156485A CN 202310199475 A CN202310199475 A CN 202310199475A CN 116156485 A CN116156485 A CN 116156485A
- Authority
- CN
- China
- Prior art keywords
- target software
- file
- vehicle
- software file
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
- H04W8/24—Transfer of terminal data
- H04W8/245—Transfer of terminal data from a network towards a terminal
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Multimedia (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a method for refreshing a vehicle software file, which comprises the following steps: in response to a received target software file acquisition request sent by the EOL tool after successfully matching with the production system of the vehicle to obtain a target software list, sending a target software file to the EOL tool so that the EOL tool can write the target software file to the vehicle; and the production system generates a broadcast file after successfully matching the target software list with the OTA system. In the method for refreshing the vehicle software file, after the OTA system is successfully matched with the production system to obtain the target software list, a target software file acquisition request of the EOL tool can be received, and the target software file is sent to the EOL tool, so that the EOL tool can refresh the target software file to the vehicle according to refreshing information in the broadcast file sent by the production system. The introduction of the OTA system enables the vehicle software to be uniformly maintained by the OTA system, saves part of labor cost, improves the accuracy of data and improves the use experience of users.
Description
Technical Field
The present disclosure relates to the field of vehicle manufacturing, and in particular, to a vehicle software file writing method, a vehicle manufacturing system, and a computer readable storage medium.
Background
In the manufacturing process of the current vehicle, the information management of the software list in the software file refreshing process required by the hardware of the vehicle is manually operated, and a software information management engineer manually selects from the released software information and manually selects different nodes to use in the subsequent vehicle manufacturing process. If the vehicle needs to update the new software version, the software information needs to be replaced manually. However, the process is cumbersome, not only is the accuracy low, but also the subsequent updating process is not facilitated.
Disclosure of Invention
A method of writing a vehicle software file, a vehicle manufacturing system, and a computer-readable storage medium are provided.
The method for refreshing the vehicle software file is used for an OTA system, and comprises the following steps:
and responding to a target software file acquisition request sent by a received EOL tool after successfully matching with a production system of a vehicle to obtain a target software list, and sending a target software file to the EOL tool so that the EOL tool can write the target software file into the vehicle, wherein the production system generates a broadcast file after successfully matching with an OTA system with the target software list, the broadcast file comprises the target software list and writing information of the target software file, and the target software file acquisition request is generated according to the broadcast file.
In this way, in the method for refreshing the vehicle software file, after the OTA system successfully matches with the production system to obtain the target software list, the OTA system can receive the target software file acquisition request of the EOL tool and send the target software file to the EOL tool, so that the EOL tool refreshes the target software file to the vehicle according to the refreshing information in the broadcast file sent by the production system and reports the refreshing information to the production system and the OTA system. The production system, the OTA system and the EOL tool form a complete closed loop. The introduction of the OTA system enables the vehicle software to be uniformly maintained by the OTA system, saves part of labor cost, improves the accuracy of data and improves the use experience of users.
The method further comprises, prior to the sending the target software file to the EOL tool:
a software file released by a development system of the vehicle after the development is completed is received and stored.
In this way, the OTA system can receive the software file released by the development system to match the production system to complete the software file version.
The method further comprises the steps of:
and responding to a target software list acquisition request automatically triggered by the production system at a preset station, and performing target software list matching according to the target software list acquisition request.
Therefore, the production system can automatically trigger sending a target software list acquisition request to the OTA system at a preset station to perform target software list matching so as to obtain a target software list for the subsequent software refreshing.
The responding to the target software list acquisition request automatically triggered by the production system at a preset station, and performing target software list matching according to the target software list acquisition request, including:
and matching the software file for the target vehicle hardware in the software file released by the research and development system according to the preset rule according to the production information and the vehicle configuration information in the target software file request so as to obtain the target software list.
In this manner, the OTA system can match the target software inventory based on the target software file request, and the production system receives and stores the target software inventory to generate a broadcast file for retrieving the target software file.
The method further comprises the steps of:
if the target vehicle is a first-class vehicle, if part of the hardware of the target vehicle is matched with a target software file, the successful matching with the production system is confirmed;
and if the target vehicle is a second-class vehicle, and if all hardware of the target vehicle is matched to obtain a software file, confirming successful matching with the production system.
Therefore, the OTA system needs to execute different matching rules according to the vehicle types, and obtains a vehicle target software list through matching so as to brush and write target software files for vehicles of different types.
The method for refreshing the vehicle software file is used for an EOL tool and comprises the following steps:
after a production system of a vehicle is successfully matched with an OTA system to obtain a target software list, receiving a broadcast file sent by the production system, wherein the broadcast file comprises the target software list and the refreshing information of the target software file;
according to the broadcast file, a target software file acquisition request is sent to the OTA system;
and receiving a target software file returned by the OTA system, and refreshing the target software file to the vehicle according to the refreshing information.
Therefore, the EOL tool can receive the broadcast file sent by the production system, send the target software file acquisition request, finish the refreshing process of the target software file according to the refreshing information in the broadcast file, save part of labor cost and improve the accuracy of data.
The method comprises the following steps:
and after the vehicle finishes the target software file refreshing, reporting the finishing information to the production system, and reporting the finishing information to the OTA system by the production system.
Therefore, after the target software file of the vehicle is written, the EOL tool can report the completion information to the production system and the OTA system, so that the writing process of the vehicle software file forms a complete closed-loop structure, the manpower is reduced, the accuracy of data is improved, and the user experience is improved.
The method for refreshing the vehicle software file is used for an OTA system and comprises the following steps:
responding to a received target software file acquisition request sent by a production system after successfully matching with the production system of the vehicle to obtain a target software list;
and sending a software file to the vehicle to write the software file into the vehicle, wherein the production system generates a broadcast file after successfully matching a target software list with an OTA system, the broadcast file comprises the target software list and writing information of the target software file, and the target software file acquisition request is generated according to the broadcast file.
Thus, the OTA system can directly interact with the production system and send the software file to the vehicle to finish the process of refreshing the vehicle software file. The direct data refreshing in the OTA system can lead the production process and the data sources in the market to be managed uniformly, and the accuracy of the data is improved.
The method for refreshing the vehicle software file is used for an EOL tool and comprises the following steps:
after a production system of a vehicle is successfully matched with an OTA system to obtain a target software list, receiving a broadcast file sent by the production system, wherein the broadcast file comprises the target software list and refreshing information of the target software file, and the OTA system sends the target software file to a CDN server according to the target software list;
according to the broadcast file, a target software file acquisition request is sent to the CDN server;
and receiving the target software file returned by the CDN server, and refreshing the target software file to the vehicle according to the refreshing information.
Thus, the CDN server is introduced to store the target software file for the EOL tool to directly apply for taking the target software file. The load of a server of the OTA system is reduced, and the stability of the system is improved.
The vehicle manufacturing system comprises a production system, an OTA system and an EOL tool, wherein the production system is used for generating a broadcast file after being successfully matched with the OTA system to obtain a target software list, and the broadcast file comprises the target software list and the refreshing information of the target software file;
The production system is further configured to send the broadcast file to an EOL tool;
the EOL tool is configured to send a target software file acquisition request to the OTA system according to the broadcast file;
the OTA system is used for returning the target software file to the EOL tool according to the target software file acquisition request;
the EOL tool is further configured to flush the target software file to the vehicle according to the flush information.
The vehicle manufacturing system comprises a production system and an OTA system, wherein the production system is used for generating a broadcast file after being successfully matched with the OTA system to obtain a target software list, and the broadcast file comprises the target software list and the refreshing information of the target software file;
the production system is also used for generating a target software file acquisition request according to the broadcast file and sending the target software file acquisition request to the OTA system;
the OTA system is used for sending the target software file to the vehicle according to the target software file acquisition request, and refreshing the target software file to the vehicle according to the refreshing information.
The vehicle manufacturing system comprises a production system, an OTA system, a CDN server and an EOL tool, wherein the production system is used for generating a broadcast file after successfully matching a target software list with the OTA system, and the broadcast file comprises the target software list and the refreshing information of the target software file;
The production system is further configured to send the broadcast file to an EOL tool;
the OTA system is used for sending the target software file to a CDN server according to the target software list;
the EOL tool is configured to send a target software file acquisition request to the CDN server according to the broadcast file;
the CDN server is used for returning a target software file to the EOL tool according to the target software file acquisition request;
the EOL tool is further configured to flush the target software file to the vehicle according to the flush information.
The computer readable storage medium of the present application stores a computer program that, when executed by one or more processors, implements the method of flashing a vehicle software file described above.
Additional aspects and advantages of embodiments of the 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 the application.
Drawings
The foregoing and/or additional aspects and advantages of the present application will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings, in which:
FIG. 1 is a schematic diagram of a method of flashing a vehicle software file according to the present application;
FIG. 2 is a flow chart of a method of flashing a vehicle software file of the present application;
FIG. 3 is a timing diagram of a data flow of a method for flashing a vehicle software file of the present application;
FIG. 4 is a flow chart of a method of flashing a vehicle software file of the present application;
FIG. 5 is a flow chart of a method of flashing a vehicle software file of the present application;
FIG. 6 is a timing diagram of a data flow of a method for flashing a vehicle software file of the present application;
FIG. 7 is a flow chart of a method of flashing a vehicle software file of the present application;
FIG. 8 is a flow chart of a method of flashing a vehicle software file of the present application;
FIG. 9 is a flow chart of a method of flashing a vehicle software file of the present application;
FIG. 10 is a timing diagram of a data flow of a method for flashing a vehicle software file of the present application;
FIG. 11 is a flow chart of a method of flashing a vehicle software file of the present application;
FIG. 12 is a flow chart of a method of flashing a vehicle software file of the present application;
FIG. 13 is a timing diagram of a data flow of a method for flashing a vehicle software file of the present application;
FIG. 14 is a flow chart of a method of flashing a vehicle software file of the present application;
FIG. 15 is a timing diagram of a data flow for a method of flashing a vehicle software file of the present application;
FIG. 16 is a timing diagram of a data flow for a method of flashing a vehicle software file of the present application.
Detailed Description
Embodiments of the present application are described in detail below, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to like or similar elements or elements having like or similar functions throughout. The embodiments described below by referring to the drawings are exemplary only for explaining the embodiments of the present application and are not to be construed as limiting the embodiments of the present application.
In the manufacturing process of the current vehicle, the information management of the software list in the software file refreshing process required by the vehicle hardware is manually operated, and the process is complex, not only has low accuracy, but also is unfavorable for the subsequent software updating process. Moreover, the software data management mode mainly based on manual work causes inconsistent software data management modes and data sources of production lines and markets, and the version of vehicle software cannot be uniformly managed.
Based on the problems that may be encountered as described above, referring to FIG. 1, the present 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 is configured to generate a broadcast file after successfully matching with the OTA system 102 to obtain a target software list, where the broadcast file includes the target software list and the updated information of the target software file. The production system 101 is also used to send broadcast files to EOL tools 103.EOL tool 103 is configured to send a target software file acquisition request to OTA system 102 based on the broadcast file. The OTA system 102 is configured to return the target software file to the EOL tool 103 according to the target software file acquisition request. EOL tool 103 is also used to flush the target software file to the vehicle based on the flush information.
Referring to fig. 2, the present application further provides a method for refreshing a vehicle software file, and the vehicle manufacturing method of the present application may be implemented by the vehicle manufacturing system 100 of the present application. To execute the main body as the OTA system 102, the brushing method includes:
001: in response to receiving a target software file acquisition request sent by EOL tool 103 after successful matching with production system 101 of the vehicle to obtain a target software inventory, the target software file is sent to EOL tool 103 so that EOL tool 103 may flush the target software file to the vehicle.
In some embodiments, the OTA system 102 is configured to send the target software file to the EOL tool 103 in response to receiving a target software file acquisition request sent by the EOL tool 103 after successfully matching the production system 101 of the vehicle to obtain the target software inventory, so that the EOL tool 103 may flush the target software file to the vehicle.
Specifically, in the method for refreshing a vehicle software file according to the embodiment of the present application, the production system 101 may control the opening of the vehicle manufacturing process. The OTA system 102 stores and manages software information. EOL tool 103 completes the software flashing process. An Over-the-Air (OTA) system 102 is introduced to establish a connection with an EOL (End-of-life) tool 103, and the OTA system 102 can provide a method of software flashing and packaging for the EOL tool 103.
As shown in fig. 3, after the manufacturing process of the vehicle is started on the production system 101, the production system 101 first interacts with the OTA system 102. Software information required by the production system 101 is matched with software information stored and managed in the OTA system 102 to obtain a target software list. The target software inventory provides all the software files available for the target vehicle hardware, the vehicle hardware contained in different vehicle models, and as the software version is updated, the target software inventory may change.
After the production system 101 successfully matches the OTA system 102 to obtain the target software inventory, the production system 101 generates a broadcast file and sends the broadcast file to the EOL tool 103. The broadcast file comprises a target software list and the refreshing information of the target software file.
Upon receiving the broadcast file, EOL tool 103 then sends a target software file acquisition request to OTA system 102, and interacts with OTA system 102. The OTA system 102 selects a target software file in the target software manifest according to the received target software file acquisition request and sends the selected target software file back to the EOL tool 103. Finally, EOL tool 103 may flush the received target software file to the vehicle based on the flush information in the broadcast file sent from production system 101.
The introduction of the OTA system 102 supports the acquisition request of the target software file sent by different vehicles through the EOL tool 103 and the configuration information of the vehicles by means of the closed loop structure formed by the production system 101, the OTA system 102 and the EOL tool 103, so that the latest available target software list can be screened out in real time. The vehicle software can be uniformly maintained by the OTA system 102, so that part of labor cost is saved, and meanwhile, the accuracy of data is improved. And the OTA system 102 can manage the vehicle software files to achieve 'one-vehicle-one-gear', so that the user experience is improved.
In summary, in the method for refreshing a vehicle software file provided by the present application, after the OTA system successfully matches with the production system to obtain the target software list, the method may receive a target software file acquisition request of the EOL tool, and send the target software file to the EOL tool, so that the EOL tool refreshes the target software file to the vehicle according to the refreshing information in the broadcast file sent by the production system. The production system, the OTA system and the EOL tool form a complete closed loop. The introduction of the OTA system enables the vehicle software to be uniformly maintained by the OTA system, saves part of labor cost, improves the accuracy of data and improves the use experience of users.
In certain embodiments, the vehicle manufacturing system 100 further includes a development system 104. As shown in fig. 1, the development system 104 is configured to manage all software information during the development phase, maintain software versions released by different nodes in the vehicle manufacturing process, and issue audited software versions to the OTA system 102.
Referring to fig. 4, in some embodiments, the method further comprises, prior to step 001:
002: and receiving and storing the software files released by the development system of the vehicle after the development is completed.
In some implementations, the OTA system 102 is configured to receive and store software files that are released by the vehicle's development system 104 after development is complete.
Specifically, the development system 104 manages the entire software information during the development phase and maintains software versions released by different nodes of the vehicle manufacturing process. As shown in fig. 3, the development system 104 issues an audited software version to the OTA system 102, and the OTA system 102 stores the received software version.
It will be appreciated that the OTA system 102 manages the overall software release from the development system 104 during the collaborative work of the various links of the vehicle manufacturing system 100. A user may manually configure a version of a software file in OTA system 102 that is available for use by production system 101 in making a vehicle. In particular, if no user configuration record is available in the OTA system 102, the latest version of the software file may be used by default to complete the vehicle manufacturing process.
In this way, the OTA system can receive the software file released by the development system to match the production system to complete the software file version.
Referring to fig. 5, in some embodiments, the method further comprises:
003: and responding to a target software list acquisition request automatically triggered by the production system at a preset station, and performing target software list matching according to the target software list acquisition request.
In some embodiments, the OTA system 102 is configured to perform target software inventory matching according to a target software inventory acquisition request in response to a target software inventory acquisition request automatically triggered by the production system 101 at a preset workstation.
Specifically, after the OTA system 102 receives the software file released by the development system, the user may set a trigger instruction at a preset station in the production system 101, as shown in fig. 3, and send a target software inventory acquisition request to the OTA system 102. The target software inventory acquisition request is used to acquire information including software required at the time of vehicle manufacture, such as acquisition of production information, vehicle configuration information, and the like. The preset station needs to ensure that certain conditions are met, that is, after the vehicle id is generated during the vehicle manufacturing process, until the production line reaches the EOL tool 103, so that the production system 101 has enough time to use the target software inventory provided by the OTA system 102 to produce the broadcast file.
The production system 101 obtains the interactive process of the target software inventory from the OTA system 102, as shown in fig. 6. Setting a target software list acquisition request at a preset station of the production system 101, and triggering the target software list acquisition request to request the OTA system 102 for matching when the production line runs to the preset station, so as to finally obtain a target software list. The matching process is performed according to certain requirements, namely, the software information on the target software list is matched with the hardware information in the vehicle manufacturing process.
Therefore, the production system can automatically trigger sending a target software list acquisition request to the OTA system at a preset station to perform target software list matching so as to obtain a target software list for the subsequent software refreshing.
Particularly, all interaction processes of the method for refreshing the vehicle software file, including the interaction process between the production system 101 and the OTA system 102, are completed in a cloud-cloud docking mode, a protocol self-adaptive framework can be built, protocols such as HTTPS are used as interaction protocols, and interaction data are transmitted through an API interface (Application Programming Interface ).
Referring to fig. 7, in some embodiments, step 03 includes:
0031: and matching the software file for the target vehicle hardware in the software file released by the research and development system according to the preset rule to obtain a target software list according to the production information and the vehicle configuration information in the target software file request.
In some embodiments, the OTA system 102 is configured to match software files for the target vehicle hardware in the software files released by the development system 104 according to the preset rules to obtain the target software inventory according to the production information and the vehicle configuration information in the target software file request.
Specifically, in the target software file request sent by the production system 101 to the OTA system 102, there are production information of the software and vehicle configuration information. The production information comprises a vehicle frame number, a material number, an order number, a vehicle welding plan starting time and the like. The vehicle configuration information is hardware information of loading, and comprises a part assembly number, a part number and the like. The production system 101 encapsulates the information into a JSON message (JavaScript Object Notation) in a lightweight data exchange format, i.e. a target software file request, and sends the JSON message to the OTA system 102.
The OTA system 102 matches the vehicle hardware with the software files released by the development system 104, where the matching rules include: the welding plan starting time of the vehicle is more than or equal to the release time of the software; the part number in the vehicle loading hardware information is consistent with the hardware number corresponding to the software; the configuration information of the loading part number of the vehicle is consistent with the configuration information of the software, and the like. The matching rule is satisfied at the same time, and the hardware and the software can be considered to pass through the matching.
After the matching is completed, the software files available for the target vehicle hardware form a target software inventory. The target software list comprises production information and vehicle configuration information of the software, wherein the production information comprises a vehicle frame number, a material number, a list number, a vehicle welding plan starting time and the like. The vehicle configuration information is the hardware information of the loading vehicle, and comprises a part assembly number, a part number, information of an electronic control unit corresponding to the hardware, a software part number, a software version number, a storage address of a software file and the like. Finally, the OTA system 102 needs to encapsulate the above information into JSON messages, as shown in fig. 6, and combine to generate a target software manifest.
In addition, fig. 6 also shows that the target software list of the vehicle is returned to the production system 101 through HTTPS or other communication protocol, so that the production system 101 stores the target software list and generates a broadcast file for acquiring the target software file.
In this manner, the OTA system can match the target software inventory based on the target software file request, and the production system receives and stores the target software inventory to generate a broadcast file for retrieving the target software file.
Referring to fig. 8, in some embodiments, step 03 includes:
0032: if the target vehicle is a first type vehicle, if part of hardware of the target vehicle is matched with the target software file, the successful matching with the production system is confirmed;
0033: if the target vehicle is a second-class vehicle, the successful matching with the production system is confirmed under the condition that all hardware of the target vehicle is matched to obtain a software file.
In some embodiments, the OTA system 102 is configured to confirm successful matching with the production system 101 if the target vehicle is a first type of vehicle and if part of the hardware of the target vehicle matches the target software file, and confirm successful matching with the production system 101 if all of the hardware of the target vehicle matches the software file if the target vehicle is a second type of vehicle.
Specifically, the OTA system 102 can match all software information of the vehicle loading based on the production system 101 hardware information and the vehicle configuration information.
For different vehicle types of the target vehicle to be matched, the OTA system 102 may adopt different matching rules for matching. For non-mass-produced first class vehicles, i.e., pilot vehicles, the OTA system 102 performs fuzzy matching. In the fuzzy matching process, when one piece of hardware of the target vehicle is matched with the software in the target software file, the hardware is considered to pass through the matching; if the hardware is not matched with the software, skipping the hardware, and continuing to match the subsequent hardware. The matching process can not be finished when all hardware matching processes are finished because a certain hardware of the target vehicle cannot match software in the target software file, so that the successful matching with the production system 101 can be judged, and a vehicle target software list can be obtained.
For the second class of vehicles, i.e., mass production vehicles, the OTA system 102 requires precise matching. Accurate matching requires that all hardware of the target vehicle be matched to the software in the target software file before the match can be considered as passing. In the accurate matching process, if one piece of hardware is not matched with the software, the matching process is terminated, and a vehicle target software list cannot be acquired.
Therefore, the OTA system needs to execute different matching rules according to the vehicle types, and obtains a vehicle target software list through matching so as to brush and write target software files for vehicles of different types.
Referring to fig. 9, to execute the EOL tool 103, the method for refreshing a vehicle software file of the present application includes:
004: after the production system of the vehicle is successfully matched with the OTA system to obtain a target software list, receiving a broadcast file sent by the production system 101;
005: according to the broadcast file, sending a target software file acquisition request to an OTA system;
006: and receiving the target software file returned by the OTA system, and refreshing the target software file to the vehicle according to the refreshing information.
In some embodiments, the EOL tool 103 is configured to receive a broadcast file sent 101 by the production system 101 after the production system 101 of the vehicle successfully matches the OTA system 102 to obtain a target software list, send a target software file acquisition request to the OTA system 102 according to the broadcast file, receive a target software file returned by the OTA system 102, and brush the target software file to the vehicle according to the brushing information.
The method for refreshing a vehicle software file according to the present embodiment is basically identical to the method for refreshing a vehicle software file using the OTA system 102 as an execution subject, and the principle is basically identical, and the description of the relevant parts in the above embodiment is omitted here.
In particular, the target software file acquisition request may be in URL (uniform resource locator) format, as shown in fig. 10, showing the data transmission process of the EOL tool 103 and the OTA system 102, and the EOL tool 103 completes the downloading and storing of the software file.
Therefore, the EOL tool can receive the broadcast file sent by the production system, send the target software file acquisition request, finish the refreshing process of the target software file according to the refreshing information in the broadcast file, save part of labor cost and improve the accuracy of data.
Referring to fig. 11, in some embodiments, the method includes:
007: after the vehicle finishes the target software file writing, the completion information is reported to the production system 101, and the production system 101 reports the completion information to the OTA system 102.
In some embodiments, EOL tool 103 is configured to report completion information to production system 101 after the vehicle completes the target software file flush, and production system 101 is configured to report completion information to OTA system 102.
Specifically, as shown in FIG. 3, after the EOL tool 103 completes the vehicle's target software file flashing, completion information may be reported to the production system 101. After receiving the completion information, the production system 101 reports the completion information to the OTA system 102. The complete closed loop structure of the "production system-OTA system-EOL tool" as shown in fig. 1 is finally formed.
Therefore, after the target software file of the vehicle is written, the EOL tool can report the completion information to the production system and the OTA system, so that the writing process of the vehicle software file forms a complete closed-loop structure, the manpower is reduced, the accuracy of data is improved, and the user experience is improved.
It can be understood that the method for brushing the EOL tool 103 includes all the embodiments of the method for brushing the OTA system 102, and the corresponding parts will be described with reference to the foregoing embodiments, which are not repeated herein.
The present application also provides a vehicle manufacturing system 200. Specifically, vehicle manufacturing system 200 includes a production system 201 and an OTA system 202. The production system 201 is configured to generate a broadcast file after successfully matching with the OTA system 202 to obtain a target software list, generate a target software file acquisition request according to the broadcast file, and send the target software file acquisition request to the OTA system 202. The OTA system 202 is configured to send the target software file to the vehicle according to the target software file acquisition request, and to rewrite the target software file to the vehicle according to the rewrite information. The broadcast file comprises a target software list and the refreshing information of the target software file, and the target software file acquisition request is generated according to the broadcast file.
Referring to fig. 12, the present application further provides a method for refreshing a vehicle software file, and the vehicle manufacturing method of the present application may be implemented by the vehicle manufacturing system 200 of the present application. To execute the main body as the OTA system 202, the brushing method includes:
011: responding to a received target software file acquisition request sent by a production system after successfully matching with the production system of the vehicle to obtain a target software list;
012: the software file is sent to the vehicle to flush the software file to the vehicle.
In some embodiments, the OTA system 202 is configured to respond to a received target software file acquisition request sent by the production system 201 after successful matching with the production system 201 of the vehicle to obtain a target software inventory, and to send a software file to the vehicle to flush the software file to the vehicle.
Specifically, the method for writing a vehicle software file according to the present embodiment is substantially identical to the method for writing a vehicle software file based on the vehicle manufacturing system 100, in which the OTA system 102 is the main implementation, and the production system 201 and the OTA system 202 in the vehicle manufacturing system 200 are substantially identical to the corresponding structures in the vehicle manufacturing system 100, and specific functions are not repeated.
In the vehicle manufacturing system 100 based method of painting, the EOL tool 103 still uses a conventional inspection tool, i.e., the vehicle needs to complete the production process and exit the production line after the painting of the vehicle software file is completed. In order to improve the efficiency of vehicle software file refreshing, in the vehicle software file refreshing method of the present embodiment, the vehicle software file refreshing may be completed by using "OTA Client" in the OTA system of the vehicle instead of EOL tool. The data sources in the production process and the market are uniformly managed, the technical scheme of software refreshing is uniformly realized, and the accuracy of the data is improved.
As shown in fig. 13, in the process of actually performing the vehicle software file refreshing by the vehicle manufacturing system 200, when the OTA system 202 receives the target software file acquisition request sent by the production system 201, software file information required by the vehicle hardware in the target software list is refreshed to the vehicle by the "OTA Client".
Thus, the OTA system can directly interact with the production system and send the software file to the vehicle to finish the process of refreshing the vehicle software file. The direct data refreshing in the OTA system can lead the production process and the data sources in the market to be managed uniformly, and the accuracy of the data is improved.
The present application also provides a vehicle manufacturing system 300. Specifically, 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 is configured to generate a broadcast file after successfully matching with the OTA system 302 to obtain a target software manifest, and send the broadcast file to the EOL tool 304. The OTA system 302 is configured to send the target software file to the CDN server 303 according to the target software manifest. The CDN server 303 is configured to return the target software file to the EOL tool 304 according to the target software file acquisition request. The EOL tool 304 sends a target software file acquisition request to the CDN server 303 according to the broadcast file, and rewrites the target software file to the vehicle according to the brush information. The broadcast file comprises a target software list and the refreshing information of the target software file.
Referring to fig. 14, the present application further provides a method for refreshing a vehicle software file, and the vehicle manufacturing method of the present application may be implemented by the vehicle manufacturing system 300 of the present application. To execute the main body as the OTA system 302, the brushing method includes:
021: after a production system of a vehicle is successfully matched with an OTA system to obtain a target software list, receiving a broadcast file sent by the production system;
022: according to the broadcast file, a target software file acquisition request is sent to a CDN server;
023: and receiving the target software file returned by the CDN server, and refreshing the target software file to the vehicle according to the refreshing information.
In some embodiments, the OTA system 302 is configured to receive a broadcast file sent by the production system 301 after the production system 301 of the vehicle and the OTA system 302 are successfully matched to obtain a target software list, send a target software file obtaining request to the CDN server 303 according to the broadcast file, receive a target software file returned by the CDN server 303, and brush the target software file to the vehicle according to the brushing information.
Specifically, the method for writing a vehicle software file according to the present embodiment is substantially identical to the method for writing a vehicle software file based on the vehicle manufacturing system 100, which mainly includes the OTA system 102, and the production system 201, the OTA system 302, and the EOL tool 304 in the vehicle manufacturing system 200 are substantially identical to the corresponding structures in the vehicle manufacturing system 100, and specific functions are not repeated.
In the vehicle manufacturing system 100 based method of refreshing, there is a closed loop formed by the "production system 101-OTA system 102-EOL tool 103", where the OTA system 102 needs to manage all software versions of each stage of software file refreshing, which is more labor intensive. In order to reduce the load of the OTA system, in the vehicle manufacturing system 300, a CDN server 303 (Content Delivery Network ) is introduced, as shown in fig. 15, to provide a space for storing software files for the production system 301. In addition, 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, where the push result information may be, for example, information that the CDN server 303 has successfully or failed to push the target software file. The OTA system 302 does not need to store the target software file, reducing the load.
As shown in fig. 16, in the process of actually refreshing a vehicle software file by the vehicle manufacturing system 300, the production system 301 successfully matches with the OTA system 302, and after obtaining a target software list, the OTA system 302 sends the target software file to the CDN server 303 in advance according to the target software list. At this time, the EOL tool 304 may send the target software file acquisition request to the CDN server 303 without sending the target software file acquisition request to the OTA system 302, directly download the software file from the CDN server 303, and finally brush the target software file to the vehicle.
Thus, the CDN server is introduced to store the target software file for the EOL tool to directly apply for taking the target software file. The load of a server of the OTA system is reduced, and the stability of the system is improved.
In addition, in addition to the HTTPS protocol, the interactive protocol when the production system requests the target software inventory from the OTA system may also use the MQTT protocol, HTTP protocol, MQ message queues, etc.
When the production system requests the content of the target software inventory from the OTA system, the information transfer process may use XML files, text files (TXT), etc. instead of JSON message formats.
The present application also provides a computer readable storage medium storing a computer program which, when executed by one or more processors, implements the above-described method of flushing vehicle software files.
In the description of the present specification, reference to the terms "above," "specifically," "particularly," "further," and the like, means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present application. In the present specification, schematic representations of the above terms are not intended to refer to the same embodiments or examples. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and further implementations are included within the scope of the preferred embodiment of the present application in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the embodiments of the present application.
While embodiments of the present application have been shown and described above, it will be understood that the above embodiments are illustrative and not to be construed as limiting the present application, and that variations, modifications, alternatives, and variations may be made to the above embodiments by one of ordinary skill in the art within the scope of the present application.
Claims (13)
1. A method for flashing a vehicle software file for use in an OTA system, the method comprising:
and responding to a target software file acquisition request sent by a received EOL tool after successfully matching with a production system of a vehicle to obtain a target software list, and sending a target software file to the EOL tool so that the EOL tool can write the target software file into the vehicle, wherein the production system generates a broadcast file after successfully matching with an OTA system with the target software list, the broadcast file comprises the target software list and writing information of the target software file, and the target software file acquisition request is generated according to the broadcast file.
2. The method of claim 1, further comprising, prior to the sending the target software file to the EOL tool:
a software file released by a development system of the vehicle after the development is completed is received and stored.
3. The method according to claim 1, wherein the method further comprises:
and responding to a target software list acquisition request automatically triggered by the production system at a preset station, and performing target software list matching according to the target software list acquisition request.
4. A method according to claim 3, wherein said performing target software inventory matching in response to a target software inventory acquisition request automatically triggered by the production system at a preset workstation, according to the target software inventory acquisition request, comprises:
and matching the software file for the target vehicle hardware in the software file released by the research and development system according to the preset rule according to the production information and the vehicle configuration information in the target software file request so as to obtain the target software list.
5. The method according to claim 4, wherein the method further comprises:
if the target vehicle is a first-class vehicle, if part of the hardware of the target vehicle is matched with a target software file, the successful matching with the production system is confirmed;
And if the target vehicle is a second-class vehicle, and if all hardware of the target vehicle is matched to obtain a software file, confirming successful matching with the production system.
6. A method for flashing a vehicle software file for an EOL tool, comprising:
after a production system of a vehicle is successfully matched with an OTA system to obtain a target software list, receiving a broadcast file sent by the production system, wherein the broadcast file comprises the target software list and the refreshing information of the target software file;
according to the broadcast file, a target software file acquisition request is sent to the OTA system;
and receiving a target software file returned by the OTA system, and refreshing the target software file to the vehicle according to the refreshing information.
7. The method according to claim 6, characterized in that the method comprises:
and after the vehicle finishes the target software file refreshing, reporting the finishing information to the production system, and reporting the finishing information to the OTA system by the production system.
8. A method for flashing a vehicle software file for an OTA system, comprising:
in response to receiving a target software file acquisition request sent by the production system after successfully matching the production system of the vehicle to obtain a target software inventory,
And sending a software file to the vehicle to write the software file into the vehicle, wherein the production system generates a broadcast file after successfully matching a target software list with an OTA system, the broadcast file comprises the target software list and writing information of the target software file, and the target software file acquisition request is generated according to the broadcast file.
9. A method for flashing a vehicle software file for an EOL tool, comprising:
after a production system of a vehicle is successfully matched with an OTA system to obtain a target software list, receiving a broadcast file sent by the production system, wherein the broadcast file comprises the target software list and refreshing information of the target software file, and the OTA system sends the target software file to a CDN server according to the target software list;
according to the broadcast file, a target software file acquisition request is sent to the CDN server;
and receiving the target software file returned by the CDN server, and refreshing the target software file to the vehicle according to the refreshing information.
10. The vehicle manufacturing system is characterized by comprising a production system, an OTA system and an EOL tool, wherein the production system is used for generating a broadcast file after being successfully matched with the OTA system to obtain a target software list, and the broadcast file comprises the target software list and the refreshing information of the target software file;
The production system is further configured to send the broadcast file to an EOL tool;
the EOL tool is configured to send a target software file acquisition request to the OTA system according to the broadcast file;
the OTA system is used for returning the target software file to the EOL tool according to the target software file acquisition request;
the EOL tool is further configured to flush the target software file to the vehicle according to the flush information.
11. The vehicle manufacturing system is characterized by comprising a production system and an OTA system, wherein the production system is used for generating a broadcast file after being successfully matched with the OTA system to obtain a target software list, and the broadcast file comprises the target software list and the refreshing information of the target software file;
the production system is also used for generating a target software file acquisition request according to the broadcast file and sending the target software file acquisition request to the OTA system;
the OTA system is used for sending the target software file to the vehicle according to the target software file acquisition request, and refreshing the target software file to the vehicle according to the refreshing information.
12. The vehicle manufacturing system is characterized by comprising a production system, an OTA system, a CDN server and an EOL tool, wherein the production system is used for generating a broadcast file after successfully matching a target software list with the OTA system, and the broadcast file comprises the target software list and the refreshing information of the target software file;
the production system is further configured to send the broadcast file to an EOL tool;
the OTA system is used for sending the target software file to a CDN server according to the target software list;
the EOL tool is configured to send a target software file acquisition request to the CDN server according to the broadcast file;
the CDN server is used for returning the target software file to the EOL tool according to the target software file acquisition request;
the EOL tool is further configured to flush the target software file to the vehicle according to the flush information.
13. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program which, when executed by one or more processors, implements the method according to any of claims 1-9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310199475.7A CN116156485A (en) | 2023-02-24 | 2023-02-24 | Vehicle software file refreshing method, vehicle manufacturing system and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310199475.7A CN116156485A (en) | 2023-02-24 | 2023-02-24 | Vehicle software file refreshing method, vehicle manufacturing system and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116156485A true CN116156485A (en) | 2023-05-23 |
Family
ID=86356252
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310199475.7A Pending CN116156485A (en) | 2023-02-24 | 2023-02-24 | Vehicle software file refreshing method, vehicle manufacturing system and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116156485A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117215603A (en) * | 2023-11-08 | 2023-12-12 | 宁德时代新能源科技股份有限公司 | Software flashing method and device of domain controller, computer equipment and storage medium |
-
2023
- 2023-02-24 CN CN202310199475.7A patent/CN116156485A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117215603A (en) * | 2023-11-08 | 2023-12-12 | 宁德时代新能源科技股份有限公司 | Software flashing method and device of domain controller, computer equipment and storage medium |
| CN117215603B (en) * | 2023-11-08 | 2024-04-02 | 宁德时代新能源科技股份有限公司 | Software flashing method and device of domain controller, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110765099B (en) | Service construction method and device and computer equipment | |
| CN109842656B (en) | Intelligent compatible multi-protocol Internet of vehicles service method and Internet of vehicles gateway system | |
| CN102006334B (en) | Method, system and device for installing software component | |
| KR102223260B1 (en) | Resource acquisition method and related device | |
| CN116156485A (en) | Vehicle software file refreshing method, vehicle manufacturing system and storage medium | |
| KR101528210B1 (en) | Software downloading method and device | |
| US20080301640A1 (en) | Method and system for allocating id of software component | |
| CN109669703A (en) | Micro services information configuring methods, device, computer equipment and storage medium | |
| US8788710B2 (en) | Managed object member architecture for software defined radio | |
| CN111984271B (en) | Block chain application program processing method and device and block chain application system | |
| CN110659261A (en) | Data mining model publishing method, model and model service management method | |
| CN115543315A (en) | Method and system for controlling page interaction by using data model | |
| CN111104133A (en) | Configuration parameter updating system, method and storage medium | |
| CN115858108A (en) | Cloud edge coordination system constructed based on Kubeedge edge computing framework | |
| US8332462B2 (en) | Correlating groups of application systems | |
| CN110457024B (en) | VUE-based front-end request and update data plug-in iwebData implementation method | |
| CN112860308A (en) | Configuration method of interface definition, service processing method, server and storage medium | |
| WO2022012127A1 (en) | Task execution method and device, storage medium and electronic device | |
| CN115328520A (en) | Remote upgrading method and device, electronic equipment and storage medium | |
| CN115567388A (en) | Method, system, device and storage medium for automatically updating network slice configuration | |
| CN108052380B (en) | Business function docking method and device, computer equipment and storage medium | |
| CN102244619B (en) | Equipment management method, gateway and server | |
| CN115242871B (en) | Service method and device of business gateway, storage medium and electronic equipment | |
| CN116095072A (en) | Communication matrix management method and device, electronic equipment and storage medium | |
| CN116805974A (en) | Media asset data distribution method and device, storage medium and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |