WO2020211629A1 - Short link message monitoring method and apparatus based on blockchain - Google Patents

Abstract

Disclosed are a short link message monitoring method and apparatus based on a blockchain. The method comprises: acquiring a first monitoring request sent by a client, wherein the first monitoring request comprises a subject name for monitoring and a message pushing address; generating a monitoring ID of the client, and storing the monitoring ID of the client and the subject name by means of a client management contract; determining an event message and a first monitoring ID according to the subject name; and respectively sending, according to the message pushing address and the first monitoring ID, a first monitoring result to the client and a client storing the event message. When a received monitoring request does not comprise a monitoring ID, which indicates that this monitoring task is a new monitoring task, a blockchain node can generate a monitoring ID for distinguishing, when a monitoring request is subsequently received, whether same is a new monitoring task or a continuation of a previous monitoring task, such that the amount of maintenance of a monitoring client by the blockchain node is reduced, and the monitoring efficiency is improved.

Description

Method and device for monitoring short link messages based on blockchain

Cross references to related applications

This application requires the priority of a Chinese patent application filed with the Chinese Patent Office, the application number is 201910302089.X, and the application name is "a method and device for monitoring short link messages based on blockchain" on April 16, 2019. The entire content is incorporated into this application by reference.

Technical field

The embodiments of the present invention relate to the field of financial technology (Fintech), and in particular to a method and device for monitoring short link messages based on a blockchain (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 transforming to Finteh. The blockchain news subscription technology is no exception, but due to the security of the financial and payment industries , Real-time requirements, but also higher requirements for technology. At present, when the client initiates the monitoring of event messages in the blockchain in the form of short link access based on the subject name, the blockchain cannot distinguish whether the current monitoring task is a new monitoring task or a previous monitoring task. The client session of this monitoring task is stored and maintained, which will cause the blockchain node to maintain a large amount of client session information.

Summary of the invention

The embodiment of the present invention provides a short link message monitoring method and device based on a block chain, which is used to distinguish the state of monitoring tasks, reduce the maintenance amount of the block chain node to the monitoring client, and improve the monitoring efficiency.

The embodiment of the present invention provides a method for monitoring short link messages based on blockchain, including:

Acquiring a first monitoring request sent by the client, where the first monitoring request includes the name of the monitored topic and the message push address;

Generate the monitoring ID of the client, and store the monitoring ID of the client and the subject name through a client management contract; the client management contract is used to manage the client that initiates event monitoring and the subject name of the monitoring;

Determine the event message and the first monitoring ID according to the subject name, where the first monitoring ID is the monitoring ID of the client storing the event message;

Send a first monitoring result to the client and the client storing the event message according to the message push address and the first monitoring ID, and the first monitoring result includes the event message and the monitoring ID .

In the above technical solution, when the blockchain node does not include the monitoring ID in the received monitoring request, it indicates that the current monitoring task is a new monitoring task, and the monitoring ID can be generated to distinguish between subsequent monitoring requests. Whether it is a new monitoring task or the continuation of the previous monitoring task, thereby reducing the amount of maintenance of the monitoring client by the blockchain node and improving the monitoring efficiency.

Optionally, the method further includes:

Periodically send heartbeat information to the client, where the heartbeat information includes the monitored topic name and the client's monitoring ID, so that the client can determine the survival state of the blockchain node.

Optionally, after the periodically sending the heartbeat information to the client, the method further includes:

Acquire a second monitoring request sent by the client, the second monitoring request includes the monitored topic name, the message push address, and the monitoring ID of the client; the second monitoring request is the client After not receiving the heartbeat information periodically sent by the blockchain node;

Determine the event message to continue monitoring according to the monitoring ID of the client and the subject name of the monitoring;

According to the message push address and the first monitoring ID, a second monitoring result is sent to the client and the client storing the event message respectively, and the second monitoring result includes the event message that continues to be monitored and all The monitoring ID.

In the above technical solution, since the second monitoring request includes the monitoring ID, it indicates that this monitoring task is to continue the previous monitoring task, and there is no need to store the topic name and the monitoring ID, thereby reducing the amount of maintenance of the monitoring client by the blockchain node , Improve monitoring efficiency.

Optionally, the determining the event message to continue monitoring according to the monitoring ID of the client and the subject name of the monitoring includes:

Match the monitor ID of the client and the subject name of the monitor with the client management contract. If the match is successful, continue to monitor the event message to determine the event message to continue to monitor; otherwise, confirm Failed to monitor.

Optionally, the method further includes:

If the first monitoring ID is the same as the monitoring ID of the client, the monitoring result is sent to the client.

Correspondingly, an embodiment of the present invention also provides a short link message monitoring device based on a blockchain, including:

The obtaining unit is configured to obtain a first monitoring request sent by the client, where the first monitoring request includes the monitored topic name and the message push address;

The processing unit is used to generate the monitoring ID of the client, and store the monitoring ID of the client and the subject name through a client management contract; the client management contract is used to manage the client that initiates event monitoring and The name of the monitored topic; an event message and a first monitor ID are determined according to the topic name, where the first monitor ID is the monitor ID of the client that stores the event message;

The sending unit is configured to send a first monitoring result to the client and the client storing the event message according to the message push address and the first monitoring ID, and the first monitoring result includes the event message And the monitoring ID.

Optionally, the processing unit is further configured to:

Control the sending unit to periodically send heartbeat information to the client. The heartbeat information includes the monitored topic name and the client's monitoring ID, so that the client can determine the survival status of the blockchain node .

Optionally, the processing unit is further configured to:

After the periodic sending of heartbeat information to the client, the acquiring unit is controlled to acquire a second monitoring request sent by the client, where the second monitoring request includes the monitored topic name and the message Push address and the listening ID of the client; the second listening request is sent after the client does not receive the heartbeat information periodically sent by the blockchain node;

Determine the event message to continue monitoring according to the monitoring ID of the client and the subject name of the monitoring;

Control the sending unit to send a second monitoring result to the client and the client storing the event message according to the message push address and the first monitoring ID, and the second monitoring result includes the continued monitoring The event message and the monitoring ID.

Optionally, the processing unit is specifically configured to:

Match the monitor ID of the client and the subject name of the monitor with the client management contract. If the match is successful, continue to monitor the event message to determine the event message to continue to monitor; otherwise, confirm Failed to monitor.

Optionally, the processing unit is further configured to:

If the first monitoring ID is the same as the monitoring ID of the client, the sending unit is controlled to send the monitoring result to the client.

Correspondingly, an embodiment of the present invention also provides a computing device, including:

At least one memory for storing program instructions;

At least one processor is configured to call program instructions stored in the memory, and execute the above-mentioned block chain-based short link message monitoring method according to the obtained program.

Correspondingly, the embodiment of the present invention also provides a computer-readable non-volatile storage medium with a computer program stored thereon. When the computer reads and executes the computer program, the computer executes the above-mentioned blockchain-based Short link message monitoring method.

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, without creative work, other drawings can be obtained from these drawings.

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

2 is a schematic flowchart of a method for monitoring short link messages based on blockchain according to an embodiment of the present invention;

3 is a schematic flowchart of another method for monitoring short link messages based on blockchain according to an embodiment of the present invention;

4 is a schematic structural diagram of a short link message monitoring device based on a blockchain provided by an embodiment of the present invention;

Fig. 5 is a schematic structural diagram of a computing device provided by an embodiment of the present invention.

detailed description

In order to make the objectives, technical solutions and advantages of the present invention clearer, the present invention will be further described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all of them. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of the present invention.

FIG. 1 exemplarily shows a system architecture to which an embodiment of the present invention is applicable. The system architecture may include multiple clients 100 and a blockchain system 200.

The client 100 is used to communicate with the blockchain system 200, send the generated data to the blockchain system 200 for storage, and monitor event information through the blockchain system 200.

The blockchain system 200 is composed of multiple blockchain nodes 210 that communicate with the client 100 to store the data sent by the client 100, and after receiving the client 100's listening request, feedback the monitoring result to the client 100 . The multiple blockchain nodes 210 can be connected to each other for communication, and each blockchain node includes multiple blocks, and the blocks are used to store data that the client 100 needs to monitor.

It should be noted that the structure shown in FIG. 1 is only an example, which is not limited in the embodiment of the present invention.

Based on the above description, FIG. 2 exemplarily shows the flow of a method for monitoring short link messages based on a blockchain provided by an embodiment of the present invention. The flow can be executed by a short link message monitoring device based on blockchain. The device may be a blockchain node in the blockchain system 200. The following describes the process of short link message monitoring based on the blockchain by monitoring the client and notifying the client to interact with the blockchain node.

As shown in Figure 2, the process specifically includes:

Step 201: The monitoring client sends a first monitoring request to the blockchain node.

In the embodiment of the present invention. A listening client is a client that monitors event information, or it can be said to be a client that subscribes to event information. The first listening request sent by the listening client may include the listening topic name (topicName) and the message push address. The topic name is to be able to monitor event information corresponding to the topic name, and the message push address is to make the zone After the block chain node determines the event information corresponding to the topic name, it sends the event message to the listening client through the message push address.

It should be noted that the message push address can be a URL (Uniform Resource Locator, Uniform Resource Locator), or other links used for message push. When the listening client sends the first listening request, it can be sent to the blockchain node in the form of http body, that is to say, the first listening request is sent through a short link, such as https, jsonrpc and other short link access . The subject name is the subject name of the monitoring event, such as transfer, transaction, repayment, etc.

In step 202, the blockchain node generates the monitoring ID of the monitoring client, and stores the monitoring ID of the monitoring client and the subject name through the client management contract.

In the above step 201, after receiving the first monitoring request sent by the monitoring client, the blockchain node can generate the monitoring ID of the monitoring client. When generating the monitoring ID, a set of random numbers can be generated, for example, a 256-bit random number is generated through the Linux system. The monitoring ID here can be referred to as subscribeID.

In the embodiment of the present invention, the client management contract is used to manage the client that initiates event monitoring and the subject name of the monitoring, as shown in Table 1.

Table 1

The listening ID of the listening client	Subject name
Client A	Transfer

Client B	consumption
Client C	Repayment
...	...

For example, the subject name of the event that the client A needs to monitor is transfer, that is, the blockchain node needs to feed back the monitoring result of the event message related to the transfer to the client.

When the blockchain node stores the monitoring ID and topic name of the monitoring client, it can be stored in the key (subscribeID) and value (topicName) data structure. Of course, it can also be stored in the data structure of a map, which is not specifically limited in the embodiment of the present invention.

Step 203: The blockchain node determines the event message and the first monitoring ID according to the subject name.

After the blockchain node stores the monitoring ID and topic name of the monitoring client through the client management contract, it can execute the monitoring task and monitor the event message corresponding to the topic name. Specifically, according to the topic name, the event messages related to the topic name in the block can be polled.

While determining the event message, the blockchain node can also determine the monitoring ID of the client storing the event message, that is, the first monitoring ID, that is, the monitoring ID of the notification client. After receiving the storage message request sent by the notification client, the blockchain node stores the listening ID of the notification client.

Step 204: The blockchain node sends the monitoring result to the monitoring client and the notification client respectively.

In step 203, after the blockchain node determines the event message, it can send the monitoring result to the monitoring client and the notification client. The monitoring result may include the event message related to the topic name and the monitoring ID of the monitoring client. The purpose of sending the monitoring ID of the monitoring client to the notification client is to notify the notification client who listened to its stored event messages.

The blockchain node may send the monitoring result to the monitoring client according to the message push address received in step 201, and send the monitoring result to the notification client according to the first monitoring ID.

It should be noted that, when the above-mentioned first monitoring ID is the same as the monitoring ID of the monitoring client, only the monitoring result needs to be sent to the monitoring client. This situation indicates that the client storing the event message is the listening client.

Optionally, the blockchain node can also periodically send heartbeat information to the monitoring client, the heartbeat information includes the monitored subject name and the monitoring ID of the monitoring client, so that the monitoring client can determine the survival of the blockchain node status. Among them, the period of sending heartbeat information can be set based on experience.

When the monitoring client does not receive the heartbeat information in one cycle, it indicates that there is a problem with the blockchain node. At this time, the event monitoring request can be re-initiated. Specifically, the process shown in Figure 3 may include:

Step 301: The monitoring client sends a second monitoring request to the blockchain node.

The second monitoring request may include the name of the monitored topic, the message push address, and the monitoring ID of the monitoring client. By monitoring the client's monitoring ID, the blockchain node can know whether the current monitoring task is a new monitoring task or a continuing monitoring task. The second monitoring request is sent after the monitoring client receives the periodically sent heartbeat information.

Step 302: The blockchain node determines the event message to continue monitoring according to the monitoring ID of the monitoring client and the subject name of the monitoring.

The blockchain node will monitor the client's monitor ID and the subject name of the monitor, and match it with the client management contract. If the match is successful, it indicates that the current monitoring task is to continue the previous monitoring task, so continue to monitor the event message, confirm The event message to continue monitoring is output. If the match is unsuccessful, it is determined that the monitoring has failed.

Step 303: The blockchain node sends the second monitoring result to the monitoring client and the notification client respectively.

The second monitoring result may include the event message related to the topic name and the monitoring ID of the monitoring client. The purpose of sending the monitoring ID of the monitoring client to the notification client is to notify the notification client who listened to its stored event messages.

The blockchain node may send the second monitoring result to the monitoring client according to the message push address received in step 301, and send the second monitoring result to the notification client according to the first monitoring ID.

It should be noted that when the first monitoring ID is the same as the monitoring ID of the monitoring client, only the second monitoring result needs to be sent to the monitoring client. This situation indicates that the client storing the event message is the listening client.

The embodiment of the present invention shows that the first listening request sent by the client is obtained, the first listening request includes the listening topic name and the message push address, the listening ID of the client is generated, and the listening ID and topic name of the client are combined through the client management contract. For storage, the client management contract is used to manage the client that initiates event monitoring and the subject name of the listener. The event message and the first listener ID are determined according to the subject name. The first listener ID is the listener ID of the client that stores the event message. The message push address and the first monitoring ID respectively send a first monitoring result to the client and the client storing the event message, and the first monitoring result includes the event message and the monitoring ID. When the blockchain node does not include the monitoring ID in the received monitoring request, it indicates that the current monitoring task is a new monitoring task. The monitoring ID can be generated to distinguish the new monitoring task when subsequent monitoring requests are received. Continue the previous monitoring task, thereby reducing the amount of maintenance of the blockchain node on the monitoring client and improving the monitoring efficiency.

It should be noted that the monitoring client and notification client in the embodiment of the present invention may be one process on one machine, or may be different processes on multiple machines.

Based on the same technical concept, FIG. 4 exemplarily shows the structure of a block chain-based short link message monitoring device provided by an embodiment of the present invention, which can execute the process of block chain-based short link message monitoring . The device may be the blockchain node 210 in the above-mentioned blockchain system 200.

As shown in Figure 4, the device specifically includes:

The obtaining unit 401 is configured to obtain a first monitoring request sent by a client, where the first monitoring request includes the monitored topic name and message push address;

The processing unit 402 is configured to generate the monitoring ID of the client, and store the monitoring ID of the client and the subject name through the client management contract; the client management contract is used to manage the client that initiates event monitoring And the subject name of the monitoring; determine the event message and the first monitoring ID according to the subject name, where the first monitoring ID is the monitoring ID of the client storing the event message;

The sending unit 403 is configured to send a first monitoring result to the client and the client storing the event message according to the message push address and the first monitoring ID, and the first monitoring result includes the event Message and the monitoring ID.

Optionally, the processing unit 402 is further configured to:

Control the sending unit 403 to periodically send heartbeat information to the client. The heartbeat information includes the monitored topic name and the client's monitoring ID, so that the client can determine the survival of the blockchain node status.

Optionally, the processing unit 402 is further configured to:

After the periodic sending of heartbeat information to the client, the acquiring unit 401 is controlled to acquire a second monitoring request sent by the client, where the second monitoring request includes the monitored subject name, The message push address and the listening ID of the client; the second listening request is sent after the client does not receive the heartbeat information periodically sent by the blockchain node;

Determine the event message to continue monitoring according to the monitoring ID of the client and the subject name of the monitoring;

The sending unit 403 is controlled to send a second monitoring result to the client and the client storing the event message according to the message push address and the first monitoring ID, and the second monitoring result includes the continued The monitored event message and the monitoring ID.

Optionally, the processing unit 402 is specifically configured to:

Match the monitor ID of the client and the subject name of the monitor with the client management contract. If the match is successful, continue to monitor the event message to determine the event message to continue to monitor; otherwise, determine Failed to monitor.

Optionally, the processing unit 402 is further configured to:

If the first monitoring ID is the same as the monitoring ID of the client, the sending unit 403 is controlled to send the monitoring result to the client.

Based on the same technical concept, an embodiment of the present invention also provides a computing device, as shown in FIG. 5, including: a transceiver 501, a processor 502, and a memory 503, where:

The transceiver 501 may include baseband processing components, radio frequency processing components and other equipment according to actual needs, for transmitting relevant information;

The memory 503 stores one or more executable programs and is used to configure the processor 502;

The processor 502 is configured with one or more executable programs, and the one or more executable programs are used to execute the foregoing blockchain-based short link message monitoring method.

Based on the same technical concept, the embodiments of the present invention also provide a computer-readable non-volatile storage medium with a computer program stored thereon. When the computer reads and executes the computer-readable program, the computer can execute the foregoing Short link message monitoring method based on blockchain.

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

1. A method for monitoring short link messages based on blockchain, which is characterized in that it includes:

   Acquiring a first monitoring request sent by the client, where the first monitoring request includes the name of the monitored topic and the message push address;

   Generate the monitoring ID of the client, and store the monitoring ID of the client and the subject name through a client management contract; the client management contract is used to manage the client that initiates event monitoring and the subject name of the monitoring;

   Determine the event message and the first monitoring ID according to the subject name, where the first monitoring ID is the monitoring ID of the client storing the event message;

   Send a first monitoring result to the client and the client storing the event message according to the message push address and the first monitoring ID, and the first monitoring result includes the event message and the monitoring ID .
2. The method of claim 1, wherein the method further comprises:

   Periodically send heartbeat information to the client, where the heartbeat information includes the monitored topic name and the client's monitoring ID, so that the client can determine the survival state of the blockchain node.
3. The method according to claim 2, wherein after the periodically sending the heartbeat information to the client, the method further comprises:

   Acquire a second monitoring request sent by the client, the second monitoring request includes the monitored topic name, the message push address, and the monitoring ID of the client; the second monitoring request is the client After not receiving the heartbeat information periodically sent by the blockchain node;

   Determine the event message to continue monitoring according to the monitoring ID of the client and the subject name of the monitoring;

   According to the message push address and the first monitoring ID, a second monitoring result is sent to the client and the client storing the event message respectively, and the second monitoring result includes the event message that continues to be monitored and all The monitoring ID.
4. The method of claim 3, wherein the determining the event message to continue monitoring according to the monitoring ID of the client and the subject name of the monitoring comprises:

   Match the monitor ID of the client and the subject name of the monitor with the client management contract. If the match is successful, continue to monitor the event message to determine the event message to continue to monitor; otherwise, confirm Failed to monitor.
5. The method according to any one of claims 1 to 4, wherein the method further comprises:

   If the first monitoring ID is the same as the monitoring ID of the client, the monitoring result is sent to the client.
6. A block chain-based short link message monitoring device is characterized in that it comprises:

   The obtaining unit is configured to obtain a first monitoring request sent by the client, where the first monitoring request includes the monitored topic name and the message push address;

   The processing unit is used to generate the monitoring ID of the client, and store the monitoring ID of the client and the subject name through a client management contract; the client management contract is used to manage the client that initiates event monitoring and The name of the monitored topic; an event message and a first monitor ID are determined according to the topic name, where the first monitor ID is the monitor ID of the client that stores the event message;

   The sending unit is configured to send a first monitoring result to the client and the client storing the event message according to the message push address and the first monitoring ID, and the first monitoring result includes the event message And the monitoring ID.
7. The device according to claim 6, wherein the processing unit is further configured to:

   Control the sending unit to periodically send heartbeat information to the client. The heartbeat information includes the monitored topic name and the client's monitoring ID, so that the client can determine the survival status of the blockchain node .
8. The device according to claim 7, wherein the processing unit is further configured to:

   After the periodic sending of heartbeat information to the client, the acquiring unit is controlled to acquire a second monitoring request sent by the client, where the second monitoring request includes the monitored topic name and the message Push address and the listening ID of the client; the second listening request is sent after the client does not receive the heartbeat information periodically sent by the blockchain node;

   Determine the event message to continue monitoring according to the monitoring ID of the client and the subject name of the monitoring;

   Control the sending unit to send a second monitoring result to the client and the client storing the event message according to the message push address and the first monitoring ID, and the second monitoring result includes the continued monitoring The event message and the monitoring ID.
9. The device according to claim 8, wherein the processing unit is specifically configured to:

   Match the monitor ID of the client and the subject name of the monitor with the client management contract. If the match is successful, continue to monitor the event message to determine the event message to continue to monitor; otherwise, confirm Failed to monitor.
10. The device according to any one of claims 6 to 9, wherein the processing unit is further configured to:

    If the first monitoring ID is the same as the monitoring ID of the client, the sending unit is controlled to send the monitoring result to the client.
11. A computing device, characterized by comprising:

    At least one memory for storing program instructions;

    At least one processor is configured to call program instructions stored in the memory, and execute the method according to any one of claims 1 to 5 according to the obtained program.
12. A computer-readable non-volatile storage medium is characterized in that a computer program is stored on the computer-readable non-volatile storage medium, and when the computer reads and executes the computer program, the computer executes the The method of any one of 1 to 5 is required.

Images