JP3496624B2 - Channel management device and channel management method - Google Patents

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a channel management device and a channel management method for managing a physical channel of a device for remote access service, and particularly to translate a logical channel from a telephone exchange into a physical channel of the device for remote access service. The present invention relates to a channel management device and a channel management method.

[0002]

2. Description of the Related Art Conventionally, a telephone exchange for terminating a remote access service device for dial-up PPP termination outside a station owned by a telephone subscriber has a physical interface corresponding to a telephone number, like an ordinary incoming call. Channel management is performed by having physical interface information consisting of a number and a channel number as call processing information.

[0003]

However, due to rapid technological innovation, devices for remote access services have become
Compared with the subscriber interface device of the telephone exchange, the software version has been upgraded and the number of accommodated channels has been increased, and in the conventional control method in which the telephone exchange has physical interface information as call processing information, remote access is not possible. If the number of channels accommodated by the service device is changed, the call processing unit of the telephone exchange needs to be changed as another physical interface information.

The present invention has been made in view of the above problems, and an object thereof is to perform call processing of a telephone exchange even when the number of mounted remote access service devices and the number of accommodated channels are changed. A point is to provide a channel management device and a channel management method that do not require changing parts.

[0005]

The present invention has the following constitution in order to solve the above problems. A gist of the invention according to claim 1 is a channel management device for translating logical channel information from a telephone exchange into a physical channel of the device for remote access service in a gateway device in which a plurality of devices for remote access service are mounted. ,
A routing translation database in which the logical channel information and the remote access service device are associated with each other, and a routing translation means for performing a routing translation for identifying the remote access service device from the logical channel information based on the routing translation database. A channel translation database that associates the physical channel with the logical channel information from the telephone exchange, and a channel translation means that performs channel translation that identifies the physical channel from the logical channel information based on the channel translation database. The present invention resides in a channel management device including: The gist of the invention according to claim 2 resides in the channel management device according to claim 1, further comprising a routing translation database creating means for creating the routing translation database when the gateway device is initialized. The invention according to claim 3 is characterized in that it further comprises a channel translation database creating means for creating the channel translation database when the remote access service device is initialized. It exists in the management device. Further, the gist of the invention according to claim 4 is that the routing translation database creating means creates the routing translation database based on the number of the physical channels accommodated in the remote access service device. The channel management device according to any one of 1 to 3 above. A fifth aspect of the present invention is a channel management method for translating logical channel information from a telephone exchange into a physical channel of the remote access service device in a gateway device in which a plurality of remote access service devices are mounted. hand,
Performing a routing translation that identifies the remote access service device from the logical channel information based on a routing translation database that associates the logical channel information with the remote access service device,
A channel management method is characterized in that channel translation for identifying the physical channel from the logical channel information is performed based on a channel translation database in which the logical channel information from the telephone exchange and the physical channel are associated with each other. A sixth aspect of the present invention resides in the channel management method according to the fifth aspect, wherein the routing translation database is created when the gateway device is initialized. The gist of the invention according to claim 7 resides in the channel management method according to claim 5 or 6, characterized in that the channel translation database is created when the device for remote access service is initialized. Further, the gist of the invention according to claim 8 is that the routing translation database is created based on the number of accommodated physical channels of the remote access service device. It lies in the channel management method.

[0006]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiments of the present invention will be described in detail below with reference to the drawings.

FIG. 1 is a block diagram showing the configuration of an embodiment of a channel management apparatus according to the present invention.

This embodiment comprises a telephone exchange 1 and a gateway device (hereinafter referred to as GW) 3, the telephone exchange 1 and the GW 3 are connected by a highway A2, and the highway A2 is connected to the telephone exchange 1. It accommodates a time division channel with the GW 3 and a call control signal channel.

The telephone exchange 1 has a GW channel management function unit 11 and uses a logical channel group (hereinafter referred to as LCG) which is a set of a plurality of logical channels to perform GW3.
Channel management.

The GW channel management function unit 11 has a logical channel group number (hereinafter referred to as LCGN) and an LC.
It manages the logical channel information configured by the GN channel number, and the logical channel information is stored in the telephone exchange 1 and the GW 3.
The channel management for the GW 3 by the telephone exchange 1 is used as a call control signal between the
That is, it is performed by a set of LCGN and a channel number in LCGN.

The GW 3 is a time division channel multiplexing function unit 41.
, GWC translation information processing unit 42, and RAS type management unit 4
And a gateway control device (hereinafter, G
WC) 4 and remote access service devices (hereinafter referred to as RAS) 5-9, and GWC 4 and R
The ASs 5 to 9 are connected to the highways B31 to 35, respectively, and the highways B31 to 35 are connected to the GWC4 and the RAS.
It accommodates time-division channels 5 to 9 and call control signal channels. Note that the number of time-division channels of highway A2 and highway B31 to 35 is G, respectively.
Sufficiently secured for W3 and RAS5-9.

The time division channel multiplexing function unit 41 has a function of distributing time division channels from the highway A2 to the highways B31 to 35 and a function of multiplexing time division channels from the highways B31 to 35 to the highway A2, and has the same function in the GW3. The number of channels that the RASs 5 to 9 can accommodate can be determined to multiplex the time division channels.

The GWC translation information processing unit 42 uses the logical channel information and RAS number (hereinafter referred to as RAS) possessed by the telephone exchange 1.
A database (hereinafter referred to as G) showing a correspondence relationship with N).
A GWC translation DB that creates a WC translation DB) is autonomously updated, and a routing translation based on the created GWC translation DB is performed. The GWC translation DB is for guaranteeing the arrival possibility of a call control signal that is communicated between the telephone exchange 1 and the RASs 5-9 to receive a dial-up PPP call at the RASs 5-9. Is from the LCGN managed by the telephone exchange 1 to the RAS 5 to 9
Is a correspondence table for obtaining RASN indicating the physical position information of the GWC4, and is created when the GWC4 is initialized.

The RAS type management unit 43 holds information on the number of accommodated channels of the RASs 5 to 9 mounted in the GW 3 (hereinafter referred to as management RAS type information). In addition, G
The RASs 5 to 9 installed in the W3 all have the same number of accommodated channels in order to sequentially manage the LCGN, and the GW
If any of the RASs 5 to 9 in 3 is replaced with one having a different number of accommodated channels, a failure occurs.

The RASs 5 to 9 are devices for terminating the dial-up PPP, have RAS translation information processing units 51 to 91 and RAS type information units 52 to 92 in addition to the dial-up PPP terminating function, and the telephone exchange 1 Performs the requested processing by translating the logical channel information (LCGN, LCGN internal channel number) included in the call connection request and the like into the physical channel.

The RAS translation information processing units 51 to 91 store a database (hereinafter referred to as RAS translation DB) showing a correspondence relationship between the logical channel information held in the telephone exchange 1 and the physical channel group number (hereinafter referred to as PCGN). Autonomous updating of the created RAS translation DB is performed, and channel translation from LCGN to a physical channel is performed based on the created RAS translation DB. The RAS translation DB is a correspondence table for obtaining a PCGN indicating a physical channel group in the RAS 5-9 from the LCGN managed by the telephone exchange 1, and a leading LC from the GWC 4 when the RAS 5-9 is initialized.
It is updated autonomously upon receiving the notification of GN.

The RAS type information sections 52 to 92 are RAS 5
Information on the number of channels that can be accommodated in each of 9 to 9 (hereinafter, referred to as RAS type information) is held.

Next, the operation of the embodiment will be described in detail with reference to FIGS. 2 is a diagram showing an example of GWC translation DB of the GWC translation information processing unit shown in FIG. 1 and an example of RAS translation DB of RAS translation information processing unit, and FIG. 3 is a GWC translation information processing unit shown in FIG. GWC translation D
FIG. 4 is a flowchart for explaining the autonomous update processing of B, and FIG. 4 is a GWC translation information processing unit and RAS shown in FIG.
FIG. 6 is a sequence diagram for explaining an autonomous update process of the RAS translation DB performed with the translation information processing unit, and FIG.
FIG. 6 is a sequence diagram for explaining an example of call connection from a telephone exchange in the embodiment of the channel management device according to the present invention.

In the following, the number of channels per LCG is 32, and the number of channels accommodated in each of the RASs 5-9 is 96.
And the case where the number of LCGs per GW3 is 15 will be described.

First, a procedure for creating the GWC translation DB shown in FIG. 2A by the autonomous update process of the GWC translation DB will be described in detail with reference to FIG. The autonomous update process of the GWC translation DB is performed by the GWC translation information processing unit 42 during the initialization of the GWC4, and the GWC translation information processing unit 42 executes the R
The AS type management unit 43 is inquired about the management RAS type information (step 301), and the RAS type management unit 43
In this embodiment, since the number of channels accommodated in each RAS 5 to 9 is 96, the GWC translation information processing unit 42 replies that the management RAS type information is 96 ch.

Next, the GWC translation information processing unit 42 calculates the accommodated LCG number m for each RAS 5-9 by dividing the management RAS type information by the number of accommodated channels per 1 LCG. In the present embodiment, Since the number of accommodated channels per LCG is 32, the number of accommodated LCGs m = 3 is calculated (step 302).

Next, the GWC translation information processing unit 42
The number of accommodated LCGs m = 3 is sequentially allocated to AS5-9, and LCGN0 is assigned to RAS5.
2, RAS6 has LCGN3-5, RAS7 has LCGN6-8, and RAS8 has LCGN9-1.
1 and LCGNs 12 to 14 are assigned to RAS 9 (step 303).

The GWC translation information processing section 42 performs step 3
The result of allocating LCGN to each RAS5-9 in 03 is G
The GWC translation DB shown in FIG. 2A is created by reflecting it in the WC translation DB (step 304). Note that FIG.
The RASNs 1 to 5 shown in (a) are RAS 5 to 9 respectively.
Is a number corresponding to.

Next, the procedure for creating the RAS translation DB shown in FIG. 2B by the autonomous updating process of the RAS translation DB will be described in detail with reference to FIG. First, RAS6
Indicates the completion of initialization and the RAS6 initialization completion notification notifying that the RAS type information is 96ch (step 40).
Notify 1) to GWC4. The GWC translation information processing unit 42 of the GWC4 notifies the RAS6 initialization completion (step 4
01), the head LCGN corresponding to RAS6 (RASN = 2) is searched in the GWC translation DB, the head LCGN = 3 is obtained as a search result (step 402), and the search result is requested to continue RAS6 initialization (step 403). ) As R
Send to AS6.

The RAS translation information processing unit 61 of RAS6
Since the number of LCGs that can be physically accommodated is 3, the received head LCGN = 3 is sequentially allocated to the PCGN in the RAS 6, that is, PCGN = 0 is set to LCGN = 3, and PGN is set to PGN = 3.
LCGN = 4 for CGN = 1 and LCGN for PCGN = 2
= 5 (step 404).

Next, the RAS translation information processing unit 6 of the RAS 6
1 reflects the allocated result in the RAS translation DB (step 405), completes the autonomous update process, and notifies the completion of the RAS6 initial channel state notification (step 4).
06) is notified to GWC4. The GWC4 receives the RAS6 initial channel state notification (step 406),
It can be recognized that the RAS 6 is ready to terminate the call control signal. The above-mentioned autonomous update processing of the RAS translation DB is performed by RAS5, RAS7, RAS8 and R.
By performing the AS9 as well, the R shown in FIG.
An AS translation DB is created.

Next, the GWC translation DB shown in FIG. 2 (a)
Then, an example of a call connection from the telephone exchange 1 when the RAS translation DB shown in FIG. 2B is created will be described in detail with reference to FIG. First, the telephone exchange 1 is operated by LCGN (LCG
N = 3) and channel number in LCGN (ch = 10)
A call connection request (step 501) including the above is transmitted to the GWC4. The GWC4 requests call connection (step 50).
1) is received, and the GWC translation information processing unit 42 refers to the GWC translation DB to request a call connection (step 50).
RASN the LCGN (LCGN = 3) included in 1)
Translate to (RASN = 2) RASN = 2 (RAS6)
To RAS6 (step 502)
Call connection request including LCGN (LCGN = 3) and LCGN internal channel number (ch = 10) (step 50
3) is transferred.

The RAS 6 makes a call connection request (step 50).
3) is received and the RAS translation information processing unit 61 refers to the RAS translation DB, so that the LC included in the call connection request is received.
GN (LCGN = 3) is translated into PCGN (PCGN = 0), a process of identifying the channel number in RAS is performed, and call connection of the corresponding channel is performed (step 504). R
When the AS 6 terminates the call connection to the corresponding channel, it
Call connection response including GN (LCGN = 3) and LCGN internal channel number (ch = 10) (step 505)
To GWC4, and GWC4 directly sends LCGN
(LCGN = 3) and LCGN channel number (ch
= 10) is transferred to the telephone exchange 1 as a call connection response (step 506).

As described above, according to the present embodiment, the translation databases of the GWC translation information processing unit and the RAS translation information processing unit are autonomously operated even when the number of installed RASes and the number of accommodated channels are changed. By updating, it becomes possible to respond to the processing request from the telephone exchange, so that the call processing unit of the telephone exchange, that is, the GW.
There is no need to change the channel management function unit, and the GW channel management function unit of the telephone exchange can be shared regardless of the subsequent GW development.

In the present embodiment, RAS5-9 are RAS.
Although each has translation information processing units 51 to 91, R
The AS translation information processing units 51 to 91 may be included in the GWC 4. In this case, in GWC4, the telephone exchange 1
Has a translation database composed of RASNs and physical channels in RAS corresponding to logical channel information that can be managed by RAS5-9.
When the GWC 4 receives the information about the change in the number of channels from the RASs 5 to 9 due to the change in the number of accommodated channels, the physical channels in the RASs 5 to 9 can be updated in the same manner as the above-mentioned update of RASN.

It should be noted that the present invention is not limited to the above-mentioned embodiments, and it is apparent that the respective embodiments can be modified appropriately within the scope of the technical idea of the present invention. Further, the number, position, shape, etc. of the above-mentioned constituent members are not limited to those in the above-mentioned embodiment, and the number, position, shape, etc. suitable for carrying out the present invention can be adopted. In addition, in each figure, the same components are denoted by the same reference numerals.

[0032]

The channel management apparatus and the channel management method of the present invention have the GWC translation information processing unit and RA even when the number of RAS implementations and the number of accommodated channels are changed.
Since it is possible to respond to a processing request from the telephone exchange by autonomously updating the translation database of the S translation information processing unit, the call processing unit of the telephone exchange, that is, the GW channel management function unit is changed. You do n’t have to
The GW channel management function unit of the telephone exchange is
The effect is that it can be standardized regardless of development.

[Brief description of drawings]

FIG. 1 is a block diagram showing a configuration of an embodiment of a channel management device according to the present invention.

FIG. 2 is a diagram showing an example of a GWC translation DB of a GWC translation information processing unit shown in FIG. 1 and an example of a RAS translation DB of an RAS translation information processing unit.

[Fig. 3] G performed by the GWC translation information processing unit shown in Fig. 1.
It is a flowchart for demonstrating the autonomous update process of WC translation DB.

FIG. 4 is a sequence diagram for explaining an autonomous update process of the RAS translation DB performed between the GWC translation information processing unit and the RAS translation information processing unit shown in FIG.

FIG. 5 is a sequence diagram for explaining an example of call connection from the telephone exchange in the embodiment of the channel management device according to the present invention.

[Explanation of symbols]

1 telephone exchange 2 Highway A 11 GW channel management function section 3 Gateway device (GW) 31-35 Highway B 4 Gateway control device (GWC) 41 Time Division Channel Multiplexing Function Unit 42 GWC Translation Information Processing Department 43 RAS type management unit 5-9 Remote Access Service Equipment (RAS) 51-91 RAS translation information processing unit 52-92 RAS type information section

Claims (8)

(57) [Claims] 1. A channel management device for translating logical channel information from a telephone exchange into a physical channel of the remote access service device in a gateway device in which a plurality of remote access service devices are mounted, wherein the logical channel information is used. And a routing translation database in which the remote access service device is associated with each other, a routing translation means for performing a routing translation for identifying the remote access service device from the logical channel information based on the routing translation database, and the telephone exchange. And a channel translation database in which the physical channel is associated with the logical channel information, and channel translation is performed to identify the physical channel from the logical channel information based on the channel translation database. Channel management apparatus characterized by comprising a Yaneru translation means. 2. The channel management device according to claim 1, further comprising a routing translation database creating means for creating the routing translation database when the gateway device is initialized. 3. The channel management device according to claim 1, further comprising a channel translation database creating means for creating the channel translation database when initializing the device for remote access service. 4. The routing translation database creating means creates the routing translation database based on the number of the physical channels accommodated in the remote access service device. The described channel management device. 5. A channel management method for translating logical channel information from a telephone exchange into a physical channel of the remote access service device in a gateway device in which a plurality of remote access service devices are mounted, wherein the logical channel information is used. And the remote access service device are associated with each other based on a routing translation database to perform routing translation for specifying the remote access service device from the logical channel information, and the logical channel information and the physical channel from the telephone exchange. A channel management method characterized by performing channel translation for specifying the physical channel from the logical channel information based on a channel translation database in which 6. The channel management method according to claim 5, wherein the routing translation database is created when the gateway device is initialized. 7. The channel management method according to claim 5, wherein the channel translation database is created when the device for remote access service is initialized. 8. The routing translation database is created based on the number of the physical channels accommodated in the remote access service device.
8. The channel management method according to any one of 7 to 7.