JPH02105697A - Speech path managing system - Google Patents

Abstract

PURPOSE:To decrease the number of times of communication and to execute the management of path information of a network by constituting the titile system so that the necessity for executing a communication processing of a call processing processor and a main processor is eliminated, whenever a speech path is caught and released. CONSTITUTION:A speech path map managing area 20 constituted of a map managing part 13 incorporating an idle channel counter 13a and a map release request buffer 14 is mounted to every call processing processor 11. In the case of sending and receiving information between the call processing processor 11 and a main processor 12, when a speech path is released, the call processing processor 11 saves its releasing path information in a path area, and catches a path being under the control of the call processing processor in this path area. Also, the call processing processor 11 executes an idle display of the path in a path area of the speech path, when the path is released, an also, updates the counter 13a in advance, and catches an idle path from the speech path area, when the speech is caught and when the counter 13a exceeds a prescribed number. When the counter 13a exceeds the prescribed number, release path information is written directly in the map release request buffer.

Description

[Detailed Description of the Invention] [Summary] This invention relates to a call route management method that manages network path information between a plurality of call processing processors and a main processor, and aims to manage network path hunting at high speed. When information is exchanged between a plurality of call processing processors that control a path system and a main processor that controls the plurality of call processing processors, an empty channel counter that manages empty call paths and own call processing. A call path area that enables path capture and release processing within the processor and a path release request buffer that stores information for notifying the release request to the main processor are provided for each call processing processor. When a call path is released, information on the released bus is stored in the path area, and the path under the control of the call processing processor is captured in the path area.

[Industrial Application Field] The present invention relates to a call path management system for managing network path information between a plurality of call processing processors and a main processor.

Conventional bus information blockage management on a communication path involves communication processing between a call processing processor and a main processor.1. It takes a lot of processing steps. Therefore, there is a need for a communication path management system that reduces such communication processing and improves the processing capacity of the call processing processor.

[Conventional technology] FIG. 9 is a configuration diagram showing an example of an exchange system.

A plurality of call processing processors (CPRi, only one is shown in the figure) performs distributed control over the exchange network (call path) 103, and a main processor (MPR) manages data such as call connections controlled by the call processing processors. ), and an adapter for inter-processor communication (CCA) is connected between each processor.
)104.203, data is exchanged.

The call processing processor CPRi includes a control device (CC) 101,
It is composed of a memory (MM) 102, etc., and a main processor M
PR is a control device (CC) 201 and a memory (MM) 202
Consists of etc.

Therefore, the control of the communication path 103 in the call processing processor will be explained with reference to FIG.

In FIG. 10, a control device 101 controls a communication channel control memory (CM) 1 by program control in a memory 102.
By writing the address of the speech path memory (SPM) 103a to a predetermined address of the input highway 30b, the time slots (STj) on the input highway are written.

5Ti), an exchange connection is established.

This configuration is an example of call path control in one call processing processor, but in distributed control, multiple call paths (SPC#i) are each controlled by a plurality of call processing processors, and connections between the call paths are controlled. Control is also in place. Such a configuration is shown in FIG.

Figure 11 shows multiple communication paths (SPC#0 to spC#n)
It describes the exchange connections between. Although FIG. 10 shows an example of connections within the same communication path, FIG. 11 shows an example in which time slots are swapped between different communication paths.

Therefore, conventional communication path control is performed by providing communication path map information to the main processor to connect the communication paths shown in FIGS. 10 and 11. That is, the call path capturing process is performed by matching the call paths 103 to be captured on a map. To this end, as shown in FIG. 12, each call processing processor 1 has a path acquisition/release processing section 1a, and the main processor 2 has a path acquisition/release processing unit 1a for each call processing processor (CPRi, CPRj). It has a map area (MAP# and MAP#l), and processing is performed through communication exchange between each call processing processor and the main processor.

When releasing a map, it is necessary to make the corresponding path position of the map area in the main processor vacant, but this is done by communication from the call processing processor to the main processor during call release processing.

More specifically, this will be explained with reference to FIG.

FIG. 13 is an explanatory diagram of conventional communication path control.

First, map hunt request processing will be explained ((a)
reference). As shown in the figure, the communication path management system is composed of a plurality of call processing processors (CPR) 1 that control the communication path system, and a main processor (MPR) 2 that controls these plurality of call processing processors 1. Ru. In the figure, only two call processing processors CPRI and CPR2 are shown as call processing processors 1, but the number is not limited to two.

Now, if a call is made from the subscriber terminal 3, the corresponding CPRI detects the call and requests a map hunt to the MPR. When a notification of successful map hunt is returned from the MPR, the CPRI connects the communication path between the PB receiver 4 and the subscriber using the vacant path designated by the MPR. The above sequence is performed by the call processing program.

Next, map release processing will be explained (see (b)).

It is now assumed that a map release request has been issued from the CPRI. CPR is the communication route map management area 5 as shown in the figure.
and a buffer 5a for bus release request to MPR.
is built-in.

This path H release request buffer 5a is provided for each number of CPRs. Furthermore, this path release request buffer 5a
is composed of speech path management memories MAP equal in number to the number of speech path control devices SPC, and here, #0 to #15.
It consists of 16 SPCs.

When a map release request is issued from the CPRI to the channel map management area 5, a channel time slot in the corresponding SPC is searched for and "1" is set.

This indicates that the speech path for which "1" has been set has been released.The contents of this bus release request buffer 5a are sent to the MPR at a cycle of, for example, 1 second, and in the MPR, the speech path for each CPR is This means that they are constantly aware of the air blockage situation.

[Problems to be Solved by the Invention] As described above, according to the conventional system, the path information (blockage) of the communication path is managed in a centralized manner by the main processor. Therefore, communication processing between the call processing processor and the main processor is required every time a call path connection process is performed, resulting in a problem that a large number of processing steps are required and the processing time becomes long.

The present invention has been made in view of these problems, and an object of the present invention is to provide a call path management system that can perform network path hunting at high speed.

[Means for Solving the Problems] FIG. 1 is a block diagram of the principle of the present invention. In the figure,
11 is a plurality of call processing processors (
CPR), 12 are these plural call processing processors 11
The main processor (MPR) 15 that controls the processors is a path that connects these processors. Reference numeral 13 denotes a map management section that includes an empty channel counter 13a for managing empty or blocked speech paths; 14 a map release request buffer that stores information for notifying a map release request to the main processor 12; and 20 a map management section 13. and a map release request buffer 14.

Although the channel map management area 20 is shown for only one call processing processor (CPR) 11, it is implemented for each call processing processor 11.

In such a configuration, a plurality of call processing processors 11 that control a communication path system, and a plurality of call processing processors 1
1, when the call processing processor 11 releases the call path, the call processing processor 11 stores the released bus information in the path area, and the call processing processor 11 stores the released bus information in the path area. A pass is captured in the pass area.

Further, when a path is released, the call processing processor 11 displays an empty path in the path area of the call path, and updates the empty channel counter 13a, and when the call path is captured, the empty channel counter (13a) indicates a predetermined number. In the above case, an empty path is captured from the call path area.

When the counter 13a is above a predetermined value, release path information is directly written into the map release request buffer. Further, the communication path area vacancy information is periodically transferred to the bus release request buffer 14, and the call path area and the counter 13a are initialized.

[In the action map management section 13, speech bus idle/busy information for each communication path control device under the call processing processor is written.

For example, it is set to "1" when the bus is empty, and set to "0" when the bus is occupied. [Empty channel counter], 3a is updated when each call processing processor 11 issues a map release request to its own map management unit 13, and the corresponding empty channel counter 13a is updated at the same time as writing the empty/busy information. . At the time of a map hunt request, if the call path is between the call path control devices 820 under its own call processing processor CPR, each call processing processor 11 manages the call path map without performing communication processing with the main processor 12. The user accesses the area 20, scans the map management unit 13 to investigate whether the buses in his own area are occupied, finds a vacant bus, and connects the bus.

On the other hand, the contents of the channel map management area 20 held by the call processing processor 11 are as follows:
Since the call route map management area of the main processor 12 is always sent to the call path map management area held by the main processor 12 at regular intervals, the main processor 12 can grasp the busy state of the bus of each call processing processor 11. According to the present invention, when the call processing processor 1 accesses the call route map management area 20, the bus occupancy status is known, so a bus capture request to the main processor 12 is required for call route management. (2. If the communication path you want to capture is between communication path control devices under different call processing sensors, send a map capture request to the main processor MPR using the conventional procedure. I do).

[Example] Hereinafter, an example of the present invention will be described in detail with reference to the drawings.

FIG. 2 is a configuration diagram of a communication route map according to the present invention, and corresponds to the configuration of the communication route map management area 20 explained in the principle diagram of FIG. The same reference numerals in the figures indicate the same objects. In the call path area 13b, each bit indicates one call bus, and when the free/blocked call bus is indicated by Ilo, the number of free channels is stored in the free channel counter 13a. This empty state of the call path area 13b is periodically transferred to the map release request buffer 14.

FIG. 3 is a configuration diagram of an embodiment of the present invention, showing the configuration of management of the call path area of FIG. 2. In the figure, 30
is a call processing unit that controls and processes calls including switching connections, and when the call processing unit 30 seizes and releases a call bus, a bus capture unit 50 and a bus release unit 40 are activated, respectively.

The path capture unit 50 and the bus release unit 40 each perform bus capture or bus release processing using the call path area 13b of the map management unit 13. The details will be described later in each control flow, and a periodic transfer processing section 60 is provided, and the periodic transfer processing section 60 periodically transfers the contents of the call path area 13b of the map management section 13 to the map release request buffer 14. do.

The bus information (empty information) written in the map release request buffer 14 is transferred to the main processor side by the periodic transfer processing section 60.

FIG. 4 shows a control flow of the bus release processing section of FIG. 3. In the figure, when there is a bus release request, it is determined whether the communication bus is between communication path control devices within the own call processing processor CPR (Sl). If the own call processing processor CPR is the call path to be managed, then the empty channel counter 13a
is equal to or greater than a predetermined value N0 (S2), and if it is less than a predetermined value, a vacant channel is set at a predetermined position in the call path area 13b (S3), and the vacant channel counter 1 is
3a is updated (S4).

In addition, in steps SL and S2, if the processor is not under its own processor or if the number of empty channels is greater than or equal to a predetermined value,
A free space is directly set in the transfer buffer 14 and immediately notified to the main processor side (N5). FIG. 5 shows the control flow of the path capture processing section in FIG. 3. In the figure, when acquiring a path, it is determined whether the call path is within the own call processing processor (S11), and if it is within the own call processing processor, then it is determined whether the free channel counter 13a is equal to or greater than a predetermined value N1. (S12). If it is equal to or greater than the predetermined value, channel matching processing is performed (813). When the predetermined path is captured (S14), the next free call path setting area corresponding to the captured call path is blocked (S15),
The empty channel counter 13a is subtracted (S16).

Further, the steps Sll, S12. If either determination is negative in S14, the main processor MPH is requested to acquire the path (S17).

FIG. 6 shows a control flow of the periodic transfer processing section in FIG. 3. In the figure, the transfer counter held during own call processing is updated to determine whether it is 0 (521), and if it is 0, it is determined that it is the cycle to transfer, and the information of the empty channel setting area is transferred to the transfer buffer 40. (S22). Next, all vacant channel setting areas are set to be based on the channel (523), and the vacant channel counter 13a is cleared to 0 (S24). Next, initialize the transfer counter (predetermined value)
525) and transfer the contents of the transfer buffer 14 to MPH.
(S26). If the transfer counter is not 0 in step S21, the transfer counter is subtracted (S
27).

The implementation of the above processing will be described below with reference to conceptual diagrams on the system shown in FIGS. 7 and 8.

In FIG. 7, map release processing will be explained ((
(See b)). When the call processing processor CPRI receives a communication path map release request, the communication path map management process first checks whether the release request is for a communication path between networks within its own CPR. If the result of the check is self-CPR.
If it is, it is determined whether the value of the empty channel counter 13a corresponding to the network (SPC) in the local CPR call map management section 13 is less than or equal to a predetermined boundary value NO. If it is NO or below, the management memory MAP#O corresponding to the network (SPC)
~ Store traffic route information in MAP#15 and update the empty channel counter 13a. If it is N0 or more,
Immediate call path information is sent to the main processor (hereinafter abbreviated as MPR) 12
The map is stored in the map release request buffer 14, and is entrusted to release processing by a task with a one-second cycle.

Next, when a call is made from the subscriber terminal 31, the corresponding CPRI issues a map hunt request to the channel map management process (see (a)). The call route map management process that receives the request first checks whether the hunt request is for a call route between networks within its own CPR. As a result of the check, if it is within the own CPR, the value of the empty channel counter 13a corresponding to each network is determined.

Then, if it is equal to or greater than the boundary value N1, channel hunting is performed based on the information in the management memories MAP#0 to MAP#15 in the own CPR intra-call map management section 13. That is, a vacant path is found and connected to the PB receiver 32.

Here, the boundary value NO is a threshold value for avoiding exclusive use of the call path within the network only within the own CPR, and N1 is the threshold value for avoiding unnecessary processing when the network is relatively quiet (call map management within the own CPR). This is a threshold value to avoid (the probability of being able to hunt an empty channel is small). In addition, the map release process releases all map management units 13 for calls within the own CPR in a fixed time unit (for example, 30 seconds) so that the long-term hold call path monitoring process is not regarded as invalid hold.

FIG. 8 is an explanatory diagram of another embodiment of the present invention.

In the example shown in the figure, the channel map management area that was previously managed by MPR is managed and controlled separately by CPR and MPR. First, map release processing will be explained (see (b)).

The channel map management process that receives a channel map release request from the CPRI checks whether the release request is for a channel between networks within its own CPR or a channel managed within its own CPR. . If so, the network (
SPC) compatible management memory MAP# O~MAP
Store all call path information in #15 and empty channel counter]
, 3 update a. If the request is not for a communication path between networks within its own CPR, the communication path information is stored in the map release request buffer 14 to the MPR, and is entrusted to map release processing by a 1-second cycle task.

Next, we will explain the map hunt request processing ((b)
reference). The channel map management process that receives a map hunt request from the CPRI checks whether the hunt request is for a channel between networks within its own CPR. If there is an empty channel, the value of the empty channel counter 1'3a corresponding to the net node is determined, and if there is an empty channel, the own CP i
Channel hunting is performed based on the information in the map management section 13 within <.

If there is no empty channel or if there is a communication path between networks within the own CPR, MP
[Effects of the Invention] As described in detail below, according to the present invention, each time a call bus is captured and resolved, the processing block 11' is executed.
Since there is no need to perform communication processing between the node and the main processor, the number of communications (reduction in processing steps)) is reduced.
It becomes possible to perform the process at high speed.

[Brief explanation of the drawing]

Fig. 1 is a diagram of the principle of the present invention, Fig. 2 is a communication path map (1 to 1 composition diagrams) according to the present invention, and Fig. 3 is an embodiment of the present invention (1, i composition 4, Figure 4 is
FIG. 5 is a control flow diagram of the bus release processing section of the present invention; FIG. 5 is a control flow diagram of the bus capture processing section of the present invention; FIG. 7 and 8 are explanatory diagrams for explaining the present invention in detail. FIG. 9 is an illustration of the background of the present invention and/or a configuration example of a system according to the present invention. FIG. 10 is an explanation of the call path control of the call processing processor. Figure 11 is an example diagram of the communication path -(M); Figure 12 is a conceptual explanatory diagram of conventional communication bus acquisition/release control; and Figure 13 is an explanatory diagram of conventional communication path control. In the figure, 11 is a call processing block, 12 is a main processor, 13 is a map management section, 14 is a map release request buffer, 15 is a bus, and 20 is a channel map management area.

Claims (2)

[Claims] (1) Multiple call processing processors (
11) and the main processor (12) that controls the plurality of call processing processors (11), an empty channel counter (13a) that manages empty call paths.
), a call path area (13b) that enables path acquisition and release processing within the own call processing processor, and a path release request buffer (14) that stores information for notifying the release request to the main processor (12). is provided for each call processing processor (11), and in the call processing processor (11), when the call path is released,
A communication path management system characterized in that information on the path to be released is stored in the path area, and a path under the control of the call processing processor is acquired in the path area. (2) The call processing processor (11) displays an empty path in the path area of the call path when the path is released, and updates the empty channel counter (13a), and when the call path is acquired, the call processor (11) displays the empty channel counter (13a). When the counter (13a) is greater than a predetermined number, an empty path is captured from the call path area, and when the counter (13a) is greater than a predetermined value, release path information is written in the direct map release request buffer, and periodically the call path is The empty information of the area (13b) is transferred to the path release request buffer (14), and the communication path area (13b) and the counter (13a) are transferred.
2. The communication path management system according to claim 1, wherein: initial setting is performed.