JPH06153250A - Inter-system event informing method for exchange - Google Patents

Abstract

PURPOSE:To smooth the exchange service by taking an event to be faulty when a prescribed condition is satisfied by a communication processor monitoring a path state and informing a management processor of other processors of the event, thereby relieving the load of the management processor. CONSTITUTION:Plural communication processors of an exchange 1 monitor a corresponding path state and while a prescribed time elapses from a point of time when a specific event appears, a management processor B is not informed of the event. Thus, the heavy load of the processor B by every notice due to a fault event or the like recovered in a short time or a hit or the like is prevented and the exchange service is smoothed without decreasing the processing speed.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an inter-system event notification method for an exchange having a plurality of processors (processors).

Generally, an exchange has a processor for each of a plurality of functional blocks such as a central processing system and a communication processing system,
Various exchange services are realized by communication between processors called intersystem communication.

[0003]

2. Description of the Related Art Conventionally, a communication processor for monitoring a route condition has a problem that an event related to the route condition such as occurrence / clearance of congestion and occurrence / recovery of a fault such as disconnection of a line occurs every time they appear. To another predetermined processor (for example, a management processor that controls the control of the exchange).

Upon receiving the notification of the event, the management processor sequentially displays messages corresponding to the event on the screen of the console and reports the occurrence of the event to the administrator of the exchange. The administrator of the exchange, for example, if the event is the occurrence of congestion in a specific route, take a measure such as instructing the exchange to select a route that alleviates the congestion, that is, an event paired with the previous event, that is, Repeat until a message corresponding to the congestion is displayed.

[0005]

By the way, many line disconnections are instantaneous (immediate interruptions that do not hinder communication) that are restored immediately after disconnection, and congestion is naturally resolved in a relatively short time. Sometimes. That is, the occurrence / recovery of the instantaneous interruption and the occurrence / elimination of the congestion, which is eventually resolved in a short time, do not necessarily need to be notified as an event (abnormality occurrence event or abnormality cancellation event).

However, in the past, as described above, since notification was made for all events,
The communication volume between systems increases in proportion to the frequency of occurrence of events, and in particular, the load on the processor of the notification destination that executes the predetermined processing in response to the notification increases, and the processing speed decreases and the switching service is hindered. There was an occasion.

In view of the above problems, it is an object of the present invention to reduce the burden on the notified processor and to facilitate the exchange service.

[0008]

In order to solve the above-mentioned problems, the method according to the invention of claim 1 is such that, as shown in FIG. 2 and FIG. Time tN from the time when a specific event related to
The event is notified to the other processor B only when the route state corresponding to the event continues until.

In the method according to the second aspect of the present invention, the event is a transition of the path state from an abnormal state to a normal state. In the method according to the third aspect of the present invention, the processor A that monitors the route state, for the abnormality occurrence event which is the transition of the route state from the normal state to the abnormal state, has a first constant time from the time of its occurrence. Only when the abnormal state of the route continues until tM elapses, the abnormality occurrence event is notified to the other processor B, and the abnormal state is the transition from the abnormal state of the route state to the normal state. Regarding the abnormality cancellation event paired with the occurrence event, the abnormality cancellation event is sent to the other processor B only when the normal state of the route continues until the second constant time tN elapses from the appearance time. Notify against

[0010]

For example, when the route state changes from the normal state to the abnormal state, that is, when an abnormal occurrence event appears, the event notification is suspended for a period from the appearance time until a certain time tM elapses. , Route condition is constant time tM
If the abnormal state is continuously occurring during the time counting, the abnormality occurrence event is notified to the other processor B after the elapse of the fixed time tM.

After the notification of the abnormality occurrence event, when the route state changes from the abnormal state to the normal state, that is, when the abnormality cancellation event appears, the period from the appearance time to the elapse of a fixed time tN If the event notification is put on hold and the route state is continuously in the abnormal state during the time measurement of the constant time tN, the abnormality cancellation event is notified to the other processor B after the constant time tN.

[0012]

DESCRIPTION OF THE PREFERRED EMBODIMENTS FIG. 1 is a block diagram showing the configuration of an exchange 1 according to the present invention. The exchange 1 has a communication processor A that monitors the respective states of the three routes L, and a management processor B that displays a message according to the event notified by each communication processor A on the screen of the display D. There is.

FIG. 2 is a diagram schematically showing an example of event notification by the communication processor A of FIG. 1, and FIG. 3 is a diagram showing state transition of the communication processor A corresponding to FIG. When congestion occurs in the route L, the communication processor A immediately notifies the management processor B of this event (herein referred to as an occurrence event). As a result, the state of the communication processor A shifts from the normal release event notification completion state S0 to the generated event notification completion state S1, as shown in FIG.

On the other hand, when the congestion is eliminated and the route L returns to the normal state, the communication processor A does not give an event notification at the time when this event (here, a release event) appears, and for example, Time measurement of time tN of about 1 second is started. That is, the communication processor A suspends the notification of the release event and waits for the suspension time tN to elapse. When the time counting is started, the state of the communication processor A shifts from the above-described state S1 to the state S2 during the time tN counting.

When the occurrence event appears again in the state S2, the communication processor A stops the time tN. In this case, the state of the communication processor A is the state S2.
Since the state transitions from S to S1 and the notification of the release event is pending, the notification of the occurrence event paired with the release event is not performed.

On the other hand, if there is no occurrence of the occurring event during the time tN, that is, if the normal state of the route L continues until the time tN elapses from the appearance of the release event, the communication processor A The notification of the pending release event is performed when the time tN has elapsed. By the notification of the release event, the state of the communication processor A changes from the state S2 to the state S0.
Return to.

As described above, in this embodiment, by notifying the release event only when the normal state continues for 1 second or more, unnecessary event notification is reduced and the load on the management processor B is reduced. .

FIG. 4 is a diagram schematically showing another example of event notification by the communication processor A of FIG. 1, and FIG. 5 is a diagram showing state transition of the communication processor A corresponding to FIG. In these figures, the communication processor A suspends the notification of this event (here, this is referred to as an occurrence event) when a path failure occurs, and starts measuring a first suspension time tM of, for example, about 100 ms. To do. This allows
As shown in FIG. 5, the state of the communication processor A shifts from the release event notification completion state S0 which is a normal state to the state S3 during which time tM is being counted.

When the route failure is resolved and the route L is restored to the normal state in the state S3, the communication processor A stops the time tM. Then, when the path failure occurs again, the communication processor A starts counting the time tM again.

On the other hand, in the state S3, when the route event is resolved and the release event paired with the generated event does not appear, that is, time t from the time when the generated event appears.
If the route failure continues until N has elapsed, the communication processor A sends a notification of the pending event at time tM.
Will be performed when By the notification of the generated event, the state of the communication processor A shifts from the state S3 to the generated event notification completion state S1.

When the release event appears in the state S1, the communication processor A starts counting the second holding time tN. With the start of the timing, the state of the communication processor A shifts from the state S1 to the state S2 during the time tN counting.

When the occurrence event appears in the state S2, the communication processor A stops measuring the time tN. In this case, the state of the communication processor A shifts from the state S2 to the state S1.

Further, when the time tN is completed in the state S2, that is, when the normal state of the route L continues until the time tN elapses from the time when the release event appears, the communication processor A suspends. The release event is notified when the time tN has elapsed. By the notification of the release event, the state of the communication processor A changes from the state S2 to the state S0.
Return to.

As described above, in the present embodiment, the notification of the occurrence event and the release event of the failure that recovers within a short time is omitted, thereby reducing unnecessary event notification and burdening the management processor B. Is reduced.

In the above-described embodiment, the time tM and the time tN can be appropriately selected according to the type of event and the content of the process executed by the management processor B in response to the event notification.

[0026]

According to the present invention, it is possible to reduce the burden on the processor of the event notification destination and to facilitate the exchange service.

According to the second aspect of the present invention, it is possible to reduce the load on the processor of the event notification destination without impairing the handling of the route abnormality. According to the invention of claim 3, when the instantaneous route abnormality frequently occurs, it is possible to reduce the load on the processor of the event notification destination as much as possible.

[Brief description of drawings]

FIG. 1 is a block diagram showing a configuration of an exchange according to an embodiment of the present invention.

FIG. 2 is a diagram schematically showing an example of event notification by the communication processor of FIG.

FIG. 3 is a diagram showing state transitions of the communication processor corresponding to FIG.

FIG. 4 is a diagram schematically showing another example of event notification by the communication processor of FIG.

5 is a diagram showing state transitions of the communication processor corresponding to FIG.

[Explanation of symbols]

 A communication processor (processor) B management processor (other processor) tM time (first fixed time) tN time (second fixed time)

Claims (3)

[Claims] 1. A processor (A) for monitoring a route condition,
The event is sent to another processor (B) only when the route state corresponding to the event continues until a certain time (tN) elapses from the time when a specific event related to the route state appears. A method of notifying an inter-system event of an exchange characterized by notifying. 2. The inter-system event notification method according to claim 1, wherein the event is a transition from an abnormal state of a route state to a normal state. 3. A processor (A) for monitoring a route condition,
Regarding an abnormality occurrence event that is a transition from a normal state to an abnormal state of a route, only when the abnormal state of the route continues until the first constant time (tM) elapses from the time of its occurrence, Abnormal event is sent to another processor (B)
To the abnormal state of the route state from the abnormal state to the normal state and the abnormal state canceling event which is paired with the abnormal state occurring event, the second state from the time of its occurrence.
Of the inter-system event of the exchange, which notifies the other processor (B) of the abnormality cancellation event only when the normal state of the route continues until the fixed time (tN) of Method.