JP2953183B2 - Maintenance operation module monitoring method - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a maintenance operation module monitoring method for monitoring the operation status of a maintenance operation module and notifying a maintenance center.

[0002]

2. Description of the Related Art In a conventional monitoring and alarm information transfer system, a first data link for transferring control information of an exchange, alarm information from the exchange, and operation information such as an operation file between the exchange and a maintenance center is provided. A second data link is provided for transferring control information to limited exchanges and monitoring and alarm information from the exchanges.

FIG. 2 is a block diagram showing an example of a conventional monitoring / alarm information transfer system. In FIG. 2, a maintenance operation module (hereinafter, MDL) 200 is an exchange (hereinafter, SWE) 1
00 and the maintenance center (below CTR) to 800 and the interface. First route for transmitting and receiving control information and response information to through both software SWE100 between SWE100 and MDL200 (hereinafter RTA) 300
When a second route for transmitting and receiving a limited exchange control information and response information for an emergency software without the passing (hereinafter R
TB) 400.

The RTA 300 has an X25 line controller (hereinafter referred to as XLCA) 201 in the MDL 200 and a public network (hereinafter referred to as N).
W) 500 and an X25 line controller (hereinafter referred to as XLCB) 801 in the CTR 800 are connected to form an X25 data link (hereinafter DTL) 600. Also, RTB
Reference numeral 400 denotes an individual line control device (hereinafter, ILC) in the MDL 200.
A) 201 is connected to an individual line control device (hereinafter, ILCB) 802 in the CTR 800, and is connected to another link (hereinafter, LK).
700.

[0005] The MDL 200 provided on the SWE 100 side to communicate with the CTR 800 becomes a failure and the SWE 100
If communication between the CTR 100 and the CTR 800 becomes impossible,
The CTR 800 side detects a failure by the following two methods.
In the first method, general communication is performed using the X25 protocol. When the MDL 200 goes down, the XLCA 20 under the central processing unit (CPU) 203 is used.
1 cannot be controlled. The CTR 800 detects the disconnection of the X25 DTL 600 as a line abnormality. Also the second
In the method of SWE1, even if the MDL 200 becomes a failure such as a system down, the SWE1 is not affected by the software.
It has a hardware configuration capable of transmitting and receiving monitoring information and control information on the 00 side. However, the failure information of the MDL 200 is not transmitted to the LK 700 because the failure information is detected by the line failure of the first method.

[0006]

In the conventional monitoring and alarm information transfer system, when a device on the exchange side fails, the aggregated alarm information is transferred to the exchange side through another link. However, when the maintenance operation module causes a failure such as a system failure, it is not known whether the failure is due to an abnormality in the X25 line controller or a failure in the power supply system. I could only do it.

The alarm information transfer route provided by a separate link provided between the exchange and the maintenance center is mainly for transferring the alarm information on the exchange side. There was a problem that information transfer was not assumed.

[0008]

According to the present invention, in order to solve the problems], detects a fault in the operation and maintenance module relays the monitoring information and control information to monitor the operation status of an exchange maintenance center to interface with and exchange a maintenance operation module monitoring method of, transmitting and receiving control information and the response information of the communication control Sofutou <br/> the exchange and through the share of the respective online software between the operation and maintenance module and the switch a first route, provided a second route for transmitting and receiving control information and response information for emergency of the exchange of the communication control software without the passing, the said exchanger is obtained from the second route maintenance the coercive a condition obtained by determining the information of the normality confirmation test and a driving state the maintenance operation module of the central processing unit of the management module based on Start pseudo terminal connected to its own exchange internal subscriber line after detecting a failure in the operational modules and normality confirmation test performed calling operation to the maintenance center
By sending a result, the maintenance center side before it receives
Serial characterized by analyzing the failure of the operation and maintenance module from the results of the data normality confirmation test OM Mogi
A method for monitoring the rules is obtained .

Further, the pseudo end weekend operation and maintenance module monitoring method and performing a calling operation to the telephone addressed the maintenance center by passing <br/> the public circuit-switched network is obtained.

[0010]

Next, the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing an embodiment of a maintenance operation module monitoring method according to the present invention.

In FIG. 1, an exchange includes a subscriber circuit device (hereinafter referred to as LC) 1 of a pseudo terminal and a communication path device (hereinafter referred to as SPE).
2 and an MDL 3, and the SPE 2 includes a monitoring and alarm information interface controller (hereinafter, IFCB) 22 controlled by the CPU 21. The MDL 3 includes a data link controller (hereinafter, DLC) 32 and a monitoring / alarm interface controller (hereinafter, IFCA) 33 controlled by a CPU 31 that executes software. Further, the CTR 7 is provided with a telephone (hereinafter referred to as TEL) 9 and a workstation (hereinafter referred to as WKS) 10 for performing a man-machine interface with the exchange.

The SPE 2 is a line terminating device (hereinafter referred to as T
RM) 11, Public switched telephone network (PSNW) 8, CT
Connected to TEL9 via R7. Also, SPE2
And the MDL 3 are connected by a high-speed LAN (hereinafter referred to as LANA) 4 by an optical communication system for transferring control information and the like, and the IFCB 22 is connected to the CS for transferring the monitoring and alert information.
It is connected to the INFA 33 by a MA / DA low-speed LAN (hereinafter, LANB) 5. LANA4 is C
This is a main line route for transferring control information and response information between both devices operated under the control of the PU 21 and the CPU 31. The LANB 5 is a route that operates without software intervention between the two devices, and is a backup route that can operate even when the main line route fails.

[0013] between the CTR7 an exchange D in the MDL3
LC32 and public data link network are connected via (hereinafter PSDL) 6 and the <br/>. The WKS10 is for performing man-machine interface Fe ace with an exchange, the control information, transmit and receive response information and autonomous messages or the like.

In order to guarantee the normality of the route of the monitoring and alarm information, the IFCA 33 of the MDL 3 is switched to the I
A normality confirmation test is performed on FCB22. There are two methods for this normality check test.
When the specific pattern is transmitted from the IFCA 33 of the MDL 3, the IFCB 22 receiving the specific pattern returns the increment data to the received data. Also after that IF
A simulated fault report is made from the CB 22 and the normality of the MDL 3 is confirmed by a confirmation response from the MDL 3 side.

Next, in the second method, the CPU 3 of the MDL 3
1 has a console interface 34 for notifying the operating state, and the IFCA 22 of the SPE 2
The operation state of U31 can be read. Therefore, I
As a normality confirmation test from FCB22, C
The state of the PU 31 is read.

If both test results obtained by the first method and the second method are defective, the CPU 21
Judge as 3 obstacles. If the MDL 3 determines that a failure has occurred, the IFCB 2 connected to the LC 1 in the local exchange is switched on.
2 performs a calling operation to a predetermined telephone number of CTR7. LC1 is SPE2 → TRM11 → PSNW8 → CTR7 → TE as in the case of general subscribers
An outgoing connection operation is performed along the route of L9.

The CTR 7 analyzes the information by the TEL 9 and knows that it is a failure notification from the exchange, and can determine from the transmitted data that a failure has occurred in the MDL 3, so that the failure can be repaired. quickly respond to
It is possible.

[0018]

As described above, according to the present invention, the failure information at the time of system down of the maintenance and operation module can be transmitted to the local switching system without connecting the maintenance and operation module and the switching system by a dedicated line as in the conventional system. By connecting to the subscriber's circuit side, it is possible to notify the maintenance center using the public switched telephone network.

[Brief description of the drawings]

FIG. 1 is a block diagram showing an embodiment of a maintenance operation module monitoring method according to the present invention.

FIG. 2 is a block diagram illustrating an example of a conventional monitoring / alarm information transfer method.

[Explanation of symbols]

1 subscriber circuit device (LC) 2 channel device (SPE) 3 OM module (MDL) 4 Fast LAN (LANA) 5 slow LAN (LAN B.) 6 public data link network (PSDL) 7 coercive Mamoruse printer (CTR) Reference Signs List 8 public switched telephone network (PSNW) 9 telephone (TEL) 10 workstation (WKS) 11 line termination device (TRM) 21, 31 central processing unit (CPU) 22, 33 monitoring and alarm interface control device (IF)
CA, IFCB) 32 Data link controller (DLC) 34 Console interface

Claims (2)

(57) [Claims] 1. A maintenance operation module monitoring method for detecting a failure in the operation and maintenance module relays the monitoring information and control information to monitor the operation status of the switching center and the maintenance center and the interface to and exchange, Online software between the exchange and the maintenance operation module
A first route and through the communication control software of the inner transmitting and receiving control information and the response information of the exchange, the communication system
His software provided a second route for transmitting and receiving control information and response information for emergency of the exchange without the passing, the <br/> exchange of the maintenance and operation modules from the second route operating state and the maintenance after detecting failure of the operation and maintenance module based on the obtained condition by determining information normality confirmation test from the operation module of the internal self-exchange subscribers of the central processing unit Activate the pseudo terminal connected to the line to make a call to the maintenance center
In addition, by transmitting the result of the normality check test , the maintenance center side receives the data of the received result of the normality check test.
Operation and maintenance module monitoring method characterized by analyzing the failure of the operation and maintenance module from. Wherein said pseudo end weekend operation and maintenance module monitoring method according to claim 1, characterized in that the calling operation to the telephone addressed the maintenance center by through the public circuit-switched network.