JP2002044238A - Private branch exchange - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a program renewal method in a private branch exchange wherein program can be updated irrespective of operating condition of the private branch exchange. SOLUTION: In an exchange control unit 17a of a private branch exchange, two faces of a program area Aa1 and a program area Ba2 are defined in order to easily update a program. Besides, a memory area a3 for exchange control which is used for exchange control and a calling state memory area a4 which is used for controlling the state of speech or the like are installed. The program area Aa1 and the program area Ba2 are used as an operation face and a waiting face and switched by control of a system monitoring part.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to a private branch exchange,
In particular, the present invention relates to a program updating method that enables a program to be updated without stopping the system in a private branch exchange that uses a storage program method.

[0002]

2. Description of the Related Art Conventionally, in this type of program update system, for example, a first system in which a duplicated CPU is used to install an updated program in a standby system before switching to an active system, or a premises such as a file loading device. A program is loaded into a memory inside the private branch exchange using an external device or a maintenance console separate from the exchange, and the program is loaded into an IPL (Initial Program L).
There is a second method of updating a program by performing an O.D. There is also a third method in which an (EDIT) data editing device provided outside the private branch exchange is connected to the private branch exchange via a communication line, and a part of the program is patch-corrected.

In the first method, in a configuration where the control unit of the private branch exchange is duplicated, a program to be updated is loaded into a standby system irrelevant to the operation, and after the loading is completed, the active system is replaced with the standby system. , The program is updated without stopping the system. This method is disclosed in JP-A-8-242474.

In the second system, a private branch exchange is provided with a file loading device and a maintenance test device provided with a file loading means, so that even if a failure occurs in one of the devices, an external program exists. Can be loaded into the private branch exchange. This method is disclosed in JP-A-2-3844.

In the third system, an external device connected by a communication line is arranged separately from the private branch exchange, a part of the program is edited, and the edited part of the data is temporarily stopped in the system. Then, the program is partially updated by loading the data into the memory inside the private branch exchange and restarting the system when all the loading is completed. This method is disclosed in Japanese Unexamined Patent Publication No. 60-182294.
No. 6,009,045.

[0006]

In the above-mentioned conventional program updating method, the first method presupposes a system configuration in which the control unit of the private branch exchange is duplicated. In the case of failure, or in a private branch exchange with a single control unit, the program cannot be updated.

Further, in the case of the second method, the program is temporarily saved in a dedicated memory in the private branch exchange, and an IPL is required to load the saved program into an actual program area. There is a problem that the system is stopped every time the system is updated, and the program cannot be updated depending on the operation state of the private branch exchange.

Further, in the case of the third system, only a part of a program such as a patch can be updated, and the system must be temporarily stopped in order to make the patch data valid. Depending on the operation status of the private branch exchange, Cannot update the program.

It is an object of the present invention to solve the above-mentioned problems and to provide a private branch exchange that can update a program regardless of the operation state of the private branch exchange.

[0010]

A private branch exchange according to the present invention controls switching between two program storage areas and the two program storage areas to load a program and to switch the operation of the program. A switching control function.

That is, the private branch exchange according to the present invention is a private branch exchange adopting a storage program system, a program storage area on two sides, a function of performing program load and switching control of a program operation side, and a LAN (Lo).
cal Area Network) -a function for controlling an I / F (interface) and a maintenance I / F
(Read only memory) provided in the control unit.

[0012] Thus, the entire program can be updated without duplicating the configuration of the control unit of the private branch exchange. At this time, no IPL or temporary system stop is required. Regardless, the program can be updated.

Further, two areas for storing programs in a memory inside the private branch exchange are provided, and program data managed internally or externally is loaded on a standby surface to be used when a maintenance person or a failure occurs or at a predetermined time. In addition, by switching between the operation side and the standby side of the program, the program can be instantly updated regardless of the system configuration of the private branch exchange and without stopping the system.

The program update method in the private branch exchange according to the present invention can also be realized by logically dividing the magnetic disk of the storage device and managing two programs.

[0015]

Next, an embodiment of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing a configuration of a private branch exchange according to one embodiment of the present invention. In FIG. 1, a private branch exchange 1 includes digital telephone I / F (interface) circuits 11-1 to 11-n and an analog telephone I / F.
F circuits 12-1 to 12-n, switch 13, central office trunk I / F circuits 14-1 to 14-n, dedicated line trunk I / F circuits 15-1 to 15-n, CPU 16, It comprises a control unit 17, a LAN I / F card 18, a maintenance I / F card 19, and a storage device 20, and includes a digital multi-function telephone 2-1 to 2-n and an analog telephone 3-1 to
3-n, a public network 4, a dedicated line network 5, a LAN network 6, and a maintenance console 7, respectively.

The control unit 17 controls each unit in the private branch exchange 1. The storage device 20 includes a magnetic disk device (HD: hard disk) 21 and a floppy disk device (FD) 22 for performing installation on the magnetic disk device 21.

Digital telephone I / F circuits 11-1 to 11-11
-N are digital multifunction telephones 2-1 to 2-n, respectively.
Is connected to the private branch exchange 1, and the analog telephone I / F circuit 12
-1 to 12-n connect the analog telephones 3-1 to 3-n to the private branch exchange 1.

Office trunk I / F circuits 14-1 to 14-
n connects the public network 4 and the private branch exchange 1. The leased line trunk I / F circuits 15-1 to 15-n connect the leased line network 5 and the private branch exchange 1. LAN I / F card 18 is LA
The interface with the N network 6 and the maintenance I / F card 1
Reference numeral 9 denotes an interface with the maintenance console 7.

The switch 13 includes digital telephone I / F circuits 11-1 to 11-n and an analog telephone I / F circuit 12-n.
1 to 12-n and an office trunk I / F circuit 14-1 to 14-1
4-n and dedicated line trunk I / F circuits 15-1 to 15-
n, LAN I / F card 18, and maintenance I / F card 1
9 respectively.

FIG. 2 is a block diagram showing the configuration of the control unit 17 of FIG. In FIG. 2, a control unit 17 includes an exchange control unit (RAM: random access memory) 17a for mainly controlling the exchange process of the private branch exchange 1, and a system monitoring unit (ROM: read only memory) 17b for monitoring the system.
It is composed of

In the exchange control unit 17a, an exchange processing control unit 172 for mainly controlling call processing and a failure diagnosis control unit 173 for performing failure monitoring are operated under the control of an exchange control monitor 171. Further, the system monitoring unit 17b includes a restart control unit 175 that controls restart processing of the entire system, and a program load control unit 176 that controls loading of a program.
A program update control unit 177 for controlling program update, a LAN I / F control unit 178 for performing LAN I / F control, and a maintenance I / F control unit 179 for controlling an interface with the maintenance console 7. The operation is controlled by the monitoring monitor 174.

The exchange control section 17a operates on a RAM, and can freely update a program. The system monitor 17b operates on the ROM so that the program is not easily destroyed.

FIG. 3 is a block diagram showing the configuration of the exchange control unit 17a of FIG. In FIG. 3, the exchange control unit 17a
Is a program area Aa1 and a program area Ba2, which are defined in order to easily update a program, an exchange control memory area a3 for performing exchange control, and a call state for managing a call state and the like. And a memory area a4.

The program area Aa1 and the program area Ba2 are treated as an operation side and a standby side. By switching the two program areas under the control of the system monitoring section 17b, the control section 17 of the private branch exchange 1 is switched.
Can be updated without duplication and without stopping the system.

FIG. 4 is a diagram showing a configuration example of the magnetic disk drive 21 of FIG. In FIG. 4, the inside of the magnetic disk device 21 mounted in the storage device 20 is divided into four logical partitions, and a program A is installed in a partition (1) b1 and a program B is installed in a partition (2) b2. You. Further, two pieces of station data A and B for starting the private branch exchange 1 are managed in the partitions (3) b3 and (4) b4.

FIGS. 5 to 11 are sequence charts showing the operation of the private branch exchange 1 according to one embodiment of the present invention. The operation of the private branch exchange 1 according to one embodiment of the present invention will be described with reference to FIGS.

In the storage unit 20, a program is installed in the magnetic disk device 21 from the floppy disk device 22 or the maintenance console 7. Hereinafter, a sequence when the program A is installed in the magnetic disk device 21 while the program A is operating as an operation surface will be described.

First, a sequence for performing installation from the floppy disk device 22 to the magnetic disk device 21 will be described with reference to FIG. 2 and FIGS. Storage device 2
The system monitor 174 detects a request from the maintenance console 7 by inserting a floppy disk (not shown) into the floppy disk device 22 of No. 0 and sending an FD → HD installation start request (c01) from the maintenance console 7. Then, a maintenance task generation request (c02) is transmitted to the program A.

In the program A, a maintenance task is newly generated in addition to the replacement task, and at the same time, the replacement task sleeps (c03). In the generated maintenance task, FD →
The start of the HD installation process (c04) is started, and the data of the program B is read from the floppy disk in minimum units (c05) in order to minimize the sleep time of the replacement task.

The data read from the floppy disk is temporarily stored in the exchange control memory area a3, and a read completion notice (c06) is sent from the maintenance task. Is temporarily put to sleep, and the exchange task is resumed (c07) to resume the exchange processing, thereby restarting the temporarily interrupted exchange processing (c08).

Thereafter, the maintenance task that has been temporarily sleeping is restarted (c09) by the timer control of the system monitoring monitor 174, so that the replacement task sleeps again (c10), and FD → H in the maintenance task.
The D installation process is resumed (c11), and the temporarily stored data of the program B is written to the partition b2 of the magnetic disk device 21 (c12).

The maintenance task notifies the system monitoring monitor 174 that the writing has been completed (c13), sleeps again, and at the same time, resumes the exchange task (c14). The exchange task resumes the exchange process again (c15).

As described above, the processes from c02 to c15 are performed until all the data on the floppy disk is written to the magnetic disk device 21. When the writing of all the data on the floppy disk to the magnetic disk device 21 is completed, In the maintenance task, an FD → HD installation end notification (c16) is sent out, the FD → HD installation end notification (c17) is sent from the system monitoring monitor 174 to the maintenance console 7 of the request source, and the replacement processing task is executed again. A restart notification (c18) is issued, and in the replacement task, the replacement process is restarted (c19).

Next, external data of the maintenance console 7 → H
The installation sequence to D will be described with reference to FIGS. 2, 3, 4, and 6. FIG. The program B is installed in the maintenance console 7 in advance.

From the maintenance console 7, external data → H
By sending the D installation start request (d01), the system monitoring monitor 174 detects a request from the maintenance console 7, and sends a maintenance task generation request (d02) to the program A. As tasks are created in addition to exchange tasks,
The exchange task sleeps (d03).

In the generated maintenance task, external data → H
The start of the D installation process (d04) is activated, and the data of the program B is read from the maintenance console 7 in minimum units from the maintenance console 7 in order to minimize the sleep time of the replacement task (d05).

The data read from the maintenance console 7 is temporarily stored in the exchange control memory area a3, and a read completion notice (d06) is sent out. At the same time, the system monitoring monitor 174 temporarily stores the program A maintenance task. After the sleep, the exchange task is resumed (d07) in order to resume the exchange process, whereby the temporarily interrupted exchange process is resumed (d08).

Thereafter, the maintenance task that has been temporarily sleeping is restarted (d09) by the timer control of the system monitoring monitor 174, so that the replacement task sleeps again (d10), and the maintenance task external data → The HD installation process is resumed (d11), and the temporarily stored data of the program B is written to the partition b2 of the magnetic disk device 21 (d12).

The maintenance task notifies the system monitor monitor 174 that the writing has been completed (d13), and the maintenance task sleeps again, and at the same time, the replacement task resumes (d1).
4) Then, in the exchange task, the exchange process is restarted (d15).
I do.

As described above, the processing from d02 to d15 is performed until all the data from the maintenance console 7 is written to the magnetic disk device 21, and the writing of all the data of the program B to the magnetic disk device 21 is completed. At this point, the maintenance task sends an external data → HD installation process end notification (d16), and the system monitor 1
The external data → HD installation completion notification (d17) is sent from the maintenance console 7 to the requesting maintenance console 7 and a replacement processing task restart notification (d18) is issued again. The replacement task is restarted (d19) in the replacement task.

In the above two sequences, the exchange task and the maintenance task are controlled in a well-balanced manner by the system monitoring monitor 174, so that the exchange processing can be performed without stopping.

Next, a sequence for loading the program B installed in the magnetic disk device 21 into the program area B (standby plane) a2 in the above two sequences will be described with reference to FIGS. 2, 3, 4, and 7. Will be explained.

By sending an HD → standby plane load start request (e01) from the maintenance console 7, the system monitoring monitor 174 detects the request from the maintenance console 7, and the maintenance task generation request (e02) is sent to the program A. In the program A, a maintenance task is newly generated in addition to the replacement task, and at the same time, the replacement task sleeps (e03).

In the generated maintenance task, HD → standby plane load processing start (e04) is started, and the magnetic disk drive 21 is started to minimize the sleep time of the replacement task.
And read out the data of the program B in the minimum unit (e05).

The data read from the magnetic disk device 21 is temporarily stored in the exchange control memory area a3.
At the same time as sending the read completion notice (e06), the system monitoring monitor 174 temporarily puts the maintenance task of the program A to sleep, and then resumes the exchange task (e07) to resume the exchange processing, thereby temporarily The exchange process which has been interrupted is restarted (e08).

Thereafter, the maintenance task that has been temporarily sleeping is restarted (e09) by the timer control of the system monitor 174, so that the replacement task sleeps again (e10), and the maintenance task goes from HD to standby. The surface loading process is restarted (e11), and the temporarily stored data of the program B is written to the program area Ba2 (e12).

The maintenance task notifies the system monitor 174 that the writing has been completed (e13), and the maintenance task sleeps again, and at the same time, the replacement task resumes (e1).
4) Then, in the exchange task, the exchange process is restarted (e15).
I do.

As described above, the processes from e02 to e15 are performed until all the data of the program B in the magnetic disk device 21 is written to the program area Ba2. → The standby plane loading end notification (e16) is sent out, and the system monitor 174 sends H to the maintenance console 7 that has issued the request.
D → Standby plane loading end notification (e17) is sent out, and an exchange processing task restart notification (e18) is issued again. In the exchange task, the exchange processing is restarted (e19).

Next, the sequence of loading the program B from the maintenance console 7 directly into the program area B (standby plane) a2 in the event that the storage device 20 fails, is shown in FIGS. 8 will be described.

By sending the external data → standby plane load start request (f01) from the maintenance console 7, the system monitoring monitor 174 detects the request from the maintenance console 7, and the maintenance task generation request (f02) is sent to the program A. The maintenance task is newly generated in addition to the replacement task in the program A, and at the same time, the replacement task sleeps (f03).

In the generated maintenance task, the external data → standby plane load process start (f04) is started, and the data of the program B is divided into the minimum unit from the maintenance console 7 in order to minimize the sleep time of the replacement task. Read (f05).

The data read from the maintenance console 7 is temporarily stored in the exchange control memory area a3, and a read completion notice (f06) is sent out. At the same time, the system monitoring monitor 174 temporarily stores the maintenance task of the program A. After the sleep, the exchange task is resumed (f07) in order to resume the exchange process, whereby the temporarily interrupted exchange process is resumed (f08).

After that, the maintenance task that has been temporarily sleeping is resumed (f09) by the timer control of the system monitoring monitor 174, so that the replacement task sleeps again (f10), and the maintenance task uses external data. → The standby plane loading process is restarted (f11), and the temporarily stored data of the program B is written to the program area Ba2 (f12).

The maintenance task notifies the system monitor monitor 174 that the writing has been completed (f13), and the maintenance task sleeps again and the replacement task resumes (f1).
4) Then, in the exchange task, the exchange process is restarted (f15).
I do.

As described above, the processing from f02 to f15 is performed until all the data of the program B in the maintenance console 7 has been written into the program area Ba2. Data → standby plane loading end notification (f16) is sent out,
External data → standby plane load end notification (f1
7) is sent out again, and the exchange processing task restart notification (f1) is sent again.
8) is issued, and the exchange process is resumed in the exchange task (f1).
9).

Next, a switching sequence of the operation side according to an instruction from the maintenance console 7 will be described with reference to FIGS. 2, 3, 4, and 9. FIG.

By transmitting the operation plane switching request (g01) from the maintenance console 7, the system monitoring monitor 174 transmits an event reception end request (g02) to the program A which is the operation plane. Exchange processing end processing (g03) is performed.

In this exchange processing end processing (g03), a newly generated event is temporarily stored in the exchange control memory area a3. The system monitoring monitor 174 monitors (g04, g05) that all of the tasks already executed by the program A are gone. When the running tasks are gone, an operation plane switching notification (g06) is sent out, and the new operation plane is sent. By newly starting the exchange task of the program B, the exchange process is newly started in the program B (g08). Further, after the operation side is normally switched, the operation side switching completion notification is notified from the system monitoring monitor 174 to the maintenance console 7 (g07).

Next, a sequence for switching the operation plane when a failure occurs in the operation program A will be described with reference to FIGS. 2, 3, 4, and 10. FIG.

When a failure is detected in the program A during the operation in the program A, a failure occurrence notification (h01) is transmitted, and all the tasks on the exchange task executed in the program A by the system monitor 174 are released ( h02), an exchange task of the program B, which is a new operation plane, is newly generated by the operation plane switching processing (h03), and the exchange processing in the program B is started (h04).

Next, a sequence for switching the operation plane at a predetermined time will be described with reference to FIG. 2, FIG. 3, FIG. 4, and FIG.

The system monitoring monitor 174 constantly monitors the preset operation-time switching time (i01). When the system clock (not shown) of the private branch exchange 1 matches the operation switching time, the system monitoring monitor 174 sends an event acceptance end request (i02) to the operation program A. In the program A, an exchange process ending process (i03) that occurs is performed. In the exchange processing end processing (i03), a newly generated event is temporarily stored in the exchange control memory area a3.

The system monitoring monitor 174 monitors (i04, i05) that all the tasks already executed by the program A are gone. When the running task is gone, it sends an operation plane switching notification (i06), By newly starting the exchange task of the program B, which is the operation side, the exchange process is newly started in the program B (i0).
7) is done.

As described above, by adopting the above configuration and control, the program can be updated without stopping the system. In addition, since there is no need to restart the system, without restoring the active call,
The program can be updated.

Further, since two program areas are provided in the memory space in the control unit 17 of the private branch exchange 1,
Even if the control unit 17 has a single configuration, the program can be updated.

Along with the above effects, the program can be updated at a predetermined time, which is effective when it is necessary to update the program simultaneously in a large-scale network.

In addition to the above effects, even if a problem occurs in the updated program after switching to the updated program, the original program before the update is installed again without installing the original program again. Operation can be switched instantaneously.

Since the program of the present invention has a LAN I / F or a maintenance I / F, even if the storage device 20 mounted in the private branch exchange 1 fails, the program can be externally updated. Can be.

[0069]

As described above, according to the present invention, 2
By providing a program storage area on the side and a switching control function for switching the operation side of the program by loading the program by performing switching control on the program storage area on the two sides, regardless of the operation status of the private branch exchange, There is an effect that the program can be updated.

[Brief description of the drawings]

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

FIG. 2 is a block diagram illustrating a configuration of a control unit in FIG. 1;

FIG. 3 is a block diagram illustrating a configuration of an exchange control unit in FIG. 2;

FIG. 4 is a diagram showing a configuration example of the magnetic disk device of FIG. 1;

FIG. 5 is a sequence chart showing the operation of the private branch exchange according to one embodiment of the present invention.

FIG. 6 is a sequence chart showing an operation of the private branch exchange according to one embodiment of the present invention.

FIG. 7 is a sequence chart showing an operation of the private branch exchange according to one embodiment of the present invention.

FIG. 8 is a sequence chart showing the operation of the private branch exchange according to one embodiment of the present invention.

FIG. 9 is a sequence chart showing an operation of the private branch exchange according to one embodiment of the present invention.

FIG. 10 is a sequence chart showing the operation of the private branch exchange according to one embodiment of the present invention.

FIG. 11 is a sequence chart showing an operation of the private branch exchange according to one embodiment of the present invention.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Private branch exchange 2-1-2-n Digital multifunctional telephone 3-1-3-n Analog telephone 4 Public network 5 Dedicated line network 6 LAN network 7 Maintenance console 11-1-11-n Digital telephone I / F circuit 12 -1 to 12-n analog telephone I / F circuit 13 switch 14-1 to 14-n office line trunk I / F circuit 15-1 to 15-n dedicated line trunk I / F circuit 16 CPU 17 control unit 18 LANI / F card 19 Maintenance I / F card 20 Storage device 21 Magnetic disk device 22 Floppy disk device

 ──────────────────────────────────────────────────続 き Continued on the front page F-term (reference)

Claims (7)

[Claims] 1. A program storage area having two surfaces,
A private branch exchange having a switching control function of performing switching control of a program storage area on a side to load a program and switching the operation side of the program. 2. The private branch exchange according to claim 1, wherein said two program storage areas are provided in a readable and writable temporary storage means, and said switching control function is provided in a read-only storage means. . 3. The update time of a program for the two program storage areas is set in advance, and the update of the program is performed at the update time. Private branch exchange. 4. The private branch exchange according to claim 3, wherein the update time of the program is set to the same time in a large-scale network including a plurality of private branch exchanges. 5. The system according to claim 1, wherein when a failure occurs in the updated program, the switching control function performs switching control on the two program storage areas to switch the operation side. Item 6. The private branch exchange according to any one of items 4. 6. A LAN (Local Area Net)
6. The private branch exchange according to claim 1, wherein the update of the program is performed from outside using at least one of a work and a maintenance line. 7. The private branch exchange according to claim 1, wherein the programs stored in the two program storage areas are stored in a magnetic disk device under its own device.