JP3177617B2 - Line data processing method - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a line control processing system for registering and updating line data such as physical conditions, logical conditions, protocol parameters, and the like related to a communication circuit in a communication device.

A device that performs online processing using a line,
For example, in a terminal device, a host computer, an exchange, or the like, it is necessary to register and update various line data for line control processing with a change in line data. In such a case, when the registration or change of the line data is performed, the process may be performed assuming that the registration or the change is completed only after actually performing the line control process. In this case, various operations, for example, establishment and release of a logical link or call setting / release such as a packet call are performed in the line control process in accordance with registration and change. In addition, when making changes, it is necessary to shut down the line and execute it. When the line is closed and the changed line data is entered and released again, the line control process that accompanies the updated value of the data is started. Also, there is a problem that it takes a long time to complete the processing, and it is desired to improve the problem.

[0003]

2. Description of the Related Art FIG. 10 is an explanatory view of Conventional Example 1, FIG. 11 is an explanatory view of Conventional Example 2, and FIG. 12 is an explanatory view at the time of system restart when the method of Conventional Example 2 is used.

FIGS. 10 and 11 show an example of a system in which a host computer (hereinafter, referred to as a host) performs data processing by performing packet communication with a plurality of data terminals via a switching network (for example, a packet switching network or ISDN). For example, the data terminal is a number of bank terminals provided at various places, and the host corresponds to a computer (or an exchange) provided at the center. In such a system, it is necessary to register the line data in the host. The line data includes physical conditions (communication standards that can be set within a certain range such as terminal address and line speed), logical conditions (frame length, character type, timer value, etc.), and protocol parameters (HDLC X25 protocol, , X28, X32, etc., there are parameters to be selected from among the ranges that can be set in advance, such as facilities, synchronization methods, data lengths, and the like.

FIG. 10 shows two methods in which the host newly registers DTE (Data Terminal Equipment) addresses relating to a plurality of partner terminals to be communicated simultaneously (registration in a line control memory in the host). This is shown as the method of Conventional Example 1 and the method of Conventional Example 2 in FIG.

When a new DTE address is registered, a registration command is used. When the registration command is input to the host, the host executes a process of connecting a line to a corresponding terminal and executes the command. Is completed.

In FIG. 10, the time elapses from the top to the bottom in the vertical direction. For the terminal for which a new DTE address is to be registered, the host maintainer uses the console to issue a registration command for one terminal a (D of the terminal a to be registered).
When the host (including the TE address) is input (A in FIG. 10), the host issues a call accompanying this registration command and executes a call control process. That is, a CR (call request) packet is transmitted to the switching network by the received DTE address (B).

The switching network selects the partner terminal a having the address and sends out a CN (incoming call) packet (C). Upon receiving this, the other party terminal a sends a CA (call acceptance) packet to the switching network (D), and the switching network sends a CC (connection complete) packet to the calling host (E). .
Upon receiving this, the host notifies the console of the maintenance person of the end (the same F). In this way, a connection path with one newly registered terminal a is set, and the registration is completed. Next, a registration command is input for the DTE address of the other terminal b, a connection path is set in the same procedure, and registration is completed.
Hereinafter, the registration is performed for all the terminals registered in the same manner.

In the method shown in FIG. 10, since the maintenance person inputs commands one by one in order, it takes time to complete registration for all terminals. In addition, DTE
In addition to address registration, various line data (physical conditions,
Connection control is performed using commands corresponding to registration, change, or deletion of logical conditions, protocol parameters, and the like.

On the other hand, in the case of the conventional example 2 shown in FIG. 11, when registering line data, especially a DTE address, the maintenance person inputs a registration command (each DTE address) for all the terminals to be registered from the console at once. By performing A) in FIG. 11, the time is reduced. When a command is input collectively and then a start command is input (B), the host executes a call control process and transmits a CR packet using the address of the first terminal a as in FIG. C). The switching network sends and receives CN packets and CA packets to and from the partner terminal a (D and E), and
The packet is transmitted to the host (F). Upon receiving this, the host transmits a CR packet to the next terminal b (the same G), and thereafter, the call setting with each terminal is sequentially performed.

[0011] However, in the case of FIG. 11, after the batch input of the registration command and the start command, the call control processing is dependent on the command. (H in FIG. 11) is not accepted. Therefore, even if line data to be registered urgently occurs, it cannot be executed halfway.

FIG. 12 is an explanatory diagram when the system is restarted in the case of using the method of the second conventional example. In this example, as described in the above description of FIG.
When call control processing by the host is performed by the start command, the host stops the system due to a software error or a hardware failure, and then resumes the system by performing a restart processing (by executing an IPL or the like). Indicates a case where

[0013] In this case, even if the host restarts the system, when the host stops, the connection path is disconnected from the exchange or the call setting is terminated during execution. The operation ends abnormally, and the connection path setting operation remains interrupted.

[0014] Therefore, after resuming, the maintenance person must identify the one whose connection path has been disconnected or the call has not been set up, and input a registration (change, delete) command again. In the above description, the operation of registering the DTE address in the line data has been described. However, when registering, changing, or deleting other line data, the same processing is performed by the respective commands. In the case of changing (updating) the line data, it is necessary to close the line to prevent malfunction due to the existence of both the previous data and the changed data. The line can be used after performing line control processing according to the value.

[0015]

As described above, FIG.
The method of the prior art 1 of FIG. 0 has a problem that it takes a long time to register a large number of line data because commands and line control processing are individually performed at the time of registration of the line data. In the method, commands can be input collectively, but there is a problem that unless the line control processing for all commands is completed, emergency line data generated thereafter cannot be registered. Further, when the line control processing is performed by inputting commands collectively, the line connection is often disconnected from the exchange side when the system restart processing is performed as shown in FIG. In this case, there is a high possibility that the system is abnormally stopped, and there is a problem that the registration command and the start command must be input again from the beginning.

When changing the current line data instead of registering a new line, the line is closed, and when the line is released again, the line is processed according to the data update value and the line can be used. There was a problem that it took time.

According to the present invention, when it is desired to register, change, or delete line data, a line control process for correcting the line status so as to match the latest line data is performed online in parallel with a subsequent line data change process. Line data processing method that can be performed and line data processing method that continues line control processing based on line data that has been registered, changed, or deleted immediately after system restart even after system restart. The purpose is to provide.

[0018]

FIG. 1 is a diagram showing the principle of the present invention, and FIG. 2 is an explanatory diagram of a registration status table and a control status table.

In FIG. 1, 1 to 11 are communication devices such as terminals and host computers, 1 is a cycle start execution control unit, 2 is a command processing unit, 3 is a restart control unit, 4 is a line control processing unit, 9 is a table storage unit. In the line control processing unit 4, a correction processing execution unit 5 corrects the line status to a state corresponding to each input data of registration, change, and deletion.
Is a protocol control unit for controlling a protocol for connecting lines and transmitting and receiving data, 7 is a line control unit for controlling the setting of a connection path with the switching network, and 8 is for accessing a table storage unit 9 described later. It is a table driver that reads or writes data of the requested table.

The table storage unit 9 comprises a registration status table 10 and a control status table 11 as shown in FIG. 2. The registration status table 10 stores the status of the registration operation. It is composed of a serial number area B and a delete serial number area C, which are arranged in an area where the contents are guaranteed even when the system is restarted (the area where the contents are recovered even after restarting). The control status table 11 is composed of a registration serial number area D, a change serial number area E, and a deletion serial number area F. The contents of these areas are guaranteed at the time of system restart depending on whether a failure is minor or severe. When the system is restarted due to a severe failure, if the line that has already completed the correction processing is not guaranteed, the contents are placed in the area where the contents are initialized to 0, and the correction processing is originally guaranteed when the system is restarted. If there is no ability, it is placed in an area whose contents are initialized to 0.

Each bit a, located at the coordinates represented by (i, j) on each of the areas A to F of each of the tables 10 and 11,
f indicate the status at the same internal serial number, and the meaning of each bit represented by 0 and 1 is shown at the bottom of FIG. Here, the internal serial number means a number provisionally assigned to each line (or link or virtual call VC) to be controlled until the processing is completed.

According to the present invention, the status of a request for registration or change is stored in a registration status table in response to registration, change, or deletion of line data, and the status of line control processing corresponding to the registration or request is stored in a control status table. The contents of each table are periodically monitored by the execution control unit, and the line control process corrects the line status so as to match the latest line data, and continuously changes the line data online in parallel. Done
Immediately after the system restarts, the line control processing is continued based on the registered, changed, and deleted line data.

[0023]

The command processing unit 2 registers and changes line data.
When the deletion command is input collectively, the registration data is changed when the deletion command is received, the table driver 8 of the line control processing unit 4 is activated, and the following processing to the table storage unit 9 is requested. The table driver 8 updates the value of the table storage unit 9 according to the request at the time of activation.

In the case of new registration of line data, an unused internal serial number is searched for in the registration serial number area A in the registration status table 10, and in each of the registration serial number areas A and D in the registration status table 10 and the control status table 11, the unused internal serial number is searched. The bits a and d of the coordinate position corresponding to the internal serial number are set (set to "1"). As a result, the line data of the corresponding internal serial number in the registered serial number area A of each of the tables 10 and 11 indicates that the registration has been completed (registration status table) and that the processing is in progress (control status table) which means that the processing has not been completed.

In the case of a line data change, the registration serial number area A in the registration status table 10 and the control status table 11
After confirming whether the corresponding internal serial number is used in D, the registration status table 10 and the control status table 11
The bits b and e of the coordinate positions corresponding to the internal serial numbers of the changed serial number areas B and E are set (to "1"). This indicates that the line data of the corresponding internal serial number stored in the change serial number area of each of the tables 10 and 11 has a change request (registration status table) and is processing (control status table).

In the case of deleting line data, an internal serial number corresponding to the line serial number is obtained, and the bit of the coordinate position corresponding to the internal serial number in the registration serial number areas A and D in the registration status table 10 and the control status table 11 is reset (" 0 "). Also, a bit c on the coordinate corresponding to the internal serial number of the deletion serial number area C in the registration status table 10 is set (to “1”), and a bit on the corresponding coordinate of the deletion serial number area F in the control status table 11 is set. f is reset (set to "0"). Thereby, each table 10, 11
Indicates that the line data of the corresponding internal serial number stored in the delete serial number area has a deletion request (registration status table) and has not been processed (control status table).

The command processing unit 2 includes a table driver 8
When the updating process of the table storage unit 9 is completed, the periodic start execution control unit 1 is requested to periodically start the correction process execution unit 5 of the line control processing unit 4.

When activated by data registration and data change, the correction processing execution unit 5 accesses the table storage unit 9 and
The contents of the registration status table 10 and the control status table 11 are taken out, and according to the contents, the protocol control unit 6 or the line control unit 7 is inquired about the implementation status, and if not implemented, the control units 6 and 7 are activated to process. .

The protocol control unit 6 executes the protocol control by the state transition operation, and accepts and notifies a call state inquiry from the correction processing execution unit 5. Also, in accordance with the call and disconnection instructions from the correction processing execution unit 5, a call event and a disconnection event are transmitted to the line control unit 7, and when a connection completion and disconnection confirmation is received from the line control unit 7, the internal serial number is stored in a table. Notify the driver 8.

The line control unit 7 receives an inquiry about the link state and the line state from the correction processing execution unit 5, notifies the state, and responds to the link establishment, release instruction or parameter change instruction from the correction processing execution unit 5 according to each instruction. Each process is performed on the line, and when the process is completed, the corresponding internal serial number is notified to the table driver 8.

As described above, the correction processing execution unit 5 is periodically activated to execute the requested unprocessed line data processing according to the status of the table storage unit 9 and the states of the protocol control unit 6 and the line control unit 7. Since the process is executed for a certain period of time, intermittent line data update processing can be performed while the periodic activation is temporarily interrupted, even if all processing according to the previous line data update is not completed.

The restart control unit 3 is started when the system is restarted after a failure, starts the table driver 8 as soon as the system is started, and causes the periodic start execution control unit 1 to start the correction processing execution unit 5 periodically. To ask. However, the table driver 8 does not start when the contents are guaranteed as in the case of system restart due to a minor failure, and the control status table 11 in the table storage unit 9 is set to 0 as in the case of system restart due to a severe failure. Only when it is initialized to

[0033]

FIG. 3 shows an example of a system configuration to which the present invention is applied.
FIG. 4 is a block diagram of the embodiment, FIG. 5 is an explanatory diagram of a change in bit contents of each area of the registration status table and the control status table, FIG. 6 is an operation sequence of each unit when performing line control processing by periodic activation, and FIG. 8 shows an operation sequence of each unit when a plurality of periodic activation requests are generated, FIG. 8 shows an operation of each unit when the line control processing is completed, and FIG. 9 shows a processing flow of each unit when the system is restarted.

FIG. 3 shows a configuration example of a system to which the present invention is applied. FIG. In the case of the system configuration of (1), the terminal (or center device) 30 is an ISDN
(Integrated Services Digital Network) 31, the ISDN 31 is provided with a packet handler (indicated by PHM) 32 for performing packet communication, and the other packet handlers 33 and 34 are provided from the packet handler 32 via a plurality of lines. Alternatively, it connects to the packet network 35.
In such a form in which the packet handler 32 is provided when the ISDN is connected to the packet network, a protocol is defined as Case B of CCITT recommendation X31.

In this case, communication is performed between the packet handler 32 and the other packet handlers 33 and 34. Actually, one or a plurality of internal terminals (virtual terminals) are provided in the packet handler 32, and a logical channel is set between the internal terminals of the other party's packet handler 33 and the packet handler 34. Communication (status data, packet data, etc.) is performed. This A. In the above system, data such as physical conditions, logical conditions, and protocols for communicating with each other by connecting from the packet handler 32 to a number of packet handlers including the other packet handlers 33 and 34 are registered, changed, or changed. It can be implemented when deleting.

The present invention also relates to FIG. In this system, the host 36 is connected to a large number of terminals 38 via a network 37 such as a packet network or ISDN to constantly execute a service corresponding to a request from each terminal. You. In this system, one
One or many internal terminals (virtual terminals) are connected to each terminal 38 via a network, and the host 36 registers data such as physical conditions, logical conditions, and protocols for connecting and communicating with each terminal. It can be implemented when it is changed or deleted.

FIG. 4 is a block diagram of the embodiment. This embodiment is similar to the embodiment shown in FIG. 2 shows a configuration related to control of an internal terminal (virtual terminal) built in the packet handler (PHM) shown in FIG. 1 to 3 and 6 to 8 in the figure correspond to the respective units having the same reference numerals in the principle configuration of FIG.
4 is a virtual terminal program, corresponding to the line control processing unit 4 in FIG. 1, 5a is a call setting execution unit, 5b is a call release execution unit, and the combined function is the correction processing of FIG. Corresponds to the execution unit 5. The memory (MM) 9 in FIG. 4 corresponds to the table storage unit 9 in FIG. Further, reference numeral 12 in FIG. 4 denotes an OS (operating system), and the respective controls of the periodic start execution control unit 1 and the restart control unit 3 are included in the OS 12, and 13 denotes a hard disk device (denoted by DK).

The table driver 8 shown in FIG. 4 comprises three table drivers 8a to 8c.
Is activated by the restart control unit 3 to perform table processing, and
b is activated by the protocol control unit 6 via the call setting execution unit 5a to update the table, and 8c is activated by the protocol control unit 6 via the call release execution unit 5b to update the table. In the embodiment shown in FIG.
Each of the sections ８8 and 12 is realized by software.

The registration status table 10 and the control status table 11 are provided in a guaranteed area in the memory (MM) 9.
This guaranteed area is an area whose contents are guaranteed at the time of a minor failure, and is initialized (set to 0) at the time of a severe failure.
The hard disk device 13 is provided with a table 13a having the same contents as the registration status table 10. When writing to the registration status table 10 of the memory 9 is performed, writing to the table 13a of the hard disk device 13 is performed at the same time. When a failure occurs, the contents of the table 13a of the hard disk device 13 are stored in the registration status table 1 of the memory 9.
Raised to 0 (copied).

The change of the bit contents of each area of the registration status table 10 and the control status table 11 will be described with reference to FIG. 5. The registration status table 10 is used to register new line data input from a console (not shown). When a command for each registration of change and deletion is received, the table driver 8 is started from the command processing unit 2 to the registration status table 10 in the memory 9 (and the table 13a in the hard disk device 13, the same applies hereinafter) and the control status table 11. , (See the description of FIG. 1).

As a result, the bits a to f at the positions corresponding to the internal serial numbers of the respective areas of the registration status table 10 and the control status table 11 correspond to the data registration, change, and deletion shown in FIG. Are set to the bit states after the registration processing, the change processing, and the deletion processing shown as. The values in the boxes marked with “*” are the values that are set to indicate that the status has been changed, and the values in the frames without the mark “*” are changed from the previous status. Not done. Bits a to f are set for each of these items of registration, change, and deletion while the line control by registration is being executed as shown in FIG. This content is the same as that of the item except that the bit f corresponding to the item of deletion is different from the state (“0”) (“1”). When the line control corresponding to registration, change, and deletion in FIG. 5 is completed, each bit a to f in the table is set as follows.

The call setting execution unit 5a (for registering or changing line data) or the call release executing unit 5b (for deleting line data) of the virtual terminal program 4 shown in FIG. Accordingly, periodic activation is performed under the control of the periodic activation execution control unit 1 of the OS 12 (starting at a fixed period, and after receiving a suspension or completion of processing from a start destination after a predetermined amount of processing, is also started after a predetermined period). Upon activation, the registration status table 10 and the control status table 11 in the memory 9 are referred to. In this case, the respective operations of data registration, data change, and data deletion are described in the following (1) to (3).

(1) In the case of data registration, access is performed by using an internal serial number sequentially from the top of the registration serial number area A of the registration status table 10, and the bit value of the coordinate for the internal serial number is “1”.
Look for an internal serial number. If the corresponding coordinate in the control status table 11 is also "1", the protocol control unit 6 or the line control unit 7 is inquired about the execution state of the line control process relating to the corresponding internal serial number. The unit 7 is activated to perform processing with an internal serial number. If the corresponding bit of the control status table 11 is "0", nothing is performed. If the result of the inquiry about the execution state of the line control processing is other than the unexecuted state, the processing for the next internal serial number is performed. At this time, if the line control processing is started for each internal serial number continuously with the number of lines (the number of internal serial numbers) up to a predetermined number N, the periodic start execution control unit 1 once makes the next. Request to restart in the cycle of and interrupt the process. When the search reaches the end of the registration serial number area of the registration status table 10, the periodic activation ends.

(2) In the case of data change, access is performed by using an internal serial number sequentially from the top of the change serial number area B of the registration status table 10, and the bit value of the coordinate for the relevant internal serial number is “1”.
To search for the internal serial number. If control status table 1
If the corresponding coordinate of “1” is also “1”, the control unit 6 starts the protocol control unit 6 or the line control unit 7 with an internal serial number to request processing. If the corresponding bit of the control status table 11 is "0", nothing is performed. If the result of the inquiry about the execution state of the line control processing is a state other than “not executed”, the processing for the next internal serial number is performed. When activation is performed so as to continuously perform line control processing for each internal serial number up to a predetermined number N of predetermined values, the processing is interrupted by once requesting the periodic activation execution control unit 1 to restart in the next cycle. . Also, registration status table 1
When the search reaches the end of the change serial number area of 0, the periodic start is finished.

(3) In the case of data deletion, the internal serial numbers are accessed sequentially from the beginning of the deletion serial number area C of the registration status table 10 to find an internal serial number whose coordinate bit value for the relevant internal serial number is "1". If the corresponding coordinate in the control status table 11 is "0", the protocol control unit 6 or the line control unit 7 is inquired about the execution state of the line deletion related to the corresponding internal serial number. 7 and request that it be processed with an internal serial number. If the corresponding bit of the control status table 11 is "1", nothing is performed. If the inquiry result of the line deletion processing execution state is a state other than not executed, the processing for the next internal serial number is performed. When activation is performed so as to continuously perform the line control processing for each internal serial number up to the specified value N, the processing is interrupted by once requesting the periodic activation execution control unit 1 to restart in the next cycle. When the search reaches the end of the change serial number area of the registration status table 10, the periodic start is ended.

The protocol control unit 6 performs the operations described in the above (1) to (3)
In response to a call or disconnection instruction from the call setting execution unit 5a or the call release execution unit 5b, a call event and a disconnection event are transmitted to the line control unit 7, and connection completion and disconnection confirmation are received from the line control unit 7. Then, the internal serial numbers are stored in the table drivers 8b (for call connection) and 8c (for call disconnection).
Notify.

The line control unit 7 responds to the inquiry about the link state or the line state from the protocol control unit 6. In addition, it performs processing for the line in response to a link establishment or release instruction or a parameter change instruction from the protocol control unit 6.

When the call control execution unit 5a or the call release execution unit 5b completes the line control processing in the protocol control unit 6 and the line control unit 7 as described above, the virtual terminal program 4 sends the table driver from the protocol control unit 6 to the table driver. Activate 8b (for call setup) or 8c (for call release). Table driver 8b or 8c in this case
Is as follows.

In the case of data registration / data change, when the line control processing is completed, the table driver 8a or 8b informs the protocol control unit 6 of its internal serial number. D,
The corresponding coordinate bits d and e of E are set to “0”. In the case of data deletion, when the internal serial number is notified from the protocol control unit 6 when the line deletion processing is completed, the corresponding coordinate bit c of the deletion serial number area C of the registration status table 10 is set to “0”. Also, “0” is set to the bit f of the corresponding coordinate of the deletion serial number area F in the control status table 11.
The contents set in the registration status table 10 and the control status table 11 by these operations are shown as the line control completed states shown in the respective items of registration, change, and deletion in FIG.

The restart controller 3 is started when a system restart occurs, and starts the table driver 8a as soon as the system is started. However, in the case of a minor failure, the contents are not guaranteed because the contents on the memory (MM) 9 are guaranteed. In the case of a severe failure, the registration status table 1 is stored in the memory (MM) 9 from the hard disk device 13 at the time of system startup.
The content of 0 is recovered, and the content of the control status table 11 is initialized (set to "0"). The activated table driver 8 a sets the bit in the control status table 11 corresponding to the internal serial number registered or changed in the registration status table 10 to “1”, so that the call setting execution unit of the virtual terminal program 4 It requests the periodic start execution control unit 1 to start the call release execution unit 5a or the call release execution unit 5b.

If the line control processing for the deleted line data has not been performed before the system restart,
The control status table 1 for the internal serial number from which the table driver 8a started by the restart control unit 3 has been deleted
In order to set the corresponding bit of "1" to "0", it requests the periodic start execution control unit 1 to start the call setting execution unit 5a or the call release execution unit 5b.

FIGS. 6 to 9 show examples of operation sequences for registering, changing, and deleting line data. FIG. 6 shows a normal operation example of periodic startup, in which a command for registering, changing or deleting line data is input from the maintenance console (FIG. 6A). In this case, commands for a plurality of lines (assuming> N) are input. The command processing unit 2 registers the line data represented by the command in a line data registration unit (not shown) (b), generates a request to the table driver 8, and registers the registration status table 10 as described above. And control status table 1
Writing is performed on the bit in the area corresponding to 1 (c).

Further, the command processing section 2 sends a response to the maintenance console (step e), and sends a cycle start request to the cycle start execution control section 1 (step f). When activated at the timing (@t), the periodic activation execution control unit 1 activates the call setting execution unit 5a or the call release execution unit 5b (g). In FIGS. 6 to 9, the name "correction processing execution unit 5" is used as a name representing the functions of both the call setting execution unit 5a and the call release execution unit 5b.

The correction process execution unit 5 is a task that is started periodically, and the control value N is determined so that once started, the process is interrupted when only N lines of processing are performed. The correction processing execution unit 5 reads the registration status table 10 and the control status table 11 (h), and in accordance with the status, issues a correction instruction such as link establishment / release so as to match the update data with the protocol control unit 6 and the line. It is supplied to the control unit 7 (i). In response, the line controller 7 connects / disconnects (releases) the line.
Is sent to perform line processing (j).

When the processing for the N lines of the regulation value is completed, the correction processing execution unit 5 temporarily stops and notifies the periodic activation execution control unit 1 (k in the same manner). If there is a start request from another after the suspension time, the process can be executed. That is, it is possible to execute the command processing online.

Then, after the suspension, the correction processing execution unit 5 receives the activation request from the periodic activation execution control unit 1 (same as 1), and the correction processing execution unit 5 executes the remaining X times (N times) which have not been completed by the processing for N lines executed by the command a. ≦ N times), a correction instruction is issued to the protocol control unit 6 and the line control unit 7 (m), and processing is performed for each line (n).

FIG. 7 shows an example of an operation sequence in which another line data updating process is performed during a temporary suspension. Also in the sequence of FIG. 7, although not shown, the same processing as in a to f of FIG. 6 is performed, and as shown in a to d of FIG. Above)
Is executed, and the periodic start execution control unit 1 is notified of the temporary interruption (i in FIG. 7). In this sequence, when line processing for N lines is being performed, the following command is input from the maintenance console (step e). Thereby, the same operation as that of b to f of FIG. 6 is performed (f to f of FIG. 7).
g, j, k).

In this case, the correction execution section 5 runs for multiple cycles. However, since the same task cannot be started at the same time, when the start is delayed as in this case, the periodic start execution control unit 1 starts the period periodically while waiting for the start. Since both of the correction processing execution units 5 that are running for multiple periods operate while referring to the registration status table 10 and the control status table 11, the line control process for all registration data is completed (that is, the control status table 10). When 11 becomes all "0"), the periodic start is ended. In the case of FIG. 7, the correction process execution unit 5 executes a certain number of line processes by the following command (generated at k in FIG. 7) by starting (the same k), correcting instruction (the same m), and event (the same n). , Suspends and waits (same o). After that, the correction processing execution unit 5 is started (p in FIG. 7) and executed to execute the remaining line processing of the line processing (c and d in FIG. 7) executed for N lines in response to the previous command. (Id. Q, r).

FIG. 8 shows the operation when the line control processing is completed. When an event of notifying the line connection or the line release (disconnection) from the line to the line control unit 7 and the protocol control unit 6 occurs, the table driver 8 A request is made to update the registration status table 10 and the control status table 11 (FIG. 8).
A to c).

FIG. 9 shows an operation sequence when the system is restarted. The respective operations a to f in FIG. 9 are the same as the same reference numerals in FIG. 6, and after a cycle start request (f in FIG. 9) is sent from the command processing unit 2 to the cycle start execution control unit 1, in this example, It is assumed that system restart (initial setting, etc.) has been executed (g).

At this time, the restart controller 3 requests the table driver 8 to read the contents of the registration status table 10 and the control status table 11 (h to j). In the case of system restart due to a severe failure, the content of the control status table 11 is initially set to “0”. In this case, the cycle start request shown in FIG.
(K in FIG. 9). Thereafter, the correction process execution unit 5 is started by the periodic start execution control unit 1 (same as 1), and the correction process execution unit 5 reads the registration status table 10 and the control status table 11 (same as m) and before the system restarts. Line processing is executed based on the line data for which registration / change has been completed (n, o).

Although not shown in FIG. 9, when this processing is executed, the bit of the internal serial number for which the processing of the control status table 11 has been completed is set to “1”. However, if the line control processing has not been completed for the deleted line data before the system restart, the registration status table 10 is set to “0” in the corresponding bit of the control status table 11 for the deleted internal serial number. To do so, the correction processing execution unit 5 is started.

In the description of the above embodiment, the components of the periodic start execution control unit 1 to the table driver 8 shown in FIG. 4 are realized by software, but the respective functions may be realized by hardware. Also, the call setting execution unit 5
a, the call release execution unit 5b can be integrated as the correction processing execution unit 5 or, conversely, can be separated. The table drivers 8a to 8c can also be integrated or separated into one.

[0064]

According to the present invention, it is possible to complete various operations accompanying the change of line data at high speed in the online processing, and to automatically continue the line control processing after recovery from the failure. This makes it possible to improve the reliability of the line data change processing, and also to improve the performance of various devices that use the line by realizing the line data change by online processing, thereby registering, changing, and deleting the line data and the system. The burden on the maintenance person (operator) in each process of restart can be reduced.

[Brief description of the drawings]

FIG. 1 is a principle configuration diagram of the present invention.

FIG. 2 is an explanatory diagram of a registration status table and a control status table.

FIG. 3 is an example of a system configuration to which the present invention is applied.

FIG. 4 is a configuration diagram of an embodiment.

FIG. 5 is an explanatory diagram of a change in bit content of each area of a registration status table and a control status table.

FIG. 6 is an operation sequence of each unit when performing line control processing by periodic activation.

FIG. 7 is an operation sequence of each unit when a plurality of periodic activation requests are generated.

FIG. 8 is a diagram illustrating the operation of each unit when the line control processing is completed.

FIG. 9 is a processing flow of each unit when the system is restarted.

FIG. 10 is an explanatory diagram of Conventional Example 1.

FIG. 11 is an explanatory diagram of Conventional Example 2.

FIG. 12 is an explanatory diagram at the time of system restart when the method of the second conventional example is used.

[Explanation of symbols]

 REFERENCE SIGNS LIST 1 periodic start execution control unit 2 command processing unit 3 restart control unit 4 line control processing unit 5 correction processing execution unit 6 protocol control unit 7 line control unit 8 table driver 9 table storage unit 10 registration status table 11 control status table

Claims (2)

(57) [Claims] 1. A communication apparatus for performing communication via a plurality of lines, comprising: registering / updating memory data in a batch registration / update of line data such as physical conditions, logical conditions and protocol parameters of the plurality of lines; Has a structure to independently process the initial setting (link set, call setting, etc.)
Data (tables, etc.) that periodically activates the line initialization process and manages the registration status and control status
A line data processing method characterized in that when a predetermined number of data is executed for a predetermined time, the processing is interrupted halfway and another registration / update processing request is accepted at the time of the interruption. 2. The system according to claim 1, wherein data for managing a registration status and a control status is read out in the restart control when a system failure occurs, and the initial setting process is continuously restarted for each line for which the line initial setting process is not completed. Line data processing method characterized by the following.