Signature verification method and device

Abstract

The present disclosure provides a signature verification method, which relates to the field of financial technology. The method includes: obtaining transaction elements, wherein the transaction elements are sent by the user through a nested page, the nested page is nested in the page of the target application, and the target application includes any one of at least one specific application; initializing and verifying the transaction elements; and in response to the transaction elements passing the initialization verification, returning a signature verification page to the target application, wherein the signature verification page contains at least one signature verification method, and calling different signature verification methods can perform signature verification on different types of transaction data. The present disclosure also provides a signature verification device, an electronic device, a computer-readable storage medium, and a computer program product.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a signature verification method and device, an electronic device, a computer-readable storage medium, and a computer program product. Background Art

[0002] Traditional signature verification uses a centralized architecture, that is, each application uses an independent signature verification server for signature verification. Due to the importance and wide use of signature verification, and the high coupling of the centralized architecture, frequent signature verification operations will put a lot of pressure on the signature verification server. Summary of the invention

[0003] One aspect of the present disclosure provides a signature verification method, including: obtaining transaction elements, wherein the transaction elements are submitted by a user through a nested page, wherein the nested page is nested in a page of a target application, and the target application includes any one of at least one specific application; initializing verification of the transaction elements; and in response to the transaction elements passing the initialization verification, returning a signature verification page to the target application, wherein the signature verification page includes at least one signature verification method, and calling different signature verification methods can perform signature verification on different types of transaction data.

[0004] Optionally, it also includes: after returning the signature verification page to the target application, calling the signature verification method selected by the user to perform signature verification on the transaction data with signature information sent by the target application.

[0005] Optionally, the transaction element includes: a signature identifier; the method further includes: clearing the signature identifier after performing signature verification on the transaction data with signature information sent by the target application.

[0006] Optionally, the signature information includes: a signature identifier; performing signature verification on the transaction data with signature information sent by the target application, including at least one of the following: verifying whether the signature identifier is valid; verifying whether the signature identifier is legal; and verifying whether the signature identifier is consistent with the signature identifier included in the transaction element.

[0007] Optionally, performing signature verification on the transaction data with signature information sent by the target application further includes: verifying whether a user identifier associated with the transaction data with signature information is consistent with a user identifier included in the transaction element.

[0008] Optionally, the at least one signature verification method includes: a signature verification method set for each business submission; and / or a signature verification method set for batch submission of services.

[0009] Another aspect of the present disclosure provides another signature verification method, including: obtaining transaction elements input by a user in a nested page, wherein the nested page is nested in a page of a target application, and the target application includes any one of at least one specific application; sending the transaction elements to a signature verification group, so that the signature verification group performs initialization verification on the transaction elements, and returns a signature verification page to the target application when the transaction elements pass the initialization verification, wherein the signature verification page contains at least one signature verification method, and calling different signature verification methods can perform signature verification on different types of transaction data.

[0010] Optionally, it also includes: obtaining and displaying the signature verification page returned by the signature verification group in the target application; in response to a signature verification method being selected on the signature verification page, causing the target application to jump to a transaction page; obtaining transaction data with signature information entered by the user in the transaction page; and sending the transaction data with signature information to the signature verification group for signature verification.

[0011] Another aspect of the present disclosure provides a signature verification device, including: a first acquisition module, used to acquire transaction elements, wherein the transaction elements are submitted by the user through a nested page, and the nested page is nested in the page of a target application, and the target application includes any one of at least one specific application; an initialization verification module, used to perform initialization verification on the transaction elements; and a page return module, used to return a signature verification page to the target application in response to the transaction elements passing the initialization verification, wherein the signature verification page contains at least one signature verification method, and calling different signature verification methods can perform signature verification on different types of transaction data.

[0012] Optionally, the device further includes: a calling module, configured to call a signature verification method selected by the user after returning the signature verification page to the target application, and perform signature verification on the transaction data with signature information sent by the target application.

[0013] Optionally, the transaction elements include: a signature identifier; the device also includes: a clearing module, which is used to clear the signature identifier after the signature is verified on the transaction data with signature information sent by the target application.

[0014] Optionally, the signature information includes: a signature identifier; the calling module is also used to call a signature verification method selected by the user and perform at least one of the following: verifying whether the signature identifier is valid; verifying whether the signature identifier is legal; and verifying whether the signature identifier is consistent with the signature identifier included in the transaction element.

[0015] Optionally, the calling module is further used to call a signature verification method selected by the user and execute: verifying whether the user identifier associated with the transaction data with signature information is consistent with the user identifier included in the transaction element.

[0016] Optionally, the at least one signature verification method includes: a signature verification method set for each business submission; and / or a signature verification method set for batch submission of services.

[0017] Another aspect of the present disclosure provides another signature verification device, including: a second acquisition module, used to obtain transaction elements input by a user in a nested page, wherein the nested page is nested in a page of a target application, and the target application includes any one of at least one specific application; an information upload module, used to upload the transaction elements to a signature verification group, so that the signature verification group performs initialization verification on the transaction elements, and returns a signature verification page to the target application when the transaction elements pass the initialization verification, wherein the signature verification page contains at least one signature verification method, and calling different signature verification methods can perform signature verification on different types of transaction data.

[0018] Optionally, the device also includes: a third acquisition module, used to acquire and display the signature verification page returned by the signature verification group in the target application; a page jump module, used to cause the target application to jump to the transaction page in response to a signature verification method being selected on the signature verification page; a fourth acquisition module, used to acquire transaction data with signature information entered by the user in the transaction page; and a sending module, used to send the transaction data with signature information to the signature verification group for signature verification.

[0019] Another aspect of the present disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method of an embodiment of the present disclosure.

[0020] Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions, which are used to implement the method of the embodiment of the present disclosure when executed.

[0021] Another aspect of the present disclosure provides a computer program product, including a computer program, which implements the method described in the embodiment of the present disclosure when executed by a processor. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] For a more complete understanding of the present disclosure and its advantages, reference will now be made to the following description taken in conjunction with the accompanying drawings, in which:

[0023] Figure 1 The system architecture of the method and device for signature verification according to the embodiment of the present disclosure is schematically shown;

[0024] Figure 2 A flowchart of a signature verification method according to an embodiment of the present disclosure is schematically shown;

[0025] Figure 3 A flowchart of a signature verification method according to another embodiment of the present disclosure is schematically shown;

[0026] Figure 4 A flowchart of a signature verification method according to another embodiment of the present disclosure is schematically shown;

[0027] Figure 5 A schematic diagram schematically shows verification items involved in signature verification according to an embodiment of the present disclosure;

[0028] Figure 6 A flowchart of a signature verification method according to another embodiment of the present disclosure is schematically shown;

[0029] Figure 7 A block diagram of a signature verification device according to an embodiment of the present disclosure is schematically shown;

[0030] Figure 8 A block diagram schematically shows a signature verification device according to another embodiment of the present disclosure; and

[0031] Fig. 9 A block diagram of an electronic device according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0032] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0033] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0034] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification, and should not be interpreted in an idealized or overly rigid manner.

[0035] When using expressions such as "at least one of A, B, and C, etc.", they should generally be interpreted according to the meaning of the expression commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0036] Some block diagrams and / or flow charts are shown in the accompanying drawings. It should be understood that some boxes or combinations thereof in the block diagrams and / or flow charts can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that these instructions can create a device for implementing the functions / operations described in these block diagrams and / or flow charts when executed by the processor. The technology of the present disclosure can be implemented in the form of hardware and / or software (including firmware, microcode, etc.). In addition, the technology of the present disclosure can take the form of a computer program product on a computer-readable storage medium storing instructions, which can be used by an instruction execution system or used in conjunction with an instruction execution system.

[0037] The embodiment of the present disclosure provides a signature verification method and a device capable of applying the method. The method includes obtaining transaction elements, wherein the transaction elements are sent by the user through a nested page, the nested page is nested in the page of a target application, and the target application includes any one of at least one specific application; initializing and verifying the transaction elements; and returning a signature verification page to the target application in response to the transaction elements passing the initialization verification, wherein the signature verification page includes at least one signature verification method, and calling different signature verification methods can perform signature verification on different types of transaction data.

[0038] Figure 1 The system architecture of the method and device for signature verification according to the embodiment of the present disclosure is schematically shown. It should be noted that: Figure 1 What is shown is merely an example of a system architecture to which the embodiments of the present disclosure can be applied, in order to help those skilled in the art understand the technical content of the present disclosure, but it does not mean that the embodiments of the present disclosure cannot be used in other devices, systems, environments or scenarios.

[0039] like Figure 1As shown, the system architecture 100 includes: a signature verification system 101, applications 102, 103, 104, ..., and a transaction system 105.

[0040] It should be noted that, in the disclosed embodiment, the signature verification system 101 includes a signature verification group. These signature verification groups are deployed in a distributed architecture. The signature verification system 101 can provide signature verification services for multiple applications at the same time. Exemplarily, in the disclosed embodiment, after applying for transaction services, these applications need to pass the signature verification of the signature verification system 101 before they can interact with the transaction system 105 to implement transaction operations.

[0041] Traditional signature verification mostly adopts a centralized architecture, that is, each application uses an independent signature verification server for signature verification. Due to the importance and wide use of signature verification, and the high coupling of the centralized architecture, frequent signature verification operations will bring great pressure to the signature verification server.

[0042] Signature verification is an important means to ensure the security of banking transaction systems, and it is also an important way to record transaction information. Specifically, signature verification can not only ensure the transaction security of users, but also serve as a legal basis to prevent users from denying their rights.

[0043] To this end, the embodiment of the present disclosure provides a signature verification mechanism under a distributed architecture. The signature verification function is extracted from the centralized framework and divided into multiple distributed groups according to the function, which can solve the above-mentioned problems existing in the centralized signature verification service in the related art.

[0044] In the disclosed embodiment, the signature verification group can provide the signature verification function to the access party (such as various transaction systems of a bank) in the form of a page interface (nested page), thereby realizing signature verification under a distributed architecture for various applications.

[0045] It should be understood that a distributed architecture refers to a system architecture in which combined components such as hardware or software are distributed on different network computers and communicate and coordinate with each other through message passing.

[0046] It should also be understood that signature verification refers to the use of encryption methods such as U-shields and certificates to ensure that the user's transaction information is not tampered with or intercepted.

[0047] It should also be understood that the page interface, also known as the API interface, refers to some predefined functions. The purpose of setting up the API interface is to provide applications and developers with the ability to access a set of routines based on certain software or hardware, so that applications and developers do not need to access the source code or understand the details of the internal working mechanism of these routines.

[0048] In addition, in the disclosed embodiment, the signature verification group uses the GTP file transfer system for file transfer. If there are too many nodes under the GTP file transfer system, in the scenario of a surge in transaction volume, file transfer failures may occur occasionally.

[0049] It should be understood that the GTP file transfer system can provide various management, deployment and security functions required for large-scale data transmission in enterprises, making it convenient and easy to use. In the GTP file transfer system, reliable, secure and efficient file transmission between upper and lower nodes can be achieved through simple configuration.

[0050] It should be understood that Figure 1 The number of applications in the above example is only for illustration. The number of signature verification servers in the signature verification group is also only for illustration. Any number of applications and signature verification servers may be provided as required.

[0051] The present disclosure will be described in detail below with reference to specific embodiments.

[0052] Figure 2 The flowchart of the signature verification method according to an embodiment of the present disclosure is schematically shown.

[0053] like Figure 2 As shown, the method 200 includes operations S210 to S230.

[0054] In operation S210, transaction elements are obtained, wherein the transaction elements are sent by the user through a nested page, the nested page is nested in a page of a target application, and the target application includes any one of at least one specific application.

[0055] In operation S220, the transaction elements are initially verified.

[0056] In operation S230, in response to the transaction element passing the initialization verification, a signature verification page is returned to the target application, wherein the signature verification page includes at least one signature verification method, and different signature verification methods can be called to perform signature verification on different types of transaction data.

[0057] It should be noted that in the embodiment of the present disclosure, the execution subject of operations S210 to S230 may be a signature verification group, so a distributed architecture is used for signature verification. The nested page may be an API interface embedded in a specific application by a financial institution. Through the nested page, the signature verification group may provide a signature verification function for the access party.

[0058] In one embodiment of the present disclosure, the access party can perform initialization of signature verification (initialization verification) through a URL provided by the signature verification group embedded in its page. After the signature verification group passes the initialization, the signature verification page provided by the signature verification group is returned to the specific application. The signature verification page may include one or more signature verification methods, and different signature verification methods indicate signature verification for different types of transaction data. Exemplarily, the signature verification method may include a signature verification method set for each transaction submission, and may also include a signature verification method set for batch submission of services. It should be noted that in the embodiment of the present disclosure, the signature verification method contained in the signature verification page may be a JS method.

[0059] If the user selects the signature verification method set for each business submitted on the signature verification page, the signature verification method selected by the user can be called to request the signature verification group to perform signature verification on the business submitted by the user one by one. If the user selects the signature verification method set for batch submission on the signature verification page, the signature verification method selected by the user can be called to request the signature verification group to perform signature verification on the batch submission of the user.

[0060] Specifically, in the disclosed embodiment, a page (such as page 2) can be nested in a page (such as page 1) of a specific application. During the signature verification initialization (one-time signature verification), the user can enter his or her transaction elements in page 2 and submit them to the signature verification group for initialization verification. After the initialization verification passes, the signature verification group returns the signature verification page (such as page 3) to the specific application. The user can enter transaction data with signature information in page 3 for the signature verification group to perform secondary signature verification.

[0061] It should be noted that, in the embodiments of the present disclosure, the transaction elements may include one or more of the following information: signature unique identifier (signature ID, i.e., signId), transaction language (language), login user unique identifier (logon user ID, i.e., logonId), CA type (caType), media type (mediaType), bank involved in the transaction (bankKind), area code (areaCode), random number (ns), parsing rules (parsingRules), and so on.

[0062] For example, the transaction elements required to be submitted for the Iffame link of the corporate online banking transaction authentication interface are shown in Table 1. Among them, "Y" represents the transaction elements that must be submitted, and "N" represents the transaction elements that can be submitted selectively.

[0063] Table 1

[0064]

[0065] Through the disclosed embodiments, the signature verification group deployed in a distributed architecture provides a unified signature verification service to each access party, which can solve the technical problems of high coupling and difficulty in expansion of signature verification under the centralized architecture in traditional technologies. At the same time, it can reduce the request pressure of each transaction system under the centralized architecture. It is also easy to expand horizontally and can support a huge transaction volume.

[0066] As an optional embodiment, Figure 3 As shown, method 300 includes the following Figure 2 In addition to the operations S210 to S230 shown, after returning the signature verification page to the target application, the following may also be included: operation S310.

[0067] In operation S310, the signature verification method selected by the user is called to perform signature verification on the transaction data with signature information sent by the target application.

[0068] Exemplarily, the access party embeds the URL provided by the signature verification group in its own transaction page, and sends the transaction elements shown in Table 1 to the signature verification group. The signature verification group first performs initial verification on these transaction elements, such as performing different initialization verifications based on the user login ID, certificate type, media type, etc. sent by the access party.

[0069] After the initialization verification is passed, the signature verification group returns the signature verification page to the access party. The signature verification page contains the signature verification method set for each business submission, and / or the signature verification method set for batch submission of business. Users can choose different signature verification methods according to transaction needs. For example, if the user needs to submit the business one by one, you can choose the signature verification method set for each business submission; if the user needs to submit the business in batches, you can choose the signature verification method set for batch submission of business. It should be understood that when the user selects the corresponding signature verification method while submitting the transaction data, the signature verification (secondary signature verification) can be performed through the signature verification group.

[0070] Specifically, the user submits the transaction on the transaction page provided by the access party and selects the corresponding signature verification method when submitting. During this process, the user can operate the U-shield to confirm the signature information and enter the U-shield password. After the user enters the U-shield password and presses the confirmation button to submit the transaction data, the access party can automatically submit the signature information encrypted by the control to the signature verification group.

[0071] The signature verification group can perform signature verification according to the following process: verify whether the signId is valid; verify the certificate medium number and public key; verify whether the signId is legal, such as calling the signature verification component to verify whether the signId is legal; after the above verifications are passed, compare the login user name, signature string, and U shield on the screen to see if they are consistent with those sent on the page.

[0072] After the entire signature verification process is completed, whether successful or not, the verification result returned by the signature verification group can be encrypted by the encryption component and returned to the access party. Finally, the signature verification group can clear the signId from the cache to ensure the atomicity of the signature verification process (i.e., prevent repeated signature verification for signId).

[0073] It should be understood that if the user selects the signature verification method set for the batch submission business when submitting transaction data, then after the verification result is successful and the user submits the transaction data in batches successfully, the access party can proceed with the next transaction process.

[0074] It should also be understood that in the embodiments of the present disclosure, the security of transactions can be ensured through file encryption and decryption and communication encryption and decryption.

[0075] It should also be understood that while signature verification is used to ensure that the user's transaction information is not tampered with or intercepted, the signature verification information can also be recorded to prevent it from serving as legal evidence for user denial.

[0076] As an optional embodiment, the above transaction elements may include: signature identification (i.e., signature ID). Figure 4 As shown, method 400 includes the following Figure 3 In addition to the operations S210 to S230 and operation S310 shown, after the signature verification is performed on the transaction data with signature information sent by the target application, operation S410 may also be included.

[0077] Operation S410: Clear the signature flag.

[0078] Specifically, after the entire signature verification process is completed, whether successful or not, the verification result returned by the signature verification group can be encrypted by the encryption component and returned to the access party. Finally, the signature verification group can clear the signId from the cache to ensure the atomicity of the signature verification process (i.e., prevent repeated signature verification for signId).

[0079] As an optional embodiment, the above-mentioned signature information may include: a signature identifier (ie, a signature ID). Figure 5As shown, the transaction data with signature information sent by the target application is signed and verified, including at least one of the following: verifying whether the signature identifier is valid; verifying whether the signature identifier is legal; verifying whether the signature identifier is consistent with the signature identifier included in the transaction element; ...

[0080] It should be understood that verifying whether the signature mark is valid means verifying whether it is currently within the valid period of use of the signature mark. For example, if the valid period of use of the signature mark is 1 minute, from the start of the timer, verify whether the current cumulative time has exceeded 1 minute. If it is found that the current cumulative time has exceeded 1 minute, the signature mark is confirmed to be invalid, otherwise the signature mark is confirmed to be valid.

[0081] As an optional embodiment, signature verification is performed on transaction data with signature information sent by the target application. The method also includes: verifying whether the user identifier associated with the transaction data with signature information (i.e., the logged-in user ID) is consistent with the user identifier included in the transaction elements.

[0082] As an optional embodiment, the at least one signature verification method mentioned above includes: a signature verification method set for each business submission; and / or a signature verification method set for batch submission.

[0083] Exemplarily, after the initialization verification is passed, the signature verification group can return the signature verification page to the access party. The signature verification page can include the signature verification method set for each transaction submitted, and / or the signature verification method set for batch submission of services. Users can choose different signature verification methods according to transaction needs. For example, if the user needs to submit services one by one, the signature verification method set for each transaction submitted can be selected; if the user needs to submit services in batches, the signature verification method set for batch submission of services can be selected.

[0084] It should be understood that the transaction-by-transaction service usually does not involve file uploading, for example, transaction-by-transaction remittance belongs to the transaction-by-transaction service. In the disclosed embodiment, for the transaction-by-transaction service, the transaction data submitted by the user may be subjected to format conversion, authorization and other signature verification operations.

[0085] It should also be understood that batch submission services usually require uploading transaction data with files, such as payroll services, etc. In the disclosed embodiment, for batch submission services, the transaction data submitted by the user can also be format converted, authorized, and other signature verification operations.

[0086] In the disclosed embodiment, different signature verification methods are set for different transaction types, so different types of signature verification services can enter different processing flows. At the same time, transaction information can also be stored in different data tables in the database according to the transaction type and medium type.

[0087] In addition, in the disclosed embodiment, the signature verification group can also support fuses between different databases. For example, when an abnormality occurs in the primary database, the data source can be switched to the standby database to ensure that the core transaction database is read normally, thereby not affecting the signature verification process of normal transactions.

[0088] Figure 6 The following schematically shows a flow chart of a signature verification method according to another embodiment of the present disclosure.

[0089] like Figure 6 As shown, the method 600 includes operations S610 to S620.

[0090] In operation S610, a transaction element input by a user in a nested page is obtained, wherein the nested page is nested in a page of a target application, and the target application includes any one of at least one specific application.

[0091] In operation S620, the transaction elements are sent to the signature verification group, so that the signature verification group performs initial verification on the transaction elements, and returns the signature verification page to the target application when the transaction elements pass the initial verification. The signature verification page contains at least one signature verification method, and calling different signature verification methods can perform signature verification on different types of transaction data.

[0092] It should be noted that in the disclosed embodiment, the execution subject of operations S610 to S620 can be each transaction system (i.e., each access party), so a distributed architecture is used for signature verification. The nested page can be an API interface embedded in a specific application by a financial institution. Through the nested page, the signature verification group can provide the access party with a signature verification function.

[0093] In one embodiment of the present disclosure, the access party can perform initialization of signature verification (initialization verification) through a URL provided by the signature verification group embedded in its page. After the signature verification group passes the initialization, the signature verification page provided by the signature verification group is returned to the specific application. The signature verification page may include one or more signature verification methods, and different signature verification methods indicate signature verification for different types of transaction data. Exemplarily, the signature verification method may include a signature verification method set for each transaction submission, and may also include a signature verification method set for batch submission of services. It should be noted that in the embodiment of the present disclosure, the signature verification method contained in the signature verification page may be a JS method.

[0094] If the user selects the signature verification method set for each business submitted on the signature verification page, the signature verification method selected by the user can be called to request the signature verification group to perform signature verification on the business submitted by the user one by one. If the user selects the signature verification method set for batch submission on the signature verification page, the signature verification method selected by the user can be called to request the signature verification group to perform signature verification on the batch submission of the user.

[0095] Specifically, in the disclosed embodiment, a page (such as page 2) can be nested in a page (such as page 1) of a specific application. During the signature verification initialization (one-time signature verification), the user can enter his or her transaction elements in page 2 and submit them to the signature verification group for initialization verification. After the initialization verification passes, the signature verification group returns the signature verification page (such as page 3) to the specific application. The user can enter transaction data with signature information in page 3 for the signature verification group to perform secondary signature verification.

[0096] It should be noted that, in the embodiments of the present disclosure, the transaction elements may include one or more of the following information: signature unique identifier (signature ID, i.e., signId), transaction language (language), login user unique identifier (logon user ID, i.e., logonId), CA type (caType), media type (mediaType), bank involved in the transaction (bankKind), area code (areaCode), random number (ns), parsing rules (parsingRules), and so on.

[0097] Exemplarily, the transaction elements required to be submitted in the corporate online banking transaction authentication interface Iframe link are shown in Table 1. Among them, "Y" represents a transaction element that must be submitted, and "N" represents a transaction element that can be submitted selectively.

[0098] Through the disclosed embodiments, the signature verification group deployed in a distributed architecture provides a unified signature verification service to each access party, which can solve the technical problems of high coupling and difficulty in expansion of signature verification under the centralized architecture in traditional technologies. At the same time, it can reduce the request pressure of each transaction system under the centralized architecture. It is also easy to expand horizontally and can support a huge transaction volume.

[0099] As an optional embodiment, the method also includes the following operations.

[0100] Get and display the signature verification page returned by the signature verification group in the target application.

[0101] In response to a signature verification method being selected in the signature verification page, the target application is redirected to the transaction page.

[0102] Get the transaction data with signature information entered by the user on the transaction page.

[0103] Submit the transaction data with signature information to the signature verification group for signature verification.

[0104] Exemplarily, the access party embeds the URL provided by the signature verification group in its own transaction page, and sends the transaction elements shown in Table 1 to the signature verification group. The signature verification group first performs initial verification on these transaction elements, such as performing different initialization verifications based on the user login ID, certificate type, media type, etc. sent by the access party.

[0105] After the initialization verification is passed, the signature verification group returns the signature verification page to the access party. The signature verification page contains the signature verification method set for each business submission, and / or the signature verification method set for batch submission of business. Users can choose different signature verification methods according to transaction needs. For example, if the user needs to submit the business one by one, you can choose the signature verification method set for each business submission; if the user needs to submit the business in batches, you can choose the signature verification method set for batch submission of business. It should be understood that when the user selects the corresponding signature verification method while submitting the transaction data, the signature verification (secondary signature verification) can be performed through the signature verification group.

[0106] Specifically, the user submits the transaction on the transaction page provided by the access party and selects the corresponding signature verification method when submitting. During this process, the user can operate the U-shield to confirm the signature information and enter the U-shield password. After the user enters the U-shield password and presses the confirmation button to submit the transaction data, the access party can automatically submit the signature information encrypted by the control to the signature verification group.

[0107] The signature verification group can perform signature verification according to the following process: verify whether the signId is valid; verify the certificate medium number and public key; verify whether the signId is legal, such as calling the signature verification component to verify whether the signId is legal; after the above verifications are passed, compare the login user name, signature string, and U shield on the screen to see if they are consistent with those sent on the page.

[0108] After the entire signature verification process is completed, whether successful or not, the verification result returned by the signature verification group can be encrypted by the encryption component and returned to the access party. Finally, the signature verification group can clear the signId from the cache to ensure the atomicity of the signature verification process (i.e., prevent repeated signature verification for signId).

[0109] It should be understood that if the user selects the signature verification method set for the batch submission business when submitting transaction data, then after the verification result is successful and the user submits the transaction data in batches successfully, the access party can proceed with the next transaction process.

[0110] It should also be understood that in the embodiments of the present disclosure, the security of transactions can be ensured through file encryption and decryption and communication encryption and decryption.

[0111] It should also be understood that while signature verification is used to ensure that the user's transaction information is not tampered with or intercepted, the signature verification information can also be recorded to prevent it from serving as legal evidence for user denial.

[0112] Figure 7 A block diagram of a signature verification device according to an embodiment of the present disclosure is schematically shown.

[0113] like Figure 7 As shown, the processing device 700 applied to data backup includes a first acquisition module 710, an initialization verification module 720 and a page return module 730. The processing device can execute the method described in the above reference method embodiment part, which will not be repeated here.

[0114] Specifically, the first acquisition module 710 is used to acquire transaction elements, wherein the transaction elements are sent by the user through a nested page, the nested page is nested in a page of a target application, and the target application includes any one of at least one specific application.

[0115] The initialization verification module 720 is used to perform initialization verification on the transaction element.

[0116] The page return module 730 is used to return a signature verification page to the target application in response to the transaction element passing the initialization verification, wherein the signature verification page includes at least one signature verification method, and calling different signature verification methods can perform signature verification on different types of transaction data.

[0117] As an optional embodiment, the device also includes: a calling module, which is used to call the signature verification method selected by the user after returning the signature verification page to the target application, and perform signature verification on the transaction data with signature information sent by the target application.

[0118] As an optional embodiment, the transaction element includes: a signature identifier; the device also includes: a clearing module, which is used to clear the signature identifier after the transaction data with signature information sent by the target application is signed and verified.

[0119] As an optional embodiment, the signature information includes: a signature identifier; the calling module is also used to call the signature verification method selected by the user and perform at least one of the following: verifying whether the signature identifier is valid; verifying whether the signature identifier is legal; and verifying whether the signature identifier is consistent with the signature identifier included in the transaction element.

[0120] As an optional embodiment, the calling module is further used to call the signature verification method selected by the user and execute: verifying whether the user identifier associated with the transaction data with signature information is consistent with the user identifier included in the transaction element.

[0121] As an optional embodiment, the at least one signature verification method includes: a signature verification method set for each business submission; and / or a signature verification method set for batch submission of services.

[0122] Figure 8 A block diagram of a signature verification device according to another embodiment of the present disclosure is schematically shown.

[0123] like Figure 8 As shown, the processing device 800 applied to data backup includes a second acquisition module 810 and an information upload module 820. The processing device can execute the method described in the above reference method embodiment, which will not be repeated here.

[0124] Specifically, the second acquisition module 810 is used to acquire the transaction elements entered by the user in the nested page, wherein the nested page is nested in the page of the target application, and the target application includes any one of at least one specific application.

[0125] The information upload module 820 is used to upload the transaction element to the signature verification group, so that the signature verification group performs initial verification on the transaction element, and returns the signature verification page to the target application when the transaction element passes the initial verification, wherein the signature verification page contains at least one signature verification method, and calling different signature verification methods can perform signature verification on different types of transaction data.

[0126] As an optional embodiment, the device also includes: a third acquisition module, used to acquire and display the signature verification page returned by the signature verification group in the target application; a page jump module, used to cause the target application to jump to the transaction page in response to a signature verification method being selected on the signature verification page; a fourth acquisition module, used to acquire transaction data with signature information entered by the user in the transaction page; and a sending module, used to send the transaction data with signature information to the signature verification group for signature verification.

[0127] It should be noted that the embodiments of the various device parts of the present disclosure are the same or similar to the embodiments of the various method parts of the present disclosure, and the technical effects achieved are also the same or similar, which will not be repeated here.

[0128] According to any one or more of the modules of the embodiments of the present disclosure, or at least part of the functions of any one of them, can be implemented in one module. According to any one or more of the modules of the embodiments of the present disclosure, it can be split into multiple modules for implementation. According to any one or more of the modules of the embodiments of the present disclosure, it can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application-specific integrated circuit (ASIC), or can be implemented by hardware or firmware of any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware and firmware or in any appropriate combination of any of them. Alternatively, according to one or more of the modules and units of the embodiments of the present disclosure, it can be at least partially implemented as a computer program module, and when the computer program module is run, the corresponding function can be performed.

[0129] For example, any multiple of the first acquisition module 710, the initialization verification module 720, and the page return module 730 can be combined in one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the first acquisition module 710, the initialization verification module 720, and the page return module 730 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application-specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware, and firmware, or in any appropriate combination of any of them. Alternatively, at least one of the first acquisition module 710, the initialization verification module 720, and the page return module 730 can be at least partially implemented as a computer program module, and when the computer program module is run, the corresponding function can be executed.

[0130] Fig. 9 A block diagram of an electronic device according to an embodiment of the present disclosure is schematically shown. Fig. 9 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0131] like Fig. 9 As shown, the electronic device 900 includes a processor 910 and a computer-readable storage medium 920. The electronic device 900 can execute the method according to the embodiment of the present disclosure.

[0132] Specifically, the processor 910 may include, for example, a general-purpose microprocessor, an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 910 may also include an onboard memory for cache purposes. The processor 910 may be a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0133] The computer-readable storage medium 920 may be, for example, a non-volatile computer-readable storage medium, specific examples of which include but are not limited to: a magnetic storage device, such as a magnetic tape or a hard disk (HDD); an optical storage device, such as a compact disk (CD-ROM); a memory, such as a random access memory (RAM) or flash memory; and the like.

[0134] The computer-readable storage medium 920 may include a computer program 921 , which may include code / computer-executable instructions that, when executed by the processor 910 , cause the processor 910 to perform a method according to an embodiment of the present disclosure or any variation thereof.

[0135] The computer program 921 may be configured to have, for example, a computer program code including a computer program module. For example, in an example embodiment, the code in the computer program 921 may include one or more program modules, for example, including 921A, module 921B, ... It should be noted that the division method and number of modules are not fixed, and those skilled in the art may use appropriate program modules or program module combinations according to actual conditions, and when these program module combinations are executed by the processor 910, the processor 910 may execute the method according to the embodiment of the present disclosure or any variation thereof.

[0136] According to an embodiment of the present disclosure, at least one of the first acquisition module 710, the initialization verification module 720, and the page return module 730 may be implemented as a reference. Fig. 9 The computer program modules described herein, when executed by the processor 910, can implement the corresponding operations described above.

[0137] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.

[0138] The flow charts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a 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 box can also occur in a different order from the order marked in the accompanying drawings. For example, two 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 box in the block diagram or flow chart, and the combination of the boxes in the block diagram 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] It will be appreciated by those skilled in the art that, although the present disclosure has been shown and described with reference to specific exemplary embodiments of the present disclosure, it will be appreciated by those skilled in the art that, without departing from the spirit and scope of the present disclosure as defined by the appended claims and their equivalents, various changes in form and detail may be made to the present disclosure. Therefore, the scope of the present disclosure should not be limited to the above-described embodiments, but should be determined not only by the appended claims, but also by the equivalents of the appended claims.

Claims

1. A signature verification method, the method being performed by a distributed signature verification group, comprising: Acquire transaction elements, wherein the transaction elements are sent by the user through a nested page, the nested page is nested in a page of a target application, the target application includes at least one application, and the target application belongs to different transaction systems; Initializing verification of the transaction elements; and In response to the transaction element passing the initialization verification, returning a signature verification page to the target application, wherein the signature verification page includes at least one signature verification method, and different signature verification methods are called to perform signature verification on different types of transaction data; The transaction element includes identification information corresponding to the transaction system, and the initialization verification of the transaction element includes: Based on the identification information, the transaction elements are initialized for verification.

2. The method according to claim 1, further comprising: After returning the signature verification page to the target application, Call the signature verification method selected by the user to perform signature verification on the transaction data with signature information sent by the target application.

3. The method according to claim 2, wherein: The transaction elements include: signature identification; The method further comprises: after performing signature verification on the transaction data with signature information sent by the target application, clearing the signature identifier.

4. The method according to claim 2, wherein: The signature information includes: a signature identifier; The performing signature verification on the transaction data with signature information sent by the target application includes at least one of the following: Verifying whether the signature identification is valid; Verifying whether the signature is legitimate; and Verify whether the signature identifier is consistent with the signature identifier included in the transaction element.

5. The method according to claim 4, wherein: The performing signature verification on the transaction data with signature information sent by the target application also includes: Verify whether the user identification associated with the transaction data with signature information is consistent with the user identification included in the transaction element.

6. The method according to claim 1, wherein: The at least one signature verification method comprises: A signature verification method for each transaction; and / or Signature verification method set for batch submission business.

7. A signature verification method, comprising: Acquire transaction elements input by a user in a nested page, wherein the nested page is nested in a page of a target application, the target application includes at least one application, and the target application belongs to different transaction systems; Send the transaction elements to the signature verification group, so that the signature verification group performs initial verification on the transaction elements, and returns a signature verification page to the target application if the transaction elements pass the initial verification, wherein the signature verification page includes at least one signature verification method, and different signature verification methods are called to perform signature verification on different types of transaction data; The transaction element includes identification information corresponding to the transaction system, and the initialization verification of the transaction element includes: Based on the identification information, the transaction elements are initialized for verification.

8. The method according to claim 7, further comprising: Obtain and display the signature verification page returned by the signature verification group in the target application; In response to a signature verification method being selected in the signature verification page, causing the target application to jump to a transaction page; Obtaining transaction data with signature information entered by the user in the transaction page; as well as The transaction data with signature information is sent to the signature verification group for signature verification.

9. A signature verification device, the device being installed in a distributed signature verification group, comprising: A first acquisition module is used to acquire transaction elements, wherein the transaction elements are sent by the user through a nested page, the nested page is nested in a page of a target application, the target application includes at least one application, and the target application belongs to different transaction systems; An initialization verification module, used to perform initialization verification on the transaction elements; and A page return module, configured to return a signature verification page to the target application in response to the transaction element passing the initialization verification, wherein the signature verification page includes at least one signature verification method, and different signature verification methods are called to perform signature verification on different types of transaction data; The transaction element includes identification information corresponding to the transaction system, and the initialization verification of the transaction element includes: Based on the identification information, the transaction elements are initialized for verification.

10. A signature verification device, comprising: A second acquisition module is used to acquire transaction elements input by a user in a nested page, wherein the nested page is nested in a page of a target application, the target application includes at least one application, and the target application belongs to different transaction systems; An information uploading module is used to upload the transaction elements to the signature verification group, so that the signature verification group performs initial verification on the transaction elements, and returns a signature verification page to the target application when the transaction elements pass the initial verification, wherein the signature verification page includes at least one signature verification method, and different signature verification methods are called to perform signature verification on different types of transaction data; The transaction element includes identification information corresponding to the transaction system, and the initialization verification of the transaction element includes: Based on the identification information, the transaction elements are initialized for verification.

11. An electronic device, comprising: one or more processors; a memory for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 8. 12 . A computer-readable storage medium storing computer-executable instructions, wherein the instructions are used to implement the method according to claim 1 when executed.

13. A computer program product comprising a computer program, which, when executed by a processor, implements the method according to any one of claims 1 to 8.

Images