CN112631627B - Software upgrading method and device, computer equipment and storage medium - Google Patents
Software upgrading method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN112631627B CN112631627B CN202011434333.7A CN202011434333A CN112631627B CN 112631627 B CN112631627 B CN 112631627B CN 202011434333 A CN202011434333 A CN 202011434333A CN 112631627 B CN112631627 B CN 112631627B
- Authority
- CN
- China
- Prior art keywords
- software
- database
- upgrading
- main
- target software
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F16/275—Synchronous replication
Abstract
If an upgrade instruction of target software sent by a software management system is received, a main database of the target software is switched to a temporary database for storing data generated by the target software during the upgrade period, the main database is updated according to an upgrade file to obtain an upgraded main database, and then the data in the temporary database is synchronized to the upgraded main database to complete the upgrade of the target software. The method does not need to stop using the target software by using personnel, and achieves on-site noninductive upgrading of the target software. And after the upgrading operation of the target software receives the upgrading instruction sent by the software management system, the upgrading operation is carried out without manual maintenance and one-key upgrading, so that the software upgrading process is simplified, and the software upgrading efficiency is improved.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a software upgrading method and apparatus, a computer device, and a storage medium.
Background
In the current era with increasingly developed informatization, each hospital follows the pace of the era and aims at professional medical software on line in different medical technical departments, so that the accuracy and rapidity of hospital treatment are greatly improved.
Because the treatment flow of each hospital is inconsistent, the use habits of doctors are different more or less or some historical legacy reasons, the requirements of the same software for the same departments of different hospitals are different, and the medical software needs to be updated at intervals after the medical software is on line. At present, most of medical software upgrading methods finish upgrading by pushing upgrading messages and then clicking upgrading to download uniform patches by users, but if patch upgrading is frequently pushed, the users can generate dislike emotion. Still other customized medical software upgrades require engineers to remotely or in-house upgrade the department software, relying on human labor to maintain and upgrade, and requiring early notification to the physician to stop using the software before upgrading, leaving the upgrade process overnight to minimize impact.
Therefore, the software upgrading process is complex and tedious, and has a large influence on the normal business of the hospital.
Disclosure of Invention
Therefore, it is necessary to provide a software upgrading method, device, computer device and storage medium for the above technical problems, which can simplify the software upgrading process, so that the software upgrading process does not affect the normal business of the hospital, and the software field is upgraded noninductively.
In a first aspect, an embodiment of the present application provides a software upgrading method, where the method includes:
if an upgrading instruction of the target software sent by the software management system is received, switching a main database of the target software into a temporary database; the temporary database is used for storing data generated by the target software during upgrading;
updating the main database according to the upgrade file to obtain an upgraded main database;
and synchronizing the data in the temporary database to the upgraded main database to finish the upgrade of the target software.
In one embodiment, the method further comprises:
before the main database of the target software is switched to the temporary database, the main program of the target software is switched to a preset simplified program; the simplified program is used for generating a temporary database;
and updating the main program according to the upgrade file to obtain the upgraded main program.
In one embodiment, the simplified program is used for generating a temporary database according to an input/output logical relationship obtained by the operation of the main program of the target software corresponding to the data change in the main database.
In one embodiment, before synchronizing the data in the temporary database to the upgraded main database, the method further includes:
according to a preset automatic test program, carrying out automatic test on the upgraded main program and the upgraded main database;
and if the automatic test is passed, determining that the target software is upgraded.
In one embodiment, before the switching the main program to the simplified program, the method further includes:
backing up a main program and a main database of target software;
correspondingly, if the automatic test result fails, the backup main program is covered with the upgraded main program, the backup main database is covered with the upgraded main database, meanwhile, data in the temporary database is synchronized to the covered main database, and the version rollback of the target software is completed.
In one embodiment, the software management system includes a plurality of organization management pages, and each organization management page is used for managing upgrade information and software upgrade control operation of all software of a corresponding organization;
the upgrade file is sent after the software management system triggers a file copy instruction in a target mechanism management page of target software.
In one embodiment, if the network speed of the transmission network is greater than a preset network speed threshold, the upgrade file is sent by the whole software management system;
and if the network speed of the transmission network is less than or equal to the network speed threshold value, the upgrade file is sent by the software management system in blocks.
In one embodiment, the software management system sends the total upgrade file information table in advance before sending the upgrade file, and the total upgrade file information table is used for verifying the integrity of the upgrade file.
In a second aspect, an embodiment of the present application provides a software upgrading apparatus, including:
the switching module is used for switching a main database of the target software into a temporary database if an upgrading instruction of the target software sent by the software management system is received; the temporary database is used for storing data generated by the target software during upgrading;
the processing module is used for updating the main database according to the upgrade file to obtain an upgraded main database;
and the upgrading module is used for synchronizing the data in the temporary database to the upgraded main database to finish upgrading the target software.
In a third aspect, an embodiment of the present application provides a computer device, which includes a memory and a processor, where the memory stores a computer program, and the processor implements the method steps in any one of the first aspect embodiments when executing the computer program.
In a fourth aspect, embodiments of the present application provide a computer-readable storage medium, on which a computer program is stored, which, when executed by a processor, implements the method steps of any one of the embodiments of the first aspect described above.
According to the software upgrading method, the software upgrading device, the computer equipment and the storage medium, if an upgrading instruction of target software sent by a software management system is received, a main database of the target software is switched to a temporary database for storing data generated by the target software during upgrading, the main database is updated according to an upgrading file to obtain an upgraded main database, and then the data in the temporary database is synchronized to the upgraded main database to complete upgrading of the target software. According to the method, the temporary database is established, so that the temporary database can be used for replacing a main database to carry out data storage management during the upgrading of the target software, the normal operation of the target software of the organization can be ensured, the normal operation of the organization cannot be influenced in the software upgrading process, the target software does not need to be stopped by a user, and the on-site noninductive upgrading of the target software is realized. And after the upgrading operation of the target software receives the upgrading instruction sent by the software management system, the upgrading operation is carried out without manual maintenance and one-key upgrading, so that the software upgrading process is simplified, and the software upgrading efficiency is improved.
Drawings
FIG. 1 is a diagram of an application environment for a method of software upgrade provided in one embodiment;
FIG. 1a is a diagram of the internal structure of a computer device or facility server in one embodiment;
FIG. 2 is a flowchart illustrating a method for upgrading software, according to an embodiment;
FIG. 3 is a schematic diagram of a software management system and an organization software system provided in another embodiment;
FIG. 4 is a flowchart illustrating a software upgrade method according to another embodiment;
FIG. 5 is a flowchart illustrating a software upgrade method according to another embodiment;
FIG. 6 is a flowchart illustrating a software upgrade method according to another embodiment;
FIG. 7 is a schematic diagram of an upgrade file transfer provided in another embodiment;
FIG. 8 is a schematic diagram of an upgrade file copy flow provided in another embodiment;
FIG. 9 is a block diagram of a software upgrading apparatus provided in one embodiment;
fig. 10 is an internal structural diagram of a computer device in one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The software upgrading method provided by the embodiment of the application can be applied to the application environment shown in fig. 1. The computer equipment runs a software management system which communicates with the software systems of all the mechanisms to realize the management of the upgrading information and the upgrading operation of the software of all the mechanisms. The software system of each institution runs on the server of each institution, i.e. the computer device communicates with the server of each institution via a network. The mechanism software system running on the server of each mechanism is used for managing software running, upgrading, business operation and the like in the mechanism. The institution may be a hospital, a different enterprise unit, and the like, which is not limited in the embodiment of the present application. The computer devices include, but are not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices. The servers of each mechanism include, but are not limited to, general servers, special servers, desktop servers, rack servers, blade servers, and the like.
The internal structure of the computer device and the server can be seen in fig. 1a, and the processor in fig. 1a is used for providing calculation and control capability. The memory includes a nonvolatile storage medium, 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 an operating system and computer programs in the non-volatile storage medium. The database is used for storing relevant data generated in the process of the software upgrading method. The network interface is used for communicating with other external devices through network connection. The computer program, when executed by a processor, implements a software upgrade method.
The embodiment of the application provides a software upgrading method, a software upgrading device, computer equipment and a storage medium, which can simplify the software upgrading process, enable the software upgrading process not to influence the normal business of a hospital and realize the on-site noninductive upgrading of software. The following detailed description will specifically explain how the technical solutions of the present application and the technical solutions of the present application solve the above technical problems by embodiments and with reference to the accompanying drawings. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. It should be noted that, in the software upgrading method provided in the present application, the execution main bodies in fig. 2 to fig. 8 are each mechanism server (a mechanism software system runs in the mechanism server), where the execution main body may also be a software upgrading apparatus, where the apparatus may be implemented as part or all of the mechanism server by software, hardware, or a combination of software and hardware.
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments.
In one embodiment, as shown in fig. 2, a software upgrading method is provided, which is exemplified by the application environment of fig. 1, and this embodiment relates to a specific process in which after receiving an upgrade instruction of target software, an organization server switches a main database of the target software to a temporary database, stores data generated during the upgrade of the target software to the temporary database, and then upgrades the main database according to an upgrade file; this embodiment comprises the steps of:
s101, if an upgrading instruction of target software sent by a software management system is received, switching a main database of the target software into a temporary database; the temporary database is used to store data generated by the target software during the upgrade.
The software management system refers to a system for implementing upgrade information and upgrade operation of management software. Taking an organization as a hospital as an example, as shown in fig. 3, the interaction diagram between the software management system and the hospital software system is shown; generally, for the safety of information, each hospital does not access an external network, but a server (running with a hospital software system) of each hospital communicates with a computer device running with a software management system through a virtual private network (VPN for short), and can be connected with an external network file transfer server (FTP for short), for example, an upgrade file can be directly uploaded on the software management system, the upgrade file can be automatically and synchronously copied to the external network FTP, the copying progress is recorded in the copying process, and breakpoint continuous transmission is supported. When software of each hospital is upgraded, operations such as upgrading flow triggering need to be performed in the software management system, that is, the software of each hospital is upgraded through the software management system.
Therefore, the upgrading instruction of the target software is triggered in the software management system, and the mechanism server indicates that the target software in the mechanism needs to be upgraded when receiving the software upgrading instruction. Generally, the software upgrading process includes upgrading a database and upgrading an execution program, and upgrading the database and upgrading the execution program may be performed simultaneously or alternatively, which is not limited in the embodiments of the present application.
Taking a hospital as an example, for software used by the hospital, the operation of the software is the operation of the database at the bottom, and how to ensure normal operation of the service in the software upgrading process needs to be considered. When the doctor uses the software, the operation of the doctor correspondingly adds, deletes, modifies data and the like to certain tables in the database, namely, the operation of the software is an input-operation-output black box mode for the doctor, so that the doctor needs to ensure that the operation of the target software is not influenced in the upgrading process of the target software.
Taking the database upgrade as an example, a temporary database is established in advance, which may be a database generated by an execution program according to a main database of the software and including only data structures excluding specific data, and is used for storing data generated during the upgrade of the target software; for example, tables relating to patient operation may be included in the temporary database to store relevant data resulting from patient examination during the upgrade of the target software into the temporary database. Equivalently, the temporary database can be established to replace the original main database to store the service data of the hospital during the upgrading period, and the influence on the normal operation of the service of the hospital due to the upgrading of the target software is avoided. Moreover, the temporary database only comprises a data structure, and the data structure can ensure that the form format and the content of each table entry in the form are correct, so that the business data of the hospital can be correctly stored even if the temporary database is used.
And S102, updating the main database according to the upgrade file to obtain an upgraded main database.
And after the main database is switched to the temporary database, updating the main database according to the upgrading file. The upgrade file refers to a file required for upgrading the target file at this time, for example, a patch file. The upgrade file is copied from the software management system to the mechanism software system on the mechanism server in advance before the formal execution of the upgrade process, and the upgrade file is copied to the mechanism server in advance, so that the problem that the upgrade file is not copied successfully due to poor network or other abnormal conditions and the upgrade of target software is influenced can be avoided.
The software file comprises a database script to be updated, and the updating of the master database according to the upgrade file can be realized by executing the database script by the master database, so that the master database can be updated to obtain the upgraded master database.
S103, synchronizing the data in the temporary database to the upgraded main database to finish the upgrade of the target software.
And after the upgraded main database is obtained, synchronizing the data stored in the temporary database during the upgrading period to the upgraded main database, so as to finish upgrading the target software. And synchronizing the data in the temporary database to the upgraded main database, so that the integrity of the data of the organization business operation stored in the main database can be ensured.
After the target software is upgraded, the service data of the target software can be continuously managed in the upgraded main database, and the temporary database can disappear after the target software is upgraded successfully, wherein the disappearing refers to deleting or transferring to a specified position for subsequent upgrading and recalling. It should be noted that if only the database is updated, and the software is updated; however, if the execution program or other contents need to be upgraded, it is determined that the target software is upgraded until all the contents to be upgraded are upgraded. Only when the target software is upgraded and the upgrade is successful, the data in the temporary database is not needed any more, and the temporary database can disappear.
In the software upgrading method provided by this embodiment, if an upgrading instruction of target software sent by a software management system is received, a main database of the target software is switched to a temporary database for storing data generated by the target software during upgrading, then the main database is updated according to an upgrading file to obtain an upgraded main database, and then the data in the temporary database is synchronized to the upgraded main database to complete upgrading of the target software. According to the method, the temporary database is established, so that the temporary database can be used for replacing a main database to carry out data storage management during the upgrading of the target software, the normal operation of the target software of the organization can be ensured, the normal operation of the organization cannot be influenced in the software upgrading process, the target software does not need to be stopped by a user, and the on-site noninductive upgrading of the target software is realized. And after the upgrading operation of the target software receives the upgrading instruction sent by the software management system, the upgrading operation is carried out without manual maintenance and one-key upgrading, so that the software upgrading process is simplified, and the software upgrading efficiency is improved.
On the basis of the above embodiment, if the execution program of the target software needs to be upgraded, the execution program of the target software (hereinafter, referred to as a main program) needs to be upgraded, and it is determined that the target software is upgraded.
In one embodiment, as shown in fig. 4, the process of upgrading the execution program of the target software includes the following steps:
s201, before the main database of the target software is switched to the temporary database, the main program of the target software is switched to a preset simplified program; a simplified procedure is used to generate the temporary database.
Since the database of the target software needs to be updated before the database of the target software is updated, the database of the target software needs to be updated because the database of the target software needs to be stored and the like and the temporary database needs to be generated. Namely, before the main database of the target software is switched to the temporary database, the main program of the target software is switched to a preset simplified program. The simplified program has a function similar to that of the temporary database, and manages the business operation of the target software instead of the main program during the upgrade of the target software. For example, the simplified program generates a temporary database from the master data during the upgrade; as another example, the simplified program manages business data operations in the temporary database during upgrades.
In the context of hospital upgrade software, it was mentioned above that the operation of the software corresponds to the input-run-output black box operation for the physician. When the simplified program generates the temporary database, a monitoring service may be set, where the monitoring service monitors the input/output logical relationship of the target software, and the input/output logical relationship corresponds to the relationship between the operation of the main program and the change of data in the main database; optionally, when the simplified program generates the temporary database, the temporary database is generated according to an input-output logical relationship obtained by the operation of the main program of the target software corresponding to the data change in the main database. The operation of the main program of the target software can be monitored through the monitoring service, and the input and output logical relation of data change in the main database is corresponded to; further, the input/output logical relationship of the operation of the main program of the monitoring service for monitoring the selected data corresponding to the data change in the main database may be set, where the selected data is designated data, for example, data related to patient information, or data that is used most frequently by a doctor during consultation, or data that must be used by a night emergency clinic, and the like, and the embodiment of the present application is not limited thereto; then, in one embodiment, a simplified procedure is used to generate the temporary database based on the input-output logical relationship of selected data in the primary database. The simplified program generates an input-output relation table according to the input-output logic relation of the selected data, and the output-output relation table is a temporary database. The temporary database is generated based on the input-output logical relationship, and only contains a data structure and does not contain specific data.
During the target software upgrade, the main program is switched to a simplified program, and the simplified program replaces the main program to temporarily take over the business data for the temporary database. And for the user, when the user operates the target software, the business operation of the target software is normal. For example, during software upgrade, the main program and the main database are switched, if there is an emergency patient, when a doctor operates the target software, the business operation is performed by simplifying the program, and the business data is inserted into the temporary database, and the operations of adding, deleting and modifying the data are all performed in the background.
And S202, updating the main program according to the upgrade file to obtain the upgraded main program.
And after the main program is switched to the simplified program, updating the main program according to the upgrading file. The upgrade file may include a program file in addition to the database script. When the main program is updated, the updating can be performed according to the program file. Specifically, the program file can replace the corresponding file of the main program installed in the instruction path, that is, the old program file of the main program is replaced by the program file in the upgrade file, so as to complete the updating of the main program, and obtain the upgraded main program.
In this embodiment, before the main database of the target software is switched to the temporary database, the main program of the target software is switched to a preset simplified program; the simplified program is used for generating a temporary database, and then the main program is updated according to the upgrade file to obtain the upgraded main program. By setting the simplified program, the simplified program can be used for replacing a main program to perform business operation during the upgrading of the target software, the business operation of the target software of the mechanism can be ensured to be normally performed, the normal business of the mechanism can not be influenced in the software upgrading process, a user does not need to stop using the target software, and the on-site noninductive upgrading of the target software is realized.
When the software is upgraded or the software is on-line, software testing is needed, and the success of software upgrading can be determined only if the software passes the testing. Based on this, the present application further provides an embodiment, which relates to a process of testing upgraded software, and as shown in fig. 5, the embodiment includes:
s301, according to a preset automatic test program, carrying out automatic test on the upgraded main program and the upgraded main database.
The automatic test program is pre-developed and can be set at the beginning of the on-line of the target software for automatically testing the upgraded software. The automatic test can be completed by triggering an automatic test program to run. The mode of triggering the operation of the automated test program may be that a software upgrade completion instruction is received as a trigger condition, or that an instruction output by a user is received as a trigger condition, and the like, which is not limited in the embodiment of the present application.
And S302, if the automatic test is passed, determining that the target software is upgraded.
If the test result of the automatic test program is passed after the automatic test, the target software can be determined to be successfully upgraded, otherwise, if the test result is failed, the target software is determined to be unsuccessfully upgraded. The method for outputting the test result may include popping up an information frame, or giving a voice warning, and the like, which is not limited in the embodiment of the present application.
It is understood that, after the automatic test is passed, the step S103 is executed, that is, the automatic test of the target software is passed, the data in the temporary database is synchronized to the main database, and the main database is switched back to the main program, so that the completion of the upgrade of the target software can be determined.
However, if the automated test of the target software fails, a software version rollback operation is required to avoid affecting the use of the target software. Optionally, in an embodiment, before the switching the main database to the temporary database and the main program to the simplified program, the method further includes: backing up a main program and a main database of target software; correspondingly, if the automatic test result fails, the backup main program is covered with the upgraded main program, the backup main database is covered with the upgraded main database, meanwhile, data in the temporary database is synchronized to the covered main database, and the version rollback of the target software is completed.
Before the target software is upgraded, the main program and the main database are backed up, when the target software fails to be upgraded, the backed-up main program is covered with the main program which fails to be upgraded, and the backed-up main database is covered with the main database which fails to be upgraded, namely, the main program and the main database of the current target software are backed up to the position before being upgraded. The method includes that business data of target software during upgrading is recorded in a temporary database, and in order to guarantee integrity of the business data in a master database after target software version rollback, the business data in the temporary database needs to be synchronized to the retired master database, and the retired master database is a master database which fails in upgrading and is covered by a backup master database, so that the data in the temporary database is synchronized to the covered master database.
In the embodiment, the automatic test program is set to automatically test the upgraded target software, and the target software is determined to be successfully upgraded only when the automatic test is passed; if the target software automatic test fails, the backup main program and the main database are covered with the main program and the main database which fail to be upgraded, software version rollback is completed quickly, and stable operation of the field server and correct operation of the target software are guaranteed. In addition, the data in the temporary database is synchronized to the covered main database, so that the integrity of the service data in the main database after version rollback is ensured.
As shown in fig. 6, in combination with the above temporary database switching, simplified program switching, and automated testing process, an embodiment of a software upgrading method is provided, where the embodiment includes:
s401, backing up the main database and the main program.
S402, generating a temporary database.
S403, the main program is switched to a simplified program.
S404, switching the main database into a temporary database.
And S405, upgrading the main program according to the program file in the upgrading file.
And S406, upgrading the main database according to the database script in the upgrading file.
And S407, automatically testing the upgraded software.
And S408, if the automatic test is passed, synchronizing the data in the temporary database to the successfully upgraded main database.
S409, if the automatic test fails, covering the main database which is backed up with the main database which fails to be upgraded, covering the main program which is backed up with the main program which fails to be upgraded, and switching the main program and the main database; and synchronizing the data in the temporary database to the overlaid main database.
According to the software upgrading method provided by the embodiment, the software upgrading can be realized by triggering the upgrading instruction in the software management system, the upgrading mode greatly reduces the manual participation, saves the time and the labor cost, and improves the software upgrading efficiency; when in upgrading, the upgrading is directly carried out according to the upgrade files copied in advance, the upgrade process does not need to detect the version information upgraded at present, only the upgrade files need to be considered, and the upgrade of the historical upgrade files is avoided, so that the software upgrading accuracy is improved. Moreover, in the upgrading process, a temporary database and a simplified program are adopted to temporarily take over the business data operation, the front-end business operation can be normally carried out, and the non-inductive upgrading is realized.
The implementation principle and technical effect of each step in the software upgrading method provided by this embodiment are similar to those in the foregoing software upgrading methods, and are not described herein again. The implementation manner of each step in the embodiment of fig. 6 is only an example, and is not limited to this, and the order of each step may be adjusted in practical application as long as the purpose of each step can be achieved.
The copy process of the upgrade file mentioned above is explained by embodiments as follows.
As described above, the upgrade file is copied from the software management system to the organization software system on the organization server in advance before the upgrade process is formally performed, and the software management system is a system for managing the upgrade information and upgrade operation of each organization software.
Optionally, the software management system includes a plurality of organization management pages, and each organization management page is used for managing upgrade information and software upgrade control operations of all software of a corresponding organization. Taking a hospital as an example, in the software management system, different hospital management pages correspondingly manage software of different hospitals. The software management system can comprise a communication module, a debugging module, a user management module, a state monitoring module, a statistical analysis module, a network speed testing module and the like, and can divide functional modules according to specific actual conditions. The communication module is used for managing communication between the software management system and each hospital software system or communicating with other third-party services. The debugging module is used for debugging relevant information in the software upgrading process or at the beginning of online. The user management module is used for managing the account, the authority, the password and other personalized information of the user. The state monitoring module is used for monitoring information such as running state and safety state of software in each organization (hospital). The statistical analysis module is used for analyzing information such as the upgrading times, the success rate and the use frequency of software of each mechanism. The network speed testing module is used for detecting and monitoring the network transmission speed.
Correspondingly, the software management system (running on the computer device) can communicate with the hospital software system (running on the hospital server), and the hospital software system also comprises an alarm module, a host computer communication module, an automatic test module and other modules. The alarm module is used for giving an alarm when each piece of software has an abnormal condition. The host computer communicates with the server of the hospital software system to manage the communication condition with other equipment. And the automatic test module is used for carrying out automatic test on the upgraded software.
Taking a hospital as an example, the software management system (computer device) and the hospital software system (hospital server) can communicate once every a period of time to test the network communication state and the network speed. The software management system is provided with a corresponding hospital management page for each hospital, the hospital software system installed on the hospital server corresponds to the hospital management page, and the software of the corresponding hospital can be upgraded through the hospital management page. To facilitate differentiation between hospitals, each hospital's software will be assigned an institution code to indicate differentiation at the beginning of the online session. Each hospital in the software management system maintains a page, the page contains all upgrading information and control buttons, monitoring parameters, patch version information and upgrading progress of the hospital, the functions of automatic upgrading, manual upgrading, version maintenance, upgrading process monitoring, version rollback, automatic backup, VPN connection, automatic detection of upgrading completion and the like can be provided, the whole process from software release to upgrading of each hospital is managed and maintained, for example, for uploaded upgrading files, upgrading files of each version are arranged according to the sequence of modification dates, upgrading files with newer dates contain upgrading files with older dates, and for a single hospital, incremental upgrading can be performed, and problems can not occur when certain software is upgraded. For a single hospital, automatic upgrade or manual upgrade may be set, and upgrade time may be set. If automatic upgrading is set, the system can automatically and remotely upgrade the software package of the hospital server within the set upgrading time range; if manual upgrade is set, the manual upgrade can be clicked within the set upgrade time range. The normal and stable work of the hospital field server is ensured; the on-site noninductive upgrading is realized, the workload of an engineer is reduced, the efficiency and the reliability of software upgrading are improved, and meanwhile, the remote control function is provided. It should be noted that detailed descriptions of embodiments of the software upgrading method in the present application for each function of the software management software are not repeated herein.
In addition, the software management system can provide functions of WeChat small programs, short message notification and the like so as to master the software upgrading dynamics of the hospital in real time; and the doctor is supported to submit the problems on line, and the requirements or the BUG can be directly submitted through short messages or WeChat public numbers, so that related personnel can directly receive feedback information of the hospital site, intermediate processes are omitted, and time is saved. Furthermore, the software management system supports a statistical analysis function, and is convenient for a product manager to screen extractable requirements according to statistical problems.
Before the target software is upgraded, an upgrade file used for the upgrade needs to be made, and the upgrade file needs to be transmitted to a target mechanism server through a software management system in advance. Optionally, the upgrade file is sent to the software management system after a file copy instruction is triggered in a target organization management page of the target software.
The upgrade files are named according to a certain rule after being manufactured, information such as codes and dates of corresponding mechanisms can be brought in the naming, all the upgrade files are placed under the same folder, the positions of the folders are not limited, for example, different folders can be placed in different mechanisms, and the upgrade files can be distinguished according to the year and the month. When a certain upgrading file needs to be transmitted to a corresponding mechanism server, the upgrading file meeting the conditions can be matched through the regular expression. The upgrade file includes the above-described database script and/or program file. Regular expressions are generally used to retrieve and replace texts conforming to a certain pattern (rule), and most programming languages support string operations using regular expressions.
And after the upgrading file is manufactured, transmitting the upgrading file to a target mechanism server. The transmission mode can be that a file copying instruction is triggered in a target mechanism management page of the software management system so as to send the upgrading file to a target mechanism server. The upgrade file can be placed on an external network file transfer server (FTP for short), namely the upgrade file is firstly transferred to the FTP during transfer, and then the FTP is transferred to a target mechanism server; and the file synchronization request can also be directly transmitted to a target mechanism server from a software management system, so that file synchronization failure caused by network or server poisoning is avoided, and the copying speed is increased. Optionally, the software management system may be separately installed on a terminal such as a mobile phone, and the transmission of the upgrade file may be controlled by the mobile phone.
The upgrade file is copied to a hospital server, and different transmission modes can be determined by combining the network speed condition in the actual transmission process. In one embodiment, if the network speed of the transmission network is greater than a preset network speed threshold, the upgrade file is sent by the software management system as a whole; and if the network speed of the transmission network is less than or equal to the network speed threshold value, the upgrade file is sent by the software management system in blocks. Optionally, the software management system sends the total update file information table in advance before sending the update file, and the total update file information table is used for verifying the integrity of the update file.
Before the upgrade file is transmitted, the upgrade file can be divided into N blocks with 7z suffix according to different paths, wherein the different paths refer to different storage paths, and the upgrade file storage paths with different functions are different during upgrading, namely the upgrade file can be composed of a plurality of block upgrade files. As shown in fig. 7, each block includes an upgrade file in the same path and an upgrade file total information table, in which the file storage path of each block upgrade file and basic information of all files of each block upgrade file, such as size, modification date, file name, attribute, and the like, are described. And placing the block upgrading files into a total compression file, and adding an upgrading file total information table containing total information.
Optionally, before the upgrade file is transmitted, the total upgrade file information table (txt document) is transmitted to the target mechanism server, so that the target mechanism server can compare whether the transmitted upgrade file is correct and complete according to the information recorded in the total upgrade file information table, and the comparison result is used as a basis for successful copying of the upgrade file.
As shown in fig. 8, an embodiment of a file copying method is provided, which includes the following steps:
and S1, starting.
And S2, monitoring the network state.
S3, whether the network is connected or not is judged; if yes, executing S4, if not, executing S2.
And S4, upgrading the file total information table and testing the network speed.
S5, judging whether the network speed is higher or not; if yes, go to step S6, otherwise, go to step S11.
And S6, copying the whole compressed packet.
And S7, monitoring the progress in real time.
S8, whether copying is finished or not; if yes, go to step S21, otherwise, go to step S9.
And S9, stopping due to the abnormality.
S10, whether the normal state is recovered or not is judged; if yes, executing S6, otherwise, executing S2.
And S11, decompressing the upgrade file into a block upgrade file compression packet.
And S12, upgrading file copying in blocks.
And S13, comparing the copied block upgrading file with an upgrading file total information table.
And S14, marking the successfully copied block upgrading file.
S15, stopping due to abnormality; if yes, go to step S16, otherwise, go to step S19.
S16, recording the currently copied block upgrading file
S17, judging whether the network is normal or not; if yes, go to step S18, otherwise, go to step S2.
And S18, copying from the recorded block upgrading file.
And S19, copying the monitoring progress in real time.
S20, whether copying is finished or not; if so, go to step S21, otherwise, go to step S19.
And S21, ending.
In this embodiment, in order to ensure the rapidity and accuracy of copying the upgrade file, the upgrade file is transmitted in two situations:
the first method comprises the following steps: under the condition of better network speed, the copying speed is higher. For example, whether the network speed is fast or not may be determined by comparing the network speed with a network speed threshold, and if the network speed of the transmission network is greater than a preset network speed threshold, it indicates that the upgrade file copying speed is fast.
Under the condition, the upgrade file is integrally sent, namely integrally copied, and the breakpoint continuous transmission is not needed. Generally, the upgrade file does not exceed 50M, and the overall total compression package of the upgrade file is directly transmitted to the target mechanism server. And when the target mechanism server receives the upgrade file, decompressing, comparing whether the total information table of the upgrade file is consistent with the decompressed upgrade file, and if so, indicating that the upgrade file is successfully copied. If not, it indicates that the copy failed and needs to be recopied.
The failure of copying may be that a network abnormality occurs during transmission, so that the upgrade file is not transmitted to the target mechanism server at all, for example, a network is disconnected (an automatic reminder is given), and the like. Whether the copy failure caused by the past transmission is not caused in the transmission process or the copy failure caused by the transmission of part of the file to the target structure server is caused, when the upgrade file is copied again, whether the network speed is high or not needs to be judged again, and the integral copy is determined to be continued or the block copy is switched according to a new network speed judgment result.
Second, when the network speed is not fast, for example, the network speed of the transmission network is less than or equal to the network speed threshold, the network is determined to be bad. And transmitting the upgrading file to a target mechanism server in a blocking manner according to the previous blocking upgrading files, namely copying in a blocking manner. In the process of copying the blocks, after each block upgrading file is successfully transmitted, comparing the information recorded in the total information table of the upgrading files with the information recorded in the total information table of the upgrading files, and if the block upgrading file is confirmed to be successfully copied, marking the block upgrading file as true to indicate that the block upgrading file is successfully copied. In the process of block copying, if the transmission is terminated due to network abnormality, recording the currently transmitted block upgrading file, and when the network resumes to copy again, continuing to copy the rest block upgrading files from the recorded current block upgrading file.
In the embodiment, the rapidity and the accuracy of the copy of the upgrade file are ensured by different upgrade file copy modes. Especially, the scheme of copying the upgrade file in blocks supports breakpoint continuous transmission and improves the stability of copying the upgrade file.
It should be understood that although the various steps in the flow charts of fig. 2-8 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2-8 may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed in turn or alternately with other steps or at least some of the other steps.
In one embodiment, as shown in fig. 9, there is provided a software upgrading apparatus including: switching module 10, processing module 11 and upgrading module 12, wherein:
the switching module 10 is configured to switch a main database of target software to a temporary database if an upgrade instruction of the target software sent by the software management system is received; the temporary database is used for storing data generated by the target software during upgrading;
the processing module 11 is configured to update the master database according to the upgrade file to obtain an upgraded master database;
and the upgrading module 12 is used for synchronizing the data in the temporary database to the upgraded main database to complete the upgrading of the target software.
In one embodiment, the method further comprises:
the program switching module is used for switching the main program of the target software into a preset simplified program before switching the main database of the target software into a temporary database; the simplified program is used for generating a temporary database;
and the program upgrading module is used for updating the main program according to the upgrading file to obtain the upgraded main program.
In one embodiment, the simplified program is configured to generate the temporary database based on the input-output logical relationship of the selected data in the master database.
In one embodiment, the apparatus further comprises:
the test module is used for automatically testing the upgraded main program and the upgraded main database according to a preset automatic test program;
and the test passing module is used for determining to finish the upgrading of the target software if the automatic test passes.
In one embodiment, the apparatus further comprises:
the backup module is used for backing up a main program and a main database of the target software;
and the version rollback module is used for covering the updated main program with the backed-up main database and covering the updated main database with the backed-up main database if the automatic test result fails, and synchronizing data in the temporary database to the covered main database to finish the version rollback of the target software.
In one embodiment, the software management system includes a plurality of organization management pages, and each organization management page is used for managing upgrade information and software upgrade control operation of all software of a corresponding organization; the upgrade file is sent after the software management system triggers a file copy instruction in a target mechanism management page of target software.
In one embodiment, if the network speed of the transmission network is greater than a preset network speed threshold, the upgrade file is sent by the software management system as a whole;
and if the network speed of the transmission network is less than or equal to the network speed threshold value, the upgrade file is sent by the software management system in blocks.
In an embodiment, the software management system sends the upgrade file total information table in advance before sending the upgrade file, and the upgrade file total information table is used for verifying the integrity of the upgrade file.
For specific limitations of the software upgrading device, reference may be made to the above limitations of the software upgrading method, which will not be described herein again. The modules in the software upgrading device can be wholly or partially realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as shown in fig. 10 described above. The computer device includes a processor, a memory, a communication interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operating system and the computer program to run on the non-volatile storage medium. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless communication can be realized through WIFI, an operator network, NFC (near field communication) or other technologies. The computer program is executed by a processor to implement a software upgrade method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.
Those skilled in the art will appreciate that the architecture shown in fig. 10 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having a computer program stored therein, the processor implementing the following steps when executing the computer program:
if an upgrading instruction of the target software sent by the software management system is received, switching a main database of the target software into a temporary database; the temporary database is used for storing data generated by the target software during upgrading;
updating the main database according to the upgrade file to obtain an upgraded main database;
and synchronizing the data in the temporary database to the upgraded main database to finish the upgrade of the target software.
In one embodiment, the processor, when executing the computer program, performs the steps of:
before the main database of the target software is switched to the temporary database, the main program of the target software is switched to a preset simplified program; the simplified program is used for generating a temporary database;
and updating the main program according to the upgrade file to obtain the upgraded main program.
In one embodiment, the simplified program is configured to generate the temporary database based on the input-output logical relationship of the selected data in the master database.
In one embodiment, the processor when executing the computer program implements the steps of:
according to a preset automatic test program, carrying out automatic test on the upgraded main program and the upgraded main database;
and if the automatic test is passed, determining that the target software is upgraded.
In one embodiment, the processor, when executing the computer program, performs the steps of:
backing up a main program and a main database of target software;
correspondingly, if the automatic test result fails, the backup main program is covered with the upgraded main program, the backup main database is covered with the upgraded main database, meanwhile, data in the temporary database is synchronized to the covered main database, and the version rollback of the target software is completed.
In one embodiment, the software management system includes a plurality of organization management pages, each organization management page is used for managing upgrade information and software upgrade control operation of all software of a corresponding organization;
the upgrade file is sent after the software management system triggers a file copy instruction in a target mechanism management page of target software.
In one embodiment, if the network speed of the transmission network is greater than a preset network speed threshold, the upgrade file is sent by the software management system as a whole;
and if the network speed of the transmission network is less than or equal to the network speed threshold value, the upgrade file is sent by the software management system in blocks.
In an embodiment, the software management system sends the total information table of the upgrade file in advance before sending the upgrade file, and the total information table of the upgrade file is used for verifying the integrity of the upgrade file.
The implementation principle and technical effect of the computer device provided by the above embodiment are similar to those of the above method embodiment, and are not described herein again.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:
if an upgrading instruction of the target software sent by the software management system is received, switching a main database of the target software into a temporary database; the temporary database is used for storing data generated by the target software during upgrading;
updating the main database according to the upgrade file to obtain an upgraded main database;
and synchronizing the data in the temporary database to the upgraded main database to finish the upgrade of the target software.
In one embodiment, the computer program when executed by a processor implements the steps of:
before the main database of the target software is switched to the temporary database, the main program of the target software is switched to a preset simplified program; the simplified program is used for generating a temporary database;
and updating the main program according to the upgrade file to obtain the upgraded main program.
In one embodiment, the simplified program is configured to generate the temporary database based on the input-output logical relationship of the selected data in the master database.
In one embodiment, the computer program when executed by a processor implements the steps of:
according to a preset automatic test program, carrying out automatic test on the upgraded main program and the upgraded main database;
and if the automatic test is passed, determining that the target software is upgraded.
In one embodiment, the computer program when executed by a processor implements the steps of:
backing up a main program and a main database of target software;
correspondingly, if the automatic test result fails, the backup main program is covered with the upgraded main program, the backup main database is covered with the upgraded main database, meanwhile, data in the temporary database is synchronized to the covered main database, and the version rollback of the target software is completed.
In one embodiment, the software management system includes a plurality of organization management pages, and each organization management page is used for managing upgrade information and software upgrade control operation of all software of a corresponding organization;
the upgrade file is sent after the software management system triggers a file copy instruction in a target mechanism management page of target software.
In one embodiment, if the network speed of the transmission network is greater than a preset network speed threshold, the upgrade file is sent by the software management system as a whole;
if the network speed of the transmission network is less than or equal to the network speed threshold value, the upgrade file is sent by the software management system in blocks.
In an embodiment, the software management system sends the total information table of the upgrade file in advance before sending the upgrade file, and the total information table of the upgrade file is used for verifying the integrity of the upgrade file.
The implementation principle and technical effect of the computer-readable storage medium provided by the above embodiments are similar to those of the above method embodiments, and are not described herein again.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database or other medium used in the embodiments provided herein can include at least one of non-volatile and volatile memory. Non-volatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A method of upgrading software, the method comprising:
if an upgrading instruction of target software sent by a software management system is received, switching a main program of the target software into a preset simplified program, and updating the main program according to an upgrading file to obtain an upgraded main program; the simplified program is used for generating an input-output relation table according to the input-output logic relation of the selected data in the main database, and the input-output relation table is a temporary database;
switching a main database of the target software into a temporary database; the temporary database is used for storing data generated by the target software during upgrading so as to ensure that the service operation of the target software is normally carried out and the normal service is not influenced in the upgrading process of the target software; the temporary database is generated by an executive program of the target software according to a main database of the target software;
updating the main database according to the upgrade file to obtain an upgraded main database;
synchronizing the data in the temporary database to the upgraded main database to ensure the integrity of the data of the business operation stored in the main database and finish the upgrade of the target software; and the temporary database disappears after the target software is upgraded successfully.
2. The method of claim 1, wherein the upgrade file comprises a database script and a program file.
3. The method of claim 1 or 2, wherein prior to synchronizing the data in the temporary database to the upgraded master database, the method further comprises:
according to a preset automatic test program, carrying out automatic test on the upgraded main program and the upgraded main database;
and if the automatic test is passed, determining that the target software is upgraded.
4. The method of claim 3, wherein prior to switching the main program to the simplified program, the method further comprises:
backing up a main program and a main database of the target software;
correspondingly, if the automatic test result does not pass, the backup main program covers the upgraded main program, the backup main database covers the upgraded main database, and meanwhile, data in the temporary database is synchronized to the covered main database, so that the version rollback of the target software is completed.
5. The method according to claim 1 or 2, wherein the software management system comprises a plurality of organization management pages, and each organization management page is used for managing the upgrade information and software upgrade control operation of all software of a corresponding organization;
and the upgrade file is sent after the software management system triggers a file copy instruction in a target mechanism management page of the target software.
6. The method of claim 5, wherein the upgrade file is sent by the software management system as a whole if the transmission network speed is greater than a preset network speed threshold;
and if the network speed of the transmission network is less than or equal to the network speed threshold value, the upgrade file is sent by the software management system in blocks.
7. The method according to claim 5, wherein the software management system sends an upgrade file total information table in advance before sending the upgrade file, and the upgrade file total information table is used for verifying the integrity of the upgrade file.
8. A software upgrading apparatus, characterized in that the apparatus comprises:
the system comprises a switching module, a temporary database and a software management system, wherein the switching module is used for switching a main program of target software into a preset simplified program when an upgrading instruction of the target software sent by the software management system is received, updating the main program according to an upgrading file to obtain an upgraded main program, and switching a main database of the target software into the temporary database; the simplified program is used for generating an input-output relation table according to the input-output logic relation of selected data in a main database, the input-output relation table is a temporary database, and the temporary database is used for storing data generated by the target software during upgrading so as to ensure that the service operation of the target software is normally carried out and the normal service is not influenced in the upgrading process of the target software; the temporary database is generated by an executive program of the target software according to a main database of the target software;
the processing module is used for updating the main database according to the upgrading file to obtain an upgraded main database;
the upgrading module is used for synchronizing the data in the temporary database to the upgraded main database so as to ensure the integrity of the data of the business operation stored in the main database and finish upgrading the target software; and the temporary database disappears after the target software is upgraded successfully.
9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method of any of claims 1 to 7.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011434333.7A CN112631627B (en) | 2020-12-10 | 2020-12-10 | Software upgrading method and device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011434333.7A CN112631627B (en) | 2020-12-10 | 2020-12-10 | Software upgrading method and device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112631627A CN112631627A (en) | 2021-04-09 |
| CN112631627B true CN112631627B (en) | 2023-02-24 |
Family
ID=75309046
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011434333.7A Active CN112631627B (en) | 2020-12-10 | 2020-12-10 | Software upgrading method and device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112631627B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113885894B (en) * | 2021-09-15 | 2023-12-12 | 南京海泰医疗信息系统有限公司 | Method and system for packaging and updating background based on electronic medical record products |
| CN114896261B (en) * | 2022-06-22 | 2024-04-05 | 中国平安财产保险股份有限公司 | Database upgrading method and device, computer equipment and storage medium |
Family Cites Families (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100395707C (en) * | 2006-02-07 | 2008-06-18 | 华为技术有限公司 | Method of upgrading sequence |
| US8898660B2 (en) * | 2008-11-25 | 2014-11-25 | Fisher-Rosemount Systems, Inc. | Systems and methods to provide customized release notes during a software system upgrade of a process control system |
| US10938653B2 (en) * | 2015-04-21 | 2021-03-02 | Arista Networks, Inc. | System and method of updating a network |
| CN105278962A (en) * | 2015-11-04 | 2016-01-27 | 北京星网锐捷网络技术有限公司 | Applications, hot deployment method of database and device |
| CN105354063B (en) * | 2015-11-18 | 2019-01-15 | 上海联影医疗科技有限公司 | Program on-line upgrading method and system |
| US10671376B2 (en) * | 2016-03-15 | 2020-06-02 | Shenzhen Skyworth-Rgb Electronic Co., Ltd. | Server program hot upgrading method and device |
| CN107239295B (en) * | 2016-03-29 | 2020-12-25 | 腾讯科技（深圳）有限公司 | Software upgrading method and software upgrading device |
| CN108182075A (en) * | 2017-12-29 | 2018-06-19 | 成都三零凯天通信实业有限公司 | A kind of program by the automatic escalation target software of socket communication modes |
| CN110881277A (en) * | 2018-07-04 | 2020-03-13 | 华为技术有限公司 | Data storage method, device and related equipment |
| CN111142921A (en) * | 2018-11-02 | 2020-05-12 | 成都鼎桥通信技术有限公司 | Software upgrading method and device |
| CN109683931A (en) * | 2018-12-19 | 2019-04-26 | 京信通信系统（中国）有限公司 | A kind of device updating method and WEB server |
| CN111666079B (en) * | 2019-03-05 | 2023-12-05 | 北京京东振世信息技术有限公司 | Method, apparatus, system, device and computer readable medium for software upgrade |
| CN110209405B (en) * | 2019-06-04 | 2023-06-16 | 杭州安恒信息技术股份有限公司 | Automatic upgrading method and device for distributed system |
| CN111045708B (en) * | 2019-12-20 | 2022-03-11 | 新华三大数据技术有限公司 | Software upgrading method, electronic device and computer readable storage medium |
-
2020
- 2020-12-10 CN CN202011434333.7A patent/CN112631627B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN112631627A (en) | 2021-04-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11379412B2 (en) | Enabling data replication processes between heterogeneous storage systems | |
| EP2229625B1 (en) | Updating firmware of an electronic device | |
| CN112631627B (en) | Software upgrading method and device, computer equipment and storage medium | |
| CN105940397A (en) | Application synchornization | |
| US20200192693A1 (en) | Container provision support system and container provision support method | |
| CN107797887B (en) | Data backup and recovery method and device, storage medium and electronic equipment | |
| US11252019B2 (en) | Methods, apparatuses and systems for cloud-based disaster recovery | |
| US11176002B2 (en) | Methods, apparatuses and systems for cloud-based disaster recovery | |
| US10958720B2 (en) | Methods, apparatuses and systems for cloud based disaster recovery | |
| CN112698987A (en) | On-line backup method, device, equipment and storage medium for snapshot-free operating system | |
| US20230351050A1 (en) | Method and apparatus for custom development of payment application, computer device, and storage medium | |
| US10983886B2 (en) | Methods, apparatuses and systems for cloud-based disaster recovery | |
| WO2020131483A2 (en) | Methods, apparatuses and systems for cloud-based disaster recovery | |
| Cisco | Backup and Recovery Procedures | |
| CN114721681A (en) | Configuration file updating method, device, equipment and storage medium | |
| Cisco | Backup and Recovery Procedures | |
| WO2019144555A1 (en) | Disaster recovery data online synchronization device and method, and computer readable storage medium | |
| CN111913733A (en) | Method and device for making automatic upgrade package, computer equipment and storage medium | |
| US20200117549A1 (en) | System and method for device independent backup in distributed system | |
| Silva et al. | A centralized platform for geo-distributed PACS management | |
| US20210134409A1 (en) | Report management system | |
| WO2023221002A1 (en) | Ota-based system updating method and apparatus, electronic device, and storage medium | |
| CN111026434B (en) | Configuration method, device, computer equipment and storage medium of pension system | |
| US20160275293A1 (en) | Information processing system and control method of the information processing system | |
| CN113220507B (en) | Version consistency checking method and device for double-master control system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |