Software version upgrade method, device, computer equipment and storage medium

Abstract

The present application relates to a software version upgrade method, device, computer equipment and storage medium. The method includes: obtaining a configuration file to be upgraded of the software to be upgraded, storing the version identifier and preset upgrade time of the configuration file to be upgraded in a database; the database also stores the actual upgrade time of multiple historical configuration files of the software to be upgraded; obtaining the input target version identifier and the target upgrade time corresponding to the target version identifier; when the version identifier of the configuration file to be upgraded matches the target version identifier, updating the preset upgrade time of the configuration file to be upgraded to the target upgrade time, and obtaining the actual upgrade time of the updated configuration file to be upgraded; from the updated configuration file to be upgraded and multiple historical configuration files, filtering out the configuration file with the latest actual upgrade time as the target configuration file of the software to be upgraded. The use of this method can improve the flexibility of software version upgrades.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a software version upgrade method, apparatus, computer equipment, storage medium and computer program product. Background Art

[0002] With the development of banking business, the number of internal application systems of banks is growing day by day, and the scale of data exchange between multiple systems is also gradually increasing, with the daily data exchange scale reaching hundreds of TB (Terabyte). In order to maintain the performance of internal banking systems, it is necessary to regularly upgrade the data exchange system. However, the files involved in the version upgrade of the data exchange system can reach tens of thousands, which greatly increases the complexity of software version upgrade. In addition, as the development cycle of data exchange systems continues to shorten, the requirements for system production time are also getting shorter and shorter.

[0003] Traditional software version upgrades generally use software versions with fixed upgrade times, but software versions with fixed upgrade times are no longer suitable for data exchange systems with flexible production time changes. If software versions with fixed upgrade times continue to be used, when the upgrade time is suddenly changed during the bank's internal research and development process, the released software version can only be rolled back and released again after the upgrade time is modified, which reduces the efficiency of software version upgrades and limits the software upgrade time. Summary of the invention

[0004] Based on this, it is necessary to provide a software version upgrade method, apparatus, computer device, storage medium and computer program product that can improve the flexibility of software version upgrade in order to address the above technical problems.

[0005] In a first aspect, the present application provides a software version upgrade method, the method comprising:

[0006] Obtaining a configuration file to be upgraded of the software to be upgraded, and storing the version identifier and preset upgrade time of the configuration file to be upgraded in a database; the database also stores actual upgrade times of multiple historical configuration files of the software to be upgraded;

[0007] Obtaining an input target version identifier and a target upgrade time corresponding to the target version identifier;

[0008] When the version identifier of the configuration file to be upgraded matches the target version identifier, updating the preset upgrade time of the configuration file to be upgraded to the target upgrade time, and obtaining the actual upgrade time of the updated configuration file to be upgraded;

[0009] The configuration file with the latest actual upgrade time is screened out from the updated configuration file to be upgraded and the multiple historical configuration files as the target configuration file of the software to be upgraded.

[0010] In one embodiment, obtaining a configuration file to be upgraded of the software to be upgraded, and storing a version identifier and a preset upgrade time of the configuration file to be upgraded in a database includes:

[0011] Obtaining a configuration file of the software to be upgraded, and modifying the configuration file multiple times to obtain multiple modified configuration files of the configuration file;

[0012] Filtering the configuration file to be upgraded from the multiple modified configuration files; the configuration file to be upgraded is the modified configuration file obtained by the last modification;

[0013] The version identifier and the preset upgrade time of the configuration file to be upgraded are read out, and the version identifier and the preset upgrade time are stored in the database.

[0014] In one embodiment, obtaining an input target version identifier and a target upgrade time corresponding to the target version identifier includes:

[0015] Receiving an upgrade task for the software to be upgraded;

[0016] The target version identifier and the target upgrade time corresponding to the target version identifier are extracted from the upgrade task.

[0017] In one of the embodiments, when the version identifier of the configuration file to be upgraded matches the target version identifier, before updating the preset upgrade time of the configuration file to be upgraded to the target upgrade time and obtaining the actual upgrade time of the configuration file to be upgraded, the method further includes:

[0018] Querying the database to obtain a version identifier that matches the target version identifier;

[0019] Updating the actual upgrade time corresponding to the version identifier matching the target version identifier in the database to the target upgrade time;

[0020] When the version identifier of the configuration file to be upgraded matches the target version identifier, updating the preset upgrade time of the configuration file to be upgraded to the target upgrade time includes:

[0021] When the version identifier of the configuration file to be upgraded matches the target version identifier, the preset upgrade time of the configuration file to be upgraded is updated to the target upgrade time stored in the database.

[0022] In one embodiment, after obtaining the actual update time of the updated configuration file to be updated, the method further includes:

[0023] querying and obtaining, from the plurality of historical configuration files, a historical configuration file that matches the updated configuration file to be upgraded;

[0024] The effective time of the historical configuration file matching the updated configuration file to be upgraded is adjusted to the difference between the actual upgrade time of the updated configuration file to be upgraded and the preset threshold.

[0025] In one embodiment, the configuration file with the latest actual upgrade time is selected from the updated configuration file to be upgraded and the multiple historical configuration files as the target configuration file of the software to be upgraded, including:

[0026] querying the actual upgrade time stored in the database to obtain the latest actual upgrade time and the version identifier corresponding to the latest actual upgrade time;

[0027] A configuration file matching the version identifier corresponding to the latest actual upgrade time is queried from the updated configuration file to be upgraded and the multiple historical configuration files as the target configuration file for the software to be upgraded.

[0028] In one embodiment, after selecting the configuration file with the latest actual upgrade time from the updated configuration file to be upgraded and the multiple historical configuration files as the target configuration file for the software to be upgraded, the method further includes:

[0029] When it is detected that the target configuration file is an actual upgrade file of the software to be upgraded, generating operation data corresponding to the target configuration file;

[0030] The software to be upgraded is upgraded according to the operating data corresponding to the target configuration file.

[0031] In a second aspect, the present application further provides a software version upgrade device, the device comprising:

[0032] The file acquisition module is used to acquire the configuration file to be upgraded of the software to be upgraded, and store the version identification and preset upgrade time of the configuration file to be upgraded in a database; the database also stores the actual upgrade time of multiple historical configuration files of the software to be upgraded;

[0033] A time acquisition module, used to acquire an input target version identifier and a target upgrade time corresponding to the target version identifier;

[0034] An update time module, configured to update the preset update time of the configuration file to be upgraded to the target upgrade time when the version identifier of the configuration file to be upgraded matches the target version identifier, so as to obtain the actual upgrade time of the configuration file to be upgraded;

[0035] The file screening module is used to screen out the configuration file with the latest actual upgrade time from the configuration file to be upgraded and the multiple historical configuration files as the target configuration file of the software to be upgraded.

[0036] In a third aspect, the present application further provides a computer device. The computer device includes a memory and a processor, the memory stores a computer program, and the processor implements the following steps when executing the computer program:

[0037] Obtaining a configuration file to be upgraded of the software to be upgraded, and storing the version identifier and preset upgrade time of the configuration file to be upgraded in a database; the database also stores actual upgrade times of multiple historical configuration files of the software to be upgraded;

[0038] Obtaining an input target version identifier and a target upgrade time corresponding to the target version identifier;

[0039] When the version identifier of the configuration file to be upgraded matches the target version identifier, updating the preset upgrade time of the configuration file to be upgraded to the target upgrade time, and obtaining the actual upgrade time of the updated configuration file to be upgraded;

[0040] The configuration file with the latest actual upgrade time is screened out from the updated configuration file to be upgraded and the multiple historical configuration files as the target configuration file of the software to be upgraded.

[0041] In a fourth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0042] Obtaining a configuration file to be upgraded of the software to be upgraded, and storing the version identifier and preset upgrade time of the configuration file to be upgraded in a database; the database also stores actual upgrade times of multiple historical configuration files of the software to be upgraded;

[0043] Obtaining an input target version identifier and a target upgrade time corresponding to the target version identifier;

[0044] When the version identifier of the configuration file to be upgraded matches the target version identifier, updating the preset upgrade time of the configuration file to be upgraded to the target upgrade time, and obtaining the actual upgrade time of the updated configuration file to be upgraded;

[0045] The configuration file with the latest actual upgrade time is screened out from the updated configuration file to be upgraded and the multiple historical configuration files as the target configuration file of the software to be upgraded.

[0046] In a fifth aspect, the present application further provides a computer program product. The computer program product includes a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0047] Obtaining a configuration file to be upgraded of the software to be upgraded, and storing the version identifier and preset upgrade time of the configuration file to be upgraded in a database; the database also stores actual upgrade times of multiple historical configuration files of the software to be upgraded;

[0048] Obtaining an input target version identifier and a target upgrade time corresponding to the target version identifier;

[0049] When the version identifier of the configuration file to be upgraded matches the target version identifier, updating the preset upgrade time of the configuration file to be upgraded to the target upgrade time, and obtaining the actual upgrade time of the updated configuration file to be upgraded;

[0050] The configuration file with the latest actual upgrade time is screened out from the updated configuration file to be upgraded and the multiple historical configuration files as the target configuration file of the software to be upgraded.

[0051] The software version upgrade method, device, computer equipment and storage medium store the version identification and preset upgrade time of the configuration file to be upgraded in a database according to the configuration file to be upgraded of the acquired software to be upgraded, then obtain the input target version identification and the target upgrade time corresponding to the target version identification, and when the version identification of the configuration file to be upgraded matches the target version identification, update the preset upgrade time of the configuration file to be upgraded to the target upgrade time, obtain the actual upgrade time of the updated configuration file to be upgraded, and finally filter out the configuration file with the latest actual upgrade time from the updated configuration file to be upgraded and multiple historical configuration files as the target configuration file of the software to be upgraded. With this method, there is no need to predetermine the actual upgrade time of the configuration file to be upgraded, and by updating the preset upgrade time of the configuration file to be upgraded to the actual upgrade time, the upgrade time of the configuration file to be upgraded can be changed in real time according to actual development needs, thereby improving the flexibility of software version upgrade. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] Figure 1 An application environment diagram of a software version upgrade method in an embodiment;

[0053] Figure 2A flowchart of a method for upgrading a software version in one embodiment;

[0054] Figure 3 It is a flowchart of a method for upgrading a software version in another embodiment;

[0055] Figure 4 It is a flowchart of a method for upgrading a software version in another embodiment;

[0056] Figure 5 A flowchart of the steps of a data verification module and a version configuration module in one embodiment;

[0057] Figure 6 It is a structural block diagram of a software version upgrading device in one embodiment;

[0058] Figure 7 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0059] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0060] The software version upgrade method provided in this application can be applied to Figure 1 In the application environment shown. Among them, the server 101 communicates with the terminal 102 and the database 103 through the network, and the database 103 is used to store the version identification, preset upgrade time and actual upgrade time of each configuration file of the software to be upgraded. Specifically, refer to Figure 1 , the server 101 obtains the configuration file to be upgraded of the software to be upgraded, stores the version identifier and preset upgrade time of the configuration file to be upgraded in the database 103, the server 101 receives the target version identifier and the target upgrade time corresponding to the target version identifier input by the terminal 102, when the version identifier of the configuration file to be upgraded matches the target version identifier, the server 101 updates the preset upgrade time of the configuration file to be upgraded to the target upgrade time, obtains the actual upgrade time of the updated configuration file to be upgraded, and the server 101 selects the configuration file with the latest actual upgrade time from the updated configuration file to be upgraded and multiple historical configuration files as the target configuration file of the software to be upgraded. Among them, the terminal 102 can be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, Internet of Things devices and portable wearable devices, and the Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart car-mounted devices, etc. The portable wearable device can be a smart watch, a smart bracelet, a head-mounted device, etc. The server 101 can be implemented by an independent server or a server cluster composed of multiple servers.

[0061] In one embodiment, Figure 2 As shown, a software version upgrade method is provided, which is applied to Figure 1 The server in the example is used to illustrate the following steps:

[0062] Step S201, obtaining a configuration file to be upgraded of the software to be upgraded, and storing the version identifier and preset upgrade time of the configuration file to be upgraded in a database; the database also stores actual upgrade times of multiple historical configuration files of the software to be upgraded.

[0063] Among them, the software to be upgraded is the software that needs to be upgraded in the internal system of the banking industry. The configuration file to be upgraded refers to the configuration file newly developed according to the upgrade task of the software to be upgraded. The configuration file to be upgraded includes the closed board configuration file and the daily patch configuration file of the software to be upgraded. The upgrade time of the configuration file to be upgraded can be adjusted according to the actual upgrade task. The closed board configuration file refers to the configuration file of the software upgrade version obtained after a preset period of research and development, which is used for the periodic upgrade of the software to be upgraded. The daily patch configuration file refers to the patch upgrade configuration file of the software to be upgraded, which is used for the daily upgrade of the software to be upgraded.

[0064] Among them, the historical configuration file refers to the configuration file that has been upgraded for the software to be upgraded. The version identifier refers to the version number information of the configuration file, which is used to distinguish the version of the configuration file, and the version identifier includes the version number. The preset upgrade time refers to the timestamp of the virtual upgrade time, which is used to set a temporary virtual timestamp for the configuration file to be upgraded. The database stores the version identifiers, preset upgrade times, actual upgrade times and requirement numbers of the various historical configuration files of the software to be upgraded and the configuration files to be upgraded.

[0065] Specifically, the server exports the file information of the software to be upgraded from the metadata database, generates a corresponding configuration file to be upgraded based on the file information of the software to be upgraded, and stores the configuration file to be upgraded in a preset directory; obtains the file format, basic information and configuration information of the configuration file to be upgraded from the configuration file to be upgraded, and then the server obtains the version identifier and preset upgrade time of the configuration file to be upgraded, and then stores the version identifier and the preset upgrade time in a table in the database.

[0066] For example, the file format of the configuration file to be upgraded is: file name_source interface_target interface_version number_preset timestamp.BIN. The configuration file to be upgraded includes basic information of the file source interface and target interface, file addition (deletion) identification, field information, field filtering information, upstream and downstream information, file transfer approval ID and other basic information of the configuration content.

[0067] Step S202: Obtain the input target version identifier and the target upgrade time corresponding to the target version identifier.

[0068] The target version identifier refers to the version identifier of the target upgrade version set by the R&D personnel or management personnel according to the upgrade task of the software to be upgraded. The target upgrade time refers to the timestamp of the upgrade time of the target upgrade version set by the R&D personnel or management personnel according to the upgrade task of the software to be upgraded.

[0069] Specifically, the R&D personnel or management personnel input the target version identifier and the target upgrade time corresponding to the target version identifier into the server through the terminal, and the server receives the target version identifier and the target upgrade time corresponding to the target version identifier. Thus, after obtaining the target version identifier and the target upgrade time corresponding to the target version identifier, the server uses the target version identifier and the target upgrade time corresponding to the target version identifier as a matching basis to perform subsequent software version upgrade steps.

[0070] Step S203: when the version identifier of the configuration file to be upgraded matches the target version identifier, the preset upgrade time of the configuration file to be upgraded is updated to the target upgrade time, and the actual upgrade time of the updated configuration file to be upgraded is obtained.

[0071] Specifically, the server determines whether the version identifier of the configuration file to be upgraded stored in the database matches the target version identifier. If the version identifier of the configuration file to be upgraded stored in the database matches the target version identifier, the target upgrade time is stored in the database as the actual upgrade time of the configuration file to be upgraded. The configuration file to be upgraded is then updated, and the preset upgrade time of the configuration file to be upgraded is updated to the target upgrade time to obtain an updated configuration file to be upgraded.

[0072] Step S204: Filter out the configuration file with the latest actual upgrade time from the updated configuration file to be upgraded and the multiple historical configuration files as the target configuration file for the software to be upgraded.

[0073] Specifically, the database filters out the latest actual upgrade time from the actual upgrade times corresponding to the stored updated configuration files to be upgraded and multiple historical configuration files, and obtains the version identifier corresponding to the latest actual upgrade time, and then sends the latest actual upgrade time and the version identifier corresponding to the latest actual upgrade time to the server, and then the server receives and obtains the corresponding configuration file through the version identifier query as the target configuration file for the software to be upgraded, stores the target configuration file in a preset directory, and when the actual upgrade time of the target configuration file is reached, the version of the software to be upgraded is upgraded.

[0074] In the above software version upgrade method, according to the configuration file to be upgraded of the acquired software to be upgraded, the version identifier and preset upgrade time of the configuration file to be upgraded are stored in the database, and then the input target version identifier and the target upgrade time corresponding to the target version identifier are obtained. When the version identifier of the configuration file to be upgraded matches the target version identifier, the preset upgrade time of the configuration file to be upgraded is updated to the target upgrade time to obtain the actual upgrade time of the updated configuration file to be upgraded. Finally, from the updated configuration file to be upgraded and multiple historical configuration files, the configuration file with the latest actual upgrade time is screened out as the target configuration file of the software to be upgraded. With this method, there is no need to predetermine the actual upgrade time of the configuration file to be upgraded. By updating the preset upgrade time of the configuration file to be upgraded to the actual upgrade time, the upgrade time of the configuration file to be upgraded can be changed in real time according to actual development needs, thereby improving the flexibility of software version upgrade.

[0075] In one embodiment, the above step S201, obtaining the configuration file to be upgraded of the software to be upgraded, and storing the version identification and preset upgrade time of the configuration file to be upgraded in a database, specifically includes the following steps: obtaining the configuration file of the software to be upgraded, modifying the configuration file multiple times to obtain multiple modified configuration files of the configuration file; filtering out the configuration file to be upgraded from the multiple modified configuration files; the configuration file to be upgraded is the modified configuration file obtained by the last modification; reading out the version identification and preset upgrade time of the configuration file to be upgraded, and storing the version identification and the preset upgrade time in the database.

[0076] Specifically, the server uses an export tool to export data information of the software to be upgraded from the metadata database, obtains the configuration file of the software to be upgraded, stores the configuration file in a temporary directory, and adds, modifies or deletes the configuration file according to the upgrade task of the software to be upgraded. After each processing, a modified configuration file is generated and the file transfer approval ID of the modified configuration file is recorded, and multiple modified configuration files are obtained after processing; the file transfer approval IDs of the multiple modified configuration files are detected, and the modified configuration file obtained by the last modification, that is, the configuration file corresponding to the last file transfer approval ID is retained as the configuration file to be upgraded and the timestamp of the preset upgrade time of the configuration file to be upgraded is set, and the configuration file to be upgraded is stored in the preset directory; data reading processing is performed on the configuration file to be upgraded through the file reading instruction, and the version identification and preset upgrade time of the configuration file to be upgraded are read, and the version identification and preset upgrade time of the configuration file to be upgraded are stored in the table of the database.

[0077] For example, the version identifier of the configuration file to be upgraded and the preset upgrade time are stored in the table cfg_validTime of the database. The field structure of the table is shown in Table 1:

[0078] Table 1

[0079] Field Name Field Type use APPVER VARCHAR2 Version number, used to distinguish the production time of different configuration files. DEPLOYDATE VARCHAR2 The production time corresponding to the version number. YTIME VARCHAR2 The preset production time corresponding to the version number. REITEMID VARCHAR2 Requirement number, reserved field.

[0080] It should be noted that, due to the rapid iteration of the upgrade requirements in the development process of the software to be upgraded, the configuration file to be upgraded at this time may not have obtained the actual upgrade time, or the configuration file to be upgraded has obtained the actual upgrade time but needs to be modified later as the upgrade task changes. Therefore, a virtual preset upgrade time (YTIME) is set for the configuration file to be upgraded. Assuming that the actual upgrade time of the current configuration file to be upgraded is T, the preset upgrade time can be set to T, T-1, T-2, T+1, T+2, etc., and of course it can also be adjusted according to the actual situation, and no specific limitation is made here. If the actual upgrade time (DEPLOYDATE) of the configuration file to be upgraded has not been obtained at this time, the actual upgrade time corresponding to the version identifier (APPVER) of the configuration file to be upgraded in the database can be set to T, or a null value (NULL), or filled with a random number.

[0081] In this embodiment, a configuration file to be upgraded of the software to be upgraded is obtained, and the version identifier and the preset upgrade time are stored in a database. By adopting this method, there is no need to set a fixed upgrade time in the configuration file to be upgraded in advance. By setting a timestamp of the preset upgrade time for the configuration file to be upgraded, and by updating the preset upgrade time of the configuration file to be upgraded to the actual upgrade time, the upgrade time of the configuration file to be upgraded can be changed in real time according to actual development needs, thereby improving the flexibility of software version upgrade, and there is no need to roll back and modify the actual upgrade time of the configuration file to be upgraded. The subsequent update of the actual upgrade time can be quickly realized through the table structure of the database, thereby reducing the update processing time of the target configuration file, and further improving the flexibility of software version upgrade.

[0082] In one embodiment, the above step S202, obtaining the input target version identifier and the target upgrade time corresponding to the target version identifier, specifically includes the following steps: receiving an upgrade task for the software to be upgraded; and extracting the target version identifier and the target upgrade time corresponding to the target version identifier from the upgrade task.

[0083] Specifically, when the R&D personnel or management personnel need to upgrade the software version of the software to be upgraded, an upgrade request is initiated on the terminal, and the terminal responds to the request, generates an upgrade task for the software to be upgraded, and sends the upgrade task to the server. Then, the server receives the upgrade task, performs data extraction processing on the upgrade task, and obtains the target version identifier in the upgrade task and the target upgrade time corresponding to the target version identifier. Thus, after obtaining the target version identifier and the target upgrade time corresponding to the target version identifier, the server uses the target version identifier and the target upgrade time corresponding to the target version identifier as the update basis to perform subsequent software version upgrade steps. For example, the server obtains configuration information in the format of "version number_preset timestamp_actual timestamp.TXT", extracts the version number and actual timestamp from the configuration information, and stores the extracted version number and actual timestamp in the database for version upgrade of the software to be upgraded. The configuration information can be updated with the change of the upgrade task.

[0084] In this embodiment, the server obtains the upgrade task sent for the software to be upgraded, and extracts the target version identifier and the target upgrade time corresponding to the target version identifier. With this method, there is no need to predetermine the actual upgrade time of the configuration file to be upgraded. The configuration file to be upgraded is matched according to the target version identifier, and the preset upgrade time of the configuration file to be upgraded is updated to the target upgrade time, so that the upgrade time of the configuration file to be upgraded can be changed in real time according to actual development needs, thereby improving the flexibility of software version upgrades.

[0085] In one embodiment, before the preset upgrade time of the configuration file to be upgraded is updated to the target upgrade time and the actual upgrade time of the configuration file to be upgraded is obtained when the version identifier of the configuration file to be upgraded matches the target version identifier, the method further includes: querying and obtaining a version identifier matching the target version identifier from a database; updating the actual upgrade time corresponding to the version identifier matching the target version identifier in the database to the target upgrade time; the above step S203, when the version identifier of the configuration file to be upgraded matches the target version identifier, updating the preset upgrade time of the configuration file to be upgraded to the target upgrade time and obtaining the updated actual upgrade time of the configuration file to be upgraded, specifically includes the following content: when the version identifier of the configuration file to be upgraded matches the target version identifier, updating the preset upgrade time of the configuration file to be upgraded to the target upgrade time stored in the database.

[0086] Specifically, the server generates a version identifier query instruction, queries in the database to obtain a version identifier that matches the target version identifier, and then generates a data modification instruction to modify the actual upgrade time corresponding to the version identifier that matches the target version identifier in the database to the target upgrade time; obtains the version identifier of the configuration file stored in the preset directory through a judgment tool, including the version identifier of the configuration file to be upgraded and the version identifier of the historical configuration file, and generates a corresponding identifier matching instruction according to the target version identifier. All configuration files stored in the preset directory are matched through the identifier matching instruction. When the version identifier of the configuration file to be upgraded matches the target version identifier, the preset upgrade time of the configuration file to be upgraded in the preset directory is updated to the target upgrade time stored in the database.

[0087] For example, the original file format of the configuration file to be upgraded is: file name_source interface_target interface_version number_preset timestamp.BIN. After the preset upgrade time of the configuration file to be upgraded is updated to the target upgrade time stored in the database, the file format of the updated configuration file to be upgraded is: file name_source interface_target interface_version number_target upgrade time.BIN.

[0088] In this embodiment, the version identifier that matches the target version identifier is obtained by querying the database, and the actual upgrade time corresponding to the version identifier in the database is updated to the target upgrade time. When the version identifier of the configuration file to be upgraded in the preset directory matches the target version identifier in the database, the preset upgrade time of the configuration file to be upgraded in the preset directory is updated to the target upgrade time stored in the database. With this method, there is no need to roll back and modify the configuration file to be upgraded. The timestamp update of the actual upgrade time of the configuration file to be upgraded is realized through the connected database, which reduces the update processing time of the actual upgrade time and improves the flexibility of software version upgrade.

[0089] In one embodiment, after obtaining the actual upgrade time of the configuration file to be upgraded, the method further includes: querying and obtaining a historical configuration file matching the updated configuration file to be upgraded from multiple historical configuration files; and adjusting the effective time of the historical configuration file matching the updated configuration file to be upgraded to the difference between the actual upgrade time of the updated configuration file to be upgraded and a preset threshold.

[0090] The historical configuration file that matches the updated configuration file to be upgraded refers to a configuration file whose file name, source interface, and target interface all match the updated configuration file to be upgraded, for example, a configuration file of the current version of the software to be upgraded.

[0091] Specifically, after the preset upgrade time of the configuration file to be upgraded is updated to the target upgrade time stored in the database, the server queries from multiple historical configuration files to obtain a historical configuration file whose file name, source interface, and target interface all match the updated configuration file to be upgraded, and then adjusts the effective time of the historical configuration file that matches the updated configuration file to be upgraded to the difference between the actual upgrade time of the updated configuration file to be upgraded and the preset threshold value, to obtain the adjusted historical configuration file of the configuration file to be upgraded, which is used as the historical configuration file of the subsequent business of the software to be upgraded, so that the business personnel can view or use the historical data of the software to be upgraded. Among them, the preset threshold value can be set to 1, 2, 3, etc., and of course it can also be adjusted according to the actual situation, which is not specifically limited here.

[0092] For example, the effective time of the adjusted historical configuration file of the configuration file to be upgraded is the actual upgrade time of the configuration file to be upgraded minus one day. When the historical configuration file of the configuration file to be upgraded expires, the configuration file to be upgraded is upgraded. At the same time, the historical configuration file of the configuration file to be upgraded can also be stored as the historical version data of the software to be upgraded.

[0093] In this embodiment, a historical configuration file matching the updated configuration file to be upgraded is queried from multiple historical configuration files, and the effective time of the historical configuration file matching the updated configuration file to be upgraded is adjusted. With this method, there is no need to manually replace the configuration file of the current version of the software to be upgraded, and the configuration file can be automatically stopped when the effective date of the configuration file expires, and the upgrade process can be performed when the actual upgrade time of the configuration file to be upgraded is reached, thereby reducing the manpower and time costs required for upgrading the software to be upgraded and improving the flexibility of software version upgrades.

[0094] In one embodiment, the above step S204, screening out the configuration file with the latest actual upgrade time from the updated configuration file to be upgraded and multiple historical configuration files as the target configuration file for the software to be upgraded, specifically includes the following contents: querying and obtaining the latest actual upgrade time and the version identifier corresponding to the latest actual upgrade time from the actual upgrade time stored in the database; querying and obtaining the configuration file that matches the version identifier corresponding to the latest actual upgrade time from the updated configuration file to be upgraded and multiple historical configuration files as the target configuration file for the software to be upgraded.

[0095] Specifically, the server generates a time judgment instruction and sends the time judgment instruction to the database. The database judges the latest actual upgrade time in the relevant data table of the configuration file of the software to be upgraded, and then the database obtains the latest actual upgrade time and the version identifier corresponding to the latest actual upgrade time. Then the database sends the version identifier corresponding to the latest actual upgrade time to the server. The server receives the version identifier, obtains the version identifiers of all configuration files in the preset directory through a judgment tool, matches the obtained version identifiers of all configuration files with the version identifier corresponding to the latest actual upgrade time. If the version identifier of the updated configuration file to be upgraded matches the version identifier corresponding to the latest actual upgrade time, the updated configuration file to be upgraded is used as the target configuration file for the software to be upgraded.

[0096] In addition, when R&D personnel or managers need to roll back the version of the software to be upgraded or put the historical version back online (that is, reconfigure), the target version identifier can be set to the version identifier of the historical configuration file of the corresponding version, and the target upgrade time can be set to the actual upgrade time of the historical configuration file that needs to be put online again. Then the R&D personnel or managers send the target version identifier and the target upgrade time to the server through the terminal. The server receives the target version identifier and the target upgrade time, modifies the corresponding actual upgrade time in the database, and then determines to obtain the historical configuration file in the preset directory that matches the target version identifier, and then updates the actual upgrade time of the historical configuration file to obtain the updated historical configuration file. When the updated historical configuration file matches the version identifier corresponding to the latest actual upgrade time, the updated historical configuration file is used as the target configuration file for the software to be upgraded.

[0097] In this embodiment, a configuration file that matches the version identifier corresponding to the latest actual upgrade time is used as the target configuration file of the software to be upgraded. By adopting this method, there is no need to predetermine the actual upgrade time of the configuration file to be upgraded. By updating the preset upgrade time of the configuration file to be upgraded to the actual upgrade time, the upgrade time of the configuration file to be upgraded can be changed in real time according to actual development needs, thereby improving the flexibility of software version upgrade. At the same time, the historical configuration file can be reconfigured according to the upgrade task, realizing flexible switching of the upgrade version of the software to be upgraded, thereby improving the flexibility of software version upgrade.

[0098] In one embodiment, after selecting the configuration file with the latest actual upgrade time from the updated configuration file to be upgraded and multiple historical configuration files as the target configuration file for the software to be upgraded, the method further includes: when it is detected that the target configuration file is the actual upgrade file of the software to be upgraded, generating operation data corresponding to the target configuration file; and performing upgrade processing on the software to be upgraded according to the operation data corresponding to the target configuration file.

[0099] The actual upgrade file is the upgrade configuration file of the determined software to be upgraded. The running data refers to the pre-installed data of the software to be upgraded.

[0100] Specifically, the server sends the target configuration file from the upstream application to the source directory (SOURCE directory), and re-detects the actual upgrade time of all files in the source directory. When it is detected that the actual upgrade time of the target configuration file is the latest upgrade time of the software to be upgraded, the target configuration file is confirmed to be the actual upgrade file of the software to be upgraded, and the target configuration file is moved to the target upgrade directory. Then, the files in the target upgrade directory are scanned to generate real-time operation data. Then, according to the version configuration instructions, the real-time operation data is decoded, distributed, split, and file transcoded, and finally the upgrade file required by the downstream application is generated. When it is determined that the actual upgrade time of the target configuration file has been reached, the relevant operations of the version upgrade are performed; when it is detected that the target configuration file is not the actual upgrade file of the software to be upgraded, the target configuration file is moved to the error directory.

[0101] In this embodiment, by re-detecting the upgrade time of the files in the source directory, the configuration files of the software to be upgraded generated after the target configuration file are avoided from being ignored, which can effectively reduce the errors in software version upgrade, thereby improving the accuracy of software version upgrade.

[0102] In one embodiment, Figure 3 As shown, another software version upgrade method is provided, which is applied to Figure 1 The server in the example is used to illustrate the following steps:

[0103] Step S301, obtaining a configuration file of the software to be upgraded, modifying the configuration file multiple times to obtain multiple modified configuration files of the configuration file; filtering out the configuration file to be upgraded from the multiple modified configuration files; the configuration file to be upgraded is the modified configuration file obtained by the last modification.

[0104] Step S302: read out the version identifier and preset upgrade time of the configuration file to be upgraded, and store the version identifier and preset upgrade time in a database.

[0105] Step S303, receiving an upgrade task for the software to be upgraded; extracting a target version identifier and a target upgrade time corresponding to the target version identifier from the upgrade task.

[0106] Step S304, querying and obtaining a version identifier that matches the target version identifier from the database; updating the actual upgrade time corresponding to the version identifier that matches the target version identifier in the database as the target upgrade time.

[0107] Step S305: When the version identifier of the configuration file to be upgraded matches the target version identifier, the preset upgrade time of the configuration file to be upgraded is updated to the target upgrade time stored in the database.

[0108] Step S306, query and obtain a historical configuration file matching the updated configuration file from multiple historical configuration files; adjust the effective time of the historical configuration file matching the updated configuration file to be upgraded to the difference between the actual upgrade time of the updated configuration file to be upgraded and the preset threshold.

[0109] Step S307: query and obtain the latest actual upgrade time and the version identifier corresponding to the latest actual upgrade time from the actual upgrade time stored in the database.

[0110] Step S308: Query a configuration file that matches the version identifier corresponding to the latest actual upgrade time from the updated configuration file to be upgraded and the multiple historical configuration files, and use it as the target configuration file for the software to be upgraded.

[0111] Step S309: when it is detected that the target configuration file is the actual upgrade file of the software to be upgraded, the operation data corresponding to the target configuration file is generated; and the software to be upgraded is upgraded according to the operation data corresponding to the target configuration file.

[0112] The above software version upgrade method does not need to predetermine the actual upgrade time of the configuration file to be upgraded. By updating the preset upgrade time of the configuration file to be upgraded to the actual upgrade time, the upgrade time of the configuration file to be upgraded can be changed in real time according to actual development needs, thereby improving the flexibility of software version upgrade.

[0113] In order to more clearly illustrate the software version upgrade method provided by the embodiment of the present disclosure, the software version upgrade method is specifically described below with a specific embodiment. Figure 4 As shown, the present disclosure also provides a software version upgrade method, which specifically includes the following contents:

[0114] Step S401, data dependency module: store basic information such as file information to be transmitted, source interface and target interface information, field information, upstream and downstream information, version production time, etc., use a specific tool to export the stored basic information, and generate a configuration file.

[0115] Step S402, data verification module: according to the time sequence of adding, deleting or modifying the revision files corresponding to the upgrade tasks of the software to be upgraded, the configuration files are processed accordingly, and the configuration files modified for the last time are retained as the configuration files to be upgraded. During the modification process, the preset timestamp of the configuration files to be upgraded and the target version identifier and target upgrade time of the software to be upgraded are also obtained and stored in the database.

[0116] Step S403, version configuration module: call the timestamp configuration instruction, switch the preset upgrade time of the configuration file to be upgraded to the target upgrade time, obtain the target configuration file, and at the same time adjust the effective time of the file in the historical configuration file that has the same file name, source interface, and target interface as the configuration file to be upgraded to the actual upgrade time of the configuration file to be upgraded minus 1 day.

[0117] Step S404, file scanning module: transfer the upstream application to the file in the source directory, match it according to the actual upgrade time in the configuration information of the file, obtain the configuration file with the latest actual upgrade time, move the configuration file with the latest actual upgrade time to the processing directory, and move the configuration file that does not match the latest actual upgrade time to the error directory.

[0118] Step S405, file scheduling module: generates real-time operation data of files moved to the processing directory through version configuration instructions.

[0119] Step S406, file processing module: through the version configuration instruction, perform file decoding and processing related operations on the generated real-time operation data to generate the upgrade file required by the final downstream application.

[0120] In this embodiment, there is no need to return, re-modify and then re-publish the already published target configuration file according to the actual needs of the upgrade task. The actual upgrade time can be quickly updated through the table structure of the database, which reduces the update processing time of the target configuration file. Therefore, the upgrade time of the configuration file to be upgraded can be changed in real time according to the actual development needs, thereby improving the flexibility of software version upgrades. According to the needs of the business system, historical version data can also be automatically upgraded or extracted for use without the need for additional configuration operations, further improving the flexibility of software version upgrades.

[0121] In one embodiment, Figure 5 As shown, the above steps S402 and S403 also provide another implementation method, which specifically includes the following contents:

[0122] Step 501, first obtain the original configuration file of the software to be upgraded through the export tool. The format of the original configuration file is as follows: file name_source interface_target interface_version number_preset timestamp.BIN. The configuration content includes the basic information of the file source interface and target interface, file addition (deletion) identification, field information, field filtering information, upstream and downstream information, file transfer approval ID and other basic information. At the same time, the configuration information of version number_preset timestamp_actual timestamp.TXT is obtained. This configuration information can be updated with the daily version, and each new version of the configuration information will overwrite the previous overwrite file.

[0123] Step 502: Place the board-sealing configuration file and daily patch configuration file of the software to be upgraded in a temporary directory and modify them multiple times. The import tool reads the file information. When the board-sealing configuration file and the daily patch configuration file are modified multiple times in the current version, the configuration file corresponding to the last file transfer approval id of the same file in the current version is retained to obtain the configuration file to be upgraded. While modifying the file, import it into the library table cfg_validTime according to the determined time correspondence. The field structure of the table is as follows:

[0124] Field Name Field Type use APPVER VARCHAR2 Version number, used to distinguish the production time of different configuration files. DEPLOYDATE VARCHAR2 The production time corresponding to the version number. YTIME VARCHAR2 The preset production time corresponding to the version number. REITEMID VARCHAR2 Requirement number, reserved field.

[0125] Step 503, the preset production time is T, T-1, T-2 of the current version, which can be extended to T+1, T+2 as needed. The import tool determines the version identifier of the configuration file to be upgraded, switches the timestamp of the preset production time of the configuration file to be upgraded to the timestamp of the production time corresponding to the version, and updates the format in the configuration file to be upgraded: the original format "file name_source interface_target interface_version number_preset timestamp.BIN" is updated to "file name_source interface_target interface_version number_production time.BIN".

[0126] Step 504, after the timestamp of the preset commissioning time of the configuration file to be upgraded corresponding to the current version is switched to the new commissioning time, the timestamp of the effective time of the configuration file in the historical configuration file that is the same as the file name, source interface, and target interface of the configuration file to be upgraded is adjusted to the current commissioning time minus 1, and the adjusted historical configuration file is used for subsequent business to download the data of the historical version, so as to avoid obtaining the data of the historical version through manual adjustment when the subsequent business needs it.

[0127] It should be understood that although Figure 2-5 The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figure 2-5At least part of the steps may include multiple steps or multiple stages. These steps or stages are not necessarily performed at the same time, but can be performed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed in turn or alternately with other steps or at least part of the steps or stages in other steps.

[0128] Based on the same inventive concept, the embodiment of the present application also provides a software version upgrade device for implementing the software version upgrade method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more software version upgrade device embodiments provided below can refer to the limitations of the software version upgrade method above, and will not be repeated here.

[0129] In one embodiment, Figure 6 As shown, a software version upgrade device 600 is provided, including: a file acquisition module 601, a time acquisition module 602, an update time module 603 and a file screening module 604, wherein:

[0130] The file acquisition module 601 is used to acquire the configuration file to be upgraded of the software to be upgraded, and store the version identification and preset upgrade time of the configuration file to be upgraded in a database; the database also stores the actual upgrade time of multiple historical configuration files of the software to be upgraded;

[0131] The time acquisition module 602 is used to acquire the input target version identifier and the target upgrade time corresponding to the target version identifier;

[0132] An update time module 603 is used to update the preset update time of the configuration file to be upgraded to the target upgrade time when the version identifier of the configuration file to be upgraded matches the target version identifier, so as to obtain the actual upgrade time of the configuration file to be upgraded;

[0133] The file screening module 604 is used to screen out the configuration file with the latest actual upgrade time from the configuration file to be upgraded and the multiple historical configuration files as the target configuration file of the software to be upgraded.

[0134] In one embodiment, the file acquisition module 601 is also used to obtain the configuration file of the software to be upgraded, modify the configuration file multiple times to obtain multiple modified configuration files of the configuration file; filter out the configuration file to be upgraded from the multiple modified configuration files; the configuration file to be upgraded is the modified configuration file obtained by the last modification; read out the version identifier and preset upgrade time of the configuration file to be upgraded, and store the version identifier and the preset upgrade time in the database.

[0135] In one embodiment, the time acquisition module 602 is further used to receive an upgrade task of the software to be upgraded; and extract a target version identifier and a target upgrade time corresponding to the target version identifier from the upgrade task.

[0136] In one embodiment, the software version upgrade device 600 also includes a database update module, which is used to query and obtain a version identifier that matches the target version identifier from the database; and update the actual upgrade time corresponding to the version identifier that matches the target version identifier in the database to the target upgrade time.

[0137] The update time module 603 is further configured to update the preset update time of the configuration file to be upgraded to the target upgrade time stored in the database when the version identifier of the configuration file to be upgraded matches the target version identifier.

[0138] In one embodiment, the software version upgrade device 600 also includes a time adjustment module, which is used to query and obtain a historical configuration file that matches the upgraded configuration file to be updated from multiple historical configuration files; and adjust the effective time of the historical configuration file that matches the updated configuration file to be upgraded to the difference between the actual upgrade time of the updated configuration file to be upgraded and a preset threshold.

[0139] In one embodiment, the file screening module 604 is also used to query the latest actual upgrade time and the version identifier corresponding to the latest actual upgrade time from the actual upgrade time stored in the database; and query the configuration file that matches the version identifier corresponding to the latest actual upgrade time from the updated configuration file to be upgraded and the multiple historical configuration files as the target configuration file for the software to be upgraded.

[0140] In one embodiment, the software version upgrade device 600 also includes a software upgrade module, which is used to generate operating data corresponding to the target configuration file when it is detected that the target configuration file is the actual upgrade file of the software to be upgraded; and upgrade the software to be upgraded according to the operating data corresponding to the target configuration file.

[0141] Each module in the above-mentioned software version upgrade device can be implemented in whole or in part by software, hardware and their combination. Each of the above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory in the computer device in the form of software, so that the processor can call and execute the operations corresponding to each of the above modules.

[0142] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 7As shown. The computer device includes a processor, a memory and a network interface connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data such as version identification, preset upgrade time, actual upgrade time, etc. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a software version upgrade method is implemented.

[0143] Those skilled in the art will understand that Figure 7 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0144] In one embodiment, a computer device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above method embodiments when executing the computer program.

[0145] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0146] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0147] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0148] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0149] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0150] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A software version upgrade method, characterized in that: The method comprises: Obtaining a configuration file to be upgraded of the software to be upgraded, and storing the version identifier and preset upgrade time of the configuration file to be upgraded in a database; the database also stores actual upgrade times of multiple historical configuration files of the software to be upgraded; Obtaining an input target version identifier and a target upgrade time corresponding to the target version identifier; When the version identifier of the configuration file to be upgraded matches the target version identifier, updating the preset upgrade time of the configuration file to be upgraded to the target upgrade time, and obtaining the actual upgrade time of the updated configuration file to be upgraded; Filtering out the configuration file with the latest actual upgrade time from the updated configuration file to be upgraded and the multiple historical configuration files as the target configuration file of the software to be upgraded; Wherein, when the version identifier of the configuration file to be upgraded matches the target version identifier, updating the preset upgrade time of the configuration file to be upgraded to the target upgrade time, and obtaining the actual upgrade time of the updated configuration file to be upgraded, the method further includes: Querying the database to obtain a version identifier that matches the target version identifier; Updating the actual upgrade time corresponding to the version identifier in the database that matches the target version identifier to the target upgrade time, wherein the database stores the version identifier, the preset upgrade time, the actual upgrade time and the requirement number of the configuration file to be upgraded; When the version identifier of the configuration file to be upgraded matches the target version identifier, updating the preset upgrade time of the configuration file to be upgraded to the target upgrade time includes: When the version identifier of the configuration file to be upgraded matches the target version identifier, updating the preset upgrade time of the configuration file to be upgraded in the preset directory to the target upgrade time stored in the database; The step of selecting the configuration file with the latest actual upgrade time from the updated configuration file to be upgraded and the multiple historical configuration files as the target configuration file for the software to be upgraded includes: querying the actual upgrade time stored in the database to obtain the latest actual upgrade time and the version identifier corresponding to the latest actual upgrade time; A configuration file matching the version identifier corresponding to the latest actual upgrade time is queried from the updated configuration file to be upgraded and the multiple historical configuration files as the target configuration file for the software to be upgraded.

2. The method according to claim 1, characterized in that: The step of obtaining a configuration file to be upgraded of the software to be upgraded, and storing the version identifier and the preset upgrade time of the configuration file to be upgraded in a database includes: Obtaining a configuration file of the software to be upgraded, and modifying the configuration file multiple times to obtain multiple modified configuration files of the configuration file; Filtering the configuration file to be upgraded from the multiple modified configuration files; the configuration file to be upgraded is the modified configuration file obtained by the last modification; The version identifier and the preset upgrade time of the configuration file to be upgraded are read out, and the version identifier and the preset upgrade time are stored in the database.

3. The method according to claim 1, characterized in that The step of obtaining an input target version identifier and a target upgrade time corresponding to the target version identifier includes: Receiving an upgrade task for the software to be upgraded; The target version identifier and the target upgrade time corresponding to the target version identifier are extracted from the upgrade task.

4. The method according to claim 1, characterized in that: After obtaining the actual upgrade time of the updated configuration file to be upgraded, the method further includes: querying and obtaining, from the plurality of historical configuration files, a historical configuration file that matches the updated configuration file to be upgraded; The actual update time of the historical configuration file matching the updated configuration file to be updated is adjusted to the difference between the actual update time of the updated configuration file to be updated and a preset threshold value, so as to invalidate the historical configuration file.

5. The method according to claim 1, characterized in that After selecting the configuration file with the latest actual upgrade time from the configuration file to be upgraded and the multiple historical configuration files as the target configuration file of the software to be upgraded, the method further includes: When it is detected that the target configuration file is an actual upgrade file of the software to be upgraded, generating operation data corresponding to the target configuration file; The software to be upgraded is upgraded according to the operating data corresponding to the target configuration file.

6. A software version upgrade device, characterized in that: The device comprises: The file acquisition module is used to acquire the configuration file to be upgraded of the software to be upgraded, and store the version identification and preset upgrade time of the configuration file to be upgraded in a database; the database also stores the actual upgrade time of multiple historical configuration files of the software to be upgraded; A time acquisition module, used to acquire an input target version identifier and a target upgrade time corresponding to the target version identifier; An update time module, configured to update the preset update time of the configuration file to be upgraded to the target upgrade time when the version identifier of the configuration file to be upgraded matches the target version identifier, so as to obtain the actual upgrade time of the configuration file to be upgraded; A file screening module, used for screening out the configuration file with the latest actual upgrade time from the configuration file to be upgraded and the multiple historical configuration files, as the target configuration file of the software to be upgraded; The database update module is used to query and obtain a version identifier that matches the target version identifier from the database; update the actual upgrade time corresponding to the version identifier that matches the target version identifier in the database to the target upgrade time, wherein the database stores the version identifier, preset upgrade time, actual upgrade time and requirement number of the configuration file to be upgraded; The update time module is further used to update the preset upgrade time of the configuration file to be upgraded in the preset directory to the target upgrade time stored in the database when the version identifier of the configuration file to be upgraded matches the target version identifier; Among them, the file screening module is also used to query the latest actual upgrade time and the version identifier corresponding to the latest actual upgrade time from the actual upgrade time stored in the database; and query the configuration file that matches the version identifier corresponding to the latest actual upgrade time from the updated configuration file to be upgraded and the multiple historical configuration files as the target configuration file for the software to be upgraded.

7. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 5 are implemented.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 5 are implemented.

9. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 5 are implemented.

Images