JP2000224623A - Operation file update system for telephone exchange and recording medium recording operation file update program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To eliminate the need for a job of a worker to visit an installed place of a telephone exchange by providing an operation file update section that generates a command to update an operation file to update the operation file and an operation control section that transmits the command to a telephone exchange and informs the operation file update section of a command execution result and a result of collating collation data and the command execution result. SOLUTION: A procedure generating section 3 of an operation file update system 1 generates a procedure file 9 that describes procedures for updating an operation file. An operation file update section 4 extracts only commands from procedure data recorded on the procedure file 9 and gives them to an operation control section 6. The operation control section 6 transmits the commands to an exchange via a control means control section 7. The exchange executes the commands and returns the result to the operation file update system 1. The operation file can be updated by executing the commands described in the procedure file 9 in this way.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an operation file update system for a telephone exchange for updating an operation file in which a program for operating the telephone exchange is described, and a recording medium storing an operation file update program.

[0002]

2. Description of the Related Art A telephone exchange is operated based on a program described in an operation file recorded in the telephone exchange. This operation file needs to be updated to provide new services and functions to users using the telephone. In the prior art, the operation file is updated by using the terminal device 24-1 connected to the telephone exchange 22-1 every time a new service or function is provided, as shown in FIG. I was FIG. 16 shows the procedure of this updating work.

In the updating operation, first, the operation status of the telephone exchange 22-1 whose operation file is to be updated is confirmed (step S31). Since the operation of updating the operation file needs to be performed while the telephone exchange 22-1 is operating, it is necessary to determine whether or not the operation file can be updated at the present time. Therefore, the operator issues a command for confirming the operation status to the telephone exchange 22-1, determines the timing of updating the operation file according to the result, and waits until the update work can be performed. (Step S32).

[0004] Next, when it becomes possible to update the operation file, the operator issues a command to load the contents of the new operation file into the memory in the telephone exchange 22-1. A new operation file has been created in advance.

[0005] The telephone exchange 22-n has two different memory areas, one of which is loaded with the contents of an operation file used for the current operation. The other memory is an area for loading the contents of a new operation file when the operation file is updated. The reason for having two memories in this way is that the contents of a new operation file are pre-loaded into the memory so that the operation file can be updated instantaneously, This is because the operation file is updated by switching.

Next, the operator switches to the contents of the loaded operation file (step S34). Thus, the operation of the telephone exchange 22-1 is performed based on the program described in the new operation file.

Next, the operator checks the operation status of the telephone exchange 22-1 (step S35), and checks whether there is any abnormality (step S36). Then, if there is no abnormality, the operation file update work ends.

On the other hand, if there is a newly generated abnormality due to updating to a new operation file, the operator
This abnormal situation is grasped and appropriate measures are taken (step S37).

As described above, the update work is performed while confirming the operation status of the telephone exchange 22-1 to be updated, so that the update work can be performed while the telephone exchange 22-1 is operating. .

[0010]

The updating work shown in FIG. 16 must be performed also in the terminal 24-2 connected to the telephone exchange 22-2 shown in FIG. The same operation needs to be performed in the terminal device 24-n connected to the telephone exchange 22-n as in the terminal device 22-n.

[0011] Therefore, a plurality of workers are assigned to each telephone exchange 2
An operation file work procedure manual must be created for each 2-n, and work must be performed at the installation location of each telephone exchange 22-n.

Therefore, when the operation files are individually updated in the terminal devices 24-n connected to the respective telephone exchanges 22-n, the operation file updating work can be quickly and quickly performed for a plurality of telephone exchanges 22-n. It needs to be done in a short period of time, but this has the problem of requiring a lot of personnel.

[0013] In addition, when the operation file is individually updated, there is a problem that the quality of the update work varies due to a difference in knowledge and experience of the operator who performs the update work. Furthermore, since the number of workers with a high level of technical skills is small, it is not practical to update the operation files of multiple telephone exchanges in a short period of time and at the same time, and the timing of starting a new service differs depending on the telephone exchange. There is also a problem.

SUMMARY OF THE INVENTION The present invention has been made in view of the above circumstances, and maintains a constant quality of an operation file update operation, and furthermore, an operation file update system and operation system for a telephone exchange which does not require a worker having specialized skills. An object of the present invention is to provide a recording medium on which a file update program is recorded.

[0015]

According to a first aspect of the present invention, there is provided an operation file updating system for a telephone exchange for updating an operation file in which an operation program of the telephone exchange is described. A procedure file in which an operation file update procedure is described, an operation file update unit that generates a command for updating the operation file based on the procedure file, and updates the operation file, and transmits the command to the telephone. An operation control unit that transmits the command to the exchange, obtains an execution result of the command, and notifies the operation file update unit of a result obtained by comparing the execution result with the verification data.

According to a second aspect of the present invention, in the telephone exchange operating file update system, an area management file in which an area where the telephone exchange is installed is defined;
Referring to a unit management file in which the types of telephone exchanges installed in each area are defined and a macro command file in which routine procedures are defined in advance, create the procedure manual file from the input work contents. The method further comprises a procedure manual preparation unit for performing the operation.

According to a third aspect of the present invention, the operation file updating system for a telephone exchange further comprises an operation monitoring unit for monitoring an operation status periodically transmitted from the telephone exchange, and the operation file updating unit. Is characterized in that an operation file is updated according to the operation state.

According to a fourth aspect of the present invention, there is provided a computer readable recording medium storing an operation file update program for a telephone exchange for updating an operation file in which an operation program of the telephone exchange is described. The update program generates an operation file update command based on a procedure file in which an operation file update procedure is described, generates an operation file update command, and updates the operation file. And transmitting the command to the computer to perform an operation control process of obtaining an execution result of the command, and notifying the operation file update process of a result obtained by comparing the execution result with the collation data.

According to a fifth aspect of the present invention, in the operation file update program, the area management file in which an area where the telephone exchange is installed is defined, and a type of the telephone exchange installed for each area is provided. The method further comprises a procedure manual creation process for creating the procedure manual file from the input work content by referring to a defined unit management file and a macro command file in which a standard procedure is defined in advance. I do.

According to a sixth aspect of the present invention, the operation file updating program further includes an operation monitoring process for monitoring an operation state periodically transmitted from the telephone exchange,
The operation file updating process is characterized in that an operation file is updated according to the operation state.

[0021]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, an operation file updating system according to an embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is a block diagram showing the overall configuration of the embodiment. In this figure, reference numeral 1 denotes an operation file updating system. Reference numeral 21 denotes a center device to which a plurality of telephone exchanges 22-n are connected by a network 23. The center device 21 is connected to the operation file updating system 1 by a network 20.

FIG. 2 is a block diagram showing the configuration of the operation file updating system 1 shown in FIG. In FIG.
Reference numeral 2 denotes an HMI (Human Machine Interface) unit for displaying a message to an operator and inputting information input by the operator via a display device (not shown) and an input device (not shown). Reference numeral 3 denotes a procedure manual creating unit that creates a procedure for updating the operation file. Symbol 4 is
An operation file update unit that updates the operation file according to the procedure manual created by the procedure manual creation unit 3. Reference numeral 5 denotes a telephone exchange 22- which is a target of the operation file update.
n is an operation monitoring unit that monitors the operation status of n. Symbol 6 is
An operation control unit that controls the operation of the telephone exchange 22-n to be updated in the operation file. Reference numeral 7 denotes a center device 21 and a telephone exchange 22-n via a network 20.
It is a communication control unit that establishes communication with.

Reference numeral 8 denotes a telephone exchange 2 from the operation control unit 6.
2-n is a macro command file in which macro commands to be transmitted to n are defined. Reference numeral 9 denotes the procedure manual creation unit 3
Is a procedure manual file for recording the procedure manual created in the above. Reference numeral 10 denotes an area management file in which an area where the telephone exchange 22-n is installed is defined.
Reference numeral 11 denotes a unit management file in which the models of the telephone exchanges 22-n are defined. Reference numeral 12 denotes a collation data file for issuing a command to the telephone exchange 22-n and recording collation data for collating the result. Reference numeral 13 denotes an execution result file that records the result of executing a command on the telephone exchange 22-n.
Reference numeral 14 denotes a telephone exchange 22- output by the operation monitoring unit 5.
n is a log file that records the operation status of n.

FIG. 3 is a block diagram showing the configuration of the procedure manual creating unit 3 shown in FIG. In FIG. 3, reference numeral 31 denotes
An input / output unit that inputs and outputs data to and from the HMI unit 2.
Reference numeral 32 denotes an area management processing unit that reads area data from the area management file 10. Reference numeral 33 denotes a procedure manual data generation unit that generates procedure manual data. Code 34
Is a macro command processing unit for reading macro command data from the macro command file 8. Code 35
Is a unit management processing unit that reads unit data from the unit management file 11. Reference numeral 36 denotes a procedure manual file output unit that outputs the procedure manual data generated by the procedure manual data generation unit 33 to the procedure manual file 9.

FIG. 4 shows the operation file updating unit 4 shown in FIG.
FIG. 3 is a block diagram showing the configuration of FIG. In FIG.
Reference numeral 1 denotes a procedure file input unit for reading procedure data from the procedure file 9. Reference numeral 42 denotes a macro command input unit that reads a command file from the macro command file 8. Reference numeral 43 denotes a procedure manual data execution unit that executes the procedure manual data step by step. Code 4
Reference numeral 4 denotes a command generation unit that generates a command for controlling the telephone exchange 22-n based on the procedure manual data. Reference numeral 45 denotes an update history output unit that writes a history of updating the operation file into the unit management file 11. Reference numeral 46 denotes an operation monitoring data input unit for inputting operation monitoring data output from the operation monitoring unit 5.

FIG. 5 is a block diagram showing a configuration of the operation monitoring unit 5 shown in FIG. In FIG. 5, reference numeral 51 denotes a monitoring data receiving unit that receives monitoring data output from the telephone exchange 22-n. Reference numeral 52 denotes a monitoring data notification unit that notifies the operation file updating unit 4 of the received monitoring data. Reference numeral 53 denotes the received monitoring data as H
This is a monitoring data display section that is displayed via the MI section 2. Reference numeral 54 denotes a monitoring data output unit that outputs the received monitoring data to the log file 14 in order to record the monitoring data.

FIG. 6 is a block diagram showing the configuration of the operation control unit 6 shown in FIG. In FIG. 6, reference numeral 61 denotes a command transmitting unit that transmits a command to the telephone exchange 22-n. Reference numeral 62 denotes an execution result data receiving unit that receives execution result data as a result of executing the command. Reference numeral 63 denotes a collation unit for collating the execution result data with the collation data. Reference numeral 64 denotes a collation result notifying unit that notifies a collation result of the execution result data collated by the collation unit 63.

Next, the operation of updating the operation file in the operation file updating system 1 shown in FIG. 2 will be described with reference to FIGS. 2 to 6 and FIGS. FIG. 7 is a flowchart showing an operation of creating procedure manual data in the procedure manual creating section 3 shown in FIG. FIG. 8 is a flowchart showing an operation of updating the operation file based on the procedure manual data recorded in the procedure manual file 9.

First, an operation for creating procedure manual data will be described with reference to FIG. First, when the operator gives an instruction to create a procedure manual, the procedure manual data generation unit 33 reads the contents of the area management file via the area management processing unit 32 and outputs the contents to the input / output unit 31. In response to this, the input / output unit 31 displays the content on a display device (not shown) via the HMI unit 2. by this,
The display device displays area management data defined in the area management file.

FIG. 9 shows an example of area management data defined in the area management file. As shown in the figure, the area management data defines an area where the telephone exchange 22-n is installed. The operator operates the telephone exchange 22-n to update the operation file from the displayed area.
Is selected using an input device (not shown). In response, the procedure manual data generation unit 33
Reads the area selected by the operator via the HMI unit 2 and the input / output unit 31, and sets this area as a target area (step S1). Here, it is assumed that “Sapporo” has been selected and set as the target area.

Next, the procedure manual data generation unit 33 reads the unit management data corresponding to the target area from the unit management data defined in the unit management data 11 via the unit management processing unit 35, and reads the contents. Is output to the input / output unit 31. The input / output unit 31 receives the
The contents are displayed on the display device via the MI unit 2. Thus, only the unit management data relating to the previously set target area among the unit management data defined in the unit management file is displayed on the display device.

FIG. 10 shows an example of the unit management data. As shown in this figure, the unit management data defines the telephone exchanges 22-n installed in the area, and a "unit name" for identifying these telephone exchanges 22-n and a "system" indicating the model. And the "update history" of the operation file executed for the telephone exchange 22-n. The operator uses the input device to select a unit corresponding to the telephone exchange 22-n for updating the operation file from the displayed unit. In response, the procedure manual data generation unit 33 reads the unit selected by the operator via the HMI unit 2 and the input / output unit 31,
This unit is set as a target unit (step S2). Here, it is assumed that “Odori-A” and “Makomanai-Z” have been selected and set as the target units.

The conditions for updating the operation file are determined by steps S1 and S2 described above. Here, the operator names the procedure manual data of the operation file update procedure to be created, and inputs an outline of the procedure manual contents. FIG. 11 shows an example in which the conditions for updating the operation file are determined. Here, the input procedure book name becomes the file name of the procedure book file 9.

It should be noted that the procedure manual file 9 in which the procedure manual data is recorded may be searched in the past, and new procedure manual data may be created by diverting the procedure manual data. . At this time, as shown in FIG. 12, a procedure manual management file for managing the procedure manual created in the past is provided for each area, and the name of the procedure manual created in the past is recorded in this file. Sometimes this content is displayed on a display device. In response to this, the operator selects the corresponding procedure manual name from among them, thereby specifying past procedure manual data created.

Next, the procedure manual data generation unit 33 outputs a message prompting input of the work content to the input / output unit 31. The HMI unit 2 displays this message on a display device. In response to this message, the operator inputs the contents of the operation at the time of updating the operation file from the input device. In response to this, the procedure manual data generation unit 33 reads the work content input by the operator via the HMI unit 2 and the availability unit 31, and
This is set as work contents (step S3). Here, the contents of work that can be input by the worker are a command for controlling the telephone exchange, a macro command in which this command sequence is defined in advance, and a comment used by the worker as a memo.

Here, if the input work content is a macro command, the procedure manual data generation unit 33 inquires the macro command processing unit 34 whether or not the corresponding macro command exists. In response to this, the macro command processing unit 34 searches the contents of the macro command file 8 and notifies the procedure manual data generation unit 33 whether or not the corresponding macro command exists. As a result, when the corresponding macro command does not exist, the procedure manual data generation unit 33 notifies the operator that the non-existent macro command has been input by an error message or the like.

Next, when the operation content input by the operator is a command or a macro command, the procedure manual data generation unit 33 compares the execution result when the command or the macro command is executed with the collation data. An inquiry is made to the worker as to whether or not to perform the setting, and the answer is set (step S4). With this setting, whether or not to perform collation with collation data is set.

Next, as a result of executing the command, if an error is found, the procedure manual data generating unit 33 inquires of an operator whether or not to suspend the command execution at that time, and sets the answer ( Step S5). With this setting, it is set whether or not to suspend processing before executing the next command when an abnormality is found.

Next, the procedure manual data generation unit 33 inquires of the operator whether or not the next work content is to be set, and if there is an answer to the setting, returns to step S3 and repeats the same operation (step S3). Step S6).

When the setting of the work contents is completed, the work contents set in steps S3 to S5 are displayed on the display device in the order in which the list is set, as shown in FIG.
In this figure, the procedure numbers are numbers assigned in the order of the set work contents. The work content is a comment, followed by a command or a macro command in which a command name is set. In the case of a comment alone, the command name column is blank.

Next, the procedure manual data generation section 33 inquires of the operator whether to designate a jump destination for each set work content (step S7).

In response to this inquiry, if the operator replies that the designation is not made, the procedure manual data generation unit 33 transmits the set work contents via the procedure manual file output unit 36 to the procedure manual file. 9 is written (step S10).

On the other hand, when there is a reply that the jump destination is specified, the procedure manual data generation unit 33 requests the operator to specify the jump destination for each work content. Here, the designation of the jump destination is to designate the work content to be executed after the command corresponding to the work content is executed. In response to this request, the operator specifies a jump destination for each work content by a procedure number. At this time, the operator does not specify the work content having no jump destination.

Next, the procedure manual data generation unit 33 reads the jump destination specified by the worker and sets each work content (step S8). This result is written in the jump destination column shown in FIG. The designation of the jump destination is repeated until the worker ends (step S9).

Next, when the designation of the jump destination is completed, the procedure manual data generation unit 33 writes the work contents shown in FIG. 13 into the procedure manual file 9 via the procedure manual file output unit 36. At this time, each procedure number becomes a record record number. Therefore, the record records in the procedure manual file 9 are “procedure number”, “work content”, “command name”,
It consists of fields of “collation”, “interruption”, and “destination”.

As described above, the procedure manual file 9 describing the procedure for updating the operation file is created by the operation shown in FIG.

Next, an operation of updating the operation file based on the procedure manual data recorded in the previously created procedure manual file 9 will be described.

First, the procedure manual data execution unit 43 reads one procedure record of the procedure manual data recorded in the procedure manual file 9 via the procedure manual file input unit 41 (step S11). At this time, EOF of procedure file 9
If (End Of File) is detected, the process ends (step S12).

Next, the procedure manual data execution unit 43 determines whether the read procedure manual data is a command or a macro command (step S13).

If the read procedure manual data is not a command but a comment, the process returns to step S11.

On the other hand, if the read procedure manual data is data referencing a macro command, the procedure manual data execution unit 43 is further recorded in the macro command file 8 via the macro command input unit 42. Read the current macro command data. In the macro command file 8, a plurality of commands are defined for each macro command.

Next, the procedure manual data execution unit 43 passes the read procedure manual data to the command generation unit 44. At this time, if the procedure manual data to be passed to the command generation unit 44 is a macro command, the command sequence read by the macro command input unit 42 is also passed at the same time. In response to this, the command generating unit 44 extracts only the command from the received procedure manual data, and passes a flag indicating whether or not to perform collation with the command to the command transmitting unit 61. At this time,
The procedure manual data execution unit 43 determines the timing at which the command is passed from the command generation unit 44 to the command transmission unit 61 with reference to the operation status notified from the operation monitoring data input unit 46. This makes it possible to know whether it is time to execute the command to be transmitted.

Here, the operation monitoring section 5 will be described.
The monitoring data receiving unit 51 receives monitoring data periodically transmitted from the telephone exchange 22-n via the communication control unit 7. Then, the monitoring data notification unit 52 sends the monitoring data to the procedure manual data execution unit 43 via the operation monitoring data input unit 46.

The monitoring data display section 53 displays the monitoring data on the display device via the HMI section 2. this is,
This is for notifying the operator of the operation status of the telephone exchange 22-n. Further, the monitoring data output unit 54 records the monitoring data in the log file 14. This is to record the operating status up to that time when an abnormality is discovered at a later date and use it for analysis.

Next, the command transmission section 61 transmits the received command to the telephone exchange 22-n via the communication control section 7.
(Step S14). On the other hand, a flag indicating whether or not to perform collation is passed to the collation unit 6.

By this operation, a command for performing control can be transmitted to the telephone exchange 22-n.

Next, a process of receiving the execution result of the transmitted command will be described. First, the telephone exchange 22-n executes the command transmitted from the operation file updating system 1, and returns the result to the operation file updating system 1 via the center device 21.

On the other hand, the execution result receiving unit 62 receives the execution result (step S15), records it in the execution result file 13, and simultaneously notifies the collating unit 63 that the execution result of the command has arrived. Notice.

Subsequently, the collating unit 63 reads the execution result recorded in the execution result file 13 and determines whether the command has been executed normally (step S16). If the result of the determination is not normal, the matching unit 63 notifies the matching result notifying unit 6 that the command was not executed normally.
4 to the procedure manual data execution unit 43.

Next, when the execution of the command is not performed normally, the procedure manual data execution unit 43 temporarily suspends the execution of the command (step S22). Then, the fact that the command execution has been interrupted is displayed on the display device via the HMI unit 2. Here, the operator determines this situation, determines whether or not to continue the processing, and inputs an instruction as to whether or not to continue from the input device. In response, the procedure manual data execution unit 43 reads this instruction via the HMI unit 2 and determines whether to continue the command execution (step S2).
3).

When an instruction to continue is input, the procedure manual data execution unit 43 continues executing the command. On the other hand, when an instruction not to continue is input, the procedure data execution unit 43
Waits as it is. Here, after taking an appropriate measure, the operator inputs a continuation instruction or cancels the operation file update work.

If the command has been normally executed in step S16, the collating unit 63 determines whether a collating flag has been transmitted from the command transmitting unit 61 (step S17).

When the collation flag has not been transmitted, the collation unit 63 notifies the procedure manual data execution unit 43 via the collation result notification unit 64 to execute the next command. In response to this, the procedure manual data execution unit 43 repeats the processing from step S11.

On the other hand, when the collation flag is transmitted,
The collation unit 63 reads the collation data file 12 and collates the collation data corresponding to the execution result of the command executed at the current time with the execution result (step S18). The collation referred to here is to compare the collation data, which is the execution result recorded in advance under normal conditions, with the execution result obtained by actually executing the command, and determine whether the same result as the collation data was obtained. It is to judge. FIG. 14 shows an example of the collation data.

Subsequently, the collating unit 63 notifies the procedure result data executing unit 43 of the collation result via the collation result notifying unit 64. In response, the procedure manual data execution unit 43
Determines whether the collation results notified from the collation result notification unit 64 match (step S19).

If the collation data does not match the execution result as a result of the determination, the execution of the command is interrupted (step S22). The following operation is the same operation as described above.

On the other hand, when the collation results match, the procedure manual data execution unit 43 outputs the command executed at this time as a history via the update history output unit to the unit management file 1.
Record to 1. Subsequently, the procedure manual data execution unit 43 determines whether a jump destination has been set in the procedure manual data containing the command executed at this time (step S20).

If the result of this determination is that the jump destination has not been set, the flow returns to step S11, and the processing is repeated. When the jump destination is set, the procedure manual data execution unit 43 reads the procedure number set as the jump destination, and
The procedure number to be executed next is set to the read procedure number (step S21). Thus, the procedure number to be executed next by the procedure manual data execution unit is determined. Then, in step S11, the procedure manual data execution unit 43 reads the procedure manual data having this procedure manual number from the procedure manual file and continues the process.

As described above, the operation file can be updated by sequentially reading the procedure manual data recorded in the procedure manual file 9 and executing the command described therein. By describing the procedure recorded in the procedure manual file 9 as a procedure as shown in FIG. 16, it is possible to execute exactly the same procedure as a task conventionally relying on an operator.

By setting the execution of the command to be interrupted for all commands, the set command can be executed while confirming the result for each step.

A program for implementing the steps shown in FIGS. 7 and 8 is recorded on a computer-readable recording medium, and the program recorded on the recording medium is read by a computer system and executed. An operation file update operation may be performed. Here, the “computer system” includes an OS and hardware such as peripheral devices. The “computer-readable recording medium” refers to a portable medium such as a floppy disk, a magneto-optical disk, a ROM, a CD-ROM, and a storage device such as a hard disk built in a computer system.

Further, a “computer-readable recording medium” is a program that is dynamically transmitted for a short time, such as a communication line for transmitting a program via a network such as the Internet or a communication line such as a telephone line. In this case, a program that holds a program for a certain period of time, such as a volatile memory in a computer system serving as a server or a client in that case, is also included. Further, the above-mentioned program may be for realizing a part of the above-mentioned functions, or may be for realizing the above-mentioned functions in combination with a program already recorded in a computer system.

[0073]

As described above, according to the first and fourth aspects of the present invention, since the operation file of the telephone exchange is updated by remote control, the worker goes to the installation location of the telephone exchange. This eliminates the need to perform any work. In addition, an operation file update unit and an operation control unit are provided, and an effect is obtained that the operation file can be updated based on the procedure manual file without the operator working. In addition, since the operation file can be updated for a plurality of telephone exchanges using one operation file update system, there is an advantage that work can be performed in a short period of time and simultaneously even with a small number of workers. Can be Further, there is an effect that the operation file can be updated even by a worker who does not have specialized skills.

According to the second and fifth aspects of the present invention, the area management file, the unit management file, and the macro command file are prepared in advance, and the procedure manual file is created by referring to these files. ,
The effect is obtained that the quality of the procedure manual can be kept constant. As a result, the quality of the operation file update work can be kept constant.

According to the third and sixth aspects of the present invention, since the operation monitoring unit is provided, the update operation can be performed while monitoring the operation status of the target telephone exchange, and the operation file can be updated. The effect that the trouble can be prevented from occurring in the telephone exchange can be obtained.

[Brief description of the drawings]

FIG. 1 is a block diagram showing an overall configuration of an embodiment of the present invention.

FIG. 2 is a block diagram showing a configuration of an operation file updating system 1 shown in FIG.

FIG. 3 is a block diagram showing a configuration of a procedure manual creating unit 3 shown in FIG.

FIG. 4 is a block diagram showing a configuration of an operation file updating unit 4 shown in FIG.

FIG. 5 is a block diagram showing a configuration of an operation monitoring unit 5 shown in FIG.

FIG. 6 is a block diagram showing a configuration of an operation control unit 6 shown in FIG.

FIG. 7 is a flowchart illustrating an operation of creating a procedure manual.

FIG. 8 is a flowchart illustrating an operation of updating an operation file.

FIG. 9 is an explanatory diagram showing an example of an area management file 10.

FIG. 10 is an explanatory diagram showing an example of a unit management file 11.

FIG. 11 is an explanatory diagram showing an example of conditions for creating a procedure manual.

FIG. 12 is an explanatory diagram illustrating an example of a procedure manual management file.

FIG. 13 is an explanatory diagram showing an example of a procedure manual file 9;

FIG. 14 is an explanatory diagram showing an example of a collation data file 12.

FIG. 15 is a block diagram showing a configuration of a conventional technique.

FIG. 16 is a flowchart showing a procedure for updating an operation file.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 ... Operation file update system, 2 ... HMI part, 3 ... Procedure manual preparation part, 4 ... Operation file update part, 5 ... Operation monitoring part, 6 ... Operation control part, 7: Communication control unit, 8: Macro command file, 9: Procedure file, 10: Area management file, 11: Unit management file, 12: Verification data file, 13 ··· Execution result file, 14 ··· Log file.

 ──────────────────────────────────────────────────続 き Continuing on the front page (72) Inventor Jun Kawasaki 1-9-1 Konan, Minato-ku, Tokyo NTT Communications Wear Corporation (72) Inventor Koji Yasuda 1-chome Konan, Minato-ku, Tokyo No. 9-1 NTT Communicationware Co., Ltd. (72) Inventor Hiroyuki Nomura 9-1-1 Konan, Minami-ku, Tokyo, Japan NTT Communicationware Co., Ltd. (72) Inventor Akihiko Sato F-term (reference) 5K024 AA00 5K026 AA23 CC07 GG27, NTT Communications Wear Co., Ltd. 1-9-1 Konan, Minato-ku, Tokyo

Claims (6)

[Claims] 1. An operation file update system for a telephone exchange for updating an operation file in which an operation program of the telephone exchange is described, the operation file update system comprising: a procedure file in which an operation file update procedure is described; An operation file update unit that generates a command for updating the operation file based on the procedure manual file and updates the operation file; and transmits the command to the telephone exchange, and executes the command. And an operation control unit for notifying the operation file updating unit of a result of collating the execution result with the collation data, and an operation file updating system for a telephone exchange. 2. An operation file updating system for a telephone exchange, comprising: an area management file in which an area in which the telephone exchange is installed is defined; and a unit in which a type of the telephone exchange installed in each area is defined. A procedure file creating unit for creating the procedure document file from input work contents by referring to a management file and a macro command file in which a standard procedure is defined in advance. 2. The operation file updating system for a telephone exchange according to 1. 3. The operation file updating system for a telephone exchange, further comprising: an operation monitoring unit that monitors an operation state periodically transmitted from the telephone exchange, wherein the operation file update unit is configured to perform an operation according to the operation state. The operation file updating system for a telephone exchange according to claim 1, wherein the operation file is updated by performing the update. 4. A computer-readable recording medium storing an operation file update program for a telephone exchange for updating an operation file in which an operation program of the telephone exchange is described, wherein the operation file update program is an operation file update. An operation file update process for generating a command for updating the operation file based on a procedure manual file in which a procedure is described and updating the operation file; and transmitting the command to the telephone exchange, An operation file update program for telephone exchanges, characterized by causing the computer to perform an operation control process of notifying the operation file update process of a result obtained by comparing the execution result and the collation data with the execution result. Computer readable recording medium. 5. The operation file update program comprises: an area management file in which an area where the telephone exchange is installed is defined; and a unit management file in which a type of the telephone exchange installed for each area is defined. 5. The method according to claim 4, further comprising: a procedure manual creation process for creating the procedure manual file from the input work content by referring to a macro command file in which a standard procedure is defined in advance. And a computer-readable recording medium storing the telephone exchange operating file update program. 6. The operation file update program further includes an operation monitoring process for monitoring an operation status periodically sent from the telephone exchange, and the operation file update process includes an operation file according to the operation status. 5. A computer-readable recording medium storing a telephone exchange operation file update program according to claim 4, wherein the program is updated.