Multi-scene two-dimensional code authentication method and device, electronic equipment and storage medium

Abstract

The invention provides a multi-scene two-dimensional code authentication method and device, electronic equipment and a storage medium, and the method comprises the steps that a user sends a registration request to a first terminal, and the registration request comprises user information; the first terminal generates a decentralized identity (DID) based on the user information; the user applies for authorization certificates from a plurality of scene authorization parties through the first terminal; the scene authorization party performs authorization certificate auditing on the user according to the DID; and after the verification is passed, the first terminal generates a fused two-dimensional code, and the fused two-dimensional code is used for authentication of a plurality of scenes.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and in particular to a multi-scenario QR code authentication method, device, electronic device, and storage medium. Background Technology

[0002] Most existing urban public services use independent QR code systems, which are incompatible across different scenarios. For example, users need to generate a dynamic ride code through a dedicated app to take the bus or subway, use their ID card or a special library card to borrow books from the library, and generate a reservation code through a dedicated mini-program to visit parks and scenic spots. This leads to various problems, such as users having to switch between multiple media, making the process cumbersome; each scenario's user system is independent, and data cannot be shared across scenarios; and most systems in each scenario use a centralized approach to store user data, increasing the risk of privacy data leaks. Summary of the Invention

[0003] This disclosure provides a multi-scenario QR code authentication method, device, electronic device, and storage medium to at least solve the above-mentioned technical problems existing in the prior art.

[0004] According to a first aspect of this disclosure, a multi-scenario QR code authentication method is provided, wherein the method includes:

[0005] The user sends a registration request to the first terminal, the registration request including user information;

[0006] The first terminal generates a decentralized identity (DID) based on the user information;

[0007] The user applies for authorization credentials from multiple scenario-authorizing parties through the first terminal;

[0008] The authenticator in the scenario verifies the user's authorization credentials based on the DID;

[0009] After the review is approved, the first terminal generates a fusion QR code, which is used for authentication in multiple scenarios.

[0010] In one possible implementation, the scenario licensor is provided with a second terminal;

[0011] The authenticator in the scenario verifies the user's authorization credentials based on the DID, including:

[0012] The user information in the DID is compared with the user information in the second terminal;

[0013] If the user information in the DID is the same as the user information in the second terminal, the review is approved;

[0014] If the user information in the DID is different from the user information in the second terminal, the review will fail.

[0015] In one possible implementation, the method further includes:

[0016] After scanning the fused QR code, the scanning terminal in each scenario parses the fused QR code and obtains the DID, the first hash value, and the first signature value from the fused QR code;

[0017] The scanning terminal submits the DID, the first hash value, the first signature value, and the authorization signature information of the scene licensor to the blockchain to verify the fused QR code;

[0018] The blockchain will return the verification result to the scanning terminal.

[0019] In one possible implementation, the method further includes:

[0020] Based on the verification result, the scanning terminal submits a transaction request to the blockchain;

[0021] The blockchain processes the transaction according to the transaction request and returns the transaction result;

[0022] The scanning terminal determines whether the first terminal has approved the transaction based on the transaction result.

[0023] According to a second aspect of this disclosure, a multi-scenario QR code authentication device is provided, wherein the device includes:

[0024] The sending unit is configured to allow a user to send a registration request to a first terminal, wherein the registration request includes user information;

[0025] The first generation unit is configured to generate a decentralized identity (DID) based on the user information by the first terminal.

[0026] The application unit is configured so that the user can apply for authorization credentials from multiple scenario licensors through the first terminal;

[0027] The review unit is configured to allow the scenario licensor to review the user's authorization credentials based on the DID.

[0028] The second generation unit is configured to generate a fusion QR code on the first terminal after the review is approved. The fusion QR code is used for authentication in multiple scenarios.

[0029] In one possible implementation, the scenario licensor is provided with a second terminal;

[0030] The audit unit includes:

[0031] The comparison unit is configured to compare the user information in the DID with the user information in the second terminal;

[0032] If the user information in the DID is the same as the user information in the second terminal, the review is approved;

[0033] If the user information in the DID is different from the user information in the second terminal, the review will fail.

[0034] In one possible embodiment, the device further includes:

[0035] The parsing unit is configured to parse the fused QR code after scanning it, and obtain the DID, the first hash value and the first signature value from the fused QR code.

[0036] The verification unit is configured such that the scanning terminal submits the DID, the first hash value, the first signature value, and the authorization signature information of the scene licensor to the blockchain to verify the fused QR code;

[0037] The return unit is configured so that the blockchain returns the verification result to the scanning terminal.

[0038] In one possible embodiment, the device further includes:

[0039] The submission unit is configured to submit a transaction request to the blockchain based on the verification result;

[0040] A transaction unit is configured to enable the blockchain to process transactions based on the transaction request and return the transaction result;

[0041] The determining unit is configured to determine whether the first terminal has approved the transaction based on the transaction result.

[0042] According to a third aspect of this disclosure, an electronic device is provided, comprising:

[0043] At least one processor; and

[0044] A memory communicatively connected to the at least one processor; wherein,

[0045] The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the methods described in this disclosure.

[0046] According to a fourth aspect of this disclosure, a non-transitory computer-readable storage medium is provided storing computer instructions for causing the computer to perform the methods described in this disclosure.

[0047] The multi-scenario QR code authentication method, device, electronic device, and storage medium disclosed herein first generate a decentralized identity (DID) for the user, then map the DID to multiple scenarios, and after obtaining authorization from the scenario authorizing party, generate a fused QR code. The fused QR code enables access to multiple scenarios, eliminates the need for media switching, and can greatly reduce the complexity of use for users.

[0048] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0049] The above and other objects, features, and advantages of this disclosure will become readily apparent from the following detailed description of exemplary embodiments, taken in conjunction with the accompanying drawings. Several embodiments of this disclosure are illustrated in the drawings by way of example and not limitation, in which:

[0050] In the accompanying drawings, the same or corresponding reference numerals indicate the same or corresponding parts.

[0051] Figure 1 A flowchart of a multi-scenario QR code authentication method provided in this disclosure embodiment;

[0052] Figure 2 A flowchart illustrating the QR code authentication process for the public transportation system;

[0053] Figure 3 This is a schematic diagram of the structure of the multi-scenario QR code authentication device provided in the embodiments of this disclosure;

[0054] Figure 4 A schematic diagram of the composition structure of an electronic device according to an embodiment of the present disclosure is shown. Detailed Implementation

[0055] To make the objectives, features, and advantages of this disclosure more apparent and understandable, the technical solutions in the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this disclosure, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this disclosure without creative effort are within the scope of protection of this disclosure.

[0056] This disclosure provides a multi-scenario QR code authentication method. Figure 1 A flowchart of the multi-scenario QR code authentication method provided in the embodiments of this disclosure is shown below. Figure 1 As shown, the method includes:

[0057] Step 101: The user sends a registration request to the first terminal, which includes user information.

[0058] The first terminal can be an application (APP) or a mini-program.

[0059] When a user sends a registration request to the first terminal, the user information can be sent to the first terminal so that the first terminal can assign an account to the user based on the user information and make the account correspond to the user information, thus ensuring the uniqueness of the account.

[0060] User information may include the user's mobile phone number, ID card number, and other information.

[0061] Step 102: The first terminal generates a decentralized identity (DID) based on user information.

[0062] The first terminal generates a decentralized identity (DID) based on user information. A DID is a decentralized identifier used to uniquely identify a user's blockchain digital identity.

[0063] The DID is encoded as follows:

[0064] DID="did:city:"+SM3(phone_hash+idcard_hash);

[0065] Among them, did:city: indicates which city the QR code is applied to; phone_hash represents the hash value of the mobile phone number; idcard_hash represents the hash value of the ID card number; SM3 indicates that the mobile phone number and ID card number are encrypted.

[0066] Step 103: The user applies for authorization credentials from multiple scenario licensors through the first terminal.

[0067] After obtaining the DID, users need to apply for authorization from the scene licensor where the QR code can be used in order to activate the QR code. Only after the scene licensor agrees to the authorization can the QR code be used in that scene.

[0068] Step 104: The scenario licensor verifies the user's authorization credentials based on the DID.

[0069] In one embodiment, the scene licensor has a second terminal;

[0070] The scene licensor verifies the user's authorization credentials based on the DID, including:

[0071] Compare the user information in the DID with the user information in the second terminal;

[0072] If the user information in the DID is the same as the user information in the second terminal, the review is approved;

[0073] If the user information in the DID is different from the user information in the second terminal, the review will fail.

[0074] Specifically, the second terminal of the scenario licensor contains an existing user system. This existing user system contains user information from when the user originally registered for the account on the second terminal. For example, in the public transportation system, if the user originally registered for the account on the second terminal using a mobile phone number, the mobile phone number in the DID can be compared with the mobile phone number in the second terminal. If the mobile phone number in the DID exists in the existing user system of the second terminal, it means that the user's information exists in the existing user system. The public transportation system licensor can then grant authorization, and the subsequently generated integrated QR code can be applied to the public transportation system.

[0075] In this disclosure, the scenario licensor establishes a one-to-one mapping between the existing user system and the DID, achieving multi-system identity association through the DID mapping table without altering the architecture of the original user system. Simultaneously, the scenario licensor's business information and processing procedures remain within the original user system, reducing conflicts of interest with stakeholders in the original user system. The DID identifier is visible across the entire chain, while the true identity information is only visible to the original user system, resolving the issue of minimizing the collection and protection of sensitive data.

[0076] Step 105: After the review is approved, the first terminal generates a fusion QR code, which is used for authentication in multiple scenarios.

[0077] The first terminal generates a merged QR code in a unified format based on the authorized scenarios. For example, taking multiple scenarios including buses, libraries, and parks as examples, the procedure for merging QR codes is as follows:

[0078]

[0079] The aforementioned integrated QR code includes information such as the cities where it can be used. When used as a public transportation QR code, it is a dynamic code with a refresh interval of 30 seconds. When used as a library access QR code, it is a static code with a borrowing level of 2. When used as a park access QR code, it is an annual pass type with an expiration date of a specific year, month, and day. The integrated QR code also includes a first hash value (tx_hash) and a first signature value (SM2 signature).

[0080] In one embodiment, the method further includes: after scanning the fused QR code, the scanning terminal in each scenario parses the fused QR code and obtains the DID, the first hash value and the first signature value from the fused QR code;

[0081] The scanning terminal submits the DID, first hash value, first signature value, and authorization signature information of the scene licensor to the blockchain to verify the fused QR code;

[0082] The blockchain will return the verification results to the scanning terminal.

[0083] In one embodiment, the method further includes: based on the verification result, the scanning terminal submits a transaction request to the blockchain;

[0084] The blockchain processes transactions based on transaction requests and returns the transaction results.

[0085] The scanning terminal determines whether the first terminal has approved the transaction based on the transaction result.

[0086] Specifically, each scenario has a scanning terminal, such as a turnstile.

[0087] The following is a detailed step-by-step explanation using a public transportation system as an example:

[0088] Figure 2 A flowchart illustrating the QR code authentication process for the public transportation system.

[0089] like Figure 2 As shown, when a user presents a fusion QR code, the bus gate receives the fusion QR code, parses it, and extracts the DID, the first hash value tx_hash, and the first signature value SM2 signature value from the fusion QR code.

[0090] Next, the bus gate submits the DID, tx_hash, SM2 signature value, and the authorization signature information of the scenario licensor to the blockchain for verification. The authorization signature information of the scenario licensor is generated after the authorization certificate is approved, and the authorization signature information submitted here is the authorization signature information of the bus system.

[0091] Next, the blockchain verifies the SM2 signature value and the authorization signature information of the scene licensor to determine the validity of the merged QR code. The SM2 signature value is the signature created when data is uploaded to the blockchain; it verifies whether the data was sent by the data provider. For example, in this case, it ensures that the QR code information is provided by the user's primary terminal and not copied by someone else, thus enabling scanning verification. The authorization signature information of the scene licensor confirms whether the user has obtained authorization credentials from the scene licensor. If both the SM2 signature value and the authorization signature information of the scene licensor match, the merged QR code is valid.

[0092] Next, the transaction information is queried using `tx_hash`. The smart contract in the blockchain then verifies the permissions, DID information, and QR code validity for that scenario based on the transaction information. Verifying permissions means checking if the QR code is authorized for that scenario. For example, if the public transportation system doesn't have the user's account, then the user's QR code won't be authorized to pass through the bus gate. Verifying the DID information is to check if the user information on the QR code corresponds to the user information in the public transportation system's existing user database. Verifying the QR code's validity is necessary because public transportation QR codes are dynamic and expire after a certain period; this verification process checks whether the QR code has expired.

[0093] After verifying the above information, the verification result will be returned to the bus gate.

[0094] If the verification fails, the user needs to confirm which of the aforementioned information is problematic. For example, if the dynamic code has expired, it needs to be updated and re-verified. If the verification passes, the bus gate can then process the payment.

[0095] The bus gate determines the fare deduction rules and submits a deduction request to the blockchain; the smart contract deducts the fare and updates the user's balance; the smart contract returns the deduction result and the updated user balance; the bus gate determines whether to allow passage based on the deduction result. For example, if the deduction is successful, passage is allowed; if the user's balance is insufficient, the deduction fails, and passage is not allowed.

[0096] In this disclosure, a decentralized identity (DID) for the user is first generated, and then the DID is mapped to multiple scenarios. After obtaining authorization from the scenario licensor, a fusion QR code is generated. The fusion QR code enables access to multiple scenarios, eliminating the need for media switching and greatly reducing the complexity for users.

[0097] This disclosure also provides a multi-scenario QR code authentication device. Figure 3 This is a schematic diagram of the structure of the multi-scenario QR code authentication device provided in the embodiments of this disclosure, as shown below. Figure 3 As shown, the device includes:

[0098] Sending unit 301 is configured to send a registration request from a user to a first terminal, the registration request including user information;

[0099] The first generation unit 302 is configured to generate a decentralized identity (DID) based on user information by the first terminal;

[0100] Application unit 303 is configured for users to apply for authorization credentials from multiple scenario licensors through a first terminal;

[0101] Audit unit 304 is configured to allow the scenario licensor to audit the user's authorization credentials based on the DID.

[0102] The second generation unit 305 is configured to generate a fusion QR code on the first terminal after the review is approved. The fusion QR code is used for authentication in multiple scenarios.

[0103] In one embodiment, the scene licensor has a second terminal;

[0104] Audit Unit 304 includes:

[0105] The comparison unit is configured to compare the user information in the DID with the user information in the second terminal;

[0106] If the user information in the DID is the same as the user information in the second terminal, the review is approved;

[0107] If the user information in the DID is different from the user information in the second terminal, the review will fail.

[0108] In one embodiment, the apparatus further includes:

[0109] The parsing unit 306 is configured to parse the fused QR code after scanning it, and obtain the DID, the first hash value and the first signature value from the fused QR code.

[0110] Verification unit 307 is configured to have the scanning terminal submit the DID, first hash value, first signature value and authorization signature information of the scene licensor to the blockchain to verify the fused QR code;

[0111] Return unit 308 is configured to return the verification result to the scanning terminal via blockchain.

[0112] In one embodiment, the apparatus further includes:

[0113] Submission unit 309 is configured to scan the terminal to submit a transaction request to the blockchain based on the verification result;

[0114] Transaction unit 310 is configured to enable the blockchain to process transactions based on transaction requests and return transaction results;

[0115] The determining unit 311 is configured to scan the terminal to determine whether the first terminal has passed the transaction based on the transaction result.

[0116] It should be noted here that the above description of the embodiments for multi-scenario QR code authentication devices is consistent with the foregoing Figure 1 and Figure 2 The method embodiments shown are described similarly and have the same characteristics as described above. Figure 1 and Figure 2The beneficial effects of the methods illustrated are similar and will not be described in detail here. For technical details not disclosed in the multi-scenario QR code authentication device embodiments of this disclosure, please refer to the foregoing of this disclosure. Figure 1 and Figure 2 The method embodiments shown are for understanding purposes only and will not be described in detail here for the sake of brevity.

[0117] According to embodiments of this disclosure, this disclosure also provides an electronic device and a readable storage medium.

[0118] Figure 4 A schematic block diagram of an example electronic device 400 that can be used to implement embodiments of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the present disclosure described and / or claimed herein.

[0119] like Figure 4 As shown, device 400 includes a computing unit 401, which can perform various appropriate actions and processes based on a computer program stored in read-only memory (ROM) 402 or a computer program loaded from storage unit 408 into random access memory (RAM) 403. RAM 403 may also store various programs and data required for the operation of device 400. The computing unit 401, ROM 402, and RAM 403 are interconnected via bus 404. Input / output (I / O) interface 405 is also connected to bus 404.

[0120] Multiple components in device 400 are connected to I / O interface 405, including: input unit 406, such as keyboard, mouse, etc.; output unit 407, such as various types of monitors, speakers, etc.; storage unit 408, such as disk, optical disk, etc.; and communication unit 409, such as network card, modem, wireless transceiver, etc. Communication unit 409 allows device 400 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0121] The computing unit 401 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 401 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 401 performs the various methods and processes described above, such as the multi-scene QR code authentication method. For example, in some embodiments, the multi-scene QR code authentication method can be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 408. In some embodiments, part or all of the computer program can be loaded and / or installed on device 400 via ROM 402 and / or communication unit 409. When the computer program is loaded into RAM 403 and executed by the computing unit 401, one or more steps of the multi-scene QR code authentication method described above can be performed. Alternatively, in other embodiments, the computing unit 401 can be configured to perform the multi-scene QR code authentication method by any other suitable means (e.g., by means of firmware).

[0122] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip (SoCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0123] The program code used to implement the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0124] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0125] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0126] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with embodiments of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0127] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact via communication networks. Client-server relationships are created by computer programs running on the respective computers and having a client-server relationship with each other. Servers can be cloud servers, servers in distributed systems, or servers incorporating blockchain technology.

[0128] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this disclosure can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this disclosure can be achieved, and this is not limited herein.

[0129] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this disclosure, "a plurality of" means two or more, unless otherwise explicitly specified.

[0130] The above description is merely a specific embodiment of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

1. A multi-scenario QR code authentication method, characterized in that, The method includes: The user sends a registration request to the first terminal, the registration request including user information; The first terminal generates a decentralized identity (DID) based on the user information; The user applies for authorization credentials from multiple scenario-authorizing parties through the first terminal; The authenticator in the scenario verifies the user's authorization credentials based on the DID; After the review is approved, the first terminal generates a fusion QR code, which is used for authentication in multiple scenarios.

2. The method according to claim 1, characterized in that, The licensor of the scenario has a second terminal set up; The authenticator in the scenario verifies the user's authorization credentials based on the DID, including: The user information in the DID is compared with the user information in the second terminal; If the user information in the DID is the same as the user information in the second terminal, the review is approved; If the user information in the DID is different from the user information in the second terminal, the review will fail.

3. The method according to claim 1, characterized in that, The method further includes: After scanning the fused QR code, the scanning terminal in each scenario parses the fused QR code and obtains the DID, the first hash value, and the first signature value from the fused QR code; The scanning terminal submits the DID, the first hash value, the first signature value, and the authorization signature information of the scene licensor to the blockchain to verify the fused QR code; The blockchain will return the verification result to the scanning terminal.

4. The method according to claim 3, characterized in that, The method further includes: Based on the verification result, the scanning terminal submits a transaction request to the blockchain; The blockchain processes the transaction according to the transaction request and returns the transaction result; The scanning terminal determines whether the first terminal has approved the transaction based on the transaction result.

5. A multi-scenario QR code authentication device, characterized in that, The device includes: The sending unit is configured to allow a user to send a registration request to a first terminal, wherein the registration request includes user information; The first generation unit is configured to generate a decentralized identity (DID) based on the user information by the first terminal. The application unit is configured so that the user can apply for authorization credentials from multiple scenario licensors through the first terminal; The review unit is configured to allow the scenario licensor to review the user's authorization credentials based on the DID. The second generation unit is configured to generate a fusion QR code on the first terminal after the review is approved. The fusion QR code is used for authentication in multiple scenarios.

6. The apparatus according to claim 5, characterized in that, The licensor of the scenario has a second terminal set up; The audit unit includes: The comparison unit is configured to compare the user information in the DID with the user information in the second terminal; If the user information in the DID is the same as the user information in the second terminal, the review is approved; If the user information in the DID is different from the user information in the second terminal, the review will fail.

7. The apparatus according to claim 5, characterized in that, The device further includes: The parsing unit is configured to parse the fused QR code after scanning it, and obtain the DID, the first hash value and the first signature value from the fused QR code. The verification unit is configured such that the scanning terminal submits the DID, the first hash value, the first signature value, and the authorization signature information of the scene licensor to the blockchain to verify the fused QR code; The return unit is configured so that the blockchain returns the verification result to the scanning terminal.

8. The apparatus according to claim 7, characterized in that, The device further includes: The submission unit is configured to submit a transaction request to the blockchain based on the verification result; A transaction unit is configured to enable the blockchain to process transactions based on the transaction request and return the transaction result; The determining unit is configured to determine whether the first terminal has approved the transaction based on the transaction result.

9. An electronic device, characterized in that, include: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-4.

10. A non-transitory computer-readable storage medium storing computer instructions, characterized in that, The computer instructions are used to cause the computer to perform the method according to any one of claims 1-4.

Images