Cloud platform signature verification method and device, electronic equipment, storage medium and program product

Abstract

The embodiment of the invention provides a cloud platform signature verification method and device, electronic equipment, a storage medium and a program product, and the method comprises the steps: responding to a signature request sent by a receiving service end, and obtaining the load state data of a cloud platform according to the signature request; adjusting parameters of an anti-quantum algorithm according to the load state data of the cloud platform to obtain adjusted security parameters; splitting a signature verification task in the signature request into a plurality of signature verification sub-tasks; executing a plurality of signature verification sub-tasks according to the adjusted security parameters, and generating a plurality of signature verification results; and the plurality of signature verification results are spliced, and the spliced signature verification results are sent to the service end, so that signature verification is completed, and the code redundancy is reduced.

Description

Technical Field

[0001] This application relates to the field of cloud computing technology, and in particular to a cloud platform signature verification method, apparatus, electronic device, storage medium and program product. Background Technology

[0002] The development of cloud computing technology has driven the centralized deployment of cryptographic services in the cloud. Cryptographic cloud platforms, through standardized services such as digital signatures and signature verification, have become the infrastructure for ensuring data integrity and user identity authenticity in multiple application scenarios.

[0003] In existing technologies, to avoid the problem that classical cryptographic algorithms rely on traditional mathematical problems, quantum-resistant cryptographic algorithms are used to solve the mathematical problems of classical cryptographic algorithms, thereby improving the security of cryptographic cloud platforms.

[0004] However, in existing technologies, when verifying signatures, quantum-resistant cryptographic algorithms require the deployment of separate verification logic for quantum-resistant and classical algorithms, leading to increased code redundancy. Summary of the Invention

[0005] This application provides a cloud platform signature verification method, apparatus, electronic device, storage medium, and program product to solve the problem of increased code redundancy in the prior art.

[0006] In a first aspect, embodiments of this application provide a cloud platform signature verification method, including:

[0007] In response to a signature request sent by the receiving service, the load status data of the cloud platform is obtained based on the signature request;

[0008] The parameters of the quantum-resistant algorithm are adjusted based on the load status data of the cloud platform to obtain the adjusted security parameters;

[0009] The signature verification task in the signature request is split into multiple signature verification sub-tasks;

[0010] Execute the multiple signature verification sub-tasks according to the adjusted security parameters to generate multiple signature verification results;

[0011] The multiple signature verification results are concatenated, and the concatenated signature verification result is sent to the business terminal to complete the signature verification.

[0012] In one possible implementation, adjusting the parameters of the quantum-resistant algorithm based on the load status data of the cloud platform to obtain the adjusted security parameters includes: determining the load status of the cloud platform based on the load status data of the cloud platform; querying a security parameter mapping table based on the load status of the cloud platform to obtain a method for adjusting the security parameters; and adjusting the parameters of the quantum-resistant algorithm according to the method for adjusting the security parameters to obtain the adjusted security parameters.

[0013] In one possible implementation, after adjusting the parameters of the anti-quantum algorithm according to the method for adjusting the security parameters to obtain the adjusted security parameters, the method further includes: calling a security verification tool to detect the security level of the adjusted security parameters; if the security level of the adjusted security parameters is lower than a preset security threshold, then a callback operation is performed on the parameters of the anti-quantum algorithm to obtain the default parameters of the anti-quantum algorithm.

[0014] In one possible implementation, the step of splitting the signature verification task in the signature request into multiple signature verification subtasks includes: obtaining the data to be signed in the signature request; dividing the data to be signed in the signature request according to a preset task length to generate multiple subtask blocks; and encapsulating the multiple subtask blocks to obtain multiple signature verification subtasks.

[0015] In one possible implementation, after encapsulating the multiple subtask blocks to obtain multiple signature verification subtasks, the method further includes: obtaining the thread states of multiple threads in a thread pool; allocating multiple signature verification subtasks according to the thread states of the multiple threads in the thread pool, generating thread allocation results; and executing the multiple signature verification subtasks according to the thread allocation results.

[0016] In one possible implementation, the step of executing the multiple signature verification sub-tasks according to the adjusted security parameters to generate multiple signature verification results includes: obtaining multiple request identifiers in the signature request; identifying the multiple request identifiers to obtain the signature verification algorithm types corresponding to the multiple request identifiers; matching the signature verification process according to the signature verification algorithm types; and executing the multiple signature verification sub-tasks according to the signature verification process to generate multiple signature verification results.

[0017] Secondly, embodiments of this application provide a cloud platform signature verification device, comprising:

[0018] The load monitoring module is used to respond to the signature request sent by the business terminal and obtain the load status data of the cloud platform according to the signature request;

[0019] The parameter adjustment module is used to adjust the parameters of the anti-quantum algorithm according to the load status data of the cloud platform to obtain the adjusted security parameters;

[0020] The task splitting module is used to split the signature verification task in the signature request into multiple signature verification sub-tasks;

[0021] The parallel computing module is used to execute the multiple signature verification subtasks according to the adjusted security parameters and generate multiple signature verification results;

[0022] The splicing module is used to splice the multiple signature verification results and send the spliced ​​signature verification results to the business terminal to complete the signature verification.

[0023] Thirdly, embodiments of this application provide an electronic device, including: a memory and a processor;

[0024] The memory stores computer-executed instructions;

[0025] The processor executes computer execution instructions stored in the memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above.

[0026] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect and / or various possible implementations of the first aspect.

[0027] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the first aspect and / or various possible implementations of the first aspect.

[0028] The cloud platform signature verification method, device, electronic device, storage medium, and program product provided in this application embodiment obtain the load status data of the cloud platform in real time, adjust the parameters of the quantum-resistant algorithm according to the load status data, split the signature verification task in the signature request into multiple signature verification sub-tasks, and execute the signature verification sub-tasks through the adjusted security parameters to generate signature verification results. By executing multiple signature verification sub-tasks in parallel through task splitting, the signature verification logic is avoided and the code redundancy is reduced. Attached Figure Description

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

[0030] Figure 1 This is a schematic diagram of the system structure of a computer device provided in an embodiment of this application;

[0031] Figure 2 A flowchart illustrating the cloud platform signature verification method provided for this application;

[0032] Figure 3 A schematic diagram of the cloud platform signature verification device provided in this application;

[0033] Figure 4 A schematic diagram of the structure of the electronic device provided in this application.

[0034] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0035] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0036] The development of cloud computing technology has driven the centralized deployment of cryptographic services in the cloud. Cryptographic cloud platforms, through standardized services such as digital signatures and signature verification, have become the infrastructure for ensuring data integrity and user identity authenticity in various application scenarios. In existing technologies, to avoid the problem of classical cryptographic algorithms relying on traditional mathematical problems, quantum-resistant cryptographic algorithms are used to solve these mathematical problems, thus improving the security of cryptographic cloud platforms. However, in existing technologies, when verifying signatures, quantum-resistant cryptographic algorithms require separate deployments of verification logic for the quantum-resistant and classical algorithms, leading to increased code redundancy.

[0037] To address the aforementioned technical problems, this application proposes the following technical concept: The inventors considered obtaining real-time load status data from the cloud platform, adjusting the parameters of the quantum-resistant algorithm based on the load status data, and dividing the signature verification task in the signature request into multiple signature verification sub-tasks. The adjusted security parameters are used to execute multiple signature verification sub-tasks, generate multiple signature verification results, and concatenate the multiple signature verification results to complete the signature verification. This avoids redundant deployment of signature verification logic and reduces code redundancy.

[0038] Figure 1 This is a schematic diagram of the system architecture of the computer device provided in an embodiment of this application. Figure 1 As shown, the computer device includes: a receiving device 101, a processing device 102, and a display device 103.

[0039] It is understood that the structure illustrated in the embodiments of this application does not constitute a specific limitation on the cloud platform signature verification method. In other feasible embodiments of this application, the above architecture may include more or fewer components than illustrated, or combine some components, or split some components, or arrange different components, which can be determined according to the actual application scenario and is not limited here. Figure 1 The components shown can be implemented in hardware, software, or a combination of both.

[0040] In the specific implementation process, the receiving device 101 can be an input / output interface or a communication interface, and can receive signature requests sent by the business terminal.

[0041] The processing device 102 can adjust the parameters of the quantum-resistant algorithm and generate multiple signature verification results.

[0042] The display device 103 can be used to display the above-mentioned multiple signature verification results, etc.

[0043] The display device can also be a touch screen, used to receive user commands while displaying the above content, so as to realize the operation interaction with the user.

[0044] It should be understood that the above-mentioned processing device can be implemented by a processor reading instructions from memory and executing those instructions, or it can be implemented by a chip circuit.

[0045] Furthermore, the network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0046] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0047] Figure 2 A flowchart illustrating the cloud platform signature verification method provided in this application is shown below. Figure 2 As shown, the method includes:

[0048] S201: In response to the signature request sent by the business terminal, obtain the load status data of the cloud platform based on the signature request.

[0049] In this embodiment, the load status data of the cloud platform includes, but is not limited to, CPU utilization, memory usage, and number of concurrent requests.

[0050] Specifically, the load monitoring module collects real-time load status data from the cloud platform.

[0051] Optionally, to reduce the impact of the latency in acquiring load data on the speed of signature verification for a single request, the signature verification service can periodically (e.g., every second) asynchronously collect and cache load status data, and directly read the latest cache when a signature request is received.

[0052] S202: Adjust the parameters of the quantum-resistant algorithm based on the load status data of the cloud platform to obtain the adjusted security parameters.

[0053] Specifically, the system determines the load status of the cloud platform, queries the security parameter mapping table based on the load status, obtains the adjustment method for the security parameters, and adjusts the parameters of the anti-quantum algorithm according to the adjustment method.

[0054] S203: Break down the signature verification task in the signature request into multiple signature verification sub-tasks.

[0055] Specifically, the data to be signed in the signature request is divided according to the preset task length to generate multiple sub-task blocks, and the multiple sub-task blocks are encapsulated to generate multiple signature verification sub-tasks.

[0056] S204: Execute multiple signature verification subtasks based on the adjusted security parameters to generate multiple signature verification results.

[0057] Specifically, the process involves obtaining the request identifier from the signature request, identifying the request identifier and obtaining the corresponding signature verification algorithm type, matching the signature verification process according to the signature verification algorithm type, executing the signature verification subtask according to the signature verification process, and generating multiple signature verification results.

[0058] S205: Concatenate multiple signature verification results and send the concatenated signature verification result to the business end to complete the signature verification.

[0059] Specifically, logical aggregation is performed based on the types of multiple signature verification results to generate a concatenated signature verification result.

[0060] For example, if the subtasks return independent Boolean results, the multiple signature verification results are concatenated using AND logic, and the final signature verification result is only passed when all subtask results are passed.

[0061] For example, if the subtask returns an intermediate calculation result (e.g., polynomial coefficients), the intermediate result is processed (e.g., hash values ​​are merged) to generate the final signature verification result.

[0062] As can be seen from the above embodiments, by acquiring the load status data of the cloud platform in real time, adjusting the parameters of the quantum-resistant algorithm according to the load status data, the signature verification task in the signature request is split into multiple signature verification sub-tasks, and the signature verification sub-tasks are executed through the adjusted security parameters to generate signature verification results. By splitting the tasks, multiple signature verification sub-tasks are executed in parallel, avoiding repeated deployment of signature verification logic and reducing code redundancy.

[0063] In one embodiment of this application, step S202 includes:

[0064] S2021: Determine the load status of the cloud platform based on the cloud platform's load status data.

[0065] In this embodiment, the load status of the cloud platform includes a high load status and a low load status.

[0066] Specifically, when the load status data of the cloud platform exceeds the preset load threshold, the load status of the cloud platform is determined to be high load.

[0067] Specifically, when the load status data of the cloud platform is lower than the preset load threshold, the load status of the cloud platform is determined to be low load.

[0068] S2022: Query the security parameter mapping table based on the cloud platform's load status to obtain the method for adjusting security parameters.

[0069] Specifically, when the cloud platform is under high load, the security parameter mapping table is queried to reduce the hash length of the security parameters.

[0070] Specifically, when the cloud platform is under low load, the security parameter mapping table is queried to obtain the hash length of the standard parameter, and the security parameter is replaced with the standard parameter.

[0071] For example, a high load state is determined when the CPU utilization is greater than or equal to 50% or the number of concurrent requests is greater than or equal to 5000 per second.

[0072] For example, when the CPU utilization is less than 50% and the number of concurrent requests is less than 5000 per second, it is determined to be a low-load state.

[0073] S2023: Adjust the parameters of the anti-quantum algorithm according to the adjustment method of the security parameters to obtain the adjusted security parameters.

[0074] Specifically, the safety parameters are adjusted according to the adjustment instructions.

[0075] For example, in the adjustment method of reducing parameter dimensions, the cloud platform's parameter configurator locates the parameter configuration file to be modified, verifies the modification permission, calculates the modified parameter value after the modification permission verification is passed, and modifies the original parameters in the parameter configuration file to obtain the adjusted security parameters.

[0076] As can be seen from the above embodiments, by introducing a security parameter mapping table, querying the security parameter mapping table according to the load status of the cloud platform, obtaining the adjustment method of the security parameters, adjusting the parameters of the quantum-resistant algorithm, realizing the adaptation of the quantum-resistant algorithm to different types of signature requests, and avoiding waste of system resources.

[0077] In one embodiment of this application, after step S2023, the method further includes:

[0078] S2024: Call the security verification tool to check the security level of the adjusted security parameters.

[0079] In this embodiment, the security verification tool is a software tool used to evaluate the security of cryptographic algorithms.

[0080] Specifically, the security verification tool takes the adjusted security parameters as input, performs quantitative analysis on the adjusted security parameters, and generates a security level.

[0081] S2025: If the security level of the adjusted security parameters is lower than the preset security threshold, then the parameters of the quantum algorithm will be executed in a callback operation to obtain the default parameters of the quantum algorithm.

[0082] Specifically, if the security level of a security parameter is lower than the preset security threshold, the versioned parameter repository is accessed to obtain the parameter configuration file that was previously verified and met the security level, and the current runtime parameter configuration is overwritten. A callback operation is then performed to obtain the default parameters.

[0083] As can be seen from the above embodiments, by calling the security verification tool to detect the adjusted security parameters, it is determined whether the security level of the adjusted security parameters is lower than the security threshold. If it is lower than the security threshold, a callback operation is executed to avoid over-optimization causing security vulnerabilities.

[0084] In one embodiment of this application, step S203 includes:

[0085] S2031: Retrieve the data to be signed from the signature request.

[0086] Specifically, the received signature request message is parsed by the request preprocessing unit, and the metadata and the data to be signed are separated from the message.

[0087] S2032: Divide the data to be signed in the signature request into multiple sub-task blocks according to the preset task length.

[0088] Specifically, based on the preset task length and the length of the data to be signed, the data to be signed in the buffer is logically divided into multiple subtask blocks.

[0089] S2033: Encapsulate multiple subtask blocks to obtain multiple signature verification subtasks.

[0090] Specifically, each subtask block is standardized and encapsulated by a task encapsulator, and the encapsulated independent task unit is called a signature verification subtask.

[0091] The encapsulated content includes, but is not limited to, the serialized data of the subtask block, the complete signature request header information (including algorithm identifier and key handle), and a link to the parent request context.

[0092] As can be seen from the above embodiments, dividing the data to be signed in the signature request into multiple sub-tasks by using a preset task length improves the efficiency of the system in performing signature verification tasks.

[0093] In one embodiment of this application, after step S2033, the method further includes:

[0094] S2034: Get the thread status of multiple threads in the thread pool.

[0095] Specifically, before distributing tasks, the task scheduler first queries the thread pool manager for information. The manager returns the thread states of multiple threads in the thread pool.

[0096] In this embodiment, the thread state includes, but is not limited to, each thread's ID, current state (such as "idle", "busy", "blocked"), continuous runtime, and the type of the most recently processed task.

[0097] S2035: Assign multiple signature verification subtasks based on the thread states of multiple threads in the thread pool, and generate thread allocation results.

[0098] Specifically, the task scheduler adopts a thread scheduling strategy based on the thread state, mapping multiple signature verification subtasks in the queue to the selected thread one by one.

[0099] S2036: Execute multiple signature verification subtasks based on the thread allocation result.

[0100] Specifically, the task scheduler, based on the thread allocation results, dispatches each signature verification subtask to the corresponding thread through the thread pool's API. Each thread, in its independent execution context, invokes the cryptographic computation library and uses the specified key and algorithm to perform the specific signature verification calculations on its assigned subtask block. All threads execute concurrently, collectively completing the verification process for the entire signature request.

[0101] As can be seen from the above embodiments, by obtaining the thread status of the threads in the thread pool, allocating multiple signature verification sub-tasks according to the thread status, and executing the signature verification sub-tasks, the utilization rate of threads is improved.

[0102] In one embodiment of this application, step S204 includes:

[0103] S2041: Retrieve multiple request identifiers from the signature request.

[0104] Specifically, multiple request identifiers in the signature request are obtained through a multi-algorithm interface layer.

[0105] In this embodiment, the request identifier is recorded in the request header.

[0106] S2042: Identify multiple request identifiers and obtain the signature verification algorithm type corresponding to the multiple request identifiers.

[0107] Specifically, based on each request identifier, the request algorithm registry is queried to obtain the algorithm type corresponding to each request identifier.

[0108] In this embodiment, the request algorithm registry is established during the request initialization phase and records the cryptographic algorithm pre-set for each request identifier.

[0109] S2043: Match the signature verification process according to the signature verification algorithm type.

[0110] Specifically, if the request is for a quantum-resistant algorithm, then a dynamic quantum-resistant algorithm parameter adjustment and parallel computing process is triggered.

[0111] Specifically, for requests using classic algorithms, the signature verification process is executed directly by calling the algorithm library.

[0112] S2044: Execute multiple signature verification sub-tasks according to the signature verification process to generate multiple signature verification results.

[0113] Specifically, based on the signature verification results output by the algorithm library and the parallel computing engine, the signature verification results are summarized to generate multiple signature verification results.

[0114] As can be seen from the above embodiments, by obtaining the request identifier in the signature request, identifying the request identifier, obtaining the corresponding signature verification algorithm type, and matching the signature verification process according to different signature verification algorithm types, the switching between quantum-resistant algorithms and classical algorithms can be realized, reducing code redundancy.

[0115] Figure 3 This is a schematic diagram of the cloud platform signature verification device provided in this application, as shown below. Figure 3As shown, the cloud platform signature verification device 30 provided in this embodiment includes: a load monitoring module 301, a parameter adjustment module 302, a task splitting module 303, a parallel computing module 304, and a splicing module 305.

[0116] The load monitoring module 301 is used to respond to the signature request sent by the receiving business terminal and obtain the load status data of the cloud platform according to the signature request.

[0117] The parameter adjustment module 302 is used to adjust the parameters of the anti-quantum algorithm according to the load status data of the cloud platform to obtain the adjusted security parameters.

[0118] The task splitting module 303 is used to split the signature verification task in the signature request into multiple signature verification sub-tasks.

[0119] The parallel computing module 304 is used to execute multiple signature verification subtasks based on the adjusted security parameters and generate multiple signature verification results.

[0120] The splicing module 305 is used to splice multiple signature verification results and send the spliced ​​signature verification results to the business end to complete the signature verification.

[0121] In one possible implementation, the parameter adjustment module 302 includes:

[0122] The judgment unit is used to determine the load status of the cloud platform based on the load status data of the cloud platform.

[0123] The query unit is used to query the security parameter mapping table based on the cloud platform's load status and obtain methods for adjusting security parameters.

[0124] The adjustment unit is used to adjust the parameters of the quantum-resistant algorithm according to the adjustment method of the security parameters, so as to obtain the adjusted security parameters.

[0125] In one possible implementation, the parameter adjustment module 302 further includes:

[0126] The detection unit is used to call the security verification tool to detect the security level of the adjusted security parameters.

[0127] The callback unit is used to perform a callback operation on the parameters of the quantum algorithm if the security level of the adjusted security parameters is lower than the preset security threshold, so as to obtain the default parameters of the quantum algorithm.

[0128] In one possible implementation, the task splitting module 303 includes:

[0129] The first acquisition unit is used to acquire the data to be signed in the signature request.

[0130] The partitioning unit is used to divide the data to be signed in the signature request into multiple sub-task blocks according to the preset task length.

[0131] The encapsulation unit is used to encapsulate multiple subtask blocks to obtain multiple signature verification subtasks.

[0132] In one possible implementation, the task splitting module 303 further includes:

[0133] The second acquisition unit is used to acquire the thread status of multiple threads in the thread pool.

[0134] The allocation unit is used to allocate multiple signature verification subtasks based on the thread states of multiple threads in the thread pool and generate thread allocation results.

[0135] The first execution unit is used to execute multiple signature verification subtasks based on the thread allocation results.

[0136] In one possible implementation, the parallel computing module 304 includes:

[0137] The third acquisition unit is used to acquire multiple request identifiers in the signature request.

[0138] The identification unit is used to identify multiple request identifiers and obtain the signature verification algorithm type corresponding to the multiple request identifiers.

[0139] The matching unit is used to match the signature verification process according to the signature verification algorithm type.

[0140] The second execution unit is used to execute multiple signature verification sub-tasks according to the signature verification process and generate multiple signature verification results.

[0141] The cloud platform signature verification device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0142] Figure 4 A schematic diagram of the structure of the electronic device provided in this application. Figure 4 As shown, the electronic device 40 provided in this embodiment includes at least one processor 401 and a memory 402. Optionally, the electronic device 40 further includes a communication component 403. The processor 401, memory 402, and communication component 403 are connected via a bus.

[0143] In the specific implementation process, at least one processor 401 executes computer execution instructions stored in memory 402, causing at least one processor 401 to execute the above-mentioned cloud platform signature verification method.

[0144] The specific implementation process of processor 401 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0145] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0146] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0147] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0148] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the cloud platform signature verification method described above.

[0149] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the aforementioned cloud platform signature verification method.

[0150] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0151] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0152] The division of units is merely a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0153] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0154] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0155] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0156] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0157] Finally, it should be noted that other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein, and is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A cloud platform signature verification method, characterized in that, include: In response to a signature request sent by the receiving service, the load status data of the cloud platform is obtained based on the signature request; The parameters of the quantum-resistant algorithm are adjusted based on the load status data of the cloud platform to obtain the adjusted security parameters; The signature verification task in the signature request is split into multiple signature verification sub-tasks; Execute the multiple signature verification sub-tasks according to the adjusted security parameters to generate multiple signature verification results; The multiple signature verification results are concatenated, and the concatenated signature verification result is sent to the business terminal to complete the signature verification.

2. The method according to claim 1, characterized in that, The step of adjusting the parameters of the quantum-resistant algorithm based on the load status data of the cloud platform to obtain the adjusted security parameters includes: The load status of the cloud platform is determined based on the load status data of the cloud platform; The security parameter mapping table is queried based on the load status of the cloud platform to obtain the method for adjusting the security parameters; The parameters of the quantum-resistant algorithm are adjusted according to the aforementioned method for adjusting security parameters to obtain the adjusted security parameters.

3. The method according to claim 2, characterized in that, After adjusting the parameters of the anti-quantum algorithm according to the method for adjusting the security parameters to obtain the adjusted security parameters, the method further includes: Use security verification tools to check the security level of the adjusted security parameters; If the security level of the adjusted security parameters is lower than the preset security threshold, a callback operation is performed on the parameters of the quantum algorithm to obtain the default parameters of the quantum algorithm.

4. The method according to claim 1, characterized in that, The step of splitting the signature verification task in the signature request into multiple signature verification sub-tasks includes: Obtain the data to be signed from the signature request; The data to be signed in the signature request is divided into multiple sub-task blocks according to the preset task length; The multiple subtask blocks are encapsulated to obtain multiple signature verification subtasks.

5. The method according to claim 4, characterized in that, After encapsulating the multiple subtask blocks to obtain multiple signature verification subtasks, the process further includes: Get the thread status of multiple threads in the thread pool; Multiple signature verification subtasks are assigned based on the thread states of multiple threads in the thread pool, and thread allocation results are generated. The multiple signature verification subtasks are executed based on the thread allocation result.

6. The method according to claim 1, characterized in that, The process of executing the multiple signature verification subtasks based on the adjusted security parameters to generate multiple signature verification results includes: Retrieve multiple request identifiers from the signature request; Identify the multiple request identifiers to obtain the signature verification algorithm types corresponding to the multiple request identifiers; The signature verification process is matched according to the signature verification algorithm type; The multiple signature verification sub-tasks are executed according to the signature verification process to generate multiple signature verification results.

7. A cloud platform signature verification device, characterized in that, include: The load monitoring module is used to respond to the signature request sent by the business terminal and obtain the load status data of the cloud platform according to the signature request; The parameter adjustment module is used to adjust the parameters of the anti-quantum algorithm according to the load status data of the cloud platform to obtain the adjusted security parameters; The task splitting module is used to split the signature verification task in the signature request into multiple signature verification sub-tasks; The parallel computing module is used to execute the multiple signature verification subtasks according to the adjusted security parameters and generate multiple signature verification results; The splicing module is used to splice the multiple signature verification results and send the spliced ​​signature verification results to the business terminal to complete the signature verification.

8. An electronic device, characterized in that, include: Memory, processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the cloud platform signature verification method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the cloud platform signature verification method as described in any one of claims 1 to 6.

10. A computer program product, characterized in that, It includes a computer program that, when executed by a processor, implements the cloud platform signature verification method according to any one of claims 1 to 6.

Images