CN110099108B - Block chain event duplicate removal method and device, computer equipment and storage medium - Google Patents
Block chain event duplicate removal method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN110099108B CN110099108B CN201910342419.8A CN201910342419A CN110099108B CN 110099108 B CN110099108 B CN 110099108B CN 201910342419 A CN201910342419 A CN 201910342419A CN 110099108 B CN110099108 B CN 110099108B
- Authority
- CN
- China
- Prior art keywords
- event
- identifier
- block chain
- contract
- release
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3827—Use of message hashing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Computer Security & Cryptography (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a block chain event duplicate removal method, a block chain event duplicate removal device, computer equipment and a storage medium, wherein the block chain event duplicate removal method comprises the steps that a block chain system receives a transaction request sent by an issuing server, the transaction request is used for requesting to issue an event, the transaction request comprises an issuing identifier of the event to be issued, the block chain system calls a duplicate removal contract, and if it is determined that the event identifier corresponding to the issuing identifier is stored in the block chain system, the event identifier corresponding to the issuing identifier is sent to the issuing server. The technical scheme avoids the issue server issuing the same event to the blockchain system for multiple times, thereby reducing the pressure of the blockchain system.
Description
Technical Field
The embodiment of the invention relates to the field of financial technology (Fintech), in particular to a block chain (Blockchain) event duplicate removal method and device, computer equipment and a storage medium.
Background
The block chain is a chain formed by a series of blocks, each block records the data of the block and the hash value of the previous block, and all the blocks are successively formed into a chain in this way. The cryptography and the decentralized idea on which the blockchain is based make it impossible to tamper with the historical information on the chain.
With the development of computer technology, more and more technologies are applied in the financial field, the traditional financial industry is gradually changing to the financial technology, the block chain message and event transmission technology is no exception, but higher requirements are also put forward on the technologies due to the requirements of the security and the real-time performance of the financial and payment industries.
In the event publishing subscription, the producer writes the event to be published into the blockchain system, and the consumer reads the event to be acquired from the blockchain system. After the producer issues the event to the blockchain system, if the producer does not receive the response message of the blockchain system within the preset time period, the same event will be reissued to the blockchain system, but the number of events that can be processed by the blockchain system at the same time is limited, and if the producer issues the same event to the blockchain system for multiple times, unnecessary stress on the blockchain system will be caused.
Disclosure of Invention
Embodiments of the present invention provide a method and an apparatus for removing duplicate block chain events, a computer device, and a storage medium, which avoid a publishing server from publishing the same event to a block chain system multiple times, thereby reducing the pressure of the block chain system.
The block chain event duplicate removal method provided by the embodiment of the invention comprises the following steps:
the block chain system receives a transaction request sent by an issuing server; the transaction request is used for requesting to issue an event; the transaction request comprises a release identifier of an event to be released;
the block chain system calls a deduplication contract to determine whether an event identifier corresponding to the release identifier is stored in the block chain system; the event identification is used for uniquely identifying a published event;
and if the block chain system determines that the event identifier corresponding to the release identifier is stored in the block chain system, sending the event identifier corresponding to the release identifier to the release server.
In the technical scheme, after the block chain system receives the transaction request sent by the publishing server, a transaction log for recording the event to be published is not directly generated, but a duplicate removal contract is called to judge whether the event identifier corresponding to the publishing identifier of the event to be published exists in the block chain system, if so, the event to be published can be determined to be successfully published to the block chain system, and the event to be published does not need to be published again, namely, the publishing server is prevented from publishing the same event to the block chain system for multiple times, the number of events processed by the block chain system at the same time is reduced, the working pressure of the block chain system is reduced, a consumer is prevented from subscribing the same event, and the user experience is improved.
Optionally, the method further includes:
if the block chain system determines that the event identifier corresponding to the release identifier is not stored in the block chain system, calling a theme contract of the theme to which the event to be released belongs; the theme contract is used for recording the event to be issued and the event identifier of the event to be issued in a transaction log;
and the block chain system sends the event identifier of the event to be issued to the issuing server, and correspondingly stores the event identifier of the event to be issued and the issuing identifier into the storage space of the de-duplication instruction.
In the above technical solution, after the blockchain system receives the transaction request sent by the issuing server, if it is determined that the event identifier corresponding to the issuing identifier is not stored, it is determined that the event to be issued has not been successfully issued to the blockchain system, and a topic contract of a topic to which the event to be issued belongs needs to be called to execute issuing, so that it is ensured that the event to be issued in the transaction request sent by the issuing server is successfully issued to the blockchain system.
Optionally, the overlap elimination is approximately provided with a maximum storage duration;
the method further comprises the following steps:
and the block chain system deletes the corresponding relation between the release identifier and the event identifier reaching the maximum storage time length from the storage space indicated by the de-duplication restriction.
In the technical scheme, considering that the storage space for storing the corresponding relation between the release identifier and the event identifier in the block chain system is limited, the interval time for the release server to release the same event is short, the maximum storage duration is set in the duplicate removal contract, the corresponding relation in the duplicate removal contract is periodically cleared, and the problem that the function is limited due to insufficient storage space for removing the duplicate is solved. And the maximum storage duration is set, so that the workload of removing the coincidence about searching the event identifier corresponding to the release identifier can be reduced, and the working efficiency of the block chain system is further improved.
Optionally, the blockchain system includes a plurality of storage spaces;
the block chain system correspondingly stores the event identifier of the event to be issued and the issuing identifier into the storage space of the de-duplication instruction, and the method comprises the following steps:
the block chain system determines a storage space of the de-duplication instruction from the plurality of storage spaces according to the release identifier of the event to be released; and correspondingly storing the event identifier of the event to be issued and the issuing identifier into the de-duplication restriction indication storage space.
In the technical scheme, a plurality of storage spaces are stored in the block chain system, and different events to be issued are set to be mapped to the corresponding storage spaces according to the events to be issued, so that the corresponding relation between the issuing identification and the event identification is classified into the plurality of storage spaces according to rules, and more corresponding relations between the issuing identification and the event identification are stored.
Optionally, the block chain system calls a deduplication contract, including:
and the block chain system calls a subject contract of the subject to which the event to be issued belongs, and calls the deduplication contract through the subject contract of the subject to which the event to be issued belongs.
In the technical scheme, after receiving the transaction request, the blockchain system calls the theme contract of the theme to which the event to be issued belongs, and calls the deduplication contract from the theme contract, so that the orderliness of the blockchain system in the actual work is improved.
Correspondingly, an embodiment of the present invention further provides a block chain event deduplication method, including:
the release server sends a deployment request to the blockchain system; the deployment request is used for deploying the deduplication contract in a blockchain system; the de-overlap contract is used for determining whether an event identifier corresponding to the release identifier of the event to be released is stored in the block chain system; the event identification is used for uniquely identifying a published event;
the issuing server receives a deployment response, wherein the deployment response is used for indicating that the de-duplication contract deployment is successful.
In the technical scheme, the release server deploys the deduplication contract in the blockchain system in advance, so that when the transaction request is sent to the blockchain system, the blockchain system can filter out the same event, and simultaneously feeds back the event identifier corresponding to the release identifier to the release server, thereby preventing the release server from releasing the transaction request of the same event to the blockchain system for many times, and improving the working efficiency of the release server.
Correspondingly, an embodiment of the present invention further provides a device for removing duplicate block chain events, including:
the receiving and sending unit is used for receiving the transaction request sent by the issuing server; the transaction request is used for requesting to issue an event; the transaction request comprises a release identifier of an event to be released;
the processing unit is used for calling a deduplication contract and determining whether an event identifier corresponding to the release identifier is stored in the block chain system; the event identification is used for uniquely identifying a published event;
the processing unit is further configured to control the transceiver unit to send the event identifier corresponding to the release identifier to the release server if it is determined that the event identifier corresponding to the release identifier is stored in the block chain system.
Optionally, the processing unit is further configured to:
if the event identifier corresponding to the release identifier is determined not to be stored in the block chain system, calling a theme contract of the theme to which the event to be released belongs; the theme contract is used for recording the event to be issued and the event identifier of the event to be issued in a transaction log;
and controlling the transceiver unit to send the event identifier of the event to be issued to the issuing server, and correspondingly storing the event identifier of the event to be issued and the issuing identifier into the storage space of the de-duplication instruction.
Optionally, the overlap elimination is approximately provided with a maximum storage duration;
the processing unit is further configured to:
and deleting the corresponding relation between the release identifier and the event identifier reaching the maximum storage time length from the storage space indicated by the de-duplication.
Optionally, the blockchain system includes a plurality of storage spaces;
the processing unit is specifically configured to:
determining a storage space of the de-duplication instruction from the plurality of storage spaces according to the release identifier of the event to be released; and correspondingly storing the event identifier of the event to be issued and the issuing identifier into the de-duplication restriction indication storage space.
Optionally, the processing unit is specifically configured to:
and calling a subject contract of the subject to which the event to be issued belongs, and calling the duplicate removal contract through the subject contract of the subject to which the event to be issued belongs.
Correspondingly, an embodiment of the present invention further provides a device for removing duplicate block chain events, including:
a sending unit, configured to send a deployment request to a blockchain system; the deployment request is used for deploying the deduplication contract in a blockchain system; the de-overlap contract is used for determining whether an event identifier corresponding to the release identifier of the event to be released is stored in the block chain system; the event identification is used for uniquely identifying a published event;
a receiving unit, configured to receive a deployment response, where the deployment response is used to indicate that the de-duplication approximation deployment is successful.
Correspondingly, an embodiment of the present invention further provides a computer device, including:
a memory for storing program instructions;
and the processor is used for calling the program instruction stored in the memory and executing the block chain event duplicate removal method according to the obtained program.
Accordingly, an embodiment of the present invention further provides a computer-readable non-volatile storage medium, which includes computer-readable instructions, and when the computer-readable instructions are read and executed by a computer, the computer is enabled to execute the above block chain event deduplication method.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic diagram of a system architecture according to an embodiment of the present invention;
fig. 2 is a flowchart illustrating a method for removing duplicate block chain events according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a block chain event deduplication apparatus according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a block chain event deduplication apparatus according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention clearer, the present invention will be described in further detail with reference to the accompanying drawings, and it is apparent that the described embodiments are only a part of the embodiments of the present invention, not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Fig. 1 schematically shows a system architecture to which an embodiment of the present invention provides a block chain event deduplication method, where the system architecture may include a producer 100, a publishing server 200, a block chain system 300, a subscription server 400, and a consumer 500. The producer 100 is used to generate an event to be published, the publishing server 200 is used to write the event to be published into the blockchain system 300, and the consumer 500 is used to subscribe to the event from the blockchain system 300 through the subscribing server 400.
When a producer 100 needs to issue an event, the event to be issued is sent to the issuing server 200, the issuing server 200 generates a transaction request according to the event to be issued, the issuing server 200 sends the transaction request to the blockchain system 300, and the blockchain system 300 executes a contract according to the transaction request and records the event to be issued, that is, the event issue of the producer 100 is completed.
When the consumer 500 needs to acquire an event, an acquisition request is sent to the subscription server 400, and the subscription server 400 determines the event corresponding to the acquisition request from the block chain system 300 according to the received acquisition request and feeds the event back to the consumer 500, that is, completes the event subscription of the consumer 500.
The publishing server 200 and the subscribing server 400 in the system architecture may be physically one server, which completes the publishing and subscribing functions, or may be two separate servers, which respectively complete the publishing function and the subscribing function, and are not limited herein.
The blockchain system 300 executes the contract according to the transaction request and records the event to be issued, the event to be issued is stored in the blockchain system 300 after being issued, and the blockchain system 300 has the characteristic of being not easy to be tampered and deleted due to the fact that the blockchain system 300 is in the chain structure, and the safety of the event to be issued stored in the blockchain system 300 is guaranteed.
After the publishing server 200 sends the transaction request to the blockchain system 300, if the publishing server 200 can obtain a response message of the publishing event from the blockchain system 300 and the response message records an event identifier of the publishing event, the publishing server 200 determines that the event to be published is successfully published to the blockchain system 300, otherwise, the publishing server 200 determines that the event to be published is not successfully published to the blockchain system 300 and needs to re-publish the event to be published to the blockchain system 300, and with reference to the description, the embodiments of the present invention relate to the following scenarios:
scene one: the issuing server sends a transaction request to the blockchain system, the blockchain system successfully generates a transaction log and feeds back a response message, the response message has an event identifier of an issuing event, and the issuing server receives the response message and determines that the event is successfully issued.
Scene two: the issuing server sends a transaction request to the blockchain system, the blockchain system successfully generates a transaction log, but the issuing server does not receive a response message fed back by the blockchain system, or the fed back response message does not have an event identifier of the issued event, the issuing server considers that the event is not successfully issued and needs to issue again, the same event is stored in the transaction request and sent to the blockchain system, and the blockchain system determines that the event identifier of the issued event is already stored in the blockchain system and feeds back the event identifier of the issued event to the issuing server, so that the issuing server is informed that the event is successfully issued.
Scene three: the method comprises the steps that a release server sends a transaction request to a blockchain system, the blockchain system does not successfully generate a transaction log, the release server does not receive a response message fed back by the blockchain system, or the fed back response message does not have an event identifier of a release event, the release server considers that the event is not successfully released and needs to re-release, the same event is stored in the transaction request and sent to the blockchain system, the blockchain system determines that the event identifier of the release event is not stored in the blockchain system, a theme contract of a theme to which the event to be released belongs is called, the transaction log is generated, and the response message recorded with the event identifier of the release event is fed back to the release server, so that the release server is informed that the event is successfully released.
In conjunction with the above scenario, fig. 2 exemplarily illustrates a flow of a method for removing a blockchain event duplicate according to an embodiment of the present invention, where the flow may be performed by a blockchain event duplicate removal apparatus, which may be located in a blockchain system, or may be the blockchain system. As shown in fig. 2, the process involves an execution subject having a distribution server and a blockchain system, and the specific process is as follows.
In step 201, the publishing server sends a transaction request to the blockchain system.
The release server receives a release request sent by a producer, generates a transaction request according to the release request, and sends the transaction request to the blockchain system, wherein the transaction request is used for requesting to release an event, and the transaction request comprises a release identifier of the event to be released. The release Identifier of the event to be released may include information such as a producer IP (Internet Protocol, Protocol for interconnection between networks) address, a thread ID (Identification number), a timestamp, a time increment value, and the like of the event to be released, and is used to uniquely determine the event to be released.
Further, the release identifier of the event to be released may be generated by a producer, or may be generated by a release server, and when the release server generates the release identifier of the event to be released, all received events to be released are identified according to a certain rule, so as to ensure that the release identifier of the event to be released is used for uniquely determining the event to be released.
In step 202, the blockchain system calls a deduplication contract.
Specifically, whether an event identifier corresponding to the release identifier of the event to be released is stored in the blockchain system is determined through the deduplication contract, so that the release server is prevented from releasing the same event to be released to the blockchain system.
In the embodiment of the present invention, the release server may pre-deploy the deduplication contract, specifically, the release server sends a deployment request to the blockchain system, where the deployment request is used to deploy the deduplication contract in the blockchain system, the blockchain system deploys the deduplication contract in the blockchain system according to the deployment request after receiving the deployment request, and after the blockchain system completes deduplication contract deployment, the blockchain system sends a deployment response to the release server to notify the release server that deployment is successful.
In step 203, the blockchain system determines whether an event identifier is stored in the blockchain system.
If the event to be published is successfully published in the blockchain system, the blockchain system generates a transaction log in which the event to be published is recorded, the generation of the transaction log means that the event to be published becomes the published event, an event identifier is recorded in the transaction log, and the event identifier is used for uniquely identifying the published event and is also in corresponding relation with the published identifier of the event to be published.
In the embodiment of the invention, the corresponding relation between the issuing identifier of the event and the event identifier can be stored in the storage space indicated by the deduplication contract, and the block chain system can directly call the deduplication contract to determine whether the storage space indicated by the deduplication contract stores the event identifier corresponding to the issuing identifier of the event to be issued. The deduplication contract can also be called through the theme contract of the theme to which the event to be published belongs, that is, the theme contract of the theme to which the event to be published belongs is called through the blockchain system, and the deduplication contract is called through the theme contract of the theme to which the event to be published belongs.
In the embodiment of the invention, because the storage space indicated by the duplicate removal contract in the block chain system is limited, and the interval time for issuing the same event by the issuing server is short, the maximum storage time length can be set in the duplicate removal contract, and if the corresponding relation between the issuing identifier and the event identifier of the event stored in the duplicate removal contract exceeds the maximum storage time length, the corresponding relation between the issuing identifier and the event identifier is deleted.
Step 204, the blockchain system sends the event identifier corresponding to the release identifier to the release server.
If the event identifier corresponding to the release identifier is stored in the block chain system, the release of the event to be released is determined to be completed, and the event identifier corresponding to the determined release identifier is sent to the release server to inform the release server that the release of the event to be released is completed.
Of course, in the embodiment of the present invention, it may also be determined that the to-be-issued event is not yet issued if the blockchain system determines that the event identifier is not stored in the blockchain system, and the blockchain system needs to execute a contract to issue the to-be-issued event, specifically, the blockchain system calls a topic contract of a topic to which the to-be-issued event belongs to generate a transaction log in which the to-be-issued event and the event identifier of the to-be-issued event are recorded, and the blockchain system sends the event identifier of the to-be-issued event to the issue server, and correspondingly stores the event identifier and the issue identifier of the to-be-issued event into a storage space indicated in the deduplication contract.
Furthermore, in order to improve the system performance, a block chain system may be further configured to include a plurality of storage spaces. After the blockchain system generates the event identifier according to the release identifier, the corresponding relationship between the two event identifiers can be stored in the storage space indicated by the de-duplication rule according to the release identifier. Optionally, the block system may determine, according to the timestamp of the release identifier of the event to be released, a storage space indicated by the deduplication contract from the plurality of storage spaces, and correspondingly store the event identifier and the release identifier of the event to be released into the storage space indicated by the deduplication contract. Correspondingly, when judging whether the event identifier corresponding to the release identifier is stored in the block chain system, the storage space indicated by the de-duplication rule can be determined according to the time stamp of the release identifier of the event to be released, and whether the event identifier corresponding to the release identifier is stored in the storage space can be searched. In addition, the scheme can also calculate the hash value of the release identifier, take the key field of the release identifier and the like to determine the storage space indicated by the de-duplication contract. For example, mapping structure mapping may be used to implement mapping of the deduplication contract with multiple storage spaces. The scheme can expand the space for storing the corresponding relation between the release identifier and the event identifier in the block chain system, and further improve the system performance.
In the above embodiment, after receiving the transaction request sent by the publishing server, the blockchain system does not directly generate a transaction log recording the event to be published, but first calls a deduplication contract to determine whether the event identifier corresponding to the publishing identifier of the event to be published already exists in the blockchain system, and if the event identifier exists, it can be determined that the event to be published has been successfully published into the blockchain system, and the event to be published does not need to be published again, that is, the publishing server is prevented from publishing the same event into the blockchain system, the number of events processed by the blockchain system at the same time is reduced, the working pressure of the blockchain system is reduced, and the consumer is prevented from subscribing to the same event, so that the user experience is improved.
Based on the same inventive concept, fig. 3 exemplarily illustrates a structure of a blockchain event deduplication apparatus, which may perform a flow of a blockchain event deduplication method according to an embodiment of the present invention.
A transceiving unit 301, configured to receive a transaction request sent by a publishing server; the transaction request is used for requesting to issue an event; the transaction request comprises a release identifier of an event to be released;
the processing unit 302 is configured to invoke a deduplication contract, and determine whether an event identifier corresponding to the release identifier is stored in the blockchain system; the event identification is used for uniquely identifying a published event;
the processing unit 302 is further configured to control the transceiver unit 301 to send the event identifier corresponding to the release identifier to the release server if it is determined that the event identifier corresponding to the release identifier is stored in the blockchain system.
Optionally, the processing unit 302 is further configured to:
if the event identifier corresponding to the release identifier is determined not to be stored in the block chain system, calling a theme contract of the theme to which the event to be released belongs; the theme contract is used for recording the event to be issued and the event identifier of the event to be issued in a transaction log;
the transceiver unit 301 is controlled to send the event identifier of the event to be published to the publishing server, and correspondingly store the event identifier of the event to be published and the publishing identifier into the storage space of the de-duplication instruction.
Optionally, the overlap elimination is approximately provided with a maximum storage duration;
the processing unit 302 is further configured to:
and deleting the corresponding relation between the release identifier and the event identifier reaching the maximum storage time length from the storage space indicated by the de-duplication.
Optionally, the blockchain system includes a plurality of storage spaces;
the processing unit 302 is specifically configured to:
determining a storage space of the de-duplication instruction from the plurality of storage spaces according to the release identifier of the event to be released; and correspondingly storing the event identifier of the event to be issued and the issuing identifier into the de-duplication restriction indication storage space.
Optionally, the processing unit 302 is specifically configured to:
and calling a subject contract of the subject to which the event to be issued belongs, and calling the duplicate removal contract through the subject contract of the subject to which the event to be issued belongs.
Based on the same inventive concept, fig. 4 exemplarily shows a structure of a blockchain event deduplication apparatus, which may perform a flow of a blockchain event deduplication method according to an embodiment of the present invention.
A sending unit 401, configured to send a deployment request to the blockchain system; the deployment request is used for deploying the deduplication contract in a blockchain system; the de-overlap contract is used for determining whether an event identifier corresponding to the release identifier of the event to be released is stored in the block chain system; the event identification is used for uniquely identifying a published event;
a receiving unit 402, configured to receive a deployment response, where the deployment response is used to indicate that the de-duplication approximation deployment is successful.
Based on the same inventive concept, an embodiment of the present invention further provides a computer device, including:
a memory for storing program instructions;
and the processor is used for calling the program instruction stored in the memory and executing the block chain event duplicate removal method according to the obtained program.
Based on the same inventive concept, an embodiment of the present invention further provides a computer-readable non-volatile storage medium, which includes computer-readable instructions, and when the computer reads and executes the computer-readable instructions, the computer is caused to execute the above block chain event deduplication method.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.
Claims (14)
1. A method for block chain event deduplication, comprising:
the block chain system receives a transaction request sent by an issuing server; the transaction request is used for requesting to issue an event in the blockchain system; the transaction request comprises a release identifier of an event to be released;
the block chain system calls a deduplication contract to determine whether an event identifier corresponding to the release identifier is stored in the block chain system; the event identification is used for uniquely identifying a published event;
and if the block chain system determines that the event identifier corresponding to the release identifier is stored in the block chain system, sending the event identifier corresponding to the release identifier to the release server.
2. The method of claim 1, further comprising:
if the block chain system determines that the event identifier corresponding to the release identifier is not stored in the block chain system, calling a theme contract of the theme to which the event to be released belongs; the theme contract is used for recording the event to be issued and the event identifier of the event to be issued in a transaction log;
and the block chain system sends the event identifier of the event to be issued to the issuing server, and correspondingly stores the event identifier of the event to be issued and the issuing identifier into the storage space of the de-duplication instruction.
3. The method of claim 2, wherein the de-coincidence is set approximately with a maximum storage duration;
the method further comprises the following steps:
and the block chain system deletes the corresponding relation between the release identifier and the event identifier reaching the maximum storage time length from the storage space indicated by the de-duplication restriction.
4. The method of claim 2, wherein the blockchain system comprises a plurality of memory spaces;
the block chain system correspondingly stores the event identifier of the event to be issued and the issuing identifier into the storage space of the de-duplication instruction, and the method comprises the following steps:
the block chain system determines a storage space of the de-duplication instruction from the plurality of storage spaces according to the release identifier of the event to be released; and correspondingly storing the event identifier of the event to be issued and the issuing identifier into the storage space of the de-duplication restriction indication.
5. The method of any of claims 1 to 4, wherein the block chain system calls a deduplication contract, comprising:
and the block chain system calls a subject contract of the subject to which the event to be issued belongs, and calls the deduplication contract through the subject contract of the subject to which the event to be issued belongs.
6. A method for block chain event deduplication, comprising:
the release server sends a deployment request to the blockchain system; the deployment request is used for deploying the deduplication contract in a blockchain system; the de-overlap contract is used for determining whether an event identifier corresponding to the release identifier of the event to be released is stored in the block chain system; the event identification is used for uniquely identifying a published event; the block chain system also stores the published event;
the issuing server receives a deployment response, wherein the deployment response is used for indicating that the de-duplication contract deployment is successful.
7. A block chain event deduplication apparatus, comprising:
the receiving and sending unit is used for receiving the transaction request sent by the issuing server; the transaction request is used for requesting to issue an event in the blockchain system; the transaction request comprises a release identifier of an event to be released;
the processing unit is used for calling a deduplication contract and determining whether an event identifier corresponding to the release identifier is stored in the block chain system; the event identification is used for uniquely identifying a published event;
the processing unit is further configured to control the transceiver unit to send the event identifier corresponding to the release identifier to the release server if it is determined that the event identifier corresponding to the release identifier is stored in the block chain system.
8. The apparatus as recited in claim 7, said processing unit to further:
if the event identifier corresponding to the release identifier is determined not to be stored in the block chain system, calling a theme contract of the theme to which the event to be released belongs; the theme contract is used for recording the event to be issued and the event identifier of the event to be issued in a transaction log;
and controlling the transceiver unit to send the event identifier of the event to be issued to the issuing server, and correspondingly storing the event identifier of the event to be issued and the issuing identifier into the storage space of the de-duplication instruction.
9. The apparatus of claim 8, wherein the de-coincidence is set approximately with a maximum storage duration;
the processing unit is further configured to:
and deleting the corresponding relation between the release identifier and the event identifier reaching the maximum storage time length from the storage space indicated by the de-duplication.
10. The apparatus of claim 8, wherein the blockchain system comprises a plurality of storage spaces;
the processing unit is specifically configured to:
determining a storage space of the de-duplication instruction from the plurality of storage spaces according to the release identifier of the event to be released; and correspondingly storing the event identifier of the event to be issued and the issuing identifier into the de-duplication restriction indication storage space.
11. The apparatus according to any one of claims 7 to 10, wherein the processing unit is specifically configured to:
and calling a subject contract of the subject to which the event to be issued belongs, and calling the duplicate removal contract through the subject contract of the subject to which the event to be issued belongs.
12. A block chain event deduplication apparatus, comprising:
a sending unit, configured to send a deployment request to a blockchain system; the deployment request is used for deploying the deduplication contract in a blockchain system; the de-overlap contract is used for determining whether an event identifier corresponding to the release identifier of the event to be released is stored in the block chain system; the event identification is used for uniquely identifying a published event; the block chain system also stores the published event;
a receiving unit, configured to receive a deployment response, where the deployment response is used to indicate that the de-duplication approximation deployment is successful.
13. A computer device, comprising:
a memory for storing program instructions;
a processor for calling program instructions stored in said memory to execute the method of any one of claims 1 to 6 in accordance with the obtained program.
14. A computer-readable non-transitory storage medium including computer-readable instructions which, when read and executed by a computer, cause the computer to perform the method of any one of claims 1 to 6.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910342419.8A CN110099108B (en) | 2019-04-26 | 2019-04-26 | Block chain event duplicate removal method and device, computer equipment and storage medium |
| PCT/CN2020/084282 WO2020216077A1 (en) | 2019-04-26 | 2020-04-10 | Blockchain event deduplication method and apparatus, and computer device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910342419.8A CN110099108B (en) | 2019-04-26 | 2019-04-26 | Block chain event duplicate removal method and device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110099108A CN110099108A (en) | 2019-08-06 |
| CN110099108B true CN110099108B (en) | 2022-04-01 |
Family
ID=67445904
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910342419.8A Active CN110099108B (en) | 2019-04-26 | 2019-04-26 | Block chain event duplicate removal method and device, computer equipment and storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN110099108B (en) |
| WO (1) | WO2020216077A1 (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110099108B (en) * | 2019-04-26 | 2022-04-01 | 深圳前海微众银行股份有限公司 | Block chain event duplicate removal method and device, computer equipment and storage medium |
| CN110555625B (en) * | 2019-08-16 | 2024-04-26 | 腾讯科技（深圳）有限公司 | Information processing method, device, computer equipment and storage medium |
| CN111275553B (en) * | 2020-01-20 | 2023-08-11 | 联动优势科技有限公司 | Block chain data storage method and block chain system |
| CN114363162B (en) * | 2021-12-31 | 2024-05-03 | 支付宝(杭州)信息技术有限公司 | Block chain log generation method and device, electronic equipment and storage medium |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107295002A (en) * | 2017-07-12 | 2017-10-24 | 联动优势科技有限公司 | The method and server of a kind of high in the clouds data storage |
| CN107301536A (en) * | 2017-06-12 | 2017-10-27 | 腾讯科技（深圳）有限公司 | Resource transfers method and device |
| CN108062671A (en) * | 2017-11-03 | 2018-05-22 | 深圳市轱辘车联数据技术有限公司 | Data trade method, block chain node server and data submit terminal |
| WO2018144302A1 (en) * | 2017-01-31 | 2018-08-09 | Rush Thomas Jay | Blockchain data-processing engine |
| CN108573741A (en) * | 2017-12-25 | 2018-09-25 | 北京金山云网络技术有限公司 | Business datum recording method, device, equipment and storage medium |
| CN108805569A (en) * | 2018-05-29 | 2018-11-13 | 阿里巴巴集团控股有限公司 | Transaction processing method and device, electronic equipment based on block chain |
| CN108846752A (en) * | 2018-06-06 | 2018-11-20 | 北京京东金融科技控股有限公司 | Data processing method, system, block platform chain and readable storage medium storing program for executing |
| CN108961052A (en) * | 2018-06-25 | 2018-12-07 | 百度在线网络技术（北京）有限公司 | Verification method, storage method, device, equipment and the medium of block chain data |
| CN109615383A (en) * | 2018-10-26 | 2019-04-12 | 阿里巴巴集团控股有限公司 | Data based on block chain deposit card, acquisition methods and device |
Family Cites Families (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170134161A1 (en) * | 2015-11-06 | 2017-05-11 | Cable Television Laboratories, Inc | Blockchaining for media distribution |
| KR101780636B1 (en) * | 2016-05-16 | 2017-09-21 | 주식회사 코인플러그 | Method for issuing certificate information and blockchain-based server using the same |
| CN107395557B (en) * | 2017-03-28 | 2020-05-15 | 创新先进技术有限公司 | Service request processing method and device |
| US10839379B2 (en) * | 2017-07-20 | 2020-11-17 | Chicago Mercantile Exchange Inc. | Blockchain including linked digital assets |
| CN107464117B (en) * | 2017-08-04 | 2021-06-22 | 平安科技（深圳）有限公司 | Block chain based data management method and block chain system |
| CN108614878B (en) * | 2018-04-27 | 2023-01-10 | 腾讯科技（深圳）有限公司 | Protocol data management method, device, storage medium and system |
| CN108769751B (en) * | 2018-05-02 | 2020-09-08 | 中广热点云科技有限公司 | Network audio-visual management support system based on intelligent contract |
| CN108681572B (en) * | 2018-05-04 | 2020-12-29 | 蔷薇大树科技有限公司 | Data storage method and device of block chain and electronic equipment |
| CN108647974A (en) * | 2018-05-11 | 2018-10-12 | 北京奇虎科技有限公司 | A kind of Information Authentication method, apparatus and system based on block chain |
| CN110099108B (en) * | 2019-04-26 | 2022-04-01 | 深圳前海微众银行股份有限公司 | Block chain event duplicate removal method and device, computer equipment and storage medium |
-
2019
- 2019-04-26 CN CN201910342419.8A patent/CN110099108B/en active Active
-
2020
- 2020-04-10 WO PCT/CN2020/084282 patent/WO2020216077A1/en active Application Filing
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2018144302A1 (en) * | 2017-01-31 | 2018-08-09 | Rush Thomas Jay | Blockchain data-processing engine |
| CN107301536A (en) * | 2017-06-12 | 2017-10-27 | 腾讯科技（深圳）有限公司 | Resource transfers method and device |
| CN107295002A (en) * | 2017-07-12 | 2017-10-24 | 联动优势科技有限公司 | The method and server of a kind of high in the clouds data storage |
| CN108062671A (en) * | 2017-11-03 | 2018-05-22 | 深圳市轱辘车联数据技术有限公司 | Data trade method, block chain node server and data submit terminal |
| CN108573741A (en) * | 2017-12-25 | 2018-09-25 | 北京金山云网络技术有限公司 | Business datum recording method, device, equipment and storage medium |
| CN108805569A (en) * | 2018-05-29 | 2018-11-13 | 阿里巴巴集团控股有限公司 | Transaction processing method and device, electronic equipment based on block chain |
| CN108846752A (en) * | 2018-06-06 | 2018-11-20 | 北京京东金融科技控股有限公司 | Data processing method, system, block platform chain and readable storage medium storing program for executing |
| CN108961052A (en) * | 2018-06-25 | 2018-12-07 | 百度在线网络技术（北京）有限公司 | Verification method, storage method, device, equipment and the medium of block chain data |
| CN109615383A (en) * | 2018-10-26 | 2019-04-12 | 阿里巴巴集团控股有限公司 | Data based on block chain deposit card, acquisition methods and device |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2020216077A1 (en) | 2020-10-29 |
| CN110099108A (en) | 2019-08-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110099108B (en) | Block chain event duplicate removal method and device, computer equipment and storage medium | |
| CN110083629B (en) | Event subscription method and device based on blockchain | |
| EP3185125B1 (en) | Data backup method, system, node and computer storage media | |
| CN109614209B (en) | Task processing method, application server and system | |
| CN103475899B (en) | Data distributing method and device | |
| CN111782360A (en) | Distributed task scheduling method and device | |
| CN110611707B (en) | Task scheduling method and device | |
| CN111061685B (en) | Log query method and device, node equipment and storage medium | |
| CN106685894B (en) | Risk identification method, device and system | |
| CN110009347B (en) | Block chain transaction information auditing method and device | |
| CN110098979A (en) | A kind of short link message monitor method and device based on block chain | |
| CN111177257A (en) | Data storage and access method, device and equipment of block chain | |
| CN110704438A (en) | Method and device for generating bloom filter in block chain | |
| CN111984601A (en) | Log file deleting method and device, electronic equipment and storage medium | |
| CN110071968B (en) | Block chain based message storage method and device | |
| CN113626399B (en) | Data synchronization method, device, server and storage medium | |
| CN111124631A (en) | Task processing method and device based on block chain network | |
| CN111640012A (en) | Block chain transaction tracing method and device | |
| CN110825758B (en) | Transaction processing method and device | |
| CN112416534A (en) | Agent-based task management method and device | |
| CN115454599A (en) | Task processing method, system, device, storage medium and electronic equipment | |
| CN116244062A (en) | Data processing method and device, electronic equipment and storage medium | |
| CN113515387B (en) | Data processing method and device and electronic device | |
| CN105790975A (en) | Service processing operation execution method and device | |
| CN113656374A (en) | Method and device for processing service message with attachment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |