CN113381863A - Call-type broadcasting system and method for block chain - Google Patents
Call-type broadcasting system and method for block chain Download PDFInfo
- Publication number
- CN113381863A CN113381863A CN202010163520.XA CN202010163520A CN113381863A CN 113381863 A CN113381863 A CN 113381863A CN 202010163520 A CN202010163520 A CN 202010163520A CN 113381863 A CN113381863 A CN 113381863A
- Authority
- CN
- China
- Prior art keywords
- data
- node
- broadcast
- queue
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
- G06F16/2471—Distributed queries
-
- 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/1881—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with schedule organisation, e.g. priority, sequence management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
Abstract
The invention discloses a call-in type broadcasting system and method for a block chain, which comprises a notification broadcaster, a data inquirer and a queue manager, wherein the notification broadcaster is connected with the data inquirer; the system broadcasts information characteristics to the network through a broadcaster, and queue management reads the broadcast information and manages the broadcast information; receiving broadcast from the node by using a data querier, querying broadcast abstract information, comparing abstract of node detail data, and querying the data; and performing queue acquisition operation on the data details which do not belong to the blacklist, finishing the processing of all requests through the data querier, and finishing the request response operation. The invention solves the problem that the broadcasting occupies a large amount of block time, and realizes the function of high-efficiency and quick broadcasting.
Description
Technical Field
The present invention relates to the field of block chain technology, and more particularly, to a call-in type broadcasting system and method for a block chain.
Background
As an infrastructure for solving the credit problem, in the future, more and more participants will be added, and more participants are added, which means that the network has more nodes, and more nodes mean that one item of data is received by all nodes in the network, more broadcasting time is required, and longer broadcasting time not only causes greater performance consumption, but also may cause a broadcasting queue of old data to block the queuing problem of new data.
If the data is broadcasted only to a part of nodes, a part of the data can never be received by the nodes of the processing block, which greatly reduces the reliability of the network and the experience of the upper layer application. How to provide a method, the problem of broadcast congestion can not be caused without using excessive occupied block time, and the arrival rate of network broadcast can be greatly improved to a certain extent, which becomes a problem to be solved urgently.
Disclosure of Invention
The invention aims to provide a calling type broadcasting system and method for a block chain.
A kind of calling type broadcasting system used for block chain, including notifying the broadcaster, data querier, queue manager; the method is characterized in that: the notification broadcaster is used for extracting message characteristics, and then broadcasting data with the characteristics to the network where the notification broadcaster is located, so that other nodes in the network can actively request the data with the characteristics; the data querier is used for placing data to be broadcasted into the data querier, and other nodes provide independent fast reading service when querying; the queue manager is used for managing a queue for notification broadcasting and a queue for query requests;
the system broadcasts information characteristics to the network through a broadcaster, and queue management reads the broadcast information and manages the broadcast information; receiving broadcast from the node by using a data querier, querying broadcast abstract information, comparing abstract of node detail data, and querying the data; and performing queue acquisition operation on the data details which do not belong to the blacklist, finishing the processing of all requests through the data querier, and finishing the request response operation.
Further, in the block chain network of the notification broadcaster, the broadcast is to a single node, or may be to a group of nodes; the query of the data querier is performed asynchronously.
Further, the queue manager respectively manages a broadcast queue and a query queue, wherein the broadcast queue is used for occupying a consultation queue preferentially, and a minimization principle is adopted in management; the query queue preferentially guarantees reliability.
Further, the notification broadcaster comprises a message digest module, a node list module and a data sending module;
the Message summarization module is used for extracting feature information of data to be broadcasted, extracting transaction IDs and block IDs in a block chain, uniformly calculating other data without the characteristics of the transaction IDs and the block IDs into a feature, and calculating a data summarization in an MD5Message-Digest Algorithm mode;
the node list module is used for recording a node list needing broadcasting and the characteristics of the nodes, recording the type of the broadcasting and the state of the broadcasted data;
the data sending module is used for sending data to the block chain.
Further, the data inquiry device comprises an interface management module, a blacklist management module and a data storage module;
the interface management module is used for providing query service for other nodes to acquire the data of the node, checking the legality of the other node when the other node requests access, and intercepting and stopping response processing on illegal requests;
the blackout and lighting management module is used for managing illegal addresses and illegal access characteristics, the illegal access characteristics are set during initial creation, dynamic update is carried out on subsequent access requests, and different characteristics are updated according to different safety requirements of different upper-layer applications; for accesses initiated by addresses already in the blacklist, responses will be denied, for access characteristic behaviors in the blacklist, responses will be denied;
the data storage module is used for storing data provided for external inquiry.
Further, the queue manager comprises a broadcast queue module and a query queue module;
the broadcast queue module is used for managing the order of data broadcast from the local, including the sending order and the priority, and the data related to the stability of the whole platform has the highest priority to be broadcast preferentially;
the query queue module is used for providing queuing capacity for external query requests, so that as many nodes as possible acquire data, and if the nodes possibly wait for timeout, the current queuing condition of the nodes is informed, so that the nodes can request the data at the proper time by using the proper timeout time.
A call-in type broadcasting method for a block chain, comprising the steps of:
s1 broadcasting an information feature to the network
S11 through the broadcaster: a node prepares to broadcast a piece of data, acquires the content of the data, extracts abstract information of the data, and an array manager extracts a broadcast array and a circulating broadcast array;
s12, the queue manager reads a piece of broadcast information, extracts the summary information of the broadcast, judges whether the summary information is consistent with the information to be sent, if not, continues the next cycle; if the information is consistent with the broadcast information, marking that the information is in the queue, and finishing the broadcast information processing; ending the broadcast queue cycle;
s13 the queue manager judges if the information is in the broadcast queue, if not, the broadcast information is added to the broadcast queue module; if the message is returned, the information is in the queue; a list of other local nodes;
s14 informs the broadcaster: a circular node list; all broadcast sending of all nodes is completed; proceeding to S2;
s2 query for a datum
S21 data querier: the node receives a broadcast, extracts the summary information of the broadcast and circulates the local data; finishing local data comparison, judging whether the data exists or not, if the data exists, discarding the broadcast by the data inquiry device, and ending the processing; if the data does not exist, the data querier: extracting the source address of the broadcast and establishing connection to the broadcast address;
s211, if the connection is available, the data inquiry device sends a request for inquiring the summary details to the node, the node returns the data details corresponding to the data summary, the node acquires the detail data, calculates the summary of the detail data, compares whether the calculated summary is the summary inquired by the node, and if the calculated summary is legal, stores the data to the local to finish the data inquiry of the node; if not, finishing the data query of the node, and switching to the next node which sends the query to the node to continue the query;
s212, if the connection can not be carried out, switching to the node to continue inquiring, and finishing the data inquiring operation of the node;
s22, the data inquiry device checks whether the local data is acquired, if so, the data inquiry operation is completed; if not, go to S23;
s23, extracting a local node list and a circular node list by the data inquiry device;
s24, completing all node circulation;
s25 the data inquirer checks whether the local data is existed or not again, if yes, the inquiry is finished; if not, returning the query failure;
s3 response request operation
S31 data inquiry device, node opens external request interface, receives an inquiry request, extracts the character of the inquiry request, extracts the source address of the inquiry request, extracts local blacklist list;
s32 data inquiry device, circulating black list; completing the matching of all black and white lists;
s321, the queue manager extracts a request queue to obtain the information of the request queue;
s322 the queue manager compares whether the request information is consistent with the information in the queue, if not, the queue manager continues to check the next request;
s323, if the request is consistent, the request already exists, the request is ignored, and the request operation is finished; a requested check is completed.
S33, the queue manager extracts the local request queue and circulates the request queue;
the queue manager extracts the request information S331,
s332, the data querier inquires local data according to the requested abstract, inquires the requested data and other data details, and returns the detail data to the request;
s333, the data querier does not inquire the data, informs the node that the node does not have the data, and completes the processing of the request.
And S34, the data querier completes the processing of all requests and completes the request response operation.
Further, the S14 notifies the broadcaster: the cyclic node list specifically includes:
s141, notifying the broadcaster to read the node information, and attempting to establish a connection with the node;
s142 if the connection cannot be established, notifying the broadcaster to continue trying the next node;
s143, if the connection can be established, the queue manager extracts the broadcast queue and circulates the broadcast queue;
s144 sends the broadcast information to the node through another piece of broadcast information of the broadcaster, and completes sending the broadcast information;
s145 notifies the broadcaster of completion of the node information transmission.
Further, the loop local data of S21 specifically includes:
s211, extracting local data, generating whether the received abstract is consistent with the local abstract, and if not, continuously comparing the abstract with the local abstract;
s212, if the data are consistent, the data querier marks that the data exist locally; the processing of the data is completed.
Further, the cyclic node list of S23 specifically includes:
s231, the data querier reads the node information, tries to establish connection with the node, skips the node if the connection cannot be established, and continues to try the next node;
s232, if the connection is available, the data querier initiates a request that the summary information is obvious for data query, the node returns obvious data, and the node returns summary information of detailed data;
s233, the data querier calculates the abstract information of the returned obvious data, compares the calculated abstract information with the queried abstract information, if not, skips the node, and continues to try the next node; if the data is consistent and legal, the data is stored locally, and the node data request is completed.
Compared with the prior art, the method and the device solve the problem that the broadcasting occupies a large amount of block time, and realize the function of high-efficiency and quick broadcasting.
Drawings
FIG. 1 is a schematic diagram of a paging type broadcasting system for block chains according to the present invention
Fig. 2 is a schematic diagram of the components of the notification broadcaster of the present invention;
FIG. 3 is a schematic diagram of the data query engine according to the present invention;
FIG. 4 is a schematic diagram of the queue manager according to the present invention;
fig. 5 is a flow chart of a call-in type broadcasting method for a block chain according to the present invention;
FIG. 6 is a schematic flow chart of S14 according to the present invention;
FIG. 7 is a schematic flow chart of S21 according to the present invention;
FIG. 8 is a schematic flow chart of S23 according to the present invention;
wherein: 100 informs broadcaster, 200 data querier, 300 queue manager; a 101 message abstract module, a 102 node list module and a 103 data sending module; 201 interface management module, 202 blacklist management module, 203 data storage module; 301 broadcast queue module, 302 query queue module.
Detailed Description
The invention is described in further detail below with reference to the figures and specific examples. It should be noted that the technical features involved in the embodiments of the present invention described below may be combined with each other as long as they do not conflict with each other.
As shown in fig. 1, a call-in type broadcasting system for a block chain includes a notification broadcaster 100, a data inquirer 200, a queue manager 300; the method is characterized in that: the notification broadcaster 100 is configured to extract a message feature, and then broadcast data having the feature to a network where the notification broadcaster is located, so that other nodes in the network actively request the data of the feature; the data querier 200 is used for placing data to be broadcasted into the data querier, and other nodes provide independent fast reading service when querying; the queue manager 300 is used for managing a queue for notification broadcasting and a queue for query requests;
the system broadcasts information characteristics to the network through the broadcaster 100, and the queue management reads the broadcast information and manages the broadcast information; receiving broadcast from the node by using the data inquirer 200, inquiring broadcast abstract information, comparing the abstract of node detail data, and inquiring the data; and performing queue acquisition operation on the data details which do not belong to the blacklist, completing the processing of all requests through the data querier 200, and completing the request response operation.
In the blockchain network of the notification broadcaster 100, a broadcast is to a single node, or may be to a group of nodes; the querying of the data querier 200 is performed asynchronously. The broadcast can independently and quickly read and independently provide service, and the query is asynchronously carried out, so the broadcast does not occupy the broadcast time, the broadcast is lighter and faster and easier, a message characteristic is easier to spread all over the network in a short time, other nodes in the network can prepare in advance, at least the time of 'one data downloading time' can be saved, more waiting time consumed by the data waiting for broadcast can be saved, the data acquisition rate in the network is greatly improved, in addition, the block branching is greatly reduced in the block chain network, and blocks can be forged by the nodes in the block chain if the nodes do not wait for the blocks required by the nodes.
The queue manager 300 manages a broadcast queue and a query queue respectively, the broadcast queue is used for occupying a consultation queue preferentially, and a minimization principle is adopted in management; the query queue preferentially guarantees reliability. Broadcast and query are completely different concepts with different priorities, and the queue manager 300 manages the broadcast queue and the query queue separately. The quality of the broadcast queue greatly affects the reliability of the block chain network, so the broadcast queue is used as a queue which preferentially occupies resources, a minimization principle is adopted in management, as little data as possible is broadcast, in the query queue, the most important constraint factor is the time that an opposite side is willing to wait, and the time does not occupy the block time, so the queue in the position preferentially ensures the reliability, and ensures that as many nodes as possible obtain data.
As shown in fig. 2, the notification broadcaster 100 includes a message digest module 101, a node list module 102, and a data transmission module 103;
the Message summarization module 101 is configured to extract feature information of data to be broadcast, extract a transaction ID and a block ID in a block chain, uniformly calculate a feature for other data without the characteristics of the transaction ID and the block ID, and calculate a data summary in an MD5Message-Digest Algorithm;
the node list module 102 is configured to record a node list that needs to be broadcasted, characteristics of the node, a type of the broadcast, and a state of the broadcasted data;
the data sending module 103 is configured to send data to a blockchain; the node list module is mainly used for recording a node list needing broadcasting, whether the characteristics of the nodes need one-to-one broadcasting or group broadcasting, and recording the state of the broadcasted data. In different upper-layer services, the node list is not necessarily fixed, in a public chain of a block chain, the node list is usually updated and maintained by a node manager, in a alliance chain and a private chain, the node list is usually a fixed effective node, and as the node is supposed to be credible and effective, the node manager is not used for specially adding, modifying and deleting the node; no matter how the node list is obtained or managed, the implementation of the invention is not influenced, the core of the system is how to send the node list, and the node list is not sent to a person, and different sending objects exist in different upper-layer services, which do not restrict the application range of the invention.
As shown in fig. 3, the data query device 200 includes an interface management module 201, a blacklist management module 202, and a data storage module 203;
the interface management module 201 is configured to provide an external query service for other nodes to obtain data of the node, check the validity of the other node when the other node requests access, and intercept and stop responding to an illegal request;
the blackout and blackout management module 202 is configured to manage an illegal address and an illegal access characteristic, where the illegal access characteristic is set during initial creation, dynamically updated in a subsequent access request, and updated with different characteristics according to different security requirements of different upper-layer applications; for accesses initiated by addresses already in the blacklist, responses will be denied, for access characteristic behaviors in the blacklist, responses will be denied;
the data storage module 203 is used for storing data provided for external queries.
As shown in fig. 4, the queue manager 300 includes a broadcast queue module 301 and a query queue module 302;
the broadcast queue module 301 is configured to manage the order of data broadcast from local, including the sending order and priority, where data related to the stability of the entire platform will have the highest priority for broadcast;
the query queue module 302 is used to provide a queuing capability for external query requests, so that as many nodes as possible can obtain data, and if a node may wait for timeout, the current queuing situation will be notified to the node, so that the node can request data at an appropriate time with an appropriate timeout.
As shown in fig. 5 to 8, a call-in type broadcasting method for a block chain includes the steps of:
s1 broadcasting an information feature to the network
S11 through the broadcaster: a node prepares to broadcast a piece of data, acquires the content of the data, extracts abstract information of the data, and an array manager extracts a broadcast array and a circulating broadcast array;
s12, the queue manager reads a piece of broadcast information, extracts the summary information of the broadcast, judges whether the summary information is consistent with the information to be sent, if not, continues the next cycle; if the information is consistent with the broadcast information, marking that the information is in the queue, and finishing the broadcast information processing; ending the broadcast queue cycle;
s13 the queue manager judges if the information is in the broadcast queue, if not, the broadcast information is added to the broadcast queue module; if the message is returned, the information is in the queue; a list of other local nodes;
s14 informs the broadcaster: a circular node list; all broadcast sending of all nodes is completed; proceeding to S2;
said S14 informs the broadcaster: the cyclic node list specifically includes: s141, notifying the broadcaster to read the node information, and attempting to establish a connection with the node; s142 if the connection cannot be established, notifying the broadcaster to continue trying the next node; s143, if the connection can be established, the queue manager extracts the broadcast queue and circulates the broadcast queue; s144 sends the broadcast information to the node through another piece of broadcast information of the broadcaster, and completes sending the broadcast information; s145 notifies the broadcaster of completion of the node information transmission;
s2 query for a datum
S21 data querier: the node receives a broadcast, extracts the summary information of the broadcast and circulates the local data; finishing local data comparison, judging whether the data exists or not, if the data exists, discarding the broadcast by the data inquiry device, and ending the processing; if the data does not exist, the data querier: extracting the source address of the broadcast and establishing connection to the broadcast address; the loop local data of S21 is specifically: s211, extracting local data, generating whether the received abstract is consistent with the local abstract, and if not, continuously comparing the abstract with the local abstract; s212, if the data are consistent, the data querier marks that the data exist locally; the processing of the data is completed.
S211, if the connection is available, the data inquiry device sends a request for inquiring the summary details to the node, the node returns the data details corresponding to the data summary, the node acquires the detail data, calculates the summary of the detail data, compares whether the calculated summary is the summary inquired by the node, and if the calculated summary is legal, stores the data to the local to finish the data inquiry of the node; if not, finishing the data query of the node, and switching to the next node which sends the query to the node to continue the query;
s212, if the connection can not be carried out, switching to the node to continue inquiring, and finishing the data inquiring operation of the node;
s22, the data inquiry device checks whether the local data is acquired, if so, the data inquiry operation is completed; if not, go to S23;
s23, extracting a local node list and a circular node list by the data inquiry device; the cyclic node list of S23 specifically includes: s231, the data querier reads the node information, tries to establish connection with the node, skips the node if the connection cannot be established, and continues to try the next node; s232, if the connection is available, the data querier initiates a request that the summary information is obvious for data query, the node returns obvious data, and the node returns summary information of detailed data; s233, the data querier calculates the abstract information of the returned obvious data, compares the calculated abstract information with the queried abstract information, if not, skips the node, and continues to try the next node; if the data is consistent and the data is legal, the data is stored locally, and the node data request is completed;
s24, completing all node circulation;
s25 the data inquirer checks whether the local data is existed or not again, if yes, the inquiry is finished; if not, returning the query failure;
s3 response request operation
S31 data inquiry device, node opens external request interface, receives an inquiry request, extracts the character of the inquiry request, extracts the source address of the inquiry request, extracts local blacklist list;
s32 data inquiry device, circulating black list; completing the matching of all black and white lists;
s321, the queue manager extracts a request queue to obtain the information of the request queue;
s322 the queue manager compares whether the request information is consistent with the information in the queue, if not, the queue manager continues to check the next request;
s323, if the request is consistent, the request already exists, the request is ignored, and the request operation is finished; a requested check is completed.
S33, the queue manager extracts the local request queue and circulates the request queue;
the queue manager extracts the request information S331,
s332, the data querier inquires local data according to the requested abstract, inquires the requested data and other data details, and returns the detail data to the request;
s333, the data querier does not inquire the data, informs the node that the node does not have the data, and completes the processing of the request.
And S34, the data querier completes the processing of all requests and completes the request response operation.
The above-mentioned embodiments are only preferred embodiments of the present invention, and do not limit the technical scope of the present invention, so that the changes and modifications made by the claims and the specification of the present invention should fall within the scope of the present invention.
Claims (10)
1. A kind of calling type broadcasting system used for block chain, including notifying the broadcaster, data querier, queue manager; the method is characterized in that: the notification broadcaster is used for extracting message characteristics, and then broadcasting data with the characteristics to the network where the notification broadcaster is located, so that other nodes in the network can actively request the data with the characteristics; the data querier is used for placing data to be broadcasted into the data querier, and other nodes provide independent fast reading service when querying; the queue manager is used for managing a queue for notification broadcasting and a queue for query requests;
the system broadcasts information characteristics to the network through a broadcaster, and queue management reads the broadcast information and manages the broadcast information; receiving broadcast from the node by using a data querier, querying broadcast abstract information, comparing abstract of node detail data, and querying the data; and performing queue acquisition operation on the data details which do not belong to the blacklist, finishing the processing of all requests through the data querier, and finishing the request response operation.
2. A call-in type broadcasting system for a block chain as claimed in claim 1, wherein: in the block chain network of the notification broadcaster, the broadcast is to a single node, or to a group of nodes; the query of the data querier is performed asynchronously.
3. A call-in type broadcasting system for a block chain as claimed in claim 1, wherein: the queue manager respectively manages a broadcast queue and a query queue, the broadcast queue is used for occupying a consultation queue preferentially, and a minimization principle is adopted in management; the query queue preferentially guarantees reliability.
4. A call-in type broadcasting system for a block chain as claimed in claim 1, wherein: the notification broadcaster comprises a message abstract module, a node list module and a data sending module;
the Message summarization module is used for extracting feature information of data to be broadcasted, extracting transaction IDs and block IDs in a block chain, uniformly calculating other data without the characteristics of the transaction IDs and the block IDs into a feature, and calculating a data summarization in an MD5Message-DigestAlgorithm mode;
the node list module is used for recording a node list needing broadcasting and the characteristics of the nodes, recording the type of the broadcasting and the state of the broadcasted data;
the data sending module is used for sending data to the block chain.
5. A call-in type broadcasting system for a block chain as claimed in claim 1, wherein: the data inquiry device comprises an interface management module, a blacklist management module and a data storage module;
the interface management module is used for providing query service for other nodes to acquire the data of the node, checking the legality of the other node when the other node requests access, and intercepting and stopping response processing on illegal requests;
the blackout and lighting management module is used for managing illegal addresses and illegal access characteristics, the illegal access characteristics are set during initial creation, dynamic update is carried out on subsequent access requests, and different characteristics are updated according to different safety requirements of different upper-layer applications; for accesses initiated by addresses already in the blacklist, responses will be denied, for access characteristic behaviors in the blacklist, responses will be denied;
the data storage module is used for storing data provided for external inquiry.
6. A call-in type broadcasting system for a block chain as claimed in claim 1, wherein: the queue manager comprises a broadcast queue module and a query queue module;
the broadcast queue module is used for managing the order of data broadcast from the local, including the sending order and the priority, and the data related to the stability of the whole platform has the highest priority to be broadcast preferentially;
the query queue module is used for providing queuing capacity for external query requests, so that as many nodes as possible acquire data, and if the nodes possibly wait for timeout, the current queuing condition of the nodes is informed, so that the nodes can request the data at the proper time by using the proper timeout time.
7. A call-in type broadcasting method for a block chain, comprising the steps of:
s1 broadcasting an information feature to the network
S11 through the broadcaster: a node prepares to broadcast a piece of data, acquires the content of the data, extracts abstract information of the data, and an array manager extracts a broadcast array and a circulating broadcast array;
s12, the queue manager reads a piece of broadcast information, extracts the summary information of the broadcast, judges whether the summary information is consistent with the information to be sent, if not, continues the next cycle; if the information is consistent with the broadcast information, marking that the information is in the queue, and finishing the broadcast information processing; ending the broadcast queue cycle;
s13 the queue manager judges if the information is in the broadcast queue, if not, the broadcast information is added to the broadcast queue module; if the message is returned, the information is in the queue; a list of other local nodes;
s14 informs the broadcaster: a circular node list; all broadcast sending of all nodes is completed; proceeding to S2;
s2 query for a datum
S21 data querier: the node receives a broadcast, extracts the summary information of the broadcast and circulates the local data; finishing local data comparison, judging whether the data exists or not, if the data exists, discarding the broadcast by the data inquiry device, and ending the processing; if the data does not exist, the data querier: extracting the source address of the broadcast and establishing connection to the broadcast address;
s211, if the connection is available, the data inquiry device sends a request for inquiring the summary details to the node, the node returns the data details corresponding to the data summary, the node acquires the detail data, calculates the summary of the detail data, compares whether the calculated summary is the summary inquired by the node, and if the calculated summary is legal, stores the data to the local to finish the data inquiry of the node; if not, finishing the data query of the node, and switching to the next node which sends the query to the node to continue the query;
s212, if the connection can not be carried out, switching to the node to continue inquiring, and finishing the data inquiring operation of the node;
s22, the data inquiry device checks whether the local data is acquired, if so, the data inquiry operation is completed; if not, go to S23;
s23, extracting a local node list and a circular node list by the data inquiry device;
s24, completing all node circulation;
s25 the data inquirer checks whether the local data is existed or not again, if yes, the inquiry is finished; if not, returning the query failure;
s3 response request operation
S31 data inquiry device, node opens external request interface, receives an inquiry request, extracts the character of the inquiry request, extracts the source address of the inquiry request, extracts local blacklist list;
s32 data inquiry device, circulating black list; completing the matching of all black and white lists;
s321, the queue manager extracts a request queue to obtain the information of the request queue;
s322 the queue manager compares whether the request information is consistent with the information in the queue, if not, the queue manager continues to check the next request;
s323, if the request is consistent, the request already exists, the request is ignored, and the request operation is finished; a requested check is completed.
S33, the queue manager extracts the local request queue and circulates the request queue;
the queue manager extracts the request information S331,
s332, the data querier inquires local data according to the requested abstract, inquires the requested data and other data details, and returns the detail data to the request;
s333, the data querier does not inquire the data, informs the node that the node does not have the data, and completes the processing of the request.
And S34, the data querier completes the processing of all requests and completes the request response operation.
8. A method of claim 7 for a hailing type broadcast of a block chain, characterized in that: said S14 informs the broadcaster: the cyclic node list specifically includes:
s141, notifying the broadcaster to read the node information, and attempting to establish a connection with the node;
s142 if the connection cannot be established, notifying the broadcaster to continue trying the next node;
s143, if the connection can be established, the queue manager extracts the broadcast queue and circulates the broadcast queue;
s144 sends the broadcast information to the node through another piece of broadcast information of the broadcaster, and completes sending the broadcast information;
s145 notifies the broadcaster of completion of the node information transmission.
9. A method of claim 7 for a hailing type broadcast of a block chain, characterized in that: the loop local data of S21 is specifically:
s211, extracting local data, generating whether the received abstract is consistent with the local abstract, and if not, continuously comparing the abstract with the local abstract;
s212, if the data are consistent, the data querier marks that the data exist locally; the processing of the data is completed.
10. A method of claim 7 for a hailing type broadcast of a block chain, characterized in that: the cyclic node list of S23 specifically includes:
s231, the data querier reads the node information, tries to establish connection with the node, skips the node if the connection cannot be established, and continues to try the next node;
s232, if the connection is available, the data querier initiates a request that the summary information is obvious for data query, the node returns obvious data, and the node returns summary information of detailed data;
s233, the data querier calculates the abstract information of the returned obvious data, compares the calculated abstract information with the queried abstract information, if not, skips the node, and continues to try the next node; if the data is consistent and legal, the data is stored locally, and the node data request is completed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010163520.XA CN113381863A (en) | 2020-03-10 | 2020-03-10 | Call-type broadcasting system and method for block chain |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010163520.XA CN113381863A (en) | 2020-03-10 | 2020-03-10 | Call-type broadcasting system and method for block chain |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113381863A true CN113381863A (en) | 2021-09-10 |
Family
ID=77569522
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010163520.XA Pending CN113381863A (en) | 2020-03-10 | 2020-03-10 | Call-type broadcasting system and method for block chain |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113381863A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106506638A (en) * | 2016-11-04 | 2017-03-15 | 江苏通付盾科技有限公司 | Block storage method and device in block chain |
| CN106789908A (en) * | 2016-11-23 | 2017-05-31 | 江苏通付盾科技有限公司 | Block common recognition method for building up and system in block chain |
| CN107493227A (en) * | 2017-08-29 | 2017-12-19 | 山东科技大学 | A kind of instant active information push method towards Coal Mine Disasters early warning demand |
| CN109471744A (en) * | 2018-11-21 | 2019-03-15 | 北京蓝石环球区块链科技有限公司 | The more subchain system architectures of main chain adduction row based on block chain |
| WO2019100991A1 (en) * | 2017-11-27 | 2019-05-31 | 北京京东金融科技控股有限公司 | Information processing method, device and system, storage medium, and electronic device |
| CN110838924A (en) * | 2019-11-19 | 2020-02-25 | 北京沃东天骏信息技术有限公司 | Block transmission method and device |
-
2020
- 2020-03-10 CN CN202010163520.XA patent/CN113381863A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106506638A (en) * | 2016-11-04 | 2017-03-15 | 江苏通付盾科技有限公司 | Block storage method and device in block chain |
| CN106789908A (en) * | 2016-11-23 | 2017-05-31 | 江苏通付盾科技有限公司 | Block common recognition method for building up and system in block chain |
| CN107493227A (en) * | 2017-08-29 | 2017-12-19 | 山东科技大学 | A kind of instant active information push method towards Coal Mine Disasters early warning demand |
| WO2019041721A1 (en) * | 2017-08-29 | 2019-03-07 | 山东科技大学 | Instant active information push method oriented at early warning requirement for coal mining disasters |
| WO2019100991A1 (en) * | 2017-11-27 | 2019-05-31 | 北京京东金融科技控股有限公司 | Information processing method, device and system, storage medium, and electronic device |
| CN109471744A (en) * | 2018-11-21 | 2019-03-15 | 北京蓝石环球区块链科技有限公司 | The more subchain system architectures of main chain adduction row based on block chain |
| CN110838924A (en) * | 2019-11-19 | 2020-02-25 | 北京沃东天骏信息技术有限公司 | Block transmission method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20200404073A1 (en) | Method, apparatus, and equipment for exposing edge network capability, and storage medium | |
| CN109673037B (en) | Network function discovery method and equipment | |
| US20040085980A1 (en) | System and method for maintaining transaction cache consistency in mobile computing environment | |
| US10616784B2 (en) | Methods and apparatus for management of data privacy | |
| WO2021051922A1 (en) | Method for transmitting data in group, terminal and computer-readable storage medium | |
| US20200359220A1 (en) | Network Access Control Method, Apparatus, and Device | |
| CN114364031B (en) | Service providing method, device and storage medium | |
| KR20230043919A (en) | service request processing | |
| CN113381863A (en) | Call-type broadcasting system and method for block chain | |
| RU2767991C1 (en) | Information processing method, terminal device and data medium | |
| CN111796772A (en) | Cache management method, cache node and distributed storage system | |
| KR101264315B1 (en) | Method, apparatus and record carrier for interworking between applications on a mobile platform | |
| CN116996376A (en) | Method, device, equipment and storage medium for updating configuration of fixed network terminal | |
| CN101854678A (en) | Access control method and device | |
| WO2023056713A1 (en) | Cloud platform binding method and system for internet of things card, and device and medium | |
| CN113973294B (en) | Signaling processing method, network warehouse function network element and communication system | |
| CN111277982B (en) | Face retrieval method and system for reducing IOT platform server consumption | |
| CN115514797A (en) | Backup SMF discovery method, device, electronic equipment and medium | |
| CN114945173B (en) | Cross-PLMN signaling forwarding method, electronic equipment and storage medium | |
| CN111615073B (en) | Real-time data sharing method, device and system for 5G base station | |
| CN112235414B (en) | File caching method, operator server and MEC server | |
| CN116415303A (en) | Authorization token processing method and system | |
| CN112105069B (en) | Internet edge computing wireless network switching method and system | |
| CN113535415B (en) | Resource acquisition method and terminal | |
| CN115460695A (en) | Paging priority access method, base station, and computer-readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |