WO2020224250A1 - Procédé, appareil et dispositif pour déclenchement de contrat intelligent, et support de stockage - Google Patents
Procédé, appareil et dispositif pour déclenchement de contrat intelligent, et support de stockage Download PDFInfo
- Publication number
- WO2020224250A1 WO2020224250A1 PCT/CN2019/122038 CN2019122038W WO2020224250A1 WO 2020224250 A1 WO2020224250 A1 WO 2020224250A1 CN 2019122038 W CN2019122038 W CN 2019122038W WO 2020224250 A1 WO2020224250 A1 WO 2020224250A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- contract
- trigger
- user
- type
- information
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3829—Payment protocols; Details thereof insuring higher security of transaction involving key management
Definitions
- This application relates to the field of computer technology, and in particular to a method, device, device and computer-readable storage medium for triggering smart contracts.
- Blockchain is an Internet protocol and a basic data structure. Just as HTTP is the most important application protocol in the Internet application layer, the blockchain is also a point-to-point transmission protocol in the application layer.
- the blockchain defines a distributed ledger by "block” and "chain”. "Blocks” are similar to transaction records in securities transactions, recording all equity transfer relationships that occurred within a specific time period; there is a strict and unique succession relationship between these "blocks", forming a "block” “chain”. The unique mechanism of the block chain guarantees the rationality and uniqueness of the "block” record content and the succession relationship. This process does not depend on a specific central node. Smart contracts are the core component of the blockchain and are used to implement business logic running on the blockchain. However, since the execution of the existing smart contract needs to be called by the business server, the execution cost of the contract is increased.
- the main purpose of this application is to provide a method, device, device, and computer-readable storage medium for triggering smart contracts, aiming to solve the technical problem of high execution costs of existing smart contracts.
- this application provides a method for triggering a smart contract, which includes the following steps:
- the trigger condition is a custom trigger type, obtain the condition script uploaded by the user, and add the condition script to the registration cache in the blockchain;
- the method further includes:
- the information to be queried is acquired and displayed for the current user to view.
- this application also provides a smart contract triggering device
- the smart contract triggering device includes:
- the trigger type judgment module is configured to obtain the trigger condition type in the contract registration instruction when receiving the contract registration instruction sent by the user, and determine whether the trigger condition type is a custom trigger type;
- the conditional script registration module is used to obtain the conditional script uploaded by the user if the trigger condition is a custom trigger type, and add the conditional script to the registration cache in the blockchain;
- the smart contract execution module is used to execute the corresponding contract transaction according to the preset smart contract when it monitors the occurrence of the transaction defined by the conditional script.
- the smart contract triggering device includes a processor, a memory, and a computer program that is stored on the memory and can be executed by the processor. Reading instructions, wherein when the computer-readable instructions are executed by the processor, the steps of the above-mentioned smart contract triggering method are realized.
- the present application also provides a computer-readable storage medium having computer-readable instructions stored on the computer-readable storage medium, and when the computer-readable instructions are executed by a processor, the implementation is as described above The steps of the trigger method of the smart contract.
- This application provides a method for triggering a smart contract, that is, when a contract registration instruction sent by a user is received, the trigger condition type in the contract registration instruction is obtained, and whether the trigger condition type is a custom trigger type; if If the trigger condition is a custom trigger type, the condition script uploaded by the user is obtained, and the condition script is added to the registration cache in the blockchain; when the occurrence of a transaction meeting the definition of the condition script is monitored, the The preset smart contract executes the corresponding contract transaction.
- this application triggers by registering the conditions to be completed in the smart contract, and according to the condition script uploaded by the user, sets the trigger rules of the smart contract, and executes the corresponding smart contract when a transaction that meets the trigger rule occurs Contract transactions.
- the automatic execution of the contract is realized without calling the clerk server to call the contract, which saves the contract execution cost, improves the execution efficiency of the contract, and solves the technical problem of the high execution cost of the existing smart contract.
- FIG. 1 is a schematic diagram of the hardware structure of the smart contract trigger device involved in the solution of the embodiment of the application;
- FIG. 2 is a schematic flowchart of the first embodiment of the triggering method of the smart contract of the application
- FIG. 3 is a schematic flowchart of a second embodiment of a method for triggering a smart contract under this application
- FIG. 4 is a schematic flowchart of a third embodiment of a method for triggering a smart contract in this application.
- FIG. 5 is a schematic diagram of the functional modules of the first embodiment of the triggering device of the smart contract of this application.
- the smart contract triggering method involved in the embodiments of the present application is mainly applied to the triggering device of the smart contract, and the triggering device of the smart contract may be a device with display and processing functions such as a PC, a portable computer, and a mobile terminal.
- FIG. 1 is a schematic diagram of the hardware structure of the smart contract trigger device involved in the solution of the embodiment of the application.
- the device for triggering the smart contract may include a processor 1001 (for example, a CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005.
- the communication bus 1002 is used to realize the connection and communication between these components;
- the user interface 1003 may include a display (Display), an input unit such as a keyboard (Keyboard);
- the network interface 1004 may optionally include a standard wired interface, a wireless interface (Such as WI-FI interface);
- the memory 1005 can be a high-speed RAM memory or a stable memory (non-volatile memory), such as a disk memory.
- the memory 1005 may optionally be a storage device independent of the aforementioned processor 1001.
- FIG. 1 does not constitute a limitation on the trigger device of the smart contract, and may include more or less components than shown in the figure, or a combination of certain components, or different components Layout.
- the memory 1005 as a computer-readable storage medium in FIG. 1 may include an operating system, a network communication module, and computer-readable instructions.
- the network communication module is mainly used to connect to the server and perform data communication with the server; and the processor 1001 can call computer-readable instructions stored in the memory 1005 and execute the smart contract triggering method provided in the embodiments of the present application.
- the embodiment of the application provides a method for triggering a smart contract.
- FIG. 2 is a schematic flowchart of a first embodiment of a method for triggering a smart contract in this application.
- the method for triggering the smart contract includes the following steps:
- Step S10 when receiving the contract registration instruction sent by the user, obtain the trigger condition type in the contract registration instruction, and determine whether the trigger condition type is a custom trigger type;
- the triggering of the condition to be completed is registered in the smart contract, and the triggering rule of the smart contract is set according to the condition script uploaded by the user, and when it is satisfied When the transaction triggering the rule, the contract transaction corresponding to the smart contract is executed.
- the automatic execution of the contract is realized without calling the clerk server to call the contract, which saves the cost of contract execution and improves the efficiency of contract execution.
- the user can send a contract registration instruction to the blockchain through the client, that is, the user will need to automatically execute the trigger rules of the smart contract to register.
- the trigger condition registration is specifically performed according to the trigger condition type in the contract registration instruction, such as a custom trigger type, a time trigger type or a blockchain height trigger type.
- the trigger condition type can be judged by judging the variable type in the trigger condition. For example, when the variable is time, it is the time trigger type, and when the variable is the blockchain height, it is the blockchain height trigger type.
- the variable is a user-defined trigger rule, it is a custom trigger type. Therefore, by determining whether the variable type in the trigger condition is a user-defined trigger rule, it is determined whether the trigger condition type is a custom trigger type.
- the custom trigger rule can be "When the number of people in the group reaches 3 before 10 o'clock on the same day, the group will start”. The trigger rule is "when the number of people in the group reaches 3 before 10 o'clock on the same day", the contract transaction is "open group”.
- Step S20 if the trigger condition is a custom trigger type, obtain the condition script uploaded by the user, and add the condition script to the registration cache in the blockchain;
- the variable type in the trigger condition is a user-defined trigger rule, for example, when the number of people in the group reaches 3 before 10 o'clock on the same day, the group is opened.
- the trigger rule is "when the number of people in the group reaches 3 before 10 o'clock on the same day", the contract transaction is "open group”.
- the user can set the trigger rule of the smart contract by uploading the condition script edited by himself.
- the condition script uploaded by the user is received, the condition script is added to the registration cache in the blockchain.
- the condition script is parsed, the trigger logic in the condition script is obtained, and the trigger logic generation monitoring command is added to the condition module.
- the monitoring module detects that the transaction that meets the trigger logic occurs, it will execute Regular contract transactions in the smart contract. Such as "start a group” or "issue wages”, etc.
- step S30 when it is monitored that a transaction meeting the definition of the conditional script occurs, the corresponding contract transaction is executed according to the preset smart contract.
- transaction monitoring is performed by the monitoring module.
- the verification node will first perform signature verification on the transaction to ensure the validity of the transaction. After the verification node passes the verification, the transaction will be automatically executed, that is, the transaction will be executed automatically.
- the contract transaction corresponding to the transaction in the smart contract.
- step S10 it further includes:
- the trigger condition type is a time trigger type
- obtain the trigger time in the contract registration instruction add the trigger time to the registration cache, and when the time variable is monitored as the trigger time, according to the smart
- the contract executes the corresponding contract transaction.
- the trigger condition type of the contract is a time trigger type.
- step S10 it further includes:
- the trigger condition type is the blockchain height trigger type
- obtain the blockchain height threshold in the contract registration instruction add the blockchain height threshold to the registration cache, and monitor the blockchain height
- the variable is the block chain height threshold
- the trigger condition type of the contract is the blockchain height trigger type.
- the height of the blockchain increases with the increase of transaction blocks added to the blockchain. Therefore, if the trigger condition type is the blockchain height trigger type, it means the number of transaction blocks in the blockchain When the number reaches the threshold, the contract transaction specified by the smart contract is performed.
- the monitoring module detects that the block chain height variable reaches the trigger block chain height value, a contract execution instruction is generated to execute the corresponding contract transaction according to the contract provisions in the smart contract, such as "block chain The transaction block increased to 1000".
- This embodiment provides a method for triggering a smart contract, that is, when a contract registration instruction sent by a user is received, the trigger condition type in the contract registration instruction is obtained, and whether the trigger condition type is a custom trigger type is determined; If the trigger condition is a custom trigger type, the condition script uploaded by the user is obtained, and the condition script is added to the registration cache in the blockchain; when it is monitored that a transaction meeting the definition of the condition script occurs, then Execute the corresponding contract transaction according to the preset smart contract.
- this application triggers by registering the conditions to be completed in the smart contract, and according to the condition script uploaded by the user, sets the trigger rules of the smart contract, and executes the corresponding smart contract when a transaction that meets the trigger rule occurs Contract transactions.
- the automatic execution of the contract is realized without calling the clerk server to call the contract, which saves the contract execution cost, improves the execution efficiency of the contract, and solves the technical problem of the high execution cost of the existing smart contract.
- FIG. 3 is a schematic flowchart of a second embodiment of a method for triggering a smart contract in this application.
- the method further includes:
- Step S41 When receiving the query instruction sent by the user, obtain the identity of the current user and the information to be queried in the query instruction, and determine whether the current user has the pending information based on the zero-knowledge proof and the identity. Information access to query information;
- the information reading authority of each alliance member is set through the zero-knowledge proof technology, so as to give different alliance members the corresponding information reading Permissions. Specifically, when a query instruction sent by a user is received, the information to be queried in the query instruction and the identity of the current user who sent the query instruction, such as an identity number or a work number, are obtained. It is determined whether there is an identity identifier of the current user in the authority user identity identifier corresponding to the information to be queried, and if so, the current user has the information reading permission of the information to be queried.
- Step S42 If the current user has the information reading permission of the information to be queried, acquire and display the information to be queried so that the current user can view it.
- the information to be queried is obtained, and the information to be queried is displayed on the current terminal interface so that the current User to view.
- step S41 it further includes:
- a corresponding reminder message without the read permission is generated according to the information to be queried, so as to remind the current user that the current user does not have Read the read permission of the information to be queried. Then, in order to facilitate the current user to understand his own corresponding read permission, according to the user read permission corresponding to the current user, obtain the relevant information corresponding to the user read permission, obtain the relevant information, and display the relevant information through the terminal interface , So that the current user can make the corresponding selection and view.
- the relevant information exceeds a preset information threshold, the information type and information summary corresponding to the relevant information are obtained, and the information type and information summary are displayed, so that the current user can make a corresponding selection and view.
- Fig. 4 is a schematic flowchart of a third embodiment of a method for triggering a smart contract in this application.
- the step S10 specifically includes:
- Step S11 when receiving the contract registration instruction sent by the user, obtain the verification signature of the user, and determine whether the user has the registration authority according to the verification signature;
- the registration authority judgment is performed on the user who registers the contract. Specifically, when the contract registration instruction sent by the user is received, the verification signature of the user is obtained, and the key information and user information in the verification signature are obtained. The key information and the user information are compared with the authority user information corresponding to the smart contract, so as to determine whether the user has the registration authority of the smart contract. That is, it is determined that the key in the verification signature is correct, and the user information matches the authority user information corresponding to the smart contract, and then it is determined that the user has the registration authority of the trigger condition of the smart contract.
- Step S12 when the user has the registration authority, obtain the trigger condition type in the contract registration instruction, and determine whether the trigger condition type is a custom trigger type.
- the trigger condition registration is specifically performed according to the trigger condition type in the contract registration instruction, such as a custom trigger type, a time trigger type, or a block Chain height trigger type.
- the trigger condition type can be judged by judging the variable type in the trigger condition. For example, when the variable is time, it is the time trigger type, and when the variable is the blockchain height, it is the blockchain height trigger type.
- the variable is a user-defined trigger rule, it is a custom trigger type. Therefore, by determining whether the variable type in the trigger condition is a user-defined trigger rule, it is determined whether the trigger condition type is a custom trigger type.
- step S30 it further includes:
- condition change reminder message is generated, and the condition change reminder message is sent to the contract member to remind the contract member.
- a trigger condition modification function is provided, that is, the permission user can modify the trigger condition of the smart contract with one key through the trigger condition modification function.
- the identity of the authority user may be verified, and when it is determined that the authority user is a legal modification user, the target trigger condition in the trigger condition modification instruction is acquired. Then the target trigger condition is replaced with the registered trigger condition defined by the condition script in the registration cache, thereby changing the trigger condition of the smart contract.
- the corresponding condition change reminder message is generated according to the registered trigger condition before the replacement and the target trigger condition after the replacement, and the condition change reminder message is sent to the corresponding contract member with viewing rights for The contract members are aware of the replacement of contract trigger conditions in time.
- the embodiment of the present application also provides a device for triggering a smart contract.
- FIG. 5 is a schematic diagram of the functional modules of the first embodiment of the device for triggering a smart contract in this application.
- the device for triggering the smart contract includes:
- the trigger type judgment module 10 is configured to obtain the trigger condition type in the contract registration instruction when the contract registration instruction sent by the user is received, and determine whether the trigger condition type is a custom trigger type;
- the conditional script registration module 20 is configured to, if the trigger condition is a custom trigger type, obtain the conditional script uploaded by the user, and add the conditional script to the registration cache in the blockchain;
- the smart contract execution module 30 is configured to execute the corresponding contract transaction according to the preset smart contract when it monitors that a transaction meeting the definition of the condition script occurs.
- the triggering device of the smart contract further includes:
- the time trigger module is configured to, if the trigger condition type is a time trigger type, obtain the trigger time in the contract registration instruction, add the trigger time to the registration cache, and when the time variable is monitored as the trigger time When, execute the corresponding contract transaction according to the smart contract.
- the triggering device of the smart contract further includes:
- the height trigger module is used to obtain the blockchain height threshold value in the contract registration instruction if the trigger condition type is the blockchain height trigger type, add the blockchain height threshold value to the registration cache, and set When it is detected that the block chain height variable is the block chain height threshold value, the corresponding contract transaction is executed according to the smart contract.
- the triggering device of the smart contract further includes:
- the information query module is used to obtain the identity of the current user and the information to be queried in the query instruction when receiving the query instruction sent by the user, and determine whether the current user has the identity based on the zero-knowledge proof and the identity identifier
- the information read permission of the information to be queried;
- the first information display module is configured to obtain and display the information to be queried for viewing by the current user if the current user has the information reading permission of the information to be queried.
- the triggering device of the smart contract further includes:
- the permission reminder module is configured to generate and display that if the current user does not have the information read permission of the information to be queried, it is generated and displayed that the current user does not have the read permission of the information to be queried;
- the second information display module is configured to obtain the user read permission corresponding to the current user, and display related information that the current user can read according to the user read permission, so that the current user can view it.
- the trigger type judgment module 10 specifically includes:
- the registration authority judging unit is configured to obtain the verification signature of the user when the contract registration instruction sent by the user is received, and determine whether the user has the registration authority according to the verification signature;
- the trigger type determining unit is configured to obtain the trigger condition type in the contract registration instruction when the user has the registration authority, and determine whether the trigger condition type is a custom trigger type.
- the triggering device of the smart contract further includes:
- the trigger condition modification module is used to obtain the target trigger condition in the trigger condition modification instruction when the trigger condition modification instruction is received, and replace the target trigger condition with the registered trigger condition defined by the condition script in the registration cache ;
- the condition change reminder module is used to generate a corresponding condition change reminder message according to the registered trigger condition and the target trigger condition, and send the condition change reminder message to the contract member to remind the contract member.
- each module in the above-mentioned smart contract triggering device corresponds to each step in the above-mentioned smart contract triggering method embodiment, and its functions and implementation processes are not repeated here.
- the embodiments of the present application also provide a computer-readable storage medium, and the computer-readable storage medium may be a non-volatile readable storage medium.
- the computer-readable storage medium of the present application stores computer-readable instructions, and when the computer-readable instructions are executed by a processor, the steps of the above-mentioned smart contract trigger method are realized.
- the method implemented when the computer-readable instruction is executed can refer to the various embodiments of the smart contract triggering method of the present application, which will not be repeated here.
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Computer Security & Cryptography (AREA)
- Finance (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
L'invention concerne un procédé, un appareil et un dispositif pour déclenchement de contrat intelligent et un support de stockage. Le procédé consiste à : lors de la réception d'une instruction d'enregistrement de contrat envoyée par un utilisateur, acquérir un type de condition de déclenchement dans l'instruction d'enregistrement de contrat, et déterminer si le type de condition de déclenchement est un type de déclenchement personnalisé (S10) ; si la condition de déclenchement est un type de déclenchement personnalisé, acquérir un script de condition téléchargé par l'utilisateur, et ajouter le script de condition à un cache d'enregistrement dans une chaîne de blocs (S20) ; et après détection de la survenue d'un événement satisfaisant la définition du script de condition, exécuter une transaction de contrat correspondante conformément à un contrat intelligent préalablement configuré (S30). Dans le procédé, lorsqu'il est détecté qu'un événement satisfaisant la règle de déclenchement se produit, une transaction de contrat correspondant au contrat intelligent est exécutée, ce qui permet d'obtenir une exécution automatique du contrat, en éliminant la nécessité d'appeler un serveur de ventes pour l'invocation de contrat, en réduisant les coûts d'exécution de contrat, en améliorant l'efficacité d'exécution de contrat et en résolvant le problème technique de coûts d'exécution élevés de contrats intelligents existants.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910376461.1A CN110264190A (zh) | 2019-05-07 | 2019-05-07 | 智能合约的触发方法、装置、设备及存储介质 |
CN201910376461.1 | 2019-05-07 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020224250A1 true WO2020224250A1 (fr) | 2020-11-12 |
Family
ID=67914330
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2019/122038 WO2020224250A1 (fr) | 2019-05-07 | 2019-11-29 | Procédé, appareil et dispositif pour déclenchement de contrat intelligent, et support de stockage |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN110264190A (fr) |
WO (1) | WO2020224250A1 (fr) |
Families Citing this family (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110264190A (zh) * | 2019-05-07 | 2019-09-20 | 深圳壹账通智能科技有限公司 | 智能合约的触发方法、装置、设备及存储介质 |
CN111176207B (zh) * | 2020-01-06 | 2021-11-23 | 上海电气自动化设计研究所有限公司 | 一种地铁车站一键式运营启动系统 |
SG11202102366SA (en) | 2020-06-08 | 2021-04-29 | Alipay Labs Singapore Pte Ltd | User management of blockchain-based custom clearance service platform |
WO2020169126A2 (fr) | 2020-06-08 | 2020-08-27 | Alipay Labs (singapore) Pte. Ltd. | Gestion d'autorisations d'utilisateur pour des services de dédouanement basés sur une chaîne de blocs |
CN111989663B (zh) * | 2020-06-08 | 2024-07-16 | 支付宝实验室(新加坡)有限公司 | 基于区块链的智能合约池 |
EP3844654B1 (fr) | 2020-06-08 | 2023-05-17 | Alipay Labs (Singapore) Pte. Ltd. | Enregistrement de document basé sur une chaîne de blocs pour le dédouanement |
CN111936995A (zh) | 2020-06-08 | 2020-11-13 | 支付宝实验室(新加坡)有限公司 | 海关清关数据的分布式存储 |
EP3844699A4 (fr) | 2020-06-08 | 2021-08-18 | Alipay Labs (Singapore) Pte. Ltd. | Traitement de données de dédouanement d'importation basé sur une chaîne de blocs |
CN111770201B (zh) * | 2020-08-31 | 2020-12-04 | 支付宝(杭州)信息技术有限公司 | 一种数据验证方法、装置及设备 |
CN112905554B (zh) * | 2021-02-07 | 2024-05-10 | 全链通有限公司 | 基于区块链的数据共享方法和装置 |
CN112837155B (zh) * | 2021-02-10 | 2024-05-31 | 中国人民银行数字货币研究所 | 区块链中智能合约的注册、执行方法和装置 |
CN113034137A (zh) * | 2021-03-12 | 2021-06-25 | 腾讯科技(深圳)有限公司 | 基于区块链的数据处理方法、装置及相关设备 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108475394A (zh) * | 2016-03-31 | 2018-08-31 | 汤森路透全球资源无限公司 | 用于向分布式分类账系统中的金融工具提供金融数据的系统和方法 |
US20180322588A1 (en) * | 2017-05-06 | 2018-11-08 | Adp, Llc | Implementation of payroll smart contract on a distributed ledger |
CN109347799A (zh) * | 2018-09-13 | 2019-02-15 | 深圳市图灵奇点智能科技有限公司 | 一种基于区块链技术的身份信息管理方法及系统 |
CN109684869A (zh) * | 2018-12-12 | 2019-04-26 | 杭州基尔区块链科技有限公司 | 一种去中心化芯片研发交易方法及系统 |
CN110264190A (zh) * | 2019-05-07 | 2019-09-20 | 深圳壹账通智能科技有限公司 | 智能合约的触发方法、装置、设备及存储介质 |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108665253A (zh) * | 2018-05-18 | 2018-10-16 | 百度在线网络技术(北京)有限公司 | 一种区块链网络的数据处理方法、装置、设备及存储介质 |
-
2019
- 2019-05-07 CN CN201910376461.1A patent/CN110264190A/zh active Pending
- 2019-11-29 WO PCT/CN2019/122038 patent/WO2020224250A1/fr active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108475394A (zh) * | 2016-03-31 | 2018-08-31 | 汤森路透全球资源无限公司 | 用于向分布式分类账系统中的金融工具提供金融数据的系统和方法 |
US20180322588A1 (en) * | 2017-05-06 | 2018-11-08 | Adp, Llc | Implementation of payroll smart contract on a distributed ledger |
CN109347799A (zh) * | 2018-09-13 | 2019-02-15 | 深圳市图灵奇点智能科技有限公司 | 一种基于区块链技术的身份信息管理方法及系统 |
CN109684869A (zh) * | 2018-12-12 | 2019-04-26 | 杭州基尔区块链科技有限公司 | 一种去中心化芯片研发交易方法及系统 |
CN110264190A (zh) * | 2019-05-07 | 2019-09-20 | 深圳壹账通智能科技有限公司 | 智能合约的触发方法、装置、设备及存储介质 |
Also Published As
Publication number | Publication date |
---|---|
CN110264190A (zh) | 2019-09-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2020224250A1 (fr) | Procédé, appareil et dispositif pour déclenchement de contrat intelligent, et support de stockage | |
WO2019109957A1 (fr) | Procédé, appareil, et dispositif de fourniture de service basé sur un bus de service d'entreprise (esb), et support d'informations lisible | |
WO2021006616A1 (fr) | Procédé pour fournir un service d'identifiant décentralisé relationnel et nœud de chaîne de blocs l'utilisant | |
WO2020233090A1 (fr) | Procédé, appareil et dispositif de configuration d'application basés sur une page h5, et support de stockage | |
WO2019174090A1 (fr) | Procédé, appareil et dispositif de commande de partage de fichier de capture d'écran, et support de stockage informatique | |
WO2020147385A1 (fr) | Procédé et appareil d'entrée de données, terminal et support d'informations lisible par ordinateur | |
WO2014069787A1 (fr) | Sécurité par le biais d'orchestrateurs de métadonnées | |
WO2020042464A1 (fr) | Procédé, appareil et dispositif d'interaction de données, et support d'informations lisible | |
WO2020253120A1 (fr) | Procédé, système et dispositif d'enregistrement de page web, et support de stockage informatique | |
WO2020000632A1 (fr) | Procédé, appareil et dispositif d'émission de facture, et support d'informations lisible par ordinateur | |
WO2023038381A1 (fr) | Système de collecte de données api et procédé associé | |
WO2020087981A1 (fr) | Procédé et appareil de génération de modèle d'audit de contrôle de risque, dispositif, et support de stockage lisible | |
WO2021141235A1 (fr) | Dispositif, système et procédé de gestion d'informations personnelles, et support non transitoire lisible par ordinateur associé | |
WO2019024485A1 (fr) | Procédé et dispositif de partage de données, et support de stockage lisible par ordinateur | |
WO2020062658A1 (fr) | Procédé et appareil de génération de contrat, dispositif et support de stockage | |
WO2013085144A1 (fr) | Procédé permettant de fournir un service d'invitation dans un groupe sns et serveur sns associé | |
WO2020233060A1 (fr) | Procédé et appareil de notification d'événement, serveur de notification d'événement et support de stockage | |
WO2020108111A1 (fr) | Procédé d'identification de comportement de fraude d'assurance médicale, appareil, dispositif et support de mémoire lisible | |
WO2014112754A1 (fr) | Procédé de pousser de service web, serveur de pousser de service web et serveur de fourniture de service web l'exécutant | |
WO2021003956A1 (fr) | Procédé, appareil et dispositif de gestion d'informations de produit et support d'enregistrement | |
WO2020119384A1 (fr) | Procédé, appareil et dispositif de détection d'anomalie d'assurance médicale sur la base d'une analyse de mégadonnées, et support | |
WO2020062641A1 (fr) | Procédé d'identification d'un rôle d'utilisateur, équipement utilisateur, support d'informations et appareil d'identification d'un rôle d'utilisateur | |
WO2018035929A1 (fr) | Procédé et appareil de traitement de code de vérification | |
WO2021040283A1 (fr) | Serveur de système de gestion de temps et de présence pouvant effectuer une gestion de temps et de présence sur la base d'informations d'accès ap sans fil, et son procédé de fonctionnement | |
WO2020062661A1 (fr) | Procédé, dispositif et appareil de vérification de cohérence de données de contrat et support d'enregistrement |
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: 19927846 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 19927846 Country of ref document: EP Kind code of ref document: A1 |