KR100636528B1 - Method for controlling call process in access gateway system - Google Patents

Abstract

A call processing control method in an access gateway system is provided to be capable of interrupting call processing progress on a subscriber line if an abnormal state occurs, so as to prevent pseudo traffic from being excessively generated, thus the system can be protected from overload. An access gateway system monitors a subscriber transition event consecutively occurring correspondingly to a hook event of a subscriber terminal for a preset subscriber state monitoring time, and counts the number of times an abnormal transition event occurs(S31-S33). If the preset subscriber state monitoring time comes, the system compares an abnormal transition event count value counted so far with the reference frequency for determining an abnormal state to confirm whether a subscriber is in the abnormal state(S34,S35). If so, the system stops detecting and monitoring the subscriber transition event for a certain time, and blocks a subscriber line to stop call processing progress for the corresponding subscriber, or executes call cancellation as informing an exchange system of the results(S37).

Description

Method for Controlling Call Process In Access Gateway System

1 is a view schematically showing an interworking structure of a general access gateway system and a switching system.

2 is a diagram illustrating an internal subscriber control structure for stopping an abnormal call processing process in an access gateway system according to the present invention;

3 is a flowchart illustrating a sequence of operations for stopping abnormal call processing progress in an access gateway system according to the present invention.

4 is an operation timing diagram for FIG. 3.

Explanation of symbols on the main parts of the drawings

10: exchange system 20: access gateway system

21: device processing unit 21-1: transition event generation unit

21-2: transition event processing unit 22: device control unit

23: status / failure management unit 24: call processing unit

The present invention relates to call processing in an access gateway system. In particular, when an abnormal state such as a failure of a subscriber station or a failure of a subscriber line, flooding, lightning, or the like occurs, the call processing for the subscriber line is interrupted, resulting in excessive pseudo traffic. The present invention relates to a call processing control method in an access gateway system capable of protecting a system from overload by preventing it from being generated.

Recently, an Access Gateway system has been developed to efficiently handle voice and data traffic for Public Switched Telephone Network / Integrated Service Digital Network (PSTN / ISDN) subscribers and rapidly expanding high-speed xDSL subscribers. The access gateway system accommodates PSTN / ISDN / xDSL subscribers to provide voice and data integration services.

As shown in FIG. 1, the access gateway system 20 defines a local exchange system (LE; 10) and electrical, physical characteristics, procedural requirements, and protocol requirements. The V5.2 protocol connects subscribers to each other.

The conventional access gateway system 20 detects a hook-off event of an AG subscriber when a subscriber connected to it (ie, an AG subscriber) attempts to make a call, and transmits a message corresponding thereto. 10) Initiate call processing by V5.2 protocol interworking by forwarding to the side, and if the Hook-On event of AG subscriber is detected, call processing by forwarding corresponding message to exchange system 10 side. When the hook-flash event of the AG subscriber is detected, the call waiting process is performed by transmitting a message corresponding thereto to the switching system 10 side.

Here, the hook off, hook on, and hook flash events are events related to call start, call end, and call waiting processing of a subscriber, and a message generated by such call processing related events is called pseudo traffic.

By the way, in the conventional access gateway system 20 to process the call processing-related events of the AG subscriber, by passing the pseudo traffic by the V5.2 protocol interworking with the switching system 10 side to perform the corresponding call processing When an abnormal condition such as a failure of a subscriber station or a subscriber line failure, flooding, lightning, etc. occurs in the call processing process, the access gateway system 20 does not recognize the call even though normal call processing is not performed. Pseudo-traffic traffic is repeatedly transmitted to the system 10 side, thereby increasing system load and causing system failure, such as unnecessary processing is repeatedly performed in the access gateway system 20 and the switching system 10. There was this.

SUMMARY OF THE INVENTION The present invention has been made to solve the above-mentioned problems, and an object thereof is to monitor a subscriber transition event occurring for a predetermined time in an access gateway system so as to check an abnormal state of a subscriber, and when the abnormal state is confirmed. It is possible to stop the process of call processing for subscribers.

Another object of the present invention is to prevent abnormal pseudo traffic from being excessively generated by stopping the call processing process when the subscriber of the access gateway system is confirmed to be in an abnormal state, thereby protecting the system from overload, thereby enabling stable system operation. To make it happen.

Yet another object of the present invention is to notify the operator when a subscriber abnormality state is confirmed through monitoring of a subscriber transition event in an access gateway system, thereby enabling rapid maintenance / maintenance for the subscriber.

A feature of the present invention for solving the above object is to monitor the subscriber transition event that occurs continuously in response to the hook event of the subscriber station during the preset subscriber state check time in the access gateway system to detect the abnormal number of transition events Counting; Checking whether the subscriber is in an abnormal state by comparing the abnormal transition event count value counted up to now and the abnormal state determination reference number when the preset subscriber state inspection time is reached; If the subscriber is found to be in an abnormal state, the detection and monitoring of the subscriber transition event is stopped for a certain period of time, and the subscriber line is blocked to stop the processing of the call for the corresponding subscriber, or to release the call and notify the switching system side. Is to implement a call processing control method in an access gateway system comprising a process.

The counting of the number of abnormal transition event occurrences may include starting a subscriber transition event monitoring and a subscriber state check time count for a subscriber status check when a first subscriber transition event corresponding to a hook event of a subscriber station occurs. ; Monitoring a subscriber transition event that is continuously generated in response to a hook event of the subscriber station, and calculating a repeater transition event repetition time taken from when a previous subscriber transition event occurs to when a next subscriber transition event occurs; And comparing the subscriber transition event repetition time and the reference transition event repetition time calculated above to increase or decrease the number of occurrences of the abnormal transition event according to the comparison result.

In the aforementioned access gateway system, the call processing control method detects and monitors a subscriber transition event continuously generated during a preset subscriber station state return check time when a predetermined time elapses after blocking the subscriber line in the abnormal state. Checking whether the subscriber returns to the normal state; If the subscriber does not return to the normal state, the process further comprises the step of stopping the subscriber transition event detection and monitoring for a predetermined time while maintaining the subscriber line in the block state, and notifying the operator of the subscriber abnormal state. .

The checking of whether the subscriber returns to the normal state may include: detecting and monitoring a subscriber transition event continuously occurring during a preset subscriber normal state return test time and counting an abnormal number of transition event occurrences; Checking whether the subscriber returns to the normal state by comparing the abnormal transition event count value and the normal state return determination reference number; When the subscriber returns to the normal state (when the abnormal transition event count value does not exceed the number of normal state return determination criteria), the subscriber station releases the block state of the subscriber line after initializing the abnormal transition event count value to manage the normal state. Characterized in that it comprises a step.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

In the access gateway system of the present invention, by monitoring the transition event of the subscriber, which is the basis of call processing, an abnormal transition event occurs due to a failure of the subscriber station, a subscriber line failure, flooding, lightning, etc. If the subscriber status is recognized as abnormal and stops the call processing process for the corresponding subscriber, it is intended to prevent abnormal repeated traffic from being repeatedly delivered to the switching system. In this case, the switching system 10 and the access gateway system Since the interlocking structure of 20 is the same as that of FIG. 1, the description thereof will be omitted.

In the access gateway system 20 (for example, TAM-HS system) of the present invention, an internal subscriber control structure for stopping an abnormal call processing progress is illustrated in the accompanying drawings, as shown in FIG. The device control unit 22, the state / failure management unit 23, and the call processing unit 24 have a structure that interoperates with each other.

The device processing unit 21 is physically connected to the subscriber line to collect subscriber transition events and report them to the device control unit 22. The device processing unit 21 is physically connected to each subscriber line, so that a hook event (eg, The transition event generator 21-1 and the transition event generator 21-1, each of which comprises a subscriber analog line card for generating a subscriber transition event corresponding to a hook on, a hook off, a hook flash, and the like. Switching & Line Control Card that controls / manages an analog line card, collects the subscriber call processing related transition events generated by the transition event generator 21-1, and reports them to the device controller 22 It includes a transition event processing unit 21-2.

The device controller 22 monitors the subscriber transition event reported from the device processor 21 and transfers the call processing basic message by the subscriber call processing algorithm to the upper call processor 24 to request a corresponding call processing progress. By monitoring subscriber transition event according to the condition of subscriber status check, it checks whether the subscriber is in abnormal state, and if the subscriber abnormal state is confirmed, stops the occurrence of abnormal pseudo traffic by stopping the detection of subscriber transition event for a certain time. At the same time, it reports the subscriber abnormal status to the status / failure management unit 23, detects and monitors the transition event for the subscriber identified as abnormal after the predetermined time elapses (that is, the subscriber is in the line block state). Verify that the subscriber returns to normal status and join If the steady-state check and report back to the subscriber returns to normal status status / fault management (23). This device control function is implemented in a subscriber device access card.

At this time, the device controller 22 calculates a time difference between the subscriber transition events continuously reported from the device processor 21 during the preset subscriber state check time and compares it with the reference transition event repeating interval LS_INTERVAL to generate an abnormal transition event. After counting the number of times, it is checked whether the abnormal transition event count value exceeds the abnormality state determination criterion to check whether the subscriber is in an abnormal state, and when the subscriber abnormal state is confirmed, the detection of the subscriber transition event is stopped for a predetermined time. Calculates the time difference between the subscriber transition events continuously reported from the device processing unit 21 during the subscriber steady state return check time and compares it with the reference transition event iteration time period LS_INTERVAL. After counting the number of times an event occurred Flange design, by checking whether its abnormal transition event count exceeds the normal state return decisions based on the number of subscribers to determine whether the normal state return.

When the subscriber abnormality is reported from the device control unit 22, the state / failure management unit 23 blocks the subscriber line and manages it in the line block state, and manages the block state of the subscriber line in the call processing unit 24. If it is reported that the subscriber in the line block state has returned to the normal state, the subscriber line is unblocked and managed in the normal state at the same time, and the call processing unit 24 indicates that the subscriber line has returned to the normal state. Report as.

The call processing unit 24 starts or ends the call processing through pseudo traffic based on the V5.2 protocol with the exchange system 10 side according to the call processing basic message transmitted from the device control unit 22, but the status / fault When the block state of the subscriber line is reported from the management unit 23, the call processing for the corresponding subscriber is interrupted or the call is released and notified to the switching system 10, and the subscriber in the line block state is normal. If it is reported that the status has been returned, the call processing for the subscriber is performed again normally.

A series of operations for stopping abnormal call processing in an access gateway system having such a configuration will be described with reference to FIGS. 3 and 4 as follows.

3 is a flowchart illustrating a series of operation sequences for stopping abnormal call processing progress in the access gateway system according to the present invention, and FIG. 4 is an operation timing diagram.

First, in order to perform the function of stopping the abnormal call processing, the subscriber state check condition must be set, where the reference transition event repeat interval time (LS_INTERVAL) is set after the hook event is generated in the subscriber line during normal call processing. It refers to a reference time required to generate a hook event (for example, a time taken until a hook off event is generated after a hook on event is generated, typically 3.6 seconds), and is a subscriber transition event to check subscriber status. The number of times of detecting and monitoring an error state, a reference number for determining whether the subscriber is in an abnormal state (number of abnormal state determination criteria), and a reference number for checking whether the subscriber returns to a normal state in case of an abnormal state (number of determinations for returning to a normal state) Block the subscriber line if the subscriber is in an abnormal state. The state of management (e.g., 60 seconds) and the time (e.g., 32 seconds) of detecting and monitoring a subscriber transition event again to confirm that an abnormal subscriber returns to a normal state can be changed by an operator command. Do.

When the subscriber state check condition is set, the transition event generation unit 21-1 of the device processing unit 21 calls a call corresponding to the hook on or hook off event when the subscriber station is hooked on or hooked off by the subscriber. A subscriber transition event related to the processing is generated, and the transition event processor 21-2 sequentially reports the subscriber transition event generated by the transition event generator 21-1 to the device controller 22.

At this time, when the first subscriber transition event is reported, the device controller starts monitoring the subscriber transition event for the subscriber status check (step S31), and the subscriber continuously reported from the device processing unit 21 during the preset subscriber status check time. By calculating the time difference between transition events and comparing it with the reference transition event iteration time (LS_INTERVAL), the number of occurrences of abnormal transition events is counted.

That is, when the first subscriber transition event is reported, the device controller 22 starts the subscriber state check time count, and the time difference between the subscriber transition events continuously reported from the device processor 21, that is, the previous subscriber transition event is reported. After calculating the subscriber transition event repetition time by calculating the time taken from the time point until the next subscriber transition event is reported (step S32), the subscriber transition event repetition time and the reference transition event repetition interval time (LS_INTERVAL) are compared. .

In this case, when it is determined that the subscriber transition event repetition time is shorter than the reference transition event repetition interval time LS_INTERVAL, that is, when the next subscriber transition event occurs less than the reference transition event repetition interval time LS_INTERVAL, the device control unit 22 ) Increases the abnormal transition event count by '1' and, on the contrary, when the subscriber transition event repetition time is found to be longer than the reference transition event repetition time (LS_INTERVAL), that is, longer than the reference transition event repetition time (LS_INTERVAL). When the next subscriber transition event occurs in time, the device controller 22 decreases the abnormal transition event count by '1' (step S33).

Then, the device control unit 22 checks whether the subscriber state inspection time counting internally reaches the preset subscriber state inspection time (step S34), that is, until the subscriber state inspection time is reached, that is, the preset subscriber state inspection time. By calculating the time difference between the subscriber transition event continuously reported from the device processing unit 21 and comparing it with the reference transition event iteration time (LS_INTERVAL) it performs a series of operations to count the number of times the abnormal transition event occurred.

Thereafter, when the preset subscriber state inspection time is reached, the device controller 22 checks whether the subscriber is in an abnormal state by checking whether the abnormal transition event count value counted so far exceeds the abnormal state determination reference number (step S35). ).

If the abnormal transition event count value does not exceed the abnormality state determination criterion number, it means that the subscriber is in a normal state, and thus the subscriber state check operation is restarted after initializing the corresponding abnormal transition event count value. Step S36).

However, when the abnormal transition event count value exceeds the abnormal state determination reference number, this means that the subscriber is in an abnormal state, and thus the device controller 22 stops detecting the subscriber transition event for a predetermined time, thereby causing excessive pseudo traffic. At the same time, it starts counting the subscriber transition event detection stop time, and reports the subscriber abnormal status to the status / failure management unit 23.

At this time, the status / failure management unit 23 blocks the subscriber line as the subscriber abnormality is reported from the device controller 22, manages the subscriber line in the block state, and also manages the block state of the subscriber line. The call processing unit 24 reports the block state of the subscriber line from the state / failure management unit 23, and the call processing unit 24 stops the call processing progress for the corresponding subscriber or releases the call release in progress. Then, this is notified to the exchange system 10 side (step S37).

Thereafter, the device controller 22 checks whether the subscriber transition event detection stop time, which is counted internally, reaches a preset subscriber line blocking time (step S38), that is, until the subscriber line blocking time is reached, that is, the preset subscriber line is reached. The detection and monitoring of the subscriber transition event reported from the device processing unit 21 is stopped during the block time.

When the subscriber transition event detection stop time reaches the preset subscriber line blocking time, the device controller 22 checks whether the subscriber identified as an abnormal state, that is, the subscriber who has been in the line block state until now, returns to the normal state. The subscriber line event monitoring is restarted while the subscriber line is managed in the normal state return check state, and the time difference between the subscriber transition events continuously reported from the device processing unit 21 during the preset subscriber station return check time is calculated. The number of occurrences of an abnormal transition event is counted by comparing with the reference transition event repetition interval time LS_INTERVAL.

That is, when the first subscriber transition event is reported after restarting the subscriber transition event monitoring, the device controller 22 starts the subscriber steady state return check time count, and between the subscriber transition events continuously reported from the device processor 21. After calculating the time difference (i.e., the time taken from when the previous subscriber transition event is reported until the next subscriber transition event is reported), the subscriber transition event repetition time is calculated (step S39), and the subscriber transition event repetition time and reference The transition event repeat interval time (LS_INTERVAL) is compared.

At this time, if it is determined that the subscriber transition event repetition time is shorter than the reference transition event repetition interval time LS_INTERVAL, the device controller 22 indicates that the next subscriber transition event has occurred at a time shorter than the reference transition event repetition interval time LS_INTERVAL. This means that the abnormal transition event count is increased by '1', and conversely, when the subscriber transition event repetition time is found to be longer than the reference transition event iteration time (LS_INTERVAL), it is longer than the reference transition event iteration time (LS_INTERVAL). Since the next subscriber transition event has occurred, the abnormal transition event count is decreased by '1' (step S40).

Then, the device controller 22 checks whether the subscriber steady state return test time, which is counted internally, reaches the preset subscriber steady state return test time (step S41), that is, until the subscriber steady state return test time is reached. A series of counting the number of times an abnormal transition event occurs by calculating a time difference between subscriber transition events continuously reported from the device processing unit 21 during the preset subscriber steady state return test time and comparing it with the reference transition event repetition interval time LS_INTERVAL. The operation will be repeated.

Thereafter, when the preset subscriber steady state return test time is reached, the device controller 22 checks whether the subscriber returns to the normal state by comparing the abnormal transition event count value counted so far with the number of normal state return determination criteria. (Step S42).

If the abnormal transition event count value does not exceed the normal state return determination criterion, it means that the subscriber has returned to the normal state. Thus, after initializing the corresponding abnormal transition event count value, the subscriber is transmitted to the state / fault management unit 23. Will return to its normal state.

At this time, the status / failure management unit 23 releases the block state of the subscriber line as it is reported from the device control unit 22 that the subscriber has returned to the normal state, and manages the subscriber line in the normal state, and also the subscriber line. The return to the steady state is reported to the call processing unit 24 (step S43).

However, if the abnormal transition event count value exceeds the normal state return determination reference number, this means that the subscriber is in an abnormal state, so that the device controller 22 returns to step S37 and stops the subscriber transition event detection and monitoring again for a predetermined time. As a result, excessive pseudo traffic is prevented from being generated, and the subscriber line repeatedly performs the above-described subscriber transition event detection and monitoring operation while maintaining a block state. By notifying the operator of the abnormal state of the subscriber, the abnormal state can be recovered quickly (step S44).

In addition, the embodiments according to the present invention are not limited to the above-described embodiments, and various alternatives, modifications, and changes can be made within the scope apparent to those skilled in the art.

As described above, the present invention monitors the subscriber transition event for a predetermined time in the access gateway system to check whether the subscriber is in an abnormal state, and stops the call processing process for the corresponding subscriber when it is determined to be in an abnormal state to the switching system side. It is possible to prevent abnormal pseudo traffic from being repeatedly delivered, and thus, to prevent excessive occurrence of abnormal pseudo traffic, it is possible to protect the access gateway system and the switching system from overload and at the same time ensure stable system operation. Will be.

In addition, the present invention enables a rapid maintenance / maintenance of a subscriber by notifying an operator when a subscriber abnormality is confirmed through monitoring a subscriber transition event in an access gateway system.

Claims (4)

Counting an abnormal number of transition event occurrences by monitoring a subscriber transition event continuously occurring in response to a hook event of a subscriber station during a preset subscriber state inspection time in an access gateway system; Checking whether the subscriber is in an abnormal state by comparing the abnormal transition event count value counted up to now and the abnormal state determination reference number when the preset subscriber state inspection time is reached; If a subscriber is found to be in an abnormal state, it stops detecting and monitoring subscriber transition events for a certain period of time, and blocks the subscriber line to stop the processing of a call for the corresponding subscriber, or performs a call release and notifies the switching system side. Call processing control method in an access gateway system comprising a process. The method of claim 1, The counting of the number of abnormal transition event occurrences may include: starting a subscriber transition event monitoring and a subscriber state inspection time count for a subscriber state check when a first subscriber transition event corresponding to a hook event of a subscriber station occurs; Monitoring a subscriber transition event that is continuously generated in response to a hook event of the subscriber station, and calculating a repeater transition event repetition time taken from when a previous subscriber transition event occurs to when a next subscriber transition event occurs; And comparing the subscriber transition event repetition time and the reference transition event repetition time calculated above to increase or decrease the number of occurrences of an abnormal transition event according to the comparison result. Processing control method. The method of claim 1, When a predetermined time elapses after blocking the abnormal subscriber line, detecting and monitoring a subscriber transition event continuously generated during a preset subscriber normal state return test time to check whether the subscriber returns to the normal state; If the subscriber does not return to the normal state, the process of stopping the subscriber transition event detection and monitoring again for a predetermined time while maintaining the subscriber line in a block state, and further comprising the step of notifying the operator abnormal status to the operator Call processing control method in an access gateway system. The method of claim 3, wherein The checking of whether the subscriber returns to the normal state may include detecting and monitoring a subscriber transition event continuously occurring during a preset subscriber normal state return test time and counting an abnormal number of transition event occurrences; Checking whether the subscriber returns to the normal state by comparing the abnormal transition event count value and the normal state return determination reference number; When the subscriber returns to the normal state (when the abnormal transition event count value does not exceed the number of normal state return determination criteria), the subscriber station releases the block state of the subscriber line after initializing the abnormal transition event count value to manage the normal state. And controlling the call processing in the access gateway system.

Images