JP2012147367A - Private branch exchange system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a private branch exchange system for guaranteeing telephone communication by switching to another private branch exchange when the entire private branch exchange fails.SOLUTION: The private branch exchange system includes a first private branch exchange, a second private branch exchange and a switching device. When receiving a switching request from the first private branch exchange or the second private branch exchange, the switching device transmits standby information to the first private branch exchange under operation, transmits operation information to the second private branch exchange on standby, and changes the connection destination of a telephone network and an extension terminal to the second private branch exchange.

Description

  The present invention relates to a private branch exchange system that duplicates a private branch exchange that accommodates external lines such as public networks, private lines, and extension terminals such as extension telephones and digital cordless telephones (PHS terminals).

  The technique described in Patent Document 1 is a technique for coping with a partial failure in a private branch exchange. Therefore, the technique of Patent Document 1 cannot cope with a case where the entire private branch exchange has failed.

  Further, although the technology described in Patent Document 2 is a duplex system of a private branch exchange apparatus, the control at the time of switching transmits an “interrupt” message to the ISDN line to place the ISDN line on hold. The system is switched to the emergency system switch, and after the switchover, the "resume" message is transmitted from the emergency system switch to the pending ISDN line, and the ISDN line is returned to the call state. For this reason, the technique described in Patent Document 2 has not been switched in real time.

Sho 62-005759 JP 2001-103158 A

  The present invention provides a private telephone that guarantees calls not only for ISDN lines but also for analog lines in real time without stopping the telephone exchange process by switching to another private branch exchange when the whole private branch exchange is broken. Provide an exchange system.

  The present invention relates to a normally operated private branch exchange and a standby private branch exchange system, and a normal operated private branch exchange between the normal private branch exchange and the standby private branch exchange. A switching device is installed that has a means for recognizing a switching request from a telephone exchange or a waiting private telephone exchange and generating a switching request for the opposite private telephone exchange. The switching device comprises means for notifying the respective private branch exchanges of the current situation (operation / standby) simultaneously with switching. The private branch exchange includes a means for recognizing operation information and standby information.

  In the present invention, memory writing, speech path control operation, and control over lines (extension trunk, outside trunk, etc.) generated during call processing performed in a normally operated private branch exchange are simultaneously on standby. Means are provided for reflecting in the memory, speech path, and line (external trunk, external trunk, etc.) of the private branch exchange.

  Further, the present invention uses the line data to be switched in the memory written from the private branch exchange that is normally operated when the switching request is issued as it is, and rescues only the switching target line. , With means to stand up.

  The problem described above is a private branch exchange system comprising a first private branch exchange, a second private branch exchange, and a switching device, wherein the switching device is switched from the first private branch exchange or the second private branch exchange. When the request is received, the standby information is transmitted to the first private branch exchange in operation, the operation information is transmitted to the second private branch exchange in standby, and the connection destination between the telephone network and the extension terminal is set to the second private branch exchange. This can be achieved by a private branch exchange system that changes to a switch.

  According to the present invention, it is possible to provide a private branch exchange system that can resume the telephone exchange operation while taking over the state of the private branch exchange that has been operated without stopping the telephone exchange operation.

It is a hardware block diagram of a private branch exchange system in a normal state. It is a hardware block diagram of the private branch exchange system after switching. It is the block diagram which showed the time when the private branch exchange 1 is an operation state by two external connection apparatuses and a switching apparatus. It is the block diagram which showed the time when the private branch exchange 2 is an operation state by two external connection apparatuses and a switching apparatus. It is a block diagram explaining the connection relation of two BUF apparatuses. It is the figure which showed the time of the private branch exchange 1 of the memory in two central processing units in an operation state. It is the figure which showed the time of the private branch exchange 2 of the memory in two central processing units in an operation state. FIG. 4 is a diagram showing a memory operation when the private branch exchange 2 is started up when switching from the private branch exchange 1 to the private branch exchange 2 is performed. FIG. 6 is a diagram showing a memory operation when the private branch exchange 1 is started up when the private branch exchange 2 is switched back to the private branch exchange 1. FIG. 3 is a sequence diagram for switching from the private branch exchange 1 to the private branch exchange 2 (startup from software). FIG. 3 is a sequence diagram for switching from the private branch exchange 1 to the private branch exchange 2 (startup from software, part 2). FIG. 10 is a sequence diagram until a “switch request” is generated when an abnormality occurs in an application (software). FIG. 3 is a sequence diagram for switching from the private branch exchange 1 to the private branch exchange 2 (startup from hardware). FIG. 3 is a sequence diagram for switching from the private branch exchange 1 to the private branch exchange 2 (forced switching by a switch). FIG. 4 is a sequence diagram for switching back from the private telephone exchange 2 to the private telephone exchange 1 (startup from software). FIG. 3 is a sequence diagram for switching back from the private telephone exchange 2 to the private telephone exchange 1 (activation from software, part 2).

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings using examples. The same reference numerals are assigned to substantially the same parts, and the description will not be repeated.

  The configuration of the private branch exchange system will be described with reference to FIG. In FIG. 1, a private branch exchange system 100 includes an active private branch exchange 1, a standby private branch exchange 2, and a switching device 3.

  The private branch exchange 1 includes a central processing unit 11, a BUF (buffer) device 12, an external connection device 13, a speech path SW14, an internal trunk 15 connected to the speech path SW14, and a line trunk. 16 and an extension trunk 17. The private branch exchange 2 includes a central processing unit 21 connected to the bus 29, a BUF device 22, an external connection device 23, a speech path SW24, an internal trunk 25 connected to the speech path SW24, a line trunk 26, And an extension trunk 27. The switching device 3 includes two switches 32 and 33 and a forced switching switch 31.

  The BUF device 12 is connected to the central processing unit 11 and the BUF device 22 by a cable. Similarly, the BUF device 22 is connected to the central processing unit 21 with a cable. The extension trunks 17 and 27 are connected to the telephone set 6 that is not subject to switching. The external connection devices 13 and 23 are connected to the switching device 3. The extension trunks 15 and 25 are connected to the extension terminal 4 via the switch 32. The office line trunks 16 and 26 are connected to the public network 5 via the switch 33.

  The BUF device 12 notifies the private branch exchange 2 that is waiting for information on the memory and the communication path. The BUF device 22 receives memory / speech path information from the private branch exchange 1 that is normally operated.

  Next, the switching device 3 connects the extension terminal 4 to be switched to the public network 5. The switching device 3 includes a switching SW 31 that allows forcible switching, and further, the extension trunk 15 and the office trunk 16 accommodated in the normally operated private branch exchange 1 and the standby campus It is connected to an extension trunk 25 and an office trunk 26 accommodated in the telephone exchange 2.

  FIG. 1 also shows a state when the private branch exchange 1 is in an operational state, and it can be seen that the telephone 4 to be switched and the public network 5 are connected to the private branch exchange 1 side. The external connection devices 13 and 23 can transmit a “switching request” to the switching device 3. The switching device 3 that has received the “switching request” transmits “operation” or “standby” information to the external connection devices 13 and 23.

  FIG. 2 is a diagram showing a state in which the private branch exchange 2 is in an operating state with the same configuration of the private branch exchange system as in FIG. In FIG. 2, a telephone 4 to be switched and a public network 5 are connected to the private branch exchange 2 side.

  With reference to FIG. 3, the connection mode between the external connection device 23 accommodated in the private branch exchange 1 and the external connection device 13 accommodated in the private branch exchange 2 and the switching device 3 will be described. Here, FIG. 3 also shows a state in which the private branch exchange 1 is in an operational state. The telephone 4 to be switched and the public network 5 are connected to the private branch exchange 1 side, and the private branch exchange 1 is “operating”. The information shows that the private branch exchange 2 is notified of "standby" information.

  FIG. 4 is a diagram showing a state in which the configuration is the same as that in FIG. 3 and the private branch exchange 2 is in an operating state. The telephone 4 to be switched and the public network 5 are connected to the private branch exchange 2 side, and The exchange 1 is notified of “standby” information, and the private branch exchange 2 is notified of “operation” information.

  With reference to FIG. 5, the connection form between the central processing unit 11 and the BUF device 12 accommodated in the private branch exchange 1 and the central processing unit 21 and the BUF device 22 accommodated in the private branch exchange 2 will be described.

  In FIG. 5, when the central processing unit 11 of the private branch exchange 1 is operating normally, data from the central processing unit 11 enters the BUF device 22 (solid line) via the BUF device 12, and the central processing unit 11. Is expanded to the central processing unit 21.

  When the central processing unit 21 of the private branch exchange 2 is in normal operation, data from the central processing unit 21 enters the BUF device 12 via the BUF device 22 (one-dot broken line). Are expanded to the central processing unit 11.

  With reference to FIG. 6, the configuration of the memory of the central processing unit 11 and the configuration of the memory of the central processing unit 21 will be described. In FIG. 6, when the CPU that is normally operated is the central processing unit 11 of the private branch exchange 1, the data when the memory is controlled by the call processing performed by the central processing unit 11 is also stored in the memory of the central processing unit 21. make a copy. FIG. 6 is a diagram in which the BUF device is omitted from FIG. 5 and the memory is described in detail.

  In FIG. 6, the central processing units 11 and 12 are waiting for various write data from the areas 601 and 607 for storing various data for executing the call processing of the own device and the private telephone exchange in operation. Areas 604 and 610 are provided for storing data when the private branch exchange receives the data.

  Each area has areas 602, 605, 608, 611 for storing data of switching target lines and areas 603, 606, 609, 612 for storing data of non-switching target lines. ing.

  When call processing is performed in the central processing unit 11 and various data is rewritten, the data from the central processing unit 11 is written in the area 610 of the central processing unit 21, so The area 610 of the processing device 21 always has the same contents.

  7 has the same configuration as that of FIG. 6, and when the normally operating apparatus is the central processing unit 21 of the private branch exchange 2, the data of the memory when the memory is controlled by the call processing performed by the central processing unit 21 is shown. Write path.

  When call processing is performed in the central processing unit 21 and various data is rewritten, the data from the central processing unit 21 is written in the area 604 of the central processing unit 11, so that the central processing unit 21 and the area 607 The area 604 of the processing device 11 always has the same contents.

  With reference to FIG. 8, the memory operation performed by the central processing unit 21 accommodated in the private branch exchange 2 when the switching from the private branch exchange 1 to the private branch exchange 2 occurs will be described. In FIG. 8, the central processing unit 21 of the private branch exchange 2 that has received the switching request from the private branch exchange 1 displays an area 611 in which the data for switching target line of the area 610 having the same contents as the private branch exchange 1 is stored. , Copy to area 608 (solid line) and resume call control. As a result, the data of the switching target line is taken over as it is, and the call on the switching target line is switched from the private branch exchange 1 to the private branch exchange 2. The broken line in FIG. 8 is a data copy path immediately before switching.

  With reference to FIG. 9, the memory operation performed by the central processing unit 11 accommodated in the private branch exchange 1 when a switchback from the private branch exchange 2 to the private branch exchange 1 occurs will be described. In FIG. 9, the central processing unit 11 of the private branch exchange 1 that has received the switching request from the private branch exchange 2 displays an area 605 in which the data for switching target line of the area 604 having the same contents as the private branch exchange 2 is stored. , Copy to area 602 (solid line) and resume call control. As a result, the data of the switching target line is taken over as it is, and the call on the switching target line is switched from the private branch exchange 2 to the private branch exchange 1. The broken line in FIG. 9 is a data copy path immediately before switchback.

With reference to FIG. 10, the sequence for switching to the standby private branch exchange 2 when a failure occurs in the private branch exchange 1 that is normally operated will be described. In FIG. 10A, private branch exchange 1 and private branch exchange 2 start up normally. The switching device 3 notifies the private branch exchange 1 of the “operation” state (S1002). On the other hand, the switching device 3 notifies the private branch exchange 2 of the “standby” state (S1003). The private branch exchange 1 is in operation. On the other hand, the private branch exchange 2 is in a standby state. The private branch exchange 1 performs call processing, and controls various memories and speech path switches (S1004). The private branch exchange 1 executes line trunk control (S1005). When the private branch exchange 1 executes the control, the private branch exchange 1 notifies the private branch exchange 2 of the information. As a result, the private branch exchange 2 also executes various memory control and speech path switch control (S1006). The private branch exchange 2 also executes line trunk control (S1007). It should be noted that line trunk relay control and the like are performed under the control of the communication path switch (S1005, S1007) to form a call-enabled state.

  In FIG. 10B, a failure occurs in the private branch exchange 1 (details will be described later with reference to FIG. 11). The central processing unit 11 detects a failure (S1008). The central processing unit 11 sends a “switch request” to the external connection device 13 (S1009). The external connection device 13 that has received the “switching request” sends a “switching request” to the switching device 3 (S1010).

  When the switching device 3 receives the “switching request”, it sends a “switching instruction” to the external connection device 13 (S1011). When receiving the “switching instruction”, the external connection device 13 notifies the central processing unit 11 of the “switching instruction” (S1012). The external connection device 13 notifies the central processing unit 11 that it is in the “standby” state (S1013). The central processing unit 11 that has received the “switching instruction” determines whether or not the failed part that has occurred is a reboot target (S1020). When the central processing unit 11 determines that the reboot is necessary, the central processing unit 11 performs the reboot (S1021), and initializes the private branch exchange 1. If it is determined in step 1020 that reboot is not necessary, the central processing unit 11 initializes only the faulty part (S1022) and transitions to a standby state (S1014). As a result, a call in a stable state such as during a call can be kept in the state.

Further, the switching device 3 sends a “switching instruction” to the external connection device 23 of the private branch exchange 2 (S1015). When receiving the “switching instruction”, the external connection device 23 notifies the central processing unit 21 of the “switching instruction” (S1016). The external connection device 23 notifies the central processing device 21 that it is in the “operation” state (S1017). The central processing unit 21 that has received the “switching instruction” makes a transition to the operation state according to the “operation” state received in step 1017 (S1018). The central processing unit 21 writes data from the private telephone exchange 1 that has been normally operated, and copies the area 611 having the same contents as the private telephone exchange 1 to the data area 608 used in normal call processing, and then restarts. Is raised (S1019).
With the above processing, the private branch exchange 2 can start operation while the call setting state of the private branch exchange 1 is continued.

  With reference to FIG. 11, a sequence until a switching instruction is generated when the application program (application) shown in FIG. 10 becomes a failure will be described. In FIG. 11, a WDT (Watch Dog Timer) timer set in the microcomputer (MPU) is started immediately after rising (S1401). The application periodically restarts the timer (S1402). When the application is normal, the MPU confirms the normality of the application by not expiring the timer. However, if an abnormality occurs in the application, the timer cannot be restarted, so the WDT timer expires (S1407). The MPU determines that the application is abnormal, and issues a forced interruption to the application (S1408). When an interrupt occurs, the application determines that the interrupt is due to a failure (S1409). The application sends a “switch request” to the external connection device 13 (S1411). With the above processing, it is possible to switch even when an application becomes a failure. It is because another part of the program can determine that a fault has occurred even when a fault has occurred.

  With reference to FIG. 12, a description will be given of a sequence for switching from the hardware to the standby private branch exchange 2 when a failure occurs in the private branch exchange 1 that is normally operated. In FIG. 12, after the private branch exchange 1 and the private branch exchange 2 start up normally, call processing is performed in the private branch exchange 1, the information is notified to the private branch exchange 2, and the control of the communication path switch and the line are also made on the private branch exchange 2 side. Until the trunk control is executed, it is the same as FIG.

  The external connection device 13 monitors at any time whether the central processing unit 11 of the private branch exchange 1 that is normally operated is operating normally (S1101). Here, in the central processing unit 11, a failure that prevents the software from operating occurs. The external connection device 13 detects an abnormality because there is no response to the abnormality monitoring (S1103). The external connection device 13 sends a “switching request” to the switching device 3 (S1104). Thereafter, the same operation as that described in FIG. 10B is executed, and the switching is completed.

  With reference to FIG. 13, a sequence for forcibly switching from the private telephone exchange 1 that is normally operated to the standby private telephone exchange 2 will be described. FIG. 13 shows a procedure for switching the private branch exchange by turning on the forcible changeover switch 31 of the switching device 3 even when the state shown in FIG. 10 or FIG. 12 is not switched. . In FIG. 13, the external connection device 13 in which the forced changeover switch 31 is turned ON sends a “switching instruction” to the private branch exchange 1 and the private branch exchange 2. Thereafter, the same operation as that described in FIG. 10B is executed, and the switching is completed.

  The operation for switching from the normally operated private branch exchange 1 to the standby private branch exchange 2 has been described above.

  It is also possible to switch back from the private branch exchange 2 to the private branch exchange 1. This will be described with reference to FIG. FIG. 14 shows a sequence of switching from software.

  In FIG. 14A, the private branch exchange 1 is switched to the private branch exchange 2 for some reason (S1301), the private branch exchange 2 is in operation, and the private branch exchange 1 is on standby. In this state, the private branch exchange 2 performs call processing, and executes various memory control, speech path switch control (S1302), and line trunk control (S1303). The private branch exchange 2 notifies the private branch exchange 1 of the information. The private branch exchange 1 executes various memory controls, speech path switch control (S1304), and line trunk control (S1305). In addition, line trunk relay control and the like are performed by the control of the communication path switch (S1303, 1305), thereby forming a call-enabled state.

  In FIG. 14B, the private branch exchange 2 has a failure, and the central processing unit 21 detects the failure (S1306). The central processing unit 21 sends a “switch request” to the external connection device 23 (S1307). Next, the external connection device 23 that has received the “switching request” sends a “switching request” to the switching device 3 (S1308).

  When the switching device 3 receives the “switching request”, it sends a “switching instruction” to the external connection device 23 (S1309). Next, when the external connection device 23 receives the “switching instruction”, it notifies the central processing unit 21 of the “switching instruction” (S1310). The external connection device 23 also notifies the central processing unit 21 that it is in the “standby” state (S1311). The central processing unit 21 that has received the “switching instruction” determines whether the failed part that has occurred is a reboot target (S1318). When the central processing unit 21 determines that the reboot is necessary, the central processing unit 21 performs the reboot (S1319), and initializes the private branch exchange 2. If it is determined in step 1318 that there is no need for reboot, only the faulty part is initialized (S1320), and a transition is made to a standby state according to the “standby” state received in step 1311 (S1312). As a result, a call in a stable state such as during a call can be kept in the state.

  Further, the switching device 3 sends a “switching instruction” to the private branch exchange 1 (S1313). Next, when the external connection device 13 receives the “switching instruction”, it notifies the central processing unit 11 of the “switching instruction” (S1314). The external connection device 13 also notifies the central processing unit 11 that it is in the “operation” state (S1315). The central processing unit 11 that has received the “switching instruction” makes a transition to the operation state in accordance with the “operation” state received in step 1315 (S1316). The central processing unit 11 writes data from the private branch exchange 2 that has been normally operated, and copies the area 605 having the same contents as the private branch exchange 2 to the data area 602 used for normal call processing, and then restarts. Is raised (S1317). As described above, the private branch exchange 1 can start operation while the state of the private branch exchange 2 is continued.

  DESCRIPTION OF SYMBOLS 1 ... Private branch exchange, 2 ... Private branch exchange, 3 ... Switching apparatus, 4 ... Extension terminal, 5 ... Public network, 6 ... Extension terminal (Excluded from switching), 11 ... Central processing unit, 12 ... BUF apparatus, 13 ... External connection device, 14 ... Communication path switch, 15 ... extension trunk, 16 ... office trunk, 17 ... extension trunk (not subject to switching), 21 ... central processing unit, 22 ... BUF device, 23 ... external connection device, 24 ... Communication path switch, 25 ... extension trunk, 26 ... office trunk, 27 ... extension trunk (not subject to switching), 31 ... forced switching switch, 32 ... extension terminal connection destination selection switch, 33 ... network connection destination selection switch, 100 ... Private branch exchange system.

Claims (2)

A private branch exchange system comprising a first private branch exchange, a second private branch exchange, and a switching device,
When the switching device receives a switching request from the first private branch exchange or the second private branch exchange, the switching device transmits standby information to the first private branch exchange in operation, and the second private branch exchange is waiting for the second private branch exchange. A private branch exchange system characterized in that operational information is transmitted to the private branch exchange, and the connection destination between the telephone network and the extension terminal is changed to the second private branch exchange. A private branch exchange system according to claim 1,
The private branch exchange in operation sends the memory write and speech path control data generated in the call processing to the private branch exchange in standby,
The standby private branch exchange stores the memory write and speech path control data in a communication data storage area, and moves the memory write and speech path control data to an actual operation area when receiving operation information. A private branch exchange system.

Images