CN110806894A - Automobile part software version management method, equipment, storage medium and device - Google Patents
Automobile part software version management method, equipment, storage medium and device Download PDFInfo
- Publication number
- CN110806894A CN110806894A CN201911057973.8A CN201911057973A CN110806894A CN 110806894 A CN110806894 A CN 110806894A CN 201911057973 A CN201911057973 A CN 201911057973A CN 110806894 A CN110806894 A CN 110806894A
- Authority
- CN
- China
- Prior art keywords
- automobile
- software version
- version
- ecu
- detected
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- 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
Abstract
The invention discloses a method, a device, a storage medium and a device for managing software versions of automobile parts, wherein the method comprises the following steps: the method comprises the steps of receiving an updating request sent by an automobile client, extracting a vehicle identification number of an automobile from the updating request, determining an Electronic Control Unit (ECU) part corresponding to the automobile according to the vehicle identification number, taking the ECU part as a part to be detected, obtaining a part number, a hardware version and a software version to be detected of the part to be detected, determining a cloud software version and a cloud data packet corresponding to the part to be detected according to the part number and the hardware version, comparing the software version to be detected with the cloud software version, and if the software version to be detected is different from the cloud software version, sending the cloud data packet to the automobile client, so that the software version of the automobile part is uniformly managed through a part management system, and the influence of human factors on upgrading work is avoided.
Description
Technical Field
The invention relates to the technical field of automobile software versions, in particular to a method, equipment, a storage medium and a device for managing automobile part software versions.
Background
With the development trend of vehicle electrification, intellectualization and networking, the proportion of electronic products on the whole vehicle is increased year by year. Meanwhile, in the quality problem of the finished automobile after sale, the software problem becomes an important influence factor, and the quality problem is increased year by year. Compared with a solution for replacing parts of hardware problems of the parts, the software problems have the advantages of repairability, no need of replacing parts, quick updating and the like. At present, the refreshing mode in the after-sale process of production mainly comprises the following modes, namely the refreshing of equipment such as Bluetooth and EOL through CAN refreshing, the refreshing of a USB flash disk through USB and the refreshing of OTA through a vehicle-mounted terminal.
No matter the equipment such as bluetooth refreshes, USB flash disk refreshes or remote refreshes, software refreshing work is upgrading work carried out by self-loading software by designers, and the influence of human factors is more. The problems that the software versions of all parts of the vehicle are in a non-management state, the software upgrading is carried out without the approval and confirmation of the refreshing software, the vehicle refreshing process is missed to be refreshed, the vehicle refreshing process is mistakenly refreshed and the like exist. Therefore, how to uniformly manage the software versions of the automobile parts through the part management system is an urgent technical problem to be solved.
The above is only for the purpose of assisting understanding of the technical aspects of the present invention, and does not represent an admission that the above is prior art.
Disclosure of Invention
The invention mainly aims to provide a method, equipment, a storage medium and a device for managing automobile part software versions, and aims to solve the technical problem of how to uniformly manage the automobile part software versions in the prior art.
In order to achieve the above object, the present invention provides a method for managing software versions of automobile parts, comprising the steps of:
receiving an updating request sent by an automobile client, and extracting a vehicle identification number of an automobile from the updating request;
determining Electronic Control Unit (ECU) parts corresponding to the automobile according to the vehicle identification number, and taking the ECU parts as parts to be detected;
acquiring a part number, a hardware version and a software version of the part to be detected;
determining a cloud software version and a cloud data packet corresponding to the part to be detected according to the part number and the hardware version;
comparing the software version to be detected with the cloud software version;
and if the data packets are different, the cloud data packet is sent to the automobile client.
Preferably, before the step of receiving an update request sent by an automobile client and extracting the vehicle identification number of the automobile from the update request, the method for managing the version of the automobile part software further includes:
obtaining samples of various vehicle types;
traversing the vehicle type sample, and taking the traversed vehicle type sample as a current vehicle type sample;
acquiring an ECU part of a current vehicle model sample, and taking the ECU part sample as an ECU part corresponding to the current vehicle model sample;
after traversing the vehicle model sample, establishing a preset first mapping relation table according to the corresponding relation between the vehicle model sample and the ECU part sample;
correspondingly, the determining the electronic control unit ECU part corresponding to the automobile according to the vehicle identification number, and using the ECU part as the part to be detected includes:
and determining the Electronic Control Unit (ECU) parts corresponding to the automobile through the preset first mapping relation table according to the vehicle identification number, and taking the ECU parts as the parts to be detected.
Preferably, the determining, according to the vehicle identification number, an electronic control unit ECU part corresponding to the automobile through the preset first mapping table, and using the ECU part as a part to be detected includes:
determining a vehicle type to be matched according to the vehicle identification number, and matching the vehicle type to be matched with a vehicle type sample in a preset first mapping relation table;
and if the matching is successful, taking the ECU part sample corresponding to the successfully matched vehicle model sample as the part to be detected.
Preferably, after the ECU part sample of the current model sample is obtained and the ECU part sample is used as the ECU part corresponding to the current model sample, the method for managing the software version of the automobile part further includes:
acquiring a preset part number, a preset hardware version, a software version and a data packet of an ECU part corresponding to a current vehicle model sample;
taking the preset hardware version as a part number corresponding to a preset part number, taking the software version as a software version corresponding to the preset hardware version, and taking the data packet as a data packet corresponding to the preset hardware version;
after traversing the vehicle model sample, establishing a preset second mapping relation table according to the corresponding relation;
correspondingly, the step of determining the cloud software version and the cloud data packet corresponding to the part to be detected according to the part number and the hardware version specifically includes:
and determining a cloud software version and a cloud data packet corresponding to the part to be detected according to the part number and the hardware version through a preset second mapping relation table.
Preferably, the determining, according to the part number and the hardware version, a cloud software version and a cloud data packet corresponding to the part to be detected through a preset second mapping relation table includes:
matching the part number with a preset part number in a preset second mapping relation table, and if the matching is successful, acquiring a preset hardware version corresponding to the successfully matched preset part number;
and matching the hardware version with a preset hardware version, if the matching is successful, taking a software version corresponding to the successfully matched preset hardware version as a cloud software version corresponding to the part to be detected, and taking a data packet corresponding to the successfully matched preset hardware version as a cloud data packet corresponding to the part to be detected.
Preferably, after determining the cloud software version and the cloud data packet corresponding to the part to be detected according to the part number and the hardware version, the method for managing the software version of the automobile part further includes:
acquiring a new software version and a new data packet corresponding to the part number and the hardware version uploaded by a management terminal;
and updating the cloud software version and the cloud data packet according to the new software version and the new data packet.
Preferably, if the version number of the software version of the automobile part is different, after the cloud data packet is sent to the automobile client, the method for managing the software version of the automobile part further includes:
acquiring a software version number of a part to be detected;
verifying whether the cloud software version and the cloud data packet are compatible with the software version to be detected;
and if the software version numbers are not compatible, adding one to the software version number of the part to be detected, and sending the part to be detected to the automobile client.
In addition, in order to achieve the above object, the present invention further provides an automobile part software version management device, where the automobile part software version management device includes a memory, a processor, and an automobile part software version management program stored in the memory and operable on the processor, and the automobile part software version management program is configured to implement the steps of the automobile part software version management method.
In addition, in order to achieve the above object, the present invention further provides a storage medium, wherein the storage medium stores an automobile part software version management program, and the automobile part software version management program, when executed by a processor, implements the steps of the automobile part software version management method as described above.
In addition, in order to achieve the above object, the present invention further provides an automobile part software version management device, including: the device comprises a receiving module, an ECU part confirming module, an ECU part information acquiring module, an update package downloading module, a comparing module and an updating module;
the receiving module is used for receiving an updating request sent by an automobile client and extracting the automobile identification number of the automobile from the updating request;
the ECU part confirmation module is used for determining the electronic control unit ECU parts corresponding to the automobile according to the vehicle identification number and taking the ECU parts as parts to be detected;
the ECU part information acquisition module is used for acquiring the part number, the hardware version and the software version of the part to be detected;
the updating package downloading module is used for determining a cloud software version and a cloud data package corresponding to the part to be detected according to the part number and the hardware version;
the comparison module is used for comparing the to-be-detected software version with the cloud software version;
and the updating module is used for sending the cloud data packet to the automobile client if the cloud data packet is different from the automobile client.
In the invention, an updating request sent by an automobile client is received, the vehicle identification number of an automobile is extracted from the updating request, determining the Electronic Control Unit (ECU) parts corresponding to the automobile according to the vehicle identification number, and the ECU part is used as a part to be detected, the part number, the hardware version and the software version of the part to be detected are obtained, determining a cloud software version and a cloud data packet corresponding to the part to be detected according to the part number and the hardware version, comparing the software version to be detected with the cloud software version, if different, and sending the cloud data packet to the automobile client, and performing unified updating management on each ECU part of the vehicle through a part management system, so that the influence of human factors on upgrading work is avoided, and the management of ECU part software versions of the vehicle in the after-sales production process is realized.
Drawings
FIG. 1 is a schematic structural diagram of an automobile part software version management device of a hardware operating environment according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a method for managing software versions of automotive components according to a first embodiment of the present invention;
FIG. 3 is a flowchart illustrating a second embodiment of a method for managing software versions of automotive components according to the present invention;
FIG. 4 is a flowchart illustrating a third exemplary embodiment of a method for managing software versions of automotive components according to the present invention;
fig. 5 is a block diagram of the first embodiment of the software version management device for automobile parts according to the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Referring to fig. 1, fig. 1 is a schematic structural diagram of an automobile part software version management device in a hardware operating environment according to an embodiment of the present invention.
As shown in fig. 1, the automobile part software version management apparatus may include: a processor 1001, such as a Central Processing Unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display screen (Display), and the optional user interface 1003 may further include a standard wired interface and a wireless interface, and the wired interface for the user interface 1003 may be a USB interface in the present invention. The network interface 1004 may optionally include a standard wired interface, a WIreless interface (e.g., a WIreless-FIdelity (WI-FI) interface). The Memory 1005 may be a Random Access Memory (RAM) Memory or a Non-volatile Memory (NVM), such as a disk Memory. The memory 1005 may alternatively be a storage device separate from the processor 1001.
Those skilled in the art will appreciate that the configuration shown in fig. 1 does not constitute a limitation of the automotive component software version management apparatus and may include more or fewer components than those shown, or some components in combination, or a different arrangement of components.
As shown in FIG. 1, memory 1005, identified as one type of computer storage medium, may include an operating system, a network communication module, a user interface module, and an automobile parts software version management program.
In the software version management device for automobile parts shown in fig. 1, the network interface 1004 is mainly used for connecting a background server and performing data communication with the background server; the user interface 1003 is mainly used for connecting user equipment; the automobile part software version management device calls an automobile part software version management program stored in the memory 1005 through the processor 1001 and executes the automobile part software version management method provided by the embodiment of the invention.
Based on the hardware structure, the embodiment of the software version management method for the automobile parts is provided.
Referring to fig. 2, fig. 2 is a schematic flow chart of a first embodiment of the method for managing the software version of the automobile part, and provides the first embodiment of the method for managing the software version of the automobile part.
In a first embodiment, the method for managing the software version of the automobile part comprises the following steps:
step S10: and receiving an updating request sent by the automobile client, and extracting the vehicle identification number of the automobile from the updating request.
It should be understood that the execution subject of the embodiment is the component data management system installed in the automobile component software version management device, wherein the automobile component software version management device may be an electronic device such as a personal computer or a server.
In this embodiment, the method for receiving an update request sent by an automobile client and extracting a vehicle identification number of an automobile from the update request includes: and the vehicle box TBOX receives the vehicle identification VIN code in the finished vehicle test EOL system, and inserts the VIN code into Bluetooth equipment, reads EOL equipment and the like.
Step S20: and determining the Electronic Control Unit (ECU) parts corresponding to the automobile according to the vehicle identification number, and taking the ECU parts as the parts to be detected.
It can be understood that the preset first mapping relation table is a relation table obtained by counting an ECU part sample of an existing vehicle model sample, and the relation table includes information such as a part number, manufacturer information, a hardware number, a hardware version, a software number, and a software version of the ECU part.
Step S30: acquiring the part number, the hardware version and the software version of the part to be detected.
Note that the part number, the hardware version, and the software version to be detected of the ECU part installed in the automobile are generally acquired by TBOX. In an automobile system, each ECU part corresponds to a part number and a hardware version, and the type of the ECU part can be determined by acquiring the part number and the hardware version of the part to be detected, so that a part data management system determines the latest version of the ECU part.
Step S40: and determining a cloud software version and a cloud data packet corresponding to the part to be detected according to the part number and the hardware version.
It should be understood that, the latest software version is determined according to the part number and the hardware version, and the correspondence between the part number and the hardware version and the cloud software version and the cloud data package can be established in advance, wherein the cloud software version and the cloud data package are the latest software version of the ECU part designed by a software manager according to the design-trial-production-mass-production process.
Step S50: and comparing the software version to be detected with the cloud software version.
It should be noted that, comparing the detection software version with the cloud software version may compare differences between the two software versions, where the differences include: version upgrading identification, version distinguishing positions, contents needing to be modified, ending identification and the like.
Step S60: and if the data packets are different, the cloud data packet is sent to the automobile client.
It should be understood that if the same, the version of the software to be detected does not need to be updated. The part data management system can log the whole verification process and store the log in the system. If not, the cloud software version and the cloud data packet need to be sent to the automobile client, the automobile client updates according to the cloud software version and the cloud data packet, after updating is completed, further verification is needed, whether the updated software version is the cloud software version or not is achieved, updating failure is prevented, automobile use is threatened, updating data can be counted after updating, and the updating data comprise task statistics, part version statistics, vehicle updating statistics, part updating statistics, updating failure reason statistics and the like.
In the first embodiment, an updating request sent by an automobile client is received, the vehicle identification number of an automobile is extracted from the updating request, determining the Electronic Control Unit (ECU) parts corresponding to the automobile according to the vehicle identification number, and the ECU part is used as a part to be detected, the part number, the hardware version and the software version of the part to be detected are obtained, determining a cloud software version and a cloud data packet corresponding to the part to be detected according to the part number and the hardware version, comparing the software version to be detected with the cloud software version, if different, and sending the cloud data packet to the automobile client, and performing unified updating management on each ECU part of the vehicle through the part data management system, so that the influence of human factors on the upgrading work is avoided, and the unified management and upgrading of the ECU part software version of the vehicle in the after-sales production process are realized.
Referring to fig. 3, fig. 3 is a flowchart illustrating a second embodiment of the method for managing software versions of automotive components according to the present invention, and the second embodiment of the method for managing software versions of automotive components according to the present invention is proposed based on the first embodiment illustrated in fig. 2.
In the second embodiment, before the step S10, the method further includes:
step S01: and obtaining a plurality of vehicle model samples.
It can be understood that various automobiles exist in real life, different automobile models have different ECU parts, and when the corresponding relation between the automobile model samples and the ECU parts is established, the automobile model samples need to be obtained as much as possible.
Step S02: traversing the vehicle type sample, and taking the traversed vehicle type sample as a current vehicle type sample.
It should be understood that, when establishing the correspondence between the vehicle model samples and the ECU components, the correspondence between the vehicle model samples and the ECU components needs to be established one by one, and therefore, the vehicle model samples need to be traversed, and the traversed vehicle model samples are used as the current vehicle model samples.
Step S03: and acquiring the ECU parts of the current vehicle model sample, and taking the ECU parts sample as the ECU parts corresponding to the current vehicle model sample.
The method for obtaining the ECU components of the current model sample includes: inserting Bluetooth equipment, acquiring EOL equipment, directly reading part data management systems and the like.
Step S04: and after traversing the vehicle model sample, establishing a preset first mapping relation table according to the corresponding relation between the vehicle model sample and the ECU part sample.
It can be understood that after the vehicle model samples are traversed, the method is equivalent to obtaining ECU parts of all the vehicle model samples, and the ECU parts and the vehicle model samples are in one-to-one correspondence, and at the moment, the correspondence between the vehicle model samples and the ECU part samples can be established only according to the correspondence.
Accordingly, step S20 includes: and determining the Electronic Control Unit (ECU) parts corresponding to the automobile through the preset first mapping relation table according to the vehicle identification number, and taking the ECU parts as the parts to be detected.
In the second embodiment, after the step S03, the method further includes:
step S031: and acquiring a preset part number, a preset hardware version, a software version and a data packet of the ECU part corresponding to the current vehicle model sample.
It should be noted that the method for acquiring the part number, the hardware version, the software version and the data package of the ECU part corresponding to the current vehicle model includes: TBOX was extracted from the car.
Step S032: and taking the preset hardware version as a part number corresponding to a preset part number, taking the software version as a software version corresponding to the preset hardware version, and taking the data packet as a data packet corresponding to the preset hardware version.
It can be understood that the preset hardware version corresponds to the preset part number, the software version corresponds to the preset hardware version, and the data packet corresponds to the preset hardware version, so that when comparison is carried out, the corresponding data packet can be obtained only by comparing the part number.
Step S033: and after traversing the vehicle model sample, establishing a preset second mapping relation table according to the corresponding relation.
It should be understood that after the traversal of the model sample is finished, it is equivalent to obtaining the part number, the hardware version, the software version and the data package of all the model samples.
Accordingly, step S40 includes: and determining a cloud software version and a cloud data packet corresponding to the part to be detected according to the part number and the hardware version through a preset second mapping relation table.
In a second embodiment, a plurality of vehicle type samples are obtained, the vehicle type samples are traversed, the traversed vehicle type samples are used as current vehicle type samples, ECU parts of the current vehicle type samples are obtained, the ECU parts samples are used as the ECU parts corresponding to the current vehicle type samples, the preset part numbers, the preset hardware versions, the software versions and the data packets of the ECU parts corresponding to the current vehicle type samples are obtained, the preset hardware versions are used as the part numbers corresponding to the preset part numbers, the software versions are used as the software versions corresponding to the preset hardware versions, the data packets are used as the data packets corresponding to the preset hardware versions, a preset second mapping relation table is established according to the corresponding relation after the vehicle type samples are traversed, a preset first mapping relation table is established according to the corresponding relation between the vehicle type samples and the ECU parts samples after the vehicle type samples are traversed, the vehicle model sample corresponds to the software version by establishing a preset first mapping relation table and a preset second mapping relation table so as to realize the management of the software version of the ECU parts in the production and after-sale process of the vehicle.
Referring to fig. 4, fig. 4 is a flowchart illustrating a method for managing software versions of automobile parts according to a third embodiment of the present invention, and the method for managing software versions of automobile parts according to the third embodiment of the present invention is provided based on the second embodiment shown in fig. 3.
In the third embodiment, the step S20 includes:
step S201: and determining the vehicle type to be matched according to the vehicle identification number, and matching the vehicle type to be matched with a vehicle type sample in a preset first mapping relation table.
It can be understood that one automobile only has one vehicle identification code, the information such as the automobile type and the date of delivery of the automobile can be determined through the vehicle identification code, the automobile type is matched with the automobile type sample in the preset first mapping relation table, and the ECU parts of the automobile are obtained.
Step S202: and if the matching is successful, taking the ECU part sample corresponding to the successfully matched vehicle model sample as the part to be detected.
It should be understood that, in order to more accurately analyze the ECU components in the automobile, the model may be matched with the model sample in the preset first mapping table, so as to obtain the ECU components of the automobile.
In the third embodiment, the step S40 includes:
step S401: and matching the part number with a preset part number in a preset second mapping relation table, and if the matching is successful, acquiring a preset hardware version corresponding to the successfully matched preset part number.
It will be appreciated that typically the part number and hardware version of an ECU part are unique, and that this is the same ECU part as long as the part number and hardware version are the same.
Step S402: and matching the hardware version with a preset hardware version, if the matching is successful, taking a software version corresponding to the successfully matched preset hardware version as a cloud software version corresponding to the part to be detected, and taking a data packet corresponding to the successfully matched preset hardware version as a cloud data packet corresponding to the part to be detected.
It should be noted that, the matching success may be that the part number and the hardware version are the same as the preset part number and the preset hardware version, or one of them may be the same.
In the third embodiment, after the step S40, the method further includes:
step S403: and acquiring a new software version and a new data packet corresponding to the part number and the hardware version uploaded by the management terminal.
It should be noted that, in order to implement the unified version and upgrade of the software version of the ECU component in the after-market process of the vehicle, the software version of the ECU component needs to be updated by the unified component data management system, and the latest software version needs to be designed by the administrator according to the design-trial-run-mass production process and then uploaded to the component data management system.
Step S404: and updating the cloud software version and the cloud data packet according to the new software version and the new data packet.
In a specific implementation, the manner of updating the cloud software version and the cloud data package according to the new software version and the new data package includes: and identifying the version number, version characteristics, version upgrading identification and the like of the software version to update the cloud software version and the cloud data packet according to the new software version and the new data packet.
In the third embodiment, after the step S60, the method further includes:
step S601: and acquiring the software version number of the part to be detected.
It should be understood that, in the design, production, and after-sale stages, the software and hardware versions of the parts have the phenomena of version upgrade, software and hardware change, etc., and in order to effectively distinguish the states before and after the software change, the software version number is used for identification.
Step S602, verifying whether the cloud software version and the cloud data packet are compatible with the software version to be detected.
It should be noted that, if the cloud software version cannot be downward compatible, normal use of the client may be affected, so that during updating, if the pushed version of the incompatible PLM end is pushed, the client needs to be notified by using a specific identifier, and if the pushed version of the downward compatible PLM end is pushed, the software version number in this embodiment is not changed. The implementation is realized by changing the software version number, and when the software version is not downward compatible, the software version number is added with 1.
Step S603: and if the software version numbers are not compatible, adding one to the software version number of the part to be detected, and sending the part to be detected to the automobile client.
It can be understood that the cloud software version cannot be downward compatible, which may affect the normal use of the client, so that when updating is performed, if the pushed version is an incompatible PLM version, the client needs to be notified by a specific identifier, this implementation is implemented by changing the software version number, and when the software version cannot be downward compatible, the software version number is increased by 1.
In a third embodiment, an update request sent by an automobile client is received, a vehicle identification number of an automobile is extracted from the update request, an automobile type to be matched is determined according to the vehicle identification number, the automobile type to be matched is matched with an automobile type sample in a preset first mapping relation table, if the automobile type to be matched is successfully matched, an ECU part sample corresponding to the automobile type sample successfully matched is used as a part to be detected, a part number, a hardware version and a software version to be detected of the part to be detected are obtained, the part number is matched with a preset part number in a preset second mapping relation table, if the automobile type is successfully matched, a preset hardware version corresponding to the preset part number successfully matched is obtained, the hardware version is matched with the preset hardware version, and if the automobile type is successfully matched, a software version corresponding to the preset hardware version successfully matched is used as a cloud software version corresponding to the part to be detected, and using a data packet corresponding to the successfully matched preset hardware version as a cloud data packet corresponding to the part to be detected, acquiring a new software version and a new data packet corresponding to the part number and the hardware version uploaded by a management terminal, updating the cloud software version and the cloud data packet according to the new software version and the new data packet, comparing the software version to be detected with the cloud software version, if the software version is different from the cloud software version, sending the cloud data packet to the automobile client, acquiring a software version number of the part to be detected, verifying whether the software version and the cloud data packet are compatible with the software version to be detected, if the software version number is not compatible, adding one to the software version number of the part to be detected, sending the added part to the automobile client, uniformly updating and managing each ECU part of the automobile through a part data management system, and avoiding the influence of human factors on the upgrading work, and the management of software versions of ECU parts in the production and after-sale processes of the vehicle is realized.
In addition, an embodiment of the present invention further provides a storage medium, where an automobile part software version management program is stored on the storage medium, and when being executed by a processor, the automobile part software version management program implements the steps of the automobile part software version management method described above.
In addition, referring to fig. 5, an embodiment of the present invention further provides an automobile part software version management device, where the automobile part software version management device includes: the system comprises a receiving module 10, an ECU component confirming module 20, an ECU component information acquiring module 30, an update package downloading module 40, a comparing module 50 and an updating module 60;
the receiving module 10 is configured to receive an update request sent by an automobile client, and extract a vehicle identification number of the automobile from the update request;
it should be understood that the execution subject of the embodiment is a product lifecycle component data management system, and the component data management system may be installed in the automobile component software version management device, where the automobile component software version management device may be an electronic device such as a personal computer or a server.
In this embodiment, the method for receiving an update request sent by an automobile client and extracting a vehicle identification number of an automobile from the update request includes: and the vehicle box TBOX receives the vehicle identification VIN code in the finished vehicle test EOL system, and inserts the VIN code into Bluetooth equipment, reads EOL equipment and the like.
The ECU part confirmation module 20 is configured to determine an ECU part of an electronic control unit corresponding to the automobile according to the vehicle identification number, and use the ECU part as a part to be detected;
it can be understood that the preset first mapping relation table part data management system is a relation table obtained by counting an ECU part sample of an existing vehicle model sample, and the relation table includes information such as a part number, manufacturer information, a hardware number, a hardware version, a software version, and the like of the ECU part.
The ECU part information acquiring module 30 is configured to acquire a part number, a hardware version, and a software version of the part to be detected;
note that the part number, the hardware version, and the software version to be detected of the ECU part installed in the automobile are generally acquired by TBOX. In an automobile system, each ECU part corresponds to a part number and a hardware version, and the type of the ECU part can be determined by acquiring the part number and the hardware version of the part to be detected, so that a part data management system determines the latest version of the ECU part.
The update package downloading module 40 is configured to determine a cloud software version and a cloud data package corresponding to the component to be detected according to the component number and the hardware version;
it should be understood that, the latest software version is determined according to the part number and the hardware version, and the correspondence between the part number and the hardware version and the cloud software version and the cloud data package can be established in advance, wherein the cloud software version and the cloud data package are the latest software version of the ECU part designed by a software manager according to the design-trial-production-mass-production process.
The comparison module 50 is configured to compare the to-be-detected software version with the cloud software version;
it should be noted that, comparing the detection software version with the cloud software version may compare differences between the two software versions, where the differences include: version upgrading identification, version distinguishing positions, contents needing to be modified, ending identification and the like.
And the updating module 60 is configured to send the cloud data packet to the automobile client if the cloud data packet is different from the automobile client.
It should be understood that if the same, the version of the software to be detected does not need to be updated. The part data management system can log the whole verification process and store the log in the system. If not, the cloud software version and the cloud data packet need to be sent to the automobile client, the automobile client updates according to the cloud software version and the cloud data packet, after updating is completed, further verification is needed, whether the updated software version is the cloud software version or not is achieved, updating failure is prevented, automobile use is threatened, updating data can be counted after updating, and the updating data comprise task statistics, part version statistics, vehicle updating statistics, part updating statistics, updating failure reason statistics and the like.
In the embodiment, the updating request sent by the automobile client is received, the vehicle identification number of the automobile is extracted from the updating request, determining the Electronic Control Unit (ECU) parts corresponding to the automobile according to the vehicle identification number, and the ECU part is used as a part to be detected, the part number, the hardware version and the software version of the part to be detected are obtained, determining a cloud software version and a cloud data packet corresponding to the part to be detected according to the part number and the hardware version, comparing the software version to be detected with the cloud software version, if different, and sending the cloud data packet to the automobile client, and performing unified updating management on each ECU part of the vehicle through the part data management system, so that the influence of human factors on upgrading work is avoided, and the management of ECU part software versions of the vehicle in the after-sale production process is realized.
In one embodiment, the device for managing software version of automobile parts further comprises: establishing a preset first mapping relation table module;
the system comprises a model establishing module, a model creating module and a first mapping relation table establishing module, wherein the model establishing module is used for obtaining a plurality of model samples, traversing the model samples, taking the traversed model samples as current model samples, obtaining ECU parts of the current model samples, taking the ECU parts samples as ECU parts corresponding to the current model samples, and establishing the first mapping relation table according to the corresponding relation between the model samples and the ECU parts samples after the model samples are traversed.
In an embodiment, the ECU part information obtaining module is further configured to determine a vehicle type to be matched according to the vehicle identification number, match the vehicle type to be matched with a vehicle type sample in a preset first mapping table, and if the matching is successful, take the ECU part sample corresponding to the vehicle type sample that is successfully matched as the part to be detected.
In one embodiment, the device for managing software version of automobile parts further comprises: establishing a preset second mapping relation table module;
the preset second mapping relation table establishing module is used for acquiring a preset part number, a preset hardware version, a software version and a data package of an ECU part corresponding to a current vehicle model sample, taking the preset hardware version as the part number corresponding to the preset part number, taking the software version as the software version corresponding to the preset hardware version, taking the data package as the data package corresponding to the preset hardware version, and establishing a preset second mapping relation table according to the corresponding relation after traversing the vehicle model sample.
In an embodiment, the update package downloading module is further configured to match the part number with a preset part number in a preset second mapping relation table, obtain a preset hardware version corresponding to the successfully matched preset part number if the matching is successful, match the hardware version with the preset hardware version, use a software version corresponding to the successfully matched preset hardware version as a cloud software version corresponding to the part to be detected if the matching is successful, and use a data package corresponding to the successfully matched preset hardware version as a cloud data package corresponding to the part to be detected.
And the new version uploading module is used for acquiring a new software version and a new data package corresponding to the part number and the hardware version uploaded by the management terminal, and updating the cloud software version and the cloud data package according to the new software version and the new data package.
In one embodiment, the device for managing software version of automobile parts further comprises: a version number updating module;
the version number updating module is used for acquiring the software version number of the part to be detected, verifying whether the cloud software version and the cloud data packet are compatible with the software version to be detected, and if not, adding one to the software version number of the part to be detected and then sending the added version number to the automobile client.
Other embodiments or specific implementation manners of the device for managing the software version of the automobile part can refer to the above method embodiments, and are not described herein again.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The use of the words first, second, third, etc. do not denote any order, but rather the words first, second, third, etc. are to be interpreted as names.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be substantially implemented or a part contributing to the prior art may be embodied in the form of a software product, where the computer software product is stored in a storage medium (e.g., a Read Only Memory (ROM)/Random Access Memory (RAM), a magnetic disk, an optical disk), and includes several instructions for enabling a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. A method for managing the software version of automobile parts is characterized by comprising the following steps:
receiving an updating request sent by an automobile client, and extracting a vehicle identification number of an automobile from the updating request;
determining Electronic Control Unit (ECU) parts corresponding to the automobile according to the vehicle identification number, and taking the ECU parts as parts to be detected;
acquiring a part number, a hardware version and a software version of the part to be detected;
determining a cloud software version and a cloud data packet corresponding to the part to be detected according to the part number and the hardware version;
comparing the software version to be detected with the cloud software version;
and if the data packets are different, the cloud data packet is sent to the automobile client.
2. The method for managing the software version of an automobile part according to claim 1, wherein before the step of receiving an update request from an automobile client and extracting the vehicle identification number of the automobile from the update request, the method for managing the software version of an automobile part further comprises:
obtaining samples of various vehicle types;
traversing the vehicle type sample, and taking the traversed vehicle type sample as a current vehicle type sample;
acquiring an ECU part of a current vehicle model sample, and taking the ECU part sample as an ECU part corresponding to the current vehicle model sample;
after traversing the vehicle model sample, establishing a preset first mapping relation table according to the corresponding relation between the vehicle model sample and the ECU part sample;
correspondingly, the step of determining the Electronic Control Unit (ECU) part corresponding to the automobile according to the vehicle identification number and using the ECU part as the part to be detected specifically comprises the following steps:
and determining the Electronic Control Unit (ECU) parts corresponding to the automobile through the preset first mapping relation table according to the vehicle identification number, and taking the ECU parts as the parts to be detected.
3. The method for managing software versions of automobile parts according to claim 2, wherein the step of determining the Electronic Control Unit (ECU) part corresponding to the automobile through the preset first mapping table according to the vehicle identification number and using the ECU part as the part to be detected specifically includes:
determining a vehicle type to be matched according to the vehicle identification number, and matching the vehicle type to be matched with a vehicle type sample in a preset first mapping relation table;
and if the matching is successful, taking the ECU part sample corresponding to the successfully matched vehicle model sample as the part to be detected.
4. The method for managing software versions of automotive parts according to claim 2, wherein after the step of obtaining an ECU part sample of a current vehicle type and taking the ECU part sample as an ECU part corresponding to the sample of the current vehicle type, the method for managing software versions of automotive parts further comprises;
acquiring a preset part number, a preset hardware version, a software version and a data packet of an ECU part corresponding to a current vehicle model sample;
taking the preset hardware version as a part number corresponding to a preset part number, taking the software version as a software version corresponding to the preset hardware version, and taking the data packet as a data packet corresponding to the preset hardware version;
after traversing the vehicle model sample, establishing a preset second mapping relation table according to the corresponding relation;
correspondingly, the step of determining the cloud software version and the cloud data packet corresponding to the part to be detected according to the part number and the hardware version specifically includes:
and determining a cloud software version and a cloud data packet corresponding to the part to be detected according to the part number and the hardware version through a preset second mapping relation table.
5. The method for managing software versions of automobile parts according to claim 4, wherein the step of determining the cloud software version and the cloud data packet corresponding to the part to be detected through a preset second mapping relation table according to the part number and the hardware version specifically includes:
matching the part number with a preset part number in a preset second mapping relation table, and if the matching is successful, acquiring a preset hardware version corresponding to the successfully matched preset part number;
and matching the hardware version with a preset hardware version, if the matching is successful, taking a software version corresponding to the successfully matched preset hardware version as a cloud software version corresponding to the part to be detected, and taking a data packet corresponding to the successfully matched preset hardware version as a cloud data packet corresponding to the part to be detected.
6. The method for managing the software version of the automobile part as claimed in any one of claims 1 to 5, wherein after the step of determining the cloud software version and the cloud data packet corresponding to the part to be detected according to the part number and the hardware version, the method for managing the software version of the automobile part further comprises:
acquiring a new software version and a new data packet corresponding to the part number and the hardware version uploaded by a management terminal;
and updating the cloud software version and the cloud data packet according to the new software version and the new data packet.
7. The method for managing the version of the software of the automobile part according to any one of claims 1 to 5, wherein after the step of sending the cloud data packet to the automobile client if the version of the software of the automobile part is different from the version of the software of the automobile part, the method for managing the version of the software of the automobile part further comprises:
acquiring a software version number of a part to be detected;
verifying whether the cloud software version and the cloud data packet are compatible with the software version to be detected;
and if the software version numbers are not compatible, adding one to the software version number of the part to be detected, and sending the part to be detected to the automobile client.
8. An automobile part software version management device, characterized by comprising: a memory, a processor and an automotive part software version management program stored on the memory and operable on the processor, the automotive part software version management program when executed by the processor implementing the steps of the automotive part software version management method of any one of claims 1 to 7.
9. A storage medium having an automobile part software version management program stored thereon, the automobile part software version management program, when executed by a processor, implementing the steps of the automobile part software version management method according to any one of claims 1 to 7.
10. An automobile part software version management device, characterized in that the automobile part software version management device comprises: the device comprises a receiving module, an ECU part confirming module, an ECU part information acquiring module, an update package downloading module, a comparing module and an updating module;
the receiving module is used for receiving an updating request sent by an automobile client and extracting the automobile identification number of the automobile from the updating request;
the ECU part confirmation module is used for determining the electronic control unit ECU parts corresponding to the automobile according to the vehicle identification number and taking the ECU parts as parts to be detected;
the ECU part information acquisition module is used for acquiring the part number, the hardware version and the software version of the part to be detected;
the updating package downloading module is used for determining a cloud software version and a cloud data package corresponding to the part to be detected according to the part number and the hardware version;
the comparison module is used for comparing the to-be-detected software version with the cloud software version;
and the updating module is used for sending the cloud data packet to the automobile client if the cloud data packet is different from the automobile client.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911057973.8A CN110806894B (en) | 2019-10-31 | 2019-10-31 | Automobile part software version management method, equipment, storage medium and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911057973.8A CN110806894B (en) | 2019-10-31 | 2019-10-31 | Automobile part software version management method, equipment, storage medium and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110806894A true CN110806894A (en) | 2020-02-18 |
| CN110806894B CN110806894B (en) | 2021-02-05 |
Family
ID=69500900
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911057973.8A Active CN110806894B (en) | 2019-10-31 | 2019-10-31 | Automobile part software version management method, equipment, storage medium and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110806894B (en) |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111708555A (en) * | 2020-05-25 | 2020-09-25 | 上海迪璞电子科技股份有限公司 | Data processing device, method and system |
| CN111707477A (en) * | 2020-05-25 | 2020-09-25 | 上海迪璞电子科技股份有限公司 | Vehicle detection method, device and system |
| CN112181456A (en) * | 2020-09-24 | 2021-01-05 | 上海仙塔智能科技有限公司 | Vehicle version management method, system and computer storage medium |
| CN112526976A (en) * | 2020-12-07 | 2021-03-19 | 广州小鹏自动驾驶科技有限公司 | Simulation test method and system for automatic parking controller |
| CN112783527A (en) * | 2021-01-25 | 2021-05-11 | 中国重汽集团济南动力有限公司 | Method and device for upgrading vehicle controller program |
| CN113778498A (en) * | 2021-08-23 | 2021-12-10 | 武汉中海庭数据技术有限公司 | Vehicle data updating method, OTA cloud and vehicle data updating system |
| WO2023045440A1 (en) * | 2021-09-27 | 2023-03-30 | 北京国家新能源汽车技术创新中心有限公司 | Ecu program-flashing method and apparatus |
| CN116205210A (en) * | 2023-05-05 | 2023-06-02 | 江铃汽车股份有限公司 | Method and system for judging matching performance of electric parts of whole vehicle |
| CN116224973A (en) * | 2023-05-08 | 2023-06-06 | 江铃汽车股份有限公司 | Off-line OTA data stream breakpoint control method and system based on upper computer control |
| CN116521202A (en) * | 2023-05-04 | 2023-08-01 | 浙江大学 | Method and device for automatically upgrading firmware of large-scale remote parts |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101840206A (en) * | 2010-01-15 | 2010-09-22 | 北汽福田汽车股份有限公司 | ECU (Electric Control Unit) data flashing system |
| US20110197187A1 (en) * | 2010-02-08 | 2011-08-11 | Seung Hyun Roh | Vehicle software download system and method thereof |
| CN103455027A (en) * | 2013-08-16 | 2013-12-18 | 深圳市元征科技股份有限公司 | Automobile ECU recovery system and recovery method |
| CN105208112A (en) * | 2015-08-28 | 2015-12-30 | 安徽江淮汽车股份有限公司 | Automobile controller software remote upgrade method and internet-of-vehicle system |
| CN106650660A (en) * | 2016-12-19 | 2017-05-10 | 深圳市华尊科技股份有限公司 | Vehicle type recognition method and terminal |
| CN108627222A (en) * | 2018-05-11 | 2018-10-09 | 安徽江淮汽车集团股份有限公司 | A kind of oil meter nucleus correcting system |
| CN109189422A (en) * | 2018-08-13 | 2019-01-11 | 北京新能源汽车股份有限公司 | A kind of remote upgrade method and device of electronic control unit |
| CN109582340A (en) * | 2018-12-07 | 2019-04-05 | 安徽江淮汽车集团股份有限公司 | A kind of method and system of electric car remote upgrade |
-
2019
- 2019-10-31 CN CN201911057973.8A patent/CN110806894B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101840206A (en) * | 2010-01-15 | 2010-09-22 | 北汽福田汽车股份有限公司 | ECU (Electric Control Unit) data flashing system |
| US20110197187A1 (en) * | 2010-02-08 | 2011-08-11 | Seung Hyun Roh | Vehicle software download system and method thereof |
| CN103455027A (en) * | 2013-08-16 | 2013-12-18 | 深圳市元征科技股份有限公司 | Automobile ECU recovery system and recovery method |
| CN105208112A (en) * | 2015-08-28 | 2015-12-30 | 安徽江淮汽车股份有限公司 | Automobile controller software remote upgrade method and internet-of-vehicle system |
| CN106650660A (en) * | 2016-12-19 | 2017-05-10 | 深圳市华尊科技股份有限公司 | Vehicle type recognition method and terminal |
| CN108627222A (en) * | 2018-05-11 | 2018-10-09 | 安徽江淮汽车集团股份有限公司 | A kind of oil meter nucleus correcting system |
| CN109189422A (en) * | 2018-08-13 | 2019-01-11 | 北京新能源汽车股份有限公司 | A kind of remote upgrade method and device of electronic control unit |
| CN109582340A (en) * | 2018-12-07 | 2019-04-05 | 安徽江淮汽车集团股份有限公司 | A kind of method and system of electric car remote upgrade |
Non-Patent Citations (1)
| Title |
|---|
| 王玮等: "CAN诊断协议在生产线EOL系统中的应用", 《汽车实用技术》 * |
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111707477B (en) * | 2020-05-25 | 2022-07-05 | 上海迪璞电子科技股份有限公司 | Vehicle detection method, device and system |
| CN111707477A (en) * | 2020-05-25 | 2020-09-25 | 上海迪璞电子科技股份有限公司 | Vehicle detection method, device and system |
| CN111708555A (en) * | 2020-05-25 | 2020-09-25 | 上海迪璞电子科技股份有限公司 | Data processing device, method and system |
| CN111708555B (en) * | 2020-05-25 | 2023-09-29 | 上海迪璞电子科技股份有限公司 | Data processing equipment, method and system |
| CN112181456A (en) * | 2020-09-24 | 2021-01-05 | 上海仙塔智能科技有限公司 | Vehicle version management method, system and computer storage medium |
| CN112526976A (en) * | 2020-12-07 | 2021-03-19 | 广州小鹏自动驾驶科技有限公司 | Simulation test method and system for automatic parking controller |
| CN112783527B (en) * | 2021-01-25 | 2023-09-05 | 中国重汽集团济南动力有限公司 | Upgrading method and equipment for vehicle controller program |
| CN112783527A (en) * | 2021-01-25 | 2021-05-11 | 中国重汽集团济南动力有限公司 | Method and device for upgrading vehicle controller program |
| CN113778498A (en) * | 2021-08-23 | 2021-12-10 | 武汉中海庭数据技术有限公司 | Vehicle data updating method, OTA cloud and vehicle data updating system |
| WO2023045440A1 (en) * | 2021-09-27 | 2023-03-30 | 北京国家新能源汽车技术创新中心有限公司 | Ecu program-flashing method and apparatus |
| CN116521202A (en) * | 2023-05-04 | 2023-08-01 | 浙江大学 | Method and device for automatically upgrading firmware of large-scale remote parts |
| CN116521202B (en) * | 2023-05-04 | 2023-11-07 | 浙江大学 | Method and device for automatically upgrading firmware of large-scale remote parts |
| CN116205210A (en) * | 2023-05-05 | 2023-06-02 | 江铃汽车股份有限公司 | Method and system for judging matching performance of electric parts of whole vehicle |
| CN116205210B (en) * | 2023-05-05 | 2023-08-18 | 江铃汽车股份有限公司 | Method and system for judging matching performance of electric parts of whole vehicle |
| CN116224973A (en) * | 2023-05-08 | 2023-06-06 | 江铃汽车股份有限公司 | Off-line OTA data stream breakpoint control method and system based on upper computer control |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110806894B (en) | 2021-02-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110806894B (en) | Automobile part software version management method, equipment, storage medium and device | |
| US20170242678A1 (en) | Method and apparatus for vehicle software update installation | |
| US20170242679A1 (en) | Method and apparatus for over the air updates | |
| CN113703814B (en) | Configuration method, system, storage medium and configuration equipment of Internet of vehicles APP | |
| CN111031115A (en) | Electronic controller version updating system and method based on Internet of vehicles | |
| US20110176456A1 (en) | Connection setting apparatus, connection setting method, and computer program product | |
| CN110825072B (en) | Automobile fault diagnosis method, equipment, storage medium and device | |
| CN109739536A (en) | The method, apparatus and storage medium of vehicle remote firmware updating | |
| CN111176695A (en) | Vehicle ECU configuration method, server and terminal | |
| CN111538523A (en) | Differential upgrading method, device and storage medium | |
| CN111708555B (en) | Data processing equipment, method and system | |
| CN116775079A (en) | Vehicle part refreshing method and device, electronic equipment and storage medium | |
| CN105791017A (en) | Vehicle-mounted module refreshing method and apparatus | |
| CN110908943A (en) | Board card automatic adapting method, device, network equipment and storage medium | |
| CN115437915A (en) | Vehicle-based version testing method and device and electronic equipment | |
| Shi et al. | A vehicle electric control unit over-the-air reprogramming system | |
| CN112507087B (en) | Terminal equipment identification method, equipment, storage medium and device | |
| CN113220322A (en) | Test software updating method, electronic device and storage medium | |
| CN112306041A (en) | Vehicle configuration information writing method and device and electronic equipment | |
| CN112433935A (en) | Test method, test device, electronic equipment and storage medium | |
| CN115543816A (en) | Software regression test result verification method, device, equipment and storage medium | |
| CN113434164B (en) | Cloud configuration updating method and system for setting item of vehicle-mounted entertainment host | |
| CN115118577A (en) | Method and device for determining remote upgrade abnormal reason, electronic equipment and storage medium | |
| CN114610341A (en) | Production line flashing method and device, electronic equipment, chip and storage medium | |
| CN112559000B (en) | Whole vehicle software updating method and device for vehicle |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |