CN116112568A - Distributed connection management uplink message receiving system based on message queue - Google Patents
Distributed connection management uplink message receiving system based on message queue Download PDFInfo
- Publication number
- CN116112568A CN116112568A CN202310130142.9A CN202310130142A CN116112568A CN 116112568 A CN116112568 A CN 116112568A CN 202310130142 A CN202310130142 A CN 202310130142A CN 116112568 A CN116112568 A CN 116112568A
- Authority
- CN
- China
- Prior art keywords
- service processing
- connection management
- server
- uplink
- internet
- 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
- 238000012545 processing Methods 0.000 claims abstract description 116
- 238000000034 method Methods 0.000 claims abstract description 26
- 230000008569 process Effects 0.000 claims abstract description 17
- 230000005540 biological transmission Effects 0.000 claims description 8
- 238000013507 mapping Methods 0.000 claims description 5
- 238000005538 encapsulation Methods 0.000 claims description 3
- 238000011144 upstream manufacturing Methods 0.000 claims description 3
- 238000004891 communication Methods 0.000 description 9
- 238000010586 diagram Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000003491 array Methods 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 210000001072 colon Anatomy 0.000 description 1
- 239000002131 composite material Substances 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
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/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/163—In-band adaptation of TCP data exchange; In-band control procedures
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Telephonic Communication Services (AREA)
Abstract
The application relates to the technical field of equipment management of the Internet of things, in particular to a distributed connection management uplink message receiving system based on a message queue, which comprises the following components: a message queue server, a service processing server group and a plurality of connection management servers; the connection management server receives uplink data sent by the Internet of things equipment through a TCP protocol, constructs uplink messages according to the uplink data, adds a preset subscription theme into the uplink messages, and sends the uplink messages to the message queue server; the message queue server searches a service processing server group subscribed to a preset subscription theme, determines a final service processing server from all service processing servers subscribed to the preset subscription theme in the service processing server group, and pushes the uplink message to the final service processing server; and the final service processing server processes the uplink information.
Description
Technical Field
The application relates to the technical field of equipment management of the Internet of things, in particular to a distributed connection management uplink message receiving system based on a message queue.
Background
In a common internet of things system (internet of things equipment and a management platform), most of communication protocols of the internet of things equipment are custom non-standard interfaces, most of various internet of things equipment are connected to the management platform in a TCP (Transmission Control Protocol ) mode, and a large number of internet of things equipment exist in the system, so that TCP connection management and load balancing become a key point of the management platform. In order to solve the processing efficiency of mass data, a plurality of machines are required to be deployed for load balancing by the TCP connection management server and the service processing server, and a many-to-many relationship is formed between the TCP connection management server and the service processing server.
For the management of mass internet of things devices, the mass internet of things devices are divided according to whether device communication protocols are standardized or not, and two implementation methods are generally adopted:
1) Standardized device management based on MQTT (Message Queuing Telemetry Transport, message queue telemetry transport) protocol
MQTT is a communication protocol based on publish/subscribe mode, which is built on the TCP/IP protocol. The MQTT has the greatest advantages that: providing real-time reliable messaging services to connected remote devices with very little code and limited bandwidth. The business processing server subscribes to Topic (subscription subject) corresponding to the uplink message sent by the internet of things device through the MQTT, and when the internet of things device sends the uplink message to the corresponding Topic, the business processing server receives the corresponding data. However, this solution is limited in that: the internet of things device must support the MQTT protocol, and if the internet of things device does not support the MQTT protocol, this mode cannot be used.
2) Personalized device management based on custom protocol
At present, many internet of things devices do not support the MQTT protocol, but the application layer transmission protocol based on TCP is customized, and the transmission protocols among different types of internet of things devices are inconsistent.
For processing uplink messages, most of the internet of things devices adopt the same mode: the internet of things equipment sends data to a load balancing gateway, the load balancing gateway forwards the data to a connection management server, the connection management server forwards the data to a service processing server for processing after processing, and some systems do not even distinguish roles of the connection management server and the service processing server, and all services are processed in one server.
The existing management mode of the internet of things equipment cannot ensure that the uplink data of mass internet of things equipment can be accurately distributed to the service processing server, so that the accurate uploading of the data is realized.
Disclosure of Invention
In order to solve the problem that the management mode of the Internet of things equipment cannot guarantee that the uplink data of mass Internet of things equipment can be accurately distributed to a service processing server in the related technology at least to a certain extent and realize accurate uploading of the data, the application provides a distributed connection management uplink message receiving system based on a message queue.
The scheme of the application is as follows:
a message queue based distributed connection management uplink message receiving system, comprising:
a message queue server, a service processing server group and a plurality of connection management servers;
the connection management server receives uplink data sent by the Internet of things equipment through a TCP protocol, constructs uplink messages according to the uplink data, adds a preset subscription theme into the uplink messages, and sends the uplink messages to the message queue server;
the message queue server searches a service processing server group subscribed to the preset subscription theme, determines a final service processing server from all service processing servers subscribed to the preset subscription theme in the service processing server group, and pushes the uplink message to the final service processing server;
and the final service processing server processes the uplink information.
Preferably, the preset subscription theme supports subscription by different service processing servers in the same service processing server group, and only supports subscription once by the same service processing server;
different service processing servers in the same service processing server group support subscribing to the same subscription topic, and different service processing servers in the same service processing server group support subscribing to different subscription topics.
Preferably, the system further comprises: a load balancing server;
the load balancing server is used for receiving uplink data sent by the Internet of things equipment through a TCP protocol, and determining a final connection management server in the plurality of connection management servers so as to send the uplink data to the final connection management server through the TCP protocol.
Preferably, the final connection management server is a connection management server with least current processing task matters among a plurality of connection management servers.
Preferably, the connection management server determines a unique identifier of the connection management server, obtains a unique identifier of the internet of things device sending the uplink data, allocates the unique identifier to the uplink data, and constructs the uplink message according to the uplink data, the unique identifier of the connection management server, the unique identifier of the internet of things device and the unique identifier of the uplink data.
Preferably, the encapsulation format of the uplink message is:
the connection management server itself uniquely identifies: unique identification of the internet of things device: unique identification of uplink data: uplink data.
Preferably, the service processing server tracks the sending state of the uplink message according to the unique identifier of the uplink data; and positioning the source position of the uplink message according to the unique identifier of the connection management server and the unique identifier of the Internet of things equipment.
Preferably, the system further comprises: a caching device;
the cache device is used for caching the mapping relation between the unique identifier of the connection management server and the unique identifier of the internet of things device and is used for identifying the connection management server connected with the internet of things device.
The technical scheme that this application provided can include following beneficial effect: the distributed connection management uplink message receiving system based on the message queue in the application comprises: a message queue server, a service processing server group and a plurality of connection management servers; the connection management server receives uplink data sent by the Internet of things equipment through a TCP protocol, constructs uplink messages according to the uplink data, adds a preset subscription theme into the uplink messages, and sends the uplink messages to the message queue server; the message queue server searches a service processing server group subscribed to a preset subscription theme, determines a final service processing server from all service processing servers subscribed to the preset subscription theme in the service processing server group, and pushes the uplink message to the final service processing server; and the final service processing server processes the uplink information. According to the technical scheme, the fact that the TCP custom protocol is adopted by many Internet of things equipment at present and the MQTT protocol is not supported is considered, so that the TCP protocol is adopted in the technical scheme in the application during data transmission. Because of the inconsistent TCP transmission protocols between different types of Internet of things devices, message queues are used in the present application to handle communication connections. The traditional message queue service only has the processing capability of massive messages, the number of subscription topics and the number of connections supported by the traditional message queue service are limited, and each piece of internet of things equipment cannot be allocated with one subscription topic and/or one connection, so that the traditional message queue service has no capability of processing the access of the massive internet of things equipment. The technical scheme in the application is based on the traditional message queue service, continuously adopts a publish/subscribe mode to realize communication, and further optimizes the connection management capability on the basis of the publish/subscribe mode: the method comprises the steps that a preset subscription theme is added into an uplink message through a connection management server, the uplink message is pushed to a final selection service processing server subscribed to the preset subscription theme through a message queue server, and the final selection service processing server processes the uplink message independently. Therefore, when a plurality of service processing servers in the same service processing server group subscribe to the same preset subscription theme, only one service processing server can process the preset subscription theme, namely only one service processing server can receive the uplink message, so that the load balance of service processing can be realized, and the access management of mass Internet of things equipment is realized. In the application, the TCP connection management of the mass Internet of things equipment is realized through the cooperation of the message queue server and the plurality of connection management servers.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.
FIG. 1 is a block diagram of a distributed connection management uplink message receiving system based on message queues according to one embodiment of the present application;
fig. 2 is a block diagram of another distributed connection management uplink message receiving system based on a message queue according to an embodiment of the present application.
Reference numerals: a message queue server-1; a service processing server group-2; a connection management server-3; load balancing server-4.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the accompanying claims.
Fig. 1 is a block diagram of a distributed connection management uplink message receiving system based on a message queue according to an embodiment of the present application, and referring to fig. 1, a distributed connection management uplink message receiving system based on a message queue includes:
a message queue server 1, a service processing server group 2, and a plurality of connection management servers 3;
the connection management server 3 receives uplink data sent by the Internet of things equipment through a TCP protocol, constructs uplink messages according to the uplink data, adds a preset subscription theme into the uplink messages, and sends the uplink messages to the message queue server 1;
the message queue server 1 searches a service processing server group 2 subscribed to a preset subscription theme, determines a final service processing server from all service processing servers subscribed to the preset subscription theme in the service processing server group 2, and pushes the uplink message to the final service processing server;
and the final service processing server processes the uplink information.
It should be noted that, since many of the internet of things devices currently adopt the TCP custom protocol and cannot use the MQTT mode, it is an ideal mode to process the connection by adopting the message queue service. However, the conventional message queuing service (such as Kafka, rabbitMQ) only has the processing capability of mass messages, the number of topics and the number of connections supported by the conventional message queuing service are limited, and it is impossible to allocate one Topic to each internet of things device and/or one connection, so the conventional message queuing service has no capability of processing access of mass devices. The scheme is based on the traditional message queue service, continuously adopts a publish/subscribe mode to realize communication, and further optimizes the connection management capability on the basis of the publish/subscribe mode, thereby realizing access management of mass equipment.
In the message queue mechanism, the producer sends information to the message queue, and the consumer pulls/retrieves information from the message queue. The consumer obtains the message by subscribing to the Topic (Topic for short) and may therefore also be referred to as a subscriber. Subscribers must belong to a certain subscriber group (simply referred to as a group), which is a relationship between individuals and groups, one subscriber may belong to one or more subscriber groups, and one or more subscribers may exist within one subscriber group. When a producer publishes a message to a given Topic, multiple subscribers to that Topic within the same group, and only one subscriber can receive the message; multiple subscribers to the Topic within different groups can all receive the message. That is, all groups associated with Topic can receive messages, but there is and only one subscriber in each group that can receive messages. In a practical scenario, both the producer and the consumer are composed of various servers.
The technical scheme in this embodiment introduces three server roles:
1) And a connection management server 3. The connection management server 3 is specially used for processing the connection of the internet of things equipment, and although each machine has limited capability of processing the connection, the system can realize the management of mass connection by deploying a large number of connection management servers 3. Each connection management server 3 may manage different internet of things device connections and only process data connected to the internet of things devices in the present server.
2) And a service processing server. The service processing servers are responsible for processing service data, are deployed in a cluster mode, and each service processing server has the same state and can process data of any one Internet of things device.
3) Message queue server 1. Message queues can handle a large number of messages, but cannot support a large number of connections and a large number of Topic subscriptions, such as Kafka, rabbitMQ.
It should be noted that, the preset subscription theme supports subscription by different service processing servers in the same service processing server group 2, and only supports subscription once by the same service processing server;
different service processing servers in the same service processing server group 2 support subscribing to the same subscription topic, and different service processing servers in the same service processing server group 2 support subscribing to different subscription topics.
Therefore, when a plurality of service processing servers in the same service processing server group 2 subscribe to the same Topic, only one service processing server can process the data of the Topic, namely, only one service processing server can receive the message, thereby realizing the load balance of service processing.
It should be noted that, referring to fig. 2, the system further includes: a load balancing server 4;
the load balancing server 4 is configured to receive uplink data sent by the internet of things device through a TCP protocol, and determine a final connection management server 3 from the plurality of connection management servers 3, so as to send the uplink data to the final connection management server 3 through the TCP protocol.
In specific practice, the final connection management server is the connection management server 3 with the least current processing task among the plurality of connection management servers 3, i.e., the relatively idle connection management server 3.
The uplink data is data uploaded by the internet of things device, and the uplink message is a composite message constructed by the connection management server 3 according to the uplink data.
In this technical scheme, the connection management server 3 receives uplink data sent by the internet of things device through the TCP protocol, and constructs an uplink message according to the uplink data. The specific process is as follows:
the connection management server 3 determines the unique identifier of the connection management server, obtains the unique identifier of the internet of things device sending the uplink data, allocates the unique identifier for the uplink data, and constructs the uplink message according to the uplink data, the unique identifier of the connection management server 3, the unique identifier of the internet of things device and the unique identifier of the uplink data.
The encapsulation format of the uplink message is as follows:
the connection management server 3 itself uniquely identifies: unique identification of the internet of things device: unique identification of uplink data: uplink data.
Illustrating:
the uplink message comprises the following components:
1) Cserversuid, the connection management server 3 uniquely identifies, describes which connection management server 3 the current message is received by.
2) The DeviceUID, the internet of things device unique identification, describes which internet of things device the current message was sent by.
3) The MsgUID, the unique message identifier, does not distinguish between the uplink and downlink messages, is used for tracking the sending state of the current message.
4) The data formats of the uplink data sent by the Internet of things equipment and different types of Internet of things equipment can be customized.
The components of the uplink message are separated by colon, namely:
“CServerUID:DeviceUID:MsgUID:UpMsgData”。
in specific practice, the technical scheme introduces a Topic (namely preset subscription theme) type:
1) TcpRecvOne for processing data upstream of an internet of things device, there being one and only one of this type of Topic.
Correspondingly, a group (i.e. service processing server group) type is also introduced:
2) RecvGroup, all subscribed to Topic: the service processing servers of TcpRecvOne all belong to this group, which has and only one.
It should be noted that TcpRecvOne is only an exemplary name shown in this embodiment, and may be replaced by other names defined by themselves in specific practice. RecvGroup is just an exemplary name shown in this embodiment and may be replaced with other names that are self-defining in specific practice.
The unique identifier of the connection management server 3 may be the connection management server 3ID, or may be replaced by another identifier of the connection management server 3, or may be replaced by another name defined by itself. The unique identifier of the internet of things equipment can be the internet of things equipment ID, can be replaced by other identifiers of the internet of things equipment, and can be replaced by other names defined by users.
All service processing servers subscribe to Topic in the RecvGroup group: tcpRecvOne.
In a specific implementation, the internet of things device reports data, connects to the load balancing server 4 through TCP, and the load balancing server 4 forwards the connection to a relatively idle connection management server 3 (i.e. the terminating connection management server 3). After receiving uplink data sent by the internet of things device, the connection management server 3 finds out its own unique identifier cserverouid, obtains the unique identifier DeviceUID of the internet of things device, packetizes and packetizes the uplink data according to the user-defined protocol packet identifier of the internet of things device to obtain uplink data UpMsgData sent by the internet of things device, finally distributes the unique identifier msgsuid to the uplink data, and constructs an uplink message according to the mode of 'cserverouid: msuid: upMsgData', and the message queue server 1 assigns a preset subscription theme Topic to the uplink message: tcpRecvOne.
Since all the service processing servers are in the same group recvcgroup and all subscribe to Topic: since TcpRecvOne only one of the service processing servers receives the uplink message, the service data is processed. The service processing server analyzes the unique identifier of the connection management server 3, the unique identifier of the internet of things device, the unique identifier of the uplink data and the uplink data in the uplink message, analyzes the uplink data according to the corresponding device communication protocol, and then performs service processing.
At the same time, the system globally caches the mapping relationship between the device DeviceUID and the connection management server 3cserver uid, so as to identify which device is connected to which connection management server 3.
It should be noted that, the service processing server tracks the sending state of the uplink message according to the unique identifier of the uplink data; and positioning the source position of the uplink message according to the unique identifier of the connection management server 3 and the unique identifier of the Internet of things equipment.
It can be understood that, in the technical scheme, by embedding the connection management server 3 unique identifier CServerUID and the internet of things device unique identifier DeviceUID in the uplink message, the source position of the uplink data can be rapidly positioned after the service processing server processes the data, and excessive global cache inquiry is not needed.
It should be noted that the system further includes: a caching device;
the caching device is used for caching the mapping relation between the unique identifier of the connection management server 3 and the unique identifier of the internet of things device, and is used for identifying the connection management server 3 connected with the internet of things device.
It can be understood that in this embodiment, the mapping relationship between the unique identifier of the connection management server 3 and the unique identifier of the internet of things device is globally cached by the caching device, so as to identify which internet of things device is connected to which connection management server 3.
It can be understood that, in the technical scheme in this embodiment, because many of the current internet of things devices adopt the TCP custom protocol and do not support the MQTT protocol, the technical scheme in this application adopts the TCP protocol during data transmission. Because of the inconsistent TCP transmission protocols between different types of Internet of things devices, message queues are used in the present application to handle communication connections. The traditional message queue service only has the processing capability of massive messages, the number of subscription topics and the number of connections supported by the traditional message queue service are limited, and each piece of internet of things equipment cannot be allocated with one subscription topic and/or one connection, so that the traditional message queue service has no capability of processing the access of the massive internet of things equipment. The technical solution in this embodiment is based on the conventional message queue service, and the communication is continuously implemented in the publish/subscribe mode, and on this basis, the connection management capability is further optimized: the method comprises the steps that a preset subscription theme is added into an uplink message through a connection management server, the uplink message is pushed to a final selection service processing server subscribed to the preset subscription theme through a message queue server, and the final selection service processing server processes the uplink message independently. Therefore, when a plurality of service processing servers in the same service processing server group subscribe to the same preset subscription theme, only one service processing server can process the preset subscription theme, namely only one service processing server can receive the uplink message, so that the load balance of service processing can be realized, and the access management of mass Internet of things equipment is realized. In the application, the TCP connection management of the mass Internet of things equipment is realized through the cooperation of the message queue server and the plurality of connection management servers.
It is to be understood that the same or similar parts in the above embodiments may be referred to each other, and that in some embodiments, the same or similar parts in other embodiments may be referred to.
It should be noted that in the description of the present application, the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. Furthermore, in the description of the present application, unless otherwise indicated, the meaning of "plurality" means at least two.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and further implementations are included within the scope of the preferred embodiment of the present application in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the embodiments of the present application.
It is to be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above-described embodiments, the various steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, may be implemented using any one or combination of the following techniques, as is well known in the art: discrete logic circuits having logic gates for implementing logic functions on data signals, application specific integrated circuits having suitable combinational logic gates, programmable Gate Arrays (PGAs), field Programmable Gate Arrays (FPGAs), and the like.
Those of ordinary skill in the art will appreciate that all or a portion of the steps carried out in the method of the above-described embodiments may be implemented by a program to instruct related hardware, where the program may be stored in a computer readable storage medium, and where the program, when executed, includes one or a combination of the steps of the method embodiments.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing module, or each unit may exist alone physically, or two or more units may be integrated in one module. The integrated modules may be implemented in hardware or in software functional modules. The integrated modules may also be stored in a computer readable storage medium if implemented in the form of software functional modules and sold or used as a stand-alone product.
The above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, or the like.
In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present application. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiments or examples. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
Although embodiments of the present application have been shown and described above, it will be understood that the above embodiments are illustrative and not to be construed as limiting the application, and that variations, modifications, alternatives, and variations may be made to the above embodiments by one of ordinary skill in the art within the scope of the application.
Claims (8)
1. A distributed connection management uplink message receiving system based on a message queue, comprising:
a message queue server, a service processing server group and a plurality of connection management servers;
the connection management server receives uplink data sent by the Internet of things equipment through a TCP protocol, constructs uplink messages according to the uplink data, adds a preset subscription theme into the uplink messages, and sends the uplink messages to the message queue server;
the message queue server searches a service processing server group subscribed to the preset subscription theme, determines a final service processing server from all service processing servers subscribed to the preset subscription theme in the service processing server group, and pushes the uplink message to the final service processing server;
and the final service processing server processes the uplink information.
2. The system of claim 1, wherein the pre-set subscription topic supports subscriptions by different service processing servers within the same service processing server group and only one subscription by the same service processing server;
different service processing servers in the same service processing server group support subscribing to the same subscription topic, and different service processing servers in the same service processing server group support subscribing to different subscription topics.
3. The system of claim 1, wherein the system further comprises: a load balancing server;
the load balancing server is used for receiving uplink data sent by the Internet of things equipment through a TCP protocol, and determining a final connection management server in the plurality of connection management servers so as to send the uplink data to the final connection management server through the TCP protocol.
4. A system according to claim 3, wherein the terminating connection management server is the connection management server having the least current processing task among the plurality of connection management servers.
5. The system of claim 1, wherein the connection management server determines a unique identifier of the connection management server, obtains a unique identifier of the internet of things device that transmits the uplink data, assigns a unique identifier to the uplink data, and constructs the uplink message according to the uplink data, the unique identifier of the connection management server, the unique identifier of the internet of things device, and the unique identifier of the uplink data.
6. The system of claim 5, wherein the encapsulation format of the uplink message is:
the connection management server itself uniquely identifies: unique identification of the internet of things device: unique identification of uplink data: uplink data.
7. The system of claim 5, wherein the service processing server tracks the transmission status of the upstream message based on a unique identification of upstream data; and positioning the source position of the uplink message according to the unique identifier of the connection management server and the unique identifier of the Internet of things equipment.
8. The system of claim 5, wherein the system further comprises: a caching device;
the cache device is used for caching the mapping relation between the unique identifier of the connection management server and the unique identifier of the internet of things device and is used for identifying the connection management server connected with the internet of things device.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310130142.9A CN116112568A (en) | 2023-02-17 | 2023-02-17 | Distributed connection management uplink message receiving system based on message queue |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310130142.9A CN116112568A (en) | 2023-02-17 | 2023-02-17 | Distributed connection management uplink message receiving system based on message queue |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116112568A true CN116112568A (en) | 2023-05-12 |
Family
ID=86267147
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310130142.9A Pending CN116112568A (en) | 2023-02-17 | 2023-02-17 | Distributed connection management uplink message receiving system based on message queue |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116112568A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109451072A (en) * | 2018-12-29 | 2019-03-08 | 广东电网有限责任公司 | A kind of message caching system and method based on Kafka |
| CN110012083A (en) * | 2019-03-26 | 2019-07-12 | 青岛聚好联科技有限公司 | A kind of data transmission method, server and data transmission device |
| CN110022226A (en) * | 2019-01-04 | 2019-07-16 | 国网浙江省电力有限公司 | A kind of data collection system and acquisition method based on object-oriented |
| CN111432295A (en) * | 2020-03-18 | 2020-07-17 | 北京科东电力控制系统有限责任公司 | Power consumption information acquisition master station system based on distributed technology |
-
2023
- 2023-02-17 CN CN202310130142.9A patent/CN116112568A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109451072A (en) * | 2018-12-29 | 2019-03-08 | 广东电网有限责任公司 | A kind of message caching system and method based on Kafka |
| CN110022226A (en) * | 2019-01-04 | 2019-07-16 | 国网浙江省电力有限公司 | A kind of data collection system and acquisition method based on object-oriented |
| CN110012083A (en) * | 2019-03-26 | 2019-07-12 | 青岛聚好联科技有限公司 | A kind of data transmission method, server and data transmission device |
| CN111432295A (en) * | 2020-03-18 | 2020-07-17 | 北京科东电力控制系统有限责任公司 | Power consumption information acquisition master station system based on distributed technology |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11184299B2 (en) | Hierarchical publish and subscribe system | |
| US8688854B2 (en) | Messenger notification system and method using synchronization server | |
| CN101540775B (en) | Method and device for distributing contents and network system for distributing contents | |
| CN101426726B (en) | System and method for optimizing inter-domain event services | |
| US20050228895A1 (en) | Method, Web service gateway (WSG) for presence, and presence server for presence information filtering and retrieval | |
| US20110264777A1 (en) | Communications device and method | |
| CN110661871B (en) | Data transmission method and MQTT server | |
| US9269080B2 (en) | Hierarchical publish/subscribe system | |
| US9762405B2 (en) | Hierarchical publish/subscribe system | |
| US20040047303A1 (en) | Apparatus, system and method for managing call requests in a communication network providing a plurality of communication services | |
| US20080034078A1 (en) | Presence information management system, presence server device, gateway device and client device | |
| US9569753B2 (en) | Hierarchical publish/subscribe system performed by multiple central relays | |
| EP3496432A1 (en) | Communication method and device | |
| CN111131443B (en) | Task pushing method and system | |
| EP1480381A2 (en) | Method and system for message based policy distribution | |
| CN106899605B (en) | Communication method and device based on STOMP protocol | |
| US7325072B2 (en) | Inter-subnet multicast relaying service-a network infrastructure independent solution to cross subnet multicasting | |
| WO2022126837A1 (en) | Intelligent scheduling system for video monitoring service | |
| CN116112568A (en) | Distributed connection management uplink message receiving system based on message queue | |
| US20070064726A1 (en) | Endpoint transparent independent messaging scheme system and method | |
| CN114051030A (en) | Communication method, communication device, smart community system and storage medium | |
| KR101969652B1 (en) | Apparatus and method for transmitting data, iot system employing the same, program recording dataum, and program recorded on medium for executing the method | |
| CN116170499A (en) | Broadcast message and acknowledgement message processing method based on message queue | |
| KR20240058522A (en) | Method and Apparatus for Two-way Communication Between Large Number of Devices and Cloud Server System | |
| CN116192942A (en) | Method for processing downlink message and acknowledgement message based on message queue |
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 |