QR code processing method and device, storage medium and electronic device

Abstract

The present invention discloses a method and device for processing a QR code, a storage medium, and an electronic device. The method comprises: obtaining first QR code information sent by a first application, wherein the first QR code information records a first business scenario identifier for representing a first business scenario corresponding to when the first application scans a target QR code, sending the first QR code information to the second application background device based on the callback address of the second application background device corresponding to the second application identifier, and returning the response data sent by the second application background device to the first application, thereby enabling data intercommunication between different applications and ensuring the privacy and security of data intercommunication. The present invention solves the technical problem of data non-intercommunication between different applications and poor user experience.

Description

Technical Field

[0001] The present invention relates to the field of computers, and in particular to a two-dimensional code processing method and device, a storage medium, and an electronic device. Background Art

[0002] In the current related technologies, when scanning a QR code through an application in the same scenario, if the user is in different regions, or uses different applications to scan, it is difficult to complete the parsing of the same QR code. The QR codes generated by different applications are difficult to recognize each other, resulting in the user needing to repeatedly register different applications when using the QR code in different regions or different scenarios, resulting in low privacy security of user personal information and data, and inconvenience for users.

[0003] To address the above-mentioned problems, no effective solutions have been proposed so far. Summary of the Invention

[0004] The embodiments of the present invention provide a method and device for processing a QR code, a storage medium, and an electronic device, so as to at least solve the technical problems of data non-intercommunication between different applications and poor user experience.

[0005] According to one aspect of an embodiment of the present invention, a method for processing a QR code is provided, including: obtaining first QR code information sent by a first application, wherein the first QR code information includes: a first user identifier, a second application identifier and a first business scenario identifier, the first user identifier and the second application identifier are identifiers obtained by the first application scanning a target QR code, and the first business scenario identifier is used to represent the first business scenario corresponding to the first application scanning the target QR code; obtaining a callback address of a second application background device corresponding to the second application identifier, and sending the first user identifier and the first business scenario identifier to the second application background device according to the callback address; obtaining first response data sent by the second application background device, wherein the first response data is response data of the first user identifier in the first business scenario represented by the first business scenario identifier; and sending the first response data to the first application.

[0006] Optionally, before obtaining the first QR code information sent by the first application, the method also includes: obtaining an application registration request sent by the access party, wherein the application registration request carries the callback address of the second application background device, and the access party is the second application background device, or the second application corresponding to the second application background device; in response to the application registration request, allocating the second application identifier to the access party, and recording the callback address of the second application background device carried in the application registration request; and sending the second application identifier to the access party.

[0007] Optionally, after sending the second application identifier to the access party, the method further includes: when the access party is the second application background device, configuring one or more business scenario identifiers on the second application background device, wherein the one or more business scenario identifiers include the first business scenario identifier; generating the target QR code on the second application background device based on the first user identifier and the second application identifier.

[0008] Optionally, after sending the second application identifier to the access party, the method further includes: if the access party is the second application background device, configuring one or more business scenario identifiers on the second application background device, wherein the one or more business scenario identifiers include the first business scenario identifier; sending the second application identifier to the second application on the second application background device, and generating the target QR code on the second application based on the first user identifier and the second application identifier; or if the access party is the second application background device, sending the second application identifier to the second application on the second application background device, generating the target QR code on the second application based on the first user identifier and the second application identifier, and configuring one or more business scenario identifiers on the second application, wherein the one or more business scenario identifiers include the first business scenario identifier.

[0009] Optionally, after sending the second application identifier to the access party, the method further includes: when the access party is the second application, configuring one or more business scenario identifiers on the second application, wherein the one or more business scenario identifiers include the first business scenario identifier; generating the target QR code on the second application based on the first user identifier and the second application identifier.

[0010] Optionally, after sending the second application identifier to the access party, the method also includes: when the access party is the second application, configuring one or more business scenario identifiers on the second application, wherein the one or more business scenario identifiers include the first business scenario identifier; sending the second application identifier to the second application background device on the second application, and generating the target QR code on the second application background device based on the first user identifier and the second application identifier; or when the access party is the second application, sending the second application identifier to the second application background device on the second application, generating the target QR code on the second application background device based on the first user identifier and the second application identifier, and configuring one or more business scenario identifiers on the second application background device, wherein the one or more business scenario identifiers include the first business scenario identifier.

[0011] Optionally, after obtaining the application registration request sent by the access party, the method further includes: allocating a target encryption key and a target decryption key to the access party; and sending the target encryption key and the target decryption key to the access party.

[0012] Optionally, before obtaining the first QR code information sent by the first application, the method also includes: scanning the target QR code on the first application to obtain the first user identifier and the second application identifier, wherein, when the target QR code is scanned on the first application, the business scenario where the first application is located is the first business scenario; obtaining the first business scenario identifier of the first business scenario on the first application; and determining the first QR code information on the first application to include the first user identifier, the second application identifier and the first business scenario identifier.

[0013] Optionally, the method also includes: obtaining second QR code information sent by the third application, wherein the second QR code information includes: a first user identifier, a second application identifier, and a second business scenario identifier, the first user identifier and the second application identifier are identifiers obtained by the third application scanning the target QR code, and the second business scenario identifier is used to represent the second business scenario corresponding to the third application scanning the target QR code; obtaining the callback address of the second application background device corresponding to the second application identifier, and sending the first user identifier and the second business scenario identifier to the second application background device according to the callback address; obtaining second response data sent by the second application background device, wherein the second response data is the response data of the first user identifier in the second business scenario represented by the second business scenario identifier; and sending the second response data to the third application.

[0014] According to another aspect of an embodiment of the present invention, a QR code processing device is also provided, including: a first acquisition module, used to obtain first QR code information sent by a first application, wherein the first QR code information includes: a first user identifier, a second application identifier and a first business scenario identifier, the first user identifier and the second application identifier are identifiers obtained by the first application scanning the target QR code, and the first business scenario identifier is used to represent the first business scenario corresponding to the first application scanning the target QR code; a processing module, used to obtain the callback address of the second application background device corresponding to the second application identifier, and send the first user identifier and the first business scenario identifier to the second application background device according to the callback address; a second acquisition module, used to obtain first response data sent by the second application background device, wherein the first response data is the response data of the first user identifier in the first business scenario represented by the first business scenario identifier; a sending module, used to send the first response data to the first application.

[0015] Optionally, the device is also used to: before obtaining the first QR code information sent by the first application, obtain an application registration request sent by the access party, wherein the application registration request carries the callback address of the second application background device, and the access party is the second application background device, or the second application corresponding to the second application background device; in response to the application registration request, allocate the second application identifier to the access party, and record the callback address of the second application background device carried in the application registration request; and send the second application identifier to the access party.

[0016] Optionally, the device is also used to: when the access party is the second application background device, configure one or more business scenario identifiers on the second application background device, wherein the one or more business scenario identifiers include the first business scenario identifier; send the second application identifier to the second application on the second application background device, and generate the target QR code on the second application based on the first user identifier and the second application identifier.

[0017] Optionally, the device is also used to: after sending the second application identifier to the access party, when the access party is the second application background device, configure one or more business scenario identifiers on the second application background device, wherein the one or more business scenario identifiers include the first business scenario identifier; generate the target QR code on the second application background device based on the first user identifier and the second application identifier; or when the access party is the second application background device, send the second application identifier to the second application on the second application background device, generate the target QR code on the second application based on the first user identifier and the second application identifier, and configure one or more business scenario identifiers on the second application, wherein the one or more business scenario identifiers include the first business scenario identifier.

[0018] Optionally, the device is also used to: after sending the second application identifier to the access party, if the access party is the second application, configure one or more business scenario identifiers on the second application, wherein the one or more business scenario identifiers include the first business scenario identifier; generate the target QR code on the second application based on the first user identifier and the second application identifier; or if the access party is the second application, configure one or more business scenario identifiers on the second application, wherein the one or more business scenario identifiers include the first business scenario identifier; send the second application identifier to the second application background device on the second application, and generate the target QR code on the second application background device based on the first user identifier and the second application identifier; or if the access party is the second application, send the second application identifier to the second application background device on the second application, generate the target QR code on the second application background device based on the first user identifier and the second application identifier, and configure one or more business scenario identifiers on the second application background device, wherein the one or more business scenario identifiers include the first business scenario identifier.

[0019] Optionally, the device is further used to: after obtaining the application registration request sent by the access party, allocate a target encryption key and a target decryption key to the access party; and send the target encryption key and the target decryption key to the access party.

[0020] Optionally, the device is also used to: before obtaining the first QR code information sent by the first application, scan the target QR code on the first application to obtain the first user identifier and the second application identifier, wherein when the target QR code is scanned on the first application, the business scenario in which the first application is located is the first business scenario; obtain the first business scenario identifier of the first business scenario on the first application; determine the first QR code information on the first application to include the first user identifier, the second application identifier and the first business scenario identifier.

[0021] Optionally, the device is also used to: obtain second QR code information sent by a third application, wherein the second QR code information includes: a first user identifier, a second application identifier, and a second business scenario identifier, the first user identifier and the second application identifier are identifiers obtained by the third application scanning the target QR code, and the second business scenario identifier is used to represent the second business scenario corresponding to the third application scanning the target QR code; obtain the callback address of the second application background device corresponding to the second application identifier, and send the first user identifier and the second business scenario identifier to the second application background device according to the callback address; obtain the second response data sent by the second application background device, wherein the second response data is the response data of the first user identifier in the second business scenario represented by the second business scenario identifier; and send the second response data to the third application.

[0022] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is provided, in which a computer program is stored. The computer program is configured to execute the above-mentioned two-dimensional code processing method when running.

[0023] According to another aspect of an embodiment of the present invention, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the above-mentioned QR code processing method through the computer program.

[0024] In an embodiment of the present invention, a method is adopted in which first QR code information sent by a first application is obtained, wherein the first QR code information records a first business scenario identifier for representing a first business scenario corresponding to when the first application scans a target QR code. Based on the callback address of the second application background device corresponding to the second application identifier, the above-mentioned first QR code information is sent to the second application background device, and the response data sent by the second application background device is returned to the first application. By configuring corresponding business scenario identifiers, interconnection between different application data is achieved, and the purpose of different applications being able to recognize each other's QR codes to provide corresponding services is achieved, thereby achieving the technical effect of improving the privacy security of user personal information and data and optimizing the user experience, thereby solving the technical problems of data not being interoperable between different applications and poor user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0026] Figure 1 is a schematic diagram of an application environment of an optional QR code processing method according to an embodiment of the present invention;

[0027] Figure 2 is a flowchart of an optional method for processing a QR code according to an embodiment of the present invention;

[0028] Figure 3 is a schematic diagram of an optional method for processing a QR code according to an embodiment of the present invention;

[0029] Figure 4 is a flowchart of another optional method for processing a QR code according to an embodiment of the present invention;

[0030] Figure 5 is a flowchart of another optional method for processing a QR code according to an embodiment of the present invention;

[0031] Figure 6 is a flowchart of another optional method for processing a QR code according to an embodiment of the present invention;

[0032] Figure 7 is a flowchart of another optional method for processing a QR code according to an embodiment of the present invention;

[0033] Figure 8 is a flowchart of another optional method for processing a QR code according to an embodiment of the present invention;

[0034] Figure 9is a schematic structural diagram of an optional QR code processing device according to an embodiment of the present invention;

[0035] Figure 10 FIG. 4 is a schematic structural diagram of an optional electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0036] In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the embodiments described are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of the present invention.

[0037] It should be noted that the terms "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0038] First, some nouns or terms that appear in the description of the embodiments of the present application are subject to the following interpretations:

[0039] Business template ID (identity): Each business template ID represents a business scenario and the request and response parameter formats agreed upon by the business scenario.

[0040] The present invention will be described below in conjunction with embodiments:

[0041] According to one aspect of an embodiment of the present invention, a method for processing a two-dimensional code is provided. Optionally, in this embodiment, the method for processing a two-dimensional code can be applied to Figure 1 In the hardware environment composed of the server 101 and the user terminal 103 shown in FIG. Figure 1As shown, the server 101 is connected to the terminal 103 via a network and can be used to provide services for the user terminal or the client installed on the user terminal. The client can be a video client, an instant messaging client, a browser client, an education client, etc. A database 105 can be set on the server or independently of the server to provide data storage services for the server 101. The above-mentioned network can include but is not limited to: a wired network, a wireless network, wherein the wired network includes: a local area network, a metropolitan area network and a wide area network, and the wireless network includes: Bluetooth, WIFI and other networks that realize wireless communication. The user terminal 103 can be a terminal configured with a target client, and can include but is not limited to at least one of the following: a mobile phone (such as an Android phone, an iOS phone, etc.), a laptop computer, a tablet computer, a PDA, an MID (Mobile Internet Device) Devices, mobile Internet devices), PADs, desktop computers, smart TVs and other computer devices. The above-mentioned server can be a single server, a server cluster composed of multiple servers, or a cloud server, which can include but is not limited to routing or gateways. The QR code processing application 107 is displayed through the user terminal 103. The target QR code generated or displayed by the second application 109 for QR code processing can be scanned through the entrance of the first application 107 for QR code processing configured on the terminal. The above-mentioned QR code processing service has been used. The above-mentioned first application 107 and the second application 109 are both connected to the server 101 through the network. The above is only an example and is not limited to this in this embodiment.

[0042] Optionally, as an optional implementation method, taking the application of the above-mentioned QR code processing service to the server as an example, Figure 2 As shown, the processing method of the above-mentioned QR code includes:

[0043] S202: Obtain first QR code information sent by the first application, where the first QR code information includes: a first user identifier, a second application identifier, and a first business scenario identifier, where the first user identifier and the second application identifier are identifiers obtained by the first application scanning a target QR code, and the first business scenario identifier is used to indicate a first business scenario corresponding to the first application scanning the target QR code;

[0044] Optionally, in this embodiment, the above-mentioned QR code can be generated by the above-mentioned first application or the second application, and this embodiment is further described by taking the above-mentioned QR code being generated by the above-mentioned second application.

[0045] It should be noted that the above-mentioned first QR code information may include but is not limited to the first QR code information generated after the above-mentioned first application 107 scans the QR code. In the case that the QR code scanned by the above-mentioned first application 107 is generated by the second application 109 corresponding to the above-mentioned second application identifier, the above-mentioned first application 107 scans the QR code generated by the above-mentioned second application 109 in the corresponding first business scenario and generates a first QR code information recording the above-mentioned first user identifier, second application identifier and first business scenario identifier. The above-mentioned first user identifier is used to represent the user who has pre-registered in the above-mentioned first application 107 and the second application 109. It can be recorded in the QR code generated by the above-mentioned second application 109, or it can be generated after the above-mentioned first application 107 scans the above-mentioned QR code. After obtaining the above-mentioned first QR code information, the server 101 can determine the second application based on the second application identifier in the above-mentioned first QR code information, determine the user identifier corresponding to the data to be obtained from the second application background device based on the first user identifier, and obtain the data corresponding to the first user identifier in the second application background device according to the above-mentioned first business scenario. The type of the above-mentioned data is determined by the above-mentioned first business scenario.

[0046] Optionally, in this embodiment, the first application may include but is not limited to an application program, an App (application), a mini-program, etc. Figure 3 is a schematic diagram of an optional QR code processing method according to an embodiment of the present invention. The first QR code information may include but is not limited to the following: Figure 3 As shown, the second application identifier in the first QR code information is Figure 3 The preset string of "appid" in the first business scenario is Figure 3 The preset string corresponding to the "code" in the first user ID is Figure 3 The preset character string corresponding to the "user ID" in the first QR code information may also include but is not limited to a timestamp identifier for indicating the validity period of the target QR code, for example, Figure 3 The preset string corresponding to "expireTime" in is the part used to indicate the validity period of the QR code.

[0047] Optionally, in this embodiment, the above-mentioned first business scenario may include but is not limited to the first business scenario among multiple business scenarios that require calling the same type of data. For example, the use of a bus card in a different place, the bus scenario corresponding to the city where the first application is located is the first business scenario, wherein the first application and the second application respectively correspond to the bus ride services in different cities. After the user completes the bus information registration and recharge in the second application, the user uses the QR code generated by the second application and scans it through the scanning area of the first application. The server obtains the relevant data corresponding to the bus scenario from the database corresponding to the second application based on the first QR code information generated after the first application scans the QR code, and feeds it back to the above-mentioned first application for subsequent processing by the first application. The above-mentioned relevant data may include but is not limited to name, age, balance, etc.

[0048] Optionally, in this embodiment, the above-mentioned first business scenario may also include but is not limited to the first business scenario among multiple business scenarios that require recording the same type of data in advance, for example, bus riding and shopping payment, both of which require recording the user's financial information.

[0049] The above-mentioned first business scenario may also include but is not limited to the first business scenario in multiple business scenarios where the database content can be shared but the purpose of business processing can be the same or different, for example, shopping, transportation, access control, medical treatment, virtual account login, dining, ticket purchase, financial services, social services, etc., all business scenarios that can be processed by the same user. The above is only an example. The specific business scenario category may include but is not limited to one or more combinations of the above, and the present invention does not make specific limitations on this.

[0050] S204, obtaining a callback address of a second application background device corresponding to the second application identifier, and sending the first user identifier and the first business scenario identifier to the second application background device according to the callback address;

[0051] Optionally, in this embodiment, the second application may be, but is not limited to, consistent with the business scenario of the first application, and may also include but is not limited to being associated with the business scenario of the first application, or the background device of the second application may store the data corresponding to the target QR code required by the first application.

[0052] Optionally, in this embodiment, the callback address is a callback address assigned to the first application and the second application by the gateway or the router when the first application and the second application are registered in the gateway.

[0053] S206, obtaining first response data sent by the second application background device, wherein the first response data is response data of the first user identifier in the first business scenario indicated by the first business scenario identifier;

[0054] Optionally, in this embodiment, the above-mentioned first response data is a data packet generated by the above-mentioned second application background device based on the first business scenario identifier and the first user identifier recorded in the first QR code information. The above-mentioned first business scenario identifier and the corresponding response data are corresponded through preset rules. The above-mentioned preset rules are pre-configured in the server. Before obtaining the first response data sent by the above-mentioned second application background device, the above-mentioned preset rules are sent to the above-mentioned second application background device to enable the second application background device to generate corresponding response data based on the above-mentioned first business scenario identifier.

[0055] S208: Send first response data to the first application.

[0056] Optionally, in this embodiment, taking the user "Zhang San" as an example, the user "Zhang San" wants to go shopping in the supermarket: "Zhang San" needs to take the bus to the supermarket. At this time, he opens a small program to show his own QR code (equivalent to the target QR code) and pays by swiping the bus QR code. After "Zhang San" arrives at the supermarket door, he needs to measure his body temperature and check his health status. At this time, the same QR code is shown. After the inspector uses his own inspection equipment to scan the code, he can check the health status of "Zhang San". After scanning the code, the inspector will send the QR code information displayed by "Zhang San" and the first business scenario identifier corresponding to his own inspection equipment to the server. The server will check the health status of "Zhang San" according to the obtained QR code information and the corresponding The first business scenario identifier for health detection is used to perform subsequent logical processing in accordance with the pre-configured business logic corresponding to the first business scenario identifier, which may specifically include but is not limited to obtaining health information corresponding to "Zhang San". After "Zhang San" completes shopping, he presents the QR code to check out again. The cashier scans the same QR code to deduct the money. After scanning the code, the cashier will send the QR code information displayed by "Zhang San" and the first business scenario identifier corresponding to his own scanning device to the server. The server will perform subsequent logical processing again according to the business logic pre-configured corresponding to the first business scenario identifier based on the acquired QR code information and the first business scenario identifier corresponding to the payment.

[0057] Through this embodiment, the first QR code information sent by the first application is obtained, wherein the first QR code information records a first business scenario identifier for representing the first business scenario corresponding to when the first application scans the target QR code. Based on the callback address of the second application background device corresponding to the second application identifier, the above-mentioned first QR code information is sent to the second application background device, and the response data sent by the second application background device is returned to the first application. By configuring the corresponding business scenario identifier, the interconnection between different application data is realized, and the purpose of different applications being able to recognize each other's QR codes to provide corresponding services is achieved, thereby achieving the technical effect of improving the privacy security of user personal information and data and optimizing the user experience, thereby solving the technical problems of data not being interoperable between different applications and poor user experience.

[0058] In an optional embodiment, Figure 4 is a flow chart of an optional QR code processing method according to an embodiment of the present invention. Before obtaining the first QR code information sent by the first application, the method further includes:

[0059] S402: Obtain an application registration request sent by the access party, wherein the application registration request carries a callback address of the second application background device, and the access party is the second application background device, or the second application corresponding to the second application background device;

[0060] S404, in response to the application registration request, allocating a second application identifier to the access party, and recording the callback address of the second application background device carried in the application registration request;

[0061] S406: Send the second application identifier to the access party.

[0062] Optionally, in this embodiment, the above-mentioned access party may include but is not limited to the first application and the second application, may include but is not limited to the above-mentioned target QR code generator, may also be the above-mentioned target QR code parsing and processing party, and may also include an application program or a background device of an application program that generates a target QR code and parses a target QR code. The above is only an example, and the present invention does not impose any specific restrictions on this.

[0063] It should be noted that both the first application and the second application need to complete the above registration process on the server, and then receive the application identifiers allocated by the server to the first application and the second application according to the application registration request, so as to facilitate subsequent QR code processing.

[0064] Through this embodiment, the access party is registered with the server so that the server can issue an application identifier to the access party and obtain a callback address corresponding to the access party, so as to realize the interconnection and intercommunication of data between different access parties through the server, thereby achieving the technical effect of optimizing the user experience, and thus solving the technical problems of data non-intercommunication between different applications and poor user experience.

[0065] In an optional embodiment, Figure 5 is a flow chart of an optional method for processing a QR code according to an embodiment of the present invention, such as Figure 5 As shown, after sending the second application identifier to the access party, the above method further includes:

[0066] S502, when the access party is a second application background device, configuring one or more business scenario identifiers on the second application background device, wherein the one or more business scenario identifiers include a first business scenario identifier; generating a target QR code on the second application background device according to the first user identifier and the second application identifier; or

[0067] S504: When the access party is a second application background device, configure one or more business scenario identifiers on the second application background device, wherein the one or more business scenario identifiers include the first business scenario identifier; send the second application identifier to the second application on the second application background device, and generate a target QR code on the second application according to the first user identifier and the second application identifier; or

[0068] S506, when the access party is the second application background device, the second application identifier is sent to the second application on the second application background device, a target QR code is generated on the second application based on the first user identifier and the second application identifier, and one or more business scenario identifiers are configured on the second application, wherein the one or more business scenario identifiers include the first business scenario identifier.

[0069] Optionally, in this embodiment, the execution order of the above steps S502, S504 and S506 is selected.

[0070] Optionally, in this embodiment, the above-mentioned target QR code can be generated by including but not limited to a second application background device or a second application, and can also be generated by including but not limited to the above-mentioned second application background device. The business scenario identifier is then sent to the above-mentioned second application to achieve the business scenario identifier being carried in the above-mentioned target QR code.

[0071] Optionally, in this embodiment, it may also include but not be limited to the server allocating a corresponding business scenario identifier to the above-mentioned second application background device, or other applications or other application background devices allocating a corresponding business scenario identifier to the above-mentioned second application background device.

[0072] Through this embodiment, when the access party is the second application background device, configuring the business scenario identifier for the second application background device can enable the generated target QR code to record the business scenario information corresponding to the background device that generates the QR code, thereby enabling the corresponding business execution logic to be obtained according to the preset business scenario identifier, and then executing the corresponding business, so that multiple applications and application background devices can obtain the data required to execute the business through the above-mentioned target QR code, complete the data interconnection between multiple applications, and thus solve the technical problems of data non-interoperability between different applications and poor user experience.

[0073] In an optional embodiment, Figure 6 is a flow chart of an optional method for processing a QR code according to an embodiment of the present invention, such as Figure 6 As shown, after sending the second application identifier to the access party, the above method further includes:

[0074] S602: When the access party is a second application, configure one or more business scenario identifiers on the second application, wherein the one or more business scenario identifiers include the first business scenario identifier; generate a target QR code on the second application according to the first user identifier and the second application identifier; or

[0075] S604: When the access party is a second application, configure one or more business scenario identifiers on the second application, wherein the one or more business scenario identifiers include the first business scenario identifier; send the second application identifier to a second application background device on the second application, and generate a target QR code on the second application background device according to the first user identifier and the second application identifier; or

[0076] S606, when the access party is the second application, the second application identifier is sent to the second application background device on the second application, a target QR code is generated on the second application background device according to the first user identifier and the second application identifier, and one or more business scenario identifiers are configured on the second application background device, wherein the one or more business scenario identifiers include the first business scenario identifier.

[0077] Optionally, in this embodiment, the above-mentioned target QR code can be generated by including but not limited to a second application background device or a second application, and can also be generated by including but not limited to the above-mentioned second application background device. The business scenario identifier is then sent to the above-mentioned second application to achieve the business scenario identifier being carried in the above-mentioned target QR code.

[0078] Optionally, in this embodiment, it may also include but not be limited to the server allocating a corresponding business scenario identifier to the above-mentioned second application, or other applications or other application background devices allocating a corresponding business scenario identifier to the above-mentioned second application.

[0079] Through this embodiment, when the access party is the second application, configuring a business scenario identifier for the second application can enable the generated target QR code to record the business scenario information corresponding to the application that generates the QR code, thereby enabling the corresponding business execution logic to be obtained according to the preset business scenario identifier, and then executing the corresponding business, so that multiple applications and application background devices can obtain the data required to execute the business through the above-mentioned target QR code, complete the data interconnection between multiple applications, and thus solve the technical problems of data non-interoperability between different applications and poor user experience.

[0080] In an optional embodiment, after obtaining the application registration request sent by the access party, the above method further includes: allocating a target encryption key and a target decryption key to the access party; and sending the target encryption key and the target decryption key to the access party.

[0081] Optionally, in this embodiment, the target encryption key and target decryption key may be pre-configured by the server for the access party, and the server may return the target encryption key and target decryption key to the access party after the access party sends a registration request message to the server. The server may also pre-configure an algorithm for generating the target encryption key and target decryption key based on the application identifier, and the access party itself may generate the target encryption key and target decryption key based on the algorithm.

[0082] Optionally, in this embodiment, during data exchange between the first application and the second application and the server, each data packet needs to carry the target encryption key and the target decryption key, and the target encryption key and the target decryption key correspond to the application identifier. For example, the first application corresponds to the first target encryption key and the first target decryption key, and the second application corresponds to the second target encryption key and the second target decryption key.

[0083] Through this embodiment, the security of the first QR code information and the first response information during transmission is effectively guaranteed, achieving the technical effect of secure and reliable data transmission during data interconnection.

[0084] In an optional embodiment, before obtaining the first QR code information sent by the first application, the above method also includes: scanning the target QR code on the first application to obtain the first user identifier and the second application identifier, wherein, when scanning the target QR code on the first application, the business scenario where the first application is located is the first business scenario; obtaining the first business scenario identifier of the first business scenario on the first application; and determining the first QR code information on the first application to include the first user identifier, the second application identifier and the first business scenario identifier.

[0085] Optionally, in this embodiment, the above-mentioned target QR code can be but is not limited to being generated by a second application. Therefore, when scanning the above-mentioned target QR code, the second application identifier corresponding to the above-mentioned second application can be obtained, and the QR code information obtained after scanning the target QR code is repackaged, and the above-mentioned first QR code information is obtained by adding the first business scenario identifier to the QR code information obtained after scanning the target QR code.

[0086] Through this embodiment, based on the second application identifier, the server can forward the above-mentioned first QR code information to the second application corresponding to the second application identifier. The background device of the second application obtains data associated with the user and the business scenario based on the first user identifier and the first business scenario identifier, and returns it to the server. The server then sends the above-mentioned data to the first application, realizing the interconnection between the first application and the second application, thereby achieving the technical effect of optimizing the user experience.

[0087] For example, in the case where the above-mentioned first business scenario is a health check, the background device of the above-mentioned second application obtains data associated with the user and the business scenario based on the first user identifier and the first business scenario identifier, which may include but is not limited to: "Name", "Telephone", "Gender", "Birthday", "Document Type, "ID Card", "City", "Address", "Creation Time", "Health Risk Rating", etc. The above is only an example. The above-mentioned data associated with the user and business scenario may include one or more combinations of the above, and the present invention does not make specific limitations on this.

[0088] In an optional embodiment, the above method also includes: obtaining second QR code information sent by the third application, wherein the second QR code information includes: a first user identifier, a second application identifier, and a second business scenario identifier, the first user identifier and the second application identifier are identifiers obtained when the third application scans the target QR code, and the second business scenario identifier is used to represent the second business scenario corresponding to when the third application scans the target QR code; obtaining the callback address of the second application background device corresponding to the second application identifier, and sending the first user identifier and the second business scenario identifier to the second application background device according to the callback address; obtaining the second response data sent by the second application background device, wherein the second response data is the response data of the first user identifier in the second business scenario represented by the second business scenario identifier; sending the second response data to the third application.

[0089] Optionally, in this embodiment, the above-mentioned third application may include but is not limited to applications with business scenarios that are different from the first application and the second application, and may also include but is not limited to applications that are the same as the first application or the second application. The above-mentioned second user identifier may be the same as or different from the first user identifier. When the above-mentioned second user identifier is different from the first user identifier, the second user identifier and the first user identifier correspond to different users, thereby being able to realize an application scenario that serves multiple people.

[0090] Optionally, in this embodiment, before obtaining the second QR code information sent by the third application for data intercommunication, the third application needs to be registered to the server so that the third application can simultaneously communicate with the first application and the second application, thereby optimizing the user experience.

[0091] The present invention will be further described below in conjunction with specific embodiments:

[0092] Take the target QR code as an example, Figure 7 is a flow chart of an optional method for processing a QR code according to an embodiment of the present invention, such as Figure 7 As shown, the process steps are as follows:

[0093] S702, Mini Program A (equivalent to the first application) and Mini Program B (equivalent to the second application) register their app information in the routing center (equivalent to the server);

[0094] S704, the routing center returns AppID (equivalent to the first application identifier and the second application identifier) and appsecret (equivalent to the target encryption key and target decryption key corresponding to the first application and the target encryption key and target decryption key corresponding to the second application) to mini program A and mini program B.

[0095] S706, Mini Program B requests the QR code content from the Mini Program B backend.

[0096] S708, Mini Program B generates a target QR code in the background and sends it to Mini Program B;

[0097] S710 , Mini Program A scans the target QR code corresponding to Mini Program B;

[0098] S712, Mini Program A sends a message requesting the QR code content to the backend of Mini Program A;

[0099] S714, the backend of Mini Program A sends a request message to the routing center;

[0100] S716, the routing center forwards the request message to the backend of mini program B through the pre-configured callback interface;

[0101] S718, the backend of Mini Program B generates a processing result based on the request message and returns it to the routing center;

[0102] S720: The routing center sends the processing result to the backend of Mini Program A through the pre-configured callback interface.

[0103] S722, the backend of Mini Program A feeds back the above processing results to Mini Program A.

[0104] In addition, the routing center can also maintain the appsecret key and corresponding callback interface of the aforementioned mini-program A or B. To ensure interface security, registered mini-programs cannot arbitrarily call each other's mini-program interfaces. Before the two mini-programs need to call each other, one of them must initiate an application before the interface can be called to finally realize data interconnection and interoperability.

[0105] Among them, the business template is a set of business scenarios agreed upon by interoperable mini-programs and the conventions of unified parameters and return values for the corresponding scenarios.

[0106] For example: the business template ID is 10001, which represents the business template for obtaining user identity information. The request parameters of this business template are

[0107] ask:

[0108]

[0109]

[0110] Request parameters: path? toappid=appidB&tplid=00001;

[0111] Toappid: The ID of the application that is finally processed. The routing center uses this ID to identify the target application to which the request is forwarded.

[0112] tplid: template ID, the business scenario corresponding to this request.

[0113] Access Party Request Header

[0114] Request header:

[0115]

[0116]

[0117] The above is only an example, and this embodiment does not impose any specific limitation on the composition of the specific response parameters and request parameters.

[0118] In an alternative embodiment, Figure 8 is a flow chart of an optional method for processing a QR code according to an embodiment of the present invention, such as Figure 8 As shown, the process steps are as follows:

[0119] S802: The administrator creates an application for the access party in the routing center. When creating the application, the administrator fills in the access party's callback address and assigns the appid and appsecret to the access party.

[0120] S804: After identifying the QR code, the client (terminal, app, or mini-program) of the access party needs to determine the template ID based on the current business scenario (payment, health check, etc.). When sending a request message to the routing center, it needs to carry the QR code parameters and the template ID, and sign it with appid and appscert according to the requirements of the routing center. Then, the routing center is requested to process the QR code and return the result.

[0121] S806: The access party needs to provide the interface address to the routing center for processing the intercommunication QR code business. The interface needs to use appid and appscert for security signature verification according to the signature requirements of the routing center. The verification is implemented through the template ID of the parameter to implement the corresponding business scenario.

[0122] It should be noted that for the aforementioned method embodiments, for simplicity of description, they are all expressed as a series of action combinations. However, those skilled in the art should be aware that the present invention is not limited by the order of the actions described, because according to the present invention, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in this specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present invention.

[0123] According to another aspect of the embodiments of the present invention, a two-dimensional code processing device for implementing the above-mentioned two-dimensional code processing method is also provided. Figure 9 As shown, the device includes:

[0124] The first acquisition module 902 is used to obtain the first QR code information sent by the first application, wherein the first QR code information includes: a first user identifier, a second application identifier and a first business scenario identifier, the first user identifier and the second application identifier are identifiers obtained when the first application scans the target QR code, and the first business scenario identifier is used to represent the first business scenario corresponding to when the first application scans the target QR code; the processing module 904 is used to obtain the callback address of the second application background device corresponding to the second application identifier, and send the first user identifier and the first business scenario identifier to the second application background device according to the callback address; the second acquisition module 906 is used to obtain the first response data sent by the second application background device, wherein the first response data is the response data of the first user identifier in the first business scenario represented by the first business scenario identifier; the sending module 908 is used to send the first response data to the first application.

[0125] In an optional embodiment, the device is also used to: before obtaining the first QR code information sent by the first application, obtain an application registration request sent by the access party, wherein the application registration request carries the callback address of the second application background device, and the access party is the second application background device, or the second application corresponding to the second application background device; in response to the application registration request, assign a second application identifier to the access party, and record the callback address of the second application background device carried in the application registration request; and send the second application identifier to the access party.

[0126] In an optional embodiment, the device is also used to: after sending the second application identifier to the access party, if the access party is a second application background device, configure one or more business scenario identifiers on the second application background device, wherein the one or more business scenario identifiers include the first business scenario identifier; generate a target QR code on the second application background device based on the first user identifier and the second application identifier; or if the access party is a second application background device, configure one or more business scenario identifiers on the second application background device, wherein the one or more business scenario identifiers include the first business scenario identifier; send the second application identifier to the second application on the second application background device, and generate a target QR code on the second application based on the first user identifier and the second application identifier; or if the access party is a second application background device, send the second application identifier to the second application on the second application background device, generate a target QR code on the second application based on the first user identifier and the second application identifier, and configure one or more business scenario identifiers on the second application, wherein the one or more business scenario identifiers include the first business scenario identifier.

[0127] In an optional embodiment, the device is also used to: after sending the second application identifier to the access party, if the access party is the second application, configure one or more business scenario identifiers on the second application, wherein the one or more business scenario identifiers include the first business scenario identifier; generate a target QR code on the second application based on the first user identifier and the second application identifier; or if the access party is the second application, configure one or more business scenario identifiers on the second application, wherein the one or more business scenario identifiers include the first business scenario identifier; send the second application identifier to the second application background device on the second application, and generate a target QR code on the second application background device based on the first user identifier and the second application identifier; or if the access party is the second application, send the second application identifier to the second application background device on the second application, generate a target QR code on the second application background device based on the first user identifier and the second application identifier, and configure one or more business scenario identifiers on the second application background device, wherein the one or more business scenario identifiers include the first business scenario identifier.

[0128] In an optional embodiment, the device is further used to: after obtaining the application registration request sent by the access party, allocate a target encryption key and a target decryption key to the access party; and send the target encryption key and the target decryption key to the access party.

[0129] In an optional embodiment, the device is also used to: scan the target QR code on the first application before obtaining the first QR code information sent by the first application to obtain the first user identifier and the second application identifier, wherein when the target QR code is scanned on the first application, the business scenario in which the first application is located is the first business scenario; obtain the first business scenario identifier of the first business scenario on the first application; determine the first QR code information on the first application to include the first user identifier, the second application identifier and the first business scenario identifier.

[0130] In an optional embodiment, the device is also used to: obtain second QR code information sent by a third application, wherein the second QR code information includes: a first user identifier, a second application identifier, and a second business scenario identifier, the first user identifier and the second application identifier are identifiers obtained when the third application scans the target QR code, and the second business scenario identifier is used to represent the second business scenario corresponding to when the third application scans the target QR code; obtain the callback address of the second application background device corresponding to the second application identifier, and send the first user identifier and the second business scenario identifier to the second application background device according to the callback address; obtain the second response data sent by the second application background device, wherein the second response data is the response data of the first user identifier in the second business scenario represented by the second business scenario identifier; and send the second response data to the third application.

[0131] According to another aspect of the embodiment of the present invention, an electronic device for implementing the above-mentioned two-dimensional code processing method is also provided. The electronic device may be Figure 1 The terminal device or server shown in FIG. This embodiment is described by taking the electronic device as a server as an example. Figure 10 As shown, the electronic device includes a memory 1002 and a processor 1004. The memory 1002 stores a computer program, and the processor 1004 is configured to execute the steps in any of the above method embodiments through the computer program.

[0132] Optionally, in this embodiment, the electronic device may be located in at least one network device among a plurality of network devices of a computer network.

[0133] Optionally, in this embodiment, the processor may be configured to execute the following steps through a computer program:

[0134] S1. Obtain first QR code information sent by a first application, where the first QR code information includes: a first user identifier, a second application identifier, and a first business scenario identifier. The first user identifier and the second application identifier are identifiers obtained by the first application scanning a target QR code. The first business scenario identifier is used to indicate a first business scenario corresponding to the first application scanning the target QR code.

[0135] S2, obtaining a callback address of a second application background device corresponding to the second application identifier, and sending the first user identifier and the first business scenario identifier to the second application background device according to the callback address;

[0136] S3, obtaining first response data sent by the second application background device, wherein the first response data is response data of the first user identifier in the first business scenario indicated by the first business scenario identifier;

[0137] S4: Send first response data to the first application.

[0138] Alternatively, those skilled in the art will appreciate that Figure 10 The structure shown is for illustration only, and the electronic device may also be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a PDA, a mobile Internet device (MID), a PAD, or other terminal devices. Figure 10 It does not limit the structure of the electronic device. For example, the electronic device may also include Figure 10 More or fewer components (such as network interfaces, etc.) as shown in, or with Figure 10 Different configurations shown.

[0139] Among them, the memory 1002 can be used to store software programs and modules, such as the program instructions / modules corresponding to the two-dimensional code processing method and device in the embodiment of the present invention. The processor 1004 executes various functional applications and data processing by running the software programs and modules stored in the memory 1002, that is, realizing the above-mentioned two-dimensional code processing method. The memory 1002 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 1002 may further include a memory remotely located relative to the processor 1004, and these remote memories can be connected to the terminal via a network. Examples of the above-mentioned networks include but are not limited to the Internet, corporate intranets, local area networks, mobile communication networks and combinations thereof. Among them, the memory 1002 can be used specifically, but not limited to, to store information such as user data and application-related data. As an example, such as Figure 10 As shown, the memory 1002 may include, but is not limited to, the first acquisition module 902, processing module 904, second acquisition module 906 and sending module 908 in the QR code processing device, which are used to send first response data to the first application.

[0140] In addition, it may also include but is not limited to other module units in the above-mentioned QR code processing device, which will not be repeated in this example.

[0141] Optionally, the transmission device 1006 is configured to receive or send data via a network. Specific examples of the network may include a wired network and a wireless network. In one embodiment, the transmission device 1006 includes a network interface controller (NIC), which can be connected to other network devices and a router via a network cable to communicate with the Internet or a local area network. In one embodiment, the transmission device 1006 is a radio frequency (RF) module, which is configured to communicate with the Internet wirelessly.

[0142] In other embodiments, the terminal device or server may be a node in a distributed system, wherein the distributed system may be a blockchain system, and the blockchain system may be a distributed system formed by connecting multiple nodes through network communication. The nodes may form a peer-to-peer (P2P) network, and any computing device, such as a server, terminal, or other electronic device, may become a node in the blockchain system by joining the peer-to-peer network.

[0143] According to another aspect of an embodiment of the present invention, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in the various optional implementations of processing a QR code.

[0144] Optionally, in this embodiment, the computer-readable storage medium may be configured to store a computer program for performing the following steps:

[0145] S1. Obtain first QR code information sent by a first application, where the first QR code information includes: a first user identifier, a second application identifier, and a first business scenario identifier. The first user identifier and the second application identifier are identifiers obtained by the first application scanning a target QR code. The first business scenario identifier is used to indicate a first business scenario corresponding to the first application scanning the target QR code.

[0146] S2, obtaining a callback address of a second application background device corresponding to the second application identifier, and sending the first user identifier and the first business scenario identifier to the second application background device according to the callback address;

[0147] S3, obtaining first response data sent by the second application background device, wherein the first response data is response data of the first user identifier in the first business scenario indicated by the first business scenario identifier;

[0148] S4: Send first response data to the first application.

[0149] Optionally, in this embodiment, a person of ordinary skill in the art may understand that all or part of the steps in the various methods of the above embodiments may be completed by instructing the hardware related to the terminal device through a program, and the program may be stored in a computer-readable storage medium, which may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0150] The serial numbers of the above embodiments of the present invention are for description only and do not represent the advantages or disadvantages of the embodiments.

[0151] If the integrated units in the above embodiments are implemented in the form of software functional units and sold or used as independent products, they can be stored in the above-mentioned computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the existing technology, or all or part of the technical solution can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes a number of instructions for causing one or more computer devices (such as personal computers, servers, or network devices) to execute all or part of the steps of the methods described in various embodiments of the present invention.

[0152] In the above embodiments of the present invention, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0153] In the several embodiments provided in this application, it should be understood that the disclosed client can be implemented in other ways. Among them, the device embodiments described above are merely illustrative. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, and can be electrical or other forms.

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

[0155] In addition, the functional units in the various embodiments of the present invention may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units or devices may be implemented in the form of hardware or software functional units.

[0156] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as within the scope of protection of the present invention.

Claims

1. A method for processing a two-dimensional code, characterized in that: include: Obtaining first QR code information sent by a first application, where the first QR code information includes: a first user identifier, a second application identifier, and a first business scenario identifier, where the first user identifier and the second application identifier are identifiers obtained by the first application scanning a target QR code, and the first business scenario identifier is used to indicate a first business scenario corresponding to the first application scanning the target QR code, where the first business scenario belongs to multiple business scenarios that require calling data of the same type; Obtaining a callback address of a second application background device corresponding to the second application identifier, and sending the first user identifier and the first business scenario identifier to the second application background device according to the callback address, where the callback address of the second application background device represents the callback address assigned by the gateway when the second application is registered with the gateway; Obtaining first response data generated and sent by the second application background device according to the first business scenario identifier and the first user identifier, where the first response data is response data of the first user identifier in the first business scenario; and sending the first response data to the first application; Before obtaining the first QR code information sent by the first application, the method also includes: obtaining an application registration request sent by the second application background device, the application registration request carrying the callback address of the second application background device; in response to the application registration request, allocating the second application identifier to the second application background device, and recording the callback address of the second application background device; sending the second application identifier to the second application background device, and configuring the first business scenario identifier on the second application background device; generating the target QR code on the second application background device based on the first user identifier and the second application identifier.

2. The method according to claim 1, characterized in that Before obtaining the first QR code information sent by the first application, the method further includes: Obtaining an application registration request sent by the access party, wherein the application registration request carries a callback address of the second application background device, and the access party is the second application background device, or the second application corresponding to the second application background device; In response to the application registration request, assign the second application identifier to the access party, and record the callback address of the second application background device carried in the application registration request; Send the second application identifier to the access party.

3. The method according to claim 2, characterized in that After sending the second application identifier to the access party, the method further includes: When the access party is the second application background device, one or more business scenario identifiers are configured on the second application background device, wherein the one or more business scenario identifiers include the first business scenario identifier; and the target QR code is generated on the second application background device according to the first user identifier and the second application identifier.

4. The method according to claim 2, characterized in that After sending the second application identifier to the access party, the method further includes: When the access party is the second application, one or more business scenario identifiers are configured on the second application, wherein the one or more business scenario identifiers include the first business scenario identifier; and the target QR code is generated on the second application based on the first user identifier and the second application identifier.

5. The method according to claim 2, characterized in that After obtaining the application registration request sent by the access party, the method further includes: Allocating a target encryption key and a target decryption key to the access party; The target encryption key and the target decryption key are sent to the access party.

6. The method according to claim 1, characterized in that Before obtaining the first QR code information sent by the first application, the method further includes: Scanning the target QR code on the first application to obtain the first user identifier and the second application identifier, wherein when the target QR code is scanned on the first application, the business scenario of the first application is the first business scenario; Obtaining the first business scenario identifier of the first business scenario on the first application; The first QR code information is determined on the first application to include the first user identifier, the second application identifier, and the first business scenario identifier.

7. The method according to claim 1, characterized in that The method further comprises: Obtaining second QR code information sent by a third application, wherein the second QR code information includes: a first user identifier, the second application identifier, and a second business scenario identifier, where the first user identifier and the second application identifier are identifiers obtained by the third application scanning the target QR code, and the second business scenario identifier is used to indicate a second business scenario corresponding to when the third application scans the target QR code; Obtaining the callback address of the second application background device corresponding to the second application identifier, and sending the first user identifier and the second business scenario identifier to the second application background device according to the callback address; Obtaining second response data sent by the second application background device, wherein the second response data is response data of the first user identifier in the second business scenario represented by the second business scenario identifier; The second response data is sent to the third application.

8. A two-dimensional code processing device, characterized in that: include: A first acquisition module is configured to acquire first QR code information sent by a first application, the first QR code information including: a first user identifier, a second application identifier, and a first business scenario identifier, the first user identifier and the second application identifier being identifiers obtained by the first application scanning a target QR code, the first business scenario identifier being used to indicate a first business scenario corresponding to the first application scanning the target QR code, the first business scenario being one of multiple business scenarios requiring the invocation of the same type of data; a processing module, configured to obtain a callback address of a second application background device corresponding to the second application identifier, and send the first user identifier and the first business scenario identifier to the second application background device according to the callback address, where the callback address of the second application background device represents the callback address assigned by the gateway when the second application is registered with the gateway; A second acquisition module is configured to acquire first response data generated and sent by the second application background device according to the first business scenario identifier and the first user identifier, where the first response data is response data of the first user identifier in the first business scenario represented by the first business scenario identifier; A sending module, configured to send the first response data to the first application; The device is also used to: before obtaining the first QR code information sent by the first application, obtain an application registration request sent by the second application background device, and the application registration request carries the callback address of the second application background device; in response to the application registration request, allocate the second application identifier to the second application background device, and record the callback address of the second application background device; send the second application identifier to the second application background device, and configure the first business scenario identifier on the second application background device; generate the target QR code on the second application background device according to the first user identifier and the second application identifier.

9. The device according to claim 8, characterized in that The device is also used for: Before obtaining the first QR code information sent by the first application, obtaining an application registration request sent by the access party, wherein the application registration request carries the callback address of the second application background device, and the access party is the second application background device, or the second application corresponding to the second application background device; In response to the application registration request, assign the second application identifier to the access party, and record the callback address of the second application background device carried in the application registration request; Send the second application identifier to the access party.

10. The device according to claim 9, characterized in that The device is also used for: When the access party is the second application background device, one or more business scenario identifiers are configured on the second application background device, wherein the one or more business scenario identifiers include the first business scenario identifier; the second application identifier is sent to the second application on the second application background device, and the target QR code is generated on the second application based on the first user identifier and the second application identifier.

11. The device according to claim 9, characterized in that The device is also used for: When the access party is the second application, one or more business scenario identifiers are configured on the second application, wherein the one or more business scenario identifiers include the first business scenario identifier; the second application identifier is sent to the second application background device on the second application, and the target QR code is generated on the second application background device based on the first user identifier and the second application identifier.

12. The device according to claim 9, characterized in that The device is also used for: After obtaining the application registration request sent by the access party, allocating a target encryption key and a target decryption key to the access party; The target encryption key and the target decryption key are sent to the access party.

13. The device according to claim 8, characterized in that The device is also used for: Before obtaining the first QR code information sent by the first application, scanning the target QR code on the first application to obtain the first user identifier and the second application identifier, wherein when scanning the target QR code on the first application, the business scenario of the first application is the first business scenario; Obtaining the first business scenario identifier of the first business scenario on the first application; The first QR code information is determined on the first application to include the first user identifier, the second application identifier, and the first business scenario identifier.

14. A computer-readable storage medium comprising a stored program, wherein: When the program is executed, the method described in any one of claims 1 to 7 is executed.

15. An electronic device comprising a memory and a processor, characterized in that: A computer program is stored in the memory, and the processor is configured to execute the method according to any one of claims 1 to 7 through the computer program.

Images