A software upgrade query method based on multi-task and multi-version

Abstract

The present invention discloses a software upgrade query method based on multiple tasks and multiple versions, which relates to the technical field of software upgrade query. An application terminal requests a server background to query vehicle upgrade information through information such as project name, device number, vehicle platform, software type and version number. After receiving the query request data, the server background obtains query condition information, queries software upgrade package information records that meet the project name, vehicle platform and software type conditions from a software upgrade package information table, queries software upgrade package information, task release information, grayscale device information and software version number information, and finally returns the software upgrade package information that meets the requirements. The method solves the problem of how to quickly find the query of device software upgrade package information and the problem of multi-task independent upgrade of different devices.

Description

Technical Field

[0001] The present invention belongs to the field of software upgrade query, relates to software upgrade version query technology, and specifically is a software upgrade query method based on multi-task and multi-version. Background Art

[0002] As the automotive industry shifts from gasoline-powered vehicles to electric vehicles, users are increasingly valuing the intelligent features of electric vehicle equipment. The core of intelligent equipment lies in the intelligent software installed within the hardware. To ensure a better user experience, the functionality of intelligent software often requires continuous upgrades. Therefore, software developers need to periodically release updated versions of intelligent software to meet user needs.

[0003] However, due to the diversity of devices and software, the abundance of software versions, and the diversity of release statuses, software version upgrade queries are difficult. Therefore, a method is needed to quickly and easily find device software upgrade package information.

[0004] In addition, since different devices have different software update times and are often in different release groups, different software versions will be upgraded to different versions. Therefore, multiple software update tasks for different devices need to be independent of each other and not affect each other.

[0005] Therefore, a software upgrade query method based on multi-task and multi-version is proposed. Summary of the Invention

[0006] The present invention aims to solve at least one of the technical problems existing in the prior art. To this end, the present invention proposes a software upgrade query method based on multiple tasks and multiple versions. The software upgrade query method based on multiple tasks and multiple versions uses information such as project name, device number, vehicle platform, software type and version number to request vehicle upgrade information from the server backend. After receiving the query request data, the server backend obtains the query condition information, queries the software upgrade package information records that meet the project name, vehicle platform and software type conditions from the software upgrade package information table, calculates the software upgrade package information, calculates the task release information, calculates the grayscale device information, calculates the software version number information, etc., and finally returns the software upgrade package information that meets the requirements. The method solves the problem of how to quickly find the query of device software upgrade package information and the problem of multi-task independent upgrade of different devices.

[0007] To achieve the above object, according to an embodiment of the first aspect of the present invention, a software upgrade query method based on multiple tasks and multiple versions is proposed, comprising the following steps:

[0008] Step 1: The server uploads all software upgrade package information and constructs a software upgrade package information table to save the software upgrade package information;

[0009] Step 2: Create a grayscale device group table on the server backend and add or import grayscale device information to the grayscale device group table.

[0010] Step 3: The server background creates task release information and constructs a task release table to save the task release information;

[0011] Step 4: The application terminal requests the server backend for upgrade information using information such as the project name, device number, vehicle platform, software type, and software version number. If the query is successful, the software upgrade package download address and other information will be returned. If the query fails, no upgrade information will be returned.

[0012] The application terminal requests the server backend to query the upgrade information, which includes the following steps:

[0013] Step S1: The server backend queries the software upgrade package information table to search for software upgrade package information records that match the project name, vehicle platform, and software type. It is understandable that the query result may be one record or multiple multi-version software record sets V1, V2, V3...Vn of the same type; that is, records of different software version numbers of the same software recorded in the software upgrade package information table; wherein, V1, V2, V3...Vn are version numbers of the same type of software sorted in chronological order, and Vn is the latest version number.

[0014] Step S2: polling the above software upgrade package information; for any record Vi, querying the task release information table to query the release information record of the project name, vehicle platform, and software type that meets the conditions; where i = 1, 2, ..., n;

[0015] It is understandable that the queried software release record may be one or more task release record sets P1, P2, P3, ..., Pm of the same type; query whether the software upgrade package Vi information is in the task release record and whether it is in the full release or phased release status; where m is the number of all release records of the same software in the task release information table; poll all task release record sets; for any task release record Pj therein, execute steps S3-S4; where j = 1, 2, ..., m;

[0016] Step S3: The application terminal uploads the device to be updated and the version number Vc of its corresponding software; determines whether the release status in the task release record Pj is a phased release or a full release;

[0017] If the release status is full release, the software version number Vc uploaded by the application terminal is compared with the software version number Vs recorded in the release task record Pj; if the terminal software version number Vc is less than the release software version number Vj, the query returns that the upgrade is successful; otherwise, if the terminal software version number Vc is greater than or equal to the release software version number Vj, the query returns that the upgrade failed;

[0018] If the release status is grayscale release, query the grayscale device group ID in the release task record Pj, and then obtain the corresponding grayscale device list information from the grayscale device group table based on the grayscale device ID to determine whether the device number uploaded by the terminal is in this grayscale device record; if the device exists in the grayscale information, compare the terminal version Vc with the software version number Vs of the release task record Pj. If the terminal software version number Vc is less than the release software version number Vs, return a query success; otherwise, if the terminal software version number Vc is greater than or equal to the release software version number Vs, return a query failure.

[0019] Step S4: When the query for upgrade information is successful, the software version information is returned, including software ID, software name, vehicle platform, software type, software version number, release time and download address.

[0020] Compared with the prior art, the present invention has the following beneficial effects:

[0021] The application terminal of the present invention requests vehicle upgrade information from the server background through information such as project name, device number, vehicle platform, software type and version number. After receiving the query request data, the server background obtains the query condition information, queries the software upgrade package information record that meets the project name, vehicle platform and software type conditions from the software upgrade package information table, calculates the software upgrade package information, calculates the task release information, calculates the grayscale device information, calculates the software version number information, etc., and finally returns the software upgrade package information that meets the requirements; it solves the problem of how to quickly find the query of device software upgrade package information and the problem of multi-task independent upgrade of different devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 Flowchart of the present invention. DETAILED DESCRIPTION

[0023] The technical solutions of the present invention will be clearly and completely described below in conjunction with the embodiments. Obviously, the embodiments described are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.

[0024] like Figure 1As shown, a software upgrade query method based on multi-task and multi-version includes the following steps:

[0025] Step 1: The server uploads all software upgrade package information and constructs a software upgrade package information table to save the software upgrade package information;

[0026] Step 2: Create a grayscale device group table on the server backend and add or import grayscale device information to the grayscale device group table.

[0027] Step 3: The server background creates task release information and constructs a task release table to save the task release information;

[0028] Step 4: The application terminal requests the server backend for upgrade information using the project name, device number, vehicle platform, software type, and software version number. If the query is successful, the software upgrade package download address and other information will be returned. If the query fails, no upgrade information will be returned.

[0029] The software upgrade package information includes software ID, software name, project, vehicle platform, software type, software version number and download address;

[0030] The software upgrade package information table can be constructed using a relational database; the construction method is to use the software ID as the primary key and the project, vehicle platform, software type, software version number and download address as attributes; the relational database can be MySQL, Oracle and SQL Server;

[0031] The grayscale device information includes the grayscale device group ID and the grayscale device list; the grayscale device group is used to manage the device numbers involved in a software upgrade; the grayscale device group ID is the updated version number; for example, V1 indicates the first software update; the grayscale device list is a list of device numbers upgraded for each version update;

[0032] The task release information includes the task ID, vehicle platform, software type, software version number, grayscale device group ID, release status, release time, and publisher;

[0033] The task release table can be constructed using a relational database; the construction method is to use the software ID as the primary key, and the vehicle platform, software type, software version number, grayscale device group ID, release status, release time, and publisher as attributes; wherein the release status includes unreleased, grayscale release, and full release;

[0034] It is understandable that each software recorded in the task release information table may not contain all software version numbers; for example, some versions of some software cannot be released due to some subjective and objective reasons;

[0035] Furthermore, the grayscale device group ID in the task release information table is entered only when the release status is grayscale release. If the release status is unreleased or fully released, the grayscale device group ID can be left blank.

[0036] The application terminal requests the server backend to query the upgrade information, which includes the following steps:

[0037] Step S1: The server backend queries the software upgrade package information table to search for software upgrade package information records that match the project name, vehicle platform, and software type. It is understandable that the query result may be one record or multiple multi-version software record sets V1, V2, V3...Vn of the same type; that is, records of different software version numbers of the same software recorded in the software upgrade package information table; wherein, V1, V2, V3...Vn are version numbers of the same type of software sorted in chronological order, and Vn is the latest version number.

[0038] Step S2: polling the above software upgrade package information; for any record Vi, querying the task release information table to query the release information record of the project name, vehicle platform, and software type that meets the conditions; where i = 1, 2, ..., n;

[0039] It is understandable that the queried software release record may be one or more task release record sets P1, P2, P3, ..., Pm of the same type; query whether the software upgrade package Vi information is in the task release record and whether it is in the full release or phased release status; where m is the number of all release records of the same software in the task release information table; poll all task release record sets; for any task release record Pj therein, execute steps S3-S4; where j = 1, 2, ..., m;

[0040] Step S3: The application terminal uploads the device to be updated and the version number Vc of its corresponding software; determines whether the release status in the task release record Pj is a phased release or a full release;

[0041] If the release status is full release, the software version number Vc uploaded by the application terminal is compared with the software version number Vs recorded in the release task record Pj; if the terminal software version number Vc is less than the release software version number Vj, the query returns that the upgrade is successful; otherwise, if the terminal software version number Vc is greater than or equal to the release software version number Vj, the query returns that the upgrade failed;

[0042] If the release status is grayscale release, query the grayscale device group ID in the release task record Pj, and then obtain the corresponding grayscale device list information from the grayscale device group table based on the grayscale device ID to determine whether the device number uploaded by the terminal is in this grayscale device record; if the device exists in the grayscale information, compare the terminal version Vc with the software version number Vs of the release task record Pj. If the terminal software version number Vc is less than the release software version number Vs, return a query success; otherwise, if the terminal software version number Vc is greater than or equal to the release software version number Vs, return a query failure.

[0043] Step S4: When the query for upgrade information is successful, the software version information is returned, including software ID, software name, vehicle platform, software type, software version number, release time and download address.

[0044] The above embodiments are only used to illustrate the technical method of the present invention and are not intended to limit the present invention. Although the present invention has been described in detail with reference to the preferred embodiments, those skilled in the art should understand that the technical method of the present invention may be modified or replaced by equivalents without departing from the spirit and scope of the technical method of the present invention.

Claims

1. A software upgrade query method based on multi-task and multi-version, characterized in that: The following steps are involved: Step 1: The server uploads all software upgrade package information and constructs a software upgrade package information table to save the software upgrade package information; Step 2: Create a grayscale device group table on the server backend and add or import grayscale device information to the grayscale device group table. Step 3: The server background creates task release information and constructs a task release table to save the task release information; Step 4: The application terminal requests the server backend for upgrade information by entering the project name, device number, vehicle platform, software type, and software version number; If the query is successful, the software upgrade package information will be returned; if the query fails, no upgrade information will be returned; The application terminal requests the server backend to query the upgrade information, including the following steps: Step S1: The server backend queries the software upgrade package information table to search for software upgrade package information records that match the project name, vehicle platform, and software type. The query results in a set of multiple versions of the same type of software, V1, V2, V3, ..., Vn. V1, V2, V3, ..., Vn are the version numbers of the same type of software sorted in chronological order, with Vn being the latest version number. Step S2: poll the above software upgrade package information; for any record Vi, query the task release information table to query the release information record of the project name, vehicle platform, and software type that meet the conditions; where i=1, 2, ..., n; The queried software release records are multiple sets of task release records of the same type, P1, P2, P3, ..., Pm. Query whether the software upgrade package Vi information is in the task release record and whether it is in a full release or phased release state. Where m is the number of all release records for the same software in the task release information table. Poll all task release record sets. For any task release record Pj, execute steps S3-S4. Where j = 1, 2, ..., m. Step S3: The application terminal uploads the device to be updated and the version number Vc of its corresponding software; determines whether the release status in the task release record Pj is a phased release or a full release; If the release status is full release, compare the software version number Vc uploaded by the application terminal with the software version number Vs recorded in the release task record Pj; if the terminal software version number Vc is less than the release software version number Vj, return a query success; otherwise, if the terminal software version number Vc is greater than or equal to the release software version number Vj, return a query failure; If the release status is grayscale release, query the grayscale device group ID in the release task record Pj, and then obtain the corresponding grayscale device list information from the grayscale device group table based on the grayscale device ID to determine whether the device number uploaded by the terminal is in this grayscale device record; if the device exists in this grayscale device record, compare the terminal version Vc with the software version number Vs of the release task record Pj. If the terminal software version number Vc is less than the release software version number Vs, return a query success; otherwise, if the terminal software version number Vc is greater than or equal to the release software version number Vs, return a query failure. Step S4: When the query for upgrade information is successful, the software version information is returned.

2. The software upgrade query method based on multi-task and multi-version according to claim 1, characterized in that: The software upgrade package information includes software ID, project, vehicle platform, software type, software version number and download address.

3. The software upgrade query method based on multi-task and multi-version according to claim 1, characterized in that: The grayscale device information includes a grayscale device group ID and a grayscale device list; the grayscale device group ID is an updated version number.

4. The software upgrade query method based on multi-task and multi-version according to claim 1, characterized in that: The task release information includes task ID, software name, vehicle platform, software type, software version number, grayscale device group ID, release status, release time and publisher.

5. The software upgrade query method based on multi-task and multi-version according to claim 1, characterized in that: The software version information includes software ID, software name, vehicle platform, software type, software version number, release time and download address.

Images