CN102377685A - Subscription message sending system and subscription message sending method - Google Patents
Subscription message sending system and subscription message sending method Download PDFInfo
- Publication number
- CN102377685A CN102377685A CN2010102520835A CN201010252083A CN102377685A CN 102377685 A CN102377685 A CN 102377685A CN 2010102520835 A CN2010102520835 A CN 2010102520835A CN 201010252083 A CN201010252083 A CN 201010252083A CN 102377685 A CN102377685 A CN 102377685A
- Authority
- CN
- China
- Prior art keywords
- message
- address information
- oriented middleware
- server
- target address
- 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.)
- Granted
Links
Images
Landscapes
- Computer And Data Communications (AREA)
Abstract
The invention discloses a subscription message sending system and a subscription message sending method. A main technical scheme is as follows: a first message middleware server receives a subscription message and corresponding object address information sent by a message publish server, and sends the subscription message to a subscriber terminal corresponding to the object address information, when sending the subscription message is failed, and the object address information corresponding to the subscription message is sent to a database server which is used for storing the subscription message which is failed in sending and the corresponding object address information; a second message middleware server acquires the subscription message and the corresponding object address information stored in the database server, and sends the subscription message to the subscriber terminal corresponding to the object address information. According to the technical scheme, the subscription message which is failed in sending will not lead sending retardation of a subscription message which newly arrives at the first message middleware server.
Description
Technical field
The present invention relates to the Message Processing technical field, relate in particular to a kind of transmitting system of subscribe message and the sending method of subscribe message.
Background technology
In the message subscribing system; The issue of subscribe message generally all realizes based on the message-oriented middleware server; Be that the message publisher server sends to the message-oriented middleware server with subscribe message, this subscribe message be published to each message subscribing person terminal by this message-oriented middleware server.
In the practical application, in order to satisfy the delivery demand of numerous subscribe message, generally dispose many message-oriented middleware servers in the message subscribing system, each message-oriented middleware server is all born the task of delivering different subscribe message to different subscribers terminal.The conventional message ordering system is as shown in Figure 1, and this message subscribing system comprises message publisher server 101, message-oriented middleware server 102 (possibly be many, Fig. 1 only shows 2) and subscriber terminal 103 (maybe be for a plurality of, Fig. 1 only shows 4).Based on message subscribing system shown in Figure 1, realize the process that subscribe message is sent, as shown in Figure 2, comprise the steps:
After step 202, message-oriented middleware server 102 receive subscribe message, preserve this subscribe message, and this subscribe message is added message send queue;
This subscribe message that step 205, deletion are preserved so far, finishes the transmission flow of current subscribe message.
According to above flow process, in the conventional message ordering system, message-oriented middleware server 102 can be deleted this subscribe message after subscribe message is sent successfully, to reduce taking storage resources in the message middleware server 102; Message-oriented middleware server 102 is after subscribe message is sent failure; Need resend this subscribe message; Be about to wait in this subscribe message adding message send queue resend that in order to realize this purpose, message-oriented middleware server 102 needs to continue to preserve this subscribe message.Generally speaking, the subscribe message that the message-oriented middleware server is responsible for sending is very many, especially in large-scale distributed environment; The subscribe message of sending is a lot, and every day, subscribe message will send to a lot of subscribers terminal, and in the practical application; Because the factors such as disposal ability at network state, subscriber terminal; Be difficult to guarantee that the message-oriented middleware server sends the success rate of subscribe message, therefore in the conventional message ordering system, may have following problem:
Because it is according to this message send queue that the message-oriented middleware server sends subscribe message; Therefore; The subscribe message of sending failure is joined in the message send queue, may influence the transmission of the subscribe message in the follow-up arrival message-oriented middleware server, make new subscribe message can not send to the subscriber terminal in time; Thereby prolong the transmitting time of new subscribe message, especially can produce very big influence the subscribe message that has real-time to require.Therefore, in the conventional message ordering system, exist owing to the subscribe message of sending failure adds message send queue to resend the sluggish problem of subscribe message transmission that causes newly to arrive the message-oriented middleware server.
Summary of the invention
In view of this; The application embodiment provides a kind of transmitting system of subscribe message and the sending method of subscribe message, is used for solving prior art and resends the sluggish problem of subscribe message transmission that causes newly arriving the message-oriented middleware server owing to the subscribe message of sending failure adds message send queue.
The application embodiment realizes through following technical scheme:
According to the aspect of the application embodiment, a kind of transmitting system of subscribe message is provided, comprise the first message-oriented middleware server, database server and the second message-oriented middleware server; Wherein:
The said first message-oriented middleware server; After being used to receive subscribe message that the message publisher server sends and corresponding target address information; Said subscribe message is sent at subscriber terminal to corresponding with said target address information; And after sending said subscribe message failure, said subscribe message and corresponding target address information are sent to said database server;
Said database server is used to preserve subscribe message and the corresponding target address information that the said first message-oriented middleware server sends;
The said second message-oriented middleware server is used for obtaining subscribe message and the corresponding target address information that said database server is preserved, and sends said subscribe message to the subscriber terminal corresponding with said target address information.
According to another aspect of the application embodiment, a kind of transmitting system of subscribe message also is provided, comprise the first message-oriented middleware server and the second message-oriented middleware server; Wherein:
The said first message-oriented middleware server; After being used to receive subscribe message that the message publisher server sends and corresponding target address information; Said subscribe message is sent at subscriber terminal to corresponding with said target address information; And after sending said subscribe message failure, said subscribe message and corresponding target address information are sent to the said second message-oriented middleware server;
The said second message-oriented middleware server is used for subscribe message and corresponding target address information according to said first message-oriented middleware server transmission, and sends said subscribe message to the subscriber terminal corresponding with said target address information.
According to another aspect of the application embodiment, a kind of sending method of subscribe message also is provided, comprising:
Behind subscribe message that first message-oriented middleware server reception message publisher server sends and the corresponding target address information; Said subscribe message is sent at subscriber terminal to corresponding with said target address information; And after sending said subscribe message failure, said subscribe message and corresponding target address information are sent to the database server that is used to preserve the subscribe message of sending failure and corresponding target address information;
The second message-oriented middleware server obtains subscribe message and the corresponding target address information of preserving in the said database server, and sends said subscribe message to the subscriber terminal corresponding with said target address information.
According to another aspect of the application embodiment, a kind of sending method of subscribe message also is provided, comprising:
Behind subscribe message that first message-oriented middleware server reception message publisher server sends and the corresponding target address information; Said subscribe message is sent at subscriber terminal to corresponding with said target address information; And after sending said subscribe message failure, said subscribe message and corresponding target address information are sent to the second message-oriented middleware server;
The said second message-oriented middleware server sends said subscribe message according to subscribe message and corresponding target address information that the said first message-oriented middleware server sends to the subscriber terminal corresponding with said target address information.
Above-mentioned at least one technical scheme that provides through the application embodiment; The first message-oriented middleware server is after sending said subscribe message failure; This subscribe message and corresponding target address information are sent to the database server or the second message-oriented middleware server; This second message-oriented middleware server sends said subscribe message according to subscribe message and corresponding target address information or subscribe message of from database server, obtaining and corresponding target address information that the first message-oriented middleware server sends to the subscriber terminal corresponding with this target address information.According to this technical scheme; The first message-oriented middleware server is after sending the subscribe message failure; The subscribe message of this transmission failure is responsible for resending by the second message-oriented middleware server; Compared with prior art, the subscribe message of this transmission failure can not cause newly arriving the transmission sluggishness of the subscribe message of the first message-oriented middleware server.
The application's further feature and advantage will be set forth in specification subsequently, and, partly from specification, become obvious, perhaps understand through implementing the application.The application's purpose can realize through the structure that in the specification of being write, claims and accompanying drawing, is particularly pointed out and obtain with other advantages.
Description of drawings
Accompanying drawing is used to provide the further understanding to the application, and constitutes the part of specification, is used to explain the application with the application embodiment, does not constitute the restriction to the application.In the accompanying drawings:
Fig. 1 is a message subscribing system schematic of the prior art;
Fig. 2 realizes the flow chart that subscribe message is sent in the prior art;
The transmitting system sketch map of the subscribe message that Fig. 3 provides for the application embodiment one;
The transmitting system sketch map of the subscribe message that Fig. 4 provides for the application embodiment two;
The transmitting system sketch map of the subscribe message that Fig. 5 provides for the application embodiment three;
The sending method flow chart of the subscribe message that Fig. 6 provides for the application embodiment four;
The sending method flow chart of the subscribe message that Fig. 7 provides for the application embodiment five;
The sending method flow chart of the subscribe message that Fig. 8 provides for the application embodiment six.
Embodiment
Owing to resending the subscribe message that causes newly arriving the message-oriented middleware server, the subscribe message adding message send queue that sends failure sends the implementation of sluggish problem in order to provide to solve in the prior art; The application embodiment provides a kind of transmitting system of subscribe message and the sending method of subscribe message; This technical scheme can be applied to the process that subscribe message is sent; Both can be implemented as a kind of system, also can be implemented as a kind of method.Describe below in conjunction with the preferred embodiment of Figure of description, should be appreciated that preferred embodiment described herein only is used for explanation and explains the application, and be not used in qualification the application the application.And under the situation of not conflicting, embodiment and the characteristic among the embodiment among the application can make up each other.
Embodiment one
The application embodiment one provides a kind of transmitting system of subscribe message, and is as shown in Figure 3, and the transmitting system of this subscribe message comprises:
The first message-oriented middleware server 301 (possibly be many, shown in the figure two as an example), database server 302 and the second message-oriented middleware server 303 (possibly be many, shown in the figure two as an example);
Wherein:
The first message-oriented middleware server 301; After being used to receive subscribe message that the message publisher server sends and corresponding target address information; Send subscribe message to the subscriber terminal corresponding with this target address information; And after sending this subscribe message failure, this subscribe message and corresponding target address information are sent to database server 302;
The second message-oriented middleware server 303 is used for obtaining subscribe message and the corresponding target address information that database server 302 is preserved, and sends subscribe message to the subscriber terminal corresponding with this target address information.
Particularly; The first message-oriented middleware server 301; Specifically behind the target address information of subscribe message that receives the transmission of message publisher server and correspondence; This subscribe message and corresponding target address information are added message send queue, and after sending this subscribe message success, this subscribe message in the deletion message send queue and corresponding target address information.
Particularly, the second message-oriented middleware server 303 after sending the subscribe message success, also is used for sending successful information to database server 302 feedbacks;
Correspondingly, this database server 302 also is used for after the transmission successful information that receives the second message-oriented middleware server, 303 feedbacks, subscribe message that deletion is preserved and corresponding target address information.
Particularly; The second message-oriented middleware server 303; After specifically in mode specified data storehouse server 302, having preserved the subscribe message that satisfies self processing requirements and corresponding target address information, obtain subscribe message and corresponding target address information that this satisfies self processing requirements through poll.Particularly; Purpose for the treating capacity that reaches the subscribe message that balanced each 303 pairs of needs of the second message-oriented middleware server resend; Can set processing requirements for each second message-oriented middleware server 303, the second promptly different message-oriented middleware servers 303 is responsible for handling the subscribe message of different transmission failures.The second message-oriented middleware server 303 is through the mode Query Database server 302 of poll; If confirm to have preserved in this database server 302 when requiring the subscribe message of coupling, then obtain this subscribe message and corresponding target address information that satisfies self processing requirements and handle with self corresponding processing.Wherein, can set flexibly according to actual needs to the processing requirements that the second message-oriented middleware server 303 is set, for example:
The second message-oriented middleware server, 303 corresponding processing require: the subscribe message that the needs of preserving in the database server 302 resend is from setting the first message-oriented middleware server 301; Promptly set up the corresponding relation of the second message-oriented middleware server 303 and the first message-oriented middleware server 301, the second message-oriented middleware server 303 is responsible for resending the subscribe message that the first message-oriented middleware server 301 corresponding with it sends failure.In the practical application; A plurality of second message-oriented middleware servers 303 can corresponding one first message-oriented middleware server 301; Perhaps one second message-oriented middleware server 303 can corresponding a plurality of first message-oriented middleware servers 301, and actual subscribe message transmission situation is dynamically adjusted in the concrete viewing system.
The second message-oriented middleware server, 303 corresponding processing require: the corresponding setting identification of the subscribe message that the needs of preserving in the database server 302 resend; Promptly set up the corresponding relation of the second message-oriented middleware server 303 and sign, the second message-oriented middleware server 303 be responsible for resending through with the subscribe message of its corresponding identification mark.In the practical application, the subscribe message that database server 302 can need resend for each bar is added sign, and this sign is used to indicate this subscribe message to be assigned to which second message-oriented middleware server 303 to resend.
In the practical application, processing requirements can be provided with flexibly, repeats no more here.Through this embodiment, avoided a plurality of second message-oriented middleware servers 303 to repeat to send same subscribe message on the one hand; On the other hand; The traffic volume of subscribe message in can balanced each second message-oriented middleware server 303; It is too much to avoid occurring in the second message-oriented middleware server 303 some subscribe message quantity to be sent, and perhaps some is in the problem of idle state in the second message-oriented middleware server 303.
In the transmitting system of subscribe message shown in Figure 3; The quantity of the first message-oriented middleware server 301 can dynamically be adjusted according to the quantity of the subscribe message of message publisher server transmission in the unit interval; For example; When the quantity of the subscribe message that the message publisher server sends in certain period surpasses first setting threshold; Can increase the quantity of the first message-oriented middleware server 301 in the transmitting system of subscribe message,, alleviate the burden that the single first message-oriented middleware server 301 sends subscribe message to improve the promptness that subscribe message is sent.When the quantity of the subscribe message that the message publisher server sends in certain period is lower than second setting threshold; Can reduce the quantity of the first message-oriented middleware server 301 in the transmitting system of subscribe message; To avoid the idle of server resource, improve the utilance of server resource.Here, the size of first setting threshold and second setting threshold can be according to confirming as the quantity N1 of the quantity M1 of the first message-oriented middleware server 301 of pre-treatment subscribe message and the subscribe message that can handle in each 301 unit interval of the first message-oriented middleware server in the system.For example this first setting threshold can equal M1*N1 or be slightly larger than M1*N1 or be slightly less than M1*N1; This second setting threshold can equal (M1-1) * N1 or be slightly larger than (M1-1) * N1 or be slightly less than (M1-1) * N1.If the quantity of the subscribe message that the message publisher server sends in the unit interval greater than first setting threshold, then increases the quantity of the first message-oriented middleware server 301 of handling subscribe message; If the quantity of the subscribe message that the message publisher server sends in the unit interval less than this second setting threshold, then reduces the quantity of the second message-oriented middleware server 303 of handling subscribe message.Be to be understood that; Value for first setting threshold and second setting threshold is merely giving an example of embodiment of the present invention preferred embodiment here; In the practical application; This first setting threshold and second setting threshold can be provided with flexibly, as long as the subscribe message that the message publisher server sends in can guarantor unit's time can access timely processing, and can not cause subscribe message to overstock or the first message-oriented middleware server, 301 resources are got final product by a large amount of wastes.
In the transmitting system of subscribe message shown in Figure 3, the quantity of the second message-oriented middleware server 303 can dynamically be adjusted according to the quantity of the subscribe message of preserving in the database server in the unit interval 302 (i.e. the first message-oriented middleware server 301 send failure and not by the quantity of the subscribe message of the second message-oriented middleware server, 303 transmissions).For example; When the quantity of the subscribe message of in the unit interval, preserving in the database server 302 surpasses the 3rd setting threshold; Can increase the quantity of the second message-oriented middleware server 303 in the transmitting system of subscribe message; To improve the efficient that the subscribe message of sending failure is sent once more, alleviate the single second message-oriented middleware server 303 and send the burden of piling up subscribe message.When the quantity of the subscribe message of in database server 302, preserving is lower than the 4th setting threshold; Can reduce the quantity of the second message-oriented middleware server 303 in the transmitting system of subscribe message; To avoid the idle of server resource, improve the utilance of server resource.
Here, the size of the 3rd setting threshold and the 4th setting threshold can be according to confirming as the quantity N2 of the quantity M2 of the second message-oriented middleware server 303 of pre-treatment subscribe message and the subscribe message that can handle in each 303 unit interval of the second message-oriented middleware server in the system.For example the 3rd setting threshold can equal M2*N2 or be slightly larger than M2*N2 or be slightly less than M2*N2; The 4th setting threshold can equal (M2-1) * N2 or be slightly larger than (M2-1) * N2 or be slightly less than (M2-1) * N2.If the quantity of the subscribe message that the message publisher server sends in the unit interval greater than the 3rd setting threshold, then increases the quantity of the second message-oriented middleware server 303 of handling subscribe message; If the quantity of the subscribe message that the message publisher server sends in the unit interval less than the 4th setting threshold, then reduces the quantity of the second message-oriented middleware server 303 of handling subscribe message.Be to be understood that; Value for the 3rd setting threshold and the 3rd setting threshold is merely giving an example of embodiment of the present invention preferred embodiment here; In the practical application; The 3rd setting threshold and the 4th setting threshold can be provided with flexibly, as long as the subscribe message that the message publisher server sends in can guarantor unit's time can access timely processing, and can not cause subscribe message to overstock or the second message-oriented middleware server, 303 resources are got final product by a large amount of wastes.
Embodiment two
The application embodiment two provides a kind of transmitting system of subscribe message, and is as shown in Figure 4, and the transmitting system of this subscribe message also further comprises monitoring server 304 on the basis of embodiment one; Particularly, this monitoring server 304 is used for:
Subscribe message quantity to preserving in the database server in the unit interval 302 is monitored;
When the first message-oriented middleware server 301 that in monitoring the transmitting system of this quantity greater than the 5th setting threshold and this subscribe message, comprises was many, at least one the first message-oriented middleware server 301 in many first message-oriented middleware servers 301 sent the indication of first load balancing; Correspondingly; Receive the first message-oriented middleware server 301 of first load balancing indication; Specifically after receiving the indication of first load balancing; Stop to receive subscribe message and the corresponding target address information that the message publisher server sends, and obtain subscribe message and the corresponding target address information of preserving in the database server 302, send this subscribe message to the subscriber terminal corresponding with this target address information; Here, the concrete setting up procedure of the 5th setting threshold and the concrete setting up procedure of above-mentioned the 3rd setting threshold are similar, repeat no more here.Among this embodiment; When the second message-oriented middleware server 303 that in system, comprises is not enough to the subscribe message of preservation in the process database server 302; Need to increase the quantity of the second message-oriented middleware server 303; Specifically, realize through the mode that converts at least one in the system first message-oriented middleware server 301 into second message-oriented middleware server 303 in order not increase extra server resource;
When the second message-oriented middleware server 303 that in monitoring the transmitting system of this quantity less than the 6th setting threshold and this subscribe message, comprises was many, at least one the second message-oriented middleware server 303 in many second message-oriented middleware servers 303 sent the indication of second load balancing; Correspondingly; The second message-oriented middleware server 303 that receives the indication of second load balancing is after receiving the indication of second load balancing; Stop to obtain subscribe message and the corresponding target address information preserved in the database server 302; And the subscribe message and the corresponding target address information of the transmission of reception message publisher server; Send subscribe message to the subscriber terminal corresponding, and after sending this subscribe message failure, this subscribe message and corresponding target address information are sent to database server 302 with this target address information.Here; The concrete setting up procedure of the 6th setting threshold and the concrete setting up procedure of above-mentioned the 4th setting threshold are similar; Repeat no more here; Among this embodiment; In the time of possibly occurring idle situation during subscribe message that the second message-oriented middleware server 303 that in system, comprises is preserved in process database server 302, need to reduce the quantity of this second message-oriented middleware server 303, and realize through the mode that converts at least one in the system second message-oriented middleware server 303 into first message-oriented middleware server 301.
The monitoring server 304 that comprises in the transmitting system of the subscribe message that provides through this embodiment; Can be on the basis that does not increase new server resource; The dynamic adjustment of first message-oriented middleware server 301 that comprises in the transmitting system of realization to subscribe message and the second message-oriented middleware server, 303 quantity; To reach the equilibrium of internal system server resource; Improve the transmitting efficiency of the subscribe message of 301 pairs of message publisher servers transmissions of the first message-oriented middleware server, and improve the transmitting efficiency that 303 pairs first message-oriented middleware servers of the second message-oriented middleware server 301 send the subscribe message of failure.
Apparently; This embodiment two can combine with embodiment one; Realize the mutual conversion between the first message-oriented middleware server 301 and the second message-oriented middleware server 303, and the dynamic adjustment of the quantity of the quantity of the first message-oriented middleware server 301 and the second message-oriented middleware server 303.
Embodiment three
The application embodiment three provides a kind of transmitting system of subscribe message, and is as shown in Figure 5, and the transmitting system of this subscribe message comprises:
The first message-oriented middleware server 501 (possibly be many, shown in the figure two as an example) and the second message-oriented middleware server 502 (possibly be many, shown in the figure two as an example);
Wherein:
The first message-oriented middleware server 501; After being used to receive subscribe message that the message publisher server sends and corresponding target address information; Send subscribe message to the subscriber terminal corresponding with this target address information; And after sending this subscribe message failure, this subscribe message and corresponding target address information are sent to the second message-oriented middleware server 502;
The second message-oriented middleware server 502 is used for subscribe message and corresponding target address information according to 501 transmissions of the first message-oriented middleware server, and sends said subscribe message to the subscriber terminal corresponding with this target address information.
In the transmitting system of subscribe message shown in Figure 5, can set up the corresponding relation between the first message-oriented middleware server 501 and the second message-oriented middleware server 502 in advance.According to this corresponding relation; The first message-oriented middleware server 501 is after sending the subscribe message failure; Can the subscribe message and the corresponding target address information of this transmission failure be sent to the second message-oriented middleware server 502 corresponding with it, this second message-oriented middleware server 502 is responsible for sending once more this subscribe message.
In the transmitting system of subscribe message shown in Figure 5, also can in each first message-oriented middleware server 501, preserve each the second message-oriented middleware server, 502 corresponding address information list.According to this address information tabulation; The first message-oriented middleware server 501 is after sending the subscribe message failure; Can select the second message-oriented middleware server 502 according to this tabulation; And the subscribe message and the corresponding target address information that will send failure are sent to the second message-oriented middleware server of selecting 502, these second message-oriented middleware server, 502 responsible these subscribe message of sending once more.
Embodiment four
The transmitting system of the subscribe message that provides corresponding to the foregoing description one, the application embodiment four provides a kind of method of subscribe message, and is as shown in Figure 6, and this method comprises the steps:
Step 601, the first message-oriented middleware server 301 receive subscribe message and the corresponding target address information that the message publisher server sends;
In the step 605 of flow process shown in Figure 6; Whether the second message-oriented middleware server 303 has the subscribe message that needs transmission in the mode specified data storehouse server 302 through poll in advance; If confirm the result for being, then obtain the subscribe message of preserving in this database server 302 and the target address information of correspondence.
Further; Under the second message-oriented middleware server 303 is a plurality of situation; Repeat to send same subscribe message for fear of a plurality of second message-oriented middleware servers 303; Can set processing requirements for the second message-oriented middleware server 303, the second message-oriented middleware server 303 can require polling data storehouse server 302 through self corresponding processing, for example:
Subscribe message by database server 302 need resend for each bar is added sign, and this sign is used to indicate this subscribe message to be assigned to which second message-oriented middleware server 303 to resend; Alternatively, also can be with notifying each second message-oriented middleware server 303 with each the second message-oriented middleware server, 303 corresponding identification; Subscribe message in the second message-oriented middleware server, the 303 periodic polls database servers 302; If preserved the subscribe message corresponding in the specified data storehouse server 302, then obtain subscribe message and the corresponding target address information preserved in this database server 302 and carry out handled with the sign of distributing to self.Through this mode; Avoided a plurality of second message-oriented middleware servers 303 to repeat to send same subscribe message on the one hand; On the other hand; The traffic volume of subscribe message in can balanced each second message-oriented middleware server 303 avoids a certain second message-oriented middleware server 303 to handle the idle problem of the big or a certain second message-oriented middleware server 303 of subscribe message pressure.Other of processing requirements are provided with and in said system embodiment one, describe in detail, repeat no more here.
After the step 606 that executes flow process shown in Figure 6, promptly the second message-oriented middleware server 303 also can send successful information to database server 302 feedbacks further after sending the subscribe message success; Correspondingly; Database server 302 is after the transmission successful information that receives the second message-oriented middleware server, 303 feedbacks; This subscribe message that deletion is preserved and corresponding target address information; Thereby avoid this subscribe message to be repeated to send, the unnecessary subscribe message of avoiding database server 302 to preserve, the response speed of raising database server 302.
Through above-mentioned flow process; Can be with subscribe message that newly arrives the first message-oriented middleware server 301 and the transmission flow separation of sending the subscribe message of failure; The i.e. newly arrived subscribe message of the first message-oriented middleware server, 301 main processing; The second message-oriented middleware server, 303 main processing, the first message-oriented middleware server 301 sends the subscribe message of failure, thereby has avoided sending the influence of the subscribe message of failure to the transmission promptness of new arrival subscribe message.
Flow process shown in Figure 6 has mainly been described the first message-oriented middleware server 301 and has been sent a handling process after the subscribe message failure; In the practical application; The first message-oriented middleware server 301 may receive a plurality of subscribe message from a message publisher server or the transmission of a plurality of message publisher server, and the first message-oriented middleware server 301 needs send each subscribe message successively according to the reception order of these a plurality of subscribe message.Particularly:
In the above-mentioned steps 601; The first message-oriented middleware server 301 is behind the target address information of subscribe message that receives the transmission of message publisher server and correspondence; Before carrying out above-mentioned steps 602, this subscribe message that at first will receive and corresponding target address information add message send queue, in the above-mentioned steps 602; The first message-oriented middleware server 301 sends this subscribe message to the subscriber terminal corresponding with this target address information, specifically comprises:
From message send queue, obtain current subscribe message and the corresponding target address information that needs transmission, and this subscribe message is sent at the corresponding subscriber terminal of the target address information in the information of obtaining;
Correspondingly, after above-mentioned steps 603 judges that this subscribe message is sent whether success, process ends temporarily, carry out following steps:
Delete subscribe message and corresponding target address information in this message send queue; And judge whether also have the subscribe message of not sending in the message send queue; If judged result is for being; Then obtain this subscribe message and corresponding target address information, and the described flow process of execution in step 602 to step 606; If judged result is not, then process ends.
Embodiment five
The transmitting system of the subscribe message that provides corresponding to the foregoing description two; The application embodiment five provides a kind of method of subscribe message; This method is applicable to that the first message-oriented middleware server 301 that comprises in the transmitting system of subscribe message and the second message-oriented middleware server 303 are many situation; Can be on the basis that does not increase new server resource through this method; The dynamic adjustment of first message-oriented middleware server 301 that comprises in the transmitting system of realization to subscribe message and the second message-oriented middleware server, 303 quantity is to reach the equilibrium of internal system server resource.
As shown in Figure 7, this method comprises the steps:
The quantity of the target address information of subscribe message of preserving in step 701,304 pairs of database servers 302 of monitoring server and correspondence is monitored;
Whether the quantity of the subscribe message of preserving in step 702, the monitoring server 304 judgment data storehouse servers 302 greater than the 7th setting threshold, if, execution in step 703～step 704, if not, execution in step 705～step 707; Here, the 7th setting threshold is corresponding to the 5th setting threshold in the foregoing description two, and concrete establishing method specifies in the foregoing description two, repeats no more here.
In this step 704; This first message-oriented middleware server 301 is after stopping to receive subscribe message that the message publisher server sends and corresponding target address information; Further carry out and obtain subscribe message and the corresponding target address information of preserving in the database server, send the step of subscribe message to the subscriber terminal corresponding with this target address information.
Whether the quantity of the subscribe message of preserving in step 705, the monitoring server 304 judgment data storehouse servers 302 less than the 8th setting threshold, if, execution in step 706～step 707 then; If not, return step 701; Here, the 8th setting threshold is corresponding to the 6th setting threshold in the foregoing description two, and concrete establishing method specifies in the foregoing description two, repeats no more here.
The second message-oriented middleware server 303 of step 707, the indication of reception second load balancing stops to obtain subscribe message and the corresponding target address information preserved in the database server after receiving the indication of second load balancing.
In this step 707; This second message-oriented middleware server 303 is after stopping to obtain the subscribe message of preserving in the database server and corresponding target address information; Further carry out and receive subscribe message and the corresponding target address information that the message publisher server sends; Send this subscribe message to the subscriber terminal corresponding, and after sending this subscribe message failure, this subscribe message and corresponding target address information are sent to database server 302 with this target address information.
Flow process shown in Figure 7 sends to database server 302 back execution at subscribe message and the corresponding target address information that the first message-oriented middleware server 301 will send failure, also can periodically carry out.
In the flow process shown in Figure 7; Indicate the first message-oriented middleware server 301 no longer as the server that sends new subscribe message through above-mentioned steps 703～step 704; And be responsible for the subscribe message of sending failure in the database server 302 is resend; Particularly; After the first message-oriented middleware server 301 that monitoring server 304 control is set was accomplished the functions conversion, the first message-oriented middleware server 301 of this setting (having converted the second message-oriented middleware server 303 into) can notify each message publisher server to break off and self be connected, and each message publisher server is no longer to the first message-oriented middleware server, the 301 transmission subscribe message of this setting.
In the flow process shown in Figure 7; Indicate the second message-oriented middleware server 303 no longer as the server that the subscribe message of sending failure is resend through above-mentioned steps 706～step 707; And be responsible for the subscribe message that the message publisher server sends is sent; Particularly; After monitoring server 304 control was set the second message-oriented middleware server 303 and accomplished the functions conversion, the second message-oriented middleware server 303 of this setting (having converted the first message-oriented middleware server 301 into) can be set up and self be connected with each message publisher server, and each message publisher server can be to the second message-oriented middleware server, the 303 transmission subscribe message of this setting.
Embodiment six
The transmitting system of the subscribe message that provides corresponding to the foregoing description three, the application embodiment six provides a kind of method of subscribe message, and is as shown in Figure 8, and this method comprises the steps:
Subscribe message and corresponding target address information that step 805, the second message-oriented middleware server 502 send according to the first message-oriented middleware server 501; Send subscribe message to the subscriber terminal corresponding with this target address information; So far, finish the transmission flow of current subscribe message.
After the step 805 that executes flow process shown in Figure 8, promptly the second message-oriented middleware server 502 can be deleted this subscribe message and corresponding target address information after sending the subscribe message success, thereby avoids this subscribe message to be repeated to send.
Flow process shown in Figure 8 has mainly been described the first message-oriented middleware server 501 and has been sent a handling process after the subscribe message failure; In the practical application; The first message-oriented middleware server 501 may receive the subscribe message of sending from one or more message publisher servers, and the first message-oriented middleware server 501 can send each subscribe message successively according to the reception order of these a plurality of subscribe message.Particularly:
In the above-mentioned steps 801; The first message-oriented middleware server 501 is behind the target address information of subscribe message that receives the transmission of message publisher server and correspondence; Before carrying out above-mentioned steps 802, this subscribe message that at first will receive and corresponding target address information add message send queue, in the above-mentioned steps 802; The first message-oriented middleware server 501 sends this subscribe message to the subscriber terminal corresponding with this target address information, specifically comprises:
From message send queue, obtain current subscribe message and the corresponding target address information that needs transmission, and this subscribe message is sent at the corresponding subscriber terminal of the target address information in the information of obtaining;
Correspondingly, after above-mentioned steps 803 judges that this subscribe message is sent whether success, finish the transmission flow of this subscribe message, carry out following steps:
Delete subscribe message and corresponding target address information in this message send queue; And judge whether also have the subscribe message of not sending in the message send queue; If judged result is for being; Then obtain this subscribe message and corresponding target address information, and the described flow process of execution in step 802 to step 805; If judged result is not, then process ends.
Above-mentioned at least one technical scheme that provides through the application embodiment; The first message-oriented middleware server is after sending said subscribe message failure; This subscribe message and corresponding target address information are sent to the database server or the second message-oriented middleware server; This second message-oriented middleware server sends said subscribe message according to subscribe message and corresponding target address information or subscribe message of from database server, obtaining and corresponding target address information that the first message-oriented middleware server sends to the subscriber terminal corresponding with this target address information.According to this technical scheme; The first message-oriented middleware server is after sending the subscribe message failure; The subscribe message of this transmission failure is responsible for resending by the second message-oriented middleware server; Compared with prior art, the subscribe message of this transmission failure can not cause newly arriving the transmission sluggishness of the subscribe message of the first message-oriented middleware server.
Further; The technical scheme that provides according to the application embodiment; The first message-oriented middleware server is after sending the subscribe message failure; The subscribe message of this transmission failure is responsible for resending by the second message-oriented middleware server; Compared with prior art; Can be, and under the storage resources condition of limited of the first message-oriented middleware server owing to a large amount of speeds of service that influence the first message-oriented middleware server that take of sending the subscribe message of failure to storage resources in the first message-oriented middleware server, not can owing to a large amount of subscribe message of sending failure to taking of storage resources in the first message-oriented middleware server and possibly cause can't preserve newly arrived subscribe message.
The application is that reference is described according to the flow chart and/or the block diagram of method, equipment (system) and the computer program of the application embodiment.Should understand can be by the flow process in each flow process in computer program instructions realization flow figure and/or the block diagram and/or square frame and flow chart and/or the block diagram and/or the combination of square frame.Can provide these computer program instructions to the processor of all-purpose computer, special-purpose computer, Embedded Processor or other programmable data processing device to produce a machine, make the instruction of carrying out through the processor of computer or other programmable data processing device produce to be used for the device of the function that is implemented in flow process of flow chart or a plurality of flow process and/or square frame of block diagram or a plurality of square frame appointments.
These computer program instructions also can be stored in ability vectoring computer or the computer-readable memory of other programmable data processing device with ad hoc fashion work; Make the instruction that is stored in this computer-readable memory produce the manufacture that comprises command device, this command device is implemented in the function of appointment in flow process of flow chart or a plurality of flow process and/or square frame of block diagram or a plurality of square frame.
These computer program instructions also can be loaded on computer or other programmable data processing device; Make on computer or other programmable devices and to carry out the sequence of operations step producing computer implemented processing, thereby the instruction of on computer or other programmable devices, carrying out is provided for being implemented in the step of the function of appointment in flow process of flow chart or a plurality of flow process and/or square frame of block diagram or a plurality of square frame.
Obviously, those skilled in the art can carry out various changes and modification and the spirit and the scope that do not break away from the application to the application.Like this, belong within the scope of the application's claim and equivalent technologies thereof if these of the application are revised with modification, then the application also is intended to comprise these changes and modification interior.
Claims (12)
1. the transmitting system of a subscribe message is characterized in that, comprises the first message-oriented middleware server, database server and the second message-oriented middleware server; Wherein:
The said first message-oriented middleware server; After being used to receive subscribe message that the message publisher server sends and corresponding target address information; Said subscribe message is sent at subscriber terminal to corresponding with said target address information; And after sending said subscribe message failure, said subscribe message and corresponding target address information are sent to said database server;
Said database server is used to preserve subscribe message and the corresponding target address information that the said first message-oriented middleware server sends;
The said second message-oriented middleware server is used for obtaining subscribe message and the corresponding target address information that said database server is preserved, and sends said subscribe message to the subscriber terminal corresponding with said target address information.
2. the system of claim 1; It is characterized in that; The said first message-oriented middleware server specifically behind the target address information of subscribe message that receives the transmission of message publisher server and correspondence, adds message send queue with said subscribe message and corresponding target address information; And after sending said subscribe message success, delete said subscribe message and corresponding target address information in the said message send queue.
3. the system of claim 1 is characterized in that, the said second message-oriented middleware server after sending said subscribe message success, also is used for sending successful information to said database server feedback;
Said database server also is used for after the transmission successful information that receives the said second message-oriented middleware server feedback, said subscribe message that deletion is preserved and corresponding target address information.
4. the system of claim 1; It is characterized in that; The said second message-oriented middleware server; Specifically confirm to have preserved in the said database server subscribe message that satisfies self processing requirements and corresponding target address information through the mode of poll after, obtain said subscribe message and the corresponding target address information that satisfies self processing requirements, and send said subscribe message to the subscriber terminal corresponding with said target address information.
5. the system of claim 1 is characterized in that, also comprises being used for monitoring server:
Quantity to the subscribe message of preserving in the said database server is monitored;
Monitoring said quantity when being many greater than first setting threshold and the said first message-oriented middleware server, at least one first message-oriented middleware server in the said first message-oriented middleware server of Xiang Duotai sends the indication of first load balancing; Receive the first message-oriented middleware server of said first load balancing indication; Specifically after receiving said first load balancing indication; Stop to receive subscribe message and the corresponding target address information that the message publisher server sends; And obtain subscribe message and the corresponding target address information of preserving in the said database server, send said subscribe message to the subscriber terminal corresponding with said target address information;
Monitoring said quantity when being many less than second setting threshold and the said second message-oriented middleware server, at least one second message-oriented middleware server in the said second message-oriented middleware server of Xiang Duotai sends the indication of second load balancing; The second message-oriented middleware server that receives said second load balancing indication is after receiving said second load balancing indication; Stop to obtain subscribe message and the corresponding target address information preserved in the said database server; And the subscribe message and the corresponding target address information of the transmission of reception message publisher server; Said subscribe message is sent at subscriber terminal to corresponding with said target address information; And after sending said subscribe message failure, said subscribe message and corresponding target address information are sent to said database server.
6. the transmitting system of a subscribe message is characterized in that, comprises the first message-oriented middleware server and the second message-oriented middleware server; Wherein:
The said first message-oriented middleware server; After being used to receive subscribe message that the message publisher server sends and corresponding target address information; Said subscribe message is sent at subscriber terminal to corresponding with said target address information; And after sending said subscribe message failure, said subscribe message and corresponding target address information are sent to the said second message-oriented middleware server;
The said second message-oriented middleware server is used for subscribe message and corresponding target address information according to said first message-oriented middleware server transmission, and sends said subscribe message to the subscriber terminal corresponding with said target address information.
7. the sending method of a subscribe message is characterized in that, comprising:
Behind subscribe message that first message-oriented middleware server reception message publisher server sends and the corresponding target address information; Said subscribe message is sent at subscriber terminal to corresponding with said target address information; And after sending said subscribe message failure, said subscribe message and corresponding target address information are sent to database server;
Said database server is preserved subscribe message and the corresponding target address information that the said first message-oriented middleware server sends;
The second message-oriented middleware server obtains subscribe message and the corresponding target address information of preserving in the said database server, and sends said subscribe message to the subscriber terminal corresponding with said target address information.
8. method as claimed in claim 7 is characterized in that, said method also comprises:
The said first message-oriented middleware server is behind the target address information of subscribe message that receives the transmission of message publisher server and correspondence; Said subscribe message and corresponding target address information are added message send queue; And after sending said subscribe message success, delete said subscribe message and corresponding target address information in the said message send queue.
9. method as claimed in claim 7 is characterized in that, the said second message-oriented middleware server after sending said subscribe message success, also comprises:
Send successful information to said database server feedback;
Said database server is deleted said subscribe message and the corresponding target address information preserved after the transmission successful information that receives the said second message-oriented middleware server feedback.
10. method as claimed in claim 7 is characterized in that, the said second message-oriented middleware server obtains before the subscribe message of preserving in the said database server and the corresponding target address information, also comprises:
The said second message-oriented middleware server confirms to have preserved in the said database server subscribe message and the corresponding target address information that satisfies self processing requirements through the mode of poll.
11. method as claimed in claim 7 is characterized in that, said method also comprises:
Monitoring server is monitored the quantity of the subscribe message of preserving in the said database server and corresponding target address information after the said first message-oriented middleware server sends to said database server with said subscribe message and corresponding target address information; Or periodically the quantity of the subscribe message of preserving in the said database server and corresponding target address information is monitored;
Monitoring server is monitoring said quantity when being many greater than first setting threshold and the said first message-oriented middleware server, and at least one first message-oriented middleware server in the said first message-oriented middleware server of Xiang Duotai sends the indication of first load balancing; Receive the first message-oriented middleware server of said first load balancing indication; Specifically after receiving said first load balancing indication; Stop to receive subscribe message and the corresponding target address information that the message publisher server sends; And obtain subscribe message and the corresponding target address information of preserving in the said database server, send said subscribe message to the subscriber terminal corresponding with said target address information;
Monitoring server is monitoring said quantity when being many less than second setting threshold and the said second message-oriented middleware server, and at least one second message-oriented middleware server in the said second message-oriented middleware server of Xiang Duotai sends the indication of second load balancing; The second message-oriented middleware server that receives said second load balancing indication is after receiving said second load balancing indication; Stop to obtain subscribe message and the corresponding target address information preserved in the said database server; And the subscribe message and the corresponding target address information of the transmission of reception message publisher server; Said subscribe message is sent at subscriber terminal to corresponding with said target address information; And after sending said subscribe message failure, said subscribe message and corresponding target address information are sent to said database server.
12. the sending method of a subscribe message is characterized in that, comprising:
Behind subscribe message that first message-oriented middleware server reception message publisher server sends and the corresponding target address information; Said subscribe message is sent at subscriber terminal to corresponding with said target address information; And after sending said subscribe message failure, said subscribe message and corresponding target address information are sent to the second message-oriented middleware server;
The said second message-oriented middleware server sends said subscribe message according to subscribe message and corresponding target address information that the said first message-oriented middleware server sends to the subscriber terminal corresponding with said target address information.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010252083.5A CN102377685B (en) | 2010-08-06 | 2010-08-06 | Subscription message sending system and subscription message sending method |
| HK12104320.9A HK1163970A1 (en) | 2010-08-06 | 2012-05-03 | A system and method for sending subscription information |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010252083.5A CN102377685B (en) | 2010-08-06 | 2010-08-06 | Subscription message sending system and subscription message sending method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102377685A true CN102377685A (en) | 2012-03-14 |
| CN102377685B CN102377685B (en) | 2015-04-29 |
Family
ID=45795677
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010252083.5A Active CN102377685B (en) | 2010-08-06 | 2010-08-06 | Subscription message sending system and subscription message sending method |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN102377685B (en) |
| HK (1) | HK1163970A1 (en) |
Cited By (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103677988A (en) * | 2013-12-11 | 2014-03-26 | 北京爱唯光石信息技术有限公司 | Multi-process communication method and system for software system |
| CN104102604A (en) * | 2013-04-12 | 2014-10-15 | 杭州迪普科技有限公司 | Business processing device |
| CN104243611A (en) * | 2014-09-30 | 2014-12-24 | 浪潮软件股份有限公司 | Distribution thought based message service middleware system |
| CN104899247A (en) * | 2015-04-20 | 2015-09-09 | 广州华多网络科技有限公司 | Information subscription method and system |
| CN105593817A (en) * | 2013-05-20 | 2016-05-18 | 派克赛泽有限责任公司 | Method and system for flexible node composition on local or distributed computer systems |
| CN105824842A (en) * | 2015-01-07 | 2016-08-03 | 阿里巴巴集团控股有限公司 | Distributed transaction processing method and system |
| CN106330994A (en) * | 2015-06-18 | 2017-01-11 | 天脉聚源（北京）科技有限公司 | User message publishing method and system |
| CN106851411A (en) * | 2016-12-29 | 2017-06-13 | 深圳Tcl数字技术有限公司 | Television set control message transmission method, system and device |
| CN106911766A (en) * | 2017-01-23 | 2017-06-30 | 北京思特奇信息技术股份有限公司 | A kind of method for message transmission |
| CN107133302A (en) * | 2017-04-28 | 2017-09-05 | 努比亚技术有限公司 | Realize method, system, terminal and the computer-readable recording medium of data consistency |
| CN109255091A (en) * | 2018-08-23 | 2019-01-22 | 北京城市网邻信息技术有限公司 | Method, apparatus, equipment and the computer readable storage medium of shared theme message |
| CN109542647A (en) * | 2018-11-21 | 2019-03-29 | 泰康保险集团股份有限公司 | Information transmitting administrative method and device, electronic equipment, storage medium |
| CN110417646A (en) * | 2019-08-01 | 2019-11-05 | 北京吉旗咨询服务有限公司 | The method and device for subscribing to message are pushed based on RPC application program |
| CN111625366A (en) * | 2020-06-02 | 2020-09-04 | 深圳市网是科技有限公司 | Elastic expansion service method based on release and subscription model |
| CN112328404A (en) * | 2020-11-26 | 2021-02-05 | 北京百度网讯科技有限公司 | Load balancing method and device, electronic equipment and computer readable medium |
| CN113342606A (en) * | 2021-06-07 | 2021-09-03 | 平安证券股份有限公司 | Data monitoring method, device, equipment and storage medium based on message middleware |
| CN113590715A (en) * | 2021-07-30 | 2021-11-02 | 工银科技有限公司 | Block chain-based information push method, apparatus, device, medium, and program product |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6304913B1 (en) * | 1998-11-09 | 2001-10-16 | Telefonaktiebolaget L M Ericsson (Publ) | Internet system and method for selecting a closest server from a plurality of alternative servers |
| CN1496088A (en) * | 2002-09-11 | 2004-05-12 | 三星电子株式会社 | Server and method for special-purpose radio network short information service |
-
2010
- 2010-08-06 CN CN201010252083.5A patent/CN102377685B/en active Active
-
2012
- 2012-05-03 HK HK12104320.9A patent/HK1163970A1/en unknown
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6304913B1 (en) * | 1998-11-09 | 2001-10-16 | Telefonaktiebolaget L M Ericsson (Publ) | Internet system and method for selecting a closest server from a plurality of alternative servers |
| CN1496088A (en) * | 2002-09-11 | 2004-05-12 | 三星电子株式会社 | Server and method for special-purpose radio network short information service |
Cited By (24)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104102604A (en) * | 2013-04-12 | 2014-10-15 | 杭州迪普科技有限公司 | Business processing device |
| CN104102604B (en) * | 2013-04-12 | 2017-07-04 | 杭州迪普科技股份有限公司 | A kind of business processing device |
| CN105593817A (en) * | 2013-05-20 | 2016-05-18 | 派克赛泽有限责任公司 | Method and system for flexible node composition on local or distributed computer systems |
| US10491687B2 (en) | 2013-05-20 | 2019-11-26 | Packsize Llc | Method and system for flexible node composition on local or distributed computer systems |
| CN103677988A (en) * | 2013-12-11 | 2014-03-26 | 北京爱唯光石信息技术有限公司 | Multi-process communication method and system for software system |
| CN104243611A (en) * | 2014-09-30 | 2014-12-24 | 浪潮软件股份有限公司 | Distribution thought based message service middleware system |
| CN104243611B (en) * | 2014-09-30 | 2017-07-07 | 浪潮软件股份有限公司 | A kind of messenger service middleware system based on distribution thought |
| CN105824842A (en) * | 2015-01-07 | 2016-08-03 | 阿里巴巴集团控股有限公司 | Distributed transaction processing method and system |
| CN105824842B (en) * | 2015-01-07 | 2019-05-10 | 阿里巴巴集团控股有限公司 | Distributed transaction processing method and its system |
| CN104899247B (en) * | 2015-04-20 | 2018-09-25 | 广州华多网络科技有限公司 | A kind of information customization method and system |
| CN104899247A (en) * | 2015-04-20 | 2015-09-09 | 广州华多网络科技有限公司 | Information subscription method and system |
| CN106330994A (en) * | 2015-06-18 | 2017-01-11 | 天脉聚源（北京）科技有限公司 | User message publishing method and system |
| CN106851411A (en) * | 2016-12-29 | 2017-06-13 | 深圳Tcl数字技术有限公司 | Television set control message transmission method, system and device |
| CN106911766A (en) * | 2017-01-23 | 2017-06-30 | 北京思特奇信息技术股份有限公司 | A kind of method for message transmission |
| CN107133302A (en) * | 2017-04-28 | 2017-09-05 | 努比亚技术有限公司 | Realize method, system, terminal and the computer-readable recording medium of data consistency |
| CN109255091A (en) * | 2018-08-23 | 2019-01-22 | 北京城市网邻信息技术有限公司 | Method, apparatus, equipment and the computer readable storage medium of shared theme message |
| CN109542647A (en) * | 2018-11-21 | 2019-03-29 | 泰康保险集团股份有限公司 | Information transmitting administrative method and device, electronic equipment, storage medium |
| CN109542647B (en) * | 2018-11-21 | 2020-11-24 | 泰康保险集团股份有限公司 | Information transmission management method and device, electronic device and storage medium |
| CN110417646A (en) * | 2019-08-01 | 2019-11-05 | 北京吉旗咨询服务有限公司 | The method and device for subscribing to message are pushed based on RPC application program |
| CN111625366A (en) * | 2020-06-02 | 2020-09-04 | 深圳市网是科技有限公司 | Elastic expansion service method based on release and subscription model |
| CN112328404A (en) * | 2020-11-26 | 2021-02-05 | 北京百度网讯科技有限公司 | Load balancing method and device, electronic equipment and computer readable medium |
| CN112328404B (en) * | 2020-11-26 | 2023-08-08 | 北京百度网讯科技有限公司 | Load balancing method and device, electronic equipment and computer readable medium |
| CN113342606A (en) * | 2021-06-07 | 2021-09-03 | 平安证券股份有限公司 | Data monitoring method, device, equipment and storage medium based on message middleware |
| CN113590715A (en) * | 2021-07-30 | 2021-11-02 | 工银科技有限公司 | Block chain-based information push method, apparatus, device, medium, and program product |
Also Published As
| Publication number | Publication date |
|---|---|
| HK1163970A1 (en) | 2012-09-14 |
| CN102377685B (en) | 2015-04-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102377685B (en) | Subscription message sending system and subscription message sending method | |
| CN103561049A (en) | Method for processing terminal scheduling request, system thereof and device thereof | |
| US10148565B2 (en) | OPENFLOW communication method and system, controller, and service gateway | |
| CN102469064B (en) | Realization Method of Communication and communication equipment | |
| CN109327513B (en) | Interaction method, interaction device and computer-readable storage medium | |
| CN103491102A (en) | Method, system and device for monitoring stability of internet audio and video | |
| CN103312528B (en) | A kind of heartbeat message sending method and user terminal | |
| CN104796337A (en) | Method and device for forwarding message | |
| CN101909048A (en) | Centralized trans-coding treatment method and device | |
| CN102469033A (en) | Message subscription system and message sending method | |
| EP3582458A1 (en) | Communication system, communication device, and communication method | |
| CN103971687A (en) | Method and device for realizing load balance of voice recognition system | |
| CN104935622A (en) | Method used for message distribution and consumption and apparatus thereof, and system used for message processing | |
| CN105407413A (en) | Distributed video transcoding method and related device and system | |
| CN103634224A (en) | Method and system for transmitting data in network | |
| CN102724132A (en) | Method and device for improving transmission control protocol (TCP) connection multiplexing processing efficiency | |
| US11218371B2 (en) | Method and apparatus for performing communication in internet of things | |
| CN102957626A (en) | Message forwarding method and device | |
| CN100334834C (en) | A proxy server system and method for realizing proxy communication thereof | |
| CN110071968B (en) | Block chain based message storage method and device | |
| US20120173652A1 (en) | Method for handling communications over a non-permanent communication link | |
| CN104580209A (en) | Device and method for implementing multi-platform message processing | |
| KR101272077B1 (en) | System and method for providing push service | |
| CN104243483A (en) | Message processing method and message processing equipment | |
| CN102685235A (en) | Message dispatching method and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 1163970 Country of ref document: HK |
|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: GR Ref document number: 1163970 Country of ref document: HK |