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
- subscription
- entity
- endpoint
- notification
- push
- 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
- 238000003672 processing method Methods 0.000 title claims abstract description 16
- 238000001914 filtration Methods 0.000 claims abstract description 25
- 238000000034 method Methods 0.000 claims description 22
- 239000003795 chemical substances by application Substances 0.000 description 49
- 239000004973 liquid crystal related substance Substances 0.000 description 8
- 239000000463 material Substances 0.000 description 8
- 238000013507 mapping Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 238000004891 communication Methods 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
Images
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 network communication technologies, and in particular, to a publish-subscribe system and a notification message processing method thereof.
Background
The publication subscription (Publish/Subscribe) system based on the Web Service (Web Service) technology is increasingly widely applied, a Subscriber (Subscriber) sends a subscription request to a notification agent to Subscribe information needing attention, and acquires a notification message meeting the subscription request in the notification messages sent to the publication subscription system by the Publisher (Publisher) in a Pull (Pull) mode.
Currently, in a publish-subscribe system based on a Web-Service Notification (Web-Service Notification) standard formulated by an Organization for facilitating Structured Information Standards (OASIS), a Notification message is not actively sent to a subscriber, but in a scene where a publish-subscribe system is increasingly applied, such as bank exchange rate Service, stock Service and network game operation Service, it is urgently needed to actively send the Notification message to the subscriber so as to meet the requirement that the Notification message arrives in time;
meanwhile, in an application scenario where a publish-subscribe system is required to process a large number of notification messages, how to balance the load of the publish-subscribe system and improve data processing performance is also an urgent problem to be solved.
Disclosure of Invention
In view of the above, the main objective of the present invention is to provide a publish-subscribe system and a notification message processing method thereof, so as to meet the application scenario requirement of actively sending a notification message to a subscriber; meanwhile, the load of the publish-subscribe system is balanced, so that the publish-subscribe system is suitable for application scenarios needing to process a large number of notification messages.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
the invention provides a publishing and subscribing system, which comprises a subscriber, a notification agency, a publisher, an internal publisher, a subscription entity corresponding to the internal publisher, a message receiving entity corresponding to the subscriber and established by the subscriber, a push endpoint established by the notification agency, and an inference entity established by the subscription entity; wherein,
the notification agent is used for receiving the notification message sent by the publisher and forwarding the notification message to the internal publisher;
the internal publisher is used for forwarding the notification message to the inference entity through the subscription entity when determining that the current load of the subscription entity does not exceed a set threshold;
the reasoning entity is used for sending the notification message to a pushing endpoint associated with the subscription entity when determining that the notification message meets the initialization filtering condition of the reasoning entity;
the push endpoint is used for forwarding a notification message to a message receiving entity associated with the push endpoint;
and the message receiving entity is used for sending the received notification message to the subscriber.
Preferably, the first and second liquid crystal materials are,
the notification agent is further configured to update a subscription relationship description according to the subscription request, where the subscription relationship description includes semantic priority ordering of the subscription request and the subordinate subscription request, and keywords carried by the subscription request and the subordinate subscription request.
Preferably, the first and second liquid crystal materials are,
the notification agent is further configured to determine, after receiving the notification message sent by the publisher, a subscription request and/or an affiliated subscription request carrying a keyword matched with the keyword carried by the notification message according to the subscription relationship description, rank the matched subscription request and/or affiliated subscription request according to semantic priority, and send the notification message to an internal publisher corresponding to a subscription entity established according to the matched subscription request and/or affiliated subscription request according to the ranking.
Preferably, the first and second liquid crystal materials are,
the notification agent is further configured to establish a push endpoint when receiving a request message for establishing the push endpoint by the subscriber; registering a message receiving entity address carried by the request message at a pushing endpoint, associating the message receiving entity with the pushing endpoint, and forwarding the message receiving entity and the pushing endpoint to the subscriber when receiving the pushing endpoint address returned by the pushing endpoint.
Preferably, the first and second liquid crystal materials are,
the notification agent is further configured to establish a subscription entity when receiving a subscription request sent by the subscriber after establishing the push endpoint, initialize the subscription entity with a subscription name, a keyword and a filtering condition carried in the subscription request, register a push endpoint address carried in the subscription request in the subscription entity, and associate the push endpoint with the subscription entity;
the subscription entity is also used for establishing an inference entity and initializing the inference entity according to the filter condition carried by the subscription request.
Correspondingly, the invention also provides a notification message processing method, which is applied to a publish-subscribe system and comprises the following steps:
after receiving the notification message sent by the publisher, the notification agent forwards the notification message to the internal publisher;
when the internal publisher determines that the current load of the subscription entity does not exceed a set threshold value, the notification message is forwarded to the inference entity through the subscription entity;
when the inference entity determines that the notification message meets the initialization filtering condition of the inference entity, the inference entity sends the notification message to a push endpoint associated with the subscription entity;
the push endpoint forwards the notification message to a message receiving entity associated with the push endpoint, and the message receiving entity sends the notification message to the subscriber.
Preferably, the notification message processing method further includes:
and the notification agent updates subscription relation description according to the subscription request, wherein the subscription relation description comprises semantic priority ordering of the subscription request and subordinate subscription requests of the subscription request, and keywords carried by the subscription request and the subordinate subscription requests.
Preferably, after receiving the notification message sent by the publisher, the notification broker forwards the notification message to the internal publisher, where the notification message includes:
and after receiving the notification message sent by the publisher, the notification agent determines a subscription request and/or an affiliated subscription request matched with the keywords carried by the notification message according to the subscription relationship description, sorts the matched subscription request and/or affiliated subscription request according to semantic priority, and sends the notification message to an internal publisher corresponding to a subscription entity established according to the matched subscription request and/or affiliated subscription request according to the sorting.
Preferably, the notification message processing method further includes:
when the notification agent receives a request message for establishing a push endpoint by the subscriber, establishing the push endpoint;
and the notification agent registers the message receiving entity address carried by the request message at the push endpoint, associates the message receiving entity with the push endpoint, and forwards the message receiving entity and the push endpoint to the subscriber when receiving the push endpoint address returned by the push endpoint.
Preferably, after the notification agent establishes the push endpoint, the notification message processing method further includes:
the notification agent establishes a subscription entity when receiving a subscription request sent by the subscriber, initializes the subscription entity by a subscription name, a keyword and a filtering condition carried by the subscription request, registers a push endpoint address carried by the subscription request in the subscription entity, and associates the push endpoint and the subscription entity;
and the subscription entity establishes an inference entity, and initializes the inference entity according to the filter condition carried by the subscription request.
In the technical scheme provided by the invention, the notification message meeting the filtering condition is sent to the associated message receiving entity through the push endpoint by establishing the push endpoint and is forwarded to the subscriber through the message receiving entity, so that the active sending of the notification message is realized, and the application scene requirement of actively sending the notification message to the subscriber is met;
meanwhile, the internal publisher sends the notification message to the subscription entity when the current load of the subscription entity does not exceed the set threshold, so that the load of the publishing and subscription system is balanced, and the data processing performance is improved;
preferably, the notification agent sends the notification message to the internal publisher corresponding to the subscription entity established according to the matching subscription request according to the semantic priority ranking of the matching subscription request, so that when the subscriber needs to send a large number of subscription requests and the subscription requests sent by the subscriber have an affiliation, the affiliation among all the subscription requests needing to be sent can be specified in one subscription request, and the notification message meeting the filtering conditions of a plurality of subscription requests can be subscribed by sending one subscription request, thereby improving the processing efficiency of the publish-subscribe system.
Drawings
FIG. 1 is a schematic flow chart of an implementation of a notification message processing method according to the present invention;
FIG. 2 is a schematic diagram of the structure of the publish-subscribe system of the present invention;
FIG. 3 is a schematic view of the processing flow of the publish-subscribe system according to the present invention;
fig. 4 is a schematic view of the processing flow of the publish-subscribe system for notification messages according to the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and specific embodiments.
Fig. 1 is a schematic diagram of an implementation flow of a notification message processing method of the present invention, where the notification message processing method is applied to a publish-subscribe system, where the publish-subscribe system includes a subscriber, a notification broker, a publisher, an internal publisher, a subscription entity corresponding to the internal publisher, a message receiving entity corresponding to the subscriber established by the subscriber, a push endpoint established by the notification broker, and an inference entity established by the subscription entity, and as shown in fig. 1, the notification message processing method includes:
step 101: after receiving the notification message sent by the publisher, the notification agent forwards the notification message to the internal publisher;
here, before step 101, it is preferable that the method further includes a process of the subscriber establishing a message receiving entity corresponding to the subscriber.
The process comprises the following steps: and the subscriber establishes a message receiving entity corresponding to the subscriber and receives a message receiving entity address returned by the message receiving entity.
Here, it is preferable that after the subscriber establishes the message receiving entity, a flow of the notification agent establishing the push endpoint is further included.
The process comprises the following steps: when the notification agent receives a request message for establishing a push endpoint by the subscriber, establishing the push endpoint; and the notification agent registers the message receiving entity address carried by the request message at a pushing endpoint, associates the pushing endpoint with the message receiving entity, and forwards the message receiving entity address to the subscriber when receiving the pushing endpoint address returned by the pushing endpoint.
Here, after the notification agent establishes a push endpoint according to the request of the subscriber, preferably, the method further includes a process in which the subscriber sends a subscription request to the notification agent, where the subscription request carries the push endpoint address, the subscription name, the keyword, and the filtering condition.
Here, the subscription request and the notification message may be described using a Resource Description Framework (RDF).
Here, when the notification agent receives the subscription request sent by the subscriber, it is preferable that the notification agent further includes a process of establishing a subscription entity according to the subscription request.
The process comprises the following steps:
when the notification agent receives a subscription request sent by the subscriber, a subscription entity is established, the established subscription entity is initialized according to a subscription name, a keyword and a filtering condition carried by the subscription request, a pushing endpoint address carried by the subscription request is registered in the subscription entity, and the pushing endpoint and the subscription entity are associated; and receiving a subscription address returned by a subscription entity, and storing the mapping relation between the initialized subscription name of the subscription entity and the address of the subscription entity. The notification agent receives subscription requests sent by other subscribers in a subsequent manner, and when the subscription name, the keyword and the filtering condition carried by the subscription requests received in the subsequent manner are the same as the subscription name, the keyword and the filtering condition carried by the subscription requests received in the prior manner, the notification agent can register the message receiving entity address carried by the subscription requests in the subsequent manner with a push endpoint established when the subscription requests are received in the prior manner, and associate a plurality of message receiving entities with the push endpoint.
Here, when receiving the subscription request sent by the subscriber, the notification broker preferably further includes a process of updating a subscription relationship description according to the received subscription request, where the subscription relationship description includes semantic priority rankings of the subscription request and subordinate subscription requests of the subscription request, and keywords carried by the subscription request and the subordinate subscription requests.
Wherein the subscription request carries an affiliated subscription request of the subscription request, the semantic priority ordering described by the subscription relationship is determined according to the affiliation between the subscription request and the affiliated subscription request, and the setting of the semantic priority ordering includes: the subscription request semantic priority is lower than the subscription request to which the subscription request pertains.
Here, after the notification agent establishes the subscription entity according to the subscription request, it preferably further includes a process of establishing an inference entity by the subscription entity.
The process comprises the following steps: and the subscription entity establishes an inference entity and initializes the inference entity according to the filter condition carried by the subscription request.
Here, when the notification broker receives the notification message sent by the publisher, it is preferable that the notification broker further includes a process in which the notification broker establishes an internal publisher according to the notification message.
The process comprises the following steps: when the notification agent receives the notification message sent by the publisher, determining a subscription request and/or a subordinate subscription request carrying a keyword matched with the notification message carrying the keyword according to the keyword carried by the notification message traversing and matching the keywords carried by the subscription request and the subordinate subscription request in the subscription relationship description, and for each of said matching subscription requests and/or subordinate subscription requests, establishing an internal publisher, this ensures that the internal publishers can have a one-to-one correspondence with the subscribing entities established from the matching subscription request and/or subordinate subscription request, and sending a notification message to an internal publisher corresponding to the subscription entity established according to the matching subscription request and/or the subordinate subscription request in a semantic priority sequence according to the matching subscription request and/or the subordinate subscription request. For example, there are subscription requests with subscription names A, B and C, respectively, a subscription request a sent by a publisher carries subordinate subscription requests B and C subordinate to the subscription request a, and the subordinate subscription request C is further subordinate to the subordinate subscription request B, then the semantic priority ordering of the subscription requests A, B and C in the subscription relationship description is as follows: subscription request a > subscription request B > subscription request C.
Here, after receiving the notification message sent by the publisher, the notification broker forwards the notification message to the internal publisher, including:
the notification agent receives notification messages sent by publishers, determines subscription requests and/or subordinate subscription requests matched with keywords carried by the notification messages according to the subscription relationship description, sorts the matched subscription requests and/or subordinate subscription requests according to semantic priority, sorts the matched subscription requests and/or subordinate subscription requests according to the semantic priority, and sends the notification messages to internal publishers corresponding to subscription entities established according to the matched subscription requests and/or subordinate subscription requests. For example, the keywords carried by the notification message match the keywords carried by the subscription requests A, B and C in the subscription relationship description, and the semantic priorities of the subscription requests A, B and C are: subscription request a > subscription request B > subscription request C, the notification broker sends notification messages sequentially to the internal publishers corresponding to the subscribing entities with initial subscription names A, B and C.
Step 102: when the internal publisher determines that the current load of the subscription entity does not exceed a set threshold value, the notification message is forwarded to the inference entity through the subscription entity;
here, the load of the subscription entity may be described by the notification message processing amount per second of the subscription entity, and the threshold is preset according to the data processing capability and the application scenario of the publish-subscribe system; the internal publisher determines the address of the subscription entity associated with the internal publisher according to the mapping relation between the initialized subscription name of the subscription entity and the address of the subscription entity stored by the notification agent, so as to send the notification message to the subscription entity associated with the internal publisher, and the subscription entity forwards the notification to the inference entity established by the subscription entity.
Step 103: when the inference entity determines that the notification message meets the initialization filtering condition of the inference entity, the inference entity sends the notification message to a push endpoint associated with the subscription entity;
here, the filtering condition may be described in the form of a boolean expression.
Step 104: the push endpoint forwards the notification message to a message receiving entity associated with the push endpoint, and the message receiving entity sends the notification message to the subscriber.
Here, the subscriber is a subscriber corresponding to the message receiving entity.
Fig. 2 is a schematic structural diagram of a publish-subscribe system according to the present invention, and as shown in fig. 2, the publish-subscribe system includes a subscriber 21, a notification broker 22, a publisher 23, an internal publisher 26, a subscription entity 27 corresponding to the internal publisher 26, a message receiving entity 24 corresponding to the subscriber 21 and established by the subscriber 21, a push endpoint 25 established by the notification broker 22, and an inference entity 28 established by the subscription entity 27; wherein,
the notification agent 22 is configured to receive the notification message sent by the publisher 23 and forward the notification message to the internal publisher 26;
the internal publisher 26 is configured to forward the notification message to the inference entity 28 through the subscription entity 27 when determining that the current load of the subscription entity 27 does not exceed a set threshold;
the inference entity 28 is configured to send the notification message to the push endpoint 25 associated with the subscription entity 27 when determining that the notification message satisfies the initialized filtering condition of the inference entity 28;
the push endpoint 25 is configured to forward a notification message to a message receiving entity 24 associated with the push endpoint 25;
the message receiving entity 24 is configured to send the received notification message to the subscriber 21.
Preferably, the first and second liquid crystal materials are,
the notification agent 22 is further configured to, when receiving a subscription request sent by the subscriber 21, update a subscription relationship description according to the subscription request, where the subscription relationship description includes semantic priority ordering of subscription requests and subordinate subscription requests of the subscription requests, and keywords carried by the subscription requests and the subordinate subscription requests.
Preferably, the first and second liquid crystal materials are,
the notification broker 22 is further configured to, after receiving the notification message sent by the publisher 23, determine, according to the subscription relationship description, a subscription request and/or an affiliated subscription request that matches the keyword carried in the notification message, rank the matched subscription request and/or affiliated subscription request according to the semantic priority, and send, according to the rank, the notification message to the internal publisher 26 corresponding to the subscription entity 27 that is established according to the matched subscription request and/or affiliated subscription request.
Preferably, the first and second liquid crystal materials are,
the notification agent 22 is further configured to establish a push endpoint 25 when receiving a request message for establishing the push endpoint 25 by the subscriber 21; registering the address of the message receiving entity 24 carried by the request message at a push endpoint 25, associating the message receiving entity 24 with the push endpoint 25, and forwarding the address to the subscriber 21 when receiving the address of the push endpoint 25 returned by the push endpoint 25.
Preferably, the first and second liquid crystal materials are,
the notification broker 22 is further configured to, when receiving a subscription request sent by the subscriber 21, establish a subscription entity 27, initialize the subscription entity 27 with a subscription name, a keyword, and a filtering condition carried in the subscription request, register a push endpoint 25 address carried in the subscription request in the subscription entity 27, and associate the push endpoint 25 and the subscription entity 27;
the subscription entity 27 is further configured to establish an inference entity 28, and initialize the inference entity 28 with the filter condition carried in the subscription request.
FIG. 3 is a schematic view of a processing flow of a publish-subscribe system according to the present invention for a subscription request, where the publish-subscribe system includes a subscriber, a notification broker, a publisher, an internal publisher, a subscription entity corresponding to the internal publisher, a message receiving entity corresponding to the subscriber established by the subscriber, a push endpoint established by the notification broker, and an inference entity established by the subscription entity; as shown in fig. 3, the processing flow for the subscription request includes the following steps:
step 301-302: the subscriber establishes a message receiving entity, receives the address of the message receiving entity returned by the message receiving entity:
step 303: a subscriber sends a request message for establishing a push endpoint to a notification agent;
wherein the request message carries an address of a message receiving entity.
Step 304-306: the notification agent establishes a pushing endpoint, receives a pushing endpoint address returned by the pushing endpoint and forwards the pushing endpoint address to the subscriber;
in step 304, the notification broker registers the address of the message receiving entity with the push endpoint, associating the push endpoint with the message receiving entity.
Step 307: a subscriber sends a subscription request to a notification agent;
the subscription request carries a push endpoint address, a subscription name, keywords and filtering conditions.
Step 308-309: the notification agent establishes a subscription entity according to a subscription request sent by a subscriber and receives a subscription entity address returned by the subscription entity;
in step 308, the notification agent initializes the established subscription entity with the subscription name, the keyword and the filtering condition carried by the subscription request, registers the push endpoint address carried by the subscription request in the subscription entity, and associates the push endpoint and the subscription entity;
in step 308, if the subscription request received by the notification agent is the same as the subscription name, the keyword, and the filtering condition carried by the previously received subscription request and the subscription name, the keyword, and the filtering condition carried by the previously received subscription request, the message receiving entity address carried by the subscription request received in step 308 is registered with the push endpoint established when the previously received subscription request is received, and a plurality of message receiving entities are associated with the push endpoint.
In step 309, the notification agent stores the mapping relationship between the initialized subscription name and the address of the subscription entity according to the address of the subscription entity returned by the subscription entity.
Preferably, when the notification agent receives a subscription request sent by a subscriber, the notification agent further updates a subscription relationship description according to the subscription request, where the subscription relationship description includes semantic priority ordering of the subscription request and subordinate subscription requests of the subscription request, and keywords carried by the subscription request and the subordinate subscription requests.
Step 310-311: subscribing and establishing a reasoning entity, initializing the reasoning entity according to the filtering condition carried by the subscription request, and receiving a success establishing message returned by the reasoning entity;
step 312-313: and the notification agent receives a subscription success message returned by the subscription entity and forwards the message to the subscriber.
FIG. 4 is a schematic view of a processing flow of a publish-subscribe system for notification messages according to the present invention, where the publish-subscribe system includes a subscriber, a notification broker, a publisher, an internal publisher, a subscription entity corresponding to the internal publisher, a message receiving entity corresponding to the subscriber established by the subscriber, a push endpoint established by the notification broker, and an inference entity established by the subscription entity; as shown in fig. 4, the process flow for notification message includes the following steps:
step 401: the publisher sends a notification message to the notification agent;
step 402-403: informing the agent to establish the internal publisher, and receiving a successful establishment message returned by the internal publisher;
in step 402, when the notification agent receives the notification message sent by the publisher, the notification agent determines the subscription request and/or the subordinate subscription request carrying the keyword matched with the notification message carrying the keyword according to the keyword traversal matching subscription relation description carried by the notification message and the keyword carried by the subscription request and the subordinate subscription request, and establishes an internal publisher according to each matched subscription request and/or subordinate subscription request.
Step 404: the notification agent sends a notification message to the internal publisher;
specifically, the notification agent determines semantic priority ranking of the matching subscription request and/or the subordinate subscription request in step 403 according to the subscription relationship description, and sends the notification message to the internal publisher corresponding to the subscription entity established according to the matching subscription request and/or the subordinate subscription request according to the ranking.
Step 405: when the internal publisher determines that the load of the subscription entity does not exceed a set threshold, sending a notification message to the subscription entity corresponding to the internal publisher;
wherein the subscription entity is the subscription entity corresponding to the internal publisher in step 403.
The load of the subscription entity can be described by the notification message processing amount of the subscription entity per second, and the threshold is preset according to the data processing capacity and the application scene of the publish-subscribe system.
The internal publisher determines the address of the subscription entity corresponding to the internal publisher according to the mapping relation between the initialized subscription name of the subscription entity and the address of the subscription entity stored by the notification agent, and sends a notification message to the subscription associated with the internal publisher.
Step 406: the subscription entity forwards the notification message to the inference entity;
step 407: when the inference entity determines that the notification message meets the initialization filtering condition, sending the notification message to a push endpoint associated with the subscription entity:
step 408: the push endpoint sends a notification message to a message receiving entity associated with the push endpoint;
step 409: the message receiving entity transmits a notification message to the subscriber who established the message receiving entity.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.
Claims (10)
1. A publish-subscribe system comprising a subscriber, a notification broker, a publisher, an internal publisher, a subscription entity corresponding to the internal publisher, a message receiving entity established by the subscriber corresponding to the subscriber, a push endpoint established by the notification broker, and an inference entity established by the subscription entity; wherein,
the notification agent is used for receiving the notification message sent by the publisher and forwarding the notification message to the internal publisher;
the internal publisher is used for forwarding the notification message to the inference entity through the subscription entity when determining that the current load of the subscription entity does not exceed a set threshold;
the reasoning entity is used for sending the notification message to a pushing endpoint associated with the subscription entity when determining that the notification message meets the initialization filtering condition of the reasoning entity;
the push endpoint is used for forwarding a notification message to a message receiving entity associated with the push endpoint;
and the message receiving entity is used for sending the received notification message to the subscriber.
2. The publish-subscribe system of claim 1,
the notification agent is further configured to update a subscription relationship description according to the subscription request, where the subscription relationship description includes semantic priority ordering of the subscription request and the subordinate subscription request, and keywords carried by the subscription request and the subordinate subscription request.
3. The publish-subscribe system of claim 1,
the notification agent is further configured to determine, after receiving the notification message sent by the publisher, a subscription request and/or an affiliated subscription request carrying a keyword matched with the keyword carried by the notification message according to the subscription relationship description, rank the matched subscription request and/or affiliated subscription request according to semantic priority, and send the notification message to an internal publisher corresponding to a subscription entity established according to the matched subscription request and/or affiliated subscription request according to the ranking.
4. The publish-subscribe system of claim 1, 2 or 3,
the notification agent is further configured to establish a push endpoint when receiving a request message for establishing the push endpoint by the subscriber; registering a message receiving entity address carried by the request message at a pushing endpoint, associating the message receiving entity with the pushing endpoint, and forwarding the message receiving entity and the pushing endpoint to the subscriber when receiving the pushing endpoint address returned by the pushing endpoint.
5. The publish-subscribe system of claim 4,
the notification agent is further configured to establish a subscription entity when receiving a subscription request sent by the subscriber after establishing the push endpoint, initialize the subscription entity with a subscription name, a keyword and a filtering condition carried in the subscription request, register a push endpoint address carried in the subscription request in the subscription entity, and associate the push endpoint with the subscription entity;
the subscription entity is also used for establishing an inference entity and initializing the inference entity according to the filter condition carried by the subscription request.
6. A notification message processing method is applied to a publish-subscribe system, and is characterized by comprising the following steps:
after receiving the notification message sent by the publisher, the notification agent forwards the notification message to the internal publisher;
when the internal publisher determines that the current load of the subscription entity does not exceed a set threshold value, the notification message is forwarded to the inference entity through the subscription entity;
when the inference entity determines that the notification message meets the initialization filtering condition of the inference entity, the inference entity sends the notification message to a push endpoint associated with the subscription entity;
the push endpoint forwards the notification message to a message receiving entity associated with the push endpoint, and the message receiving entity sends the notification message to the subscriber.
7. The method of claim 6, wherein when the notification agent receives the subscription request from the subscriber, the method further comprises:
and the notification agent updates subscription relation description according to the subscription request, wherein the subscription relation description comprises semantic priority ordering of the subscription request and subordinate subscription requests of the subscription request, and keywords carried by the subscription request and the subordinate subscription requests.
8. The method of claim 6, wherein the forwarding of the notification message sent by the publisher to the internal publisher by the notification broker comprises:
and after receiving the notification message sent by the publisher, the notification agent determines a subscription request and/or an affiliated subscription request matched with the keywords carried by the notification message according to the subscription relationship description, sorts the matched subscription request and/or affiliated subscription request according to semantic priority, and sends the notification message to an internal publisher corresponding to a subscription entity established according to the matched subscription request and/or affiliated subscription request according to the sorting.
9. The method of claim 6, 7 or 8, further comprising:
when the notification agent receives a request message for establishing a push endpoint by the subscriber, establishing the push endpoint;
and the notification agent registers the message receiving entity address carried by the request message at the push endpoint, associates the message receiving entity with the push endpoint, and forwards the message receiving entity and the push endpoint to the subscriber when receiving the push endpoint address returned by the push endpoint.
10. The method of claim 9, wherein after the notification agent establishes the push endpoint, the method further comprises:
the notification agent establishes a subscription entity when receiving a subscription request sent by the subscriber, initializes the subscription entity by a subscription name, a keyword and a filtering condition carried by the subscription request, registers a push endpoint address carried by the subscription request in the subscription entity, and associates the push endpoint and the subscription entity;
and the subscription entity establishes an inference entity, and initializes the inference entity according to the filter condition carried by the subscription 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 (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 |
| 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 |
| WO2024139762A1 (en) * | 2022-12-27 | 2024-07-04 | 华为技术有限公司 | Data publishing method and device |
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 (8)
| 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 |
| WO2024139762A1 (en) * | 2022-12-27 | 2024-07-04 | 华为技术有限公司 | Data publishing method and device |
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 | |
| AU2012348048B2 (en) | Contextual and location awareness for device interaction | |
| CN107431664B (en) | Message transmission system and method | |
| CN103326929B (en) | Method and device for transmitting messages | |
| CN106210049B (en) | Cluster communication method and system based on message queue | |
| EP2835938B1 (en) | Message publishing and subscribing method and apparatus | |
| US20130067024A1 (en) | Distributing multi-source push notifications to multiple targets | |
| CN105991731A (en) | Method for obtaining information, intelligent terminal and server side | |
| EP3255849A1 (en) | Multi-channel communications for sending push notifications to mobile devices | |
| US20130066980A1 (en) | Mapping raw event data to customized notifications | |
| US9935861B2 (en) | Method, system and apparatus for detecting instant message spam | |
| KR101950050B1 (en) | Scale-out system to acquire event data | |
| JP2011191911A (en) | Advertisement distribution device, advertisement distribution system, advertisement distribution method and program | |
| CN101620717A (en) | Method and system for analyzing user demands | |
| EP2466854A1 (en) | Mobile search method and system thereof | |
| CN111147534B (en) | Communication method and system under micro-service architecture | |
| US20130151553A1 (en) | Method and apparatus for processing a composite context event | |
| JP2013134541A (en) | Short message system | |
| CN102170476B (en) | Cloud computing method and device based on cloud node autonomic learning | |
| CN102739562A (en) | Method and device for sending collection information | |
| CN104092735A (en) | Cloud computing data access method and system based on binary tree | |
| CN110677496B (en) | Middleware service scheduling method and device and readable storage medium | |
| US9930000B2 (en) | Method for posing requests in a social networking site | |
| CN110247808B (en) | Information transmission method, device, equipment and readable storage medium | |
| WO2016206477A1 (en) | Interaction method, apparatus, and system for unstructured supplementary services data, and computer readable storage medium |
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 |