WO2020207445A1

WO2020207445A1 - Blockchain-based event subscription method and apparatus

Info

Publication number: WO2020207445A1
Application number: PCT/CN2020/084028
Authority: WO
Inventors: 梅芬; 苏小康; 张开翔; 范瑞彬
Original assignee: 深圳前海微众银行股份有限公司
Priority date: 2019-04-09
Filing date: 2020-04-09
Publication date: 2020-10-15
Also published as: CN110110269B; CN110110269A

Abstract

A blockchain-based event subscription method and apparatus, relating to the technical field of scientific and technological finance. The method comprises: an intermediate server receives a subscription request sent by a client; determine all key event sequences corresponding to a target theme and roles corresponding to all the key event sequences according to the subscription request, the key event sequences being determined by collecting statistics about historical service information of different roles; determine a target event sequence from all the key event sequences corresponding to the target theme according to the role corresponding to the client, and send the target event sequence to the client. The key event sequence is determined by collecting statistics about the historical service information of different roles. Therefore, when the subscription request is received, the key event sequence corresponding to the client can be determined according to the role of the client and sent to the client, instead of sending the whole event sequence to the client, so that information which is not concerned by some consumers is prevented from being returned, the bandwidth is saved, and the service speed can be ensured when the subscription is violently increased.

Description

Method and device for event subscription based on blockchain

Cross references to related applications

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office, the application number is 201910280096.4, and the application name is "a blockchain-based event subscription method and device" on April 9, 2019, the entire content of which is by reference Incorporated in this application.

Technical field

The embodiment of the present invention relates to the field of technology and finance technology, and in particular to a method and device for event subscription based on blockchain.

Background technique

With the development of computer technology, more and more technologies are applied in the financial field. The traditional financial industry is gradually changing to Finteh. Blockchain technology is no exception, but due to the security and real-time requirements of the financial industry , But also higher requirements for technology. A blockchain is a chain composed of a series of blocks. In addition to recording the data of this block, each block also records the Hash value of the previous block. In this way, a chain is formed. There are two core concepts of the blockchain, one is cryptography and the other is decentralization. Based on these two concepts, the historical information on the blockchain cannot be tampered with. A block is composed of a block header and a block body. The block header definition includes important fields such as the block height h and the hash value of the previous block. The block body mainly stores transaction data. The producer publishes a topic through the publishing interface, the topic includes the entire sequence of events, and the successfully published events will be permanently stored on the blockchain. When consumers subscribe to the topic, they will receive the entire sequence of events on the topic. Perhaps not every event in this topic is of concern to consumers, so some information that consumers do not pay attention to will be returned, which will waste bandwidth and affect service speed.

Summary of the invention

Since consumers will receive the entire sequence of events on the topic when subscribing to a topic, the consumer will receive unconcerned information, which will waste bandwidth and affect service speed. The embodiment of the present invention provides a blockchain-based event subscription. Method and device.

On the one hand, an embodiment of the present invention provides a blockchain-based event subscription method, including:

Receive the subscription request sent by the client;

Determine the target theme according to the subscription request, and determine all the key event sequences corresponding to the target theme and the roles corresponding to each key event sequence, the key event sequences are determined by counting historical business information of different roles;

Determine the target event sequence corresponding to the client from all key event sequences corresponding to the target theme according to the role corresponding to the client;

Sending the target event sequence to the client.

Optionally, the key event sequence is determined by counting historical business information of different roles, including:

For each role, acquiring historical business information of the role, where the historical business information includes historical subscription events and the sequence between historical subscription events;

Perform frequency statistics on the sequence between the historical subscription events to determine the key event sequence of the role.

Optionally, it also includes:

Save the key event sequence of each role to the blockchain.

Optionally, it also includes:

Cache the key event sequence of each role.

On the one hand, an embodiment of the present invention provides a blockchain-based event subscription device, including:

The receiving module is used to receive the subscription request sent by the client;

The processing module is used to determine the target theme according to the subscription request, and determine all the key event sequences corresponding to the target theme and the role corresponding to each key event sequence, the key event sequence is based on statistics of historical business information of different roles definite;

A query module, configured to determine the target event sequence corresponding to the client from all key event sequences corresponding to the target theme according to the role corresponding to the client;

The sending module is used to send the target event sequence to the client.

Optionally, the processing module is specifically configured to:

Optionally, the processing module is further used for:

Save the key event sequence of each role to the blockchain.

Optionally, the processing module is further used for:

Cache the key event sequence of each role.

On the one hand, an embodiment of the present invention provides a computer device, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor. When the processor executes the program, a blockchain-based The steps of the event subscription method.

On the one hand, an embodiment of the present invention provides a computer-readable storage medium that stores a computer program executable by a computer device. When the program runs on the computer device, the computer device executes a blockchain-based The steps of the event subscription method.

In one aspect, an embodiment of the present invention provides a computer program product containing instructions. The computer program product includes a computing program stored on a non-transitory computer-readable storage medium. The computer program includes program instructions. When the instructions are executed by the computer, the computer executes the steps of the blockchain-based event subscription method.

Since the historical business information of different roles is calculated in advance to determine the key event sequence, each target topic can include key event sequences corresponding to multiple roles. When a client's subscription request is received, the client in the target topic can be determined according to the role of the client Corresponding key event sequence, and then send the key event sequence to the client, instead of sending the entire event sequence of the target topic to the client, so as to avoid returning some information that consumers don’t care about. This saves bandwidth and saves bandwidth. The speed of service can also be guaranteed during a surge.

Description of the drawings

In order to more clearly describe the technical solutions in the embodiments of the present invention, the following will briefly introduce the drawings needed in the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings may be obtained from these drawings without creative labor.

FIG. 1 is a schematic diagram of an application scenario provided by an embodiment of the present invention;

2 is a schematic flowchart of a blockchain-based event subscription method provided by an embodiment of the present invention;

3 is a schematic flowchart of a method for determining a sequence of key events provided by an embodiment of the present invention;

4 is a schematic flowchart of another blockchain-based event subscription method provided by an embodiment of the present invention;

5 is a schematic structural diagram of a blockchain-based event subscription device provided by an embodiment of the present invention;

Fig. 6 is a schematic diagram of a computer-based structure provided by an embodiment of the present invention.

detailed description

In order to make the objectives, technical solutions and beneficial effects of the present invention clearer, the following further describes the present invention in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the present invention, but not to limit the present invention.

To facilitate understanding, the terms involved in the embodiments of the present invention are explained below.

Event: A change in the state of an object. For example, opening a door is an event, and closing a door is also an event.

Topic: The same type of event is a topic, and the topics are independent of each other.

Publish events (Publish): send events to specific topics.

Subscribe to events (Subscribe): Receive events from a specific topic.

Producer (Producer): The main body of the publishing event.

Consumer: The subject of the subscription event.

Smart contract: A piece of open and transparent code that runs on the blockchain.

Event ID (Event ID): After each event is successfully published, there will be a unique ID within the subject area.

Block chain: A block chain is a chain composed of a series of blocks. In addition to recording the data of this block, each block also records the hash value of the previous block. In this way, a chain is formed. There are two core concepts of the blockchain, one is cryptography and the other is decentralization. Based on these two concepts, the historical information on the blockchain cannot be tampered with. A block is composed of a block header and a block body. The block header definition includes important fields such as the block height h and the hash value of the previous block. The block body mainly stores transaction data.

Node: Each participant in the network is a node, and the node participates in network formation and data exchange. In the blockchain network, a node refers to a participant with a unique identity. The node has a complete copy of the ledger and has the ability to participate in the consensus and maintenance of the blockchain network.

The blockchain-based event subscription method in the embodiment of the present invention can be applied to a blockchain scenario. For example, as shown in FIG. 1, the scenario includes a client 101, an intermediate server 102, a blockchain 103, and The client 104 and the client 101 may be a producer or a consumer. When the client 101 is a producer, it can publish a topic to the intermediate server 102 through the Publish interface, or publish an event on a certain topic. The intermediate server 102 will verify whether the topic or event published by the client 101 is legal, and if it is legal, save the topic or event published by the client 101 in the blockchain 103. When the client 101 is a consumer, it can subscribe to a topic from the intermediate server 102 through the Subscribe interface. When the subscription is successful, the intermediate server 102 obtains the event on the topic from the blockchain 103 and sends the event on the topic Happened to client 101. When the producer publishes a new event on the topic, the intermediate server 102 sends the new event to the client 101. The client 101 can provide users with corresponding services. For example, when the user needs to query an event, the client 104 sends a query request to the client 101. The query request carries the event ID, and the client 101 obtains the corresponding event according to the event ID. Send to the client 104. The intermediate server 102 can obtain the historical service information of the client 101, that is, the events that the client 104 inquired from the client 101 and the sequence of the inquired events. The intermediate server 102 obtains the role of the client 101 and the corresponding key event sequence by performing statistics on the historical business information of the client 101. The intermediate server 102 may be a server or a server cluster composed of several servers or a cloud computing center. The user terminal 104 is an electronic device with network communication capabilities, and the electronic device may be a smart phone, a tablet computer, or a portable personal computer. The client 101 is connected to the intermediate server 102 through a wireless network.

Based on the application scenario diagram shown in Figure 1, the embodiment of the present invention provides a process of a blockchain-based event subscription method. The process of the method can be executed by a blockchain-based event subscription device. The event subscription device may be the intermediate server 102 shown in FIG. 1.

As shown in Figure 2, it includes the following steps:

Step 201: Receive a subscription request sent by the client.

Step 202: Determine the target topic according to the subscription request, and determine all key event sequences corresponding to the target topic and the role corresponding to each key event sequence.

Specifically, the key event sequence is determined by counting historical business information of different roles. Different roles correspond to different businesses, so the events of concern will not be the same.

Exemplarily, the operator of the set airport publishes a theme M, and the theme M includes 6 events, namely:

Event 1, check-in: passengers go through the check-in procedures and check their luggage.

Event 2, security check: passengers enter/leave the security check area.

Event 3, baggage handling: scan baggage at the security checkpoint and load the baggage into the container.

Event 4, cabin door operation: the cabin door is opened, boarded, finally boarded, and closed.

Event 5, flight operations: boarding gate, loading container, departure, takeoff.

Event 6, customer service: review baggage for new flights.

For the backend of the passenger APP, the role can be defined as a passenger, and the corresponding business is to provide passengers with information related to taking an airplane. Therefore, the events of greater concern are event 1, event 2, and event 3 in theme M. For the airline system, the role can be defined as an airline, and the corresponding business is to provide flight information for the airline. Therefore, the more concerned events are event 4, event 5 and event 6 in theme M.

Step 203: Determine the target event sequence corresponding to the client from all the key event sequences corresponding to the target theme according to the role corresponding to the client.

When a subscription request sent by the client is received, the role corresponding to the client can be determined first, and then all the key event sequences corresponding to the target topic are queried according to the role, and then the key event sequence matching the role is regarded as the target event sequence. For example, the target theme includes two key event sequences, sequence 1 and sequence 2, where the role corresponding to sequence 1 is role A, and the role corresponding to sequence 2 is role B. If the role of the client is role A, then sequence 1 is used as the client's target event sequence.

Step 204: Send the target event sequence to the client.

The following specifically introduces the specific process of determining the sequence of key events by counting historical business information of different roles, as shown in Figure 3, including the following steps:

Step 301: For each role, obtain historical business information of the role.

Specifically, the historical service information includes historical subscription events and the sequence between historical subscription events. For example, the background role of the passenger APP is set to passengers, and the corresponding business is to provide passengers with information related to taking the plane. Therefore, historical business information includes at least the passenger's inquiries on ticketing, security, baggage handling and other events and queries on the passenger APP The sequence of events such as check-in, security check and baggage handling. For another example, set the role of the airline system to airlines, and the corresponding business is to provide airlines with flight information. Therefore, historical business information includes at least the airline's inquiries about cabin operations, flight operations, and customer services on the airline system. Events and query the sequence of events such as cabin door operations, flight operations, and customer service.

Step 302: Perform frequency statistics on the sequence of historical subscription events to determine the key event sequence of the role.

Specifically, frequency statistics are performed on the order between historical subscription events, that is, the number of times the user first queries event 1 and then queries event 2. Exemplarily, when the role is a passenger, the frequency statistics of candidate order A and candidate order B are performed. Candidate order A and candidate order B include corresponding historical subscription events. It should be noted that the specific implementation is not only for the above two The order for frequency statistics can also include other candidate orders.

Specifically, for the candidate sequence A: event 1→event 2→event 3.

By counting the historical query records of passengers on the passenger APP, the statistical value of the frequency of passengers from query event 1 to query event 2 is 5, and the statistical value of the frequency of passengers from query event 2 to query event 3 is 3. Then, by calculating the sum of the statistical values of all orders, the total frequency statistical value of candidate order A is 8.

For candidate order B: event 4→event 5→event 6.

By counting the historical query records of passengers on the passenger APP, it can be seen that the statistical value of the frequency of passengers from query event 4 to query event 5 is 1, and the statistical value of the frequency of passengers from query event 5 to query event 6 is 0. Then, by calculating the sum of the statistical values of all orders, the total frequency statistical value of candidate order B is 1.

Through comparison, it can be seen that for the client whose role is passenger, the more concerned sequence is candidate sequence A, so candidate sequence A can be determined as the key event sequence of the role (passenger), and then candidate sequence A and role (passenger) Save accordingly.

Exemplarily, when the role is an airline, frequency statistics are performed on candidate order A and candidate order B, specifically, for candidate order A: event 1→event 2→event 3.

By counting the historical query records of airlines in the airline system, the statistical value of the frequency from query event 1 to query event 2 of the airline is 1, and the statistical value of frequency from query event 2 to query event 3 of the airline is 1. Then, by calculating the sum of the statistical values of all orders, the total frequency statistical value of candidate order A is 2.

For candidate order B: event 4→event 5→event 6.

By counting the historical query records of airlines in the airline system, the statistical value of the frequency from query event 4 to query event 5 of the airline is 6, and the statistical value of frequency from query event 5 to query event 6 of the airline is 4. Then, by calculating the sum of the statistical values of all orders, the total frequency statistical value of candidate order B is 10.

Through comparison, it can be seen that for the client whose role is an airline, the more concerned sequence is candidate sequence B, so candidate sequence B can be determined as the key event sequence of the role (airline), and then candidate sequence B and role ( Airlines) corresponding to save.

Through statistical analysis of the sequence of events concerned by each type of role, the key event sequence corresponding to each type of role is obtained. Therefore, when the client's subscription request is received, the key event sequence of the client is returned according to the role of the client, so as to achieve rapid response to the client And the effect of increasing the throughput of the entire system.

In a possible implementation manner, after determining the key event sequence of each role, the intermediate server may cache the key event sequence of each role. For example, for the theme M, when the intermediate server determines that the key event sequence of the role (passenger) is the candidate sequence A, it caches the candidate sequence A and the role (passenger) correspondingly. When the intermediate server determines that the key event sequence of the role (airline) is the candidate sequence B, it caches the candidate sequence B and the role (airline) correspondingly, and the topic M includes two cached key event sequences.

When receiving the subscription request sent by the client, the intermediate server obtains the target event sequence corresponding to the client from all the key event sequences corresponding to the cached target topic according to the role of the client. Exemplarily, if the role of the client is a passenger, from the two key event sequences corresponding to the theme M in the cache, the key event sequence corresponding to the role (passenger) is determined to be the candidate sequence A. If the role of the client is an airline, from the two key event sequences corresponding to the topic M in the cache, the key event sequence corresponding to the role (airline) is determined to be the candidate order B.

Since the statistical analysis of the sequence of events concerned by each type of role is performed, after the key event sequence corresponding to each type of role is obtained, the key event sequence corresponding to the role is cached locally, so when subsequent subscription requests sent by the client are received, you can directly The cached key event sequence is returned to the client, so that in the case of a surge in business, business pressure can be relieved in time and the normal and stable operation of the business can be guaranteed.

In a possible implementation manner, after determining the key event sequence of each role, the intermediate server may save the key event sequence of each role in the blockchain. For example, for theme M, when the intermediate server determines that the key event sequence of the role (passenger) is the candidate sequence A, the candidate sequence A and the role (passenger) are correspondingly saved in the blockchain. When the intermediate server determines that the key event sequence of the role (airline) is the candidate sequence B, the candidate sequence B and the role (airline) are correspondingly saved in the blockchain.

When receiving the subscription request sent by the client, the intermediate server obtains the target event sequence corresponding to the client from all the key event sequences corresponding to the target topic stored in the blockchain according to the role of the client. Exemplarily, if the role of the client is a passenger, the key event sequence corresponding to the role (passenger) is obtained from the blockchain, that is, candidate sequence A, and then candidate sequence A is sent to the client as the target event sequence. If the role of the client is an airline, the key event sequence corresponding to the role (airline) is obtained from the blockchain, that is, candidate sequence B, and then candidate sequence B is sent to the client as the target event sequence.

In addition, the roles and corresponding key event sequences saved in the blockchain can be shared with other institutions, so that other institutions do not need to re-analyze the roles and the events that the role focuses on, but directly pull them from the blockchain according to the role of the client. Take the corresponding key event sequence to bring convenience to other institutions.

In order to better explain the embodiments of the present invention, the following describes a blockchain-based event subscription method provided by the embodiments of the present invention in combination with specific implementation scenarios. The method consists of client 1, server 1, blockchain, and server 2. Perform interactively with client 2. As shown in Figure 4, the method includes the following steps:

In step 401, the server 1 obtains historical service information of each role. The historical service information includes historical subscription events and the sequence between historical subscription events.

Specifically, for any topic, the roles of consumers who subscribe to the topic can be defined. For example, the roles of consumers who subscribe to topic N include role A and role B. If the service provided by the role A for the user is the service P, the historical service information when the role A provides the service P for the user is acquired. If the service provided by role B for the user is service Q, then obtain the historical service information when role B provides the user with service Q. The events corresponding to service P and service Q are different. Therefore, the historical subscription events and history of role A The order between subscription events is also different from the historical subscription events of role B and the order between historical subscription events.

In step 402, the server 1 performs frequency statistics on the sequence of historical subscription events, and determines the key event sequence of each role.

Exemplarily, the set theme N includes event 1, event 2, event 3, event 4, event 5, and event 6. Use the historical business information of role A to perform frequency statistics on sequence 1 and sequence 2.

For sequence 1: event 1→event 3→event 5→event 6.

Through the statistical role A to provide the user with the historical record of the service P, it can be seen that the user’s frequency from query event 1 to query event 3 is 5, and the user’s frequency from query event 3 to query event 5 is 3. The frequency statistic value from 5 to query event 6 is 1. Then, by calculating the sum of the statistical values of all orders, the total frequency statistical value of sequence 1 is 9.

For sequence 2: event 1→event 2→event 4→event 6.

Through the statistical role A to provide the user with the historical record of the service P, it can be seen that the statistical value of the frequency of the user from query event 1 to query event 2 is 1, and the statistical value of the frequency of the user from query event 2 to query event 4 is 1. The statistical value of frequency from 4 to 6 is 0. Then, by calculating the sum of the statistical values of all orders, the total frequency statistical value of sequence 2 is 2.

Through comparison, it can be seen that for character A, the more concerned sequence is sequence 1, so sequence 1 can be determined as the key event sequence of character A. Based on the same method described above, the key event sequence of character B can be determined, assuming that the statistical result is that sequence 2 is the key event sequence of character B.

In step 403, the server 1 caches the role and the corresponding key event sequence.

Cache role A and sequence 1 correspondingly, and cache role B and sequence 2.

In step 404, the server 1 saves the role and the corresponding key event sequence in the blockchain.

The role A and sequence 1 are correspondingly saved in the blockchain, and the role B and sequence 2 are correspondingly saved in the blockchain.

Step 405: The client 1 sends a first subscription request to the server 1.

In step 406, the server 1 determines all key event sequences corresponding to topic N and the role corresponding to each key event sequence from the cached data.

Specifically, the server 1 determines that the target topic is topic N according to the first subscription request, all key event sequences corresponding to topic N are sequence 1 and sequence 2, the role corresponding to sequence 1 is role A, and the role corresponding to sequence 2 is role B.

In step 407, the server 1 determines the target event sequence corresponding to the client 1 from all the key event sequences corresponding to the topic N according to the role corresponding to the client 1.

If the role of client 1 is role A, sequence 1 is acquired as the target event sequence. If the role of client 1 is role B, sequence 2 is acquired as the target event sequence.

Step 408: The server 1 sends the target event sequence corresponding to the client 1 to the client 1.

Step 409: The client 2 sends a second subscription request to the server 2.

In step 410, the server 2 obtains the target event sequence corresponding to the client 2 from all the key event sequences corresponding to the target theme stored in the blockchain according to the role of the client 2.

In step 411, the blockchain returns the target event sequence corresponding to the client 2 to the server 2.

If the role of client 2 is role A, sequence 1 is acquired as the target event sequence. If the role of client 2 is role B, sequence 2 is acquired as the target event sequence.

In step 412, the server 2 sends the target event sequence corresponding to the client 2 to the client 2.

Based on the same technical concept, an embodiment of the present invention provides a blockchain-based event subscription device. As shown in FIG. 5, the blockchain-based event subscription device 500 includes:

The receiving module 501 is configured to receive a subscription request sent by the client;

The processing module 502 is configured to determine the target topic according to the subscription request, and determine all the key event sequences corresponding to the target topic and the role corresponding to each key event sequence, the key event sequence is based on statistics of historical business of different roles Information confirmed;

The query module 503 is configured to determine the target event sequence corresponding to the client from all the key event sequences corresponding to the target theme according to the role corresponding to the client;

The sending module 504 is configured to send the target event sequence to the client.

Optionally, the processing module 502 is specifically configured to:

Optionally, the processing module 502 is further configured to:

Save the key event sequence of each role to the blockchain.

Optionally, the processing module 502 is further configured to:

Cache the key event sequence of each role.

Based on the same technical concept, an embodiment of the present invention provides a computer device. As shown in FIG. 6, it includes at least one processor 601 and a memory 602 connected to the at least one processor. The embodiment of the present invention does not limit the processor. For the specific connection medium between the 601 and the memory 602, the connection between the processor 601 and the memory 602 in FIG. 6 is taken as an example. The bus can be divided into address bus, data bus, control bus, etc.

In the embodiment of the present invention, the memory 602 stores instructions that can be executed by at least one processor 601. By executing the instructions stored in the memory 602, the at least one processor 601 can execute the aforementioned blockchain-based event subscription method. A step of.

Among them, the processor 601 is the control center of the terminal device, which can use various interfaces and lines to connect to various parts of the terminal device, and subscribe to events by running or executing instructions stored in the memory 602 and calling data stored in the memory 602 . Optionally, the processor 601 may include one or more processing units, and the processor 601 may integrate an application processor and a modem processor. The application processor mainly processes the operating system, user interface, and application programs, etc. The adjustment processor mainly deals with wireless communication. It can be understood that the foregoing modem processor may not be integrated into the processor 601. In some embodiments, the processor 601 and the memory 602 may be implemented on the same chip, and in some embodiments, they may also be implemented on separate chips.

The processor 601 may be a general-purpose processor, such as a central processing unit (CPU), a digital signal processor, an application specific integrated circuit (ASIC), a field programmable gate array or other programmable logic devices, discrete gates or transistors Logic devices and discrete hardware components can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present invention. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present invention may be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.

The memory 602, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. The memory 602 may include at least one type of storage medium, for example, may include flash memory, hard disk, multimedia card, card type memory, random access memory (Random Access Memory, RAM), static random access memory (Static Random Access Memory, SRAM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), magnetic memory, disk , CD, etc. The memory 602 is any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto. The memory 602 in the embodiment of the present invention may also be a circuit or any other device capable of realizing a storage function, for storing program instructions and/or data.

Based on the same technical concept, the embodiments of the present invention provide a computer-readable storage medium that stores a computer program executable by a computer device. When the program runs on the computer device, the computer device executes a region-based The steps of the event subscription method of the blockchain.

Based on the same inventive concept, the embodiments of the present application provide a computer program product containing instructions, and the embodiments of the present invention provide a computer program product containing instructions. The computer program product includes storage on a non-transitory computer-readable storage medium The computer program includes program instructions that, when executed by a computer, cause the computer to execute the steps of the blockchain-based event subscription method.

Those skilled in the art should understand that the embodiments of the present invention may be provided as methods or computer program products. Therefore, the present invention may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

The present invention is described with reference to flowcharts and/or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and/or block in the flowchart and/or block diagram, and the combination of processes and/or blocks in the flowchart and/or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing equipment to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing equipment are generated It is a device that realizes the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device. The device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment. The instructions provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram.

Although the preferred embodiments of the present invention have been described, those skilled in the art can make additional changes and modifications to these embodiments once they learn the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications falling within the scope of the present invention.

Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. In this way, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalent technologies, the present invention is also intended to include these modifications and variations.

Claims

A blockchain-based event subscription method, which is characterized in that it includes:

Receive the subscription request sent by the client;

Determine the target theme according to the subscription request, and determine all the key event sequences corresponding to the target theme and the roles corresponding to each key event sequence, the key event sequences are determined by counting historical business information of different roles;

Determine the target event sequence corresponding to the client from all key event sequences corresponding to the target theme according to the role corresponding to the client;

Sending the target event sequence to the client.
The method according to claim 1, wherein the key event sequence is determined by counting historical business information of different roles, and comprises:

For each role, acquiring historical business information of the role, where the historical business information includes historical subscription events and the sequence between historical subscription events;

Perform frequency statistics on the sequence between the historical subscription events to determine the key event sequence of the role.
The method of claim 2, further comprising:

Save the key event sequence of each role to the blockchain.
The method of claim 2, further comprising:

Cache the key event sequence of each role.
A blockchain-based event subscription device, which is characterized in that it includes:

The receiving module is used to receive the subscription request sent by the client;

The processing module is used to determine the target theme according to the subscription request, and determine all the key event sequences corresponding to the target theme and the role corresponding to each key event sequence, the key event sequence is based on statistics of historical business information of different roles definite;

A query module, configured to determine the target event sequence corresponding to the client from all key event sequences corresponding to the target theme according to the role corresponding to the client;

The sending module is used to send the target event sequence to the client.
The device according to claim 5, wherein the processing module is specifically configured to:

For each role, acquiring historical business information of the role, where the historical business information includes historical subscription events and the sequence between historical subscription events;

Perform frequency statistics on the sequence between the historical subscription events to determine the key event sequence of the role.
The device of claim 6, wherein the processing module is further configured to:

Save the key event sequence of each role to the blockchain.
The device of claim 6, wherein the processing module is further configured to:

Cache the key event sequence of each role.
A computer device, comprising a memory, a processor, and a computer program stored on the memory and running on the processor, wherein the processor executes the program when the program is executed by any one of claims 1 to 4 The steps of the method.
A computer-readable storage medium, characterized in that it stores a computer program that can be executed by a computer device, and when the program runs on a computer device, the computer device executes the method described in any one of claims 1 to 4 A step of.
A computer program product, characterized in that, the computer program product includes a calculation program stored on a non-transitory computer-readable storage medium, the computer program includes program instructions, and when the program instructions are executed by a computer, The computer executes the method described in any one of claims 1 to 4.