Application release verification method, system and device, storage medium and program product

Abstract

The invention discloses an application release verification method, system and device, a storage medium and a program product, and relates to the technical field of computers, and the method comprises the steps: receiving an application file through a system front end, and sending the application file to a file service; and under the condition that the system rear end monitors that the application file is completely uploaded, the application file is acquired from the file service through the system rear end, the verification service corresponding to the application file is pulled, and the application file is verified according to the verification service. According to the application, the front end and the rear end are separated, so that the burden of the rear end service is reduced, the rear end can concentrate on processing the verification service, the signature verification efficiency of the rear end is improved, the verification service corresponding to the application file is pulled through the rear end to be processed after the rear end of the system monitors that the file is uploaded completely, and the verification efficiency is improved. The asynchronous processing mode allows the concurrent processing capability of the back-end service, so that the back-end service can process verification services of a large number of application files more efficiently, and the signature verification efficiency is improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to an application publishing verification method, system, device, storage medium and program product. Background Art

[0002] In the era of mobile Internet, with the popularity of smart phones and various mobile devices, APP (Application) has become an indispensable part of people's daily life. In order to protect the safety and rights of users and maintain the order of the application market, it is particularly important to strictly verify and re-sign the application files submitted by developers. Signature verification is a key link to ensure that the source of application files is reliable and the content has not been tampered with. Its purpose is to confirm the integrity and authenticity of application files by verifying the digital signature of application files. At present, the common practice of application file signature verification is that after uploading and receiving application files in the application market, the backend service directly decompresses, verifies the signature and re-signs them. In this process, the backend service needs to undertake all tasks of file uploading, storage, processing and result feedback. Specifically, the developer uploads the application file to the application market server. After receiving the file, the server first decompresses it, and then uses the pre-stored public key to verify the digital signature in the application file to confirm whether the application file is generated by a legitimate developer and the content has not been tampered with. If the signature verification passes, the application file is re-signed as needed to meet the distribution requirements of the application market. In the entire processing flow, the backend service needs to continue to occupy resources until the task is completed.

[0003] However, as the user base continues to grow, the number of application files that need to be processed in the application market has also increased dramatically. Since the back-end service needs to handle the upload, decompression, signature verification and re-signature tasks of a large number of application files at the same time, it leads to huge consumption of server resources (such as memory, disk I / O, etc.). As a result, the time for the back-end service to process each application file will be significantly extended, affecting the efficiency of signature verification.

[0004] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention

[0005] The main purpose of this application is to provide an application release verification method, system, device, storage medium and program product, aiming to solve the technical problem of low efficiency of signature verification of application files by the back-end server.

[0006] To achieve the above purpose, the present application proposes an application release verification method, the method comprising:

[0007] Receiving application files through the system front end and sending the application files to the file service;

[0008] When the system backend monitors that the application file has been uploaded, the system backend obtains the application file from the file service, pulls the verification service corresponding to the application file, and verifies the application file according to the verification service.

[0009] In one embodiment, the method further comprises:

[0010] Generate task information through a message notification mechanism, wherein the task information includes the link status of the application file in each publishing link;

[0011] Acquiring the publishing status of the application file through the message notification mechanism, and updating the task information based on the publishing status to obtain updated task information;

[0012] The updated task information is obtained through the system backend, and when it is determined based on the updated task information that the link status of the file upload link in each publishing link is a completed state, it is determined that the application file has been uploaded.

[0013] In one embodiment, after the step of obtaining the publishing status of the application file through the message notification mechanism and updating the task information based on the publishing status to obtain updated task information, the step further includes:

[0014] Acquire the updated task information through the system front end;

[0015] The link status of each publishing link in the updated task information is determined through the system front end and displayed.

[0016] In one embodiment, the verification service includes a signature verification service and a re-signature service, and each of the publishing links includes a signature verification link and a re-signature link; the step of obtaining the publishing status of the application file through the message notification mechanism, and updating the task information based on the publishing status to obtain the updated task information includes:

[0017] Obtaining the first publishing status of the signature verification service and the second publishing status of the re-signature service from the system backend through the message notification mechanism;

[0018] The link status of the signature verification link is updated according to the first publishing status through the message notification mechanism, and the link status of the re-signature link is updated according to the second publishing status to obtain updated task information.

[0019] In one embodiment, the file service includes a plurality of service nodes; the step of sending the application file to the file service includes:

[0020] Determine the resource load of each of the service nodes, and detect whether there are multiple low-load nodes among the service nodes, wherein the low-load node is the service node with the lowest resource load among the service nodes;

[0021] If there are no multiple low-load nodes, determining the low-load node as the target service node;

[0022] If there are multiple low-load nodes, the node with the lowest number of visits among the low-load nodes is determined as the target service node;

[0023] The application file is sent to the target service node.

[0024] In one embodiment, the target service node includes a plurality of sub-nodes; the step of sending the application file to the target service node includes:

[0025] Determine the node with the lowest number of accesses among the subnodes as the main node, send the application file to the main node, and copy the file data of the application file to the standby node, wherein the standby node is a subnode among the subnodes except the main node;

[0026] After the step of sending the application file to the target service node, the method further includes:

[0027] When a failure of the master node is detected, a new master node is determined from the backup nodes, and file access is accepted through the new master node.

[0028] In addition, to achieve the above purpose, the present application also proposes an application release verification system, the application release verification system comprising:

[0029] A system front end, used for receiving application files through the system front end and sending the application files to the file service;

[0030] The system backend is used to obtain the application file from the file service through the system backend when the system backend monitors that the application file has been uploaded, and pull the verification business corresponding to the application file, and verify the application file according to the verification business.

[0031] In addition, to achieve the above-mentioned purpose, the present application also proposes an application release verification device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, and the computer program is configured to implement the steps of the application release verification method described above.

[0032] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by the processor, the steps of the application release verification method described above are implemented.

[0033] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the application release verification method described above are implemented.

[0034] In this application, the application file is received through the system front end, and the application file is sent to the file service; when the system back end monitors that the application file has been uploaded, the system back end obtains the application file from the file service, and pulls the verification service corresponding to the application file, and verifies the application file according to the verification service. This application separates the front end and the back end, receives the application file through the system front end, and sends the file to a dedicated file service, which reduces the burden on the back end service, so that the back end can focus on processing the verification service, while tasks such as file uploading and storage are undertaken by the file service, thereby improving the efficiency of the back end in signature verification and resource utilization. In addition, this application pulls the verification service corresponding to the application file through the back end after the system back end monitors that the file upload is completed, and the asynchronous processing method allows the back end service to process the verification service of an application file without blocking the upload and processing of other files, thereby improving the concurrent processing capability, so that the back end service can more efficiently process the verification service of a large number of application files, reducing the processing time and improving the efficiency of signature verification. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0036] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0037] Figure 1 A flowchart of the first embodiment of the verification method for publishing an application is provided;

[0038] Figure 2 A flowchart of the second embodiment of the verification method for publishing an application is provided;

[0039] Figure 3A brief flowchart of an application publishing verification method provided in an embodiment of the present application;

[0040] Figure 4 This is a schematic diagram of the module structure of the application release verification system of the embodiment of the present application;

[0041] Figure 5 A schematic diagram of the device structure of the hardware operating environment involved in the application release verification method in the embodiment of the present application.

[0042] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0043] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0044] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0045] The main solution of the embodiment of the present application is: receiving application files through the system front end and sending the application files to the file service; when the system back end monitors that the application file has been uploaded, obtaining the application file from the file service through the system back end, and pulling the verification business corresponding to the application file, and verifying the application file according to the verification business.

[0046] In this embodiment, for the convenience of description, the following description is made with the application publishing verification device as the execution subject.

[0047] Signature verification is a key step to ensure that the source of application files is reliable and the content has not been tampered with. Its purpose is to confirm the integrity and authenticity of application files by verifying the digital signature of application files. At present, the common practice of application file signature verification is that after uploading and receiving application files in the application market, the backend service directly decompresses, verifies the signature and re-signs them. In this process, the backend service needs to undertake all tasks of file uploading, storage, processing and result feedback. Specifically, the developer uploads the application file to the application market server. After the server receives the file, it first decompresses it, and then uses the pre-stored public key to verify the digital signature in the application file to confirm whether the application file is generated by a legitimate developer and the content has not been tampered with. If the signature verification passes, the application file is re-signed as needed to meet the distribution requirements of the application market. During the entire processing flow, the backend service needs to continue to occupy resources until the task is completed.

[0048] However, as the user base continues to grow, the number of application files that need to be processed in the application market has also increased dramatically. Since the back-end service needs to handle the upload, decompression, signature verification and re-signature tasks of a large number of application files at the same time, the server resources (such as CPU, memory, disk I / O, etc.) are consumed greatly, resulting in the back-end service processing Each application file The time will be significantly extended, affecting the efficiency of signature verification.

[0049] This application proposes a solution that separates the front-end and the back-end, receives application files through the system front-end, and sends the files to a dedicated file service, which reduces the burden on the back-end service, allowing the back-end to focus on processing verification services, while tasks such as file upload and storage are undertaken by the file service, thereby improving the efficiency of the back-end signature verification and resource utilization. In addition, this application pulls the verification service corresponding to the application file through the back-end after the system back-end monitors the completion of file upload. The asynchronous processing method allows the back-end service to process the verification service of an application file without blocking the upload and processing of other files, thereby improving the concurrent processing capability, allowing the back-end service to more efficiently process the verification services of a large number of application files, reducing processing time and improving the efficiency of signature verification.

[0050] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device capable of realizing the above functions, an application publishing verification device, etc. The following takes the application publishing verification device as an example to illustrate this embodiment and the following embodiments.

[0051] Based on this, the present application embodiment provides an application release verification method, referring to Figure 1 , Figure 1 This is a flowchart of the first embodiment of the application release verification method of this application.

[0052] In this embodiment, the application publishing verification method includes steps S10 to S20:

[0053] Step S10, receiving the application file through the system front end, and sending the application file to the file service;

[0054] It should be noted that application files refer to application files to be released, which usually contain application code, resources, configuration and other information. Users access the user interface provided by the system front end through a browser or application client, upload application files to the front end interface, and after the front end interface receives the application file, it sends the file to the file service for storage through an internal communication mechanism (such as HTTP request). The file service receives the file and returns confirmation information of successful storage to the front end interface. It can be understood that by separating file storage from the front end interface, the scalability and security of the system are improved.

[0055] Step S20, when the system backend monitors that the application file has been uploaded, the system backend obtains the application file from the file service, pulls the verification business corresponding to the application file, and verifies the application file according to the verification business.

[0056] If the system backend detects that the file has been uploaded through a monitoring mechanism (such as an event notification of the completion of file upload), the backend obtains the application file from the file service, and pulls the verification service corresponding to the file from the verification service library based on information such as the file type or user request. The backend verifies the files one by one according to the requirements of the verification service. It should be noted that the verification service refers to the business logic of performing a series of verification operations on the application files to ensure that the application files meet specific release requirements or standards, such as code signature verification, security checks, compatibility tests, etc. It can be understood that by separating the verification logic from the front-end interface, the maintainability and scalability of the system are improved, and the accuracy and efficiency of verification are improved.

[0057] In this embodiment, the application publishing system is composed of a front-end system, a back-end system and a file service. The front-end system includes a user interface, a front-end logic and a communication module. By providing a user interaction interface, it receives application files uploaded by users based on the user interface, and sends the application files to the file service through the communication module. The back-end system is used to monitor the file upload status. Once it detects that the file upload is complete, it obtains the application file from the file service, pulls the verification business corresponding to the application file and executes the verification logic. The file service is used to receive application files uploaded by the front-end system and store them in the file storage module. At the same time, the file service also provides a file access interface so that the back-end system or other services can access and operate these files. The file service and the system back-end can be deployed on the same server, or on separate servers respectively, which is not limited here.

[0058] In one feasible implementation, the file service includes a plurality of service nodes; the step of sending the application file to the file service includes:

[0059] Step S101, determining the resource load of each of the service nodes, and detecting whether there are multiple low-load nodes among the service nodes, wherein the low-load node is the service node with the lowest resource load among the service nodes;

[0060] A service node is an independent running instance or component in a file service, responsible for processing a part of the file service functions. A service node can be a physical server, virtual machine or container, etc. Each service node has some or all of the file service functions and can receive and process file operation requests from the system front end and system back end. Resource load refers to the total amount of system resources (such as memory, disk I / O, etc.) consumed by a service node when processing file service requests. By monitoring resource load, performance bottlenecks or overloads can be discovered and handled in a timely manner.

[0061] Collect resource load data of each service node according to the preset period, process the collected data, determine the resource load of each service node, compare the resource load of each service node, find the service node with the lowest resource load, and determine whether there are multiple such low-load nodes. By monitoring resource load, performance bottlenecks or overloads can be discovered and handled in a timely manner.

[0062] Step S102: if there are no multiple low-load nodes, determine the low-load node as a target service node;

[0063] In the case that there are no multiple low-load nodes, a unique low-load node is determined as the target service node.

[0064] Step S103: if there are multiple low-load nodes, determine the node with the lowest number of visits among the low-load nodes as the target service node;

[0065] If there are multiple low-load nodes, the node with the lowest number of visits is determined as the target service node. The number of visits reflects the activity level of the service node in the past period of time. Selecting the node with the lowest number of visits helps to balance the load of each node, avoid some nodes being overloaded while other nodes are idle, and improve the overall performance and stability of the system.

[0066] Step S104: sending the application file to the target service node.

[0067] The system front end sends the application file to the target service node through an internal communication mechanism (such as HTTP request, FTP transmission, etc.), and the target service node receives the file and stores it in a specified location.

[0068] In a feasible implementation manner, the target service node includes a plurality of sub-nodes; the step S104: sending the application file to the target service node includes:

[0069] Step S1041, determining the node with the lowest number of accesses among the subnodes as the primary node, sending the application file to the primary node, and copying the file data of the application file to the backup node, wherein the backup node is a subnode among the subnodes except the primary node;

[0070] In this embodiment, the file service adopts a distributed architecture, which is composed of multiple service nodes. The service nodes can be deployed in different physical locations and connected to each other through the network to form a unified file service system. Each service node contains multiple sub-nodes. The sub-node is an independent running entity in the service node, responsible for specific file storage and access tasks. The sub-node can be a physical server, a virtual machine, a container, etc. The sub-nodes are connected to each other through an internal communication mechanism (such as a network communication protocol) to form a closely coordinated service node cluster. In this embodiment, the service node is a master-slave node architecture, and the sub-nodes are divided into master nodes and standby nodes. The master node is the main executor responsible for processing the current file operation, receiving requests from the client, performing corresponding file storage and access operations, and returning the results to the client. The standby node is a backup of the master node, used to store a copy of the file data on the master node. When the master node fails, the standby node can take over the tasks of the master node to ensure the continuity and reliability of the file service.

[0071] Inside the target service node, determine the number of accesses to each sub-node, and select the sub-node with the lowest number of accesses as the master node. Then, send the application file to the master node for storage, and copy the file data to other standby nodes.

[0072] After the step S104: sending the application file to the target service node, the method further includes:

[0073] Step S105: When it is detected that the master node fails, a new master node is determined from the backup nodes, and file access is accepted through the new master node.

[0074] If a failure of the master node is detected (such as downtime, network interruption, etc.), the fault recovery mechanism is immediately started to select a suitable node from the backup nodes as the new master node. The selection process may be based on factors such as the resource load, access times, network delay, etc. of the backup node. The new master node accepts and processes file access requests to ensure the continuity and reliability of file services. The fault recovery mechanism improves the reliability and fault tolerance of file services, avoids service interruptions caused by single point failures, and enhances the stability and reliability of the system.

[0075] This embodiment separates the front-end and the back-end, receives application files through the system front-end, and sends the files to a dedicated file service, which reduces the burden on the back-end service, allowing the back-end to focus on processing verification services, while tasks such as file upload and storage are undertaken by the file service, thereby improving the efficiency of the back-end signature verification and resource utilization. In addition, this embodiment, after the system back-end monitors that the file upload is completed, the back-end pulls the verification service corresponding to the application file for processing. The asynchronous processing method allows the back-end service to process the verification service of an application file without blocking the upload and processing of other files, thereby improving the concurrent processing capability, allowing the back-end service to more efficiently process the verification services of a large number of application files, reducing the processing time and improving the efficiency of signature verification.

[0076] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can be referred to the above introduction, and will not be repeated in the following. Figure 2 , the method further comprises:

[0077] Step S30, generating task information through a message notification mechanism, wherein the task information includes the link status of the application file in each publishing link;

[0078] The message notification mechanism is a mechanism for transmitting information within a system or between systems. In the file publishing process, the message notification mechanism can be used to notify the system backend, front-end users or other system components about changes in the file publishing status so that corresponding actions can be taken. The message notification mechanism can be event-driven or polling-based. Task information refers to a data set that records the status and progress of application files in each publishing link, including the file name, version, size, upload time, current link, link status and other information, which is used to track the release progress and status of the file. The publishing link refers to each stage or step in the file publishing process, such as file upload, file verification, file publishing, etc. Each publishing link has specific tasks and goals to ensure that the file can be correctly and safely published to the target location. The link status refers to the current status of the publishing link, such as pending, processing, processing completed, processing failed, etc. The link status is used to indicate the progress and results of the publishing link in the file publishing process.

[0079] When the release process of the application file begins, task information is generated through the message notification mechanism to record the initial status and release links of the file.

[0080] Step S40, obtaining the publishing status of the application file through the message notification mechanism, and updating the task information based on the publishing status to obtain updated task information;

[0081] The publishing status is used to characterize the current stage of the application file in the publishing process and the progress of this stage, such as the upload stage, verification stage, such as waiting to be uploaded, uploading, upload completed, publishing, publishing successful, publishing failed, etc. That is, the publishing status is used to indicate the position and progress of the file in the publishing process.

[0082] Monitor changes in the release status through the message notification mechanism. When the release status changes, update the corresponding fields in the task information according to the new release status. By updating the release status in the task information in real time, ensure the accuracy and timeliness of the information, and provide the latest task information for subsequent steps so that corresponding actions can be taken.

[0083] Step S50, obtaining the updated task information through the system backend, and determining that the application file has been uploaded when the link status of the file upload link in each publishing link is completed based on the updated task information.

[0084] The system backend obtains updated task information according to the preset cycle, and checks the link status of the file upload link in the task information. When the link status of the file upload link is completed, the system backend determines that the application file has been uploaded. By recording, updating and judging the status of each link and release status of the application file in the release process, the smooth progress of the release process and the accurate release of the file are ensured, which improves the automation and reliability of the system and reduces the need for manual intervention and the error rate.

[0085] In a feasible implementation manner, after the step S40: obtaining the publishing status of the application file through the message notification mechanism, and updating the task information based on the publishing status to obtain updated task information, the step further includes:

[0086] Step S60, obtaining the updated task information through the system front end;

[0087] The updated task information is obtained through the system front end, parsed and stored locally or in memory for subsequent display and processing.

[0088] Step S70, determining the link status of each publishing link in the updated task information through the system front end and displaying it.

[0089] After receiving the updated task information, the front end parses and extracts the status of each publishing link. Depending on the status of each link, the front end will display it to the user in different ways. For example, you can use progress bars, status icons, text prompts, etc. to display information such as file upload progress, verification status, and publishing results.

[0090] For completed or erroneous links, the front end can also provide further operation options, such as re-uploading, viewing error details, etc. By providing an intuitive and clear interface display, users can easily understand the release progress and status of the file, which improves the user's operational convenience and satisfaction and reduces the risk of operational errors caused by information lag or errors.

[0091] In a feasible implementation manner, the verification service includes a signature verification service and a re-signature service, and each of the publishing links includes a signature verification link and a re-signature link; the step S40: obtaining the publishing status of the application file through the message notification mechanism, and updating the task information based on the publishing status to obtain the updated task information, includes:

[0092] Step S401, obtaining the first publishing status of the signature verification service and the second publishing status of the re-signature service from the system backend through the message notification mechanism;

[0093] When processing the release process of application files, the system backend will generate corresponding release status according to different business logics (such as signature verification and re-signature business), that is, the first release status of signature verification and the second release status of re-signature business. The release status will be sent to the message notification mechanism in real time or periodically through the message notification mechanism (such as event-driven, polling, etc.).

[0094] Step S402: Update the link status of the signature verification link according to the first publishing status through the message notification mechanism, and update the link status of the re-signing link according to the second publishing status to obtain updated task information.

[0095] The link status of the signature verification link is updated according to the first release status through the message notification mechanism, and the link status of the re-signature link is updated according to the second release status to obtain updated task information. The real-time update of task information reflects the latest status of the application file in the release process, improves the transparency and traceability of the system, and users or administrators can clearly understand the progress and results of each release link, making problem troubleshooting and fault handling easier and more accurate.

[0096] This embodiment separates the front-end and the back-end, receives application files through the system front-end, and sends the files to a dedicated file service, which reduces the burden on the back-end service, allowing the back-end to focus on processing verification services, while tasks such as file upload and storage are undertaken by the file service, thereby improving the efficiency of the back-end signature verification and resource utilization. In addition, after the system back-end monitors that the file upload is completed, the application pulls the verification service corresponding to the application file through the back-end for processing. The asynchronous processing method allows the back-end service to process the verification service of an application file without blocking the upload and processing of other files, thereby improving the concurrent processing capability, allowing the back-end service to more efficiently process the verification services of a large number of application files, reducing processing time and improving the efficiency of signature verification.

[0097] For example, to help understand the implementation process of the application publishing verification method obtained by combining the above-mentioned embodiment 1 and embodiment 2, please refer to Figure 3 , Figure 3 A brief flowchart of an application release verification method is provided, specifically:

[0098] 1. The system front end uploads the application file to a separate file service, the file service is isolated from the application service, and a multi-node cluster service is used for the file service (that is, the application file is received through the system front end, and the application file is sent to the file service, wherein the file service includes multiple service nodes; the step of sending the application file to the file service includes: determining the resource load of each of the service nodes, and detecting whether there are multiple low-load nodes in each of the service nodes, wherein the low-load node is the service node with the lowest resource load among the service nodes; if there are no multiple low-load nodes, the A low-load node is determined as a target service node; if there are multiple low-load nodes, the node with the lowest number of accesses among the low-load nodes is determined as the target service node; wherein the target service node includes multiple child nodes; the node with the lowest number of accesses among the child nodes is determined as a master node, the application file is sent to the master node, and the file data of the application file is copied to a standby node, wherein the standby node is a child node among the child nodes except the master node; when a failure of the master node is detected, a new master node is determined from the standby nodes, and file access is accepted through the new master node);

[0099] 2. Through the message notification mechanism, a task information is generated when the file upload starts. The task information includes the link status of each link, such as upload status, signature verification status, re-signature status, etc. After the file is uploaded to the file service, the status of this task information will be updated to uploaded through a message (that is, the task information is generated through the message notification mechanism, wherein the task information includes the link status of the application file in each publishing link; the publishing status of the application file is obtained through the message notification mechanism, and the task information is updated based on the publishing status to obtain the updated task information);

[0100] 3. The back-end signature service monitors the task status, pulls the uploaded files for signature verification and re-signature services, and updates the task status at the corresponding node (that is, obtains the first release status of the signature verification service and the second release status of the re-signature service from the system back-end through the message notification mechanism; updates the link status of the signature verification link according to the first release status through the message notification mechanism, and updates the link status of the re-signature link according to the second release status, to obtain the updated task information);

[0101] 4. The front end obtains the publishing status of the application file through websocket (network socket, a computer communication protocol) and presents the real-time progress on the page.

[0102] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the application release verification method of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

[0103] This application also provides an application release verification system, please refer to Figure 4 , the application release verification system comprises:

[0104] The system front end 10 is used to receive the application file through the system front end and send the application file to the file service;

[0105] The system backend 20 is used to obtain the application file from the file service through the system backend when the system backend monitors that the application file has been uploaded, and pull the verification business corresponding to the application file, and verify the application file according to the verification business.

[0106] Optionally, the device further comprises a generating module, configured to:

[0107] Generate task information through a message notification mechanism, wherein the task information includes the link status of the application file in each publishing link;

[0108] Acquiring the publishing status of the application file through the message notification mechanism, and updating the task information based on the publishing status to obtain updated task information;

[0109] The updated task information is obtained through the system backend, and when it is determined based on the updated task information that the link status of the file upload link in each publishing link is a completed state, it is determined that the application file has been uploaded.

[0110] Optionally, the generating module is further used to:

[0111] Acquire the updated task information through the system front end;

[0112] The link status of each publishing link in the updated task information is determined through the system front end and displayed.

[0113] Optionally, the verification service includes a signature verification service and a re-signature service, and each of the publishing links includes a signature verification link and a re-signature link; the generation module is further used to:

[0114] Obtaining the first publishing status of the signature verification service and the second publishing status of the re-signature service from the system backend through the message notification mechanism;

[0115] The link status of the signature verification link is updated according to the first publishing status through the message notification mechanism, and the link status of the re-signature link is updated according to the second publishing status to obtain updated task information.

[0116] Optionally, the file service includes multiple service nodes; the system front end 10 is also used for:

[0117] Determine the resource load of each of the service nodes, and detect whether there are multiple low-load nodes among the service nodes, wherein the low-load node is the service node with the lowest resource load among the service nodes;

[0118] If there are no multiple low-load nodes, determining the low-load node as the target service node;

[0119] If there are multiple low-load nodes, the node with the lowest number of visits among the low-load nodes is determined as the target service node;

[0120] The application file is sent to the target service node.

[0121] Optionally, the target service node includes a plurality of sub-nodes; the system front end 10 is further used for:

[0122] Determine the node with the lowest number of accesses among the subnodes as the main node, send the application file to the main node, and copy the file data of the application file to the standby node, wherein the standby node is a subnode among the subnodes except the main node;

[0123] After the step of sending the application file to the target service node, the method further includes:

[0124] When a failure of the master node is detected, a new master node is determined from the backup nodes, and file access is accepted through the new master node.

[0125] The application release verification system provided by the present application adopts the application release verification method in the above embodiment, which can solve the technical problem of low efficiency of signature verification of APP by the back-end server. Compared with the prior art, the beneficial effects of the application release verification system provided by the present application are the same as the beneficial effects of the application release verification method provided by the above embodiment, and other technical features of the application release verification system are the same as the features disclosed in the above embodiment method, which will not be repeated here.

[0126] The present application provides an application release verification device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the application release verification method in the above-mentioned embodiment.

[0127] Reference below Figure 5 , which shows a schematic diagram of the structure of an application publishing verification device suitable for implementing the embodiment of the present application. The application publishing verification device in the embodiment of the present application may include but is not limited to terminals such as servers. Figure 5 The application release verification device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0128] like Figure 5As shown, the application release verification device may include a processing device 1001 (e.g., a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the application release verification device are also stored. The processing device 1001, ROM1002, and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the application publishing verification device to communicate with other devices wirelessly or by wire to exchange data. Although the figure shows an application publishing verification device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or provided instead.

[0129] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0130] The application release verification device provided by the present application adopts the application release verification method in the above embodiment, which can solve the technical problem of low efficiency of signature verification of APP by the back-end server. Compared with the prior art, the beneficial effects of the application release verification device provided by the present application are the same as the beneficial effects of the application release verification method provided by the above embodiment, and the other technical features in the application release verification device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0131] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0132] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0133] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the application release verification method in the above-mentioned embodiment.

[0134] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM: Random Access Memory), a read-only memory (ROM: Read Only Memory), an erasable programmable read-only memory (EPROM: Erasable Programmable Read Only Memory or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM: CD-Read Only Memory), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency: Radio Frequency), etc., or any suitable combination of the above.

[0135] The computer-readable storage medium may be included in the application publishing and verification device; or may exist independently without being assembled into the application publishing and verification device.

[0136] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by the application publishing and verification device, the application publishing and verification device: receives the application file through the system front end, and sends the application file to the file service; when the system back end monitors that the application file has been uploaded, pulls the verification business corresponding to the application file through the system back end, and updates the file status of the application file according to the publishing status of the verification business; obtains the file status through the system front end and displays it.

[0137] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0138] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0139] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0140] The readable storage medium provided by the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned application release verification method, and can solve the technical problem of low efficiency of signature verification of APP by the back-end server. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the present application are the same as the beneficial effects of the application release verification method provided by the above-mentioned embodiment, and will not be repeated here.

[0141] The present application also provides a computer program product, including a computer program, which implements the steps of the above-mentioned application release verification method when executed by a processor.

[0142] The computer program product provided by this application can solve the technical problem of low efficiency of signature verification of APP by the back-end server. Compared with the prior art, the beneficial effects of the computer program product provided by this application are the same as the beneficial effects of the application release verification method provided by the above embodiment, which will not be repeated here.

[0143] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. An application release verification method, characterized in that: The application release verification method comprises: Receiving application files through the system front end and sending the application files to the file service; When the system backend monitors that the application file has been uploaded, the system backend obtains the application file from the file service, pulls the verification service corresponding to the application file, and verifies the application file according to the verification service.

2. The application publishing verification method according to claim 1, characterized in that: The method further comprises: Generate task information through a message notification mechanism, wherein the task information includes the link status of the application file in each publishing link; Acquiring the publishing status of the application file through the message notification mechanism, and updating the task information based on the publishing status to obtain updated task information; The updated task information is obtained through the system backend, and when it is determined based on the updated task information that the link status of the file upload link in each publishing link is a completed state, it is determined that the application file has been uploaded.

3. The application publishing verification method according to claim 2, characterized in that: After the step of obtaining the publishing status of the application file through the message notification mechanism and updating the task information based on the publishing status to obtain updated task information, the method further includes: Acquire the updated task information through the system front end; The link status of each publishing link in the updated task information is determined through the system front end and displayed.

4. The application publishing verification method according to claim 2, characterized in that: The verification service includes a signature verification service and a re-signature service, and each of the publishing links includes a signature verification link and a re-signature link; the step of obtaining the publishing status of the application file through the message notification mechanism, and updating the task information based on the publishing status to obtain the updated task information includes: Obtaining the first publishing status of the signature verification service and the second publishing status of the re-signature service from the system backend through the message notification mechanism; The link status of the signature verification link is updated according to the first publishing status through the message notification mechanism, and the link status of the re-signature link is updated according to the second publishing status to obtain updated task information.

5. The application publishing verification method according to any one of claims 1 to 4, characterized in that: The file service includes a plurality of service nodes; the step of sending the application file to the file service includes: Determine the resource load of each of the service nodes, and detect whether there are multiple low-load nodes among the service nodes, wherein the low-load node is the service node with the lowest resource load among the service nodes; If there are no multiple low-load nodes, determining the low-load node as the target service node; If there are multiple low-load nodes, the node with the lowest number of visits among the low-load nodes is determined as the target service node; The application file is sent to the target service node.

6. The application publishing verification method according to claim 5, characterized in that: The target service node includes a plurality of sub-nodes; the step of sending the application file to the target service node includes: Determine the node with the lowest number of accesses among the subnodes as the main node, send the application file to the main node, and copy the file data of the application file to the standby node, wherein the standby node is a subnode among the subnodes except the main node; After the step of sending the application file to the target service node, the method further includes: When a failure of the master node is detected, a new master node is determined from the backup nodes, and file access is accepted through the new master node.

7. An application release verification system, characterized in that: The application release verification system comprises: A system front end, used for receiving application files through the system front end and sending the application files to the file service; The system backend is used to obtain the application file from the file service through the system backend when the system backend monitors that the application file has been uploaded, and pull the verification business corresponding to the application file, and verify the application file according to the verification business.

8. An application publishing verification device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the application release verification method according to any one of claims 1 to 6.

9. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the application release verification method according to any one of claims 1 to 6 are implemented.

10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the application release verification method according to any one of claims 1 to 6 are implemented.

Images