CN114070662A - Message bus system - Google Patents
Message bus system Download PDFInfo
- Publication number
- CN114070662A CN114070662A CN202010755868.8A CN202010755868A CN114070662A CN 114070662 A CN114070662 A CN 114070662A CN 202010755868 A CN202010755868 A CN 202010755868A CN 114070662 A CN114070662 A CN 114070662A
- Authority
- CN
- China
- Prior art keywords
- bus
- node
- message
- bus node
- nodes
- 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
- 230000006854 communication Effects 0.000 claims abstract description 25
- 238000004891 communication Methods 0.000 claims abstract description 24
- 230000007175 bidirectional communication Effects 0.000 claims description 12
- 230000005540 biological transmission Effects 0.000 claims description 5
- 238000010586 diagram Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000002457 bidirectional effect Effects 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 239000011159 matrix material Substances 0.000 description 1
- 238000000034 method Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000001681 protective effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L12/40006—Architecture of a communication node
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L12/40169—Flexible bus arrangements
- H04L12/40176—Flexible bus arrangements involving redundancy
- H04L12/40195—Flexible bus arrangements involving redundancy by using a plurality of nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/42—Loop networks
- H04L12/437—Ring fault isolation or reconfiguration
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Small-Scale Networks (AREA)
Abstract
The application provides a message bus system, it includes the data bus module, the data bus module includes three bus node group, arbitrary the bus node group includes three bus node, two-way communication connects between two arbitrary bus nodes in the three bus node, respectively have a bus node as the main bus node in the three bus node group, two-way communication connects between two arbitrary main bus nodes in the three main bus node. The message bus system can improve the fault tolerance rate.
Description
Technical Field
The application belongs to the technical field of middleware, and particularly relates to a message bus system.
Background
There are usually one or more bus nodes (also called nodes, proxies, and brokers) in a message bus system, and how to design the topology between these bus nodes to improve fault tolerance is a technical problem that those skilled in the art continuously push to solve.
Disclosure of Invention
The present application is directed to providing a message bus system for addressing the deficiencies of the prior art.
In order to solve the technical problem, the following technical scheme is adopted in the application: a message bus system comprising: the data bus module comprises three bus node groups, any bus node group comprises three bus nodes, any two bus nodes in the three bus nodes are in bidirectional communication connection, one bus node in each bus node group serves as a main bus node, and any two main bus nodes in the three main bus nodes are in bidirectional communication connection.
Optionally, two data transmission lines in opposite directions exist between any two of the three bus nodes, and the three main bus nodes are connected by TCP.
Optionally, in any of the bus node groups, a bus node with the smallest default number is used as a main bus node, and when the main bus node is down, a bus node with the smallest default number in the remaining bus nodes is used as the main bus node; or in any bus node group, the bus node with the largest default number is used as the main bus node, and when the main bus node goes down, the bus node with the largest default number in the rest bus nodes is used as the main bus node.
Optionally, in the bus node group, a master bus node synchronously stores the service node connection table of the data bus module and the bus node connection table of the data bus module, and the other bus nodes synchronously store the service node connection table of the bus node group and the bus node connection table of the bus node group.
Optionally, in any of the bus node groups, each bus node monitors heartbeats of two adjacent bus nodes at intervals of a first set time, and if the heartbeats of one adjacent bus node are not monitored after the last monitored heartbeat of the bus node exceeds a second set time, the communication connection with the bus node is disconnected, and the service node connection table and the bus node connection table stored in all the bus nodes are updated, wherein the second set time is longer than the first set time.
Optionally, the method further comprises: at least one agent node, each of which is in bidirectional communication connection with one bus node; the bus node is used for connecting a service node, and the agent node is used for connecting a consumption node; the agent node is used for storing subscription information of the consumption nodes connected with the agent node, the bus node is used for receiving messages from the connected service nodes and forwarding the messages to all the agent nodes, and the agent node is used for sending the received new messages to the consumption nodes corresponding to the subscription information successfully matched under the condition that the received new messages are successfully matched with the subscription information stored in the agent node.
Optionally, the message format of the message sent and received by the bus system includes: a first message header and a message body; the first message header includes a source bus node number and a destination bus node number.
Optionally, the first message header further includes: a source bus node group identification and a target bus node group identification.
Optionally, the message format further includes: an extension header flag and a second message header, the extension header flag identifying whether the message bus system has a proxy node; if the message bus structure has a proxy node, the second message header includes a message source handle number and a message source user number.
Optionally, the message format further includes a third message header, where the third message header includes a bus node message receiving time and a bus node message answering time.
Optionally, in the message format, the characters adopt UTF-8 protocol, and the endianness adopts BIG-ENDIAN network endianness.
Compared with the prior art, the beneficial effect of this application is: inside each bus node group, three bus nodes are in bidirectional communication with each other to form a bus node group, and closed-loop communication loops in two directions exist in the bus node group; even if the communication from one bus node to the other bus node is interrupted, a closed-loop communication loop in the other direction still exists, and the communication among the three bus nodes in the bus node group is not influenced; based on the same principle, closed-loop communication loops in two directions exist among the three main bus nodes; thus, the fault tolerance of the whole message bus system is high.
Drawings
Fig. 1 is a schematic structural diagram of a data bus module according to an embodiment of the present application.
Fig. 2 is a schematic structural diagram of a message bus system provided by an embodiment of the present application.
Fig. 3 is a flowchart of message pushing in an embodiment of the present application.
Fig. 4 is a schematic structural diagram of a message format provided by an embodiment of the present application.
Detailed Description
In this application, it is to be understood that terms such as "including" or "having" are intended to indicate the presence of the disclosed features, numbers, steps, acts, components, parts, or combinations thereof, and are not intended to preclude the presence or addition of one or more other features, numbers, steps, acts, components, parts, or combinations thereof.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
The application is further described with reference to examples of embodiments shown in the drawings.
As shown in fig. 1, an embodiment of the present application provides a message bus system, including: the data bus module 1 comprises three bus node groups, any bus node group comprises three bus nodes, any two bus nodes in the three bus nodes are in bidirectional communication connection, one bus node in each bus node group serves as a main bus node, and any two main bus nodes in the three main bus nodes are in bidirectional communication connection.
Inside each bus node group, three bus nodes are in bidirectional communication with each other to form a bus node group, and closed-loop communication loops in two directions exist in the bus node group; even if the communication from one bus node to the other bus node is interrupted, a closed-loop communication loop in the other direction still exists, and the communication among the three bus nodes in the bus node group is not influenced; based on the same principle, closed-loop communication loops in two directions exist among the three main bus nodes; thus, the fault tolerance of the whole message bus system is high.
It should be noted that a data bus module as shown in fig. 1 may be provided in the message bus system. Or 3 data center modules shown in fig. 1 may be provided, and each of the 3 data bus modules selects one main bus node to be connected with each other in bidirectional communication.
Optionally, two data transmission lines in opposite directions exist between any two of the three bus nodes, and the three main bus nodes are connected by TCP.
For example, two bus nodes realize bidirectional data transmission through two network cables, and one network cable is responsible for data transmission in one direction. Even if one network cable is pulled out by mistake, the communication in the bus node group is not influenced.
The main bus nodes are in soft connection, so that the reliability is higher, and a distributed message bus system can be realized.
Optionally, in any of the bus node groups, a bus node with the smallest default number is used as a main bus node, and when the main bus node is down, a bus node with the smallest default number in the remaining bus nodes is used as the main bus node; or in any bus node group, the bus node with the largest default number is used as the main bus node, and when the main bus node goes down, the bus node with the largest default number in the rest bus nodes is used as the main bus node.
I.e. the master bus node is responsible for the communication between the bus node groups. Each bus node, whether or not it is a master bus node, may connect one or more consuming nodes and one or more serving nodes. The selection of the main bus nodes is automatically completed, and the system fault tolerance is high. In a bus node group, assuming that a main bus node is down, one non-main bus node can be upgraded to the main bus node, a service node in communication connection with the original main bus node can automatically establish communication with other two bus nodes, and the normal operation of the whole system cannot be influenced.
Optionally, in the bus node group, a master bus node synchronously stores the service node connection table of the data bus module and the bus node connection table of the data bus module, and the other bus nodes synchronously store the service node connection table of the bus node group and the bus node connection table of the bus node group.
The service node connection table records connection information of service nodes, and the record information about one service node in one service node includes the following items, for example.
In the bus node group, the main bus node stores the connection information of all the service nodes connected with the data bus module, and the other bus nodes store the connection information of the service nodes connected with the bus node group.
The bus node connection table records the connection state between the bus nodes. The bus node connection table of the data bus module contains connection information of 3 bus node groups.
For example, referring to FIG. 1, assume bus nodes A, B and C are in one group, bus nodes D, E and F are in one group, and bus nodes G, H and I are in one group. The bus node connection table of the data bus module is for example of the form that contains 3 tables.
| TABLE 1 | A | | C |
| A | |||
| 1 | 1 | 1 | |
| B | 0 | 1 | 1 |
| |
1 | 1 | 1 |
| TABLE 2 | E | F | G |
| |
1 | 1 | 0 |
| F | 1 | 1 | 1 |
| |
1 | 1 | 1 |
| TABLE 3 | H | I | |
| H | |||
| 1 | 1 | 1 | |
| I | 0 | 1 | 1 |
| |
1 | 1 | 1 |
In the table, 1 indicates that the communication connection from one bus node to another bus node is normal, and 0 indicates that the communication connection from one bus node to another bus node is not normal.
The bus node connection table of the bus node group records the connection state inside the bus node group. For example, referring to FIG. 1, bus node A maintains an intra-group bus node connection table as follows. That is, for bus nodes other than the main bus node, only the connection states of the three bus nodes in the bus node group need to be recorded.
| Matrix array | A | B | C |
| A | 1 | 1 | 1 |
| B | 0 | 1 | 1 |
| |
1 | 1 | 1 |
In the table, 1 indicates that the communication connection from one bus node to another bus node is normal, and 0 indicates that the communication connection from one bus node to another bus node is not normal.
For example, referring to fig. 1, when a certain consuming node connected to bus node B sends a request to bus node B, bus node B will look up the service node connection table according to the service node identification (number for identifying service nodes providing the same service, there may be 1 or more service nodes providing the same service) and command (for identifying which specific service node among the service nodes providing the same service), and determine that a certain service node connected to bus node a provides the service to the request through a balancing algorithm. The bus node B transfers the request to the bus node A, the selected service node provides service, and then sends a response message to the bus node A, the bus node A sends the response message to the bus node B, and the bus node B sends the response message to the consumption node which makes the request.
Optionally, in any of the bus node groups, each bus node monitors heartbeats of two adjacent bus nodes at intervals of a first set time length, and if the heartbeat of one adjacent bus node is not monitored after the last monitored heartbeat of the bus node exceeds a second set time length, the communication connection with the bus node is disconnected, and a service node connection table and a bus node connection table stored in all the bus nodes are updated.
For example, referring to FIG. 1, bus nodes A, B and C listen to each other for heartbeats, once every 5 s. For example, if the bus node a does not detect the heartbeat of the bus node B after more than 15s, the bus node a disconnects the communication with the bus node B. The service node connection table and the bus node connection table held by all the bus nodes should be checked and guarded every 15 s.
Optionally, referring to fig. 2, the message bus system further comprises: at least one agent node, each of which is in bidirectional communication connection with one bus node; the bus node is used for connecting a service node, and the agent node is used for connecting a consumption node; the agent node is used for storing subscription information of the consumption nodes connected with the agent node, the bus node is used for receiving messages from the connected service nodes and forwarding the messages to all the agent nodes, and the agent node is used for sending the received new messages to the consumption nodes corresponding to the subscription information successfully matched under the condition that the received new messages are successfully matched with the subscription information stored in the agent node.
The consumer node is, for example, a smartphone or a program running on the smartphone. A service node is a device that provides a service. In contrast, the number of consumption nodes is much larger than that of service nodes, and the number of ports of the data bus module 1 is limited, so that the consumption nodes are hung on the data bus module 1 through the proxy nodes. Each broker node may be connected to a plurality of consuming nodes. The subscription service is operated by the agent node, so that the operation amount of the data bus module 1 is greatly reduced.
Referring to fig. 3, the entire communication process is as follows. Step 1, a consumption node (for example, a consumption node A) registers subscription information on a proxy node connected with the consumption node A. And step 2, the service node broadcasts the push message to each bus node of the data bus module 1. And 3, each bus node pushes the push message to each agent node connected with the bus node. And 4, after each agent node receives the new push message, matching operation is carried out, and whether a consumption node in the consumption nodes connected with the agent node needs the new push message or not is judged. And 5, the agent node sends the new push message to the consumption nodes needing the push message in the consumption nodes connected with the agent node.
For the above message bus system, the embodiment of the present application also provides a corresponding message format.
Optionally, referring to fig. 4, the message format of the message sent and received by the bus system includes:
the message format of the bus system for transmitting and receiving messages comprises: a first message header and a message body; the first message header includes a source bus node number and a destination bus node number.
The source bus node number indicates the logical number of the bus node to which the message sender is connected.
The target bus node number indicates the logical number of the bus node to which the message receiver is connected.
Of course, other fields may also be included in the message format.
Referring to the table below, in one particular embodiment, the fields of the message format are as follows. In the message format, characters adopt UTF-8 protocol, and byte order adopts BIG-ENDIAN network byte order.
The following table is information of fields in the first header in a specific example.
The following table is illustrative of the meaning represented by the part bits of the message header flag.
The following table is an illustration of the fields of the second header.
The following table is an illustration of the fields of the third message header.
| Field(s) | Format | Remarks for note |
| Bus node message reception time | INT64 | To the millisecond degree |
| Bus node reply message time | INT64 | To the millisecond degree |
The embodiments in the present application are described in a progressive manner, and the same and similar parts among the embodiments can be referred to each other, and each embodiment focuses on the differences from the other embodiments.
The protective scope of the present application is not limited to the above-described embodiments, and it is apparent that various modifications and variations can be made to the present application by those skilled in the art without departing from the scope and spirit of the present application. It is intended that the present application also include such modifications and variations as come within the scope of the appended claims and their equivalents.
Claims (11)
1. A message bus system, comprising: the data bus module comprises three bus node groups, any bus node group comprises three bus nodes, any two bus nodes in the three bus nodes are in bidirectional communication connection, one bus node in each bus node group serves as a main bus node, and any two main bus nodes in the three main bus nodes are in bidirectional communication connection.
2. The message bus system as recited in claim 1, wherein there are two data transmission lines in opposite directions between any two of the three bus nodes, and wherein there are TCP connections between the three primary bus nodes.
3. The message bus system as recited in claim 1, wherein the lowest numbered bus node of any of said group of bus nodes is designated as a primary bus node, and wherein when said primary bus node is down, the lowest numbered bus node of the remaining bus nodes is designated as the primary bus node; or
And in any bus node group, the bus node with the largest default number is used as the main bus node, and when the main bus node goes down, the bus node with the largest default number in the rest bus nodes is used as the main bus node.
4. The message bus system as recited in claim 1, wherein a master bus node of the bus node group synchronously stores the service node connection table of the data bus module and the bus node connection table of the data bus module, and the other bus nodes synchronously store the service node connection table of the bus node group and the bus node connection table of the bus node group.
5. The message bus system according to claim 1, wherein in any of the bus node groups, each bus node monitors heartbeats of two adjacent bus nodes at intervals of a first set time, if the heartbeat of one adjacent bus node is not monitored after exceeding a second set time since the last monitored heartbeat of the bus node, the communication connection with the bus node is disconnected, and the service node connection table and the bus node connection table stored in all the bus nodes are updated, and the second set time is longer than the first set time.
6. The message bus system as recited in claim 1, further comprising: at least one agent node, each of which is in bidirectional communication connection with one bus node; the bus node is used for connecting a service node, and the agent node is used for connecting a consumption node; the agent node is used for storing the subscription information of the consumption node connected with the agent node, and the bus node is used for receiving the message from the service node connected with the agent node and forwarding the message to all the agent nodes.
7. A messaging bus system as in any of claims 1-6, wherein the messaging format for the bus system to send and receive messages comprises: a first message header and a message body; the first message header includes a source bus node number and a destination bus node number.
8. The message bus system as recited in claim 7, wherein said first message header further comprises: a source bus node group identification and a target bus node group identification.
9. The message bus system as recited in claim 7, wherein the message format further comprises: an extension header flag and a second message header, the extension header flag identifying whether the message bus system has a proxy node; if the message bus structure has a proxy node, the second message header includes a message source handle number and a message source user number.
10. The message bus system as recited in claim 7, wherein the message format further comprises a third message header, the third message header comprising a bus node receive message time and a bus node reply message time.
11. The message bus system as claimed in claim 7, wherein the message format is such that characters are in UTF-8 protocol and endianness is in BIG-ENDIAN network endianness.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010755868.8A CN114070662A (en) | 2020-07-31 | 2020-07-31 | Message bus system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010755868.8A CN114070662A (en) | 2020-07-31 | 2020-07-31 | Message bus system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114070662A true CN114070662A (en) | 2022-02-18 |
Family
ID=80227369
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010755868.8A Pending CN114070662A (en) | 2020-07-31 | 2020-07-31 | Message bus system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114070662A (en) |
Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO1999048254A1 (en) * | 1998-03-17 | 1999-09-23 | Fujitsu Limited | Communication network and exchanger |
| EP1158712A1 (en) * | 2000-05-25 | 2001-11-28 | Lucent Technologies Inc. | Optical communication network architectures having reduced loss |
| US20040071468A1 (en) * | 2002-10-15 | 2004-04-15 | Sang-Hyun Doh | Optical multi-ring network for burst data communication |
| CN101262406A (en) * | 2008-04-10 | 2008-09-10 | 艾默生网络能源有限公司 | Two-way loop network system and its control method |
| CN101330423A (en) * | 2007-06-21 | 2008-12-24 | 日本电气株式会社 | Packet ring network system and packet transport method |
| JP2009219047A (en) * | 2008-03-12 | 2009-09-24 | Kddi Corp | Communication node devices constituting hierarchical ring network, network system, program, and method |
| CN102365554A (en) * | 2009-01-28 | 2012-02-29 | 海德沃特合作I有限公司 | Network based service policy implementation with network neutrality and user privacy |
| CN103457816A (en) * | 2013-08-29 | 2013-12-18 | 上海铁路通信有限公司 | Jumper connection looped network system applicable to rail transit vehicle |
| CN105516658A (en) * | 2015-11-30 | 2016-04-20 | 浙江宇视科技有限公司 | Monitoring equipment control method and device |
| CN108809791A (en) * | 2018-07-05 | 2018-11-13 | 福州福大海矽微电子有限公司 | A kind of more equipment loop configuration communication means and system |
| CN109525445A (en) * | 2018-12-29 | 2019-03-26 | 北京东土军悦科技有限公司 | Link switch-over method, link redundancy backup network and computer readable storage medium |
| CN110176974A (en) * | 2019-05-30 | 2019-08-27 | 郑州轨道交通信息技术研究院 | A kind of data sampling synchronous method, device and its unit of wide area relay protection |
| CN110199502A (en) * | 2016-11-23 | 2019-09-03 | 德吉润股份有限公司 | Arrange loop network |
| CN110838962A (en) * | 2019-11-18 | 2020-02-25 | 上海船舶研究设计院（中国船舶工业集团公司第六0四研究院） | Marine network system and marine system |
-
2020
- 2020-07-31 CN CN202010755868.8A patent/CN114070662A/en active Pending
Patent Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1065846A1 (en) * | 1998-03-17 | 2001-01-03 | Fujitsu Limited | Communication network and exchanger |
| WO1999048254A1 (en) * | 1998-03-17 | 1999-09-23 | Fujitsu Limited | Communication network and exchanger |
| EP1158712A1 (en) * | 2000-05-25 | 2001-11-28 | Lucent Technologies Inc. | Optical communication network architectures having reduced loss |
| US20040071468A1 (en) * | 2002-10-15 | 2004-04-15 | Sang-Hyun Doh | Optical multi-ring network for burst data communication |
| CN101330423A (en) * | 2007-06-21 | 2008-12-24 | 日本电气株式会社 | Packet ring network system and packet transport method |
| JP2009219047A (en) * | 2008-03-12 | 2009-09-24 | Kddi Corp | Communication node devices constituting hierarchical ring network, network system, program, and method |
| CN101262406A (en) * | 2008-04-10 | 2008-09-10 | 艾默生网络能源有限公司 | Two-way loop network system and its control method |
| CN102365554A (en) * | 2009-01-28 | 2012-02-29 | 海德沃特合作I有限公司 | Network based service policy implementation with network neutrality and user privacy |
| CN103457816A (en) * | 2013-08-29 | 2013-12-18 | 上海铁路通信有限公司 | Jumper connection looped network system applicable to rail transit vehicle |
| CN105516658A (en) * | 2015-11-30 | 2016-04-20 | 浙江宇视科技有限公司 | Monitoring equipment control method and device |
| CN110199502A (en) * | 2016-11-23 | 2019-09-03 | 德吉润股份有限公司 | Arrange loop network |
| CN108809791A (en) * | 2018-07-05 | 2018-11-13 | 福州福大海矽微电子有限公司 | A kind of more equipment loop configuration communication means and system |
| CN109525445A (en) * | 2018-12-29 | 2019-03-26 | 北京东土军悦科技有限公司 | Link switch-over method, link redundancy backup network and computer readable storage medium |
| CN110176974A (en) * | 2019-05-30 | 2019-08-27 | 郑州轨道交通信息技术研究院 | A kind of data sampling synchronous method, device and its unit of wide area relay protection |
| CN110838962A (en) * | 2019-11-18 | 2020-02-25 | 上海船舶研究设计院（中国船舶工业集团公司第六0四研究院） | Marine network system and marine system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105338086A (en) | Distributed message forwarding method | |
| US5588119A (en) | Method for correlating logical device names with a hub port in a local area network | |
| CN101009662A (en) | Message processing method, system and device based on the load balance technology | |
| CN101019385B (en) | Port aggregation across stack of devices | |
| EP1729481A3 (en) | Distributed kernel operating system | |
| CN101458637A (en) | Method, apparatus and system for implementing progress communication | |
| CN105939325A (en) | TCP (Transmission Control Protocol) bypass blocking method and device | |
| CN104618466A (en) | System for balancing load and controlling overload based on message transfer and control method of system | |
| CN108289055B (en) | Distributed real-time chat system and method based on Redis subscription service | |
| CN108449745B (en) | Method for automatically connecting and transmitting data by multiple Bluetooth devices in complex scene | |
| CN114070662A (en) | Message bus system | |
| CN114490100B (en) | Message queue telemetry transmission load balancing method, device and server | |
| JP4808731B2 (en) | Method for adjusting load between subsystems in a communication network system | |
| CN102055657B (en) | Load distributing method of fiber channel (FC) data message and FC exchanger system | |
| CN108462537A (en) | A kind of implementation method of one master and multiple slaves communication | |
| US8321585B2 (en) | Communication network system of bus network structure and message routing method using the system | |
| CN110365802A (en) | A kind of method for message transmission, message forwarding device and storage medium | |
| CN113204436A (en) | Message processing method, device, equipment and computer readable storage medium | |
| US8346892B2 (en) | Communication network system of bus network structure and method using the communication network system | |
| CN113364869B (en) | Block chain message transmission method, equipment and storage medium | |
| NZ328398A (en) | Dynamic channel allocation in wireless local loop radio systems | |
| CN102025583B (en) | Refresh control method, system and network node | |
| KR20210078115A (en) | Apparatus and method for forwarding message of private branch exchange system | |
| CN113542129B (en) | Single transmission method using signal linked list | |
| CN113923095B (en) | Cluster message forwarding method, system and 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 | ||
| CB02 | Change of applicant information |
Address after: 200082 floor 2-4, floor 1, No. 27, No. 23, Jingzhou Road, Yangpu District, Shanghai Applicant after: Shanghai international currency brokerage Co.,Ltd. Address before: 200120 rooms 2601-02 and 2605-08, Huiya building, No. 1233, Lujiazui Ring Road, China (Shanghai) pilot Free Trade Zone, Pudong New Area, Shanghai Applicant before: Shanghai international currency brokerage Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20220218 |
|
| WD01 | Invention patent application deemed withdrawn after publication |