CN112612494A

CN112612494A - Version update management method and related device

Info

Publication number: CN112612494A
Application number: CN202011569200.0A
Authority: CN
Inventors: 王正也; 周杰
Original assignee: Agricultural Bank of China
Current assignee: Agricultural Bank of China
Priority date: 2020-12-26
Filing date: 2020-12-26
Publication date: 2021-04-06

Abstract

The application discloses a version update management method and a related device. The self-service equipment obtains a neighboring equipment list and a file list file corresponding to the target version from a head office system; the neighboring device list comprises at least one neighboring self-service device of the self-service device which is updated to the target version; the file list file comprises file names of all version files of the target version and check codes of all version files; sending a first downloading request to the adjacent self-service equipment in the adjacent equipment list to request for downloading the version file; determining whether the version file is successfully downloaded to the self-service equipment or not according to the received check code of the file and the check code of the version file in the file list file; updating the version of the self-service equipment according to the successfully downloaded version file; and reporting the current version of the self-service equipment to the head office system after the updating is finished. The updating scheme based on the peer-to-peer network can meet the version updating requirement without additionally increasing network bandwidth, and is convenient for the control and management of the head office system on the version updating condition.

Description

Version update management method and related device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a version update management method and a related apparatus.

Background

With the continuous development of information technology and internet technology, emerging technology and bank service are continuously fused, the materialization removing characteristic of financial transaction is highlighted, the customer experience requirement is continuously improved, and the bank outlets are gradually transformed to intellectualization, light weight and marketing. The throwing-in force of the bank to the self-service equipment is continuously increased, the difficulty of centralized management work of the self-service equipment is continuously increased, and the requirements of financial enterprises on the flexibility and the expansibility of the software version of the self-service equipment are continuously improved. Financial enterprise self-service equipment relates to intelligent transformation of network points, and generally relates to counter transaction migration, program component diversification and regional business specialization, and provides numerous requirements for software version management of the self-service equipment.

The traditional self-service equipment version management mode cannot meet the complex network topology structure of a business bank head office, a branch office and a branch office. If a traditional self-service equipment version management mode is used, with the continuous increase of self-service equipment, enterprises need to continuously increase network bandwidth to meet the requirement of continuous increase of version distribution, and can not meet the customization requirements of self-service equipment software centralized control, version control, safety control and the like. Meanwhile, the traditional file distribution network cannot perform fine customized management on the version, the upgrading time (software version updating time) and the like of the equipment, cannot track the upgrading record (software version updating record) of the equipment, and therefore cannot meet the auditing requirement. Improving the software version management mode of the current self-service equipment has become a technical problem solved in the field.

Disclosure of Invention

Based on the above problems, the present application provides a version update management method and a related apparatus, so as to reduce the difficulty of version update management of self-service equipment under a complex network topology structure of head office, branch office and branch office, save network bandwidth, and implement management control of self-service equipment software version.

The embodiment of the application discloses the following technical scheme:

the first aspect of the present application provides a version update management method, where a self-service device obtains a neighboring device list and a file list file corresponding to a target version from a head office system; the list of neighboring devices includes: at least one of the self-service devices having updated to a neighboring self-service device of the target version; the file list file comprises file names of all version files of the target version and check codes of all the version files;

the self-service equipment sends a first downloading request to the adjacent self-service equipment in the adjacent equipment list so as to request for downloading the version file;

the self-service equipment determines whether the version file is successfully downloaded to the self-service equipment according to the received check code of the file and the check code of the version file in the file list file;

the self-service equipment carries out version updating on the self-service equipment according to the successfully downloaded version file;

and after the version updating is finished, the self-service equipment reports the current version of the self-service equipment to the head office system.

Optionally, each level of branch line is respectively deployed with a cache server; the self-service equipment is in communication connection with the cache server of the nearest level of branch; the cache servers of adjacent hierarchical lines are mutually communicated and connected, and the cache server of the first hierarchical line is mutually communicated and connected with the head office system; the method further comprises the following steps:

when the self-service equipment cannot successfully download the version file from the adjacent self-service equipment in the adjacent equipment list, the self-service equipment sends a second downloading request to the cache server of the nearest level branch to request for downloading the version file.

Optionally, the method further comprises:

when the self-service equipment cannot successfully download the version file from the cache server of the latest branch line, the cache server of the latest branch line sends a third download request to the cache server of the upper branch line or the head office system of the latest branch line so as to request for downloading the version file.

Optionally, the determining, by the self-service device, whether the version file is successfully downloaded to the self-service device according to the received check code of the file and the check code of the version file in the file list file includes:

the self-service equipment compares whether the check code of the received file is consistent with the check code of the version file in the file list file or not, and when the check codes are consistent, the version file is determined to be successfully downloaded to the self-service equipment; otherwise, determining that the version file is not successfully downloaded to the self-service equipment.

Optionally, the target version comprises:

a target platform version and/or a target application set version; the set of target applications includes: at least one target application to be updated.

Optionally, the check code is an md5 value.

Optionally, the method further comprises:

and when determining that a certain adjacent self-service device in the adjacent device list provides files for the self-service device overtime, the self-service device deletes the adjacent self-service device providing files overtime from the adjacent device list.

Optionally, the head office system comprises: the system comprises a head office management system, a head office deployed version server and a version issuing control server;

the self-service equipment obtains a file list file corresponding to the adjacent equipment list and the target version from the head office system, and the method specifically comprises the following steps:

the self-service equipment sends a version updating query request to the version issuing control server;

the self-service equipment receives the version number of the target version and the adjacent equipment list fed back by the version issuing control server;

and the self-service equipment obtains the file list file corresponding to the target version from the version server according to the version number of the target version.

Optionally, before the self-service device sends a version update query request to the version delivery control server, the method further includes:

and restarting the self-service equipment.

A second aspect of the present application provides a version update management apparatus, which is applied to a self-service device, and the apparatus includes:

the first acquisition module is used for acquiring a file list file corresponding to the adjacent equipment list and the target version from the head office system; the list of neighboring devices includes: at least one of the self-service devices having updated to a neighboring self-service device of the target version; the file list file comprises file names of all version files of the target version and check codes of all the version files;

a first sending module, configured to send a first download request to a neighboring self-service device in the neighboring device list to request to download the version file;

the verification module is used for determining whether the version file is successfully downloaded to the self-service equipment or not according to the received verification code of the file and the verification code of the version file in the file list file;

the version updating module is used for updating the version of the self-service equipment according to the successfully downloaded version file;

and the feedback module is used for reporting the current version of the self-service equipment to the head office system after the version updating is finished.

Compared with the prior art, the method has the following beneficial effects:

according to the version updating management method provided by the application, self-service equipment obtains a neighboring equipment list and a file list file corresponding to a target version from a head office system; the list of neighboring devices includes: at least one neighboring self-service device of the self-service devices that has been updated to the target version; the file list file comprises file names of all version files of the target version and check codes of all version files; the self-service equipment sends a first downloading request to the adjacent self-service equipment in the adjacent equipment list so as to request for downloading the version file; the self-service equipment determines whether the version file is successfully downloaded to the self-service equipment according to the received check code of the file and the check code of the version file in the file list file; the self-service equipment updates the version of the self-service equipment according to the successfully downloaded version file; and after the version updating is finished, the self-service equipment reports the current version of the self-service equipment to the head office system. The technical scheme of self-service equipment software updating management based on the Peer-to-Peer network (P2P) is customized, even if the number of self-service equipment is increased, the network bandwidth does not need to be additionally increased, the version updating requirement is met, the versions can be updated in batches, version files can be requested and obtained among the self-service equipment, and software version updating is simply, conveniently, quickly and efficiently realized. In addition, after the version is updated, the self-service equipment reports the current version to the head office system, so that the head office system can conveniently carry out overall planning and control management on the version updating condition of the self-service equipment.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive exercise.

Fig. 1 is a schematic view of an application scenario of a version update management method according to an embodiment of the present application;

fig. 2 is a flowchart of a version update management method according to an embodiment of the present application;

FIG. 3 is a flowchart of another version update management method according to an embodiment of the present application;

FIG. 4 is a schematic diagram of a self-service device sending a second download request to a cache server of a nearest level of a branch line to request downloading of a version file;

FIG. 5 is a flowchart of another version update management method according to an embodiment of the present application;

FIG. 6 is a diagram illustrating a cache server in a next-most hierarchical branch sending a third download request to a cache server in a higher hierarchical branch to request downloading of a version file;

fig. 7 is a schematic structural diagram of a version update management apparatus according to an embodiment of the present application.

Detailed Description

As described above, the conventional version management method for self-service devices is difficult to satisfy the complex network topology structure of the head office, branch office and branch office of the commercial bank, and when the number of self-service devices is continuously increased, the network bandwidth needs to be continuously increased to realize the version management of the self-service devices. In addition, the traditional self-service equipment version management mode cannot meet the customization requirements of self-service equipment software centralized control management and the like.

Based on the above problems, the inventors have studied to provide a technical solution for implementing software version update management in a peer-to-peer network. The self-service equipment which finishes version updating firstly drives other self-service equipment which does not finish version updating to realize version updating, so that the network bandwidth is saved, version management control is realized more, and the operability is stronger.

In order to make the technical solutions of the present application better understood, 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 only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

Before describing the embodiments of the present application, terms referred to in the present application will be explained first for the understanding.

The head office: financial industry headquarters such as the chinese agricultural bank.

Dividing the rows: branch institutions under the financial industry main institution, such as Beijing branch lines of China agricultural Bank, Haihu branch lines of China agricultural Bank, and the like. The partial rows may include multiple levels, such as first level partial rows, second level partial rows, and the like. The grade (level) of the division can be divided according to administrative regions, for example, the largest division of the city in the direct jurisdiction and the provincial meeting city is called a first-level division, and the largest division of the district in the direct jurisdiction and the other city-level areas except the provincial meeting is called a second-level division. And so on.

Self-service equipment: the network point is provided with an interactive environment formed by multimedia databases such as films, pictures, music and the like, thereby being specially used for storing information and providing electronic information equipment with various services such as information inquiry, printing, payment, product sale and the like. Self-service equipment in the financial industry generally includes: ATM, super counter, self-service terminal, number calling machine and the like.

A cache server: the network content which needs to be accessed frequently is stored in the server which is closer to the user and has higher access speed, so as to improve the content access speed.

The head office management system: the system for providing version management service for the self-service equipment supports the uploading of versions of a platform, a head office and a branch office, and can set the batch, time and the like issued by the versions.

Version server of head office: a server storing a version of the self-service device software.

The version of the head office issues a control server: and interacting with self-service equipment deployed at the network point, and feeding back a version to be updated (namely a target version) of the self-service equipment when the self-service equipment inquires.

Referring to fig. 1, the figure is a schematic view of an application scenario of a version update management method according to an embodiment of the present application. The application scenario shown in fig. 1 includes: the head office system 100 and the multi-level branch lines are respectively provided with cache servers W1, W2 and the like. In the figure, only two levels of rows are illustrated, and in practical applications, more levels of rows may be included, for example, three levels of rows, four levels of rows, and the like, which is not limited herein. The subordinate branches are provided with network points, and self-service equipment of the network points can be in communication connection with the cache server of the nearest branch. The adjacent-level cache servers W1 and W2 are communicatively connected to each other. The level one sub-line cache server W1 is communicatively coupled to the head line system 100. Fig. 1 also illustrates the topology of head-branch-dot.

The head office system 100 may specifically include: a head office management system 101, a version server 102 and a version issuing control server 103. The cache server W1 of the first-level branch is in communication connection with the version server 102, and the self-service device can be in communication connection with the version issuing control server 103 through an agent program.

The head office management system 101 may be understood as a management system that may be oriented to a program manager of a platform, a program manager of various applications, and a program manager of a branch system. A program manager of the platform, a program manager of various applications, and a program manager of the branch system may create a version file in the head office management system 101 by logging in an account, thereby implementing software version customization. The version server 102 of the head office may generate and store version resources from files uploaded by the head office management system 101. The version issuing control server 103 of the head office is used for responding to a version updating query request of the website self-service equipment, informing the self-service equipment of a target version, and feeding back a neighboring equipment list, so that the self-service equipment can start a file downloading and version updating process according to the indication of the version issuing control server 103 and the provided neighboring equipment list.

The version update management method provided by the present application is described in detail below with reference to embodiments.

Referring to fig. 2, the flowchart of a version update management method according to an embodiment of the present application is shown. In the flow illustrated in fig. 2, a self-service device is used as an execution subject of the method. As shown in fig. 2, the version update management method includes:

s201: and the self-service equipment obtains a file list file corresponding to the adjacent equipment list and the target version from the head office system.

The list of neighboring devices includes: at least one of the self-service devices has updated to a target version of a neighboring self-service device. As an example, in the version update management method provided in the embodiment of the present application, the self-service device to be upgraded is TERM0, and the obtained neighboring self-service devices in the neighboring device list include 10 neighboring self-service devices upgraded to the target version from TERM1 to TERM 10.

The adjacent self-service equipment can be divided according to the position of the network point or the deployment relationship between the network point and the nearest branch. For example, a kiosk that is within 3km of its perimeter of kiosk TERM0 is referred to as a proximity kiosk. Or, for example, a kiosk at a site that is affiliated with a second level branch with kiosk TERM0 becomes a neighboring kiosk. There is no limitation on the implementation of partitioning neighboring self-service devices.

In the embodiment of the present application, the head office system may manage version upgrade conditions of self-service devices at various websites, and thus may provide the above-mentioned neighboring device list to the self-service device TERM0 according to actual conditions.

The file list file comprises file names of all version files of the target version and check codes of all version files. In order to facilitate understanding of the file list file, the process of forming the file list file is described below.

In embodiments of the present application, the target version may include a target platform version and/or a target application collection version. That is, the content to be updated may include only the content to be updated of the platform portion, only the content to be updated of the application portion, or may include both the content to be updated of the platform portion and the content to be updated of the application portion. The platform supports the self-service equipment to run, and the application program runs on the self-service equipment to realize various application functions.

A program administrator of the platform can make a version program file according to various requirements of program operation, compress the version program file into a zip package, and upload a platform program version to a version server deployed by a head office in a head office management system. And the president version server decompresses the version platform and the president zip file, generates a platform version number according to an uploading sequence, and simultaneously generates a FileList. Xml file stores each file in zip compressed package and check code of corresponding file.

Program managers of various applications can make jar packages of various applications of versions according to customized service requirements of various general branches, and upload application program versions to a version server deployed by a general branch in a general branch management system. And the president version server decompresses jar packages of the version application programs, generates application program version numbers APPV1 and APPV2 according to the uploading sequence, and simultaneously generates corresponding versions of APPFileList. Xml file stores each file in jar compression package and check code of corresponding file.

The applications to be updated may include a plurality of applications, so that a branch system administrator may select appropriate application versions and combine them into PACK packages in the head office management system, and each PACK package may combine the applications according to various needs of the branch. For example, PACKV1 may contain APPV1, APPV2, while generating corresponding versions of packfilelist. Xml stores the locations of appfile list xml files corresponding to all applications in the PACK package and the check codes of the corresponding files.

The branch system administrator can distribute platform version V1 and application program set version PACKV1 to the self-service equipment TERM0 through the head office management system. The step that the version issuing control server of the head office can obtain the target version from the head office management system comprises the following steps: version V1 of the platform and/or the application suite version PACKV 1. When the target version includes both V1 and PACKV1, the file list file specifically includes: xml file and packfilelist xml file.

S202: the self-service device sends a first download request to a neighboring self-service device in the neighboring device list to request a download of the version file.

In the embodiment of the application, a peer-to-peer network mechanism is adopted for version updating. When the version of the self-service equipment TERM0 at a certain level needs to be upgraded, the system of the head office queries the nearby equipment which is upgraded, and automatically initiates polling to the queried adjacent equipment list to acquire the version file. Once the update of self-service device TERM0 is completed, the current device status is updated in the president version server to be updated, so that other nearby self-service devices that do not complete version updates can subsequently obtain the version file from the self-service device TERM 0. Step S202 specifically describes that the self-service device TERM0 sends a first download request to the self-service devices TERM 1-TERM 10.

There are usually multiple version files included in the file list file, and the TERM0 may specifically send a first download request to different neighboring self-service devices to respectively download different version files. Therefore, the downloading speed of the version files in the file list file is accelerated.

S203: and the self-service equipment determines whether the version file is successfully downloaded to the self-service equipment according to the received check code of the file and the check code of the version file in the file list file.

When the files are returned to the self-service device TERM0 by the adjacent self-service devices TERM 1-TERM 10, the files are returned, and the check codes of the files are also returned to the self-service device TERM 0. As mentioned previously, self-service device TERM0 has obtained a file list file from the head office system that contains the file name and the check code of the version file.

To determine whether a version file was successfully downloaded to self-service TERM0, self-service TERM0 can validate the version file against the check codes of files received from neighboring self-service TERMs 1-10 and the check codes of the version files in the file list file.

As a possible implementation manner, the self-service device TERM0 compares whether the check code of the received file is consistent with the check code of the version file in the file list file, and when the check codes are consistent, determines that the version file is successfully downloaded to the self-service device TERM 0; otherwise, it is determined that the version file was not successfully downloaded to self-service device TERM 0. The method for confirming whether the files of other versions are downloaded successfully is the same as the above.

S204: and the self-service equipment carries out version updating on the self-service equipment according to the successfully downloaded version file.

When the self-service device TERM0 confirms that all version files included in the file list file have been successfully downloaded to the self-service device TERM0 in the manner of S203, version updating can be performed according to the downloaded version files.

S205: and after the version updating is finished, the self-service equipment reports the current version of the self-service equipment to the head office system.

That is, after the self-service device TERM0 finishes updating the target version, it reports to the head office system that it has updated to the target version. By reporting the current version, the head office system can timely, accurately and pertinently control the version updating link and ensure the continuation of the peer-to-peer network mechanism.

The version update management method provided by the embodiment of the application is described above. According to the self-service equipment software updating management method based on the P2P network mechanism, even if the number of self-service equipment is increased, the network bandwidth does not need to be additionally increased, the version updating requirement is met, the versions can be tried in batches, version files can be requested and obtained among the self-service equipment, and software version updating is simply, conveniently, quickly and efficiently achieved. In addition, after the version is updated, the self-service equipment reports the current version to the head office system, so that the head office system can conveniently carry out overall planning and control management on the version updating condition of the self-service equipment.

With reference to the structure of the head office system 100 shown in fig. 1, in S201, the obtaining, by the self-service device, the file list file corresponding to the neighboring device list and the target version from the head office system may specifically include:

the self-service equipment sends a version updating query request to the version issuing control server 103; the self-service equipment receives the version number of the target version and the adjacent equipment list fed back by the version issuing control server 103; and the self-service equipment obtains the file list file corresponding to the target version from the version server 102 according to the version number of the target version.

In addition, in the above embodiment, S201 may be executed after each restart of the self-service device, or may be executed periodically, for example, once every 12 hours. The execution frequency and execution timing are not limited herein.

In practical application, the file name and check code of the version file may be carried in the first download request sent by the self-service device TERM0 to the neighboring self-service devices TERM 1-TERM 10. After receiving the first download request, the neighboring self-service devices TERM 1-TERM 10 may first compare whether the file with the same name exists locally, and if so, further compare the check codes of the local file and the version file, and only if the check codes are consistent, return the file to the self-service device TERM 0. If the same-name file does not exist or the check codes of the same-name files are inconsistent, the first downloading request is rejected, and the file is not transmitted back to the TERM0 of the self-service equipment.

In practical applications, the neighboring self-service devices TERM 1-TERM 10 can also choose whether to return the file or reject the first download request according to the current network conditions. For example, if neighboring kiosk TERM1 has provided file sharing services for N kiosks simultaneously (N is a set threshold, N is a positive integer), then the download request of kiosk TERM0 is denied.

In conjunction with the above description, the neighboring kiosks TERM 1-TERM 10 may reject the first download request. In addition, in practical applications, a situation of file return failure or file download timeout may also occur. That is, kiosk TERM0 may not be able to complete the download of all versions of files in the file list file from neighboring kiosks in the neighboring device list. Based on the problem, the application further provides another version update management method.

Fig. 3 is a flowchart of another version update management method according to an embodiment of the present application. As shown in fig. 3, the method includes:

s301: and the self-service equipment obtains a file list file corresponding to the adjacent equipment list and the target version from the head office system.

S302: the self-service device sends a first download request to a neighboring self-service device in the neighboring device list to request a download of the version file.

S303: and the self-service equipment determines whether the version file is successfully downloaded to the self-service equipment according to the received check code of the file and the check code of the version file in the file list file.

The implementation manners of S301 to S303 are substantially the same as those of S201 to S203 in the foregoing embodiment, and related descriptions may refer to the foregoing embodiment, which is not described herein again.

S304: and when the self-service equipment cannot successfully download the version file from the adjacent self-service equipment in the adjacent equipment list, the self-service equipment sends a second download request to the cache server of the nearest level branch to request for downloading the version file.

FIG. 4 is a schematic diagram of the self-service device sending a second download request to the cache server of the nearest level branch to request downloading of the version file. As shown in FIG. 4, when a self-service device cannot obtain a version file from a neighboring self-service device, it may choose to initiate a download request to the cache server. Thus, the problem that the adjacent self-service equipment cannot provide or completely provides the version file is solved. And the external part requests the cache server in the latest branch to download the version file, so that the return speed of the file can be ensured to be higher, and the requirement of self-service equipment for quickly updating the version can be met.

After the execution of S304 in this embodiment, similar to S303, the self-service device TERM0 may further determine whether the corresponding version file is successfully downloaded to the self-service device according to the check code of the file returned by the cache server in the latest hierarchical branch and the check code of the version file in the file list file.

S305: and the self-service equipment carries out version updating on the self-service equipment according to the successfully downloaded version file.

S306: and after the version updating is finished, the self-service equipment reports the current version of the self-service equipment to the head office system.

The implementation manners of S305 to S306 are substantially the same as the implementation manners of S204 to S205 in the foregoing embodiment, and related descriptions may refer to the foregoing embodiment, which is not described herein again.

In the version update management method introduced in the above embodiment, the self-service device sends the second download request to the cache server in the closest hierarchical branch when the self-service device cannot obtain all the version files from the neighboring self-service device, so that the success rate of downloading the version files is improved, and the version update is successfully completed.

The second download request may carry a file name and a check code of the version file. After receiving the second download request, the cache server in the latest branch can also compare whether the file with the same name exists locally, if so, further compare the check codes of the local file and the version file, and only if the check codes are consistent, the file is returned to the self-service device TERM 0. If the same-name file does not exist or the check codes of the same-name files are not consistent, the second download request is rejected, and the file is not returned to the self-service device TERM 0.

In a possible implementation manner, after the number of service files cached by the cache server deployed in each level of the line exceeds a preset number, the locally least frequently used files may be cleaned according to the LRU algorithm.

In conjunction with the above description, the cache server most recently affiliated with the self-service device may deny the second download request. In addition, in practical applications, a situation of file return failure or file download timeout may also occur. That is, the version file to be downloaded may not be available from the last level cache server by self-service device TERM 0. Based on the problem, the application further provides another version update management method.

Fig. 5 is a flowchart of another version update management method according to an embodiment of the present application. As shown in fig. 5, the method includes:

s501: and the self-service equipment obtains a file list file corresponding to the adjacent equipment list and the target version from the head office system.

S502: the self-service device sends a first download request to a neighboring self-service device in the neighboring device list to request a download of the version file.

S503: and the self-service equipment determines whether the version file is successfully downloaded to the self-service equipment according to the received check code of the file and the check code of the version file in the file list file.

S504: and when the self-service equipment cannot successfully download the version file from the adjacent self-service equipment in the adjacent equipment list, the self-service equipment sends a second download request to the cache server of the nearest level branch to request for downloading the version file.

The implementation manners of S501 to S504 are substantially the same as those of S301 to S304 in the foregoing embodiment, and related descriptions may refer to the foregoing embodiment, which is not described herein again.

S505: when the self-service equipment cannot successfully download the version file from the cache server of the latest branch line, the cache server of the latest branch line sends a third download request to the cache server of the upper branch line or the head office system of the latest branch line so as to request for downloading the version file.

Fig. 6 is a schematic diagram illustrating that the cache server in the latest subline sends a third download request to the cache server in the upper subline to request to download the version file. As shown in fig. 6, when the self-service device cannot obtain a version file from the cache server M2 of the latest level branch, the cache server M2 may initiate a third download request to the cache server M1. Thus, the problem that the cache server M2 cannot provide the version file to the self-service device is solved.

After the cache server M2 downloads the version file required by the self-service device from the cache server M1, the version file may be transmitted back to the self-service device.

If the self-service device's last level of the branch cache server is level of the branch cache server M1, the cache server M1 may request the download version file directly from the head office system. Specifically, the third download request may be sent to the version server 102 of the head office.

S506: and the self-service equipment carries out version updating on the self-service equipment according to the successfully downloaded version file.

S507: and after the version updating is finished, the self-service equipment reports the current version of the self-service equipment to the head office system.

The implementation manners of S506 to S507 are substantially the same as the implementation manners of S305 to S306 in the foregoing embodiment, and related descriptions may refer to the foregoing embodiment, which is not described herein again.

In the version update management method described in the above embodiment, the self-service device may request the download from the cache server of the closest-level branch upwards when the self-service device cannot download the version file from the cache server of the closest-level branch. Therefore, the success rate of downloading the version file is improved, and the version updating is successfully completed. Because the version server of the head office system stores and manages all version resources, the self-service equipment can necessarily obtain the version file of the target version to complete version updating.

In the above embodiments, the cache server and each self-service device may compare the check codes according to the file to realize file confirmation. In particular implementations, the check code may be formed in a number of different ways. As one possible implementation, the check code may be a hash value generated according to a cryptographic hash function, such as a 128-bit (16-byte) MD5 value. The implementation manner of generating the check code is not limited herein.

As mentioned previously, a nearby self-service device may not be able to successfully provide files to the self-service device, a problem such as a file download timeout occurs, indicating that a transmission problem has occurred. In one possible implementation, when it is determined that a neighboring self-service device in the neighboring device list provides a file timeout for the self-service device, the self-service device may delete the neighboring self-service device providing the file timeout from the neighboring device list. Avoiding the self-service device from repeatedly issuing requests to the neighboring self-service device.

Based on the embodiments introduced in the foregoing, the main idea of the technical solution of the present application is that a peer-to-peer network (P2P) mechanism is applied to self-service devices under different hierarchical organizations in the financial industry, when a self-service device under a certain level needs to perform version upgrade, a server unified by a head office queries nearby devices that complete upgrade, and automatically initiates polling to a queried device list to obtain a version file. And if the device list is failed to obtain the updated device list or the version of the device in the polling list is failed to obtain, inquiring the cache server for downloading along the topological structure.

Compared with the traditional Content Delivery Network (CDN) software and the traditional full-update version issuing mechanism, the technical scheme of the application customizes the proprietary peer-to-peer Network-based self-service equipment software management method and device according to the levels and Network deployment relations of financial institutions, headquarters, branches and Network points. The method can realize that the full download of the self-service equipment software version can be realized in an incremental updating mode under the condition of optimal network utilization. Meanwhile, a mechanism for batch trial-run and timely rollback of the equipment is designed according to special requirements of the financial industry, and fine management requirements of self-service equipment of the financial industry are met.

Based on the version update management method provided by the foregoing embodiment, correspondingly, the present application further provides a version update management apparatus, which is applied to a self-service device of a version to be updated. The following description is made with reference to the embodiments and the accompanying drawings.

Referring to fig. 7, this figure is a schematic structural diagram of a version update management apparatus according to an embodiment of the present application. As shown in fig. 7, the apparatus 700 includes:

a first obtaining module 701, configured to obtain, from a head office system, a file list file corresponding to a neighboring device list and a target version; the list of neighboring devices includes: at least one of the self-service devices having updated to a neighboring self-service device of the target version; the file list file comprises file names of all version files of the target version and check codes of all the version files;

a first sending module 702, configured to send a first download request to a neighboring self-service device in the neighboring device list to request to download the version file;

a verification module 703, configured to determine whether the version file is successfully downloaded to the self-service device according to a received verification code of the file and a verification code of the version file in the file list file;

a version update module 704, configured to update the version of the self-service device according to the successfully downloaded version file;

a feedback module 705, configured to report the current version of the self-service device to the head office system after the version update is finished.

The technical scheme of self-service equipment software updating management based on the Peer-to-Peer network (P2P) is customized, even if the number of self-service equipment is increased, the network bandwidth does not need to be additionally increased, the version updating requirement is met, the versions can be updated in batches, version files can be requested and obtained among the self-service equipment, and software version updating is simply, conveniently, quickly and efficiently realized. In addition, after the version is updated, the self-service equipment reports the current version to the head office system, so that the head office system can conveniently carry out overall planning and control management on the version updating condition of the self-service equipment.

In combination with the scenario shown in fig. 1, in practical applications, since the neighboring self-service devices in the neighboring device list may not be able to provide all version files for the self-service devices, the version update management apparatus may further include:

and the second sending module is used for sending a second downloading request to the cache server of the nearest level branch to request for downloading the version file when the self-service equipment cannot successfully download the version file from the adjacent self-service equipment in the adjacent equipment list.

Optionally, the verification module 703 is specifically configured to compare whether the verification code of the received file is consistent with the verification code of the version file in the file list file, and when the verification code of the received file is consistent with the verification code of the version file in the file list file, determine that the version file is successfully downloaded to the self-service device; otherwise, determining that the version file is not successfully downloaded to the self-service equipment.

Optionally, the target version comprises:

Optionally, the check code is an md5 value.

Optionally, the version update management apparatus may further include:

and the deleting module is used for deleting the neighboring self-service equipment which provides the file overtime from the neighboring equipment list when determining that a certain neighboring self-service equipment in the neighboring equipment list provides the file overtime for the self-service equipment.

The above description is only one specific embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present application should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A version update management method, the method comprising:

the self-service equipment obtains a neighboring equipment list and a file list file corresponding to the target version from a head office system; the list of neighboring devices includes: at least one of the self-service devices having updated to a neighboring self-service device of the target version; the file list file comprises file names of all version files of the target version and check codes of all the version files;

2. The method according to claim 1, wherein each level of branch line is respectively deployed with a cache server; the self-service equipment is in communication connection with the cache server of the nearest level of branch; the cache servers of adjacent hierarchical lines are mutually communicated and connected, and the cache server of the first hierarchical line is mutually communicated and connected with the head office system; the method further comprises the following steps:

3. The method of claim 2, further comprising:

4. The method according to any one of claims 1-3, wherein the self-service device determining whether the version file was successfully downloaded to the self-service device according to the received check code of the file and the check code of the version file in the file list file comprises:

5. The method of claim 1, wherein the target version comprises:

6. The method of claim 1, wherein the check code is an md5 value.

7. The method of claim 1, further comprising:

8. The method of claim 1, wherein the head office system comprises: the system comprises a head office management system, a head office deployed version server and a version issuing control server;

9. The method of claim 8, wherein before the self-service device sends a version update query request to the version delivery control server, the method further comprises:

and restarting the self-service equipment.

10. A version update management device is applied to self-service equipment, and comprises: