JPH11232126A - Event notification method and notification network - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an event notification method capable of notifying even a consumer who meets requirements after event delivery of an event and a notification network to execute this method without reducing the processing speed or the like. SOLUTION: When an event having an event holding period designated as one attribute is transmitted from a supplier 11 to an N.S.(notification server) 21, the N.S. checks the requirements of the even with respect to consumers 13 and 14 and delivers the event only to the consumer 13 meting a filter condition and stores this event; and thereafter, when the consumer 14 changes the filter condition in this holding period, the N.S. collates the held attribute of the event with the changed filter condition and notifies the event meeting the filter condition to the consumer 14.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a distributed object environment, and more particularly to an event notification method and a notification network for improving the reliability of event notification between distributed objects (hereinafter, simply referred to as objects). Things.

[0002]

2. Description of the Related Art In a distributed object environment, an event message may be transmitted and received between objects. In this case, it is desirable that the event message is multicast only to objects that need it.

[0003] Notification service (OMG:
“Notification Service Request For Proposal” OM
G Document: telecom / 97-01-03, see)
The event communication function between an event information provider (hereinafter, referred to as a supplier) and an event information receiver (hereinafter, referred to as a consumer), which are objects, is referred to as a notification server (hereinafter, referred to as NS). ) Is a service provided using push-type notification, pull-type notification,
It has functions such as multicast communication.

FIG. S. This shows a conventional event notification method using the event ID. S. 12 is transmitted to N.12. S. Reference numeral 12 denotes an event request condition (filter) for the consumers 13 and 14 registered at that time, and the event is added to only the consumer whose attribute value added to the event satisfies the filter condition. Deliver, and after this delivery, the event is discarded.

[0005]

As described above, in the conventional event notification method, the N.I. S. Once the event has been delivered by the consumer 12, the event is not delivered even if the consumer 14 is changed to receive the filter condition, and the event is not delivered to the newly registered consumer. there were.

An object of the present invention is to provide an event notification method capable of notifying an event to a consumer who has satisfied a required condition after the event delivery.

Another object of the present invention is to provide a notification network which can execute the event notification method without lowering the processing speed.

[0008]

According to the present invention, in order to achieve the above object, an event notification method for notifying an event message between an event information provider and an event information receiver in a distributed object environment via a notification server. In, the event information provider provides the event to the notification server by designating the retention period thereof, and the notification server delivers the event to the event information receiver that satisfies the requirement when receiving the event The first processing and, after the first processing, the event is held for a designated period, and during that time, the event is held in response to an event search request from an event information receiver that has fulfilled the required condition. And performing a second process of searching for and notifying an event.

According to the above configuration, the event is held for a predetermined period after the event is delivered, and if the event is within the period, the event information recipient who has satisfied the required condition is also notified. Event information recipients who are satisfied can be notified of the event.

Further, in a notification network in which one domain is constituted by a plurality of notification servers using the same shared information, a notification that executes the first processing in the event notification method according to claim 1 is provided. And a notification server that executes the second process in the event notification method according to claim 1 in the same domain, and processes requests from an event information provider and an event information receiver via a proxy. And transmitting the notification to any one of the notification servers.

[0011] According to the above configuration, the conventional event notification processing, the event is held during the designated period, and the event held by the search request from the event information receiver satisfying the request condition is searched and notified. Since the extended function processing to be performed can be shared and processed by a plurality of notification servers, the event notification method described in claim 1 can be implemented without lowering the processing speed.

[0012]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, the present invention will be described in more detail based on the illustrated embodiments.

FIG. 2 shows an example of an embodiment of an event notification method according to the present invention. In FIG. 2, the same components as those in FIG. 1 are denoted by the same reference numerals. That is, 11 is a supplier, 1
Consumers 3 and 14; S. It is.

N. S. 21 receives the event from the supplier, performs a first process of delivering the event to a consumer that satisfies the request condition, and, when an event holding period is specified as one of the attributes of the event, within the specified period. A second process of holding the event and searching for and notifying the held event in response to an event search request from a consumer satisfying the request condition is performed.

In the above configuration, the event from the supplier 11 is set to N. S. 21 is transmitted to N.21. S. 21 checks the event request condition (filter) for the consumers 13 and 14 registered at that time, and sends the event to only the consumer whose attribute value added to the event satisfies the filter condition, here 13 only. to deliver.

At this time, if the event holding period is designated by the supplier 11 as one of the attributes of the event, the N.I. S. 21 stores the event even after the delivery to the consumer 13 as long as the designated holding period has not elapsed.

Thereafter, during this holding period, the consumer 1
4 changes the filter condition so as to receive the event, and requests a search for the event. S. Reference numeral 21 compares the held event attribute with the changed filter condition. As a result, if there is an event that satisfies the filter condition, the event is notified (distributed) to the consumer 14.

Also, when an event search request is received from a new consumer registered during the holding period, the N.I. S. Reference numeral 21 compares the held event attribute with the filter condition, and notifies (delivery) if there is an event satisfying the filter condition.

As described above, according to the present invention, an event can be notified to a consumer who has satisfied a required condition after event delivery.

By the way, the event is held for a period designated by the supplier, and the consumer is searched and notified so as to notify the held event. S. When the function is extended, the load increases as compared with the case of only the conventional event notification service. Therefore, the load affects the conventional service, such as a delay in processing. In addition, the ability (scalability) to cope with the increase in the number of suppliers and consumers and the amount of events is also required.

Therefore, in the present invention, the N.I. S. , Processing an extended function.
S. And a server that manages information such as event type names and attributes defined by the supplier and filter conditions set by the consumer (hereinafter, referred to as shared information). S. The interworking method (sharing of information sharing and event delivery processing, etc.) is used to eliminate the influence of the processing load of the extended function on the conventional notification service and to improve the scalability.

That is, as shown in FIG. 3, a plurality of N.S. S. Constitutes one common range (hereinafter, referred to as a notification domain or simply a domain). S. 311 to 31
3, the domain 31, N. S. The domain 32, N. S. The notification network 30 is configured by configuring a domain 33 by 331 to 333.
And two types of interworking in each domain and interworking between domains are provided, and N.I. in the former domain is provided. S. The interworking between networks allows providing an extended function without lowering the processing speed of the conventional notification service. S. To the user.

All N.Ds in the domain S. Share event type names, attributes and filter definitions, supplied event data, and users (suppliers and consumers)
Which N. S. A uniform sending and receiving of events is provided irrespective of the connection. Also, the user and N.I.
S. There is a distributed object (hereinafter, referred to as a proxy) that transmits a request to and from which N.A. requests a user for a processing request (event transmission, filter condition setting, etc.).
S. Does not show whether to run, N. S. Since no interworking between them is shown, from the user's point of view, the domain is one N.D. S. Becomes

With such a domain configuration, N.N. S. , Which processes the extended functions (event storage and retrieval). S. Is used to process the conventional notification. S. Receives the event from the supplier and processes the extended function before discarding the event when the multicast to the registered consumer is finished. S. Deliver to

When an event is supplied from a supplier,
N. in the domain S. Performs a match with each filter condition and multicasts to the consumer to be sent, but N.D. S. N. in charge of an extended function
S. Holds the event, so that it can be delivered to the consumer whose registration or filter condition has been changed. Further, the N.V. that holds an event that matches the newly set filter condition is held. S. N. responsible for searching from S. Only for the conventional event notification service without being affected by this processing load. S.
, The responsiveness equivalent to the conventional event notification service is guaranteed.

FIG. 4 shows an example of the embodiment of the notification network of the present invention, in which one domain is shown in detail.

In FIG. 4, reference numeral 40 denotes a notification domain. S. 4
1, 42, 43, and 44 and a shared information management server 45. S. 41, N.M. S. 42 is in charge of conventional event notification processing. S. 43, N.P. S. 44 is in charge of processing of the extended function, and the shared information management server 45 manages shared information in the domain 40. This server 45 may be integrated with another server in the domain.

Reference numerals 51, 52, 53, and 54 are suppliers, 61, 62, 63, 64, 65, and 66 are consumers, and 71, 72, 73, 74, 75, and 76 are proxies. Proxies 71-76 communicate with users (suppliers and consumers) and N.P. S. Is an object that mediates between N. and N. S. Conceal the group to make one N.D.
S. Make it look like

Next, the N.D. in the domain having the above-described characteristics is used. S. A mechanism for realizing interworking will be described.

Each N. S. They are connected so that the event transfer direction is the direction of the arrow in the figure. That is,
N. S. 41, N.I. S. 42 is both a supplier and a consumer. S. 43 is a consumer; S. I don't know about 4. Similarly, N.
S. 43, N.N. S. 41 is a supplier; S. No information about N.42. S. 44 is both a supplier and a consumer.

The suppliers 51 and 52 are proxies 71 and 7
2 through N.I. S. 41 and the suppliers 53 and 5
4 is transmitted through the proxy 73, 74 to the N.4. S. 42. Consumer 6 already registered and filter set
1, 62 are N.I. S. Consumers 63 and 64 that have been connected and connected to the N. S. 42. Further, the consumer 65 before registration or filter setting sets the N.V. S. 43, and the consumer 66 also before registration or filter setting is connected to the N.C. S. 44.

Here, when the supplier 51 or 52 transmits an event to the proxy 71 or 72, the proxy 71 or 72 transmits the event to the N.P. S. 41 to N.41 S. 41 compares the event with the filter condition of each consumer, and consumers 61, 62,
Further, N. S. 42, N.P. S. Multicast to consumer 43, and multicast to consumers 63 and 64
S. 42, and can cope with an increase in the number of consumers.

When the supplier 53 or 54 sends an event to the proxy 73 or 74, the event is transmitted from the proxy 73 or 74 to the N.P. S. N.41 instead of N.41
S. The event is forwarded to the N.42. S. 42 performs matching with the filter condition, and consumers 63, 64,
N. S. 41, N.P. S. Multicast to N.44 and further to N.44. S. Multicasting to consumers 61 and 62 is performed by 41, and it is possible to cope with an increase in the number of suppliers and an increase in the amount of events.

Here, when the consumer 65 executes a filter setting operation on the proxy 75,
Proxy 75 is N.N. S. The filter condition is transmitted to 43.
N. S. 43 compares the attributes of all the held events with the filter conditions, and when an event that satisfies the condition is detected, transmits the event to the consumer 65.

During this process, N.I. S. 41 and N.I. S. 4
2 can execute the conventional event notification processing. S. 43 does not affect the processing load. Similarly, when the consumer 66 sets the filter via the proxy 76, the N.V. S. 44 performs a process of detecting and notifying an event that satisfies the filter condition from all the held events. S. 41 and N. S. No less than 42.

As described above, the conventional event notification processing can be provided with the conventional responsiveness, and can cope with an increase in the number of consumers and the amount of events.

In the above-described embodiment, the N.I. S. Perform extended function processing. S.
N. of a domain composed of two S. Although the interworking has been described, the present invention is not limited to this configuration, and the N.V. S. Can also be applied to three or more configurations.

[0038]

As described above, according to the present invention,
(1) The supplier can set and hold a retention period for an event, and the consumer can search and retrieve the event during that period. (2) Provide a conventional event notification service that is not affected by the load of the extended function processing. Can be obtained.

[Brief description of the drawings]

FIG. 1 is a diagram showing a conventional event notification method.

FIG. 2 is a diagram showing an example of an embodiment of an event notification method according to the present invention.

FIG. 3 is a diagram showing an outline of a notification network of the present invention.

FIG. 4 is a diagram showing an example of an embodiment of a notification network according to the present invention.

[Explanation of symbols]

11, 51 to 54: Supplier, 13, 14, 61 to 6
6: Consumer, 21, 311 to 313, 321 to 3
23, 331 to 333, 41 to 44: Notification server (NS), 31 to 33, 40: Notification domain, 30: Notification network, 45: Shared information management server, 71 to 76:
Proxy.

Claims (2)

[Claims] 1. An event notification method for notifying an event message between an event information provider and an event information receiver in a distributed object environment via a notification server, wherein the event information provider sends an event to the notification server. The notification server specifies the retention period, and the notification server, upon receiving the event, performs a first process of delivering the event to an event information receiver that satisfies the request condition, and a designated process after the first process. During the period, hold the event,
And performing a second process of searching and notifying an event held in response to an event search request from an event information receiver that has fulfilled the request condition. 2. A notification network for executing a first process in the event notification method according to claim 1, wherein in a notification network in which one domain is constituted by a plurality of notification servers using the same shared information. A notification server that executes the second processing in the event notification method according to claim 1 in the same domain, and processes processing requests from an event information provider and an event information receiver via a proxy. A notification network, wherein the notification is transmitted to any one of the notification servers.