WO2018171543A1 - 一种广播消息的方法及装置 - Google Patents
一种广播消息的方法及装置 Download PDFInfo
- Publication number
- WO2018171543A1 WO2018171543A1 PCT/CN2018/079435 CN2018079435W WO2018171543A1 WO 2018171543 A1 WO2018171543 A1 WO 2018171543A1 CN 2018079435 W CN2018079435 W CN 2018079435W WO 2018171543 A1 WO2018171543 A1 WO 2018171543A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- message
- processing device
- consensus node
- message processing
- thread
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/1854—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with non-centralised forwarding system, e.g. chaincast
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/1863—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast comprising mechanisms for improved reliability, e.g. status reports
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/542—Event management; Broadcasting; Multicasting; Notifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/182—Distributed file systems
- G06F16/1834—Distributed file systems implemented based on peer-to-peer networks, e.g. gnutella
- G06F16/1837—Management specially adapted to peer-to-peer storage networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/1863—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast comprising mechanisms for improved reliability, e.g. status reports
- H04L12/1868—Measures taken after transmission, e.g. acknowledgments
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/06—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols the encryption apparatus using shift registers or memories for block-wise or stream coding, e.g. DES systems or RC4; Hash functions; Pseudorandom sequence generators
- H04L9/0618—Block ciphers, i.e. encrypting groups of characters of a plain text message using fixed encryption transformation
- H04L9/0637—Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
- H04L9/3239—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees
Definitions
- the present application relates to the field of blockchain technology, and in particular, to a method and an apparatus for broadcasting a message.
- consensus node In the field of blockchain technology, the blockchain node responsible for consensus verification of the service is called a consensus node. Under the trend of blockchain globalization, consensus nodes are often distributed around the world.
- Each consensus node often needs to broadcast messages (such as service messages, consensus messages, etc.) to other consensus nodes during the acceptance of services and consensus verification. Due to the globalization of heterogeneous networks, the message transmission process is unstable. For example, the Chinese network and the US network are heterogeneous networks. The consensus nodes located in the US network may not receive messages from the consensus nodes in the Chinese network. Therefore, It is guaranteed that the success rate of each other consensus node receiving the message is high, and the consensus node of the broadcast message usually creates a thread for each other consensus node, and performs a task of sending a message to the other consensus node through the thread.
- the consensus node of the broadcast message sends a message to the other consensus node by the thread, it waits to receive the notification returned by the other consensus node (declaring that the message has been received), and if it is not received through the thread within the specified time, The notification will send a message to the consensus node again through the thread until the notification is received, or if the notification has not been received by the thread, the thread will be revoked. In this case, the success rate of receiving the message by the other consensus nodes can be ensured to be high.
- a consensus node of a broadcast message performs a task of sending a message to other consensus nodes through a thread created by it, it is often necessary to repeatedly send a message, and a consensus node of the broadcast message consumes a large amount of computing resources, which will give a broadcast message.
- the consensus node creates an excessive burden.
- the embodiment of the present invention provides a method and an apparatus for broadcasting a message, so as to solve the problem that an existing method for broadcasting a message causes an excessive burden on a consensus node of a broadcast message.
- the consensus node obtains the first broadcast message
- the second thread is revoked.
- a sending module configured to create a first thread for the message processing device corresponding to the device, and send the first broadcast message to the message processing device by using the first thread, so that the message processing device corresponds to another consensus node Transmitting, by the message processing device, the first broadcast message;
- the first receiving module receives a first broadcast message sent by the consensus node corresponding to the device
- a sending module configured to create a second thread for the message processing device corresponding to each other consensus node, and send the first broadcast message to the message processing device corresponding to the other consensus node by using the second thread;
- the revocation module cancels the second thread when it is determined that the message processing device corresponding to the other consensus node receives the first broadcast message.
- a message processing device is allocated for each consensus node, and the work of broadcasting messages between the consensus nodes is performed by each message processing device.
- the corresponding message processing device may create a thread for the message processing device corresponding to the other consensus nodes to perform the task of broadcasting the message until the message processing device corresponding to the other consensus node receives the broadcast message.
- the thread executing the broadcast message task only consumes the computing resources of the message processing device, but does not consume the resources of the consensus node, thereby not burdening the consensus node, and enabling the consensus node to more effectively verify the service.
- FIG. 1 is a flowchart of a method for broadcasting a message according to an embodiment of the present application
- FIG. 2 is a schematic diagram of comparison between a conventional broadcast message method and a broadcast message method provided by the present application;
- FIG. 3 is a schematic diagram of an apparatus for broadcasting a message according to an embodiment of the present application.
- FIG. 4 is a schematic diagram of another apparatus for broadcasting a message according to an embodiment of the present application.
- the embodiment of the present application provides a method and an apparatus for broadcasting a message.
- FIG. 1 is a flowchart of a method for broadcasting a message according to an embodiment of the present application, including the following steps:
- S101 The consensus node acquires the first broadcast message.
- the consensus node is a blockchain node participating in the consensus verification of the service in the blockchain network.
- each blockchain node can participate in consensus verification as a consensus node.
- a special blockchain network such as a blockchain network consisting of a coalition chain subnet and a public chain subnetwork
- not all blockchain nodes can participate in consensus verification as a consensus node.
- the consensus nodes need to broadcast or send messages to each other. This is the application scenario of the embodiment of the present application.
- the acceptance service phase means that a certain consensus node receives the service message and broadcasts the service message to other consensus nodes, so that each consensus node receives the service message, so as to facilitate subsequent consensus verification on the service message.
- the consensus verification phase refers to the stage in which the consensus nodes follow a consensus algorithm and reach a consensus on the verification results. In the consensus verification phase, the consensus nodes need to send verification messages to each other to reach a consensus.
- the first broadcast message may be the foregoing service message, or may be the foregoing verification message, or may be a message that a consensus node broadcasts or sends to other consensus nodes.
- the executor of the method may be any one of the consensus nodes.
- the consensus node may receive the service message sent by the client or the non-consensus node as the obtained first broadcast message.
- the consensus node may generate a verification message as the obtained first broadcast message after verifying the service message.
- the consensus node creates a first thread for the message processing device corresponding to the consensus node, and sends the first broadcast message to the message processing device by using the first thread.
- the consensus node may send the first broadcast message to its corresponding message processing device, and completely process the task of broadcasting or sending the first broadcast message to its corresponding message processing device. And the message processing device ensures that the message processing device of the other consensus node successfully receives the first broadcast message. In this way, the consensus node does not need to consume computing resources to ensure that each other consensus node receives the first broadcast message as much as possible.
- the message processing device corresponding to the consensus node is a computing device independent of the consensus node.
- the message interaction between the consensus nodes is performed by the message processing devices corresponding to the respective consensus nodes.
- the consensus node only needs to create a first thread for its corresponding message processing device, and after the first broadcast message is sent to the corresponding message processing device by the first thread, the first The thread continues to maintain the first thread without consuming computing resources.
- the first thread is a thread created by the consensus node for its corresponding message processing device
- the second thread described below is a thread created by the message processing device for the message processing device corresponding to the other consensus node.
- the consensus node uses an asynchronous calling technology to create a first thread for sending the first broadcast message to its corresponding message processing device, and the first broadcast message is to be sent by the first thread. After the consensus node does not care whether the message processing device receives the first broadcast message, the first thread may be directly revoked.
- the consensus node and its corresponding message processing device are generally not distributed in a heterogeneous network, that is, the information interaction between the consensus node and its corresponding message processing device is stable, and message processing is performed.
- a device is generally capable of successfully receiving a message sent by its corresponding consensus node at a time.
- the regional dedicated line may be used to connect the consensus node and the message processing device corresponding to the consensus node.
- the consensus node may, in addition to instructing its corresponding message processing device to broadcast a message to the outside, may also use its corresponding message processing device to receive messages broadcast by other consensus nodes.
- the consensus node may receive the second broadcast message sent by the message processing device corresponding to the consensus node, where the second broadcast message is broadcast by the message processing device corresponding to the other consensus node.
- the message processing device may receive the second broadcast message broadcast by the message processing device corresponding to the other consensus node, and then send the second broadcast message to the consensus node.
- first broadcast message and the second broadcast message are broadcast messages broadcast by the consensus node, and the first broadcast message and the second broadcast message may both be the foregoing service message and the verification message. Wait.
- the message processing device creates a second thread for the message processing device corresponding to each other consensus node, and sends the first broadcast message to the message processing device corresponding to the other consensus node by the second thread.
- S105 The message processing device cancels the second thread when it is determined that the message processing device corresponding to the other consensus node receives the first broadcast message.
- the work of the external broadcast message is that the consensus node is responsible for itself, and the consensus node creates a thread that occupies its own computing resources, and through the thread to ensure that each other consensus node receives its broadcasted message as much as possible.
- the consensus node only needs to send the first broadcast message to its corresponding message processing device.
- the message processing device as a computing device independent of the consensus node, can independently be responsible for externally broadcasting messages. This frees the consensus node so that the consensus node can focus on limited computing resources to perform consensus verification work more efficiently.
- the message processing device creates a second thread for the message processing device corresponding to each other consensus node, and consumes the computing resources of the message processing device by the second thread to wait for confirmation of the consensus.
- the node successfully receives the first broadcast message.
- the message processing device may send the first broadcast message to a message processing device corresponding to each other consensus node by using a second thread created for each other consensus node; and counting the number of received response signals
- the response signal is returned by the message processing device corresponding to the other consensus node after receiving the first broadcast message; if the number of statistics is less than the specific value, the first broadcast message is resent by each second thread, Until the counted number of received response signals is not less than the specific value, the specific value is an integer greater than zero.
- the specific value is configurable. The higher the specific value, the more the number of consensus nodes that can receive the first broadcast message can be ensured, and the success rate of the consensus node broadcast message is higher. This application does not limit the specific value to a specific value.
- the message processing device may continue to send the first broadcast message to the message processing device that does not return the response signal by using the second thread corresponding to the message processing device that does not return the response signal. Until the total number of received response signals of the previous statistics is not less than the specific value; the first broadcast message may be sent to all other message processing devices again by each second thread until the next time the statistics are received. The number of response signals is not less than the specific value.
- the message processing device sends the first broadcast message to a certain other message processing device by the second thread for a specified number of times, if the second thread still does not receive the other message processing device returns In response to the signal, the first broadcast message may be suspended from being sent to the message processing device; after the specified time limit, the first broadcast message is continued to be sent to the message processing device.
- the message processing device may first broadcast the first broadcast message to other message processing devices, and then determine other message processing devices that do not return a response signal (ie, the message that the first broadcast message is not received). Processing the device), and sending the first broadcast message to the message processing device that does not receive the first broadcast message, if it is repeated. After repeatedly transmitting the first broadcast message to the same other message processing device for three times, it indicates that there is a transmission problem that cannot be solved temporarily (may be a failure of the message processing device that failed to receive success or a large failure of the network), so The first broadcast message is first suspended to be sent to the other message processing device, and after waiting for a long time (the transmission problem may have been resolved), the first broadcast message is sent to the other message processing device.
- the message processing device may cancel the second thread after ensuring that the first broadcast message is received by the message processing device corresponding to each other consensus node. It is worth emphasizing that the message processing device can adopt various message delivery strategies, such as delayed delivery, compensation delivery (by the entity that has not received the message, actively requesting compensation for the message), etc., to ensure that the first broadcast message is The message processing device corresponding to the consensus node is received.
- the message delivery policy adopted by the message processing device is not specifically limited.
- the message processing device actually uses a synchronous calling technology to create a second thread for sending the first broadcast message to the message processing device for the message processing device corresponding to each other consensus node.
- the second thread continues to wait for confirmation that the message processing device receives the first broadcast message, and if the message processing device does not receive, re-passes the second thread.
- the first broadcast message is sent to the message processing device until the message processing device actually receives the first broadcast message or triggers a condition to stop sending, and the second thread is revoked.
- the message processing device corresponding to the other consensus node sends the first broadcast message to the corresponding other consensus node.
- consensus nodes can use their corresponding message processing devices to receive messages broadcast by other consensus nodes.
- a message processing device is allocated to each consensus node, and the work of broadcasting messages between the consensus nodes is performed by each message processing device.
- the corresponding message processing device may create a thread for the message processing device corresponding to each other consensus node to perform the task of broadcasting the message until the message processing device corresponding to the other consensus node receives the broadcast message. .
- the thread executing the broadcast message task only consumes the computing resources of the message processing device, but does not consume the resources of the consensus node, thereby not burdening the consensus node, and enabling the consensus node to more effectively verify the service. .
- the embodiment of the present application further provides a device for broadcasting a message, as shown in FIG. 3 , including:
- the obtaining module 301 is configured to obtain a first broadcast message.
- the sending module 302 is configured to create a first thread for the message processing device corresponding to the device, and send the first broadcast message to the message processing device by using the first thread, so that the message processing device sends the message processing device to other consensus nodes. Corresponding message processing device sends the first broadcast message;
- the undo module 303 revokes the first thread.
- the device is connected to the message processing device via a regional line.
- the device further includes: a receiving module 304, which receives a second broadcast message sent by the message processing device corresponding to the device, where the second broadcast message is broadcast by a message processing device corresponding to another consensus node.
- the embodiment of the present application further provides another device for broadcasting a message, as shown in FIG. 4 , including:
- the first receiving module 401 receives a first broadcast message sent by the consensus node corresponding to the device;
- the sending module 402 is configured to create a second thread for the message processing device corresponding to each other consensus node, and send the first broadcast message to the message processing device corresponding to the other consensus node by using the second thread;
- the revocation module 403 when it is determined that the message processing device corresponding to the other consensus node receives the first broadcast message, cancels the second thread.
- the revocation module 403 by using the second thread, the number of the received response signals, wherein the response signal is returned by the message processing device corresponding to the other consensus node after receiving the first broadcast message; If the value is less than the specific value, the first broadcast message is retransmitted by each second thread until the number of the received received response signals is not less than the specific value, and the specific value is an integer greater than 0.
- the device further includes: a second receiving module 404, receiving a second broadcast message broadcast by the message processing device corresponding to the other consensus node; and sending the second broadcast message to the consensus node.
- PLD Programmable Logic Device
- FPGA Field Programmable Gate Array
- HDL Hardware Description Language
- the controller can be implemented in any suitable manner, for example, the controller can take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (eg, software or firmware) executable by the (micro)processor.
- computer readable program code eg, software or firmware
- examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, The Microchip PIC18F26K20 and the Silicone Labs C8051F320, the memory controller can also be implemented as part of the memory's control logic.
- the controller can be logically programmed by means of logic gates, switches, ASICs, programmable logic controllers, and embedding.
- Such a controller can therefore be considered a hardware component, and the means for implementing various functions included therein can also be considered as a structure within the hardware component.
- a device for implementing various functions can be considered as a software module that can be both a method of implementation and a structure within a hardware component.
- the system, device, module or unit illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product having a certain function.
- a typical implementation device is a computer.
- the computer can be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or A combination of any of these devices.
- embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
- computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
- the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
- the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
- These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
- the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
- a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
- processors CPUs
- input/output interfaces network interfaces
- memory volatile and non-volatile memory
- the memory may include non-persistent memory, random access memory (RAM), and/or non-volatile memory in a computer readable medium, such as read only memory (ROM) or flash memory.
- RAM random access memory
- ROM read only memory
- Memory is an example of a computer readable medium.
- Computer readable media includes both permanent and non-persistent, removable and non-removable media.
- Information storage can be implemented by any method or technology.
- the information can be computer readable instructions, data structures, modules of programs, or other data.
- Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory. (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, Magnetic tape cartridges, magnetic tape storage or other magnetic storage devices or any other non-transportable media can be used to store information that can be accessed by a computing device.
- computer readable media does not include temporary storage of computer readable media, such as modulated data signals and carrier waves.
- embodiments of the present application can be provided as a method, system, or computer program product.
- the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment in combination of software and hardware.
- the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
- the application can be described in the general context of computer-executable instructions executed by a computer, such as a program module.
- program modules include routines, programs, objects, components, data structures, and the like that perform particular tasks or implement particular abstract data types.
- the present application can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are connected through a communication network.
- program modules can be located in both local and remote computer storage media including storage devices.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Multimedia (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Computer And Data Communications (AREA)
- Mobile Radio Communication Systems (AREA)
- Multi Processors (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
Claims (12)
- 一种广播消息的方法,其特征在于,包括:共识节点获取第一广播消息;针对所述共识节点对应的消息处理设备创建第一线程,并通过所述第一线程向所述消息处理设备发送所述第一广播消息,以使所述消息处理设备向其他共识节点对应的消息处理设备发送所述第一广播消息;撤销所述第一线程。
- 根据权利要求1所述的方法,其特征在于,所述共识节点与所述消息处理设备通过区域专线连接。
- 根据权利要求1所述的方法,其特征在于,所述方法还包括:接收所述共识节点对应的消息处理设备发送的第二广播消息,所述第二广播消息是其他共识节点对应的消息处理设备广播的。
- 一种广播消息的方法,其特征在于,包括:消息处理设备接收所述消息处理设备对应的共识节点发送的第一广播消息;针对每个其他共识节点对应的消息处理设备创建第二线程,并通过该第二线程向该其他共识节点对应的消息处理设备发送所述第一广播消息;当确定该其他共识节点对应的消息处理设备接收到所述第一广播消息时,撤销该第二线程。
- 根据权利要求4所述的方法,其特征在于,确定该其他共识节点对应的消息处理设备接收到所述第一广播消息,具体包括:通过各第二线程统计接收到的响应信号的数量,其中,响应信号是其他共识节点对应的消息处理设备在接收到所述第一广播消息后返回的;若统计的数量小于特定值,则通过各第二线程重新发送所述第一广播消息,直至统计的接收到的响应信号的数量不小于所述特定值为止,所述特定值为大于0的整数。
- 根据权利要求4所述的方法,其特征在于,所述方法还包括:接收其他共识节点对应的消息处理设备广播的第二广播消息;将所述第二广播消息发送给所述共识节点。
- 一种广播消息的装置,其特征在于,包括:获取模块,获取第一广播消息;发送模块,针对所述装置对应的消息处理设备创建第一线程,并通过所述第一线程向所述消息处理设备发送所述第一广播消息,以使所述消息处理设备向其他共识节点对应的消息处理设备发送所述第一广播消息;撤销模块,撤销所述第一线程。
- 根据权利要求7所述的装置,其特征在于,所述装置与所述消息处理设备通过区域专线连接。
- 根据权利要求7所述的装置,其特征在于,所述装置还包括:接收模块,接收所述装置对应的消息处理设备发送的第二广播消息,所述第二广播消息是其他共识节点对应的消息处理设备广播的。
- 一种广播消息的装置,其特征在于,包括:第一接收模块,接收所述装置对应的共识节点发送的第一广播消息;发送模块,针对每个其他共识节点对应的消息处理设备创建第二线程,并通过该第二线程向该其他共识节点对应的消息处理设备发送所述第一广播消息;撤销模块,当确定该其他共识节点对应的消息处理设备接收到所述第一广播消息时,撤销该第二线程。
- 根据权利要求10所述的装置,其特征在于,所述撤销模块,通过各第二线程统计接收到的响应信号的数量,其中,响应信号是其他共识节点对应的消息处理设备在接收到所述第一广播消息后返回的;若统计的数量小于特定值,则通过各第二线程重新发送所述第一广播消息,直至统计的接收到的响应信号的数量不小于所述特定值为止,所述特定值为大于0的整数。
- 根据权利要求10所述的装置,其特征在于,所述装置还包括:第二接收模块,接收其他共识节点对应的消息处理设备广播的第二广播消息;将所述第二广播消息发送给所述共识节点。
Priority Applications (13)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2019528064A JP6859510B2 (ja) | 2017-03-24 | 2018-03-19 | メッセージをブロードキャストするための方法およびデバイス |
MX2019005982A MX2019005982A (es) | 2017-03-24 | 2018-03-19 | Metodo y dispositivo para mensajes de difusion. |
MYPI2019002875A MY192565A (en) | 2017-03-24 | 2018-03-19 | Method and device for broadcasting messages |
CA3044603A CA3044603C (en) | 2017-03-24 | 2018-03-19 | Method and device for broadcasting messages |
RU2019115869A RU2730039C1 (ru) | 2017-03-24 | 2018-03-19 | Способ и устройство для широковещательной передачи сообщений |
AU2018240583A AU2018240583B2 (en) | 2017-03-24 | 2018-03-19 | Method and device for broadcasting messages |
BR112019010520-4A BR112019010520B1 (pt) | 2017-03-24 | 2018-03-19 | Método implementado por computador para transmitir mensagens e sistema para transmitir mensagens |
EP18772238.4A EP3531618B1 (en) | 2017-03-24 | 2018-03-19 | Method and device for broadcasting messages |
KR1020197014976A KR102205750B1 (ko) | 2017-03-24 | 2018-03-19 | 메시지 브로드캐스트를 위한 방법 및 디바이스 |
PH12019501151A PH12019501151A1 (en) | 2017-03-24 | 2019-05-23 | Method and device for broadcasting messages |
ZA2019/03267A ZA201903267B (en) | 2017-03-24 | 2019-05-23 | Method and device for broadcasting messages |
US16/516,841 US10824485B2 (en) | 2017-03-24 | 2019-07-19 | Methods and devices for broadcasting messages |
US16/917,393 US11003514B2 (en) | 2017-03-24 | 2020-06-30 | Methods and devices for broadcasting messages |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710182459.1A CN107196772B (zh) | 2017-03-24 | 2017-03-24 | 一种广播消息的方法及装置 |
CN201710182459.1 | 2017-03-24 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/516,841 Continuation US10824485B2 (en) | 2017-03-24 | 2019-07-19 | Methods and devices for broadcasting messages |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2018171543A1 true WO2018171543A1 (zh) | 2018-09-27 |
Family
ID=59870952
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2018/079435 WO2018171543A1 (zh) | 2017-03-24 | 2018-03-19 | 一种广播消息的方法及装置 |
Country Status (16)
Country | Link |
---|---|
US (2) | US10824485B2 (zh) |
EP (1) | EP3531618B1 (zh) |
JP (1) | JP6859510B2 (zh) |
KR (1) | KR102205750B1 (zh) |
CN (1) | CN107196772B (zh) |
AU (1) | AU2018240583B2 (zh) |
BR (1) | BR112019010520B1 (zh) |
CA (1) | CA3044603C (zh) |
MX (1) | MX2019005982A (zh) |
MY (1) | MY192565A (zh) |
PH (1) | PH12019501151A1 (zh) |
RU (1) | RU2730039C1 (zh) |
SG (1) | SG10202100605QA (zh) |
TW (1) | TW201836372A (zh) |
WO (1) | WO2018171543A1 (zh) |
ZA (1) | ZA201903267B (zh) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110602249A (zh) * | 2019-09-29 | 2019-12-20 | 腾讯科技(深圳)有限公司 | 一种资源分配的方法以及相关装置 |
CN113012466A (zh) * | 2021-02-23 | 2021-06-22 | 中国联合网络通信集团有限公司 | 基于区块链的车位共享方法、用户节点、设备及存储介质 |
Families Citing this family (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107196772B (zh) * | 2017-03-24 | 2020-03-13 | 创新先进技术有限公司 | 一种广播消息的方法及装置 |
CN108052392B (zh) * | 2017-12-26 | 2020-12-25 | 成都质数斯达克科技有限公司 | 一种基于区块链的业务处理方法及装置 |
WO2020033048A1 (en) * | 2018-08-09 | 2020-02-13 | Hrl Laboratories, Llc | System and method for consensus ordering of broadcast messages |
US11277260B2 (en) * | 2019-09-17 | 2022-03-15 | International Business Machines Corporation | Off-chain notification of updates from a private blockchain |
US12099997B1 (en) | 2020-01-31 | 2024-09-24 | Steven Mark Hoffberg | Tokenized fungible liabilities |
CN112019599A (zh) * | 2020-03-16 | 2020-12-01 | 支付宝(杭州)信息技术有限公司 | 在区块链共识处理时进行处理消息同步的方法及装置 |
CN114358938A (zh) * | 2021-12-31 | 2022-04-15 | 杭州复杂美科技有限公司 | 交易、区块的广播方法、设备和存储介质 |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1980411A (zh) * | 2006-10-27 | 2007-06-13 | 华为技术有限公司 | 业务消息传输方法和系统 |
CN104579905A (zh) * | 2013-10-15 | 2015-04-29 | 阿里巴巴集团控股有限公司 | 消息传递方法和系统及mom服务器、接收端 |
CN104580253A (zh) * | 2015-01-30 | 2015-04-29 | 网易(杭州)网络有限公司 | 一种处理用户数据的方法及装置 |
US20160261685A1 (en) * | 2015-03-02 | 2016-09-08 | Dell Products L.P. | Deferred configuration or instruction execution using a secure distributed transaction ledger |
CN106446067A (zh) * | 2016-09-06 | 2017-02-22 | 联动优势科技有限公司 | 一种获取交易数据的方法和装置 |
CN107196772A (zh) * | 2017-03-24 | 2017-09-22 | 阿里巴巴集团控股有限公司 | 一种广播消息的方法及装置 |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8799402B2 (en) | 2007-06-29 | 2014-08-05 | Qualcomm Incorporated | Content sharing via mobile broadcast system and method |
US8199688B2 (en) | 2008-03-22 | 2012-06-12 | Qualcomm Incorporated | Signaling and management of broadcast-multicast waveform embedded in a unicast waveform |
CN101801113B (zh) * | 2009-02-05 | 2012-07-11 | 华为技术有限公司 | 网络拓扑分簇处理方法和处理系统 |
WO2012141677A1 (en) * | 2011-04-11 | 2012-10-18 | Hewlett-Packard Development Company, L.P. | Performing a task in a system having different types of hardware resources |
US20150223028A1 (en) | 2012-10-03 | 2015-08-06 | Qualcomm Incorporated | Broadcast/Multicast Used for M2M/MTC |
CN104079389A (zh) * | 2013-03-25 | 2014-10-01 | 株式会社Ntt都科摩 | 移动广播业务的重传方法 |
JP6326736B2 (ja) * | 2013-08-26 | 2018-05-23 | 富士通株式会社 | 中継装置、中継方法、及び中継プログラム |
US9397917B2 (en) | 2014-01-10 | 2016-07-19 | Huawei Technologies Co., Ltd. | System and method for zoning in software defined networks |
US10275772B2 (en) * | 2014-06-16 | 2019-04-30 | Bank Of America Corporation | Cryptocurrency risk detection system |
US9967334B2 (en) * | 2015-03-02 | 2018-05-08 | Dell Products Lp | Computing device configuration and management using a secure decentralized transaction ledger |
US10095558B2 (en) * | 2015-05-26 | 2018-10-09 | Cavium, Inc. | Systems and methods for offloading inline SSL processing to an embedded networking device |
JP6452156B2 (ja) * | 2015-09-03 | 2019-01-16 | 日本電信電話株式会社 | 許諾情報管理システム、利用者端末、権利者端末、許諾情報管理方法、および、許諾情報管理プログラム |
KR101701131B1 (ko) * | 2016-04-28 | 2017-02-13 | 주식회사 라피 | 이종간 블록체인 연결을 이용한 데이터 기록/검증 방법 및 시스템 |
-
2017
- 2017-03-24 CN CN201710182459.1A patent/CN107196772B/zh active Active
- 2017-11-21 TW TW106140237A patent/TW201836372A/zh unknown
-
2018
- 2018-03-19 MX MX2019005982A patent/MX2019005982A/es unknown
- 2018-03-19 KR KR1020197014976A patent/KR102205750B1/ko active IP Right Grant
- 2018-03-19 AU AU2018240583A patent/AU2018240583B2/en active Active
- 2018-03-19 BR BR112019010520-4A patent/BR112019010520B1/pt active IP Right Grant
- 2018-03-19 RU RU2019115869A patent/RU2730039C1/ru active
- 2018-03-19 WO PCT/CN2018/079435 patent/WO2018171543A1/zh unknown
- 2018-03-19 MY MYPI2019002875A patent/MY192565A/en unknown
- 2018-03-19 SG SG10202100605QA patent/SG10202100605QA/en unknown
- 2018-03-19 CA CA3044603A patent/CA3044603C/en active Active
- 2018-03-19 EP EP18772238.4A patent/EP3531618B1/en active Active
- 2018-03-19 JP JP2019528064A patent/JP6859510B2/ja active Active
-
2019
- 2019-05-23 PH PH12019501151A patent/PH12019501151A1/en unknown
- 2019-05-23 ZA ZA2019/03267A patent/ZA201903267B/en unknown
- 2019-07-19 US US16/516,841 patent/US10824485B2/en active Active
-
2020
- 2020-06-30 US US16/917,393 patent/US11003514B2/en active Active
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1980411A (zh) * | 2006-10-27 | 2007-06-13 | 华为技术有限公司 | 业务消息传输方法和系统 |
CN104579905A (zh) * | 2013-10-15 | 2015-04-29 | 阿里巴巴集团控股有限公司 | 消息传递方法和系统及mom服务器、接收端 |
CN104580253A (zh) * | 2015-01-30 | 2015-04-29 | 网易(杭州)网络有限公司 | 一种处理用户数据的方法及装置 |
US20160261685A1 (en) * | 2015-03-02 | 2016-09-08 | Dell Products L.P. | Deferred configuration or instruction execution using a secure distributed transaction ledger |
CN106446067A (zh) * | 2016-09-06 | 2017-02-22 | 联动优势科技有限公司 | 一种获取交易数据的方法和装置 |
CN107196772A (zh) * | 2017-03-24 | 2017-09-22 | 阿里巴巴集团控股有限公司 | 一种广播消息的方法及装置 |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110602249A (zh) * | 2019-09-29 | 2019-12-20 | 腾讯科技(深圳)有限公司 | 一种资源分配的方法以及相关装置 |
CN110602249B (zh) * | 2019-09-29 | 2021-10-22 | 腾讯科技(深圳)有限公司 | 一种资源分配的方法以及相关装置 |
CN113012466A (zh) * | 2021-02-23 | 2021-06-22 | 中国联合网络通信集团有限公司 | 基于区块链的车位共享方法、用户节点、设备及存储介质 |
Also Published As
Publication number | Publication date |
---|---|
CA3044603C (en) | 2021-01-19 |
CA3044603A1 (en) | 2018-09-27 |
EP3531618A4 (en) | 2019-10-02 |
CN107196772B (zh) | 2020-03-13 |
TW201836372A (zh) | 2018-10-01 |
MY192565A (en) | 2022-08-29 |
BR112019010520A2 (pt) | 2019-09-17 |
JP6859510B2 (ja) | 2021-04-14 |
EP3531618B1 (en) | 2022-01-12 |
US20190340042A1 (en) | 2019-11-07 |
ZA201903267B (en) | 2021-09-29 |
JP2020504928A (ja) | 2020-02-13 |
US10824485B2 (en) | 2020-11-03 |
BR112019010520B1 (pt) | 2022-04-26 |
SG10202100605QA (en) | 2021-02-25 |
RU2730039C1 (ru) | 2020-08-14 |
AU2018240583A1 (en) | 2019-06-06 |
US20200334090A1 (en) | 2020-10-22 |
KR20190069554A (ko) | 2019-06-19 |
MX2019005982A (es) | 2019-08-12 |
US11003514B2 (en) | 2021-05-11 |
AU2018240583B2 (en) | 2020-09-03 |
CN107196772A (zh) | 2017-09-22 |
EP3531618A1 (en) | 2019-08-28 |
PH12019501151A1 (en) | 2019-12-16 |
KR102205750B1 (ko) | 2021-01-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2018171543A1 (zh) | 一种广播消息的方法及装置 | |
TWI727120B (zh) | 一種發送交易資訊和共識驗證的方法及裝置 | |
JP6675518B1 (ja) | サービス要求を処理するための方法およびデバイス | |
KR102152556B1 (ko) | 서비스 프로세싱 및 합의 방법 및 디바이스 | |
WO2018219283A1 (zh) | 一种区块链共识方法及设备 | |
WO2018161901A1 (zh) | 一种共识方法及装置 | |
WO2018177235A1 (zh) | 一种区块链共识方法及装置 | |
WO2018177250A1 (zh) | 一种基于区块链的数据处理方法及设备 | |
KR20190118630A (ko) | 합의 검증을 위한 방법 및 장치 | |
TW201837748A (zh) | 一種基於區塊鏈的共識方法及裝置 | |
WO2019144809A1 (zh) | 一种服务更新方法及装置、系统 | |
CN116939006A (zh) | 一种消息传输方法、装置及设备 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 18772238 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 3044603 Country of ref document: CA |
|
ENP | Entry into the national phase |
Ref document number: 2019528064 Country of ref document: JP Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 20197014976 Country of ref document: KR Kind code of ref document: A |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112019010520 Country of ref document: BR |
|
ENP | Entry into the national phase |
Ref document number: 2018240583 Country of ref document: AU Date of ref document: 20180319 Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2018772238 Country of ref document: EP Effective date: 20190523 |
|
ENP | Entry into the national phase |
Ref document number: 112019010520 Country of ref document: BR Kind code of ref document: A2 Effective date: 20190523 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |