CN109324821B - Self-service terminal system version management method - Google Patents
Self-service terminal system version management method Download PDFInfo
- Publication number
- CN109324821B CN109324821B CN201811178136.6A CN201811178136A CN109324821B CN 109324821 B CN109324821 B CN 109324821B CN 201811178136 A CN201811178136 A CN 201811178136A CN 109324821 B CN109324821 B CN 109324821B
- Authority
- CN
- China
- Prior art keywords
- file
- version
- self
- service terminal
- files
- 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
- G06F8/658—Incremental updates; Differential updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Abstract
The invention discloses a self-service terminal system version management method. After the system file of the new version is checked and compared with the original version, the incremental file is stored in the database instead of forming a patch package. Therefore, the database stores file information of all versions, and the development process of the system version can be conveniently checked through the database. Meanwhile, the database is adopted to store the system version files, when the system files are tampered or the versions need to be rolled back at the self-service terminal, only the required system files stored in the database need to be directly read and packaged, the problem that designated files are difficult to be extracted from a plurality of patch packages when the files of a plurality of different versions are needed under the condition that patch package upgrading is adopted is avoided, the process is simplified, and the efficiency is improved.
Description
Technical Field
The invention relates to a self-service terminal system version management method.
Background
At present, with the gradual progress of intellectualization and paperless, some service industry units with large flow of people and manual counters for providing simple services are being replaced by equipment such as self-service terminals. Such as banks, hospitals and the like, various self-service terminals are used for providing intelligent operation services for customers, and good effects are obtained.
Hospitals, as medical service providers, have certain specialties, such as large-scale comprehensive hospitals, which include many different departments. This also puts higher demands on the use of self-service terminals, that is, one hospital may need hundreds of self-service terminals to operate and provide services at the same time, and then needs to control the operation of all the self-service terminals at the same time, so that the software systems operating on the self-service terminals also need to be managed uniformly, so as to avoid the background data confusion caused by the non-uniformity of the system data. Meanwhile, as the hospital has a plurality of different departments, the requirements of the departments on the self-service terminal are different, and even the specific requirements of the department of the hospital and the department of the clinic are different. And because hundreds of self-service terminals run continuously at the same time, when the software system is upgraded, a plurality of self-service terminals are generally adopted to upgrade and run in a trial mode, problems are discovered and processed in time, and after the new version is stable, the software system is pushed to all the self-service terminals, so that when the self-service terminals are uniformly controlled, different program versions of different self-service terminals are allowed. Moreover, because the flow of people in the hospital is large, each self-service terminal cannot be strictly protected, and therefore, when the self-service terminal program is tampered, the function of conveniently restoring the system to a correct program should be achieved.
Disclosure of Invention
In order to solve the technical problem that hospitals have more requirements on the operation of self-service terminals at present, the invention provides a self-service terminal system version management method capable of uniformly managing the self-service terminals.
In order to achieve the technical purpose, the technical scheme of the invention is as follows:
a self-service terminal system version management method comprises the following steps:
and updating the new version:
step one, uploading a new version: uploading the self-service terminal system file of the new version to a server through a monitoring background to generate a version number, reading the system file of the last version from a database through the monitoring background, performing matching verification on the system files of the two versions, and storing the incremental file to the database so as to finish uploading the new version;
step two, issuing a new version: selecting a self-service terminal needing system updating for issuing, packaging a system increment file of a version required by the self-service terminal from a database by a monitoring background to form an increment updating package, and generating a version issuing instruction to the database;
step three, executing the new version update: when the terminal updating program is started, calling an interface to check whether an updating and issuing instruction exists, and if the updating and issuing instruction exists, downloading an incremental updating package and updating;
in the first step, after the self-service terminal system file of the new version is uploaded to the server, the method further comprises the step of deleting the junk file, wherein the junk file is a file irrelevant to a file required by system upgrading.
In the first step, after deleting the junk files, the method further comprises the step of detecting whether the uploaded system files still have files, namely detecting whether the junk files are mistakenly transmitted as the system files, if yes, continuing to execute the subsequent steps, and if not, stopping executing.
In the step one, the generated version number is synthesized as the version number of the uploaded system file according to the large version number information stored in the uploaded system file and the uploading times of the system file with the large version number.
In the first step, the matching verification of the system files of the two versions is performed according to md5 and a file url.
In the first step, after matching and checking the system files of the two versions, if no incremental file exists, the error transmission is judged to occur, and the subsequent steps are stopped.
The version management method of the self-service terminal system further comprises the following steps of rolling back versions:
the monitoring platform executes the version issuing action of the corresponding rollback version to the self-service terminal needing to perform the version rollback: the monitoring background packs the system increment files of the versions required by the self-service terminal from the database to form an increment rollback package, and generates a version issuing instruction to the database; and when the terminal updating program is started, calling an interface to check whether a rollback issuing instruction exists, if so, downloading the incremental rollback package, deleting the system file of the original version, and installing the incremental rollback package.
The self-service terminal system version management method further comprises the following steps of version self-checking:
the terminal updating program scans the system files of the current self-service terminal and uploads the scanning information to the monitoring background, the monitoring background reads the full file list of the version of the terminal and checks the full file list, and finally two sets are obtained: and (3) adding and modifying a file information set and deleting a file information set after the version is updated, packaging the added file, returning the two sets and the download address, downloading and covering the tampered file if the differentiated file to be downloaded exists after self-checking, and deleting the file if the differentiated file to be deleted exists.
In the self-service terminal system version management method, the monitoring background reads and verifies the full file list of the version of the terminal, and the file md5 and the file URL are uploaded to the monitoring background through an interface for verification.
The invention has the technical effect that after the system file of the new version is checked and compared with the original version, the incremental file is stored in the database instead of forming a patch package. Therefore, the database stores file information of all versions, and the development process of the system version can be conveniently checked through the database. Meanwhile, the database is adopted to store the system version files, when the system files are tampered or the versions need to be rolled back at the self-service terminal, only the required system files stored in the database need to be directly read and packaged, the problem that designated files are difficult to be extracted from a plurality of patch packages when the files of a plurality of different versions are needed under the condition that patch package upgrading is adopted is avoided, the process is simplified, and the efficiency is improved.
Drawings
FIG. 1 is a schematic view of a process for uploading a new version system file according to the present invention;
FIG. 2 is a schematic diagram of a process for issuing a new version system file according to the present invention;
fig. 3 is a schematic flow chart of the system rollback of the present invention.
Detailed Description
Referring to fig. 1, the present invention, when executing a new version update, includes the following steps:
the method comprises the steps that firstly, a monitoring background uploads a self-service terminal system file of a new version to a server to generate a version number, then the monitoring background reads the system file of the previous version from a database, matching and checking the system files of the two versions, and an incremental file is stored in the database, so that the uploading of the new version is completed;
step two, issuing a new version: selecting a self-service terminal needing system updating for issuing, packaging a system increment file of a version required by the self-service terminal from a database by a monitoring background to form an increment updating package, and generating a version issuing instruction to the database;
step three, executing the new version update: when the terminal updating program is started, calling an interface to check whether an updating and issuing instruction exists, and if the updating and issuing instruction exists, downloading an incremental updating package and updating;
when the system file update is developed, some files which are irrelevant to the system update may be stored in the update version file, such as a log file, a temporary file, and the like. When the new version is released, the files may be wrongly uploaded to the release version, and since the files are likely to be identified as the incremental files generated by the system upgrade in the verification process after being uploaded to the self-service terminal, the method further comprises the step of deleting the junk files after the system files of the new version are uploaded to the server, so that the purity of the system files is ensured. The junk files are files which are irrelevant to files required by system upgrading and include, but are not limited to, the log files, the temporary files and the like, specific junk file identification can be classified and summarized by a research and development party, and the new version system files are uploaded to a server and then are correspondingly checked and deleted.
Because the system files of the new version are generally released by manual uploading, and manual operation may have errors, that is, a series of files which are all garbage files may be mistakenly transmitted as the system files of the new version, when the garbage files are detected, all the files are deleted, that is, the uploaded system files are deleted to be empty files. Therefore, after the junk files are deleted, the method also comprises the step of detecting whether the uploaded system files have files, namely detecting whether the junk files are mistakenly transmitted as the system files, if so, continuing to execute the subsequent steps, otherwise, stopping execution so as to avoid other errors.
In order to distinguish the system files uploaded at different periods, the system file uploading method generates a corresponding version number when the system files are uploaded, and the version number is synthesized as the version number of the uploaded system files according to the large version number information stored in the uploaded system files and the uploading times of the system files with the large version number. The large version number information stored in the system file is generally recorded in a specific encrypted file, the large version number is parsed from the encrypted file, then the small version number is accumulated backwards according to the uploading times of the system file adopting the large version number, for example, the large version number is 1.2, the system file adopting the large version number 1.2 received this time is the 3 rd uploaded system file, and the generated version number is 1.2.03. The use mode of the specific version number can be adjusted according to the actual situation.
In order to perform accurate matching verification and improve efficiency as much as possible, the matching verification is performed according to md5 and the file url when performing matching verification of the system files of the two versions. The file URL is a path of a file, and a file name and a file suffix are reserved from the outermost directory of the program file.
Similarly, in order to prevent the system file with the same version as the previous version from being mistransmitted, after the system files of the two versions are subjected to matching verification, if no incremental file exists, the mistransmission is judged to occur, and the subsequent steps are stopped.
When a new system file generated by the self-service terminal does not adapt to the current operation requirement, or a new version has a problem and needs to return to a previous version, the monitoring platform executes a version issuing action of a corresponding rollback version to the self-service terminal needing to rollback the version: the monitoring background packs the system increment files of the versions required by the self-service terminal from the database to form an increment rollback package, and generates a version issuing instruction to the database; and when the terminal updating program is started, calling an interface to check whether a rollback issuing instruction exists, if so, downloading the incremental rollback package, deleting the system file of the original version, and installing the incremental rollback package.
In order to restore the self-service terminal lost by the system file to a normal system caused by tampering or system error of the system file, the invention also comprises a version self-checking step: the terminal updating program scans the system files of the current self-service terminal and uploads the scanning information to the monitoring background, the monitoring background reads the full file list of the version of the terminal and checks the full file list, and finally two sets are obtained: and (3) adding and modifying a file information set and deleting a file information set after the version is updated, packaging the added file, returning the two sets and the download address, downloading and covering the tampered file if the differentiated file to be downloaded exists after self-checking, and deleting the file if the differentiated file to be deleted exists.
Similarly, in order to perform accurate matching verification and improve efficiency as much as possible, the monitoring background reads the full-text file list of the version of the terminal and performs verification, namely, the file md5 and the file URL are uploaded to the monitoring background through an interface for verification.
In fact, when the terminal program file is tampered or lost, two steps are generally required to be performed: firstly, program files of the self-service terminal are verified, so that version information of the self-service terminal and file information of the whole version (not a patch package) are required to be stored in a background; second, the difference file and the missing file (which may exist separately in multiple versions of the upgrade patch) are extracted and packaged into a specific restore patch package for the terminal.
If the system updating is carried out in the form of the patch package, the related information of the system file needs to be stored additionally, and if the updating is carried out in the form of the database of the invention, the related information is already stored in the database and does not need to be stored additionally. In order to implement the second step, the specified files must be extracted from each patch package and then repackaged into a special patch package, which is difficult, and especially has very low efficiency in case of concurrence. However, for storing the file in the database, the file stream can be directly read from each version and then packaged into a special restoration patch package, so that the process is very simple and the efficiency is high.
Claims (8)
1. A self-service terminal system version management method is characterized by comprising the following steps:
and updating the new version:
step one, uploading a new version: uploading the self-service terminal system file of the new version to a server through a monitoring background to generate a version number, reading the system file of the last version from a database through the monitoring background, performing matching verification on the system files of the two versions, and storing the incremental file to the database so as to finish uploading the new version;
step two, issuing a new version: selecting a self-service terminal needing system updating for issuing, packaging a system increment file of a version required by the self-service terminal from a database by a monitoring background to form an increment updating package, and generating a version issuing instruction to the database;
step three, executing the new version update: when the terminal updating program is started, calling an interface to check whether an updating and issuing instruction exists, and if the updating and issuing instruction exists, downloading an incremental updating package and updating;
further comprising the step of rolling back the version:
the monitoring platform executes the version issuing action of the corresponding rollback version to the self-service terminal needing to perform the version rollback: the monitoring background packs the system increment files of the versions required by the self-service terminal from the database to form an increment rollback package, and generates a version issuing instruction to the database; and when the terminal updating program is started, calling an interface to check whether a rollback issuing instruction exists, if so, downloading the incremental rollback package, deleting the system file of the original version, and installing the incremental rollback package.
2. The self-service terminal system version management method according to claim 1, wherein in the first step, after the self-service terminal system file of the new version is uploaded to the server, the method further comprises a step of deleting the junk file, wherein the junk file is a file irrelevant to a file required by system upgrading.
3. The self-service terminal system version management method according to claim 2, characterized in that in the first step, after deleting the junk file, the method further comprises a step of detecting whether a file still exists in the uploaded system file, that is, detecting whether the junk file is mistakenly transmitted as the system file, if so, continuing to execute the subsequent steps, otherwise, stopping executing.
4. The self-service terminal system version management method according to claim 1, wherein in the first step, the generation of the version number is integrated as the version number of the uploaded system file according to the large version number information stored in the uploaded system file and the uploading times of the system file with the large version number.
5. The self-service terminal system version management method according to claim 1, wherein in the first step, matching verification is performed on the two versions of system files according to md5 and a file url.
6. The self-service terminal system version management method according to claim 1, characterized in that in the first step, after matching verification is performed on the system files of the two versions, if no incremental file exists, it is determined that mistransmission occurs, and execution of the subsequent steps is stopped.
7. The self-service terminal system version management method according to claim 1, further comprising a version self-check step:
the terminal updating program scans the system files of the current self-service terminal and uploads the scanning information to the monitoring background, the monitoring background reads the full file list of the version of the terminal and checks the full file list, and finally two sets are obtained: and (3) adding and modifying a file information set and deleting a file information set after the version is updated, packaging the added file, returning the two sets and the download address, downloading and covering the tampered file if the differentiated file to be downloaded exists after self-checking, and deleting the file if the differentiated file to be deleted exists.
8. The self-service terminal system version management method according to claim 7, wherein the monitoring background reads and verifies a full file list of the version of the terminal, and uploads a file md5 and a file URL to the monitoring background through an interface for verification.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811178136.6A CN109324821B (en) | 2018-10-10 | 2018-10-10 | Self-service terminal system version management method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811178136.6A CN109324821B (en) | 2018-10-10 | 2018-10-10 | Self-service terminal system version management method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109324821A CN109324821A (en) | 2019-02-12 |
| CN109324821B true CN109324821B (en) | 2021-11-05 |
Family
ID=65261967
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811178136.6A Active CN109324821B (en) | 2018-10-10 | 2018-10-10 | Self-service terminal system version management method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109324821B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111061699B (en) * | 2019-11-05 | 2024-02-09 | 广西电网有限责任公司 | Method and device for updating version of electric energy meter database |
| CN110826030B (en) * | 2019-11-08 | 2023-09-15 | 湖南长城医疗科技有限公司 | Self-service software and related module authorization use method |
| CN112434051A (en) * | 2020-11-03 | 2021-03-02 | 北京思特奇信息技术股份有限公司 | Method and system for efficiently storing music copyright data |
| CN114020299A (en) * | 2021-11-16 | 2022-02-08 | 四川长虹电器股份有限公司 | Method for updating android device system file |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103701930A (en) * | 2014-01-07 | 2014-04-02 | 浙江大学 | Mobile application program real-time updating method and system |
| CN103713928A (en) * | 2013-12-31 | 2014-04-09 | 优视科技有限公司 | Incremental file generating method, and application program installing file updating method and device |
| CN105591824A (en) * | 2016-01-14 | 2016-05-18 | 杭州赫智电子科技有限公司 | Method and system for firmware upgrade |
| CN105763369A (en) * | 2016-02-04 | 2016-07-13 | 湖南长城信息金融设备有限责任公司 | Terminal equipment remote software version distribution method and system |
| EP3070621A1 (en) * | 2015-03-16 | 2016-09-21 | HERE Global B.V. | Version management for incrementally compiled map data |
| CN106648716A (en) * | 2015-10-30 | 2017-05-10 | 北京数码视讯科技股份有限公司 | Increment updating method, server and intelligent card |
| CN108469960A (en) * | 2017-07-28 | 2018-08-31 | 新华三技术有限公司 | A kind of method for edition management and device |
-
2018
- 2018-10-10 CN CN201811178136.6A patent/CN109324821B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103713928A (en) * | 2013-12-31 | 2014-04-09 | 优视科技有限公司 | Incremental file generating method, and application program installing file updating method and device |
| CN103701930A (en) * | 2014-01-07 | 2014-04-02 | 浙江大学 | Mobile application program real-time updating method and system |
| EP3070621A1 (en) * | 2015-03-16 | 2016-09-21 | HERE Global B.V. | Version management for incrementally compiled map data |
| CN106648716A (en) * | 2015-10-30 | 2017-05-10 | 北京数码视讯科技股份有限公司 | Increment updating method, server and intelligent card |
| CN105591824A (en) * | 2016-01-14 | 2016-05-18 | 杭州赫智电子科技有限公司 | Method and system for firmware upgrade |
| CN105763369A (en) * | 2016-02-04 | 2016-07-13 | 湖南长城信息金融设备有限责任公司 | Terminal equipment remote software version distribution method and system |
| CN108469960A (en) * | 2017-07-28 | 2018-08-31 | 新华三技术有限公司 | A kind of method for edition management and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109324821A (en) | 2019-02-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109324821B (en) | Self-service terminal system version management method | |
| US9565250B2 (en) | Data transfer service | |
| US9235411B2 (en) | Automated application generation | |
| US9754242B2 (en) | Deployment mechanism for non-versioning business process artifacts | |
| US8954949B2 (en) | Smart patch delivery system | |
| US20060080653A1 (en) | Methods and systems for patch distribution | |
| CN111162953B (en) | Data processing method, system upgrading method and server | |
| US9384020B2 (en) | Domain scripting language framework for service and system integration | |
| CN106575227B (en) | Automatic software update framework | |
| US20140208169A1 (en) | Domain scripting language framework for service and system integration | |
| CN106815049B (en) | Method and device for upgrading feature library | |
| CN108052336A (en) | A kind of distributed software upgrade-system and its implementation | |
| US7181739B1 (en) | Installation relationship database | |
| CN111694612A (en) | Configuration checking method, device, computer system and storage medium | |
| CN111338656A (en) | Method and device for installing software package to target host and computer equipment | |
| EP2897046A1 (en) | Method and device for installing assembly-type multi-mode network management patch pack | |
| CN112328284A (en) | Application program upgrading method, system, equipment and storage medium | |
| EP3346642A1 (en) | Method and device for managing network element model | |
| JP4621709B2 (en) | Version management system and program version management method | |
| CN105303116A (en) | ERP (enterprise resource planning) product security protection apparatus and method | |
| US20150033213A1 (en) | Compiling method, storage medium and compiling apparatus | |
| CN114978904A (en) | Remote firmware upgrading method, system, device, embedded equipment and storage medium | |
| CN113157307A (en) | Software version upgrading method and device | |
| CN112165512B (en) | File release method and device, terminal equipment and storage medium | |
| CN113032006B (en) | Plug-in construction method, device, equipment and storage medium |
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 |