WO2020042464A1 - 数据交互方法、装置、设备及可读存储介质 - Google Patents

数据交互方法、装置、设备及可读存储介质 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
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/CN2018/122639
Other languages
English (en)
French (fr)
Inventor
郭镭波
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.)
OneConnect Smart Technology Co Ltd
Original Assignee
OneConnect Smart 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 OneConnect Smart Technology Co Ltd filed Critical OneConnect Smart Technology Co Ltd
Publication of WO2020042464A1 publication Critical patent/WO2020042464A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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

本申请涉及区块链加密技术领域。本申请公开了一种数据交互方法、装置、设备及可读存储介质，该方法包括步骤：当联盟链中的接收节点接收到数据交互的交互请求后，获取所述交互请求对应的第一交互信息，其中，所述联盟链设置在服务器中；检测所述第一交互信息是否存在联盟链各个节点的白名单和第一黑名单中，得到检测结果；若所述检测结果符合第一预设条件，则执行所述交互请求。本申请通过区块链的去中心化特性减少服务器的数据交互，降低了服务器的数据处理压力，且由于联盟链中的各个节点是相互独立且只有授权后的节点才能加入联盟链中的，提高了服务器的可靠性。

Description

数据交互方法、装置、设备及可读存储介质
本申请要求于2018年08月31日提交中国专利局、申请号为201811008900.5、发明名称为“数据交互方法、装置、设备及可读存储介质”的中国专利申请的优先权，其全部内容通过引用结合在申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种数据交互方法、装置、设备及可读存储介质。
背景技术
目前的数据交互都是基于中心化的服务器进行数据交互，即第一终端需要与第二终端进行数据交互，需要先将数据发送给服务器，由服务器转发给第二客户端，当客户端接收到该数据后，再将响应结果发送给服务器，由服务器将响应结果发送给第一终端，以实现第一终端和第二终端的数据交互。由此可知，频繁的数据交互将会给服务器造成巨大的压力，且基于中心服务器的架构，只有中心服务器是可靠且被信任的，其它节点都不被信任，导致服务器的可靠性低下。
发明内容
本申请的主要目的在于提供一种数据交互方法、装置、设备及可读存储介质，旨在解决现有的在数据交互过程中，服务器数据处理压力大，可靠性低下的技术问题。
为实现上述目的，本申请提供一种数据交互方法，所述数据交互方法包括步骤：
当联盟链中的接收节点接收到数据交互的交互请求后，获取所述交互请求对应的第一交互信息，其中，所述联盟链设置在服务器中；
检测所述第一交互信息是否存在联盟链各个节点的白名单和第一黑名单中，得到检测结果；
若所述检测结果符合第一预设条件，则执行所述交互请求。
此外，为实现上述目的，本申请还提供一种数据交互装置，所述数据交互装置包括：
获取模块，用于当联盟链中的接收节点接收到数据交互的交互请求后，获取所述交互请求对应的第一交互信息，其中，所述联盟链设置在服务器中；
检测模块，用于检测所述第一交互信息是否存在联盟链各个节点的白名单和第一黑名单中，得到检测结果；
执行模块，用于若所述检测结果符合第一预设条件，则执行所述交互请求。
此外，为实现上述目的，本申请还提供一种数据交互设备，所述数据交互设备包括存储器、处理器和存储在所述存储器上并可在所述处理器上运行的计算机可读指令，所述计算机可读指令被所述处理器执行时实现如上所述的数据交互方法的步骤。
此外，为实现上述目的，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机可读指令，所述计算机可读指令被处理器执行时实现如上所述的数据交互方法的步骤。
本申请通过当服务器联盟链中的某个节点接收到数据交互的交互请求后，检测该交互请求对应的第一交互信息是否存在联盟链各个节点的白名单和第一黑名单中，得到检测结果，若该检测结果符合第一预设条件，则执行该交互请求，以将该交互请求发送给另一终端，以通过区块链的去中心化特性减少服务器的数据交互，降低了服务器的数据处理压力，且由于联盟链中的各个节点是相互独立且只有授权后的节点才能加入联盟链中的，提高了服务器的可靠性；进一步地，由于联盟链中的各个节点共享白名单和黑名单，提高了数据交互的安全性。
附图说明
图1是本申请数据交互方法第一实施例的流程示意图；
图2是本申请数据交互方法第二实施例的流程示意图；
图3是本申请数据交互方法第三实施例的流程示意图；
图4为本申请数据交互装置较佳实施例的功能示意图模块图；
图5是本申请实施例方案涉及的硬件运行环境的结构示意图。
本申请目的的实现、功能特点及优点将结合实施例，参照附图做进一步说明。
具体实施方式
应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
本申请提供一种数据交互方法，参照图1，图1为本申请数据交互方法第一实施例的流程示意图。
本申请实施例提供了数据交互方法的实施例，需要说明的是，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
在数据交互方法的各个实施例中，为了便于描述，以联盟链中的某个节点执行主体进行阐述各个实施例。
以下对本申请中所用的专业名词进行解释：
区块链是由一系列区块组成的一条链，每个块上除了记录本块的数据还会记录上一块的Hash（哈希）值，通过这种方式组成一条链。区块链的核心理念有两个，一个是密码学技术，另一个是去中心化思想，基于这两个理念做到区块链上的历史信息无法被篡改。一个区块由块头和块体组成，其中块头定义包括该区块高度，上一个区块的哈希值等重要字段，而块体主要存储交易数据。
区块链从访问权限的开放程度（也称“去中心化程度”）出发，可以分为三类：公有链、私有链和联盟链。
联盟链的各个节点通常有与之对应的实体机构组织，通过授权后才能加入与退出网络。联盟链本质上也属于私有链，但链上的节点是受多机构控制，私有化的程度较私有链的低。同时两者之间的权限控制会有不同，联盟链的读写权限面向链上的全部或部分节点，权限控制设计更为复杂。
节点特指参与到区块链网络里，进行交易和数据交换的网络节点，每个独立机构成员可以拥有一个到多个交易节点，每个交易节点是一组物理网络，计算机，区块链应用软件以及数据库的组合。节点和节点之间，通过TCP/IP（Transmission Control Protocol/Internet Protocol，传输控制协议/因特网互联协议）协议互相连接。
数据交互方法包括：
步骤S10，当联盟链中的接收节点接收到数据交互的交互请求后，获取所述交互请求对应的第一交互信息，其中，所述联盟链设置在服务器中。
在本实施例中，联盟链设置在服务器中，将联盟链中接收用户通过其终端发送的交互请求的节点称为接收节点。当接收节点接收到数据交互的交互请求后，接收节点获取交互请求对应的第一交互信息。其中，该交互请求可由对应用户根据需要而触发，第一交互信息包括但不限于登录账号、身份证号码和手机号码等。登录账号为该用户在联盟链中注册后用于登录的账号。在本实施例中，若用户需要与联盟链中的节点进行数据交互，就必须在联盟链中注册，拥有其对应的登录账号。需要说明的是，在交互请求中，携带有第一交互信息，因此，当接收节点接收到交互请求后，可在交互请求中提取第一交互信息，以获取到第一交互信息。
步骤S20，检测所述第一交互信息是否存在联盟链各个节点的白名单和第一黑名单中，得到检测结果。
在联盟链中，每个节点都拥有自己的黑名单和白名单，加入联盟链中的节点会共享各自的黑名单和白名单。当接收节点获取到联盟链中其它节点共享的黑名单和白名单时，会存储其它节点的黑名单和白名单。在本实施例中，将接收节点对应的黑名单、联盟链中其它节点共享的黑名单称为第一黑名单。其中，联盟链中的每个节点都存在对应的节点标识，在黑名单和白名单中，携带有对应节点的节点标识，因此，通过节点标识即可区分各个节点对应的黑名单和白名单。
当接收节点获取到交互请求对应的第一交互信息后，接收节点检测第一交互信息是否存在联盟链各个节点的白名单和第一黑名单中，得到检测结果。需要说明的是，由于一个节点对应的一个黑名单和一个白名单，所得的检测结果存在三种情况，分别为：存在第一黑名单中；存在白名单中；或者即不存在第一黑名单中，也不存在白名单中。不同的检测结果对应不同的结果标识，在本实施例中不限制结果标识的表现形式，如可将存在第一黑名单中的结果标识设置为“00”，将存在白名单中的结果标识设置为“11”，将既不存在第一黑名单中，也不存在白名单中的结果标识设置为“01”。
需要说明的是，不同节点对应的检测结果中还携带有节点标识，以区分不同节点的检测结果。如若某个节点的节点标识为“a”，对应的检测结果为存在第一黑名单中，对应的检测标识为“a00”。由此可知，检测标识是由结果标识和节点标识组成的，因此，通过检测标识即可确定第一交互信息对应的检测结果。在本实施例中不限制结果标识和节点标识的组成方式。
步骤S30，若所述检测结果符合第一预设条件，则执行所述交互请求。
当接收节点得到检测结果后，接收节点获取检测结果对应的检测标识，通过检测标识判断检测结果是否符合第一预设条件。若确定检测结果符合第一预设条件，接收节点则执行该交互请求，将该交互请求发送给另一终端。需要说明的是，不同业务场景对应的第一预设条件可能不一样，如在银行业务场景中，第一预设条件可设置为银行账号不能存在联盟链任何一个节点的第一黑名单中，且需要存在联盟链至少两个节点的白名单中；在贷款业务场景中，预设条件可以设置为手机号码和/或身份证号码不能存在联盟链任何一个节点的第一黑名单中，且需要存在联盟链其中一个节点的白名单中。
进一步地，若接收节点确定检测结果不符合第一预设条件，接收节点则拒绝执行该交互请求，并生成提示信息，将该提示信息发送给该交互请求对应终端。当终端接收到该提示信息后，输出该提示信息，以根据该提示信息提示用户交互请求被拒绝执行，或者根据该提示信息提示用户交互请求执行失败，以便于用户及时了解交互请求的执行结果。在本实施例中，不限制终端输出该提示信息的输出方式，如可通过语音或者文字等方式输出该提示信息。
本实施例通过当联盟链中的某个节点接收到数据交互的交互请求后，检测该交互请求对应的第一交互信息是否存在联盟链各个节点的白名单和第一黑名单中，得到检测结果，若该检测结果符合第一预设条件，则执行该交互请求，以将该交互请求发送给另一终端，以通过区块链的去中心化特性减少服务器的数据交互，降低了服务器的数据处理压力，且由于联盟链中的各个节点是相互独立且只有授权后的节点才能加入联盟链中的，提高了服务器的可靠性；进一步地，由于联盟链中的各个节点共享白名单和黑名单，提高了数据交互的安全性。
进一步地，提出本申请数据交互方法第二实施例。
所述数据交互方法第二实施例与所述数据交互方法第一实施例的区别在于，参照图2，数据交互方法还包括：
步骤S40，当侦测到在所述接收节点注册的注册请求后，检测所述注册请求是否符合所述联盟链的注册条件。
当接收节点侦测到注册请求后，接收节点检测该注册请求是否符合联盟链的注册条件。需要说明的是，在联盟链中，预先设置好了的注册条件，该注册条件可根据具体需要而设置。如若联盟链中存在10个节点，则可将注册条件设置为只有当6个节点都同意执行该注册请求时，才确定该注册请求符合联盟链的注册条件。
步骤S50，若所述注册请求符合所述注册条件，则执行所述注册请求，并在成功执行所述注册请求后检测是否接收到所述交互请求。
若确定该注册请求符合注册条件，接收节点则执行该注册请求，并在成功执行该注册请求后，即用户在联盟链中成功注册后，接收节点检测是否接收到交互请求。需要说明的是，当某个用户在联盟链中的某个节点注册成功后，该用户可在联盟链中的任一节点进行数据交互。
进一步地，若确定该注册请求未符合注册条件，接收节点则发送提示信息给注册请求对应终端。当该终端接收到该提示信息后，输出该提示信息，根据该提示信息提示用户注册失败。
本实施例通过在联盟链节点的注册过程中，需要检测该注册请求是否符合注册条件，只有符合注册条件时，才执行该注册请求，进一步提高了基于联盟链进行数据交互的安全性。
进一步地，提出本申请数据交互方法第三实施例。
所述数据交互方法第三实施例与所述数据交互方法第二实施例的区别在于，参照图3，数据交互方法还包括：
步骤S60，若所述检测结果未符合所述第一预设条件，则获取所述交互请求对应的第二交互信息。
若确定检测结果未符合第一预设条件，接收节点则获取交互请求对应的第二交互信息。其中，第二交互信息是接收节点风控策略对应的信息，第二交互信息可与第一交互信息不同，也可与第一交互信息相同。在联盟链中，各个节点对应的风控策略是预先设置好的。
步骤S70，获取所述接收节点对应的风控策略，通过所述风控策略检测所述第二交互信息是否符合第二预设条件。
接收节点获取其风控策略，通过该风控策略检测第二交互信息是否符合第二预设条件。如某个节点的风控策略为：检测银行卡号码是否存在其黑名单中，且身份证号码是否存在白名单中。若该用户的银行卡号码存在黑名单中，和/或身份证号码不存在白名单中，接收节点则确定第二交互信息不符合第二预设条件；若银行卡号码未存在黑名单中，且身份证号码存在白名单中，接收节点则确定第二交互信息符合第二预设条件。
进一步地，还可根据该数据交互请求类型的不同，设置第二交互信息的优先级。如当该数据交互请求为查询余额的请求时，设置为银行卡账号的优先级高于身份证号码的优先级，身份证号码的优先级高于手机号码的优先级；当该数据交互请求为贷款请求时，设置为电话号码的优先级高于身份证号码优先级，身份证号码的优先级高于登录账号的优先级。此时，在设置风控策略时，可根据第二交互信息的优先级来设置不同类型数据交互请求对应的风控策略。
如可将查询余额对应的交互请求的风控策略设置为：当检测到银行卡账号未存在联盟链各个节点的黑名单中，且身份证号码或者手机号码存在联盟链其中一个节点的白名单中时，接收节点确定第二交互信息符合第二预设条件；当检测到银行卡账号存在联盟链其中一个节点的黑名单中，和/或该身份证号码或者手机号码未存在联盟链各个节点的白名单中时，接收节点确定第二交互信息未符合第二预设条件。
需要说明的是，风控策略对应的判断条件与第一预设条件对应的判断条件是不同的。如若某个节点的第一预设条件为：银行账号不能存在联盟链任何一个节点的第一黑名单中，且需要存在联盟链至少两个节点的白名单中，则风控策略可设置为：银行账号只要不存在联盟链中任何一个节点的黑名单中即可。
步骤S80，若所述第二交互信息符合所述第二预设条件，则启动人工审核流程，并检测是否接收到审核结果。
若确定第二交互信息符合第二预设条件，接收节点则生成审核提示信息，该将审核提示信息发送给审核人员，具体地，可将审核提示信息发送给审核人员所持终端，提示审核人员审核该交互请求，以启动人工审核流程。当审核人员审核完该交互请求后，可在对应终端的审核界面中输入人工审核结果。当审核人员所持终端接收到审核人员在审核界面输入的审核结果后，将该审核结果发送给接收节点。
进一步地，若确定第二交互信息未符合第二预设条件，接收节点则拒绝执行该交互请求。
步骤S90，当接收到所述审核结果，且根据所述审核结果确定所述交互请求通过人工审核后，执行所述交互请求。
当接收节点接收到审核结果后，提取该审核结果中的审核标识，根据该审核标识确定交互请求是否通过人工审核。当接收节点确定交互请求通过人工审核后，接收节点执行该交互请求。其中，审核结果包括两种，一种为“通过审核”，另一种为“未通过审核”。具体地，可将“通过审核”的审核标识设置为“1”，“未通过审核”的审核标识设置为“0”。需要说明的是，审核标识的表现形式并不限制本实施例所描述的，如还可将“通过审核”的审核标识设置为“a”，“未通过审核”的审核标识设置为“b”。
进一步地，若根据该审核结果确定该交互请求未通过人工审核，接收节点则拒绝执行该交互请求。
本实施例通过当确定检测结果未符合第一预设条件时，检测交互请求的第二交互信息是否满足第二预设条件，当满足第二预设条件时，进行人工审核，当交互请求通过人工审核后，执行该交互请求，提高了交互请求的执行成功率，提高了数据交互的成功率。
进一步地，提出本申请数据交互方法第四实施例。
所述数据交互方法第四实施例与所述数据交互方法第一、第二或第三实施例的区别在于，步骤S80包括：
步骤a，若所述第二交互信息符合所述第二预设条件，则将所述第二交互信息发送给所述联盟链中除所述接收节点外的其它节点，以供所述其它节点检测所述第二交互信息是否存在对应的第二黑名单中，并返回对应的检测结果，其中，所述联盟链中的每一节点都存在对应的第二黑名单。
为了保证联盟链中各个节点独特性，联盟链中的各个节点必须共享预设比例的黑名单和白名单，即允许联盟链中的各个节点保留部分黑名单和/或白名单，不共享给联盟链中的其它节点。在本实施例中，将各个节点保留的黑名单称为第二黑名单。其中，预设实例可根据具体需要而设置，如可设置为70%、80%或者85%等。
当确定第二交互信息符合第二预设条件时，接收节点将第二交互信息发送给联盟链中除该接收节点外的其它节点。当联盟链中的其它节点接收到第二交互信息时，该其它节点检测第二交互信息是否存在其对应的第二黑名单中，得到检测结果，并将检测结果发送给接收节点。联盟链中的每一节点都存在对应的第二黑名单。
可以理解的是，其它节点检测第二交互信息是否存在其对应的第二黑名单中是检测第二交互信息是否存在其对应的，未共享给接收节点的黑名单中。
进一步地，为了保证在联盟链中进行数据交互的安全性，以及保证联盟链中各个节点的灵活性和自主性，步骤a包括：
步骤a1，若所述第二交互信息符合所述第二预设条件，则将所述第二交互信息发送给所述联盟链中除所述接收节点外的其它节点，以供所述其它节点在接收到所述第二交互信息后，确定所述第二交互信息的类别。
若确定第二交互信息符合第二预设条件，接收节点则将第二交互信息发送给联盟链中除接收节点外的其它节点。当联盟链中的其它节点接收到该第二交互信息后，确定第二交互信息的类型。第二交互信息所属类别是预先设置好的，如可将身份证号码和银行卡号码设置为第一类，将手机号码和登录账号设置为第二类。
步骤a2，当确定所述第二交互信息属于第一类时，由所述其它节点检测所述第二交互信息是否存在对应的所述第二黑名单中，并将所得的检测结果发送给所述接收节点。
当其它节点确定第二交互信息属于第一类时，联盟链中的其它节点检测第二交互信息是否存在其对应的第二黑名单中，即检测是否在第二黑名单中查找到与第二交互信息相同的信息，得到检测结果，并将检测结果发送给联盟链中的接收节点。
步骤a3，当确定所述第二交互信息属于第二类时，由所述其它节点获取当前的资源利用率。
当其它节点确定第二交互信息属于第二类时，其它节点获取其当前对应的资源利用率。具体地，该资源利用率可为CPU（Central Processing Unit，中央处理器）资源利用率。
步骤a4，当所述资源利用率小于预设阈值时，检测所述第二交互信息是否存在所述第二黑名单中，并将所得的检测结果发送给所述接收节点。
当其它节点获取到其对应的资源利用率时，其它节点判断其资源利用率是否小于预设阈值。当确定资源利用率小于预设阈值时，其它节点检测第二交互信息是否存在其对应的第二黑名单中，得到检测结果，并将该检测结果发送给接收节点。当确定资源利用率大于或者等于预设阈值时，其它节点拒绝检测第二交互信息是否存在其对应的第二黑名单中。其中，预设阈值可根据具体需要而设置，在本实施例中不限制预设阈值的具体数值。
进一步地，为了提高数据交互的效率，步骤a还包括：
步骤a5，若所述第二交互信息符合所述第二预设条件，则将所述第二交互信息发送给所述联盟链中除所述接收节点外的其它节点，并检测是否接收到所述其它节点发送的等待时长，其中，所述等待时长为所述其它节点接收到所述第二交互信息至得到所述检测结果的时长。
当确定第二交互信息符合第二预设条件后，接收节点将第二交互信息发送给联盟链中除接收节点外的其它节点。当接收节点将第二交互信息发送给其它节点后，接收节点检测是否接收到其它节点发送的等待时长，其中，等待时长为其它节点接收到第二交互信息至得到所述检测结果的时长。当其它节点接收到第二交互信息后，其它节点根据其当前的资源利用率确定得到检测结果的时长，即确定等待时长，并将该等待时长发送给接收节点。需要说明的是，可在其它节点中预先存储资源利用率与等待时长之间的映射关系，根据该映射关系即可确定对应的等待时长。
步骤a6，当接收到所述等待时长，且所述等待时长小于预设时长时，发送检测请求给所述其它节点，以供所述其它节点在接收到所述检测请求后，检测所述第二交互信息是否存在对应的所述第二黑名单中，并返回对应的检测结果。
当接收节点接收到等待时长后，判断该等待时长是否小于预设时长，其中，预设时长可根据具体需要而设置，在本实施例中不限制预设时长对应的具体时间。当接收节点确定该等待时长小于预设时长后，接收节点发送检测请求给其它节点。当其它节点接收到该检测请求后，根据该检测请求检测第二交互信息是否存在对应的第二黑名单中，得到检测结果，并将该检测结果发送给接收节点。进一步地，当接收节点确定等待时长大于或者等于预设时长时，接收节点发送禁止请求给其它节点。当其它节点接收到禁止请求后，其它节点根据该禁止请求禁止检测第二交互信息是否存在对应的第二黑名单中。
步骤b，当接收到所述检测结果后，根据所述检测结果确定在所述第二黑名单中查找到所述第二交互信息的黑名单数量。
当接收节点接收到检测结果后，接收节点根据该检测结果确定在其它节点对应的第二黑名单中查找到第二交互信息的黑名单数量。可以理解的是，根据检测标识即可确定黑名单数量，即根据检测结果中携带有存在第二黑名单中的标识个数即可确定黑名单数量。如检测结果携带有存在第二黑名单中的标识个数为3个，即可确定黑名单数量为3个。
步骤c，若所述黑名单数量小于或者等于预设数量，则执行所述交互请求。
当接收节点确定黑名单数量后，接收节点判断黑名单数量是否小于或者等于预设数量。当确定黑名单数量小于或者等于预设数量后，接收节点执行该交互请求。其中，预设数量可根据联盟链中的总节点数量而设置。如联盟链中存在6个节点，只有黑名单数量小于或者等于2时，接收节点才会执行该交互请求。
进一步地，当接收节点确定黑名单数量大于预设数量后，接收节点拒绝执行该交互请求。
本实施例通过当确定第二交互信息符合第二预设条件时，将第二交互信息发送给联盟链中除接收节点外的其它节点，只有当根据其它节点返回的检测结果确定黑名单数量小于或者等于预设数量时，才执行该交互请求，进一步提高了数据交互的安全性。
进一步地，提出本申请数据交互方法第五实施例。
所述数据交互方法第五实施例与所述数据交互方法第一、第二、第三或第四实施例的区别在于，数据交互方法还包括：
步骤d，当所述接收节点检测到数据丢失后，确定已丢失数据。
接收节点实时或者定时检测其所存储的数据是否丢失。其中，接收节点所存储的数据包括但不限于黑名单、白名单和与交互请求有关的数据。当接收节点检测到其所存储的数据丢失后，接收节点确定已丢失数据。
步骤e，从所述联盟链中的其它节点中获取所述已丢失数据，并存储所述已丢失数据。
当接收节点确定已丢失数据后，接收节点从联盟链中的其它节点中获取已丢失数据，并存储从其它节点所获取的已丢失数据。
本实施例通过联盟链中的某个节点丢失数据后，通过区块链的特性从其它节点中获取所丢失的数据，以保证联盟链中各个节点数据的完整性，提高了数据交互过程中，数据的可靠性。
此外，参照图4，本申请还提供一种数据交互装置，所述数据交互装置包括：
获取模块10，用于当联盟链中的接收节点接收到数据交互的交互请求后，获取所述交互请求对应的第一交互信息，其中，所述联盟链设置在服务器中；
检测模块20，用于检测所述第一交互信息是否存在联盟链各个节点的白名单和第一黑名单中，得到检测结果；
执行模块30，用于若所述检测结果符合第一预设条件，则执行所述交互请求。
进一步地，所述检测模块20还用于当侦测到在所述接收节点注册的注册请求后，检测所述注册请求是否符合所述联盟链的注册条件；
所述执行模块30还用于若所述注册请求符合所述注册条件，则执行所述注册请求；
所述检测模块20还用于在成功执行所述注册请求后检测是否接收到所述交互请求。
进一步地，所述获取模块10还用于若所述检测结果未符合所述第一预设条件，则获取所述交互请求对应的第二交互信息；
所述数据交互装置还包括：
启动模块，用于获取所述接收节点对应的风控策略；
所述检测模块20还用于通过所述风控策略检测所述第二交互信息是否符合第二预设条件；
所述启动模块还用于若所述第二交互信息符合所述第二预设条件，则启动人工审核流程；
所述检测模块20还用于检测是否接收到审核结果；
所述执行模块30还用于当接收到所述审核结果，且根据所述审核结果确定所述交互请求通过人工审核后，执行所述交互请求。
进一步地，所述数据交互装置还包括：
发送模块，用于若所述第二交互信息符合所述第二预设条件，则将所述第二交互信息发送给所述联盟链中除所述接收节点外的其它节点，以供所述其它节点检测所述第二交互信息是否存在对应的第二黑名单中，并返回对应的检测结果，其中，所述联盟链中的每一节点都存在对应的第二黑名单；
第一确定模块，用于当接收到所述检测结果后，根据所述检测结果确定在所述第二黑名单中查找到所述第二交互信息的黑名单数量；
所述执行模块30还用于若所述黑名单数量小于或者等于预设数量，则执行所述交互请求。
进一步地，所述发送模块还用于若所述第二交互信息符合所述第二预设条件，则将所述第二交互信息发送给所述联盟链中除所述接收节点外的其它节点，以供所述其它节点在接收到所述第二交互信息后，确定所述第二交互信息的类别；其中，当确定所述第二交互信息属于第一类时，由所述其它节点检测所述第二交互信息是否存在对应的所述第二黑名单中，并将所得的检测结果发送给所述接收节点；当确定所述第二交互信息属于第二类时，由所述其它节点获取当前的资源利用率；当所述资源利用率小于预设阈值时，检测所述第二交互信息是否存在所述第二黑名单中，并将所得的检测结果发送给所述接收节点。
进一步地，所述发送模块包括：
发送单元，用于若所述第二交互信息符合所述第二预设条件，则将所述第二交互信息发送给所述联盟链中除所述接收节点外的其它节点；
检测单元，用于检测是否接收到所述其它节点发送的等待时长，其中，所述等待时长为所述其它节点接收到所述第二交互信息至得到所述检测结果的时长；
所述发送单元还用于当接收到所述等待时长，且所述等待时长小于预设时长时，发送检测请求给所述其它节点，以供所述其它节点在接收到所述检测请求后，检测所述第二交互信息是否存在对应的所述第二黑名单中，并返回对应的检测结果。
进一步地，所述数据交互装置还包括：
第二确定模块，用于当所述接收节点检测到数据丢失后，确定已丢失数据；
所述获取模块10还用于从所述联盟链中的其它节点中获取所述已丢失数据；
存储模块，用于存储所述已丢失数据。
需要说明的是，数据交互装置的各个实施例与上述数据交互方法的各实施例基本相同，在此不再详细赘述。
此外，本申请还提供一种数据交互设备。如图5所示，图5是本申请实施例方案涉及的硬件运行环境的结构示意图。
需要说明的是，图5即可为数据交互设备的硬件运行环境的结构示意图。本申请实施例数据交互设备可以是PC，便携计算机等终端设备。
如图5所示，该数据交互设备可以包括：处理器1001，例如CPU，存储器1005，用户接口1003，网络接口1004，通信总线1002。其中，通信总线1002用于实现这些组件之间的连接通信。用户接口1003可以包括显示屏（Display）、输入单元比如键盘（Keyboard），可选用户接口1003还可以包括标准的有线接口、无线接口。网络接口1004可选的可以包括标准的有线接口、无线接口（如WI-FI接口）。存储器1005可以是高速RAM存储器，也可以是稳定的存储器（non-volatile memory），例如磁盘存储器。存储器1005可选的还可以是独立于前述处理器1001的存储装置。
可选地，数据交互设备还可以包括摄像头、RF（Radio Frequency，射频）电路，传感器、音频电路、WiFi模块等等。
本领域技术人员可以理解，图5中示出的数据交互设备结构并不构成对数据交互设备的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
如图5所示，作为一种计算机存储介质的存储器1005中可以包括操作系统、网络通信模块、用户接口模块以及计算机可读指令。其中，操作系统是管理和控制数据交互设备硬件和软件资源的程序，支持计算机可读指令以及其它软件或程序的运行。
在图5所示的数据交互设备中，用户接口1003主要用于接收交互请求和注册请求等；网络接口1004主要用于连接后台服务器，与后台服务器进行数据通信，如获取联盟链节点存储的黑名单和白名单等；处理器1001可以用于调用存储器1005中存储的计算机可读指令，并执行如上所述的数据交互方法的步骤。
本申请数据交互设备具体实施方式与上述数据交互方法各实施例基本相同，在此不再赘述。
此外，本申请实施例还提出一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机可读指令，所述计算机可读指令被处理器执行时实现如上所述的数据交互方法的步骤。计算机可读存储介质可以为非易失性可读存储介质。
本申请计算机可读存储介质具体实施方式与上述数据交互方法各实施例基本相同，在此不再赘述。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
上述本申请实施例序号仅仅为了描述，不代表实施例的优劣。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质（如ROM/RAM、磁碟、光盘）中，包括若干指令用以使得一台终端设备（可以是手机，计算机，服务器，空调器，或者网络设备等）执行本申请各个实施例所述的方法。
以上仅为本申请的优选实施例，并非因此限制本申请的专利范围，凡是利用本申请说明书及附图内容所作的等效结构或等效流程变换，或直接或间接运用在其他相关的技术领域，均同理包括在本申请的专利保护范围内。

Claims (20)

  1. 一种数据交互方法，其特征在于，所述数据交互方法包括以下步骤：
    当联盟链中的接收节点接收到数据交互的交互请求后，获取所述交互请求对应的第一交互信息，其中，所述联盟链设置在服务器中；
    检测所述第一交互信息是否存在联盟链各个节点的白名单和第一黑名单中，得到检测结果；
    若所述检测结果符合第一预设条件，则执行所述交互请求。
  2. 如权利要求1所述的数据交互方法，其特征在于，所述当联盟链中的接收节点接收到数据交互的交互请求后，获取所述交互请求对应的第一交互信息的步骤之前，还包括：
    当侦测到在所述接收节点注册的注册请求后，检测所述注册请求是否符合所述联盟链的注册条件；
    若所述注册请求符合所述注册条件，则执行所述注册请求，并在成功执行所述注册请求后检测是否接收到所述交互请求。
  3. 如权利要求1所述的数据交互方法，其特征在于，所述检测所述第一交互信息是否存在联盟链各个节点的白名单和第一黑名单中，得到检测结果的步骤之后，还包括：
    若所述检测结果未符合所述第一预设条件，则获取所述交互请求对应的第二交互信息；
    获取所述接收节点对应的风控策略，通过所述风控策略检测所述第二交互信息是否符合第二预设条件；
    若所述第二交互信息符合所述第二预设条件，则启动人工审核流程，并检测是否接收到审核结果；
    当接收到所述审核结果，且根据所述审核结果确定所述交互请求通过人工审核后，执行所述交互请求。
  4. 如权利要求3所述的数据交互方法，其特征在于，所述获取所述接收节点对应的风控策略，通过所述风控策略检测所述第二交互信息是否符合第二预设条件的步骤之后，还包括：
    若所述第二交互信息符合所述第二预设条件，则将所述第二交互信息发送给所述联盟链中除所述接收节点外的其它节点，以供所述其它节点检测所述第二交互信息是否存在对应的第二黑名单中，并返回对应的检测结果，其中，所述联盟链中的每一节点都存在对应的第二黑名单；
    当接收到所述检测结果后，根据所述检测结果确定在所述第二黑名单中查找到所述第二交互信息的黑名单数量；
    若所述黑名单数量小于或者等于预设数量，则执行所述交互请求。
  5. 如权利要求4所述的数据交互方法，其特征在于，所述若所述第二交互信息符合所述第二预设条件，则将所述第二交互信息发送给所述联盟链中除所述接收节点外的其它节点，以供所述其它节点检测所述第二交互信息是否存在对应的第二黑名单中，并返回对应的检测结果的步骤包括：
    若所述第二交互信息符合所述第二预设条件，则将所述第二交互信息发送给所述联盟链中除所述接收节点外的其它节点，以供所述其它节点在接收到所述第二交互信息后，确定所述第二交互信息的类别；
    当确定所述第二交互信息属于第一类时，由所述其它节点检测所述第二交互信息是否存在对应的所述第二黑名单中，并将所得的检测结果发送给所述接收节点；
    当确定所述第二交互信息属于第二类时，由所述其它节点获取当前的资源利用率；
    当所述资源利用率小于预设阈值时，检测所述第二交互信息是否存在所述第二黑名单中，并将所得的检测结果发送给所述接收节点。
  6. 如权利要求4所述的数据交互方法，其特征在于，所述若所述第二交互信息符合所述第二预设条件，则将所述第二交互信息发送给所述联盟链中除所述接收节点外的其它节点，以供所述其它节点检测所述第二交互信息是否存在对应的第二黑名单中，并返回对应的检测结果的步骤包括：
    若所述第二交互信息符合所述第二预设条件，则将所述第二交互信息发送给所述联盟链中除所述接收节点外的其它节点，并检测是否接收到所述其它节点发送的等待时长，其中，所述等待时长为所述其它节点接收到所述第二交互信息至得到所述检测结果的时长；
    当接收到所述等待时长，且所述等待时长小于预设时长时，发送检测请求给所述其它节点，以供所述其它节点在接收到所述检测请求后，检测所述第二交互信息是否存在对应的所述第二黑名单中，并返回对应的检测结果。
  7. 如权利要求1所述的数据交互方法，其特征在于，所述数据交互方法还包括：
    当所述接收节点检测到数据丢失后，确定已丢失数据；
    从所述联盟链中的其它节点中获取所述已丢失数据，并存储所述已丢失数据。
  8. 一种数据交互装置，其特征在于，所述数据交互装置包括：
    获取模块，用于当联盟链中的接收节点接收到数据交互的交互请求后，获取所述交互请求对应的第一交互信息，其中，所述联盟链设置在服务器中；
    检测模块，用于检测所述第一交互信息是否存在联盟链各个节点的白名单和第一黑名单中，得到检测结果；
    执行模块，用于若所述检测结果符合第一预设条件，则执行所述交互请求。
  9. 如权利要求8所述的数据交互装置，其特征在于，所述检测模块还用于当侦测到在所述接收节点注册的注册请求后，检测所述注册请求是否符合所述联盟链的注册条件；
    所述执行模块还用于若所述注册请求符合所述注册条件，则执行所述注册请求；
    所述检测模块还用于在成功执行所述注册请求后检测是否接收到所述交互请求。
  10. 如权利要求8所述的数据交互装置，其特征在于，所述获取模块还用于若所述检测结果未符合所述第一预设条件，则获取所述交互请求对应的第二交互信息；
    所述数据交互装置还包括：
    启动模块，用于获取所述接收节点对应的风控策略；
    所述检测模块还用于通过所述风控策略检测所述第二交互信息是否符合第二预设条件；
    所述启动模块还用于若所述第二交互信息符合所述第二预设条件，则启动人工审核流程；
    所述检测模块还用于检测是否接收到审核结果；
    所述执行模块还用于当接收到所述审核结果，且根据所述审核结果确定所述交互请求通过人工审核后，执行所述交互请求。
  11. 如权利要求10所述的数据交互装置，其特征在于，所述数据交互装置还包括：
    发送模块，用于若所述第二交互信息符合所述第二预设条件，则将所述第二交互信息发送给所述联盟链中除所述接收节点外的其它节点，以供所述其它节点检测所述第二交互信息是否存在对应的第二黑名单中，并返回对应的检测结果，其中，所述联盟链中的每一节点都存在对应的第二黑名单；
    第一确定模块，用于当接收到所述检测结果后，根据所述检测结果确定在所述第二黑名单中查找到所述第二交互信息的黑名单数量；
    所述执行模块还用于若所述黑名单数量小于或者等于预设数量，则执行所述交互请求。
  12. 如权利要求11所述的数据交互装置，其特征在于，所述发送模块还用于若所述第二交互信息符合所述第二预设条件，则将所述第二交互信息发送给所述联盟链中除所述接收节点外的其它节点，以供所述其它节点在接收到所述第二交互信息后，确定所述第二交互信息的类别；其中，当确定所述第二交互信息属于第一类时，由所述其它节点检测所述第二交互信息是否存在对应的所述第二黑名单中，并将所得的检测结果发送给所述接收节点；当确定所述第二交互信息属于第二类时，由所述其它节点获取当前的资源利用率；当所述资源利用率小于预设阈值时，检测所述第二交互信息是否存在所述第二黑名单中，并将所得的检测结果发送给所述接收节点。
  13. 如权利要求11所述的数据交互装置，其特征在于，
    所述发送模块包括：
    发送单元，用于若所述第二交互信息符合所述第二预设条件，则将所述第二交互信息发送给所述联盟链中除所述接收节点外的其它节点；
    检测单元，用于检测是否接收到所述其它节点发送的等待时长，其中，所述等待时长为所述其它节点接收到所述第二交互信息至得到所述检测结果的时长；
    所述发送单元还用于当接收到所述等待时长，且所述等待时长小于预设时长时，发送检测请求给所述其它节点，以供所述其它节点在接收到所述检测请求后，检测所述第二交互信息是否存在对应的所述第二黑名单中，并返回对应的检测结果。
  14. 如权利要求8所述的数据交互装置，其特征在于，所述数据交互装置还包括：
    第二确定模块，用于当所述接收节点检测到数据丢失后，确定已丢失数据；
    所述获取模块还用于从所述联盟链中的其它节点中获取所述已丢失数据；
    存储模块，用于存储所述已丢失数据。
  15. 一种数据交互设备，其特征在于，所述数据交互设备包括存储器、处理器和存储在所述存储器上并可在所述处理器上运行的计算机可读指令，所述计算机可读指令被所述处理器执行时实现如下步骤：
    当联盟链中的接收节点接收到数据交互的交互请求后，获取所述交互请求对应的第一交互信息，其中，所述联盟链设置在服务器中；
    检测所述第一交互信息是否存在联盟链各个节点的白名单和第一黑名单中，得到检测结果；
    若所述检测结果符合第一预设条件，则执行所述交互请求。
  16. 如权利要求15所述的数据交互设备，其特征在于，所述当联盟链中的接收节点接收到数据交互的交互请求后，获取所述交互请求对应的第一交互信息的步骤之前，
    所述计算机可读指令被所述处理器执行时实现如下步骤：
    当侦测到在所述接收节点注册的注册请求后，检测所述注册请求是否符合所述联盟链的注册条件；
    若所述注册请求符合所述注册条件，则执行所述注册请求，并在成功执行所述注册请求后检测是否接收到所述交互请求。
  17. 如权利要求15所述的数据交互设备，其特征在于，所述检测所述第一交互信息是否存在联盟链各个节点的白名单和第一黑名单中，得到检测结果的步骤之后，
    所述计算机可读指令被所述处理器执行时实现如下步骤：
    若所述检测结果未符合所述第一预设条件，则获取所述交互请求对应的第二交互信息；
    获取所述接收节点对应的风控策略，通过所述风控策略检测所述第二交互信息是否符合第二预设条件；
    若所述第二交互信息符合所述第二预设条件，则启动人工审核流程，并检测是否接收到审核结果；
    当接收到所述审核结果，且根据所述审核结果确定所述交互请求通过人工审核后，执行所述交互请求。
  18. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有计算机可读指令，所述计算机可读指令被处理器执行时实现如下步骤：
    当联盟链中的接收节点接收到数据交互的交互请求后，获取所述交互请求对应的第一交互信息，其中，所述联盟链设置在服务器中；
    检测所述第一交互信息是否存在联盟链各个节点的白名单和第一黑名单中，得到检测结果；
    若所述检测结果符合第一预设条件，则执行所述交互请求。
  19. 如权利要求18所述的计算机可读存储介质，其特征在于，所述当联盟链中的接收节点接收到数据交互的交互请求后，获取所述交互请求对应的第一交互信息的步骤之前，
    所述计算机可读指令被所述处理器执行时实现如下步骤：
    当侦测到在所述接收节点注册的注册请求后，检测所述注册请求是否符合所述联盟链的注册条件；
    若所述注册请求符合所述注册条件，则执行所述注册请求，并在成功执行所述注册请求后检测是否接收到所述交互请求。
  20. 如权利要求18所述的计算机可读存储介质，其特征在于，所述检测所述第一交互信息是否存在联盟链各个节点的白名单和第一黑名单中，得到检测结果的步骤之后，
    所述计算机可读指令被所述处理器执行时实现如下步骤：
    若所述检测结果未符合所述第一预设条件，则获取所述交互请求对应的第二交互信息；
    获取所述接收节点对应的风控策略，通过所述风控策略检测所述第二交互信息是否符合第二预设条件；
    若所述第二交互信息符合所述第二预设条件，则启动人工审核流程，并检测是否接收到审核结果；
    当接收到所述审核结果，且根据所述审核结果确定所述交互请求通过人工审核后，执行所述交互请求。
PCT/CN2018/122639 2018-08-31 2018-12-21 数据交互方法、装置、设备及可读存储介质 Ceased WO2020042464A1 (zh)

Applications Claiming Priority (2)

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

Publications (1)

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

Family

ID=66184479

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/122639 Ceased WO2020042464A1 (zh) 2018-08-31 2018-12-21 数据交互方法、装置、设备及可读存储介质

Country Status (2)

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

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 (4)

* 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 广东电网有限责任公司电力调度控制中心 一种电力物联网终端接入网络的方法及装置
CN112883411B (zh) * 2020-12-29 2025-01-14 杭州趣链科技有限公司 基于区块链的数据处理方法、系统、电子设备及存储介质

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 (zh) 数据交互方法、装置、设备及可读存储介质
WO2021002692A1 (en) Method for providing virtual asset service based on decentralized identifier and virtual asset service providing server using them
WO2021006616A1 (en) Method for providing relational decentralized identifier service and blockchain node using the same
WO2020147383A1 (zh) 基于区块链系统的流程审批方法、装置、系统及非易失性存储介质
WO2020220413A1 (zh) 个人信息的零知识证明方法、系统及存储介质
WO2020147385A1 (zh) 数据录入方法、装置、终端及计算机可读存储介质
WO2020189926A1 (ko) 블록체인 네트워크를 이용하여 사용자의 아이덴티티를 관리하는 방법 및 서버, 그리고, 블록체인 네트워크 기반의 사용자 아이덴티티를 이용하여 사용자를 인증하는 방법 및 단말
WO2021072881A1 (zh) 基于对象存储的请求处理方法、装置、设备及存储介质
WO2019127973A1 (zh) 镜像仓库的权限认证方法、系统、设备及存储介质
WO2020224246A1 (zh) 基于区块链的数据管理方法、装置、设备和存储介质
WO2018192472A1 (zh) 访问认证的方法及服务器、智能终端和存储装置
WO2018000787A1 (zh) 一种终端、伪基站识别方法及系统
WO2020087981A1 (zh) 风控审核模型生成方法、装置、设备及可读存储介质
WO2018233352A1 (zh) 数据传输方法、装置、终端以及计算机可读存储介质
WO2020042471A1 (zh) 防火墙策略验证方法、系统、设备及可读存储介质
WO2013189134A1 (zh) 信息推送方法及系统
WO2020130331A1 (ko) 블록체인에서 노드들간 블록 및 전자 문서를 공유 및 검증하는 방법
WO2020206899A1 (zh) 基于时间戳的身份验证方法、装置、设备及存储介质
WO2020189927A1 (ko) 블록체인 네트워크를 이용하여 사용자의 아이덴티티를 관리하는 방법 및 서버, 그리고, 블록체인 네트워크 기반의 사용자 아이덴티티를 이용하여 사용자를 인증하는 방법 및 단말
WO2020253120A1 (zh) 网页注册方法、系统、设备和计算机存储介质
WO2015101332A1 (zh) 密码分级管理方法和系统
WO2020147384A1 (zh) 基于区块链的安全交易方法、装置、设备及存储介质
WO2020077832A1 (zh) 云桌面的访问方法、装置、设备及存储介质
WO2020107591A1 (zh) 重复投保限制方法、装置、设备及可读存储介质
WO2019205288A1 (zh) 连接建立方法、系统、设备及计算机可读存储介质

Legal Events

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

Ref document number: 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