WO2021022714A1 - Message processing method for cross-block chain node, device, apparatus and medium - Google Patents

Abstract

The present disclosure provides a message processing method for cross-block chain node, a device, an apparatus and a medium, relating to the technical field of computers. The method comprises: starting a message queue monitoring process according to a starting node in a block chain, and creating a node index area through the message queue monitoring process; acquiring a current message in a message queue of the block chain node through the message queue monitoring process; acquiring a target parameter of the current message according to the node index area, and calling a system interface according to the target parameter so as to configure the starting node according to node attribute of a request node corresponding to the current message; updating a node label field in a target file corresponding to the request node through the node attribute of the starting node, so as to process the current message in the request node through the message queue monitoring process in the starting node. The technical solution of the embodiment of the present disclosure can correctly update the node label field of the file when the request node is changed, improving the message processing efficiency of the long connection process.

Description

Method, device, equipment and medium for processing messages across blockchain nodes Technical field

This application claims the priority of the Chinese patent application CN 201910713843.9 filed on August 2, 2019 with the title of "message processing method and device, equipment and medium across blockchain nodes", and the entire contents of which are incorporated herein by reference Here.

The present disclosure relates to the field of computer technology, and in particular, to a message processing method across blockchain nodes, a message processing device across blockchain nodes, electronic equipment, and computer-readable storage media.

Background technique

With the rapid development of technology, blockchain technology has received more and more attention. Blockchain technology (distributed ledger technology) is a decentralized distributed database technology with many characteristics such as openness, transparency, non-tampering, and trustworthiness.

At present, when a blockchain node processes a message queue, it usually starts a long connection process for processing. When a pending message is detected in the message queue, the message is processed. When a large number of messages enter the message queue at the same time, the messages in the message queue can be processed one by one through the long connection process. The inventor realized that: when the long connection process is started, the startup blockchain node will be set as the "current node" by default, and the input/output program (input/output, referred to as IO program) will use the "current node" to update the file The node label field, that is, regardless of the blockchain node that initiates the request message to the front-end server, the node label of the blockchain node that initiated the persistent connection process is always marked when the file is updated. Therefore, this MQ (message The queue) persistent connection scheme is only applicable to those cases where the requesting blockchain node that initiates the message is consistent with the blockchain node that initiates the persistent connection process.

Summary of the invention

technical problem

The solution to the problem

Technical solutions

The purpose of the embodiments of the present disclosure is to provide a cross-blockchain node message processing method and related equipment, so as to overcome at least to a certain extent the nodes in the prior art that request nodes to change and cannot update files when the long connection process processes the message queue. The label field and node handle capacity is limited.

In a first aspect, a message processing method across blockchain nodes is provided, which includes: starting a message queue monitoring process according to a starting node in the blockchain, and creating a corresponding node index area through the message queue monitoring process; Obtain the current message in the message queue of the blockchain node through the message queue monitoring process; obtain the target parameter of the current message according to the node index area, so as to obtain the target parameter according to the target parameter and the corresponding current message The request node configures the node attributes of the message queue monitoring process; the node label field of the target file corresponding to the request node is updated through the node attributes of the message queue monitoring process, so as to process the request node through the message queue monitoring process The current message in.

In a second aspect, a message processing device across blockchain nodes is provided, including: a startup unit configured to start a message queue monitoring process according to the startup node in the blockchain, and create a corresponding message queue monitoring process through the message queue monitoring process The node index area of the node; an obtaining unit configured to obtain the current message in the message queue of the blockchain node through the message queue monitoring process; a modification unit configured to obtain the target of the current message according to the node index area Parameter to configure the node attribute of the message queue monitoring process according to the target parameter and the request node corresponding to the current message; the processing unit is configured to update the node attribute of the request node through the node attribute of the message queue monitoring process The node label field of the target file is used to process the current message in the requesting node through the message queue monitoring process.

In a third aspect, an electronic device is provided, including: a processor; and a memory, on which computer-readable instructions are stored, and when the computer-readable instructions are executed by the processor, the above-mentioned cross-blockchain is implemented The node's message processing method.

In a fourth aspect, a computer non-volatile readable storage medium is provided, on which a computer program is stored, and the computer program, when executed by a processor, realizes the message processing across blockchain nodes according to any one of the above method.

The technical solution provided by the embodiments of the present disclosure may include the following beneficial effects: through the method of the present disclosure, on the one hand, the target parameter of the current message is obtained in the node index area and the corresponding system interface is called through the target parameter to pass the request node corresponding to the current message The node attribute configuration of the startup node avoids the problem that the requested blockchain node and the blockchain node that initiates the long connection process must be consistent, and improves the efficiency of processing the message queue in the long connection process; on the other hand, it realizes the processing of the long connection process In the message queue, the node label field of the file can be updated correctly even if the requesting node changes; on the other hand, by creating a node index area to store nodes and node handles, the node handles of the same node can be reused, which solves the limited capacity of node handles The problem.

The beneficial effects of the invention

Brief description of the drawings

Description of the drawings

The drawings herein are incorporated into the specification and constitute a part of the specification, show embodiments conforming to the disclosure, and are configured together with the specification to explain the principle of the disclosure. The following drawings are only some embodiments of the present disclosure. For those of ordinary skill in the art, other drawings can be obtained from these drawings without creative work.

Fig. 1 schematically shows a schematic diagram of a cross-blockchain interaction system according to some embodiments of the present disclosure;

Fig. 2 shows a schematic diagram of a message processing method across blockchain nodes according to some embodiments of the present disclosure;

Figure 3 shows a schematic diagram of a message processing flow across blockchain nodes according to some embodiments of the present disclosure;

Fig. 4 shows a schematic diagram of a message processing device across blockchain nodes according to some embodiments of the present disclosure;

Fig. 5 shows a schematic structural diagram of a computer system of an electronic device according to some embodiments of the present disclosure;

Fig. 6 schematically shows a schematic diagram of a computer non-volatile readable storage medium according to some embodiments of the present disclosure.

Invention embodiment

Embodiments of the invention

Example embodiments will now be described more fully with reference to the accompanying drawings. However, the example embodiments can be implemented in various forms, and should not be construed as being limited to the examples set forth herein; on the contrary, the provision of these embodiments makes the present disclosure more comprehensive and complete, and fully conveys the concept of the example embodiments To those skilled in the art.

Fig. 1 shows a schematic diagram of a cross-blockchain interaction system according to some embodiments of the present disclosure. Among them, the subscription client corresponds to a blockchain node in the first blockchain, and is used to maintain a message queue corresponding to the blockchain node, and the message queue contains messages subscribed by the blockchain node. The publishing client corresponds to the second blockchain and is used to obtain and publish messages generated by the second blockchain. The cross-chain interaction terminal (cross-chain interaction terminal 1, cross-chain interaction terminal 2) is used to obtain the subscription conditions of the blockchain nodes in the first blockchain, and when the end of the message queue contains messages that meet the subscription conditions, the The publishing client requests a message that meets the subscription condition and sends it to the subscribing client to update it in the message queue, so that the blockchain node in the first blockchain can pull the message from the message queue.

When the blockchain node subscribing to the client processes the message queue (MQ), it usually starts a long connection process for processing. When a pending message is detected in the message queue, the message is processed. When a large number of messages enter the message queue at the same time, the messages in the message queue can be processed one by one through the long connection process. However, since the startup blockchain node is set as the "current node" by default when the persistent connection process is started, the input/output program (Input/Output, referred to as IO program) will use the "current node" to update the node label field of the file , That is, regardless of the blockchain node that initiates the request message to the front-end server, it is always set to the node label of the blockchain node that initiated the long connection process when the file is updated. Therefore, this message queue long connection scheme is only suitable for configuration The case where the requesting blockchain node that initiates the message is consistent with the blockchain node that initiated the long connection process.

Based on this, a method for message processing across blockchain nodes is first provided. Referring to Figure 2, the method for processing messages across blockchain nodes may include the following steps:

In step S210, a message queue monitoring process is started according to the start node in the blockchain, and a corresponding node index area is created through the message queue monitoring process.

The startup node may refer to the node corresponding to the message queue monitoring process in the blockchain. The startup node may be a client in the blockchain. For example, referring to Figure 1, the blockchain node may correspond to the first zone. The subscription client of the blockchain. The message queue monitoring process can refer to a process configured to monitor and process messages in the message queue. For example, the message queue monitoring process can be a long connection process. Specifically, starting a message queue monitoring process can be a long connection process corresponding to the message queue. . In this embodiment, the long connection process is relative to the short connection process, that is, the long connection process can continuously monitor the message queue. Once unprocessed messages are found, they will be taken out and processed until the messages in the message queue are processed. . Of course, the message queue monitoring process may also be a short connection process, and a message queue monitoring process to be started may be one or more short connection processes corresponding to the message queue. The short connection process is a processing process generated separately for a certain message, and it terminates after processing the message. The node index area is used to store the correspondence between the request node of the message in the message queue and the node handle corresponding to the request node. The node index area can be understood as a memory area.

In one embodiment, step S210 includes: obtaining a preset system interface based on the message queue monitoring process; creating a corresponding node index area according to the system interface, wherein the node index area is configured to store the current message in the message queue The corresponding relationship between the request node and the node handle of the request node. The system interface can be pre-stored in the storage device of the client corresponding to the startup node, or can be configured by the developer. After the system starts the message queue monitoring process on the node, it calls the system interface through the message queue monitoring process and creates a node index area through the system interface. For example, suppose there are currently two pending messages A and B in the message queue, corresponding to the requesting node A that initiates message A and the requesting node B that initiates message B. Requesting node A can create a node handle A, The requesting node B can create a node handle B correspondingly, and the corresponding relations between the requesting node A and the node handle A, and the requesting node B and the node handle B are respectively stored in the node index area.

In step S220, the current message in the message queue of the blockchain node is obtained through the message queue monitoring process.

In one embodiment, the current message refers to the message to be processed with the logical position at the top in the message queue, that is, the current message is not a fixed message, but changes dynamically. For example, a message queue has messages to be processed A, message B to be processed, and message C to be processed in order of priority. At this time, the logical position of message A to be processed in the message queue is at the top. Therefore, it is considered that message A to be processed is Current message; In the order of entering the message queue, there are pending message C, pending message A, and pending message B. At this time, pending message C is at the top of the logical position in the message queue, so it is considered pending message C Is the current message.

Step S220 further includes: sorting the messages to be processed in the message queue according to preset rules to generate a sequence list; and obtaining the current messages in the message queue in sequence according to the sequence list through the message queue monitoring process. The preset rule may refer to a rule set by the user in advance for sorting messages to be processed, such as the priority of messages to be processed in a message queue, or the order in which messages enter the message queue. The messages to be processed in the message queue are sorted and processed according to preset rules (the persistent connection process can only process the messages in the message queue one by one), for example, the messages to be processed are processed according to the priority of the message to be processed. Of course, you can also directly process the messages one by one according to the order in which the messages to be processed enter the message queue. The message queue monitoring process obtains the current message in the generated sequence list or obtains the current message according to the time sequence when the message to be processed enters the message queue.

In step S230, the target parameter of the current message is obtained according to the node index area, and the corresponding system interface is called according to the target parameter to configure the startup node through the node attribute of the request node corresponding to the current message.

The target parameter refers to the input parameter that is associated with the current message and is configured to call the system interface, such as the node handle corresponding to the request node of the current message, or the request node of the current message (get it through the request node of the current message in the node index Corresponding node handle, and then take the node handle as the input parameter of calling the system interface). The node attributes include at least one attribute information such as the name of the node, the value of the node, and the type of the node. The system can allocate computing resources and other services to the node according to the node attribute. The message queue monitoring process calls the corresponding system interface according to the target parameter, and the system interface configures the startup node through the node attribute of the request node corresponding to the current message.

When processing the message queue, the system uses the startup node in the blockchain to start a long connection process for message processing. When a large number of messages in the message queue enter the message queue, the messages in the message queue can be processed one by one through the long connection process. To deal with it. However, since the persistent connection process will set the startup node as the "current node" by default when the startup node is started, the IO program will use the "current node" to update the node label field of the file. At this time, the persistent connection process will process the current message of the requesting node at the start node. Due to inconsistent node attributes, the persistent connection process may fail to process the current message or reduce the efficiency of processing the message. Therefore, it is necessary to configure the startup node according to the node attributes of the request node corresponding to the current message through the node handle, so that the IO program can correctly update the node label field corresponding to the request node according to the node attributes of the startup node, so that the persistent connection process in the startup node can be accurate Process the current message in the requesting node quickly and accurately.

Specifically, it is judged whether the request node of the current message and the request node of the previous message in the message queue are the same node; if it is determined that the request node of the current message and the request node of the previous message in the message queue are the same node, start The node attribute of the node updates the node label field in the target file corresponding to the request node to process the current message in the request node by starting the message queue monitoring process in the node. The previous message may refer to a message that has been processed by the message queue monitoring process and is adjacent to the position of the current message in the message queue. For example, a message queue has pending message A, pending message B, and pending message C arranged in priority order. At this time, pending message A is the current message. After the message queue monitoring process has processed pending message A, Then the pending message B is the current message, and the processed message A is the previous message. The target file may refer to the compiled code corresponding to the requested node, and the node label field is stored in the target file. The node label field can include node attribute value, node label name, etc. According to the node attribute of the message queue monitoring process, changing the node label field of the target file of the request node can enable the start node and current message of the persistent connection process started by the message queue monitoring process. The request nodes are kept consistent, so that the long connection process can better process the current message.

When the message queue monitoring process determines that the request node of the current message and the request node of the previous message in the message queue are the same node, the node attribute of the current node is considered to be the same as the node attribute of the previous message, so there is no need to monitor the message queue The node attribute of the starting node corresponding to the process is updated, the node label field in the target file corresponding to the request node is directly updated through the node attribute of the starting node, and the current message in the request node is processed through the message queue monitoring process in the starting node.

Optionally, if the message queue monitoring process determines that the request node of the current message and the request node of the previous message in the message queue are not the same node, then it is considered that the node attributes of the request node of the current message and the request node of the previous message are different, Therefore, when processing the current message, it is first necessary to update the node attributes corresponding to the startup node corresponding to the message queue monitoring process. Therefore, the message queue monitoring process takes the request node of the current message as the target parameter (input parameter), calls the corresponding system interface to access the node index area to obtain the node handle of the current message request node, and calls the corresponding system interface according to the node handle. Get the node attribute of the request node of the current message, and configure the startup node through the node attribute of the request node, and then update the node label field in the target file corresponding to the request node through the node attribute of the startup node to pass the message queue in the startup node The monitoring process processes the current message in the request node.

Further, the message queue monitoring process determines whether there is a node handle corresponding to the request node of the current message in the node index area; if it is determined that there is a node handle corresponding to the request node of the current message in the node index area, the current message is directly obtained from the node index area. The node handle corresponding to the request node of the message, and the request node of the current message (which may include node attributes) according to the node handle corresponding to the request node of the current message, and configure the message queue monitoring process corresponding to the node attribute of the request node of the current message Start the node so that the message queue monitoring process can correctly process the current messages in the message queue, and improve the efficiency of message processing.

Optionally, if the message queue monitoring process determines that the node handle corresponding to the request node of the current message does not exist in the node index area, the request node of the current message is used as the target parameter (input parameter), and the corresponding system interface is called to create a request for the current message. The node handle corresponding to the node, and the node handle is stored in the node index area. Create a node handle corresponding to the request node of the current message that does not exist in the original node index area by calling the corresponding system interface in the node index area, and continuously improve the node index area to facilitate subsequent processing of messages of the same request node, and further improve the message processing effectiveness.

In step S240, the node label field in the target file corresponding to the requesting node is updated by the node attribute of the initiating node to process the current message in the requesting node through the message queue monitoring process in the initiating node.

The node label field can include node attribute value, node label name, etc. According to the node attribute of the message queue monitoring process, changing the node label field of the target file of the request node can enable the start node and current message of the persistent connection process started by the message queue monitoring process. The request nodes are kept consistent, so that the long connection process can better process the current message. The target file refers to the compiled code corresponding to the requested node, and the node label field is stored in the target file.

Optionally, the message queue monitoring process can determine whether there are still messages to be processed in the message queue, and if there are still messages to be processed in the message queue, then determine whether it is allowed to obtain messages in the message queue: if the messages to be processed are allowed, then The pending messages in the message queue are processed; if acquisition is not allowed, the message queue monitoring process is terminated; if there are no messages to be processed, the message queue monitoring process can enter an infinite waiting mode until messages to be processed appear in the message queue.

Through the method of the present disclosure, first, the target parameter of the current message is obtained in the node index area and the corresponding system interface is called through the target parameter to configure the startup node through the node attribute of the request node corresponding to the current message, which breaks the request block of the prior art The chain node and the blockchain node that initiates the long connection process must be defined consistently, which improves the efficiency of the long connection process in processing the message queue; secondly, when the long connection process is used to process the message queue, the file can be updated correctly even if the requesting node changes Moreover, by creating a node index area to store nodes and node handles, the node handles of the same node can be reused, which solves the problem of limited node handle capacity.

FIG. 3 schematically shows a schematic diagram of a message processing flow across blockchain nodes according to some embodiments of the present disclosure, including: step S301, initiating a message queue monitoring process at the startup node in the blockchain. Step S302: After the message queue monitoring process is started, the message queue monitoring process calls the corresponding system interface to create a node index area, which can be stored in the storage area of the client corresponding to the blockchain node. In step S303, the message queue monitoring process can determine whether there are still messages to be processed in the message queue. If there are still messages to be processed in the message queue, it is determined whether it is allowed to obtain the messages in the message queue. If the messages to be processed are allowed to be obtained, then proceed to step S304: If acquisition is not allowed, end the message queue monitoring process. Step S304, the message queue monitoring process reads the current message from the message queue. Step S305: The message queue monitoring process judges whether the request node of the current message and the request node of the previous message in the message queue are the same node, if it is determined that the request node of the current message and the request node of the previous message in the message queue are the same node , Proceed to step S312; if it is determined that the request node of the current message and the request node of the previous message in the message queue are not the same node, proceed to step S306. In step S306, the message queue monitoring process takes the request node of the current message as an input parameter, and calls the corresponding system interface to access the node index area to obtain the node attribute of the current message request node. Step S307: The message queue monitoring process determines whether there is a node handle corresponding to the requesting node of the current message in the node index area; if it is determined that there is a node handle corresponding to the requesting node of the current message in the node index area, proceed to step S308; if the node index is determined If there is no node handle corresponding to the request node of the current message in the area, step S309 is performed. Step S308: The message queue monitoring process obtains the node handle corresponding to the current message request node from the node index area. In step S309, the message queue monitoring process calls the corresponding system interface with the request node of the current message as an input parameter, and creates a node handle corresponding to the request node of the current message according to the system interface. In step S310, the message queue monitoring process calls the corresponding system interface to store the message node and the created node handle in the node index area. In step S311, the message queue monitoring process uses the node handle as an input parameter, calls the corresponding system interface to obtain the node attribute of the request node corresponding to the current message, and configures the startup node through the node attribute of the request node. In step S312, the system calls the message queue monitoring process to process the message, and changes the node label field of the file according to the node attribute of the startup node corresponding to the message queue monitoring process.

It should be noted that although the various steps of the method in the present disclosure are described in a specific order in the drawings, this does not require or imply that these steps must be performed in the specific order, or that all the steps shown must be performed to Achieve the desired result. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step for execution, and/or one step may be decomposed into multiple steps for execution, etc.

In addition, in this exemplary embodiment, a message processing device across blockchain nodes is also provided. 4, the cross-blockchain node message processing device 400 includes: the activation unit 410 is configured to activate a message queue monitoring process according to the activation node in the blockchain, and create a corresponding node index through the message queue monitoring process The obtaining unit 420 is configured to obtain the current message in the message queue of the blockchain node through the message queue monitoring process; the modification unit 430 is configured to obtain the target parameter of the current message according to the node index area, so as to obtain the target parameter of the current message according to the target parameter and the current message The request node configures the node attributes of the message queue monitoring process; the processing unit 440 is configured to update the node label field of the target file corresponding to the request node through the node attributes of the message queue monitoring process, so as to process the current message in the request node through the message queue monitoring process.

In an embodiment, the obtaining unit 420 is configured to: sort the messages to be processed in the message queue according to preset rules to generate a sequence list; and obtain the current messages in the message queue in sequence according to the sequence list through the message queue monitoring process.

In an embodiment, the starting unit 410 is configured to: obtain a preset system interface based on the message queue monitoring process; create a node index area according to the system interface; the node index area is configured to store the request node and request of the current message in the message queue Correspondence between node and node handle.

In an embodiment, the modification unit 430 includes: a judging unit configured to judge whether the request node of the current message and the request node of the previous message in the message queue are the same node; the node attribute modification unit is configured to determine whether the request node of the current message The request node and the request node of the previous message in the message queue are the same node, and the node label field in the target file corresponding to the request node is directly updated through the node attribute of the starting node to process the request through the message queue monitoring process in the starting node The current message in the node.

In an embodiment, the node attribute modification unit includes: an access unit configured to, if it is determined that the request node of the current message and the request node of the previous message in the message queue are not the same node, call the corresponding system according to the request node of the current message The interface accesses the node index area to obtain the node handle corresponding to the request node; calls the corresponding system interface according to the node handle to configure the startup node through the node attributes of the request node of the current message, and update the target file corresponding to the request node through the node attributes of the startup node The node label field in the node to process the current message in the requesting node by starting the message queue monitoring process in the node.

In one embodiment, the cross-blockchain node message processing device 400 is configured to: determine whether there is a node handle corresponding to the request node of the current message in the node index area; if there is a node handle corresponding to the request node of the current message in the node index area Node handle, the node handle of the requesting node of the current message is obtained from the node index area to call the corresponding system interface according to the node handle to configure the startup node through the node attribute configuration of the requesting node corresponding to the current message; if there is no current message in the node index area The node handle corresponding to the request node of the current message is called by the request node of the current message to call the corresponding system interface to create the node handle corresponding to the request node of the current message and store it in the node index area.

In one embodiment, the processing unit 440 is configured to determine whether there is a current message to be processed in the message queue based on the message queue monitoring process; if there is a current message in the message queue, process the current message; if there is no current message in the message queue Message, the message queue monitoring process is ended.

The specific details of each module of the above device have been described in detail in the corresponding method embodiment, and will not be repeated here.

It should be noted that although several modules or units of the message processing device across blockchain nodes are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more modules or units described above may be embodied in one module or unit. The features and functions of a module or unit described above can be further divided into multiple modules or units to be embodied.

The present disclosure also provides an electronic device capable of implementing the above-mentioned cross-blockchain node message processing method.

It can be understood that various aspects of the present disclosure can be implemented as a system, a method, or a program product. Therefore, the color of the present disclosure can be realized through a complete hardware embodiment, a complete software embodiment (including firmware, microcode, etc.), or a combination of hardware and software, which can be collectively referred to herein as "circuits", "modules" or "system".

The electronic device 500 according to such an embodiment of the present disclosure will be described below with reference to FIG. 5. The electronic device 500 shown in FIG. 5 is only an example, and should not bring any limitation to the function and scope of use of the embodiments of the present disclosure.

As shown in FIG. 5, the electronic device 500 is represented in the form of a general-purpose computing device. The components of the electronic device 500 may include but are not limited to: at least one processing unit 510, at least one storage unit 520, a bus 530 connecting different system components, and a display unit 540.

The storage unit stores program code, and the program code can be executed by the processing unit 510, so that the processing unit 510 executes the method in the foregoing method embodiment. For example, the processing unit 510 may perform steps S210-S240 as shown in FIG. 2.

The storage unit 520 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 521 and/or a cache storage unit 522, and may further include a read-only storage unit (ROM) 523. The storage unit 520 may also include a program/utility tool 524 having a set of (at least one) program module 525. Such program module 525 includes but is not limited to: an operating system, one or more application programs, other program modules, and program data, Each of these examples or some combination may include the implementation of a network environment.

The bus 530 may represent one or more of several types of bus structures, including a storage unit bus or a storage unit controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local area using any bus structure among multiple bus structures. bus.

The electronic device 500 may also communicate with one or more external devices 570 (such as keyboards, pointing devices, Bluetooth devices, etc.), and may also communicate with one or more devices that enable a user to interact with the electronic device 500, and/or communicate with Any device (such as a router, modem, etc.) that enables the electronic device 500 to communicate with one or more other computing devices. This communication can be performed through an input/output (I/O) interface 550. In addition, the electronic device 500 may also communicate with one or more networks (for example, a local area network (LAN), a wide area network (WAN), and/or a public network, such as the Internet) through the network adapter 560. The network adapter 560 communicates with other modules of the electronic device 500 through the bus 530. It should be understood that although not shown in the figure, other hardware and/or software modules can be used in conjunction with the electronic device 500, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tapes Drives and data backup storage systems, etc.

Through the description of the above embodiments, those skilled in the art can easily understand that the exemplary embodiments described here can be implemented by software, or can be implemented by combining software with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure can be embodied in the form of a software product, and the software product can be stored in a computer non-volatile readable storage medium (which can be a CD-ROM, U disk, mobile hard disk, etc.) Or on the network, several instructions are included to make a computing device (which may be a personal computer, a server, a terminal device, or a network device, etc.) execute the method according to the embodiments of the present disclosure.

In the exemplary embodiment of the present disclosure, there is also provided a computer non-volatile readable storage medium on which is stored a program product capable of implementing the above-mentioned method in this specification. In some possible embodiments, various aspects of the present disclosure may also be implemented in the form of a program product, which includes program code. When the program product runs on a terminal device, the program code is used to make the terminal device execute the foregoing的方法实施例。 Example of the method.

Figure 6 shows a program product 600 for implementing the above-mentioned cross-blockchain node message processing method, which can adopt a portable compact disk read-only memory (CD-ROM) and include program code, and can be used in terminal devices, such as personal On the computer, run. The program product of the present disclosure is not limited thereto, and the computer non-volatile readable storage medium may also be any tangible medium that contains or stores a program, and the program may be used by or in combination with an instruction execution system, apparatus, or device.

The program product can adopt any combination of one or more computer non-volatile readable storage media. The computer non-volatile readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any combination of the above. More specific examples (non-exhaustive list) of readable storage media include: electrical connections with one or more wires, portable disks, hard disks, random access memory (RAM), read only memory (ROM), erasable Type programmable read only memory (EPROM or flash memory), optical fiber, portable compact disk read only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above.

The program code for performing the operations of the present disclosure can be written in any combination of one or more programming languages. The programming languages include object-oriented programming languages-such as Java, C++, etc., as well as conventional procedural programming. Language-such as "C" language or similar programming language. The program code can be executed entirely on the user's computing device, partly on the user's device, executed as an independent software package, partly on the user's computing device and partly executed on the remote computing device, or entirely on the remote computing device or server Executed on. In the case of a remote computing device, the remote computing device can be connected to a user computing device through any kind of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using Internet service providers) Business to connect via the Internet).

In addition, the above-mentioned drawings are merely schematic illustrations of the processing included in the method according to the exemplary embodiments of the present disclosure, and are not intended for limitation. It is easy to understand that the processing shown in the above drawings does not indicate or limit the time sequence of these processings. In addition, it is easy to understand that these processes can be executed synchronously or asynchronously in multiple modules, for example.

Through the description of the above embodiments, those skilled in the art can easily understand that the exemplary embodiments described here can be implemented by software, or can be implemented by combining software with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, U disk, mobile hard disk, etc.) or on the network , Including several instructions to make a computing device (which may be a personal computer, a server, a touch terminal, or a network device, etc.) execute the method according to the embodiments of the present disclosure.

It should be understood that the present disclosure is not limited to the precise structure that has been described above and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present disclosure is limited only by the appended claims.

Claims (28)

1. A message processing method for cross-blockchain nodes includes: starting a message queue monitoring process according to the start node in the block chain, and creating a corresponding node index area through the message queue monitoring process; monitoring through the message queue The process obtains the current message in the message queue of the blockchain node; obtains the target parameter of the current message according to the node index area, and calls the corresponding system interface according to the target parameter to pass the message corresponding to the current message The node attribute of the requesting node configures the starting node; the node label field in the target file corresponding to the requesting node is updated by the node attribute of the starting node, so as to pass the message queue monitoring process in the starting node. The current message in the request node.
2. The method according to claim 1, wherein obtaining the current messages in the message queue of the blockchain node through the message queue monitoring process further comprises: sorting and generating messages to be processed in the message queue according to preset rules Sequence list; obtain the current messages in the message queue in sequence according to the sequence list through the message queue monitoring process.
3. The method according to claim 1, wherein the creating a corresponding node index area through the message queue monitoring process comprises: obtaining a preset system interface based on the message queue monitoring process; creating according to the system interface Corresponding node index area; wherein, the node index area is used to store the correspondence between the request node of the current message in the message queue and the node handle of the request node.
4. The method according to claim 3, wherein the target parameter includes the node handle, and the corresponding system interface is invoked according to the target parameter to configure the startup node through the node attribute of the request node corresponding to the current message Before, the method further includes: judging whether the requesting node of the current message and the requesting node of the previous message in the message queue are the same node; if it is determined that the requesting node of the current message is The requesting node of the previous message is the same node, then the node label field in the target file corresponding to the requesting node is updated directly through the node attribute of the initiating node, so as to be processed by the message queue monitoring process in the initiating node The current message in the request node.
5. The method according to claim 4, wherein the target parameter includes the request node of the current message, and the corresponding system interface is invoked according to the target parameter to configure the node property of the request node corresponding to the current message. Before starting the node, the method further includes: if it is determined that the request node of the current message and the request node of the previous message in the message queue are not the same node, calling the corresponding node according to the request node of the current message. The system interface accesses the node index area to obtain the node handle corresponding to the request node; calls the corresponding system interface according to the node handle to configure the startup node through the node attributes of the request node of the current message, And update the node label field in the target file corresponding to the requesting node by the node attribute of the initiating node, so as to process the current message in the requesting node through the message queue monitoring process in the initiating node.
6. The method according to claim 5, wherein, after calling the corresponding system interface to access the node index area according to the requesting node of the current message, the method further comprises: judging whether there is in the node index area The node handle corresponding to the request node of the current message; if the node handle corresponding to the request node of the current message exists in the node index area, the node of the request node of the current message is obtained from the node index area The handle is to call the corresponding system interface according to the node handle to configure the startup node through the node attributes of the request node corresponding to the current message; if the node index area does not exist in the node index area corresponding to the request node of the current message Node handle, the node handle corresponding to the request node of the current message is created by invoking the corresponding system interface by the request node of the current message and stored in the node index area.
7. The method according to claim 1, wherein the processing the current message through the message queue monitoring process further comprises: judging whether there is the current message to be processed in the message queue based on the message queue monitoring process If there is the current message in the message queue, the current message is processed; if there is no current message in the message queue, the message queue monitoring process is ended.
8. A message processing device for cross-blockchain nodes includes: a start unit configured to start a message queue monitoring process according to the start node in the block chain, and create a corresponding node index area through the message queue monitoring process; obtain The unit is configured to obtain the current message in the message queue of the blockchain node through the message queue monitoring process; the modification unit is configured to obtain the target parameter of the current message according to the node index area, and according to the The target parameter calls the corresponding system interface to configure the startup node through the node attributes of the request node corresponding to the current message; the processing unit is configured to update the target file in the target file corresponding to the request node through the node attributes of the startup node The node label field is used to process the current message in the request node through the message queue monitoring process in the startup node.
9. 8. The device according to claim 8, wherein the acquiring unit is configured to: sort the messages to be processed in the message queue according to a preset rule to generate a sequence list; and obtain sequentially according to the sequence list through the message queue monitoring process The current message in the message queue.
10. 8. The device according to claim 8, wherein the activation unit is configured to: obtain a preset system interface based on the message queue monitoring process; create a corresponding node index area according to the system interface; wherein the node The index area is used to store the correspondence between the request node of the current message in the message queue and the node handle of the request node.
11. The device according to claim 10, wherein the target parameter includes the node handle, and the modification unit includes: a judging unit configured to judge the request node of the current message and the previous message in the message queue Whether the requesting node of is the same node; the node attribute modification unit is configured to directly pass the node of the initiating node if it is determined that the requesting node of the current message and the requesting node of the previous message in the message queue are the same node The attribute updates the node label field in the target file corresponding to the request node to process the current message in the request node through the message queue monitoring process in the start node.
12. The apparatus according to claim 11, wherein the node attribute modification unit comprises: an access unit configured to, if it is determined that the request node of the current message and the request node of the previous message in the message queue are not the same node, then According to the request node of the current message, call the corresponding system interface to access the node index area to obtain the node handle corresponding to the request node; according to the node handle, call the corresponding system interface to pass the current message The node attribute of the requesting node configures the starting node, and the node label field in the target file corresponding to the requesting node is updated through the node attribute of the starting node to monitor the process through the message queue in the starting node Process the current message in the requesting node.
13. The apparatus according to claim 12, wherein the apparatus is further configured to: determine whether there is a node handle corresponding to the requesting node of the current message in the node index area; if the node index area exists in the node handle The node handle corresponding to the requesting node of the current message is obtained from the node index area to call the corresponding system interface according to the node handle to pass the corresponding node of the current message The node attribute of the requesting node configures the startup node; if the node handle corresponding to the requesting node of the current message does not exist in the node index area, the requesting node of the current message calls the corresponding system interface to create the The node handle corresponding to the request node of the current message is stored in the node index area.
14. 8. The device according to claim 8, wherein the processing unit is configured to: based on the message queue monitoring process, determine whether there is the current message to be processed in the message queue; if there is a message in the message queue If the current message is described, the current message is processed; if there is no current message in the message queue, the message queue monitoring process is ended.
15. An electronic device includes: a processor; and a memory on which computer-readable instructions are stored, and when the computer-readable instructions are executed by the processor, the following steps are implemented:

    Start a message queue monitoring process according to the startup node in the blockchain, and create a corresponding node index area through the message queue monitoring process; obtain the current information in the message queue of the blockchain node through the message queue monitoring process Message; obtain the target parameter of the current message according to the node index area, and call the corresponding system interface according to the target parameter to configure the startup node through the node attributes of the request node corresponding to the current message; The node attribute of the initiating node updates the node label field in the target file corresponding to the requesting node to process the current message in the requesting node through the message queue monitoring process in the initiating node.
16. The electronic device according to claim 15, wherein, in the step of obtaining the current message in the message queue of the blockchain node through the message queue monitoring process, the processor is configured to: according to a preset rule The messages to be processed in the message queue are sorted to generate a sequence list; and the current messages in the message queue are sequentially acquired according to the sequence list through the message queue monitoring process.
17. The electronic device according to claim 15, wherein, in the step of creating a corresponding node index area through the message queue monitoring process, the processor is configured to: obtain a preview based on the message queue monitoring process Set the system interface; create a corresponding node index area according to the system interface; wherein the node index area is used to store the corresponding relationship between the request node of the current message in the message queue and the node handle of the request node .
18. The electronic device according to claim 17, wherein the target parameter includes the node handle, and the corresponding system interface is invoked according to the target parameter to configure the node attribute of the request node corresponding to the current message Before the step of starting the node, the processor is further configured to:

    Determine whether the request node of the current message and the request node of the previous message in the message queue are the same node; if it is determined that the request node of the current message is the same as the request node of the previous message in the message queue Node, then directly update the node label field in the target file corresponding to the request node through the node attribute of the initiating node, so as to process the request node in the request node through the message queue monitoring process in the initiating node Current news.
19. The electronic device according to claim 18, wherein, when the target parameter includes the request node of the current message, the corresponding system interface is called according to the target parameter to pass the node attribute of the request node corresponding to the current message Before the step of configuring the startup node, the processor is further configured to:

    If it is determined that the requesting node of the current message and the requesting node of the previous message in the message queue are not the same node, call the corresponding system interface according to the requesting node of the current message to access the node index area to obtain The node handle corresponding to the request node; according to the node handle, the corresponding system interface is invoked to configure the startup node through the node attributes of the request node of the current message, and update the startup node through the node attributes of the startup node The node label field in the target file corresponding to the request node is used to process the current message in the request node through the message queue monitoring process in the start node.
20. The electronic device according to claim 19, wherein, after the step of invoking the corresponding system interface to access the node index area by the requesting node of the current message, the processor is further configured to:

    Determine whether there is a node handle corresponding to the request node of the current message in the node index area; if there is a node handle corresponding to the request node of the current message in the node index area, obtain it from the node index area The node handle of the requesting node of the current message to call the corresponding system interface according to the node handle to configure the startup node through the node attributes of the requesting node corresponding to the current message; if the node index area does not exist The node handle corresponding to the request node of the current message is then invoked by the request node of the current message to call the corresponding system interface to create the node handle corresponding to the request node of the current message and store it in the node index area.
21. The electronic device according to claim 15, wherein, in the step of processing the current message through the message queue monitoring process, the processor is further configured to:

    Based on the message queue monitoring process, it is determined whether there is the current message to be processed in the message queue; if the current message is in the message queue, the current message is processed; if the message queue is in If there is no current message, the message queue monitoring process ends.
22. A computer non-volatile readable storage medium on which a computer program is stored, wherein the computer program is executed by a processor to implement the following steps:

    Start a message queue monitoring process according to the startup node in the blockchain, and create a corresponding node index area through the message queue monitoring process; obtain the current message queue of the blockchain node through the message queue monitoring process Message; obtain the target parameter of the current message according to the node index area, and call the corresponding system interface according to the target parameter to configure the startup node through the node attributes of the request node corresponding to the current message; The node attribute of the initiating node updates the node label field in the target file corresponding to the requesting node to process the current message in the requesting node through the message queue monitoring process in the initiating node.
23. The computer non-volatile readable storage medium according to claim 22, wherein, in the step of acquiring the current message in the message queue of the blockchain node through the message queue monitoring process, the processing The device is also configured to:

    The messages to be processed in the message queue are sorted according to a preset rule to generate a sequence list; the current messages in the message queue are sequentially acquired according to the sequence list through the message queue monitoring process.
24. The computer non-volatile readable storage medium according to claim 22, wherein, in the step of creating a corresponding node index area through the message queue monitoring process, the processor is configured to:

    Obtain a preset system interface based on the message queue monitoring process; create a corresponding node index area according to the system interface; wherein the node index area is used to store the request node of the current message in the message queue and The corresponding relationship between the request node and the node handle.
25. The computer non-volatile readable storage medium according to claim 24, wherein the target parameter includes the node handle, and the corresponding system interface is called according to the target parameter to correspond to the current message Before the step of requesting the node attributes of the node to configure the starting node, the processor is further configured to:

    Determine whether the request node of the current message and the request node of the previous message in the message queue are the same node; if it is determined that the request node of the current message is the same as the request node of the previous message in the message queue Node, then directly update the node label field in the target file corresponding to the request node through the node attribute of the initiating node, so as to process the request node in the request node through the message queue monitoring process in the initiating node Current news.
26. The computer non-volatile readable storage medium according to claim 25, wherein the target parameter includes the request node of the current message, and the corresponding system interface is called according to the target parameter to pass the current message Before the step of configuring the starting node with the node attributes of the requesting node corresponding to the message, the processor is further configured to:

    If it is determined that the requesting node of the current message and the requesting node of the previous message in the message queue are not the same node, call the corresponding system interface according to the requesting node of the current message to access the node index area to obtain The node handle corresponding to the request node; according to the node handle, the corresponding system interface is invoked to configure the startup node through the node attributes of the request node of the current message, and update the startup node through the node attributes of the startup node The node label field in the target file corresponding to the request node is used to process the current message in the request node through the message queue monitoring process in the start node.
27. The computer non-volatile readable storage medium according to claim 26, wherein, after the step of calling the corresponding system interface to access the node index area according to the requesting node of the current message, the processor further Is configured as:

    Determine whether there is a node handle corresponding to the request node of the current message in the node index area; if there is a node handle corresponding to the request node of the current message in the node index area, obtain it from the node index area The node handle of the requesting node of the current message to call the corresponding system interface according to the node handle to configure the startup node through the node attributes of the requesting node corresponding to the current message; if the node index area does not exist The node handle corresponding to the request node of the current message is then invoked by the request node of the current message to call the corresponding system interface to create the node handle corresponding to the request node of the current message and store it in the node index area.
28. The computer non-volatile readable storage medium according to claim 22, wherein, in the step of processing the current message through the message queue monitoring process, the processor is further configured to:

    Based on the message queue monitoring process, it is determined whether there is the current message to be processed in the message queue; if the current message is in the message queue, the current message is processed; if the message queue is in If there is no current message, the message queue monitoring process ends.

Images