JP2000293387A - Event notification system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To obtain an event notification system in which transfer delay time about each event is short regardless of the height/lowness of an event reception frequency. SOLUTION: An event that is received by an event receiving means 30 and sent from an event generation source component is fetched by the event collecting means 32 of an event collection processing means 31 and stored as an event array in an event storing means 33 and also, a transmission decision instruction is outputted to an event transmission deciding means 34. The means 34 measures from the time when the transmission decision instruction is outputted by receiving the event from the event generation source component until preliminarily decided waiting time D in comparison with a conventional manner and transmits the event array with an event transmitting means 35 not only when the number of events stored in the event array becomes a maximum collection number M, but when these times measured by a timer pass their respectively set times even though it does not reach the number M.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to an event notification system in a distributed system, and more particularly, to an event notification system for batch-transferring a plurality of events.

[0002]

2. Description of the Related Art A distributed system equalizes the processing load accompanying the advancement and complexity of information processing. A component is a generic term for components such as devices, subsystems, and processes in a distributed system. These components perform processing by being transmitted and received in the form of events as information communicated asynchronously with each other. The event notification system is responsible for mediating such an event.

FIG. 8 schematically shows the configuration of a distributed system to which such an event notification system is applied. This distributed system includes an event source component 10 in which an event to be notified has occurred, an event notification destination component 11 that is a notification destination of the generated event, and an event notification system 12. The event source component 10 is connected to an event notification destination component 11 via an event notification system 12. Such an event notification system 12
Receives an event from the event source component 10 and transfers the event to the notification destination component 11. Such an event notification system is useful for asynchronously notifying a failure of a device or a program in network management or system management, particularly from the viewpoint of event notification.

When some components exist between the event source component 10 and the event notification destination component 11, such an event notification system is inserted between the components. Event source component 10, event notification system 11, and event notification destination component 12
Between them, general communication information is transferred in addition to the event notification described above. Therefore, this type of event notification system conventionally improves the transfer efficiency of events by collectively transferring a plurality of generated events, and reduces the load on communication processing other than the event notification.

FIG. 9 shows such an event notification system 1.
2 shows an outline of the event notification process in FIG. In the event notification system 12, the maximum collection number M of events that can be transferred collectively is determined in advance. Also,
A predetermined collection time T is measured by a timer that is reset every time an event is received. First, in the event notification system 12, the event source component 1
It monitors the reception of an event to be notified from 0 (step S13: N). Then, when this is received (Step S13: Y), the received event is stored in an array (Step S14). Event notification system 12
In this example, the number of received events is counted in order to batch-transfer the events stored in this array, and this is held as the event reception number R. When the received events are stored in the array in step S14, the number of received events R is counted up (step S15). Then, when the event reception number R reaches the maximum collection number M (step S16: Y), the events to be stored in the array are grouped by one.
The transfer is performed by the first transmission process (step S17). afterwards,
The number of event receptions R which has been counted up is reset to "0" (step S18), and the timer is also reset (step S19).

In step S16, when the event reception number R is not the maximum collection number M (step S16: N), it is determined whether or not this time exceeds the collection time T by referring to the time measured by the timer described above. (Step S20). Then, even when the time measured by the timer has exceeded the collection time T (step S20: Y), the events to be stored in the array are collectively transferred by one transmission process (step S17). When the time measured by the timer has not elapsed the collection time T in step S20 (step S2).
At 0: N), the monitoring of the reception of the event is continued (step S13).

As described above, the conventional event notification system 1
2 does not immediately transfer the event to the event notification destination component 11, which is the notification destination, even if the event is received from the event generation source component 10. Then, as shown in FIG. 9, when the number of events stored in the array reaches the maximum collection number M, or when the elapsed time from the last event transmission exceeds the collection time T, the array Is transferred in one transmission process. As a result, the number of transmissions can be reduced as compared with the case where events are individually transferred. Therefore, it is possible to reduce the communication protocol processing time spent for the overhead time for the transmission and the like, and it is possible to improve the transfer throughput.

[0008]

In such a conventional event notification system, when the reception frequency is high, the collection time T
When the number of received events reaches the maximum number of collections M within this time, the events stored in the array are transferred collectively regardless of the collection time T, so that the transfer throughput can be improved. However, if the frequency of reception decreases, the collection time T
Within this time, the number of received events will not reach the maximum number of collections M, and events received immediately after the measurement of the collection time T will not be forwarded until the collection time T elapses. In other words, there is a problem that the delay time of the event transfer to the event notification destination component increases even though the number of events is small.

An object of the present invention is to provide an event notification system having a small transfer delay time for each event regardless of whether the frequency of event reception is high or low.

[0010]

According to the first aspect of the present invention, (a) an event receiving means for receiving an event as information which is asynchronously communicated between the components of the distributed system; and (b) this event Event storage means for storing an event received by the reception means;
(C) event transmission determination means for instructing event transmission when the next event is not received until a predetermined waiting time has elapsed since the last reception of the event by the event reception means; and (d) this event transmission The event notification system is provided with an event transmission unit that collectively transmits the predetermined number of events stored in the event storage unit in response to an event transmission instruction from the determination unit.

That is, in the first aspect of the present invention, the event received by the event receiving means is stored in the event storage means. In the event transmission determining means, an instruction to transmit an event is issued when the next event is not received until a predetermined waiting time has elapsed since the event was last received by the event receiving means. In response to this instruction, the event transmission means transmits the event in batches for each of a predetermined number of events stored in the event storage means.

In the invention according to the second aspect, (a) an event receiving means for receiving an event as information which is asynchronously communicated between the components of the distributed system;
(B) an event storage means for storing the events received by the event receiving means, (c) a counting means for counting the number of events received by the event receiving means, and (d) predetermined for each transmission of the event. First timer means for measuring the acquired collection time, (e) second timer means for measuring a predetermined waiting time every time an event is received by the event receiving means, and (f) counting by the counting means. When the numerical value reaches a predetermined maximum collection number, or when the time measured by the first timer means has reached the collection time, or when the time measured by the second timer means has reached the waiting time, an event is transmitted. And (g) an event transmission determining means for instructing an event transmission from the event transmission determining means. Is provided and an event transmission means for transmitting together for each event of a predetermined number of units in the event notification system.

That is, according to the second aspect of the invention, the event received by the event receiving means is stored in the event storage means. The counting means counts the number of events received by the event receiving means, the first timer means measures a predetermined collection time for each transmission of the event, and the second timer means receives the event by the event receiving means. Each time a predetermined waiting time is measured. In the event transmission determining means, when the count value of the counting means has reached a predetermined maximum collection number, or when the time measured by the first timer means has reached the collection time, or When the measurement time reaches the waiting time, an instruction to send an event is issued. In response to this instruction, the event transmission means transmits the event in batches for each of a predetermined number of events stored in the event storage means.

According to the third aspect of the present invention, (a) an event receiving means for receiving an event as information communicated asynchronously between components of the distributed system;
(B) event storage means for storing the events received by the event receiving means, (c) counting means for counting the number of events received by the event receiving means, and (d) timer means for measuring time. (E) a first activation time set when the count value of the counting means reaches a predetermined maximum number of collections, or a time measured by the timer means after the collection time elapses for each transmission of the event, or an event receiving means. Each time an event is received, a second time set after a predetermined waiting time elapses
When the start time of the event is reached, an event transmission determining means for instructing event transmission, and (f) a batch of predetermined number of events stored in the event storage means in response to the event transmission instruction from the event transmission determining means. And an event transmitting means for transmitting the event.

That is, in the invention according to claim 3, the event received by the event receiving means is stored in the event storage means. The number of events received by the event receiving means is counted by the counting means, and the time is measured by the timer means. In the event transmission determining means, when the count value of the counting means reaches a predetermined maximum number of collections, or the time measured by the timer means is set to a first activation time set after the collection time elapses for each transmission of the event. Alternatively, every time an event is received by the event receiving means, an event transmission is instructed when the second activation time set after a predetermined waiting time elapses. In response to this instruction, the event transmission means transmits the event in batches for each of a predetermined number of events stored in the event storage means.

According to a fourth aspect of the present invention, in the event notification system according to the first to third aspects, the waiting time is determined by a predetermined number of events to be transmitted corresponding to the number of events to be transmitted based on a preset event reception interval expected value. It is characterized by the time obtained by subtracting the time.

That is, in the invention according to claim 4, the waiting time is calculated by subtracting the event transmission time corresponding to the number of events to be transmitted from a preset event reception interval expected value. Is optimized, and the transfer throughput can be further improved.

According to a fifth aspect of the present invention, in the event notification system of the first to fourth aspects, the event storage means stores an event array in which pointers to the respective events received by the event receiving means are stored. It is characterized by doing.

That is, in the invention according to the fifth aspect, the event storage means stores an event array in which pointers to the respective events received by the event receiving means are stored, so that batch transfer of events is performed. Can greatly simplify the processing for a group of data units.

[0020]

BEST MODE FOR CARRYING OUT THE INVENTION

[0021]

DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention will be described in detail below with reference to embodiments.

FIG. 1 shows an outline of the configuration of an event notification system according to an embodiment of the present invention. The event notification system in this embodiment is applied to the distributed system shown in FIG. This event notification system collects an event received by an event notification unit 30 that receives an event notified from an event generation source component (not shown), and notifies the event notification destination component (not illustrated) of the event. An event collection and transmission processing unit 31 is provided.
The event collection and transmission processing unit 31
Event collecting means 32 for extracting the events received by the event collecting means 32, an event storing means 33 for storing the events extracted by the event collecting means 32, and an event transmission for determining a transmission instruction according to the collection status of the event collecting means 32 The determination unit 34 and the event storage unit 3 store the event notification destination component (not shown) in accordance with the transmission instruction from the event transmission determination unit
And an event transmission unit 35 for batch-transferring the events stored in the event storage unit 3.

The event receiving means 30 has a queue, and stores an event received from an event source component (not shown). Event collecting means 32
Retrieves the event stored in the queue of the event receiving unit 30 and stores it in the event storage unit 33. The size of the event storage means 33 is the maximum number of collected events M
And a memory having a storage capacity corresponding to.

FIG. 2 shows an example of the storage configuration of the events stored in the event storage means 33. That is, the event storage unit 33 stores a plurality of events as an array 36. In this case, each element holds a pointer to each event. Element 37
₁ is a pointer to the first event 38 _1, pointer elements 37 ₂ to the second event 38 ₂ are respectively stored.

The event collection means 32 stores the extracted events in the event storage means 33 in such a data structure, and outputs an instruction to start the transmission judgment to the event transmission judgment means 34. The event transmission determination means 34
It has first and second timers (not shown). First
Is a timer for measuring a predetermined collection time T from the previous transmission of the event array, and notifying that the time has elapsed. On the other hand, the second timer is for measuring the waiting time D from the point in time when a transmission determination start instruction is input from the event collection unit 32, and notifying that the time has elapsed. Such an event transmission determination means 34
The number of events stored in the array is the maximum collection number M
Not only does the transmission instruction take place when the time has elapsed or when the elapsed time since the last event transmission has exceeded the collection time T, but also when the waiting time D has elapsed, the event transmission means 35 Is instructed to transfer the event array stored in the event storage unit 33 to the event storage unit 33. The event transmitting unit 35 extracts the event array stored in the event storage unit 33 when the start of transmission is determined by the event transmission determining unit 34, and collectively transmits the event array to an event notification destination component (not shown). I do.

Hereinafter, the operation of the event notification system according to the present embodiment having such a configuration will be described in detail. Here, it is assumed that the event receiving unit 30 and the event collection / transmission processing unit 31 operate in different threads or different processes. As described above, in the event notification system according to the present embodiment, the event receiving unit 30 receives an event from the event source component.

FIG. 3 shows an outline of the operation flow of the event receiving means 30. That is, the event receiving means 30 monitors the reception of an event from the event source component, and upon receiving the event (step S40), checks whether there is a free space in the internal queue (step S41). When there is no free space in the queue (step S41: N), the process waits until a free space is generated. on the other hand,
When there is a free space in the queue (step S41: Y), the received event is stored in this queue (step S4).
2) Monitor the reception of the event again (return).

The events received by the event receiving means 30 are taken out by the event collection / transmission processing unit 31 and are stored in an array according to the number of events to be stored, the elapsed time since the last event transmission, and the waiting time. The event array stored in the storage unit 33 is transferred collectively.

FIG. 4 shows an outline of the operation flow of the event collection and transmission processing unit 31. The event collection / transmission processing unit 31 causes the event collection unit 32 to check whether there is an event to be notified in the queue of the event reception unit 30 (Step S45). When there is no event to be notified in the queue (step S45: N), the process waits until the event to be notified is stored in this queue. on the other hand,
When there is an event to be notified to the queue (step S4
5: Y), the event collecting means 32 fetches the event from this queue (step S46), and stores the fetched event in the array of the data structure shown in FIG. 2 (step S47). Next, "1" is added to the event reception number R held in advance (step S48). The event reception number R is the number of events stored in the event array. Next, the event reception number R and the maximum collection number M are compared (step S49). Number of received events R
Is not equal to the maximum collection number M (step S49:
N) A wait time D, which is a timer time set in the second timer and is an upper limit value of the time from when the transmission determination start instruction is input from the event collection unit 32, is calculated (step S50). In the event transmission determining means 34,
Waiting time D from the start instruction of transmission determination to the next event
If the next event is not received before the elapse, a transmission instruction is output to the event transmission unit 35 to transmit the event sequence stored in the event storage unit 33.

The event transmission determining means 34 calculates the waiting time D until the next event based on the event reception interval expected value P and the event transmission required time S. The event reception interval expected value P is a value expected as a time interval from the reception of the current event to the reception of the next event. This value is set in advance in consideration of the average value of the reception intervals of each event and the allowable delay time of event arrival at the event notification destination component. Since the event array is always transmitted to the event notification destination component for each collection time T, the event reception interval expected value P is meaningless unless shorter than the collection time T. The event transmission required time S is a time required for transmitting the currently stored event array to the event notification destination component. This increases depending on the number n of events, and can be approximated by the following equation.

S = A · n + B (1) where A and B are constants and are given in advance at the time of system design.

From the event reception interval expected value P and the required event transmission time S, the waiting time D until the next event is expressed by the following equation.

D = P−S (2)

As expressed by the equation (2), the waiting time D until the next event is equal to the event reception interval expected value P
Means that the next event is expected to be received at the time when the time has elapsed, and that the next event is to be waited until the time required for event transmission S is subtracted therefrom.

FIG. 5 shows the relationship between the waiting time D after receiving a certain first event e ₁ and the receiving time of a _second event e ₂ which is the next event. FIG. 9A shows a case where the second event e ₂ is received after the collection time T. FIG. 2B shows the second
Although event e ₂ of is received within the acquisition time T, shows a case that has been received after waiting D. Figure (c)
Indicates that the second event e ₂ is received within the event reception interval expected value P, but is received after the waiting time D. Here, it is assumed that the time t ₀ is a reference time of the collection time T, and the first event e ₁ is received at the time t ₁ . Further, the time after elapse of the preset event reception interval expected value P from the time t ₁ is t ₃ , and the time obtained by subtracting the event transmission time S from the time t ₃ is t _2.
And That is, the waiting time D until the next event
Is between from time t ₁ to time t _2. Time t ₀
, The time when the collection time T has elapsed is represented by t ₄ .

First, referring to FIG. 3A, the second event e ₂ has been received after the collection time T. Therefore, in the conventional event notification system, the first event e ₁ was transmitted to the event notification destination component at time t ₄ . However, in the event notification system in this embodiment, the first event e ₁ is sent to the event notification destination component in the time t ₂ after elapse of the waiting time D as described above. That is, the delay time is only D.

Referring to FIG. 2B, the second event e ₂ is received within the collection time T, but is received after the waiting time D. Therefore, in the conventional event notification system, the first and second events e ₁ and e ₂
Was sent to the event notification destination component at time t ₄ . However, focusing on the first event e ₁ , the transfer delay time is shorter than the transmission delay time together with the second event e ₂ . Since the second event e ₂ is received after the event reception interval predicted value P, the time S for transmitting a first event e ₁ is secured by a first transmitting process of event e ₁ never receiving and transmitting process of the second event e ₂ is delayed.

Still referring to FIG. 3C, the second event e ₂ is received within the expected event receiving interval P, but is received after the waiting time D. In this case, the single-processor machine, during the first transmission process event e ₁ can not operate the event receiving means, receiving and sending processing of the second event e ₂ can be no longer a delay Occurs. However, this phenomenon occurs stochastically, and its delay is within S, so that it is very small compared to the collection time T. Further, when many events occur, the event receiving interval is smaller than the expected event receiving interval P, so that the probability of occurrence of this phenomenon is small, so that the merits of batch transfer can be maintained.

As described above, the event transmission determining means 34
Waiting time D from the start instruction of transmission determination to the next event
If the next event until after it is received, since the to send event sequences stored in the event storage section 33, to significantly reduce the transfer delay time focusing on the first event e ₁ Can be.

Returning to FIG. 4, the description will be continued. Step S5
0, the waiting time D until the next event as described above
Is calculated. Then, using this waiting time D,
The second timer is set to start after D has elapsed (step S5).
1) Returning to step S45, the presence or absence of an event stored in the queue is monitored. At this time, the first timer is not updated.

On the other hand, in step S49, the number of event receptions R
Is equal to the maximum collection number M (step S49: Y),
A transmission instruction is output from the event transmission determining unit 34 to the event transmitting unit 35. The event transmitting unit 35 to which this is input extracts the event array stored in the event storage unit 33 and transmits this to the event notification destination component (step S52). Next, all the elements of the event array in the event storage unit 33 are cleared, the number of event receptions R is reset to "0" (step S53), the first timer is reset, and the predetermined collection time T is reset. Then, the activation after the elapse of T is set in the first timer (step S54). Further, the second timer is reset (step S55),
Returning to step S45, the presence or absence of an event stored in the queue is monitored.

By the way, the first and second timers operate in a separate thread from the event collection and transmission processing unit 31, and monitor the measurement time of the first and second timers, and set the time set respectively. As described above, step S52
Of the event array is transmitted.

FIG. 6 shows an outline of the flow of an event array transmission process based on such timer monitoring. That is, as shown in FIG. 4, when the second timer is reset by the event collection and transmission processing unit in step S55 (step S60: Y), the first timer is reset in step S54.
Is set to start after T has elapsed in the timer
Referring to the measurement time of the first timer (step S6)
1). Then, it is checked whether or not the measured time has reached the activation time set in step S54 (step S62). Here, when the first timer reaches the set activation time (step S62: Y), the event transmission determining unit 34 causes the event transmitting unit 35 to output a transmission instruction. If the first timer has not reached the set activation time (step S62: N), the process returns to step S61 again and refers to the measurement time of the first timer. The event transmitting unit 35 to which the transmission instruction output in step S62 has been input extracts the event array stored in the event storage unit 33 and transmits this to the event notification destination component (step S6).
3). Next, all elements of the event array of the event storage means 33 are cleared, the number of event receptions R is reset to "0" (step S64), the first timer is reset, and the predetermined collection time T is reset. First using
Is set to start after T has elapsed (step S6).
5). Further, the second timer is reset (step S66), and the process returns to step S60 (return). Step S63 and subsequent steps are the same as step S52 and subsequent steps in FIG.

On the other hand, if the second timer is not reset in step S60 (step S60: N), it is checked whether or not the second timer is set to start after D has elapsed (step S67). When the setting of the start after the lapse of D has not been made in the second timer (step S67:
In N), the process returns to step S60 again. Step S67
When the setting of activation after the lapse of D is performed on the second timer (step S67: Y), the setting of the activation after the lapse of D is performed on the second timer in step S51. The time measured by the timer is referred to (step S68). Then, it is checked whether or not the measured time has reached the start time set in step S51 (step S6).
9). Here, when the second timer reaches the set start time (step S69: Y), the transmission instruction is output from the event transmission determining unit 34 to the event transmitting unit 35. If the second timer has not reached the set start time (step S69: N), step S69 is performed again.
Returning to 68, the measurement time of the second timer is referred to. The event transmitting unit 35 to which the transmission instruction output in step S69 has been input extracts the event array stored in the event storage unit 33 and transmits this to the event notification destination component (step S63). Next, all elements of the event array of the event storage means 33 are cleared, the number of event receptions R is reset to "0" (step S64), the first timer is reset, and the predetermined collection time T is reset. Then, the activation after the elapse of T is set in the first timer (step S65). Further, the second timer is reset (step S66),
It returns to step S60 (return). Step S63 and subsequent steps are the same as step S52 and subsequent steps in FIG.

Next, the operation of the event notification system according to this embodiment described above will be specifically described.

FIG. 7 shows the relationship between the collection time T and the event reception time. Here, the maximum collection number M is “5”. FIG. 9A shows a case where events of the maximum number of collections “5” or more are received within the collection time T, and the reception interval of each event is shorter than the event waiting time D. FIG. 3B shows a case where events having a number less than the maximum collection number “5” are received within the collection time T, and the reception interval of each event is shorter than the event waiting time D. FIG. 9C shows a case where the event reception interval is longer than the waiting time D within the collection time T.
First, FIG. A reference time of FIG (a) the acquisition time of the time t ₀ T, event e ₁ to e ₆ of the first to sixth assumed to be received in t ₁ ~t ₆ respectively time. Further, the time when the collection time T has elapsed from the time t _{0 is} defined as t ₇ . In this manner, the first to fifth events e _{1 to} e ₅ have an interval shorter than the event waiting time D,
Moreover, since the time is within the collection time T from time t ₀ , there is no event sequence transmission instruction from step S57 as shown in FIG. 4, and all events are stored in the event sequence. At the time of storing the event e ₅ of the fifth to the event sequence, the number of events has reached five, the transmission of the event sequence shown in step S52 from the step S49 shown in FIG. 4 is performed.
Then, the event reception number is reset at step S53, time after acquisition time T has passed that starting from the time t ₅ to the first timer in step S54 is set. In step S55, the second timer is reset, and the setting of the start time is not performed. Note that the sixth event e ₆ is processed within the next collection time T.

Next, FIG. 7B will be described. In FIG. (B), the time t ₀ to the reference time of the acquisition time T, the first to fourth event e ₁ to e ₄ are each time t _1, t ₈ ~
It is assumed to be received in t _10. Further, the time when the collection time T has elapsed from the time t _{0 is} defined as t ₇ . As described above, since the intervals of the _first to fourth events e _{1 to} e ₄ are shorter than the event waiting time D and are within the collection time T from the time t _{0, the} steps S 57 to S 57 shown in FIG. There is no event array transmission instruction, and all are stored in the event array. Since within the acquisition time T in is not received following events of the fourth event e ₄ is, conditions in step S49 are not satisfied, performs the activation time setting of the second timer in step S50 and step S51, step S45
Keep waiting for the next event. Meanwhile the collection time T
Has elapsed and the event sequence is transmitted from step S57 to step S52. Then, the number of received events is reset in step S53, and the first
The time after the collection time T starting from the time t ₄ is set in the timer of (1). In step S55, the second timer is reset, and the setting of the start time is not performed.

Next, FIG. 7C will be described. Same figure
In (c), the time t₀Is the reference time for the collection time T,
1st to 3rd event e₁~ E_ThreeIs the time t₁,
t₁₁, T₁₃It is assumed that it has been received. Time t₀
From the time when the collection time T has passed to t₇And First
Event e₁And the second event e_TwoIs the interval
Is shorter than the client wait time D and the time t₀Collection time from
T, so that the first or second timer
There is no event sequence transmission instruction from step 57,
And the second event e₁, E_TwoAccumulates in the event array
It is. Second event e _TwoAfter receiving the message, step S50
And setting the start time in the second timer in step S51.
While waiting for the next event reception in step S45
I can. Third event e_ThreeEvent wait time before receiving
Since D has elapsed, the second timer executes step S5
7 is transmitted to the step S52.
You. Then, in step S53, the number of received events is reset.
The time t is stored in the first timer at step S54.₁₂Start
The time after the collection time T as the point elapses is set. Also,
In step S55, the second timer is reset, and
The time is not set.

As described above, in FIGS. 9A and 9B, since the reception interval of each event is shorter than the waiting time D, it is the same as the conventional event notification system. , The advantages of batch transfer can be enjoyed. Even further when the reception frequency of the received long event than wait D by events as in Fig. (C) is low, first and second events e _1, e ₂
There since the transmission at time t ₁₂ is performed, it is possible to significantly reduce the transfer delay as compared with the prior art.

As described above, the event notification system according to the present embodiment uses the event transmission determining means 34 to determine whether the time elapsed since the last event transmission has reached the collection time T and the fact that the event has been received from the event source component. The time from when the transmission determination instruction is issued to when the predetermined waiting time D is reached is measured. And not only when the number of events stored in the event array reaches the maximum collection number M as in the related art,
Before reaching the maximum collection number M, the event array is transmitted when the time measured by each of these timers has passed the set time. As a result, even if the event reception frequency is high as in the related art, the events stored in the event array are collectively transferred to improve the transfer throughput, while the event reception frequency is low until the collection time T elapses. Pre-determined waiting time D without waiting
With the passage of time, the events collected so far can be batch-transferred, and the transfer delay time can be reduced for each event regardless of the frequency of event reception.

In the event notification system of the present embodiment, the receiving method is not particularly specified, but the present invention is not limited to this, and can be applied to an event notification system of any receiving method.

Further, in the event notification system of this embodiment, it is assumed that the pointers to the respective events are stored in the event storage means 33 as an event array. It may be stored. Also, a plurality of events may be stored using another data structure such as a list structure. In short, the data structure is not limited as long as a plurality of events can be handled collectively.

In the event notification system according to the present embodiment, the next event waiting time D is calculated each time and set in the second timer in order to optimize the transfer throughput. For simplicity, it may be fixedly provided in advance.

In the event notification system according to the present embodiment, the first and second event transmission
However, the present invention is not limited to this. Since it is only necessary to be able to distinguish the start time based on the collection time T and the waiting time D, one timer measures the absolute time, and the setting of the collection time T and the waiting time D is set to this absolute time each time. It is also possible to set a time after an elapsed time to be set.

[0055]

As described above, according to the first aspect of the present invention, the frequency of receiving events as information that is asynchronously communicated between the components of the distributed system is reduced. Collected events can be transferred collectively without waiting for the elapse of the collection time T measured for each transmission, so that transfer delay can be reduced and transfer throughput can be improved.

According to the second aspect of the present invention, the event stored in the event array is high even if the frequency of receiving the event as information communicated asynchronously between the components of the distributed system is high as in the related art. To collectively transfer the events collected up to a predetermined waiting time D without waiting for the collection time T to elapse even if the frequency of event reception is low, while improving the transfer throughput. This makes it possible to reduce the transfer delay time for each event regardless of the frequency of event reception.

According to the third aspect of the invention, in addition to the effect of the second aspect of the invention, the configuration of the time measurement by the timer can be simplified.

According to the fourth aspect of the present invention,
By calculating the wait time as the time obtained by subtracting the event transmission time corresponding to the number of events to be transmitted from the preset event reception interval expected value, the wait time is optimized and the transfer throughput is further improved. Will be able to do that.

According to the fifth aspect of the present invention, the event storage means stores an event array in which pointers to the respective events received by the event receiving means are stored. Processing of a group of data units to be performed can be greatly simplified.

[Brief description of the drawings]

FIG. 1 is a block diagram illustrating an outline of a configuration of an event notification system according to an embodiment.

FIG. 2 is an explanatory diagram illustrating an example of a storage configuration of an event storage unit according to the present embodiment.

FIG. 3 is a flowchart illustrating an outline of an operation of an event receiving unit in the embodiment.

FIG. 4 is a flowchart illustrating an outline of an operation of an event collection / transmission processing unit according to the embodiment.

FIG. 5 is an explanatory diagram for explaining a relationship between a waiting time D from when a _first event e ₁ is received and a receiving time of a _second event e ₂ which is the next event.

FIG. 6 is a flowchart showing an outline of the content of an event array transmission process by timer monitoring in the embodiment.

FIG. 7 is an explanatory diagram for explaining a relationship between a collection time T and an event reception time.

FIG. 8 is a configuration diagram illustrating an outline of a configuration of a distributed system to which the event notification system is applied.

FIG. 9 is a flowchart showing an outline of an event notification process in a conventionally proposed event notification system.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 10 Event origin component 11 Event notification destination component 12 Event notification system 30 Event receiving means 31 Event collection and transmission processing unit 32 Event collection means 33 Event storage means 34 Event transmission determination means 35 Event transmission means

Claims (5)

[Claims] 1. An event receiving means for receiving an event as information communicated asynchronously between components of a distributed system, an event storage means for storing an event received by the event receiving means, and the event receiving means Event transmission determining means for instructing event transmission when the next event is not received until a predetermined waiting time has elapsed since the last event received by the means, and an instruction for event transmission from the event transmission determining means An event notification system comprising: an event transmission unit that collectively transmits a predetermined number of events stored in the event storage unit. 2. An event receiving means for receiving an event as information communicated asynchronously between components of a distributed system, an event storing means for storing an event received by the event receiving means, and the event receiving means. Counting means for counting the number of events received by the means; first timer means for measuring a predetermined collection time every time an event is transmitted; and predetermined time each time an event is received by the event receiving means. Second timer means for measuring the waiting time, when the count value of the counting means has reached a predetermined maximum collection number, or when the time measured by the first timer means has reached the collection time. Or the second
An event transmission determining means for instructing an event transmission when the time measured by the timer means has reached the waiting time; and a predetermined number unit stored in the event storage means in response to the event transmission instruction from the event transmission determining means. And an event transmitting means for transmitting the event collectively for each event. 3. An event receiving means for receiving an event as information communicated asynchronously among the components of the distributed system, an event storage means for storing an event received by the event receiving means, and the event receiving means. Counting means for counting the number of events received by the means; timer means for measuring time; when the count value of the counting means reaches a predetermined maximum collection number, or the time measured by the timer means When the first activation time set after the collection time elapses for each event transmission or the second activation time set after the elapse of a predetermined waiting time every time an event is received by the event receiving means, Event transmission determining means for instructing event transmission; and Event notification system, characterized by comprising an event transmission means for transmitting together for each event of a predetermined number of units in accordance with an instruction of the vent transmission stored in said event storing means. 4. The waiting time is a time obtained by subtracting an event transmission required time corresponding to the number of events to be transmitted from a preset event reception interval expected value. The event notification system described. 5. The event according to claim 1, wherein said event storage means stores an event array in which pointers to respective events received by said event receiving means are stored. Notification system.