Verification method, device, equipment and computer storage medium

Abstract

The application discloses a shield verification method and device, equipment and a computer storage medium. The method comprises the following steps: in the case of detecting the shield insertion, shield information of a user is acquired, and the shield information comprises the type of the shield; the shield verification mode is determined according to the type of the shield; the information of the user shield and the shield verification mode are sent to a service backend device, so as to acquire a signature template and a signature time from the service backend device; the signature template and the signature time sent by the service backend device are received; a signature request is sent to a shield component server according to the signature template and the signature time, so that the signature result is obtained by the signature of the shield component server. According to the embodiment of the application, when the business scene changes, the shield verification process is not affected, the same code can be used, if other business processes that need to be verified are added, the shield verification process does not need to be rewritten, a set of codes can be directly introduced, the development and maintenance work of the front end is reduced, repeated work is avoided, the research and development cost is saved, and the response time is shortened.

Description

Technical Field

[0001] This application belongs to the field of transaction identity authentication technology, and in particular relates to a method, device, equipment and computer storage medium for verification. Background Technology

[0002] In existing fund supervision systems, scenarios involving large-scale fund flows require manual operation. Currently, there are scenarios where a high-security verification method is used to improve the security of operator identity verification.

[0003] Because there are many verification scenarios, each scenario is largely the same but there are always subtle differences, and they are heavily coupled with business logic. Every time a new verification scenario is added, it brings heavy costs to development and maintenance. Summary of the Invention

[0004] This application provides a method, apparatus, device, and computer storage medium for shield verification, which is capable of...

[0005] In a first aspect, embodiments of this application provide a shield verification method applied to a front-end device, the method comprising:

[0006] Upon detecting shield insertion, the user's shield information is obtained, including the shield type.

[0007] Determine the shield verification method based on the type of shield;

[0008] Send the user's shield information and shield verification method to the business backend device so as to obtain the signature template and signature time from the business backend device. The signature template includes transaction information and the signature time is the transaction time.

[0009] Receive the signature template and signature time sent by the business backend device;

[0010] A signature request is sent to the shield component server based on the signature template and signature time, so that the shield component server can sign the document and obtain the signature result. The signature request includes transaction information and transaction time.

[0011] In one possible implementation, the method further includes, before obtaining the user's shield information:

[0012] Receive input indicating that the shield verification switch is open;

[0013] In response to input, verify whether the current browser is the target browser;

[0014] If the current browser is the target browser, obtain the user's shield information.

[0015] In one possible implementation embodiment, it further includes:

[0016] If the current browser is not the target browser, prompt the user to switch to another browser.

[0017] In one possible implementation, after sending a signature request to the shield component server based on the signature template and signature time, the method further includes:

[0018] Receive signature result;

[0019] Send the signature result to the business backend so that the business backend device can confirm the signature result and complete the shield verification.

[0020] In one possible implementation, before sending a signature request to the shield component server device based on the signature template and signature time, the method further includes:

[0021] Send transaction information to the shield for display in the shield's display area;

[0022] Receive confirmation commands from users regarding transaction information via the shield's display area.

[0023] Secondly, embodiments of this application provide a shield verification method applied to a business backend device, the method comprising:

[0024] Receive the user's shield information and verification method sent by the front-end device. The verification method is determined based on the user's shield information.

[0025] A signature template and signature time are generated based on the user's shield information and shield verification method. The signature template includes transaction information, and the signature time is the transaction time.

[0026] Send a signature template and signature time to the front-end device so that the front-end device can send a signature request to the shield component server based on the signature template and signature time, and the shield component server will perform the signature.

[0027] Thirdly, embodiments of this application provide a shield verification device applied to a front-end device, the device comprising:

[0028] The acquisition module is used to acquire the user's shield information, including the shield type, when a shield insertion is detected.

[0029] The judgment module is used to determine the shield verification method based on the type of shield.

[0030] The first sending module is used to send the user's shield information and shield verification method to the business backend device, so as to obtain the signature template and signature time from the business backend device. The signature template includes transaction information and the signature time is the transaction time.

[0031] The first receiving module is used to receive the signature template and signature time sent by the business backend device;

[0032] The first sending module is also used to send a signature request to the shield component server according to the signature template and signature time, so that the shield component server can sign and obtain the signature result. The signature request includes transaction information and transaction time.

[0033] In one possible implementation embodiment, it further includes:

[0034] The first receiving module is also used to receive input indicating that the shield verification switch is turned on before obtaining the user's shield information;

[0035] The validation module is used to verify whether the current browser is the target browser in response to input.

[0036] The acquisition module is also used to obtain the user's shield information when the current browser is the target browser.

[0037] In one possible implementation embodiment, it further includes:

[0038] The prompt module is used to prompt the user to switch browsers when the current browser is not the target browser.

[0039] In one possible implementation embodiment, it further includes:

[0040] The first receiving module is also used to receive the signature result after sending a signature request to the shield component server according to the signature template and signature time;

[0041] The first sending module is also used to send the signature result to the business backend so that the business backend device can confirm the signature result and complete the shield verification.

[0042] In one possible implementation embodiment, it further includes:

[0043] The first sending module is also used to send transaction information to the shield before sending a signature request to the shield component server according to the signature template and signature time, so as to display it in the shield's display area;

[0044] The first receiving module is also used to receive confirmation commands from users for transaction information through the display area of ​​the shield.

[0045] Fourthly, embodiments of this application provide a verification device for use in backend business equipment. The device includes:

[0046] The second receiving module is used to receive the user's shield information and shield verification method sent by the front-end device. The shield verification method is determined based on the user's shield information.

[0047] The generation module is used to generate a signature template and signature time based on the user's shield information and shield verification method. The signature template includes transaction information, and the signature time is the transaction time.

[0048] The second sending module is used to send a signature template and signature time to the front-end device, so that the front-end device can send a signature request to the shield component server based on the signature template and time, and the shield component server can perform the signature.

[0049] Fifthly, embodiments of this application provide a shield verification device, the device comprising:

[0050] Processor and memory storing computer program instructions;

[0051] The verification method that implements any one of the above when the processor executes computer program instructions.

[0052] Sixthly, embodiments of this application provide a computer storage medium storing computer program instructions, which, when executed by a processor, implement the shield verification method described above.

[0053] In a seventh aspect, embodiments of this application provide a computer program product, characterized in that, when the instructions in the computer program product are executed by the processor of an electronic device, the electronic device is able to execute any of the above-mentioned verification methods.

[0054] The shield verification method, apparatus, device, and computer storage medium of this application embodiment obtain shield information by inserting a shield, wherein the shield information includes the shield type. The shield verification method is determined based on the shield type. A signature template and signature time are obtained based on the shield information and the shield verification method, wherein the signature template includes transaction information. A signature request is sent to the shield component server based on the signature template and signature time for the shield component server to perform signature and obtain a signature result. This process is generally applicable to fund supervision processes. By determining the shield verification method based on the shield type and obtaining the signature template and signature time based on different shield verification methods, the shield verification process remains unaffected when business scenarios change, and the same set of code can be used. Furthermore, if other business processes that require shield verification are added, there is no need to rewrite the shield verification process; a single set of code can be directly imported, reducing the front-end development workload and maintenance work, avoiding repetitive work, saving R&D costs, and shortening response time. Attached Figure Description

[0055] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0056] Figure 1 This is a schematic flowchart of a shield verification method provided in one embodiment of this application;

[0057] Figure 2This is a schematic flowchart of a shield verification method provided in another embodiment of this application;

[0058] Figure 3 This is a flowchart illustrating a shield verification method provided in another embodiment of this application;

[0059] Figure 4 This is a schematic diagram of the shield verification device provided in another embodiment of this application;

[0060] Figure 5 This is a schematic diagram of the shield verification device provided in another embodiment of this application;

[0061] Figure 6 This is a schematic diagram of the structure of a shield verification device provided in another embodiment of this application. Detailed Implementation

[0062] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.

[0063] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes said element.

[0064] It should be noted that the acquisition, storage, use, and processing of data in this application embodiment all comply with the relevant provisions of national laws and regulations.

[0065] Existing fund monitoring systems involve scenarios requiring manual intervention for large-scale fund flows during numerous transfers. Currently, a high-security verification method is used to enhance the security of operator identity verification. However, due to the large number of verification scenarios, each largely similar yet with subtle differences, and their tight coupling with business logic, adding a new verification scenario incurs significant development and maintenance costs.

[0066] To address the problems of the prior art, embodiments of this application provide a shield verification method, apparatus, device, and computer storage medium. The shield verification method provided in this application embodiment will be described first below.

[0067] Figure 1 A schematic flowchart of a shield verification method provided in one embodiment of this application is shown.

[0068] like Figure 1 As shown in the figure, the shield verification method provided in this application includes the following steps.

[0069] S110. When the front-end device detects the insertion of a shield, it obtains the user's shield information, which includes the type of shield.

[0070] When the front-end device detects the insertion of the shield, it obtains the user's shield information through the connection between the front-end device and the shield. The shield information includes the shield type.

[0071] In some embodiments, the shield information may also include account information and password information entered on the shield.

[0072] In some embodiments, the shield can be a high-strength online security product. Shield information may also include a serial number and a shield identifier. A user can have one or more shields, with each shield corresponding to a unique user. Each shield has a unique serial number and a unique shield identifier, and "multiple" here includes two or more.

[0073] S120: The front-end device determines the shield verification method based on the type of shield.

[0074] The front-end device determines the corresponding shield verification method based on the type of shield.

[0075] In some embodiments, one shield corresponds to one type of shield, and the shield verification method is determined by the shield type. One shield type corresponds to one, but not limited to, one shield verification method.

[0076] In some embodiments, the correspondence between shield type and shield verification method is preset.

[0077] S130: The front-end device sends the user's shield information and shield verification method to the business back-end device.

[0078] The front-end device sends the user's shield information and shield verification method to the business back-end device.

[0079] S140. The business backend device generates a signature template and signature time based on the user's shield information and shield verification method. The signature template includes transaction information, and the signature time is the transaction time.

[0080] The backend device generates a signature template and signature time based on the user's shield information and shield verification method. The signature template can include transaction information, and the signature time can be the transaction time.

[0081] In some embodiments, transaction information may include transaction personnel information, transaction location information, and transaction data information, and the transaction time may be the time when the transaction was initiated, which may be accurate to the second.

[0082] S150: The backend device sends the signature template and signature time to the frontend device.

[0083] The front-end device receives a signature template and signature time sent by the business back-end device. The signature template may include transaction information, and the signature time may be the transaction time.

[0084] S160. The front-end device sends a signature request to the shield component server based on the signature template and signature time, so that the shield component server can sign the signature and obtain the signature result. The signature request includes transaction information and transaction time.

[0085] The front-end device sends a signature request to the shield component server based on the signature template and signature time. The signature request can include transaction information and transaction time from the signature template and signature time. The shield component server receives the signature request and performs the signature.

[0086] This process is universally applicable to fund supervision processes. The verification method is determined based on the type of shield, and the signature template and signature time are obtained based on the different verification methods. In this way, the verification process is not affected when the business scenario changes, and the same set of code can be used. Moreover, if other business processes that require verification are added, there is no need to rewrite the verification process. A single set of code can be directly imported, which reduces the front-end development workload and maintenance work, avoids repetitive work, saves R&D costs, and shortens response time.

[0087] Based on this, in some embodiments, before the above-described S160, the following may also be included:

[0088] Send transaction information to the shield for display in the shield's display area;

[0089] Receive confirmation commands from users regarding transaction information via the shield's display area.

[0090] In some embodiments, transaction information is displayed in the display area of ​​the shield, and the user verifies the transaction information. Once the user knows the transaction content, the user confirms the transaction information in the display area.

[0091] In some embodiments, if the transaction information is correct, the shield receives the user's confirmation command for the transaction information and sends it to the front-end device.

[0092] In some embodiments, if the transaction information is incorrect, the shield receives the user's cancellation instruction for the transaction and sends it to the front end to terminate the shield verification.

[0093] This allows users to verify transaction information, improving security.

[0094] In some embodiments, such as Figure 2 As shown, prior to S110 above, the method may further include S101, S102, and S103:

[0095] S101, The front-end device receives the input that the shield verification switch is open;

[0096] S102. The front-end device responds to the input and verifies whether the current browser is the target browser;

[0097] S103. When the current browser is the target browser, the front-end device obtains the user's shield information.

[0098] Here, the target browser can be Internet Explorer.

[0099] This way, the user's security information can only be obtained when the user operates within a specified browser, thus improving security.

[0100] Based on this, in some embodiments, the method may further include:

[0101] If the current browser is not the target browser, prompt the user to switch to another browser.

[0102] This way, users are prompted to switch browsers when they are not using the target browser, preventing them from mistakenly using other browsers.

[0103] In some embodiments, such as Figure 3 As shown, after S160 above, the method may further include S170 and S180:

[0104] S170, Receive the signature result sent from the backend device of the shield component to the frontend device;

[0105] S180: The business front end sends the signature result to the business back end for the business back end device to confirm the signature result and complete the shield verification.

[0106] Upon receiving the signature result, the front-end device sends the signature result to the business back-end device, which then confirms the signature result to complete the verification process.

[0107] In some embodiments, if the backend signature of the shield component fails, a signature error message is sent to the business backend device to terminate the shield verification process.

[0108] In some embodiments, the shield can be re-inserted for verification after a signature failure.

[0109] In this way, after the backend equipment confirms the signature result and completes the entire verification process, it can continue with other business processes.

[0110] Based on the shield verification method provided in the above embodiments, this application also provides specific implementation methods of the shield verification device. Please refer to the following embodiments.

[0111] First see Figure 4 The shield verification device 300 applied to a front-end device provided in this application embodiment includes:

[0112] The acquisition module 310 is used to acquire the user's shield information when the shield insertion is detected, including the shield type;

[0113] Module 320 is used to determine the shield verification method based on the type of shield.

[0114] The first sending module 330 is used to send the user's shield information and shield verification method to the business backend device, so as to obtain the signature template and signature time from the business backend device. The signature template includes transaction information and the signature time is the transaction time.

[0115] The first receiving module 340 is used to receive the signature template and signature time sent by the business backend device;

[0116] The first sending module 330 is also used to send a signature request to the shield component server according to the signature template and signature time, so that the shield component server can sign and obtain the signature result. The signature request includes transaction information and transaction time.

[0117] Accordingly, in some embodiments, the device 300 further includes:

[0118] The first receiving module 340 is also used to receive input indicating that the shield verification switch is turned on before acquiring the user's shield information;

[0119] The validation module is used to verify whether the current browser is the target browser in response to input.

[0120] The acquisition module 310 is also used to acquire the user's shield information when the current browser is the target browser.

[0121] Accordingly, in some embodiments, the device 300 further includes:

[0122] The prompt module is used to prompt the user to switch browsers when the current browser is not the target browser.

[0123] Accordingly, in some embodiments, the device 300 further includes:

[0124] The first receiving module 340 is also used to receive the signature result after sending a signature request to the shield component server according to the signature template and the signature time;

[0125] The first sending module 330 is also used to send the signature result to the business backend so that the business backend device can confirm the signature result and complete the shield verification.

[0126] Accordingly, in some embodiments, the device 300 further includes:

[0127] The first sending module 330 is also used to send transaction information to the shield before sending a signature request to the shield component server according to the signature template and signature time, so as to display it in the shield's display area;

[0128] The first receiving module 340 is also used to receive confirmation commands from users for transaction information through the display area of ​​the shield.

[0129] See Figure 5 The verification device 400 for business backend equipment provided in this application embodiment includes:

[0130] The second receiving module 410 is used to receive the user's shield information and shield verification method sent by the front-end device. The shield verification method is determined based on the user's shield information.

[0131] The generation module 420 is used to generate a signature template and signature time based on the user's shield information and shield verification method. The signature template includes transaction information and the signature time is the transaction time.

[0132] The second sending module 430 is used to send a signature template and a signature time to the front-end device, so that the front-end device can send a signature request to the shield component server based on the signature template and time, and the shield component server can perform the signature.

[0133] The various modules of the shield verification device provided in this application embodiment can achieve Figure 1 and Figure 2 It provides the functionality for each step of the shield verification method and achieves the corresponding technical effects. For the sake of brevity, it will not be elaborated here.

[0134] Figure 6A schematic diagram of the hardware structure of the shield verification device provided in an embodiment of this application is shown.

[0135] The shield verification device may include a processor 601 and a memory 602 storing computer program instructions.

[0136] Specifically, the processor 601 may include a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0137] Memory 602 may include mass storage for data or instructions. For example, and not limitingly, memory 602 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 602 may include removable or non-removable (or fixed) media. Where appropriate, memory 602 may be internal or external to the integrated gateway disaster recovery device. In a particular embodiment, memory 602 is non-volatile solid-state memory.

[0138] Memory may include read-only memory (ROM), random access memory (RAM), disk storage media devices, optical storage media devices, flash memory devices, and electrical, optical, or other physical / tangible memory storage devices. Therefore, typically, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to one aspect of this disclosure.

[0139] The processor 601 implements any of the shield verification methods described in the above embodiments by reading and executing computer program instructions stored in the memory 602.

[0140] In one example, the verification device may also include a communication interface 603 and a bus 610. For example, Figure 6 As shown, the processor 601, memory 602, and communication interface 603 are connected through bus 610 and complete communication with each other.

[0141] The communication interface 603 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application.

[0142] Bus 610 includes hardware, software, or both, that couples components of the verification device together. For example, and not limited to, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Extended Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Linear Predictive Coding (LPC) bus, a memory bus, a MicroChannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (Peripheral Component Interconnect-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VESA Local Bus, VLB) bus, or other suitable buses, or a combination of two or more of these. Where appropriate, bus 610 may include one or more buses. Although specific buses are described and illustrated in the embodiments of this application, this application considers any suitable bus or interconnection.

[0143] This shield verification device can execute the shield verification method in this application embodiment based on the user's shield information, thereby achieving a combination of... Figure 1 and Figure 2 The method for verifying shields is described.

[0144] Furthermore, in conjunction with the shield verification methods in the above embodiments, this application embodiment can provide a computer storage medium for implementation. The computer storage medium stores computer program instructions; when these computer program instructions are executed by a processor, they implement any of the shield verification methods in the above embodiments.

[0145] This application also provides a computer program product, wherein the instructions in the computer program product, when executed by the processor of an electronic device, cause the electronic device to perform various processes implementing any of the above-described verification method embodiments.

[0146] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.

[0147] The functional blocks shown in the above-described block diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, read-only memory (ROM), flash memory, erasable read-only memory (EROM), floppy disks, compact disc read-only memory (CD-ROM), optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0148] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0149] The aspects of this disclosure have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, 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 apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by special-purpose hardware performing the specified functions or actions, or can be implemented by a combination of special-purpose hardware and computer instructions.

[0150] The above are merely specific embodiments of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.

Claims

1. A shield verification method, applied to a front-end device, characterized in that, include: Upon detecting the insertion of a shield, the user's shield information is obtained, including the shield type; the shield information also includes a serial number and a shield identifier, with each shield having a unique serial number and shield identifier; The shield verification method is determined based on the type of shield, with one shield type corresponding to one, but not limited to, verification method; the correspondence between shield types and verification methods is preset. The user shield information and the shield verification method are sent to the business backend device to obtain the signature template and signature time from the business backend device. The signature template includes transaction information, and the signature time is the transaction time. The signature template and signature time are generated by the business backend device based on the user shield information and the shield verification method sent by the frontend device. Receive the signature template and signature time sent by the business backend device; A signature request is sent to the shield component server according to the signature template and the signature time, so that the shield component server can perform the signature and obtain the signature result. The signature request includes the transaction information and the transaction time. Before obtaining the user's shield information, the method further includes: Receive input indicating that the shield verification switch is open; In response to the input, verify whether the current browser is the target browser; If the current browser is the target browser, obtain the user's shield information.

2. The shield verification method according to claim 1, characterized in that, Also includes: If the current browser is not the target browser, prompt the user to switch to another browser.

3. The shield verification method according to claim 1, characterized in that, After sending a signature request to the shield component server based on the signature template and the signature time, the method further includes: Receive the signature result; The signature result is sent to the business backend so that the business backend device can confirm the signature result and complete the verification.

4. The shield verification method according to claim 1, characterized in that, Before sending a signature request to the shield component server device based on the signature template and the signature time, the method further includes: The transaction information is sent to the shield for display in the shield's display area; Receive confirmation commands from users regarding the transaction information via the display area of ​​the shield.

5. A shield verification method, applied to business backend equipment, characterized in that, include: Receive user shield information and shield verification method sent by the front-end device, wherein the shield information includes the shield type and the shield verification method is determined based on the user's shield type; A signature template and signature time are generated based on the user's shield information and the shield verification method. The signature template includes transaction information, and the signature time is the transaction time. The signature template and the signature time are sent to the front-end device so that the front-end device can send a signature request to the shield component server based on the signature template and the time, and the shield component server can perform the signature.

6. A shield verification device, applied to a front-end device, characterized in that, The device includes: The acquisition module is used to acquire the user's shield information when the shield insertion is detected, the shield information including the shield type; The judgment module is used to determine the shield verification method based on the shield type. One shield type corresponds to one, but is not limited to, one, shield verification method. The correspondence between shield type and shield verification method is preset. The shield information also includes a serial number and a shield identifier. Each shield has a unique serial number and shield identifier. The first sending module is used to send the user's shield information and the shield verification method to the business backend device, so as to obtain a signature template and signature time from the business backend device. The signature template includes transaction information, and the signature time is the transaction time. The signature template and signature time are generated by the business backend device based on the user's shield information and the shield verification method sent by the frontend device. The first receiving module is used to receive the signature template and the signature time sent by the business backend device; The first sending module is further configured to send a signature request to the shield component server according to the signature template and the signature time, so that the shield component server can perform the signature to obtain a signature result, wherein the signature request includes the transaction information and the transaction time; Before obtaining the user's shield information, it also includes: Receive input indicating that the shield verification switch is open; In response to the input, verify whether the current browser is the target browser; If the current browser is the target browser, obtain the user's shield information.

7. The shield verification device according to claim 6, characterized in that, Also includes: The first receiving module is also used to receive input indicating that the shield verification switch is turned on before obtaining the user's shield information; The verification module is used to verify whether the current browser is the target browser in response to the input; The acquisition module is also used to acquire the user's shield information when the current browser is the target browser.

8. The shield verification device according to claim 7, characterized in that, Also includes: The prompt module is used to prompt the user to switch browsers when the current browser is not the target browser.

9. The shield verification device according to claim 6, characterized in that, Also includes: The first receiving module is further configured to receive the signature result after sending a signature request to the shield component server according to the signature template and the signature time; The first sending module is further configured to send the signature result to the service backend so that the service backend device can confirm the signature result and complete the verification.

10. The shield verification device according to claim 6, characterized in that, Also includes: The first sending module is further configured to send the transaction information to the shield before sending a signature request to the shield component server according to the signature template and the signature time, so as to display it in the display area of ​​the shield; The first receiving module is also configured to receive a confirmation command from the user for the transaction information through the display area of ​​the shield.

11. A shield verification device, applied to backend business equipment, characterized in that, include: The second receiving module is used to receive the user's shield information and shield verification method sent by the front-end device. The shield information includes the shield type, and the shield verification method is determined based on the user's shield type. The generation module is used to generate a signature template and a signature time based on the user's shield information and the shield verification method. The signature template includes transaction information, and the signature time is the transaction time. The second sending module is used to send the signature template and the signature time to the front-end device, so that the front-end device can send a signature request to the shield component server based on the signature template and the time, and the shield component server can perform the signature.

12. A shield verification device, characterized in that, The device includes: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, it implements the shield verification method as described in any one of claims 1-5.

13. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions, which, when executed by a processor, implement the shield verification method as described in any one of claims 1-5.

14. A computer program product, characterized in that, When the instructions in the computer program product are executed by the processor of the electronic device, the electronic device is able to perform the shield verification method as described in any one of claims 1-5.

Images