CN115168489B

CN115168489B - Data certification method and device based on blockchain

Info

Publication number: CN115168489B
Application number: CN202210749817.3A
Authority: CN
Inventors: 王家恒; 王炎; 乐煜炜
Original assignee: Hangzhou Tidu Technology Co ltd
Current assignee: Hangzhou Tidu Technology Co ltd
Priority date: 2022-06-28
Filing date: 2022-06-28
Publication date: 2024-03-22
Anticipated expiration: 2042-06-28
Also published as: CN115168489A

Abstract

One or more embodiments of the present disclosure provide a blockchain-based data logging method and apparatus, which are applied to a data processing platform accessing a blockchain; the method comprises the following steps: acquiring a data abstract corresponding to the source data sent by the terminal equipment, and determining whether the source data comprises a source data fragment corresponding to an abnormal event or not based on the data abstract; if so, generating an abnormal report message comprising a device identifier corresponding to the terminal device associated with the abnormal event and event information corresponding to the abnormal event, and issuing the abnormal report message to the blockchain; invoking an intelligent contract to generate a source data retrieval request including device identification and event information on the blockchain; transmitting a source data acquisition request acquired from the blockchain to terminal equipment corresponding to the equipment identifier, so that the terminal equipment extracts a source data fragment corresponding to the abnormal event based on the event information and returns the source data fragment to the data processing platform; the smart contract is invoked to document the source data segment on the blockchain.

Description

Data certification method and device based on blockchain

Technical Field

One or more embodiments of the present disclosure relate to the field of blockchain technologies, and in particular, to a blockchain-based data certification method and apparatus.

Background

Data up-link certification has become an important application mode of blockchains because it is often difficult to tamper with and traceable to certify data on blockchains. Blockchains typically rely on a distributed network, where each node in the blockchain needs to store identical copies of data to maintain data consistency between different nodes. Today, the amount of data that needs to be ul-authenticated becomes increasingly large. However, it is often difficult to ensure that there is sufficient storage space on a single node. In addition, even if there is sufficient memory space on a single node, a significant amount of time is required between different nodes to synchronize data.

Disclosure of Invention

One or more embodiments of the present disclosure provide the following technical solutions:

the specification provides a blockchain-based data certification method, which is applied to a data processing platform accessed to a blockchain; wherein, the block chain is provided with an intelligent contract for processing data; the method comprises the following steps:

receiving a data abstract corresponding to the acquired source data sent by the terminal equipment, and determining whether the source data comprises a source data fragment corresponding to an abnormal event or not based on the data abstract;

If yes, generating abnormal report information, and releasing the abnormal report information to the block chain; the abnormal report information comprises equipment identifiers corresponding to the terminal equipment associated with the abnormal event and event information corresponding to the abnormal event;

invoking source data acquisition logic in the intelligent contract, and generating a source data acquisition request on the blockchain; wherein the source data acquisition request includes the device identification and the event information;

acquiring the source data acquisition request from the blockchain, sending the source data acquisition request to terminal equipment corresponding to the equipment identifier, so that the terminal equipment extracts source data fragments corresponding to the abnormal event from the acquired source data based on the event information, and sends the extracted source data fragments to the data processing platform;

and calling a source data certification logic in the intelligent contract, and certifying the extracted source data fragments on the blockchain.

The specification also provides a data certification method based on the blockchain, which is applied to the terminal equipment; wherein, the block chain is provided with an intelligent contract for processing data; the method comprises the following steps:

Collecting source data and generating a data abstract corresponding to the source data;

transmitting the data digest to a data processing platform accessing the blockchain, so that when the data processing platform determines that the source data comprises source data fragments corresponding to an abnormal event based on the data digest, generating an equipment identifier corresponding to a terminal equipment associated with the abnormal event and abnormal report information of event information corresponding to the abnormal event, and issuing the abnormal report information to the blockchain to call source data acquisition logic in the intelligent contract, and generating a source data acquisition request comprising the equipment identifier and the event information on the blockchain;

receiving the source data acquisition request acquired and sent by the data processing platform from the blockchain;

and extracting source data fragments corresponding to the abnormal event from the source data based on the event information, and sending the extracted source data fragments to the data processing platform so that the data processing platform calls source data certification logic in the intelligent contract, and certifying the extracted source data fragments on the blockchain.

The specification also provides a blockchain-based data certification device which is applied to a data processing platform accessed to the blockchain; wherein, the block chain is provided with an intelligent contract for processing data; the device comprises:

the receiving module is used for receiving a data abstract corresponding to the acquired source data sent by the terminal equipment and determining whether the source data comprises a source data fragment corresponding to an abnormal event or not based on the data abstract;

the first generation module is used for generating abnormal report information and issuing the abnormal report information to the block chain if the abnormal report information is generated; the abnormal report information comprises equipment identifiers corresponding to the terminal equipment associated with the abnormal event and event information corresponding to the abnormal event;

the second generation module is used for calling source data acquisition logic in the intelligent contract and generating a source data acquisition request on the blockchain; wherein the source data acquisition request includes the device identification and the event information;

the acquisition module is used for acquiring the source data acquisition request from the blockchain, sending the source data acquisition request to the terminal equipment corresponding to the equipment identifier, so that the terminal equipment extracts a source data fragment corresponding to the abnormal event from the acquired source data based on the event information, and sending the extracted source data fragment to the data processing platform;

And the certification module is used for calling the source data certification logic in the intelligent contract and certifying the extracted source data fragments on the blockchain.

The specification also provides a data certification device based on the blockchain, which is applied to the terminal equipment; wherein, the block chain is provided with an intelligent contract for processing data; the device comprises:

the generation module is used for collecting source data and generating a data abstract corresponding to the source data;

the sending module is used for sending the data abstract to a data processing platform accessing the blockchain, so that when the data processing platform determines that the source data comprises source data fragments corresponding to an abnormal event based on the data abstract, generating an equipment identifier corresponding to a terminal equipment associated with the abnormal event and abnormal report information of event information corresponding to the abnormal event, and issuing the abnormal report information to the blockchain to call source data acquisition logic in the intelligent contract, and generating a source data acquisition request comprising the equipment identifier and the event information on the blockchain;

The receiving module is used for receiving the source data acquisition request acquired and sent by the data processing platform from the blockchain;

and the certification module is used for extracting source data fragments corresponding to the abnormal event from the source data based on the event information, and sending the extracted source data fragments to the data processing platform so that the data processing platform calls source data certification logic in the intelligent contract, and certifies the extracted source data fragments on the blockchain.

The present specification also provides an electronic apparatus including:

a processor;

a memory for storing processor-executable instructions;

wherein the processor implements the steps of the method as described in any of the preceding claims by executing the executable instructions.

The present specification also provides a computer readable storage medium having stored thereon computer instructions which when executed by a processor perform the steps of the method as claimed in any one of the preceding claims.

In the above technical solution, the data processing platform accessing to the blockchain may generate, when it is determined that the source data includes a source data fragment corresponding to an abnormal event based on a data digest corresponding to source data acquired by a terminal device, an equipment identifier corresponding to the terminal device associated with the abnormal event and exception reporting information of event information corresponding to the abnormal event, and issue the exception reporting information to the blockchain, so as to further invoke source data acquisition logic in an intelligent contract, and generate a source data acquisition request including the equipment identifier and the event information; subsequently, the data processing platform can send the source data acquisition request acquired from the blockchain to the terminal equipment corresponding to the equipment identifier, the terminal equipment extracts the source data fragment corresponding to the abnormal event from the source data based on the event information, the extracted source data fragment is sent to the data processing platform, and the data processing platform invokes the source data certification logic in the intelligent contract to perform uplink certification.

By adopting the mode, on one hand, the data processing platform only triggers the uplink evidence of the source data acquired by the terminal equipment under the condition that the source data comprises the source data fragment corresponding to the abnormal event based on the data abstract corresponding to the source data acquired by the terminal equipment, so that the uplink evidence of the source data under the condition that the abnormal event does not occur can be avoided, and the data quantity of the uplink evidence-bearing source data is reduced; on the other hand, because the terminal equipment can respond to the source data acquisition request, the source data fragments corresponding to the abnormal events are extracted from the acquired source data based on the event information corresponding to the abnormal events, and only the source data fragments are subjected to the uplink certification, the source data fragments of the uplink certification can be ensured to be all effective data related to the abnormal events, and the data quantity of the source data of the uplink certification is reduced.

Drawings

FIG. 1 is a schematic diagram of a blockchain-related network environment in accordance with an exemplary embodiment of the present description.

FIG. 2 is a flow chart illustrating a blockchain-based data certification method in accordance with an exemplary embodiment of the present disclosure.

FIG. 3 is a schematic diagram of another blockchain-based data certification method in accordance with an exemplary embodiment of the present disclosure.

Fig. 4 is a hardware configuration diagram of an electronic device in which a blockchain-based data storage device is located according to an exemplary embodiment of the present disclosure.

Fig. 5 is a block diagram of a blockchain-based data certification device in accordance with an exemplary embodiment of the present disclosure.

FIG. 6 is a block diagram of another blockchain-based data certification device as shown in an exemplary embodiment of the present specification.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of the present specification. Rather, they are merely examples of apparatus and methods consistent with aspects of one or more embodiments of the present description as detailed in the accompanying claims.

It should be noted that: in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, the method may include more or fewer steps than described in this specification. Furthermore, individual steps described in this specification, in other embodiments, may be described as being split into multiple steps; while various steps described in this specification may be combined into a single step in other embodiments.

Blockchains are generally divided into three types: public (Public Blockchain), private (Private Blockchain) and federated (Consortium Blockchain) chains. In addition, there may be various types of combinations as described above, such as a combination of a private chain and a federation chain, a combination of a federation chain and a public chain, and so on.

Among the three types of blockchains described above, the most decentralized is the public chain. Participants joining the public chain (which may also be referred to as nodes in the blockchain) may read data records on the chain, participate in transactions, compete for billing rights for new blocks, and so forth. Moreover, each node can freely join or leave the network and perform relevant operations.

The private chain is the opposite, the write rights of the network are controlled by some organization or organization, and the data read rights are specified by the organization. That is, the private chain may be considered as a weakly centralized system with strict restrictions on nodes and a small number of nodes. This type of blockchain is more suitable for use within a particular organization.

The alliance chain is between the public chain and the private chain, so that the 'partial decentralization' can be realized. Each node in the federation chain typically has an entity authority or organization corresponding thereto; nodes join the network by authorization and form a benefit-related federation, which collectively maintains the operation of the blockchain.

In a blockchain network, nodes are logically communicating entities; multiple blockchain nodes of different types may run on the same physical server or on different physical servers.

For data generated outside the blockchain, it may be structured into a standard transaction (transaction) format supported by the blockchain and then published to the blockchain, which transaction is consensus by all nodes in the blockchain network. After consensus is reached, the transaction may be persisted in the blockchain by a node in the blockchain network that acts as an accounting node.

In practical applications, either public, private or federated, the functionality of smart contracts (smart contracts) may be provided. Intelligent contracts on a blockchain are contracts on a blockchain that can be executed by a transaction trigger. The smart contracts may be defined in the form of codes.

The intelligent contracts may be executed independently by nodes in the blockchain network in a prescribed manner, and all execution records and related data may be saved on the blockchain. Taking a blockchain based on an account model as an example, a smart contract deployed on the blockchain is a type of blockchain account, after executing a particular smart contract, execution records and related data may be saved in the account storage space (typically a storage field) of the smart contract.

The event mechanism of an intelligent contract is one way in which the intelligent contract interacts with an off-chain entity. For intelligent contracts deployed on blockchains, it is often not possible to interact directly with off-chain entities; for example, the intelligent contract typically cannot send the results of the invocation of the intelligent contract to the invocation initiator of the intelligent contract point-to-point, approximately after the invocation is completed.

The calling results (including intermediate results and final calling results) generated during the calling process of the intelligent contract are generally recorded in the form of events (event) into a transaction log (transactions) of the transaction calling the intelligent contract, and are stored in a storage space of the blockchain node. And an off-chain entity which needs to interact with the intelligent contract can acquire the calling result of the intelligent contract by monitoring the transaction log stored in the storage space of the blockchain node.

When the data volume of the data requiring the uplink certification is large, if there is not enough storage space on a single blockchain node, the data uplink certification is highly likely to fail. In addition, even if there is sufficient memory space on a single blockchain node, a significant amount of time is spent between different blockchain nodes for data synchronization.

In order to reduce the data volume of the data of the uplink evidence, the specification provides a technical scheme of the data evidence based on the blockchain.

In a specific implementation, the terminal device may collect source data in real time and generate a data summary corresponding to the collected source data. Subsequently, the terminal device may send the generated data summary to the data processing platform, so as to trigger data storage for the source data.

The data processing platform may determine, in response to the data digest, whether the source data includes a source data fragment corresponding to an abnormal event based on the data digest, when receiving the data digest corresponding to the source data collected by the terminal device and sent by the terminal device.

The data processing platform may generate the exception reporting information when the source data collected by the terminal device includes a source data segment corresponding to an exception event. The exception reporting information may include a device identifier corresponding to the terminal device associated with the exception event, and event information corresponding to the exception event.

When the abnormal report information is generated, the data processing platform may call source data acquisition logic in the intelligent contract for processing data, which is deployed on the blockchain, in response to the abnormal report information, generate a source data acquisition request, and store the source data acquisition request on the blockchain.

The data processing platform may obtain the source data acquisition request from the blockchain, the source data acquisition request including a device identification and event information. Subsequently, the data processing platform may send the source data acquisition request to a terminal device corresponding to the device identifier in the source data acquisition request.

When the terminal device receives the source data acquisition request, the terminal device may extract, from the acquired source data, a source data fragment corresponding to the abnormal event based on event information corresponding to the abnormal event in the source data acquisition request in response to the source data acquisition request. Subsequently, the terminal device may send the extracted source data segment to the data processing platform.

When the data processing platform receives the source data segment corresponding to the abnormal event sent by the terminal device, the source data segment can be responded, and source data certification logic in the intelligent contract for processing data, which is deployed on the blockchain, is called to certify the source data segment on the blockchain.

The following describes the technical scheme of the present description in detail.

Referring to fig. 1, fig. 1 is a schematic diagram illustrating a network environment related to a blockchain according to an exemplary embodiment of the present disclosure.

In a network environment as shown in fig. 1, a client-side computing device 101, a server-side 102, and at least one blockchain system may be included; such as blockchain system 103, blockchain system 104, and blockchain system 105.

In one implementation shown, client-side computing device 101 may include a variety of different types of client-side computing devices; for example, client-side computing devices may include devices such as PC computing devices, mobile computing devices, internet of things devices, and other forms of smart devices with some computing capabilities, and so forth.

It should be noted that, the client-side computing device 101 does not represent that all the client-side computing devices thereof are in the same communication network, but is merely a generic term for these client-side computing devices.

In one implementation shown, some of the client-side computing devices 101 may be coupled to the server-side 102 through various communication networks; for example, device 3 is coupled to server side 102.

Some of the client-side computing devices 101 may be coupled directly to the blockchain system without being coupled to the server 102; for example, the device 4 may be directly coupled to the blockchain system 103.

In one implementation shown, the client-side computing device 101 may also include one or more user-side servers; such as device 5 and device 6. Some of the client-side computing devices 101 may be coupled to the user-side server; for example, device 1 is coupled to device 5 and device 2 is coupled to device 6. The client side server may be further coupled directly to the blockchain system or may be further coupled to the server side 102 through various communication networks; for example, device 5 may be further coupled directly to a blockchain system, and device 6 is further coupled to server side 102.

In one embodiment, the user side server may be implemented by a service entity that builds a user account system; the service entity may comprise an operator entity providing various online and/or offline services to the user. Correspondingly, the operation entity can comprise an operator corresponding to the service carrier; for example, the operating entity may include individuals, organizations, companies and enterprises, etc. that operate and manage the service carrier.

In one embodiment shown, server side 102 may also be coupled to one or more blockchain systems through various communication networks; for example, server side 102 is coupled to blockchain system 103, blockchain system 104, and blockchain system 105, respectively, and so on.

In one embodiment shown, the communication network may include a wired and/or wireless communication network; for example, a local area network (Local Area Network, LAN), wide area network (Wide Area Network, WAN), the internet, or a combination thereof, implemented based on an operator-provided wired or wireless access network, such as a mobile cellular network.

In one embodiment shown, each blockchain system may maintain one or more blockchains (e.g., public blockchains, private blockchains, federated blockchains, etc.) and include a plurality of blockchain nodes for carrying the one or more blockchains; for example, blockchain node 1, blockchain node 2, blockchain node 3, blockchain node 4, blockchain node i, and the like, as shown in fig. 1, may collectively carry one or more blockchains. Inter-chain data access may also be performed between blockchains included in each blockchain system, as well as between blockchain systems.

In one embodiment shown, the blockchain node may be a physical device or a virtual device implemented in a server or server cluster; for example, the blockchain node may be a physical host in the server cluster, or may be a virtual machine created by virtualizing a hardware resource mounted on the server or the server cluster based on a virtualization technology. Each blockchain node may be coupled together to form a network by various types of communication methods (e.g., TCP/IP, etc.) to carry one or more blockchains.

In one embodiment shown, the server side 102 may include a BaaS platform (also referred to as BaaS cloud) for providing blockchain services (BaaS, blockchain as a Service).

The BaaS platform may provide blockchain services to client-side computing devices coupled to the BaaS platform by providing pre-written software for activities occurring on the blockchain, such as subscription and notification, user authentication, database management, and remote updates.

For example, the BaaS platform may provide software such as MQ (Message Queue) services; the client side computing device coupled with the BaaS platform can subscribe to an intelligent contract deployed on a certain blockchain in a blockchain system coupled with the BaaS platform, and a contract event generated on the blockchain after triggering execution; the BaaS platform can monitor events generated on the blockchain after triggering and executing the intelligent contract, and then adds the contract events to the message queue in the form of notification messages based on software related to the MQ service, so that the client side computing equipment subscribing to the message queue can obtain notifications related to the contract events.

Referring to fig. 2, fig. 2 is a flowchart illustrating a blockchain-based data certification method according to an exemplary embodiment of the present disclosure.

In this embodiment, the above-mentioned data logging method based on blockchain may be applied to a data processing platform accessing blockchain.

The blockchain may have a smart contract deployed thereon for processing data.

For the data processing platform, the data processing platform can be a centralized platform outside the blockchain, is coupled to the blockchain node through various communication networks, and interacts with the blockchain node to enable the blockchain node to call an intelligent contract deployed on the blockchain to realize data storage. Alternatively, the data processing platform may include a centralized platform outside of the blockchain described above, as well as blockchain nodes; the centralized platform and the blockchain node can interact, so that the blockchain node can call an intelligent contract deployed on the blockchain to realize data storage.

It should be noted that, the centralized platform and the blockchain node may be implemented by software, or may be implemented by hardware or a combination of hardware and software. In this case, the centralized platform and the blockchain node may be deployed on different devices or on the same device.

In connection with the network environment as shown in FIG. 1, the data processing platform described above may be deployed on server side 102; alternatively, the data processing platform may include a server side 102 and an entirety of block link points in a block chain system 103; this description is not limiting.

As shown in fig. 2, the above-mentioned blockchain-based data certification method may include the following steps:

step 201: and receiving a data abstract corresponding to the acquired source data sent by the terminal equipment, and determining whether the source data comprises source data fragments corresponding to the abnormal event or not based on the data abstract.

In practical application, the terminal device may be an intelligent terminal device such as a smart phone, a tablet computer, a notebook computer, a wearable device, a vehicle-mounted intelligent terminal, and an intelligent home device.

The above-mentioned terminal devices are generally equipped with sensors, for example: temperature sensor, acceleration sensor, gyroscope, barometer, etc., the sensor can gather sensing data in real time or periodically, and upload the sensing data that gathers to terminal equipment's CPU (Central Processing Unit ) to the sensing data that gathers of sensor by terminal equipment record.

Or, the CPU of the terminal device may collect hardware operation data such as a CPU operation speed, a memory read-write speed, and software log data generated in an Application (APP) deployed on the terminal device during an operation process, and store the collected hardware operation data and software log data.

In practical applications, the data such as the sensing data, the hardware operation data, or the software log data may be regarded as source data collected by the terminal device. And, the source data collected by the terminal device can be stored, so that the stored source data can be used for corresponding business processing, for example: data tracing, anomaly detection, fault repair and the like.

In this embodiment, the terminal device may collect source data in real time and generate a data summary corresponding to the collected source data.

In order to reduce the data amount of the source data corresponding to the generated data digest, so as to facilitate data processing on the data digest, the terminal device may periodically generate the data digest corresponding to the collected source data according to a preset time period, where the data digest may include the data digest corresponding to the source data collected in one time period. For example, assuming that the time period is 5 minutes, the terminal device starts to collect source data from 19:00, the terminal device may generate a data digest corresponding to source data collected in the 5 minutes 19:00 to 19:05, and generate a data digest corresponding to source data collected in the 5 minutes 19:05 to 19:10, and so on.

In this embodiment, in the case that a data digest corresponding to the collected source data is generated, the terminal device may send the generated data digest to the data processing platform, so as to trigger a ul credit of the source data collected by the terminal device.

In order to reduce the number of data transmissions with the data processing platform, the terminal device may periodically send the generated data summary to the data processing platform according to a preset time period, where the sent data summary may include the data summary generated in one time period.

In this embodiment, when receiving the data digest corresponding to the source data collected by the terminal device and sent by the terminal device, the data processing platform may determine, based on the data digest, whether the source data includes a source data segment corresponding to an abnormal event in response to the data digest.

In practical applications, the abnormal event may include an abnormal event that occurs in the running process of software deployed on the terminal device or hardware carried on the terminal device, for example: the CPU temperature of the terminal device is too high, the memory read-write speed of the terminal device is too low, the APP operation on the terminal device collapses, the communication between the terminal device and other terminal devices is interrupted, and the like, which can be specifically set according to actual requirements, and the specification is not limited.

For the data abstract corresponding to the source data, the data processing platform can determine the specific content of the source data by carrying out data analysis on the data abstract. In this case, the data processing platform may determine, based on the data summary, whether the source data includes a source data fragment corresponding to an abnormal event, that is, determine, by performing data analysis on the data summary, specific content of the source data, and then determine, according to the specific content of the source data, whether the source data includes a source data fragment corresponding to an abnormal event.

In the illustrated embodiment, in determining whether the source data includes a source data segment corresponding to an abnormal event, it may be specifically determined whether the source data includes a source data segment corresponding to an abnormal event that has occurred, and/or whether the source data includes a source data segment corresponding to an occurrence trend of an abnormal event.

In practical application, a corresponding abnormal event detection rule may be set for each abnormal event that may occur according to the actual requirement, so as to detect the abnormal event on the source data based on the abnormal event detection rule, and determine whether the source data includes a source data segment corresponding to the abnormal event.

For example, the abnormal event detection rule set for the CPU temperature of the terminal device to be too high may include: when the CPU temperature in the source data is detected to always exceed the safety threshold value within a period of time, determining that the abnormal event occurs, wherein the source data fragment in the period of time is the source data fragment corresponding to the abnormal event in the source data; when the CPU temperature in the source data is detected to be gradually increased within a period of time and the difference value between the CPU temperature and the safety threshold value is smaller, determining that the trend of the abnormal event occurs, wherein the source data fragment in the period of time is the source data fragment corresponding to the occurrence trend of the abnormal event in the source data.

For another example, the exception event detection rules set for APP running crashes on the terminal device may include: when detecting that related content restarted after the error reporting of the APP exists in the source data, determining that the abnormal event occurs, wherein the source data fragment restarted after the error reporting of the APP is the source data fragment corresponding to the occurred abnormal event in the source data; when the related content that the APP reports errors for many times and is not restarted is detected in the source data, and the times reach a restarting threshold value, determining that the trend of the abnormal event occurs, wherein the source data fragments which represent that the APP reports errors for many times and are not restarted are the source data fragments corresponding to the occurrence trend of the abnormal event in the source data.

It should be noted that, in the case where the data processing platform is a centralized platform outside the blockchain, the step 201 may be performed by the data processing platform. In the case where the data processing platform includes a centralized platform outside of the blockchain, and blockchain nodes, the step 201 may be performed by the centralized platform in the data processing platform.

Step 202: if yes, generating abnormal report information, and releasing the abnormal report information to the block chain; the exception reporting information comprises equipment identifiers corresponding to the terminal equipment associated with the exception event and event information corresponding to the exception event.

In this embodiment, the data processing platform may generate the exception reporting information and issue the exception reporting information to the blockchain when it is determined that the source data collected by the terminal device includes a source data segment corresponding to an exception event.

The exception reporting information may include a device identifier corresponding to the terminal device associated with the exception event, and event information corresponding to the exception event. The device identification may be used to specify the terminal device and the event information may be used to specify the source data fragment collected by the terminal device.

That is, the terminal device may extract a source data fragment corresponding to an abnormal event from the acquired source data based on event information corresponding to the abnormal event.

In the illustrated embodiment, since the event information is used to specify the source data segments collected by the terminal device, in order to facilitate the terminal device to extract the source data segments corresponding to the abnormal event from the collected source data based on the event information corresponding to the abnormal event, the event information may specifically include information such as an event type and/or an event occurrence range. In this case, the terminal device may extract, from the collected source data, source data belonging to the event type within the event occurrence range, which source data constitute a source data fragment corresponding to the abnormal event, according to the event type and/or the event occurrence range.

Further, in one embodiment shown, the event occurrence ranges may specifically include a temporal range and/or a spatial range of occurrence of the event. In addition, the event occurrence range may also include a range in other dimensions of event occurrence, and may specifically be set according to actual requirements, which is not limited in this specification.

In practical application, there may be a plurality of terminal devices associated with one abnormal event, or there may be only one terminal device. For example, the terminal device associated with the abnormal event of the communication interruption between the terminal device a and the terminal device B may include the terminal device a and the terminal device B. For another example, only the terminal device a is associated with an abnormal event in which the CPU temperature of the terminal device a is too high.

In the case that the source data collected by the terminal device includes a source data segment corresponding to an abnormal event, the data processing platform may further determine, on the one hand, a terminal device associated with the abnormal event and determine a device identifier corresponding to the associated terminal device, and on the other hand, may further determine event information corresponding to the abnormal event, so that the abnormal report information may be generated based on the device identifier corresponding to the terminal device associated with the abnormal event and the event information corresponding to the abnormal event.

It should be noted that, in the case that the data processing platform is a centralized platform outside the blockchain, the step 202 may be performed by the data processing platform. In the case where the data processing platform includes a centralized platform outside of the blockchain, and blockchain nodes, the step 202 may be performed by the centralized platform in the data processing platform.

Step 203: invoking source data acquisition logic in the intelligent contract, and generating a source data acquisition request on the blockchain; wherein the source data acquisition request includes the device identification and the event information.

In this embodiment, when the exception report information is generated, the data processing platform may invoke source data acquisition logic in the intelligent contract for processing data, which is deployed on the blockchain, to generate a source data acquisition request on the blockchain in response to the exception report information.

Wherein, since the exception reporting information includes a device identifier corresponding to the terminal device associated with the exception event and event information corresponding to the exception event, the source data acquisition request may include the device identifier and the event information, accordingly.

In the illustrated embodiment, in order to further reduce the data amount of the data of the uplink ticket, for one abnormal event associated with a plurality of terminal devices, only a source data segment corresponding to the abnormal event acquired by one terminal device associated with the abnormal event may be uplink ticket.

The one terminal device may be any one of the plurality of terminal devices associated with the abnormal event, or may be a main terminal device of the plurality of terminal devices associated with the abnormal event. Taking an abnormal event of communication interruption between the terminal equipment A and the terminal equipment B as an example, only the source data fragments corresponding to the abnormal event collected by the terminal equipment A can be subjected to uplink evidence storage, or only the source data fragments corresponding to the abnormal event collected by the terminal equipment B can be subjected to uplink evidence storage; or, assuming that the abnormal event is caused by the network card failure of the terminal device a, the terminal device a may be regarded as a main terminal device, and only the source data segment corresponding to the abnormal event collected by the terminal device a is logged and verified.

Specifically, the exception reporting information may include device identifiers respectively corresponding to at least one terminal device associated with the exception event, and event information corresponding to the exception event. In this case, the above-described source data acquisition request may include the event information and the device identification corresponding to any one of the at least one terminal device (may be referred to as a target terminal device).

In addition, in the case that the data processing platform is a centralized platform outside the blockchain, the data processing platform may construct a transaction supported by the blockchain for invoking an intelligent contract based on the exception reporting information, and send the transaction to a blockchain node, so that the blockchain node may invoke source data acquisition logic in the intelligent contract in response to the transaction to generate a source data acquisition request on the blockchain.

In the case that the data processing platform includes a centralized platform outside the blockchain and a blockchain node, the centralized platform may construct a transaction supported by the blockchain for invoking an intelligent contract based on the exception reporting information, and forward the transaction to the blockchain node in the data processing platform, so that the blockchain node may invoke source data acquisition logic in the intelligent contract to generate a source data acquisition request on the blockchain in response to the transaction.

The source data acquisition request may be used as a calling result generated in the calling process of the intelligent contract, recorded in a transaction log of the transaction calling the intelligent contract in the form of an event, and stored in a storage space of the blockchain node.

Step 204: and acquiring the source data acquisition request from the blockchain, sending the source data acquisition request to terminal equipment corresponding to the equipment identifier, so that the terminal equipment extracts source data fragments corresponding to the abnormal event from the acquired source data based on the event information, and sending the extracted source data fragments to the data processing platform.

In this embodiment, since the source data acquisition request is authenticated on the blockchain, the data processing platform may acquire the source data acquisition request from the blockchain, where the source data acquisition request includes a device identifier and event information. Subsequently, the data processing platform may send the source data acquisition request to a terminal device corresponding to the device identifier in the source data acquisition request.

It should be noted that, when the data processing platform is a centralized platform outside the blockchain, according to the event mechanism of the intelligent contract, the data processing platform may acquire the call result of the intelligent contract by monitoring the transaction log stored in the storage space of the blockchain node, acquire the source data acquisition request from the blockchain, and send the source data acquisition request to the corresponding terminal device.

In the case that the data processing platform includes the centralized platform outside the blockchain and the blockchain node, according to the event mechanism of the intelligent contract, the centralized platform in the data processing platform may acquire the call result of the intelligent contract by monitoring the transaction log stored in the storage space of the blockchain node, acquire the source data acquisition request from the blockchain, and send the source data acquisition request to the corresponding terminal device.

In this embodiment, when the terminal device receives the source data acquisition request, the terminal device may extract, in response to the source data acquisition request, a source data fragment from the acquired source data based on event information in the source data acquisition request. Because the event information is the event information corresponding to the abnormal event, the extracted source data segment is the source data segment corresponding to the abnormal event. Subsequently, the terminal device may send the extracted source data segment to the data processing platform.

In the illustrated embodiment, in the case where the source data acquisition request includes the device identifier corresponding to the target terminal device and the event information, the data processing platform may send the source data acquisition request to the target terminal device, extract, by the target terminal device, a source data fragment from the acquired source data based on the event information in the source data acquisition request, and send the extracted source data fragment to the data processing platform.

Step 205: and calling a source data certification logic in the intelligent contract, and certifying the extracted source data fragments on the blockchain.

In this embodiment, when the data processing platform receives the source data segment corresponding to the abnormal event sent by the terminal device, the source data certification logic in the intelligent contract for processing data deployed on the blockchain may be called in response to the source data segment, and the source data segment is certified on the blockchain.

In the illustrated embodiment, in order to ensure the correctness of the data of the uplink certification, the data processing platform may invoke the source data certification logic in the intelligent contract, and first determine whether a source data segment corresponding to the abnormal event sent by the terminal device is matched with the abnormal reporting information for the abnormal event, that is, determine whether the source data segment is a source data segment corresponding to the abnormal event, and if yes, certify the source data segment on the blockchain.

In practical application, in order to reduce the complexity of processing such as verifying and storing source data, the data processing platform can collect, convert and package the data abstracts and source data fragments sent by different terminal devices to form structured data in a unified data format.

It should be noted that, in the case that the data processing platform is a centralized platform outside the blockchain, the data processing platform may construct a transaction supported by the blockchain for invoking an intelligent contract based on the source data fragment, and send the transaction to a blockchain node, so that the blockchain node may invoke the source data certification logic in the intelligent contract to certify the source data fragment on the blockchain in response to the transaction.

In the case that the data processing platform includes a centralized platform outside the blockchain and a blockchain node, the centralized platform may construct a transaction supported by the blockchain for invoking an intelligent contract based on the source data fragment, and forward the transaction to the blockchain node in the data processing platform, so that the blockchain node may invoke the source data certification logic in the intelligent contract to certify the source data fragment on the blockchain in response to the transaction.

Referring to fig. 3, fig. 3 is a flowchart illustrating another blockchain-based data certification method according to an exemplary embodiment of the present disclosure.

In this embodiment, the above-described blockchain-based data certification method may be applied to a terminal device.

The blockchain may have a smart contract deployed thereon for processing data.

In connection with the network environment as shown in fig. 1, the terminal device may be the device 3 or the device 6, which is not limited in this specification.

As shown in fig. 3, the above-mentioned blockchain-based data certification method may include the following steps:

step 301: and collecting source data and generating a data abstract corresponding to the source data.

Step 302: and sending the data abstract to a data processing platform connected to the blockchain, so that when the data processing platform determines that the source data comprises source data fragments corresponding to an abnormal event based on the data abstract, generating an equipment identifier corresponding to a terminal equipment associated with the abnormal event and abnormal report information of event information corresponding to the abnormal event, and issuing the abnormal report information to the blockchain to call source data acquisition logic in the intelligent contract, and generating a source data acquisition request comprising the equipment identifier and the event information on the blockchain.

Step 303: and receiving the source data acquisition request acquired and sent by the data processing platform from the blockchain.

Step 304: and extracting source data fragments corresponding to the abnormal event from the source data based on the event information, and sending the extracted source data fragments to the data processing platform so that the data processing platform calls source data certification logic in the intelligent contract, and certifying the extracted source data fragments on the blockchain.

For a specific implementation of the blockchain-based data certification method shown in fig. 3, reference may be made to the blockchain-based data certification method shown in fig. 2, which is not described herein.

It should be noted that, for the terminal device performing steps 301 to 302, if the device identifier in the source data acquisition request generated by the smart contract in step 302 is the device identifier corresponding to the terminal device, the terminal device may continue to perform steps 303 to 304; if the device identifier in the source data acquisition request generated by the smart contract in step 302 is not the device identifier corresponding to the terminal device, the terminal device does not receive the source data acquisition request, and steps 303 to 304 are not performed.

Corresponding to the foregoing embodiments of the blockchain-based data certification method, the present specification also provides embodiments of a blockchain-based data certification device.

Embodiments of blockchain-based data certification means of the present specification may be applied to electronic devices. The apparatus embodiments may be implemented by software, or may be implemented by hardware or a combination of hardware and software. Taking software implementation as an example, the device in a logic sense is formed by reading corresponding computer program instructions in a nonvolatile memory into a memory by a processor of an electronic device where the device is located for operation. In terms of hardware, as shown in fig. 4, a hardware structure diagram of an electronic device where the blockchain-based data storage device in the present disclosure is located is shown in fig. 4, and in addition to the processor, the memory, the network interface, and the nonvolatile memory shown in fig. 4, the electronic device where the device is located in the embodiment generally includes other hardware according to the actual function of the blockchain-based data storage device, which is not described herein again.

Referring to fig. 5, fig. 5 is a block diagram of a blockchain-based data storage device according to an exemplary embodiment of the present disclosure.

The above-described blockchain-based data certification device may be applied to the electronic apparatus shown in fig. 4; the electronic device may act as a data processing platform for accessing the blockchain.

Wherein, the intelligent contracts for processing data are deployed on the blockchain.

The device comprises:

a receiving module 501, configured to receive a data summary corresponding to collected source data sent by a terminal device, and determine, based on the data summary, whether the source data includes a source data segment corresponding to an abnormal event;

the first generation module 502 is configured to generate exception reporting information and issue the exception reporting information to the blockchain if the exception reporting information is generated; the abnormal report information comprises equipment identifiers corresponding to the terminal equipment associated with the abnormal event and event information corresponding to the abnormal event;

a second generating module 503, configured to invoke source data acquisition logic in the smart contract to generate a source data acquisition request on the blockchain; wherein the source data acquisition request includes the device identification and the event information;

An obtaining module 504, configured to obtain the source data obtaining request from the blockchain, send the source data obtaining request to a terminal device corresponding to the device identifier, so that the terminal device extracts a source data segment corresponding to the abnormal event from the collected source data based on the event information, and send the extracted source data segment to the data processing platform;

and the certification module 505 is configured to invoke source data certification logic in the intelligent contract to certify the extracted source data fragment on the blockchain.

Optionally, the receiving module 501 is specifically configured to:

determining whether the source data includes a source data fragment corresponding to an abnormal event that has occurred; and/or the number of the groups of groups,

and determining whether the source data comprises source data fragments corresponding to the occurrence trend of the abnormal event.

Optionally, the exception reporting information includes device identifiers respectively corresponding to at least one terminal device associated with the exception event and event information corresponding to the exception event; the source data acquisition request comprises an equipment identifier corresponding to any target terminal equipment in the at least one terminal equipment and the event information;

The obtaining module 504 is specifically configured to:

and sending the source data acquisition request to the target terminal equipment so that the target terminal equipment extracts source data fragments corresponding to the abnormal event from the acquired source data based on the event information, and sending the extracted source data fragments to the data processing platform.

Optionally, the certification module 505 is specifically configured to:

invoking source data certification logic in the intelligent contract, and determining whether the extracted source data fragment is matched with the abnormal reporting information;

if so, the source data segment is stored on the blockchain.

Optionally, the event information includes an event type and/or an event occurrence range.

Optionally, the event occurrence range includes a time range and/or a spatial range of event occurrence.

Referring to fig. 6, fig. 6 is a block diagram of a blockchain-based data storage device according to an exemplary embodiment of the present disclosure.

The above-described blockchain-based data certification device may be applied to the electronic apparatus shown in fig. 4; the electronic device may be a terminal device.

The device comprises:

a generating module 601, configured to collect source data and generate a data summary corresponding to the source data;

a sending module 602, configured to send the data digest to a data processing platform accessing the blockchain, so that when the data processing platform determines, based on the data digest, that the source data includes a source data fragment corresponding to an abnormal event, generate an exception report information including a device identifier corresponding to a terminal device associated with the abnormal event and event information corresponding to the abnormal event, and issue the exception report information to the blockchain to invoke source data acquisition logic in the intelligent contract, and generate a source data acquisition request including the device identifier and the event information on the blockchain;

a receiving module 603, configured to receive the source data acquisition request acquired and sent by the data processing platform from the blockchain;

and the certification module 604 is configured to extract a source data segment corresponding to the abnormal event from the source data based on the event information, and send the extracted source data segment to the data processing platform, so that the data processing platform invokes source data certification logic in the intelligent contract, and certifies the extracted source data segment on the blockchain.

For the device embodiments, reference is made to the description of the method embodiments for the relevant points, since they essentially correspond to the method embodiments.

The apparatus embodiments described above are merely illustrative, wherein the modules illustrated as separate components may or may not be physically separate, and the components shown as modules may or may not be physical, i.e., may be located in one place, or may be distributed over a plurality of network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the technical scheme of the specification.

The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. A typical implementation device is a computer, which may be in the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or a combination of any of these devices.

In a typical configuration, a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, read only compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage, quantum memory, graphene-based storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by the computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.

The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

The terminology used in the one or more embodiments of the specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of the specification. As used in this specification, one or more embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in one or more embodiments of the present description to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of one or more embodiments of the present description. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.

The foregoing description of the preferred embodiment(s) is (are) merely intended to illustrate the embodiment(s) of the present invention, and it is not intended to limit the embodiment(s) of the present invention to the particular embodiment(s) described.

Claims

1. A blockchain-based data certification method applied to a data processing platform accessing the blockchain; wherein, the block chain is provided with an intelligent contract for processing data; the method comprises the following steps:

if yes, generating abnormal report information, and releasing the abnormal report information to the block chain; the abnormal report information comprises equipment identifiers respectively corresponding to at least one terminal equipment associated with the abnormal event and event information corresponding to the abnormal event; the event information is used for describing the attribute of the abnormal event;

Invoking source data acquisition logic in the intelligent contract, and generating a source data acquisition request on the blockchain; wherein the source data acquisition request includes a device identifier corresponding to any one of the at least one terminal device and the event information;

acquiring the source data acquisition request from the blockchain, and sending the source data acquisition request to the target terminal equipment, so that the target terminal equipment extracts source data fragments corresponding to the abnormal event from the acquired source data based on the event information, and sends the extracted source data fragments to the data processing platform;

2. The method of claim 1, the determining whether the source data includes a source data segment corresponding to an exception event, comprising:

3. The method of claim 1, the invoking source data certification logic in the smart contract to certify the extracted source data segment on the blockchain, comprising:

if so, the source data segment is stored on the blockchain.

4. The method of claim 1, the event information comprising an event type and/or an event occurrence range.

5. The method of claim 4, the event occurrence range comprising a temporal range and/or a spatial range of event occurrence.

6. A data certification method based on block chain is applied to terminal equipment; wherein, the block chain is provided with an intelligent contract for processing data; the method comprises the following steps:

transmitting the data summary to a data processing platform accessing the blockchain, so that when the data processing platform determines that the source data comprises source data fragments corresponding to an abnormal event based on the data summary, generating device identifications respectively corresponding to at least one terminal device associated with the abnormal event and abnormal report information of event information corresponding to the abnormal event, and issuing the abnormal report information to the blockchain to call source data acquisition logic in the intelligent contract, and generating a source data acquisition request comprising the device identifications corresponding to any target terminal device in the at least one terminal device and the event information on the blockchain; wherein the event information is used for describing the attribute of the abnormal event;

7. The method of claim 6, the event information comprising event type and/or event occurrence range.

8. The method of claim 7, the event occurrence range comprising a temporal range and/or a spatial range of event occurrence.

9. A blockchain-based data certification device applied to a data processing platform accessing the blockchain; wherein, the block chain is provided with an intelligent contract for processing data; the device comprises:

The first generation module is used for generating abnormal report information and issuing the abnormal report information to the block chain if the abnormal report information is generated; the abnormal report information comprises equipment identifiers respectively corresponding to at least one terminal equipment associated with the abnormal event and event information corresponding to the abnormal event; the event information is used for describing the attribute of the abnormal event;

the second generation module is used for calling source data acquisition logic in the intelligent contract and generating a source data acquisition request on the blockchain; wherein the source data acquisition request includes a device identifier corresponding to any one of the at least one terminal device and the event information;

the acquisition module is used for acquiring the source data acquisition request from the blockchain, sending the source data acquisition request to the target terminal equipment, so that the target terminal equipment extracts source data fragments corresponding to the abnormal event from the acquired source data based on the event information, and sending the extracted source data fragments to the data processing platform;

10. A blockchain-based data certification device, which is applied to terminal equipment; wherein, the block chain is provided with an intelligent contract for processing data; the device comprises:

the sending module is used for sending the data abstract to a data processing platform accessing the blockchain, so that when the data processing platform determines that the source data comprises source data fragments corresponding to an abnormal event based on the data abstract, generating device identifiers respectively corresponding to at least one terminal device associated with the abnormal event and abnormal report information of event information corresponding to the abnormal event, and issuing the abnormal report information to the blockchain to call source data acquisition logic in the intelligent contract, and generating a source data acquisition request comprising the device identifiers corresponding to any target terminal device in the at least one terminal device and the event information on the blockchain; wherein the event information is used for describing the attribute of the abnormal event;

11. An electronic device, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to implement the method of any of claims 1-8 by executing the executable instructions.

12. A computer readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the method of any of claims 1-8.