WO2020042464A1 - Procédé, appareil et dispositif d'interaction de données, et support d'informations lisible - Google Patents

Procédé, appareil et dispositif d'interaction de données, et support d'informations lisible Download PDF

Info

Publication number
WO2020042464A1
WO2020042464A1 PCT/CN2018/122639 CN2018122639W WO2020042464A1 WO 2020042464 A1 WO2020042464 A1 WO 2020042464A1 CN 2018122639 W CN2018122639 W CN 2018122639W WO 2020042464 A1 WO2020042464 A1 WO 2020042464A1
Authority
WO
WIPO (PCT)
Prior art keywords
interaction
request
interaction information
alliance chain
node
Prior art date
Application number
PCT/CN2018/122639
Other languages
English (en)
Chinese (zh)
Inventor
郭镭波
Original Assignee
深圳壹账通智能科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 深圳壹账通智能科技有限公司 filed Critical 深圳壹账通智能科技有限公司
Publication of WO2020042464A1 publication Critical patent/WO2020042464A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/101—Access control lists [ACL]

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a data interaction method, apparatus, device, and readable storage medium.
  • the current data interaction is based on a centralized server for data interaction, that is, the first terminal needs to perform data interaction with the second terminal, and the data needs to be sent to the server first, which is forwarded by the server to the second client.
  • the client receives After the data, the response result is sent to the server, and the server sends the response result to the first terminal to implement data interaction between the first terminal and the second terminal.
  • the main purpose of this application is to provide a data interaction method, device, device and readable storage medium, which aims to solve the existing technical problems of high data processing pressure and low reliability in the data interaction process.
  • the data interaction method includes steps:
  • a receiving node in the alliance chain When a receiving node in the alliance chain receives an interaction request for data interaction, it obtains first interaction information corresponding to the interaction request, wherein the alliance chain is set in a server;
  • the interaction request is executed.
  • the present application further provides a data interaction device, where the data interaction device includes:
  • An obtaining module configured to obtain first interaction information corresponding to the interaction request after a receiving node in the alliance chain receives an interaction request for data interaction, wherein the alliance chain is set in a server;
  • a detection module configured to detect whether the first interaction information exists in a white list and a first black list of each node of the alliance chain, and obtain a detection result
  • An execution module is configured to execute the interaction request if the detection result meets a first preset condition.
  • the present application further provides a data interaction device, where the data interaction device includes a memory, a processor, and computer-readable instructions stored on the memory and executable on the processor.
  • the computer-readable instructions when executed by the processor, implement the steps of the data interaction method described above.
  • the present application also provides a computer-readable storage medium, where the computer-readable instructions are stored, and when the computer-readable instructions are executed by a processor, the above-mentioned implementation is implemented. Steps of the data interaction method.
  • a node in the server alliance chain After a node in the server alliance chain receives an interaction request for data interaction, it detects whether the first interaction information corresponding to the interaction request exists in the white list and the first black list of each node in the alliance chain, and obtains the detection result. If the detection result meets the first preset condition, the interaction request is executed to send the interaction request to another terminal, so as to reduce the server's data interaction and reduce the server's data through the decentralization of the blockchain. Dealing with pressure, and because the nodes in the alliance chain are independent of each other and only authorized nodes can join the alliance chain, which improves the reliability of the server; further, because the nodes in the alliance chain share the whitelist and blacklist To improve the security of data interaction.
  • FIG. 1 is a schematic flowchart of a first embodiment of a data interaction method according to the present application
  • FIG. 2 is a schematic flowchart of a second embodiment of a data interaction method according to the present application.
  • FIG. 3 is a schematic flowchart of a third embodiment of a data interaction method according to the present application.
  • FIG. 4 is a functional schematic block diagram of a preferred embodiment of a data interaction device of the present application.
  • FIG. 5 is a schematic structural diagram of a hardware operating environment involved in the solution of the embodiment of the present application.
  • FIG. 1 is a schematic flowchart of a first embodiment of a data interaction method of this application.
  • This embodiment of the present application provides an embodiment of a data interaction method. It should be noted that although the logical sequence is shown in the flowchart, in some cases, the shown or described may be performed in a different order than here. A step of.
  • each node is described by a node execution entity in the alliance chain.
  • a blockchain is a chain composed of a series of blocks. In addition to recording the data of this block on each block, the Hash value of the previous block is recorded. In this way, a chain is formed.
  • a block consists of a block header and a block body.
  • the block header definition includes important fields such as the block height and the hash value of the previous block, and the block mainly stores transaction data.
  • Blockchains can be divided into three categories based on the openness of access permissions (also known as “decentralization”): public chains, private chains, and alliance chains.
  • Each node of the alliance chain usually has a corresponding physical organization, and can only join and exit the network after authorization.
  • the alliance chain is also a private chain in essence, but the nodes on the chain are controlled by multiple institutions, and the degree of privatization is lower than that of the private chain. At the same time, the permission control between the two will be different.
  • the read and write permissions of the alliance chain are oriented to all or part of the nodes on the chain, and the permission control design is more complicated.
  • Nodes refer to network nodes that participate in the blockchain network for transactions and data exchange. Each independent institution member can have one or more transaction nodes. Each transaction node is a set of physical networks, computers, and blockchain applications. Software and database combination. Between nodes, through TCP / IP (Transmission Control Protocol / Internet Protocol (Transmission Control Protocol / Internet Interconnection Protocol) protocols are interconnected.
  • Data interaction methods include:
  • step S10 when a receiving node in the alliance chain receives an interaction request for data interaction, it obtains first interaction information corresponding to the interaction request, wherein the alliance chain is set in a server.
  • the alliance chain is set in a server, and a node in the alliance chain that receives an interaction request sent by a user through its terminal is referred to as a receiving node.
  • the receiving node After the receiving node receives the interaction request for data interaction, the receiving node obtains the first interaction information corresponding to the interaction request.
  • the interaction request may be triggered by a corresponding user according to requirements.
  • the first interaction information includes, but is not limited to, a login account, an ID card number, and a mobile phone number.
  • the login account is the account used by the user to log in after registering in the alliance chain.
  • the interaction request carries the first interaction information. Therefore, after receiving the interaction request, the receiving node may extract the first interaction information in the interaction request to obtain the first interaction information.
  • Step S20 It is detected whether the first interaction information exists in a white list and a first black list of each node of the alliance chain, and a detection result is obtained.
  • each node has its own blacklist and whitelist, and nodes joining the alliance chain will share their own blacklist and whitelist.
  • the receiving node obtains the blacklist and whitelist shared by other nodes in the alliance chain, it will store the blacklist and whitelist of other nodes.
  • the blacklist corresponding to the receiving node and the blacklist shared by other nodes in the alliance chain are referred to as the first blacklist.
  • each node in the alliance chain has a corresponding node identifier.
  • the blacklist and whitelist carry the node identifier of the corresponding node. Therefore, the blacklist and whitelist corresponding to each node can be distinguished by the node identifier.
  • the receiving node After the receiving node obtains the first interaction information corresponding to the interaction request, the receiving node detects whether the first interaction information exists in the white list and the first black list of each node of the alliance chain, and obtains a detection result. It should be noted that due to a black list and a white list corresponding to a node, there are three cases of detection results obtained: respectively, in the first black list; in the white list; or, there is no first black list. In addition, it does not exist in the white list. Different detection results correspond to different result identifiers. In this embodiment, the expression form of the result identifier is not limited. For example, the result identifier stored in the first black list can be set to "00", and the result identifier stored in the white list can be set. It is "11", and the result identifier that is neither in the first blacklist nor in the whitelist is set to "01".
  • the detection results corresponding to different nodes also carry a node identifier to distinguish the detection results of different nodes. For example, if the node identifier of a certain node is "a”, the corresponding detection result is stored in the first blacklist, and the corresponding detection identifier is "a00". It can be known that the detection identifier is composed of a result identifier and a node identifier. Therefore, the detection result corresponding to the first interaction information can be determined by detecting the identifier. In this embodiment, a composition manner of a result identifier and a node identifier is not limited.
  • Step S30 If the detection result meets a first preset condition, execute the interaction request.
  • the receiving node After the receiving node obtains the detection result, the receiving node obtains a detection identifier corresponding to the detection result, and determines whether the detection result meets a first preset condition by using the detection identifier. If it is determined that the detection result meets the first preset condition, the receiving node executes the interaction request and sends the interaction request to another terminal.
  • the first preset conditions corresponding to different business scenarios may be different. For example, in a banking business scenario, the first preset conditions may be set such that a bank account cannot be stored in the first blacklist of any node of the alliance chain. It needs to be in the white list of at least two nodes of the alliance chain. In the loan business scenario, the preset conditions can be set such that the mobile phone number and / or ID card number cannot be stored in the first black list of any node of the alliance chain, and It exists in the white list of one of the nodes in the alliance chain.
  • the receiving node determines that the detection result does not meet the first preset condition, the receiving node refuses to execute the interaction request, generates prompt information, and sends the prompt information to the terminal corresponding to the interaction request.
  • the terminal After receiving the prompt information, the terminal outputs the prompt information to prompt the user that the interaction request is rejected to be executed according to the prompt information, or prompts the user that the execution of the interaction request failed according to the prompt information, so that the user can timely understand the execution result of the interaction request.
  • the terminal is not limited to the output mode of the prompt information.
  • the prompt information may be output through voice or text.
  • a node in the alliance chain After a node in the alliance chain receives an interaction request for data interaction, it detects whether the first interaction information corresponding to the interaction request exists in the white list and the first black list of each node in the alliance chain to obtain the detection result. If the detection result meets the first preset condition, the interaction request is executed to send the interaction request to another terminal, so as to reduce the server's data interaction and reduce the server's data through the decentralization of the blockchain. Dealing with pressure, and because the nodes in the alliance chain are independent of each other and only authorized nodes can join the alliance chain, which improves the reliability of the server; further, because the nodes in the alliance chain share the whitelist and blacklist To improve the security of data interaction.
  • the data interaction method further includes:
  • step S40 after detecting a registration request registered with the receiving node, it is detected whether the registration request meets the registration conditions of the alliance chain.
  • the receiving node checks whether the registration request meets the registration conditions of the alliance chain. It should be noted that, in the alliance chain, the registration conditions are set in advance, and the registration conditions can be set according to specific needs. If there are 10 nodes in the alliance chain, the registration conditions can be set to determine that the registration request meets the registration conditions of the alliance chain only when all 6 nodes agree to execute the registration request.
  • Step S50 If the registration request meets the registration conditions, execute the registration request, and check whether the interaction request is received after the registration request is successfully performed.
  • the receiving node executes the registration request, and after the registration request is successfully executed, that is, after the user successfully registers in the alliance chain, the receiving node detects whether an interaction request is received. It should be noted that after a user successfully registers with a node in the alliance chain, the user can perform data interaction at any node in the alliance chain.
  • the receiving node sends prompt information to the terminal corresponding to the registration request.
  • the terminal receives the prompt message, it outputs the prompt message, and prompts the user to fail to register according to the prompt message.
  • the data interaction method further includes:
  • Step S60 if the detection result does not meet the first preset condition, obtain second interaction information corresponding to the interaction request.
  • the receiving node obtains the second interaction information corresponding to the interaction request.
  • the second interaction information is information corresponding to the risk control strategy of the receiving node, and the second interaction information may be different from the first interaction information or the same as the first interaction information.
  • the risk control strategy corresponding to each node is set in advance.
  • Step S70 Obtain a wind control policy corresponding to the receiving node, and detect whether the second interaction information meets a second preset condition by using the wind control policy.
  • the receiving node obtains its risk control strategy, and detects whether the second interaction information meets the second preset condition through the risk control strategy.
  • a node's risk control strategy is to detect whether a bank card number is on its blacklist and whether an ID card number is on its whitelist. If the user's bank card number is on the black list and / or the ID card number is not on the white list, the receiving node determines that the second interaction information does not meet the second preset condition; if the bank card number is not on the black list, And the ID number is stored in the white list, the receiving node determines that the second interaction information meets the second preset condition.
  • the priority of the second interaction information may be set according to the type of the data interaction request. For example, when the data interaction request is a balance inquiry request, the priority of the bank card account is set higher than the priority of the ID card number, and the priority of the ID card number is higher than the priority of the mobile phone number. When the data interaction request is When making a loan request, the priority of the phone number is set higher than the priority of the ID card number, and the priority of the ID number is higher than the priority of the login account. At this time, when setting the risk control policy, the risk control policies corresponding to different types of data interaction requests may be set according to the priority of the second interaction information.
  • the risk control policy of the interactive request corresponding to the query balance can be set as follows: when it is detected that the bank card account does not exist in the blacklist of each node of the alliance chain, and the ID card number or mobile phone number exists in the whitelist of one of the nodes of the alliance chain When the receiving node determines that the second interaction information meets the second preset condition; when it is detected that the bank card account exists in a blacklist of one of the nodes in the alliance chain, and / or the identity card number or mobile phone number does not exist in each node of the alliance chain When in the white list, the receiving node determines that the second interaction information does not meet the second preset condition.
  • the judgment condition corresponding to the risk control strategy is different from the judgment condition corresponding to the first preset condition. If the first preset condition of a node is that the bank account number cannot be in the first blacklist of any node in the alliance chain and needs to be in the whitelist of at least two nodes in the alliance chain, the risk control strategy can be set to: The bank account number does not need to be in the blacklist of any node in the alliance chain.
  • step S80 if the second interaction information meets the second preset condition, a manual review process is started and it is detected whether an audit result is received.
  • the receiving node If it is determined that the second interaction information meets the second preset condition, the receiving node generates audit prompt information, which sends the audit prompt information to the reviewer.
  • the audit prompt information may be sent to the terminal held by the reviewer to prompt the reviewer to review.
  • This interactive request initiates a manual review process. After reviewers have reviewed the interaction request, they can enter the manual review results in the review interface of the corresponding terminal.
  • the terminal held by the auditor receives the audit result entered by the auditor on the audit interface, it sends the audit result to the receiving node.
  • the receiving node refuses to execute the interaction request.
  • step S90 when the audit result is received and it is determined that the interaction request passes a manual review according to the audit result, the interaction request is executed.
  • the receiving node When the receiving node receives the audit result, it extracts the audit ID in the audit result, and determines whether the interaction request passes the manual audit based on the audit ID. After the receiving node determines that the interaction request passes the manual review, the receiving node executes the interaction request.
  • the audit results include two types, one is "passed the audit” and the other is "not passed the audit”. Specifically, the audit flag of “Passed Audit” may be set to “1”, and the audit flag of “Failed Audit” may be set to “0”. It should be noted that the expression form of the audit mark does not limit the description in this embodiment. For example, the audit mark of "passed the audit” can be set to "a”, and the audit mark of "failed the audit” is set to "b” .
  • the receiving node refuses to execute the interaction request.
  • step S80 includes:
  • Step a if the second interaction information meets the second preset condition, send the second interaction information to other nodes in the alliance chain other than the receiving node for the other nodes Detecting whether the second interaction information exists in a corresponding second blacklist and returning a corresponding detection result, wherein each node in the alliance chain has a corresponding second blacklist.
  • each node in the alliance chain must share a preset proportion of blacklists and whitelists, that is, each node in the alliance chain is allowed to retain part of the blacklist and / or whitelist and not share it with the alliance.
  • the blacklist reserved by each node is referred to as a second blacklist.
  • the preset instance can be set according to specific needs, such as 70%, 80%, or 85%.
  • the receiving node When it is determined that the second interaction information meets the second preset condition, the receiving node sends the second interaction information to other nodes in the alliance chain except the receiving node.
  • the other node detects whether the second interaction information exists in its corresponding second blacklist, obtains the detection result, and sends the detection result to the receiving node.
  • Each node in the alliance chain has a corresponding second blacklist.
  • the detection of whether the second interaction information exists in the corresponding second black list by other nodes is the detection of the existence of the second interaction information in the corresponding second black list, and it is not shared in the black list of the receiving node.
  • step a includes:
  • Step a1 if the second interaction information meets the second preset condition, send the second interaction information to other nodes in the alliance chain except the receiving node for the other nodes After receiving the second interaction information, a category of the second interaction information is determined.
  • the receiving node sends the second interaction information to other nodes in the alliance chain except the receiving node. After other nodes in the alliance chain receive the second interaction information, they determine the type of the second interaction information.
  • the category to which the second interactive information belongs is preset. For example, the ID number and bank card number can be set to the first category, and the mobile phone number and login account can be set to the second category.
  • Step a2 When it is determined that the second interaction information belongs to the first category, the other node detects whether the second interaction information exists in the corresponding second blacklist, and sends the obtained detection result to the second blacklist. Said receiving node.
  • step a3 when it is determined that the second interaction information belongs to the second type, the other nodes obtain the current resource utilization rate.
  • the resource utilization may be CPU (Central Processing Unit (central processing unit) resource utilization.
  • Step a4 when the resource utilization rate is less than a preset threshold, detecting whether the second interaction information exists in the second blacklist, and sending the obtained detection result to the receiving node.
  • the other nodes determine whether their resource utilization is less than a preset threshold. When it is determined that the resource utilization is less than a preset threshold, other nodes detect whether the second interaction information exists in its corresponding second blacklist, obtain a detection result, and send the detection result to the receiving node. When it is determined that the resource utilization is greater than or equal to a preset threshold, other nodes refuse to detect whether the second interaction information exists in its corresponding second blacklist.
  • the preset threshold may be set according to specific needs, and the specific value of the preset threshold is not limited in this embodiment.
  • step a further includes:
  • Step a5 if the second interaction information meets the second preset condition, send the second interaction information to other nodes in the alliance chain except the receiving node, and detect whether all the The waiting time sent by other nodes is described, wherein the waiting time is the time from when the other node receives the second interaction information to when the detection result is obtained.
  • the receiving node After determining that the second interaction information meets the second preset condition, the receiving node sends the second interaction information to other nodes in the alliance chain except the receiving node. After the receiving node sends the second interaction information to other nodes, the receiving node detects whether the waiting period sent by the other nodes is received, where the waiting period is the time from when the other node receives the second interaction information until the detection result is obtained. After other nodes receive the second interaction information, the other nodes determine the length of the detection result based on their current resource utilization, that is, determine the waiting time, and send the waiting time to the receiving node. It should be noted that the mapping relationship between resource utilization and waiting time may be stored in other nodes in advance, and the corresponding waiting time may be determined according to the mapping relationship.
  • Step a6 When the waiting time is received and the waiting time is shorter than a preset time, a detection request is sent to the other node, so that the other node detects the first time after receiving the detection request. Whether two pieces of interaction information exist in the corresponding second blacklist, and return a corresponding detection result.
  • the receiving node After the receiving node receives the waiting time, it is judged whether the waiting time is shorter than a preset time, wherein the preset time can be set according to specific needs, and the specific time corresponding to the preset time is not limited in this embodiment.
  • the receiving node After the receiving node determines that the waiting time is shorter than the preset time, the receiving node sends a detection request to other nodes. After receiving the detection request, other nodes detect whether the second interaction information exists in the corresponding second blacklist according to the detection request, obtain a detection result, and send the detection result to the receiving node. Further, when the receiving node determines that the waiting time is greater than or equal to a preset time, the receiving node sends a prohibition request to other nodes. After other nodes receive the prohibition request, other nodes prohibit the detection of whether the second interaction information exists in the corresponding second blacklist according to the prohibition request.
  • Step b After receiving the detection result, determine the number of blacklists in which the second interaction information is found in the second blacklist according to the detection result.
  • the receiving node determines the number of blacklists in which the second interaction information is found in the second blacklist corresponding to other nodes according to the detection result. It can be understood that the number of blacklists can be determined according to the detection identifier, that is, the number of blacklists can be determined according to the detection result that carries the number of identifiers stored in the second blacklist. If the detection result carries three identifiers stored in the second blacklist, it can be determined that the number of blacklists is three.
  • Step c if the number of blacklists is less than or equal to a preset number, execute the interaction request.
  • the receiving node determines whether the number of blacklists is less than or equal to a preset number. After determining that the number of blacklists is less than or equal to the preset number, the receiving node executes the interaction request.
  • the preset number can be set according to the total number of nodes in the alliance chain. If there are 6 nodes in the alliance chain, the receiving node will execute the interaction request only when the number of blacklists is less than or equal to 2.
  • the receiving node determines that the number of blacklists is greater than a preset number, the receiving node refuses to execute the interaction request.
  • the second interaction information when it is determined that the second interaction information meets the second preset condition, the second interaction information is sent to other nodes in the alliance chain except the receiving node. Or the interaction request is executed only when it is equal to a preset number, which further improves the security of data interaction.
  • the difference between the fifth embodiment of the data interaction method and the first, second, third, or fourth embodiments of the data interaction method is that the data interaction method further includes:
  • step d when the receiving node detects data loss, it determines that the data has been lost.
  • the receiving node detects whether its stored data is lost in real time or at regular intervals.
  • the data stored by the receiving node includes, but is not limited to, blacklist, whitelist, and data related to the interaction request.
  • the receiving node determines that the data has been lost.
  • Step e Obtain the lost data from other nodes in the alliance chain, and store the lost data.
  • the receiving node After the receiving node determines that the data has been lost, the receiving node obtains the lost data from other nodes in the alliance chain and stores the lost data obtained from the other nodes.
  • a node in the alliance chain uses the characteristics of the blockchain to obtain the lost data from other nodes to ensure the integrity of the data of each node in the alliance chain and improves the data interaction process. Data reliability.
  • the present application further provides a data interaction device.
  • the data interaction device includes:
  • An obtaining module 10 is configured to obtain first interaction information corresponding to the interaction request after a receiving node in the alliance chain receives an interaction request for data interaction, where the alliance chain is set in a server;
  • a detection module 20 is configured to detect whether the first interaction information exists in a white list and a first black list of each node of the alliance chain, and obtain a detection result;
  • the execution module 30 is configured to execute the interaction request if the detection result meets a first preset condition.
  • the detection module 20 is further configured to detect whether the registration request meets the registration conditions of the alliance chain after detecting a registration request registered at the receiving node;
  • the execution module 30 is further configured to execute the registration request if the registration request meets the registration conditions;
  • the detection module 20 is further configured to detect whether the interaction request is received after the registration request is successfully performed.
  • the obtaining module 10 is further configured to obtain second interaction information corresponding to the interaction request if the detection result does not meet the first preset condition;
  • the data interaction device further includes:
  • a startup module configured to obtain a risk control strategy corresponding to the receiving node
  • the detection module 20 is further configured to detect whether the second interaction information meets a second preset condition by using the risk control strategy;
  • the starting module is further configured to start a manual review process if the second interaction information meets the second preset condition
  • the detection module 20 is further configured to detect whether an audit result is received
  • the execution module 30 is further configured to execute the interaction request after receiving the review result and determining that the interaction request passes a manual review according to the review result.
  • the data interaction device further includes:
  • a sending module configured to send the second interaction information to other nodes in the alliance chain except the receiving node if the second interaction information meets the second preset condition for the Other nodes detect whether the second interaction information exists in the corresponding second blacklist and return corresponding detection results, wherein each node in the alliance chain has a corresponding second blacklist;
  • a first determining module configured to determine the number of blacklists in which the second interaction information is found in the second blacklist according to the detection results after receiving the detection results;
  • the execution module 30 is further configured to execute the interaction request if the number of the blacklists is less than or equal to a preset number.
  • the sending module is further configured to send the second interaction information to other nodes in the alliance chain except the receiving node if the second interaction information meets the second preset condition
  • the sending module includes:
  • a sending unit configured to send the second interaction information to other nodes in the alliance chain except the receiving node if the second interaction information meets the second preset condition
  • a detecting unit configured to detect whether a waiting period sent by the other node is received, where the waiting period is a period from when the other node receives the second interaction information to when the detection result is obtained;
  • the sending unit is further configured to send a detection request to the other node when the waiting period is received and the waiting period is shorter than a preset period, so that the other node receives the detection request after receiving the detection request. Detecting whether the second interaction information exists in the corresponding second blacklist, and returning a corresponding detection result.
  • the data interaction device further includes:
  • a second determining module configured to determine that data has been lost when the receiving node detects data loss
  • the obtaining module 10 is further configured to obtain the lost data from other nodes in the alliance chain;
  • a storage module configured to store the lost data.
  • each embodiment of the data interaction device is basically the same as each embodiment of the foregoing data interaction method, and details are not described herein again.
  • FIG. 5 is a schematic structural diagram of a hardware operating environment involved in the solution of the embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of a hardware operating environment of a data interaction device.
  • the data interaction device in this embodiment of the present application may be a terminal device such as a PC or a portable computer.
  • the data interaction device may include a processor 1001, such as a CPU, a memory 1005, a user interface 1003, a network interface 1004, and a communication bus 1002.
  • the communication bus 1002 is used to implement connection and communication between these components.
  • the user interface 1003 may include a display, an input unit such as a keyboard, and the optional user interface 1003 may further include a standard wired interface and a wireless interface.
  • the network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface).
  • the memory 1005 may be a high-speed RAM memory or a non-volatile memory. memory), such as disk storage.
  • the memory 1005 may optionally be a storage device independent of the foregoing processor 1001.
  • the data interaction device may further include a camera, RF (Radio Frequency) circuits, sensors, audio circuits, WiFi modules, and more.
  • RF Radio Frequency
  • FIG. 5 does not constitute a limitation on the data interaction device, and may include more or fewer components than shown in the figure, or combine some components or different components Layout.
  • the memory 1005 as a computer storage medium may include an operating system, a network communication module, a user interface module, and computer-readable instructions.
  • the operating system is a program that manages and controls the hardware and software resources of the data interaction device, and supports the operation of computer-readable instructions and other software or programs.
  • the user interface 1003 is mainly used to receive interaction requests and registration requests, etc .
  • the network interface 1004 is mainly used to connect to the background server and perform data communication with the background server, such as to obtain the black storage of the alliance chain node. List, white list, etc .
  • the processor 1001 may be used to call the computer-readable instructions stored in the memory 1005 and execute the steps of the data interaction method as described above.
  • an embodiment of the present application also provides a computer-readable storage medium, where the computer-readable storage medium stores computer-readable instructions, and when the computer-readable instructions are executed by a processor, the data interaction method described above is implemented.
  • the computer-readable storage medium may be a non-volatile readable storage medium.
  • the methods in the above embodiments can be implemented by means of software plus a necessary universal hardware platform, and of course, also by hardware, but in many cases the former is better.
  • Implementation Based on such an understanding, the technical solution of this application that is essentially or contributes to the existing technology can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, The optical disc) includes several instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in the embodiments of the present application.
  • a terminal device which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Telephonic Communication Services (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

La présente invention se rapporte au domaine technique du chiffrement de chaînes de bloc. La présente invention concerne un procédé, un appareil et un dispositif d'interaction de données, et un support d'informations lisible, le procédé comprenant les étapes consistant : une fois qu'un nœud de réception dans une chaîne d'alliance reçoit une demande d'interaction en vue d'une interaction de données, à acquérir des premières informations d'interaction correspondant à la demande d'interaction, la chaîne d'alliance étant disposée dans un serveur ; à détecter si les premières informations d'interaction existent dans une liste blanche et une première liste noire de chaque nœud de la chaîne d'alliance pour obtenir un résultat de détection ; si le résultat de détection satisfait une première condition prédéfinie, à exécuter la demande d'interaction. La présente invention réduit l'interaction de données d'un serveur et réduit la surcharge relative au traitement de données du serveur au moyen des propriétés décentralisées d'une chaîne de blocs, et étant donné que tous les nœuds dans une chaîne d'alliance sont indépendants les uns par rapport aux autres et que seuls des nœuds autorisés peuvent rejoindre la chaîne d'alliance, la fiabilité du serveur est améliorée.
PCT/CN2018/122639 2018-08-31 2018-12-21 Procédé, appareil et dispositif d'interaction de données, et support d'informations lisible WO2020042464A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811008900.5A CN109688186B (zh) 2018-08-31 2018-08-31 数据交互方法、装置、设备及可读存储介质
CN201811008900.5 2018-08-31

Publications (1)

Publication Number Publication Date
WO2020042464A1 true WO2020042464A1 (fr) 2020-03-05

Family

ID=66184479

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/122639 WO2020042464A1 (fr) 2018-08-31 2018-12-21 Procédé, appareil et dispositif d'interaction de données, et support d'informations lisible

Country Status (2)

Country Link
CN (1) CN109688186B (fr)
WO (1) WO2020042464A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111813853A (zh) * 2020-05-29 2020-10-23 平安医疗健康管理股份有限公司 基于区块链系统的数据采集方法、装置和计算机设备
CN112613052A (zh) * 2020-12-24 2021-04-06 北京金山云网络技术有限公司 一种权益管理方法及装置
CN113158212A (zh) * 2021-04-23 2021-07-23 深圳前海华兆新能源有限公司 基于区块链技术的分布式数据库安全认证方法
CN114726561A (zh) * 2020-12-22 2022-07-08 京东科技信息技术有限公司 一种数据处理方法、装置和系统
CN115604035A (zh) * 2022-12-13 2023-01-13 杭州城市大脑有限公司（Cn） 一种基于联盟链的城市大脑数据共享方法

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110245187A (zh) * 2019-05-20 2019-09-17 深圳壹账通智能科技有限公司 一种基于区块链的名单类型查询方法及节点
CN110335031A (zh) * 2019-07-11 2019-10-15 中国银行股份有限公司 一种问题账号信息排查方法及装置
CN112492591B (zh) * 2020-11-06 2022-12-09 广东电网有限责任公司电力调度控制中心 一种电力物联网终端接入网络的方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106878000A (zh) * 2017-03-06 2017-06-20 中钞信用卡产业发展有限公司北京智能卡技术研究院 一种联盟链共识方法及系统
CN107682331A (zh) * 2017-09-28 2018-02-09 复旦大学 基于区块链的物联网身份认证方法
CN108156159A (zh) * 2017-12-27 2018-06-12 质数链网科技成都有限公司 一种多应用系统登陆方法以及区块链分布式总账系统
CN108256988A (zh) * 2016-12-30 2018-07-06 深圳壹账通智能科技有限公司 征信机构联盟的数据处理方法及装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8473611B1 (en) * 2009-09-04 2013-06-25 Blue Coat Systems, Inc. Referrer cache chain
CN107707644A (zh) * 2017-09-27 2018-02-16 北京趣拿软件科技有限公司 请求消息的处理方法、装置、存储介质、处理器及终端

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108256988A (zh) * 2016-12-30 2018-07-06 深圳壹账通智能科技有限公司 征信机构联盟的数据处理方法及装置
CN106878000A (zh) * 2017-03-06 2017-06-20 中钞信用卡产业发展有限公司北京智能卡技术研究院 一种联盟链共识方法及系统
CN107682331A (zh) * 2017-09-28 2018-02-09 复旦大学 基于区块链的物联网身份认证方法
CN108156159A (zh) * 2017-12-27 2018-06-12 质数链网科技成都有限公司 一种多应用系统登陆方法以及区块链分布式总账系统

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111813853A (zh) * 2020-05-29 2020-10-23 平安医疗健康管理股份有限公司 基于区块链系统的数据采集方法、装置和计算机设备
CN111813853B (zh) * 2020-05-29 2022-07-22 深圳平安医疗健康科技服务有限公司 基于区块链系统的数据采集方法、装置和计算机设备
CN114726561A (zh) * 2020-12-22 2022-07-08 京东科技信息技术有限公司 一种数据处理方法、装置和系统
CN114726561B (zh) * 2020-12-22 2024-04-05 京东科技信息技术有限公司 一种数据处理方法、装置和系统
CN112613052A (zh) * 2020-12-24 2021-04-06 北京金山云网络技术有限公司 一种权益管理方法及装置
CN113158212A (zh) * 2021-04-23 2021-07-23 深圳前海华兆新能源有限公司 基于区块链技术的分布式数据库安全认证方法
CN115604035A (zh) * 2022-12-13 2023-01-13 杭州城市大脑有限公司（Cn） 一种基于联盟链的城市大脑数据共享方法
CN115604035B (zh) * 2022-12-13 2023-03-28 杭州城市大脑有限公司 一种基于联盟链的城市大脑数据共享方法

Also Published As

Publication number Publication date
CN109688186B (zh) 2021-01-08
CN109688186A (zh) 2019-04-26

Similar Documents

Publication Publication Date Title
WO2020042464A1 (fr) Procédé, appareil et dispositif d'interaction de données, et support d'informations lisible
WO2021002692A1 (fr) Procédé de fourniture de service d'actifs virtuels sur la base d'un identifiant décentralisé et serveur de fourniture de service d'actifs virtuels les utilisant
WO2020029585A1 (fr) Procédé et dispositif de modélisation de fédération de réseau neuronal faisant intervenir un apprentissage par transfert et support d'informations
WO2018000787A1 (fr) Terminal, et procédé et système pour identifier une pseudo-station de base
WO2020147383A1 (fr) Procédé, dispositif et système d'examen et d'approbation de processus utilisant un système de chaîne de blocs, et support de stockage non volatil
WO2020220413A1 (fr) Procédé et système de preuve à divulgation nulle de connaissance pour informations personnelles, et support de données
WO2019127973A1 (fr) Procédé, système et dispositif d'authentification d'autorité pour référentiel de miroirs et support de stockage
WO2020224250A1 (fr) Procédé, appareil et dispositif pour déclenchement de contrat intelligent, et support de stockage
WO2020189926A1 (fr) Procédé et serveur permettant de gérer une identité d'utilisateur en utilisant un réseau à chaîne de blocs, et procédé et terminal d'authentification d'utilisateur utilisant l'identité d'utilisateur basée sur un réseau à chaîne de blocs
WO2021006616A1 (fr) Procédé pour fournir un service d'identifiant décentralisé relationnel et nœud de chaîne de blocs l'utilisant
WO2021003975A1 (fr) Procédé de test d'interface de passerelle, dispositif terminal, support de stockage et appareil
WO2020189927A1 (fr) Procédé et serveur de gestion de l'identité d'un utilisateur à l'aide d'un réseau de chaîne de blocs, et procédé et terminal d'authentification d'utilisateur à l'aide d'une identité d'utilisateur sur la base d'un réseau de chaîne de blocs
WO2013189134A1 (fr) Procédé et système pour un « pousser » d'informations
WO2020253120A1 (fr) Procédé, système et dispositif d'enregistrement de page web, et support de stockage informatique
WO2021072881A1 (fr) Procédé, appareil et dispositif de traitement de demande fondée sur un stockage d'objet, et support de stockage
WO2020147385A1 (fr) Procédé et appareil d'entrée de données, terminal et support d'informations lisible par ordinateur
WO2020147384A1 (fr) Procédé, dispositif et appareil de transaction sécurisée à base de chaîne de blocs, et support de stockage
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
WO2015101332A1 (fr) Procédé et système de gestion de classification de mots de passe
WO2020107591A1 (fr) Procédé, appareil, dispositif de limitation de double assurance et support d'informations lisible
WO2020042471A1 (fr) Procédé, système, et dispositif de vérification de politique de pare-feu, et support de stockage lisible par machine
WO2020220412A1 (fr) Procédé et système de protection de la confidentialité de citoyen à base de preuve à divulgation nulle de connaissance, et support de stockage
WO2012060479A1 (fr) Système pour fournir un service d'authentification et de gestion de données de position et procédé pour son fonctionnement
WO2020233060A1 (fr) Procédé et appareil de notification d'événement, serveur de notification d'événement et support de stockage
WO2020206899A1 (fr) Procédé, appareil et dispositif de vérification d'identité basée sur un horodatage, et support d'informations

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 09.06.2021)

122 Ep: pct application non-entry in european phase

Ref document number: 18931413

Country of ref document: EP

Kind code of ref document: A1