CN107026917A - The method and system pushed for message - Google Patents
The method and system pushed for message Download PDFInfo
- Publication number
- CN107026917A CN107026917A CN201710455135.0A CN201710455135A CN107026917A CN 107026917 A CN107026917 A CN 107026917A CN 201710455135 A CN201710455135 A CN 201710455135A CN 107026917 A CN107026917 A CN 107026917A
- Authority
- CN
- China
- Prior art keywords
- topic
- client
- message
- information
- push message
- 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
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
-
- 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/12—Avoiding congestion; Recovering from congestion
- H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
-
- 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
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/562—Brokering proxy services
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
A kind of method and system pushed for message of disclosure.This method includes：Obtain the information for the destination client for treating PUSH message and push；According to the information of the destination client, treat that PUSH message is sent in the corresponding topic of the message-oriented middleware comprising multiple topic by described；It will treat that PUSH message is pushed to the destination client described in the corresponding topic, can be according to the information of destination client, from the corresponding topic of multiple topic message-oriented middleware, reduce and subscribe to the number of client that the broker processes and broker processes of the topic are required to look up, realize and equilibrium is carried out to load using the message-oriented middleware including multiple topic so that the method that the message provided in the embodiment of the present invention is pushed can apply to the peak traffic phase of PUSH message.
Description
Technical field
The present invention relates to computer science and technology field, in particular to a kind of method pushed for message and it is
System.
Background technology
With the development of internet, generating much needs the reality of the business of real time propelling movement message, such as page end message
When message, and some live type business.Existing message, which pushes mode, can not meet the push of multi-service amount message, so that
Cause message push delay or information push efficiency low, even result in systemic breakdown.
Accordingly, it would be desirable to a kind of new method and system pushed for message.
Above- mentioned information is only used for strengthening the understanding of the background to the present invention, therefore it disclosed in the background section
It can include not constituting the information to prior art known to persons of ordinary skill in the art.
The content of the invention
In view of this, the present invention provides a kind of method pushed for message and server, can utilize comprising multiple
Topic message-oriented middleware improves the performance that message is pushed.
First aspect according to embodiments of the present invention is used for the method that message is pushed there is provided a kind of, wherein, methods described bag
Include：Obtain the information for the destination client for treating PUSH message and push；According to the information of the destination client, treated described
PUSH message is sent in the corresponding topic of the message-oriented middleware comprising multiple topic；By the corresponding topic
In described treat that PUSH message is pushed to the destination client.
According to some embodiments, the information of the destination client includes：In device identification, group identification and topic mark
At least one.
According to some embodiments, when the information of the destination client is group identification, according to the destination client
Information, treat that PUSH message is sent in the corresponding topic of the message-oriented middleware comprising multiple topic by described, including：
According to the group identification, the device identification of the client in the group is found；According to the device identification of each client,
Get the topic corresponding with the device identification of each client；To treat that PUSH message is sent to described each by described
Corresponding topic.
According to some embodiments, when the information of the destination client identifies for topic, according to the destination client
Information, treat that PUSH message is sent in the corresponding topic of the message-oriented middleware comprising multiple topic by described, including：
Identified according to the topic, find the device identification for the client that have subscribed the topic；According to the equipment of each client
Mark, gets the topic corresponding with the device identification of each client；To treat that PUSH message is sent to described by described
Each corresponding topic.
According to some embodiments, according to the device identification of each client, the equipment with each client is got
The corresponding topic of mark, including：According to the device identification of each client, corresponding broker processes mark is found
Know；Broker processes and topic modulus standard are set；According to the broker process identification (PID)s and the modulus standard, obtain
The topic corresponding with the broker process identification (PID)s found.
According to some embodiments, it will treat that PUSH message is pushed to the target visitor described in the corresponding topic
Family end, including：According to the broker processes and topic modulus standard, find and have subscribed the corresponding topic's
Broker processes；According to the information of the target customer, connected from the broker processes with have subscribed the corresponding topic
Client in find destination client；It will treat that PUSH message is pushed to the mesh described in the corresponding topic
Mark client.
According to some embodiments, methods described also includes：By Nginx systems, set up between client and server
Link.
Second aspect according to embodiments of the present invention is used for the system that message is pushed there is provided a kind of, wherein, the system bag
Include：Acquisition module, the information for obtaining the destination client for treating PUSH message and push；Sending module, for according to institute
The information of destination client is stated, treats that PUSH message is sent to the corresponding of the message-oriented middleware comprising multiple topic by described
In topic；Pushing module, for will treat that PUSH message is pushed to the target customer described in the corresponding topic
End.
According to some embodiments, the information of the destination client includes：In device identification, group identification and topic mark
At least one.
According to some embodiments, when the information of the destination client is group identification, the sending module, including：
Searching unit, for according to the group identification, finding the device identification of the client in the group；
Acquiring unit, for the device identification according to each client, gets the equipment mark with each client
Sensible corresponding topic；
Transmitting element, for treating that PUSH message is sent to each corresponding topic by described.
In the embodiment of the present invention, by the information for obtaining the destination client for treating PUSH message and push；According to described
The information of destination client, treats that PUSH message is sent to the corresponding of the message-oriented middleware comprising multiple topic by described
In topic；It will treat that PUSH message is pushed to the destination client described in the corresponding topic, can be according to mesh
The information of client is marked, from the corresponding topic of multiple topic message-oriented middleware, reduces and subscribes to the topic's
The number for the client that broker processes and broker processes are required to look up, realizing to utilize includes multiple topic message
Middleware carries out balanced to load so that the method that the message provided in the embodiment of the present invention is pushed can apply to PUSH message
The peak traffic phase.
Brief description of the drawings
Its example embodiment is described in detail by referring to accompanying drawing, above and other target, feature and advantage of the invention will
Become more fully apparent.
Fig. 1 is a kind of flow chart of method pushed for message provided in an embodiment of the present invention.
Fig. 2 schematically shows the embodiment of the present invention and provides company between the first Nginx system and server and client
Connect the schematic diagram of relation.
Fig. 3 is a kind of structure chart of system pushed for message provided in an embodiment of the present invention.
Specific embodiment
Example embodiment is described more fully with referring now to accompanying drawing.However, example embodiment can be real in a variety of forms
Apply, and be not understood as limited to embodiment set forth herein；On the contrary, thesing embodiments are provided so that the present invention will be comprehensively and complete
It is whole, and the design of example embodiment is comprehensively conveyed into those skilled in the art.Identical reference is represented in figure
Same or similar part, thus repetition thereof will be omitted.
Implement in addition, described feature, structure or characteristic can be combined in any suitable manner one or more
In example.Embodiments of the invention are fully understood so as to provide there is provided many details in the following description.However,
It will be appreciated by persons skilled in the art that technical scheme can be put into practice without one or more in specific detail,
Or can be using other methods, constituent element, device, step etc..In other cases, it is not shown in detail or describes known side
Method, device, realization operate to avoid fuzzy each aspect of the present invention.
Block diagram shown in accompanying drawing is only functional entity, not necessarily must be corresponding with physically separate entity.
I.e., it is possible to realize these functional entitys using software form, or realized in one or more hardware modules or integrated circuit
These functional entitys, or realize in heterogeneous networks and/or processor device and/or microcontroller device these functional entitys.
Flow chart shown in accompanying drawing is merely illustrative, it is not necessary to including all contents and operation/step,
It is not required to perform by described order.For example, some operation/steps can also be decomposed, and some operation/steps can be closed
And or part merge, therefore the actual order performed is possible to be changed according to actual conditions.
Fig. 1 is a kind of flow chart of method pushed for message provided in an embodiment of the present invention.
As shown in figure 1, this method includes but is not limited to following steps：
S110, obtains the information for the destination client for treating PUSH message and push.
According to example embodiment, the information of destination client can be included in device identification, group identification, topic mark
It is at least one.
It should be noted that the either information of which kind of above-mentioned destination client, the number of destination client is at least
One.For example, the information of destination client can be the information of customer end A and customer end B.In another example, the letter of destination client
Breath can be group identification X, and at least one client is included wherein in X groups.In another example, the information of destination client can be
Topic identifies M, wherein, the client for subscribing to topic mark is at least one.
In the embodiment of the present invention, by Nginx systems, the link set up between client and server.
Client initiates websocket requests, and Nginx systems are received after the request, lua modules are called, to server
The currently available broker process lists of request, after the available broker process lists of server return are received, Nginx
The broker processes that system controls customer end can be connected.It is achieved thereby that by Nginx systems, setting up client and server
Between link, the load balancing of broker processes is realized using Nginx systems, thus improve broker processes processing effect
Rate.Fig. 2 schematically shows the embodiment of the present invention and provides annexation between the first Nginx system and server and client
Schematic diagram.
S120, according to the information of the destination client, treats that PUSH message is sent to disappearing comprising multiple topic by described
In the corresponding topic for ceasing middleware.
Message-oriented middleware can include but is not limited to：redis、kafka、MQ.With including multiple in the embodiment of the present invention
Exemplified by topic kafka, it will treat that PUSH message is sent to the corresponding topic of the message-oriented middleware comprising multiple topic
, can be simultaneously by this after being sent to the corresponding of kafka after PUSH message and the Information encapsulation of destination client when middle
In topic.
According to example embodiment, when the information of destination client is group identification, according to the group identification, it can search
To the device identification of the client in the corresponding group of the group identification.When the information of destination client identifies for topic, root
Identified according to the topic, the device identification that have subscribed the client that the topic identifies corresponding topic can be found.
, can be according to each visitor after the device identification for getting each client in topic mark or group identification
The device identification at family end, gets the topic corresponding with the device identification of each client, and then will treat that PUSH message is sent
To each corresponding topic.
Server can find corresponding broker processes according to the device identification of client.For example, client is connected
To after broker processes, broker processes can record the corresponding pass between the device identification of the client and broker process identification (PID)s
System, and saves it in redis, and server subscribes to the redis, thus get device identification and broker process identification (PID)s it
Between corresponding relation, and then the device identification of each client according to acquisition finds each client in the corresponding relation
The corresponding broker process identification (PID)s of device identification at end.
It should be noted that each broker processes can also record the letter such as IP address of connected each client
Breath.
Further, according to each broker process identification (PID)s, each broker processes can be found in kafka and are subscribed to
Topic.
It should be noted that server can set broker processes and topic modulus standard.By setting broker
Process and topic modulus standards, can obtain the corresponding relation between broker and topic.And then each equipment ought be got
Identify after corresponding broker process identification (PID)s, modulus is carried out to broker process identification (PID)s, the broker process identification (PID)s pair are got
The topic that the broker answered is subscribed to, so as to realize according to broker process identification (PID)s and modulus standard, obtains and finds
The corresponding topic of broker process identification (PID)s.
For example, when kafka includes 24 topic, broker number is 48, there is provided after a kind of modulus standard, it is right
Broker1 modulus, gets the topic1 of broker1 subscription, to broker48 modulus, gets broker48 subscription
Topic24, to broker27 modulus, gets the topic3 of broker27 subscription.
After the corresponding topic in kafka is got, it will treat that PUSH message is sent to kafka above-mentioned topic
In.
It should be noted that when the device identification of the client got is multiple, multiple equipment mark can be found
Know corresponding broker process identification (PID)s, and then can be found according to broker process identification (PID)s corresponding one or more
topic。
It should be noted that each client may be coupled to a broker process, and broker process can be with
Multiple client is connected to, therefore, according to the device identification of multiple client, the corresponding broker process identification (PID)s found
Number can be less than the number of client.And for including multiple topic kafka, a broker process can subscribe to
A few topic, therefore, the corresponding topic found according to multiple broker process identification (PID)s number can be less than
The number of broker process identification (PID)s.
In the embodiment of the present invention, broker processes are shunted using the message-oriented middleware comprising multiple topic so that
Each topic broker process load balancing is subscribed to, and then reduction is subsequently treating PUSH message using the push of broker processes
When the number of client searched, improve the performance and efficiency of message push so that what is provided in the embodiment of the present invention disappears
The method that breath is pushed can apply to the peak traffic phase of PUSH message.
It should be noted that server by above-mentioned after PUSH message is sent to message-oriented middleware, no longer this is waited to push
Message is handled, but enters to be about to using the message passing mechanism of the high efficient and reliable of message-oriented middleware to treat that PUSH message is pushed to
Client, not only increases the treatment effeciency of server end, and reduces the transmission delay of PUSH message.
S130, will treat that PUSH message is pushed to destination client in above-mentioned corresponding topic.
Kafka each topic can be subscribed to by least one broker process, when will treat that PUSH message is sent to kafka
In topic after, the broker processes for subscribing to the topic parse PUSH message for the treatment of in the topic, and the PUSH message is pushed away
It is sent to destination client.
Broker processes, can be according to setting when the PUSH message is pushed into destination client in S120
The modulus standard of broker processes and topic, searches the broker processes that have subscribed above-mentioned relative topic, and then according to mesh
The information of client is marked, target customer is found from the client of the broker processes connection with subscribing to the corresponding topic
End, will treat that PUSH message is pushed to the destination client described in the topic.
It should be noted that server will treat that PUSH message is pushed to the process of message-oriented middleware, and broker enters
Journey by message-oriented middleware treat PUSH message during being pushed to destination client, it is necessary to using identical modulus standard,
So as to ensure that broker processes can will treat that PUSH message is pushed to correct destination client.
If two process modulus standards are different, for example, with reference to the example in S120, it is assumed that broker processes are by message
Between in part treat that PUSH message is pushed to destination client during, to broker1 modulus, get broker1 subscription
Topic2, to broker48 modulus, gets the topic3 of broker48 subscription, to broker27 modulus, gets
The topic4 that broker27 is subscribed to.The broker process identification (PID)s then got are different from topic corresponding relation, it is assumed that server
It will treat that PUSH message is sent to topic2, then broker processes, which are found, have subscribed topic2 broker for broker1, and with
The device identification of destination client and may not be included in the client of broker1 connections.
It should be noted that broker processes are with finding the IP of destination client according to the device identification of destination client
The information such as location, so as to will treat that PUSH message is pushed to destination client according to these information.
In the embodiment of the present invention, by the information for obtaining the destination client for treating PUSH message and push；According to described
The information of destination client, treats that PUSH message is sent to the corresponding of the message-oriented middleware comprising multiple topic by described
In topic；It will treat that PUSH message is pushed to the destination client described in the corresponding topic, can be according to mesh
The information of client is marked, from the corresponding topic of multiple topic message-oriented middleware, reduces and subscribes to the topic's
The number for the client that broker processes and broker processes are required to look up, realizing to utilize includes multiple topic message
Middleware carries out balanced to load so that the method that the message provided in the embodiment of the present invention is pushed can apply to PUSH message
The peak traffic phase.
It will be clearly understood that the present disclosure describe how forming and use particular example, but the principle of the present invention is not limited to
Any details of these examples.On the contrary, the teaching based on present disclosure, these principles can be applied to many other
Embodiment.
With reference to specific embodiment, to the method that message is pushed that is used for of the information of destination client for group identification
It is described in detail.
Group identification and the corresponding relation of device identification can be pre-set.Adding for client initiation is received for example, working as
When entering the request of group, device identification and the corresponding relation of the group identification of the group of addition of the client are set.
For example, table 1 is a kind of device identification of client provided in an embodiment of the present invention and the corresponding relation of group identification
Table.
| Device identification | Group identification |
| A、B、C、D、E | X |
| A、B、C、D、F | Y |
Table 1
As shown in table 1, each client can be added and can included in multiple groups, a group in the embodiment of the present invention
At least one client.Alternatively, it is also possible to set a upper limit for the number of clients in group, for example, in a group
Number of clients is no more than 10.
When the information of destination client is group identification, the client in the corresponding group of the group identification can be got
The device identification at end, by taking table 1 as an example, when the information of destination client is X, can get device identification A, B, C, D, E.
Get after device identification, treat that PUSH message is sent to message-oriented middleware by above-mentioned according to the device identification.
In the embodiment of the present invention, each client can record the equipment mark of the client after broker processes are connected to
Know the corresponding relation between broker process identification (PID)s.It should be noted that broker processes can also record connected
The information such as the IP address of client.
For example, table 2 is the corresponding pass between a kind of device identification provided in an embodiment of the present invention and broker process identification (PID)s
It is table.
Table 2
As shown in table 2, customer end A, B, C are all connected to Broker1, and client D, E, G are all connected to Broker2.
According to device identification A, B, C, D, E is got in table 1, device identification A, B, C and Broker1 couple can be found
Should, device identification D, E are corresponding with Broker2.
, can be in the kafka topic ordered by broker be searched from registration center according to broker process identification (PID)s
Find the topic that the corresponding broker of the broker process identification (PID)s is subscribed to.It should be noted that herein can be according to setting
Modulus standard between broker and topic is obtained.
For example, table 3 is a kind of broker process marks of the topic provided in an embodiment of the present invention with subscribing to topic marks
The corresponding relation of knowledge.
| Broker process identification (PID)s | Topic is identified |
| 1、3 | Q |
| 2、4 | H |
Table 3
As shown in table 3, Broker1,3 corresponding topic Q, Broker2,4 corresponding topic H.Found according to table 2
Broker1 and Broker2, can find corresponding topic for Q and H.So as to by PUSH message be sent to kafka this two
In individual topic.
Further, according to above-mentioned identical modulus standard, can get have subscribed the two processes Broker (1,
3 and 2,4) process, and then according to the information of target customer, from the client that the broker (1,3 and 2,4) process is connected
Find destination client.It is respectively A, B, C that can find client identification corresponding with broker1 according to table 2, with
The corresponding client identifications of broker2 are respectively D, E, and client identification corresponding with broker3 is respectively G, with broker4 pairs
The client identification answered respectively F, and according to group identification and table 1, it may be determined that needs will treat that PUSH message is pushed to client
A, B, C, D and E are held, and then according to information such as the customer end A of record, B, C, D and E IP address, will treat that PUSH message is pushed to
These clients.
In the embodiment of the present invention, by the information for obtaining the destination client for treating PUSH message and push；According to described
The information of destination client, treats that PUSH message is sent to the corresponding of the message-oriented middleware comprising multiple topic by described
In topic；It will treat that PUSH message is pushed to the destination client described in the corresponding topic, can be according to mesh
The information of client is marked, from the corresponding topic of multiple topic message-oriented middleware, reduces and subscribes to the topic's
The number for the client that broker processes and broker processes are required to look up, realizing to utilize includes multiple topic message
Middleware carries out balanced to load so that the method that the message provided in the embodiment of the present invention is pushed can apply to PUSH message
The peak traffic phase.
It should be noted that the method for being used for message push that the information of destination client, which is topic, to be identified may refer to
State embodiment.The number of the client of suggestion subscription topic does not do the upper limit in the embodiment of the present invention.
Following is present system embodiment, can be used for performing the inventive method embodiment.Device is retouched below
In stating, with preceding method identical part, it will not be described in great detail.
Fig. 3 is a kind of structure chart of system pushed for message provided in an embodiment of the present invention, as shown in figure 3, described
System 300 includes：
Acquisition module 310, the information for obtaining the destination client for treating PUSH message and push；
Sending module 320, for the information according to the destination client, treats that PUSH message is sent to comprising many by described
In the corresponding topic of individual topic message-oriented middleware；
Pushing module 330, for will treat that PUSH message is pushed to the target visitor described in the corresponding topic
Family end.
According to some embodiments, the information of the destination client includes：In device identification, group identification and topic mark
At least one.
According to some embodiments, when the information of the destination client is group identification, the sending module 320, bag
Include：
Searching unit 322, for according to the group identification, finding the device identification of the client in the group；
Acquiring unit 324, for the device identification according to each client, gets the equipment with each client
The corresponding topic of mark；
Transmitting element 326, for treating that PUSH message is sent to each corresponding topic by described.
In the embodiment of the present invention, by the information for obtaining the destination client for treating PUSH message and push；According to described
The information of destination client, treats that PUSH message is sent to the corresponding of the message-oriented middleware comprising multiple topic by described
In topic；It will treat that PUSH message is pushed to the destination client described in the corresponding topic, can be according to mesh
The information of client is marked, from the corresponding topic of multiple topic message-oriented middleware, reduces and subscribes to the topic's
The number for the client that broker processes and broker processes are required to look up, realizing to utilize includes multiple topic message
Middleware carries out balanced to load so that the method that the message provided in the embodiment of the present invention is pushed can apply to PUSH message
The peak traffic phase.
The exemplary embodiment of the present invention is particularly shown and described above.It should be appreciated that the invention is not restricted to
Detailed construction described herein, set-up mode or implementation method；On the contrary, it is intended to cover included in appended claims
Various modifications and equivalence setting in spirit and scope.
Claims (10)
1. a kind of method pushed for message, it is characterised in that methods described includes：
Obtain the information for the destination client for treating PUSH message and push；
According to the information of the destination client, treat that PUSH message is sent in the message comprising multiple theme topic by described
Between part corresponding topic in；
It will treat that PUSH message is pushed to the destination client described in the corresponding topic.
2. the method as described in claim 1, it is characterised in that the information of the destination client includes：Device identification, group
At least one of mark and topic mark.
3. method as claimed in claim 2, it is characterised in that when the information of the destination client is group identification, root
According to the information of the destination client, treat that PUSH message is sent to the relative of the message-oriented middleware comprising multiple topic by described
In the topic answered, including：
According to the group identification, the device identification of the client in the group is found；
According to the device identification of each client, the topic corresponding with the device identification of each client is got；
Treat that PUSH message is sent to each corresponding topic by described.
4. method as claimed in claim 2, it is characterised in that when the information of the destination client identifies for topic, root
According to the information of the destination client, treat that PUSH message is sent to the relative of the message-oriented middleware comprising multiple topic by described
In the topic answered, including：
Identified according to the topic, find the device identification for the client that have subscribed the topic；
According to the device identification of each client, the topic corresponding with the device identification of each client is got；
Treat that PUSH message is sent to each corresponding topic by described.
5. the method as described in claim 3 or 4, it is characterised in that according to the device identification of each client, gets and institute
The corresponding topic of the device identification of each client is stated, including：
According to the device identification of each client, corresponding broker process identification (PID)s are found；
Broker processes and topic modulus standard are set；
According to the broker process identification (PID)s and the modulus standard, obtain corresponding with the broker process identification (PID)s found
topic。
6. method as claimed in claim 5, it is characterised in that PUSH message will be treated described in the corresponding topic
The destination client is pushed to, including：
According to the broker processes and topic modulus standard, the broker that have subscribed the corresponding topic is found
Process；
According to the information of the target customer, from have subscribed the client that the broker processes of the corresponding topic are connected
Destination client is found in end；
It will treat that PUSH message is pushed to the destination client described in the corresponding topic.
7. the method as described in claim 1, it is characterised in that methods described also includes：
By Nginx systems, the link set up between client and server.
8. a kind of system pushed for message, it is characterised in that the system includes：
Acquisition module, the information for obtaining the destination client for treating PUSH message and push；
Sending module, for the information according to the destination client, treats that PUSH message is sent to comprising multiple themes by described
In the corresponding topic of topic message-oriented middleware；
Pushing module, for will treat that PUSH message is pushed to the destination client described in the corresponding topic.
9. system as claimed in claim 8, it is characterised in that the information of the destination client includes：Device identification, group
At least one of mark and topic mark.
10. system as claimed in claim 8, it is characterised in that when the information of the destination client is group identification, institute
Sending module is stated, including：
Searching unit, for according to the group identification, finding the device identification of the client in the group；
Acquiring unit, for the device identification according to each client, gets the device identification phase with each client
Corresponding topic；
Transmitting element, for treating that PUSH message is sent to each corresponding topic by described.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710455135.0A CN107026917A (en) | 2017-06-16 | 2017-06-16 | The method and system pushed for message |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710455135.0A CN107026917A (en) | 2017-06-16 | 2017-06-16 | The method and system pushed for message |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107026917A true CN107026917A (en) | 2017-08-08 |
Family
ID=59531685
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710455135.0A Pending CN107026917A (en) | 2017-06-16 | 2017-06-16 | The method and system pushed for message |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107026917A (en) |
Cited By (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107819831A (en) * | 2017-10-23 | 2018-03-20 | 丹露成都网络技术有限公司 | A kind of universal message system based on metaq and mns |
| CN108279988A (en) * | 2018-01-25 | 2018-07-13 | 微梦创科网络科技（中国）有限公司 | A kind of message treatment method and system based on Lua scripts |
| CN108390950A (en) * | 2018-05-28 | 2018-08-10 | 中国建设银行股份有限公司 | A kind of information push method, device and equipment |
| CN108390881A (en) * | 2018-02-27 | 2018-08-10 | 北京焦点新干线信息技术有限公司 | A kind of distribution high concurrent real-time messages method for pushing and system |
| CN108388479A (en) * | 2018-02-10 | 2018-08-10 | 深圳壹账通智能科技有限公司 | Postpone information push method, device, computer equipment and storage medium |
| CN108769099A (en) * | 2018-04-02 | 2018-11-06 | 武汉斗鱼网络科技有限公司 | A kind of implementation method of the message duplicate removal of message-oriented middleware |
| CN110809050A (en) * | 2019-11-08 | 2020-02-18 | 智者四海（北京）技术有限公司 | Personalized push system and method based on streaming computing |
| CN110955857A (en) * | 2019-10-18 | 2020-04-03 | 苏宁云计算有限公司 | Service processing method and device for high concurrency environment |
| CN111770172A (en) * | 2020-06-29 | 2020-10-13 | 深圳前海微众银行股份有限公司 | Message middleware consumption proxy method, device, proxy server and storage medium |
| CN111866092A (en) * | 2020-06-30 | 2020-10-30 | 北京百度网讯科技有限公司 | Message transmission method and device, electronic equipment and readable storage medium |
| CN111901619A (en) * | 2020-07-23 | 2020-11-06 | 北京达佳互联信息技术有限公司 | Message pushing method and device |
| CN112073533A (en) * | 2020-09-16 | 2020-12-11 | 广州趣丸网络科技有限公司 | Real-time message pushing method and system |
| CN112565333A (en) * | 2020-11-03 | 2021-03-26 | 南方电网数字电网研究院有限公司 | Data transmission method based on kafka-connect |
| CN112751891A (en) * | 2019-10-30 | 2021-05-04 | 中移(苏州)软件技术有限公司 | Kafka-based message processing method, electronic device and storage medium |
| CN114827171A (en) * | 2022-03-23 | 2022-07-29 | 青岛中科曙光科技服务有限公司 | Information synchronization method and device, computer equipment and storage medium |
| CN114866597A (en) * | 2022-07-11 | 2022-08-05 | 广东睿江云计算股份有限公司 | Packet management client connection method and system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101668031A (en) * | 2008-09-02 | 2010-03-10 | 阿里巴巴集团控股有限公司 | Message processing method and message processing system |
| CN106230609A (en) * | 2016-07-29 | 2016-12-14 | 上海北信源信息技术有限公司 | One population message orientation method for pushing and device |
| CN106549988A (en) * | 2015-09-18 | 2017-03-29 | 腾讯科技（深圳）有限公司 | Add group method, apparatus and system |
| CN106603711A (en) * | 2016-12-30 | 2017-04-26 | 上海擎感智能科技有限公司 | Communication method and system and message server |
-
2017
- 2017-06-16 CN CN201710455135.0A patent/CN107026917A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101668031A (en) * | 2008-09-02 | 2010-03-10 | 阿里巴巴集团控股有限公司 | Message processing method and message processing system |
| CN106549988A (en) * | 2015-09-18 | 2017-03-29 | 腾讯科技（深圳）有限公司 | Add group method, apparatus and system |
| CN106230609A (en) * | 2016-07-29 | 2016-12-14 | 上海北信源信息技术有限公司 | One population message orientation method for pushing and device |
| CN106603711A (en) * | 2016-12-30 | 2017-04-26 | 上海擎感智能科技有限公司 | Communication method and system and message server |
Cited By (26)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107819831A (en) * | 2017-10-23 | 2018-03-20 | 丹露成都网络技术有限公司 | A kind of universal message system based on metaq and mns |
| CN107819831B (en) * | 2017-10-23 | 2020-09-01 | 丹露成都网络技术有限公司 | Metaq and mns-based universal message system |
| CN108279988A (en) * | 2018-01-25 | 2018-07-13 | 微梦创科网络科技（中国）有限公司 | A kind of message treatment method and system based on Lua scripts |
| CN108279988B (en) * | 2018-01-25 | 2021-07-23 | 微梦创科网络科技（中国）有限公司 | Message processing method and system based on Lua script language |
| CN108388479B (en) * | 2018-02-10 | 2021-09-24 | 深圳壹账通智能科技有限公司 | Delayed message pushing method and device, computer equipment and storage medium |
| CN108388479A (en) * | 2018-02-10 | 2018-08-10 | 深圳壹账通智能科技有限公司 | Postpone information push method, device, computer equipment and storage medium |
| CN108390881A (en) * | 2018-02-27 | 2018-08-10 | 北京焦点新干线信息技术有限公司 | A kind of distribution high concurrent real-time messages method for pushing and system |
| CN108390881B (en) * | 2018-02-27 | 2021-06-15 | 北京焦点新干线信息技术有限公司 | Distributed high-concurrency real-time message pushing method and system |
| CN108769099A (en) * | 2018-04-02 | 2018-11-06 | 武汉斗鱼网络科技有限公司 | A kind of implementation method of the message duplicate removal of message-oriented middleware |
| CN108769099B (en) * | 2018-04-02 | 2021-09-07 | 武汉斗鱼网络科技有限公司 | Message de-duplication realization method of message middleware |
| CN108390950A (en) * | 2018-05-28 | 2018-08-10 | 中国建设银行股份有限公司 | A kind of information push method, device and equipment |
| CN110955857A (en) * | 2019-10-18 | 2020-04-03 | 苏宁云计算有限公司 | Service processing method and device for high concurrency environment |
| CN112751891A (en) * | 2019-10-30 | 2021-05-04 | 中移(苏州)软件技术有限公司 | Kafka-based message processing method, electronic device and storage medium |
| CN110809050A (en) * | 2019-11-08 | 2020-02-18 | 智者四海（北京）技术有限公司 | Personalized push system and method based on streaming computing |
| CN110809050B (en) * | 2019-11-08 | 2022-11-29 | 智者四海（北京）技术有限公司 | Personalized pushing system and method based on streaming computing |
| CN111770172A (en) * | 2020-06-29 | 2020-10-13 | 深圳前海微众银行股份有限公司 | Message middleware consumption proxy method, device, proxy server and storage medium |
| CN111770172B (en) * | 2020-06-29 | 2024-08-23 | 深圳前海微众银行股份有限公司 | Message middleware consumption proxy method, device, proxy server and storage medium |
| CN111866092A (en) * | 2020-06-30 | 2020-10-30 | 北京百度网讯科技有限公司 | Message transmission method and device, electronic equipment and readable storage medium |
| CN111866092B (en) * | 2020-06-30 | 2022-06-28 | 北京百度网讯科技有限公司 | Message transmission method and device, electronic equipment and readable storage medium |
| CN111901619A (en) * | 2020-07-23 | 2020-11-06 | 北京达佳互联信息技术有限公司 | Message pushing method and device |
| CN111901619B (en) * | 2020-07-23 | 2023-10-31 | 北京达佳互联信息技术有限公司 | Message pushing method and device |
| CN112073533A (en) * | 2020-09-16 | 2020-12-11 | 广州趣丸网络科技有限公司 | Real-time message pushing method and system |
| CN112565333A (en) * | 2020-11-03 | 2021-03-26 | 南方电网数字电网研究院有限公司 | Data transmission method based on kafka-connect |
| CN114827171A (en) * | 2022-03-23 | 2022-07-29 | 青岛中科曙光科技服务有限公司 | Information synchronization method and device, computer equipment and storage medium |
| CN114827171B (en) * | 2022-03-23 | 2023-12-15 | 青岛中科曙光科技服务有限公司 | Information synchronization method, apparatus, computer device and storage medium |
| CN114866597A (en) * | 2022-07-11 | 2022-08-05 | 广东睿江云计算股份有限公司 | Packet management client connection method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107026917A (en) | The method and system pushed for message | |
| US7603474B2 (en) | Efficient endpoint matching using a header-to-bit conversion table | |
| CN1158615C (en) | Load balancing method and equipment for convective medium server | |
| US7949704B2 (en) | Administration of a broker-based publish/subscribe messaging system | |
| CN106850782A (en) | For the method and system of log processing | |
| US7885284B2 (en) | Message-based communications | |
| CN102377640B (en) | Message processing apparatus, message processing method and preprocessor | |
| US8621078B1 (en) | Certificate selection for virtual host servers | |
| CN102316121A (en) | Filtering matching preprocessing method supporting dynamic extended frame head and device | |
| CN109474718A (en) | Domain name analytic method and device | |
| CN105227595A (en) | A kind of message method and equipment | |
| CN102523196B (en) | Information identification method, device and system | |
| CN106657206A (en) | Virtual desktop infrastructure web video redirection method | |
| CN107959672A (en) | A kind of transfer method of multicasting based on Darwin's streaming media server | |
| CN101282362B (en) | Method and apparatus for detecting depth packet | |
| CN105245588A (en) | Separation processing method of web service port | |
| EP2090072A2 (en) | Method and apparatus for improving sip parse performance | |
| CN111600929B (en) | Transmission line detection method, routing strategy generation method and proxy server | |
| CN110768911A (en) | Efficient flow guiding method, device, equipment, system and storage medium | |
| CN105025042B (en) | A kind of method and system of determining data information, proxy server | |
| CN115695512A (en) | Data subscription method, system, equipment and storage medium based on micro-service architecture | |
| JP2017123522A (en) | Communication device, control device, communication system and communication method | |
| CN105450515A (en) | General IPv4/IPv6 data translation gateway for application layer protocols and method | |
| US20140351376A1 (en) | Content distribution method, system and server | |
| CN105991373A (en) | Application protocol identification method and application protocol identification device |
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 | ||
| WD01 | Invention patent application deemed withdrawn after publication | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20170808 |