CN116886766A - Distributed message pushing method, system, equipment and medium - Google Patents

Distributed message pushing method, system, equipment and medium Download PDF

Info

Publication number
CN116886766A
CN116886766A CN202311027477.4A CN202311027477A CN116886766A CN 116886766 A CN116886766 A CN 116886766A CN 202311027477 A CN202311027477 A CN 202311027477A CN 116886766 A CN116886766 A CN 116886766A
Authority
CN
China
Prior art keywords
message
client
pushing
pushed
gateway
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
Application number
CN202311027477.4A
Other languages
Chinese (zh)
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.)
Beijing Yusys Technologies Group Co ltd
Original Assignee
Beijing Yusys Technologies Group 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 Beijing Yusys Technologies Group Co ltd filed Critical Beijing Yusys Technologies Group Co ltd
Priority to CN202311027477.4A priority Critical patent/CN116886766A/en
Publication of CN116886766A publication Critical patent/CN116886766A/en
Pending legal-status Critical Current

Links

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/50—Network services
    • H04L67/55—Push-based network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1073—Registration or de-registration
    • 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
    • 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/104—Peer-to-peer [P2P] networks
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Multimedia (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The invention discloses a distributed message pushing method, a system, equipment and a medium, which relate to the technical field of message pushing, and the method is used for a message pushing gateway, wherein the message pushing gateway is connected with a message sending end and a plurality of clients, and comprises the following steps: receiving registration information sent by a client, and registering data structures corresponding to different message types for the client according to the registration information; monitoring a message to be pushed from a message queue of a message sending end, and analyzing the message to be pushed to judge the type of the message; and pushing the message to be pushed to the corresponding client according to the data structure corresponding to the message type of the message to be pushed. The stable and efficient message pushing is ensured, the system is not dragged by message storm, the lightweight design can be realized, and the system is simple and easy to maintain.

Description

Distributed message pushing method, system, equipment and medium
Technical Field
The present invention relates to the field of message pushing technologies, and in particular, to a distributed message pushing method, system, device, and medium.
Background
Message pushing can be understood as: the server side sends a message to the client side, and the messages received by the client side in a notification bar, a screen locking notification, a WeChat message and the like belong to message pushing. The main purpose of message pushing is as follows: the information notification and reminding method comprises the steps of publishing contents such as relevant product update, content update and activity information, pushing the contents to a user through a message pushing channel, and enabling the user to know the information at the first time; the user activity and the user viscosity are improved, the message pushing can directly wake up the application, and the user activity can be effectively promoted through the direct contact of the message; the silent users are awakened, some users do not open one-time application for a long time, and the users can be awakened for one-time pushing from time to time, so that a part of lost users can be awakened; the guiding module is used, when the new module is released, the user can be prompted to use the module by pushing the guiding module, and the module utilization rate is improved.
The existing message pushing method generally generates and sends messages for each client of the whole person respectively, for example, hundreds of thousands of clients can generate and send hundreds of thousands of messages, so that massive memory of an operating system can be occupied, and the generated messages can not reach the off-line clients, so that resource waste is caused, and the message pushing efficiency is low and unstable.
Disclosure of Invention
In view of the above, the present invention provides a distributed message pushing method, system, device and medium, which at least partially solve the problems existing in the prior art.
To solve the above problems, according to one aspect of the present invention, there is provided a distributed message pushing method for a message pushing gateway, the message pushing gateway connecting a message sending end and a plurality of clients, the method comprising: step S1, receiving registration information sent by the client, and registering data structures corresponding to different message types for the client according to the registration information; step S2, monitoring a message to be pushed from the message queue of the message sending end, and analyzing the message to be pushed to judge the message type; step S3, pushing the message to be pushed to the corresponding client according to the data structure corresponding to the message type of the message to be pushed.
Preferably, the registration information includes: the system comprises a client ID, an organization ID and a theme ID, wherein the organization ID is the ID of an organization added by the client, and the theme ID is the ID of a theme subscribed by the client; the data structure comprises: point-to-point data structures, organization data structures, and topic data structures.
Preferably, the point-to-point data structure includes the client ID; when the message to be pushed is a point-to-point message, pushing the message to be pushed to a corresponding client includes: pushing the message to be pushed to a client corresponding to the client ID appointed by the message to be pushed.
Preferably, the institution data structure comprises: a mechanism ID of a mechanism, and a client ID of a client joining the mechanism; when the message to be pushed is an organization message, pushing the message to be pushed to a corresponding client includes: inquiring a client ID corresponding to the mechanism ID appointed by the message to be pushed from the mechanism data structure; pushing the message to be pushed to the client corresponding to the queried client ID.
Preferably, the theme data structure includes: topic ID of a topic and client ID of a client subscribing to the topic; when the message to be pushed is a subject message, pushing the message to be pushed to a corresponding client includes: inquiring a client ID corresponding to the topic ID appointed by the message to be pushed from the topic data structure; pushing the message to be pushed to the client corresponding to the queried client ID.
Preferably, the message push gateway is connected with the client in a long way; when the client first opens an application or wakes up a screen saver, if the long connection is in a disconnected state, the step S1 further includes: and reestablishing the long connection between the message push gateway and the client.
Preferably, the number of the message push gateways is one or more; each message pushing gateway is connected with a plurality of clients, and each client is connected with one message pushing gateway.
According to another aspect of the present invention, there is provided a distributed message pushing system for a message pushing gateway, the message pushing gateway connecting a message sending end and a plurality of clients, the system comprising: the receiving and registering module is used for receiving the registering information sent by the client and registering data structures corresponding to different message types for the client according to the registering information; the monitoring and analyzing module is used for monitoring the message to be pushed from the message queue of the message sending end and analyzing the message to be pushed to judge the message type; and the pushing module is used for pushing the message to be pushed to the corresponding client according to the data structure corresponding to the message type of the message to be pushed.
According to another aspect of the present invention, there is provided an electronic apparatus including: a processor; a memory storing a computer executable program that, when executed by the processor, causes the processor to perform the distributed message pushing method as described above.
According to another aspect of the present invention, there is provided a computer readable storage medium having stored thereon a computer program which when executed by a processor implements a distributed message pushing method as described above.
In general, through the above technical solutions conceived by the present invention, the following beneficial effects can be obtained: the method has the advantages that the message pushing gateway side is provided with the data structures corresponding to different message types, the message sending end can only generate one message, and the message is only pushed to each online client through the message pushing gateway and the unique data structure, so that the occupation of mass memory of an operating system of the message sending end is avoided, the resource waste is avoided, and the high efficiency and stability of message pushing are ensured; by combining the message queues, the stable and efficient message pushing can be ensured, and the system is not collapsed by message storm; the message pushing gateway supports cluster deployment, capacity expansion can be realized in any number horizontally, client login is only connected to one message pushing gateway, pressure of a single node is shared to a plurality of nodes, and light and efficient operation of the system is ensured.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a flowchart of a distributed message pushing method provided in an embodiment of the present invention;
fig. 2 is a schematic diagram of a connection stage of a client and a message push gateway for the first time according to an embodiment of the present invention;
fig. 3 is a schematic diagram of a message push monitoring phase according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of peer-to-peer message pushing according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of mechanism message pushing provided by an embodiment of the present invention;
FIG. 6 is a schematic diagram of theme message push provided by an embodiment of the present invention;
fig. 7 is a schematic diagram of capacity expansion of a message push gateway according to an embodiment of the present invention;
FIG. 8 is a block diagram of a distributed message pushing system provided by an embodiment of the present invention;
fig. 9 is a block diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
Embodiments of the present invention will be described in detail below with reference to the accompanying drawings.
It should be noted that, without conflict, the following embodiments and features in the embodiments may be combined with each other; and, based on the embodiments in this disclosure, all other embodiments that may be made by one of ordinary skill in the art without inventive effort are within the scope of the present disclosure.
The aspects described herein may be embodied in a wide variety of forms and any specific structure and/or function described herein is merely illustrative. Based on the present disclosure, one skilled in the art will appreciate that one aspect described herein may be implemented independently of any other aspect, and that two or more of these aspects may be combined in various ways. For example, an apparatus may be implemented and/or a method practiced using any number of the aspects set forth herein. In addition, such apparatus may be implemented and/or such methods practiced using other structure and/or functionality in addition to one or more of the aspects set forth herein.
Fig. 1 is a flowchart of a distributed message pushing method according to an embodiment of the present invention. Referring to fig. 1, the method is used for a message pushing gateway, and in combination with fig. 2 to fig. 7, a distributed message pushing method in this embodiment is described in detail, and the method includes steps S1 to S3.
Step S1, receiving registration information sent by a client, and registering data structures corresponding to different message types for the client according to the registration information.
According to an embodiment of the invention, a long connection is provided between the message push gateway and the client. The long connection does not need to be frequently established or closed, so that the memory use can be reduced, and the pushing efficiency is improved. Preferably, the message pushes a socket long connection between the gateway and the client. Compared with other long connections, the socket long connection has the advantages of less control overhead, stronger instantaneity and support expansion. When the client side opens the application for the first time or wakes up the screen saver, if the long connection is in a disconnected state, the method further comprises the following steps before executing the step S1: the long connection between the message push gateway and the client is re-established.
When the client is in the screen saver state, all processes of the operating system are interrupted, so in this embodiment, when the client opens an application for the first time or wakes up each time, a long connection is attempted to be established with the message push gateway. When the long connection has been disconnected a new long connection will be established and the client ID, the topic ID of the subscription topic, the affiliate ID of the joining entity will be registered with the message push gateway as shown in fig. 2.
For any client, the registration information sent by the client to the message push gateway includes: the client comprises a client ID, an organization ID and a theme ID, wherein the organization ID is the ID of an organization added by the client, and the theme ID is the ID of a theme subscribed by the client. The client IDs are unique and correspond one-to-one to the clients.
After receiving the registration information sent by each client, the message pushing gateway registers the registration information of the client as three different data structures: point-to-point data structures, organization data structures, and topic data structures.
Referring to fig. 2, the point-to-point data structure includes client IDs, specifically client IDs of all clients to which the message push gateway is currently connected in a long way. The organization data structure includes an organization ID, and a client ID joining the organization, including, for example, an organization ID of an organization N, IDs of all clients that are currently long connected by the message push gateway and joining the organization N, n=1, 2, … …, N, where N is the total number of organization categories. The topic data structure includes a topic ID, and a client ID subscribed to the topic, e.g., a topic ID including topic M, IDs of all clients currently long connected by the message push gateway and subscribed to topic M, n=1, 2, … …, M, where M is the total number of categories of topics.
And S2, monitoring a message to be pushed from a message queue of a message sending end, and analyzing the message to be pushed to judge the type of the message.
And the Message sending end sends the Message to be pushed in the data structure form to a Message Queue (MQ). The message push gateway monitors the message to be pushed, analyzes the data structure of the message to be pushed, and judges the message type of the message to be pushed, as shown in fig. 3. Message types include point-to-point messages, organization messages, and topic messages.
Referring to fig. 3, the point-to-point message is, for example: the user 1 client sends a 'hello' to the user 2 client; the organization message is, for example: sending a "full-member leave-out" to all clients joining the Org1 institution; the subject message is, for example: and sending 'money is already checked out' to all clients subscribed to the money release notification theme.
And step S3, pushing the message to be pushed to the corresponding client according to the data structure corresponding to the message type of the message to be pushed.
According to the message type (point-to-point message, organization message or theme message) of the message to be pushed, the corresponding client socket long connection is found by combining the data structure (point-to-point data structure, organization data structure or theme data structure) registered by the message pushing gateway, and the message content of the message to be pushed is sent to the client.
According to an embodiment of the present invention, when the message to be pushed is a point-to-point message, pushing the message to be pushed to a corresponding client includes: pushing the message to be pushed to the client corresponding to the client ID appointed by the message to be pushed.
Specifically, referring to fig. 4, when the message to be pushed is a point-to-point message, the target client user 2 that sends the point-to-point message is parsed, the message pushing gateway obtains a socket long connection of user 2 in the point-to-point data structure of the message pushing gateway, and sends the "you just" message content of the point-to-point message to the user 2 client through the socket long connection.
According to an embodiment of the present invention, when the message to be pushed is an organization message, pushing the message to be pushed to a corresponding client includes: inquiring a client ID corresponding to the mechanism ID appointed by the message to be pushed from the mechanism data structure; and pushing the message to be pushed to the client corresponding to the queried client ID.
Specifically, referring to fig. 5, when the message to be pushed is an organization message, the organization message is parsed to obtain the sent target organization org1, and the message pushing gateway obtains, for example, socket long connections of userid1 and userid2 in its organization data structure, and sends "full-member fake" message contents of the organization message to clients of userid1 and userid2 in sequence to the socket long connections.
According to an embodiment of the present invention, when the message to be pushed is a subject message, pushing the message to be pushed to a corresponding client includes: inquiring a client ID corresponding to a topic ID appointed by a message to be pushed from a topic data structure; and pushing the message to be pushed to the client corresponding to the queried client ID.
Specifically, referring to fig. 6, when the message to be pushed is a subject message, the member message is parsed to obtain a sent subject as a payment notification, and the message pushing gateway queries client IDs of all clients subscribed to the subject of the payment notification in a subject data structure thereof (for example, two clients of useid 1 and useid 2 subscribe to the subject of the payment notification), and sequentially sends "money-spent" message contents of the subject message to the clients of useid 1 and useid 2 to a socket long connection of useid 1 and useid 2.
According to an embodiment of the invention, the number of message push gateways is one or more; each message push gateway is connected to a plurality of clients, one message push gateway for each client, as shown in fig. 7.
In this embodiment, when the whole member sends a message, the message sending end only generates one message to each message pushing gateway; the message pushing gateway records the online clients, the organization information of each online client and the subject information subscribed by each online client, so that whether the online clients are target clients of the message to be pushed is traversed, and if so, the message to be pushed is pushed to the clients. The message pushing gateway supports cluster deployment, can horizontally expand any number, as shown in fig. 7, expands the original 1 message pushing gateway into 3, the client login is only connected to one message pushing gateway, the first 1 message pushing gateway needs to push messages for 3000 clients, and each message pushing gateway only pushes messages for 1000 clients after expansion, so that the pressure of a single node is shared to a plurality of nodes, and the system is lightweight and efficient to operate. Taking 10 message pushing gateways as an example, when hundreds of thousands of clients are online, the online clients of each message pushing gateway are ten thousands of, so that the operation pressure of the message pushing gateway is greatly reduced, and the pushing efficiency and pushing stability are improved.
Fig. 8 is a block diagram of a distributed message pushing system according to an embodiment of the present invention. Referring to fig. 8, the distributed message pushing system 800 includes a receiving and registering module 810, a listening and parsing module 820, and a pushing module 830.
The receiving and registering module 810, for example, executes step S1 to receive registration information sent by the client, and register data structures corresponding to different message types for the client according to the registration information.
The monitoring and parsing module 820 performs, for example, step S2, for monitoring the message to be pushed from the message queue of the message sender, and parsing the message to be pushed to determine the message type.
The pushing module 830, for example, performs step S3, and is configured to push the message to be pushed to the corresponding client according to the data structure corresponding to the message type of the message to be pushed.
The distributed message pushing system 800 is configured to perform the distributed message pushing method in the embodiments shown in fig. 1-7 described above. For details not yet in this embodiment, please refer to the distributed message pushing method in the embodiment shown in fig. 1-7, which is not described herein.
Embodiments of the present disclosure also illustrate an electronic device, as shown in fig. 9, the electronic device 900 includes a processor 910, a readable storage medium 920. The electronic device 900 may perform the distributed message pushing method described above in fig. 1-7.
In particular, processor 910 can include, for example, a general purpose microprocessor, an instruction set processor, and/or an associated chipset and/or special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), or the like. Processor 910 may also include on-board memory for caching purposes. The processor 910 may be a single processing unit or a plurality of processing units for performing different actions in accordance with the method flows of the embodiments of the disclosure described with reference to fig. 1-7.
The readable storage medium 920 may be, for example, any medium that can contain, store, communicate, propagate, or transport instructions. For example, a readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. Specific examples of the readable storage medium include: magnetic storage devices such as magnetic tape or hard disk (HDD); optical storage devices such as compact discs (CD-ROMs); a memory, such as a Random Access Memory (RAM) or a flash memory; and/or a wired/wireless communication link.
The readable storage medium 920 may include a computer program 921, which computer program 921 may include code/computer-executable instructions that, when executed by the processor 910, cause the processor 910 to perform the method flow described above in connection with fig. 1-7, and any variations thereof.
The computer program 921 may be configured to have computer program code comprising, for example, computer program modules. For example, in an example embodiment, code in the computer program 921 may include one or more program modules, including 921A, modules 921B, … …, for example. It should be noted that the division and number of modules is not fixed, and that a person skilled in the art may use suitable program modules or combinations of program modules according to the actual situation, which when executed by the processor 910, enable the processor 910 to perform a method flow such as described above in connection with fig. 1-7, and any variations thereof.
The embodiment of the invention also provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor implements the distributed message pushing method described in fig. 1-7.
The distributed message pushing method, the system, the equipment and the medium provided by the embodiment of the invention can realize the following effects:
1. the message pushing gateway side is designed with data structures corresponding to different message types, the message sending end can only generate one message, and the message is only pushed to each online client through the message pushing gateway and the unique data structure, so that the occupation of mass memory of an operating system of the message sending end is avoided, the resource waste is avoided, and the high efficiency and stability of the message pushing are ensured;
2. by combining the message queues, the stable and efficient message pushing can be ensured, and the system is not collapsed by message storm;
3. when the client opens the application for the first time or wakes up the screen saver, reestablishing long connection between the message pushing gateway and the client, and ensuring that the message is pushed to the client in time on the premise of avoiding occupying excessive communication resources;
4. the message pushing gateway supports cluster deployment, capacity expansion can be realized in any number horizontally, client login is only connected to one message pushing gateway, pressure of a single node is shared to a plurality of nodes, and light and efficient operation of the system is ensured.
The foregoing is merely illustrative of the present invention, and the present invention is not limited thereto, and any changes or substitutions easily contemplated by those skilled in the art within the scope of the present invention should be included in the present invention. Therefore, the protection scope of the invention is subject to the protection scope of the claims.

Claims (10)

1. A distributed message pushing method for a message pushing gateway, wherein the message pushing gateway connects a message sending end and a plurality of clients, the method comprising:
step S1, receiving registration information sent by the client, and registering data structures corresponding to different message types for the client according to the registration information;
step S2, monitoring a message to be pushed from the message queue of the message sending end, and analyzing the message to be pushed to judge the message type;
step S3, pushing the message to be pushed to the corresponding client according to the data structure corresponding to the message type of the message to be pushed.
2. The distributed message pushing method of claim 1, wherein the registration information comprises: the system comprises a client ID, an organization ID and a theme ID, wherein the organization ID is the ID of an organization added by the client, and the theme ID is the ID of a theme subscribed by the client;
the data structure comprises: point-to-point data structures, organization data structures, and topic data structures.
3. The distributed message pushing method of claim 2, wherein the point-to-point data structure includes the client ID;
when the message to be pushed is a point-to-point message, pushing the message to be pushed to a corresponding client includes: pushing the message to be pushed to a client corresponding to the client ID appointed by the message to be pushed.
4. The distributed message pushing method of claim 2, wherein the organization data structure comprises: a mechanism ID of a mechanism, and a client ID of a client joining the mechanism;
when the message to be pushed is an organization message, pushing the message to be pushed to a corresponding client includes: inquiring a client ID corresponding to the mechanism ID appointed by the message to be pushed from the mechanism data structure; pushing the message to be pushed to the client corresponding to the queried client ID.
5. The distributed message pushing method of claim 2, wherein the topic data structure comprises: topic ID of a topic and client ID of a client subscribing to the topic;
when the message to be pushed is a subject message, pushing the message to be pushed to a corresponding client includes: inquiring a client ID corresponding to the topic ID appointed by the message to be pushed from the topic data structure; pushing the message to be pushed to the client corresponding to the queried client ID.
6. The distributed message pushing method of claim 1, wherein the message pushing gateway is in long connection with the client;
when the client first opens an application or wakes up a screen saver, if the long connection is in a disconnected state, the step S1 further includes: and reestablishing the long connection between the message push gateway and the client.
7. The distributed message pushing method according to claim 1, wherein the number of message pushing gateways is one or more; each message pushing gateway is connected with a plurality of clients, and each client is connected with one message pushing gateway.
8. A distributed message pushing system for a message pushing gateway, wherein the message pushing gateway connects a message sending end and a plurality of clients, the system comprising:
the receiving and registering module is used for receiving the registering information sent by the client and registering data structures corresponding to different message types for the client according to the registering information;
the monitoring and analyzing module is used for monitoring the message to be pushed from the message queue of the message sending end and analyzing the message to be pushed to judge the message type;
and the pushing module is used for pushing the message to be pushed to the corresponding client according to the data structure corresponding to the message type of the message to be pushed.
9. An electronic device, comprising:
a processor;
a memory storing a computer executable program that, when executed by the processor, causes the processor to perform the distributed message pushing method of any of claims 1-7.
10. A computer readable storage medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the distributed message pushing method according to any of claims 1-7.
CN202311027477.4A 2023-08-15 2023-08-15 Distributed message pushing method, system, equipment and medium Pending CN116886766A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202311027477.4A CN116886766A (en) 2023-08-15 2023-08-15 Distributed message pushing method, system, equipment and medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202311027477.4A CN116886766A (en) 2023-08-15 2023-08-15 Distributed message pushing method, system, equipment and medium

Publications (1)

Publication Number Publication Date
CN116886766A true CN116886766A (en) 2023-10-13

Family

ID=88270029

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202311027477.4A Pending CN116886766A (en) 2023-08-15 2023-08-15 Distributed message pushing method, system, equipment and medium

Country Status (1)

Country Link
CN (1) CN116886766A (en)

Similar Documents

Publication Publication Date Title
KR101971299B1 (en) Messaging for notification-based clients
US9578081B2 (en) System and method for providing an actively invalidated client-side network resource cache
WO2016177285A1 (en) Data pushing method and device
CN111711663A (en) Processing method and device for publishing and subscribing services and electronic equipment
US10110538B2 (en) Method and apparatus for message transmission
CN110113381B (en) Method and device for subscribing theme in block chain
US8738770B2 (en) Sending synchronous responses to requests from frontend applications
CN104811459A (en) Processing method, processing device and system for message services and message service system
RU2608469C2 (en) Method and apparatus for high performance low latency real time notification delivery
CN107404512B (en) Resource subscription method, resource subscription device and resource subscription system
CN112711635B (en) Method for cross-regional data consistency of distributed Internet of things equipment and service cluster
CN114025002A (en) MQTT information transmission method, system and communication equipment
CN111064626A (en) Configuration updating method, device, server and readable storage medium
CN106899605B (en) Communication method and device based on STOMP protocol
CN113612825B (en) Internet of things message middleware server cluster expansion method and system
CN103827830A (en) System and method for preventing single-point bottleneck in a transactional middleware machine environment
US20170048081A1 (en) Multi-ring reliable messaging system
US20060020708A1 (en) System and method for peer-to-peer communication
WO2023186154A1 (en) Data transmission system and method
US8755397B2 (en) Asynchronous communication in an unstable network
WO2017032110A1 (en) Application message processing system and method, and application device
CN116886766A (en) Distributed message pushing method, system, equipment and medium
CN110768818A (en) Network management method and device
US11979338B2 (en) System and method for cellular network data storage and forwarding
CN107911477B (en) Data communication method, device and system

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