CN114938388B - Distributed data transmission method, device, system and storage medium - Google Patents

Distributed data transmission method, device, system and storage medium Download PDF

Info

Publication number
CN114938388B
CN114938388B CN202210859992.8A CN202210859992A CN114938388B CN 114938388 B CN114938388 B CN 114938388B CN 202210859992 A CN202210859992 A CN 202210859992A CN 114938388 B CN114938388 B CN 114938388B
Authority
CN
China
Prior art keywords
message
transmission
terminal device
type
subscription
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.)
Active
Application number
CN202210859992.8A
Other languages
Chinese (zh)
Other versions
CN114938388A (en
Inventor
黄文君
陈晖�
刘志勇
张帅
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Zhongkong Technology Co ltd
Original Assignee
Zhejiang Supcon Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Zhejiang Supcon Technology Co Ltd filed Critical Zhejiang Supcon Technology Co Ltd
Priority to CN202210859992.8A priority Critical patent/CN114938388B/en
Publication of CN114938388A publication Critical patent/CN114938388A/en
Application granted granted Critical
Publication of CN114938388B publication Critical patent/CN114938388B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/31—Flow control; Congestion control by tagging of packets, e.g. using discard eligibility [DE] bits
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/50—Queue scheduling

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)

Abstract

The application provides a method, a device, a system and a storage medium for transmitting distributed data, and belongs to the technical field of data communication. The method comprises the following steps: generating a transmission message and attribute information of the transmission message through a first terminal device; the first terminal equipment adopts the message queue transmission type to send the transmission message to the target server-side equipment; determining a second terminal device by the target server device according to a preset subscription relationship and a message identifier, wherein the subscription relationship is used for indicating a mapping relationship between each message queue transmission type and the terminal device, and each terminal device subscribes one message queue transmission type respectively; and the target server-side equipment sends the transmission message to the second terminal equipment in a message queue transmission type mode. The method and the device can reduce the message complexity of the whole system and reduce the delay of message transmission.

Description

Distributed data transmission method, device, system and storage medium
Technical Field
The present application relates to the field of data communication technologies, and in particular, to a method, an apparatus, a system, and a storage medium for transmitting distributed data.
Background
In a distributed system, in order to implement operations such as subscription, publishing, receiving, etc. of data, mutual transmission of messages between a terminal device and a server device in the distributed system is generally required.
In the prior art, when data is subscribed, published and received, a server device often receives data published by a terminal device, and then according to the subscription condition, the server device transmits the data to the corresponding terminal device in all available message queue transmission modes, and the terminal device selects one of the message queue transmission modes to receive the data based on a required receiving condition.
However, in the implementation process of the method, since all available message queue transmission modes are required for transmission, there is repeated transmission of data when the server device sends data to the terminal device, which increases the message complexity and message transmission delay of the whole system.
Disclosure of Invention
The present application aims to provide a method, an apparatus, a system and a storage medium for transmitting distributed data, which can reduce the message complexity of the whole system and reduce the delay of message transmission.
The embodiment of the application is realized as follows:
in one aspect of the embodiments of the present application, a method for transmitting distributed data is provided, where the method is applied to a distributed system, the distributed system includes multiple terminal devices and multiple server devices, and each server device is in communication connection with each terminal device, and the method includes:
generating a transmission message and attribute information of the transmission message through a first terminal device, wherein the transmission message comprises a message body and a message identifier, and the attribute information of the transmission message comprises: message queue transmission type and target server equipment information;
the first terminal equipment adopts the message queue transmission type to send the transmission message to the target server-side equipment;
determining a second terminal device by the target server device according to a preset subscription relationship and a message identifier, wherein the subscription relationship is used for indicating a mapping relationship between each message queue transmission type and the terminal device, and each terminal device subscribes one message queue transmission type respectively;
and the target server-side equipment sends the transmission message to the second terminal equipment in a message queue transmission type mode.
Optionally, before the target server device determines the second terminal device according to the preconfigured subscription relationship and the message identifier, the method further includes:
determining service process information through the second terminal device, wherein the service process information comprises: identification of the business process, and a message queue type used by the release business process;
the second terminal equipment sends the business process information to the target server equipment corresponding to the identification of the business process;
and establishing a subscription relation by the target server-side equipment based on the business process information.
Optionally, determining, by the second terminal device, the service progress information includes:
determining a subscription type, the subscription type comprising: a generic subscription type and a targeted subscription type;
if the subscription type is a generic subscription type, determining type set information of a message queue used by a publishing service process, and determining service process information based on the type set information;
and if the subscription type is the oriented subscription type, determining the type information of the message queue used by the issuing business process, and determining the business process information based on the type information.
Optionally, after the target server device sends the transmission message to the second terminal device in a message queue transmission type, the method further includes:
determining whether a buffer queue of the second terminal device contains a transmission message;
if not, the second terminal device recalls the transmission message, and stores the transmission message and the attribute information of the transmission message.
Optionally, after determining whether the buffer queue of the second terminal device contains the transmission message, the method further includes:
and if the buffer queue of the second terminal equipment contains the transmission message, the second terminal equipment stores the transmission message and the attribute information of the transmission message.
Optionally, after the second terminal device stores the transmission message and the attribute information of the transmission message, the method further includes:
judging whether all transmission messages in a buffer queue of the second terminal equipment are received by the corresponding second terminal equipment;
and if so, deleting the transmission message with the same message identifier.
Optionally, a client middleware is provided in the terminal device, and the method further includes:
the terminal equipment and the server side equipment initiate communication through the client middleware.
In another aspect of the embodiments of the present application, a distributed data transmission apparatus is provided, where the apparatus is applied to a distributed system, the distributed system includes a plurality of terminal devices and a plurality of server devices, and each server device is in communication connection with each terminal device, and the apparatus includes: the device comprises a generating module, a transmission module, a determining module and a returning module;
a generating module, configured to generate, by a first terminal device, a transmission message and attribute information of the transmission message, where the transmission message includes a message body and a message identifier, and the attribute information of the transmission message includes: message queue transmission type and target server equipment information;
the transmission module is used for transmitting the transmission message to the target server equipment by the first terminal equipment by adopting a message queue transmission type;
the determining module is used for determining second terminal equipment through the target server side equipment according to a preset subscription relation and the message identification, the subscription relation is used for indicating the mapping relation between each message queue transmission type and the terminal equipment, and each terminal equipment is respectively subscribed with one message queue transmission type;
and the return module is used for sending the transmission message to the second terminal equipment by the target server-side equipment in a message queue transmission type mode.
Optionally, the determining module is further configured to determine, by the second terminal device, service progress information, where the service progress information includes: identification of the business process, and a message queue type used by the release business process; the second terminal equipment sends the business process information to the target server equipment corresponding to the business process identifier; and establishing a subscription relation by the target server-side equipment based on the business process information.
Optionally, the determining module is specifically configured to determine a subscription type, where the subscription type includes: a generic subscription type and a targeted subscription type; if the subscription type is a generic subscription type, determining type set information of a message queue used by a publishing service process, and determining service process information based on the type set information; and if the subscription type is the oriented subscription type, determining the type information of the message queue used by the issuing business process, and determining the business process information based on the type information.
Optionally, the determining module is further configured to determine whether a buffer queue of the second terminal device contains the transmission message; if not, the second terminal device recalls the transmission message, and stores the transmission message and the attribute information of the transmission message.
Optionally, the determining module is further configured to store, by the second terminal device, the transmission message and the attribute information of the transmission message if it is determined that the buffer queue of the second terminal device includes the transmission message.
Optionally, the determining module is further configured to determine whether all transmission messages in the buffer queue of the second terminal device are received by the corresponding second terminal device; and if so, deleting the transmission message with the same message identifier.
Optionally, a client middleware is provided in the terminal device, and in the apparatus, the terminal device and the server device initiate communication through the client middleware.
In another aspect of the embodiments of the present application, a distributed system is provided, including: the device comprises a memory and a processor, wherein a computer program capable of running on the processor is stored in the memory, and when the processor executes the computer program, the steps of the distributed data transmission method are realized.
In another aspect of the embodiments of the present application, a computer-readable storage medium is provided, on which a computer program is stored, and the computer program, when executed by a processor, implements the steps of the method for transmitting distributed data.
The beneficial effects of the embodiment of the application include:
in the method, the device, the system and the storage medium for transmitting distributed data provided by the embodiment of the application, a transmission message and attribute information of the transmission message are generated through a first terminal device, and the transmission message comprises a message body and a message identifier; the first terminal equipment adopts the message queue transmission type to send the transmission message to the target server-side equipment; determining a second terminal device through the target server device according to a preset subscription relationship and a message identifier; and the target server-side equipment sends the transmission message to the second terminal equipment in a message queue transmission type mode. The subscription relationship is used for indicating the mapping relationship between each message queue transmission type and the terminal equipment, each terminal equipment subscribes one message queue transmission type respectively, and in the process of specifically realizing data transmission, corresponding data transmission can be carried out according to the mapping relationship between the transmission type determined in the subscription relationship and the terminal equipment, so that transmission in all realizable message queue transmission modes is avoided, repeated sending of data can be avoided, further, the message complexity of the whole system can be reduced, and the delay of message transmission is reduced.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.
Fig. 1 is a schematic structural diagram of a distributed system provided in an embodiment of the present application;
fig. 2 is a schematic diagram of data transmission of a distributed system in the prior art according to an embodiment of the present application;
fig. 3 is another schematic diagram of data transmission of a distributed system in the prior art according to an embodiment of the present application;
fig. 4 is a schematic flowchart of a distributed data transmission method according to an embodiment of the present application;
fig. 5 is another schematic flow chart of a distributed data transmission method according to an embodiment of the present application;
fig. 6 is another schematic flow chart of a distributed data transmission method according to an embodiment of the present application;
fig. 7 is a schematic diagram of data transmission of a distributed system according to an embodiment of the present application;
fig. 8 is another schematic diagram of data transmission of a distributed system according to an embodiment of the present application;
fig. 9 is a schematic workflow diagram of a middleware of a middle client in a distributed system according to an embodiment of the present application;
fig. 10 is a schematic flowchart of a distributed data transmission method according to an embodiment of the present application;
fig. 11 is a schematic flowchart of a distributed data transmission method according to an embodiment of the present application;
fig. 12 is a schematic structural diagram of a distributed data transmission apparatus according to an embodiment of the present application;
fig. 13 is a schematic structural diagram of a distributed system device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
In the description of the present application, it is noted that the terms "first", "second", "third", and the like are used merely for distinguishing between descriptions and are not intended to indicate or imply relative importance.
The following specifically explains a specific structural relationship of the distributed system provided in the embodiment of the present application.
Fig. 1 is a schematic structural diagram of a distributed system according to an embodiment of the present application, and please refer to fig. 1, where the distributed system includes a plurality of terminal devices 110 and a plurality of server devices 120, and each server device 120 is respectively in communication connection with each terminal device 110 (a communication connection relationship is not shown in the figure).
Optionally, the system may include multiple devices, where the terminal device 110 may be any type of electronic device such as a computer, a mobile phone, a tablet computer, or a dedicated electronic device, and a client may be disposed in the device, and information interaction with other devices in the system may be achieved through the client. The server device 120 may be a server, or a plurality of server clusters, or may be a sub-area under any server, and is not limited in this respect.
In the system, a plurality of terminal devices 110 and a plurality of server devices 120 may be included, any terminal device 110 may be communicatively connected to each server device 120, and accordingly, any server device 120 may also be communicatively connected to each terminal device 110.
The terminal device 110 may include: the client-side middleware can be arranged between the client side and the service module and used for performing work such as message forwarding, callback and processing.
The system can comprise the following three stages in the working process:
a subscription stage: the terminal device 110 initiates a subscription to the server device 120, and after the subscription, the server device 120 may send a corresponding subscription message to the terminal device 110.
A sending stage: a process of generating a transfer message by the first terminal device (any one of the terminal devices 110) and transmitting the transfer message to any one of the server devices 120.
A receiving stage: and receiving the message sent by the server device 120 with the subscription relationship by the second terminal device (any one of the terminal devices 110).
It should be noted that the system structure in fig. 1 is only an example, and any number of terminal devices and server devices may be set in an actual process, and any number of client types may also be set for each terminal device.
The above three phases are explained separately based on the working process of the distributed system in the prior art.
Fig. 2 is a schematic diagram of data transmission of a distributed system in the prior art according to an embodiment of the present application, please refer to fig. 2, where the process shown in fig. 2 is a process in a subscription stage in the prior art.
Wherein, this system includes: the system comprises a terminal device A, a terminal device B, a terminal device C, a server device a and a server device B.
It should be noted that the terminal device B and the terminal device C may include two types of clients, that is, when data is transmitted, the data may be transmitted in two different forms of message queues.
Taking the execution of a certain business process as an example, for example: the terminal device a is configured to initiate an alarm, the terminal device B is configured to perform alarm calculation, and the terminal device C is configured to perform alarm storage, where the terminal device B and the terminal device C both need to subscribe to corresponding server devices through two clients, and exemplarily, the terminal device B and the terminal device C both include a client 1 and a client 2, where a data transmission type of the client 1 is supported by the server a, and a data transmission type of the client 2 is supported by the server B.
In the process, the terminal device a may be an embedded device, the terminal device B may be an electronic device dedicated to alarm calculation, and the terminal device C may be a computer device implementing alarm storage. The server-side device a can be an MQTT server. And the server-side device b can be a RabbitMQ server.
Referring to fig. 2, in the subscription process of the prior art, a terminal device B and a terminal device C subscribe to a server device a through a client 1, and the terminal device B and the terminal device C subscribe to a server device B through a client 2.
The working principle of the prior art in the sending and receiving phases is explained below in connection with the relation of the subscription phase shown in fig. 2.
Fig. 3 is another schematic diagram of data transmission in a distributed system in the prior art according to an embodiment of the present application, and please refer to fig. 3, the layout of the system is the same as that in fig. 2, and an explanation thereof is not repeated.
In the sending stage and the receiving stage, the terminal device A can send original data to the server device a, the server device a transmits the original data to the client 1 of the terminal device B based on the subscription relationship, the terminal device B can perform alarm calculation to obtain alarm data based on the original data, the alarm data can be sent to the server device a through the client 1 and sent to the server device B through the client 2 because the terminal device B is uncertain of what way to send the alarm data, the server device a transmits the alarm data to the client 1 of the terminal device C based on the subscription relationship, and the server device B transmits the alarm data to the client 2 of the terminal device C based on the subscription relationship.
As is obvious from fig. 2 and fig. 3, in the prior art, when there is a repeated sending situation of the alarm data, the server device a and the server device b respectively transmit the alarm data, and in an actual implementation process, the alarm data is only received through the format of the client 2, that is, the client 1 in the terminal device C performs repeated data transmission, so that the delay of message transmission is increased, and the message complexity of the entire system is increased.
In order to solve the problem of repeated transmission of message queues as shown in fig. 2 and fig. 3 in the prior art, a method for transmitting distributed data is provided in the embodiment of the present application, and a specific implementation process of the method for transmitting distributed data in the embodiment of the present application is specifically explained below.
Fig. 4 is a schematic flowchart of a method for transmitting distributed data according to an embodiment of the present application, please refer to fig. 4, where the method includes:
s410: a transmission message and attribute information of the transmission message are generated by a first terminal device.
The transmission message comprises a message body and a message identifier, and the attribute information of the transmission message comprises: message queue transmission type and target server device information.
Alternatively, the execution subject of the method may be the aforementioned distributed system in which the transmission message and the attribute information of the transmission message may be generated by the first terminal device.
The first terminal device may be any one of the terminal devices, and is used as a message sender in the sending phase in the three phases.
Optionally, the message body specifically refers to data of the message itself, and the message identifier may be an identifier used to characterize the message, for example: message names, etc., without limitation herein.
The message queue transmission type may be a specific transmission type of the transmission message when the transmission message is transmitted between the terminal device and the server device, that is, a client type and a server device type that may be used, for example: the message queue transmission types may include: MQTT (Message Queuing Transport protocol) and RabbitMQ (rabbitmessage Queue protocol).
The target server device information may be an identifier of any one of the plurality of server devices, and is used to indicate to which specific server device the transmission message needs to be sent. The specific information may include the type, address, user name, password, etc. of the target server device.
It should be explained that the type of the server device may be specifically obtained based on the message queue transmission type, and in the same distributed system, a plurality of server devices of the same type may be generally included, and which one of the plurality of server devices of the same type is used may be specifically determined based on the target server device information.
Optionally, the transmission message may be a message that needs to be sent to the server device for storage in any task flow, and is not limited specifically here, for example, in the foregoing embodiments of fig. 2 and fig. 3, both the original data and the alarm data may be used as the transmission message.
S420: and the first terminal equipment adopts the message queue transmission type to send the transmission message to the target server-side equipment.
Optionally, after determining the attribute information of the transmission message, the client that needs to be used for transmission may be determined based on the message queue transmission type, the target server device corresponding to the transmission message may be determined based on the target server device information, and the transmission message may be transmitted to the target server device by the client using the message queue transmission type.
For example: the client can be an MQTT client specifically, and the server equipment can be an MQTT server specifically; or, the client may specifically be a RabbitMQ client, and the server device may specifically be a RabbitMQ server.
S430: and determining the second terminal equipment through the target server-side equipment according to the pre-configured subscription relationship and the message identifier.
The subscription relationship is used for indicating the mapping relationship between each message queue transmission type and the terminal equipment, and each terminal equipment subscribes one message queue transmission type respectively.
Optionally, after the first terminal device sends the transmission message to the target server device, the target server device may determine the second terminal device according to the preconfigured subscription relationship and the message identifier.
In the subscription stage, after the target server device receives the subscription message, the subscription relationship may be stored, and the subscription relationship may be used to indicate a mapping relationship between each message queue transmission type and the terminal device, for example: for the MQTT-type message, the target to be sent may be the second terminal device, and then the mapping relationship between the MQTT-type message and the second terminal device may be determined, and further, after the target server device receives the MQTT-type message, it may be determined that the MQTT-type message needs to be sent to the second terminal device.
The subscription relationship may specifically record a corresponding message in a message identifier manner, for example: the message identifier, the message queue transmission type and the terminal device to be sent can be recorded, after the target client receives the transmission message, the corresponding record can be determined based on the message identifier in the transmission message, and then the terminal device to be sent is determined based on the message queue transmission type.
S440: and the target server-side equipment sends the transmission message to the second terminal equipment in a message queue transmission type mode.
Optionally, after the target server device determines the second terminal device, the transmission message may be sent to the second terminal device in a corresponding message queue transmission type, specifically, the transmission message may be transmitted by a client corresponding to the second terminal device.
For example: if the target server-side device is an MQTT server, the message queue transmission type is an MQTT type, and the transmission message can be sent to an MQTT client of the second terminal device.
In the method for transmitting distributed data provided by the embodiment of the application, a transmission message and attribute information of the transmission message are generated through a first terminal device, and the transmission message comprises a message body and a message identifier; the first terminal equipment adopts the message queue transmission type to send the transmission message to the target server-side equipment; determining a second terminal device through the target server device according to a preset subscription relationship and a message identifier; and the target server-side equipment sends the transmission message to the second terminal equipment in a message queue transmission type mode. The subscription relationship is used for indicating the mapping relationship between each message queue transmission type and the terminal equipment, each terminal equipment subscribes one message queue transmission type, and in the process of realizing data transmission specifically, corresponding data transmission can be carried out according to the mapping relationship between the transmission type determined in the subscription relationship and the terminal equipment, so that transmission in all the achievable message queue transmission modes is avoided, repeated sending of data can be avoided, the message complexity of the whole system can be reduced, and the message transmission delay is reduced.
The following specifically explains a specific implementation process of the subscription stage in the distributed data transmission method provided in the embodiment of the present application.
Fig. 5 is another schematic flow chart of a distributed data transmission method according to an embodiment of the present application, please refer to fig. 5, where before determining, by a target server device, a second terminal device according to a preconfigured subscription relationship and a message identifier, the method further includes:
s510: and determining the service process information through the second terminal equipment.
The business process information comprises: identification of the business process, and the type of message queue used by the publishing business process.
Optionally, the second terminal device may determine an actually executed service process, specifically, determine service process information, and the service process may specifically be any type of service process, for example: the alarm service shown in the foregoing is not limited to this, and when different services are executed, different service process information may be provided, and the transmission message may be message data that needs to be transmitted in a service process.
In the service process information, the identifier of the service process may be used to indicate a corresponding service phase, for example: in the aforementioned alarm calculation stage or the alarm storage stage, a target server device corresponding to the second terminal device may be corresponded in the stage, and the target server device sent to the second terminal device in the later receiving stage may be determined based on the identifier of the service process, and the message queue type used for issuing the service process may be a message queue transmission type used when other terminal devices (such as the first terminal device) transmit to the server device in the later sending stage.
S520: and the second terminal equipment sends the business process information to the target server equipment corresponding to the business process identifier.
Optionally, after obtaining the identifier of the service process, the second terminal device may send service process information to the target server device corresponding to the identifier of the service process, where the process is also a subscription process, and the service process information is also a subscription message.
S530: and establishing a subscription relation by the target server side equipment based on the business process information.
Optionally, after the target server device receives the service process information, a subscription relationship may be established based on the type of the message queue used by the published service process in the service process information and the source (that is, the second terminal device).
It should be noted that the service process information may further include a message identifier of the transmission message, a subscription relationship may be established based on the message identifier of the transmission message, the message queue type, and the second terminal device, and in a subsequent sending stage, the target server device may send the transmission message to the second terminal device based on the subscription relationship.
The following explains a specific implementation process for determining service process information in the distributed data transmission method provided in the embodiment of the present application.
Fig. 6 is another schematic flow chart of a distributed data transmission method according to an embodiment of the present application, please refer to fig. 6, where determining service process information by a second terminal device includes:
s610: a subscription type is determined.
Wherein the subscription type includes: a generic subscription type and a targeted subscription type.
Optionally, the subscription type specifically refers to a subscription type when the second terminal device subscribes to the server device, and the generic subscription type specifically may be a subscription that specifies a message type but does not specify a specific terminal device that generates a message. The targeted subscription type may be a subscription that specifies both the type of message and the specific end device that originated the message.
It should be noted that the subscription type can be determined based on actual requirements or active settings of the user.
If the subscription type is a generic subscription type, S620: determining type set information of a message queue used by the issuing business process, and determining business process information based on the type set information.
Optionally, if the subscription type is a generic subscription type, the type set information of the message queue used by the publishing service process may be determined, a minimum set of MQ types used by all the service processes generating the message topic of the subscription message to publish the message is found by traversing from the type set information, and after the minimum set is determined, the subscription may be performed by using the minimum set of MQ types, that is, the service process information is determined.
If the subscription type is the directed subscription type, S630: the type information of the message queue used by the issuing business process and the business process information are determined.
It should be noted that the business process information may specifically include a unique identifier of the target business process.
Optionally, if the subscription type is a directed subscription type, the MQ type used by the target business process to publish the message may be directly found, and then the subscription is performed based on the MQ type, that is, the directed subscription type generally uses only one MQ type, and does not need to repeatedly receive the message.
It should be noted that the explanation of the transmission method of the distributed data is only an example, and in the actual implementation process, the method may be used in combination with the methods in fig. 2 to fig. 3, for example, whether to optimize the transmission method may be selected, and if so, the transmission is performed by using the processes of S410 to S440; if the selection is no, the message transmission can be continued in the manner shown in fig. 2 to fig. 3. And are not intended to be limiting in the manner employed in the examples of this application.
Optionally, after the target server device sends the transmission message to the second terminal device in a message queue transmission type, the method further includes: determining whether a buffer queue of the second terminal device contains a transmission message; if not, the second terminal device recalls the transmission message, and stores the transmission message and the attribute information of the transmission message.
The second terminal device may include a cache queue, where the cache queue may be a cache queue of a service module, and after the target server sends the transmission message to the second terminal device, the transmission message may be cached in the cache queue, and in order to avoid missed sending and missed sending, whether the transmission message is included in the cache queue may be checked after the sending is completed, if yes, it may be determined that the call-back has been performed, and if no, it may be determined that the call-back has not been performed, and the transmission message may be called back by the second terminal device.
It should be noted that the callback process may specifically be a process of temporarily storing the transmission message received by the second terminal device to a cache queue of the service module.
After the callback is completed, the cache queue of the service module includes the transmission message, and the transmission message and the attribute information of the transmission message may be stored by the second terminal device, where the transmission message and the attribute information of the transmission message may be specifically stored in the storage queue during storage, the storage queue and the cache queue are two different queues in the second terminal device, and the storage queue may be used to record a message that has been sent by the target server device, so that persistent storage of the message may be implemented.
Optionally, after determining whether the buffer queue of the second terminal device contains the transmission message, the method further includes: and if the buffer queue of the second terminal equipment contains the transmission message, the second terminal equipment stores the transmission message and the attribute information of the transmission message.
If it is determined that the buffer queue of the second terminal device contains the transmission message, it may be determined that the target server device successfully sends the transmission message, and the second terminal device may store the transmission message and the attribute information of the transmission message in the storage queue.
Optionally, after the second terminal device stores the transmission message and the attribute information of the transmission message, the method further includes: judging whether all transmission messages in a buffer queue of the second terminal equipment are received by the second terminal equipment; and if so, deleting the transmission message with the same message identifier.
The second terminal device may determine whether all transmission messages in its buffer queue have been received, specifically, may determine whether all transmission messages are in the buffer queue, and if so, may clear the buffer queue, specifically, may delete the transmission messages with the same message identifier, thereby reducing the buffer pressure.
Optionally, a client middleware is provided in the terminal device, and the method further includes: the terminal equipment and the server side equipment initiate communication through the client middleware.
The client middleware may be specifically set in the terminal device in the form of a software program, and based on the client middleware, the connection between the terminal device itself and the client included therein may be established, so that the connection between the terminal device and the server device may be realized through the client middleware.
The following explains a specific implementation process of the present application based on a data transmission relationship of a distributed system provided in the embodiment of the present application.
Fig. 7 is a schematic diagram of data transmission of a distributed system according to an embodiment of the present application, please refer to fig. 7, which can compare fig. 7 with fig. 2, and fig. 7 is a process of a subscription phase according to an embodiment of the present application.
Wherein, this system includes: the system comprises a terminal device A, a terminal device B, a terminal device C, a server device a and a server device B. The devices are the same as those in fig. 2, and are not described herein again.
Continuing with the aforementioned alarm service as an example, during subscription, since the terminal device B needs to receive the original data in the format under the client 1, the server device a can be subscribed only through the client 1; accordingly, since the terminal device C needs to receive the alert data in the format under the client 2, the server device b can be subscribed only through the client 2.
The working principle of the embodiment of the present application in the sending and receiving phases is explained below in conjunction with the relationship of the subscription phase shown in fig. 7.
Fig. 8 is another schematic diagram of data transmission of a distributed system according to an embodiment of the present application, please refer to fig. 8, and please refer to fig. 3, where the layout of the system is the same as that of fig. 7, and no repeated explanation is provided here.
In the sending stage and the receiving stage, the terminal device a can send original data to the server device a, the server device a transmits the original data to the client 1 of the terminal device B based on the subscription relationship, the terminal device B can perform alarm calculation to obtain alarm data based on the original data, the terminal device B can send the alarm data to the server device B through the client 2, and the server device B transmits the alarm data to the client 2 of the terminal device C based on the subscription relationship.
Based on the difference between fig. 8 and fig. 3, it can be seen that the processes of subscribing, sending, and receiving adopted in the embodiment of the present application can avoid repeated sending of messages, and reduce the working pressure and complexity of the entire system.
The following specifically explains a specific workflow of the client middleware provided in the embodiment of the present application.
Fig. 9 is a schematic view of a workflow of a client middleware in a distributed system according to an embodiment of the present application, please refer to fig. 9, where an execution main body of the method may be a second terminal device, and the client middleware may be set in the second terminal device, and the method includes:
s901: business process information is determined.
Optionally, the service process information may be obtained by loading after user configuration, and is not particularly limited herein.
S902: and judging whether to start data transmission optimization. If on, S903 is executed, and if not on, S904 is executed.
Optionally, the control may be performed specifically by a management module arranged in the system, where the management module may be a module that performs interface configuration on the terminal device, and specifically may be a control device, and whether to start data transmission optimization may be determined by an interface of the management module, a global configuration, a registry, and the like, or whether to manually set whether to start optimization, if the optimization is started, the foregoing steps S410 to S440 are executed, and if the optimization is not started, the processes shown in fig. 2 to fig. 3 are continuously executed.
S903: and sending the identification of the business process and the transmission type of the message queue for releasing to a management module.
For the subscription messages which need to be sent to a plurality of server-side devices, message themes or message identifications can be generated and labeled.
S904: the client to use is determined.
The type of the client can be provided in a dynamic library manner, or can be directly compiled into a business process as a static library, and the type of the client can be determined based on the actual use requirement of a user.
S905: the full amount of data is obtained from the management module.
The total data may refer to all relevant information of the server device, all business process information, and the like, and specifically may be data obtained by summarizing, by the management module, the identifications of the business processes sent by all the terminal devices and the transmission types of the message queues for distribution.
S906: and subscribing the message based on the full data.
Optionally, after obtaining the above-mentioned total data, the terminal device may subscribe correspondingly based on the actually executed service process, that is, execute the specific implementation steps of S510-S530.
The following explains the specific implementation steps of the sending phase and the receiving phase implemented based on the above-mentioned client middleware.
Fig. 10 is a schematic flowchart of another flow of a distributed data transmission method according to an embodiment of the present application, please refer to fig. 10, where a specific method of a client middleware in sending a message includes:
s1001: a transfer message is generated.
S1002: and judging whether to start data transmission optimization.
If on, S1003 is executed, otherwise S1004 is executed.
S1003: and determining a target server according to the message queue transmission type used for releasing the message and the corresponding server side equipment information.
S1004: and acquiring all message queue transmission types and corresponding server side equipment information, and determining all related server side equipment as target server side equipment.
S1005: and sending the transmission message to the target server-side equipment.
The specific implementation process of the above steps has been specifically explained in the foregoing, and is not repeated herein.
Fig. 11 is a schematic flowchart of another flow of a distributed data transmission method according to an embodiment of the present application, please refer to fig. 11, where a specific method for a client middleware to receive a message includes:
s1101: and receiving the transmission message from the target server-side equipment.
S1102: and determining the message body and the message identification in the transmission message.
S1103: and judging whether to start data transmission optimization.
If on, S1104 is performed, otherwise S1105 is performed.
S1104: and returning the transmission message to the service module for application.
S1105: it is determined whether the transfer message has been recalled.
The specific method is to search whether a record containing the identification of the transmission message exists in the buffer queue.
If so, S1107 is executed, otherwise, S1106 is executed.
S1106: and the transmission message is returned to the service module for application.
S1107: the transfer message is added to the store queue.
S1108: and if all the subscribed transmission messages are received by the corresponding second client equipment, deleting the transmission messages with the same message identification from the cache queue.
Optionally, the service module may be a specific part used for executing the service in the terminal device, for example: for the alarm calculation, the alarm calculation may be performed by a service module of the alarm calculation.
The callback may specifically be a process of sending a transmission message to the service module for execution after the terminal device receives the corresponding transmission message.
The specific implementation process of the above steps has been specifically explained in the foregoing, and details are not repeated herein.
It should be noted that the steps of S1001-S1005 and S1101-S1108 may be implemented by a client middleware, where the step that needs to be completed by the server device may be implemented by sending a preset monitor process to the client middleware after being acquired by the server device, for example, the process of S1105-S1108 may be implemented by sending the monitor process to the client middleware after being executed by the server device.
Optionally, in order to enable the subscriber to arbitrarily select the generic subscription or the targeted subscription without the publisher needing to care about the difference between the two subscriptions, when the service module publishes the message, the MQ client middleware needs to change the message topic transmitted by the service module, so as to facilitate the generic configuration of the subscriber in the generic subscription. Since the wildcard rules for each type of MQ are different, the MQ client middleware needs to implement different adaptation policies for different types of MQs.
Take MQTT and RabbitMQ as examples:
m Q type Change rules
M QTT New topic = original topicBusiness process identification (wherein/is the subject separator of M QTT)
RabbitMQ New subject = original subject.Business process identifier (wherein. Is subject separator of RabbitMQ)
When a subscriber subscribes, the MQ client middleware also changes the message theme transmitted by the service module, the generic subscription is different from the directed subscription, a wildcard character is added during the generic subscription, and the identifier of the target service process is indicated during the directed subscription, so that the purposes of the generic subscription and the directed subscription are achieved.
Take MQTT and RabbitMQ as examples:
m Q type Type of subscription Change rules
M QTT Generic subscriptions New theme = original theme/+ (where/is the theme separator of M QTT, + is the single-layer wildcard of M QTT)
M QTT Targeted subscriptions New theme = original theme/target business process identification (where/is theme separator of M QTT)
RabbitMQ Generic subscriptions New topic = original topic (where is topic separator of RabbitMQ, single-level wildcard of RabbitMQ)
RabbitMQ Targeted subscriptions New subject = original subject.target business process identification (where.is subject separator of RabbitMQ)
It should be noted that besides the MQ types in the above example, it may also include: the types Kafka, kestrel, rocktmq, XMPP, etc., are not particularly limited herein and may be selected based on actual needs.
The following describes a device, equipment, and a storage medium corresponding to the distributed data transmission method provided by the present application, and specific implementation procedures and technical effects thereof are referred to above, and are not described again below.
Fig. 12 is a schematic structural diagram of a distributed data transmission apparatus according to an embodiment of the present application, please refer to fig. 12, where the apparatus includes: a generation module 210, a transmission module 220, a determination module 230, and a return module 240;
a generating module 210, configured to generate, by a first terminal device, a transmission message and attribute information of the transmission message, where the transmission message includes a message body and a message identifier, and the attribute information of the transmission message includes: message queue transmission type and target server equipment information;
a transmission module 220, configured to send a transmission message to a target server device by using a message queue transmission type through a first terminal device;
a determining module 230, configured to determine, by the target server device, a second terminal device according to a preconfigured subscription relationship and the message identifier, where the subscription relationship is used to indicate a mapping relationship between each message queue transmission type and the terminal device, and each terminal device subscribes to one message queue transmission type;
a returning module 240, configured to send the transmission message to the second terminal device by the target server device in a message queue transmission type.
Optionally, the determining module 230 is further configured to determine, by the second terminal device, service progress information, where the service progress information includes: identification of the business process, and a message queue type used by the release business process; the second terminal equipment sends the business process information to the target server equipment corresponding to the business process identifier; and establishing a subscription relation by the target server side equipment based on the business process information.
Optionally, the determining module 230 is specifically configured to determine a subscription type, where the subscription type includes: a generic subscription type and a targeted subscription type; if the subscription type is a generic subscription type, determining type set information of a message queue used by a publishing service process, and determining service process information based on the type set information; and if the subscription type is the oriented subscription type, determining the type information of the message queue used by the issuing business process, and determining the business process information based on the type information.
Optionally, the determining module 230 is further configured to determine whether a buffer queue of the second terminal device contains a transmission message; if not, the second terminal device recalls the transmission message, and stores the transmission message and the attribute information of the transmission message.
Optionally, the determining module 230 is further configured to store, by the second terminal device, the transmission message and the attribute information of the transmission message if it is determined that the buffer queue of the second terminal device contains the transmission message.
Optionally, the determining module 230 is further configured to determine whether all transmission messages in the buffer queue of the second terminal device are received by the second terminal device; and if so, deleting the transmission message with the same message identifier.
Optionally, a client middleware is provided in the terminal device, and in the apparatus, the terminal device and the server device initiate communication through the client middleware.
The above-mentioned apparatus is used for executing the method provided by the foregoing embodiment, and the implementation principle and technical effect are similar, which are not described herein again.
These above modules may be one or more integrated circuits configured to implement the above methods, such as: one or more Application Specific Integrated Circuits (ASICs), or one or more microprocessors, or one or more Field Programmable Gate Arrays (FPGAs), etc. For another example, when one of the above modules is implemented in the form of a Processing element scheduler code, the Processing element may be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of calling program code. As another example, these modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).
Fig. 13 is a schematic structural diagram of a distributed system device according to an embodiment of the present application, please refer to fig. 13, in which the distributed system includes: the memory 310 and the processor 320, wherein the memory 310 stores a computer program operable on the processor 320, and the processor 320 executes the computer program to implement the steps of the distributed data transmission method.
Optionally, the structure of the distributed system may specifically refer to the structure of any device in the system, for example: the structure of a terminal device or a server device.
In performing the above-described method, the memory 310 and processor 320 based on the corresponding device may work together when the corresponding device performs the corresponding steps.
In another aspect of the embodiments of the present application, there is also provided a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the method for transmitting distributed data are implemented.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of a unit is merely a logical division, and an actual implementation may have another division, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
Units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.
The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device) or a processor (processor) to execute some steps of the methods according to the embodiments of the present invention. And the aforementioned storage medium includes: a U disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
The above description is only a preferred embodiment of the present application and is not intended to limit the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims (10)

1. A method for transmitting distributed data is characterized in that the method is applied to a distributed system, the distributed system comprises a plurality of terminal devices and a plurality of server devices, and each server device is respectively in communication connection with each terminal device, and the method comprises the following steps:
generating a transmission message and attribute information of the transmission message through a first terminal device, wherein the transmission message comprises a message body and a message identifier, and the attribute information of the transmission message comprises: message queue transmission type and target server equipment information;
determining target server equipment based on the target server equipment information;
the first terminal equipment adopts the message queue transmission type to send the transmission message to the target server-side equipment;
determining a second terminal device through the target server device according to a preset subscription relationship and the message identifier, wherein the subscription relationship records a message identifier, a message queue transmission type and a terminal device to be sent, after receiving a transmission message, determining a corresponding record based on the message identifier in the transmission message, and further determining the terminal device to be sent as the second terminal device based on the message queue transmission type, wherein each terminal device subscribes to one message queue transmission type;
and the target server-side equipment sends the transmission message to the second terminal equipment in a mode of the message queue transmission type.
2. The method of claim 1, wherein before the second terminal device is determined by the target server device according to the preconfigured subscription relationship and the message identifier, the method further comprises:
determining, by the second terminal device, service process information, where the service process information includes: identification of a business process, and a message queue transmission type used for issuing the business process;
the second terminal equipment sends the business process information to target server equipment corresponding to the business process identifier;
and establishing the subscription relation by the target server side equipment based on the business process information.
3. The method of claim 2, wherein said determining, by said second terminal device, traffic progress information comprises:
determining a subscription type, the subscription type comprising: a generic subscription type and a targeted subscription type;
if the subscription type is a generic subscription type, determining type set information of a message queue used for publishing the business process, and determining business process information based on the type set information;
and if the subscription type is a directional subscription type, determining the type information of a message queue used by the business process, and determining the business process information based on the type information.
4. The method of claim 1, wherein after the transmitting, by the target server device, the transmission message to the second terminal device in the message queue transmission type, the method further comprises:
determining whether the buffer queue of the second terminal device contains the transmission message;
if not, the second terminal device recalls the transmission message, and stores the transmission message and the attribute information of the transmission message.
5. The method of claim 4, wherein after determining whether the transmission message is contained in the buffer queue of the second terminal device, the method further comprises:
and if the buffer queue of the second terminal equipment contains the transmission message, the second terminal equipment stores the transmission message and the attribute information of the transmission message.
6. The method of claim 5, wherein after storing, by the second terminal device, the transfer message and the attribute information of the transfer message, the method further comprises:
judging whether all transmission messages in the buffer queue of the second terminal equipment are received by the second terminal equipment;
and if so, deleting the transmission message with the same message identifier.
7. The method of any one of claims 1-6, wherein client middleware is provided in the terminal device, the method further comprising:
and the terminal equipment and the server side equipment initiate communication through the client side middleware.
8. The utility model provides a transmission device of distributed data, its characterized in that, the device is applied to distributed system, including a plurality of terminal equipment and a plurality of server-side equipment in the distributed system, each server-side equipment respectively with each terminal equipment communication connection, the device includes: the device comprises a generating module, a transmission module, a determining module and a returning module;
the generating module is configured to generate a transmission message and attribute information of the transmission message through a first terminal device, where the transmission message includes a message body and a message identifier, and the attribute information of the transmission message includes: message queue transmission type and target server equipment information;
the generating module is further used for determining target server equipment based on the target server equipment information;
the transmission module is configured to send the transmission message to the target server device by using the message queue transmission type through the first terminal device;
the determining module is configured to determine, by the target server device, a second terminal device according to a preconfigured subscription relationship and the message identifier, where the subscription relationship records a message identifier, a message queue transmission type, and a terminal device to be sent, and after receiving a transmission message, determine a corresponding record based on the message identifier in the transmission message, and then determine, based on the message queue transmission type, that the terminal device to be sent serves as the second terminal device, and each terminal device subscribes to one message queue transmission type;
the return module is configured to send, by the target server device, the transmission message to the second terminal device in the message queue transmission type.
9. A distributed system, comprising: memory in which a computer program is stored which is executable on the processor, a processor which, when executing the computer program, carries out the steps of the method according to any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that the storage medium has stored thereon a computer program which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.
CN202210859992.8A 2022-07-22 2022-07-22 Distributed data transmission method, device, system and storage medium Active CN114938388B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210859992.8A CN114938388B (en) 2022-07-22 2022-07-22 Distributed data transmission method, device, system and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210859992.8A CN114938388B (en) 2022-07-22 2022-07-22 Distributed data transmission method, device, system and storage medium

Publications (2)

Publication Number Publication Date
CN114938388A CN114938388A (en) 2022-08-23
CN114938388B true CN114938388B (en) 2022-11-11

Family

ID=82868443

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210859992.8A Active CN114938388B (en) 2022-07-22 2022-07-22 Distributed data transmission method, device, system and storage medium

Country Status (1)

Country Link
CN (1) CN114938388B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116668493B (en) * 2023-07-25 2023-10-24 森智明信息科技南京有限公司 Message processing system of mqtt Internet of things equipment under distributed scene

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106230896A (en) * 2016-07-18 2016-12-14 深圳国泰安教育技术股份有限公司 A kind of information push method, Apparatus and system
CN108228625A (en) * 2016-12-15 2018-06-29 腾讯科技（深圳）有限公司 A kind of PUSH message processing method and processing device
CN109274730A (en) * 2018-09-04 2019-01-25 上海联寓智能科技有限公司 The optimization method and device that Internet of things system, MQTT message are transmitted
CN110401592A (en) * 2019-07-30 2019-11-01 三体云智能科技有限公司 The method and apparatus of stream compression in a kind of message channel
US10579449B1 (en) * 2018-11-02 2020-03-03 Dell Products, L.P. Message queue architectures framework converter
CN111212135A (en) * 2019-12-31 2020-05-29 北京金山云网络技术有限公司 Message subscription method, device, system, electronic equipment and storage medium
CN113596150A (en) * 2021-07-28 2021-11-02 南方电网数字电网研究院有限公司 Message pushing method and device, computer equipment and storage medium
CN114025002A (en) * 2021-11-05 2022-02-08 深圳市宏电技术股份有限公司 MQTT information transmission method, system and communication equipment
CN114051041A (en) * 2021-11-10 2022-02-15 深圳市赛格导航科技股份有限公司 Intelligent agricultural machinery system and communication method based on RabbitMQ and MQTT

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106230896A (en) * 2016-07-18 2016-12-14 深圳国泰安教育技术股份有限公司 A kind of information push method, Apparatus and system
CN108228625A (en) * 2016-12-15 2018-06-29 腾讯科技（深圳）有限公司 A kind of PUSH message processing method and processing device
CN109274730A (en) * 2018-09-04 2019-01-25 上海联寓智能科技有限公司 The optimization method and device that Internet of things system, MQTT message are transmitted
US10579449B1 (en) * 2018-11-02 2020-03-03 Dell Products, L.P. Message queue architectures framework converter
CN110401592A (en) * 2019-07-30 2019-11-01 三体云智能科技有限公司 The method and apparatus of stream compression in a kind of message channel
CN111212135A (en) * 2019-12-31 2020-05-29 北京金山云网络技术有限公司 Message subscription method, device, system, electronic equipment and storage medium
CN113596150A (en) * 2021-07-28 2021-11-02 南方电网数字电网研究院有限公司 Message pushing method and device, computer equipment and storage medium
CN114025002A (en) * 2021-11-05 2022-02-08 深圳市宏电技术股份有限公司 MQTT information transmission method, system and communication equipment
CN114051041A (en) * 2021-11-10 2022-02-15 深圳市赛格导航科技股份有限公司 Intelligent agricultural machinery system and communication method based on RabbitMQ and MQTT

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
发布订阅系统中高效消息投递机制的研究;刘耀等;《网络新媒体技术》;20150115(第01期);全文 *
基于ActiveMQ通信的多租户任务调度框架设计与实现;苏志宏;《电脑知识与技术》;20200630;第16卷(第18期);全文 *
基于消息队列遥测传输协议的智能家居消息中间件设计;李洋;《计算机应用》;20180630;全文 *

Also Published As

Publication number Publication date
CN114938388A (en) 2022-08-23

Similar Documents

Publication Publication Date Title
US10594641B2 (en) Dynamic filter generation for message management systems
CN108449410B (en) Message management method, system and related device in cloud platform
US7886295B2 (en) Connection manager, method, system and program product for centrally managing computer applications
US8195757B2 (en) Method, apparatus and computer program for controlling retention of publications
US6868544B2 (en) Method and system for general-purpose interactive notifications
CN112527525B (en) Distributed event bus processing method, terminal and medium based on message queue
US8103253B2 (en) System and method for transmitting messages to a wireless communication device
US9397861B1 (en) Unified communication
JP2007149099A (en) Service broker integration layer for supporting telecommunication client service request
KR20110020218A (en) Pushing identity information
CN107888787B (en) Method and device for processing media access request
CN111711697A (en) Message pushing method, device, equipment and storage medium
US20030018721A1 (en) Unified messaging with separate media component storage
CN114938388B (en) Distributed data transmission method, device, system and storage medium
CN111200606A (en) Deep learning model task processing method, system, server and storage medium
CN115022318B (en) Message publishing method and system based on micro-service architecture
CN111460038A (en) Quasi-real-time data synchronization method and device
CN114338769A (en) Access request processing method and device
US9455946B1 (en) Server for providing unified communications
CN115334155B (en) Message queue proxy method and device
CN115333942B (en) Event retry method and device, storage medium and electronic equipment
WO2019201111A1 (en) Information processing method, apparatus and device, and computer-readable storage medium
CN116192927A (en) Data transmission method and device based on SaaS service, computer equipment and medium
CN107102901B (en) Task processing method and device
CN112596933A (en) Micro-service system based on message event communication

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
GR01 Patent grant
GR01 Patent grant
CP03 Change of name, title or address
CP03 Change of name, title or address

Address after: 310053 No. 309 Liuhe Road, Binjiang District, Hangzhou City, Zhejiang Province

Patentee after: Zhongkong Technology Co.,Ltd.

Country or region after: China

Address before: 309 Liuhe Road, Binjiang District, Hangzhou, Zhejiang 310000

Patentee before: ZHEJIANG SUPCON TECHNOLOGY Co.,Ltd.

Country or region before: China