Bank batch equipment management method, device and equipment
By combining automated configuration file management with CDN technology, the version management method solves the security and network congestion problems in the batch device version management of banks, and achieves efficient and secure device version updates.
Patent Information
- Application Number
- CN202511071124.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-07-31
- Publication Date
- 2025-10-31
AI Technical Summary
Existing bank batch device version management methods have problems such as failing to verify the integrity and security of version files, failing to consider bandwidth availability and utilization, and failing to recommend a complete dynamic rollback mechanism, resulting in unsatisfactory management results.
An automated version management method based on configuration files is adopted, combined with CDN file distribution technology, multi-layer rate limiting strategies and bandwidth hierarchical management. Through a triple verification mechanism at the device, server and cloud ends, the security and integrity of version files are guaranteed, and an intelligent download scheduling algorithm is used to avoid network congestion.
It has enabled automated management of batch device versions in the bank, ensuring the security and integrity of version files, avoiding network congestion, ensuring the timeliness and efficiency of device updates, and improving the convenience and security of device management.
Smart Images
Figure CN120880904A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of computer technology, and in particular to a method, apparatus and equipment for managing batch equipment in a bank. Background Technology
[0002] With the rapid development of the social economy, major banks, as the center of financial services, have hundreds of thousands of terminal devices covering cities, towns and villages, including but not limited to super counters, ATMs and counter terminals.
[0003] On the one hand, the functionality of these batch devices needs continuous updates to meet ever-changing business demands; on the other hand, these devices need to operate stably and uninterruptedly, providing continuous services. Therefore, efficient management and timely updates of these device versions are essential. However, current common methods for batch device version management include script-based automatic updates or manual version management. These methods suffer from a series of problems, such as failing to verify the integrity and security of version files, neglecting bandwidth availability and utilization, and lacking a robust dynamic rollback mechanism, thus failing to achieve the desired management results. Summary of the Invention
[0004] The main objective of this application is to provide a method, apparatus, and device for batch management of bank devices, which can automate the entire process from application updates, version building, and version distribution based on configuration files. By utilizing CDN file distribution technology combined with multi-layered rate limiting strategies and bandwidth tiered management schemes, each branch can download device version files from the nearest branch, while ensuring reasonable bandwidth utilization, preventing bandwidth congestion, and achieving timely response and efficient version file download, thus achieving the desired batch device management effect.
[0005] This application provides a method for managing batch devices in a bank, including:
[0006] Obtain the configuration files and configuration information from the target bank's application package;
[0007] Based on the configuration file, complete the corresponding application version update and build the overall application version; and based on the configuration information, build the corresponding platform version;
[0008] The constructed platform version, the overall application version, and the updated application version are distributed to the branch equipment of the target bank through a Content Delivery Network (CDN) file, and intelligent application version updates are implemented with multi-level rate limiting and bandwidth management.
[0009] In one optional implementation, the fields of the configuration file include at least one of the following: application ID, application name, application version, and usage channel; the configuration information includes at least one of the following: application ID and version information, total application version name, applicable channel, earliest effective time, and latest effective time.
[0010] In one alternative implementation, the method further includes:
[0011] When building the overall application version and / or platform version, set the earliest and latest effective times for the version, and specify that the overall application version is available within a specific time range;
[0012] During the process of distributing the equipment to the branch offices of the target bank, the earliest download time and download interval for each device are set.
[0013] In one alternative implementation, the method further includes:
[0014] During the branch equipment update process of the target bank, a triple verification mechanism combining device-side SM3 fast verification, server-side signature verification, and cloud-based integrity auditing is used to verify the version files in order to ensure the integrity and security of the version files.
[0015] Corresponding to the above-mentioned bank batch equipment management method, this application proposes a bank batch equipment management device, comprising:
[0016] The acquisition unit is used to acquire configuration files and configuration information from the target bank's application package;
[0017] The building unit is used to complete the corresponding application version update and build the total application version according to the configuration file; and to build the corresponding platform version according to the configuration information.
[0018] The distribution unit is used to distribute the constructed platform version, the overall application version, and the updated application version to the branch equipment of the target bank through a Content Delivery Network (CDN) file, and to implement intelligent application version updates with multi-level rate limiting and bandwidth management.
[0019] In one optional implementation, the fields of the configuration file include at least one of the following: application ID, application name, application version, and usage channel; the configuration information includes at least one of the following: application ID and version information, total application version name, applicable channel, earliest effective time, and latest effective time.
[0020] In one alternative implementation, the apparatus further includes:
[0021] The first setting unit is used to set the earliest effective time and the latest effective time of the version when building the total application version and / or platform version, and to specify that the total application version is available within a specific time range;
[0022] The second setting unit is used to set the earliest download time and download interval for each device during the process of distributing the equipment to the branch equipment of the target bank.
[0023] In one alternative implementation, the apparatus further includes:
[0024] The verification unit is used to verify version files during the branch equipment update process of the target bank. It employs a triple verification mechanism that combines device-side SM3 fast verification, server-side signature verification, and cloud-based integrity auditing to ensure the integrity and security of version files.
[0025] This application embodiment also provides a bank batch equipment management device, including: a processor, a memory, and a system bus;
[0026] The processor and the memory are connected via the system bus;
[0027] The memory is used to store one or more programs, the one or more programs including instructions, which, when executed by the processor, cause the processor to perform any of the above-described implementations of the bank batch equipment management method.
[0028] This application also provides a computer-readable storage medium storing instructions that, when executed on a terminal device, cause the terminal device to perform any of the above-described bank batch device management methods.
[0029] Therefore, the embodiments of this application have the following beneficial effects:
[0030] This application provides a method, apparatus, and device for batch device management in a bank. First, it obtains the configuration file and configuration information from the target bank's application package. Then, based on the configuration file, it updates the corresponding application version and builds the overall application version. Next, based on the configuration information, it builds the corresponding platform version. Then, it distributes the built platform version, the overall application version, and the updated application version to the target bank's branch devices via a Content Distribution Network (CDN) file, implementing intelligent application version updates with multi-level rate limiting and bandwidth management. This allows each branch to download the device version file from the nearest location, ensuring reasonable bandwidth utilization, preventing bandwidth congestion, achieving timely response, and efficiently downloading version files, thus achieving the desired batch device management effect. Attached Figure Description
[0031] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0032] Figure 1 A flowchart illustrating a bank's batch equipment management method provided in this application embodiment;
[0033] Figure 2 A diagram illustrating the overall implementation process of bank batch device management provided in this application embodiment;
[0034] Figure 3 A schematic diagram illustrating the distribution of files to a target bank's branch equipment via CDN, provided as an embodiment of this application.
[0035] Figure 4 This is a schematic diagram of the composition of a bank batch equipment management device provided in an embodiment of this application. Detailed Implementation
[0036] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0037] Currently, banks have hundreds of thousands of financial equipment terminals covering cities, towns, and rural areas, including self-service teller machines, ATMs, and counter terminals. These devices are complex in type, geographically dispersed, and used in diverse environments. These characteristics present significant challenges to device version management. Traditional manual upgrade methods suffer from low efficiency, high compatibility risks, difficulty in security control, network congestion, and a lack of rollback mechanisms, failing to achieve ideal device management results.
[0038] Based on this, and to address the aforementioned problems in the existing technology, this application proposes a method, apparatus, and device for batch management of bank devices. Based on configuration files, it can fully automate application updates, version building, and version distribution. Furthermore, it can build different versions to meet the version requirements of different devices, taking into account the needs of each branch. Simultaneously, during the device version update phase, this invention distributes version files based on CDN, utilizes a triple verification mechanism to ensure the integrity and security of version files, and proposes an intelligent bandwidth scheduling algorithm to rationally utilize the network bandwidth of each branch, avoiding network congestion and achieving timely and efficient updates of device versions for each branch.
[0039] Among them, channels refer to the types of equipment used for customer services in bank branches, including super counters, self-service cash terminals (ATMs), counter terminals, queuing machines, and foreign exchange machines.
[0040] CDN refers to an intelligent virtual network built on the foundation of the existing network. By deploying cache clusters in various locations and combining the load balancing, content distribution and scheduling functions of the central platform, it enables users to obtain content from the nearest location, reduces network congestion, and improves access speed and cache hit rate.
[0041] CDN servers are the caching and distribution servers closest to the user in a CDN network, also known as edge servers. They are deployed in clusters, distributed across various first-level branches and the head office, and are uniformly managed by the bank's next-generation intranet CDN platform. They are responsible for storing and providing cached content to reduce content transmission latency and improve user access speed.
[0042] Automated execution refers to the ability to update hundreds of applications, build dozens of application master versions (platform versions), and release versions to tens of thousands of devices within 3 minutes through a pipeline. This process can meet the application version requirements of different branches and channels, as well as the platform version requirements of different operating system types. No manual intervention is required, greatly improving the security and convenience of device version management.
[0043] The bank batch equipment management method provided in this application will be described in detail below with reference to the accompanying drawings. See also Figure 1 The diagram illustrates a flowchart of an embodiment of a bank batch equipment management method provided in this application. This embodiment may include the following steps:
[0044] S101: Obtain the configuration file and configuration information from the target bank's application package.
[0045] In this embodiment, any bank that adopts the batch device management method provided in this application is defined as the target bank. In order to improve the management effect, it is first necessary to obtain the configuration file and configuration information in the target bank's application package to execute the subsequent step S102.
[0046] The specific content of the configuration file is not limited, and may include, but is not limited to, at least one of the following: application ID, application name, application version, and usage channel. The specific content of the configuration information is also not limited, and may include, but is not limited to, at least one of the following: application ID and version information, total application version name, applicable channels, earliest effective time, and latest effective time.
[0047] Specifically, before execution, the pipeline first populates a code resource package containing corresponding configuration files. Upon entering the actual execution phase, the server first parses the configuration file in the application package (fields include application ID, application name, application version, and usage channel, etc.), and updates the corresponding application version based on the configuration information. Since the application scope and version usage vary across different branches, the server then generates the corresponding total application version using the configuration information (application ID and version information, total application version name, applicable channels, earliest effective time, and latest effective time, etc.). Figure 2 As shown, this allows for the fulfillment of the different application versions required by devices in different branches and channels.
[0048] Similarly, during the platform version build process, multiple platform versions will be generated based on configuration files (operating system type, applicable operating system channels, earliest effective time, and latest effective time, etc.), such as... Figure 2 As shown, this is to meet the platform version requirements of different types of devices.
[0049] S102: Based on the configuration file, complete the corresponding application version update and build the overall application version; and based on the configuration information, build the corresponding platform version.
[0050] S103: The platform version, application version, and updated application version are distributed to the branch equipment of the target bank through the Content Delivery Network (CDN) file, and intelligent application version updates are implemented with multi-level rate limiting and bandwidth management.
[0051] In this embodiment, after obtaining the configuration file and configuration information in the target bank application package through step S101, the corresponding application version can be updated and the overall application version can be built according to the configuration file; and the corresponding platform version can be built according to the configuration information.
[0052] Specifically, after completing the construction of the overall application version and platform version, the versions can be distributed to the branch's devices as needed. To further ensure the smoothness and security of device version downloads and prevent branch bandwidth congestion or even network paralysis caused by a large number of devices updating simultaneously, the following measures can be taken: First, when building the overall application version or platform version, the earliest and latest effective times of the version can be set, specifying that the overall application version is available within a specified time range. Second, during the distribution to the target bank's branch devices, the earliest download time and download interval (e.g., 5 seconds) for each device can be set, allowing devices to download at staggered times.
[0053] For example, the application version V for the super counter needs to be distributed to 1000 super counter devices in Branch A. Let's assume we set the earliest effective time for the application version to 9 PM tonight, and the earliest download time for each device to be 8 PM today, with a download interval of 5 seconds. Based on this configuration, the first device in Branch A will start downloading application version V at 8:00:00 PM, the second device at 8:00:05 PM, and so on, completing the version download for all 1000 devices. The new version will only become effective at 9 PM. This allows us to schedule the downloads at different times and in batches, strictly controlling the available time range of the version, further improving the security of branch device version management and the rationality of branch bandwidth usage.
[0054] After the version is distributed to the devices, how the devices update to the new version, how to prevent file tampering, how to ensure bandwidth availability, and how to quickly roll back the version are all key issues that need to be addressed in the process of batch device version management. To address this, the solution proposed in this application is designed to meet the version update needs of massive terminal devices such as self-service equipment in bank branches. It utilizes a multi-dimensional technical architecture design, such as... Figure 3 As shown, this effectively solves the problems of concurrent download congestion, insufficient version integrity guarantee, and poor service continuity in traditional version management. This application constructs a complete version management technology system based on four core dimensions: security, version integrity, bandwidth utilization, and service continuity. The specific implementation process is as follows:
[0055] First, during the branch equipment update process of the target bank, a triple verification mechanism combining device-side SM3 fast verification, server-side signature verification, and cloud-based integrity auditing is used to verify the version files, ensuring the integrity and security of the version files. The specific details of each verification mechanism are as follows:
[0056] (1) Device-side SM3 fast verification: When the device downloads or receives files, SM3 verification adopts fragmented verification technology, dividing the version file into 1MB fixed-size verification units, calculating the SM3 hash value for each verification unit separately, and supporting accurate location and repair when resuming interrupted transmission. Through a fast and lightweight method, it ensures that the received data on the device is not damaged during transmission.
[0057] (2) Server-side signature verification: The SM2 algorithm is used to generate and verify the signature to ensure its non-forgeability. The SM3 algorithm is used to generate the hash value of the file, replacing the traditional MD5 or SHA-1, which provides higher security. The server generates a signature for the file (based on SM2 / SM3). After receiving the file, the device or client verifies the validity of the signature using the corresponding public key to ensure the authenticity of the file's source.
[0058] (3) Cloud Integrity Audit: Metadata monitoring (recording and checking key file attributes such as creation time, file size, and permission attributes) ensures that files have not been truncated or tampered with. SM3 hash values are used to continuously verify whether the file content is consistent with the original version, and the module's operational status is continuously audited. Logs and alarm mechanisms are combined to detect whether the server is operating normally. This forms a dual guarantee of post-event traceability and proactive defense, ensuring long-term file trustworthiness.
[0059] Secondly, a version rollback database is established to record complete verification information for each version. When a version anomaly is detected, the rollback process is automatically triggered, prioritizing restoration to the most recent stable version. A tiered rollback strategy is supported, including a three-tiered rollback mechanism at the device, branch, and national levels, thereby ensuring the security of the running versions on the devices.
[0060] The process of intelligently updating application versions by distributing CDN files to the branch equipment of the target bank and implementing multi-level rate limiting and bandwidth management can specifically include the following three aspects:
[0061] Firstly, a layered rate-limiting architecture.
[0062] (1) CDN layer: token bucket rate limiting based on IP five-tuple (maximum concurrent connections per IP ≤ 20, download speed ≤ 10Mbps).
[0063] (2) Service layer: Bandwidth quota management is implemented by branch (5%-20% of the total bandwidth is dynamically allocated).
[0064] (3) Device layer: Implement differentiated rate limiting based on device type (e.g., ATM devices have higher priority than POS terminals).
[0065] Secondly, a strict bandwidth control strategy.
[0066] Before downloading the version file, a bandwidth priority queue is first established: emergency update (QoS 1), regular update (QoS 2), and low-priority update (QoS 3). Version updates are performed sequentially according to the tasks in each queue. Considering the distinction between business hours and non-business hours (when business volume is extremely low), full bandwidth is available during non-business hours (23:00-06:00), while bandwidth compression is implemented during business hours. Simultaneously, CDN node expansion is automatically triggered when bandwidth utilization exceeds 85%.
[0067] Thirdly, intelligent download scheduling algorithms.
[0068] During the actual download process of the version file, this patent employs an incremental packet generation technology improved from the SM3 comparison algorithm. It supports multi-version baseline comparison, establishes a version difference map, records the change paths between versions, supports parallel updates of multiple apps, and ensures the feasibility of the update path through a version compatibility matrix. Furthermore, it utilizes a multi-threaded dynamic scheduling algorithm to adjust the number of threads in real time based on the device's network bandwidth (adaptive from 2 to 16 threads).
[0069] Because CDNs have intelligent node selection capabilities—that is, they make multi-dimensional decisions based on device geolocation, carrier type, and real-time load—the device selects the nearest CDN server for version updates (as shown in the figure), ensuring rapid response and minimizing network congestion. During the actual download process, block download optimization technology is used, dividing the file into configurable download blocks of 4KB-1MB, supporting resume download and priority download.
[0070] Next, the service continuity assurance system provided in this application will be introduced, specifically including:
[0071] (1) CDN multi-active data center architecture
[0072] Construct a "dual-active + N" distributed architecture: provide service clusters in two cities simultaneously, N edge CDN nodes, and establish a cross-regional version synchronization mechanism to ensure that any single point of failure does not affect the service.
[0073] (2) Self-healing update system
[0074] This application's CDN service includes an anomaly detection module. It collects real-time data on device version download success rate and response time, setting threshold conditions (download success rate ≥ 99.9%, response time ≤ 200ms). An alarm mechanism is triggered when either indicator remains abnormal. Furthermore, a redundant primary / backup CDN node architecture is employed. If the primary node's health status fails, the system uses a load balancer to perform failover within 10 seconds, ensuring the continuity of version distribution services. Finally, a health check module performs a full network device version status scan every 15 minutes, verifying the version number using heartbeat packets and generating a device health assessment report to drive subsequent repair processes.
[0075] (3) Triple authentication mechanism
[0076] A multi-factor authentication system is constructed, comprising device-side X.509 digital certificate authentication, dynamic token (OTP) time synchronization verification, and biometric identification verification. These three elements are logically linked to form access control conditions. When a device automatically requests an update from the main CDN node upon startup, it first verifies the server's digital certificate (part of the device's certificate system) to ensure the update package originates from the bank's official server. Each time a device initiates an update request, it must include a dynamic token (e.g., timestamp + signature) to ensure the request has not been tampered with or replayed. When an emergency update needs to be forcibly pushed, the device administrator must pass biometric verification before triggering the global update command.
[0077] Thus, the bank's batch equipment management solution, implemented through steps S101-S103 above, provides a detailed solution from application updates, version building, version distribution to the final version update, all without manual operation, achieving the following five beneficial effects:
[0078] (1) An automated version management mechanism has been introduced to avoid the risks of human operation and greatly improve the convenience and security of device version management.
[0079] (2) During the equipment update process, a triple verification mechanism is used to ensure the integrity and security of the version files.
[0080] (3) Combining CDN file distribution technology with multi-level rate limiting and bandwidth management strategies can enable rapid response when the device is updated, pull resources from the nearest location, and avoid network bandwidth congestion.
[0081] (4) It can ensure the continuity of services.
[0082] (5) It has a dynamic rollback strategy. If the version update is abnormal, it can roll back to the most recent stable version within minutes.
[0083] In summary, this embodiment provides a method for batch device management in banks. First, it obtains the configuration file and configuration information from the target bank's application package. Then, based on the configuration file, it updates the corresponding application version and builds the overall application version. Next, based on the configuration information, it builds the corresponding platform version. Then, it distributes the built platform version, the overall application version, and the updated application version to the target bank's branch devices via CDN files, implementing intelligent application version updates with multi-level rate limiting and bandwidth management. This allows each branch to download the device version file from the nearest location, ensuring reasonable bandwidth utilization, preventing bandwidth congestion, achieving timely response, and efficiently downloading version files, thus achieving the desired batch device management effect.
[0084] See Figure 4 As shown, this application also provides an embodiment of a bank batch equipment management device, which may include:
[0085] Acquisition unit 401 is used to acquire configuration files and configuration information from the target bank application package;
[0086] The building unit 402 is used to complete the corresponding application version update and build the total application version according to the configuration file; and to build the corresponding platform version according to the configuration information.
[0087] The distribution unit 403 is used to distribute the constructed platform version, the overall application version, and the updated application version to the branch equipment of the target bank through a Content Delivery Network (CDN) file, and to implement intelligent application version updates with multi-level rate limiting and bandwidth management.
[0088] In some possible implementations of this application, the fields of the configuration file include at least one of application ID, application name, application version, and usage channel; the configuration information includes at least one of application ID and version information, total application version name, applicable channel, earliest effective time, and latest effective time.
[0089] In some possible implementations of this application, the apparatus further includes:
[0090] The first setting unit is used to set the earliest effective time and the latest effective time of the version when building the total application version and / or platform version, and to specify that the total application version is available within a specific time range;
[0091] The second setting unit is used to set the earliest download time and download interval for each device during the process of distributing the equipment to the branch equipment of the target bank.
[0092] In some possible implementations of this application, the apparatus further includes:
[0093] The verification unit is used to verify version files during the branch equipment update process of the target bank. It employs a triple verification mechanism that combines device-side SM3 fast verification, server-side signature verification, and cloud-based integrity auditing to ensure the integrity and security of version files.
[0094] As can be seen from the above embodiments, the bank batch device management device provided in this application first obtains the configuration file and configuration information in the target bank's application package; then, based on the configuration file, it completes the corresponding application version update and builds the overall application version; and based on the configuration information, it builds the corresponding platform version; next, it distributes the built platform version, the overall application version, and the updated application version to the branch devices of the target bank through CDN files, and realizes intelligent application version updates with multi-level rate limiting and bandwidth management. This enables each branch to download the device version file from the nearest location, while ensuring reasonable bandwidth utilization, preventing bandwidth congestion, achieving timely response, and efficiently downloading version files, thereby achieving the ideal batch device management effect.
[0095] Furthermore, embodiments of this application also provide a bank batch equipment management device, including: a processor, a memory, and a system bus;
[0096] The processor and the memory are connected via the system bus;
[0097] The memory is used to store one or more programs, the one or more programs including instructions, which, when executed by the processor, cause the processor to perform any of the above-described implementations of the bank batch equipment management method.
[0098] Furthermore, embodiments of this application also provide a computer-readable storage medium storing instructions that, when executed on a terminal device, cause the terminal device to perform any of the above-described implementations of the bank batch device management method.
[0099] As can be seen from the above description of the embodiments, those skilled in the art can clearly understand that all or part of the steps in the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, a server, or a network communication device such as a media gateway, etc.) to execute the methods described in various embodiments or some parts of the embodiments of this application.
[0100] It should be noted that the various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section.
[0101] It should also be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.
[0102] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A method for managing batch equipment in a bank, characterized in that, include: Obtain the configuration files and configuration information from the target bank's application package; Based on the configuration file, complete the corresponding application version update and build the overall application version; And based on the configuration information, construct the corresponding platform version; The constructed platform version, the overall application version, and the updated application version are distributed to the branch equipment of the target bank through a Content Delivery Network (CDN) file, and intelligent application version updates are implemented with multi-level rate limiting and bandwidth management.
2. The method according to claim 1, characterized in that, The configuration file includes at least one of the following fields: application ID, application name, application version, and usage channel; the configuration information includes at least one of the following: application ID and version information, total application version name, applicable channel, earliest effective time, and latest effective time.
3. The method according to claim 1, characterized in that, The method further includes: When building the overall application version and / or platform version, set the earliest and latest effective times for the version, and specify that the overall application version is available within a specific time range; During the process of distributing the equipment to the branch offices of the target bank, the earliest download time and download interval for each device are set.
4. The method according to any one of claims 1-3, characterized in that, The method further includes: During the branch equipment update process of the target bank, a triple verification mechanism combining device-side SM3 fast verification, server-side signature verification, and cloud-based integrity auditing is used to verify the version files in order to ensure the integrity and security of the version files.
5. A bank batch equipment management device, characterized in that, include: The acquisition unit is used to acquire configuration files and configuration information from the target bank's application package; The building unit is used to complete the corresponding application version update and build the total application version according to the configuration file; and to build the corresponding platform version according to the configuration information. The distribution unit is used to distribute the constructed platform version, the overall application version, and the updated application version to the branch equipment of the target bank through a Content Delivery Network (CDN) file, and to implement intelligent application version updates with multi-level rate limiting and bandwidth management.
6. The apparatus according to claim 5, characterized in that, The configuration file includes at least one of the following fields: application ID, application name, application version, and usage channel; the configuration information includes at least one of the following: application ID and version information, total application version name, applicable channel, earliest effective time, and latest effective time.
7. The apparatus according to claim 5, characterized in that, The device further includes: The first setting unit is used to set the earliest effective time and the latest effective time of the version when building the total application version and / or platform version, and to specify that the total application version is available within a specific time range; The second setting unit is used to set the earliest download time and download interval for each device during the process of distributing the equipment to the branch equipment of the target bank.
8. The apparatus according to any one of claims 5-7, characterized in that, The device further includes: The verification unit is used to verify version files during the branch equipment update process of the target bank. It employs a triple verification mechanism that combines device-side SM3 fast verification, server-side signature verification, and cloud-based integrity auditing to ensure the integrity and security of version files.
9. A batch equipment management device for banks, characterized in that, include: Processor, memory, system bus; The processor and the memory are connected via the system bus; The memory is used to store one or more programs, the one or more programs including instructions that, when executed by the processor, cause the processor to perform the method according to any one of claims 1-4.
10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed on a terminal device, cause the terminal device to perform the method described in any one of claims 1-4.