CN103037000B - Publish-subscribe system and notification message processing method thereof - Google Patents
Publish-subscribe system and notification message processing method thereof Download PDFInfo
- Publication number
- CN103037000B CN103037000B CN201210562319.4A CN201210562319A CN103037000B CN 103037000 B CN103037000 B CN 103037000B CN 201210562319 A CN201210562319 A CN 201210562319A CN 103037000 B CN103037000 B CN 103037000B
- Authority
- CN
- China
- Prior art keywords
- entity
- subscribe request
- subscription
- propelling movement
- publisher
- 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.)
- Expired - Fee Related
Links
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
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, particularly relate 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 application is increasingly extensive, subscriber (Subscriber) sends subscribe request to notification agent, subscribe to the information needing to pay close attention to, and employing pulls (Pull) mode, obtain publisher (Publisher) and be sent to the notification message meeting subscribe request in the notification message of distribution subscription system.
Current, structure based information standard promotes tissue (OASIS, Organization for theAdvancement of Structured Information Standards) formulate network service notice (Web-Service Notification) standard distribution subscription system in, notification message initiatively can not be sent to subscriber, but, in the scene of increasing application distribution subscription system, as banker's rate business, stock business and online game operation business, in the urgent need to notification message is initiatively sent to subscriber, to meet the demand that notification message arrives in time,
Meanwhile, in the application scenarios needing a large amount of notification message of distribution subscription system process, how to balance distribution subscription system load, improving data processing performance, is also 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 the application scenarios demand of subscriber to satisfy the demand; Balance distribution subscription system load, to be suitable for the application scenarios needing to process a large amount of notification message simultaneously.
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, message sink entity, the propelling movement end points by described notification agent set up and the inferencing entity by described subscription entity set up corresponding with described subscriber set up by described subscriber; Wherein,
Described notification agent, for receiving the notification message of described publisher transmission and being forwarded to described inner publisher;
Described inner publisher, during for determining that the current loads of described subscription entity does not exceed setting threshold, is forwarded to described inferencing entity by described notification message by described subscription entity;
Described inferencing entity, during for determining that notification message meets the initialization filter condition of described inferencing entity, sends a notification message to the propelling movement end points with described subscription entity associated;
Described propelling movement end points, for forwarding notification message to the message sink entity with described propelling movement associations;
Described message sink entity, for being sent to described subscriber by the notification message of reception.
Preferably,
Described notification agent, also describe for upgrading subscribing relationship according to subscribe request, described subscribing relationship describes the semantic prioritization comprising the subscribe request of subscribe request and subordinate, and the keyword that the subscribe request of subscribe request and subordinate is carried.
Preferably,
Described notification agent, also for receive described publisher send notification message after, 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 by semantic priority, the subscribe request of coupling and/or subordinate subscribe request are sorted, described notification message is sent to inside publisher corresponding to the subscription entity set up according to subscribe request and/or the subordinate subscribe request of coupling according to described sequence.
Preferably,
Described notification agent, also for receive described subscriber set up push the request message of end points time, set up described propelling movement end points; Message sink physical address described request message carried is registered at propelling movement end points, associates 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, is forwarded to described subscriber.
Preferably,
Described notification agent, also for after setting up described propelling movement end points, set up when receiving the subscribe request of described subscriber transmission and subscribe to entity, entity is subscribed to described in the subscription name of carrying with described subscribe request, keyword and filter condition initialization, and the propelling movement end-point addresses of subscribe request being carried is registered at described subscription entity, associate described propelling movement end points and described subscription entity;
Described subscription entity, also for setting up inferencing entity, inferencing entity described in the filter condition initialization of carrying with described subscribe request.
Accordingly, present invention also offers a kind of notification message processing method, be applied in distribution subscription system, described notification message processing method comprises:
Described notification agent is forwarded to described inner publisher after receiving the notification message of described publisher transmission;
When described inner publisher determines that the current loads of described subscription entity does not exceed setting threshold, described notification message is forwarded to described inferencing entity by described subscription entity;
When described inferencing entity determines that described notification message meets the initialization filter condition of described inferencing entity, described notification message is sent to the propelling movement end points with described subscription entity associated;
Described notification message is forwarded to the message sink entity with described propelling movement associations by described propelling movement end points, 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 upgrades subscribing relationship according to subscribe request and describes, described subscribing relationship describes the semantic prioritization comprising the subordinate subscribe request of subscribe request and described subscribe request, and the keyword that described subscribe request and described subordinate subscribe request are carried.
Preferably, described notification agent is forwarded to described inner publisher, comprises after receiving the notification message of described publisher transmission:
After described notification agent receives the notification message of described publisher transmission, describe according to subscribing relationship, determine subscribe request and/or the subordinate subscribe request of the keyword match carried with described notification message, and by semantic priority, the subscribe request of coupling and/or subordinate subscribe request are sorted, described notification message is sent to inside publisher corresponding to the subscription entity set up according to subscribe request and/or the subordinate subscribe request of coupling according to described sequence.
Preferably, described notification message processing method also comprises:
Described notification agent receives described subscriber and sets up when pushing the request message of end points, sets up described propelling movement end points;
The message sink physical address that described request message is carried by described notification agent is registered at described propelling movement end points, associate 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 sets up described propelling movement end points, described notification message processing method also comprises:
Described notification agent is when receiving the subscribe request that described subscriber sends, set up and subscribe to entity, entity is subscribed to described in the subscription name of carrying with described subscribe request, keyword and filter condition initialization, and the propelling movement end-point addresses of described subscribe request being carried is registered at described subscription entity, associate described propelling movement end points and described subscription entity;
Described subscription entity sets up inferencing entity, inferencing entity described in the filter condition initialization of carrying with described subscribe request.
In technical scheme provided by the present invention, end points is pushed by setting up, the message sink entity of notification message to association of filter condition is met by pushing end points transmission, and forward described notification message to subscriber by message sink entity, the active achieving notification message sends, and meets and needs initiatively to send a notification message to the application scenarios demand of subscriber;
Meanwhile, inner publisher just sends a notification message when the current loads subscribing to entity does not exceed setting threshold to subscription entity, balances distribution subscription system load, improves 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 set up according to described coupling subscribe request, so, a large amount of subscribe request need be sent subscriber, and when there is subordinate relation in the subscribe request that subscriber sends, the subordinate relation between all subscribe request that need send can be specified in a subscribe request, by sending a subscribe request, subscribe to the notification message meeting multiple subscribe request filter conditions, improve the treatment effeciency of distribution subscription system.
Accompanying drawing explanation
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 the handling process schematic diagram of distribution subscription system of the present invention for subscribe request;
Fig. 4 is the handling process schematic diagram of distribution subscription system of the present invention for notification message.
Embodiment
Below in conjunction with drawings and the specific embodiments, the present invention is further detailed explanation.
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 distribution subscription system, described distribution subscription system comprises subscriber, notification agent, publisher, inner publisher, the subscription entity corresponding with described inner publisher, message sink entity, the propelling movement end points by described notification agent set up and the inferencing entity by described subscription entity set up corresponding with described subscriber set up by described subscriber, 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 transmission;
Here, before step 101, preferably, the flow process that described subscriber sets up the message sink entity corresponding with described subscriber is also comprised.
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, preferably, after described subscriber sets up described message sink entity, the flow process that described notification agent sets up described propelling movement end points is also comprised.
Described flow process comprises: described notification agent receives described subscriber and sets up when pushing the request message of end points, sets up and pushes end points; The message sink physical address that described request message is carried by described notification agent, register at propelling movement end points, associate 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 sets up propelling movement end points according to the request of described subscriber, preferably, also comprise described subscriber sends flow process from subscribe request to described notification agent, described subscribe request is carried described propelling movement end-point addresses, is subscribed to name, keyword and filter condition.
Here, described subscribe request and notification message can adopt resource description framework (RDF, ResourceDescription Framework) to describe.
Here, described notification agent, when receiving the subscribe request that described subscriber sends, preferably, also comprises described notification agent and sets up the flow process of subscribing to entity according to subscribe request.
Described flow process comprises:
When described notification agent receives the subscribe request of described subscriber transmission, set up and subscribe to entity, the subscription entity that the subscription name of carrying with described subscribe request, keyword and filter condition initialization are set up, and the propelling movement end-point addresses of described subscribe request being carried is in subscription registers entities, associates described propelling movement end points and described subscription entity; Receive the subscription address of subscribing to entity and returning, preserve the mapping relations that described subscription entity initialization is subscribed to name and subscribed to physical address.Wherein, the subscribe request that described other subscribers of notification agent receipt of subsequent send, and the subscribe request of described receipt of subsequent the subscription name, keyword and filter condition and the subscription name that the subscribe request of previous receipt is carried, the keyword that carry identical with filter condition time, the message sink physical address that described subsequent SUBSCRIBE request can be carried, the propelling movement end points set up when receiving described previous subscription request is registered, by multiple message sink entity and propelling movement associations.
Here, described notification agent is when receiving the subscribe request that described subscriber sends, preferably, also comprise the flow process upgrading subscribing relationship description according to the subscribe request received, described subscribing relationship describes the semantic prioritization comprising the subordinate subscribe request of subscribe request and described subscribe request, and the keyword that described subscribe request and described subordinate subscribe request are carried.
Wherein, described subscribe request carries the subordinate subscribe request of described subscribe request, the semantic prioritization that described subscribing relationship describes is determined according to the subordinate relation between described subscribe request and subordinate subscribe request, and described semantic prioritization setting comprises: the semantic priority of subscribe request is lower than the subscribe request of subscribe request institute subordinate.
Here, after described notification agent sets up described subscription entity according to subscribe request, preferably, the flow process that described subscription entity sets up inferencing entity is also comprised.
Described flow process comprises: described subscription entity sets up inferencing entity, and inferencing entity described in the filter condition initialization of carrying with subscribe request.
Here, described notification agent, when receiving the notification message that described publisher sends, preferably, also comprises described notification agent sets up inner publisher flow process according to notification message.
Described flow process comprises: when described notification agent receives the notification message of described publisher transmission, according to the keyword that subscribe request in the keyword traversal coupling subscribing relationship description that notification message carries and subordinate subscribe request are carried, determine to carry subscribe request and/or subordinate subscribe request that keyword and notification message carry keyword match, and for the subscribe request of each described coupling and/or subordinate subscribe request, set up inner publisher, so can ensure that described inner publisher can be corresponding one to one with the subscription entity set up according to described coupling subscribe request and/or subordinate subscribe request, 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 set up according to described coupling subscribe request and/or subordinate subscribe request.Such as, be provided with carry subscribe to name be respectively A, B and C subscribe request, the subscribe request A that publisher sends carries the subordinate subscribe request B and C that are subordinated to subscribe request A, and subordinate subscribe request C is subordinated to subordinate subscribe request B further, then the semantic prioritization of subscribe request in subscribing relationship describes of described subscribe request A, B and C is: subscribe request A > subscribe request B > subscribe request C.
Here, described notification agent is forwarded to described inner publisher, comprises after receiving the notification message of described publisher transmission:
Notification agent receives the notification message that publisher sends, describe according to subscribing relationship, determine subscribe request and/or the subordinate subscribe request of the keyword match carried with described notification message, and by semantic priority, the subscribe request of coupling and/or subordinate subscribe request are sorted, and according to semantic priority, the subscribe request of coupling and/or subordinate subscribe request are sorted, send a notification message to the inside publisher corresponding according to the subscription entity of described coupling subscribe request and/or the foundation of subordinate subscribe request.Such as, the keyword match that during the keyword that notification message carries and subscribing relationship describe, subscribe request A, B and C carry, and the semantic prioritization of subscribe request A, B and C is: subscribe request A > subscribe request B > subscribe request C, then notification agent order sends a notification message to subscribing to initialization and is called inside publisher corresponding to the subscription entity of A, B and C.
Step 102: when described inner publisher determines that the current loads of described subscription entity does not exceed setting threshold, is forwarded to described inferencing entity by described notification message by described subscription entity;
Here, the load of described subscription entity can be subscribed to entity notification message treating capacity per second and describe, and described threshold value is preset according to the data-handling capacity of distribution subscription system and application scenarios; Wherein, described inner publisher subscribes to name according to the subscription entity initialization that described notification agent is preserved and subscribes to the mapping relations of physical address, determine the address of the subscription entity associated with described inner publisher, to send described notification message to the subscription entity associated with described inner publisher, described subscription entity forwards the inferencing entity that described notice is set up to described subscription entity.
Step 103: when described inferencing entity determines that described notification message meets the initialization filter condition of described inferencing entity, is sent to the propelling movement end points with described subscription entity associated by described notification message;
Here, described filter condition can adopt the formal description of Boolean expression.
Step 104: described notification message is forwarded to the message sink entity with described propelling movement associations by described propelling movement end points, 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, message sink entity 24, the propelling movement end points 25 by described notification agent 22 set up and the inferencing entity 28 by described subscription entity 27 set up corresponding with described subscriber 21 set up by described subscriber 21; Wherein,
Described notification agent 22, for receiving the notification message of described publisher 23 transmission and being forwarded to described inner publisher 26;
Described inner publisher 26, during for determining that the current loads of described subscription entity 27 does not exceed setting threshold, is forwarded to described inferencing entity 28 by described notification message by described subscription entity 27;
Described inferencing entity 28, during for determining that notification message meets the initialization filter condition of described inferencing entity 28, sends described notification message to the propelling movement end points 25 associated with described subscription entity 27;
Described propelling movement end points 25, for forwarding notification message to the message sink entity 24 associated with described propelling movement end points 25;
Described message sink entity 24, for being sent to described subscriber 21 by the notification message of reception.
Preferably,
Described notification agent 22, also for receive described subscriber 21 send subscribe request time, upgrade subscribing relationship according to described subscribe request to describe, described subscribing relationship describes the semantic prioritization comprising the subordinate subscribe request of subscribe request and described subscribe request, and the keyword that described subscribe request and described subordinate subscribe request are carried.
Preferably,
Described notification agent 22, also for receive described publisher 23 send notification message after, describe according to subscribing relationship, determine subscribe request and/or the subordinate subscribe request of the keyword match carried with described notification message, and according to semantic priority, the carrying out that the subscribe request of coupling and/or subordinate subscribe request are carried out is sorted, according to described sequence, described notification message is sent to the inside publisher 26 of subscription entity 27 correspondence set up according to subscribe request and/or the subordinate subscribe request of described coupling.
Preferably,
Described notification agent 22, also for receive described subscriber 21 set up push the request message of end points 25 time, set up described propelling movement end points 25; Message sink entity 24 address of described request message being carried is registered at propelling movement end points 25, associate described message sink entity 24 and described propelling movement end points 25, and when receiving propelling movement end points 25 address that described propelling movement end points 25 returns, be forwarded to described subscriber 21.
Preferably,
Described notification agent 22, also for receive described subscriber 21 send subscribe request time, set up and subscribe to entity 27, entity 27 is subscribed to described in the subscription name of carrying with described subscribe request, keyword and filter condition initialization, and propelling movement end points 25 address of described subscribe request being carried is registered at described subscription entity 27, associate described propelling movement end points 25 and described subscription entity 27;
Described subscription entity 27, also for setting up inferencing entity 28, inferencing entity 28 described in the filter condition initialization of carrying with described subscribe request.
Fig. 3 is the handling process schematic diagram of distribution subscription system of the present invention for subscribe request, and described distribution subscription system comprises subscriber, notification agent, publisher, inner publisher, the subscription entity corresponding with described inner publisher, message sink entity, the propelling movement end points by described notification agent set up and the inferencing entity by described subscription entity set up corresponding with described subscriber set up by described subscriber; As shown in Figure 3, the described handling process for subscribe request comprises the following steps:
Step 301 ~ 302: subscriber sets up message sink entity, the message sink physical address that receipt message receiving entity returns:
Step 303: subscriber sends the request message set up and push end points to notification agent;
Wherein, described request message carries the address of message sink entity.
Step 304 ~ 306: notification agent is set up and pushed end points, receive the propelling movement end-point addresses pushing end points and return, and are forwarded to subscriber;
In step 304, the address of message sink entity is registered at propelling movement end points by notification agent, associates described propelling movement end points and message sink entity.
Step 307: subscriber sends subscribe request to notification agent;
Wherein, described subscribe request is carried and is pushed end-point addresses, subscribes to name, keyword and filter condition.
Step 308 ~ 309: notification agent is set up according to the subscribe request that subscriber sends and subscribed to entity, receives the subscription physical address subscribed to entity and return;
In step 308, the subscription entity that subscription name, keyword and filter condition initialization that notification agent is carried with subscribe request are set up, and the propelling movement end-point addresses of subscribe request being carried is registered at subscription entity, associates described propelling movement end points and subscribes to entity;
In step 308, if the subscribe request that notification agent receives, when the subscription name of carrying with the subscribe request of the subscription name that the subscribe request of previous receipt is carried, keyword and filter condition and previous receipt, keyword are identical with filter condition, the message sink physical address that carries of subscribe request then will received in step 308, the propelling movement end points set up when receiving described previous subscription request is registered, by multiple message sink entity and propelling movement associations.
In step 309, the subscription physical address that notification agent returns according to subscription entity, preserves and subscribes to the mapping relations that entity initialization subscribes to name and subscription physical address.
Preferably, when notification agent receives the subscribe request of subscriber's transmission, also upgrade subscribing relationship according to subscribe request to describe, described subscribing relationship describes the semantic prioritization comprising the subordinate subscribe request of subscribe request and described subscribe request, and the keyword that described subscribe request and described subordinate subscribe request are carried.
Step 310 ~ 311: subscribe to and set up inferencing entity, the filter condition initialization inferencing entity carried with subscribe request, what reception inferencing entity returned is successfully established message;
Step 312 ~ 313: notification agent receives the subscription success message subscribed to entity and return, and is forwarded to subscriber.
Fig. 4 is the handling process schematic diagram of distribution subscription system of the present invention for notification message, and described distribution subscription system comprises subscriber, notification agent, publisher, inner publisher, the subscription entity corresponding with described inner publisher, message sink entity, the propelling movement end points by described notification agent set up and the inferencing entity by described subscription entity set up corresponding with described subscriber set up by described subscriber; As shown in Figure 4, the described handling process for notification message comprises the following steps:
Step 401: publisher sends a notification message to notification agent;
Step 402 ~ 403: notification agent sets up inner publisher, what receive that inner publisher returns is successfully established message;
In step 402, when notification agent receives the notification message of publisher's transmission, according to the keyword that subscribe request in the keyword traversal coupling subscribing relationship description that notification message carries and subordinate subscribe request are carried, determine to carry subscribe request and/or subordinate subscribe request that keyword and notification message carry keyword match, and for the subscribe request of each described coupling and/or subordinate subscribe request, set up inner publisher.
Step 404: notification agent sends a notification message to inner publisher;
Concrete, notification agent describes according to subscribing relationship, the semantic prioritization of subscribe request and/or subordinate subscribe request is mated described in determining step 403, according to described sequence, send a notification message to the inside publisher corresponding with the subscription entity set 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 step 403.
Wherein, the load of described subscription entity can be subscribed to entity notification message treating capacity per second and describe, and described threshold value is preset according to the data-handling capacity of distribution subscription system and application scenarios.
Wherein, described inner publisher subscribes to name according to the subscription entity initialization that notification agent is preserved and subscribes to the mapping relations of physical address, determines the address of the subscription entity corresponding with inner publisher, and sends a notification message to the subscription associated with inner publisher.
Step 406: subscribe to entity and forward notification message to inferencing entity;
Step 407: when inferencing entity determination notification message meets initialization filter condition, sends a notification message to the propelling movement end points with subscription entity associated:
Step 408: push end points and send a notification message to the message sink entity with propelling movement associations;
Step 409: message sink entity transmission notification message is to the subscriber setting up message sink entity.
The above, be only preferred embodiment of the present invention, be not intended to limit protection scope of the present invention.
Claims (7)
1. a 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, message sink entity, the propelling movement end points by described notification agent set up and the inferencing entity by described subscription entity set up corresponding with described subscriber set up by described subscriber; Wherein,
Described notification agent, for receiving the notification message of described publisher transmission and being forwarded to described inner publisher;
Described inner publisher, during for determining that the current loads of described subscription entity does not exceed setting threshold, is forwarded to described inferencing entity by described notification message by described subscription entity;
Described inferencing entity, during for determining that notification message meets the initialization filter condition of described inferencing entity, sends a notification message to the propelling movement end points with described subscription entity associated;
Described propelling movement end points, for forwarding notification message to the message sink entity with described propelling movement associations;
Described message sink entity, for being sent to described subscriber by the notification message of reception;
Described notification agent is also for when receiving the subscribe request that described subscriber sends, set up and subscribe to entity, the subscription entity that the subscription name of carrying with described subscribe request, keyword and filter condition initialization are set up, and the propelling movement end-point addresses of described subscribe request being carried is in subscription registers entities, associates described propelling movement end points and described subscription entity; Receive the subscription address of subscribing to entity and returning, preserve the mapping relations that described subscription entity initialization is subscribed to name and subscribed to physical address;
Described notification agent, also for receive described subscriber set up push the request message of end points time, set up described propelling movement end points; Message sink physical address described request message carried is registered at propelling movement end points, associates 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, is forwarded to described subscriber;
Described notification agent, also for receive described publisher send notification message after, 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 by semantic priority, the subscribe request of coupling and/or subordinate subscribe request are sorted, described notification message is sent to inside publisher corresponding to the subscription entity set up according to subscribe request and/or the subordinate subscribe request of coupling according to described sequence.
2. distribution subscription system according to claim 1, is characterized in that,
Described notification agent, also describe for upgrading subscribing relationship according to subscribe request, described subscribing relationship describes the semantic prioritization comprising the subscribe request of subscribe request and subordinate, and the keyword that the subscribe request of subscribe request and subordinate is carried.
3. distribution subscription system according to claim 1, is characterized in that,
Described notification agent, also for after setting up described propelling movement end points, set up when receiving the subscribe request of described subscriber transmission and subscribe to entity, entity is subscribed to described in the subscription name of carrying with described subscribe request, keyword and filter condition initialization, and the propelling movement end-point addresses of subscribe request being carried is registered at described subscription entity, associate described propelling movement end points and described subscription entity;
Described subscription entity, also for setting up inferencing entity, inferencing entity described in the filter condition initialization of carrying with described subscribe request.
4. a notification message processing method, be applied in 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, message sink entity, the propelling movement end points by described notification agent set up and the inferencing entity by described subscription entity set up corresponding with described subscriber set up by described subscriber; Described notification message processing method comprises:
Described notification agent is forwarded to described inner publisher after receiving the notification message of described publisher transmission;
When described inner publisher determines that the current loads of described subscription entity does not exceed setting threshold, described notification message is forwarded to described inferencing entity by described subscription entity;
When described inferencing entity determines that described notification message meets the initialization filter condition of described inferencing entity, described notification message is sent to the propelling movement end points with described subscription entity associated;
Described notification message is forwarded to the message sink entity with described propelling movement associations by described propelling movement end points, and by described message sink entity, described notification message is sent to described subscriber;
Described notification agent is forwarded to described inner publisher, comprises after receiving the notification message of described publisher transmission:
After described notification agent receives the notification message of described publisher transmission, describe according to subscribing relationship, determine subscribe request and/or the subordinate subscribe request of the keyword match carried with described notification message, and by semantic priority, the subscribe request of coupling and/or subordinate subscribe request are sorted, described notification message is sent to inside publisher corresponding to the subscription entity set up according to subscribe request and/or the subordinate subscribe request of coupling according to described sequence.
5. method according to claim 4, is characterized in that, when described notification agent receives the subscribe request of described subscriber transmission, described method also comprises:
Described notification agent upgrades subscribing relationship according to subscribe request and describes, described subscribing relationship describes the semantic prioritization comprising the subordinate subscribe request of subscribe request and described subscribe request, and the keyword that described subscribe request and described subordinate subscribe request are carried.
6. the method according to claim 4 or 5, is characterized in that, described method also comprises:
Described notification agent receives described subscriber and sets up when pushing the request message of end points, sets up described propelling movement end points;
The message sink physical address that described request message is carried by described notification agent is registered at described propelling movement end points, associate 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.
7. method according to claim 6, is characterized in that, after described notification agent sets up described propelling movement end points, described method also comprises:
Described notification agent is when receiving the subscribe request that described subscriber sends, set up and subscribe to entity, entity is subscribed to described in the subscription name of carrying with described subscribe request, keyword and filter condition initialization, and the propelling movement end-point addresses of described subscribe request being carried is registered at described subscription entity, associate described propelling movement end points and described subscription entity;
Described subscription entity sets up inferencing entity, inferencing entity described in the filter condition initialization of carrying 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 CN103037000A (en) | 2013-04-10 |
| CN103037000B true 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) |
Families Citing this family (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 |
| CN105323186B (en) * | 2014-06-20 | 2020-04-21 | 中兴通讯股份有限公司 | Notification message load control method and device |
| CN108762621B (en) * | 2018-04-20 | 2021-09-21 | 维沃移动通信有限公司 | 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 (2)
| 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 |
| CN102710593A (en) * | 2012-03-19 | 2012-10-03 | 北京邮电大学 | Method, device and system for publishing message in graph mashup |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8982882B2 (en) * | 2009-11-09 | 2015-03-17 | Verisign, Inc. | Method and system for application level load balancing in a publish/subscribe message architecture |
-
2012
- 2012-12-21 CN CN201210562319.4A patent/CN103037000B/en not_active Expired - Fee Related
Patent Citations (2)
| 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 |
| CN102710593A (en) * | 2012-03-19 | 2012-10-03 | 北京邮电大学 | Method, device and system for publishing message in graph mashup |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103037000A (en) | 2013-04-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103037000B (en) | Publish-subscribe system and notification message processing method thereof | |
| US8150385B1 (en) | Automated reply messages among end user communication devices | |
| CN105991731A (en) | Method for obtaining information, intelligent terminal and server side | |
| US8260333B2 (en) | Consolidating international short message service messages destined to multiple recipients | |
| CN102739560B (en) | Instant communication method, system and device | |
| CN103795689A (en) | Resource subscription method and device | |
| CN104023020A (en) | TypeB message subscription and push system for mobile equipment and corresponding method | |
| US20140364082A1 (en) | System And Method For Routing A Message, And A Computer Program Product | |
| CN102185801A (en) | Information processing method in instant messaging and instant messaging tool | |
| CN112788074A (en) | Data transmitting method, processing method, receiving method and equipment and storage medium | |
| CN103618667A (en) | Information transfer method, access gateway and system | |
| CN103548315A (en) | Method and apparatus for high performance low latency real time notification delivery | |
| CN104539510A (en) | Multi-protocol-based information pushing system and method | |
| US9026582B2 (en) | Device management methods and related apparatus for enhancing applicability of status messages in response to commands | |
| JP2014123363A5 (en) | ||
| CN101355571B (en) | Method, apparatus and system for processing multimedia information | |
| US20140068001A1 (en) | Intermediate proxy server, communication method, and communication system based on http multi-level proxy | |
| CN101309458B (en) | Short message realizing method between multiple enterprises, system and equipment | |
| CN105743772A (en) | Message processing method and system | |
| CN109429215B (en) | Data transmission method, related device and computer readable storage medium | |
| CN105814853A (en) | Method, device and system for improving qos | |
| CN104683253A (en) | Dynamic load balancing method for unified communication system | |
| CN106851526B (en) | Method and equipment for processing MTC (machine type communication) message | |
| CN104579914A (en) | Method and device for subscribing to state for system | |
| 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 |
Granted publication date: 20150708 Termination date: 20201221 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |