CN103037000A - Publish-subscribe system and notification message processing method thereof - Google Patents
Publish-subscribe system and notification message processing method thereof Download PDFInfo
- Publication number
- CN103037000A CN103037000A CN2012105623194A CN201210562319A CN103037000A CN 103037000 A CN103037000 A CN 103037000A CN 2012105623194 A CN2012105623194 A CN 2012105623194A CN 201210562319 A CN201210562319 A CN 201210562319A CN 103037000 A CN103037000 A CN 103037000A
- Authority
- CN
- China
- Prior art keywords
- entity
- subscribe request
- subscription
- propelling movement
- notification
- 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
Abstract
The invention discloses a notification message processing method which includes the following steps: a notification broker transmits notification messages to subscription entity through an interior publisher when load the notification message, the subscription entity sends the notification messages meeting the filtering criteria to a push endpoint relevant to the subscription entity, the push endpoint transmits the notification messages a message receiving entity relative to the push endpoint and sends the notification messages to a subscriber through the message receiving entity. The invention further discloses a publish-subscribe system using the notification message processing method. Due to the technical scheme, the notification message processing method is capable of initiatively sending the notification messages to the subscriber, balancing load of the publish-subscribe system and further improving processing efficiency of the publish-subscribe system.
Description
Technical field
The present invention relates to the network communications technology, relate in particular to a kind of distribution subscription system and notification message processing method thereof.
Background technology
Distribution subscription (the Pub/Sub of service Network Based (Web Service) technology, Publish/Subscribe) system applies is increasingly extensive, subscriber (Subscriber) sends subscribe request to notification agent, subscribe to the information that needs concern, and adopt and to pull (Pull) mode, obtain the notification message that satisfies subscribe request in the notification message that publisher (Publisher) sends to distribution subscription system.
Current, promote tissue (OASIS based on the structured message standard, in the distribution subscription system of network service notice (Web-Service Notification) standard of Organization for theAdvancement of Structured Information Standards) formulating, notification message initiatively can not sent to the subscriber, but, in the scene of increasing application distribution subscription system, professional such as banker's rate, stock is professional and the online game operation is professional, in the urgent need to notification message initiatively being sent to the subscriber, the demand that in time arrives to satisfy notification message;
Simultaneously, needing distribution subscription system to process in the application scenarios of a large amount of notification messages, how the balance distribution subscription system is loaded, and improves data processing performance, also is problem demanding prompt solution.
Summary of the invention
In view of this, main purpose of the present invention is to provide a kind of distribution subscription system and notification message processing method thereof, initiatively sends a notification message to subscriber's application scenarios demand to satisfy the demand; The balance distribution subscription system is loaded simultaneously, with the applicable application scenarios that needs to process a large amount of notification messages.
For achieving the above object, technical scheme of the present invention is achieved in that
The invention provides a kind of distribution subscription system, described distribution subscription system comprises subscriber, notification agent, publisher, inner publisher, the subscription entity corresponding with described inner publisher, the propelling movement end points of setting up with message sink entity corresponding to described subscriber, by described notification agent of being set up by described subscriber and the reasoning entity of being set up by described subscription entity; Wherein,
Described notification agent is used for receiving the notification message of described publisher's transmission and being forwarded to described inner publisher;
Described inner publisher, be used for to determine described subscription entity when preload during not above setting threshold, described notification message is forwarded to described reasoning entity by described subscription entity;
Described reasoning entity, when be used for determining that notification message satisfies the initialization filtercondition of described reasoning entity, send a notification message to the propelling movement end points of described subscription entity associated;
Described propelling movement end points, be used for to transmit notification message to the message sink entity of described propelling movement associations;
Described message sink entity, the notification message that is used for receiving is sent to described subscriber.
Preferably,
Described notification agent also is used for upgrading subscribing relationship according to subscribe request and describes, and described subscribing relationship is described the semantic prioritization of the subscribe request that comprises subscribe request and subordinate, and the keyword that carries of the subscribe request of subscribe request and subordinate.
Preferably,
Described notification agent, after also being used for receiving the notification message of described publisher's transmission, describe according to subscribing relationship, determine to carry subscribe request and/or the subordinate subscribe request of the keyword match that keyword and described notification message carry, and sort by subscribe request and/or the subordinate subscribe request of semantic priority to coupling, described notification message is sent to inside publisher corresponding to subscription entity who sets up according to subscribe request and/or the subordinate subscribe request of coupling according to described ordering.
Preferably,
Described notification agent when also being used for receiving described subscriber and setting up the request message that pushes end points, is set up described propelling movement end points; The message sink physical address that described request message is carried is registered at the propelling movement end points, related described message sink entity and described propelling movement end points, and when the propelling movement end-point addresses that the described propelling movement end points of reception returns, be forwarded to described subscriber.
Preferably,
Described notification agent, after also being used for setting up described propelling movement end points, set up when receiving the subscribe request that described subscriber sends and subscribe to entity, the described subscription entity of subscription name, keyword and filtercondition initialization that carries with described subscribe request, and the propelling movement end-point addresses that subscribe request is carried registered related described propelling movement end points and described subscription entity at described subscription entity;
Described subscription entity also is used for setting up the reasoning entity, the described reasoning entity of filtercondition initialization that carries with described subscribe request.
Accordingly, the present invention also provides a kind of notification message processing method, is applied in the distribution subscription system, and described notification message processing method comprises:
Described notification agent is forwarded to described inner publisher after receiving the notification message of described publisher's transmission;
Described inner publisher determine described subscription entity when preload does not exceed setting threshold, described notification message is forwarded to described reasoning entity by described subscription entity;
When described reasoning entity determines that described notification message satisfies the initialization filtercondition of described reasoning entity, described notification message is sent to propelling movement end points with described subscription entity associated;
Described propelling movement end points is forwarded to message sink entity with described propelling movement associations with described notification message, and by described message sink entity described notification message is sent to described subscriber.
Preferably, described notification message processing method also comprises:
Described notification agent is upgraded subscribing relationship according to subscribe request and is described, described subscribing relationship is described the semantic prioritization of the subordinate subscribe request that comprises subscribe request and described subscribe request, and the keyword that carries of described subscribe request and described subordinate subscribe request.
Preferably, described notification agent is forwarded to described inner publisher after receiving the notification message of described publisher's transmission, comprising:
After described notification agent receives the notification message of described publisher's transmission, describe according to subscribing relationship, determine subscribe request and/or the subordinate subscribe request of the keyword match that carries with described notification message, and sort by subscribe request and/or the subordinate subscribe request of semantic priority to coupling, described notification message is sent to inside publisher corresponding to subscription entity who sets up according to subscribe request and/or the subordinate subscribe request of coupling according to described ordering.
Preferably, described notification message processing method also comprises:
Described notification agent receives described subscriber when setting up the request message that pushes end points, sets up described propelling movement end points;
The message sink physical address that described notification agent is carried described request message is registered at described propelling movement end points, related described message sink entity and described propelling movement end points, and when receiving the propelling movement end-point addresses that described propelling movement end points returns, be forwarded to described subscriber.
Preferably, after described notification agent was set up described propelling movement end points, described notification message processing method also comprised:
Described notification agent is when receiving the subscribe request of described subscriber's transmission, set up and subscribe to entity, the described subscription entity of subscription name, keyword and filtercondition initialization that carries with described subscribe request, and the propelling movement end-point addresses that described subscribe request is carried registered related described propelling movement end points and described subscription entity at described subscription entity;
Described subscription entity is set up the reasoning entity, the described reasoning entity of filtercondition initialization that carries with described subscribe request.
In the technical scheme provided by the present invention, push end points by setting up, send the extremely related message sink entity of notification message that satisfies filtercondition by pushing end points, and transmit described notification message to the subscriber by the message sink entity, the active that has realized notification message sends, and has satisfied needs and has initiatively sent a notification message to subscriber's application scenarios demand;
Simultaneously, inner publisher is subscribing to just the sending a notification message to the subscription entity of entity when preload does not exceed setting threshold, balance the distribution subscription system load, improved data processing performance;
Preferably, notification agent is according to the semantic prioritization of coupling subscribe request, send a notification message to the inside publisher corresponding with the subscription entity of setting up according to described coupling subscribe request, so, need send a large amount of subscribe request the subscriber, and when there is subordinate relation in the subscribe request that the subscriber sends, can in a subscribe request, specify the subordinate relation between all subscribe request that need to send, by sending subscribe request one time, subscribe to the notification message that satisfies a plurality of subscribe request filterconditions, improved the treatment effeciency of distribution subscription system.
Description of drawings
Fig. 1 is the realization flow schematic diagram of notification message processing method of the present invention;
Fig. 2 is the composition structural representation of distribution subscription system of the present invention;
Fig. 3 is that distribution subscription system of the present invention is for the handling process schematic diagram of subscribe request;
Fig. 4 is that distribution subscription system of the present invention is for the handling process schematic diagram of notification message.
Embodiment
The present invention is further detailed explanation below in conjunction with drawings and the specific embodiments.
Fig. 1 is the realization flow schematic diagram of notification message processing method of the present invention, described notification message processing method is applied in the distribution subscription system, described distribution subscription system comprises subscriber, notification agent, publisher, inner publisher, the subscription entity corresponding with described inner publisher, the propelling movement end points of setting up with message sink entity corresponding to described subscriber, by described notification agent of being set up by described subscriber and the reasoning entity of being set up by described subscription entity, as shown in Figure 1, described notification message processing method comprises:
Step 101: described notification agent is forwarded to described inner publisher after receiving the notification message of described publisher's transmission;
Here, preferred before the step 101, comprise that also described subscriber sets up the flow process of the message sink entity corresponding with described subscriber.
Described flow process comprises: described subscriber sets up the message sink entity corresponding with described subscriber, and receives the message sink physical address that described message sink entity returns.
Here, preferred, after described subscriber sets up described message sink entity, comprise that also described notification agent sets up the flow process of described propelling movement end points.
Described flow process comprises: described notification agent receives described subscriber when setting up the request message that pushes end points, sets up and pushes end points; The message sink physical address that described notification agent is carried described request message, register at the propelling movement end points, related described propelling movement end points and described message sink entity, and when receiving the propelling movement end-point addresses that described propelling movement end points returns, be forwarded to described subscriber.
Here, after described notification agent is set up the propelling movement end points according to described subscriber's request, preferably, comprise that also described subscriber sends the flow process of subscribe request to described notification agent, described subscribe request is carried described propelling movement end-point addresses, is subscribed to name, keyword and filtercondition.
Here, described subscribe request and notification message can adopt resource description framework (RDF, ResourceDescription Framework) to describe.
Here, described notification agent is when receiving the subscribe request of described subscriber's transmission, and is preferred, also comprises the described notification agent flow process that entity is subscribed in foundation according to subscribe request.
Described flow process comprises:
When described notification agent receives the subscribe request of described subscriber's transmission, set up and subscribe to entity, the subscription entity that the subscription name of carrying with described subscribe request, keyword and filtercondition initialization are set up, and the propelling movement end-point addresses that described subscribe request is carried is being subscribed to registers entities, related described propelling movement end points and described subscription entity; Receive and subscribe to the subscription address that entity returns, preserve the mapping relations that described subscription entity initialization is subscribed to name and subscribed to physical address.Wherein, the subscribe request that other subscribers of the follow-up reception of described notification agent send, and when subscription name, keyword and filtercondition that subscription name, keyword and filtercondition that the subscribe request of described follow-up reception is carried and the previous subscribe request that receives are carried are identical, the message sink physical address that described follow-up subscribe request can be carried, the propelling movement end points of setting up when receiving described previous subscribe request is registered, with a plurality of message sink entities and propelling movement associations.
Here, described notification agent is when receiving the subscribe request of described subscriber's transmission, preferably, also comprise according to the subscribe request that receives and upgrade the flow process that subscribing relationship is described, described subscribing relationship is described the semantic prioritization of the subordinate subscribe request that comprises subscribe request and described subscribe request, and the keyword that carries of described subscribe request and described subordinate subscribe request.
Wherein, described subscribe request is carried the subordinate subscribe request of described subscribe request, the semantic prioritization that described subscribing relationship is described is definite according to the subordinate relation between described subscribe request and the subordinate subscribe request, and described semantic prioritization is set and comprised: the semantic priority of subscribe request is lower than the subscribe request of subscribe request institute subordinate.
Here, preferred after described notification agent is set up described subscription entity according to subscribe request, comprise that also described subscription entity sets up the flow process of reasoning entity.
Described flow process comprises: described subscription entity is set up the reasoning entity, and the described reasoning entity of filtercondition initialization that carries with subscribe request.
Here, described notification agent is when receiving the notification message that described publisher sends, and is preferred, comprises that also described notification agent sets up inner publisher's flow process according to notification message.
Described flow process comprises: when described notification agent receives the notification message of described publisher's transmission, the keyword that subscribe request and subordinate subscribe request were carried during the keyword traversal coupling subscribing relationship of carrying according to notification message was described, determine to carry subscribe request and/or subordinate subscribe request that keyword and notification message carry keyword match, and for subscribe request and/or the subordinate subscribe request of each described coupling, set up inner publisher, can guarantee that so described inner publisher and the subscription entity of setting up according to described coupling subscribe request and/or subordinate subscribe request can be corresponding one to one, with the semantic prioritization according to described coupling subscribe request and/or subordinate subscribe request, send a notification message to the inside publisher corresponding with the subscription entity of setting up according to described coupling subscribe request and/or subordinate subscribe request.For example, be provided with to carry and subscribe to name and be respectively A, B and C subscribe request, the subscribe request A that the publisher sends carries subordinate subscribe request B and the C that is subordinated to subscribe request A, and subordinate subscribe request C further is subordinated to subordinate subscribe request B, and then the semantic prioritization of the subscribe request of described subscribe request A, B and C in subscribing relationship is described is: subscribe request A＞subscribe request B＞subscribe request C.
Here, described notification agent is forwarded to described inner publisher after receiving the notification message of described publisher's transmission, comprising:
Notification agent receives the notification message that the publisher sends, describe according to subscribing relationship, determine subscribe request and/or the subordinate subscribe request of the keyword match that carries with described notification message, and by semantic priority to the coupling subscribe request and/or subordinate subscribe request sort, and sort inside publisher corresponding to subscription entity who sends a notification message and set up to according to described coupling subscribe request and/or subordinate subscribe request according to subscribe request and/or the subordinate subscribe request of semantic priority to coupling.For example, the keyword match that subscribe request A, B and C carried during the keyword that notification message carries and subscribing relationship were described, and the semantic prioritization of subscribe request A, B and C is: subscribe request A＞subscribe request B＞subscribe request C, then notification agent sequentially sends a notification message to the inside publisher corresponding with the subscription entity of initialization subscription A, B by name and C.
Step 102: described inner publisher determine described subscription entity when preload does not exceed setting threshold, described notification message is forwarded to described reasoning entity by described subscription entity;
Here, the load of described subscription entity can be subscribed to entity per second notification message treating capacity and describe, and described threshold value is default according to data-handling capacity and the application scenarios of distribution subscription system; Wherein, the mapping relations that described inner publisher subscribes to name and subscribes to physical address according to the subscription entity initialization that described notification agent is preserved, determine the address of the subscription entity related with described inner publisher, to send described notification message to the subscription entity related with described inner publisher, described subscription entity is transmitted the reasoning entity that described notice is set up to described subscription entity.
Step 103: when described reasoning entity determines that described notification message satisfies the initialization filtercondition of described reasoning entity, described notification message is sent to propelling movement end points with described subscription entity associated;
Here, described filtercondition can adopt the formal description of Boolean expression.
Step 104: described propelling movement end points is forwarded to message sink entity with described propelling movement associations with described notification message, and by described message sink entity described notification message is sent to described subscriber.
Here, described subscriber is the subscriber corresponding with described message sink entity.
Fig. 2 is the composition structural representation of distribution subscription system of the present invention, as shown in Figure 2, described distribution subscription system comprises subscriber 21, notification agent 22, publisher 23, inner publisher 26, the subscription entity 27 corresponding with described inner publisher 26, the propelling movement end points 25 of setting up by message sink entity 24 corresponding to described subscriber 21 subscriber that set up and described 21, by described notification agent 22 and the reasoning entity 28 of being set up by described subscription entity 27; Wherein,
Described notification agent 22 is used for receiving the notification message of described publisher's 23 transmissions and being forwarded to described inner publisher 26;
Described inner publisher 26, be used for to determine described subscription entity 27 when preload during not above setting threshold, described notification message is forwarded to described reasoning entity 28 by described subscription entity 27;
Described reasoning entity 28 when be used for determining that notification message satisfies the initialization filtercondition of described reasoning entity 28, sends described notification message to the propelling movement end points 25 related with described subscription entity 27;
Described propelling movement end points 25 be used for to be transmitted notification message to the message sink entity 24 related with described propelling movement end points 25;
Described message sink entity 24, the notification message that is used for receiving is sent to described subscriber 21.
Preferably,
Described notification agent 22, when also being used for receiving the subscribe request of described subscriber's 21 transmissions, upgrading subscribing relationship according to described subscribe request describes, described subscribing relationship is described the semantic prioritization of the subordinate subscribe request that comprises subscribe request and described subscribe request, and the keyword that carries of described subscribe request and described subordinate subscribe request.
Preferably,
Described notification agent 22, after also being used for receiving the notification message of described publisher's 23 transmissions, describe according to subscribing relationship, determine subscribe request and/or the subordinate subscribe request of the keyword match that carries with described notification message, and according to subscribe request and/or subordinate subscribe request the sorting of carrying out of semantic priority to coupling, described notification message is sent to the inside publisher 26 of subscription entity 27 correspondences of setting up according to subscribe request and/or the subordinate subscribe request of described coupling according to described ordering.
Preferably,
Described notification agent 22 when also being used for receiving the request message of described subscriber's 21 foundation propelling movement end points 25, is set up described propelling movement end points 25; Message sink entity 24 addresses that described request message is carried are registered at propelling movement end points 25, related described message sink entity 24 and described propelling movement end points 25, and when propelling movement end points 25 address that the described propelling movement end points 25 of reception returns, be forwarded to described subscriber 21.
Preferably,
Described notification agent 22, when also being used for receiving the subscribe request of described subscriber's 21 transmissions, set up and subscribe to entity 27, the described subscription entity 27 of subscription name, keyword and filtercondition initialization that carries with described subscribe request, and propelling movement end points 25 addresses that described subscribe request is carried are registered related described propelling movement end points 25 and described subscription entity 27 at described subscription entity 27;
Described subscription entity 27 also is used for setting up reasoning entity 28, the described reasoning entity 28 of filtercondition initialization that carries with described subscribe request.
Fig. 3 be distribution subscription system of the present invention for the handling process schematic diagram of subscribe request, described distribution subscription system comprises subscriber, notification agent, publisher, inner publisher, the subscription entity corresponding with described inner publisher, the propelling movement end points of setting up with message sink entity corresponding to described subscriber, by described notification agent of being set up by described subscriber and the reasoning entity of being set up by described subscription entity; As shown in Figure 3, described handling process for subscribe request may further comprise the steps:
Step 301～302: the subscriber sets up the message sink entity, the message sink physical address that the receipt message receiving entity returns:
Step 303: the subscriber sends to notification agent and sets up the request message that pushes end points;
Wherein, described request message is carried the address of message sink entity.
Step 304～306: notification agent is set up and is pushed end points, receives and pushes the propelling movement end-point addresses that end points returns, and be forwarded to the subscriber;
In the step 304, notification agent is registered related described propelling movement end points and message sink entity with the address of message sink entity at the propelling movement end points.
Step 307: the subscriber sends subscribe request to notification agent;
Wherein, described subscribe request is carried and is pushed end-point addresses, subscribes to name, keyword and filtercondition.
Step 308～309: the subscribe request that notification agent sends according to the subscriber is set up and is subscribed to entity, receives and subscribes to the subscription physical address that entity returns;
In the step 308, the subscription entity that the subscription name that notification agent is carried with subscribe request, keyword and filtercondition initialization are set up, and the propelling movement end-point addresses that subscribe request is carried registers subscribing to entity, related described propelling movement end points and subscribe to entity;
In the step 308, if the subscribe request that notification agent receives, when subscription name, keyword and the filtercondition that subscription name, keyword and the filtercondition that carries with the subscribe request of previous reception and the previous subscribe request that receives are carried is identical, the message sink physical address that then subscribe request that receives in the step 308 is carried, the propelling movement end points of setting up when receiving described previous subscribe request is registered, with a plurality of message sink entities and propelling movement associations.
In the step 309, notification agent is preserved and is subscribed to entity initialization subscription name and the mapping relations of subscribing to physical address according to the subscription physical address that the subscription entity returns.
Preferably, when notification agent receives the subscribe request of subscriber's transmission, also upgrading subscribing relationship according to subscribe request describes, described subscribing relationship is described the semantic prioritization of the subordinate subscribe request that comprises subscribe request and described subscribe request, and the keyword that carries of described subscribe request and described subordinate subscribe request.
Step 310～311: subscribe to and to set up the reasoning entity, with the filtercondition initialization reasoning entity that subscribe request is carried, receive the message that is successfully established that the reasoning entity returns;
Step 312～313: notification agent receives subscribes to the subscription success message that entity returns, and is forwarded to the subscriber.
Fig. 4 be distribution subscription system of the present invention for the handling process schematic diagram of notification message, described distribution subscription system comprises subscriber, notification agent, publisher, inner publisher, the subscription entity corresponding with described inner publisher, the propelling movement end points of setting up with message sink entity corresponding to described subscriber, by described notification agent of being set up by described subscriber and the reasoning entity of being set up by described subscription entity; As shown in Figure 4, described handling process for notification message may further comprise the steps:
Step 401: the publisher sends a notification message to notification agent;
Step 402～403: notification agent is set up inner publisher, receives the message that is successfully established that inner publisher returns;
In the step 402, when notification agent receives the notification message of publisher's transmission, the keyword that subscribe request and subordinate subscribe request were carried during the keyword traversal coupling subscribing relationship of carrying according to notification message was described, determine to carry subscribe request and/or subordinate subscribe request that keyword and notification message carry keyword match, and for subscribe request and/or the subordinate subscribe request of each described coupling, set up inner publisher.
Step 404: notification agent sends a notification message to inner publisher;
Concrete, notification agent is described according to subscribing relationship, the semantic prioritization of coupling subscribe request and/or subordinate subscribe request described in the determining step 403, according to described ordering, send a notification message to the inside publisher corresponding with the subscription entity of setting up according to described coupling subscribe request and/or subordinate subscribe request.
Step 405: when inner publisher determines that the load of subscription entity does not exceed setting threshold, send a notification message to the subscription entity corresponding with inner publisher;
Wherein, described subscription entity is subscription entity corresponding with described inner publisher in the step 403.
Wherein, the load of described subscription entity can be subscribed to entity per second notification message treating capacity and describe, and described threshold value is default according to data-handling capacity and the application scenarios of distribution subscription system.
Wherein, the mapping relations that described inner publisher subscribes to name and subscribes to physical address according to the subscription entity initialization that notification agent is preserved are determined the address of the subscription entity corresponding with inner publisher, and are sent a notification message to the subscription related with inner publisher.
Step 406: subscribe to entity and transmit notification message to the reasoning entity;
Step 407: when the reasoning entity determines that notification message satisfies the initialization filtercondition, send a notification message to the propelling movement end points of subscribing to entity associated:
Step 408: push end points send a notification message to the message sink entity that pushes associations;
Step 409: message sink entity transmission notification message is to the subscriber who sets up the message sink entity.
The above is preferred embodiment of the present invention only, is not for limiting protection scope of the present invention.
Claims (10)
1. distribution subscription system, it is characterized in that, described distribution subscription system comprises subscriber, notification agent, publisher, inner publisher, the subscription entity corresponding with described inner publisher, the propelling movement end points of setting up with message sink entity corresponding to described subscriber, by described notification agent of being set up by described subscriber and the reasoning entity of being set up by described subscription entity; Wherein,
Described notification agent is used for receiving the notification message of described publisher's transmission and being forwarded to described inner publisher;
Described inner publisher, be used for to determine described subscription entity when preload during not above setting threshold, described notification message is forwarded to described reasoning entity by described subscription entity;
Described reasoning entity, when be used for determining that notification message satisfies the initialization filtercondition of described reasoning entity, send a notification message to the propelling movement end points of described subscription entity associated;
Described propelling movement end points, be used for to transmit notification message to the message sink entity of described propelling movement associations;
Described message sink entity, the notification message that is used for receiving is sent to described subscriber.
2. distribution subscription system according to claim 1 is characterized in that,
Described notification agent also is used for upgrading subscribing relationship according to subscribe request and describes, and described subscribing relationship is described the semantic prioritization of the subscribe request that comprises subscribe request and subordinate, and the keyword that carries of the subscribe request of subscribe request and subordinate.
3. distribution subscription system according to claim 1 is characterized in that,
Described notification agent, after also being used for receiving the notification message of described publisher's transmission, describe according to subscribing relationship, determine to carry subscribe request and/or the subordinate subscribe request of the keyword match that keyword and described notification message carry, and sort by subscribe request and/or the subordinate subscribe request of semantic priority to coupling, described notification message is sent to inside publisher corresponding to subscription entity who sets up according to subscribe request and/or the subordinate subscribe request of coupling according to described ordering.
4. according to claim 1,2 or 3 described distribution subscription systems, it is characterized in that,
Described notification agent when also being used for receiving described subscriber and setting up the request message that pushes end points, is set up described propelling movement end points; The message sink physical address that described request message is carried is registered at the propelling movement end points, related described message sink entity and described propelling movement end points, and when the propelling movement end-point addresses that the described propelling movement end points of reception returns, be forwarded to described subscriber.
5. distribution subscription system according to claim 4 is characterized in that,
Described notification agent, after also being used for setting up described propelling movement end points, set up when receiving the subscribe request that described subscriber sends and subscribe to entity, the described subscription entity of subscription name, keyword and filtercondition initialization that carries with described subscribe request, and the propelling movement end-point addresses that subscribe request is carried registered related described propelling movement end points and described subscription entity at described subscription entity;
Described subscription entity also is used for setting up the reasoning entity, the described reasoning entity of filtercondition initialization that carries with described subscribe request.
6. a notification message processing method is applied to it is characterized in that in the distribution subscription system, and described notification message processing method comprises:
Described notification agent is forwarded to described inner publisher after receiving the notification message of described publisher's transmission;
Described inner publisher determine described subscription entity when preload does not exceed setting threshold, described notification message is forwarded to described reasoning entity by described subscription entity;
When described reasoning entity determines that described notification message satisfies the initialization filtercondition of described reasoning entity, described notification message is sent to propelling movement end points with described subscription entity associated;
Described propelling movement end points is forwarded to message sink entity with described propelling movement associations with described notification message, and by described message sink entity described notification message is sent to described subscriber.
7. method according to claim 6 is characterized in that, when described notification agent received the subscribe request of described subscriber's transmission, described method also comprised:
Described notification agent is upgraded subscribing relationship according to subscribe request and is described, described subscribing relationship is described the semantic prioritization of the subordinate subscribe request that comprises subscribe request and described subscribe request, and the keyword that carries of described subscribe request and described subordinate subscribe request.
8. method according to claim 6 is characterized in that, described notification agent is forwarded to described inner publisher after receiving the notification message of described publisher's transmission, comprising:
After described notification agent receives the notification message of described publisher's transmission, describe according to subscribing relationship, determine subscribe request and/or the subordinate subscribe request of the keyword match that carries with described notification message, and sort by subscribe request and/or the subordinate subscribe request of semantic priority to coupling, described notification message is sent to inside publisher corresponding to subscription entity who sets up according to subscribe request and/or the subordinate subscribe request of coupling according to described ordering.
9. according to claim 6,7 or 8 described methods, it is characterized in that, described method also comprises:
Described notification agent receives described subscriber when setting up the request message that pushes end points, sets up described propelling movement end points;
The message sink physical address that described notification agent is carried described request message is registered at described propelling movement end points, related described message sink entity and described propelling movement end points, and when receiving the propelling movement end-point addresses that described propelling movement end points returns, be forwarded to described subscriber.
10. method according to claim 9 is characterized in that, after described notification agent was set up described propelling movement end points, described method also comprised:
Described notification agent is when receiving the subscribe request of described subscriber's transmission, set up and subscribe to entity, the described subscription entity of subscription name, keyword and filtercondition initialization that carries with described subscribe request, and the propelling movement end-point addresses that described subscribe request is carried registered related described propelling movement end points and described subscription entity at described subscription entity;
Described subscription entity is set up the reasoning entity, the described reasoning entity of filtercondition initialization that carries with described subscribe request.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210562319.4A CN103037000B (en) | 2012-12-21 | 2012-12-21 | Publish-subscribe system and notification message processing method thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210562319.4A CN103037000B (en) | 2012-12-21 | 2012-12-21 | Publish-subscribe system and notification message processing method thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103037000A true CN103037000A (en) | 2013-04-10 |
| CN103037000B CN103037000B (en) | 2015-07-08 |
Family
ID=48023472
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210562319.4A Expired - Fee Related CN103037000B (en) | 2012-12-21 | 2012-12-21 | Publish-subscribe system and notification message processing method thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103037000B (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103581307A (en) * | 2013-10-17 | 2014-02-12 | 北京邮电大学 | Publishing/subscribing system based on clusters and method for guaranteeing reliability of publishing/subscribing system based on clusters |
| CN105323186A (en) * | 2014-06-20 | 2016-02-10 | 中兴通讯股份有限公司 | Load control method and apparatus for notification messages |
| CN108762621A (en) * | 2018-04-20 | 2018-11-06 | 维沃移动通信有限公司 | A kind of message display method and mobile terminal |
| CN111555959A (en) * | 2020-04-23 | 2020-08-18 | 西安震有信通科技有限公司 | User-defined control global popup notification processing method and device |
| CN113656201A (en) * | 2021-08-26 | 2021-11-16 | 北京宇系航通科技有限公司 | Message model with message proxy function and message processing method |
| CN114615049A (en) * | 2022-03-08 | 2022-06-10 | 斑马网络技术有限公司 | Authority checking method and system for event subscription |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101827123A (en) * | 2010-03-29 | 2010-09-08 | 北京掌中宽途科技有限公司 | Method and system for realizing mobile widget engine with SNS function |
| US20110110267A1 (en) * | 2009-11-09 | 2011-05-12 | Verisign, Inc. | Method and system for application level load balancing in a publish/subscribe message architecture |
| CN102710593A (en) * | 2012-03-19 | 2012-10-03 | 北京邮电大学 | Method, device and system for publishing message in graph mashup |
-
2012
- 2012-12-21 CN CN201210562319.4A patent/CN103037000B/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110110267A1 (en) * | 2009-11-09 | 2011-05-12 | Verisign, Inc. | Method and system for application level load balancing in a publish/subscribe message architecture |
| CN101827123A (en) * | 2010-03-29 | 2010-09-08 | 北京掌中宽途科技有限公司 | Method and system for realizing mobile widget engine with SNS function |
| CN102710593A (en) * | 2012-03-19 | 2012-10-03 | 北京邮电大学 | Method, device and system for publishing message in graph mashup |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103581307A (en) * | 2013-10-17 | 2014-02-12 | 北京邮电大学 | Publishing/subscribing system based on clusters and method for guaranteeing reliability of publishing/subscribing system based on clusters |
| CN105323186A (en) * | 2014-06-20 | 2016-02-10 | 中兴通讯股份有限公司 | Load control method and apparatus for notification messages |
| CN105323186B (en) * | 2014-06-20 | 2020-04-21 | 中兴通讯股份有限公司 | Notification message load control method and device |
| CN108762621A (en) * | 2018-04-20 | 2018-11-06 | 维沃移动通信有限公司 | A kind of message display method and mobile terminal |
| CN111555959A (en) * | 2020-04-23 | 2020-08-18 | 西安震有信通科技有限公司 | User-defined control global popup notification processing method and device |
| CN113656201A (en) * | 2021-08-26 | 2021-11-16 | 北京宇系航通科技有限公司 | Message model with message proxy function and message processing method |
| CN114615049A (en) * | 2022-03-08 | 2022-06-10 | 斑马网络技术有限公司 | Authority checking method and system for event subscription |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103037000B (en) | 2015-07-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103037000B (en) | Publish-subscribe system and notification message processing method thereof | |
| US8260333B2 (en) | Consolidating international short message service messages destined to multiple recipients | |
| CN102185801A (en) | Information processing method in instant messaging and instant messaging tool | |
| US20140364082A1 (en) | System And Method For Routing A Message, And A Computer Program Product | |
| CN104243611A (en) | Distribution thought based message service middleware system | |
| US20170359778A1 (en) | Multi-Channel Communications For Sending Push Notifications To Mobile Devices | |
| CN103095684A (en) | Method obtaining attention user aggregate information, device and system | |
| CN104539510A (en) | Multi-protocol-based information pushing system and method | |
| CN103548315A (en) | Method and apparatus for high performance low latency real time notification delivery | |
| CN113259415B (en) | Network message processing method and device and network server | |
| CN113747373B (en) | Message processing system, device and method | |
| US9026582B2 (en) | Device management methods and related apparatus for enhancing applicability of status messages in response to commands | |
| CN103888348A (en) | E-mail application system and method and device for transferring E-mails | |
| CN111124717A (en) | Message delivery method, system and computer storage medium | |
| CN101938383B (en) | On-line monitoring method and system of user account with multiple services as well as monitoring service system | |
| CN105335313A (en) | Basic data transmission method and apparatus | |
| US11700189B2 (en) | Method for performing task processing on common service entity, common service entity, apparatus and medium for task processing | |
| CN101355571B (en) | Method, apparatus and system for processing multimedia information | |
| CN103533001A (en) | Communication method and communication system based on HTTP multi-proxy, and intermediate proxy server | |
| CN101309458B (en) | Short message realizing method between multiple enterprises, system and equipment | |
| CN103368988B (en) | resource sharing method, system and device | |
| WO2021027474A1 (en) | Positioning assistance information broadcasting method, positioning server and ran node | |
| CN104536756A (en) | Method and device for sending and processing AllJoyn network message | |
| CN105814853A (en) | Method, device and system for improving qos | |
| US10003657B2 (en) | Data transmission processing method and apparatus |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20150708 Termination date: 20201221 |