KR100369798B1 - METHOD FOR CONTROLLING BANDWIDTH IN VoIP SYSTEM - Google Patents

Abstract

The present invention provides a voice over internet protocol service having gateways for real-time two-way communication between the endpoint terminals having the ability to communicate at least two of the voice, video and data including the voice. In the bandwidth management method in a network, each of the gateways receiving a call setup request from the endpoint terminal calculates the total bandwidth used considering the number of calls currently being processed and the bandwidth used according to the usage codec of each of the calls. And transmitting the calculated total used bandwidth to other gateways of the voice over internet protocol service network.

Description

Bandwidth Management in Voice-Over Internet Protocol System {METHOD FOR CONTROLLING BANDWIDTH IN VoIP SYSTEM}

The present invention relates to a Voice over Internet Protocol (hereinafter referred to as "VoIP") system, and more particularly to a method for controlling bandwidth.

Voice over Internet Protocol (VoIP) is a new type of communication service that makes voice calls through the Internet network, rather than making voice calls through PSTN (Public Switch Telephone Network). Unlike the conventional method, the call method using the internet network uses a packet-based network, so that voice calls can be made more cheaply without paying a domestic / international telephone line fee. VoIP can transmit not only audio but also video information using the H.323 protocol, which is an International Telecommunications Union-Telecommunications standardization sector (ITU-T) standard.

VoIP service network using the Internet as a back-bone is configured as shown in FIG. Referring to FIG. 1, the VoIP service network includes the Internet 8 used as a backbone, and gateways 6 and 10 and PCs 16 and 18 are connected to the Internet 8. Each of the gateways 6 and 10 is connected to the PSTNs 4 and 12, which are connected to the telephone terminals 2 and 14, the fax terminals 3 and 13, and the like. Terminals such as telephone terminals (2, 14), fax terminals (3, 13), and PCs (16, 18), etc., have voice (required), video (select), and data (select) when performing 1: 1 communication or conference. An endpoint that has the ability to communicate with other nodes. Each of these terminals may perform real-time bidirectional communication with the gateways 6 and 10 and other terminals. The gateways 6 and 10 are terminals connected to the Internet 8, i.e., packet based networks such as PCs 16 and 18, PSDNs 4 and 12, or terminals connected to ISDN (Integrated Services Digital Network). Terminal (2,14), fax terminal (3,13) is a component that allows real-time two-way communication through the Internet (8).

There may or may not be a gatekeeper in such a VoIP service network. The gatekeeper is located between the Internet 8 and the gateways 6 and 10 and performs a function of converting an alias (alias: phone number, name) into an IP (Internet Protocol) address so as to make a call between terminals. Specific features of gatekeepers include call control, network bandwidth control, zone management, call detail record storage, alive inspection, and alternate gates. There are alternate gatekeeper functions, logging functions, and statistics functions.

In a VoIP service network with a gatekeeper, bandwidth management is performed by a gatekeeper. A method of calculating bandwidth is generally performed by calculating the number of internet calls pending at a gateway. For example, if the occupied bandwidth per call is set to 10 kbps (kilo bit per second), and 200 calls are in progress, the current used bandwidth is calculated to be 2 Mbps (mega bit per second). For T.38 fax call services, the gatekeeper does not know whether an ongoing call is a fax call and therefore handles the fax call in the same way as a voice call to calculate the bandwidth used. In fact, the fax call service requires about 20 kbps to 30 kbps of occupied bandwidth per fax call. If the fax call is treated like a voice call and the bandwidth used is calculated, the actual total bandwidth cannot be known.

And in VoIP service network without gatekeeper, gateway and endpoint cannot know current processing traffic of remote gateway and cannot use bandwidth calculation. As a result, efficient VoIP call routing was not possible in a VoIP service network without a gatekeeper.

Accordingly, an object of the present invention is to provide a method for controlling bandwidth for efficient call routing in a VoIP service network without a gatekeeper.

Another object of the present invention is to provide a method for calculating a network total bandwidth in consideration of Internet fax call processing and Internet voice call in a VoIP service network without a gatekeeper.

It is still another object of the present invention to provide a method for transmitting traffic throughput of a local gateway to a remote gateway.

It is still another object of the present invention to provide a method of transmitting a total usage amount of inter-node traffic to a remote gateway by calculating a total usage bandwidth between nodes by a local bandwidth control gateway receiving the usage bandwidth and destination node information of the local gateway.

It is still another object of the present invention to provide a method in which a local gateway performs an efficient routing according to traffic throughput of a remote gateway in a VoIP service network without a gatekeeper.

Another object of the present invention is to provide a method for controlling bandwidth for efficient call routing in a VoIP service network having a gatekeeper.

In accordance with the above object, the present invention provides a gateway for enabling real-time two-way communication through the Internet between the endpoint terminals having the ability to communicate at least two of the voice, video and data including the voice; A bandwidth management method in a voice over internet protocol service network, comprising: considering the number of calls currently being processed by each of the gateways receiving the call setup request from the endpoint terminal and the bandwidth used according to the use codec of each of the calls Calculating a total used bandwidth, and transmitting the calculated total used bandwidth to other gateways of the voice over internet protocol service network.

1 is a block diagram of a typical VoIP service network;

2 is an example of the format configuration of the VoIP packet,

3 is a signal flow diagram for concrete configuration and bandwidth management of the gateways 6 and 10 according to an embodiment of the present invention;

4 is an operation control flowchart of the gateway module GW (N) of the local node 30 according to an embodiment of the present invention;

5 is an operation control flowchart of the total bandwidth control gateway module GW (A) of the local node 30 according to an embodiment of the present invention;

6 is an operation control flowchart of the gateway module GW (n) of the remote node 40 according to an embodiment of the present invention;

7 is an operation control flowchart of the total bandwidth control gateway module GW 1 of the remote node 40 according to an embodiment of the present invention.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the same elements in the figures are represented by the same numerals wherever possible. In addition, detailed descriptions of well-known functions and configurations that may unnecessarily obscure the subject matter of the present invention will be omitted.

In describing an embodiment of the present invention, an example configuration of the VoIP service network of FIG. 1 will be referred to as an example.

Existing VoIP service had to have gatekeeper to know bandwidth of each gateway. That is, the bandwidth management function of the gatekeeper provided efficient VoIP call routing. In this case, the bandwidth is calculated based on the Internet voice call currently in progress, and may be different according to the bandwidth that may be different for each Internet call, that is, the voice codec used for each call (hereinafter referred to as a "VoIP codec"). It does not take bandwidth (5.3kbps, 6.3kbps, 8kbps, 9.6kbps, 64kbps) into consideration. As a result, efficient VoIP call routing was not possible in a VoIP service network without a gatekeeper.

In the embodiment of the present invention, each of the gateways 6 and 10 of FIG. 1 directly calculates a bandwidth used in consideration of VoIP voice call processing and FoIP fax call processing in a VoIP service network without a gatekeeper.

First, the gateways 6 and 10 calculate the bandwidth used in consideration of VoIP voice call processing.

According to an embodiment of the present invention, each of the gateways 6 and 10 calculates the actual bandwidth used considering the number of calls currently being processed and the bandwidth according to the VoIP VoIP codec of each call. Since PCM voice data of a general telephone line has a bandwidth of 64 kbps, VoIP codecs for voice compression are provided in each of the gateways 6 and 10. Common voice compression formats of voice codecs include G.723.1, G.729A, and G.711. The G.723.1 voice codec can compress PCM voice data up to 6.4 kbps, and the G.729A voice codec can compress PCM voice data up to 8 kbps.

In order to calculate the actual bandwidth used for each VoIP codec available per call according to an embodiment of the present invention, the format of the VoIP packet will be described first. 2 is an example format diagram of a VoIP packet, and is composed of four types of headers 20 and a payload 22. The headers 20 have a total of 54 bytes, and the types thereof are as follows.

RTP (Realtime Transfer Protocol) header: 12 bytes

UDP (User Datagram Protocol) header: 8 bytes

IP (Internet Protocol) header: 20 bytes

Ethernet header: 14 bytes

In general, the bandwidths (5.3kbps, 6.3kbps, 8kbps, 9.6kbps, 64kbps) defined for the VoIP codec are considered only payloads. Therefore, the headers as well as the payloads should be considered. Only the actual bandwidth of VoIP codec can be known. Therefore, in the embodiment of the present invention, the actual bandwidth is calculated according to the VoIP VoIP code used for each call for transmitting the voice packet having the above format, and the calculation is as follows.

(1) When using a G.723.1 5.3kbps VoIP codec (compression of PCM voice data to 5.3kbps as a codec in G 723.1 voice compression format): a total of 74 bytes of 20 bytes of RTP payload and 54 bytes of the headers. Send a packet every 30ms. The actual bandwidth used at this time is 19.7kbps = (20bytes + 54bytes) * (1sec / 30ms) * 8bit.

(2) When using G.723.1 6.3kbps VoIP codec (compression of PCM voice data to 6.3kbps as codec in G 723.1 voice compression format): total 78 bytes of 24 bytes of RTP payload and 54 bytes of headers. Send a packet every 30ms. At this time, the actual bandwidth used is 20.8kbps = (24bytes + 54bytes) * (1sec / 30ms) * 8bit.

(3) When using the G.729A 8kbps VoIP codec (compression of PCM voice data to 8kbps as a codec of G 729A voice compression format): A total of 64 bytes of packet consisting of 10 bytes of RTP payload and 54 bytes of headers Send every 10ms. The actual bandwidth used at this time is 51.2kbps = (10bytes + 54bytes) * (1sec / 10ms) * 8bit.

(4) When using G.711A / u 64kbps VoIP codec (compression of PCM voice data to 64kbps as codec in G.711A / u voice compression format): total of 40 bytes of RTP payload and 54 bytes of headers A 94-byte packet is sent every 5ms. In this case, the actual bandwidth used is 150.4kbps = (40bytes + 54bytes) * (1sec / 10ms) * 8bit.

The calculation of the actual bandwidth used according to the VoIP VoIP codec of each call is as follows.

G.723.1 5.3kbps: 20 byte / 30ms (actual bandwidth 19.7kbps = (20 + 54) * 33.3 * 8)

G.723.1 6.3kbps: 24 byte / 30ms (actual bandwidth 20.8kbps = (24 + 54) * 33.3 * 8)

G.729A 8kbps: 10 byte / 10ms (actual bandwidth 51.2kbps = (10 + 54) * 100 * 8)

G.711A / u 64kbps: 40 byte / 5ms (actual bandwidth 150.4kbps = (40 + 54) * 200 * 8)

In addition, the embodiment of the present invention also considers the following matters in order to reduce the calculated actual use bandwidth in the VoIP codec.

Silence Suppression: Over 50% of calls are silent (usually 60%), reducing bandwidth by more than 50%.

-Multiframe transmission function: In order to reduce the overhead of various headers, it transmits in a multiframe.

As described above, each of the VoIP codecs is configured to process 50% of the calls as silence in consideration of silence suppression. Therefore, when considering silence in the embodiment of the present invention, the bandwidth of the VoIP codec used per call is 10kbps for G.723.1 5.3kbps, 11kbps for G.723.1 6.3kbps, 26kbps for G.729A, and 75kbps for G.711. Is calculated.

In addition, considering the multiframe transmission function of the RTP payload, the actual bandwidth used can be reduced. In case of G.723.1, up to 3 frames (90ms) can be bundled and transmitted in multiframe, and in case of G.729A, up to 9 frames (90ms) can be bundled and transmitted in multiframe. At least two (180ms) frames (ie multiframes) must be buffered for jitter buffering of H.323 endpoint terminals receiving voice packets, which is specified in the H.323 specification. This is caused by limiting the delay of the terminal itself to 180 ms. Accordingly, in the exemplary embodiment of the present invention, three and nine multiframes are bundled and transmitted. Although it is possible to send a larger number of multiframes as needed, it is desirable to send the multiframes properly as the above-described delay problem occurs. Thus, in the embodiment of the present invention, in the case of G.723.1, two to three frames are bundled and transmitted in a multiframe, and in the case of G.729A, up to nine frames are bundled and transmitted in a multiframe.

An example of calculating the bandwidth of an actual VoIP codec for a call in consideration of a multiframe transmission function and a silence cancellation function according to an embodiment of the present invention is as follows.

G.723.1 When three frames using a 5.3kbps VoIP codec are bundled and transmitted in multiframe: A total of 114 bytes of packets consisting of 60 bytes (20 bytes x 3) of RTP payload and 54 bytes of headers are received every 90 ms (30 ms x 3). send. The actual bandwidth used at this time is 10kbps ≒ (60bytes + 54bytes) * (1sec / 90ms) * 8bit. Using the silence suppression function, the bandwidth of G.723.1 5.3kbps VoIP codec is calculated as 5kbps.

According to an embodiment of the present invention, the actual bandwidth used for each VoIP codec, that is, the silence cancellation function and even the multi-frame transmission function, may be calculated based on Equation 1 as follows.

Actual bandwidth used per voice call [kbps] = (header size + (payload size x number of frames) x (1sec / codec sampling period x number of frames) x0.4 (when silence is enabled)

The actual use bandwidth (actual use bandwidth per voice call) value for each VoIP codec calculated based on Equation 1 is summarized as shown in Table 1 below.

Codec frame G.7111 G.723.1 5.3 kbps G.723.1 6.3 kbps G.729A SSE SSD SSE SSD SSE SSD SSE SSD One 60.5k 150.4k 7.9k 19.7k 8.3k 20.8k 20.5k 51.2k 2 42.9k 107.2k 5.0k 12.5k 5.4k 13.6k 11.8k 29.6k 3 37.1k 92.8k 4.0k 10.1k 4.9k 11.2k 9.0k 22.4k 4 34.2k 85.6k 3.6k 8.9k 4.4k 10.9k 7.5k 18.8k 5 32.5k 81.3k 3.3k 8.2k 3.7k 9.3k 6.6k 16.6k 6 31.4k 78.4k 3.1k 7.7k 3.5k 8.8k 6.1k 15.2k 7 30.5k 76.3k 5.6k 14.1k 8 30.0k 74.8k 5.4k 13.4k 9 29.4k 73.6k 5.1k 12.8k 10 29.0k 72.6k 4.9k 12.3k

In Table 1, SSE is an abbreviation of Silence Suppress Enable, and SSD is an abbreviation of Silence Suppress Disable. The bandwidth is in kbps.

Next, according to an embodiment of the present invention, the gateways 6 and 10 of FIG. 1 will be described to calculate the bandwidth used in consideration of FoIP fax call processing. In the case of FoIP fax, it cannot be processed by the mute function and the multi-frame transmission function, so there is no way to reduce the bandwidth.

Therefore, the actual bandwidth used according to the fax data transmission method, that is, the actual bandwidth used per fax call can be calculated based on Equation 2 below.

Actual bandwidth used per fax call [kbps] = (header size + (payload size) x (1sec / transmission cycle)

There are the following types of FoIP fax data transmission methods.

-V.27 2.4kbps: 12byte / 40ms (payload / transmission cycle)

V.27 4.8kbps: 24 bytes / 40ms

-V.29 7.2kbps: 36byte / 40ms

-V.29 9.6kbps: 48byte / 40ms

-V.33 12kbps: 60byte / 40ms

V.33 14.4kbps: 72bytes / 40ms

The actual bandwidth according to the data transmission method is calculated based on Equation 2 as shown in Table 2 below. In the calculation, the header size is assumed to be 54 bytes similar to the header size in the VoIP voice packet. That is, the header size 54 bytes is composed of 12 bytes of RTP header, 8 bytes of UDP header, 20 bytes of IP header, and 14 bytes of Ethernet header.

V.xx bandwidth V.27 2.4k V.27 4.8k V.29 7.2k V.29 9.6k V.33 12k V.33 14.4k FoIP bandwidth 13.2k 15.6k 18.2k 20.4k 22.8k 25.6k

As described above, each of the gateways 6 and 10 of FIG. 1 directly calculates the bandwidth used in consideration of VoIP voice call processing and FoIP fax call processing in the VoIP service network.

The gateways 6 and 10 then transmit and receive the usage bandwidth calculated by the method described above. In more detail, the gateway that calculates the bandwidth used transmits a message to the remote gateway through UDP (User Datagram Protocol) so that the remote gateway can determine whether an incoming call is available. It also checks the total bandwidth used by the local gateway to block the use of the local gateway when outgoing calls are exceeded or to handle calls with bypass routes.

The bandwidth management performed by each of the gateways 6 and 10 by using the use bandwidth calculated as described above will be described in more detail as follows.

In the VoIP service network, it should be understood that a plurality of gateways such as the gateways 6 and 10 of FIG. 1 are provided. In FIG. 1, two gateways 6 and 10 are provided for convenience of description according to an exemplary embodiment of the present invention.

3 illustrates a specific flow of the gateways 6 and 10 and a signal flow for bandwidth management according to an exemplary embodiment of the present invention. In FIG. 3, the gateway at the originating subscriber side of the gateways 6 and 10 in FIG. 1 is called the local node 30, and the gateway at the called subscriber side is referred to as the remote node 40. In FIG. Each of the local and remote nodes 30 and 40 is equipped with a plurality of gateway modules GW (A)-(N) and GW (1) -GW (n). Gateway modules GW (A)-(N), GW (1) -GW (n) support dozens of channels per module (e.g. 16 channels) and support both local and remote nodes (e.g. 30, 40 may be added. Among the plurality of gateway modules GW (A)-(N) and GW (1) -GW (n) provided in each of the local node and the remote node 30 and 40, the GW (A) and the GW (1) are shown in FIG. The total bandwidth control gateway module for controlling the total bandwidth of the node according to an embodiment of the present invention.

For example, if a voice call is made between the gateway module GW (N) of the local node 30 and the gateway module GW (n) of the remote node 40, a VoIP call is performed between the gateway modules GW (N) and GW (n) and is actually used. The codec to be determined is determined by VoIP signaling. Subsequently, the gateway module GW (N) of the local node 30 actually uses the gateway module GW (N) calculated by the method described in each of the gateway modules GW (1) -GW (n) of the remote node 40. Simultaneously transmitting the bandwidth, the actual bandwidth of the GW (N) is transmitted to the total bandwidth control gateway module GW (A) of the local node 30 (①). The gateway module GW (n) of the remote node 40 also transmits the actual bandwidth of the gateway module GW (n) to each of the gateway modules GW (A) -GW (N) of the local node 30, and at the same time, the remote node. The actual bandwidth of the GW (n) is transmitted to the total bandwidth control gateway module GW 1 of 40 (1 ').

Accordingly, each of the total bandwidth control gateway modules GW (A) and GW (1) receives the actual bandwidth used by GW (N) and the actual bandwidth used by GW (n). Calculate The total bandwidth control gateway module GW (A) of the local node 30 is the gateway modules GW (1) of the remote node 40 if the calculated total used bandwidth at the local node 30 has changed from the previous total used bandwidth. Send the total bandwidth used by the local node 30, calculated as GW (n), respectively. Of course, if the total bandwidth used by the total bandwidth control gateway module GW (1) of the remote node 40 is changed from the previous total bandwidth, each of the gateway modules GW (A) -GW (N) of the local node 30, respectively. The total bandwidth used by the remote node 40 is calculated. Accordingly, each gateway module GW (A) -GW (N) of the local node 30 knows the total bandwidth used by the remote node 40 and the bandwidth used by the remote node gateway modules GW (1) -GW (N). There is a number. Therefore, each gateway module GW (A) -GW (N) of the local node 30 refers to the total bandwidth used by the remote node 40 and the bandwidth used by the remote node gateway modules GW (1) -GW (N). This enables efficient routing. In summary, the total bandwidth control gateway GW (A) of the local node 30 uses the remote node information transmitted by the gateway module GW (N) and the bandwidth used by the gateway module GW (N). Add the corresponding usage bandwidth according to the trial and subtract the corresponding usage bandwidth according to the call release) and transmit all the gateways GW (1) -GW (n) of the remote node 40, The total bandwidth control gateway GW 1 also performs the same operation. In addition, each of the gateway modules of the local node 30 and the remote node 40 transmits the used bandwidth to the gateway modules of other nodes except its own node according to call set-up and call release. The total bandwidth used by the node belonging to another node and the bandwidth used by the remote gateway module are known. The above bandwidth information is used as a reference value in call setup.

Hereinafter, an operation according to an embodiment of the present invention will be described in detail. In the following operation description, it is assumed that at least one or more calls are transmitted from the gateway module GW (N) of the local node 30 to the gateway module GW (n) of the remote node 40 as in the example illustrated in FIG. 3. do.

First, the operation of the gateway module GW (N) of the local node 30 will be described with reference to FIGS. 3 and 4. The gateway module GW (N) of the local node 30 requests a call to the gateway module GW (n) of the remote gateway 40 using the digit input to the gateway module GW (N) in step 100 of FIG. Figure out. The total bandwidth used by the remote node 40 (previously updated) and the bandwidth used by the gateway module GW (n) of the remote node 40 are analyzed. Thereafter, in step 102, it is determined whether the total used bandwidth of the remote node 40 does not exceed the node limit bandwidth and whether the used bandwidth of the gateway module GW (n) of the remote node 40 does not exceed the gateway module limit bandwidth. Exceeding the limit bandwidth means that there is little bandwidth available between the local and remote nodes and between the gateway modules of both nodes. Therefore, if the threshold bandwidth is exceeded in the decision of step 102, the process proceeds to step 104 of FIG. 4 to perform a detour call process. However, if the threshold bandwidth is not exceeded in the determination of FIG. 102, the process proceeds to step 106 of FIG. 4.

In step 106, the gateway module GW (N) of the local node 30 processes the IP call setup and calculates the bandwidth actually used between the gateway module GW (N) and GW (n). In short, the actual bandwidth used between the gateway module GW (N) and GW (n) is calculated by examining packets transmitted by the signaling unit and the real time transfer protocol (RTP). The actual usage bandwidth calculation is to calculate the total usage bandwidth of all calls currently being made through GW (N), and the calculation method is as described above. Thereafter, the gateway module GW (N) transmits the calculated use bandwidth to each of the gateway modules GW (1) -GW (n) of the remote node 40 in step 108 of FIG. 4. At this time, the gateway module GW (N) of the local node 30 calculates the above calculations to each of the gateway modules GW (1) -GW (n) of the remote node 40 by referring to its own remote IP (Internet Protocol) table. The actual bandwidth used by the user datagram protocol (UDP). 1 and 3 illustrate only the remote node 40 in the VoIP service network. For example, if there are nodes A, B, C, and D in the VoIP service network, the gateway module of the local node 30 is shown. It should be understood that GW (N) also transmits the calculated actual use bandwidth to each of the gateway modules of nodes A, B, C, and D. In short, the gateway module GW (N) transmits the calculated actual use bandwidth to the gate modules of all nodes except the gateway module of its own node. This is to distribute traffic. In addition, the gateway module GW (N) of the local node 30 is connected to the IP address of the remote node 40 and the GW (N) of the total bandwidth control gateway module GW (A) of the local node 30 in step 108 of FIG. 4. Send the bandwidth used. Step 108 of FIG. 4 is a step corresponding to ① of FIG.

Thereafter, in step 110 of FIG. 4, it is determined whether the bandwidth is received from the remote node 40. In the remote node 40, the bandwidth used by the remote node gateway module GW (n) and the total bandwidth used by the remote node 40 as shown in ① 'and ②' of FIG. This is because it transmits to each of (A) -GW (N). In step 110 of FIG. 4, if the bandwidth is received from the remote node 40, the process proceeds to step 112 of FIG. 4 to update the bandwidth used by the remote node gateway module GW (n) and the total bandwidth used by the remote node 40. .

Thereafter, the local node gateway module GW (N) determines whether an IP call between the gateway module GW (N) of the local node 30 and the gateway module GW (n) of the remote node 40 has been released in step 114. If the IP call is released, go to step 116. The process of steps 116 to 122 of FIG. 4 is the same as the process of steps 108 to 112. That is, as the IP call is released, the total bandwidth used by the local node 30 and the remote node 40 is increased and decreased, and the bandwidth used by the local node gateway module GW (N) and the remote node gateway module GW (n) is updated.

Next, the operation of the total bandwidth control gateway module GW (A) of the local node 30 will be described with reference to FIGS. 3 and 5.

The total bandwidth control gateway module GW (A) of the local node 30 receives the IP address of the remote node and the actual bandwidth of the GW (N) from the local node gateway module GW (N) in step 200 of FIG. 5. Proceed to step 202 of FIG. In operation 202 of FIG. 5, the total bandwidth control gateway module GW (A) calculates the total bandwidth used by the local node 30 using the actual bandwidth used by the GW (N). Thereafter, the total bandwidth used by the local node 30 calculated in step 204 of FIG. 5 is transmitted to each of the gateway modules GW (1) -GW (n) of the remote node 40 by UDP. Step 204 of FIG. 5 corresponds to step ② of FIG. 3.

Thereafter, the local node total bandwidth control gateway module GW (A) proceeds to step 206 of FIG. 5 to determine whether the bandwidth is received from the remote node 40. In the remote node 40, the bandwidth used by the remote node gateway module GW (n) and the total bandwidth used by the remote node 40 as shown in ① 'and ②' of FIG. This is because it transmits to each of (A) -GW (N). If the bandwidth is received from the remote node 40 in step 206 of FIG. 5, the flow proceeds to step 208 of FIG. 5 to update the used bandwidth of the remote node gateway module GW (n) and the total used bandwidth of the remote node 40. .

Meanwhile, after the IP call between the gateway module GW (N) of the local node 30 and the gateway module GW (n) of the remote node 40 is released, the local node gateway module GW (N) re-uses the bandwidth used for the IP call release. Calculate and transmit to local node total bandwidth control gateway module GW (A). The local node total bandwidth control gateway module GW (A) determines whether an actual use bandwidth is received from the local node gateway module GW (N) in step 210 of FIG. 5. If so, proceed to step 212. Steps 212 to 214 are the same as steps 202 to 204 described above. That is, the total bandwidth used by the local node 30 is calculated and the calculated total bandwidth used is transmitted to each of the gateway modules of other nodes.

Thereafter, the local node total bandwidth control gateway module GW (A) determines whether the bandwidth is received from the remote node 40 in step 216 of FIG. 5. In the remote node 40, the bandwidth used by the remote node gateway module GW (n) and the total bandwidth used by the remote node 40 as shown in ① 'and ②' of FIG. This is because it transmits to each of (A) -GW (N). If the bandwidth is received from the remote node 40 in step 216 of FIG. 5, the flow proceeds to step 218 of FIG. 5 to update the bandwidth used by the remote node gateway module GW (n) and the total bandwidth used by the remote node 40. .

Next, the operation of the gateway module GW (n) of the remote node 40 will be described with reference to FIGS. 3 and 6. The gateway module GW (n) of the remote node 40 is the actual bandwidth used by the GW (n) after IP call setup between the local node gateway module GW (N) and the remote node gateway module GW (n) in step 300 of FIG. 6. Calculate The method of calculating the used bandwidth is as described above. Thereafter, the remote node gateway module GW (n) transmits the calculated use bandwidth to each of the gateway modules GW (A) -GW (N) of the local node 30 in step 302 of FIG. 6. At this time, the gateway module GW (n) of the remote node 40 calculates the above calculations to each of the gateway modules GW (A) -GW (N) of the local node 30 by referring to the remote IP table. The actual bandwidth used by the user datagram protocol (UDP). 1 and 3 illustrate only the local node 30 in the VoIP service network. For example, if there are nodes A, B, C, and D in the VoIP service network, the remote node gateway module GW (n) is shown. It is to be understood that transmits the calculated actual use bandwidth to each of the gateway modules of nodes A, B, C, and D as well as the local node 30. In short, the remote node gateway module GW (n) transmits the calculated actual use bandwidth to the gate modules of all nodes except the gateway modules GW (2)-GW (n-1) of its own node. This is to distribute traffic. In addition, in step 302 of FIG. 6, the remote node gateway module GW (n) transmits the IP address of the local node 30 and the bandwidth used by the GW (n) to the remote node total bandwidth control gateway module GW 1. Step 302 of FIG. 6 corresponds to ① 'of FIG. 3.

Thereafter, the remote node gateway module GW (n) determines whether a usage bandwidth is received from the local node 30 in step 304 of FIG. 6. This is because the local node 30 uses the bandwidth of the local node gateway module GW (N) and the total bandwidth of the local node 30 as shown in ① and ② of FIG. 3. This is because the data is transmitted to each of) -GW (n). When the usage bandwidth is received from the local node 30 in step 304 of FIG. 6, the flow proceeds to step 306 of FIG. 6 to update the usage bandwidth of the local node gateway module GW (N) and the total usage bandwidth of the local node 30. do.

Thereafter, the remote node gateway module GW (n) determines whether an IP call between the gateway module GW (N) of the local node 30 and the gateway module GW (n) of the remote node 40 is released in step 308 of FIG. 6. . If the IP call is released, the flow proceeds to step 310. In operation 310 of FIG. 6, the bandwidth used by the remote node gateway module GW (n) according to the IP call setup is calculated. After performing step 310 of FIG. 6, steps 312 to 316 are the same as steps 302 to 306 of FIG. 6. That is, as the IP call is released, the total bandwidth used by the local node 30 and the remote node 40 is increased, and the bandwidth used by the local node gateway module GW (N) and the remote node gateway module GW (n) is updated.

Finally, the operation of the total bandwidth control gateway module GW 1 of the remote node 40 will be described with reference to FIGS. 3 and 7.

The total bandwidth control gateway module GW 1 of the remote node 40 receives the IP address of the local node and the actual bandwidth of the GW (n) from the remote node gateway module GW 1 in step 400 of FIG. 7. Proceed to step 402 of FIG. In step 402 of FIG. 7, the total bandwidth control gateway module GW 1 calculates the total used bandwidth of the remote node 40 using the actual used bandwidth of the GW (n). Thereafter, the total bandwidth used by the remote node 40 calculated in step 204 of FIG. 5 is transmitted to each of the gateway modules GW (A) -GW (N) of the local node 30 by UDP. Step 404 of FIG. 7 corresponds to ② 'of FIG. 3.

The remote node total bandwidth control gateway module GW 1 then proceeds to step 406 of FIG. 7 to determine whether the bandwidth is received from the local node 30. In the local node 30, as shown in ① and ② of FIG. 3, the bandwidth used by the local node gateway module GW (N) and the total bandwidth used by the local node 30 are converted to the gateway modules GW (1) of the remote node 40. This is because the data is transmitted to each of) -GW (n). If the bandwidth is received from the local node 30 in step 406 of FIG. 7, the flow proceeds to step 408 of FIG. 7 to update the used bandwidth of the local node gateway module GW (N) and the total used bandwidth of the local node 30. .

Meanwhile, after the IP call between the gateway module GW (N) of the local node 30 and the gateway module GW (n) of the remote node 40 is released, the remote node gateway module GW (n) re-uses the bandwidth used according to the IP call release. Calculate and transmit to remote node total bandwidth control gateway module GW (1). The remote node total bandwidth control gateway module GW 1 determines whether an actual use bandwidth is received from the remote node gateway module GW (n) in step 410 of FIG. 7. If so, proceed to step 412. Steps 412 to 414 are the same as steps 402 to 404 described above. That is, the total bandwidth used by the remote node 40 is calculated, and the calculated total bandwidth used is transmitted to each of the gateway modules of the other nodes.

Thereafter, the remote node total bandwidth control gateway module GW 1 determines whether a usage bandwidth is received from the local node 30 in step 416 of FIG. 7. In the local node 30, as shown in ① and ② of FIG. 3, the bandwidth used by the local node gateway module GW (N) and the total bandwidth used by the local node 30 are converted to the gateway modules GW (1) of the remote node 40. This is because the data is transmitted to each of) -GW (n). If the bandwidth is received from the local node 30 in step 416 of FIG. 7, the flow proceeds to step 418 of FIG. 7 to update the used bandwidth of the local node gateway module GW (N) and the total used bandwidth of the local node 30. .

In the above description of the present invention, a VoIP service network without a gatekeeper has been described with reference to specific embodiments, but the VoIP service network with a gatekeeper may be modified without departing from the scope of the present invention. In short, the functions of the total bandwidth control gateway module of the local node and the remote node need only be embedded in the gatekeepers. Therefore, the scope of the present invention should not be defined by the described embodiments, but should be determined by the equivalent of claims and claims.

As described above, the present invention calculates the total bandwidth used considering the number of calls currently being processed by the gateway and the bandwidth according to the codec of each call. After that, a message is sent to the remote gateway through User Datagram Protocol (UDP) so that the remote gateway knows whether an incoming call is available. It also checks the total bandwidth used by the local gateway and blocks the use of the local gateway on outgoing calls or handles the call as a bypass route if the limit bandwidth is exceeded. It calculates the bandwidth used for real call and bandwidth control gateway that calculates (increases or decreases) the bandwidth between nodes, and transmits the bandwidth to the remote gateway whenever there is a bandwidth increase or decrease of the local gateway in use. The local gateway is notified of the increased and decreased bandwidth and the remote node so that the bandwidth can be calculated. All gateways can be efficiently used for VoIP call routing using the total bandwidth between nodes and the total bandwidth actually used by each gateway.

Claims (16)

Bandwidth in a voice over internet protocol service network having gateways for real-time two-way communication through the Internet between endpoint terminals having the ability to communicate at least one of voice, video and data, including the voice. In the management method, Calculating the actual bandwidth used by each of the gateways in consideration of the number of calls currently being processed by each of the gateways receiving the call setup request from the endpoint terminal and the bandwidth used according to the usage codec of each of the calls; , And transmitting the calculated actual used bandwidth to other gateways of the voice over internet protocol service network. The method of claim 1, If there is call release among calls in progress by call setup, each of the gateways takes into account the number of calls currently being processed according to the call release and the actual bandwidth at each of the gateways considering the bandwidth used according to the usage codec of each of the calls being processed. Recalculating the bandwidth used, And transmitting the recalculated actual use bandwidth to other gateways of the voice over internet protocol service network. Bandwidth in a voice over internet protocol service network having gateways for real-time two-way communication through the Internet between endpoint terminals having the ability to communicate at least one of voice, video and data, including the voice. In the management method, Calculating, by each of the gateways receiving the call setup and call release request from the endpoint terminal, the actual bandwidth used in each of the gateways in consideration of the number of calls currently being processed and the actual packet size of each of the calls; , And transmitting the calculated actual used bandwidth to other gateways of the voice over internet protocol service network. The bandwidth management method of claim 3, wherein the calculation of the actual bandwidth used per voice call comprises calculating at least one of a silence cancellation function and a multiframe transmission function. The bandwidth management method of claim 3, wherein the actual bandwidth used for each voice call is calculated using the following equation. Actual bandwidth used per voice call [kbps] = (header size + (payload size x number of frames) x (1sec / codec sampling period x number of frames) x0.4 (when silence is enabled) The method of claim 3, wherein the calculation of the actual bandwidth used per fax call when calculating the actual bandwidth is performed using the following equation. Actual bandwidth used per fax call [kbps] = (header size + (payload size x number of frames) x (1sec / transmission cycle) A first node and a second node, the first and second nodes each comprising a plurality of gateway devices supporting a plurality of channels, wherein each of the plurality of gateway devices includes the voice, video, and data; In the bandwidth management method in a voice over Internet protocol service network that has the ability to communicate at least one, including voice to enable real-time two-way communication through the Internet between the endpoint terminal, Each of the plurality of gateway devices of the first node that receives the call setup request from the endpoint terminal may determine the set second node limit bandwidth of the second node to route and the limit bandwidth of the corresponding gateway device of the second node. Comparing the previously stored second node use bandwidth received from the use bandwidth of the corresponding gateway device of the second node, Each of the plurality of gateway devices of the first node selectively processes the Internet protocol call setup according to the comparison result, and actual bandwidth used in each of the gateway devices in consideration of the number of calls currently being processed and the actual packet size of each of the calls. And the process of calculating And transmitting the calculated actual used bandwidth to each of the plurality of gateway devices of the second node. The bandwidth management method of claim 7, wherein the calculation of the actual bandwidth used per voice call includes calculating at least one of a silence cancellation function and a multiframe transmission function. The bandwidth management method of claim 8, wherein the actual bandwidth of the voice call is calculated using the following equation when calculating the actual bandwidth. Actual bandwidth used per voice call [kbps] = (header size + (payload size x number of frames) x (1sec / codec sampling period x number of frames) x0.4 (when silence is enabled) The method of claim 7, wherein the calculation of the actual bandwidth used per fax call when calculating the actual bandwidth is calculated using the following equation. Actual bandwidth used per fax call [kbps] = (header size + (payload size x number of frames) x (1sec / transmission cycle) A first node and a second node, the first and second nodes each comprising a plurality of gateway devices supporting a plurality of channels, wherein each of the plurality of gateway devices includes the voice, video, and data; In the bandwidth management method in a voice over Internet protocol service network that has the ability to communicate at least one, including voice to enable real-time two-way communication through the Internet between the endpoint terminal, Allocating one of the plurality of gateway devices of the first node and the second node as a first node and a second node total bandwidth control gateway device, respectively; Each of the plurality of gateway devices of the first node that receives the call setup request from the endpoint terminal may determine the set second node limit bandwidth of the second node to route and the limit bandwidth of the corresponding gateway device of the second node. Comparing the stored bandwidth of the second node with the received bandwidth from the corresponding gateway device of the second node; Each of the plurality of gateway devices of the first node selectively processes the Internet protocol call setup according to the comparison result, and considers the actual bandwidth used in each of the gateway devices in consideration of the number of calls currently being processed and the actual packet size of each of the calls. Calculation process, Transmitting the calculated actual use bandwidth to each of the plurality of gateway devices of the second node; Transmitting the calculated actual used bandwidth to a first node total bandwidth control gateway device; The first node total bandwidth control gateway device calculates the total used bandwidth at the first node using the calculated actual use bandwidth and transmits the calculated first node total actual use bandwidth to the second node total bandwidth control gateway device. Bandwidth management method characterized in that consisting of. 12. The method of claim 11, wherein the calculation of the actual bandwidth used per voice call when calculating the actual bandwidth is calculated using the following equation. Actual bandwidth used per voice call [kbps] = (header size + (payload size x number of frames) x (1sec / codec sampling period x number of frames) x0.4 (when silence is enabled) 12. The method of claim 11, wherein the calculation of the actual bandwidth used per fax call when calculating the actual bandwidth is performed using the following equation. Actual bandwidth used per fax call [kbps] = (header size + (payload size x number of frames) x (1sec / transmission cycle) A first node and a second node, the first and second nodes each comprising a plurality of gateway devices supporting a plurality of channels, wherein each of the plurality of gateway devices includes the voice, video, and data; In the bandwidth management method in a voice over Internet protocol service network that has the ability to communicate at least one, including voice to enable real-time two-way communication through the Internet between the endpoint terminal, Allocating one of the plurality of gateway devices of the first node and the second node as a first node and a second node total bandwidth control gateway device, respectively; Each of the plurality of gateway devices of the first node that receives the call setup request from the endpoint terminal may determine the set second node limit bandwidth of the second node to route and the limit bandwidth of the corresponding gateway device of the second node. Comparing the previously stored second node use bandwidth received from the use bandwidth of the corresponding gateway device of the second node, Each of the plurality of gateway devices of the first node selectively processes the Internet protocol call setup according to the comparison result, and considers the actual bandwidth used in each of the gateway devices in consideration of the number of calls currently being processed and the actual packet size of each of the calls. Calculation process, Transmitting the calculated actual use bandwidth to each of the plurality of gateway devices of the second node; Transmitting the calculated actual used bandwidth to a first node total bandwidth control gateway device; The first node total bandwidth control gateway device calculates the total used bandwidth at the first node using the calculated actual use bandwidth and transmits the calculated first node total actual use bandwidth to the second node total bandwidth control gateway device. Bandwidth management method characterized in that consisting of. A first node and a second node, the first and second nodes each comprising a plurality of gateway devices supporting a plurality of channels, wherein each of the plurality of gateway devices includes the voice, video, and data; In the bandwidth management method in a voice over Internet protocol service network that has the ability to communicate at least one, including voice to enable real-time two-way communication through the Internet between the endpoint terminal, Allocating one of the plurality of gateway devices of the first node and the second node as a first node and a second node total bandwidth control gateway device, respectively; Each of the plurality of gateway devices of the first node that has received the call release request from the endpoint terminal may be configured in each of the gateway devices in consideration of the number of calls currently being processed according to the call release request and the actual packet size of each of the calls. To calculate the actual bandwidth used by Transmitting the calculated actual use bandwidth to each of the plurality of gateway devices of the second node; Transmitting the calculated actual used bandwidth to a first node total bandwidth control gateway device; The first node total bandwidth control gateway device calculates the total used bandwidth at the first node using the calculated actual use bandwidth and transmits the calculated first node total actual use bandwidth to the second node total bandwidth control gateway device. Bandwidth management method characterized in that consisting of. A first node and a second node, the first and second nodes each comprising a plurality of gateway devices supporting a plurality of channels, wherein each of the plurality of gateway devices includes the voice, video, and data; In the bandwidth management method in a voice over Internet protocol service network that has the ability to communicate at least one, including voice to enable real-time two-way communication through the Internet between the endpoint terminal, The corresponding gateway device of the second node, which is the destination node of each of the plurality of gateway devices of the first node that has received the call setup request from the endpoint terminal, takes into account the number of calls currently being processed and the actual packet size of each of the calls. Calculating the actual bandwidth used by the corresponding gateway device of the second node; Transmitting the calculated actual usage bandwidth to the call setup corresponding gateway device of the first node; The corresponding gateway device of the second node receiving the actual use bandwidth calculated at each of the first node gateway devices from each of the gateway devices of the first node, updating the actual use bandwidth calculated at the first node gateway device. Bandwidth management method characterized in that consisting of.