KR960002362B1 - Electronics switching system - Google Patents

Abstract

No content.

Description

How to operate non-residential program of large scale distributed accumulation program control method in all electronic exchange

1 is a diagram illustrating a method of using a processor memory using only a conventional resident program.

2 is a diagram illustrating a method of using a processor memory using the non-resident program of the present invention.

3 is a diagram showing a loading table for managing the resident / non-resident program of the present invention.

4 is a diagram illustrating a resident / non-resident program loading performance flow during initial loading of the present invention.

5 is a diagram illustrating an instruction data generation procedure of an instruction using the non-resident program of the present invention.

6 is a diagram showing a loading state table for managing the loading state of the non-resident program per processor of the present invention.

Figure 7a or b is a view showing the operational flow of the non-resident program when inputting the command of the present invention.

8 illustrates the operational flow of a non-resident program having a driving characteristic of a periodic nature of the present invention.

9 is a flow diagram illustrating a method of using non-resident memory of the non-normal program of the present invention.

In the electronic program exchange system of the accumulated program control method of the present invention, the present invention relates to a method of using a memory of a program. In particular, the program is divided into a resident program and a non-resident program. It is about.

Referring to FIG. 1, in a typical electronic switching system, an accumulation control program is produced as an executable file on a main computer provided with a development environment, and dumped into auxiliary storage in the system, which is used for each corresponding processor. It is stored in the main memory and is initially performed, thereby preparing to perform a unique function. These execution modules are made up of a combination of their own unique functions, and after the initial execution, in a signal reception standby state for receiving an external signal, they are started by a suitable external signal.

Programs run on a general computer can be classified into two types. That is, it is executed after the relevant file is stored in the main memory when the command is input, and is terminated by being deleted from the memory when the execution is completed, and another type already resides in the main memory and immediately executes the function when the command is input. There is a type of program. In this classification, a program used in an electronic switchboard is a type of execution wait that waits for a certain event to occur after startup in memory. This drive is driven by specific signals from matching equipment, such as telephones or trunk lines, periodically, or at the request of the operator, which can be categorized as follows:

1) A process of real-time nature that an event always occurs and must be performed immediately.

Example: call processing, equipment matching, billing process

2) periodic processes (ie, processes that continue to be performed periodically after the system has started up).

Example: periodic equipment monitoring, statistical data collection process

3) Processes that are performed only during certain times of day.

Example: subscriber (relay line) circuit / line test

4) A process that is performed at irregular intervals only at the request of the operator and has a slight delay in execution.

Example: Operator Request Command Function

In recent years, the trend of electronic switchboards requires a variety of functions such as common lines, ISDN, intelligent network collective telephones, in addition to the basic functions, and therefore, a large amount of memory is required.

However, in the conventional memory usage technique, the addition of a function means expansion of a memory, and eventually, the addition of such a memory causes an increase in supply cost. However, the basic program that runs during normal operation in the exchange has a small number of programs in total compared to the total amount of programs, and most of the programs are composed of special functions, additional services, or functions to support the operator's operational maintenance. In most cases this does not. In this development trend, even if additional development is in progress, the basic program is almost unchanged and only additional function programs are expected to increase. Therefore, there is a problem in that memory is inefficiently used by occupying the memory more than necessary for a program which rarely uses the conventional technology.

Therefore, the object of the present invention is that it can be operated with less than half of the memory compared to the general memory method, and even when adding various functions, the additional memory needs less, so that it can be used more efficiently as an optimized memory, and thus the supply cost is considerably increased. The present invention provides a method of operating a non-resident program in a large-scale distributed and accumulated program control method in an electronic switch that can reduce the cost and make program maintenance very easy.

Other objects and advantages of the present invention other than the object of the present invention will be apparent from the following description of embodiments of the present invention with reference to the accompanying drawings.

According to the present invention, a method of operating a non-resident program in a large-scale distributed accumulation program control method includes storing a disc in which the resident program and the non-resident program are stored at the same time and a resident program in the processor memory at startup of the processor, and storing the non-resident program only on the disc. Storing the memory in the processor memory only when the predetermined function is executed and recovering the memory again after the execution of the predetermined function; Determining a resident and non-resident program for each processor by loading the resident program for each processor, and processing the non-resident program upon an initial start request from the data loaded in the step; Generating instruction data of an instruction using the non-resident program; Setting a table to manage loading status of non-resident programs for the processor; Processing the non-resident program upon inputting each command after performing the step; Operating a non-resident program of a nature that is performed at a specific time period periodically after performing the step; And performing an operation as a non-resident program for an irregular program after performing the above steps.

Hereinafter, the present invention will be described in detail with reference to the accompanying drawings.

First, referring to FIG. 2, a method of using a memory in case of separate operation of a non-resident program and a resident program is illustrated. In the hard disk 20, the resident program 21 and the non-resident program 22 exist together, and when the processor is started, the resident program is stored in the processor memory 25, or the non-resident program 22 exists only in the disk 20. It is stored in the controller memory only when the corresponding function is executed (27) to perform the function, and is configured for a variable operation method of the memory for recovering the memory again after the execution is completed.

Referring to FIG. 3, a table representing positions of programs for each execution module is referred to when loading the resident program in each processor. Rows in the table identify file features, such as the file's operating location. Columns are divided into file-specific features. The loc-type represents the program location and double blocks (32). In disk, the non-resident program indicates that the program is normally located on the disk, and in block 31, the memory is a resident program, which means that the program is always stored in the memory. In order to configure non-resident program, each current function block should be classified into memory resident program and non-resident program as follows.

In other words, in the nature of the resident program.

1) Basic Call Processing Program

2) A program that is always run periodically

3) The operator request program that is used frequently by the operator.

Also, as a non-resident program,

1) Programs performed only at the request of the operator, such as detailed tests

2) Program to be executed only at certain time of day

3) Periodic program that is scheduled and operated by the operator

4) It is classified as a test program that is limitedly executed by a skilled person for error tracking or debugging.

4 illustrates a flowchart at the initial start-up of the non-resident program and the resident program. At initial startup, the loader distinguishes between resident / non-resident programs through the data in FIG. 3 described above and prepares for a load request. When a load request occurs in the block 41 of the processor, the block table is retrieved from the block 42 by referring to the table of FIG. 3, the resident / non-resident program is separated in the block 43, and the non-resident program branches to the block 46. The program branches to block 44. The resident program performs loading to store the program in memory and executes it at block 45 when loading is complete. In the case of a non-resident program, no loading is performed, only a flag is set at block 46, and the block is returned to the original program at block 47 to wait for loading of the next block.

5 illustrates an instruction data generation procedure using a non-resident program. In block 51, the input file of the type distinguishes that the instruction is a resident / non-resident program, and in the case of a non-resident program, stores the file name of the non-resident program. With this input file as input, block 52 generates MMS data by means of a man machine interface subsystem (MMS) data generation tool to generate data for non-resident program operation. At 53, these data files are stored on the disk. In block 54, data for various instructions are regenerated by referring to data when a man machine processor (hereinafter referred to as MMP) is loaded. Through this, in block 55, each instruction is prepared to be processed. Will be

6 is a non-resident program loading state table indicating a loading state of each process of the non-resident program. The rows are keyed by each processor and the columns represent the filename of the non-resident program. These indicate the state of the non-resident program to be loaded on each processor. The files that do not need to be loaded with no-needs, loads are already loaded, and nloads are used for loading status data. ) Indicates no loading status. This table is used to find out if the program is loaded into memory when it is necessary to run a non-resident program.

7 illustrates an operational processing flow diagram of a non-resident program upon input of a command by an operator. When an instruction is input, a specific block (MMS) receives it at block 71 and analyzes the information of the instruction at block 72, analyzes whether the corresponding program is a resident / non-resident program, or a processor to be processed, and then the non-resident In the case of a program, it branches to block 75, and if it is a resident program, it branches to block 74. In the case of a resident program, the process is processed in block 74 and terminates in block 81 according to the conventional instruction processing method. In the case of a non-resident program, the designated file is retrieved by the program input data for the instruction input in the block 51, and the loading of the file is referred to as an operation maintenance processor in the block 75 (hereinafter referred to as OMP). It makes a request to the loader's system startup block (system start-up and loading). The loader of the OMP receives the loading request at block 91 and searches the table of FIG. 6 above to find out whether the file has been loaded into memory at block 92 and then at block 93 if the block has already been loaded. Branches to 95 and branches to block 94 if not loaded. In the case of not loading, the non-resident program is stored in the memory by performing a partial loading scheme in block 94. If the loading is already completed, the loading completion status is notified to block 77. That is, the loader notifies the loading result of the MMS to the block 77 of the MMS at block 96, and after the loading request, the MMS waiting for the result at the block 76 receives the completion of loading at the processor, block 77. The instruction input at block 71 is transmitted to the processor executing the non-resident program at block 79, waiting for the instruction processing to end. Upon completion of the instruction processing, block 79 receives the result, notifies the loader that the non-resident program is complete in block 80, and terminates the instruction processing in block 81.

The loader, which has finished processing instructions at block 97, drives a waiting time at block 98 to prepare for the next load, which typically is not entered by one or two instructions from the operator, but continues to be entered by a group of related instructions. The purpose is to reduce the overhead of loading again when the next instruction continues by waiting for the next instruction to continue. After waiting in block 99, when the waiting time ends in block 100, the loader retrieves the memory used by the non-resident program from block 101 to allow another program to be used and ends at block 102.

8 exemplifies how to operate a non-resident program in a specific time period. These are mainly programs that are performed only at certain times of the day, such as subscriber circuits or track tests that are performed at night time. They are timed by the operator at block 111, whereby a timer is driven, and when the specified time is reached at block 112, they are notified of this and request loading to the loader at block 113. When the loading is completed in block 114, the program is executed in block 115, waits for a performance refund in block 116, deletes the memory in block 118 when a block termination notification is received in block 117, It ends at 119.

Figure 9 illustrates a flow chart of the use of non-resident memory when a developer, not an operator, or an expert in the field, wishes to use a non-regular program other than the exchange's basic program only for the purpose of temporarily tracking or testing a fault for a specific purpose. do. Such a program may be present on the disk, but is typically stored on the disk by a tester in a separate storage device (e.g., magnetic tape, etc.) at blocks 121 and 122, and at the request of the operator at block 123. Is stored in memory at block 12 via partial loading by. Thereafter, the test is performed by the operator in block 125. When the test is completed, in block 126, the operator inputs a non-resident program delete command and deletes the corresponding program from memory in block 127 and then blocks in block 128. Will end.

As can be seen from the above description, the effects of the present invention are described.

1) Since the memory usage is reduced, there is no need to add a memory board necessary for the development of additional functions, thereby reducing the supply cost.

2) Over 50% of the existing resident programs are non-resident programs, and when converting them to non-resident programs, the loading time is reduced due to the decrease of the resident programs, and as a result, the transition time from abnormal state to normal state is more than doubled. There is an advantage to shorten.

3) There is an advantage that the maximum call processing capacity and processing speed can be improved by securing extra memory due to the saving of memory.

4) When a program change occurs A non-resident program can be changed directly on the disk, making program maintenance easy.

5) It has the advantage of providing a way to use non-regular program other than regular program.

Claims (8)

In the non-resident program of the large scale distributed accumulation program control method in the electronic switchboard which communicates with the information stored in the resident program and the non-resident program on the disk and the memory for the resident program in the processor memory and the memory for the non-resident program. In the operating method, a disk in which the resident program and the non-resident program are stored at the same time and the resident program at the time of starting the processor are stored in the processor memory, and the non-resident program exists only on the disk and stored in the controller memory only when performing a predetermined function. Recovering the memory again after the completion of the execution; Determining a resident and non-resident program for each file by loading a resident program for each processor (30); Processing a non-resident program on an initial start-up request from the data loaded in step 30; Generating (50) the instructions of the command using the non-resident program; Setting (60) a table for managing loading status of non-resident programs for the processor; Processing operation of the non-resident program upon inputting each command after performing the step 60; A step (80) of operating a non-resident program of a nature which is performed at a specific time period periodically after performing the step 70; And operating the non-resident program for the non-regular program after performing the step (80). 2. The file of claim 1, wherein in the files of step 30, the row direction defines the file of the operating location of the file, wherein the disk 32 stores the non-resident program on the disk. , Memory 31 is a resident program operating method of the non-resident program, characterized in that the program is always stored in the memory. 2. The method of claim 1, wherein said step (40) comprises: requesting an initial start-up (41); Retrieving a block table by referring to the file contents when the initial startup occurs in step 41; Determining (43) whether to be a non-resident program after the step (42); Loading if it is not a non-resident program in step 43; Performing loading after the step (44) to store the program in a predetermined memory (45); Setting a flag only 46 without performing loading in the case of the non-resident program in the step 43; Returning to the original program after performing the steps (45) and (46) and waiting for the loading of the next block (47). The method of claim 1, wherein the step (50) comprises the steps of: (51) storing the file name of the non-resident program in the case of the non-resident program, distinguishing that the command is a resident and non-resident program of the input file; Generating (52) MMS data by means of a human machine matching subsystem (MMS) data generation tool for inputting the input file in step 51 to generate data for non-resident program operation; Storing (53) the data file on the disk after the step (52); Reproducing (54) data for various instructions by referring to the data upon operator matching processor (MMP) loading after step 53; And receiving (55) each command through the step (54) to prepare for execution. 2. The method of claim 1 wherein the row direction represents a processor key and the column direction represents a file name of the non-resident program in the table for managing the loading state in step (60). The method according to claim 1, 4 or 5, wherein the step (70) comprises: (71) inputting the command when various commands are generated; Analyzing (72) information of various commands in the step (71); Determining (73) whether or not a non-resident program is performed after the step (72); In the case where the result of the determination of the step 73 is a resident program, processing the existing instruction processing method 74; In the case of the non-resident program in the determination result of the step 73, the designated file is searched by the program input data for the command input in the step 51, and the loading of the file is sent to the loader of the operation maintenance processor (OMP). Requesting 75; Receiving a loading request from the rod of the OMP after the step 75; Retrieving whether the file is loaded into the memory by retrieving a table managing the loading state in the step (60); Determining (93) whether to load after performing the step (92); If it is not loaded in step 93, performing a partial loading method of loading and storing the non-resident program in a memory (94); Step 96 for notifying the MMS of the loading completion status if the loading has already been completed in step 93; Receiving (77) the MMS waiting for the loading completion state of step (96); A step (78) of transmitting the command input in the step (71) to the processor executing the non-resident program and waiting for the end of the command processing; Receiving a result (79) when the instruction processing is completed in the step (78); Notifying the loader 80 that the non-resident program is complete after the step 79; Terminating the command processing after the step 80; Receiving (97) an end of command processing in step (81); Driving 98 a waiting time after step 82 to prepare for the next loading; Waiting for a while after the step 98; After the step 99, if the waiting ends, the loader recovers the memory used by the non-resident program so that another program is used; And operating (102) after the step (101). 2. The method of claim 1, wherein said step (80) comprises: specifying a time by an operator and driving a timer by said designated time; When the predetermined time is reached after the step 111, the time is notified, and requesting the loading to the loader (112a); Completing the loading after the step 112a to perform a program function and waiting for the end of execution; And receiving a termination notification after the step (114a), deleting the memory, and terminating (117a). 2. The method as claimed in claim 1, wherein the step (90) comprises: receiving a predetermined dump command by a tester or an operator and storing the received dump command on a disk through a predetermined storage device (121a); After the step 121a, partial loading at the request of the operator and storing in the memory 122a; After the step 122a, a program test is performed by an operator, and when the test is completed, the operator inputs a non-resident program delete command to delete the program from memory and terminate the program. How to operate.