CN111178840A

CN111178840A - Service processing method, device, system, electronic equipment and storage medium

Info

Publication number: CN111178840A
Application number: CN201911374766.5A
Authority: CN
Inventors: 孙曦; 宋洁; 郑吉�; 潘勇; 左敏
Original assignee: Alipay Labs Singapore Pte Ltd
Current assignee: Advanced Nova Technology Singapore Holdings Ltd
Priority date: 2019-12-27
Filing date: 2019-12-27
Publication date: 2020-05-19

Abstract

In the service processing system, a service participant client generates a service graphic code according to service supplementary information of a service to be processed and an identity of the service participant, the service participant client is associated with at least one service response server, each associated service response server is configured with corresponding service basic information for the service participant, and a mapping relation between the service basic information and the identity of the service participant is uploaded to the storage device for storage; the service requester client analyzes the service graphic code to obtain an identity, and initiates a query request aiming at a service participant to the storage device based on the identity so that the storage device searches candidate service basic information corresponding to the identity in the query request according to a mapping relation; and acquiring target service basic information matched with the service requester client in the candidate service basic information, and processing the service to be processed based on the target service basic information and the service supplementary information.

Description

Service processing method, device, system, electronic equipment and storage medium

Technical Field

One or more embodiments of the present disclosure relate to the field of block chain technologies, and in particular, to a method and an apparatus for processing a service, a system, an electronic device, and a storage medium.

Background

The block chain technology, also called distributed ledger technology, is an emerging technology in which several computing devices participate in "accounting" together, and a complete distributed database is maintained together. The blockchain technology has been widely used in many fields due to its characteristics of decentralization, transparency, participation of each computing device in database records, and rapid data synchronization between computing devices.

Disclosure of Invention

In view of this, one or more embodiments of the present disclosure provide a service processing method, a service processing apparatus, a service processing system, an electronic device, and a storage medium.

To achieve the above object, one or more embodiments of the present disclosure provide the following technical solutions:

according to a first aspect of one or more embodiments of the present specification, there is provided a service processing system, including: the system comprises a service participant client, a service requester client and storage equipment;

the business participant client generates a business graphic code according to business supplementary information of a business to be processed and an identity of the business participant, the business participant client is associated with at least one business response server, each associated business response server is configured with corresponding business basic information aiming at the business participant, and the mapping relation between the business basic information and the identity generated by each associated business response server for the business participant is uploaded to the storage device for storage;

the service requester client analyzes the service graphic code to obtain the identity, and initiates a query request aiming at the service participant to the storage device based on the identity so that the storage device searches candidate service basic information corresponding to the identity in the query request according to the mapping relation; and acquiring target service basic information matched with the service requester client in the candidate service basic information, and processing the service to be processed based on the target service basic information and service supplementary information obtained by analyzing the service graphic code.

According to a second aspect of one or more embodiments of the present specification, there is provided a service processing method applied to a service participant client, the method including:

generating a service graphic code according to service supplementary information of a service to be processed and an identity of a service participant so as to be analyzed by a service requester client, wherein the service participant is associated with at least one service response server, each associated service response server is configured with corresponding service basic information for the service participant, and the mapping relation between the service basic information and the identity generated by each associated service response server for the service participant is uploaded to a storage device for storage;

when the service request side client analyzes the service graphic code to obtain the identity, the identity is submitted to the storage device by the service request side client through a query request aiming at the service participant client, so that the storage device searches candidate service basic information corresponding to the identity according to the mapping relation, and the service basic information adopted by the service request side client when processing the service to be processed based on the service supplementary information obtained by analyzing the service graphic code is the service basic information matched with the service request side client in the candidate service basic information.

According to a third aspect of one or more embodiments of the present specification, a service processing method is provided, which is applied to a service requester client, and includes:

analyzing a service graphic code generated by a service participant client to obtain service supplementary information of a service to be processed and an identity of the service participant, wherein the service supplementary information is contained in the service graphic code, the service participant is associated with at least one service response server, each associated service response server is configured with corresponding service basic information aiming at the service participant, and the mapping relation between the service basic information and the identity, which is generated by each associated service response server for the service participant, is uploaded to a storage device for storage;

initiating a query request aiming at the service participant to the storage equipment based on the identity so that the storage equipment searches candidate service basic information corresponding to the identity in the query request according to the mapping relation;

and acquiring target service basic information matched with the service requester client in the candidate service basic information, and processing the service to be processed based on the target service basic information and service supplementary information obtained by analyzing the service graphic code.

According to a fourth aspect of one or more embodiments of the present specification, a traffic processing method is provided, which is applied to a blockchain node, and includes:

receiving a query request aiming at a service participant, which is initiated by a service requester client, wherein the query request comprises an identity of the service participant, the identity is obtained by analyzing a service graphic code generated by the service participant client by the service requester client, the service participant is associated with at least one service response server, each associated service response server is configured with corresponding service basic information aiming at the service participant, and the mapping relation between the service basic information and the identity, which are generated by the service participant by each associated service response server, is uploaded to the storage device for storage;

and searching candidate service basic information corresponding to the identity identifier contained in the query request according to the mapping relation, acquiring target service basic information matched with the service requester client in the candidate service basic information by the service requester client, and processing the service to be processed based on the target service basic information and service supplementary information of the service to be processed, which is obtained by analyzing the service graphic code.

According to a fifth aspect of one or more embodiments of the present specification, there is provided a service processing apparatus applied to a service participant client, the apparatus including:

the generating unit is used for generating a business graphic code according to business supplementary information of a business to be processed and an identity of a business participant so as to be analyzed by a business requester client, the business participant is associated with at least one business response server, each associated business response server is configured with corresponding business basic information aiming at the business participant, and the mapping relation between the business basic information and the identity generated by each associated business response server for the business participant is uploaded to a storage device for storage;

According to a sixth aspect of one or more embodiments of the present specification, there is provided a service processing apparatus applied to a service requester client, the apparatus including:

the system comprises an analysis unit and a storage device, wherein the analysis unit is used for analyzing a service graphic code generated by a service participant client to obtain service supplementary information of a service to be processed and an identity of the service participant, the service participant is associated with at least one service response server, each associated service response server is configured with corresponding service basic information aiming at the service participant, and the mapping relation between the service basic information and the identity generated by each associated service response server for the service participant is uploaded to the storage device for storage;

the query unit initiates a query request aiming at the service participant to the storage device based on the identity so that the storage device searches candidate service basic information corresponding to the identity in the query request according to the mapping relation;

and the service processing unit is used for acquiring target service basic information matched with the service requester client in the candidate service basic information and processing the service to be processed based on the target service basic information and service supplementary information obtained by analyzing the service graphic code.

According to a seventh aspect of one or more embodiments of the present specification, there is provided a traffic processing apparatus, applied to a blockchain node, the apparatus including:

the first receiving unit is used for receiving a query request aiming at a service participant and initiated by a service requester client, wherein the query request comprises an identity of the service participant, the identity is obtained by analyzing a service graphic code generated by the service participant client by the service requester client, the service participant is associated with at least one service response server, each associated service response server is configured with corresponding service basic information aiming at the service participant, and the mapping relation between the service basic information and the identity, which are generated by the service participant, of each associated service response server is uploaded to the storage device for storage;

and the query unit is used for searching candidate service basic information corresponding to the identity identifier contained in the query request according to the mapping relation, acquiring target service basic information matched with the service requester client in the candidate service basic information by the service requester client, and processing the service to be processed based on the target service basic information and the service supplementary information of the service to be processed, which is obtained by analyzing the service graphic code.

According to an eighth aspect of one or more embodiments herein, there is provided an electronic apparatus, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor implements the service processing method as described in the second aspect by executing the executable instructions.

According to a ninth aspect of one or more embodiments of the present specification, there is provided an electronic device, including:

a processor;

a memory for storing processor-executable instructions;

wherein the processor implements the service processing method as described in the third aspect by executing the executable instructions.

According to a tenth aspect of one or more embodiments of the present specification, there is provided an electronic apparatus comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor implements the service processing method as described in the fourth aspect by executing the executable instructions.

According to an eleventh aspect of one or more embodiments of the present specification, there is provided a computer-readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the method according to any one of the second aspects described above.

According to a twelfth aspect of one or more embodiments of the present specification, there is provided a computer-readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the method according to any one of the above third aspects.

According to a thirteenth aspect of one or more embodiments of the present specification, there is provided a computer-readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the method according to any one of the above-mentioned fourth aspects.

Drawings

FIG. 1A is a schematic diagram of creating an intelligent contract, provided by an exemplary embodiment.

FIG. 1B is a schematic diagram of a calling smart contract, provided by an exemplary embodiment.

Fig. 2 is a schematic diagram of an architecture of a business processing system according to an exemplary embodiment.

Fig. 3 is a flowchart of a service processing method according to an exemplary embodiment.

Fig. 4 is a flow chart of another service processing method provided by an exemplary embodiment.

Fig. 5 is a flow chart of another service processing method provided by an exemplary embodiment.

Fig. 6A is a block diagram illustrating a code scanning payment architecture according to an exemplary embodiment.

FIG. 6B is a block diagram of another code-scanning payment architecture, as provided by an example embodiment.

Fig. 7 is a schematic diagram of an order code based payment according to an exemplary embodiment.

Fig. 8 is a schematic structural diagram of an apparatus according to an exemplary embodiment.

Fig. 9 is a block diagram of a service processing device according to an exemplary embodiment.

Fig. 10 is a schematic structural diagram of another apparatus provided in an exemplary embodiment.

Fig. 11 is a block diagram of another service processing device provided in an example embodiment.

Fig. 12 is a schematic structural diagram of another apparatus provided in an exemplary embodiment.

Fig. 13 is a block diagram of another service processing device provided in an example embodiment.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of one or more embodiments of the specification, as detailed in the claims which follow.

It should be noted that: in other embodiments, the steps of the corresponding methods are not necessarily performed in the order shown and described herein. In some other embodiments, the method may include more or fewer steps than those described herein. Moreover, a single step described in this specification may be broken down into multiple steps for description in other embodiments; multiple steps described in this specification may be combined into a single step in other embodiments.

Blockchains are generally divided into three types: public chain (Public Blockchain), private chain (PrivateBlockchain) and alliance chain (Consortium Blockchain). In addition, there are various types of combinations, such as private chain + federation chain, federation chain + public chain, and other different combinations. The most decentralized of these is the public chain. The public chain is represented by bitcoin and ether house, and the participators joining the public chain can read the data record on the chain, participate in transaction, compete for accounting right of new blocks, and the like. Furthermore, each participant (i.e., node) is free to join and leave the network and perform related operations. Private chains are the opposite, with the network's write rights controlled by an organization or organization and the data read rights specified by the organization. Briefly, a private chain can be a weakly centralized system with strictly limited and few participating nodes. This type of blockchain is more suitable for use within a particular establishment. A federation chain is a block chain between a public chain and a private chain, and "partial decentralization" can be achieved. Each node in a federation chain typically has a physical organization or organization corresponding to it; participants jointly maintain blockchain operation by authorizing to join the network and forming a benefit-related alliance.

Whether public, private, or alliance, may provide the functionality of an intelligent contract. An intelligent contract on a blockchain is a contract that can be executed on a blockchain system triggered by a transaction. An intelligent contract may be defined in the form of code.

Taking the ethernet as an example, the support user creates and invokes some complex logic in the ethernet network, which is the biggest challenge of ethernet to distinguish from bitcoin blockchain technology. The core of the ethernet plant as a programmable blockchain is the ethernet plant virtual machine (EVM), each ethernet plant node can run the EVM. The EVM is a well-behaved virtual machine, which means that a variety of complex logic can be implemented through it. The user issuing and invoking smart contracts in the etherhouse is running on the EVM. In fact, what the virtual machine directly runs is virtual machine code (virtual machine bytecode, hereinafter referred to as "bytecode"). The intelligent contracts deployed on the blockchain may be in the form of bytecodes.

For example, as shown in fig. 1A, after Bob sends a transaction containing information to create an intelligent contract to the ethernet network, the EVM of node 1 may execute the transaction and generate a corresponding contract instance. The "0 x6f8ae93 …" in fig. 1 represents the address of the contract, the data field of the transaction holds the byte code, and the to field of the transaction is empty. After agreement is reached between the nodes through the consensus mechanism, this contract is successfully created and can be invoked in subsequent procedures. After the contract is created, a contract account corresponding to the intelligent contract appears on the blockchain and has a specific address, and the contract code is stored in the contract account. The behavior of the intelligent contract is controlled by the contract code. In other words, an intelligent contract causes a virtual account to be generated on a blockchain that contains a contract code and an account store (Storage).

As shown in fig. 1B, still taking an ethernet house as an example, after Bob sends a transaction for invoking an intelligent contract to the ethernet house network, the EVM of a certain node may execute the transaction and generate a corresponding contract instance. The from field of the transaction in FIG. 1B is the address of the account of the initiator of the transaction (i.e., Bob), the "0 x6f8ae93 …" in the to field represents the address of the smart contract being invoked, and the value field is the value in EtherFang that is kept in the data field of the transaction as the method and parameters for invoking the smart contract. The intelligent contract is independently executed at each node in the blockchain network in a specified mode, and all execution records and data are stored on the blockchain, so that after the transaction is completed, transaction certificates which cannot be tampered and cannot be lost are stored on the blockchain.

After executing Bob-initiated transaction, a node in the blockchain network generates corresponding receipt (receipt) data for recording receipt information related to the transaction. In this way, information regarding the results of the execution of the transaction may be obtained by querying the receipt of the transaction. Taking the ether house as an example, the receipt data obtained by the node executing the transaction may include the following:

a Result field indicating the execution Result of the transaction;

a Gas used field representing a Gas value consumed by the transaction;

a Logs field for representing a Log generated by the transaction, wherein the Log may further comprise a From field for representing an account address of an initiator of the call, a To field for representing an account address of an object (such as a smart contract) To be called, a Topic field for representing a subject of the Log, a Log data field for representing Log data, and the like;

an Output field, representing the Output of the transaction.

It should be noted that the type of the request initiated on the blockchain by the user accessing the blockchain may specifically refer to a transaction (transaction) adopted in a conventional blockchain. Of course, the type of the request initiated on the blockchain by the user accessing the blockchain may be other than a transaction, and other forms of instructions, messages, and the like with a standard data structure may also be used. In the following embodiments, a request initiated on a blockchain by a user accessing the blockchain will be described as an example of a transaction.

In the service processing process, the service response server can establish an association relationship with the service participants to provide corresponding service support for the service participants, and the service response server configures corresponding service basic information for the service participants to use when processing the service after establishing the association relationship. When a service to be processed occurs, a service participant provides service supplementary information (corresponding to the service to be processed) for the service to be processed, a service requester acquires the service supplementary information and the service basic information, and the service participant interacts with a service response server based on the acquired information (the service supplementary information and the service basic information) to complete a processing process of the service to be processed. In the related art, when a pending service exists between a service requester and a service participant, the service participant can output service supplementary information of the pending service and service basic information of the service participant through a service participant client in the form of a service graphic code. For example, after the service graph code is generated by the service participant client, the service participant may display the generated service graph code to the service requester through the service participant client. Then, the service requester can analyze the graphic code through the service requester client to obtain service basic information and service supplementary information, and further implement the service processing process of the service to be processed.

In practical application, for the same service, there may exist a plurality of service response servers capable of providing service support to a service participant, that is, the service participant may establish an association relationship with the plurality of service response servers, and each associated service response server configures corresponding service basic information for the service participant client. Meanwhile, each service response server has a corresponding service requester client, and the service requester client can complete service processing through service basic information configured by the service response server matched with the service requester client. In this case, corresponding service graphic codes may be generated for each piece of service basic information configured by each service response server and the service supplementary information provided by the service participants, respectively (that is, the service supplementary information in the service graphic codes is the same, but the service basic information is different). In other words, each service graphic code corresponds to a service response server one to one. Then, when the service requester needs to initiate service processing related to the service participant, the service requester can select a service graphic code according to actual requirements, and scan by using a service requester client corresponding to the selected service graphic code to complete the service processing.

However, in the above scenario, when a service participant establishes an association relationship with a plurality of service response servers, a corresponding service graph code needs to be generated for the service basic information configured by each service response server, which results in higher cost and low efficiency.

Taking an application scenario of the order code of the merchant as an example, after a user (a service requester) selects a commodity to be purchased from the merchant (a service participant), the merchant generates an order code (a service graphic code; for example, an order two-dimensional code or an order bar code) of an order to be paid (a service to be processed) for the commodity selected by the user through a merchant client (a service participant client), where the order code includes order receiving information (service basic information) of the merchant on a corresponding payment platform (a service response server) and order information (service supplementary information) of the order to be paid. The user uses a payment client (such as a mobile phone, namely a service requester client) provided with a mobile payment App to scan order codes displayed by a merchant, the mobile payment App obtains order receiving information and order information of the merchant by analyzing the order codes and displays the order receiving information and the order information on an App interface to be confirmed by the user, the user can submit a payment application after confirming that the order receiving information and the order information of the merchant are correct, and the mobile payment App is in butt joint with a payment platform to complete a subsequent payment process.

The same merchant may cooperate with multiple different payment platforms (e.g., with payment platforms such as a paypal, wechat, etc.), each of which may assign corresponding billing information (e.g., an account, an identification number, a payment platform name, an access address of the payment platform, etc. assigned to the merchant) to the merchant. Then, when the merchant supports multiple payment platforms, the merchant needs to generate a corresponding order code according to the order receiving information distributed by each payment platform and the order information generated by the merchant, so that the merchant can display the order code to the user. For example, a merchant may present an order code to a user via a merchant client for a user to pay for the code. Since the mobile payment apps are usually associated with the payment platforms (that is, each payment platform develops a corresponding mobile payment App), the user needs to select an order code supported by the mobile payment apps installed by the user to scan to complete the payment.

Therefore, when the merchant is in butt joint with the plurality of payment platforms, the order receiving information configured for each payment platform needs to generate a corresponding order code to be displayed to the user by the merchant, so that the cost in the payment process is high, the user operation is complex, the efficiency is low, and the user experience is not favorably improved.

The present specification aims to provide a service processing scheme based on a graphic code, which can merge the service graphic codes corresponding to the service terminals corresponding to each service into a service graphic code supporting interoperability under the condition that the same service participant client establishes an association relationship with a plurality of service response service terminals, so that each service requester can implement the service processing related to the service participant client by scanning the service graphic code supporting interoperability, thereby reducing the cost, simplifying the user operation, and improving the service processing efficiency.

Fig. 2 is a schematic diagram of an architecture of a business processing system according to an exemplary embodiment. As shown in fig. 2, the system may include a server 22, a network 22, a number of electronic devices such as a cell phone 23, a cell phone 24, a PC25, and a PC 26.

The server 22 may be a physical server comprising a stand-alone host, or the server 22 may be a virtual server hosted by a cluster of hosts. In operation, the server 22 serves as a storage device for the business basic information of the individual business participants to be verified for querying. In one embodiment, the server 22 may be a container platform server for business basic information, so as to dynamically maintain business basic information of each business participant client. In another embodiment, the server 22 may be a blockchain link point, so that the service basic information of each service participant client is issued to the blockchain for verification.

Handsets 23-24 and PCs 25-26 are just two types of electronic devices that can be used by a service participant or a service requester. In practice it is obvious that also electronic devices of the type such as: tablet devices, notebook computers, Personal Digital Assistants (PDAs), wearable devices (e.g., smart glasses, smart watches, etc.), etc., which are not limited by one or more embodiments of the present disclosure. In the operation process, the electronic equipment can be used as a service participant client used by a service participant or a service requester client used by a service requester. The service response server establishes an association relationship with the service participant, configures service basic information for the service participant, and acquires the configured service basic information by the service requester client (when a service to be processed exists between the service requester client and the service participant) and completes service processing based on the service basic information and service supplementary information provided by the service participant client.

And the network 22 for interaction between the various electronic devices and the server 22 may include various types of wired or wireless networks. In one embodiment, the Network 22 may include the Public Switched Telephone Network (PSTN) and the Internet. Meanwhile, the electronic devices such as the mobile phones 23-24 and the PCs 25-26 can also carry out communication interaction through the network 22.

As can be seen from the above architecture, the service processing system provided in this specification includes: the system comprises a service participant client, a service requester client and a storage device.

The service participant client generates a service graphic code according to service supplementary information of a service to be processed and an identity of the service participant, the service participant is associated with at least one service response server, each associated service response server is configured with corresponding service basic information aiming at the service participant, and the mapping relation between the service basic information and the identity, which are generated by each associated service response server for the service participant, is uploaded to a storage device for storage;

the service requester client analyzes the service graphic code to obtain the identity, and initiates a query request aiming at the service participant client to a storage device based on the identity so that the storage device searches candidate service basic information corresponding to the identity in the query request according to the mapping relation; and acquiring target service basic information matched with the service requester client in the candidate service basic information, and processing the service to be processed based on the target service basic information and service supplementary information obtained by analyzing the service graphic code.

The following describes operations performed by each role in the business processing system.

Referring to fig. 3, fig. 3 is a flowchart of a method for processing based on services according to an exemplary embodiment. As shown in fig. 3, the method applied to the service participant client may include the following steps:

step 302, generating a service graphic code according to service supplementary information of a service to be processed and an identity of a service participant to be analyzed by a service requester client, wherein the service participant is associated with at least one service response server, each associated service response server is configured with corresponding service basic information for the service participant, and a mapping relation between the service basic information and the identity generated by each associated service response server for the service participant is uploaded to a storage device to be stored.

In this embodiment, when the service request party client parses the service graph code to obtain the identity, the identity is submitted to a storage device by the service request party client through a query request for the service participant client, so that the storage device searches candidate service basic information corresponding to the identity according to the mapping relationship, and the service basic information adopted by the service request party client when processing the service to be processed based on the service supplementary information obtained by parsing the service graph code is the service basic information matched with the service request party client in the candidate service basic information. The specific process of the above-mentioned service processing will be described in detail below.

In this embodiment, taking an application scenario of a merchant order code as an example, the service participant includes a merchant (that is, the service participant client includes a merchant client), the service requester includes a payer (that is, the service requester client includes a payment client), the service to be processed includes an order to be paid, the service supplementary information includes order information of the order to be paid, the service response server associated with the merchant client includes a payment platform server, and the service basic information configured by each payment platform server for the merchant includes order receiving information. For example, the order information may include a transaction amount, a transaction time, a transaction currency, transaction details, etc. of the order to be paid.

In this embodiment, the storage device is a container platform server for service basic information, so as to dynamically maintain the service basic information of each service participant. Or the storage device is a block chain link point, so that the service basic information of each service participant is issued to the block chain for storage; in other words, the mapping relationship between the business basic information and the identity involved in the business is issued to the blockchain for storage. In this case, the mapping relationship stored in the storage device may be understood as a mapping relationship of the blockchain storage certificate. For example, the mapping relationship may be packaged into a transaction by the service participant client or a service response server associated with the service participant client as a block chain client in point-to-point connection with the block chain, so that the transaction is submitted to the block chain node to verify the mapping relationship by the block chain node.

Referring to fig. 4, fig. 4 is a flowchart illustrating another method for processing based on services according to an exemplary embodiment. As shown in fig. 4, the method applied to the service requester client may include the following steps:

step 402, analyzing a service graphic code generated by a service participant client to obtain service supplementary information of a service to be processed and an identity of the service participant, wherein the service supplementary information is included in the service graphic code, the service participant is associated with at least one service response server, each associated service response server is configured with corresponding service basic information for the service participant, and a mapping relation between the service basic information and the identity, which is generated for the service participant by each associated service response server, is uploaded to a storage device for storage.

In this embodiment, the service response server provides support of a certain type of service to the service participants, and after the service participants and the service response server establish an association relationship, the service response server configures service basic information to the service participants, where the service basic information is a part of information that needs to be used when the service is implemented. And the service basic information is usually fixed. Then, when there is a need for implementing the service between the service requester and the service participant, the service supplementary information of the service generally changes dynamically according to the actual situation of the service, and needs to be provided by the service participant in real time. The service requester can implement service processing based on the service basic information configured by the service response server and the service supplementary information provided by the service participant through the service requester client matched with the service response server.

For example, in the application scenario of the merchant order code, the service requester includes a payer (i.e., the service requester client includes a payment client), the service graph code includes the order code, the service participant client includes a merchant client, the service response server associated with the merchant client includes a payment platform server, and each payment platform server is configured with corresponding order receiving information (i.e., service basic information; for example, account information of the merchant client) for the merchant client.

The merchant establishes an association with the payment platform by registering with the payment platform. The payment platform can allocate corresponding account, identification number and other receipt information to the merchant as service basic information of the payment service. Then, when the user purchases the commodity from the merchant and then makes an order, the merchant provides order information, and the user can interact with the payment platform through the mobile payment App (installed in the electronic equipment of the user) based on the order receiving information and the order information, so that the business of paying the fee in the account registered on the payment platform by the merchant is completed.

In this embodiment, the service basic information of each service participant can be recorded by the storage device. The service participant can register with the storage device through the service participant client to obtain the unique identity. Then, the storage device may store a mapping relationship between the identity of the service participant and the service basic information of the service participant.

When the storage device is a container platform server, the service participant can use the service participant client to register with the container platform server to obtain the unique identity in the container platform. Then, the container platform server may store a mapping relationship between the identity of the service participant and the service basic information of the service participant.

When the storage device is a blockchain node, the service participant can register with the blockchain using the service participant client to obtain a unique identity. The blockchain may then be used to verify a mapping between the identity of a service participant and the service infrastructure information of that service participant. Then, after configuring the service basic information to the service participant, the service response server may package a transaction including the service basic information and the identity of the service participant, and initiate the transaction to the block link point, so that the block link point stores the mapping relationship (after consensus) between the identity and the service basic information included in the transaction to the block link.

For example, in the bitcoin blockchain model, a service participant may register with the blockchain using a service participant client to obtain a wallet address as its own identity. Then, when the service basic information corresponding to the wallet address is certified, the service basic information can be packaged into the block, and an index relationship is established between the service basic information and the wallet address, so that a subsequent block chain node can inquire the service basic information according to the wallet address.

As another example, in the blockchain model for an ethernet fab, a business participant can register with the blockchain using a business participant client to obtain an account address as its identity. Then, when the business basic information corresponding to the account address is verified, the business basic information can be stored in the account corresponding to the account address, so that the subsequent block link node can query the business basic information according to the account address.

Based on the above configuration of the storage device, the service graphic code of the service participant client is not used for recording the service basic information and the service supplementary information as in the related art, but is used for recording the identity and the service supplementary information of the service participant. Then, the service requester client can obtain the identity of the service participant by scanning the service graphic code and then analyzing the identity, and further query the service basic information of the service participant to the block chain through the identity, so that the service processing is performed by using the service basic information supported by the service participant client in the service basic information of the service participant.

Step 404, initiating a query request for the service participant to the storage device based on the identity, so that the storage device searches candidate service basic information corresponding to the identity in the query request according to the mapping relationship.

In this embodiment, the service graph code generated by the service participant may also be recorded with information for accessing the storage device. When the storage device is a block chain node, the address of at least one block chain node can be recorded in the service graphic code so that the service requester client can obtain the address and then point-to-point connect with the block chain node. Or, the service graphic code may record an index of a block chain (for example, an ID of the block chain or any other index information) that is connected to the service graphic code, so that the service requestor client may analyze the service graphic code to obtain the index, and then access the corresponding block chain. Of course, the information for accessing the block chain may also be configured in the service request client corresponding to each service response server, for example, may be written in an installation package of the service request client.

When the storage device is a container platform server, in one case, the access address of the container platform server can be recorded in the service graphic code; in another case, the access address of the container platform server may also be configured in the service request client corresponding to each service response server, for example, the access address may be written in an installation package of the service request client.

Step 406, obtaining target service basic information matched with the service requester client in the candidate service basic information, and processing the service to be processed based on the target service basic information and service supplementary information obtained by analyzing the service graphic code.

In this embodiment, the mapping relationship between the service basic information and the corresponding identity of each service participant is uploaded to the storage device for recording. Therefore, the storage device can find out the service basic information corresponding to the identity identifier contained in the query transaction as the candidate service basic information according to the recorded mapping relation.

In one case, the storage device may identify target service basic information matched with the service requester client from the candidate service basic information, and return the identified target service basic information to the sender of the query request (i.e., the service requester client), so that the service requester client may receive the target service basic information returned by the storage device to obtain the target service basic information. Wherein, in case the storage device is a block link point, the logic identifying the target service basic information may be fixed into a chain code so that the logic is directly executed by the storage device node. Alternatively, a recognition intelligent contract for business basis information may be deployed on a storage device with logic declared in the recognition intelligent contract that recognizes the target business basis information. Then, a contract address identifying the intelligent contract may be recorded in the to field of the query transaction (at which time the query request belongs to a transaction in the blockchain), thereby causing the storage device node to invoke the identify intelligent contract execution logic to identify the target business basis information.

In another case, after the storage device node obtains the candidate service basic information by querying, the candidate service basic information can be directly returned to the service requester client. Then, the service requester client may receive the candidate service basic information returned by the storage device, and identify the service basic information matched with itself among the candidate service basic information as the target service basic information.

And aiming at the logic for identifying the target service basic information, when the service response server configures the service basic information, the service response server can record the self server identification in the service basic information. In other words, the service end identifier of the service end configured with any service basic information is recorded in any service basic information. Based on the setting of the service basic information, the service basic information recorded with the target service end identification can be searched in the candidate service basic information, the searched service basic information is used as the target service basic information, and the target service end identification is the service end identification of the service response service end corresponding to the service requester client. In the case that the target service basic information is identified by the storage device, a client identifier of a sender (service requester client) may be recorded in the query request, so as to determine a server identifier corresponding to the client identifier.

In this embodiment, when the service participant client provides the service supplementary information to the service requester client, there may be a possibility that the service supplementary information is maliciously tampered. Accordingly, the service supplementary information can be verified through the digital signature. And storing the mapping relation between the public key of the service participant client and the identity of the service participant client into a storage device. The storage process may refer to the process of storing the mapping relationship between the service basic information and the identity identifier, and is not described herein again.

As an exemplary embodiment, when the service participant client generates the service graphic code, the service participant client may perform hash operation on the service supplementary information and the identity to obtain an information digest, then perform signature on the information digest through a private key of the client to obtain a digital signature, and record the digital signature in the service graphic code. Then, before processing the service to be processed, a public key corresponding to the identity included in the query request and returned by the storage device node may be received, and digital signature verification may be performed on the digital signature obtained by analyzing the service graph code through the public key. Meanwhile, the hash operation is carried out on the service supplementary information and the identity mark obtained by analyzing the service graphic code to obtain a verification abstract. When the verification digest is inconsistent with the information digest obtained through the digital signature verification, it is indicated that the service supplementary information may be tampered, and thus, the operation of processing the service to be processed is prohibited.

Correspondingly, please refer to fig. 5, fig. 5 is a flowchart of a service processing method based on a graphic code according to an exemplary embodiment. As shown in fig. 5, the method applied to the storage device may include the following steps:

step 502, receiving a query request for a service participant initiated by a service requester client, where the query request includes an identity of the service participant, the identity is obtained by analyzing a service graphic code generated by the service participant client by the service requester client, the service participant is associated with at least one service response server, each associated service response server configures corresponding service basic information for the service participant, and the mapping relationship between the service basic information and the identity generated for the service participant by each associated service response server is uploaded to the storage device for storage.

In this embodiment, the service basic information stored on the storage device belongs to the private data of the service participant, and may be combined with a TEE (Trusted Execution Environment) to protect the privacy security of the service participant. The TEE can play a role of a black box in hardware, a code and data operating system layer executed in the TEE cannot be peeped, and the TEE can be operated only through an interface defined in advance in the code. In the aspect of efficiency, due to the black box property of the TEE, plaintext data is operated in the TEE instead of complex cryptography operation in homomorphic encryption, and the efficiency of the calculation process is not lost, so that the safety and the privacy of the storage device can be greatly improved on the premise of small performance loss by combining with the TEE.

As an exemplary embodiment, the service basic information may be encrypted by using a specific symmetric key, and then the encrypted service basic information may be stored in the storage device. Then, when determining the candidate service basic information, the specific symmetric key may be obtained, and the candidate service basic information is read into the TEE, so that the candidate service basic information is decrypted in the TEE by using the specific symmetric key.

Aiming at the condition that the storage equipment is a blockchain node, the service participant client can firstly package a transaction containing service basic information to be stored, encrypt the transaction by adopting a specific symmetric key, and then submit the transaction to the blockchain node, so that the blockchain node issues the transaction to the blockchain for storing the certificate after the transaction passes consensus. Because the transaction of the certificate on the block chain is in a ciphertext form, the privacy disclosure can be effectively prevented. Correspondingly, when a transaction (corresponding to the identity identifier included in the query transaction) including the candidate service basic information is queried, the blockchain node may acquire the specific symmetric key, read the transaction into the TEE, and decrypt the transaction by using the acquired specific symmetric key to obtain the candidate service basic information included in the transaction. The specific symmetric key may be, for example, a symmetric key of the service participant (or may be other symmetric keys, such as a seal key). And the business participant client encrypts the transaction containing the business basic information through the symmetric key of the business participant so as to ensure the privacy and the safety of the business basic information. Then, after the block node inquires out the candidate service basic information, the symmetric key corresponding to the service participant and maintained in the TEE is obtained, and the transaction containing the candidate service basic information is decrypted in the TEE through the symmetric key to obtain the candidate service basic information.

After the service participant client generates the symmetric key for encryption, the symmetric key can be sent to the blockchain node for the blockchain node to maintain in the TEE. And when the client of the service participant sends the symmetric key to the block link node, the symmetric key can be encrypted through the public key of the digital envelope. Therefore, after receiving the symmetric key sent by the service participant client, the blockchain node decrypts the received symmetric key in the TEE by the private key of the digital envelope, and stores the decrypted symmetric key in the TEE.

Taking the Intel SGX technology as an example, SGX provides a bounding box, i.e., an encrypted trusted execution area in the memory, and the CPU protects data from being stolen. Taking a block link point using a CPU supporting SGX as an example, a part of an area EPC (enclosure Page Cache, Enclave Page Cache, or Enclave Page Cache) may be allocated in a Memory by using a newly added processor instruction, and data therein is encrypted by an Encryption Engine MEE (Memory Encryption Engine) in the CPU. The encrypted content in the EPC is decrypted into plaintext only after entering the CPU. Therefore, in the SGX, a user may not trust an operating System, a VMM (Virtual Machine Monitor), or even a BIOS (Basic Input Output System), and only need to trust the CPU to ensure that private data is not leaked. Thus, the TEE in this specification may be established through the SGX architecture. After the TEE is remotely certified by the key management server, the public key of the digital envelope is sent to the service participant client by the key management server, and the private key of the digital envelope is sent to the enclosure of the block chain node by the key management server. For the case that the storage device is a container platform server, the service participant client may encrypt the service basic information to be stored with a specific symmetric key, and then send a request including the encrypted service basic information and its own identity to the container platform server, so that the container platform server stores the mapping relationship between the identity and the service basic information (encrypted). Because the transaction stored on the container platform server is in a ciphertext form, privacy disclosure can be effectively prevented. Correspondingly, when the container platform server side inquires the candidate service basic information, the specific symmetric key can be obtained, the candidate service basic information is read into the TEE, and the obtained specific symmetric key is adopted to decrypt the candidate service basic information. The specific form of the specific symmetric key is similar to that described above, and is not described herein again.

Step 504, searching candidate service basic information corresponding to the identity included in the query request according to the mapping relationship, so that the service requester client obtains target service basic information matched with the service requester client in the candidate service basic information, and processing the service to be processed based on the target service basic information and service supplementary information of the service to be processed, which is obtained by analyzing the service graph code.

In this embodiment, when the service participant client provides the service supplementary information to the service requester client, there may be a possibility that the service supplementary information is maliciously tampered. Accordingly, the service supplementary information can be verified through the digital signature. And storing the mapping relation between the public key of the service participant and the identity of the service participant in a storage device. The storage process may refer to the process of the mapping relationship between the certificate storing service basic information and the identity identifier, and is not described herein again.

As an exemplary embodiment, when the service participant client generates the service graphic code, the service participant client may perform hash operation on the service supplementary information and the identity to obtain an information digest, then perform signature on the information digest through a private key of the service participant to obtain a digital signature, and record the digital signature into the service graphic code. Then, the storage device node may obtain a public key corresponding to the identity included in the query request, and return the public key to the service requester client, so that the service requester client performs digital signature verification on a digital signature obtained by analyzing the service graph code through the public key. Meanwhile, the service request side client side carries out Hash operation on the service supplementary information and the identity mark obtained by analyzing the service graphic code to obtain a verification abstract. When the verification digest is inconsistent with the information digest obtained through digital signature verification, the service supplementary information is possibly tampered, and the service requester client can forbid executing the operation of processing the service to be processed.

Further, the public key and the private key used by the digital signature can be modified by the business participants. When the service participant client obtains the updated update private key and the update private key after update, a key update request (including the update public key) for the public key corresponding to the identity of the service participant can be initiated to the storage device. Meanwhile, only the service participants can be set to have the authority of modifying the public and private keys used by the digital signature. Then, when the service participant uses the service participant client to initiate a key update request to the storage device, the service participant may use its own private key (original private key, not the update private key) to digitally sign the key update request. Then, after receiving the key update request, the storage device node performs digital signature verification by using the public key (original public key) of the service participant, and when the key update request is verified to be digitally signed by the private key of the service participant, the public key corresponding to the identity of the service participant can be updated to the update public key included in the key update request.

Besides, the service basic information of the service participants can be updated. For example, it can be set that after the confirmation of the service participant is obtained, the service basic information of the service participant can be updated; or, when a certain service basic information of the service participant needs to be updated, the confirmation of the service participant and the service response server configured with the service basic information needs to be obtained at the same time. Wherein, the updating comprises adding, deleting, modifying service information and the like.

Similarly, the update of the service basic information can be realized by initiating an information update request (including the updated service basic information and the identity of the service participant client) for the service basic information of the service participant to the storage device. The meaning of "confirmation" may be expressed by means of a digital signature. Then, after receiving the information updating request, the storage device, for the first case of updating the service basic information: when the information updating request is digitally signed by the private key of the service participant (which indicates that the confirmation of the client of the service participant is obtained), the service basic information corresponding to the identity of the service participant in the mapping relation stored in the storage device is updated to be the updated service basic information. For the second case of updating the service basic information: when the information updating request is digitally signed by a private key of a service participant and a private key of any service response server associated with the service participant (namely, the private key is multiply signed by the service participant client and the any service response server), the service basic information configured by the any service response server for the service participant client is updated to the updated service basic information.

It should be noted that, for the detailed process of the service processing method, reference may be made to the embodiment shown in fig. 4, which is not described herein again.

As can be seen from the above embodiments, by introducing a storage device for recording the service basic information of each service participant, the service graphic codes corresponding to each service response server can be merged into one service graphic code supporting interoperability under the condition that the same service participant client establishes an association relationship with a plurality of service response servers, so that each service requester can obtain the service basic information and the service supplementary information by scanning the service graphic code supporting interoperability, and further implement the service processing related to the service participant, thereby reducing the cost, simplifying the user operation, and improving the service processing efficiency. The service graphic code supporting the interoperability only needs to include the identity identifier allocated to the service participant by the storage device, and does not need to include service basic information allocated to the service participant by each service response server. On one hand, the service graphic code supporting the interoperability contains relatively less information, which is beneficial to improving the efficiency of generating the service graphic code and the accuracy and speed of analyzing the service graphic code by the service requester client, thereby improving the user experience. On the other hand, the storage device only needs to execute query operation aiming at the service basic information, and does not need to execute complex operations related to data processing, such as generating a service graphic code, aggregating a plurality of service graphic codes, assisting a service requester client to implement service processing and the like, so that more processing resources are avoided being occupied; therefore, the smooth operation of the service can be ensured under the condition of low performance requirement on the storage device.

Meanwhile, the service basic information configured by each service response server is recorded through the storage device, and the service basic information configured by each service response server does not need to be combined into one graphic code, so that the original information format of the service basic information configured by each service response server can be reserved, each service response server is allowed to generate the service basic information according to the respective information format, and differentiated services are provided for service participants.

For convenience of understanding, the following describes the technical solution of the present specification in detail by taking an application scenario of the merchant order code as an example.

Referring to fig. 6A, fig. 6A is a schematic diagram of a code scanning payment architecture according to an exemplary embodiment. As shown in fig. 6A, the architecture includes a blockchain node 60 (as a storage device), a merchant client 61 used by a merchant, a payment platform server 62 of a payment platform, and a payment client 63 used by a user. The merchant client 61, the payment platform server 62 and the payment client 63 may all access the bill receiving information of the merchant certified on the blockchain through the merchant identifier of the merchant. For the receipt information of the merchant (for example, an account, an identification number, a name of the payment platform, an access address of the payment platform, and the like allocated to the merchant by the payment platform), the merchant or the payment platform may be used as an execution main body to package a transaction including the receipt information and the merchant identification, and initiate the transaction to the block link point, so that the block link point stores the mapping relationship between the merchant identification and the receipt information included in the transaction (after the common identification) onto the block link. The process of privacy protection for the order receiving information may refer to the embodiment shown in fig. 5.

For example, in the blockchain model of bitcoin, a merchant client may obtain a wallet address as its merchant identification by registering with the blockchain. Then, when the receipt information corresponding to the wallet address is stored, the receipt information can be packaged into the block, and an index relationship is established between the receipt information and the wallet address, so that the subsequent block chain node can inquire the receipt information according to the wallet address. When the mapping relation between the merchant identification and the order receiving information is updated, the index relation is updated.

As another example, in the blockchain model of etherhouses, a merchant may register with the blockchain using a merchant client to obtain an account address as its merchant identification. Then, when the receipt information corresponding to the account address is stored, the receipt information can be stored in the account corresponding to the account address, so that the subsequent block chain node can query the receipt information according to the account address. For example, in an ethernet house or a blockchain model derived based on the architecture of the ethernet house, an external account, a contract account, and the like may be included. An external account is typically owned by the user (individual or organization), and is directly controlled by the user, also referred to as a user account; the contract account corresponds to the intelligent contract in the blockchain and is created by the user through the external account. The structure of each type of account is similar, and may include, for example, a Nonce field, a Balance field, a Code field, a Storage field, and so on. The value of the Nonce field of each account starts from 0, and the value of the Nonce field is sequentially increased along with the transaction initiated by the corresponding account, so that the Nonce values contained in each transaction initiated by the account are different, thereby avoiding replay attack. The Balance field is used to store the Balance. The Code field is used to store the contract Code of the intelligent contract (in practical applications, only the hash value of the contract Code is usually maintained in the Code field, so the Code field is also usually called the Code hash field), and thus the Code field of the external account is usually empty. The Storage field is used for storing the value of the account at the corresponding node in the state tree. Thus, the service basic information can be stored into a Code field, a Storage field, or other customized fields of the external account. When the mapping relation between the merchant identification and the receipt information is updated, the receipt information is updated in the corresponding field of the account corresponding to the account address.

Referring to fig. 6B, fig. 6B is a block diagram of another code scanning payment architecture according to an exemplary embodiment. As shown in fig. 6B, the architecture includes a container platform server 64 (as a storage device), a merchant client 61 used by a merchant, a payment platform server 62 of a payment platform, and a payment client 63 used by a user. The merchant client 61, the payment platform server 62 and the payment client 63 may all access the order receiving information of the merchant recorded in the container platform server 64 through the merchant identifier of the merchant.

In the following, a case where a storage device is a blockchain node is explained, and the storage device is a container platform server side similarly.

Referring to fig. 7, fig. 7 is a schematic diagram illustrating payment based on an order code according to an exemplary embodiment. As shown in fig. 7, the payment process may include the steps of:

at step 702, the merchant client 61 generates an order code based on the order information, the merchant identification, and the merchant signature.

In the present embodiment, when the user selects a product to be purchased from the merchant, the merchant generates order information of an order to be paid for the product selected by the user through the merchant client 61. When the order code corresponding to the order to be paid is generated, hash operation can be carried out on order information and the merchant identification to obtain an information abstract, then the information abstract is signed through a private key of the information abstract, a digital signature is obtained, and the digital signature is recorded into the order code.

In step 704, the payment client 63 scans the order code of the merchant to obtain the merchant identifier, the order information and the merchant signature.

At step 706, payment client 63 sends a query transaction (containing a merchant identification) to block chain node 60.

In step 708, the block chain node 60 queries the recorded mapping relationship for order receipt information and the merchant public key corresponding to the merchant identifier included in the query transaction.

In step 710, the block chain node 60 returns the queried order receipt information (i.e., candidate order receipt information) and the merchant public key to the payment client 63.

In this embodiment, when the payment platform configures the order receipt information, the payment platform may record its own server identifier in the order receipt information. For example, the order receipt information includes a name of the payment platform, and the name is used as the server identifier. Based on the setting of the order receiving information, the order receiving information recorded with the target server identification can be searched in the candidate order receiving information, the searched order receiving information is used as the target order receiving information, and the target server identification is the server identification of the payment platform corresponding to the payment client.

In this embodiment, the blockchain 20 may also identify target order receipt information matching the payment client from the candidate order receipt information, and return the identified target order receipt information to the payment client 63. In this case, the payment client 63 may record its own client identification in the query transaction for determining the server identification corresponding to the client identification.

For example, the name of the payment platform a is a, the client identifier of a payment App (installed in a payment client of a user) of the payment platform is a, and if the order receiving information recorded with a is found to exist in the candidate order receiving information, the order receiving information is used as the order receiving information supported by the payment client a; otherwise, the payment client s does not support the current merchant, and the transaction is terminated.

In step 712, the payment client 63 performs digital signature verification on the merchant signature through the merchant public key.

The verification process may refer to corresponding parts of the embodiment described above with reference to fig. 4, and will not be described herein again.

When the verification passes, the payment client 63 identifies the supported order receipt information and completes the payment based on the supported order receipt information and the order information, step 714.

In this embodiment, the payment client 63 may display the order information for confirmation by the user before completing payment to the merchant based on the target order receiving information and the order information. For example, the order information is payment information such as transaction amount and transaction details of an order currently generated by the user and the merchant, and after the user completes confirmation of the order information, the user confirms submission for payment. The payment client submits a payment request instruction (including account information of the merchant and transaction amount in the order information) to the payment platform, so that the payment platform processes the payment instruction, the payment process is completed, and payment results are returned to the payment client and the merchant client.

As can be seen from the above embodiments, by introducing the blockchain for recording the order receiving information of each merchant client, the order codes corresponding to each payment platform can be merged into one order code (the merchant identifier allocated to the merchant client and the order information generated by the merchant client) supporting interoperability under the condition that the same merchant client establishes an association relationship with a plurality of payment platforms, so that each user can implement the payment service related to the merchant client by scanning the order code supporting interoperability, thereby reducing the cost, simplifying the user operation, and improving the payment efficiency. The order code supporting interoperability only contains the identity identifier distributed to the merchant by the block chain network, and does not need to contain business basic information distributed to the merchant by each business response server. On one hand, the order code supporting the interoperability contains relatively less information quantity, so that the efficiency of generating the order code is improved, the accuracy and the speed of analyzing the order code by the payment client side are improved, and the user experience is further improved. On the other hand, the block link points only need to execute query operation aiming at the service basic information, and do not need to execute complex operations related to data processing, such as order code generation, aggregation of a plurality of order codes, assistance of payment client to implement payment process and the like, so that more processing resources are avoided being occupied; therefore, the smooth operation of the service can be ensured under the condition of low performance requirement on the block link point.

Meanwhile, the order receiving information configured by each payment platform is recorded through the block chain nodes, the order receiving information configured by each payment platform does not need to be combined into one order code, the original information format of the order receiving information configured by each payment platform can be reserved, each payment platform is allowed to generate the order receiving information according to the respective information format, and therefore differentiated services are provided for merchants.

Corresponding to the above method embodiments, the present specification further provides an embodiment of a service processing apparatus.

The embodiment of the service processing device in the present specification can be applied to electronic equipment. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. Taking a software implementation as an example, as a logical device, the device is formed by reading, by a processor of the electronic device where the device is located, a corresponding computer program instruction in the nonvolatile memory into the memory for operation.

Referring to fig. 8, fig. 8 is a schematic block diagram of an apparatus according to an exemplary embodiment. As shown in fig. 8, at the hardware level, the apparatus includes a processor 802, an internal bus 804, a network interface 806, a memory 808, and a non-volatile memory 810, but may also include hardware required for other services. The processor 802 reads a corresponding computer program from the non-volatile memory 810 into the memory 808 and then runs the computer program, thereby forming a service processing apparatus on a logical level. Of course, besides software implementation, the one or more embodiments in this specification do not exclude other implementations, such as logic devices or combinations of software and hardware, and so on, that is, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or logic devices.

Referring to fig. 9, in a software implementation, the service processing apparatus applied to the service participant client may include:

a generating unit 91, configured to generate a service graphic code according to service supplementary information of a service to be processed and an identity of a service participant to be analyzed by a service requester client, where the service participant is associated with at least one service response server, each associated service response server configures corresponding service basic information for the service participant, and a mapping relationship between the service basic information and the identity, generated for the service participant by each associated service response server, is uploaded to a storage device for storage;

when the service request side client analyzes the service graphic code to obtain the identity, the identity is submitted to the storage device by the service request side client through a query request aiming at the service participant client, so that the storage device node searches candidate service basic information corresponding to the identity according to the mapping relation, and the service basic information adopted by the service request side client when processing the service to be processed based on the service supplementary information obtained by analyzing the service graphic code is the service basic information matched with the service request side client in the candidate service basic information.

Optionally, the storage device includes a block chain node, and the mapping relationship between the service basic information of the service participant client and the identity is issued to the block chain by the block chain node for storing the certificate.

Optionally, the service participant includes a merchant, the service requester includes a payer, the service to be processed includes an order to be paid, the service supplementary information includes order information of the order to be paid, the service response server associated with the merchant client includes a payment platform server, and the service basic information configured by each payment platform server for the merchant includes order receiving information.

Referring to fig. 10, fig. 10 is a schematic block diagram of an apparatus according to an exemplary embodiment. As shown in fig. 10, at the hardware level, the device includes a processor 1002, an internal bus 1004, a network interface 1006, a memory 1008, and a non-volatile storage 1010, although other hardware required for services may be included. The processor 1002 reads a corresponding computer program from the non-volatile memory 1010 into the memory 1008 and then runs the computer program, thereby forming a service processing apparatus on a logical level. Of course, besides software implementation, the one or more embodiments in this specification do not exclude other implementations, such as logic devices or combinations of software and hardware, and so on, that is, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or logic devices.

Referring to fig. 11, in a software implementation, the service processing apparatus, applied to the service requester client, may include:

the analysis unit 1101 is configured to analyze a service graph code generated by a service participant client to obtain service supplementary information of a service to be processed and an identity of the service participant, where the service participant is associated with at least one service response server, each associated service response server is configured with corresponding service basic information for the service participant, and a mapping relationship between the service basic information and the identity, generated for the service participant by each associated service response server, is uploaded to a storage device for storage;

a query unit 1102, configured to initiate a query request for the service participant to the storage device based on the identity identifier, so that the storage device searches candidate service basic information corresponding to the identity identifier in the query request according to the mapping relationship;

the service processing unit 1103 obtains target service basic information matched with the service requester client in the candidate service basic information, and processes the service to be processed based on the target service basic information and service supplementary information obtained by analyzing the service graphic code.

Optionally, the service graphic code further includes a digital signature obtained by signing an information digest through a private key of the service participant client, where the information digest is obtained by performing hash operation on the service supplementary information and the identity; before processing the service to be processed, the apparatus further includes:

a receiving unit 1104, configured to receive a public key corresponding to the identity included in the query request and returned by the storage device node, and perform digital signature verification on the digital signature obtained by analyzing the service graph code through the public key;

the abstract acquiring unit 1105 performs hash operation on the service supplementary information and the identity identifier obtained by analyzing the service graphic code to obtain a verification abstract;

a verifying unit 1106 configured to prohibit an operation of processing the service to be processed from being performed when the verification digest is inconsistent with the information digest obtained through the digital signature verification.

Optionally, the service processing unit 1103 is specifically configured to:

receiving the target service basic information returned by the storage device, wherein the target service basic information is identified and obtained from the candidate service basic information by the storage device;

or receiving the candidate service basic information returned by the storage device, and identifying the service basic information matched with the service requester client in the received candidate service basic information as the target service basic information.

Optionally, any service basic information records a service end identifier of a service response service end configured with the any service basic information; identifying the target service basic information by the following method:

searching the service basic information recorded with the target service end identification in the candidate service basic information, and taking the searched service basic information as the target service basic information, wherein the target service end identification is the service end identification of the service response service end corresponding to the service requester client.

Referring to fig. 12, fig. 12 is a schematic block diagram of an apparatus according to an exemplary embodiment. As shown in fig. 12, at the hardware level, the apparatus includes a processor 1202, an internal bus 1204, a network interface 1206, a memory 1208, and a non-volatile memory 1210, although it may also include hardware required for other services. The processor 1202 reads a corresponding computer program from the non-volatile memory 1210 into the memory 1208 and then runs the computer program, thereby forming a service processing apparatus on a logical level. Of course, besides software implementation, the one or more embodiments in this specification do not exclude other implementations, such as logic devices or combinations of software and hardware, and so on, that is, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or logic devices.

Referring to fig. 13, in a software implementation, the service processing apparatus applied to the storage device may include:

a first receiving unit 1301, configured to receive an inquiry request for a service participant, where the inquiry request is initiated by a service requester client, where the inquiry request includes an identity of the service participant, the identity is obtained by analyzing a service graphic code generated by the service participant client by the service requester client, the service participant is associated with at least one service response server, each associated service response server configures corresponding service basic information for the service participant, and a mapping relationship between the service basic information and the identity, generated by the service participant, of each associated service response server is uploaded to the storage device for storage;

the query unit 1302 searches for candidate service basic information corresponding to the identity included in the query request according to the mapping relationship, so that the service requester client obtains target service basic information matched with the service requester client in the candidate service basic information, and processes the service to be processed based on the target service basic information and service supplementary information of the service to be processed, which is obtained by analyzing the service graph code.

Optionally, the service basic information stored in the storage device is encrypted by using a specific symmetric key; the device further comprises:

a first obtaining unit 1303 that obtains the specific symmetric key;

the decryption unit 1304 decrypts the searched candidate service basic information by using the specific symmetric key in the trusted execution environment.

Optionally, the service graphic code further includes a digital signature obtained by signing an information digest through a private key of the service participant, where the information digest is obtained by performing hash operation on the service supplementary information and the identity; the device further comprises:

a second obtaining unit 1305, configured to obtain a public key corresponding to the identity included in the query request;

a returning unit 1306, configured to return the public key to the service requester client, so that the service requester client performs digital signature verification on the digital signature obtained by analyzing the service graph code through the public key, and prohibits execution of an operation of processing the service to be processed when a verification digest is inconsistent with an information digest obtained by the digital signature verification; and the verification abstract is obtained by performing hash operation on the service supplementary information and the identity mark obtained by analyzing the service graphic code by the service requester client.

Optionally, the method further includes:

second receiving unit 1307, configured to receive a key update request for a public key corresponding to the identity of the service participant, where the key update request includes an update public key;

the first updating unit 1308, when the key update request is digitally signed by the private key of the service participant, updates the public key corresponding to the identity of the service participant to the updated public key.

Optionally, the method further includes:

a third receiving unit 1309, receiving an information updating request for the service basic information of the service participant, where the information updating request includes updating the service basic information;

a second updating unit 1310, configured to update, when the information updating request is digitally signed by the private key of the service participant, service basic information corresponding to the identity of the service participant in the mapping relationship stored in the storage device to the updated service basic information;

or when the information updating request is digitally signed by the private key of the service participant and the private key of any service response server associated with the service participant, updating the service basic information configured by the any service response server for the service participant into the updated service basic information.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the various elements may be implemented in the same one or more software and/or hardware implementations of the present description.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

This description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks. In a typical configuration, a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage, quantum memory, graphene-based storage media or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

The terminology used in the description of the one or more embodiments is for the purpose of describing the particular embodiments only and is not intended to be limiting of the description of the one or more embodiments. As used in one or more embodiments of the present specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in one or more embodiments of the present description to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of one or more embodiments herein. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.

The above description is only for the purpose of illustrating the preferred embodiments of the one or more embodiments of the present disclosure, and is not intended to limit the scope of the one or more embodiments of the present disclosure, and any modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the one or more embodiments of the present disclosure should be included in the scope of the one or more embodiments of the present disclosure.

Claims

1. A business processing system comprising: the system comprises a service participant client, a service requester client and storage equipment;

the business participant client generates a business graphic code according to business supplementary information of a business to be processed and an identity of the business participant, the business participant is associated with at least one business response server, each associated business response server is configured with corresponding business basic information aiming at the business participant, and the mapping relation between the business basic information and the identity generated by each associated business response server for the business participant is uploaded to the storage device for storage;

2. A service processing method is applied to a service participant client, and comprises the following steps:

3. The method of claim 2, wherein the storage device comprises a blockchain node, and the mapping relationship between the service basic information and the identity of the service participant client is issued by the blockchain node to a blockchain for storage.

4. The method of claim 2, wherein the service participants include merchants, the service requesters include payers, the services to be processed include orders to be paid, the service supplementary information includes order information of the orders to be paid, the service response servers associated with the merchant clients include payment platform servers, and the service basic information configured by each payment platform server for the merchants includes order receipt information.

5. A service processing method is applied to a service requester client, and comprises the following steps:

6. The method of claim 5, wherein the service graphic code further comprises a digital signature obtained by signing an information digest by a private key of the service participant, wherein the information digest is obtained by performing a hash operation on the service supplementary information and the identity; before processing the service to be processed, the method further includes:

receiving a public key corresponding to the identity identifier contained in the query request and returned by the storage device, and performing digital signature verification on the digital signature obtained by analyzing the service graphic code through the public key;

performing hash operation on the service supplementary information and the identity mark obtained by analyzing the service graphic code to obtain a verification abstract;

and when the verification abstract is inconsistent with the information abstract obtained through the digital signature verification, forbidding to execute the operation of processing the service to be processed.

7. The method of claim 5, wherein the obtaining of the target service basic information matched with the service requester client in the candidate service basic information comprises:

8. The method according to claim 7, wherein any service basic information record has a server identifier of a service response server configured with said any service basic information; identifying the target service basic information by the following method:

9. The method of claim 5, wherein the storage device comprises a blockchain node, and the mapping relationship between the service basic information and the identity of the service participant client is issued by the blockchain node to a blockchain for storage.

10. The method of claim 5, wherein the service participants include merchants, the service requesters include payers, the service to be processed includes orders to be paid, the service supplementary information includes order information of the orders to be paid, the service response servers associated with the merchant clients include payment platform servers, and the service basic information configured by each payment platform server for the merchants includes order receipt information.

11. A service processing method is applied to a storage device, and comprises the following steps:

12. The method of claim 11, wherein the service basic information stored in the storage device is encrypted with a specific symmetric key; the method further comprises the following steps:

obtaining the specific symmetric key;

and decrypting the searched candidate service basic information by adopting the specific symmetric key in the trusted execution environment.

13. The method of claim 11, wherein the service graphical code further comprises a digital signature obtained by signing an information digest by a private key of the service participant, the information digest being obtained by hashing the service supplementary information and the identity; the method further comprises the following steps:

acquiring a public key corresponding to the identity contained in the query request;

returning the public key to the service requester client so that the service requester client performs digital signature verification on the digital signature obtained by analyzing the service graphic code through the public key and forbids to execute the operation of processing the service to be processed when a verification abstract is inconsistent with an information abstract obtained by the digital signature verification; and the verification abstract is obtained by performing hash operation on the service supplementary information and the identity mark obtained by analyzing the service graphic code by the service requester client.

14. The method of claim 13, further comprising:

receiving a key updating request aiming at a public key corresponding to the identity of the service participant, wherein the key updating request comprises an updating public key;

and when the secret key updating request is digitally signed by the private key of the service participant, updating the public key corresponding to the identity of the service participant into the updated public key.

15. The method of claim 11, further comprising:

receiving an information updating request aiming at the service basic information of the service participant, wherein the information updating request comprises the updated service basic information;

when the information updating request is digitally signed by a private key of the service participant, updating service basic information corresponding to the identity of the service participant in the mapping relation of the block chaining certificate into the updated service basic information;

16. The method of claim 11, wherein the storage device comprises a blockchain node, and the mapping relationship between the service basic information and the identity of the service participant client is issued by the blockchain node to a blockchain for storage.

17. The method of claim 11, wherein the service participants include merchants, the service requesters include payers, the service to be processed includes orders to be paid, the service supplementary information includes order information of the orders to be paid, the service response servers associated with the merchant clients include payment platform servers, and the service basic information configured by each payment platform server for the merchants includes order receipt information.

18. A service processing apparatus applied to a service participant client, the apparatus comprising:

19. The apparatus of claim 18, wherein the storage device comprises a blockchain node, and the mapping relationship between the service basic information and the identity of the service participant client is issued by the blockchain node to a blockchain for storage.

20. The apparatus of claim 18, wherein the business participants include merchants, the business requesters include payers, the business to be processed includes orders to be paid, the business supplementary information includes order information of the orders to be paid, the business response servers associated with the merchant clients include payment platform servers, and the business basic information configured by each payment platform server for the merchants includes order receipt information.

21. A service processing apparatus applied to a service requester client, the apparatus comprising:

22. The apparatus of claim 21, wherein the service graphical code further comprises a digital signature obtained by signing an information digest by a private key of the service participant, the information digest being obtained by hashing the service supplementary information and the identity; before processing the service to be processed, the apparatus further includes:

the receiving unit is used for receiving a public key which is returned by the storage device and corresponds to the identity identifier contained in the query request, and performing digital signature verification on the digital signature obtained by analyzing the service graphic code through the public key;

the abstract acquisition unit is used for carrying out Hash operation on the service supplementary information and the identity mark obtained by analyzing the service graphic code to obtain a verification abstract;

and the verification unit forbids to execute the operation of processing the service to be processed when the verification abstract is inconsistent with the information abstract obtained by the digital signature verification.

23. The apparatus of claim 21, wherein the service processing unit is specifically configured to:

24. The apparatus according to claim 23, wherein any service basic information records a service end identifier of a service response service end configured with the any service basic information; identifying the target service basic information by the following method:

25. The apparatus of claim 21, wherein the storage device comprises a blockchain node, and the mapping relationship between the service basic information and the identity of the service participant client is issued by the blockchain node to a blockchain for storage.

26. The apparatus of claim 21, wherein the business participants comprise merchants, the business requesters comprise payers, the business to be processed comprises orders to be paid, the business supplementary information comprises order information of the orders to be paid, the business response servers associated with the merchant clients comprise payment platform servers, and the business basic information configured by each payment platform server for the merchants comprises order receipt information.

27. A service processing device applied to a storage device comprises:

28. The apparatus of claim 27, wherein the service basic information stored in the storage device is encrypted with a specific symmetric key; the device further comprises:

a first acquisition unit that acquires the specific symmetric key;

and the decryption unit is used for decrypting the searched candidate service basic information by adopting the specific symmetric key in the trusted execution environment.

29. The apparatus of claim 27, wherein the service graphic code further comprises a digital signature obtained by signing an information digest by a private key of the service participant, the information digest being obtained by hashing the service supplementary information and the identity; the device further comprises:

the second acquisition unit is used for acquiring a public key corresponding to the identity identifier contained in the query request;

the return unit is used for returning the public key to the service requester client so that the service requester client performs digital signature verification on the digital signature obtained by analyzing the service graphic code through the public key and forbids to execute the operation of processing the service to be processed when a verification abstract is inconsistent with an information abstract obtained by the digital signature verification; and the verification abstract is obtained by performing hash operation on the service supplementary information and the identity mark obtained by analyzing the service graphic code by the service requester client.

30. The apparatus of claim 29, further comprising:

the second receiving unit is used for receiving a key updating request aiming at a public key corresponding to the identity of the service participant, wherein the key updating request comprises an updating public key;

and the first updating unit is used for updating the public key corresponding to the identity of the service participant into the updated public key when the key updating request is digitally signed by the private key of the service participant.

31. The apparatus of claim 27, further comprising:

a third receiving unit, configured to receive an information update request for service basic information of the service participant, where the information update request includes updated service basic information;

the second updating unit is used for updating the service basic information corresponding to the identity identification of the service participant in the mapping relation stored in the storage device into the updated service basic information when the information updating request is digitally signed by the private key of the service participant;

32. The apparatus of claim 27, wherein the storage device comprises a blockchain node, and the mapping relationship between the service basic information and the identity of the service participant client is issued by the blockchain node to a blockchain for storage.

33. The apparatus of claim 27, wherein the business participants comprise merchants, the business requesters comprise payers, the business to be processed comprises orders to be paid, the business supplementary information comprises order information of the orders to be paid, the business response servers associated with the merchant clients comprise payment platform servers, and the business basic information configured by each payment platform server for the merchants comprises order receipt information.

34. An electronic device, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor implements the method of any one of claims 2-4 by executing the executable instructions.

35. An electronic device, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor implements the method of any one of claims 5-10 by executing the executable instructions.

36. An electronic device, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor implements the method of any one of claims 11-17 by executing the executable instructions.

37. A computer readable storage medium having stored thereon computer instructions which, when executed by a processor, carry out the steps of the method according to any one of claims 2 to 4.

38. A computer readable storage medium having stored thereon computer instructions which, when executed by a processor, carry out the steps of the method according to any one of claims 5 to 10.

39. A computer readable storage medium having stored thereon computer instructions which, when executed by a processor, carry out the steps of the method according to any one of claims 11-17.