CN115220767A

CN115220767A - Software upgrading method, system, electronic equipment and storage medium

Info

Publication number: CN115220767A
Application number: CN202210899565.2A
Authority: CN
Inventors: 陈潘
Original assignee: Chongqing Changan Automobile Co Ltd
Current assignee: Chongqing Changan Automobile Co Ltd
Priority date: 2022-07-28
Filing date: 2022-07-28
Publication date: 2022-10-21

Abstract

The application provides a software upgrading method, a system, an electronic device and a storage medium, firstly selecting a vehicle type to be subjected to software upgrading, and creating vehicle version information based on the selected vehicle type; then generating a corresponding software upgrading package on an upgrading package management page according to the vehicle version information; then downloading the manufactured software upgrading package and storing the software upgrading package to the mobile storage device; and finally, connecting the mobile storage equipment with the target vehicle, and installing the software upgrading package stored in the mobile storage equipment to the target vehicle so as to upgrade the software of the target vehicle. Therefore, the software upgrading package can be manufactured for the large version of the vehicle, a user is supported to download the software upgrading package through the browser, and after the user decompresses the USB upgrading package to the USB flash disk, the software upgrading can be directly carried out through inserting the USB interface of the vehicle.

Description

Software upgrading method, system, electronic equipment and storage medium

Technical Field

The present application relates to the field of vehicle control technologies, and in particular, to a software upgrading method, system, electronic device, and storage medium.

Background

With the development of the internet vehicle technology, in order to reduce the recall of the problem vehicles, various major vehicle factories timely deal with the after-sale problems, iteratively update the functions of the vehicles in the market, improve the user experience, and deeply research and apply the upgrading technology of the software of the vehicle-mounted equipment. In addition to remote software upgrading through Over-the-Air Technology (OTA), software upgrading operation can be performed through a Universal Serial Bus (USB) port of a vehicle machine in a factory or an after-sale service point, but since the USB upgrade package manufactured offline is not only lack of uniform software package catalog management, but also needs to be locally performed with operations of upgrade package downloading, verification, packaging, upgrade configuration file writing, encryption and the like, time and labor are consumed, errors are prone to occur, and illegal downloading, illegal installation and other problems are not easy to manage. Therefore, a new software upgrading method is important.

Disclosure of Invention

In view of the above drawbacks of the prior art, the present application provides a software upgrading method, system, electronic device and storage medium to solve the above technical problems.

The application provides a software upgrading method, which comprises the following steps:

selecting a vehicle type to be subjected to software upgrading, and creating vehicle version information based on the selected vehicle type;

generating a corresponding software upgrading package on an upgrading package management page according to the vehicle version information;

downloading the manufactured software upgrading package and storing the software upgrading package to the mobile storage device;

connecting the mobile storage equipment with a target vehicle, and installing a software upgrading package stored in the mobile storage equipment to the target vehicle so as to upgrade the software of the target vehicle; the target vehicle comprises a vehicle which is determined in advance or in real time and is to be subjected to software upgrading.

In an embodiment of the present application, the process of creating the vehicle version information based on the selected vehicle type includes:

grouping different vehicle types through a pre-created vehicle type configuration group, and distributing a plurality of vehicle types with the same upgrading software set to the same vehicle type configuration group;

creating an initial version for the grouped vehicle type configuration group, and adding vehicle upgrading precondition information and software parallel upgrading information to the vehicle type configuration group with the initial version created to generate vehicle version information; alternatively, the first and second electrodes may be,

and creating an initial version for the grouped vehicle type configuration group, performing iterative update on the initial version, adding vehicle upgrade precondition information and software parallel upgrade information to the vehicle type configuration group of which the version is iteratively updated, and generating vehicle version information.

In an embodiment of the present application, the process of generating a corresponding software upgrade package on an upgrade package management page according to the vehicle version information includes:

receiving and responding to an account and a password input by an external object, and entering an upgrade package management page based on a response result;

triggering a software upgrading pack manufacturing button, and matching the vehicle version selected by the external object from the vehicle version information, the created software upgrading task, the selected vehicle type configuration grouping, the selected upgrading mode and the encryption mode based on a triggering result;

and manufacturing and generating a software upgrading package on the upgrading package management page according to the matching result.

In an embodiment of the present application, the process of generating a software upgrade package on an upgrade package management page according to a matching result includes:

inquiring the waiting task according to the task creating time, and triggering and manufacturing a software upgrading package after the task waiting time exceeds the preset time;

emptying the temporary directory file and judging whether the residual space of the temporary directory is enough;

if the residual space of the temporary directory is not enough, judging that the software upgrading package is failed to be manufactured;

if the residual space of the temporary directory is enough, inquiring upgrading certificate information, writing the upgrading certificate information into a designated folder of the temporary directory, and downloading a software upgrading package and a rollback package selected from the tasks into the temporary directory; and generating an upgrade configuration file based on vehicle upgrade precondition information and software parallel upgrade information in the vehicle version information, storing the upgrade configuration file into the temporary directory for encryption, and packaging and compressing the encrypted temporary directory to form a software upgrade package in a preset compression format.

In an embodiment of the present application, the process of generating a software upgrade package on an upgrade package management page according to the matching result further includes:

when the software upgrading package is in a waiting or manufacturing state, canceling the created software upgrading task; and the number of the first and second groups,

and when the created software upgrading task is successful, failed and cancelled, deleting the created software upgrading task.

In an embodiment of the present application, the connecting the mobile storage device with a target vehicle, and the installing the software upgrade package stored in the mobile storage device to the target vehicle includes:

connecting the mobile storage equipment with a target vehicle, reading configuration file information, and judging a corresponding software upgrading mode;

if the corresponding software upgrading mode is the after-sale mode, carrying out installation verification on a vehicle to be subjected to software upgrading, carrying out software upgrading when the vehicle conforms to the installation range of the upgrading package, and prompting a user to mount illegally when the vehicle does not conform to the installation range of the upgrading package;

and if the corresponding software upgrading mode is the factory mode, reading upgrading certificate information and configuration file information, analyzing vehicle upgrading precondition information and software parallel upgrading information according to the configuration file information, and installing the analyzed software upgrading installation package based on the upgrading certificate information until the installation is finished.

In an embodiment of the present application, the mobile storage device includes a usb disk; the software upgrade package comprises a USB software upgrade package.

The present application further provides a software upgrading system, comprising:

the version information module is used for selecting the type of the vehicle to be subjected to software upgrading and creating vehicle version information based on the selected type of the vehicle;

the software upgrading package generating module is used for generating a corresponding software upgrading package on an upgrading package management page according to the vehicle version information;

the download module is used for downloading the manufactured software upgrading package and storing the software upgrading package to the mobile storage device;

the upgrading installation module is used for connecting the mobile storage equipment with a target vehicle and installing a software upgrading package stored in the mobile storage equipment to the target vehicle so as to upgrade the software of the target vehicle; the target vehicle comprises a vehicle which is determined in advance or in real time and is to be subjected to software upgrading.

The present application further provides an electronic device, the electronic device including:

one or more processors;

storage means for storing one or more programs which, when executed by the one or more processors, cause the electronic device to implement a software upgrade method as claimed in any one of the preceding claims.

The present application also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor of a computer, causes the computer to carry out a software upgrade method as described in any one of the above.

As described above, the present application provides a software upgrading method, system, electronic device, and storage medium, which have the following advantages:

the method comprises the steps of firstly selecting a vehicle type to be subjected to software upgrading, and creating vehicle version information based on the selected vehicle type; then generating a corresponding software upgrading package on an upgrading package management page according to the vehicle version information; then downloading the manufactured software upgrading package and storing the software upgrading package to the mobile storage device; finally, connecting the mobile storage equipment with the target vehicle, and installing the software upgrading package stored in the mobile storage equipment to the target vehicle so as to upgrade the software of the target vehicle; the target vehicle comprises a vehicle which is determined in advance or in real time and is to be subjected to software upgrading. Therefore, the USB upgrade package method based on online manufacturing can be used for manufacturing large versions of vehicles (version numbers for providing consistency control on vehicle software versions and including whole vehicle software version sets). The method comprises the steps of firstly selecting information of a large vehicle version needing to be created, selecting a USB upgrading packet to manufacture a vehicle type vehicle system after the creation is finished, selecting the large vehicle version needing to be manufactured, selecting information of an upgrading packet and a rollback packet needing to be manufactured under the large version, selecting an upgrading mode (an engineering mode and an after-sale mode), leading vehicle information which is allowed to be installed in the upgrading packet into the after-sale mode, selecting an encryption mode, then starting to manufacture the USB upgrading packet, uploading the manufactured upgrading packet to a file warehouse after the manufacture is finished, supporting a user to download the USB upgrading packet by using a browser, decompressing the USB upgrading packet into a U disk by the user, and then inserting a vehicle USB interface to carry out software upgrading.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application. It is obvious that the drawings in the following description are only some embodiments of the application, and that for a person skilled in the art, other drawings can be derived from them without inventive effort. In the drawings:

FIG. 1 is a schematic diagram of an exemplary system architecture to which aspects of one or more embodiments of the present application may be applied;

fig. 2 is a schematic flowchart of a software upgrading method according to an embodiment of the present application;

fig. 3 is a schematic service flow diagram of a USB upgrade package according to an embodiment of the present application;

fig. 4 is a schematic view of a service flow of using a USB upgrade package at a vehicle end according to an embodiment of the present application;

FIG. 5 is a block diagram of an embodiment of the present application

Fig. 6 is a hardware configuration diagram of an electronic device suitable for implementing one or more embodiments of the present application.

Detailed Description

Other advantages and effects of the present application will become apparent to those skilled in the art from the disclosure herein, wherein the embodiments of the present application will be described in detail with reference to the accompanying drawings and preferred embodiments. The application is capable of other and different embodiments and its several details are capable of modifications and various changes in detail without departing from the spirit of the application. It should be understood that the preferred embodiments are for purposes of illustration only and are not intended to limit the scope of the present disclosure.

It should be noted that the drawings provided in the following embodiments are only for illustrating the basic idea of the present application, and the drawings only show the components related to the present application and are not drawn according to the number, shape and size of the components in actual implementation, and the type, number and proportion of the components in actual implementation may be changed freely, and the layout of the components may be more complicated.

In the following description, numerous details are set forth to provide a more thorough explanation of the embodiments of the present application, however, it will be apparent to one skilled in the art that the embodiments of the present application may be practiced without these specific details, and in other embodiments, well-known structures and devices are shown in block diagram form rather than in detail in order to avoid obscuring the embodiments of the present application.

Fig. 1 shows a schematic diagram of an exemplary system architecture to which technical solutions in one or more embodiments of the present application may be applied. As shown in fig. 1, system architecture 100 may include a terminal device 110, a network 120, and a server 130. The terminal device 110 may include various electronic devices such as a smart phone, a tablet computer, a notebook computer, and a desktop computer. The server 130 may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing cloud computing services. Network 120 may be a communication medium of various connection types capable of providing a communication link between terminal device 110 and server 130, such as a wired communication link or a wireless communication link.

The system architecture in the embodiments of the present application may have any number of terminal devices, networks, and servers, according to implementation needs. For example, the server 130 may be a server group composed of a plurality of server devices. In addition, the technical solution provided in the embodiment of the present application may be applied to the terminal device 110, or may be applied to the server 130, or may be implemented by both the terminal device 110 and the server 130, which is not particularly limited in this application.

In an embodiment of the present application, the terminal device 110 or the server 130 of the present application may select a vehicle type to be subjected to software upgrade, and create vehicle version information based on the selected vehicle type; then generating a corresponding software upgrading package on an upgrading package management page according to the vehicle version information; then downloading the manufactured software upgrading package and storing the software upgrading package to the mobile storage device; and finally, connecting the mobile storage equipment with the target vehicle, and installing the software upgrading package stored in the mobile storage equipment to the target vehicle so as to upgrade the software of the target vehicle. By using the terminal device 110 or the server 130 to execute the software upgrading method, the vehicle large version (the version number providing consistency control for the vehicle software version, including the whole vehicle software version set) can be manufactured. The method comprises the steps of firstly selecting information of a large vehicle version needing to be created, selecting a USB upgrading packet to manufacture a vehicle type vehicle system after the creation is finished, selecting the large vehicle version needing to be manufactured, selecting information of an upgrading packet and a rollback packet needing to be manufactured under the large version, selecting an upgrading mode (an engineering mode and an after-sale mode), leading vehicle information which is allowed to be installed in the upgrading packet into the after-sale mode, selecting an encryption mode, then starting to manufacture the USB upgrading packet, uploading the manufactured upgrading packet to a file warehouse after the manufacture is finished, supporting a user to download the USB upgrading packet by using a browser, decompressing the USB upgrading packet into a U disk by the user, and then inserting a vehicle USB interface to carry out software upgrading.

The above section introduces the content of an exemplary system architecture to which the technical solution of the present application is applied, and then the software upgrading method of the present application is continuously introduced.

Fig. 2 shows a flowchart of a software upgrading method according to an embodiment of the present application. Specifically, in an exemplary embodiment, as shown in fig. 2, the present embodiment provides a software upgrading method, including the following steps:

s210, selecting a vehicle type to be subjected to software upgrading, and creating vehicle version information based on the selected vehicle type;

s220, generating a corresponding software upgrading package on an upgrading package management page according to the vehicle version information; as an example, the software upgrade package in the present embodiment includes a USB software upgrade package.

S230, downloading the manufactured software upgrading package and storing the software upgrading package in a mobile storage device; as an example, the mobile storage device in the present embodiment includes a usb disk.

S240, connecting the mobile storage device with a target vehicle, and installing a software upgrading package stored in the mobile storage device to the target vehicle so as to upgrade the software of the target vehicle; the target vehicle comprises a vehicle which is determined in advance or in real time and is to be subjected to software upgrading.

Therefore, the embodiment provides an online-production-based USB upgrade package method, which can be produced for a large vehicle version (a version number providing consistency control for a vehicle software version, including a complete vehicle software version set). The method comprises the steps of firstly selecting information of a large vehicle version needing to be created, selecting a USB upgrading packet to manufacture a vehicle type vehicle system after the creation is finished, selecting the large vehicle version needing to be manufactured, selecting information of an upgrading packet and a rollback packet needing to be manufactured under the large version, selecting an upgrading mode (an engineering mode and an after-sale mode), leading vehicle information which is allowed to be installed in the upgrading packet into the after-sale mode, selecting an encryption mode, then starting to manufacture the USB upgrading packet, uploading the manufactured upgrading packet to a file warehouse after the manufacture is finished, supporting a user to download the USB upgrading packet by using a browser, decompressing the USB upgrading packet into a U disk by the user, and then inserting a vehicle USB interface to carry out software upgrading.

In an exemplary embodiment, the process of creating the vehicle version information based on the selected vehicle type includes: grouping different vehicle types through a pre-created vehicle type configuration group, and distributing a plurality of vehicle types with the same upgrading software set to the same vehicle type configuration group; creating an initial version for the grouped vehicle type configuration group, and adding vehicle upgrading precondition information and software parallel upgrading information to the vehicle type configuration group with the initial version created to generate vehicle version information; or, an initial version is created for the grouped vehicle type configuration group, the initial version is updated iteratively, vehicle upgrade precondition information and software parallel upgrade information are added to the vehicle type configuration group of which the version is updated iteratively, and vehicle version information is generated.

Specifically, in the present embodiment, the process of creating the vehicle major version information includes: an administrator logs in the OTA cloud system, enters a vehicle system OTA configuration page provided by the system, and distinguishes a certain type of vehicles according to the vehicle system, wherein OTA behaviors of the vehicles are consistent. First, a vehicle system needs to be selected, and all upgradable software under the vehicle system is configured for the vehicle system, and usually, a plurality of different vehicle types are provided under the vehicle system, the upgradable software of each vehicle type may be different, some vehicle types may have more upgradable software, some vehicle types may have less upgradable software, the same upgrade object of different vehicle types may have different corresponding software. The different vehicle types are grouped by creating a vehicle type configuration group, and a plurality of vehicle types with the same upgrade software set are distributed to the same vehicle type configuration group for unified management. An upgraded software set of the vehicle type configuration group may then be set, which is a subset of the above configured vehicle family software set. The software for all vehicle types under the vehicle type configuration group must be all in the upgraded software set of the vehicle type configuration group configuration. Then, a software large version needs to be created for the vehicle type configuration group, a baseline version is created first, the baseline version is an initial version, namely a version of the vehicle when leaving a factory, and then a software large version of a higher version is created according to iteration or software updating conditions. After the software large versions are created, a specific version of each piece of software in the software set needs to be set for each software large version, and when the specific version is set, a specific software version under the currently configured software large version is required to be between the software versions in the higher software large version and the lower software large version. After the specific versions of all the software under a certain software large version are set, a software large version of a vehicle type configuration group of a vehicle series is created successfully, then vehicle upgrading precondition information of the vehicle type configuration group needs to be added, and then software parallel upgrading information is added. The information of the software parallel upgrade comprises the gear position of the transmission, the state of a hand brake, the electric quantity of a storage battery allowed/forbidden to be installed, the ambient temperature and the like, the vehicle upgrade precondition information is software which can be upgraded in parallel and is obtained by judging an upgrade strategy by adding the software upgrade sequence, and the upgrade efficiency is improved.

In an exemplary embodiment, the process of generating a corresponding software upgrade package on an upgrade package management page according to the vehicle version information includes: receiving and responding to an account and a password input by an external object, and entering an upgrade package management page based on a response result; triggering a software upgrading pack manufacturing button, and matching the vehicle version selected by the external object from the vehicle version information, the created software upgrading task, the selected vehicle type configuration grouping, the selected upgrading mode and the encryption mode based on a triggering result; and manufacturing and generating a software upgrading package on the upgrading package management page according to the matching result. The process of manufacturing and generating the software upgrade package on the upgrade package management page according to the matching result comprises the following steps: inquiring the waiting task according to the task creating time, and triggering and manufacturing a software upgrading package after the task waiting time exceeds the preset time; emptying the temporary directory file and judging whether the residual space of the temporary directory is enough; if the residual space of the temporary directory is not enough, judging that the software upgrading package is failed to be manufactured; if the residual space of the temporary directory is enough, inquiring upgrade certificate information, writing the upgrade certificate information into a temporary directory specified folder, and downloading a software upgrade package and a rollback package selected in a task into the temporary directory; and generating an upgrade configuration file based on vehicle upgrade precondition information and software parallel upgrade information in the vehicle version information, storing the upgrade configuration file into the temporary directory for encryption, and packaging and compressing the encrypted temporary directory to form a software upgrade package in a preset compression format.

Specifically, in this embodiment, the process of creating a USB upgrade package production task includes: the method comprises the steps that an administrator logs in an OTA cloud system, enters an online USB upgrade package manufacturing management page, selects a corresponding service vehicle type car series, clicks a USB upgrade package manufacturing button, pops up a newly added frame, fills in a task name, selects a vehicle type configuration group, selects a large version, selects upgrade software needing to be manufactured under the large version and rollback package information (needing to be checked), selects an upgrade mode, selects an encryption mode, and clicks to confirm completion of creation. In this embodiment, if the upgrade mode is selected as the after-sales mode, vehicle Identification Number (VIN) code information needs to be added, which is used to request the cloud USB upgrade task check interface to check whether the Vehicle is in the configuration of the upgrade package when the Vehicle performs USB upgrade and detects that the USB upgrade package is in the after-sales mode, and if not, the Vehicle does not allow the upgrade. The process of manufacturing the USB upgrade package on line comprises the following steps: and the OTA server triggers the task at regular time, inquires the waiting task according to the task creating time, starts to manufacture, firstly clears the temporary directory file and judges whether the residual space of the temporary directory is enough. If not, the manufacture is failed, and the failure reason is stored. Secondly, inquiring the cloud OTA upgrade certificate information, writing in files, placing the files into a temporary directory specified folder, then downloading a software upgrade package and a rollback package selected in a task into a corresponding directory, and performing traversal encryption on all files in the temporary directory; reading software list information and detailed information of an upgrading software package under the large version according to the selected large version, firstly writing upgrading task basic information, writing software information of the upgrading, writing vehicle upgrading precondition information, calculating information capable of being upgraded in parallel according to the sequence of software upgrading, writing the information into a configuration file, storing the generated upgrading configuration file into a directory and encrypting; packaging and compressing the whole USB upgrading task temporary directory into a zip-format USB upgrading packet, calculating information such as MD5 (MD 5 Message-Digest Algorithm, MD5 information abstract Algorithm, abbreviated as MD 5) and SHA256 of the USB upgrading packet, uploading the file to a file cloud service for storage, storing file storage handle information and task manufacturing results, and clearing the temporary file directory.

In an exemplary embodiment, the process of generating a software upgrade package at the upgrade package management page manufacturing according to the matching result further includes: when the software upgrading package is in a waiting or manufacturing state, canceling the created software upgrading task; and deleting the created software upgrading task when the created software upgrading task is successful, failed and cancelled.

According to the above description, the process of connecting the mobile storage device with a target vehicle and installing the software upgrade package stored in the mobile storage device to the target vehicle includes:

Specifically, in another exemplary embodiment, as shown in fig. 3 and 4, the embodiment further provides an online production-based USB upgrade package method, which mainly includes: the method comprises the steps of creating vehicle large version information, creating a USB upgrade package manufacturing task, manufacturing a USB upgrade package on line, downloading and managing the USB upgrade package, and installing the vehicle-end USB upgrade package.

Specifically, the method comprises the following steps:

(1) Creating vehicle large version information: and creating a mapping relation of each software set corresponding to the whole vehicle version, upgrading package detailed information, vehicle upgrading precondition information, parallel upgrading information and the like. Specifically, an administrator logs in the OTA cloud system, enters an OTA configuration page of a train provided by the system, and distinguishes a certain type of train according to the train, wherein OTA behaviors of the certain type of train are consistent. First, a vehicle system needs to be selected, and all upgradable software under the vehicle system is configured for the vehicle system, and usually, a plurality of different vehicle types are provided under the vehicle system, the upgradable software of each vehicle type may be different, some vehicle types may have more upgradable software, some vehicle types may have less upgradable software, the same upgrade object of different vehicle types may have different corresponding software. The different vehicle types are grouped by creating a vehicle type configuration group, and a plurality of vehicle types with the same upgrade software set are distributed to the same vehicle type configuration group for unified management. An upgraded software set of the vehicle type configuration group, which is a subset of the above configured vehicle system software set, may then be set. The software for all vehicle types under the vehicle type configuration group must be all in the upgraded software set of the vehicle type configuration group configuration. Then, a software large version needs to be created for the vehicle type configuration group, a baseline version is created first, the baseline version is an initial version, namely a version of the vehicle when leaving a factory, and then a software large version of a higher version is created according to iteration or software updating conditions. After the software large versions are created, a specific version of each piece of software in the software set needs to be set for each software large version, and when the specific version is set, a specific software version under the currently configured software large version is required to be between the software versions in the higher software large version and the lower software large version. After the specific versions of all software under a certain software large version are set, one software large version of one vehicle type configuration group of one train is created successfully, and then vehicle upgrade precondition information (including transmission gear, handbrake state, battery capacity for allowing/forbidding installation, ambient temperature and the like) of the vehicle type configuration group needs to be added. And then adding the information of the software parallel upgrade (namely judging the upgrade strategy to obtain the software capable of being upgraded in parallel by adding the sequence of the software upgrade, and improving the upgrade efficiency).

(2) Creating a USB upgrade package manufacturing task: the system is mainly responsible for selecting software information to be manufactured and configuring configurations such as supporting vehicle information and upgrading modes. Specifically, an administrator logs in an OTA cloud system, enters an online production-USB upgrade package management page, selects a corresponding service vehicle type vehicle system, clicks a button for producing a USB upgrade package, pops up a new frame, fills in a task name, selects a vehicle type configuration group, selects a large version, selects upgrade software needing to be produced under the large version and rollback package information (required to be checked), selects an upgrade mode (wherein the upgrade mode is selected to be an after-sale mode, VIN code information needs to be added, and the functions are that when the vehicle end detects that the USB upgrade package is in the after-sale mode during USB upgrade, the vehicle end needs to request a cloud USB upgrade task check interface to check whether the vehicle is in the upgrade package configuration, and if not, upgrade is not allowed), selects an encryption mode, and clicks to confirm that creation is completed.

(3) Manufacturing a USB upgrade package on line: and performing online production of the upgrade package according to the information of the USB upgrade package production task and uploading the upgrade package to a file warehouse. Specifically, the OTA server triggers the task at regular time, inquires the waiting task according to the task creation time, starts to make, firstly clears the temporary directory file, and judges whether the residual space of the temporary directory is enough. If not, the manufacture is failed, and the failure reason is stored. Secondly, inquiring the OTA (over the air) upgrade certificate information of the cloud, writing in files, placing the files into a designated folder of a temporary directory, downloading a software upgrade package and a rollback package selected in a task into a corresponding directory, and performing traversal encryption on all files in the temporary directory; reading software list information and detailed information of an upgrading software package under the large version according to the selected large version, firstly writing upgrading task basic information, writing software information of the upgrading, writing vehicle upgrading precondition information, calculating information capable of being upgraded in parallel according to the sequence of software upgrading, writing the information into a configuration file, storing the generated upgrading configuration file into a directory and encrypting; and packaging and compressing the whole USB upgrading task temporary directory into a zip-format USB upgrading packet, calculating information such as MD5, SHA256 and the like of the USB upgrading packet, uploading the file to a file cloud service for storage, storing file storage handle information and a task manufacturing result, and clearing the temporary file directory. The structure of the temporary directory in this embodiment is shown in table 1 below, the directory is shown in table 2 below, the data content of the configuration file is shown in table 3, the detailed information content of the software package of the target version and the rollback version is shown in table 4, and the software information content is shown in table 5.

TABLE 1 Structure of temporary directory

Table 2 directory example

Table 3 profile data content

TABLE 4 target and rollback version software package information content

TABLE 5 software information content

(4) Downloading and managing a USB upgrade package: and the OTA management terminal supports downloading and managing the successfully manufactured USB upgrade package. Specifically, after the USB upgrade package is manufactured, the manufacturing result may be queried on the management page, if the manufacturing result is successful, the download button may be clicked to download the USB upgrade package, and if the manufacturing result is failure, the reason for the failure may be checked. All tasks can click on the details to make a task software list and view the upgrade mode and supported vehicle list information. The upgrade patch cancels the making function, and can cancel the making task when the state of the upgrade patch is waiting and making; and deleting the task when the manufacturing task is successful, failed and cancelled (the successfully manufactured task deletes the upgrade package of the file cloud storage at the same time).

(5) And (3) installing a vehicle-end USB upgrading packet: and the USB upgrading packet is analyzed and installed by inserting the USB flash disk into the USB port of the vehicle. Specifically, a user downloads a USB upgrading packet to a personal USB flash disk on an OTA management platform, then inserts a vehicle USB interface, firstly reads configuration file information, judges an upgrading mode, if the upgrading mode is an after-sale mode, the user needs to request an OTA cloud end to carry out vehicle installation verification, if the vehicle meets the installation range of the upgrading packet, software upgrading can be carried out, otherwise, the user is prompted to carry out illegal installation, if the upgrading mode is a factory mode, installation is directly carried out, firstly, certificate information and configuration file information are read, upgrading precondition and parallel upgrading information are analyzed according to the configuration file, then the installation packet is decrypted to carry out installation, and installation is waited to be finished. The content of the parallel upgrade information is shown in table 6 below, the content of the vehicle upgrade precondition is shown in table 7 below, and the content of the certificate file is shown in table 8 below.

Table 6 parallel upgrade information content

TABLE 7 vehicle upgrade preconditions content

TABLE 8 certificate file content

The certificate file mainly comprises each certificate id and corresponding certificate content information. As long as the software package for USB upgrade is signed, a certificate file needs to be generated. The certificate file is used for USB upgrading after the USB flash disk is encrypted at the cloud.

Example of the contents of the file:

in summary, the present application provides a software upgrading method, which includes selecting a vehicle type to be subjected to software upgrading, and creating vehicle version information based on the selected vehicle type; then generating a corresponding software upgrading package on an upgrading package management page according to the vehicle version information; then downloading the manufactured software upgrading package and storing the software upgrading package to the mobile storage device; finally, connecting the mobile storage equipment with the target vehicle, and installing the software upgrading package stored in the mobile storage equipment to the target vehicle so as to upgrade the software of the target vehicle; the target vehicle comprises a vehicle which is determined in advance or in real time and is to be subjected to software upgrading. Therefore, the method for manufacturing the USB upgrade package on line is provided, and the USB upgrade package can be manufactured according to a large version of a vehicle (the version number for providing consistency control on the software version of the vehicle includes a whole vehicle software version set). The method comprises the steps of firstly selecting information of a large vehicle version needing to be created, selecting a USB upgrading packet to manufacture a vehicle type vehicle system after the creation is finished, selecting the large vehicle version needing to be manufactured, selecting information of an upgrading packet and a rollback packet needing to be manufactured under the large version, selecting an upgrading mode (an engineering mode and an after-sale mode), leading vehicle information which is allowed to be installed in the upgrading packet into the after-sale mode, selecting an encryption mode, then starting to manufacture the USB upgrading packet, uploading the manufactured upgrading packet to a file warehouse after the manufacture is finished, supporting a user to download the USB upgrading packet by using a browser, decompressing the USB upgrading packet into a U disk by the user, and then inserting a vehicle USB interface to carry out software upgrading.

As shown in fig. 5, the present invention further provides a software upgrading system, which includes:

a version information module 510 for selecting a vehicle type to be subjected to software upgrade, and creating vehicle version information based on the selected vehicle type;

a software upgrade package generation module 520, configured to generate a corresponding software upgrade package on an upgrade package management page according to the vehicle version information;

a download module 530, configured to download the manufactured software upgrade package and store the downloaded software upgrade package in the mobile storage device;

the upgrade installation module 540 is configured to connect the mobile storage device with a target vehicle, and install the software upgrade package stored in the mobile storage device to the target vehicle to perform software upgrade on the target vehicle; the target vehicle comprises a vehicle which is determined in advance or in real time and is to be subjected to software upgrading.

It should be noted that the software upgrading system provided in this embodiment and the software upgrading method provided in the foregoing embodiment belong to the same concept, and the specific manner in which each module executes operations has been described in detail in the method embodiment, and is not described herein again. In practical applications, the software upgrading system provided in the foregoing embodiment may distribute the functions to different functional modules according to needs, that is, divide the internal structure of the system into different functional modules to complete all or part of the functions described above, which is not limited herein.

In summary, the present application provides a software upgrading system, which first selects a vehicle type to be subjected to software upgrading, and creates vehicle version information based on the selected vehicle type; then generating a corresponding software upgrading package on an upgrading package management page according to the vehicle version information; then downloading the manufactured software upgrading package and storing the software upgrading package to the mobile storage device; finally, connecting the mobile storage equipment with the target vehicle, and installing the software upgrading package stored in the mobile storage equipment to the target vehicle so as to upgrade the software of the target vehicle; the target vehicle comprises a vehicle which is determined in advance or in real time and is to be subjected to software upgrading. Therefore, the system provides a USB upgrade package method based on online manufacturing, and can manufacture a large version of a vehicle (the version number of the vehicle software version which provides consistency control and comprises a whole vehicle software version set). The method comprises the steps of firstly selecting information of a large vehicle version needing to be created, selecting a USB upgrading packet to manufacture a vehicle type vehicle system after the creation is finished, selecting the large vehicle version needing to be manufactured, selecting information of an upgrading packet and a rollback packet needing to be manufactured under the large version, selecting an upgrading mode (an engineering mode and an after-sale mode), leading vehicle information which is allowed to be installed in the upgrading packet into the after-sale mode, selecting an encryption mode, then starting to manufacture the USB upgrading packet, uploading the manufactured upgrading packet to a file warehouse after the manufacture is finished, supporting a user to download the USB upgrading packet by using a browser, decompressing the USB upgrading packet into a U disk by the user, and then inserting a vehicle USB interface to carry out software upgrading.

An embodiment of the present application further provides an electronic device, including: one or more processors; a storage device, configured to store one or more programs, which when executed by the one or more processors, cause the electronic device to implement the software upgrading method provided in the above-described embodiments.

FIG. 6 illustrates a schematic structural diagram of a computer system suitable for use in implementing the electronic device of an embodiment of the present application. It should be noted that the computer system 1000 of the electronic device shown in fig. 6 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.

As shown in fig. 6, the computer system 1000 includes a Central Processing Unit (CPU) 1001 that can perform various appropriate actions and processes, such as performing the methods described in the above embodiments, according to a program stored in a Read-Only Memory (ROM) 1002 or a program loaded from a storage portion 1008 into a Random Access Memory (RAM) 1003. In the RAM 1003, various programs and data necessary for system operation are also stored. The CPU 1001, ROM 1002, and RAM 1003 are connected to each other by a bus 1004. An Input/Output (I/O) interface 1005 is also connected to the bus 1004.

The following components are connected to the I/O interface 1005: an input section 1006 including a keyboard, a mouse, and the like; an output section 1007 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and a speaker; a storage portion 1008 including a hard disk and the like; and a communication section 1009 including a Network interface card such as a LAN (Local Area Network) card, a modem, or the like. The communication section 1009 performs communication processing via a network such as the internet. A drive 1010 is also connected to the I/O interface 1005 as necessary. A removable medium 1011 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 1010 as necessary, so that a computer program read out therefrom is mounted into the storage section 1008 as necessary.

In particular, according to embodiments of the application, the processes described above with reference to the flow diagrams may be implemented as computer software programs. For example, embodiments of the present application include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising a computer program for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from the network through the communication part 1009 and/or installed from the removable medium 1011. When the computer program is executed by a Central Processing Unit (CPU) 1001, various functions defined in the system of the present application are executed.

It should be noted that the computer readable medium shown in the embodiments of the present application may be a computer readable signal medium or a computer readable storage medium or any combination of the two. The computer readable storage medium may be, for example, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a Read-Only Memory (ROM), an Erasable Programmable Read-Only Memory (EPROM), a flash Memory, an optical fiber, a portable Compact Disc Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer-readable signal medium may comprise a propagated data signal with a computer-readable computer program embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. The computer program embodied on the computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. Each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units described in the embodiments of the present application may be implemented by software, or may be implemented by hardware, and the described units may also be disposed in a processor. Wherein the names of the elements do not in some way constitute a limitation on the elements themselves.

Another aspect of the present application also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor of a computer, causes the computer to execute the software upgrade method as described above. The computer-readable storage medium may be included in the electronic device described in the above embodiment, or may exist separately without being incorporated in the electronic device.

Another aspect of the application also provides a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and executes the computer instructions, so that the computer device executes the software upgrading method provided in the above embodiments.

The above-described embodiments are merely illustrative of the principles and utilities of the present application and are not intended to limit the application. Any person skilled in the art can modify or change the above-described embodiments without departing from the spirit and scope of the present application. Accordingly, it is intended that all equivalent modifications or changes which can be made by those skilled in the art without departing from the spirit and technical concepts disclosed in the present application shall be covered by the claims of the present application.

Claims

1. A method of upgrading software, the method comprising the steps of:

2. The software upgrading method according to claim 1, wherein the process of creating vehicle version information based on the selected vehicle type includes:

3. The software upgrading method according to claim 1 or 2, wherein the process of generating the corresponding software upgrading package on the upgrading package management page according to the vehicle version information comprises:

4. The software upgrading method according to claim 3, wherein the process of generating the software upgrading package on the upgrading package management page according to the matching result comprises:

if the residual space of the temporary directory is enough, inquiring upgrade certificate information, writing the upgrade certificate information into a temporary directory specified folder, and downloading a software upgrade package and a rollback package selected in a task into the temporary directory; and generating an upgrade configuration file based on vehicle upgrade precondition information and software parallel upgrade information in the vehicle version information, storing the upgrade configuration file into the temporary directory for encryption, and packaging and compressing the encrypted temporary directory to form a software upgrade package in a preset compression format.

5. The software upgrading method according to claim 4, wherein the process of generating the software upgrading package on the upgrading package management page according to the matching result further comprises:

6. The software upgrading method according to claim 1 or 5, wherein the mobile storage device is connected with a target vehicle, and the process of installing the software upgrading package stored in the mobile storage device to the target vehicle comprises:

7. The software upgrading method of claim 6, wherein the mobile storage device comprises a USB flash disk, and the software upgrading package comprises a USB software upgrading package.

8. A software upgrade system, said system comprising:

9. An electronic device, characterized in that the electronic device comprises:

one or more processors;

storage means for storing one or more programs which, when executed by the one or more processors, cause the electronic device to implement the software upgrade method as claimed in any one of claims 1 to 7.

10. A computer-readable storage medium, having stored thereon a computer program which, when executed by a processor of a computer, causes the computer to carry out the software upgrade method as claimed in any one of claims 1 to 7.