WO2022142436A1

WO2022142436A1 - Data processing method and apparatus based on block chain, device, and storage medium

Info

Publication number: WO2022142436A1
Application number: PCT/CN2021/116248
Authority: WO
Inventors: 宋轩; 庄湛; 张浩然; 云沐晟; 林贵旭
Original assignee: 南方科技大学
Priority date: 2020-12-30
Filing date: 2021-09-02
Publication date: 2022-07-07
Also published as: CN112635061A

Abstract

A data processing method and apparatus based on a block chain, a device, and a storage medium. When being executed by a server, the method comprises: in response to a risk event processing request, determining a risk user, and modifying a risk value of the risk user (S110); sending a close contact data obtaining request of the risk user to a user terminal of the risk user, so as to instruct the user terminal to feed back close contact data of the risk user (S120); and performing risk value updating on the close contact object of the risk user according to the obtained close contact data of the risk user and a close contact certificate of the risk user already stored in a block chain network (S130). The method can improve the accuracy and reliability of a data processing process when there is a risk event.

Description

Blockchain-based data processing method, device, equipment and storage medium

technical field

The embodiments of the present application relate to the field of computer technologies, and in particular, to a method, apparatus, device, and storage medium for data processing based on blockchain.

Background technique

In order to prevent and control the spread of risk events (such as diseases), tracking the close contacts of risk users and adjusting their risk values with close contacts is an important way to prevent and control the spread of risks. At present, when there is a risk event, the staff usually analyzes and tracks the close contacts of the risk user based on the monitoring data or the close contact data obtained by visiting the user, and adjusts the risk value. The whole process is greatly affected by human factors, the accuracy and reliability are low, and it is in urgent need of improvement.

technical problem

The present application provides a blockchain-based data processing method, device, device and storage medium, which can improve the accuracy and reliability of the data processing process when there is a risk event.

technical solutions

In the first aspect, an embodiment of the present application provides a blockchain-based data processing method, which is executed by a server, and the method includes:

In response to a risk event processing request, determining a risk user, and modifying the risk value of the risk user;

sending a request for obtaining the contact data of the risk user to the client of the risk user to instruct the client to feed back the contact data of the risk user;

According to the obtained contact data of the risk user and the secret certificate of the risk user stored in the blockchain network, the risk value of the contact object of the risk user is updated.

In the second aspect, the embodiments of the present application provide a blockchain-based data processing method, which is executed by a client, and the method includes:

In response to the contact data acquisition request of the risk user sent by the server, acquire the contact data of the risk user; wherein, the contact data acquisition request is generated after the server responds to the risk event processing request;

Feedback the risk user's secret data to the server, so as to instruct the server to determine the risk user's secret according to the risk user's secret data and the risk user's secret credentials stored in the blockchain network. The value-at-risk update is performed on the close object.

In a third aspect, an embodiment of the present application provides a blockchain-based data processing device, the device includes: a first response module, a close data request module, and a risk value update module; wherein,

the first response module, configured to determine a risk user and modify the risk value of the risk user in response to a risk event processing request;

The contact data request module is configured to send the contact data acquisition request of the risk user to the user terminal of the risk user, so as to instruct the user terminal to feed back the contact data of the risk user;

The risk value update module is configured to update the risk value of the risk user's contact object according to the obtained contact data of the risk user and the contact certificate of the risk user stored in the blockchain network.

In a fourth aspect, an embodiment of the present application provides a blockchain-based data processing device, the device includes: a second response module and a feedback module; wherein,

The second response module is configured to obtain the contact data of the risk user in response to the contact data acquisition request of the risk user sent by the server; wherein, the contact data acquisition request is generated after the server responds to the risk event processing request;

The feedback module is configured to feed back the secret data of the risk user to the server, so as to instruct the server to instruct the server according to the secret data of the risk user and the secret certificate of the risk user stored in the blockchain network , and update the risk value of the close contact object of the risk user.

In a fifth aspect, an embodiment of the present application provides an electronic device, the electronic device comprising:

one or more processors;

storage means for storing one or more programs,

When the one or more programs are executed by the one or more processors, the one or more processors implement the blockchain-based data processing method according to any embodiment of the present invention.

In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, implements the blockchain-based data processing described in any embodiment of the present invention method.

beneficial effect

The embodiments of the present application provide a blockchain-based data processing method, device, device, and storage medium. In response to a risk event processing request, a risk user is determined, and its risk value is modified; the risk user is sent to the risk user's client. The user's access data acquisition request to instruct the client to feed back the risk user's access data; according to the obtained risk user's access data and the risk user's access credentials stored in the blockchain network, the risk user's access target will be processed. VaR update. In the embodiment of the present application, when there is a risk event, the server can interact with the client, relying on the blockchain network, to automatically determine the risk user's contact object and modify the risk value of the contact object, with higher accuracy and reliability. In addition, the present application uses the risk user's contact credentials stored in the blockchain network to determine the risk user's real contact object, which prevents the risk user from providing false contact data, resulting in incorrect identification of the contact object.

It should be understood that the content described in this section is not intended to identify key or critical features of the embodiments of the application, nor is it intended to limit the scope of the application. Other features of the present application will become readily understood from the following description.

Description of drawings

The accompanying drawings are used for better understanding of the present solution, and do not constitute a limitation to the present application. in:

FIG. 1 is a first schematic flowchart of a blockchain-based data processing method provided by an embodiment of the present application;

FIG. 2 is a second schematic flowchart of the blockchain-based data processing method provided by the embodiment of the present application;

FIG. 3 is a third schematic flowchart of the blockchain-based data processing method provided by the embodiment of the present application;

FIG. 4 is a fourth schematic flowchart of the blockchain-based data processing method provided by the embodiment of the present application;

FIG. 5 is a fifth schematic flowchart of the blockchain-based data processing method provided by the embodiment of the present application;

6A is a signaling diagram of a blockchain-based data processing method provided by an embodiment of the present application;

FIG. 6B is a system flow diagram of a blockchain-based data processing method provided by an embodiment of the present application;

7 is a schematic diagram of a first structure of a blockchain-based data processing apparatus provided by an embodiment of the present application;

FIG. 8 is a second schematic structural diagram of a blockchain-based data processing apparatus provided by an embodiment of the present application;

FIG. 9 is a block diagram of an electronic device used to implement the blockchain-based data processing method according to the embodiment of the present application.

Embodiments of the present invention

The present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application, but not to limit the present application. In addition, it should be noted that, for the convenience of description, the drawings only show some but not all the structures related to the present application.

Before introducing the real-time application of this application, the use scenarios of the embodiments of this application are introduced first. The embodiments of this application are mainly suitable for preventing and controlling the spread of risk events. Based on blockchain and smart contracts, a distributed storage system is used to closely connect users. In the scenario of data analysis, the blockchain of the embodiment of this application is essentially a decentralized database, which has good immutability and authenticity. A smart contract is a self-checking, self-executing and tamper-resistant machine-readable code running on a blockchain platform, which is autonomous, distributed, traceable and irreversible. In the embodiment of the present application, the smart contract has the function of determining the close connection event, the function of retrospecting the value at risk, and the function of restoring the account. Next, based on the above introduction, the specific implementation manner of the embodiment of the present application is introduced in detail.

Example 1

FIG. 1 is a first schematic flowchart of a blockchain-based data processing method provided by an embodiment of the present application. This embodiment can be applied to the situation where the server uses the distributed storage system to analyze the dense data based on the blockchain and smart contracts. The blockchain-based data processing method provided in this embodiment may be executed by the blockchain-based data processing apparatus or electronic device provided in Embodiment 6 of this application, and the device or electronic device may be implemented by software and/or hardware. The method is implemented and integrated in the server that executes this application. Optionally, the server in the embodiment of the present application may be a blockchain node, which can invoke the risk value backtracking function of the smart contract of the blockchain network to perform the following operation steps in the embodiment of the present application.

Referring to FIG. 1, the method of this embodiment includes but is not limited to the following steps:

S110. In response to the risk event processing request, determine a risk user, and modify the risk value of the risk user.

In a specific embodiment of the present application, a risk user refers to a user infected with an infectious disease. A risk event refers to an event in which a new user at risk is added or a new user is at risk of contracting an infectious disease. The risk event processing request can be generated by the risk user after learning that he is infected and sent to the server through his client, or it can be detected by third-party institutions such as hospitals, government agencies, and CDCs. When there is a new risk user or a new user is at risk of contracting an infectious disease, a risk event processing request is generated and sent to the server. The client or a third-party institution sends a risk event processing request to the server, indicating that the risk user has contracted an infectious disease or is at risk of contracting an infectious disease.

In the specific embodiment of this application, if a user is diagnosed with an infectious disease, a risk event processing request is sent to the server through the user terminal or a third-party organization. After receiving the risk event processing request, the server will start the risk event of the smart contract The condition for the automatic execution of the value backtracking function. Respond to the risk event processing request, obtain the risk user from the risk event processing request, and modify the risk value of the risk user according to the risk value modification requirements specified by the risk retrospective function. For example, the risk value of the risky user may be set to the highest risk value. The risk value refers to the user's risk value of contracting an infectious disease.

Optionally, the server may maintain a user risk value data table in the local database. At this time, the server may increase the risk value of the risk user to the maximum value in the user risk value data table. Wherein, the user risk value data table contains at least the user address and the risk value. For example, as shown in Table 1 below.

Table 1. User risk value data table

用户地址1User address 1	风险值1VaR1
用户地址2User address 2	风险值2VaR2
用户地址3User address 3	风险值3VaR3
……	……

S120: Send a request for obtaining the contact data of the risk user to the client of the risk user, so as to instruct the client to feed back the contact data of the risk user. In the specific embodiment of the present application, the user installs the close contact application on the mobile terminal (wherein, the close contact application can be regarded as the user's client terminal), when the close contact applications between users detect each other's Bluetooth signals, they can It is regarded as a close event between users. At this time, the client will obtain the contact information of the contact event; encrypt the contact information with the public keys of the users on both sides of the contact, and obtain the contact certificate; generate an on-chain transaction request including the contact certificate and send it to the server, so that the server can make the contact certificate. The credential is stored on the chain, and the index address of the blockchain that stores the secret credential is returned from the server. At the same time, the client will also use the obtained secret information and blockchain index address as secret data, and store it in the local database of the client. Among them, the contact time is the time when the contact event currently occurs; other users and risk users are called the contact object after the contact event occurs; the address of the contact object refers to the physical address of the contact object; the public key is generated when the user registers the contact application. ; The block index address refers to the serial number of the block to be produced in the next period.

In the specific embodiment of this application, after determining the risk user and modifying the risk value of the risk user, the server will send the risk user's close data acquisition request to the risk user's client, requesting that the risk user be stored in the local database. All contact data within the incubation period of the epidemic. Among them, the incubation period of the epidemic can be half a month.

S130. Update the risk value of the risk user's close contact object according to the obtained risk user's close contact data and the risk user's close contact credentials stored in the blockchain network.

In the specific embodiments of the present application, the specific process of storing the confidential credentials of risk users in the blockchain network will be similarly described in subsequent embodiments.

Optionally, the secret credential can be a number or a string.

Optionally, the secret data contains the block index address, there are many secret certificates in a block, and these secret certificates are arranged. Therefore, when the server in this embodiment of the present application searches for the user's secret certificate from the blockchain, it may search for the corresponding block according to the block index address contained in the secret data, and within the block, a binary search method may be used to search for the corresponding block. The secret certificate corresponding to the secret object.

In the specific embodiment of the present application, after obtaining all the contact data within the scope of the epidemic incubation period of the risk user, the server includes the contact time, the address of the contact object, and the public key of the contact object for each piece of contact data. Generate a prediction credential based on the piece of concatenated data (that is, the generation method is the same as the way that the client generates the concatenated credential based on the concatenated data), which is compared with the concatenated credential obtained from the blockchain network. If the encryption certificate obtained from the blockchain network does not contain the prediction certificate, it means that the encryption data has been tampered with, ignore the encryption data, and update the risk value of the encryption object based on the encryption data; otherwise It indicates that this piece of contact data is real and effective, and it can be determined that there is a contact event between the risk user and the contact object, and the contact object has the risk of being infected with disease. Therefore, the risk value corresponding to the contact object is updated. A specific way of updating the risk value may be preset, for example, it may be to increase the preset risk value.

Further, according to the obtained access data of the risk user and the stored access credentials of the risk user in the blockchain network, update the risk value of the access object of the risk user, including: according to the obtained access data of the risk user and the block Update the risk value of the risk user's contact object with the stored risk user's secret certificate in the chain network; take the contact object as a new risk user, and return to perform the operation of updating the risk value of the new risk user's contact object until Complete the VaR iteration requirement. That is, the risk value backtracking is performed on the direct contact object and the indirect contact object of the risk user. The specific process is as follows: according to the obtained contact data of the risk user, determine the contact object, contact information and block index address of the risk user; use the public key of the contact object and the public key of the risk user to encrypt the contact information to obtain the prediction certificate ; Determine the target block according to the block index address, and determine whether there is a close-contact certificate matching the predicted certificate in the target block; if there is, update the risk value of the close-contact object. After the analysis of all the contact data of the risk user is completed, take the contact object of the risk user as a new risk user, send the contact data acquisition request to the new risk user, and repeat the execution according to the acquired contact data of the new risk user. The value-at-risk of the new risky user's encrypted credentials stored in the blockchain network is updated, and so on, so as to iteratively update the risky value of the risky user's closet object. Optionally, the iteration requirement may be the number of iterations required, and in general, two to three iterations are sufficient.

Exemplarily, risk user 1 is diagnosed with an infectious disease. If the prediction credentials of risk user 1 and the close contact data of close contact object 1 are consistent with the close contact certificate, that is, contact object 1 is the first-level contact object of risk user 1, then according to the above intelligence The risk value retrospective function method of the contract updates the risk value of risk user 1 and close object 1. Take the contact object 1 as the new risk user 2, if the prediction credential of the contact data of the risk user 2 and the contact object 2 is the same as the contact certificate, that is, the contact object 2 is the second level contact object of the risk user 1, then according to the above smart contract The risk value retrospective function method updates the risk value of risk user 2 and close contact object 2. According to this method, the direct contact objects and the indirect contact objects of the risk user are sequentially updated multiple times iteratively. Optionally, the number of iterations is preset, and the number of iterations may be two, three or more. It is understandable that a risk user can have multiple contact objects. When updating the risk value, the risk value of the second level contact object is modified less than that of the first level contact object. For example, when the risk value of the first level contact object is updated, its risk value is changed. Increase by 8; when the second-level close contact object updates the risk value, its risk value is increased by 5.

In the technical solution provided by this embodiment, in response to a risk event processing request, a risk user is determined and its risk value is modified; a request for obtaining the contact data of the risk user is sent to the risk user's client to instruct the client to feedback the risk user's data. Contact data: According to the acquired contact data of the risk user and the contact credentials of the risk user stored in the blockchain network, update the risk value of the contact object of the risk user. In the embodiment of the present application, when there is a risk event, the server interacts with the client, and relying on the blockchain network, the determination of the close object of the target object and the modification of the risk value of the close object can be performed automatically, with higher accuracy and reliability. In addition, the present application determines the real contact object of the risk user based on the contact credentials of the risk user stored in the blockchain network, which prevents the risk user from providing false contact data, resulting in an error in the determination of the contact object.

Embodiment 2

FIG. 2 is a second schematic flowchart of the blockchain-based data processing method provided by the embodiment of the present application. The embodiment of the present application is based on the above-mentioned embodiment, and this embodiment provides a detailed explanation of the specific execution process of the server responding to the up-chain transaction request including the concatenated credential when there is a concatenated event.

S210. In response to the on-chain transaction request including the secret certificate, obtain the secret certificate, and store the secret certificate in the blockchain.

Wherein, the close connection certificate is obtained by encrypting the close connection information of the two users of the close connection by using the public keys of the two users of the close connection when the close connection event is detected. The specific generation process will be described in detail in subsequent embodiments.

In the specific embodiment of the present application, for any user registered with the close contact application, the close contact application of the close contact application and the close contact application of its close contact object detect each other's Bluetooth signals, it is determined that the user and the close contact object have a close contact event. The conditions for the automatic execution of the close contact determination function of the smart contract. The contact application will generate a block of contact information and encrypt it as a contact certificate. The contact information includes at least the combination of public keys and the contact time of both users of the contact, and may also include the address of the contact object. The secret application generates an on-chain transaction request containing the secret certificate and sends it to the server. The server responds to the on-chain transaction request containing the secret certificate, obtains the secret certificate, and stores the secret certificate in the blockchain. Among them, the specific on-chain transaction refers to the server sorting and packaging the secret certificate sent by the client, and writing it into the block.

S220: Obtain the block index address for storing the secret certificate, and feed back the block index address to the client that sends the on-chain transaction request.

In the specific embodiment of the present application, the server feeds back the block index address where the secret certificate is stored to the client that sends the on-chain transaction request.

The client side saves the block index address and the obtained concatenation information together as concatenated data in the user risk value data table maintained by the local database. Optionally, the blockchain index address may be a block serial number, a block identifier, or the like.

S230. Update the risk value of the users of both parties in the close connection.

Optionally, the server can determine the identity information of the two parties according to the obtained password. Since the server maintains a user risk value data table locally, the risk value of the two parties can be obtained from the user risk value data table for comparison. When the risk value of the two parties is different, the risk value of the two parties will be updated at the same time through the smart contract. For example, it is possible to compare the value-at-risk of both parties in close contact, select a higher value of risk, and update the value of risk of both parties to the higher value of risk.

Optionally, after the risk value corresponding to the close contact object is updated, the updated risk value may also be fed back to the corresponding user terminal.

S240. In response to the risk event processing request, determine the risk user, and modify the risk value of the risk user.

S250. Send a request for obtaining the contact data of the risk user to the client terminal of the risk user, so as to instruct the client terminal to feed back the contact data of the risk user.

S260: Update the risk value of the risk user's close contact object according to the obtained risk user's close contact data and the risk user's close contact credentials stored in the blockchain network.

It should be noted that, the processes from S210 to S230 in the embodiments of the present application are related operations performed by the server in response to an up-chain transaction request including a secure credentials when a secure event exists. S240-S260 are related operations performed by the server in response to a risk event processing request when a risk event exists. The two are two independent execution processes, and there is no prior order. They may be executed according to the order of the above-mentioned embodiment, or S240-S260 may be executed first, and then S210-S230 may be executed, which is not carried out in this embodiment. limited.

The technical solution of the embodiment of the present application is to obtain the encrypted data and store it in the blockchain after responding to a request for an up-chain transaction including the encrypted certificate, and at the same time update the risk value of both parties. The embodiment of the application stores the encrypted certificate in the blockchain network. In the subsequent process of responding to the risk event processing request, the access data of the risk user can be obtained, and the access certificate can be used to verify the accuracy of the obtained access data of the risk user, to prevent the risk user from forging and tampering with the access data, and to ensure the integrity of the access data. true reliability. Obtain the block index address where the secret certificate is stored, and feed it back to the client that sends the transaction request on the chain for storage, so that the secret certificate corresponding to the secret data can be quickly searched in the blockchain network according to the secret data sent by the risk user. When there is a risk event, the server interacts with the client, relying on the blockchain network to automatically determine the target object's close object and modify the risk value of the close object, with higher accuracy and reliability.

Embodiment 3

FIG. 3 is a schematic flowchart of a third process of the blockchain-based data processing method provided by the embodiment of the present application. The embodiment of the present application is based on the above-mentioned embodiment, and this embodiment provides a detailed explanation of the account recovery function process of the smart contract.

Referring to FIG. 3, the method of this embodiment includes but is not limited to the following steps:

S310. In response to the risk event processing request, determine the risk user, and modify the risk value of the risk user.

S320. Send a request for obtaining the contact data of the risk user to the client of the risk user, so as to instruct the client to feed back the contact data of the risk user.

S330. Update the risk value of the risk user's close contact object according to the obtained risk user's close contact data and the risk user's close contact credentials stored in the blockchain network.

S340. In response to the first account encryption request, use the public key of the first account to encrypt the preset data to obtain an encryption result.

In the specific embodiment of this application, when the account becomes invalid due to the replacement of the mobile phone number or the loss of the SIM card, the user can create a second account through the new mobile phone number, and use the private key of the first account to request to restore the first account The risk value, at this time, reaches the conditions for the automatic execution of the account recovery function of the smart contract. For example, there is an option to restore the risk value of the first account on the user interface. Click this option and enter the private key of the first account to trigger the account recovery function. The user triggers the first account recovery request on the user interface. In response to the first account recovery request, the client generates a first account encryption request and sends it to the server. The server receives and responds to the first account encryption request, and uses the public key of the first account to encrypt the preset data to obtain an encryption result. Optionally, the preset data may be preset fixed data or randomly generated data. The purpose of encrypting the preset data by using the public key of the first account is to verify whether the user's private key is correct.

S350. Feed back the encryption result to the user terminal that sent the first account encryption request, so as to instruct the user terminal to feed back the verification result after verifying the first account according to the encryption result.

In the specific embodiment of the present application, in the above steps, the server uses the public key of the first account to encrypt the preset data, and after obtaining the encryption result, the server feeds back the encryption result to the client that sent the encryption request of the first account . The client uses the private key of the first line number to decrypt and analyze the encrypted result data to verify whether the private key of the first account included in the account recovery request is correct. And feedback the verification result to the server.

S360. If the received verification result is passed, use the risk value of the first account as the risk value of the current login account of the client.

In the specific embodiment of the present application, the client verifies the private key of the first account, and if the verification result is passed, the verification result is fed back to the server. If the verification result is passed, the server restores the risk value of the first account, that is, the risk value of the first account is taken as the risk value of the current login account of the client. If the verification result is not passed, the user terminal may not feed back the verification result to the server; it may also be fed back to the server, but the server detects that the verification result is not passed, and does not perform the operation of risk value recovery.

S370. Use the concatenated data of the first account as the concatenated data of the current account.

In the specific embodiment of the present application, not only the risk value of the first account but also the concatenated data of the first account can be restored. Use the account recovery function of the smart contract to obtain the secret data from the client of the first account, and then send the obtained secret data to the client of the current account (that is, the client that sent the encryption request of the first account) to indicate the client The obtained contiguous data is stored in the local database, so as to realize the recovery of the contiguous data.

It should be noted that, in the embodiments S310-S330 of the present application, when there is a risk event, the server performs related operations in response to the risk event processing request. The process from S340 to S370 is the relevant operation performed by the server in response to the first account encryption request when the user needs to restore the account risk value and the encrypted data. The two are two independent execution processes, and there is no prior order. According to the sequence of the above embodiments, S340-S370 may also be executed first, and then S310-S330 are executed, which is not limited in this embodiment.

In the technical solution provided by this embodiment, in response to the first account encryption request, the server uses the public key of the first account to encrypt the preset data to obtain an encryption result. The encryption result is fed back to the client that sent the encryption request for the first account, so as to instruct the client to feed back the verification result after verifying the first account according to the encryption result. If the received verification result is passed, the risk value of the first account is taken as the risk value of the current login account of the client, and the concatenated data of the first account can also be taken as the concatenated data of the current account. That is, by using the account recovery function of the smart contract, the problem of account invalidation caused by the replacement of the mobile phone number or the loss of the SIM card can be solved, the user's risk value and the security of the contact data can be restored, and the integrity of the contact application function can be guaranteed.

Embodiment 4

FIG. 4 is a fourth schematic flowchart of the blockchain-based data processing method provided by the embodiment of the present application. This embodiment can be applied to the situation where the user terminal analyzes and processes the dense data based on the smart contract based on the blockchain. The blockchain-based data processing method provided in the seventh embodiment of the present application may be executed by the blockchain-based data processing apparatus or electronic device provided in the embodiment of the present application, and the device or electronic device may be implemented by software and/or hardware. The method is implemented and integrated in the client that executes the present application.

4, the method of this embodiment includes but is not limited to the following steps:

S410 , in response to the request for obtaining the contact data of the risk user sent by the server, acquire the contact data of the risk user.

Wherein, the close data acquisition request is generated after the server responds to the risk event processing request. The specific generation method has been introduced in the above embodiment, and is not described in this embodiment here.

In the specific embodiment of this application, if a user is diagnosed with an infectious disease, a risk event processing request is sent to the server through the user terminal or a third-party organization, and the server responds to the risk event processing request. First, the server will increase the risk value of the risk user to the maximum value in the data table maintained in the local database. Wherein, the data table at least contains the time of the close connection, the address of the close connection object, the risk value and the block index address. In addition, the server sends the risk user's contact data acquisition request to the risk user's client, requesting to obtain all the contact data stored in the local database by the risk user within the scope of the epidemic incubation period. The client of the risk user responds to the request for obtaining the close contact data of the risk user sent by the server, and obtains all the close contact data of the risk user within the scope of the epidemic incubation period from the local database. Among them, the incubation period of the epidemic can be half a month.

S420. Feed back the risk user's contact data to the server, so as to instruct the server to update the risk value of the risk user's contact object according to the risk user's contact data and the risk user's secret certificate stored in the blockchain network.

In the specific embodiment of the present application, after acquiring the contact data of the risk user stored in the local database, the client terminal of the risk user feeds back the contact data of the risk user to the server. It instructs the server to determine the real contact object of the risk user according to the contact data of the risk user and the contact credentials of the risk user that have been stored in the blockchain network, and to update the risk value. The specific execution process has been described above. The embodiment is introduced, and is not repeated in this embodiment.

In the technical solution provided by this embodiment, the client of the risk user responds to the request for obtaining the contact data of the risk user sent by the server, obtains the contact data of the risk user, and feeds it back to the server, so as to instruct the server to obtain the contact data of the risk user according to the block chain. Update the risk value of the risk user's contact object based on the secret certificate of the risk user that has been stored in the network. In the solution of this embodiment, when there is a risk event, the client interacts with the server, and based on the risk user's secret data sent by the client and the secret certificate stored in the blockchain network, the client sends the risk user's secret link. The data is verified to ensure the accuracy of the determined contact object, which solves the problem of preventing forgery and tampering with the contact data, resulting in inaccurate determination of the contact object, thereby ensuring the accuracy of updating the risk value of the contact object.

Embodiment 5

FIG. 5 is a fifth schematic flowchart of the blockchain-based data processing method provided by the embodiment of the present application. The embodiment of the present application applies the data processing method based on the block chain to the user terminal on the basis of the above-mentioned embodiment, and the data processing process is explained in detail in this embodiment. Referring to FIG. 5, the method of this embodiment includes but is not limited to the following steps:

S510. If a close contact event is detected, acquire contact information of the close contact event.

In the specific embodiment of the present application, when the user's close application (that is, the user terminal of any user) and the close application of its close object detect each other's Bluetooth signals, it is determined that there is a close connection event between the risk user and the close object. The conditions for the automatic execution of the close contact determination function of the smart contract. The contact application obtains the contact information of the contact event. The contact information includes at least the combination of public keys and the contact time of both users of the contact, and may also include the address of the contact object. Optionally, judging that there is a close contact event between the risk user and the close contact object may be that the user terminal of the risk user detects that there is a Bluetooth signal with a strength greater than a certain threshold around, and considers that the user corresponding to the Bluetooth signal is the close contact object of the risk user. Optionally, the address of the contact object in the contact information may be obtained through Bluetooth, or may be obtained by calculation through the public key of the contact object. The public key of the contact object in the contact information can be obtained through Bluetooth, or obtained from the server after determining the contact object.

Preferably, if a close contact event is detected, acquiring the close contact information of the close contact event includes: if the close contact event is detected and the close contact event is not a repeated close contact event, acquiring the close contact information of the close contact event. Specifically, the close connection time may be in days. If the risk user is paired with the close contact object for the first time on that day and it is determined that a close contact event occurs with the close contact object, then the acquisition of the close contact information of the close contact event is performed at this time. Otherwise, even if the user performs Bluetooth pairing with the contact object on that day, the operation of acquiring the contact information of the contact event will not be performed.

S520 , encrypting the information of the close connection by using the public keys of the users of both sides of the close connection to obtain a close connection certificate.

In the specific embodiment of the present application, the encryption information is encrypted by using the public keys of the users of both parties to obtain the encryption certificate. Optionally, the encryption method for the encryption information may be an asymmetric encryption method, so that the encrypted content will not be leaked, and the user encryption data can be completely protected. Optionally, the address of the contact object in the contact information may be obtained through Bluetooth, or may be obtained by calculation through the public key of the contact object. The public key of the contact object in the contact information can be obtained through Bluetooth, or obtained from the server after determining the contact object. Optionally, the secret credential can be a number or a string.

S530. Generate and send an on-chain transaction request including the secret credential to the server, so as to instruct the server to store the secret credential on the chain.

In the specific embodiment of the present application, the client sends an on-chain transaction request containing the secret certificate to the server, and the server responds to the on-chain transaction request containing the secret certificate, obtains the secret certificate, and stores the secret certificate in the blockchain. . The specific chaining process has been described in detail in the above embodiment, and will not be repeated here.

S540: Obtain the block index address of the storage secret credential returned by the server.

In the specific embodiment of this application, after the server has stored the secret certificate on the chain, it will feed back the block index address where the secret certificate is stored to the client that sent the transaction request on the chain. At this time, the client obtains the feedback from the server. The index address of the block where the encryption certificate is stored.

S550. Store the concatenation information and the block index address locally as concatenated data.

In the specific embodiment of the present application, the user terminal saves the contact information and the block index address as the contact data in the contact data table maintained by the local database, as shown in Table 2 below.

Table 2. Adhesion data table

S560, in response to the request for obtaining the contact data of the risk user sent by the server, acquire the contact data of the risk user.

S570. Feed back the risk user's contact data to the server, so as to instruct the server to update the risk value of the risk user's contact object according to the risk user's contact data and the risk user's secret certificate stored in the blockchain network.

Further, after the user installs the close connection application on the user terminal, the user needs to register his own close connection account when using the close connection application for the first time. In response to an account registration request triggered by the user, the client terminal generates account information of the user, wherein the account information includes: the public key, private key, account address and initial risk value of the account. Among them, the private key is generated by encrypting the mobile phone number information combined with a cryptographically secure random source; the public key is calculated by the private key through elliptic curve multiplication; the address is hashed once by the public key and the RIPEMD160 hash value is calculated, Then it is obtained after Bases8Check coding; when the account is registered, the user sets the disease risk value to be initially set to zero.

Optionally, the client can send the generated public key and disease risk value to the server to instruct the server to store the information on the chain or in a local database for other users to query. To ensure the security of user account information, the private key value generated by the client is stored in the local database.

Further, when the account is invalid due to the replacement of the mobile phone number or the loss of the SIM card, the user can create a second account through the new mobile phone number, and use the private key of the first account to request the restoration of the risk value of the first account. The conditions for the automatic execution of the account recovery function of the smart contract. For example, there is an option to restore the risk value of the first account on the user interface. Click this option and enter the private key of the first account to trigger the account recovery function. The user sends a first account recovery request on the user interface. In response to the account recovery request triggered by the user, the client generates a first account encryption request and sends it to the server to instruct the server to encrypt the preset data with the public key of the first account, and feed back the encryption result; use the private key of the first account to verify the service The encrypted result is fed back, and the verification result is fed back to the server, so as to instruct the server to perform the account data recovery operation based on the verification result. The specific execution process has been described in detail in the foregoing embodiment, and is not repeated in this embodiment here.

In the technical solution provided by this embodiment, the contact information of the contact event is obtained by detecting the contact event; the contact information is encrypted by the public keys of the users of both parties to obtain the contact certificate; the client generates an upload transaction request including the contact certificate and sends it to The server instructs the server to store the secret certificate on the chain and update the risk value of the users on both sides of the secret; the client obtains the block index address of the secret certificate returned by the server, and stores the secret information and block index address as secret data in the Local; the client obtains the contact data of the risk user in response to the request for obtaining the contact data of the risk user sent by the server. Feedback the risk user's contact data to the server to instruct the server to update the risk value of the risk user's contact object according to the risk user's contact data and the risk user's secret certificate stored in the blockchain network. In this embodiment, the user's encrypted data is stored locally on the user end, and the encrypted data's encrypted credentials are stored in the blockchain network, so as to prevent the user's encrypted data from being leaked and ensure the security and privacy of the encrypted data. Even if the user sends his own forged or tampered data to the value server, the server can identify it based on the encrypted data stored in the blockchain network, which greatly improves the confidentiality and accuracy of information during the processing of the encrypted data.

Embodiment 6

FIG. 6A is a signaling diagram of the blockchain-based data processing method provided by the embodiment of the present application; FIG. 6B is a system flowchart of the blockchain-based data processing method provided by the embodiment of the present application. On the basis of the above-mentioned embodiment, the embodiment of the present application provides a preferred example of mutual data processing between the client and the server based on the blockchain. Specifically, this embodiment includes the following steps:

S601. If the first user terminal detects the close connection event, obtain the close connection information of the close connection event.

S602: The first user terminal uses the public keys of the users of both sides of the close connection to encrypt the close connection information to obtain a close connection certificate.

S603. The first client generates an on-chain transaction request including the secret credential and sends it to the server.

S604, the server obtains the secret certificate in response to the on-chain transaction request including the secret certificate, and stores the secret certificate in the blockchain.

S605. The server obtains the block index address for storing the encryption certificate, and feeds back the block index address to the first client that sends the on-chain transaction request.

S606. The first client obtains the block index address of the storage secret credential fed back by the server.

S607: The first user terminal stores the concatenation information and the block index address locally as concatenated data.

S608, the server updates the risk value of the users of both parties in the close connection.

Wherein, S601-S608 is a process for the server to update the risk value of both users of the close connection when there is a close connection event between the risk users. As shown in FIG. 6B , when the close connection applications between user A and user B detect each other's Bluetooth signals, it can be regarded as a close connection event between users. At this time, the first client (in this case, both the contact applications of user A and user B can be used as the first client) will acquire contact information of the contact event. Wherein, the contact information includes at least the combination of public keys and the contact time of both users of the contact (i.e., user A and user B), and may also include the address of the contact object. The first client uses the public keys of the users of both parties to encrypt the contact information, and obtains a certificate for the contact information, which is used to verify whether the contact information is authentic. The first client generates an on-chain transaction request including the secret credential and sends it to the server, and the server packages the secret credential, sorts it according to the hash value, and writes it into the blockchain. The server obtains the block index address where the secret certificate is stored, and feeds it back to the first client. The first user terminal stores the concatenation information and the block index address locally as concatenated data. The server updates the risk value of users on both sides of the connection.

S609, the server determines the risk user in response to the risk event processing request, and modifies the risk value of the risk user.

S610. The server sends a request for obtaining the contact data of the risk user to the client of the risk user.

S611. The client terminal of the risk user, in response to the request for obtaining the contact data of the risk user sent by the server, acquires the contact data of the risk user.

S612. The client of the risk user feeds back the close data of the risk user to the server.

S613. The server updates the risk value of the risk user's contact object according to the obtained contact data of the risk user and the contact certificate of the risk user stored in the blockchain network.

Wherein, S609-S613 is a process in which the server modifies the risk value of the risk user and the risk value of the close contact object of the risk user when a user becomes a risk user after changing an infectious disease. As shown in Figure 6B, after a professional institution such as a hospital detects that a patient has been diagnosed, it sends a risk event processing request to the server through the user terminal or a third-party institution. After receiving the risk event processing request, the server determines the risk user and modifies the risk User's value at risk. After the server receives the risk event processing request, it will activate the conditions for the automatic execution of the risk value backtracking function of the smart contract. The server requests to obtain all the contact data of the risk user's client within the scope of the epidemic incubation period, and generates a prediction certificate based on each contact data. The risk value of the user's contact object is updated.

S614. The second client terminal generates account information of the user in response to the account registration request triggered by the user. The account information includes: the public key, private key, account address and initial risk value of the account.

S615. In response to the account recovery request triggered by the user, the third client terminal generates a first account encryption request and sends the request to the server.

S616. The server, in response to the first account encryption request, encrypts the preset data by using the public key of the first account to obtain an encryption result.

S617: The server feeds back the encryption result to the client that sent the first account encryption request.

S618. The third client uses the private key of the first account to verify the encryption result fed back by the service, and feeds back the verification result to the server.

S619: If the received verification result is passed, the server uses the risk value of the first account as the risk value of the current login account of the client.

S620. The server uses the concatenated data of the first account as the concatenated data of the current account.

Among them, S614 is the first time the user uses the close connection application to register an account. S615-S620 is to use the account recovery function to restore the contact information of the first account when the account becomes invalid due to the replacement of the user's mobile phone number or the loss of the SIM card.

It should be noted that, the first user terminal, the second user terminal, the third user terminal, and the user terminal of the risk user in the embodiment of the present application may be the user terminal of the same user or the user terminal of different users. This embodiment will not describe redundantly.

It should be noted that the servers involved in the embodiments of the present application may be determined from at least two candidate servers based on a Byzantine consensus mechanism. Specifically, the server in this embodiment of the present application is not a centralized server, but a server cluster composed of multiple candidate servers. When performing the operations in the foregoing embodiments, it is possible to specifically select which server in the server cluster to perform the operations. It is determined by a consensus mechanism. Optionally, the consensus mechanism can be proof of work (PoW), proof of stake (PoS), and Practical Byzantine Fault Tolerance (PBFT). The consensus mechanism preferably adopted in the embodiment is PBFT. According to the multi-PBFT consensus mechanism, Byzantine behavior can be detected and automatically recovered to avoid program crash caused by master node abnormality. Unlike early Byzantine fault-tolerant algorithms that could only run on synchronous systems, practical Byzantine fault-tolerant algorithms can work in an asynchronous environment, and improve the response performance of early Byzantine fault-tolerant algorithms by more than an order of magnitude.

Embodiment 7

FIG. 7 is a schematic diagram of a first structure of a blockchain-based data processing apparatus provided by an embodiment of the present application. As shown in FIG. 7 , the apparatus 700 may include:

The first response module 710 is configured to, in response to a risk event processing request, determine a risk user, and modify the risk value of the risk user.

The contact data request module 720 is configured to send the contact data acquisition request of the risk user to the client terminal of the risk user, so as to instruct the client terminal to feed back the contact data of the risk user.

The risk value updating module 730 is configured to update the risk value of the risk user's contact object according to the obtained contact data of the risk user and the risk user's secret certificate stored in the blockchain network.

Further, the above-mentioned risk value update module 730 is specifically configured to, according to the obtained close contact data of the risk user and the close contact credentials of the risk user stored in the blockchain network, perform a close contact operation on the risk user's close contact object. Risk value update; take the contact object as a new risk user, and return to perform the operation of updating the risk value of the contact object of the new risk user until the risk value iteration requirement is completed. Further, the above-mentioned risk value update module 730 is specifically configured to, according to the obtained contact data of the risk user, determine the contact object, contact information and block index address of the risk user; adopt the public key of the contact object. and the public key of the risk user, encrypt the contact information, and obtain a prediction certificate; determine a target block according to the block index address, and determine whether there is a match with the prediction certificate in the target block. Contact credentials; if there is, update the risk value of the contact object.

Further, the above-mentioned blockchain-based data processing device may further include: an on-chain transaction request module 740 (not shown in the figure), configured to obtain the encrypted connection in response to an upper-chain transaction request including a certificate, and store the close connection certificate in the blockchain, wherein the close connection certificate is obtained by using the public keys of the users of both sides of the close connection to encrypt the close connection information of the users of both sides of the close connection when a close connection event is detected; update The risk value of the users on both sides of the close connection. Acquiring the block index address that stores the secret certificate, and feeding back the block index address to the client that sent the on-chain transaction request.

Further, the above-mentioned blockchain-based data processing device may further include: a first account recovery module 750 (not shown in the figure), for responding to the first account encryption request, using the first account The public key is used to encrypt the preset data to obtain an encryption result; the encryption result is fed back to the client that sent the first account encryption request to instruct the client to verify the first account according to the encryption result. Then, the verification result is fed back; if the received verification result is passed, the risk value of the first account is used as the risk value of the current login account of the user terminal. The concatenated data of the first account is used as the concatenated data of the current account.

Optionally, in the blockchain-based data processing apparatus provided in any of the foregoing embodiments, the server is determined from at least two candidate servers based on a Byzantine consensus mechanism.

The blockchain-based data processing apparatus provided in this embodiment is applicable to the blockchain-based data processing method provided by any of the above embodiments, and has corresponding functions and beneficial effects.

Embodiment 8

FIG. 8 is a second schematic structural diagram of a blockchain-based data processing apparatus provided by an embodiment of the present application. As shown in FIG. 8 , the apparatus 800 may include:

The second response module 810 is configured to obtain the contact data of the risk user in response to the contact data acquisition request of the risk user sent by the server; wherein the contact data acquisition request is generated by the server in response to the risk event processing request.

The feedback module 820 is configured to feed back the contact data of the risk user to the server, so as to instruct the server to instruct the server according to the contact data of the risk user and the secret certificate of the risk user stored in the blockchain network, The risk value update is performed on the close object of the risk user.

Further, the above-mentioned blockchain-based data processing device may further include: a response to an uplink transaction request module 830 (not shown in the figure), configured to obtain the close connection of the close connection event if a close connection event is detected. use the public keys of the users of both parties to encrypt the secret information to obtain the secret certificate; generate an on-chain transaction request including the secret certificate and send it to the server to instruct the server to store the secret certificate on the chain, And update the risk value of the users on both sides of the close connection. In addition, if a close contact event is detected, and the close contact event is not a repeated close contact event, then the contact information of the close contact event is acquired.

Further, the above-mentioned blockchain-based data processing device may further include: a close data storage module 840 (not shown in the figure) for obtaining the block index address fed back by the server for storing the close pass certificate; The concatenation information and the block index address are stored locally as concatenated data.

Further, the above-mentioned blockchain-based data processing device may also include: a response account registration request module 850 (not shown in the figure), for generating an account of the user in response to an account registration request triggered by a user information, wherein the account information includes: the public key, private key, account address and initial risk value of the account.

Further, the above-mentioned blockchain-based data processing device may further include: a first account recovery request module 860 (not shown in the figure), configured to generate a first account in response to an account recovery request triggered by a user The encryption request is sent to the server to instruct the server to use the public key of the first account to encrypt the preset data, and feed back the encryption result; use the private key of the first account to verify the encryption result fed back by the service, and feed back to the server The verification result is used to instruct the server to perform an account data recovery operation based on the verification result.

Embodiment 9

According to the embodiments of the present application, the present application further provides an electronic device and a readable storage medium.

As shown in FIG. 9 , it is a block diagram of an electronic device of a blockchain-based data processing method according to an embodiment of the present application. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. Electronic devices may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are by way of example only, and are not intended to limit implementations of the application described and/or claimed herein.

As shown in FIG. 9, the electronic device includes: one or more processors 910, a memory 920, and interfaces for connecting various components, including a high-speed interface and a low-speed interface. The various components are interconnected using different buses and may be mounted on a common motherboard or otherwise as desired. The processor may process instructions executed within the electronic device, including instructions stored in or on memory to display graphical information of the GUI on an external input/output device, such as a display device coupled to the interface. In other embodiments, multiple processors and/or multiple buses may be used with multiple memories and multiple memories, if desired. Likewise, multiple electronic devices may be connected, each providing some of the necessary operations (eg, as a server array, a group of blade servers, or a multiprocessor system). A processor 910 is taken as an example in FIG. 9 .

The memory 920 is the non-transitory computer-readable storage medium provided by the present application. Wherein, the memory stores instructions executable by at least one processor, so that the at least one processor executes the blockchain-based data processing method provided by the present application. The non-transitory computer-readable storage medium of the present application stores computer instructions, and the computer instructions are used to cause the computer to execute the blockchain-based data processing method provided by the present application.

As a non-transitory computer-readable storage medium, the memory 920 can be used to store non-transitory software programs, non-transitory computer-executable programs and modules, such as a program corresponding to a blockchain-based data processing method in the embodiments of the present application Instructions/modules (eg, the first response module 710, the contact data request module 720, and the risk value update module 730 shown in FIG. 7; the second response module 810, the feedback module 820 shown in FIG. 8). The processor 910 executes various functional applications and data processing of the server by running the non-transitory software programs, instructions and modules stored in the memory 920, that is, implementing a blockchain-based data processing method in the above method embodiments .

The memory 920 may include a storage program area and a storage data area, wherein the storage program area may store an operating system and an application program required by at least one function; the storage data area may store data of an electronic device according to a blockchain-based data processing. Use the created data, etc. Additionally, memory 920 may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, the memory 920 may optionally include memory located remotely from the processor 910, and these remote memories may be connected via a network to a blockchain-based data processing electronic device. Examples of such networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

The electronic device based on the block chain data processing method may further include: an input device 930 and an output device 940 . The processor 910, the memory 920, the input device 930, and the output device 940 may be connected by a bus or in other ways, and the connection by a bus is taken as an example in FIG. 9 . The input device 930 can receive input numerical or character information, and generate key signal input related to user settings and function control of a blockchain-based data processing electronic device, such as a touch screen, keypad, mouse, trackpad, Input devices such as touchpads, pointing sticks, one or more mouse buttons, trackballs, joysticks, etc. The output device 940 may include a display device, auxiliary lighting devices (eg, LEDs), haptic feedback devices (eg, vibration motors), and the like. The display device may include, but is not limited to, a liquid crystal display (LCD), a light emitting diode (LED) display, and a plasma display. In some implementations, the display device may be a touch screen.

Various implementations of the systems and techniques described herein can be implemented in digital electronic circuitry, integrated circuit systems, application specific ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include being implemented in one or more computer programs executable and/or interpretable on a programmable system including at least one programmable processor that A processor, which may be a special purpose or general-purpose programmable processor, may receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device output device.

These computational programs (also referred to as programs, software, software applications, or codes) include machine instructions for programmable processors, and may be implemented using high-level procedural and/or object-oriented programming languages, and/or assembly/machine languages calculation program. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and/or apparatus for providing machine instructions and/or data to a programmable processor ( For example, magnetic disks, optical disks, memories, programmable logic devices (PLDs), including machine-readable media that receive machine instructions as machine-readable signals. The term "machine-readable signal" refers to any signal used to provide machine instructions and/or data to a programmable processor.

To provide interaction with a user, the systems and techniques described herein may be implemented on a computer having a display device (eg, a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user ); and a keyboard and pointing device (eg, a mouse or trackball) through which a user can provide input to the computer. Other kinds of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (eg, visual feedback, auditory feedback, or tactile feedback); and can be in any form (including acoustic input, voice input, or tactile input) to receive input from the user. The systems and techniques described herein may be implemented on a computing system that includes back-end components (eg, as a data server), or a computing system that includes middleware components (eg, an application server), or a computing system that includes front-end components (eg, a user's computer having a graphical user interface or web browser through which a user may interact with implementations of the systems and techniques described herein), or including such backend components, middleware components, Or any combination of front-end components in a computing system. The components of the system may be interconnected by any form or medium of digital data communication (eg, a communication network). Examples of communication networks include: Local Area Networks (LANs), Wide Area Networks (WANs), the Internet, and blockchain networks.

A computer system can include clients and servers. Clients and servers are generally remote from each other and usually interact through a communication network. The relationship of client and server arises by computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also known as a cloud computing server or a cloud host. It is a host product in the cloud computing service system to solve the traditional physical host and VPS services, which are difficult to manage and weak in business scalability. defect.

According to the technical solutions of the embodiments of the present application, the server, in response to the risk event processing request, determines the risk user, and modifies its risk value; and sends the risk user's close data acquisition request to the risk user's client to instruct the client to feedback the risk user. The risk user's contact data; according to the obtained risk user's contact data and the risk user's secret certificate stored in the blockchain network, the risk value of the risk user's contact object is updated. In the embodiment of the present application, when there is a risk event, the server interacts with the client, and relying on the blockchain network, the determination of the close object of the target object and the modification of the risk value of the close object can be performed automatically, with higher accuracy and reliability. In addition, the present application determines the real contact object of the risk user based on the contact credentials of the risk user stored in the blockchain network, which prevents the risk user from providing false contact data, resulting in an error in the determination of the contact object.

It should be understood that steps may be reordered, added or deleted using the various forms of flow shown above. For example, the steps described in the present application can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solutions disclosed in the present application can be achieved, no limitation is imposed herein.

The above-mentioned specific embodiments do not constitute a limitation on the protection scope of the present application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modifications, equivalent replacements and improvements made within the spirit and principles of this application shall be included within the protection scope of this application.

Claims

A blockchain-based data processing method, characterized in that it is executed by a server, the method comprising:

In response to a risk event processing request, determining a risk user, and modifying the risk value of the risk user;

sending a request for obtaining the contact data of the risk user to the client of the risk user to instruct the client to feed back the contact data of the risk user;

According to the obtained contact data of the risk user and the secret certificate of the risk user stored in the blockchain network, the risk value of the contact object of the risk user is updated.
The method according to claim 1, characterized in that, according to the obtained contact data of the risk user and the secret certificate of the risk user stored in the blockchain network, the risk user's contact object is subject to risk Value updates, including:

According to the obtained contact data of the risk user and the contact credentials of the risk user stored in the blockchain network, update the risk value of the contact object of the risk user;

The contact object is regarded as a new risk user, and the operation of updating the risk value of the contact object of the new risk user is returned to until the iteration requirement of the risk value is completed.
The method according to claim 1, characterized in that, according to the obtained contact data of the risk user and the secret certificate of the risk user stored in the blockchain network, the risk user's contact object is subject to risk Value updates, including:

According to the obtained contact data of the risk user, determine the contact object, the contact information and the block index address of the risk user;

Using the public key of the contact object and the public key of the risk user, encrypting the contact information to obtain a prediction certificate;

Determine a target block according to the block index address, and determine whether there is a contiguous credential matching the predicted credential in the target block;

If it exists, update the risk value of the contact object.
The method of claim 1, further comprising:

In response to an on-chain transaction request including a close-contact credential, obtain the close-contact credential and store the close-contact credential in the blockchain, wherein the close-contact credential is when a close-contact event is detected, using the public keys of the users on both sides of the close-contact certificate. , and obtains by encrypting the close connection information of the two users of the close connection;

Update the risk value of the users on both sides of the close contact.
The method according to claim 4, characterized in that after storing the secret credential in the blockchain, the method further comprises:

Acquiring the block index address that stores the secret certificate, and feeding back the block index address to the client that sent the on-chain transaction request.
The method of claim 1, further comprising:

In response to the first account encryption request, using the public key of the first account to encrypt the preset data to obtain an encryption result;

Feeding back the encryption result to the client that sent the first account encryption request, to instruct the client to feed back the verification result after verifying the first account according to the encryption result;

If the received verification result is passed, the risk value of the first account is used as the risk value of the current login account of the client.
The method according to claim 6, wherein after using the risk value of the first account as the risk value of the current login account of the user terminal, the method further comprises:

The concatenated data of the first account is used as the concatenated data of the current account.
The method according to any one of claims 1-7, wherein the server is determined from at least two candidate servers based on a Byzantine consensus mechanism.
A blockchain-based data processing method, characterized in that it is executed by a client, the method comprising:

In response to the contact data acquisition request of the risk user sent by the server, acquire the contact data of the risk user; wherein, the contact data acquisition request is generated after the server responds to the risk event processing request; feedback the contact data of the risk user to the server to instruct the server to update the risk value of the risk user's contact object according to the risk user's contact data and the risk user's secret certificate stored in the blockchain network.
The method of claim 9, further comprising:

If a close contact event is detected, obtain the close contact information of the close contact event;

Using the public keys of the users of both sides of the close connection to encrypt the close connection information to obtain the close connection certificate;

Generating an on-chain transaction request including the secret credential and sending it to the server to instruct the server to store the secret credential on the chain, and to update the risk value of the users on both sides of the secret.
The method according to claim 10, characterized in that after generating and sending the on-chain transaction request including the close credential to the server, the method further comprises:

Obtain the block index address that stores the secret credential fed back by the server;

The concatenation information and the block index address are stored locally as concatenated data.
The method according to claim 10, wherein if a close contact event is detected, acquiring the close contact information of the close contact event, comprising:

If a close contact event is detected, and the close contact event is not a repeated close contact event, then the contact information of the close contact event is acquired.
The method of claim 9, further comprising:

In response to the account registration request triggered by the user, the account information of the user is generated, wherein the account information includes: the public key, the private key, the account address and the initial risk value of the account.
The method of claim 9, further comprising:

In response to the account recovery request triggered by the user, a first account encryption request is generated and sent to the server to instruct the server to encrypt the preset data with the public key of the first account, and feed back the encryption result;

Use the private key of the first account to verify the encryption result fed back by the service, and feed back the verification result to the server to instruct the server to perform an account data recovery operation based on the verification result.
A data processing device based on blockchain, the device comprises: a first response module, a data request module for close connection and a risk value update module; wherein,

the first response module, configured to determine a risk user and modify the risk value of the risk user in response to a risk event processing request;

The contact data request module is configured to send the contact data acquisition request of the risk user to the user terminal of the risk user, so as to instruct the user terminal to feed back the contact data of the risk user;

The risk value updating module is configured to update the risk value of the risk user's contact object according to the obtained contact data of the risk user and the contact certificate of the risk user stored in the blockchain network.
A data processing device based on blockchain, the device comprises: a second response module and a feedback module; wherein,

The second response module is configured to obtain the contact data of the risk user in response to the contact data acquisition request of the risk user sent by the server; wherein, the contact data acquisition request is generated after the server responds to the risk event processing request;

The feedback module is configured to feed back the secret data of the risk user to the server, so as to instruct the server to instruct the server according to the secret data of the risk user and the secret certificate of the risk user stored in the blockchain network , and update the risk value of the close contact object of the risk user.
An electronic device, characterized in that the electronics include:

one or more processors;

storage means for storing one or more programs,

When executed by the one or more processors, the one or more programs cause the one or more processors to implement the blockchain-based blockchain of any one of claims 1-8 or 9-14 data processing method.
A computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, implements the blockchain-based data processing method according to any one of claims 1-8 or 9-14.