WO2020103557A1 - 业务处理的方法和装置 - Google Patents

业务处理的方法和装置

Info

Publication number
WO2020103557A1
WO2020103557A1 PCT/CN2019/106890 CN2019106890W WO2020103557A1 WO 2020103557 A1 WO2020103557 A1 WO 2020103557A1 CN 2019106890 W CN2019106890 W CN 2019106890W WO 2020103557 A1 WO2020103557 A1 WO 2020103557A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
service
business
signature
data block
Prior art date
Application number
PCT/CN2019/106890
Other languages
English (en)
French (fr)
Inventor
林明树
Original Assignee
阿里巴巴集团控股有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Priority to SG11202100493SA priority Critical patent/SG11202100493SA/en
Priority to EP19886106.4A priority patent/EP3885956A4/en
Publication of WO2020103557A1 publication Critical patent/WO2020103557A1/zh
Priority to US17/157,884 priority patent/US11315109B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
    • H04L9/3239—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G06F21/6245—Protecting personal data, e.g. for financial or medical purposes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits
    • G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • G06Q20/065—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits
    • G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • G06Q20/065—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
    • G06Q20/0658—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash e-cash managed locally
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/22—Payment schemes or models
    • G06Q20/223—Payment schemes or models based on the use of peer-to-peer networks
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3825—Use of electronic signatures
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3827—Use of message hashing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3829—Payment protocols; Details thereof insuring higher security of transaction involving key management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/405—Establishing or using transaction specific rules
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/12—Applying verification of the received information
    • H04L63/123—Applying verification of the received information received data contents, e.g. message integrity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/06—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols the encryption apparatus using shift registers or memories for block-wise or stream coding, e.g. DES systems or RC4; Hash functions; Pseudorandom sequence generators
    • H04L9/0643—Hash functions, e.g. MD5, SHA, HMAC or f9 MAC
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3271—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using challenge-response
    • H04L9/3273—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using challenge-response for mutual authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees

Definitions

  • One or more embodiments of this specification relate to the field of computers, and in particular, to a method and apparatus for business processing.
  • a business may involve a business initiator and one or more business related parties.
  • blockchain technology is used to store business data interacted by multiple parties in the process of business processing.
  • the business data After the business data is recorded on the blockchain network, it can prevent individual blockchain members from denying or tampering with the data.
  • One of the foundations is that everyone participates in the recording, and each blockchain member can get all the data on the blockchain network.
  • business data contains sensitive data (such as user privacy data)
  • sensitive data such as user privacy data
  • One or more embodiments of this specification describe a business processing method and device, which can use the blockchain network to store business data without causing leakage of sensitive data.
  • a method for business processing is provided.
  • the method is executed by a business initiator and includes:
  • the service confirmation response includes a first data block and first signature data
  • the first data block includes a service provider using a preset The first encoded data generated by encoding the service data, the first confirmation result, and the identification of the service related party; the first signature data is performed on the first data block using the private key of the service related party Calculated by signature;
  • the method further includes:
  • the target business is processed through the blockchain network.
  • processing of the target business through the blockchain network includes:
  • a method for business processing is provided.
  • the method is executed by business related parties and includes:
  • the service confirmation response including the first data block and the first signature data; so that the service initiator determines the confirmation result of each of the service related parties When both of them are confirmed to pass, the first data block and the first signature data of each of the business related parties and the data of the business initiator are stored through the blockchain network.
  • the method further includes:
  • a method for business processing is provided.
  • the method is executed by a blockchain network and includes:
  • the first data block includes The first coded data, the first confirmation result, and the identification of the business related party generated by the business related party encoding the business data using a preset encoding method
  • the first signature data is the private data of the business related party
  • the key is obtained by signing and calculating the first data block
  • the second data block includes second encoded data and second confirmation generated by the service initiator using the preset encoding method to encode the service data
  • the second signature data is obtained by using the private key of the service initiator to sign and calculate the second data block;
  • the first data block and the first signature data of each of the service related parties, and the second data block and the second signature data of the service initiator are stored.
  • the method further includes:
  • processing of the target business includes:
  • the method before storing the first data block and the first signature data of each of the service related parties, and the second data block and the second signature data of the service initiator, the method also includes:
  • the storing the first data block and the first signature data of each of the service related parties, and the second data block and the Second signature data including:
  • the first data block and the first signature data of each of the service-related parties, and the second data block and the second signature data of the service initiator are stored in one block.
  • a service processing device is provided.
  • the device is provided on a service initiator and includes:
  • a sending unit configured to send a business confirmation request to each business related party for the target business, where the business confirmation request includes business data
  • a receiving unit configured to receive a service confirmation response from each of the service-related parties, where the service confirmation response includes a first data block and first signature data; wherein, the first data block includes It is assumed that the first encoded data, the first confirmation result, and the identification of the business related party generated by encoding the business data in an encoding manner; the first signature data is used to encrypt the business data by using the private key of the business related party The first data block is obtained by signature calculation;
  • An encoding unit configured to encode the service data using the preset encoding method to generate second encoded data; and generate a second confirmation result;
  • a signature unit configured to use the private key of the service initiator to sign the second data block including the second encoded data, the second confirmation result, and the identifier of the service initiator to obtain second signature data;
  • a storage unit configured to determine that each of the first confirmation result received by the receiving unit and the second confirmation result generated by the encoding unit are both confirmed to pass, and store the reception unit reception through the blockchain network
  • a device for business processing is provided.
  • the device is provided to a business-related party and includes:
  • a receiving unit configured to receive a service confirmation request for a target service from a service initiator, where the service confirmation request includes service data;
  • a confirmation unit configured to generate a first confirmation result according to the service data received by the receiving unit
  • An encoding unit configured to encode the service data received by the receiving unit using a preset encoding method to generate first encoded data
  • a signature unit configured to sign the first data block containing the first confirmation result and the first encoded data using the private key of the service related party to obtain first signature data
  • a sending unit configured to send a service confirmation response to the service initiator, the service confirmation response including the first data block and the first signature data; so that the service initiator determines each of the services
  • the confirmation results of the related parties are all confirmed to pass, the first data block and the first signature data of each of the service related parties and the data of the service initiator are stored through the blockchain network.
  • a device for business processing is provided.
  • the device is set in a blockchain network and includes:
  • a receiving unit configured to receive the first data block and the first signature data of each service-related party from the service initiator of the target service, and the second data block and the second signature data of the service initiator; wherein, the The first data block includes the first encoded data generated by the business related party encoding the business data by using a preset encoding method, a first confirmation result, and the identification of the business related party; The private key of the service-related party is obtained by signing and calculating the first data block; the second data block includes a second code generated by the service initiator using the preset coding method to encode the service data Data, a second confirmation result, and the identifier of the service initiator; the second signature data is obtained by using the private key of the service initiator to sign and calculate the second data block;
  • a storage unit configured to store the first data block and the first signature data of each service-related party received by the receiving unit, and the second data block and the The second signature data.
  • a computer-readable storage medium on which a computer program is stored, and when the computer program is executed in a computer, the computer is caused to execute the method of the first aspect or the second aspect or the third aspect.
  • An eighth aspect provides a computing device, including a memory and a processor, where executable code is stored in the memory, and when the processor executes the executable code, the first aspect or the second aspect or the third aspect is implemented Aspects.
  • the business initiating party sends business data to the business related party, thereby facilitating the business related party to confirm the business, but the business related party will not directly return the business data and the confirmation result to the business initiating party.
  • the business related parties encode the business data to obtain the encoded data, and return the encoded data and the confirmation result to the business initiator.
  • the subsequent business initiator does not directly store the business data and the confirmation result in the blockchain network, but stores the encoded data
  • the confirmation result is stored as a data block in the blockchain network, and the blockchain members will not know the business data, so that when the blockchain network is used to store the business data, it will not cause the leakage of sensitive data.
  • FIG. 1 is a schematic diagram of an implementation scenario disclosed in this specification
  • FIG. 2 is a schematic diagram of a blockchain accounting implementation scenario corresponding to the implementation scenario shown in FIG. 1;
  • FIG. 3 shows a flowchart of a business processing method according to an embodiment
  • FIG. 5 shows a flowchart of a method for business processing according to another embodiment
  • FIG. 6 shows a schematic diagram of the interaction process of various members in the business process according to an embodiment
  • FIG. 8 shows a schematic block diagram of a service processing apparatus according to an embodiment
  • FIG. 9 shows a schematic block diagram of a service processing apparatus according to another embodiment
  • FIG. 10 shows a schematic block diagram of a service processing apparatus according to another embodiment
  • FIG. 11 shows a schematic block diagram of a business processing system according to an embodiment.
  • FIG. 1 is a schematic diagram of an implementation scenario of an embodiment disclosed in this specification.
  • This implementation scenario involves a fund transaction business, specifically a transfer business.
  • Figure 1 shows a simplified version of the transfer process.
  • Zhang San transfers money to Li Si in the second wallet through the first wallet.
  • the flow of funds is: first wallet (first member) ⁇ fund circulation bank (second member) ⁇ second wallet (third member).
  • blockchain accounting is introduced.
  • FIG. 2 is a schematic diagram of a blockchain accounting implementation scenario corresponding to the implementation scenario shown in FIG. 1.
  • This implementation scenario involves data recording through the blockchain during the transfer process.
  • the transaction service is initiated through the first wallet
  • the blockchain records the transaction data, and sends the recorded transaction data to all members.
  • risk scans such as anti-money laundering, anti-terrorist financing, etc.
  • These risk scans often require users' sensitive data (such as ID numbers). Therefore, a risk scan needs to be initiated during the transaction.
  • the risk scan can be initiated by any one of the first member, the second member, and the third member.
  • the service initiator is not limited to the first member.
  • each member of the funds link After the first member initiates a risk scan, each member of the funds link performs a risk scan and feeds back the scan results.
  • the detailed information of the risk scan often contains a lot of privacy information. Chain, then this information will be leaked out.
  • business data is encoded and stored on the blockchain to achieve desensitization of business information, thereby solving the problem that each member of the business link recognizes the business and is not repulsive , Does not disclose business information.
  • this implementation scenario involves a scenario where multiple members participate in a blockchain business and each member needs to recognize the business.
  • the above-mentioned multi-members may be only two, for example, one business initiator and one business related party, and the above-mentioned multi-members may also be three or more, for example, one business initiator and multiple business related parties.
  • the above-mentioned business may be a capital transaction business or a non-capital transaction business.
  • the non-fund transaction business may be a car rental business.
  • the first member may be an intermediary / platform
  • the second member is a leasing company of a car provider
  • the first member submits the information of the actual leaser to the second member in clear text to confirm whether the lease
  • the second member encodes the above information and signs the encoded data together with the confirmation result back to the first member.
  • the first member puts the desensitized information on the blockchain.
  • FIG. 3 shows a flowchart of a business processing method according to an embodiment.
  • the method is executed by a business initiator, for example, the first member in the scenario shown in FIG. 2.
  • the business processing method in this embodiment includes the following steps: Step 31, a business confirmation request is sent to each business-related party for the target business, and the business confirmation request includes business data; Step 32, from each The service-related party receives a service confirmation response, and the service confirmation response includes a first data block and first signature data; wherein, the first data block includes the service data by the service-related party using a preset encoding method to the service data
  • the first signature data is obtained by signing the first data block using the private key of the business related party ;
  • Step 33 the business data is encoded using the preset encoding method to generate second encoded data; and a second confirmation result is generated;
  • Step 34 using the private key pair of the service initiator
  • step 31 a service confirmation request is sent to each service related party for the target service, and the service confirmation request includes service data.
  • the content contained in the business data is not limited, for example, it may include the user's name, ID number, age and other private information, but it is not limited to this.
  • a service confirmation response is received from each of the service related parties, and the service confirmation response includes a first data block and first signature data; wherein, the first data block includes It is assumed that the first encoded data, the first confirmation result, and the identification of the business-related party generated by encoding the business data in an encoding manner; the first signature data is to use the private key of the business-related party to The first data block is obtained by signature calculation.
  • the preset encoding method may use any encoding method in which it is not easy to obtain original data by encoding data, for example, a hash encoding method.
  • the above first confirmation result is used to indicate whether the business related party approves the target business.
  • the above signature data can be used to prove identity.
  • Each member of the blockchain has a member ID and a pair of public and private keys.
  • the public key is public, and the public and private keys can be used to prove identity.
  • A can sign data D with private key to get signature string S;
  • A sends data D and signature string S to B;
  • B uses A's public key to verify and sign data D and signature string S if they match , Indicating that the data received by B is indeed from A.
  • step 33 the service data is encoded using the preset encoding method to generate second encoded data; and a second confirmation result is generated.
  • the service initiator and the service related parties generate coded data in the same way.
  • the first coded data and the second coded data are also applied in the same way.
  • the blockchain network can subsequently check whether the two are the same.
  • the above second confirmation result is used to indicate whether the service initiator approves the target service.
  • step 34 the second data block including the second encoded data, the second confirmation result, and the identifier of the service initiator is signed using the private key of the service initiator to obtain second signature data.
  • step 35 when it is determined that each of the first confirmation result and the second confirmation result is confirmed to be passed, the first data block and the The first signature data, and the second data block and the second signature data of the service initiator.
  • the target business may also be processed through the blockchain network. For example, recording the processing result information of the target business through the blockchain network; and sending the processing result information of the target business to each of the business related parties through the blockchain network, so that each The business related party processes the target business.
  • the business initiating party sends business data to the business related party, thereby facilitating the business related party to confirm the business, but the business related party will not directly return the business data and confirmation result to the business initiating party, but the business
  • the relevant parties encode the business data to obtain the encoded data, and return the encoded data and the confirmation result to the business initiator.
  • the subsequent business initiator does not directly store the business data and the confirmation result in the blockchain network, but stores the encoded data and the confirmation As a result, it is stored as a data block in the blockchain network, and blockchain members will not know the business data, so that when the blockchain network is used to store business data, it will not lead to the leakage of sensitive data.
  • FIG. 4 shows a flowchart of a business processing method according to another embodiment.
  • the method is performed by a business related party, for example, the second member or the third member in the scenario shown in FIG. 2.
  • the method for business processing in this embodiment includes the following steps: Step 41, receiving a business confirmation request for a target business from a business initiator, the business confirmation request includes business data; Step 42, according to the Business data to generate a first confirmation result; Step 43, encode the business data using a preset encoding method to generate first encoded data; Step 44, use the private key of the business-related party to include the first confirmation The result and the first data block of the first encoded data are signed to obtain the first signature data; Step 45, a service confirmation response is sent to the service initiator, the service confirmation response includes the first data block and The first signature data; so that when the business initiator determines that the confirmation result of each of the business related parties is confirmed to be passed, the first data of each of the business related parties is stored through the blockchain network Block and the first signature data
  • step 41 a service confirmation request for the target service is received from the service initiator, and the service confirmation request includes service data.
  • the content contained in the business data is not limited, for example, it may include the user's name, ID number, age and other private information, but it is not limited to this.
  • a first confirmation result is generated based on the business data.
  • the above first confirmation result is used to indicate whether the business related party approves the target business.
  • step 43 the service data is encoded using a preset encoding method to generate first encoded data.
  • the service initiator and the service related parties generate coded data in the same way.
  • the first coded data and the second coded data are also applied in the same way.
  • the blockchain network can subsequently check whether the two are the same.
  • step 44 the private key of the service related party is used to sign the first data block containing the first confirmation result and the first encoded data to obtain first signature data.
  • a service confirmation response is sent to the service initiator, the service confirmation response includes the first data block and the first signature data; so that the service initiator determines each of the services
  • the confirmation results of the related parties are all confirmed to pass, the first data block and the first signature data of each of the service related parties and the data of the service initiator are stored through the blockchain network.
  • the data of the service initiator includes the second data block and the second signature data of the service initiator. For details, refer to the description corresponding to FIG. 3.
  • the method further includes:
  • the business related party receives the business data from the business initiator, thereby facilitating the business related party to confirm the business, but the business related party will not directly return the business data and confirmation result to the business initiator
  • the business related parties encode the business data to obtain the encoded data, and return the encoded data and the confirmation result to the business initiator.
  • the subsequent business initiator does not directly store the business data and the confirmation result in the blockchain network, but stores the encoded data and
  • the confirmation result is stored as a data block in the blockchain network, and the blockchain members will not know the business data, so that when the blockchain network is used to store the business data, it will not cause the leakage of sensitive data.
  • FIG. 5 shows a flowchart of a business processing method according to another embodiment.
  • the method is executed by a blockchain network, which may be simply referred to as a blockchain, for example, the blockchain in the scenario shown in FIG. 2 .
  • the business processing method in this embodiment includes the following steps:
  • Step 51 Receive the first data block and the first signature data of each service related party from the service initiator of the target service, and the second data block and the second signature data of the service initiator; wherein, the first The data block includes the first coded data generated by the business related party encoding the business data by using a preset encoding method, a first confirmation result, and the identification of the business related party; the first signature data is used to utilize the business related
  • the private data of the party is obtained by signing and calculating the first data block;
  • the second data block includes second encoded data generated by the service initiator using the preset encoding method to encode the business data, The second confirmation result and the identifier of the service initiator; the second signature data is obtained by performing signature calculation on the second data block using the private key of the service initiator.
  • business initiators and business related parties can join the blockchain network in advance and become members of the blockchain network.
  • Step 52 Store the first data block and the first signature data of each of the service related parties, and the second data block and the second signature data of the service initiator.
  • the method may further include: processing the target service. For example, recording the processing result information of the target business; and, sending the processing result information of the target business to each of the business related parties, so that each of the business related parties processes the target business.
  • the method may further include:
  • step 52 may specifically include the first data block and the first signature data of each of the service related parties, and the second data block and the second signature data of the service initiator Stored in a block.
  • the blockchain network does not directly receive business data and confirmation results from the business initiator, but receives encoded data and confirmation results, and stores the encoded data and confirmation results as a data block in the block
  • the blockchain members will not know the business data, so that when the blockchain network is used to store the business data, it will not cause the leakage of sensitive data.
  • FIG. 6 shows a schematic diagram of the interaction process of various members in the business process according to an embodiment.
  • FIG. 7 shows a business process sequence diagram according to one embodiment.
  • the service link involves a first member, a second member, and a third member.
  • the first member is a service initiator, and the second member and the third member are service related parties. Permission of members, second members and third members.
  • FIG. 8 shows a schematic block diagram of a service processing apparatus according to an embodiment. As shown in FIG. 8, the device 800 includes:
  • the sending unit 81 is configured to send a service confirmation request to each service related party for the target service, where the service confirmation request includes service data;
  • the receiving unit 82 is configured to receive a service confirmation response from each of the service related parties, where the service confirmation response includes a first data block and first signature data; wherein, the first data block includes the service related party A first encoding data generated by encoding the business data by a preset encoding method, a first confirmation result, and an identification of the business related party; the first signature data is obtained by using the private key of the business related party Obtained by performing signature calculation on the first data block;
  • An encoding unit 83 configured to encode the service data by using the preset encoding method to generate second encoded data; and generate a second confirmation result;
  • the signature unit 84 is configured to use the private key of the service initiator to sign the second data block including the second encoded data, the second confirmation result, and the identifier of the service initiator to obtain second signature data;
  • the storage unit 85 is configured to determine that each of the first confirmation result received by the receiving unit 82 and the second confirmation result generated by the encoding unit 83 are both confirmed to pass, and store the The first data block and the first signature data of each service-related party received by the receiving unit 82, and the second data block and the second signature data of the service initiator.
  • the device further includes:
  • the processing unit is configured to determine that when each of the first confirmation result and the second confirmation result received by the receiving unit 82 are confirmed to pass, process the target business through the blockchain network.
  • processing unit is specifically used for:
  • the sending unit 81 sends business data to the business related parties, thereby facilitating the business related parties to confirm the business, but the business related parties will not directly return the business data and the confirmation result to the receiving unit 82, but The business related party encodes the business data to obtain the encoded data, and returns the encoded data and the confirmation result to the receiving unit 82.
  • the subsequent storage unit 85 does not directly store the business data and the confirmation result in the blockchain network, but stores the encoded data and The confirmation result is stored as a data block in the blockchain network, and the blockchain members will not know the business data, so that when the blockchain network is used to store the business data, it will not cause the leakage of sensitive data.
  • an apparatus for business processing is also provided, and the apparatus is provided at a business-related party.
  • 9 shows a schematic block diagram of a service processing apparatus according to another embodiment. As shown in FIG. 9, the device 900 includes:
  • the receiving unit 91 is configured to receive a service confirmation request for the target service from the service initiator, where the service confirmation request includes service data;
  • the confirmation unit 92 is configured to generate a first confirmation result according to the service data received by the receiving unit 91;
  • An encoding unit 93 configured to encode the service data received by the receiving unit 91 by using a preset encoding method to generate first encoded data
  • the signature unit 94 is used to sign the first data block containing the first confirmation result and the first encoded data using the private key of the service related party to obtain first signature data;
  • the sending unit 95 is configured to send a service confirmation response to the service initiator, where the service confirmation response includes the first data block and the first signature data; so that the service initiator determines each of the When the confirmation results of the business related parties are all confirmed to pass, the first data block and the first signature data of each of the business related parties and the data of the business initiator are stored through the blockchain network.
  • the receiving unit 91 is also used to receive the processing result information of the target service from the blockchain network;
  • the device also includes:
  • the processing unit is configured to process the target service according to the processing result information received by the receiving unit 91.
  • the receiving unit 91 receives business data from the business initiator, thereby facilitating the confirmation unit 92 to confirm the business, but the sending unit 95 does not directly return the business data and confirmation result to the business initiator, but The business related parties encode the business data to obtain the encoded data, and return the encoded data and the confirmation result to the business initiator.
  • the subsequent business initiator does not directly store the business data and the confirmation result in the blockchain network, but stores the encoded data and
  • the confirmation result is stored as a data block in the blockchain network, and the blockchain members will not know the business data, so that when the blockchain network is used to store the business data, it will not cause the leakage of sensitive data.
  • FIG. 10 shows a schematic block diagram of a service processing apparatus according to another embodiment. As shown in FIG. 10, the device 1000 includes:
  • the receiving unit 1001 is configured to receive the first data block and the first signature data of each service-related party, and the second data block and the second signature data of the service initiator from the service initiator of the target service;
  • the first data block includes first encoded data generated by a business-related party encoding business data using a preset encoding method, a first confirmation result, and an identification of the business-related party;
  • the first signature data is used for The private key of the service related party is obtained by signing and calculating the first data block;
  • the second data block includes a second generated by the service initiator using the preset encoding method to encode the service data The encoded data, the second confirmation result, and the identifier of the service initiator;
  • the second signature data is obtained by using the private key of the service initiator to perform signature calculation on the second data block;
  • the storage unit 1002 is configured to store the first data block and the first signature data of each service-related party received by the receiving unit 1001, and the second data block and the second data block of the service initiator The second signature data.
  • the device further includes:
  • a processing unit configured to store the first data block and the first signature data of each of the service-related parties in the storage unit 1002, and the second data block and the After the second signature data, the target service is processed.
  • processing unit is specifically used for:
  • the device further includes:
  • a verification unit configured to store the first data block and the first signature data of each of the service-related parties in the storage unit 1002, and the second data block and the Before the second signature data, check the following items:
  • the determining unit is configured to determine that the verification result of each verification obtained by the verification unit is yes.
  • the storage unit 1002 is specifically configured to store the first data block and the first signature data of each of the service-related parties received by the receiving unit 1001, and all The second data block and the second signature data of the service initiator are stored in one block.
  • the receiving unit 1001 does not directly receive service data and confirmation results from the service initiator, but receives encoded data and confirmation results, and the storage unit 1002 stores the encoded data and confirmation results as a data block in
  • blockchain members will not know the business data, so that when the blockchain network is used to store business data, it will not cause the leakage of sensitive data.
  • FIG. 11 shows a schematic block diagram of a business processing system according to an embodiment. As shown in Figure 11, the processing of the system includes:
  • the first member that is, the business initiator
  • the data in the request includes detailed data of the transaction agreement (hereinafter collectively referred to as BIZ_DATA).
  • the receiving module of the first member's blockchain bridging system sends the data to all members on the transaction link in the agreed format through the sending module.
  • the sent data includes BIZ_DATA.
  • the receiving module of the blockchain bridge system of the second member receives the request and forwards the data to the business of the second member
  • the system confirms the transaction and the received data includes BIZ_DATA.
  • the confirmation result (hereinafter collectively referred to as RESULT) is returned to the receiving module of the blockchain bridge system.
  • the receiving module transmits the BIZ_DATA and the result to the desensitization module for processing.
  • the desensitization module of the second member's blockchain bridge system performs hash processing on the BIZ_DATA (other encoding methods can also be used) to calculate the corresponding hash code (hash code) . Then, pass the hash code and RESULT to the signature module.
  • the signature module of the second member's blockchain bridging system uses the hash code, RESULT and the member ID preset by the second member as a data block (hereinafter collectively referred to as CHECK_RESULT) according to the agreed format, and then uses the private Key calculation signature (hereinafter collectively referred to as SIGNATURE).
  • the sending module of the second member's blockchain bridge system returns the CHECK_RESULT and SIGNATURE to the first member.
  • the sending module of the first member's blockchain bridging system receives the CHECK_RESULT and SIGNATURE returned by all members on the transaction link, it parses and checks whether the transaction confirmation result (the RESULT) in all received CHECK_RESULT They are all confirmed to pass. If the confirmation is passed, continue to call the access module.
  • the access module of the first member's blockchain bridging system sends the CHECK_RESULT and SIGNATURE of all members on the transaction link to the blockchain for processing.
  • the verification module in the blockchain performs the following verification: parses all CHECK_RESULTs, the parsed data includes the hash code, RESULT, and member ID; verifies all the member IDs and all members on the transaction link Whether the IDs match; check whether the hash codes of each member are exactly the same; check each pair of CHECK_RESULT and SIGNATURE, get the corresponding member's public key through the member ID, and use the public key to sign and verify the CHECK_RESULT and SIGNATURE to verify whether they match.
  • the blockchain can call the business module of the blockchain for business processing.
  • a computer-readable storage medium on which a computer program is stored, and when the computer program is executed in a computer, the computer is caused to execute the description described in any of FIGS. 3 to 5 Methods.
  • a computing device including a memory and a processor, where executable code is stored in the memory, and when the processor executes the executable code, the implementation is combined with FIG. 3 to FIG. 5 Any of the methods described.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Computer Security & Cryptography (AREA)
  • Accounting & Taxation (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Finance (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • Computing Systems (AREA)
  • Software Systems (AREA)
  • Power Engineering (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Databases & Information Systems (AREA)
  • Medical Informatics (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Telephonic Communication Services (AREA)

Abstract

一种业务处理的方法和装置，业务发起方执行的方法包括：针对目标业务向各业务相关方发送业务确认请求，业务确认请求中包括业务数据（31）；从每个业务相关方接收业务确认应答，业务确认应答中包括第一数据块和第一签名数据；其中，第一数据块包括由业务相关方采用预设编码方式对业务数据进行编码而生成的第一编码数据、第一确认结果和业务相关方的标识；第一签名数据为利用业务相关方的私钥对第一数据块进行签名计算得到的（32）；采用所述预设编码方式对所述业务数据进行编码，从而生成第二编码数据；以及生成第二确认结果（33）；利用所述业务发起方的私钥对包括第二编码数据、第二确认结果和所述业务发起方的标识的第二数据块进行签名，得到第二签名数据（34）；确定每个所述第一确认结果和所述第二确认结果均为确认通过时，通过区块链网络存储每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的所述第二数据块和所述第二签名数据（35）。该方法能够在利用区块链网络存储业务数据时，不会导致敏感数据的泄露。

Description

业务处理的方法和装置 技术领域
本说明书一个或多个实施例涉及计算机领域，尤其涉及业务处理的方法和装置。
背景技术
当前，在进行业务处理时，通常需要多方参与，例如，一项业务可以涉及一个业务发起方以及一个或多个业务相关方。随着区块链技术的发展，在业务处理的过程中利用了区块链技术存储多方交互的业务数据。
业务数据记录到区块链网络上之后，可以防止个别区块链成员抵赖或者篡改数据，其一个基础就是大家参与记录，每个区块链成员都可以拿到区块链网络上的所有数据。当业务数据中包含敏感数据时(比如用户隐私数据)，如果将敏感数据写入区块链，那么这些敏感数据就会泄露给所有区块链成员。
因此，希望能有改进的方案，能够在利用区块链网络存储业务数据时，不会导致敏感数据的泄露。
发明内容
本说明书一个或多个实施例描述了一种业务处理的方法和装置，能够在利用区块链网络存储业务数据时，不会导致敏感数据的泄露。
第一方面，提供了一种业务处理的方法，方法由业务发起方执行，并包括：
针对目标业务向各业务相关方发送业务确认请求，所述业务确认请求中包括业务数据；
从每个所述业务相关方接收业务确认应答，所述业务确认应答中包括第一数据块和第一签名数据；其中，所述第一数据块包括由业务相关方采用预设编码方式对所述业务数据进行编码而生成的第一编码数据、第一确认结果和所述业务相关方的标识；所述第一签名数据为利用所述业务相关方的私钥对所述第一数据块进行签名计算得到的；
采用所述预设编码方式对所述业务数据进行编码，从而生成第二编码数据；以及生成第二确认结果；
利用所述业务发起方的私钥对包括第二编码数据、第二确认结果和所述业务发起方的标识的第二数据块进行签名，得到第二签名数据；
确定每个所述第一确认结果和所述第二确认结果均为确认通过时，通过区块链网络存储每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的所述第二数据块和所述第二签名数据。
在一种可能的实施方式中，所述方法还包括：
确定每个所述第一确认结果和所述第二确认结果均为确认通过时，通过所述区块链网络处理所述目标业务。
进一步地，所述通过所述区块链网络处理所述目标业务，包括：
通过所述区块链网络记录所述目标业务的处理结果信息；以及，
通过所述区块链网络向每个所述业务相关方发送所述目标业务的处理结果信息，以使每个所述业务相关方处理所述目标业务。
第二方面，提供了一种业务处理的方法，方法由业务相关方执行，并包括：
从业务发起方接收针对目标业务的业务确认请求，所述业务确认请求中包括业务数据；
根据所述业务数据，生成第一确认结果；
采用预设编码方式对所述业务数据进行编码，生成第一编码数据；
利用所述业务相关方的私钥对包含所述第一确认结果和所述第一编码数据的第一数据块进行签名，得到第一签名数据；
向所述业务发起方发送业务确认应答，所述业务确认应答中包括所述第一数据块和所述第一签名数据；以使所述业务发起方确定每个所述业务相关方的确认结果均为确认通过时，通过区块链网络存储每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的数据。
在一种可能的实施方式中，所述方法还包括：
从所述区块链网络接收所述目标业务的处理结果信息；
根据所述处理结果信息，处理所述目标业务。
第三方面，提供了一种业务处理的方法，方法由区块链网络执行，并包括：
从目标业务的业务发起方接收每个业务相关方的第一数据块和第一签名数据，以及所述业务发起方的第二数据块和第二签名数据；其中，所述第一数据块包括由业务相关方采用预设编码方式对业务数据进行编码而生成的第一编码数据、第一确认结果和所述业务相关方的标识；所述第一签名数据为利用所述业务相关方的私钥对所述第一数据块进行签名计算得到的；所述第二数据块包括由业务发起方采用所述预设编码方式对所述业务数据进行编码而生成的第二编码数据、第二确认结果和所述业务发起方的标识；所述第二签名数据为利用所述业务发起方的私钥对所述第二数据块进行签名计算得到的；
存储每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的所述第二数据块和所述第二签名数据。
在一种可能的实施方式中，所述存储每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的所述第二数据块和所述第二签名数据之后，所述方法还包括：
处理所述目标业务。
进一步地，所述处理所述目标业务，包括：
记录所述目标业务的处理结果信息；以及，
向每个所述业务相关方发送所述目标业务的处理结果信息，以使每个所述业务相关方处理所述目标业务。
进一步地，所述存储每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的所述第二数据块和所述第二签名数据之前，所述方法还包括：
进行如下各项核对：
核对所述业务相关方的标识和/或所述业务发起方的标识是否与所述目标业务的业务链路上的成员标识相匹配；
核对每个所述第一编码数据和所述第二编码数据是否相同；
利用每个所述业务相关方的公钥对每个所述业务相关方的所述第一数据块和所述第一签名数据进行签名验证，验证所述第一数据块和所述第一签名数据是否匹配；
利用所述业务发起方的公钥对所述业务发起方的所述第二数据块和所述第二签名数据进行签名验证，验证所述第二数据块和所述第二签名数据是否匹配；
确定所述各项核对的核对结果均为是。
在一种可能的实施方式中，所述存储每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的所述第二数据块和所述第二签名数据，包括：
将每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的所述第二数据块和所述第二签名数据存储在一个区块中。
第四方面，提供了一种业务处理的装置，装置设置于业务发起方，并包括：
发送单元，用于针对目标业务向各业务相关方发送业务确认请求，所述业务确认请求中包括业务数据；
接收单元，用于从每个所述业务相关方接收业务确认应答，所述业务确认应答中包括第一数据块和第一签名数据；其中，所述第一数据块包括由业务相关方采用预设编码方式对所述业务数据进行编码而生成的第一编码数据、第一确认结果和所述业务相关方的标识；所述第一签名数据为利用所述业务相关方的私钥对所述第一数据块进行签名计算得到的；
编码单元，用于采用所述预设编码方式对所述业务数据进行编码，从而生成第二编码数据；以及生成第二确认结果；
签名单元，用于利用所述业务发起方的私钥对包括第二编码数据、第二确认结果和所述业务发起方的标识的第二数据块进行签名，得到第二签名数据；
存储单元，用于确定所述接收单元接收的每个所述第一确认结果和所述编码单元生成的所述第二确认结果均为确认通过时，通过区块链网络存储所述接收单元接收的每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的所述第二数据块和所述第二签名数据。
第五方面，提供了一种业务处理的装置，装置设置于业务相关方，并包括：
接收单元，用于从业务发起方接收针对目标业务的业务确认请求，所述业务确认请求中包括业务数据；
确认单元，用于根据所述接收单元接收的业务数据，生成第一确认结果；
编码单元，用于采用预设编码方式对所述接收单元接收的业务数据进行编码，生成第一编码数据；
签名单元，用于利用所述业务相关方的私钥对包含所述第一确认结果和所述第一编码数据的第一数据块进行签名，得到第一签名数据；
发送单元，用于向所述业务发起方发送业务确认应答，所述业务确认应答中包括所述第一数据块和所述第一签名数据；以使所述业务发起方确定每个所述业务相关方的确认结果均为确认通过时，通过区块链网络存储每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的数据。
第六方面，提供了一种业务处理的装置，装置设置于区块链网络，并包括：
接收单元，用于从目标业务的业务发起方接收每个业务相关方的第一数据块和第一签名数据，以及所述业务发起方的第二数据块和第二签名数据；其中，所述第一数据块包括由业务相关方采用预设编码方式对业务数据进行编码而生成的第一编码数据、第一确认结果和所述业务相关方的标识；所述第一签名数据为利用所述业务相关方的私钥对所述第一数据块进行签名计算得到的；所述第二数据块包括由业务发起方采用所述预设编码方式对所述业务数据进行编码而生成的第二编码数据、第二确认结果和所述业务发起方的标识；所述第二签名数据为利用所述业务发起方的私钥对所述第二数据块进行签名计算得到的；
存储单元，用于存储所述接收单元接收的每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的所述第二数据块和所述第二签名数据。
第七方面，提供了一种计算机可读存储介质，其上存储有计算机程序，当所述计算机程序在计算机中执行时，令计算机执行第一方面或第二方面或第三方面的方法。
第八方面，提供了一种计算设备，包括存储器和处理器，所述存储器中存储有可执行代码，所述处理器执行所述可执行代码时，实现第一方面或第二方面或第三方面的方法。
通过本说明书实施例提供的方法和装置，业务发起方向业务相关方发送业务数据，从而便于业务相关方对业务进行确认，但是业务相关方不会直接返回给业务发起方业务数据和确认结果，而是业务相关方对业务数据进行编码得到编码数据，将编码数据和确认结果返回给业务发起方，后续业务发起方不是直接将业务数据和确认结果存储在区块链网络中，而是将编码数据和确认结果作为一个数据块存储在区块链网络中，区块链成员不会知道业务数据，从而能够在利用区块链网络存储业务数据时，不会导致敏感数据的泄露。
附图说明
为了更清楚地说明本发明实施例的技术方案，下面将对实施例描述中所需要使用的 附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其它的附图。
图1为本说明书披露的一个实施例的实施场景示意图；
图2为图1所示实施场景对应的区块链记账实施场景示意图；
图3示出根据一个实施例的业务处理的方法流程图；
图4示出根据另一个实施例的业务处理的方法流程图；
图5示出根据另一个实施例的业务处理的方法流程图；
图6示出根据一个实施例的业务处理过程中各成员交互过程示意图；
图7示出根据一个实施例的业务处理时序图；
图8示出根据一个实施例的业务处理的装置的示意性框图；
图9示出根据另一个实施例的业务处理的装置的示意性框图；
图10示出根据另一个实施例的业务处理的装置的示意性框图；
图11示出根据一个实施例的业务处理的系统的示意性框图。
具体实施方式
下面结合附图，对本说明书提供的方案进行描述。
图1为本说明书披露的一个实施例的实施场景示意图。该实施场景涉及资金交易业务，具体为转账业务，图1中示出精简版的转账过程，张三通过第一钱包汇款给第二钱包的李四。参照图1，资金的流向是：第一钱包(第一成员)→资金流通银行(第二成员)→第二钱包(第三成员)。为了保障资金流转的可靠性、简化对账和缩短转账周期等原因，引入了区块链记账。
图2为图1所示实施场景对应的区块链记账实施场景示意图。该实施场景涉及转账过程中通过区块链进行数据记录。参照图2，第一成员加入区块链后，通过第一钱包发起交易业务，区块链记录交易数据，并且把记录的交易数据发送给所有的成员。由于在金融监管里要求，每个资金链路的参与方都需要进行风险扫描，比如反洗钱、反恐怖融资等等，这些风险扫描往往需要用户的敏感数据(比如身份证号码)。所以，交易环节 中需要发起风险扫描，发起风险扫描的可以为第一成员、第二成员和第三成员中的任意一个，本说明书实施例中仅以第一成员作为业务发起方来举例描述，但是可以理解的是，业务发起方并不限定于第一成员。第一成员发起风险扫描后，资金链路中的各成员进行风险扫描，并反馈扫描结果。为了防止个别成员抵赖等风险，需要将各成员进行风险扫描的详细信息和扫描结果写入区块链，但是，风险扫描的详细信息里往往包含了大量隐私信息，如果将这些信息写入区块链，那么这些信息就会被泄露出去。
针对上述问题，本说明书实施例在进行业务处理时，业务数据经过编码后存储到区块链上，实现了业务信息的脱敏，从而解决业务链路的各成员对业务进行认可，并不可抵赖，不泄露业务信息。
需要说明的是，该实施场景涉及多成员参与一个区块链业务，并且需要各成员对于业务进行认可的场景。其中，上述多成员可以仅为两个，例如，一个业务发起方，一个业务相关方，上述多成员还可以为三个或更多个，例如，一个业务发起方，多个业务相关方。
此外，上述业务可以是资金交易业务，也可以是非资金交易业务。
例如，非资金交易业务可以是汽车租赁业务。该业务可以不存在中间方，第一成员可以是中介/平台，第二成员是某个汽车提供方的租赁公司，第一成员将实际租赁人的信息明文提交给第二成员进行确认是否可以租赁，然后第二成员对上述信息进行编码，并将编码数据和确认结果一起进行签名返回给第一成员。最后第一成员将脱敏的信息放到区块链上。
可以理解的是，本说明实施例业务处理的方法可以应用的实施场景有很多，只要是多成员参与一个区块链业务，并且需要各成员对于业务进行认可的场景均适用，在此不再赘述。
图3示出根据一个实施例的业务处理的方法流程图，所述方法由业务发起方执行，例如，图2所示场景中的第一成员。如图3所示，该实施例中业务处理的方法包括以下步骤：步骤31，针对目标业务向各业务相关方发送业务确认请求，所述业务确认请求中包括业务数据；步骤32，从每个所述业务相关方接收业务确认应答，所述业务确认应答中包括第一数据块和第一签名数据；其中，所述第一数据块包括由业务相关方采用预设编码方式对所述业务数据进行编码而生成的第一编码数据、第一确认结果和所述业务相关方的标识；所述第一签名数据为利用所述业务相关方的私钥对所述第一数据块进行签 名计算得到的；步骤33，采用所述预设编码方式对所述业务数据进行编码，从而生成第二编码数据；以及生成第二确认结果；步骤34，利用所述业务发起方的私钥对包括第二编码数据、第二确认结果和所述业务发起方的标识的第二数据块进行签名，得到第二签名数据；步骤35，确定每个所述第一确认结果和所述第二确认结果均为确认通过时，通过区块链网络存储每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的所述第二数据块和所述第二签名数据。下面描述以上各个步骤的具体执行方式。
首先在步骤31，针对目标业务向各业务相关方发送业务确认请求，所述业务确认请求中包括业务数据。
本说明书实施例中，对于业务数据包含的内容不做限定，例如，可以包括用户的姓名、身份证号码、年龄等隐私信息，但并不限定于此。
接着在步骤32，从每个所述业务相关方接收业务确认应答，所述业务确认应答中包括第一数据块和第一签名数据；其中，所述第一数据块包括由业务相关方采用预设编码方式对所述业务数据进行编码而生成的第一编码数据、第一确认结果和所述业务相关方的标识；所述第一签名数据为利用所述业务相关方的私钥对所述第一数据块进行签名计算得到的。
可以理解的是，上述业务相关方的数目可以为多个，也可以为一个。
上述预设编码方式可以采用任一通过编码数据不容易获取原始数据的编码方式，例如，哈希编码方式。
上述第一确认结果用于指示业务相关方是否认可该目标业务。
上述签名数据可以用于证明身份，区块链的每个成员都有一个成员ID和一对公私钥，公钥是公开的，公私钥可以用于证明身份。例如，A可以用私钥对数据D进行签名，得到签名串S；A把数据D和签名串S发送给B；B通过A的公钥，对数据D和签名串S进行验证签名，如果匹配，说明B收到的数据确实来自于A。
然后在步骤33，采用所述预设编码方式对所述业务数据进行编码，从而生成第二编码数据；以及生成第二确认结果。
可以理解的是，业务发起方与业务相关方生成编码数据的方式相同，理论上，第一编码数据与第二编码数据也应用相同，后续可以由区块链网络对二者是否相同进行核对。
上述第二确认结果用于指示业务发起方是否认可该目标业务。
再在步骤34，利用所述业务发起方的私钥对包括第二编码数据、第二确认结果和所述业务发起方的标识的第二数据块进行签名，得到第二签名数据。
签名计算的方式，前面已有描述，在此不做赘述。
最后在步骤35，确定每个所述第一确认结果和所述第二确认结果均为确认通过时，通过区块链网络存储每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的所述第二数据块和所述第二签名数据。
在一个示例中，确定每个所述第一确认结果和所述第二确认结果均为确认通过时，还可以通过所述区块链网络处理所述目标业务。例如，通过所述区块链网络记录所述目标业务的处理结果信息；以及，通过所述区块链网络向每个所述业务相关方发送所述目标业务的处理结果信息，以使每个所述业务相关方处理所述目标业务。
通过本说明书实施例提供的方法，业务发起方向业务相关方发送业务数据，从而便于业务相关方对业务进行确认，但是业务相关方不会直接返回给业务发起方业务数据和确认结果，而是业务相关方对业务数据进行编码得到编码数据，将编码数据和确认结果返回给业务发起方，后续业务发起方不是直接将业务数据和确认结果存储在区块链网络中，而是将编码数据和确认结果作为一个数据块存储在区块链网络中，区块链成员不会知道业务数据，从而能够在利用区块链网络存储业务数据时，不会导致敏感数据的泄露。
图4示出根据另一个实施例的业务处理的方法流程图，所述方法由业务相关方执行，例如，图2所示场景中的第二成员或第三成员。如图4所示，该实施例中业务处理的方法包括以下步骤：步骤41，从业务发起方接收针对目标业务的业务确认请求，所述业务确认请求中包括业务数据；步骤42，根据所述业务数据，生成第一确认结果；步骤43，采用预设编码方式对所述业务数据进行编码，生成第一编码数据；步骤44，利用所述业务相关方的私钥对包含所述第一确认结果和所述第一编码数据的第一数据块进行签名，得到第一签名数据；步骤45，向所述业务发起方发送业务确认应答，所述业务确认应答中包括所述第一数据块和所述第一签名数据；以使所述业务发起方确定每个所述业务相关方的确认结果均为确认通过时，通过区块链网络存储每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的数据。下面描述以上各个步骤的具体执行方式。
首先在步骤41，从业务发起方接收针对目标业务的业务确认请求，所述业务确认请 求中包括业务数据。
本说明书实施例中，对于业务数据包含的内容不做限定，例如，可以包括用户的姓名、身份证号码、年龄等隐私信息，但并不限定于此。
接着在步骤42，根据所述业务数据，生成第一确认结果。
上述第一确认结果用于指示业务相关方是否认可该目标业务。
然后在步骤43，采用预设编码方式对所述业务数据进行编码，生成第一编码数据。
可以理解的是，业务发起方与业务相关方生成编码数据的方式相同，理论上，第一编码数据与第二编码数据也应用相同，后续可以由区块链网络对二者是否相同进行核对。
再在步骤44，利用所述业务相关方的私钥对包含所述第一确认结果和所述第一编码数据的第一数据块进行签名，得到第一签名数据。
签名计算的方式，前面已有描述，在此不做赘述。
最后在步骤45，向所述业务发起方发送业务确认应答，所述业务确认应答中包括所述第一数据块和所述第一签名数据；以使所述业务发起方确定每个所述业务相关方的确认结果均为确认通过时，通过区块链网络存储每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的数据。
其中，所述业务发起方的数据包括所述业务发起方的所述第二数据块和所述第二签名数据，具体可以参见图3对应的描述。
在一个示例中，所述方法还包括：
从所述区块链网络接收所述目标业务的处理结果信息；
根据所述处理结果信息，处理所述目标业务。
通过本说明书实施例提供的方法，业务相关方从业务发起方接收业务数据，从而便于业务相关方对业务进行确认，但是业务相关方不会直接返回给业务发起方业务数据和确认结果，而是业务相关方对业务数据进行编码得到编码数据，将编码数据和确认结果返回给业务发起方，后续业务发起方不是直接将业务数据和确认结果存储在区块链网络中，而是将编码数据和确认结果作为一个数据块存储在区块链网络中，区块链成员不会知道业务数据，从而能够在利用区块链网络存储业务数据时，不会导致敏感数据的 泄露。
图5示出根据另一个实施例的业务处理的方法流程图，所述方法由区块链网络执行，区块链网络可以简称为区块链，例如，图2所示场景中的区块链。如图5所示，该实施例中业务处理的方法包括以下步骤：
步骤51，从目标业务的业务发起方接收每个业务相关方的第一数据块和第一签名数据，以及所述业务发起方的第二数据块和第二签名数据；其中，所述第一数据块包括由业务相关方采用预设编码方式对业务数据进行编码而生成的第一编码数据、第一确认结果和所述业务相关方的标识；所述第一签名数据为利用所述业务相关方的私钥对所述第一数据块进行签名计算得到的；所述第二数据块包括由业务发起方采用所述预设编码方式对所述业务数据进行编码而生成的第二编码数据、第二确认结果和所述业务发起方的标识；所述第二签名数据为利用所述业务发起方的私钥对所述第二数据块进行签名计算得到的。
可以理解的是，业务发起方和业务相关方可以预先加入该区块链网络，成为该区块链网络的成员。
步骤52，存储每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的所述第二数据块和所述第二签名数据。
在一个示例中，步骤52之后，所述方法还可以包括：处理所述目标业务。例如，记录所述目标业务的处理结果信息；以及，向每个所述业务相关方发送所述目标业务的处理结果信息，以使每个所述业务相关方处理所述目标业务。
在一个示例中，步骤52之前，所述方法还可以包括：
进行如下各项核对：
核对所述业务相关方的标识和/或所述业务发起方的标识是否与所述目标业务的业务链路上的成员标识相匹配；
核对每个所述第一编码数据和所述第二编码数据是否相同；
利用每个所述业务相关方的公钥对每个所述业务相关方的所述第一数据块和所述第一签名数据进行签名验证，验证所述第一数据块和所述第一签名数据是否匹配；
利用所述业务发起方的公钥对所述业务发起方的所述第二数据块和所述第二签名数据进行签名验证，验证所述第二数据块和所述第二签名数据是否匹配；
确定所述各项核对的核对结果均为是。
作为示例，步骤52具体可以将每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的所述第二数据块和所述第二签名数据存储在一个区块中。
通过本说明书实施例提供的方法，区块链网络不是直接从业务发起方接收业务数据和确认结果，而是接收编码数据和确认结果，并且将编码数据和确认结果作为一个数据块存储在区块链网络中，区块链成员不会知道业务数据，从而能够在利用区块链网络存储业务数据时，不会导致敏感数据的泄露。
图6示出根据一个实施例的业务处理过程中各成员交互过程示意图。图7示出根据一个实施例的业务处理时序图。参照图6或图7，业务链路涉及第一成员、第二成员和第三成员，第一成员为业务发起方，第二成员和第三成员为业务相关方，业务的进行需要得到第一成员、第二成员和第三成员的许可。
根据另一方面的实施例，还提供一种业务处理的装置，所述装置设置于业务发起方。图8示出根据一个实施例的业务处理的装置的示意性框图。如图8所示，该装置800包括：
发送单元81，用于针对目标业务向各业务相关方发送业务确认请求，所述业务确认请求中包括业务数据；
接收单元82，用于从每个所述业务相关方接收业务确认应答，所述业务确认应答中包括第一数据块和第一签名数据；其中，所述第一数据块包括由业务相关方采用预设编码方式对所述业务数据进行编码而生成的第一编码数据、第一确认结果和所述业务相关方的标识；所述第一签名数据为利用所述业务相关方的私钥对所述第一数据块进行签名计算得到的；
编码单元83，用于采用所述预设编码方式对所述业务数据进行编码，从而生成第二编码数据；以及生成第二确认结果；
签名单元84，用于利用所述业务发起方的私钥对包括第二编码数据、第二确认结果和所述业务发起方的标识的第二数据块进行签名，得到第二签名数据；
存储单元85，用于确定所述接收单元82接收的每个所述第一确认结果和所述编码单元83生成的所述第二确认结果均为确认通过时，通过区块链网络存储所述接收单元82接收的每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业 务发起方的所述第二数据块和所述第二签名数据。
可选地，作为一个实施例，所述装置还包括：
处理单元，用于确定所述接收单元82接收的每个所述第一确认结果和所述第二确认结果均为确认通过时，通过所述区块链网络处理所述目标业务。
进一步地，所述处理单元，具体用于：
通过所述区块链网络记录所述目标业务的处理结果信息；以及，
通过所述区块链网络向每个所述业务相关方发送所述目标业务的处理结果信息，以使每个所述业务相关方处理所述目标业务。
通过本说明书实施例提供的装置，发送单元81向业务相关方发送业务数据，从而便于业务相关方对业务进行确认，但是业务相关方不会直接返回给接收单元82业务数据和确认结果，而是业务相关方对业务数据进行编码得到编码数据，将编码数据和确认结果返回给接收单元82，后续存储单元85不是直接将业务数据和确认结果存储在区块链网络中，而是将编码数据和确认结果作为一个数据块存储在区块链网络中，区块链成员不会知道业务数据，从而能够在利用区块链网络存储业务数据时，不会导致敏感数据的泄露。
根据另一方面的实施例，还提供一种业务处理的装置，所述装置设置于业务相关方。图9示出根据另一个实施例的业务处理的装置的示意性框图。如图9所示，该装置900包括：
接收单元91，用于从业务发起方接收针对目标业务的业务确认请求，所述业务确认请求中包括业务数据；
确认单元92，用于根据所述接收单元91接收的业务数据，生成第一确认结果；
编码单元93，用于采用预设编码方式对所述接收单元91接收的业务数据进行编码，生成第一编码数据；
签名单元94，用于利用所述业务相关方的私钥对包含所述第一确认结果和所述第一编码数据的第一数据块进行签名，得到第一签名数据；
发送单元95，用于向所述业务发起方发送业务确认应答，所述业务确认应答中包括所述第一数据块和所述第一签名数据；以使所述业务发起方确定每个所述业务相关方的确认结果均为确认通过时，通过区块链网络存储每个所述业务相关方的所述第一数 据块和所述第一签名数据，以及所述业务发起方的数据。
可选地，作为一个实施例，
所述接收单元91，还用于从所述区块链网络接收所述目标业务的处理结果信息；
所述装置还包括：
处理单元，用于根据所述接收单元91接收的处理结果信息，处理所述目标业务。
通过本说明书实施例提供的装置，接收单元91从业务发起方接收业务数据，从而便于确认单元92对业务进行确认，但是发送单元95不会直接返回给业务发起方业务数据和确认结果，而是业务相关方对业务数据进行编码得到编码数据，将编码数据和确认结果返回给业务发起方，后续业务发起方不是直接将业务数据和确认结果存储在区块链网络中，而是将编码数据和确认结果作为一个数据块存储在区块链网络中，区块链成员不会知道业务数据，从而能够在利用区块链网络存储业务数据时，不会导致敏感数据的泄露。
根据另一方面的实施例，还提供一种业务处理的装置，所述装置设置于区块链网络，具体地，设置于区块链网络的节点，可以简称为区块链。图10示出根据另一个实施例的业务处理的装置的示意性框图。如图10所示，该装置1000包括：
接收单元1001，用于从目标业务的业务发起方接收每个业务相关方的第一数据块和第一签名数据，以及所述业务发起方的第二数据块和第二签名数据；其中，所述第一数据块包括由业务相关方采用预设编码方式对业务数据进行编码而生成的第一编码数据、第一确认结果和所述业务相关方的标识；所述第一签名数据为利用所述业务相关方的私钥对所述第一数据块进行签名计算得到的；所述第二数据块包括由业务发起方采用所述预设编码方式对所述业务数据进行编码而生成的第二编码数据、第二确认结果和所述业务发起方的标识；所述第二签名数据为利用所述业务发起方的私钥对所述第二数据块进行签名计算得到的；
存储单元1002，用于存储所述接收单元1001接收的每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的所述第二数据块和所述第二签名数据。
可选地，作为一个实施例，所述装置还包括：
处理单元，用于在所述存储单元1002存储每个所述业务相关方的所述第一数据 块和所述第一签名数据，以及所述业务发起方的所述第二数据块和所述第二签名数据之后，处理所述目标业务。
进一步地，所述处理单元，具体用于：
记录所述目标业务的处理结果信息；以及，
向每个所述业务相关方发送所述目标业务的处理结果信息，以使每个所述业务相关方处理所述目标业务。
进一步地，所述装置还包括：
核对单元，用于在所述存储单元1002存储每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的所述第二数据块和所述第二签名数据之前，进行如下各项核对：
核对所述业务相关方的标识和/或所述业务发起方的标识是否与所述目标业务的业务链路上的成员标识相匹配；
核对每个所述第一编码数据和所述第二编码数据是否相同；
利用每个所述业务相关方的公钥对每个所述业务相关方的所述第一数据块和所述第一签名数据进行签名验证，验证所述第一数据块和所述第一签名数据是否匹配；
利用所述业务发起方的公钥对所述业务发起方的所述第二数据块和所述第二签名数据进行签名验证，验证所述第二数据块和所述第二签名数据是否匹配；
确定单元，用于确定所述核对单元得到的所述各项核对的核对结果均为是。
可选地，作为一个实施例，所述存储单元1002，具体用于将所述接收单元1001接收的每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的所述第二数据块和所述第二签名数据存储在一个区块中。
通过本说明书实施例提供的装置，接收单元1001不是直接从业务发起方接收业务数据和确认结果，而是接收编码数据和确认结果，并且存储单元1002将编码数据和确认结果作为一个数据块存储在区块链网络中，区块链成员不会知道业务数据，从而能够在利用区块链网络存储业务数据时，不会导致敏感数据的泄露。
根据另一方面的实施例，还提供一种业务处理的系统，所述系统包括第一成员业务系统、第二成员业务系统、区块链桥接系统和区块链。图11示出根据一个实施例的业务处理的系统的示意性框图。如图11所示，该系统的处理过程包括：
首先，第一成员(即业务发起方)向第一成员的区块链桥接系统发起交易确认请求，请求中的数据包括交易约定的明细数据(以下统称BIZ_DATA)。
接下来，第一成员的区块链桥接系统的接收模块收到请求后，经过发送模块将数据按照约定的格式发送给交易链路上的所有成员，发送的数据包括BIZ_DATA。
然后，第二成员(如果业务相关方还包括第三成员，则与第二成员采用相同的处理逻辑)的区块链桥接系统的接收模块收到请求后，将数据转发给第二成员的业务系统，进行交易确认，收到的数据包括BIZ_DATA。第二成员进行确认后，将确认结果(以下统称RESULT)返回给区块链桥接系统的接收模块。接收模块，将所述的BIZ_DATA和所述的结果传给脱敏模块处理。
再然后，第二成员的区块链桥接系统的脱敏模块，对所述的BIZ_DATA进行哈希(hash)处理(也可采用其他的编码方式)，计算出对应的哈希编码(hash code)。然后，将hash code、RESULT传给签名模块。
再然后，第二成员的区块链桥接系统的签名模块，将所述的hash code、RESULT和第二成员预设的成员ID按照约定的格式作为一个数据块(以下统称CHECK_RESULT)，然后用私钥计算签名(以下统称SIGNATURE)。
再然后，第二成员的区块链桥接系统的发送模块将所述的CHECK_RESULT和SIGNATURE返回给第一成员。
再然后，第一成员的区块链桥接系统的发送模块收到交易链路上所有成员返回的CHECK_RESULT和SIGNATURE后，解析并检查所有收到的CHECK_RESULT里的交易确认结果(所述的RESULT)是否都是确认通过，如果确认通过，则继续调用接入模块。
再然后，第一成员的区块链桥接系统的接入模块，将交易链路上所有成员的CHECK_RESULT和SIGNATURE发送给区块链进行处理。
再然后，区块链里的核对模块进行以下核对：解析所有的CHECK_RESULT，解析后的数据包括所述的hash code、RESULT和成员ID；核对解析得到的所有成员ID和交易链路上的所有成员ID是否匹配；核对每个成员的hash code是否完全相同；检查每一对CHECK_RESULT和SIGNATURE，通过成员ID拿到对应成员的公钥，利用公钥对CHECK_RESULT和SIGNATURE进行签名验证，验证是否匹配。
最后，区块链在上述核对都完成后就可以调用区块链的业务模块进行业务处理 了。
根据另一方面的实施例，还提供一种计算机可读存储介质，其上存储有计算机程序，当所述计算机程序在计算机中执行时，令计算机执行结合图3至图5中任一所描述的方法。
根据再一方面的实施例，还提供一种计算设备，包括存储器和处理器，所述存储器中存储有可执行代码，所述处理器执行所述可执行代码时，实现结合图3至图5中任一所描述的方法。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本发明所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。
以上所述的具体实施方式，对本发明的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本发明的具体实施方式而已，并不用于限定本发明的保护范围，凡在本发明的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本发明的保护范围之内。

Claims (22)

  1. 一种业务处理的方法，所述方法由业务发起方执行，并包括：
    针对目标业务向各业务相关方发送业务确认请求，所述业务确认请求中包括业务数据；
    从每个所述业务相关方接收业务确认应答，所述业务确认应答中包括第一数据块和第一签名数据；其中，所述第一数据块包括由业务相关方采用预设编码方式对所述业务数据进行编码而生成的第一编码数据、第一确认结果和所述业务相关方的标识；所述第一签名数据为利用所述业务相关方的私钥对所述第一数据块进行签名计算得到的；
    采用所述预设编码方式对所述业务数据进行编码，从而生成第二编码数据；以及生成第二确认结果；
    利用所述业务发起方的私钥对包括第二编码数据、第二确认结果和所述业务发起方的标识的第二数据块进行签名，得到第二签名数据；
    确定每个所述第一确认结果和所述第二确认结果均为确认通过时，通过区块链网络存储每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的所述第二数据块和所述第二签名数据。
  2. 如权利要求1所述的方法，其中，所述方法还包括：
    确定每个所述第一确认结果和所述第二确认结果均为确认通过时，通过所述区块链网络处理所述目标业务。
  3. 如权利要求2所述的方法，其中，所述通过所述区块链网络处理所述目标业务，包括：
    通过所述区块链网络记录所述目标业务的处理结果信息；以及，
    通过所述区块链网络向每个所述业务相关方发送所述目标业务的处理结果信息，以使每个所述业务相关方处理所述目标业务。
  4. 一种业务处理的方法，所述方法由业务相关方执行，并包括：
    从业务发起方接收针对目标业务的业务确认请求，所述业务确认请求中包括业务数据；
    根据所述业务数据，生成第一确认结果；
    采用预设编码方式对所述业务数据进行编码，生成第一编码数据；
    利用所述业务相关方的私钥对包含所述第一确认结果和所述第一编码数据的第一数据块进行签名，得到第一签名数据；
    向所述业务发起方发送业务确认应答，所述业务确认应答中包括所述第一数据块和 所述第一签名数据；以使所述业务发起方确定每个所述业务相关方的确认结果均为确认通过时，通过区块链网络存储每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的数据。
  5. 如权利要求4所述的方法，其中，所述方法还包括：
    从所述区块链网络接收所述目标业务的处理结果信息；
    根据所述处理结果信息，处理所述目标业务。
  6. 一种业务处理的方法，所述方法由区块链网络执行，并包括：
    从目标业务的业务发起方接收每个业务相关方的第一数据块和第一签名数据，以及所述业务发起方的第二数据块和第二签名数据；其中，所述第一数据块包括由业务相关方采用预设编码方式对业务数据进行编码而生成的第一编码数据、第一确认结果和所述业务相关方的标识；所述第一签名数据为利用所述业务相关方的私钥对所述第一数据块进行签名计算得到的；所述第二数据块包括由业务发起方采用所述预设编码方式对所述业务数据进行编码而生成的第二编码数据、第二确认结果和所述业务发起方的标识；所述第二签名数据为利用所述业务发起方的私钥对所述第二数据块进行签名计算得到的；
    存储每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的所述第二数据块和所述第二签名数据。
  7. 如权利要求6所述的方法，其中，所述存储每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的所述第二数据块和所述第二签名数据之后，所述方法还包括：
    处理所述目标业务。
  8. 如权利要求7所述的方法，其中，所述处理所述目标业务，包括：
    记录所述目标业务的处理结果信息；以及，
    向每个所述业务相关方发送所述目标业务的处理结果信息，以使每个所述业务相关方处理所述目标业务。
  9. 如权利要求7所述的方法，其中，所述存储每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的所述第二数据块和所述第二签名数据之前，所述方法还包括：
    进行如下各项核对：
    核对所述业务相关方的标识和/或所述业务发起方的标识是否与所述目标业务的业务链路上的成员标识相匹配；
    核对每个所述第一编码数据和所述第二编码数据是否相同；
    利用每个所述业务相关方的公钥对每个所述业务相关方的所述第一数据块和所述第一签名数据进行签名验证，验证所述第一数据块和所述第一签名数据是否匹配；
    利用所述业务发起方的公钥对所述业务发起方的所述第二数据块和所述第二签名数据进行签名验证，验证所述第二数据块和所述第二签名数据是否匹配；
    确定所述各项核对的核对结果均为是。
  10. 如权利要求6所述的方法，其中，所述存储每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的所述第二数据块和所述第二签名数据，包括：
    将每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的所述第二数据块和所述第二签名数据存储在一个区块中。
  11. 一种业务处理的装置，所述装置设置于业务发起方，并包括：
    发送单元，用于针对目标业务向各业务相关方发送业务确认请求，所述业务确认请求中包括业务数据；
    接收单元，用于从每个所述业务相关方接收业务确认应答，所述业务确认应答中包括第一数据块和第一签名数据；其中，所述第一数据块包括由业务相关方采用预设编码方式对所述业务数据进行编码而生成的第一编码数据、第一确认结果和所述业务相关方的标识；所述第一签名数据为利用所述业务相关方的私钥对所述第一数据块进行签名计算得到的；
    编码单元，用于采用所述预设编码方式对所述业务数据进行编码，从而生成第二编码数据；以及生成第二确认结果；
    签名单元，用于利用所述业务发起方的私钥对包括第二编码数据、第二确认结果和所述业务发起方的标识的第二数据块进行签名，得到第二签名数据；
    存储单元，用于确定所述接收单元接收的每个所述第一确认结果和所述编码单元生成的所述第二确认结果均为确认通过时，通过区块链网络存储所述接收单元接收的每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的所述第二数据块和所述第二签名数据。
  12. 如权利要求11所述的装置，其中，所述装置还包括：
    处理单元，用于确定所述接收单元接收的每个所述第一确认结果和所述第二确认结果均为确认通过时，通过所述区块链网络处理所述目标业务。
  13. 如权利要求12所述的装置，其中，所述处理单元，具体用于：
    通过所述区块链网络记录所述目标业务的处理结果信息；以及，
    通过所述区块链网络向每个所述业务相关方发送所述目标业务的处理结果信息，以使每个所述业务相关方处理所述目标业务。
  14. 一种业务处理的装置，所述装置设置于业务相关方，并包括：
    接收单元，用于从业务发起方接收针对目标业务的业务确认请求，所述业务确认请求中包括业务数据；
    确认单元，用于根据所述接收单元接收的业务数据，生成第一确认结果；
    编码单元，用于采用预设编码方式对所述接收单元接收的业务数据进行编码，生成第一编码数据；
    签名单元，用于利用所述业务相关方的私钥对包含所述第一确认结果和所述第一编码数据的第一数据块进行签名，得到第一签名数据；
    发送单元，用于向所述业务发起方发送业务确认应答，所述业务确认应答中包括所述第一数据块和所述第一签名数据；以使所述业务发起方确定每个所述业务相关方的确认结果均为确认通过时，通过区块链网络存储每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的数据。
  15. 如权利要求14所述的装置，其中，
    所述接收单元，还用于从所述区块链网络接收所述目标业务的处理结果信息；
    所述装置还包括：
    处理单元，用于根据所述接收单元接收的处理结果信息，处理所述目标业务。
  16. 一种业务处理的装置，所述装置设置于区块链网络，并包括：
    接收单元，用于从目标业务的业务发起方接收每个业务相关方的第一数据块和第一签名数据，以及所述业务发起方的第二数据块和第二签名数据；其中，所述第一数据块包括由业务相关方采用预设编码方式对业务数据进行编码而生成的第一编码数据、第一确认结果和所述业务相关方的标识；所述第一签名数据为利用所述业务相关方的私钥对所述第一数据块进行签名计算得到的；所述第二数据块包括由业务发起方采用所述预设编码方式对所述业务数据进行编码而生成的第二编码数据、第二确认结果和所述业务发起方的标识；所述第二签名数据为利用所述业务发起方的私钥对所述第二数据块进行签名计算得到的；
    存储单元，用于存储所述接收单元接收的每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的所述第二数据块和所述第二签名数据。
  17. 如权利要求16所述的装置，其中，所述装置还包括：
    处理单元，用于在所述存储单元存储每个所述业务相关方的所述第一数据块和所述 第一签名数据，以及所述业务发起方的所述第二数据块和所述第二签名数据之后，处理所述目标业务。
  18. 如权利要求17所述的装置，其中，所述处理单元，具体用于：
    记录所述目标业务的处理结果信息；以及，
    向每个所述业务相关方发送所述目标业务的处理结果信息，以使每个所述业务相关方处理所述目标业务。
  19. 如权利要求17所述的装置，其中，所述装置还包括：
    核对单元，用于在所述存储单元存储每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的所述第二数据块和所述第二签名数据之前，进行如下各项核对：
    核对所述业务相关方的标识和/或所述业务发起方的标识是否与所述目标业务的业务链路上的成员标识相匹配；
    核对每个所述第一编码数据和所述第二编码数据是否相同；
    利用每个所述业务相关方的公钥对每个所述业务相关方的所述第一数据块和所述第一签名数据进行签名验证，验证所述第一数据块和所述第一签名数据是否匹配；
    利用所述业务发起方的公钥对所述业务发起方的所述第二数据块和所述第二签名数据进行签名验证，验证所述第二数据块和所述第二签名数据是否匹配；
    确定单元，用于确定所述核对单元得到的所述各项核对的核对结果均为是。
  20. 如权利要求16所述的装置，其中，所述存储单元，具体用于将所述接收单元接收的每个所述业务相关方的所述第一数据块和所述第一签名数据，以及所述业务发起方的所述第二数据块和所述第二签名数据存储在一个区块中。
  21. 一种计算机可读存储介质，其上存储有计算机程序，当所述计算机程序在计算机中执行时，令计算机执行权利要求1-10中任一项的所述的方法。
  22. 一种计算设备，包括存储器和处理器，所述存储器中存储有可执行代码，所述处理器执行所述可执行代码时，实现权利要求1-10中任一项的所述的方法。
PCT/CN2019/106890 2018-11-20 2019-09-20 业务处理的方法和装置 WO2020103557A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
SG11202100493SA SG11202100493SA (en) 2018-11-20 2019-09-20 Transaction processing method and apparatus
EP19886106.4A EP3885956A4 (en) 2018-11-20 2019-09-20 TRANSACTION PROCESSING METHOD AND DEVICE
US17/157,884 US11315109B2 (en) 2018-11-20 2021-01-25 Transaction processing method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811385400.3A CN109598149B (zh) 2018-11-20 2018-11-20 业务处理的方法和装置
CN201811385400.3 2018-11-20

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/157,884 Continuation US11315109B2 (en) 2018-11-20 2021-01-25 Transaction processing method and apparatus

Publications (1)

Publication Number Publication Date
WO2020103557A1 true WO2020103557A1 (zh) 2020-05-28

Family

ID=65960161

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/106890 WO2020103557A1 (zh) 2018-11-20 2019-09-20 业务处理的方法和装置

Country Status (6)

Country Link
US (1) US11315109B2 (zh)
EP (1) EP3885956A4 (zh)
CN (1) CN109598149B (zh)
SG (1) SG11202100493SA (zh)
TW (1) TWI709925B (zh)
WO (1) WO2020103557A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114666157A (zh) * 2022-04-14 2022-06-24 西安邮电大学 一种区块链跨链威胁情报的共享系统及其方法
CN117993021A (zh) * 2024-04-07 2024-05-07 北京惠每云科技有限公司 远程检查系统安全性提升方法及装置

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109598149B (zh) * 2018-11-20 2020-04-07 阿里巴巴集团控股有限公司 业务处理的方法和装置
US20200313859A1 (en) * 2019-03-29 2020-10-01 Accenture Global Solutions Limited Cryptologic Blockchain-Based Off-Chain Storage Verification
CN112612856B (zh) * 2019-07-09 2024-03-29 创新先进技术有限公司 基于区块链的数据处理方法和装置
CN112632059B (zh) * 2019-10-09 2023-08-15 浙江大搜车软件技术有限公司 数据核对方法、装置、电子设备及机器可读存储介质
CN110866753B (zh) * 2019-10-24 2021-04-06 腾讯科技（深圳）有限公司 一种第三方结算的控制方法、装置、电子设备和存储介质
US11456869B2 (en) * 2019-12-16 2022-09-27 The Toronto-Dominion Bank Secure management of transfers of digital assets between computing devices using permissioned distributed ledgers
CN111310237B (zh) * 2020-01-22 2024-04-26 腾讯科技（深圳）有限公司 一种基于区块链的业务处理方法、装置以及设备
CN112884579A (zh) * 2021-02-08 2021-06-01 京东数科海益信息科技有限公司 区块链交易共识方法和装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160342989A1 (en) * 2015-05-21 2016-11-24 Mastercard International Incorporated Method and system for processing blockchain-based transactions on existing payment networks
CN106603198A (zh) * 2016-12-02 2017-04-26 深圳大学 具有网络编码的区块链分布式存储方法及系统
CN108335103A (zh) * 2017-12-28 2018-07-27 中国人民银行数字货币研究所 一种基于数字货币的扣款方法和系统
CN109598149A (zh) * 2018-11-20 2019-04-09 阿里巴巴集团控股有限公司 业务处理的方法和装置

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040024750A1 (en) 2002-07-31 2004-02-05 Ulyanov Sergei V. Intelligent mechatronic control suspension system based on quantum soft computing
US9032206B2 (en) 2013-02-25 2015-05-12 Surfeasy, Inc. Rule sets for client-applied encryption in communications networks
US10915891B1 (en) * 2015-03-16 2021-02-09 Winklevoss Ip, Llc Autonomous devices
CN105260675B (zh) * 2015-10-16 2017-03-15 北京源创云网络科技有限公司 电子数据一致性验证方法、装置、系统及存证验证平台
WO2017091530A1 (en) * 2015-11-24 2017-06-01 Gartland & Mellina Group Blockchain solutions for financial services and other transaction-based industries
CN106503994B (zh) * 2016-11-02 2020-07-28 西安电子科技大学 基于属性加密的区块链隐私数据访问控制方法
CN106941487B (zh) * 2017-02-24 2021-01-05 创新先进技术有限公司 一种数据发送方法及装置
KR102414732B1 (ko) 2017-04-05 2022-06-28 삼성에스디에스 주식회사 블록체인 기반 디지털 아이덴티티 관리 방법
EP3396608A1 (en) * 2017-04-24 2018-10-31 BlockSettle AB Method and system for settling a blockchain transaction
CN107392040B (zh) * 2017-04-28 2019-08-09 阿里巴巴集团控股有限公司 一种共识验证的方法及装置
US10135834B1 (en) 2017-10-20 2018-11-20 Social Patent LLC System and method of executing operations in a social network application
CN107911216B (zh) * 2017-10-26 2020-07-14 矩阵元技术（深圳）有限公司 一种区块链交易隐私保护方法及系统
CN108009441B (zh) * 2017-11-23 2023-05-30 创新先进技术有限公司 资源转移和资金转移的方法和装置
US10657261B2 (en) 2017-11-30 2020-05-19 Mocana Corporation System and method for recording device lifecycle transactions as versioned blocks in a blockchain network using a transaction connector and broker service
CN108009810A (zh) * 2017-12-27 2018-05-08 光载无限（北京）科技有限公司 一种可信数字资产交易方法
CN108551437B (zh) * 2018-03-13 2021-04-02 百度在线网络技术（北京）有限公司 用于认证信息的方法和装置
US10783545B2 (en) * 2018-04-19 2020-09-22 American Express Travel Related Services Company, Inc. Reward point redemption for cryptocurrency
CN108694238A (zh) * 2018-05-14 2018-10-23 腾讯科技（深圳）有限公司 基于区块链的业务数据处理方法、装置及存储介质
US20190385215A1 (en) * 2018-06-19 2019-12-19 American Express Travel Related Services Company, Inc. Buyer-centric marketplace using blockchain
CN109697606A (zh) * 2018-09-30 2019-04-30 贝克链区块链技术有限公司 基于创新性的信誉证明共识协议的分布式网络及生态系统
KR20210082194A (ko) * 2018-10-19 2021-07-02 디지털 에셋 (스위츠랜드) 게엠베하 프라이버시 보호 유효성 검사 및 커밋 아키텍처

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160342989A1 (en) * 2015-05-21 2016-11-24 Mastercard International Incorporated Method and system for processing blockchain-based transactions on existing payment networks
CN106603198A (zh) * 2016-12-02 2017-04-26 深圳大学 具有网络编码的区块链分布式存储方法及系统
CN108335103A (zh) * 2017-12-28 2018-07-27 中国人民银行数字货币研究所 一种基于数字货币的扣款方法和系统
CN109598149A (zh) * 2018-11-20 2019-04-09 阿里巴巴集团控股有限公司 业务处理的方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3885956A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114666157A (zh) * 2022-04-14 2022-06-24 西安邮电大学 一种区块链跨链威胁情报的共享系统及其方法
CN117993021A (zh) * 2024-04-07 2024-05-07 北京惠每云科技有限公司 远程检查系统安全性提升方法及装置

Also Published As

Publication number Publication date
SG11202100493SA (en) 2021-02-25
US11315109B2 (en) 2022-04-26
EP3885956A4 (en) 2022-07-27
TWI709925B (zh) 2020-11-11
CN109598149B (zh) 2020-04-07
EP3885956A1 (en) 2021-09-29
CN109598149A (zh) 2019-04-09
US20210174359A1 (en) 2021-06-10
TW202036402A (zh) 2020-10-01

Similar Documents

Publication Publication Date Title
WO2020103557A1 (zh) 业务处理的方法和装置
US11972412B2 (en) Device provisioning using partial personalization scripts
US10977632B2 (en) Electronic bill management method, apparatus, and storage medium
CN110692214B (zh) 用于使用区块链的所有权验证的方法和系统
JP5657672B2 (ja) 高信頼性メッセージ記憶、転送プロトコルおよびシステム
WO2021204273A1 (zh) 资产类型注册、交易记录验证
CN109308416B (zh) 业务服务数据处理方法、装置、系统、存储介质和设备
US11303450B2 (en) Techniques for securely performing offline authentication
US11716200B2 (en) Techniques for performing secure operations
WO2022206433A1 (zh) 一种在Fabric区块链中预执行链码的方法和装置
CN110191123B (zh) 一种线上办卡方法、客户端及系统
US20220353058A1 (en) Conditional offline interaction system and method
WO2021121030A1 (zh) 一种资源转移的方法及结账终端、服务器节点
AU2014307582B2 (en) System and method for generating payment credentials
CN115867931A (zh) 保护隐私的分散式支付工具网络
US20140067687A1 (en) Clone defence system for secure mobile payment
US11880810B1 (en) Systems and methods for securely sharing public blockchain addresses
US20240242203A1 (en) Device provisioning using partial personalization scripts
CN106059773B (zh) 数字签名方法及系统
CN115412256A (zh) 基于区块链的身份认证方法及装置、存储介质、终端设备
CN117290826A (zh) 权限获取方法、装置、电子设备和存储介质
CN115880088A (zh) 账务处理方法、接入服务器、节点服务器及账务处理系统
CN116777460A (zh) 资源转移方法、装置、计算机设备和存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19886106

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019886106

Country of ref document: EP

Effective date: 20210621