KR100462860B1 - Setup method of new version software package for open architecture system - Google Patents

Abstract

The present invention relates to a method for installing a new version of a software package in an ATM switching system in an Asynchronous Transfer Mode (hereinafter referred to as ATM) switching system when the version of the software package is newly changed.

An open switching system, such as an ATM switching system, includes a loading server block (WSLSF) of a workstation, a loading server block (LSF) located in a master main processor of an exchange, and an interprocessor communication block responsible for communication between the WSLSF and an LSF. IPC). In the open switching system, a new version software package installation method includes a new package dumping step in which the WSLSF receives an operator's request and dumps a new version of the software package stored in the workstation to a specific directory of the master main processor of the exchange. ; Applying a new package by the LSF of the master main processor to apply the dumped new version of the software package to each main processor of the exchange.

Description

Setup method of new version software package for open architecture system

The present invention relates to an asynchronous transfer mode (hereinafter referred to as ATM) switching system, and more particularly, to a method of installing a new version of a software package in an ATM switching system when a version of a software package is newly changed. will be.

In general, in ATM switching systems (ACE64, ACE256, ACE2000), when a software package version changes, a new software package is dumped from the workstation to the auxiliary disk of the exchange's main processor and the dumped software package is changed. By applying it to all main processors of the exchange.

In conventional ATM switching systems (ACE64, ACE256), the exchange's Load Server Function controls a new software package on the workstation's disk and dumps it to the exchange's disk using a file control library. do. That is, the switching server block (LSF) of the exchange transfers the file information to be dumped to the file control library, and the file control library retrieves the corresponding file from the disk of the workstation and designates the designated directory of the exchange main disk (hd0). By writing to, you dump the new version of the software package one block at a time. Subsequently, when an operator's request is input, the software package applied to the exchange disk is applied to all main processors of the exchange with reference to the loading information to be loaded for each main processor.

This conventional approach is controlled by the Loading Server Block (LSF) present at the switchboard of the new software package present at the workstation. In addition, since the block information to be loaded for each main processor is present in a programmable logic device (PLD) in the form of a database, it is recommended to receive the correct dump file list or to replace the software package version automatically when applying a new package. There is an impossible problem.

In summary, the loading server block (LSF) running at the existing exchange is newly added or deleted because the loading server block (LSF) controls the software package existing on the workstation's disk. Since the file information is not known, only the software block information of the software package existing in the workstation disk is present in the currently running PLD is dumped from the workstation disk to the exchanger disk. In addition, newly added or deleted software blocks, the PLD information of the main processor of the exchanger disk is manually placed on the exchanger disk using SROS Ethernet primitive, and the operation / maintenance processor (OMP) Since it can be applied by restarting, there is a problem that the software package version cannot be automatically installed.

In addition, the loading server block (LSF) transmits the file information to be dumped to the file control library, and the file control library dumps the file existing on the workstation disk to the exchanger disk by IPC (Inter Processor Communication), so that the data of the execution block Transparency could not be guaranteed. Because the file control library only has the ability to open, read, and write files on the workstation, and there is no function to cope with errors between the workstation and the exchange. There is no problem.

It is an object of the present invention to perform all operations online at the request of an operator when applying a new version of a software package to an exchange system, and to handle / recover any errors between the workstation and the exchange disk. By providing a method for installing a new software package in an open exchange system that minimizes service delays and facilitates operator convenience and transparency of software packages.

The new version of the software package installation method in the open switching system of the present invention to achieve the above object, the loading server block (WSLSF) of the workstation, the loading server block (LSF) located in the master main processor of the exchange, and the WSLSF and In an open exchange system having an interprocessor communication block (IPC) that is responsible for communication between LSFs, the WSLSF receives an operator's request and specifies a new version of the software package stored at the workstation to specify the master main processor of the exchange. A new package dump step of dumping to a directory, and applying a new package to the LSF of the master main processor applying the dumped new version of the software package to each main processor of the exchange.

1 is a configuration block diagram for installing a new version of the software package in an open communication system according to the present invention;

2 is a signal flow diagram illustrating a software package dump process according to the present invention;

3 is an operational flowchart illustrating a new software package version replacement process according to the present invention.

※ Explanation of code about main part of drawing ※

11: MMC (man & machine communication) processing unit

11a: Package Dump Installation Class (ActPkgDump.cpp)

11b: Package Application Class (RstPkg.cpp)

12: MMC handler class (MMCHandler.cpp)

12a: Package dump installation function (ActPkgDump method)

12b: Package application function (RstPkgSys method)

13: File handler management class (FileHdleMgr)

14: disk

15: Load Server Function

15a: PkgDump Process

15b: Apply New Package (RstPkgSys) Process

16: disk

17: Inter Process Communication

Hereinafter, with reference to the accompanying drawings illustrating a new version software package installation method in the open exchange system of the present invention.

For normal service of the ATM switching system, the main processor consists of pre-installed hardware and loaded and executed software. The processor must provide this software package with the necessary information for dumping, backing up, and starting up the package between the operator matching workstation and the secondary storage of the master main processor. Should be newly applied to the exchange system.

1 is a block diagram illustrating the installation of a new version of a software package in an open communication system according to the present invention. This is largely composed of a Loading Server Function in WorkStation (hereinafter referred to as WSLSF) of a workstation and a Loading Server Function (hereinafter referred to as LSF) 15 of an exchange. The WSLSF and the LSF perform data communication by inter processor communication (hereinafter referred to as IPC) 17.

WSLSF accepts the operator's request and executes the dump command, the new package application command, and each operator's request command, and outputs the result of the execution to the operator. It consists of a class library part that accepts, performs the actual function, and performs the matching function with the exchange. The LSF 15 resides in a specific main processor of the exchange (main processor for ACC0 disk control) (hereinafter referred to as master main processor). The master main processor ACC0 is a main processor operating as a master of a maintenance function that can be interlocked with the disk 16.

The MMC processing unit 11 dumps two packages and uses two boundary classes (Package Dump Installation Class (ActPkgDump.cpp) 11a and Package Application Class (RstPkg.cpp) 11b) for MMC processing to apply a new package. And two control library classes (MMC handler class (MMCHandler.cpp) 12 and file handler management class (FileHdleMgr) 13). The MMC handler class 12 includes a package dump installation function (ActPkgDump method) 12a and a package application function (RstPkgSys method) 12b. The two boundary classes above link the control library together to form an independent class library, which creates an ACT-PKG-DUMP for package dump and an RST-PKG-SYS for new package application on the exchange main processor. . In addition, OS primitives provided by SROSD, which provides a communication channel with the exchange, and other Solaris operating systems, the Solaris environment.

The LSF 15 exists only in ACC0 with the disk 16, and forms a list of blocks to be loaded on each main processor, and the loading client function (hereinafter referred to as LCF) present in each main processor. On request, the block is read from disk 16 and sent to the LCF. It also accepts the operator's request (MMC) and performs its functions. The LCF 15 resides in all main processors of the exchange and loads a block of data (a.out) sent from the LSF into the memory of the master main processor.

The package dump installation (ActPkgDump) class (11a) of the MMC processing unit (11) is an independent execution class. When the dump is requested, the package dump (PkgDump) member function of the MMC handler (MMCHandler) 12 is executed. Outputs an error code when performing an abnormal dump. In addition, if timeout occurs during interprocessor communication (IPC) between WSLSF and LSF, the package dump (ACT-PKG-DUMP) process is automatically terminated.

The new package apply (RST-PKG-SYS) class, created by the package apply (RstPkgSys) class, is an independent execution class that accommodates the operator's package replacement needs. It executes the package application (PstPkgSys) member function of the MMC handler and outputs the execution result to the operator. Automatically terminates the new package application (RST-PKG-SYS) process when a timeout occurs.

First, the function of each component constituting the present invention will be described.

The MMC handler class 12 performs interprocessor communication (IPC) between the WSLSF and the LSF. The MMC handler class 12 performs IPC communication with the exchange in this class when the operator requests the loading MMC. For this function, the MMC handler class 12 includes a package dump (PkgDump) member function and a package apply (RstPkgSys) member function. The package dump (PkgDump) member function is a class member function that handles the dump execution request of the operator. It performs the package dump operation by LSF and interprocessor communication (IPC) together with the file handler management (FileHdleMgr) class. The block information is output to the operator at the completion of one block dump. Package application (RstPkgSys) member function is a class member function that handles the package replacement request of the operator. It requests LSF through the package version information IPC of the replaced package and returns a response from the LSF to the package application (PstPkgSys) class. .

The file handler management (FileHdleMgr) class (13) provides the MMC handler class (12) and input parameter control and initialization for performing package dump / backup functions, reading / writing of workstation directory files, and sending dump code to the exchange. Perform. This file handler management class contains several member functions, which include ReadLBInfo (), Ver2Dir (), ReadVerInfo (), GetSize (), Initbuf (), TxBlkDump (), and Isspace ().

The member function ReadLBinfo () returns a block information existing in LBINFO and LBINFO / version (VERSION) file information in order to obtain dump block information when an operator dumps. Here, LBINFO is a file holding block information to be loaded to the exchange, and reads the LBINFO file from the LSF to create a block list to be mounted in each main processor. The member function Ver2Dir () changes the path information entered by the operator into a directory structure. The member function ReadVerinfo () reads and returns the version (VERSION) information for a particular workstation directory. The member function GetSize () calculates and returns the actual size of the block in LBINFO. The member function Initbuf () is used to initialize a character array to a null state. The member function TxBlkDump () reads a block from the directory and sends it to the exchange 1k bytes per IPC. The member function Isspace () checks the space area when searching LBINFO / VERSION.

The version information is a file containing operational package information on the exchange disk in a directory structure, and is always present at the disk root (hd0: /). If the contents of the version file are hd0: / SEC, then each main processor is loaded with executables existing under hd0: / SEC /.

The LSF 15 is present only in ACC0 and starts the process of performing a dump / package replacement by accepting the operator's request via WSLSF. ACC0 is an exchange master main processor that can be linked with a disk and acts as a master for maintenance functions. Check whether the dump is executed by flag to prevent another dump or backup function from being executed. The LSF has a package dump (PkgDump) process 15a and a package apply (RstPkgSys) process 15b. The package dump (PkgDump) process is a process performed on the request of ACT-PKG-DUMP. The package dump (PkgDump) process dumps the contents of the workstation's LBINFO by 1k bytes (maximum IPC size) in the directory requested by the operator. However, LSF's PkgDump process can only be used if the path to be dumped is the current directory, or if the directory creation fails, or if the interprocessor communication (IPC) transfer with WSLSF has failed (the dump is repeated three times). If any of the LBINFO / KBINFO / VERSION files are not in the dump list, it is treated as a dump error.

The new package application (RstPkgSys) process is a load server processor of an exchange that executes an operator's packet version replacement request, and performs a package version replacement function using an algorithm as shown in FIG. It performs a function of notifying the user.

Now look at the software package dump process with reference to the signal flow diagram of Figure 2 as follows. Software packages created outside the system must be finally loaded into the main memory of each processor. Therefore, after the first move to the operator registration workstation to match the outside of the system, it is transferred to the disk attached to the master main processor (ACC0 in the case of the ACE2000 system to which the present invention is applied) and stored, and the main startup process through the processor startup procedure Is moved to the main memory of The process of moving a software package from the operator registration workstation to the secondary storage of the master main processor is called a software package dump. This is done at the operator's request. When the operator has not yet loaded any software packages on the system or needs to move a newer version of the software package into the system, the software package dump function after storing the appropriate software package in the auxiliary storage of the operator matching workstation. Is performed. At this time, the operator specifies the location of the software package stored in the auxiliary storage of the operator matching workstation and the location to be stored in the auxiliary storage of the master main processor. That is, the operator enters the directory name of the workstation where the package exists through MMC and the directory name to be moved to the disk of ACC0.

When the package dump installation request (ACT-PKG-DUMP) (S201) is input from the operator as described above, the package dump installation (ActPkgDump) class 11a checks the version information from the file handler management (FileHdleMgr) class 13 (S202), the package dump function (PkgDump Method) of the MMC handler class 12 is called (S203). The MMC handler class 12 then sends a software package dump request to the LSF 15 (S204), and the LSF requests a dump list from the MMC handler class 12 (S205). Then, the MMC handler class 12 reads the LBINFO file and the version (VERSION) information from the file handler management class 13 to generate a dump list (S206), and transfers the dump list to the LSF 15 (S207). . The LSF 15 receives a response to the dump list from the MMC handler class 12 (S208), and sequentially requests blocks to be dumped based on the received dump list (S209). Then, the MMC handler class 12 requests the file handler management class 13 to dump the reception block (S210). Then, the file handler management class 13 transmits a dump code having a size set in 1k or IPC to the LSF 15 (S211), and the LSF 15 stores the received dump code in a directory designated by the operator. The MMC handler class 12 responds to the dump code (S212). The MMC handler class 12 repeats the dump request of the reception block to the file handler management class 13 (S213). The dump request of the reception block is repeated until the dump of one block is completed. When the dump of one receiving block is completed, the MMC handler class 12 transmits a dump completion message to the LSF 15 (S214), and outputs a block dump completion message to the operator (S215). In addition, the LSF 15 transmits a response message to the dump completion message to the MMC handler class 12. The LSF 15 requests the dump block repeatedly from step S209 for the next dump block to which the block size is larger than zero based on the above dump list. When the dump for all blocks is completed, the MMC handler class 12 transmits a dump output completion message to the package dump installation class 11a (S217).

When dumping a package, IPC loss of the workstation and the exchange period may occur. If you record only the received data to the exchange without accounting for this IPC loss, you will have to perform a recovery procedure because it may not cause any problems. In the present invention, in order to prepare for the occurrence of IPC loss, a method of transmitting a response to all IPC transmissions between the ActPkgDump a.out and LSF_PkgDump processes must be used (stop and wait), and register a timer after each IPC transmission. If no response is received during the process, it is determined that the IPC is lost, and the dump is completed until the dump is completed. Even if other errors occur (file read / write / open / create error), the current errors are notified to each other between ActPkgDump a.out or LSF_PkgDump processors so that control of the error (request of the next block dump in case of recovery / recovery failure) occurs. Do it.

Referring to the operation of the package in the LSF with reference to the operation flowchart of FIG. 3 as follows.

When the new package is dumped to a specific directory (eg, hd0: / SEC /) of the hard disk (hd0 :) of ACC0 by using the package dump function through the processes as shown in FIG. Apply the newly dumped software blocks to all main processors. In the ACE2000 to which the present invention is applied, a method of applying a new software package includes a standby loading function and a package applying function using the RST-PKG-SYS command. Explain.

After the operator dumps the new software package to a specific directory on the hard disk (hd0 :), the operator uses the MMC to apply the newly dumped software block to all main processors. When the operator enters the RST-PKG-SYS command and the name of the directory in which the newly applied software package is stored, the package application function of the MMC handler is called, and this package application creates an LSF_RstPkgSys process of the LSF block to introduce the new package to the system. Apply.

The package application process of the master main processor (ACC0) operates to accommodate the new package application requirements of the operator, and executes an operation flowchart as shown in FIG. Change to the directory where the package to be applied is dumped. This will be described in detail as follows.

First, when the package application process starts (S301), the master main processor checks the path for restart (S302), and if the package is applicable to the restart path (S303), checks the state of all main processors (S303). S304). However, if the package is not applicable (S303), an error message is reported (S305) and ends.

The state of all main processors is checked (S304), and if all main processors are normal (S306), the flow advances to step S307 to store the number of main processors and to suppress database backup. If all main processors are abnormal (S308), the process proceeds to step S305 and an error message is reported. If all the mail processors are abnormal in step S308, the flow advances to step S307 to store the number of main processors operating normally and to suppress database backup.

Next, if the database backup suppression is not successful (S309), the flow advances to step S310 to allow database backup (S310) and then ends. However, if database backup suppression is successful (S309), step S311 and step S317 are performed simultaneously. In step S311, restart signals are transmitted to the main processors in the normal state, and a timer is set. When the response is received from the main processors, the reception count value is increased (S312). If all the main processors that have sent the restart signal receive a response and the restart signal transmission count and the reception count value are the same (S313), the corresponding package application result is reported (S315). Restart the master main processor (ACC0) (S316) and ends. However, if the restart signal transmission count and the reception count value are not the same in step S313, it is detected whether the timer is in an active state (S314). If the timer is in an active state, step S312 is performed, and if the timer is not in an active state, step S315 is performed. .

On the other hand, if the database backup is suppressed in step S309, in step S317 the version file is exchanged for a new package version (S317). If the exchange of the version file fails (S318), the previous version file is recovered (S319), and the path (hd0: / BMT /) in which the existing software package is stored is stored as the version file (S320). On the other hand, if the version file is successfully exchanged (S318), the path (hd0: / SEC /) where the new software package is stored is stored as a version file (S321), and the path where the existing software package is stored (hd0: / BMT /) is Save the previous version file (S322, S323).

As described above, according to the present invention, a new software package can be dumped (PST-PKG-DUMP), and the operator can apply the new software package (RST-PKG-SYS) while on-line. Reduce downtime and easily apply new software packages to the switching system. In addition, by accommodating error recovery during data dump by IPC transmission between the workstation and the exchange main processor, the transparency of package data can be guaranteed.

Although described above with reference to a preferred embodiment of the present invention, those skilled in the art will be variously modified and changed within the scope of the invention without departing from the spirit and scope of the invention described in the claims below I can understand that you can.

Claims (6)

In an open switching system having a loading server block (WSLSF) of a workstation, a loading server block (LSF) located at a master main processor of an exchange, and an interprocessor communication block (IPC) that is responsible for communication between the WSLSF and the LSF. In a method for installing a new version software package on the exchange, A new package dumping step of the WSLSF receiving an operator's request and dumping a new version of the software package stored in the workstation to a specific directory of the master main processor of the exchange; When a software package apply command is input from the operator, the LSF changes the contents of a version file to the specific directory where the new software package is dumped so that the main processors of the exchange load the new software package dumped in the specific directory. Making a step; Requesting restart by the LSF from the main processors in a normal state among the main processors; If all of the response signals for the restart request are input from the main processors requesting the restart, the LSF outputs a new package application success result to the operator and restarts the master main processor of the exchange; The LSF sets the new software package in the specific directory as the current version and saves the existing software package as the previous version if the new version of the software package is successfully applied. How to install. The method of claim 1, wherein the dumping of the new package of the WSLSF, When the software package dump command is input from the operator, the WSLSF checking the version information of the new package and transmitting a software package dump request to the LSF; When a dump list is requested from the LSF, the WSLSF generating a dump list including an LBINFO file and version information in which software package information to be dumped to the exchange is recorded and passing the dump list to the LSF; When a dump list reception response is input from the LSF and a block to be dumped is requested, a dump code of the blocks to be dumped is divided into a predetermined size and transmitted to the LSF, but after the dump code of the predetermined size is transmitted, a response is received from the LSF. How to install a new version of the software package in an open exchange system, characterized in that it comprises the step of transmitting the dump code in the following sequence if it is entered. The method of claim 2, wherein the new package dump step of the LSF, If a software package dump request is input from the WSLSF, the LSF requesting a dump list from the WSLSF; When the dump list is input from the WSLSF, the LSF sends a dump list reception response to the WSLSF and requests the WSLSF to sequentially send blocks to be dumped based on the dump list; When the dump code of a predetermined size obtained by dividing the block requested to be transmitted from the WSLSF is input, the LSF further comprises storing the dump code of the predetermined size in the specific directory and receiving a response to the WSLSF. How to install a new version software package on a switching system. delete The LSF of claim 1, wherein if the response signal for the restart request is not input from all main processors requesting the restart within a predetermined time, the LSF outputs a new package application failure result to the operator and sends the master main processor of the exchange. Installing a new version of the software package on an open exchange system, further comprising a restart step. 6. The open exchange system of claim 5, further comprising: recovering a version file of the existing software package if the application of the new version of the software package fails, and maintaining the existing software package at the current version. How to install a new version software package.