WO2009018744A1

WO2009018744A1 - Implementation method, system, media gateway and media gateway controller for route control

Info

Publication number: WO2009018744A1
Application number: PCT/CN2008/071724
Authority: WO
Inventors: Zhijun Liao; Haopeng Zhu
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-08-09
Filing date: 2008-07-23
Publication date: 2009-02-12
Also published as: EP2139154A4; CN101365169A; CN101365169B; EP2139154A1

Abstract

An implementation method,system, media gateway and media gateway controller for route control are disclosed. The implementation method for route control includes: detecting IP bearing of a link connecting the media gateway MGW with an opposite terminal, acquiring a detection result (201); performing call route control based on the detection result of the IP bearing (202).

Description

Method, system, media gateway and media gateway controller for implementing routing control

The present invention relates to telecommunications technologies, and in particular, to a method, system, media gateway, and media gateway controller for implementing routing control.

Background technique

At present, telecommunication services and technologies are constantly evolving. The traditional service and control of the Public Switched Telephone Network (PSTN) based on Time Division Multiple Access (TDM) is completed by switches. This technology can guarantee the excellent quality of voice, but provides New business requires a longer period of time. At the same time, the development of network technology and the increasing demand for computer interconnections have resulted in the use of Internet Protocol (IP)/Asynchronous Transfer Mode.

The (AB) packet-switched data network is growing. This kind of packet-switched network is suitable for the transmission of various types of information. The network resource utilization is high, and the operation and maintenance costs are very low. Therefore, IP voice has appeared.

(VoIP), that is, voice signals are exchanged in IP networks in groups.

In this case, the Next Generation Network (NGN) emerges as the times require, and the traditional circuit-switched PSTN gradually transitions to the packet-switched IP network. The NGN carries all the services of the original PSTN network. , offloading a large amount of data transmission to the IP network to alleviate the heavy load of the PSTN network, and adding many new services and enhancing many old services with the new features of IP technology. In this sense, NGN is a product of TDM-based PSTN voice network and IP/ATM-based packet network convergence, which makes it possible to integrate voice, video, data and other services on a new generation network.

In the NGN network architecture, a separate structure, namely a Media Gateway Controller (MGC) and a Media Gateway (MGW), is introduced. As shown in Figure 1, it is a networking diagram of the NGN network architecture. The Media Gateway Controller (MGC) is a core network element that forms a network domain with the attached Media Gateway (MGW). MGC's software-based distributed switching and control platform is a network device oriented to the service control layer. It is located at the center of the domain, controls other related network modules, and completes call flow control. The MGW implements user access in various modes, accepts control of the MGC, and executes process commands, usually completing end-to-end service connections, that is, bearer functions. MGC controls MGW through the standard H.248/MGCP protocol interface. The separation of business and call control is now available. The calling process between the local end and the peer end includes a signaling interaction process and a traffic interaction process. The signaling interaction process is performed by the MGC in the local network domain and the MGC in the peer network domain, where the MGC and the MGC are based on the BICC/SIP protocol. Communication; The traffic interaction process is completed by the MGW under the control of the MGC in the local network domain and the MGW under the control of the MGC in the peer network domain. In addition, IP bearer connections can also be used between the mobile network, the Radio Network Controller (RNC) and the Base Station Controller (BSC) and the Core Network Equipment (MGC, MGW). Among them, in the mobile phone network, the MGC can be a mobile switching center-server (MSC-SERVER). The role of the Mobile Switching Center (MSC) is similar to that of fixed-line telephone switching equipment. Its main function is to control and manage mobile users located in its control area, providing interfaces to other regional MSCs and numerous base stations, and The connection to the mobile user's call and the exchange of information.

In the above NGN network architecture, both TDM bearers and IP bearers can be used, and the two can be backed up each other. When using IP bearer, when the MGC is disconnected from the MGW, or there is no available circuit resources on the MGC, the MGC can trigger routing reselection for the newly occurring call and select a route with available resources (TDM backup route or other available IP routes). Try to ensure that the call is successfully connected. However, in the process of implementing the present invention, the inventors have found that the technology can only solve the H.248 link between the MGW and the MGC, or the link between the MGC and the MGC, or the link between the MGC and the RNC/BSC. In this case, the backup of the traffic is shared, and the IP bearer between the MGW and the MGW in different network domains cannot be detected, and whether the IP bearer between the RNC/BSC and the MGW is interrupted or fails, and the route cannot be solved in this case. If the IP bearer between the MGW and the MGW or between the RNC/BSC and the MGW is congested or faulty, the service becomes unavailable and the service performance of the network is reduced.

Summary of the invention

In view of this, an embodiment of the present invention provides a method for implementing route control, and another aspect provides a system for implementing a route control, a media gateway, and a media gateway controller, so as to improve service performance of a call. A method for implementing route control provided by an embodiment of the present invention includes:

Detecting the IP bearer of the inter-network interconnection protocol of the link connecting the media gateway MGW with the peer end; According to the obtained detection result, call routing control is performed.

A system for implementing routing control according to another embodiment of the present invention includes:

The detecting module is configured to detect the IP bearer of the link connected to the peer end of the media gateway MGW, and the routing control processing module is configured to perform call routing control according to the detection result obtained by the detecting module.

A media gateway provided by another embodiment of the present invention includes:

a detecting module, configured to detect an IP bearer of a link connected to the peer end of the media gateway MGW, and a detection information reporting module, configured to send to the media gateway controller according to the detection result of the detecting module

The MGC reports the detection information.

A media gateway controller according to another embodiment of the present invention includes:

The routing control execution module is configured to obtain a detection result of the IP bearer, and perform call routing control according to the detection result of the IP bearer.

As shown in the foregoing solution, in the embodiment of the present invention, the IP bearer of the link connected to the MGW is detected, and the call routing control is performed according to the detection result. Therefore, when the IP bearer of the link connected to the MGW is faulty or congested, the route can be connected in time, which improves the service performance of the network.

DRAWINGS

1 is a networking diagram of an NGN network architecture in the prior art;

2 is an exemplary flowchart of a method for implementing route control according to an embodiment of the present invention;

Figure 3 (a) _ Figure 3 (e) is a networking diagram of several specific implementations in the method flow shown in Figure 2; Figure 4 is an exemplary flow chart of the implementation system of the routing control in the embodiment of the present invention;

Figure 5 is a first specific implementation structure diagram of the system shown in Figure 4;

6 is a second specific implementation structure diagram of the system shown in FIG. 4;

7 is a third specific implementation structure diagram of the system shown in FIG. 4;

Figure 8 is a fourth concrete implementation structure diagram of the system shown in Figure 4;

FIG. 9 is a diagram showing the internal structure of an MGW according to an embodiment of the present invention. detailed description

In the embodiment of the present invention, an IP bearer of a link connected to the MGW is detected; and call routing control is performed according to the obtained detection result. For convenience of description, the remote MGW that communicates with the current MGW or the RNC/BSC of the local end is collectively referred to as the peer.

In order to make the objects, the technical solutions and the advantages of the present invention more comprehensible, the present invention will be further described in detail below with reference to the embodiments and drawings.

FIG. 2 is an exemplary flowchart of a method for implementing route control according to an embodiment of the present invention. As shown in Figure 2, the process includes the following steps:

Step 201: Detect the IP bearer of the link connected to the peer end by the MGW, and obtain a detection result. In this step, when detecting the IP bearer of the link between the MGW and the peer end, the quality of service (QoS) and link continuity of the IP bearer are detected, and the specific detection method may be various, for example, At least the following five types are shown. Figure 3 (a) _ Figure 3 (e) is a networking diagram for the implementation of the five methods. The local and remote ends can communicate with each other through the tandem office. In addition, the assumption is assumed. There are two IP domains between the local MGW and the remote MGW, namely IP domain 1 and IP domain 2. There are two IP domains between the local MGW and the local RNC/BSC, namely IP domain 1 and IP domain 2.

The first method: The local MGW detects the IP address of the peer IP address or the network segment. Referring to FIG. 3 (a), in this method, when the local MGW establishes a call connection with the opposite end, the destination IP address of the current call to the opposite end can be obtained, and therefore, the local MGW can be different to the peer's different IP address or network segment. The IP bearer link is detected.

The detection of the IP bearer link of each peer IP address or network segment may include at least the following two methods:

Manner 1: The local MGW detects the packet loss rate of the current IP address of the peer end, or counts the packet loss rate, delay, and jitter to detect the quality of service (QoS) of the IP link.

In specific implementation, if there are multiple calls to the peer IP address/network segment, in order to reduce the operation rate, it is not necessary to perform packet loss rate, packet loss rate, delay, and jitter statistics for all calls. You can select a few randomly, for example, you can arbitrarily select a few (for example, 3) calls. Statistics In a method, the packet loss rate or packet loss rate, delay, and jitter on the sample call paths can be monitored in real time. Among them, the RTCP protocol can be directly used for statistics. The above method is applicable to the IP bearer between the MGW and the MGW, and also between the MGW and the RNC or the BSC.

Manner 2: Detects the QoS of the IP link due to the failure rate of the call due to the unreachable current IP address of the peer.

In the specific implementation, if the NbUP negotiation process is initiated before the bearer plane is established, the call failure rate (that is, the call loss rate) caused by the unreachable current IP address of the peer end is obtained by collecting the NbUP negotiation timeout failure rate. ) to detect the QoS of the IP link.

Alternatively, under the existing mechanism, a continuity detection mechanism under the IP bearer network may be added, that is, in the call setup phase, after the MGC completes the session description protocol (SDP, Ses s ion descr ipt ion protocol) negotiation, the MGW is paired. The IP address of the terminal sends a handshake message and starts the timer. If the peer does not receive the acknowledgment after the timeout, the device can resend the packet. If the retransmission is not received, the peer IP address is unreachable.

In the above two methods, in order to identify the result of the Qos, the packet loss rate (such as 5%) or the packet loss rate, the jitter and the delay threshold or the call loss rate (such as 30%) may be preset. According to the packet loss rate and the preset packet loss rate threshold, or according to the packet loss rate, jitter and delay value, and the preset packet loss rate, jitter and delay threshold, or according to the call loss rate and the preset call The loss rate is wide, and the IP bearer is detected for congestion or failure. After detecting the packet loss rate or the packet loss rate, the jitter and the delay value, or the call loss rate reaching a preset threshold, it may be determined that the IP bearer link is congested or faulty.

The second method is: The MGC instructs the peer end to perform the IP bearer detection to the MGW, and the MGW detects the IP bearer of the indicated call, that is, the MGC notifies the MGW to perform the IP bearer detection. Referring to Figure 3 (b), the method does not require the MGW to actively perform the statistics of the destination IP address. Instead, the MGC indicates the MGW to the peer call for which the IP bearer is to be detected by the ADD command of H.248. IP bearer QoS is detected.

The peer call for performing the IP bearer detection includes: a call between the MGW to which the IP bearer detection is to be performed to all the MGWs controlled by the remote MGC, or a call between the MGW pair formed by the MGW and the remote MGW. Calling, or calling the MGW to the local radio network controller RNC/base station controller BSC in the scenario where the MGW and the access side use the IP bearer.

The MGW for the current call indicated by the remote MGC may notify the local MGC, and may not notify the local MGC. Therefore, when the local MGC does not know that the opposite end is responsible for the MGW carried by the current call, the local end The MGC can randomly select several calls on the peer MGC as the sample call, and instruct the MGW to perform statistics. When the local MGC knows that the peer is responsible for the MGW carried by the call, the local MGC can randomly select the few on the opposite MGW. As a call, the call is randomly selected as a call between the current MGW of the local end and the MGW pair formed by the current MGW of the opposite end. In addition, the local MGC can also randomly select several calls on the local RNC/BSC as a sample call.

The MGW collects the packet loss rate or packet loss rate, jitter, and delay value of the IP bearer corresponding to the corresponding call link according to the received ADD command, according to the packet loss rate or packet loss rate, jitter and delay value, and the preset width. The value detects whether the IP bearer is congested or faulty. When the packet loss rate or the jitter and delay values are greater than a preset threshold, it may be determined that the IP bearer link is congested or faulty.

The third method: The MGC performs IP bearer detection according to the statistics of the connection rate between the local end and the opposite end. Referring to Figure 3 (c), this method can be used without the participation of the MGW. The MGC counts the call rate of the call to the peer (including the remote MGC, RNC/BSC) according to the most recent cycle, according to the connection rate and the preset. The connection rate threshold detects whether the IP bearer is congested or faulty. When the connection rate is reduced to the set connection rate threshold, it can be judged that there is congestion or failure of the IP bearer in this direction. Or, according to the statistical result of the connection rate, the call loss rate is obtained, and whether the IP bearer is congested or faulty is detected according to the call loss rate and the preset call loss rate threshold. When the call loss rate exceeds the set call loss rate threshold, it can be judged that there is congestion or failure of the IP bearer in this direction.

The fourth method: The MGW directly obtains whether the IP bearer detection result is congestion or fault according to the state of the local IP port.

Referring to Figure 3 (d), in this method, if the IP physical port is faulty, or the connection is interrupted, the MGW can detect it immediately.

The fifth method: During the call, according to the result of the user plane negotiation process, the IP bearer check is obtained. Check if the result is faulty or congested.

Referring to Figure 3(e), the bearer plane is established after the NbUP negotiation process is completed. Therefore, when the NbUP negotiation fails, it can generally be considered that the bearer plane is faulty.

Alternatively, under the existing mechanism, a continuity detection mechanism under the IP bearer network may be added. That is, after the SDP negotiation is completed between the MGCs, the MGW sends a handshake message to the peer IP and starts a timer. If the peer does not receive the acknowledgment, the device can resend it. If the retransmission is still repeated for a certain number of times, the IP bearer cannot be considered.

Step 202: Perform call routing control according to the detection result of the IP bearer.

For the two methods in the first method in step 201, referring to FIG. 3(a), when detecting that the IP bearer is congested or faulty, the MGW may be based on the packet loss rate or the packet loss rate, the delay, and the jitter value. Or, according to the value of the call loss rate, the bearer released ind message is actively reported to the MGC in proportion to the subsequent call to the IP address or the network segment, and the reason identifier is carried in the message (for example, the call may be set The reason value is 83), which is used to indicate that the IP link is unreachable. The higher the packet loss rate or the call loss rate, the higher the proportion of calls that the MGW actively releases, but the MGW still needs to keep at least a small number of calls for detecting the recovery of the bearer path.

When the MGC receives the bearer release indication message reported by the MGW during the call setup phase, and carries the cause identifier indicating that the IP link is unreachable (for example, the cause value is 83), the MGC may perform route reselection or IP domain handover (ie, IP domain reselection), routing the current call to the backup route or other available IP routing or IP bearer, as indicated by the ADD. req message to indicate the new IP domain.

For the second method in step 201, referring to FIG. 3(b), when detecting that the IP bearer is congested or faulty, the MGW may report a notification (Noitfy) message to the MGC, where the notification message carries the QoS level. At this time, the event type in the notification (Noitfy) message may be a quality alert event of the H.248.1E.11 Network Package. If the MGW detects that the congestion or fault level reaches the highest level, the IP bearer network may be considered to be interrupted, and the event type of the notification (Noitfy) message may be a network failure event defined in the network packet. After receiving the notification (Not ify ) message indicating the QoS level of the local MGW to the peer IP bearer link from the H.248 interface, the MGC may reduce the local MGW according to the QoS level in the Notify message. The call of the corresponding IP bearer link, the call is returned to other available routes, or the call is routed from the other MGWs of the local end to the peer to share the traffic. That is, other MGWs are used for traffic interaction, that is, the MGC controls the pair according to the QoS level. Some or all of the endpoints are routed for reselection; or when there are multiple IP domains between the local end and the peer end, the MGC can switch the IP domain of the partial call, and the ADD. req message carries the new IP domain indication. The MGW allocates IP resources of the corresponding domain.

For the third method in step 201, referring to FIG. 3(c), when it is detected that the IP bearer is congested or faulty, for example, when the IP domain 1 fault is detected, an alarm message may be sent, and the traffic between the routes is automatically performed. The traffic switching between the sharing and the routing, the traffic in the fault direction is gradually shared to the backup route, and the IP domain switching can also be performed, and the traffic is shared to other IP domains (for example, IP domain 2). If the statistics connection rate is 0, the MGC automatically switches all traffic to the backup route or other IP domain.

For the fourth method in step 201, referring to FIG. 3(d), when detecting that the IP bearer is congested or faulty, for example, when detecting that the interface between the MGW and the IP domain 1 fails, the MGC initiates a call, and When the MGW is required to allocate IP resources on this port, the MGW can return a special cause value in the response message (ADD. rsp) and indicate the bearer interruption. When the MGC initiates a call and asks the MGW to allocate IP resources on the port, the ADD command can be used; the response message returned by the MGW can be an ADD. rsp message.

When the MGC uses the ADD command to add an endpoint, and the MGW returns a response message indicating that the interrupt is interrupted, the MGC initiates a failed route reselection or an IP domain switch according to the failure cause value indicating the bearer interruption, routes the call to the backup route, or switches to another. On the IP route, the IP field 2 can be indicated by ADD. re (!

For the fifth method in step 201, referring to FIG. 3(e), when the local MGW that initiates the negotiation process (such as NbUP negotiation) determines that the negotiation process exceeds the set duration, the negotiation process of the IP domain 1 is exceeded. When the duration is set, the bearer release indication indicating that the negotiation process fails may be reported to the MGC. ( bearer released ind ) message, which can carry a special cause value. When the MGC receives the bearer release indication message from the MGW and indicates that the negotiation fails, the MGC may end the establishment process of the bearer first, and then perform route reselection or IP domain handover (for example, the IP may be indicated by an ADD. req message). Domain 2). The roaming number needs to be re-acquired before routing re-selection.

In the above five methods, when a fault or congestion occurs, an alarm message can be further sent.

Further, after the IP bearer fails, the service on the interface can be restored.

In the first method in step 201, when the mode is used, the MGW detects that the packet loss rate of the peer IP address is lower than the set packet loss rate, or when the mode 2 is used. If the number of calls that fail to negotiate NbUP is lower than the set call loss rate, the MGW determines that the IP bearer is restored to normal by congestion or failure, and gradually reduces the proportion of active release according to the degree of recovery. Directly restore the original communication, no longer actively released.

For the second method in step 201, the MGW detects the packet loss rate information on the call path in real time according to the indication of the MGC, if the bearer plane recovers from failure or congestion to normal, or when the packet loss rate is less than a preset threshold Then, the notification (Not ify ) message reported by the MGW to the MGC carries the QoS recovery information. At this time, the event type of the notification (Not ify ) message may be a Qualitative Alert Ceas ing event. The MGC gradually recovers the call traffic between the corresponding MGC direction or the corresponding MGW pair according to this Not Notify message.

For the third method in step 201, the maintenance personnel can perform fault processing according to the alarm information, and restore the original traffic load sharing ratio.

For the fourth method in step 201, when the IP port of the MGW is restored to normal and the connection is normal, the MGW receives the call initiated by the MGC and requests the MGW to allocate the IP resource on the IP port, and returns the indication success. In response to the message, the call is automatically restored to the original routing direction, that is, according to the normal situation, the call is connected in the original routing direction.

For the fifth method in step 201, if the bearer between the MGWs is restored, the negotiation process such as NbUP can also succeed, and the call is normally connected. The method for performing route reselection includes: selecting a TDM backup route, or other available IP routes; IP domain switching method: The MGC sends different domain parameters in the ADD. req command to instruct the MGW to use other available IP bearer planes. Assign the corresponding IP resources. The method described herein is to switch or share multiple calls in a statistical sense. Switching or sharing here refers to routing reselection or IP domain switching for some or all of the calls.

The method for implementing the routing control provided by the embodiment of the present invention detects the IP bearer of the link connected with the MGW, and performs call routing control according to the detection result. Therefore, when the IP bearer of the link connected to the MGW is faulty or congested, the route can be connected in time, which improves the service performance of the network.

FIG. 4 is an exemplary structural diagram of an implementation system of route control in an embodiment of the present invention. As shown in FIG. 4, the system includes: a detection module and a route control processing module.

The detecting module is configured to detect an IP bearer of the link between the MGW and the peer end.

The routing control processing module is configured to perform call routing control according to the detection result obtained by the detecting module.

In the specific implementation, the foregoing system may have multiple implementation forms, and five of them are listed below: FIG. 5 shows a first specific implementation structure diagram. As shown in FIG. 5, the detection module in the system includes a statistics module and The result determining module, the routing control processing module includes a detection information reporting module and a routing control module.

The statistics module is used to collect the packet loss rate or packet loss rate, jitter and delay, or call loss rate to the peer IP address.

The result determining module is configured to determine whether the IP bearer is congested or faulty according to the packet loss rate or the packet loss rate, the jitter and the delay or the call loss rate, and the preset threshold value obtained by the statistics module.

The detection information reporting module is configured to send, to the routing control module, a reason flag indicating that the IP link is unreachable, according to the degree of congestion or failure, when the detection result is that there is congestion or a fault. The bearer release indication message.

The routing control module is configured to release the bearer according to the reason indicating that the IP link is unreachable The indication message is used to perform route reselection or IP domain switching on the call corresponding to the message.

In the above system, as shown by the dotted line in FIG. 5, the statistics module, the result determination module, and the detection information reporting module may be set in the MGW, and the routing control module may be set in the MGC, and the flow shown in FIG. 2 The scheme of the first method described in the above corresponds, and the specific operation process of each module can also be consistent with the operation of the first method described in the flow shown in FIG. 2.

Further, the detection information reporting module may further reduce the reason for the subsequent occurrence of the call to the IP address when the IP bearer is recovered by the congestion or the failure, and reduce the reason for the transmission of the indication IP link to the routing control module according to the degree of recovery. The ratio of the identified bearer release indication message.

FIG. 6 shows a second specific implementation structure diagram. As shown in FIG. 6, the detection module in the system includes a detection indication module and a detection execution module, and the route control processing module includes a detection information reporting module and a routing control module.

The detection indication module is configured to send a call indication for performing IP bearer detection to the detection execution module.

The detection execution module is configured to collect a packet loss rate of the IP bearer of the call or a packet loss rate, jitter, and delay of the IP bearer of the call, according to a packet loss rate or a packet loss rate, a jitter, and a delay value. The preset threshold detects whether the IP bearer is congested or faulty.

The detection information reporting module is configured to send a notification message carrying the quality of service level to the routing control module when the detection result is that there is congestion or failure.

The routing control module is configured to perform routing reselection or IP domain switching on part or all of the calls to the peer according to the quality of service level in the notification message.

In the above system, as shown by the dotted line in FIG. 6, the detection indication module and the routing control module can be set in the MGC, and the detection execution module and the detection information reporting module can be set in the MGW, and the flow shown in FIG. 2 is The scheme of the second method described corresponds to the specific operation procedure of each module, which can also be consistent with the operation of the second method described in the flow shown in FIG. 2.

Further, the detection information reporting module may further send a notification message carrying the quality of service recovery to the routing control module when detecting that the IP bearer is restored by congestion or failure; the routing control module Further, when receiving the notification message carrying the quality of service restoration, the original routing control is restored. FIG. 7 shows a third specific implementation structure diagram. As shown in FIG. 7, the detection module in the system includes a statistics module and a result determination module, and the route control processing module includes a route control module.

The statistics module is configured to perform statistics on the connection rate or the call loss rate of the IP bearer to the peer end.

The result determining module is configured to determine whether the IP bearer is congested or faulty according to the connection rate or the call loss rate obtained by the statistics module, and the preset connection rate threshold or the call loss rate threshold.

The routing control module is configured to send an alarm message when the detection result is that there is congestion or a fault, and perform traffic sharing between routes or traffic switching between routes, or perform IP domain switching.

In the above system, the statistical module, the result determining module and the routing control module can all be set in the MGC. In this case, corresponding to the solution of the third method described in the flow shown in FIG. 2, the specific operation process of each module can also be performed. It is consistent with the operation of the third method described in the flow shown in FIG. 1.

FIG. 8 shows a fourth specific implementation structure diagram. As shown in FIG. 8, the detection module in the system includes a state detection module, and the route control processing module includes a detection information reporting module and a routing control module.

The status detection module is configured to obtain, according to the status of the IP port, whether the IP bearer is congested or faulty.

The detection information reporting module is configured to report a response message indicating that the bearer is interrupted to the routing control module when receiving the call initiated by the MGC and requesting the MGW to allocate the IP resource on the IP port when the detection result is that the congestion or fault occurs.

The routing control module is configured to perform route reselection or IP domain switching according to the response message indicating that the bearer is interrupted.

In the above system, the detection module and the detection information reporting module may be set in the MGW, and the routing control module may be disposed in the MGC, corresponding to the solution of the fourth method described in the flow shown in FIG. 2, The specific operation process can also be consistent with the operation of the fourth method described in the flow shown in FIG. 2.

The fifth concrete implementation, the structure diagram is consistent with the structure diagram shown in Figure 8, in the system The detection module includes a state detection module, and the route control processing module includes a detection information reporting module and a routing control module.

The status detection module is configured to obtain whether the IP bearer is congested or faulty according to the result of the user plane negotiation process.

The detection information reporting module is configured to report, to the routing control module, a bearer release indication message indicating that the negotiation process fails when determining that the negotiation process exceeds the set duration.

The routing control module is configured to end the establishment process of the current bearer according to the release indication message, and perform route reselection or IP domain switching. The roaming number can be reacquired before routing reselection.

In the above system, the detection module and the detection information reporting module can be set in the MGW, and the routing control module can be set in the MGC, corresponding to the solution of the fifth method described in the flow shown in FIG. 2, The specific operation process can also be consistent with the operation of the fifth method described in the flow shown in FIG. 1.

The internal structure of the MGW in the embodiment of the present invention may be as shown in FIG. 9 , and includes: a detection module and a detection information reporting module.

The detecting module is configured to detect an IP bearer of the link that is connected to the peer end by the MGW, and the detecting information reporting module is configured to report the detecting information to the media gateway controller according to the detection result of the detecting module.

In the specific implementation, the detection module and the detection information reporting module can have various forms.

For example, the detection module can include a statistics module and a result determination module.

At this time, the detection information reporting module can perform a call to the IP address subsequent to the IP bearer detection result of an IP address, according to the degree of congestion or failure, according to the degree of congestion or failure. Sending a bearer release indication message carrying a cause identifier indicating that the IP link is unreachable to the routing control module. Specifically, the information generating module and the information reporting module may be included.

The information generating module is configured to generate, according to the degree of congestion or fault, a bearer release indication message carrying a cause identifier indicating that the IP link is unreachable according to the degree of congestion or fault when the detection result is that there is congestion or a fault.

The information reporting module is configured to report the bearer release indication message carrying the cause identifier indicating that the IP link is unreachable.

At this time, corresponding to the scheme of the first method described in the flow shown in Fig. 2, the specific operation procedure of each module can also be consistent with the operation of the first method described in the flow shown in Fig. 1.

For example, the detection module may include: a detection execution module, configured to perform statistics on a packet loss rate of an IP bearer that indicates an MGC, or a packet loss rate, jitter, and delay of an IP bearer that is instructed by the MGC, according to a packet loss rate or a loss rate. The packet rate, jitter and delay values and the preset threshold value detect whether the IP bearer is congested or faulty.

At this time, the detection information reporting module sends a notification message carrying the quality of service level to the routing control module when the detection result is that there is congestion or failure. The specific implementation may include: an information generating module and an information reporting module.

The information generating module is configured to generate a notification message carrying a service quality level when the detection result is that there is congestion or a fault.

The information reporting module is configured to report the notification message carrying the quality of service level.

At this time, corresponding to the scheme of the second method described in the flow shown in Fig. 2, the specific operation procedure of each module can also be consistent with the operation of the second method described in the flow shown in Fig. 1.

For example, the detecting module may include: a state detecting module, configured to obtain, according to the state of the IP port, whether the IP bearer is congested or faulty.

At this time, the detection information reporting module receives the response when the detection result is that there is congestion or failure.

When the MGC initiates a call and asks the MGW to allocate IP resources on the IP port, it reports a response message indicating that the bearer is interrupted to the routing control module. The specific implementation may include: an information generating module and information Report module.

The information generating module is configured to receive, when the detection result is that there is congestion or failure,

When the MGC initiates a call and asks the MGW to allocate IP resources on this IP port, it generates a response message indicating that the bearer is interrupted.

The information reporting module is configured to report the response message indicating that the bearer is interrupted.

At this time, corresponding to the scheme of the fourth method described in the flow shown in Fig. 2, the specific operation procedure of each module can also be consistent with the operation of the fourth method described in the flow shown in Fig. 2.

For another example, the detecting module may include: a state detecting module, configured to obtain, according to a result of the user plane negotiation process, whether the IP bearer is congested or faulty.

At this time, when the negotiation information reporting module determines that the negotiation process exceeds the set duration, the detection information reporting module reports a bearer release indication message indicating that the negotiation process fails. The specific implementation may include: an information generating module and an information reporting module.

The information generating module is configured to: when determining that the negotiation process exceeds the set duration, generate a bearer release indication message indicating that the negotiation process fails.

The information reporting module is configured to report the bearer release indication message indicating that the negotiation process fails.

At this time, corresponding to the scheme of the fifth method described in the flow shown in Fig. 2, the specific operation procedure of each module can also be consistent with the operation of the fifth method described in the flow shown in Fig. 2.

In addition, the MGC in the embodiment of the present invention includes: a routing control execution module, configured to obtain a detection result of an IP bearer, and perform call routing control according to the detection result of the IP bearer. .

In a specific implementation, corresponding to the solution of the first method described in the process shown in FIG. 2, the route control execution module may include: an information receiving module and a routing control module.

The information receiving module is configured to receive a bearer release indication message carrying a cause identifier indicating that the IP link is unreachable.

The routing control module is configured to carry an original that indicates that the IP link is unreachable according to the information received by the information receiving module. The call corresponding to the message is route reselected or IP domain switched due to the identified bearer release indication message.

Corresponding to the solution of the second method described in the flow shown in FIG. 2, the routing control execution module may include: an information receiving module and a routing control module.

The information receiving module is configured to receive a notification message carrying a quality of service level.

The routing control module is configured to perform routing reselection or IP domain switching on part or all of the calls to the peer according to the quality of service level in the notification message received by the information receiving module.

Corresponding to the solution of the third method described in the flow shown in FIG. 2, the media gateway controller further includes: a statistics module and a result determination module.

The statistics module is configured to perform statistics on the connection rate or the call loss rate of the IP bearer to the peer end. The result determining module is configured to determine whether the IP bearer is congested or faulty according to the connection rate or the call loss rate obtained by the statistics module, and the preset connection rate threshold or the call loss rate threshold.

In addition, the routing control execution module includes: a routing control module, configured to: when the detection result determined by the result determining module is that there is congestion or a fault, issue alarm information, and perform traffic sharing between routes or traffic switching between routes , or perform an IP domain switch.

Corresponding to the solution of the fourth method described in the flow shown in FIG. 2, the route control execution module may include: an information receiving module and a route control module.

The information receiving module is configured to receive a response message indicating that the bearer is interrupted.

The routing control module is configured to perform routing reselection or IP domain switching according to the response message received by the information receiving module indicating that the bearer is interrupted.

Corresponding to the solution of the fifth method described in the flow shown in FIG. 2, the routing control execution module may include: an information receiving module and a routing control module.

The information receiving module is configured to receive a release indication message indicating that the negotiation process fails.

The routing control module is configured to end the establishment process of the current bearer according to the release indication message received by the information receiving module, indicating that the negotiation process fails, and perform route reselection or IP domain switching. The roaming number can be reacquired before routing reselection. The implementation system of the routing control provided by the embodiment of the present invention detects the IP bearer of the link connected with the MGW, and performs call routing control according to the detection result. Therefore, when the IP bearer of the link connected to the MGW is faulty or congested, the route can be connected in time to improve the service performance of the network.

A person skilled in the art can understand that all or part of the steps of implementing the foregoing embodiments can be completed by a program instructing related hardware, and the program can be stored in a computer readable storage medium, the storage. Media, such as: R0M/RAM, disk, CD, etc.

The above described specific embodiments of the present invention are further described in detail, and it is to be understood that the foregoing description is only the preferred embodiments of the present invention The scope of the present invention is intended to be included within the scope of the present invention. Any modifications, equivalents, improvements, etc., are included in the scope of the present invention.

Claims

Claim

A method for implementing route control, comprising:

The media gateway MGW detects the inter-network interconnection protocol IP bearer of the link connected to the peer end; and performs call routing control according to the obtained detection result.

The method for implementing the routing control according to claim 1, wherein the detecting, by the media gateway MGW, the inter-network interconnection protocol IP bearer of the link connected to the peer end comprises: IP address or IP bearer of the network segment is detected;

According to the obtained detection result, the call routing control includes: when the media gateway MGW detects that the IP bearer is congested or faulty, the subsequent call to the IP address or the network segment is proportional according to the degree of congestion or fault. Sending, by the media gateway controller MGC, a message carrying a cause identifier indicating that the IP link is unreachable; the media gateway controller MGC performs routing reselection on the call corresponding to the message according to the message carrying the cause identifier indicating that the IP link is unreachable. IP domain switching.

The method for implementing the routing control according to claim 2, wherein the method further comprises: when the media gateway MGW detects that the IP bearer is recovered by congestion or failure, and subsequently calls the IP address, according to the call The degree of recovery reduces the proportion of messages sent to the Media Gateway Controller MGC that carry a cause indication indicating that the IP link is unreachable.

The method for implementing the routing control according to claim 2 or 3, wherein the media gateway MGW detects the IP bearer to the peer IP address or the network segment as: The media gateway MGW pairs to the peer IP Check the packet loss rate of the address, or the packet loss rate, delay, and jitter of the peer IP address. Check whether the IP bearer is congested according to the packet loss rate or packet loss rate, delay and jitter value, and the preset threshold. Or fault; or

The media gateway MGW detects the IP bearer to the peer IP address or the network segment as follows: The media gateway MGW counts the call loss rate caused by the unreachable IP address of the peer end, according to the call loss rate and the preset call loss. The rate value detects whether the IP bearer is congested or faulty.

The method for implementing the routing control according to claim 1, wherein the detecting, by the media gateway MGW, the inter-network interconnection protocol IP bearer of the link connected to the peer end is: the media gateway controller The MGC sends a call indication for the IP bearer detection to the media gateway MGW, and the media gateway MGW counts the packet loss rate of the IP bearer of the call or the packet loss rate, jitter, and delay of the IP bearer of the call, according to the packet loss. Rate or packet loss rate, jitter and delay value, and preset threshold to detect whether the IP bearer is congested or faulty;

According to the obtained detection result, performing call routing control includes: sending a message carrying a quality of service level to the media gateway controller MGC when detecting that the IP bearer is congested or faulty; the media gateway controller MGC according to the message The quality of service level controls the reselection or IP domain switching of some or all of the calls to the peer.

The method for implementing the routing control according to claim 5, wherein the method further comprises: when the media gateway MGW detects that the IP bearer is restored by congestion or failure according to the indication of the media gateway controller MGC, and sends the packet to the MGC. The message carrying the quality of service recovery, the media gateway controller MGC receives the message carrying the quality of service recovery, and restores the original routing control.

The method for implementing the routing control according to claim 1, wherein the detecting, by the media gateway MGW, the inter-network interconnection protocol IP bearer of the link connected to the peer end is: the local media gateway controller MGC Counting the connection rate of the IP bearer to the peer end, and detecting whether the IP bearer is congested or faulty according to the connection rate and the preset connection rate threshold; or

The network gateway MGW of the link between the media gateway MGW and the peer end is detected as follows: The local media gateway controller MGC collects the connection rate of the IP bearer to the peer end, according to the statistics of the connection rate. As a result, the call loss rate is obtained, and whether the IP bearer is congested or faulty is detected according to the call loss rate and the preset call loss rate threshold;

According to the obtained detection result, the call routing control includes: when the media gateway controller MGC detects that the IP bearer is congested or faulty, performs traffic sharing between routes or traffic switching between routes, or performs IP domain switching. .

The method for implementing the routing control according to claim 1, wherein the detecting, by the media gateway MGW, the inter-network interconnection protocol IP bearer of the link connected to the peer end is: the local media gateway MGW according to the present invention The status of the end IP port directly obtains whether the IP bearer is congested or faulty. According to the obtained detection result, performing call routing control includes: when detecting that the IP bearer is congested or faulty, the media gateway MGW receives the call initiated by the media gateway controller MGC and requests the media gateway MGW to allocate the IP port. The IP resource returns a response message indicating the bearer interruption to the media gateway controller MGC; the media gateway controller MGC performs route reselection or IP domain switching according to the response message.

The method for implementing the routing control according to claim 8, wherein the method further comprises: when the IP port is restored by congestion or failure, the media gateway MGW receives the call initiated by the media gateway controller MGC and requests the media. When the gateway MGW allocates IP resources on this IP port, it returns a response message indicating success and continues the call.

The method for implementing the routing control according to claim 1, wherein the detecting, by the media gateway MGW, the inter-network interconnection protocol IP bearer of the link connected to the peer end is: according to the result of the user plane negotiation process , whether there is congestion or failure of the IP bearer;

According to the obtained detection result, the call routing control includes: the local media gateway MGW reports a message indicating that the negotiation process fails to the local media gateway controller MGC when determining that the negotiation process exceeds the set duration; the local media gateway The controller MGC receives the message indicating that the negotiation process fails, ends the establishment process of the current bearer, and performs route reselection or IP domain switching.

The method for implementing the routing control according to claim 10, further comprising: re-acquiring the roaming number before performing the routing reselection.

12. A system for implementing route control, comprising:

The system for implementing the routing control according to claim 12, wherein the detecting module comprises:

The statistics module is configured to perform statistics on packet loss rate or packet loss rate, jitter and delay, or call loss rate to the peer IP address; a result determining module, configured to determine, according to a packet loss rate or a packet loss rate, a jitter and a delay or a call loss rate, and a preset threshold value, whether the IP bearer is congested or faulty; the routing control process Modules include:

The detection information reporting module is configured to send a call indicating that the IP link is unreachable to the routing control module according to the degree of congestion or fault when the detection result is that there is congestion or a fault. News

The routing control module is configured to perform routing reselection or IP domain switching on the call corresponding to the message according to the message carrying the reason indicating that the IP link is unreachable.

The system for implementing the routing control according to claim 13, wherein the statistics module, the result determining module, and the detecting information reporting module are disposed in the media gateway MGW, and the routing control module is disposed in the media gateway. Controller MGC.

a detection indication module, configured to send a call indication for performing IP bearer detection to the detection execution module, and a detection execution module, configured to use a packet loss rate of the IP bearer of the call or a packet loss rate, jitter, and an IP bearer of the call The delay is counted, and whether the IP bearer is congested or faulty is detected according to the packet loss rate or the packet loss rate, the jitter and the delay value, and the preset threshold.

The route control processing module includes:

a detection information reporting module, configured to send a message carrying a quality of service level to the routing control module when the detection result is that there is congestion or failure;

The routing control module is configured to perform routing reselection or IP domain switching on part or all of the calls to the peer according to the quality of service level in the message.

The implementation system of the routing control according to claim 15, wherein the detection indication module and the routing control module are disposed in a media gateway controller MGC, and the detection execution module and the detection information are reported. The module is set in the media gateway MGW.

17. The system of implementing routing control according to claim 12, wherein said detecting mode The block includes:

The statistics module is configured to perform statistics on the connection rate or the call loss rate of the IP bearer to the peer end;

a result determining module, configured to determine whether the IP bearer is congested or faulty according to a connection rate or a call loss rate obtained by the statistics module, and a preset connection rate threshold or a call loss rate threshold;

The route control processing module includes:

The system for implementing the routing control according to claim 17, wherein the statistical module, the result determining module, and the routing control module are disposed in the media gateway controller MGC.

The system for implementing the routing control according to claim 12, wherein the detecting module comprises: a state detecting module, configured to obtain, according to the state of the IP port, whether the IP bearer is congested or faulty;

The route control processing module includes:

The detecting information reporting module is configured to report the indication bearer to the routing control module when receiving the call initiated by the media gateway controller MGC and requesting the media gateway MGW to allocate the IP resource on the IP port when the detection result is that the congestion or the fault occurs. Interrupted response message;

The implementation system of the routing control according to claim 19, wherein the status detecting module and the detecting information reporting module are disposed in the media gateway MGW, and the routing control module is disposed in the media gateway controller MGC.

The system for implementing the routing control according to claim 12, wherein the detecting module comprises: a state detecting module, configured to obtain, according to a result of the user plane negotiation process, whether the IP bearer is congested or faulty;

The route control processing module includes:

The detection information reporting module is configured to perform routing control when determining that the negotiation process exceeds the set duration The module reports a message indicating that the negotiation process has failed;

The routing control module is configured to end the establishment process of the current bearer according to the message indicating that the negotiation process fails, and perform route reselection or IP domain switching.

The implementation system of the routing control according to claim 21, wherein the detection module and the detection information reporting module are disposed in the media gateway MGW, and the routing control module is disposed in the media gateway controller MGC.

23. A media gateway, comprising:

The detecting module is configured to detect the IP bearer of the link connected to the peer end of the media gateway MGW, and the detecting information reporting module is configured to report the detecting information to the media gateway controller MGC according to the detection result of the detecting module.

The media gateway according to claim 23, wherein the detecting module comprises: a statistics module, configured to perform packet loss rate or packet loss rate, jitter and delay, or call loss rate to the peer IP address Conduct statistics;

a result determining module, configured to determine, according to a packet loss rate or a packet loss rate, a jitter and a delay, or a call loss rate, and a preset threshold value, whether the IP bearer is congested or faulty; and the detecting information is reported Modules include:

The information generating module is configured to: when the detection result is that there is a congestion or a fault, the call that subsequently occurs to the IP address is proportionally generated according to the degree of congestion or the fault, and the message indicating the cause identifier indicating that the IP link is unreachable is generated;

The information reporting module is configured to report the message carrying the cause identifier indicating that the IP link is unreachable.

The media gateway according to claim 23, wherein the detecting module comprises: a detecting execution module, configured to indicate, to the media gateway controller MGC, a packet loss rate of the IP bearer of the call or a media gateway controller MGC indication The packet loss rate, jitter, and delay of the IP bearer of the call are counted, and whether the IP bearer is congested or faulty is detected according to the packet loss rate or the packet loss rate, the jitter and the delay value, and the preset threshold. The detection information reporting module includes:

An information generating module, configured to generate a message carrying a quality of service level when the detection result is that there is congestion or a fault;

The information reporting module is configured to report the message carrying the quality of service level.

The media gateway according to claim 23, wherein the detecting module comprises: a state detecting module, configured to obtain, according to a state of the IP port, whether the IP bearer is congested or faulty;

The detection information reporting module includes:

The information generating module is configured to: when receiving the call initiated by the media gateway controller MGC and requesting the media gateway MGW to allocate the IP resource on the IP port, if the detection result is that there is congestion or a fault, generate a response message indicating that the bearer is interrupted;

The media gateway according to claim 23, wherein the detecting module comprises: a state detecting module, configured to obtain, according to a result of the user plane negotiation process, whether the IP bearer is congested or faulty;

The detection information reporting module includes:

An information generating module, configured to generate a message indicating that the negotiation process fails when determining that the negotiation process exceeds the set duration;

The information reporting module is configured to report the message indicating that the negotiation process fails.

28. A media gateway controller, comprising:

The media gateway controller according to claim 28, wherein the routing control execution module comprises:

An information receiving module, configured to receive a message carrying a cause identifier indicating that the IP link is unreachable, and a routing control module, configured to receive, according to the information receiving module, an original that indicates that the IP link is unreachable The route corresponding to the message is route reselected or IP domain switched due to the identified message.

An information receiving module, configured to receive a message carrying a quality of service level;

The routing control module is configured to perform routing reselection or IP domain switching on part or all of the calls to the peer according to the quality of service level in the message received by the information receiving module.

The media gateway controller according to claim 28, further comprising: a statistics module, configured to perform statistics on a connection rate or a call loss rate to the peer IP bearer;

The routing control execution module includes: a routing control module, configured to: when the detection result determined by the result determining module is that there is congestion or a fault, issue alarm information, and perform traffic sharing between routes or traffic switching between routes , or perform IP domain switching.

An information receiving module, configured to receive a response message indicating that the bearer is interrupted;

The routing control module is configured to perform route reselection or IP domain switching according to the response message received by the information receiving module indicating that the bearer is interrupted.

An information receiving module, configured to receive a message indicating that the negotiation process fails;

The routing control module is configured to end the current bearer establishment process according to the received message indicating that the negotiation process fails, and perform route reselection or IP domain switching.