CN101052014B - IP bearing call connection control method and device - Google Patents

Abstract

The method comprises: according to the bandwidth allocation and traffic model carried by IP bearer, determining the amounts of calls capable of being currently supported by the IP bearer; counting the amounts of calls which are carried by the IP bearer and already accessed the IP bearer; when a new call requests to access said IP bearer, deciding if the IP bearer reaches the number of calls currently capable of being supported by the IP bearer; if not, allowing the call to access the IP bearer; otherwise, rejecting the call.

Description

A method and device for IP bearer call access control

technical field

The present invention relates to the field of invalid communication, in particular to a call access control method and device of IP bearer.

Background technique

In early computer networks and packet forwarding networks, the network only provided best-effort services. For the service flow entering the network, the service flow is grouped in a first-come-first-served manner. With the rapid development of the Internet and various services, especially the rapid growth of multimedia services such as video and voice, the IP network has also changed from a single data network to a multi-service integrated digital network. At this time, the weakness of the traditional IP network without quality of service guarantee has emerged.

At present, the construction of the next generation telecommunication network based on the NGN (Next Generation Network, next-generation network) architecture is in the ascendant, and the key part of the NGN network is to ensure the security of the IP bearer network and QoS (Quality of Service, service quality).

The industry has proposed the concept of IP QoS, hoping to provide corresponding QoS guarantees for user services on the IP network. In order to more effectively monitor and control the resources of the entire network, in the new generation model, the concept of bandwidth agent, that is, network resource manager, is proposed. The bandwidth proxy collects network topology, node and link status information, manages network resources, and performs admission control in combination with the policy specified by the policy server to ensure the QoS of the IP bearer network. For example: to detect the QoS status of the IP bearer network, when it detects that the QoS status of the IP bearer network begins to decline, it will start to limit the amount of incoming calls; if the QoS status is severely degraded, it will refuse to access any calls or tear down low-priority calls. To ensure the QoS of the incoming call; if the QoS is recovered, the call will be connected normally.

The above-mentioned technical solution has the following disadvantages: the control of the incoming call volume is passive control based on the QoS status detection of the IP bearer network, that is, the call access control is performed only when it is detected that the QoS status of the IP bearer network has deteriorated. The QoS of incoming calls has been degraded and user experience has been compromised.

At the same time, the control of the access call volume in the above technical solution is subject to the accuracy of QoS status detection. If there are errors or fluctuations in the QoS detection report, a wrong call access control strategy may be generated, which will bring inconvenience to the operator. Necessary loss and user complaints.

Contents of the invention

An embodiment of the present invention provides a method for controlling IP bearer call access, so as to ensure the QoS of IP bearer by actively controlling call access. The method includes the following steps:

According to the bandwidth allocation and traffic model of the IP bearer, determine the number of calls currently supported by the IP bearer; count the number of calls currently accessed by the IP bearer; when there is a call request to access the IP bearer, determine the Whether the number of calls currently accessed by the IP bearer reaches the number of calls currently supported by the IP bearer, if not, allow the call to be accessed, and select a gateway with a small load for call access, the load A small gateway is a gateway with a large number of currently accessible calls from the gateway to the office route or to the IP bearer connected to the network element; otherwise, reject the call.

Another embodiment of the present invention also provides an IP bearer call access control device, which includes:

A calculation module, configured to calculate the number of calls currently supported by the IP bearer according to the bandwidth allocation and traffic model of the IP bearer;

A statistical module, configured to count the number of calls currently accessed by the IP bearer;

A control module, configured to determine whether the number of calls currently accessed by the IP bearer calculated by the statistical module reaches the current number of calls of the IP bearer calculated by the calculation module when there is a call request to access the IP bearer. If the number of calls that can be supported has not been reached, the call is allowed to be accessed, and a gateway with a small load is selected for call access. The gateway with a small load is the IP bearer from the gateway to the office or to the connected network element A gateway with a large number of calls currently accessible; otherwise, deny access to the call.

In the above-mentioned embodiments of the present invention, by calculating the call volume that the IP bearer can currently support and the call volume that has been accessed, it is judged whether the IP bearer can support new call access at present, so as to achieve active control of call access , thus guaranteeing the QoS of the incoming call.

Description of drawings

FIG. 1 is a schematic diagram of a call access control flow over IP bearer according to Embodiment 1 of the present invention;

FIG. 2 is a networking structure adopted in Embodiment 1 of the present invention;

FIG. 3 is a schematic diagram of a virtual circuit state maintenance process in Embodiment 1 of the present invention;

4 is a schematic structural diagram of an IP bearer call access control device according to Embodiment 2 of the present invention;

FIG. 5 is a schematic structural diagram of an IP bearer call access control device according to Embodiment 3 of the present invention.

Detailed ways

Embodiments of the present invention will be described in detail below in conjunction with the accompanying drawings.

The first embodiment of the present invention proposes an IP bearer network QoS active control scheme based on the concept of virtual circuits, so that the number of incoming calls in the IP bearer network is limited by the number of virtual circuits, thereby ensuring the QoS of incoming calls.

Referring to Fig. 1, it is a schematic diagram of the call access control flow of the IP bearer in Embodiment 1 of the present invention, and the specific steps include:

Step 101 , acquire the IP bandwidth allocation of each IP bearer segment, and make statistics on the traffic model.

Obtain the IP bandwidth allocated by the IP bearer network to an office route, a gateway, or a connected network element. For example, obtain the IP bearer section between MGW (Media GateWay, media gateway) and BSC (Base Station Controller, base station controller), the IP bearer section between each MGW, or the IP bearer section between MGW and RNC (RadioNetwork Controller, radio network controller) The IP bandwidth allocation of the IP bearer segment.

According to the bearer data type transmitted by each IP bearer segment in each traffic model, calculate the bandwidth theoretically occupied by each IP bearer segment in this traffic model. For example, if the traffic model is a voice call (enhanced variable rate coder EVRC is used to compress the voice codec), a single call in the BSC-MGW section occupies 8K bandwidth.

Step 102, according to the IP bandwidth and traffic model of each IP bearer segment, calculate the maximum number of various calls (ie, the number of virtual circuits) supported by the IP bearer network under different traffic models.

This embodiment uses the networking structure shown in FIG. 2 as an example to illustrate the calculation of the number of virtual circuits supported by the IP bearer network under different traffic models.

In the networking structure shown in Figure 2, it includes mobile softswitch centers MSCe A and MSCe B, as well as the base station controller BSC and media gateway MGW1-2 on the MSCe A side, the radio network controller RNC and the media gateway on the MSCe B side Gateway MGW3-4. MSCe communicates with MGW through H.248 media gateway control protocol, communicates with MSCe through SIP (Session Initiation Protocol, session initiation protocol), communicates with MSCe through A1p interface, and communicates with RNC through Iu interface Connection, BSC and MGW are connected through A2p interface. The dotted line in the figure indicates the signaling flow, and the thick solid line indicates the IP bearer flow. The IP bearer segment includes:

MGW1-BSC segment, allocated bandwidth 1M; traffic model: all voice calls (using EVRC compressed voice codec); a single call occupies a bandwidth of 8K, and this segment is under full load, allowing 128 calls in theory (1M/8K=128);

MGW4-RNC segment, allocated bandwidth 2M; traffic model: 50% voice call, 50% video call; assuming that a single voice call occupies a bandwidth of 10K, and a single video call occupies a bandwidth of 50K, then this segment is under full load, theoretically Allows access to 34 voice calls and 34 video calls.

As shown in the figure, the other IP bearer segments can similarly calculate the number of calls allowed to be accessed (that is, the number of virtual circuits).

When calculating the number of virtual circuits for each IP bearer segment, the impact of various conditions needs to be considered, such as the impact of the length of the data packet on the occupied bandwidth, and the network maintenance message will also occupy part of the bandwidth. Therefore, it is generally impossible to balance the capacity of the IP bearer segment at the theoretical value, and a certain margin needs to be left. You can set a threshold. For example, if the IP bandwidth is 100M, it is a balanced value when the estimated load is 70%. Therefore, calculate the maximum number of virtual circuits according to 70M. At the same time, the traffic model is not a single line, and various services must fluctuate. Therefore, in the case of multi-service access, it is necessary to appropriately expand the number of virtual circuits for each single service. For example, currently 50 voice calls and 50 video calls can be received; but at a certain moment, 50 voice calls have been received, but only 10 video calls have been received, so the IP bearer network actually still has the capacity to carry on call. In order to make full use of the bandwidth, the number of voice or video calls can be appropriately adjusted. For example, in the above case, the number of voice calls can be increased to 60 calls.

When configuring the number of virtual circuits for each IP bearer segment, you need to consider the ease of configuration. For example, in the MGW1-MGW2 segment, an MGW pair can be used to identify a section of IP bearer; while in the MGW1-BSC segment, an office gateway pair can be used to identify it. At the same time record the maximum number of virtual circuits for each IP bearer segment.

Call access is controlled by the number of virtual circuits. Therefore, it is necessary to maintain the status of virtual circuits in real time and count the number of occupied or available virtual circuits in real time. The following steps 103-106 describe the control process of call access through the virtual circuit and the maintenance process of the virtual circuit.

Step 103 , after receiving the call request, the network side judges whether there is any virtual circuit available at present, and if so, executes step 104 , otherwise executes step 106 .

When MSCe receives a call access request, it needs to select a gateway for the call. When choosing a gateway, it is necessary to consider the load condition of the gateway. A gateway with a small load is preferred, and the load can be determined according to the occupancy of the virtual circuit from the gateway to a certain office route or a certain entity. If the gateway is full, the call is rejected.

Take the network diagram 2 as an example: the call comes from BSC and connects to MSCeA from MGW1. Assume that the number of virtual circuits configured for BSC-MGW1 section IP bearer is 1000. If the number of currently occupied virtual circuits is less than 1000, there are still available If the number of occupied virtual circuits has reached 1000 and no virtual circuits are available, the call is rejected.

Step 104: When there are currently available virtual circuits, a call is received, and the number of available virtual circuits is updated.

In the system of this embodiment, a counter is set for each IP bearer segment to count the number of currently available virtual circuits. This counter is decremented by 1 each time a call is received. When the counter value is zero, it means that the maximum number of virtual circuits has been reached at present, that is, there is no virtual circuit available at present.

Step 105, release the call after the call ends, and update the number of available virtual circuits.

Each time a call is released, the counter value is incremented by 1.

Step 106, when there is no virtual circuit currently available, reject the incoming call.

Before each call is received, the count value of the counter is judged, and if it is zero, the call is rejected.

The foregoing embodiment uses a counter to count the number of currently available virtual circuits, and may also use a counter to count the number of currently occupied virtual circuits. In this case, the initial value of the counter is zero, and every time a call is received, the counter is incremented by 1; every time a call is released, the counter is decremented by 1. Before receiving a call, it is judged whether the count value of the counter reaches the maximum number of virtual circuits, if not, the call is accepted; otherwise, the access is rejected.

In the above embodiments, the load of the gateway needs to be considered in each link of the call, so as to select the correct gateway or route.

When configuring the number of virtual circuits in the IP bearer network, it can be configured according to the network structure and traffic model, and the number of virtual circuits can be adjusted in real time according to the system operation status, so as to realize the control of call access and ensure the QoS of call access . That is to say, the number of virtual circuits in the IP bearer network can be dynamically configured and adjusted according to the actual situation. For example, if the traffic model changes, the number of virtual circuits in the IP bearer network needs to be configured based on the new traffic model; As mentioned above, if the volume of voice calls accessed by a certain IP bearer segment has reached the corresponding number of configured virtual circuits, but the volume of incoming video calls is much lower than the corresponding number of configured virtual circuits, the number of virtual circuits for voice calls can be set appropriately. Increase, so that more calls can be received without affecting the QoS of incoming calls as much as possible, and the utilization rate of network resources can be improved.

For steps 103-105 in FIG. 1, the process of maintaining the virtual circuit state can be described by taking the call processing flow shown in FIG. 3 as an example.

Referring to FIG. 3 , it is a schematic diagram of a virtual circuit state maintenance flow chart according to Embodiment 1 of the present invention, and the specific steps include:

P1: Call access request. The request can come from another office/BSC/RNC, etc., or it can be an outbound or landing request to the BSC/RNC. The call needs to establish an IP bearer (the present invention only involves calls related to the IP bearer), and apply to the MGW for establishing the IP bearer. The steps ADD and ADD REPLY in the figure are the process of establishing the IP bearer.

P2: MSCe records that a virtual circuit is occupied after receiving the successful response returned by MGW; the virtual circuit belongs to a certain IP bearer segment, and the IP bearer segment to which it belongs can be a MGW pair or an IP office-to-gateway pair, depending on the user Depends on the configuration. The IP bearer segment to which the virtual circuit belongs can be obtained from the call attribute. Taking the network diagram shown in Figure 2 as an example, the call comes from the BSC and accesses the MSCe from the MGW1, and the unique IP bearer segment can be marked according to this information. Other cases can be deduced by analogy.

P3: Call release request. The steps SUB and SUB REPLY in the figure are the process of IP bearer release.

P4: When the MSCe releases the call, it releases the virtual circuit occupied by the call at the same time.

The second embodiment of the present invention provides an IP bearer call access control device.

Referring to FIG. 4 , it is a schematic structural diagram of an IP bearer call access control device according to Embodiment 2 of the present invention. The device includes a calculation module, a statistical module and a control module.

The calculation module is used to calculate the number of calls currently supported by the IP bearer according to the bandwidth allocation and traffic model of the IP bearer. The calculation module includes an acquisition sub-module, a calculation sub-module and an adjustment sub-module, wherein the acquisition sub-module is used to obtain the current bandwidth allocation and traffic model of the IP bearer; the calculation sub-module is used to obtain the IP bearer according to the acquisition sub-module Calculate the number of calls that the IP bearer can support based on the bandwidth allocation situation and the traffic model; the adjustment submodule is used to multiply the number of calls that the IP bearer can support calculated by the calculation submodule by a coefficient that is less than 1.

The statistical module is a first counter, which is used for counting the number of new calls that can still be accessed by the IP bearer. The initial value of the first counter is set to the number of calls currently supported by the IP bearer calculated by the calculation module, and every time a call is received, the value of the first counter is decremented by 1; every time a call is released, the value of the first counter is increased by 1 .

When there is a call request to access the IP bearer, the control module judges whether the count value of the first counter is greater than or equal to 1, if so, it indicates that the number of calls currently accessed by the IP bearer has not yet reached the number of calls that the IP bearer can currently support If the control module judges that the count value of the first counter is zero, it indicates that the number of calls currently accessed by the IP bearer has reached the number of calls that the IP bearer can currently support, so it refuses to accept the call. into the call.

The third embodiment of the present invention also provides an IP bearer call access control device.

Referring to FIG. 5 , it is a schematic structural diagram of an IP bearer call access control device according to Embodiment 3 of the present invention. The device includes a calculation module, a statistical module and a control module.

Wherein, the calculation module is the same as the calculation module shown in FIG. 4 .

The statistical module is a second counter, which is used to count the number of calls currently accessed by the IP bearer; the initial value of the second counter is set to 0, and each time a call is received, the value of the second counter is increased by 1; each time a call is released , decrement the value of the second counter by 1.

When there is a call request to access the IP bearer, the control module judges whether the count value of the second counter is equal to the number of calls currently supported by the IP bearer counted by the calculation module, if the count value of the second counter is less than the value calculated by the calculation module , it indicates that the number of calls that the IP bearer has currently accessed has not yet reached the number of calls it can support, so the call is allowed to be accessed; if the second counter count value is equal to the value calculated by the calculation module, it indicates that the IP bearer is currently The number of calls that have been placed has reached the number of calls it can support, and the call is refused to be admitted.

In summary, the above embodiments of the present invention calculate the maximum call volume that each IP bearer segment can support based on the traffic model based on the acquired IP bandwidth allocation and traffic model of each IP bearer segment, and When inserting/releasing a call, it counts the number of calls currently received; before accessing a call, according to the maximum call volume that the IP bearer segment can support and the current call volume that the IP bearer segment has already received, determine the number of calls that can still be accessed Call volume, and then control call access according to the judgment result, thus ensuring that the QoS of the received call is not affected. In addition, when the embodiment of the present invention calculates the maximum call volume supported by the IP bearer segment, it can also adjust the calculated maximum call volume in real time according to the system permission and the traffic model, thereby further ensuring the QoS of the incoming call.

Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalent technologies, the present invention also intends to include these modifications and variations.

Claims (10)

1. IP bearing call connection control method, described calling are the calling relevant with the IP carrying, it is characterized in that, may further comprise the steps:

According to the allocated bandwidth and the traffic model of IP carrying, determine the current call number that can support of described IP carrying;

Add up the current call number that has inserted of described IP carrying;

When call request inserts described IP carrying, judge whether the current call number that has inserted of described IP carrying reaches the current call number that can support of described IP carrying, if also do not reach, then allow to insert described calling, and select the little gateway of load to call out access, the gateway that described load is little carries the big gateway of the current call number that inserts for this gateway to office direction or to the IP that connects network element; Otherwise refusal inserts described calling.

2. the method for claim 1 is characterized in that, described allocated bandwidth and traffic model according to the IP carrying determined the call number that described IP carrying can be supported, comprises step:

Obtain the maximum of described each IP carrying distribution and support the shared bandwidth of individual call in bandwidth, traffic model and this traffic model;

Support the shared bandwidth of individual call in bandwidth, traffic model and this traffic model according to the maximum that each the IP carrying that gets access to distributes, calculate the calculated value of the call number of described IP carrying support.

3. method as claimed in claim 2 is characterized in that, behind the calculated value of the call number that bandwidth and traffic model according to described IP carrying calculate described IP carrying support, also comprises step:

Described calculated value is adjusted, obtained the current call number that can support of described IP carrying;

Process to described calculated value adjustment comprises: described calculated value be multiply by coefficient less than 1, obtain the current call number that can support of described IP carrying.

4. the method for claim 1, it is characterized in that, when multi-service inserts, the call number that has inserted when wherein partial service type reaches the call number of current this type of service that can support of described IP carrying, and the call number that another part type of service has inserted is not when also reaching the call number of this type of service that described IP carrying can support, the former the current call number that can support of described IP carrying of type of service correspondence is increased designated value, obtain the call number of current this type of service that can support of described IP carrying.

5. the method for claim 1 is characterized in that, described allocated bandwidth and traffic model according to the IP carrying determined the current call number that can support of described IP carrying, comprising:

Be office direction, gateway or connect the bandwidth that network element distributes according to the IP bearer network, calculate the current call number that can support of IP carrying section between described office direction, gateway or the connection network element respectively.

6. an IP bearing call access control apparatus is characterized in that, comprising:

Computing module is used for allocated bandwidth and traffic model according to the IP carrying, calculates the current call number that can support of described IP carrying;

Statistical module is used to add up the current call number that has inserted of described IP carrying;

Control module, be used for when call request inserts described IP carrying, judge whether the current call number that has inserted of described IP carrying that described statistical module counts goes out reaches the current call number that can support of described IP carrying that described computing module calculates, if also do not reach, then allow to insert described calling, and select the little gateway of load to call out access, the gateway that described load is little carries the big gateway of the current call number that inserts for this gateway to office direction or to the IP that connects network element; Otherwise refusal inserts described calling.

7. device as claimed in claim 6 is characterized in that, described statistical module is first counter, and the initial value of described first counter is the current call number that can support of described IP carrying that described computing module calculates; And calling of every access subtracts 1 with described first counter values, and calling of every release adds 1 with described first counter values;

Described control module more than or equal to 1 o'clock, allows to insert described calling at the numerical value of described first counter; When the numerical value of described counter was zero, refusal inserted described calling.

8. device as claimed in claim 6 is characterized in that, described statistical module is second counter, and the initial value of described second counter is 0; And calling of every access adds 1 with described second counter values, and calling of every release subtracts 1 with described second counter values;

During the current call number that can support of the described IP carrying that described control module calculates less than described computing module in described second counter values, allow to insert described calling; When described counter values equaled the current call number that can support of described IP carrying that described computing module calculates, refusal inserted described calling.

9. as the described device of the arbitrary claim of claim 6-8, it is characterized in that described computing module comprises:

Obtain submodule, be used for obtaining maximum support bandwidth, traffic model and the shared bandwidth of this traffic model individual call that each IP carrying distributes;

Calculating sub module is used for obtaining the maximum that each IP carrying that submodule gets access to distributes and supporting bandwidth, traffic model and the shared bandwidth of this traffic model individual call according to described, calculates the call number that described IP carrying can be supported.

10. device as claimed in claim 9 is characterized in that described computing module also comprises the adjustment submodule, and the call number that the described IP carrying that is used for that described calculating sub module is calculated can be supported multiply by the coefficient less than 1.

Images