WO2021073516A1 - Blockchain-based workflow node certification method and device - Google Patents

Blockchain-based workflow node certification method and device Download PDF

Info

Publication number
WO2021073516A1
WO2021073516A1 PCT/CN2020/120771 CN2020120771W WO2021073516A1 WO 2021073516 A1 WO2021073516 A1 WO 2021073516A1 CN 2020120771 W CN2020120771 W CN 2020120771W WO 2021073516 A1 WO2021073516 A1 WO 2021073516A1
Authority
WO
WIPO (PCT)
Prior art keywords
certification
template
data
workflow
general
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2020/120771
Other languages
French (fr)
Inventor
Duanxin LU
Qiangle GENG
Bangya MA
Jianliang Gu
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shanghai Weilian Information Technology Co Ltd
Original Assignee
Shanghai Weilian Information Technology Co Ltd
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 Shanghai Weilian Information Technology Co Ltd filed Critical Shanghai Weilian Information Technology Co Ltd
Priority to US17/768,349 priority Critical patent/US12238220B2/en
Priority to JP2022519265A priority patent/JP2022552110A/en
Priority to EP20878003.1A priority patent/EP4046009A4/en
Publication of WO2021073516A1 publication Critical patent/WO2021073516A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • G06F8/31—Programming languages or programming paradigms
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/103—Workflow collaboration or project management
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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 OR CALCULATING; 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
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • 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
    • 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

  • the present disclosure relates to the field of workflow information security, and more particularly, to a blockchain-based workflow node certification method and device.
  • the present disclosure provides a blockchain-based workflow node certification method and device.
  • the method and the device are configured to solve the technical problems of data tampering and data leakage caused by the lack of a scheme for certifying specific data of workflow nodes in the prior art.
  • a blockchain-based workflow node certification method including:
  • step S101 establishing, by a certification party, a general workflow template using a JSON language, the general workflow template comprising a plurality of workflow nodes each having an audit attribute for indicating whether the workflow node needs to be certified;
  • step S102 establishing, by the certification party, a general data template using the JSON language based on the general workflow template, the general data template defining data needing to be collected and transmitted in a workflow execution process;
  • step S103 instantiating the general data template and the general workflow template.
  • step S104 acquiring a current workflow node in the instantiated general workflow template, determining, based on the audit attribute, whether the current workflow node needs to be certified, if yes, certifying, by a centralized certification party, data needing to be received or sent by the current workflow node defined in the general workflow template and a data template defined in an instantiating process, and depositing certification, by a blockchain, for the data needing to be received by the current workflow node and the data template received in the instantiating process, the certification and certification deposition for the data template referring to the certification and certification deposition for specific data in the data template.
  • the general data template has uuid, name, version, languageType, contentType, required, validation, and content fields
  • the uuid field is configured to define a unique identifier of the general data template
  • the name field is configured to define a name of the general data template
  • the version field is configured to define a version of the general data template
  • the languageType field defines a language type implementing the general data template
  • the contentType field defines a data type
  • the required field defines whether the data is required
  • the validation field is configured for logical validation, and may contain a validation script or link to external services to determine whether a data format is correct
  • the content field may be nested with other data templates.
  • step S104 includes:
  • step S1041 acquiring a current workflow node in the instantiated general workflow template, determining, based on the audit attribute, whether the current workflow node needs to be certified, if yes, proceeding to step S1042, and if no, proceeding to step S1044;
  • step S1042 acquiring the instantiated current workflow node, acquiring data needing to be received or sent, which is defined in the general workflow template by the current workflow node, and a data template defined in an instantiating process, and sending the data and the data template to the certification party for certification audit;
  • step S1043 after passing the certification audit, performing, by the certification party, Hash calculation on the data and the data template to obtain a Hash value, and sending the Hash value to the blockchain for certification deposition;
  • step S1044 determining whether the current workflow node is an end node, if yes, ending the method, and if no, proceeding to step S1045;
  • step S1045 setting the current workflow node as a next workflow node, and proceeding to step S1042.
  • the certification party obtains an ID of the certification deposition operation, and associates the ID with original data.
  • a blockchain-based workflow node certification device including:
  • a general workflow template module configured to establish, by a certification party, a general workflow template using a JSON language, the general workflow template comprising a plurality of workflow nodes each having an audit attribute for indicating whether the workflow node needs to be certified;
  • a general data template module configured to establish, by the certification party, a general data template using the JSON language based on the general workflow template, the general data template defining data needing to be collected and transmitted in a workflow execution process;
  • an instantiating module configured to instantiate the general data template and the general workflow template
  • a certification and deposition module configured to acquire a current workflow node in the instantiated general workflow template, determine, based on the audit attribute, whether the current workflow node needs to be certified, if yes, certify, by a centralized certification party, data needing to be received or sent by the current workflow node defined in the general workflow template and a data template defined in an instantiating process, and deposit certification, by a blockchain, for the data needing to be received by the current workflow node and the data template received in the instantiating process, the certification and certification deposition for the data template referring to the certification and certification deposition for specific data in the data template.
  • the general data template has uuid, name, version, languageType, contentType, required, validation, and content fields
  • the uuid field is configured to define a unique identifier of the general data template
  • the name field is configured to define a name of the general data template
  • the version field is configured to define a version of the general data template
  • the languageType field defines a language type implementing the general data template
  • the contentType field defines a data type
  • the required field defines whether the data is required
  • the validation field is configured for logical validation, and may contain a validation script or link to external services to determine whether a data format is correct
  • the content field may be nested with other data templates.
  • the certification and certification deposition module includes:
  • a first determination sub-module configured to acquire a current workflow node in the instantiated general workflow template, and determine, based on the audit attribute, whether the current workflow node needs to be certified;
  • a certification sub-module configured to acquire the instantiated current workflow node, acquire data needing to be received or sent, which is defined in the general workflow template by the current workflow node, and a data template defined in an instantiating process, and send the data and the data template to the certification party for certification audit;
  • a deposition sub-module configured to perform, by the certification party, Hash calculation on the data and the data template after passing the certification audit to obtain a Hash value, and send the Hash value to the blockchain for certification deposition;
  • a second determination sub-module configured to determine whether the current workflow node is an end node
  • a setting sub-module configured to set the current workflow node as a next workflow node.
  • an association sub-module is also included, which is configured to obtain, by the certification party, an ID of the certification deposition operation after the blockchain completes the certification deposition and synchronization, and associate the ID with original data.
  • a blockchain-based workflow node certification system including:
  • a processor configured to execute a plurality of instructions
  • a memory configured to store the plurality of instructions.
  • the plurality of instructions are configured to be stored by the memory and loaded by the processor to perform the blockchain-based workflow node certification method as described previously.
  • a computer-readable storage medium stores a plurality of instructions therein that are configured to be loaded by a processor and perform the blockchain-based workflow node certification method as described previously.
  • users can create and modify transaction processes as needed to meet the needs of changeable transaction.
  • central certification with blockchain certification deposition and certifying workflow node data needing to be certified, the security of workflow node process implementation and the privacy of specific data are ensured.
  • FIG. 1 is a flowchart of a blockchain-based workflow node certification method according to the present disclosure
  • FIG. 2 is a structural diagram of a general workflow template according to the present disclosure
  • FIG. 3 is a structural diagram of a general data template according to the present disclosure.
  • FIG. 4 is a block diagram of components of a blockchain-based workflow node certification device according to the present disclosure.
  • FIG. 1 is a flowchart of one example implementation of a blockchain-based workflow node certification method according to the present disclosure. As shown in FIG. 1, the method includes the following steps:
  • step S101 establishing, by a certification party, a general workflow template using a JSON language, the general workflow template comprising a plurality of workflow nodes each having an audit attribute for indicating whether the workflow node needs to be certified;
  • step S102 establishing, by the certification party, a general data template using the JSON language based on the general workflow template, the general data template defining data needing to be collected and transmitted in a workflow execution process;
  • step S103 instantiating the general data template and the general workflow template.
  • step S104 acquiring a current workflow node in the instantiated general workflow template, determining, based on the audit attribute, whether the current workflow node needs to be certified, if yes, a centralized certification party certifying data needing to be received or sent by the current workflow node defined in the general workflow template and a data template defined in an instantiating process, and a blockchain depositing the certification for the data needing to be received by the current workflow node and the data template received in the instantiating process.
  • the certification and certification deposition for the data template refers to the certification and certification deposition for specific data in the data template.
  • Step S101 of establishing, by a certification party using a JSON language, a general workflow template that includes a plurality of workflow nodes each having an audit attribute for indicating whether the workflow node needs to be certified includes the following steps.
  • the certification party may be a third-party certification authority
  • the general workflow template is configured to describe an actual transaction process
  • a user may determine various nodes that need to be experienced in the transaction process according to transaction and functions to be implemented by a software system
  • the general workflow template is then defined by the various nodes, and different nodes are connected in series through a specified node to form a complete transaction process.
  • the software system may read and identify these nodes.
  • the general workflow template has a structure shown in FIG. 2, and the general workflow template has three fields: process_id, process_name, and definitions.
  • the process_id field is configured to define a unique identifier of a transaction process corresponding to the general workflow template
  • the process_name field is configured to define a name of the transaction process
  • the definitions field is configured to define various workflow nodes needed in the transaction process.
  • the definitions field may define a plurality of workflow nodes, and each workflow node has node_id, node_name, title, type, target, render, and audit fields.
  • the node_id field defines a unique identifier of a workflow node
  • the node_name field defines a name of the workflow node
  • the title field defines a title of the workflow node
  • the type field is configured to define a type of the workflow node
  • the type of the workflow node includes a start node, an intermediate task node, or an end node.
  • the target field is configured to define a next node ID after the workflow node is executed, and configured to indicate an execution order of the workflow nodes
  • the render field defines the input and output of the workflow node through the from and to attributes
  • the audit field is configured to define whether the node needs to be certified.
  • a complex transaction process may include a plurality of start nodes. For example, a user may actively initiate the same transaction process and submit relevant information, or a server may passively initiate the same transaction process and acquire the relevant information from the user.
  • Step S102 of establishing, by the certification party using the JSON language based on the general workflow template, a general data template that defines data needing to be collected and transmitted in a workflow execution process includes the following steps.
  • the general data template has a structure shown in FIG. 3, and the general data template has uuid, name, version, languageType, contentType, required, validation, and content fields.
  • the uuid field is configured to define a unique identifier of the general data template.
  • the name field is configured to define a name of the general data template.
  • the version field is configured to define a version of the general data template.
  • the languageType field defines a language type implementing the general data template.
  • the contentType field defines a data type.
  • the required field defines whether the data is required.
  • the validation field is configured for logical validation, and may contain a validation script or link to external services to determine whether a data format is correct and determine whether data conforms to rules, for example, whether the data is within a predetermined range.
  • the content field may be nested with other data templates.
  • Step S103 of instantiating the general data template and the general workflow template includes the following steps.
  • the general data template may be configured to define data needing to be collected and transmitted in an execution process of the general workflow template.
  • the general data template and the general workflow template are combined to meet the needs of actual transaction processes.
  • Required data is input according to the transaction process. Specifically, for the start node, the input data is input by the user, and for other workflow nodes, the input data may be data in a data template received by the workflow node.
  • step S1041 a current workflow node in the instantiated general workflow template is acquired, it is determined, based on the audit attribute, whether the current workflow node needs to be certified, if yes, the process proceeds to step S1042, and if no, the process proceeds to step S1044.
  • step S1042 acquiring the instantiated current workflow node, acquiring data needing to be received or sent, which is defined in the general workflow template by the current workflow node, and a data template defined in an instantiating process, and sending the data and the data template to the certification party for certification audit;
  • the certification party may be a third-party certification authority, and a certification audit system of the third-party certification authority audits data and data in the data template.
  • step S1043 after passing the certification audit, performing, by the certification party, Hash calculation on the data and the data template to obtain a Hash value, and sending the Hash value to the blockchain for certification deposition;
  • the data template participating in the Hash calculation refers to the data in the data template.
  • the reason for not directly uploading original data is that the blockchain is a publicly accessible network, and uploading the original data will cause data leakage. Therefore, the original data is stored in a centralized system of the certification party, and the Hash value is stored on the blockchain, which can ensure the traceability of data in the centralized system.
  • the certification party may obtain an ID of the certification deposition operation, and associate the ID with original data.
  • step S1044 it is determined whether the current workflow node is an end node, if yes, the method is ended, and if no, the process proceeds to step S1045.
  • step S1045 the current workflow node is set as a next workflow node, and the process proceeds to step S1042.
  • the following example embodiments illustrate the blockchain-based workflow node certification method of an identity card-based KYC (know-your-customer) certification transaction process.
  • a certification party defines a KYC general workflow template.
  • the KYC general workflow template is specifically defined as follows.
  • the KYC general workflow template has four workflow nodes.
  • the first workflow node is a start node, which represents the start of a KYC transaction process.
  • the start node does not carry out any transaction description, but only informs the KYC transaction process to start from this node.
  • a target attribute of this node indicates information of a next process node.
  • the second workflow node is a data submission node, which is defined as a task node with a node name Submit, and configured to wait for a user to submit information, and describe, in the to attribute of render, that it should submit a data template set with an ID value to a next node when this node task is ended, that is, a data template with the same ID value, which is defined in the KYC general data template. Only after the user submits data conforming what is defined in the data template, the workflow node will be ended and a next workflow node will be started.
  • the third workflow node is a data audit node, which is also defined as a task node with a node name Audit, and configured to wait for an audit service provider to audit the data submitted by the user, and describe, in the from attribute of render of the workflow node, a data template needing to be received from a previous node.
  • the to attribute of render is defined in the Submit node, a data template with an ID 9435d866-7107-4b7c-8243-180e8c3a0ccc needs to be transmitted, and target is specified as a node with an id 893b9c55-b915-482d-8723-852fc22e7d26, that is, the Audit node.
  • the from attribute of render of the Audit node defines a data template with an ID 9435d866-7107-4b7c-8243-180e8c3a0ccc, which needs to be received.
  • the transmission of a data template between two workflow nodes has been defined. In an actual process, what is transmitted is not the template itself, but data contained in the template, that is, data information that is filled in by the user and generated through the workflow node.
  • the fourth workflow node is an end node, which indicates that the KYC transaction process is ended here.
  • step S202 the certification party establishes a KYC general data template.
  • the KYC general data template is specifically defined as follows.
  • the KYC general data template defines four items of information that a user must fill in, including a name, an identity card number, an identity card front photo, and an identity card back photo. A regular expression verification on the identity card number has been added for the identity card number.
  • the following data information is obtained.
  • data required in the content field in the KYC general data template is obtained.
  • uuid unique ID of data, which is generated every time the user submits data.
  • 66286228-c455-4b82-957c-d1e8b1078f09 is associated with Name in the data template to acquire the name of the user;
  • 1dcabbf0-5e70-4fd4-87ba-e043e7a5c0ad is associated with IDCard in the data template to acquire the identity card number of the user;
  • b9e77f0b-121e-4c8a-9bad-31f2cf74e63e is associated with IDCard Photo Front in the data template to acquire the identity card front photo of the user;
  • 3653da78-0c3c-4d9e-94ff-d642f7706d3a is associated with IDCard Photo Back in the data template to acquire the identity card back photo of the user.
  • the system should verify actual data according to the data template defined in the KYC general data template to determine whether the submitted data content is correct.
  • step S203 the KYC general workflow template and the KYC general data template are instantiated based on the KYC general workflow template and the data input by the user.
  • the KYC general workflow template and the KYC general data template are instantiated, and the instantiated KYC general workflow template and KYC general data template are combined.
  • step S204 the determination shows that an audit attribute value in an Audit workflow node is true, indicating that the workflow node needs to be certified.
  • Data needing to be received which is defined by the Audit workflow node in the general workflow template, and a received data template are acquired.
  • what is transmitted is not the template itself, but data contained in the template.
  • the data and the data template are sent to the certification party for certification audit.
  • the certification party needs to audit an identity card number, a name, an identity card front photo, and an identity card back photo submitted by the user.
  • the certification party performs Hash calculation on the data and the data in the data template to obtain a Hash value, and sends the Hash value to a blockchain for certification deposition.
  • the certification party may obtain an ID of the certification deposition operation and associate the ID with original data.
  • FIG. 4 is a functional block diagram of one example of a blockchain-based workflow node certification device according to the present disclosure.
  • the device includes:
  • a general workflow template module configured to establish, by a certification party, a general workflow template using a JSON language, the general workflow template comprising a plurality of workflow nodes each having an audit attribute for indicating whether the workflow node needs to be certified;
  • a general data template module configured to establish, by the certification party, a general data template using the JSON language based on the general workflow template, the general data template defining data needing to be collected and transmitted in a workflow execution process;
  • an instantiating module configured to instantiate the general data template and the general workflow template
  • a certification and deposition module configured to acquire a current workflow node in the instantiated general workflow template, determine, based on the audit attribute, whether the current workflow node needs to be certified, if yes, certify, by a centralized certification party, data needing to be received or sent by the current workflow node defined in the general workflow template and a data template defined in an instantiating process, and deposit certification, by a blockchain, for the data needing to be received by the current workflow node and the data template received in the instantiating process, the certification and certification deposition for the data template referring to the certification and certification deposition for specific data in the data template.
  • the general data template has uuid, name, version, languageType, contentType, required, validation, and content fields
  • the uuid field is configured to define a unique identifier of the general data template
  • the name field is configured to define a name of the general data template
  • the version field is configured to define a version of the general data template
  • the languageType field defines a language type implementing the general data template
  • the contentType field defines a data type
  • the required field defines whether the data is required
  • the validation field is configured for logical validation, and may contain a validation script or link to external services to determine whether a data format is correct
  • the content field may be nested with other data templates.
  • the certification and deposition module includes:
  • a first determination sub-module configured to acquire a current workflow node in the instantiated general workflow template, and determine, based on the audit attribute, whether the current workflow node needs to be certified;
  • a certification sub-module configured to acquire the instantiated current workflow node, acquire data needing to be received or sent, which is defined in the general workflow template by the current workflow node, and a data template defined in an instantiating process, and send the data and the data template to the certification party for certification audit;
  • a deposition sub-module configured to perform, by the certification party, Hash calculation on the data and the data template after passing the certification audit to obtain a Hash value, and send the Hash value to the blockchain for certification deposition;
  • a second determination sub-module configured to determine whether the current workflow node is an end node
  • a setting sub-module configured to set the current workflow node as a next workflow node.
  • an association sub-module is also included, which is configured to obtain, by the certification party, an ID of the certification deposition operation after the blockchain completes the certification deposition and synchronization, and associate the ID with original data.
  • An embodiment of the present disclosure further provides a blockchain-based workflow node certification system is provided, including:
  • a processor configured to execute a plurality of instructions
  • a memory configured to store the plurality of instructions.
  • the plurality of instructions are configured to be stored by the memory and loaded by the processor to perform the blockchain-based workflow node certification method as described above.
  • An embodiment of the present disclosure further provides a computer-readable storage medium.
  • the storage medium stores a plurality of instructions therein that are configured to be loaded by a processor and perform the blockchain-based workflow node certification method as described above.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the illustrated and described units is only a logical function division, and there may be other divisions in actual implementation.
  • multiple units or components may be combined or may be integrated into another system, or some features may be ignored or not executed.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices, or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objective of the solution of the present embodiment.
  • each embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above integrated unit may be implemented in the form of hardware or in the form of hardware and a software functional unit.
  • the above integrated unit implemented in the form of the software functional unit may be stored in a computer-readable storage medium.
  • the above software functional unit is stored in a storage medium and includes a plurality of instructions to make a computer device (which may be a personal computer, a physical server, or a network cloud server, etc., required to be installed with, e.g., Windows or Windows Server operating systems) to perform part of the steps of the method in each embodiment of the present disclosure.
  • the aforementioned storage medium includes one or more of: a U disk, a mobile hard disk, a Read-Only Memory (ROM) , a Random Access Memory (RAM) , a magnetic disk or an optical disk, and other media that may store program code.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Human Resources & Organizations (AREA)
  • Computer Security & Cryptography (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Economics (AREA)
  • Operations Research (AREA)
  • General Business, Economics & Management (AREA)
  • Data Mining & Analysis (AREA)
  • Tourism & Hospitality (AREA)
  • Quality & Reliability (AREA)
  • Marketing (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • General Health & Medical Sciences (AREA)
  • Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Stored Programmes (AREA)

Abstract

A blockchain-based workflow node certification method and device. The method includes: a certification party establishing a general workflow template, the general workflow template including a plurality of workflow nodes each having an audit attribute for indicating whether the workflow node needs to be certified; the certification party establishing a general data template based on the general workflow template; instantiating the general data template and the general workflow template; and acquiring a current workflow node in the instantiated general workflow template, determining, based on the audit attribute, whether the current workflow node needs to be certified, if yes, performing certification by a centralized certification party, and depositing certification by a blockchain. Users can create and modify transaction processes as needed to meet the needs of changeable transaction. By combining central certification with blockchain certification deposition, the security of workflow node process implementation and the privacy of specific data are ensured.

Description

BLOCKCHAIN-BASED WORKFLOW NODE CERTIFICATION METHOD AND DEVICE Technical Field
The present disclosure relates to the field of workflow information security, and more particularly, to a blockchain-based workflow node certification method and device.
Background
In a current software system, there are two ways to implement specific transaction processes. One way is to directly implement specific functions with code after collecting demands and write the code into the software system. The other way is to write the code into the software system in a process modeling manner. Users can flexibly modify the transaction process as needed.
However, in the prior art, no excellent security determination mechanism has been established for the security of specific data of workflow nodes, and there are risks such as data tampering and data leakage.
Summary of the Invention
In order to solve the above technical problem, the present disclosure provides a blockchain-based workflow node certification method and device. The method and the device are configured to solve the technical problems of data tampering and data leakage caused by the lack of a scheme for certifying specific data of workflow nodes in the prior art.
According to a first aspect of the present disclosure, a blockchain-based workflow node certification method is provided, including:
step S101: establishing, by a certification party, a general workflow template using a JSON language, the general workflow template comprising a plurality of workflow nodes each having an audit attribute for indicating whether the workflow node needs to be certified;
step S102: establishing, by the certification party, a general data template using the JSON language based on the general workflow template, the general data template defining data needing to be collected and transmitted in a workflow execution process;
step S103: instantiating the general data template and the general workflow template; and
step S104: acquiring a current workflow node in the instantiated general workflow template, determining, based on the audit attribute, whether the current workflow node needs to be certified, if yes, certifying, by a centralized certification party, data needing to be received or sent by the current workflow node defined in the general workflow template and a data template defined in an instantiating process, and depositing certification, by a blockchain, for the data needing to be received by the current workflow node and the data template received in the instantiating process, the certification and certification deposition for the data template referring to the certification and certification deposition for specific data in the data template.
Further, the general data template has uuid, name, version, languageType, contentType, required, validation, and content fields, the uuid field is configured to define a unique identifier of the general data template, the name field is configured to define a name of the general data template, the version field is configured to define a version of the general data template, the languageType field defines a language type implementing the general data template, the contentType field defines a data type, the required field defines whether the data is required, the validation field is configured for logical validation, and may contain a validation script or link to external services to determine whether a data format is correct, and the content field may be nested with other data templates.
Further, step S104 includes:
step S1041: acquiring a current workflow node in the instantiated general workflow template, determining, based on the audit attribute, whether the current workflow node needs to be certified, if yes, proceeding to step S1042, and if no, proceeding to step S1044;
step S1042: acquiring the instantiated current workflow node, acquiring data needing to be received or sent, which is defined in the general workflow template by the current workflow node, and a data template defined in an instantiating process, and sending the data and the data template to the certification party for certification audit;
step S1043: after passing the certification audit, performing, by the certification party, Hash  calculation on the data and the data template to obtain a Hash value, and sending the Hash value to the blockchain for certification deposition;
step S1044: determining whether the current workflow node is an end node, if yes, ending the method, and if no, proceeding to step S1045; and
step S1045: setting the current workflow node as a next workflow node, and proceeding to step S1042.
Further, after the blockchain completes the certification deposition and synchronization, the certification party obtains an ID of the certification deposition operation, and associates the ID with original data.
According to a second aspect of the present disclosure, a blockchain-based workflow node certification device is provided, including:
a general workflow template module, configured to establish, by a certification party, a general workflow template using a JSON language, the general workflow template comprising a plurality of workflow nodes each having an audit attribute for indicating whether the workflow node needs to be certified;
a general data template module, configured to establish, by the certification party, a general data template using the JSON language based on the general workflow template, the general data template defining data needing to be collected and transmitted in a workflow execution process;
an instantiating module, configured to instantiate the general data template and the general workflow template; and
a certification and deposition module, configured to acquire a current workflow node in the instantiated general workflow template, determine, based on the audit attribute, whether the current workflow node needs to be certified, if yes, certify, by a centralized certification party, data needing to be received or sent by the current workflow node defined in the general workflow template and a data template defined in an instantiating process, and deposit certification, by a blockchain, for the data needing to be received by the current workflow node and the data template received in the instantiating process, the certification and certification deposition for the  data template referring to the certification and certification deposition for specific data in the data template.
Further, the general data template has uuid, name, version, languageType, contentType, required, validation, and content fields, the uuid field is configured to define a unique identifier of the general data template, the name field is configured to define a name of the general data template, the version field is configured to define a version of the general data template, the languageType field defines a language type implementing the general data template, the contentType field defines a data type, the required field defines whether the data is required, the validation field is configured for logical validation, and may contain a validation script or link to external services to determine whether a data format is correct, and the content field may be nested with other data templates.
Further, the certification and certification deposition module includes:
a first determination sub-module, configured to acquire a current workflow node in the instantiated general workflow template, and determine, based on the audit attribute, whether the current workflow node needs to be certified;
a certification sub-module, configured to acquire the instantiated current workflow node, acquire data needing to be received or sent, which is defined in the general workflow template by the current workflow node, and a data template defined in an instantiating process, and send the data and the data template to the certification party for certification audit;
a deposition sub-module, configured to perform, by the certification party, Hash calculation on the data and the data template after passing the certification audit to obtain a Hash value, and send the Hash value to the blockchain for certification deposition;
a second determination sub-module, configured to determine whether the current workflow node is an end node; and
a setting sub-module, configured to set the current workflow node as a next workflow node.
Further, an association sub-module is also included, which is configured to obtain, by the certification party, an ID of the certification deposition operation after the blockchain completes  the certification deposition and synchronization, and associate the ID with original data.
According to a third aspect of the present disclosure, a blockchain-based workflow node certification system is provided, including:
a processor, configured to execute a plurality of instructions; and
a memory, configured to store the plurality of instructions.
The plurality of instructions are configured to be stored by the memory and loaded by the processor to perform the blockchain-based workflow node certification method as described previously.
According to a fourth aspect of the present disclosure, a computer-readable storage medium is provided. The storage medium stores a plurality of instructions therein that are configured to be loaded by a processor and perform the blockchain-based workflow node certification method as described previously.
According to the above solution of the present disclosure, users can create and modify transaction processes as needed to meet the needs of changeable transaction. By combining central certification with blockchain certification deposition and certifying workflow node data needing to be certified, the security of workflow node process implementation and the privacy of specific data are ensured.
The above description is only an overview of the technical solution of the present disclosure. In order to understand the technical means of the present disclosure more clearly and implement it in accordance with the content of the specification, preferred embodiments of the present disclosure will be described in detail below with the accompanying drawings.
Brief Description of the Drawings
The drawings constituting a part of the present disclosure are used to provide a further understanding of the present disclosure. The present disclosure provides the following drawings for illustration. In the drawings:
FIG. 1 is a flowchart of a blockchain-based workflow node certification method according to the present disclosure;
FIG. 2 is a structural diagram of a general workflow template according to the present disclosure;
FIG. 3 is a structural diagram of a general data template according to the present disclosure; and
FIG. 4 is a block diagram of components of a blockchain-based workflow node certification device according to the present disclosure.
Detailed Description
FIG. 1 is a flowchart of one example implementation of a blockchain-based workflow node certification method according to the present disclosure. As shown in FIG. 1, the method includes the following steps:
step S101: establishing, by a certification party, a general workflow template using a JSON language, the general workflow template comprising a plurality of workflow nodes each having an audit attribute for indicating whether the workflow node needs to be certified;
step S102: establishing, by the certification party, a general data template using the JSON language based on the general workflow template, the general data template defining data needing to be collected and transmitted in a workflow execution process;
step S103, instantiating the general data template and the general workflow template; and
step S104, acquiring a current workflow node in the instantiated general workflow template, determining, based on the audit attribute, whether the current workflow node needs to be certified, if yes, a centralized certification party certifying data needing to be received or sent by the current workflow node defined in the general workflow template and a data template defined in an instantiating process, and a blockchain depositing the certification for the data needing to be received by the current workflow node and the data template received in the instantiating process.
The certification and certification deposition for the data template refers to the certification and certification deposition for specific data in the data template.
Step S101 of establishing, by a certification party using a JSON language, a general  workflow template that includes a plurality of workflow nodes each having an audit attribute for indicating whether the workflow node needs to be certified includes the following steps.
The certification party may be a third-party certification authority, the general workflow template is configured to describe an actual transaction process, a user may determine various nodes that need to be experienced in the transaction process according to transaction and functions to be implemented by a software system, the general workflow template is then defined by the various nodes, and different nodes are connected in series through a specified node to form a complete transaction process. The software system may read and identify these nodes.
In the present embodiment, the general workflow template has a structure shown in FIG. 2, and the general workflow template has three fields: process_id, process_name, and definitions. The process_id field is configured to define a unique identifier of a transaction process corresponding to the general workflow template, the process_name field is configured to define a name of the transaction process, and the definitions field is configured to define various workflow nodes needed in the transaction process. Specifically, the definitions field may define a plurality of workflow nodes, and each workflow node has node_id, node_name, title, type, target, render, and audit fields. The node_id field defines a unique identifier of a workflow node, the node_name field defines a name of the workflow node, the title field defines a title of the workflow node, the type field is configured to define a type of the workflow node, and the type of the workflow node includes a start node, an intermediate task node, or an end node. The target field is configured to define a next node ID after the workflow node is executed, and configured to indicate an execution order of the workflow nodes, the render field defines the input and output of the workflow node through the from and to attributes, and the audit field is configured to define whether the node needs to be certified.
Other fields may be set in the general workflow template in combination with specific transaction processes.
A complex transaction process may include a plurality of start nodes. For example, a user may actively initiate the same transaction process and submit relevant information, or a server  may passively initiate the same transaction process and acquire the relevant information from the user.
Step S102 of establishing, by the certification party using the JSON language based on the general workflow template, a general data template that defines data needing to be collected and transmitted in a workflow execution process includes the following steps.
In the present embodiment, the general data template has a structure shown in FIG. 3, and the general data template has uuid, name, version, languageType, contentType, required, validation, and content fields. The uuid field is configured to define a unique identifier of the general data template. The name field is configured to define a name of the general data template. The version field is configured to define a version of the general data template. The languageType field defines a language type implementing the general data template. The contentType field defines a data type. The required field defines whether the data is required. The validation field is configured for logical validation, and may contain a validation script or link to external services to determine whether a data format is correct and determine whether data conforms to rules, for example, whether the data is within a predetermined range. The content field may be nested with other data templates.
Other fields may be set in the general data template in combination with specific data needed by the general workflow template.
Step S103 of instantiating the general data template and the general workflow template includes the following steps.
The general data template may be configured to define data needing to be collected and transmitted in an execution process of the general workflow template. The general data template and the general workflow template are combined to meet the needs of actual transaction processes.
Required data is input according to the transaction process. Specifically, for the start node, the input data is input by the user, and for other workflow nodes, the input data may be data in a data template received by the workflow node.
Step S104 of acquiring a current workflow node in the instantiated general workflow template, determining, based on the audit attribute, whether the current workflow node needs to be certified, if yes, certifying, by a centralized certification party, data needing to be received or sent by the current workflow node defined in the general workflow template and a data template defined in an instantiating process, and depositing certification, by a blockchain, for the data needing to be received by the current workflow node and the data template received in the instantiating process in which the certification and certification deposition for the data template refers to the certification and certification deposition for specific data in the data template includes the following steps.
In step S1041, a current workflow node in the instantiated general workflow template is acquired, it is determined, based on the audit attribute, whether the current workflow node needs to be certified, if yes, the process proceeds to step S1042, and if no, the process proceeds to step S1044.
step S1042: acquiring the instantiated current workflow node, acquiring data needing to be received or sent, which is defined in the general workflow template by the current workflow node, and a data template defined in an instantiating process, and sending the data and the data template to the certification party for certification audit;
The certification party may be a third-party certification authority, and a certification audit system of the third-party certification authority audits data and data in the data template.
step S1043: after passing the certification audit, performing, by the certification party, Hash calculation on the data and the data template to obtain a Hash value, and sending the Hash value to the blockchain for certification deposition;
The data template participating in the Hash calculation refers to the data in the data template. The reason for not directly uploading original data is that the blockchain is a publicly accessible network, and uploading the original data will cause data leakage. Therefore, the original data is stored in a centralized system of the certification party, and the Hash value is stored on the blockchain, which can ensure the traceability of data in the centralized system.
After the blockchain completes the certification deposition and synchronization, the certification party may obtain an ID of the certification deposition operation, and associate the ID with original data.
In step S1044, it is determined whether the current workflow node is an end node, if yes, the method is ended, and if no, the process proceeds to step S1045.
In step S1045, the current workflow node is set as a next workflow node, and the process proceeds to step S1042.
The following example embodiments illustrate the blockchain-based workflow node certification method of an identity card-based KYC (know-your-customer) certification transaction process.
In step S201, a certification party defines a KYC general workflow template. In one example, the KYC general workflow template is specifically defined as follows.
Figure PCTCN2020120771-appb-000001
The KYC general workflow template has four workflow nodes. The first workflow node is a start node, which represents the start of a KYC transaction process. The start node does not carry out any transaction description, but only informs the KYC transaction process to start from this node. A target attribute of this node indicates information of a next process node.
The second workflow node is a data submission node, which is defined as a task node with a  node name Submit, and configured to wait for a user to submit information, and describe, in the to attribute of render, that it should submit a data template set with an ID value to a next node when this node task is ended, that is, a data template with the same ID value, which is defined in the KYC general data template. Only after the user submits data conforming what is defined in the data template, the workflow node will be ended and a next workflow node will be started.
The third workflow node is a data audit node, which is also defined as a task node with a node name Audit, and configured to wait for an audit service provider to audit the data submitted by the user, and describe, in the from attribute of render of the workflow node, a data template needing to be received from a previous node.
In the present embodiment, the to attribute of render is defined in the Submit node, a data template with an ID 9435d866-7107-4b7c-8243-180e8c3a0ccc needs to be transmitted, and target is specified as a node with an id 893b9c55-b915-482d-8723-852fc22e7d26, that is, the Audit node.
Meanwhile, the from attribute of render of the Audit node defines a data template with an ID 9435d866-7107-4b7c-8243-180e8c3a0ccc, which needs to be received. Through the above mode, the transmission of a data template between two workflow nodes has been defined. In an actual process, what is transmitted is not the template itself, but data contained in the template, that is, data information that is filled in by the user and generated through the workflow node.
The fourth workflow node is an end node, which indicates that the KYC transaction process is ended here.
In step S202, the certification party establishes a KYC general data template. The KYC general data template is specifically defined as follows.
Figure PCTCN2020120771-appb-000002
The KYC general data template defines four items of information that a user must fill in, including a name, an identity card number, an identity card front photo, and an identity card back photo. A regular expression verification on the identity card number has been added for the  identity card number.
After the user fills in the above four items of information, the following data information is obtained. After the data information is extracted, data required in the content field in the KYC general data template is obtained.
Figure PCTCN2020120771-appb-000003
Where
uuid: unique ID of data, which is generated every time the user submits data.
data: corresponding specific user data containing uuid, specific information for this embodiment being:
66286228-c455-4b82-957c-d1e8b1078f09 is associated with Name in the data template to acquire the name of the user;
1dcabbf0-5e70-4fd4-87ba-e043e7a5c0ad is associated with IDCard in the data template to acquire the identity card number of the user;
b9e77f0b-121e-4c8a-9bad-31f2cf74e63e is associated with IDCard Photo Front in the data template to acquire the identity card front photo of the user;
3653da78-0c3c-4d9e-94ff-d642f7706d3a is associated with IDCard Photo Back in the data template to acquire the identity card back photo of the user.
Preferably, during the acquisition, the system should verify actual data according to the data template defined in the KYC general data template to determine whether the submitted data content is correct.
In step S203, the KYC general workflow template and the KYC general data template are instantiated based on the KYC general workflow template and the data input by the user.
The KYC general workflow template and the KYC general data template are instantiated, and  the instantiated KYC general workflow template and KYC general data template are combined.
In step S204, the determination shows that an audit attribute value in an Audit workflow node is true, indicating that the workflow node needs to be certified. Data needing to be received, which is defined by the Audit workflow node in the general workflow template, and a received data template are acquired. In the present embodiment, what is transmitted is not the template itself, but data contained in the template. The data and the data template are sent to the certification party for certification audit. In the present embodiment, the certification party needs to audit an identity card number, a name, an identity card front photo, and an identity card back photo submitted by the user. After the certification audit is passed, the certification party performs Hash calculation on the data and the data in the data template to obtain a Hash value, and sends the Hash value to a blockchain for certification deposition. After the blockchain completes the certification deposition and synchronization, the certification party may obtain an ID of the certification deposition operation and associate the ID with original data.
FIG. 4 is a functional block diagram of one example of a blockchain-based workflow node certification device according to the present disclosure. In the illustrated example, the device includes:
a general workflow template module, configured to establish, by a certification party, a general workflow template using a JSON language, the general workflow template comprising a plurality of workflow nodes each having an audit attribute for indicating whether the workflow node needs to be certified;
a general data template module, configured to establish, by the certification party, a general data template using the JSON language based on the general workflow template, the general data template defining data needing to be collected and transmitted in a workflow execution process;
an instantiating module, configured to instantiate the general data template and the general workflow template; and
a certification and deposition module, configured to acquire a current workflow node in the instantiated general workflow template, determine, based on the audit attribute, whether the  current workflow node needs to be certified, if yes, certify, by a centralized certification party, data needing to be received or sent by the current workflow node defined in the general workflow template and a data template defined in an instantiating process, and deposit certification, by a blockchain, for the data needing to be received by the current workflow node and the data template received in the instantiating process, the certification and certification deposition for the data template referring to the certification and certification deposition for specific data in the data template.
Further, the general data template has uuid, name, version, languageType, contentType, required, validation, and content fields, the uuid field is configured to define a unique identifier of the general data template, the name field is configured to define a name of the general data template, the version field is configured to define a version of the general data template, the languageType field defines a language type implementing the general data template, the contentType field defines a data type, the required field defines whether the data is required, the validation field is configured for logical validation, and may contain a validation script or link to external services to determine whether a data format is correct, and the content field may be nested with other data templates.
Further, the certification and deposition module includes:
a first determination sub-module, configured to acquire a current workflow node in the instantiated general workflow template, and determine, based on the audit attribute, whether the current workflow node needs to be certified;
a certification sub-module, configured to acquire the instantiated current workflow node, acquire data needing to be received or sent, which is defined in the general workflow template by the current workflow node, and a data template defined in an instantiating process, and send the data and the data template to the certification party for certification audit;
a deposition sub-module, configured to perform, by the certification party, Hash calculation on the data and the data template after passing the certification audit to obtain a Hash value, and send the Hash value to the blockchain for certification deposition;
a second determination sub-module, configured to determine whether the current workflow node is an end node; and
a setting sub-module, configured to set the current workflow node as a next workflow node.
Further, an association sub-module is also included, which is configured to obtain, by the certification party, an ID of the certification deposition operation after the blockchain completes the certification deposition and synchronization, and associate the ID with original data.
An embodiment of the present disclosure further provides a blockchain-based workflow node certification system is provided, including:
a processor, configured to execute a plurality of instructions; and
a memory, configured to store the plurality of instructions.
The plurality of instructions are configured to be stored by the memory and loaded by the processor to perform the blockchain-based workflow node certification method as described above.
An embodiment of the present disclosure further provides a computer-readable storage medium. The storage medium stores a plurality of instructions therein that are configured to be loaded by a processor and perform the blockchain-based workflow node certification method as described above.
It should be noted that the embodiments in the present disclosure and the features in the embodiments may be combined with each other without conflict.
In the several embodiments provided by the present disclosure, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the illustrated and described units is only a logical function division, and there may be other divisions in actual implementation. For example, multiple units or components may be combined or may be integrated into another system, or some features may be ignored or not executed. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces,  devices, or units, and may be in electrical, mechanical or other forms.
The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objective of the solution of the present embodiment.
In addition, the functional units in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit. The above integrated unit may be implemented in the form of hardware or in the form of hardware and a software functional unit.
The above integrated unit implemented in the form of the software functional unit may be stored in a computer-readable storage medium. The above software functional unit is stored in a storage medium and includes a plurality of instructions to make a computer device (which may be a personal computer, a physical server, or a network cloud server, etc., required to be installed with, e.g., Windows or Windows Server operating systems) to perform part of the steps of the method in each embodiment of the present disclosure. The aforementioned storage medium includes one or more of: a U disk, a mobile hard disk, a Read-Only Memory (ROM) , a Random Access Memory (RAM) , a magnetic disk or an optical disk, and other media that may store program code.
Various modifications and additions can be made without departing from the spirit and scope of this disclosure. Features of each of the various embodiments described above may be combined with features of other described embodiments as appropriate in order to provide a multiplicity of feature combinations in associated new embodiments. Furthermore, while the foregoing describes a number of separate embodiments, what has been described herein is merely illustrative of the application of the principles of the present disclosure. Additionally, although particular methods herein may be illustrated and/or described as being performed in a specific order, the ordering is highly variable within ordinary skill to achieve aspects of the present disclosure. Accordingly, this description is meant to be taken only by way of example, and not to  otherwise limit the scope of this disclosure. Any simple alterations, equivalent changes, and modifications made to the above embodiments based on the technical essence of the present disclosure still fall within the scope of the technical solution of the present disclosure.

Claims (10)

  1. A blockchain-based workflow node certification method, comprising:
    step S101: establishing, by a certification party, a general workflow template, the general workflow template comprising a plurality of workflow nodes each having an audit attribute for indicating whether the workflow node needs to be certified;
    step S102: establishing, by the certification party, a general data template based on the general workflow template, the general data template defining data needing to be collected and transmitted in a workflow execution process;
    step S103: instantiating the general data template and the general workflow template; and
    step S104: acquiring a current workflow node in the instantiated general workflow template, determining, based on the audit attribute, whether the current workflow node needs to be certified, if yes, certifying, by a centralized certification party, data needing to be received or sent by the current workflow node defined in the general workflow template and a data template defined in an instantiating process, and depositing certification, by a blockchain, for the data needing to be received by the current workflow node and the data template received in the instantiating process, wherein the certification and certification deposition for the data template are the certification and certification deposition for specific data in the data template.
  2. The blockchain-based workflow node certification method according to claim 1, wherein the general data template has uuid, name, version, languageType, contentType, required, validation, and content fields, the uuid field is configured to define a unique identifier of the general data template, the name field is configured to define a name of the general data template, the version field is configured to define a version of the general data template, the languageType field defines a language type implementing the general data template, the contentType field defines a data type, the required field defines whether the data is required, the validation field is configured for logical validation, and may contain a validation script or link to external services to determine whether a data format is correct, and the content field may be nested with other data templates.
  3. The blockchain-based workflow node certification method according to claim 1, wherein step S104 comprises:
    step S1041: acquiring a current workflow node in the instantiated general workflow template, determining, based on the audit attribute, whether the current workflow node needs to be certified, if yes, proceeding to step S1042, and if no, proceeding to step S1044;
    step S1042: acquiring the instantiated current workflow node, acquiring data needing to be received or sent, which is defined in the general workflow template by the current workflow node, and a data template defined in an instantiating process, and sending the data and the data template to the certification party for certification audit;
    step S1043: after passing the certification audit, performing, by the certification party, Hash calculation on the data and the data template to obtain a Hash value, and sending the Hash value to the blockchain for certification deposition;
    step S1044: determining whether the current workflow node is an end node, if yes, ending the method, and if no, proceeding to step S1045; and
    step S1045: setting the current workflow node as a next workflow node, and proceeding to step S1042.
  4. The blockchain-based workflow node certification method according to claim 3, wherein after the blockchain completes the certification deposition and synchronization, the certification party obtains an ID of the certification deposition operation, and associates the ID with original data.
  5. A blockchain-based workflow node certification device, comprising:
    a general workflow template module, configured to establish, by a certification party, a general workflow template, the general workflow template comprising a plurality of workflow nodes each having an audit attribute for indicating whether the workflow node needs to be certified;
    a general data template module, configured to establish, by the certification party, a general data template based on the general workflow template, the general data template defining data  needing to be collected and transmitted in a workflow execution process;
    an instantiating module, configured to instantiate the general data template and the general workflow template; and
    a certification and deposition module, configured to acquire a current workflow node in the instantiated general workflow template, determine, based on the audit attribute, whether the current workflow node needs to be certified, if yes, certify, by a centralized certification party, data needing to be received or sent by the current workflow node defined in the general workflow template and a data template defined in an instantiating process, and deposit certification, by a blockchain, for the data needing to be received by the current workflow node and the data template received in the instantiating process, whereinthe certification and certification deposition for the data template are the certification and certification deposition for specific data in the data template.
  6. The blockchain-based workflow node certification device according to claim 5, wherein the general data template has uuid, name, version, languageType, contentType, required, validation, and content fields, the uuid field is configured to define a unique identifier of the general data template, the name field is configured to define a name of the general data template, the version field is configured to define a version of the general data template, the languageType field defines a language type implementing the general data template, the contentType field defines a data type, the required field defines whether the data is required, the validation field is configured for logical validation, and may contain a validation script or link to external services to determine whether a data format is correct, and the content field may be nested with other data templates.
  7. The blockchain-based workflow node certification device according to claim 5, wherein the certification and deposition module comprises:
    a first determination sub-module, configured to acquire a current workflow node in the instantiated general workflow template, and determine, based on the audit attribute, whether the current workflow node needs to be certified;
    a certification sub-module, configured to acquire the instantiated current workflow node, acquire data needing to be received or sent, which is defined in the general workflow template by the current workflow node, and a data template defined in an instantiating process, and send the data and the data template to the certification party for certification audit;
    a deposition sub-module, configured to perform, by the certification party, Hash calculation on the data and the data template after passing the certification audit to obtain a Hash value, and send the Hash value to the blockchain for certification deposition;
    a second determination sub-module, configured to determine whether the current workflow node is an end node; and
    a setting sub-module, configured to set the current workflow node as a next workflow node.
  8. The blockchain-based workflow node certification device according to claim 7, further comprising an association sub-module, configured to obtain, by the certification party, an ID of the certification deposition operation after the blockchain completes the certification deposition and synchronization, and associate the ID with original data.
  9. A blockchain-based workflow node certification system, comprising:
    a processor, configured to execute a plurality of instructions; and
    a memory, configured to store the plurality of instructions,
    wherein the plurality of instructions are configured to be stored by the memory and loaded by the processor to perform the blockchain-based workflow node certification method according to any one of claims 1-4.
  10. A computer-readable storage medium, storing a plurality of instructions therein that are configured to be loaded by a processor and perform the blockchain-based workflow node certification method according to any one of claims 1-4.
PCT/CN2020/120771 2019-10-14 2020-10-14 Blockchain-based workflow node certification method and device Ceased WO2021073516A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US17/768,349 US12238220B2 (en) 2019-10-14 2020-10-14 Blockchain-based workflow node certification method and device
JP2022519265A JP2022552110A (en) 2019-10-14 2020-10-14 Blockchain-based workflow node authentication method and device
EP20878003.1A EP4046009A4 (en) 2019-10-14 2020-10-14 Blockchain-based workflow node certification method and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910973162.6 2019-10-14
CN201910973162.6A CN110928534B (en) 2019-10-14 2019-10-14 Workflow node authentication method and device based on block chain

Publications (1)

Publication Number Publication Date
WO2021073516A1 true WO2021073516A1 (en) 2021-04-22

Family

ID=69848941

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/120771 Ceased WO2021073516A1 (en) 2019-10-14 2020-10-14 Blockchain-based workflow node certification method and device

Country Status (5)

Country Link
US (1) US12238220B2 (en)
EP (1) EP4046009A4 (en)
JP (1) JP2022552110A (en)
CN (1) CN110928534B (en)
WO (1) WO2021073516A1 (en)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110928534B (en) * 2019-10-14 2021-11-09 上海唯链信息科技有限公司 Workflow node authentication method and device based on block chain
CN112465448B (en) * 2020-11-11 2023-07-07 中国人民大学 Cross-organization workflow operation method and system based on blockchain
CN112433900B (en) * 2020-12-03 2023-03-14 海光信息技术股份有限公司 Method, system, device and storage medium for chip verification
CN114492844B (en) * 2022-02-17 2025-06-20 京东城市(北京)数字科技有限公司 Method, device, electronic device and storage medium for constructing machine learning workflow
US12537694B1 (en) * 2023-10-06 2026-01-27 The Bank Of New York Mellon System and method for validating an instruction with multiple digital signatures

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170244757A1 (en) * 2016-02-22 2017-08-24 Bank Of America Corporation System for external validation of secure process transactions
CN109767190A (en) * 2018-12-29 2019-05-17 中国工商银行股份有限公司 Across mechanism workflow processing method, platform and system based on block chain
US20190205884A1 (en) * 2017-12-28 2019-07-04 International Business Machines Corporation Converting processes into multiple blockchain smart contracts
CN110163755A (en) * 2019-04-30 2019-08-23 阿里巴巴集团控股有限公司 Block chain-based data compression and query method and device and electronic equipment
CN110278246A (en) * 2019-05-23 2019-09-24 阿里巴巴集团控股有限公司 A method, device and equipment for certificate deposit business transfer for consortium chain
CN110928534A (en) * 2019-10-14 2020-03-27 上海唯链信息科技有限公司 A blockchain-based workflow node authentication method and device

Family Cites Families (65)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6115690A (en) * 1997-12-22 2000-09-05 Wong; Charles Integrated business-to-business Web commerce and business automation system
US7937655B2 (en) * 2000-12-22 2011-05-03 Oracle International Corporation Workflows with associated processes
US7581011B2 (en) * 2000-12-22 2009-08-25 Oracle International Corporation Template based workflow definition
US8015600B2 (en) * 2000-12-22 2011-09-06 Oracle International Corporation Employing electronic certificate workflows
US7802174B2 (en) * 2000-12-22 2010-09-21 Oracle International Corporation Domain based workflows
US7761591B2 (en) * 2005-12-16 2010-07-20 Jean A. Graham Central work-product management system for coordinated collaboration with remote users
CA2881597C (en) * 2012-08-09 2017-06-06 Steven L. BUTH Multi-application workflow integration
US10628578B2 (en) * 2013-03-15 2020-04-21 Imagine Communications Corp. Systems and methods for determining trust levels for computing components using blockchain
CN103279840B (en) * 2013-06-08 2017-02-08 北京首钢自动化信息技术有限公司 Workflow engine implement method based on dynamic language and event processing mechanism
US20170236084A1 (en) * 2013-12-12 2017-08-17 NetSuite Inc. System and methods for implementing custom transactions within a multi-tenant platform
EP3257222B1 (en) * 2015-02-13 2019-10-16 Yoti Holding Limited Authentication of web content
US10007913B2 (en) * 2015-05-05 2018-06-26 ShoCard, Inc. Identity management service using a blockchain providing identity transactions between devices
US11436598B2 (en) * 2017-12-15 2022-09-06 Fmr Llc Social data tracking datastructures, apparatuses, methods and systems
US10033702B2 (en) * 2015-08-05 2018-07-24 Intralinks, Inc. Systems and methods of secure data exchange
US10362058B2 (en) * 2016-05-13 2019-07-23 Vmware, Inc Secure and scalable data transfer using a hybrid blockchain-based approach
WO2017219007A1 (en) * 2016-06-17 2017-12-21 Weimer Jonathan Blockchain systems and methods for user authentication
US11146535B2 (en) * 2016-10-12 2021-10-12 Bank Of America Corporation System for managing a virtual private ledger and distributing workflow of authenticated transactions within a blockchain distributed network
US10361853B2 (en) * 2016-10-12 2019-07-23 Bank Of America Corporation Automated data authentication and service authorization via cryptographic keys in a private blockchain
US10586210B2 (en) * 2016-11-30 2020-03-10 International Business Machines Corporation Blockchain checkpoints and certified checkpoints
US9998286B1 (en) * 2017-02-17 2018-06-12 Accenture Global Solutions Limited Hardware blockchain consensus operating procedure enforcement
CN106888087B (en) 2017-03-15 2018-09-04 腾讯科技（深圳）有限公司 A kind of method and apparatus of management certificate
US20180276625A1 (en) * 2017-03-27 2018-09-27 Justin Saye Contract ratification by automated agents through distributed ledger technology
US20180285996A1 (en) * 2017-04-03 2018-10-04 FutureLab Consulting Inc. Methods and system for managing intellectual property using a blockchain
US20180315055A1 (en) * 2017-05-01 2018-11-01 International Business Machines Corporation Blockchain For Issue/Defect Tracking System
JP2019016660A (en) 2017-07-05 2019-01-31 株式会社日本マイクロニクス Secondary battery and method for manufacturing secondary battery
US11321718B1 (en) * 2017-07-17 2022-05-03 Agasthya P. Narendranathan Systems and methods for blockchain based identity assurance and risk management
US10664797B2 (en) * 2017-07-19 2020-05-26 Amazon Technologies, Inc. Distributed ledger certification
WO2019032113A1 (en) * 2017-08-10 2019-02-14 Visa International Service Association Biometric verification process using certification token
CN107705114A (en) * 2017-08-31 2018-02-16 中链科技有限公司 Copyright data processing method, system and storage medium based on block chain technology
WO2019090005A1 (en) * 2017-11-01 2019-05-09 Clause, Inc. System and method for a blockchain-based network transitioned by a legal contract
US20190164157A1 (en) * 2017-11-28 2019-05-30 American Express Travel Related Services Company, Inc. Transaction authorization process using blockchain
US10162968B1 (en) * 2017-11-30 2018-12-25 Mocana Corporation System and method for securely updating a registered device using a development system and a release management system operated by an update provider and an update publisher
US10896418B2 (en) 2017-12-29 2021-01-19 Ebay Inc. Secure management of data files using a blockchain
US20190251573A1 (en) * 2018-02-09 2019-08-15 Airbus (S.A.S.) Systems and methods of verifying credentials of aircraft personnel using a blockchain computer system
US20190251199A1 (en) * 2018-02-14 2019-08-15 Ivan Klianev Transactions Across Blockchain Networks
CN108573341B (en) * 2018-03-23 2021-09-14 杭州云象网络技术有限公司 Workflow system construction method based on alliance chain
US20190384587A1 (en) * 2018-06-14 2019-12-19 Honeywell International Inc. System and method for installing loadable software airplane parts (lsap) of a set of certified orchestrated procedures using a blockchain network
US20190384842A1 (en) * 2018-06-19 2019-12-19 Toyota Motor Engineering & Manufacturing North America, Inc. Systems, methods and data structures for workflow blockchains
CN108922012B (en) * 2018-07-11 2020-05-19 北京大账房网络科技股份有限公司 Invoice checking method without leakage of original information based on block chain technology
US20200028691A1 (en) * 2018-07-20 2020-01-23 Honeywell International Inc. System and method for a blockchain based automated certifiable workflow process
CN109246197B (en) * 2018-08-15 2021-10-15 交通银行股份有限公司 Data processing method and device based on intelligent contract
US10880074B2 (en) * 2018-10-15 2020-12-29 Adobe Inc. Smart contract platform for generating and customizing smart contracts
CN113196270B (en) * 2018-10-19 2024-06-25 数字资产(瑞士)股份有限公司 Privacy-preserving verification and submission architecture
US20230274244A1 (en) * 2018-11-02 2023-08-31 Verona Holdings Sezc Trading analytics for cryptographic tokens that link to real world objects
US20230274245A1 (en) * 2018-11-02 2023-08-31 Verona Holdings Sezc Initiating a workflow in a digital token transaction system based on a recognized activity in a customer relationship management system
KR102206950B1 (en) * 2018-11-07 2021-01-26 어드밴스드 뉴 테크놀로지스 씨오., 엘티디. Management of private transactions on the blockchain network based on workflow
US12166858B2 (en) * 2018-11-14 2024-12-10 Royal Bank Of Canada System and method for storing contract data structures on permissioned distributed ledgers
CN109783572A (en) * 2018-12-14 2019-05-21 平安科技（深圳）有限公司 Block chain multichain creation method, device, equipment and storage medium
US20200211000A1 (en) * 2018-12-26 2020-07-02 Wipro Limited Blockchain network and nodes for tracking device as a service operations
US20200218815A1 (en) * 2019-01-04 2020-07-09 Comcast Cable Communications, Llc Systems and methods for distributed ledger management
CN109753288B (en) * 2019-01-14 2022-02-15 杭州云象网络技术有限公司 Intelligent contract compiling method suitable for formalized verification
US11971874B2 (en) * 2019-01-31 2024-04-30 Salesforce, Inc. Systems, methods, and apparatuses for implementing efficient storage and validation of data and metadata within a blockchain using distributed ledger technology (DLT)
US11811769B2 (en) * 2019-01-31 2023-11-07 Salesforce, Inc. Systems, methods, and apparatuses for implementing a declarative, metadata driven, cryptographically verifiable multi-network (multi-tenant) shared ledger
US11411739B2 (en) * 2019-02-07 2022-08-09 Internatiional Business Machines Corporation Smart device to impose trust at the edge of a blockchain
EP3909198B1 (en) * 2019-02-08 2024-09-18 Keyless Technologies Ltd Authentication processing service
US11038771B2 (en) * 2019-04-26 2021-06-15 Salesforce.Com, Inc. Systems, methods, and apparatuses for implementing a metadata driven rules engine on blockchain using distributed ledger technology (DLT)
US12609849B2 (en) * 2019-04-29 2026-04-21 Dtcc Digital (Us) Inc. Method, apparatus, and computer-readable medium for transaction management spanning multiple heterogeneous computing networks
CN110113334B (en) 2019-05-05 2021-09-10 江苏全链通信息科技有限公司 Contract processing method and device based on block chain and storage medium
US11507562B1 (en) * 2019-05-22 2022-11-22 Splunk Inc. Associating data from different nodes of a distributed ledger system
CN111316303B (en) * 2019-07-02 2023-11-10 创新先进技术有限公司 Systems and methods for blockchain-based cross-entity authentication
US11062307B2 (en) * 2019-08-26 2021-07-13 Capital One Services, Llc System and method of using localized blockchain to enable payment card use without connectivity
EP3692487B1 (en) * 2019-08-27 2022-08-24 Advanced New Technologies Co., Ltd. System and method for registering subscribable sub-states in blockchain
WO2019228552A2 (en) * 2019-08-27 2019-12-05 Alibaba Group Holding Limited System and method for blockchain-based notification
EP4035115A4 (en) * 2019-09-26 2023-07-26 Sliwka, Lukasz Jakub Distributed ledger lending systems having a smart contract architecture and methods therefor
KR102810469B1 (en) * 2019-10-07 2025-05-21 삼성전자주식회사 Electronic device and method for blockchain address management thereof

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170244757A1 (en) * 2016-02-22 2017-08-24 Bank Of America Corporation System for external validation of secure process transactions
US20190205884A1 (en) * 2017-12-28 2019-07-04 International Business Machines Corporation Converting processes into multiple blockchain smart contracts
CN109767190A (en) * 2018-12-29 2019-05-17 中国工商银行股份有限公司 Across mechanism workflow processing method, platform and system based on block chain
CN110163755A (en) * 2019-04-30 2019-08-23 阿里巴巴集团控股有限公司 Block chain-based data compression and query method and device and electronic equipment
CN110278246A (en) * 2019-05-23 2019-09-24 阿里巴巴集团控股有限公司 A method, device and equipment for certificate deposit business transfer for consortium chain
CN110928534A (en) * 2019-10-14 2020-03-27 上海唯链信息科技有限公司 A blockchain-based workflow node authentication method and device

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
US20240154813A1 (en) 2024-05-09
CN110928534B (en) 2021-11-09
US12238220B2 (en) 2025-02-25
JP2022552110A (en) 2022-12-15
CN110928534A (en) 2020-03-27
EP4046009A1 (en) 2022-08-24
EP4046009A4 (en) 2023-11-08

Similar Documents

Publication Publication Date Title
WO2021073516A1 (en) Blockchain-based workflow node certification method and device
KR102738475B1 (en) Extracting data from blockchain networks
CN109710236B (en) Service development and implementation method, device, platform and medium based on shared service
US11683281B2 (en) Systems and methods for initiating external actions via a group-based communication system
US12293352B2 (en) System and method for integration and validation
US11038685B1 (en) Correcting blockchain transactions with cryptocurrency type mistakes
CN110602056A (en) Service parameter transmission method and device
AU2010339650A1 (en) Syndication of multiple service instances
CN111381820A (en) Method and device for automatically generating API based on GUI
US11755631B2 (en) Workflow-based dynamic data model and application generation
CN111522840B (en) Label configuration method, device, equipment and computer readable storage medium
CN113052347A (en) Foreign currency reservation method, device and system based on 5G message
CN117992115B (en) System configuration processing method, device, equipment, medium and program product
CN109359794A (en) Service access method, apparatus, electronic device, and computer-readable storage medium
CN112256689A (en) Service data cleaning method and device and electronic equipment
CN111339189A (en) Data processing method and device and computer readable storage medium
CN118211928A (en) Request approval processing method and device
CN114722108B (en) Customer service data processing methods, devices, electronic equipment and storage media
US20240061890A1 (en) Hybrid metaverse using edge nodes to support a soft repository for event processing
CN114169733B (en) Resource allocation method and device
US12425226B2 (en) Multi-party blockchain transaction approval workflow
CN114970477B (en) A report generation method, device, equipment and storage medium
US20260072943A1 (en) Systems and methods for batch processing of blockchain operations
CN113536562A (en) Method, device and electronic device for generating message
CN112256688A (en) Service data cleaning method and device and electronic equipment

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: 20878003

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022519265

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 17768349

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020878003

Country of ref document: EP

Effective date: 20220516

WWG Wipo information: grant in national office

Ref document number: 17768349

Country of ref document: US

WWG Wipo information: grant in national office

Ref document number: 11202203355S

Country of ref document: SG

WWP Wipo information: published in national office

Ref document number: 11202203355S

Country of ref document: SG

WWW Wipo information: withdrawn in national office

Ref document number: 2020878003

Country of ref document: EP