JPH06141359A - Private automatic exchange - Google Patents

Abstract

PURPOSE:To relieve the load on a main processor circuit by managing unifiedly system data of a central processing section of the private automatic exchange as a database and reserving/releasing the database area. CONSTITUTION:The private exchange is provided with an exclusive database management table memory 11 implementing write or read processing to system data from/to a data storage memory 10 storing the system data as a database, and the database management table memory 11 is provided with a memory pool management table 12 and a free memory management table 13 and also provided with a means rewriting the memory pool management table 12 and the free memory management table 13 and a means releasing the free memory management table 13 in the database area when the database are built up.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a private automatic exchange, and more particularly, to centrally manage system data of a central control unit as a database, secure and release the database area, and reduce the load on the main processor circuit. Pertain to.

[0002]

2. Description of the Related Art A private automatic branch exchange is equipped with various functions capable of responding to different conditions depending on the installation location. Along with the expansion of the functions, system data of system information such as extension numbers and number translation tables for controlling the private automatic branch exchange are also stored in the data storage memory.

Data management of a central control unit of a conventional private automatic branch exchange will be described below with reference to the drawings.
FIG. 5 is a block diagram showing a configuration of a central control unit of a conventional private automatic branch exchange. In FIG. 5, 1 is a main processor circuit, 2 is an input / output circuit, 3 is a program memory, and 4 is a data storage memory. The data storage memory 4 stores system data such as extension numbers and number translation tables for controlling the private automatic branch exchange.

Next, the operation of the central control unit will be described. The main processor circuit 1 gives an instruction to write the system data of software in the program memory 3 into the data storage memory 4. Further, the main processor circuit 1 accesses the data storage memory 4 to access the data storage memory 4
Directly read the system data stored in the.

FIG. 6 is a diagram showing the configuration of software in the program memory 3 of FIG. In FIG. 6, 5 is an application program section and 6 is system data. The system data 6 is stored in the data storage memory 4, and the system data of the application program unit 5 is written,
Alternatively, when the reading process is performed, the number of information indicating the physical position of the system data 6 stored in the data storage memory 4, that is, the memory address is designated.

[0006]

However, in the above-mentioned conventional data management, the application program section 5 uses the system data 6 stored in the data storage memory 4.
It is necessary to grasp all the memory addresses of the above and the internal configuration of the system data 6. In particular, the number of types of system data is very large, and the configuration also differs for each type of system data, so the application program section is complicated,
The amount of work to do the development increases.

Further, in order to deal with various functions of the private automatic branch exchange, it is necessary to secure a maximum storage area of system data stored and secured in the data storage memory 4. Depending on the installation location of the private branch exchange, an area corresponding to system data that is not used due to its function or the number of lines is prepared, so it becomes an unused area, and effective use of the data storage memory 4 is made sufficient. It had the problem of not having it.

The present invention has been made in view of such conventional problems, and the memory address of the system data 6 reserved in the data storage memory 4 by the application program unit 5 and the system data. 6 It is possible to write or read system data without knowing all the complicated configurations inside, and to reserve a data storage area of unused system data once secured in the data storage memory 4. The object is to provide a device which can be released.

[0009]

In order to solve the problems of the conventional apparatus, the present invention is dedicated to writing or reading data in a memory for storing the system data of a private automatic branch exchange as a database. A memory pool management table for managing a start address and a memory capacity of an unused database area in the memory for data storage, which has a memory for database management table in a central control unit, and a memory for data storage It has a start address of the database area of the system data that is no longer needed and released in the memory, and a free memory management table that manages the memory capacity, and secures a required amount of data storage area when building the system data database. Memory pool management table for And means for rewriting the Memori management table, and means for releasing the free memory management unit table in the database area which becomes unnecessary by reduction of the system data.

[0010]

According to the present invention, the application program section uses means for rewriting the database management table memory and the data storage memory when writing or reading the system data managed as the database. To do. When the database is constructed by the application program section, a means for rewriting the memory pool management table and the free memory management table is used to secure the database area in the memory for data storage,
Further, the memory for data storage is effectively used by using the means for releasing the once secured database area.

[0011]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described below with reference to the drawings.

FIG. 1 is a block diagram showing the configuration of an embodiment of the present invention. In FIG. 1, 7 is a main processor circuit,
8 is an input / output circuit, 9 is a program memory, 10 is a data storage memory, 11 is a database management table memory,
12 is a memory pool management table, and 13 is a free memory management table. The data storage memory 10 stores system data such as extension numbers and number translation tables. In addition, the database management table memory 11, the memory pool management table 12, the free memory management table 13
FIG. 3 is a block diagram added to implement the device of the present invention.

FIG. 2 is a diagram showing the relationship between the memory pool management table 12 and the data storage memory 10 shown in FIG.
In FIG. 2, in the memory pool management table 12
Reference numeral 14 is a memory start address storage unit, 15 is a memory capacity storage unit, 16 is an unused area address storage unit, and 17 is an unused area capacity storage unit. Further, 18 of the data storage memory 10 is a usable memory area, 18A is a used area, and 18B is an unused area.

The start address of the usable memory area 18 is stored in the memory start address storage section 14 of the memory pool management table 12, and the total memory capacity of the usable memory area 18 is stored in the memory capacity storage section 15. The unused area address storage unit 16 stores the start address of the unused area 18B, and the unused area capacity storage unit 17 stores the memory capacity of the unused area 18B.

When the software in the program memory 9 of FIG. 1 constructs a database, the data storage memory 10
Every time a part of the area is allocated as a database area, contents related to the unused area 18B set in the unused area address storage unit 16 and the unused area capacity storage unit 17 in the memory pool management table 12 To update.

FIG. 3 is a diagram showing the relationship between the free memory management table 13 and the data storage memory 10 shown in FIG.
In FIG. 3, 18C is a free area, and the other codes use those mentioned above. The free memory management table 13 stores information for managing the released area when releasing the memory area used as the database area in the data storage memory 10. Figure 3
As shown in, the free memory area 18C has a free memory address 18C-1 and a free memory size 18C at the head of the free area 18C.
-2 has an area to store free memory address 18
The address of the next area to be linked is provided in C-1, and the memory capacity of the released area is set in the free memory size 18C-2.

Each time the software in the program memory 9 of FIG. 1 releases a part of the area used as the database area, the free memory management table 13 shows the free memory address 18C of the released free area 18C.
C-1 is updated and linked.

FIG. 4 is a diagram showing a software configuration in the program memory 9 of FIG. In FIG. 4, 19 is an application program section, 20 is a database, 21 is a database management section, 22 is a memory pool management section, 23 is a free memory management section, 24 is an unused database area, and 25 is a free memory group.

The application program unit 19 performs a writing process or a reading process on the system data 6, and the database 20 is constructed in the data storage memory 10. The system data 6 is stored in the database 20. The database management unit 21 receives and processes an access request to the database 6. The application program unit 19 issues a database access request 27 to the database management unit 21 when performing a writing process or a reading process on the system data 6.

At this time, information indicating the type of system data 6 is designated. Hereinafter, that information will be referred to as a relation number. The database management unit 21 is the memory pool management unit 22.
And a free memory management unit 23. The memory pool management unit 22 manages an unused database area 24. The free memory management unit 23 manages the free memory group 25 of the released database area.

Table 1 is a relation table 26. This relation table is a relation table of the required memory amount (M) for storing the system data corresponding to each relation number (R) and the database management address (A). The database management unit 21 manages the relation table 26,
A memory amount (M) required to store the system data 6 in the database 20 corresponding to the relation number is preset. Further, the database management address (A) assigned by the request for securing the database area can be stored for each relation number (R).

[0022]

[Table 1]

The operation of this embodiment will be described with reference to FIG.

(1) System data database construction operation. The application program unit 19 uses the relation number (R) of the relation table 26 (Table 1) of the system data 6
Is specified and the database management unit 21 is requested to secure a database area. The database management unit 21 acquires the required memory amount (M) corresponding to the relation number (R) from the relation table 26. The database management unit 21 manages a memory area corresponding to the required memory amount (M) by the free memory management unit 23.
Search from inside.

Free memory address 18C-at the head of free area 18C (FIG. 3) connected to free memory management unit 23
If the memory area which can correspond to the required memory amount (M) is found by tracing the link of 1, the free area 18C is allocated as the database area of the system data 6. If no memory area corresponding to the required memory amount (M) is found in the free memory group 25 managed by the free memory management section 23, the memory is searched from the unused database area 24 managed by the memory pool management section 22. , The memory is allocated to the system data 6 to be used area 18A (FIG. 3). The database management unit 21 uses the address of the memory allocated as the database area in the relation table.
It is stored in the database management address (A) of 26 and stored in the corresponding database management address (A).

(2) Release operation of the system data database. The application program section 19 specifies the relation number (R) of the system data 6 and the database management section 21.
Request to free the database area. The release of the database area is used to release an unnecessary area in the used area 18A due to the function of the private branch exchange, the reduction of the number of lines, and the like, and return it to the management of the database management unit 21.

The database management unit 21 that has received the database area release request receives the database management address (A) of the area storing the system database management table corresponding to the relation number (R) and its required memory capacity.
(M) is acquired from the relation table 26. The database management unit 21 indicates that the database area of the system data 6 corresponding to the specified relation number (R) does not exist, and thus the database management address of the relation number (R) in the relation table 26.
A code indicating unallocation is set in the area (A). The released memory area is managed by the free memory management unit 23.

(3) Write system data, or
Read operation. The application program unit 19 specifies the relation number (R) of the system data 6 and requests the database management unit 21 to write or read the database area. The database management unit 21, which has received the writing or reading in the database area, sets the address of the area storing the system data 6 corresponding to the specified relation number (R) to the relation number (in the relation table 26). R). For write requests, the application program section 19
The address of the designated write data is written to the address of the area where the system data 6 obtained from the relation table 26 is stored. In the read request, the relation number (R) of the relation table 26
The data is read from the obtained address of the area where the system data is stored into the buffer designated by the application program unit 19.

In this way, the access request to the database is used as a user interface only for designating the relation number indicating the type of system data, and access to the database area using the physical address is made to the database management unit 21. Entrust the processing.

[0030]

As described above, the private branch exchange of the present invention improves the operability and logicality of data by centrally managing the system data as a database by the relation table managed by the database management unit. be able to. In particular, the application program unit can write or read without being aware of the physical position or configuration of the area in which system data is stored.

Further, since the database area is not fixedly secured but a method of allocating a memory area having a required memory amount is adopted at any time, it is possible to adapt to the fluctuation of the function and the number of lines of the private automatic branch exchange. Only the required amount of memory chips need be mounted.

Furthermore, since it is possible to release the memory once allocated as the database area and reallocate the memory as another database area,
The data storage memory can be effectively used.

[Brief description of drawings]

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

FIG. 2 is a diagram showing a relationship between a memory pool management table and a data storage memory shown in FIG.

FIG. 3 is a diagram showing a relationship between a free memory management table and a data storage memory shown in FIG.

FIG. 4 is a diagram showing a configuration of software in a program memory shown in FIG.

FIG. 5 is a block diagram showing a configuration of a central control unit of a conventional private automatic branch exchange.

FIG. 6 is a diagram showing a configuration of soatware in the program memory of FIG.

[Explanation of symbols]

6 ... System data, 7 ... Main processor circuit, 8 ...
Input / output circuit, 9 ... Program memory, 10 ... Data storage memory, 11 ... Database management table memory, 12 ... Memory pool management table, 13 ... Free memory management table, 14 ... Memory start address storage unit,
15 ... Memory capacity storage section, 16 ... Unused area address storage section, 17 ... Unused area capacity storage section, 18 ... Memory area,
18A ... Used area, 18B ... Unused area, 18C ...
Free area, 19 ... Application program section, 20 ... Database, 21 ... Database management section, 22 ... Memory pool management section, 23 ... Free memory management section, 24 ... Unused database area, 25 ... Free memory group, 26 ... Relation table , 27… Database access request.

Claims (1)

[Claims] 1. A central control unit has a dedicated database management table memory for writing or reading a data storage memory for storing system data of a private automatic branch exchange as a database, and the database management table memory is provided with the database management table memory. , A memory pool management table for managing the start address and memory capacity of an unused database area in the data storage memory, and the start address and memory capacity of the database area of the system data released and unnecessary in the data storage memory And a means for rewriting the memory pool management table and a free memory management table for securing a necessary amount of data storage area when a system data database is constructed. And deleting system data An automatic private branch exchange, comprising means for releasing the free memory management table in the database area which is no longer needed due to the reduction.