KR930010286B1 - Maintenace system in electronic exchange - Google Patents

Abstract

The method for generating processor load data suitable to relations registered to a data administration system and for generating data to be reference to distributed data base system. The method comprises the steps of: (A) verifying input station data necessary to operate an exchange; (B) sending error message when errors are detected from the input station data; (C) generating relation data by processor units and generating object files; (D) generating tuple data and constructing files by processor units; (E) generating relation data; (F) generating relation search data; and (F) generating process or load data by linking results of the step (A)-(E).

Description

PLD Manufacturing Method for Initial Operation of Electronic Switching System

1 is a block diagram of an electric electron exchanger to which the present invention is applied.

Figure 2 is a structural diagram showing the flow of the PLD manufacturing method according to the present invention.

3 is a flow chart of a PLD manufacturing method according to the present invention.

4 is a flowchart showing a data verification process in generating relation actual data of FIG.

* Explanation of symbols for main parts of the drawings

1: ASS 2: CCS

3: INS 4: ASP

5: MMP 6: OMP

7: DBMS 8: LDB

9: PLD 10: INP and NIP

11: CDB

The present invention relates to a method of manufacturing a processor load data (PLD) for the initial operation of the electronic exchanger.

In the existing data generation, the data required for the operation of each switching center was inputted to the generating program, and the program was executed to generate the data. Therefore, there was a need to change the program even if some data was changed as well as the exchange installation station. However, with the development of communication means and the rapid increase in the demand for communication, the type and amount of data has become enormous, and moreover, the recent electronic switchboard has a wider service area, a wider variety of services, and increased capacity than the existing exchange system. It became. Therefore, it is very difficult and inefficient to input data necessary for the operation of the exchange by the human being for each exchange installation system and to change the data generation program each time. Therefore, it is necessary to quickly generate accurate data for the electronic switching system and develop a tool for processing the same.

Therefore, the present invention generates the data necessary for operation of each switching center in accordance with the structure of the relation registered in the Data Adiministration System (DAS) and provides the data to the user in a distributed database of the electronic switchboard. The purpose is to provide a PLD manufacturing method that accurately generates the referenced information.

In order to achieve the above object, the present invention provides a Central Control Subsystem (CCS) that performs operations and maintenance functions, an Interconnection Network Subsysytem (INS) that performs centralized call processing, and an ASS (distributed call processing). In the method of manufacturing PLD (Processor Load Data) of an electronic switching system including an Access Switching Subsystem, the first step of verifying the data when the station data necessary for the operation of the exchange is input is to generate the actual data of the relation. A second step, a third step of generating relation search information, and a fourth step of comprehensively linking the results generated in the first step and the second step and completing a PLD production.

Hereinafter, with reference to the accompanying drawings will be described an embodiment of the present invention;

1 is a schematic diagram of an electronic exchanger to which the present invention is applied, 1 is ASS, 2 is CCS, 3 is INS, 4 is ASP, 5 is MMP, 6 is OMP, 7 is DBMS, 8 is LDB, and 9 is PLD. , 10 represents INP, and 11 represents CDB.

The electronic switch to which the present invention is applied has a subscriber switching subsystem (hereinafter referred to as ASS: Access Switching Subsystem) 1, and an interconnection network subsystem (INS) as shown in FIG. They provide subscriber and trunk line matching functions, respectively, exchange data and control messages between ASS (1) or CCS (2), and oversee the system's operation management and maintenance functions.

Since the relations used in all electronic exchanges cannot be created and deleted online due to the characteristics of the exchanges, the structure and actual data of the relations are uniformly generated by the all electronic exchange data generator (hereinafter referred to as T10DG: TDX-10 Data Generator). give. And when a request for access to a relation occurs from the user, it creates information to search the relation in a distributed database. This information is stored in a file called a PLD, which is produced by the T10DG on a general purpose computer and loaded into the electronic switchgear system. The T10DG can generate an address to store the PLD in the corresponding memory. The contents of the PLD are stored at the beginning of the PLD where the initialization routine braked by the Concurrent Realtime Operating System (CROS) is loaded at the processor, and the information and relations actually referenced in the distributed database are stored at the specified address in the PLD. Are stored.

2 is a structural diagram showing the flow of the PLD manufacturing method according to the present invention.

Referring to FIG. 2, the overall flow of generating a PLD by registering data used in an electronic switching system by a user is as follows. The amount of data created and managed by the programmers is so large that it cannot guarantee independence between the data, and the continuous change of programs and data cannot effectively accommodate the continuous change. These problems are automatically verified by the programmer-defined data using a software system called a data administration system (hereinafter referred to as a data administration system) and stored in the DAS database (101). The data registered through the DAS is configured in an optimized form through modeling (102), so that a data definition file generator (hereinafter referred to as DFSG: Data Definition File Generator) 103 and a data structure description generator (hereinafter referred to as DFSG: Date) Format Specitication Generatior (104). DDFG is a tool that generates 105 a data definition language (DDL) input file using the Troll / USE database system created by the DAS. At this time, the generated DDL input file forms a meta database (Meta Data Base) for each processor through a data definition language processor (hereinafter referred to as a DDLP) 106 and provides the input to the DDLP. The DDL statements that should be formed form one file for each processor. The FSG is a tool that generates a set of information referenced by the T10DG to create a PLS. This information is needed to obtain actual data of various directories / dictionaries or tables for the minute database (104). T10 G can be divided into two processes for the production of PLD. The first step is to convert 108 the station data specification into the actual values of the relations controlled by the electronic switch distribution database and generate relation-specific data suitable for the relation structure (109). The station data specification describes the data required for the initial operation of the system, such as subscriber-specific service data, trunk line data, and system pyramids. The second process is to generate 110 the actual values of directories / dictionaries and tables referenced in the distributed database by accepting the DDLP and DFSG information. The contents of directories / dictionaries and tables contain all the information a distributed database needs to access a relation: how to access the relation, the number and type of attributes, the number of tuples, the type of storage, and the storage location. After the above two steps are performed, if each piece of information becomes a link, a PLD is generated 111 for each processor. In order to load the PLD into the electronic switchboard, tape making 112 is performed to store the disk 113 installed in the switch 113 and then load the corresponding PLD into each processor (114). When the relation check and change request come from the application program, the distributed database refers to the PLD and passes the information stored at the address to the user.

3 is a flowchart of a PLD manufacturing method according to the present invention.

When information on the system mounting state of the switching center installing the electronic switching system and the information for the initial operation of the switching unit is input 301, the process of generating the relation data and the relation searching information is performed by dividing the relation (step 302). The actual data generation of the relation is performed using the verification and generator (hereinafter referred to as DGV: Data Generation Verification) to verify data (303). In DVG, the range between the number of input tuples and the maximum number of tuples that can be registered and the storage location An error message is output (304) when an error occurs by increasing data occurrence, data suitability for attribute number and type, and correlation between relations in master / slave. If there is no error, a data file matching the structure of the relation is output for each processor (305), and then an object file is generated (306) after compiling. This is provided as input when performing link 316. In addition, the DVG generates information about the number of tuples into which data to be stored in the memory is input for each relation (307) and collects them for each processor to form one file for each processor (308). This file is then used as an input 313 for generating relation information.

The first step of generating relation search information is converted to relation unique number (309), which analyzes a file (ASP_CAT) in which processor information to be stored for each switching center and group information according to the processor is inputted, and the relation is uniquely assigned to each relation. To create a list, the list becomes a factor in determining the size of a directory / dictionary or table. The relation list generation by processor compares the contents of the global catalog (G_CAT) generated by the DDLP based on the group information generated by the DAS, and changes the unique number of the relation to be actually stored in each processor. In the case of a new exchange, a PLD needs to be generated for all processors to be mounted, but when a task for all processors is required when expansion or change is required, a PLD can be generated for a specific processor (310). Therefore, when performing a task for a specific processor, a relation-specific list to be stored in the processor is generated (311). When batch processing for the entire processor, a processor name to be produced from the ASP_CAT is extracted, and a list is generated for all processors. (312). The relational self information generation 313, the interprocessor communication information generation 314, and the distributed relation information generation 315 may be processed at the same time. These processes include information generated by DAS (INDEX_INFORM, DIS_INFORM, DIRECT_INFORM, OTR_INFORM), information generated by DDLP (G_CAT, R_A_CAT, V_A_ACT, L_CAT, J_CAT, P_CAT, DIS_CAT, ACM_CAT), and information generated by DFSG. _TNO, Group_BINSA, Group_LOCK_INFO, Group_HASH, REP_INFORM) are used to create the directory / dictionary and tables referenced by the distributed database by referencing the information needed for execution. In the relation information generation step 313, a real relation directory / dictionary (RDIR / RDIC) including information on each configuration domain of each relation, an access method, the number and size of attributes, the maximum tuple number, and the number of input tuples. ), Join directory / dictionary (JDIR / JDIC), tables for relations stored only on disk (DKO_HEADER, DKO_TABLE), duplicate tables (PEP_TABLE) with information such as processor information with duplicate relations stored and duplicate storage types. Generates the actual value for the one-tuple table (ORT_TABLE) for a relation with a maximum number of tuples. If the access method among the relations stored in the processor is binary search, the work area for the processing is secured in the distributed database. Generating the information necessary for interprocessor communication (14) includes the global directory (GDIR), the lock table (LOCK_TABLE), the direct access function table (DIRECT_TABLE) for relations requiring fast data processing, and the project view relay. Create the actual values of the project directory / dictionaries (RDIR_PDIC). The generation of information about distributed relations (315) generates information about such relations in the distribution tables DIS_HEADER and DIS_TABLE when one relation is distributed and stored in multiple processors. When this information and relations are linked 316, the start address of the directory / dictionary and tables is determined, and the contents are stored in the PLD header information DB_HEADER. In addition, the information is related to each other, so that pointers are connected to be accessed from a distributed database, and a PLD is generated 317 so that all work is completed.

4 is a flowchart showing a data verification process in generating actual data of a relation. When a data verification and relation data file generation request 318 for the input data occurs, it is determined whether a data file is input for each block (319). If not, the relation actual data of the block is matched to the relation structure registered in the DAS. Initialize and generate (320). If the data file is input, the registered data is read in tuple units (321). The data type of each attribute is checked (322) to determine whether it matches the relation structure. If an inconsistency occurs, an error is generated (323). Otherwise, the verified data content is output to the relational data file for each processor (324). In this case, the number of input tuples is compared with the maximum number of tuples that can be registered at maximum (325). If the number of input tuples is small, the tuples corresponding to the difference are initialized (326). . If an overflow error does not occur in the number of input tuples, information on the number of tuples input for each relation is generated (327). If there is data of the block to be generated among the registered station data, it is determined (329). If there is, the data of the next block is verified (330). It is determined whether there is a relation registered in the DAS but not inputted as the station data (331), and if present, the data is initialized for the remaining relation (332). The contents of the directory / dictionary and table generated when relation information is generated, communication information between other processors, and distributed information are generated are as follows.

TABLE 1

TABLE 2

TABLE 3

TABLE 4

TABLE 5

TABLE 6

TABLE 7

TABLE 8

TABLE 9

TABLE 10

TABLE 11

TABLE 12

TABLE 13

TABLE 14

TABLE 15

TABLE 16

The present invention configured and operated as described above loads the PLD required for the operation of the electronic switch in an offline (off-line) operation and loads it into the exchange system. Even if a change request occurs during the operation of the exchange, the operation of the exchange is not stopped. It can be produced without a program change and PLD can be generated only by performing T10DG without changing the program. Therefore, there is an effect of generating inconsistent data and accurate and rapid information.

Claims (5)

Central Control Subsystem (CCS) (1) to perform operations and maintenance, Interconnection Network Subsysytem (INS) to perform centralized call processing, and Access Switching Subsystem (ASS) to perform distributed call processing In the manufacturing method of PLD (Processor Load Data) of the electro-electronic exchanger comprised including (3); When the station data necessary for the operation of the exchange is input, the second step (303 to 308) of generating the actual data of the relation after performing the first step (301, 302) of verifying the data and performing the first step (301, 302). ), After performing the second step (303 to 308), the third step (309 to 315) for generating relation search information and the results generated in the first step and the second step collectively linked to produce the PLD PLD manufacturing method characterized in that performed by the fourth step (316,317) to complete. The method of claim 1, wherein the second steps (303 to 308) are performed; Verifying the data and outputting an error message if it is an error and proceeding to the next step if it is normal, and after performing the first process 303, generating relation data and processing a target file in units of processors. After performing the second process (305, 306), the second process (305, 306), after the third process (307, 308) and the third process (307, 308) for generating information on the number of input tuples for each relation and configure files for each processor And a fourth process (313) of generating the relation information itself. The method of claim 1, wherein the third step (309 to 315) comprises: A second process of generating a relation unique number list for the processor by searching whether the first process 309 converts to a unique number of the relation, the first process 309, and whether the specific processor selection is performed or the batch processing for all processors; After performing the process 310,311,312, the second process (310,311,312), the third process (313) for generating the relation itself information, and after performing the second process (310,311,312), the second process for generating information that can communicate with other processors And performing a fourth process (314) and a fifth process (315) of generating information on distributed relations after performing the second process (310,311 312). 3. The method of claim 2, wherein the first process (303) comprises: The process of retrieving whether the data file exists when the data verification and relation data file creation request is input, if not exists, initializes it according to the registered relation structure, and if the data file exists, reads the registered data and retrieves the data type for each attribute. (318 to 322), after performing the process (318 to 322), if the data type of each attribute is inconsistent, an error message is output, and if it matches, the corresponding data is generated in the relation data file for each processor, and the maximum number of tuples entered By comparing the number of tuples that can be registered, if the number of tuples entered is larger than the maximum number of tuples, if the maximum number of tuples is greater than or equal to the number of tuples that cause a tuple overflow error, the tuples are initialized by the difference. Generating number information (323 to 328), and After execution, it is determined whether there is relation data to be generated among the registered station data, and if present, the process returns to the registered data reading process and is registered in the DAS (Data Administration System), but is not inputted to the station data. PLD manufacturing method characterized in that performed by the first to third processes (329 to 332) to initialize the data for the relation by determining the existence of the relation. The method of claim 3, wherein the first process (309); And generating a relation list using a relation unique number by analyzing a file in which processor information to be stored for each exchange and group information according to the processor are input.