WO2007137515A1

WO2007137515A1 - The method for mgc obtaining the bearer status, mgw, mgc and the system thereof

Info

Publication number: WO2007137515A1
Application number: PCT/CN2007/070011
Authority: WO
Inventors: Ming Kang; Jie Li
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2006-05-11
Filing date: 2007-05-11
Publication date: 2007-12-06

Abstract

The method for MGC obtaining the bearer status, MG, MGC and the system thereof. The method includes: firstly, MGW determines the status of the bearer interface and transmits it to MGC; then MGC receives and obtains the bearer interface status which has changed and adjusts the MGW policy according to the obtained status information flexibly. The present invention enables MGC to obtain the status information of the bearer interface corresponding to each bearer channel within MGW which connects with multiple bearer entities, so that MGC can adjusts the policy for selecting MGW according to the obtained status information flexibly, and the availability of the network resource within the network framework in which the bearer and control are separated can be improved.

Description

Instruction manual

Method for obtaining bearer status by media gateway controller, media gateway and media gateway control and system

[1] Technical field

[2] The present invention relates to the field of network communication technologies, and in particular, to a technical solution for realizing state synchronization between a media gateway and a media gateway controller.

[3] Background of the invention

[4] Under the softswitch architecture with separate bearer and control, the circuit domain core network includes (G) MSC

Server (gate mobile switching center server) and MGW (media gateway), described (G) MSC

The interface between Server and MGW is called the Mc interface.

[5] Under the above softswitch architecture, the (G) MSC

The server is used to complete call control and mobility management, and the MGW is used to perform bearer control and bearer transmission and media stream maintenance functions. Moreover, the (G) MSC

The server uses the H.248 message to complete the bearer control of the MGW through the Mc interface, and the MGW reports the bearer resource related information to the (G) MSC Server through the Mc interface.

[6] Taking the UMTS (Universal Mobile Telecommunications System) / GSM (Global System for Mobile Communications) network as an example, as shown in Figure 1, under the network architecture with bearer control, the call control channel and the bearer channel are all from the same network. The processing is performed such that, for the case where the state between the call control channel and the bearer channel that may occur is inconsistent (for example, the call control channel is available and the bearer channel is unavailable), since the MSC participates in the management of the bearer state, The MSC can discriminate between the states and take corresponding measures.

[7] However, under the bearer control separation architecture, as shown in Figure 2, due to the separation of the call control channel and the bearer channel, at this time, if the above state is inconsistent, if (G) MSC

Server needs to correct the inconsistency between the states, you must know the status information of the bearer channel.

[8] In Figure 2, the bearer channel may be ATM (Asynchronous Transfer Mode) (or ATM over

El ) or IP (or IP over

El) type. For ATM and IP bearer modes, gateway reporting capability changes are currently provided (event, Implementation of signals, media, etc.). Through this implementation, the change of media capabilities of the entire gateway can be known in time.

[9] In the ATM and IP bearer modes, as shown in Figure 3, when the MGW is connected to only one peer bearer entity

(ie, MGW2 in FIG. 3), the state synchronization problem of the bearer channel and the control channel can be solved by using the implementation scheme of the reporting capability change.

[10] However, in the two bearer modes of ATM and IP, when the MGW is connected to multiple peer bearer entities (such as M in Figure 3)

In the case of GW1, or MGW in Fig. 4, the state of the bearer channel cannot be accurately updated by the above implementation.

[11] Still taking FIG. 3 as an example, it is assumed that the bearer interface between the MGW1 and the RNC/IP-BSC in FIG. 3 is faulty, and the bearer channel cannot work normally, but the bearer between MGW1 and MGW3 is normal, that is, MGW1 and MGW3. The bearer channel between the MGW1 and the MGW3 will be used. The MGW1 will directly report the corresponding MGW1 bearer capability invalidation information to the MSC. The bearer resources that can be used between the MGW1 and the MGW3 will also be unavailable.

[12] Moreover, as shown in FIG. 4, since the MGC generally uses the round-robin method to determine the MGW for the bearer in the prior art, then the MGW and the network entity directly connected to the optional bearer path are When the connection status changes, it may still be determined by the MGC as the MGW for the bearer, which may result in call loss. For example, the connection between the MGW-1 and the wireless access side device has failed, and the signal cannot be received normally. However, if a user terminal under the wireless access side device initiates a call and the MGC receives the call setup request message, the MGC needs to determine the MGW for carrying the current call. If the current bearer task should be assumed by the MGW-1 in the order of the round robin, the MGC will determine that the MGW-1 is the MGW for the bearer, and then control the bearer between the MGW-1 and the radio access side device. However, in fact, since the connection between the MGW-1 and the wireless access side device has failed, it is impossible to complete the task of the call, resulting in the loss of the call.

[13] Therefore, it is not difficult to see that the notification mechanism that implements the change of bearer status by using the foregoing implementation scheme may cause serious waste of bearer resources, so that limited network resources are not utilized reasonably, and call loss may occur.

[14] Summary of the invention

[15] Embodiments of the present invention provide a method for a media gateway controller to acquire a bearer state, a media gateway, and a media gateway controller and system, so that a reasonable management of the softswitch network with separate bearer control can be implemented. Use limited network resources.

An embodiment of the present invention provides a method for implementing a media gateway controller to manage a bearer, including: [17] the media gateway determines a bearer interface state, and sends the status to the media gateway controller;

[18] The media gateway controller receives the bearer interface status of the media gateway, and obtains a corresponding bearer status.

An embodiment of the present invention provides a method for implementing resource scheduling, including:

[20] The media gateway controller obtains the bearer interface status of each bearer interface sent by the media gateway, and adjusts the policy of selecting the media gateway according to the state of the bearer interface.

[21] The embodiment of the present invention provides a media gateway, including a bearer interface status sending unit, configured to report the status of the bearer interface of the at least one bearer interface in the media gateway to the media gateway controller.

[22] The embodiment of the present invention provides a media gateway controller, including a bearer interface state obtaining unit, configured to receive and obtain status information of a bearer interface sent by a media gateway, and determine a corresponding bearer state.

[23] The embodiment of the present invention provides a system for acquiring a bearer status by a media gateway controller, including:

[24] The media gateway is responsible for sending the bearer interface status to the media gateway controller;

[25] The media gateway controller receives and obtains the status of the bearer interface sent by the media gateway.

[26] An embodiment of the present invention provides an apparatus for implementing resource scheduling, where the apparatus is configured in a media gateway controller.

And including a bearer interface state obtaining unit and a scheduling policy control unit, where:

[27] The bearer interface state obtaining unit is configured to obtain a bearer interface state of each bearer interface in the media gateway; [28] a scheduling policy control unit, configured to adjust a policy of selecting a media gateway according to the state of the bearer interface.

[29] It can be seen from the technical solutions provided by the foregoing embodiments of the present invention that, in the embodiment of the present invention, the MGW can be sent to the MGC.

Reporting the connection status change between the directly connected network entities on the bearer path. Therefore, the MGC can determine the connection status of the MGW for the bearer, so that the MGC can be used to the MGW.

The effective management of the bearer can avoid call loss and improve the utilization of network resources.

[30] BRIEF DESCRIPTION OF THE DRAWINGS

[31] FIG. 1 is a schematic diagram of a network architecture of bearer control integration;

[32] Figure 2 is a schematic diagram of a network architecture for bearer control separation;

[33] FIG. 3 is a schematic diagram of a network structure of a base station controller connecting multiple MGWs;

4 is a schematic structural view of a typical MINI-IU-FLEX network in the prior art; [35] FIG. 5a is a schematic structural diagram of a network in which a base station controller connects multiple MGWs according to an embodiment of the present invention;

FIG. 5b is a schematic structural diagram of a network in which an MGW is connected to multiple base station controllers according to an embodiment of the present invention; FIG.

6 is a schematic diagram of an implementation process of Embodiment 1 of a method according to an embodiment of the present invention;

FIG. 7 is a schematic diagram of an implementation process of Embodiment 2 of a method according to an embodiment of the present invention; FIG.

FIG. 8 is a schematic diagram of an implementation process of Embodiment 3 of the method according to the embodiment of the present invention; FIG.

FIG. 9 is a schematic structural diagram of an embodiment of a system according to an embodiment of the present invention.

FIG. 10 is a schematic structural diagram of a system according to an embodiment of the present invention; FIG.

FIG. 11 is a schematic diagram of a processing procedure of a method according to an embodiment of the present invention; FIG.

[43] Mode for carrying out the invention

The embodiments of the present invention will be further described in detail below with reference to the drawings and specific embodiments.

[45] In the embodiment of the present invention, as shown in FIG. 5a and FIG. 5b, the MGW is connected to multiple peer bearer entities, and at least one bearer interface uses ATM, IP bearer mode, or ATM or IP over.

The network structure of the non-TDM bearer mode, such as the TDM (TDM, time division multiplexing) bearer mode, can also synchronize the state of the control channel and the bearer channel, thereby solving the problem that the bearer and the control state are inconsistent, and can effectively avoid wasteful networking. Internet resources.

In the embodiment of the present invention, the MGC may be a media gateway controller (G) MSC in a bearer control separation architecture in a UMTS/GSM network.

SERVER, which can also be a media gateway controller MSCe (emulated mobile switching center) under the bearer control separation architecture in a CDMA (Code Division Multiple Access) network, can also be other MGC-like entities in the network.

Embodiments of the present invention are applicable to a CDMA network, an NGN (Next Generation Network) or a UMTS/GSM network, and the like.

In the embodiment of the present invention, the MGW may specifically notify the status of the ATM and the IP bearer interface (ie, the connection state) on the MGC gateway through the H248 message, and carry the bearer interface identifier, which may include, but is not limited to, the following messages. At least one notification of the status of the changed bearer interface:

[49] (1) The MGW reports the status change of the bearer interface to the MGC by using the service change descriptor to carry the bearer interface identifier.

[50] (2) The MGC obtains the bearer interface status of the MGW through auditing;

[51] (3) The MGC obtains the state change of the bearer interface of the MGW through the event detection mode. [52] After the MGC obtains the state information of the bearer interface sent by the MGW, if the status of the bearer interface of the MGW to a peer bearer entity changes, for example, the state of an interface changes from the working state to the fault state (or After the fault state is changed to the working state, the MGC adjusts the policy selected by the media gateway after acquiring the state change information of the bearer interface, and no longer selects the bearer channel corresponding to the bearer interface that has failed (or chooses to restore normal) to transmit data.

[53] In order to facilitate the understanding of the embodiments of the present invention, the specific implementations of several application embodiments will be described in detail below with reference to the accompanying drawings. In the various implementations provided below, various implementations can be used simultaneously. Various implementations can also be used independently.

[54] Implementation of the first implementation provided

[55] In this implementation, the MGW actively notifies the bearer status information to the softswitch MGC through the H248 message, where the notification needs to include the bearer interface identifier, and the message used for the active notification may be Service Change, or Is other news.

[56] As shown in Figure 6, to use Service

Change is used as a notification message. The corresponding processing includes:

[57] (1) The MGW reports a bearer interface failure:

[58] Step 51: The MGW sends a service change request to the MGC Service Change

The Req command carries the bearer interface identifier information.

[59] In this embodiment, by Service

The change descriptor (the parameter set of the ServerChange command protocol) is extended, and the peer bearer entity for indicating the MGW connection or the parameter used by the MGC to uniquely identify a bearer interface in the MGW is given in the ServiceChange descriptor. The parameter may be a signaling point code of the opposite bearer entity, a device identifier, or some identifier that the MGC and the MGW can mutually understand and recognize;

[60] The parameters described therein may be, but are not limited to, the following representations:

[61] For ATM bearer devices, the device ATM address/interface can be used;

[62] RNC ID (RNC logo) can be used for RNC (Radio Network Controller);

[63] For an IP bearer device, you can use the device IP address identifier and the device IP interface identifier.

[64] For MGW, BCU can be used

ID; or the bearer direction identifier set according to the network topology, such as office direction; [65] Wait.

[62] Step 52: After receiving the command, the MGC obtains the bearer interface status reported by the MGW, and then notifies the MGW that the MGW has received the bearer interface fault information by using the service change response Service Change Rsp command.

[67] (2) MGW reporting bearer interface failure recovery:

[68] Step 53: The MGW sends a Service Change to the MGC

The Req command also carries the bearer interface identification information in the command;

[69] In this step, the manner in which the bearer interface identifier information is carried by the command is the same as that described in step 51, and therefore is not described in detail herein.

[70] Step 54: After receiving the command, the MGC obtains the fault recovery information of the bearer interface reported by the MGW, and then

MGW sends Service Change

The Rsp command is used to notify the MGW that it has received the bearer interface failure recovery information.

[71] The second implementation provided by the second embodiment

[72] Since the bearer interface belongs to the concept of a gateway hierarchy, in this implementation, the definition is extended by H.

The ROOT packet attribute of the 248 is added with a list of attributes indicating the status of the bearer interface of the gateway, so that the status of the bearer interface status is implemented between the MGW and the MGC.

[73] As shown in Figure 7, the process of the MGC auditing the MGW to obtain the status of the bearer interface includes:

[74] Step 61: MGC sends audit parameter request Audit Value

The Req message is sent to the MGW, and the message carries the bearer interface state, which is used to indicate that the MGC needs to obtain the bearer interface state of the bearer interface state;

[75] Step 62: The MGW receives the stated Audit Value

After the Req message, return the audit parameter response to the MGC Audit Value

The Rsp message carries the bearer interface state list information that the MGC needs to obtain in the response message, so that the MGC obtains the corresponding bearer interface state information.

[76] Through the audit for this attribute shown in Figure 7, the MGC can reliably obtain the status information of the bearer interface of the gateway.

[77] The third implementation provided in Embodiment 3

[78] In this implementation, the event detection method of the H.248 protocol is used to obtain the status information of the bearer interface by using the event detection mode. [79] Specifically, the bearer state change detection packet may be used to complete the detection of the bearer state of the gateway or the endpoint. When the bearer state of the gateway is changed, the MGW reports the bearer state change event to the MGC, thereby implementing the MGC on the MGW. Management of the bearer status.

[80] Of course, other methods of event detection can also be used to achieve the corresponding purpose.

[81] As shown in FIG. 8, the process of obtaining the status of the bearer interface by detecting the change of the bearer status of the gateway includes:

[82] Step 71: MGC sends a modification request to the MGW Mod

Req message, the message indicates that the message is used to transmit a bearer state change detection event;

[83] Step 72: After receiving the bearer status change detection event sent by the MGC, the MGW returns a modification response to the MGC. Mod

Rsp message;

[84] After performing the above steps 71 and 72, when the state of the bearer interface of the MGW changes, that is, when the state of the bearer channel changes, step 73 is performed;

[85] Step 73: The MGW sends a notification request to the MGC Notify

The Req message carries a bearer status change event, that is, a bearer interface identifier whose bearer status changes and its corresponding bearer interface status information;

[86] Step 74: MGC receives the Notify as described

After the Req message, the changed MGW bearer interface state information is obtained, and a notification response Notify Rsp message is also returned to the MGW, so that the MGW can know that the MGC has been accurately known.

The corresponding bearer interface state change information.

[87] Through the above three specific implementation schemes, the MGC can obtain the state information of the bearer interfaces of each MGW in a timely and accurate manner, thereby facilitating the synchronization of the state of the bearer channel and the control channel in the network architecture with separate bearer and control. It is beneficial to the effective management of each bearer channel resource and control channel resources.

An embodiment of the present invention provides an embodiment of the method for implementing the resource scheduling, and the processing provided by the embodiment includes:

[89] First, the media gateway controller obtains the state of the bearer interface, and the implementation manner of obtaining the state of the bearer interface has been described in detail above, and is not described in detail herein;

[90] Then, the media gateway controller adjusts the policy of selecting the media gateway according to the acquired status of the bearer interface.

, that is, adjusting the scheduling application policy of the network resource, for example, when the media gateway controls and a certain media gateway If the bearer channel fails, only the use of the bearer channel is stopped. For other bearer channels that do not have an abnormality, the service communication is still normally used, thereby improving the rationality of resource utilization.

[91] The embodiment of the present invention further provides a system for acquiring a bearer state by a media gateway controller, and a specific implementation structure of the system embodiment is shown in FIG. 9, which includes:

[92] (1) Media Gateway

[93] The bearer interface status sending unit is configured to report the status of the bearer interface of the at least one of the media interfaces to the media gateway controller. The media gateway may further include a bearer interface state monitoring unit, configured to monitor a change of the bearer interface state of the media gateway to which the at least one bearer entity is connected, and send the changed bearer interface state to the media by using the bearer interface state sending unit. The gateway controller, that is, used to send the status of the bearer interface in the media gateway connected to the multiple bearer entities to the media gateway controller, where the multiple bearer entities include working in ATM and/or IP bearer mode. Carrying entity

[94] The bearer interface status sending unit may be any one or more of the following units:

[95] (1) A bearer interface state sending unit that is configured to send a bearer interface state to the media gateway controller by actively carrying the bearer interface identifier by using a service change manner;

[96] (2) The bearer interface status sending unit based on the auditing operation is configured to send the status of the bearer interface to the media gateway controller in an auditing manner according to the information sent by the media gateway controller, including the specificity of the bearer interface identifier and the bearer interface. status information;

[97] (3) A bearer interface status sending unit, configured to send a bearer interface status, including a bearer interface identifier and a bearer interface, to the media gateway controller by means of event detection according to the information sent by the media gateway controller. Specific status information.

[98] (2) Media Gateway Controller

[99] A media interface controller is configured with a bearer interface state obtaining unit, which is configured to receive and obtain a bearer interface state of each bearer interface sent by the media gateway, so as to obtain a corresponding bearer interface state, so as to facilitate network resources. Schedule the app.

[100] When the media gateway includes the unit described in (2) or (3) above, the media gateway controller further includes the following corresponding units:

[101] Acquiring a bearer interface state initiating unit based on an audit operation, for using an auditing manner to a media gateway Sending a request to obtain information about the status of the bearer interface, such as sending an audit request message, where the message carries the bearer interface identifier that needs to obtain the state information;

[102] The acquisition bearer interface state initiating unit is configured to send, by means of event detection, information to the media gateway to obtain the status of the bearer interface, such as sending an event detection request message, where the message carries the status information that needs to be acquired. Bearer interface identifier.

[103] Through the above system, the media gateway controller can obtain status information of the corresponding bearer channel in the media gateway.

According to the status information, the media gateway controller can control the policy of selecting the media gateway, for example, selecting a media gateway that exists in the working state bearer channel.

An embodiment of the present invention further provides an apparatus for implementing resource scheduling, where the apparatus is specifically configured with a media gateway controller, and includes a bearer interface state acquiring unit and a scheduling policy control unit, where: [105] An interface state obtaining unit, configured to acquire the state of the bearer interface;

[106] The scheduling policy control unit is configured to adjust the policy of selecting the media gateway according to the state of the bearer interface acquired by the bearer interface state acquiring unit, that is, adjusting to apply only the media gateway with the normal bearer interface status to perform service communication, thereby ensuring network resources. Reasonable scheduling application.

[107] It can be seen that, in the embodiment of the present invention, the MGC can learn the MGW connection status, and can determine that the connection status is normal according to the learned connection status of the MGW (for example, according to the connection status table for recording the MGW connection status). The MGW is to use the MGW whose connection state is normal as the MGW for the bearer.

Specifically, in the embodiment of the present invention, a connection status table for recording the MGW connection status may be set in the MGC in advance, and all the MGWs connected to the MGC and the wireless access side device are recorded in the connection status table. Medium, and set the connection status initial value to normal.

In the embodiment of the present invention, the MGW recorded in the connection state table determines whether the connection state of the network entity directly connected to the optional bearer path changes in real time, and if the change occurs, the MGC reports that the connection is carried. The connection status change request message of the status change condition, and the MGC updates its own connection status table in real time according to the message. Thereafter, the MGC can select an MGW with a normal connection state as the MGW for the bearer according to the connection state table.

[110] The connection state change described here includes two cases: one case where the connection state changes from normal to failure, and the other case to transition from failure to normal.

[111] In actual application, the network entity directly connected to the MGW and the optional bearer path may be a packet connection mode. That is, the ATM connection mode or the IP mode. The port between the network entity directly connected to the optional bearer path on the MGW is an ATM port or an IP port. The MGW can detect whether the signal of the ATM port or the IP port is normal according to the physical layer protocol. If the received signal is interrupted or out of synchronization, it is determined that the connection is faulty; otherwise, it is determined that the connection is normal. If the ATM port or IP port of the MGW can receive signals normally, it indicates that the connection status between the MGW and the network entity directly connected to the optional bearer path is normal. Otherwise, the MGW is directly connected to the optional bearer path. The connection status between the network entities has failed. That is to say, the M GW can determine whether the connection between itself and the network entity directly connected to the optional bearer path has changed according to the physical layer protocol.

[112] In order to better illustrate the solution of the embodiment of the present invention, an application embodiment is used to illustrate the MGC.

Determine the method used to host the MGW.

FIG. 10 is a schematic structural diagram of the system of the embodiment. Figure 10

As shown in the embodiment, the first media gateway, the second media gateway, and the third media gateway are included in the embodiment, that is,

MGW-1, MGW-2, MGW-3; MGC and MGW-1 and MGW-2

Connected; the radio access side device is a radio network controller (RNC), and the RNC is also connected to MGW-1 and MGW-2; MGW-1, MGW-2, and MGW-3 are connected through a bearer network; MGW-1 and RNC The port connected to the RNC in the MGW-1 is an ATM port. The MGW-2 is connected to the RNC through an ATM. The port connected to the RNC in the MGW-2 is an ATM port.

[114] In this embodiment, the media gateway number of the MGW-1 is 111, the media gateway number 222 of the MGW-2, and the signaling point of the RNC is 555. The media gateway number of MGW-1 and MGW-2, and the signaling point number of the RNC can be used as their own network entity identifier. In practice, the global network encoding can also be used to identify the RNC.

[115] In this embodiment, the ATM connection between the MGW-1 and the RNC is interrupted, and the RNC

The next user terminal initiates a call to a user terminal in the PSTN.

[116] FIG. 11 shows the implementation of the MGW determined by the MGC for bearer in this embodiment.

The process of the method includes the following steps:

[117] Step 301: Set up MGW in MGC

Connect the status table and set the connection status initial value to normal.

[118] In this embodiment, it is necessary to set one in the MGC for recording MGW-1 and MGW-2 in advance. Connection status table for connection status, and MGW-1 and MGW-2

The initial value of the connection status is set to normal. In this embodiment, the connection status table is as shown in Table 1:

Table I

[120]

[121] In this embodiment, the bearer network is not associated with MGW-1 or MGW-2.

Other network entities directly connected are recorded in the connection status table. In practical applications, it may be necessary to connect the optional bearer path with MGW-1 or MGW-2.

Other network entities directly connected are recorded in the connection status table. For example: If the MGW-4 in the bearer network is on the optional bearer path and is directly connected to the MGW-1, the MGW-4 should be connected.

Also recorded in the connection status table. MGW-1 will also judge itself and MGW-4 in real time.

Whether the connection status changes, and if so, it is reported to MGC, by MGC

Update the connection status table. Of course, due to the RNC and the MGW-4

All are located on the optional bearer path, which requires the connection status between MGW-1 and RNC, MGW-1 and

MGC can only use MGW-1 when the connection status between MGW-4 is in the normal state at the same time.

As the MGW for the bearer.

[122] In addition, in practical applications, if there are n MGWs simultaneously with the wireless access side equipment and MGC

Connected, you need to record the n MGWs in the connection status table.

[123] Step 302: MGW-1 judges itself and RNC

The connection between the two fails, it will carry its own media gateway number, RNC

A connection status change request message for signaling point code and connection failure information is sent to the MGC.

[124] In practical applications, MGW-1 can judge its own ATM connected to RNC in real time.

Whether the port is normal, that is, whether the electrical signal can be received normally, and if so, the ATM

The port is normal, that is, the connection is normal; otherwise, the ATM port is faulty, that is, the connection is faulty.

[125] The connection failure information described here is a case where the connection state changes. In practical applications, you can use '1' to indicate a connection failure and '0' to indicate that the connection is normal. Of course, in practice, you can also use ' 1 ' indicates that the connection status has changed, when MGC

After receiving the connection status change request message, the MGW in the connection status table can be

The corresponding connection status changes from 'normal' to 'fault' or from 'fault' to 'normal'.

[126] Of course, in practical applications, when the connection between MGW-1 and RNC returns to normal, MGW-1 can carry its own media gateway number, RNC.

Signaling point code and connection status change request message for connecting normal information to MGC

. At this time, the connection normal information is also a connection state change condition.

[127] In an actual application, the connection status change request message reported by the MGW to the MGC may be an extended Mc interface protocol message.

[128] In addition, in practical applications, MGW

The connection between the network entities directly connected to the optional bearer path can also be IP connection. Then, MGW-1 and MGW-2 will be based on their own IP.

If the port is normal, it is determined that the connection status is normal. The method is similar to the method in this embodiment, and details are not described here.

[129] In short, as long as MGW

When the connection status of the network entity directly connected to the optional bearer path changes, the connection status change is reported to the MGC.

[130] Step 303: The MGC updates the MGW connection status table according to the connection status change request message sent by the MGW-1.

[131] In this embodiment, the MGW connection status table after the MGC update is as shown in Table 2:

[132] Table 2

[133]

Step 304: The MGC queries the MGW connection status table, and determines the MGW-2 with the normal connection status as the MGW for the bearer.

In this embodiment, after step 303, if the MGC Receive incoming autonomous caller setup request message, MGC

The task of establishing a bearer path will be performed, and the MGW-2 with normal connection can be determined as a MGW for bearer according to the connection state table. That is, after the bearer path is established, RNC, MGW-2, MGW-3, PSTN

It will form the path that will carry this call. As for how to establish a bearer path, it belongs to the prior art, and details are not described in this embodiment.

[136] In an actual application, the MGC receives the call setup request message from the calling party and receives the connection state change request message from the MGW, and the two are independent of each other, as long as the MGC receives the call setup request message. The query connection status table determines an MGW for bearer.

[137] In addition, in practical applications, in order to ensure that the connection status recorded in the connection status table is consistent with the actual connection status of MGW-1 and MGW-2, it can be in MGC.

The status audit period is set, and a query status request message is sent to MGW-1 and MGW-2 at the end of each status audit period, and MGW-1 and MGW-2 respectively return the current connection status between the respective units and the RNC to the MGC. Happening.

[138] Alternatively, in actual applications, the connection status reporting period can also be set in MGW-1 and MGW-2.

MGW-1 and MGW-2 respectively to MGC at the end of each connection status reporting period

Reports the status of the connection between the current self and the RNC.

[139] In summary, the MGC can accurately and effectively understand the resource status of each bearer interface on the MGW, and overcome the problem of possible waste of network resources caused by the gateway capability change mechanism in the prior art. It provides a basis for rational scheduling of application network resources.

[140] That is, in the embodiment of the present invention, a more reasonable implementation scheme is adopted, so that the MGC can obtain the state information of the bearer interface corresponding to each bearer channel in the MGW connected to multiple bearer entities in time, so that the MGC can obtain the state information according to the acquired information. The policy of selecting the MGW can be flexibly adjusted, so that the utilization of network resources in the network architecture with separate bearer and control can be effectively improved.

The above description is only a preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of within the technical scope disclosed by the present invention. Changes or substitutions are intended to be included within the scope of the invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

Claim

[1] A method for obtaining a bearer status by a media gateway controller, comprising:

The media gateway determines the status of the bearer interface and sends it to the media gateway controller. The media gateway controller receives the bearer interface status of the media gateway and obtains the corresponding bearer status.

[2] The method according to claim 1, wherein the determining, by the media gateway, the interface status comprises: connecting a media gateway of the at least one bearer entity, and detecting the at least one bearer entity in time or in real time. Whether there is a state change in the connection state between the two, and if so, the changed connection state is taken as the state of the bearer interface that needs to be sent to the media gateway controller.

[3] The method according to claim 1, wherein the bearer entity comprises at least one of the following:

Working in an asynchronous transfer mode bearer entity in ATM bearer mode;

a bearer entity working in an IP bearer mode;

A bearer entity working in TDM-based ATM or IP bearer mode.

[4] The method according to claim 1, 2 or 3, wherein the process of obtaining the interface status by the media gateway controller comprises:

The media gateway actively carries the bearer interface identifier to report the status of the bearer interface to the media gateway controller in a service change manner;

The media gateway controller obtains the status of the bearer interface of the media gateway by means of an audit; and the media gateway controller obtains the state of the bearer interface of the media gateway by means of event detection; at least one of three ways.

[5] The method according to claim 4, wherein the process of reporting, by the media gateway, the status of the bearer interface to the media gateway network controller comprises:

Send the bearer interface status and bearer interface identifier information corresponding to each bearer interface to the media gateway controller.

[6] 6. A method for implementing resource scheduling, which is characterized in that:

The media gateway controller obtains the status of the bearer interface of each bearer interface sent by the media gateway, and adjusts the policy of selecting the media gateway according to the state of the bearer interface.

[7] 7. A media gateway, comprising:

The bearer interface status sending unit is configured to report the status of the bearer interface of the at least one bearer interface in the media gateway to the media gateway controller.

[8] The media gateway according to claim 7, further comprising a bearer interface state monitoring unit, configured to monitor a changed bearer interface state of the media gateway to which the at least one bearer entity is connected, and The changed bearer interface status is sent to the media gateway controller through the bearer interface status sending unit.

[9] The media gateway according to claim 8, wherein the bearer entity comprises a bearer entity working in an ATM and/or an IP bearer mode.

[10] The media gateway according to claim 7, 8 or 9, wherein the bearer interface status sending unit comprises at least one of the following units:

a bearer interface state sending unit, configured to send a bearer interface state to the media gateway controller by using a service change manner, and a bearer interface state sending unit based on the auditing operation, according to the media gateway controller The sent information is sent to the media gateway controller by means of the audit response. The bearer interface status sending unit is configured to detect the status change event according to the information sent by the media gateway controller. Send the bearer interface status to the media gateway controller.

[11] 11. A media gateway controller, comprising: a bearer interface state obtaining unit, configured to receive and obtain state information of a bearer interface sent by a media gateway, and determine a corresponding bearer state.

[12] 12. The media gateway controller according to claim 11, further comprising:

The acquiring bearer interface state initiating unit is configured to send, by using an auditing manner, information to the media gateway to obtain the status of the bearer interface; and

The acquiring bearer interface state initiating unit is configured to send, by means of event detection, a message requesting to acquire the state of the bearer interface to the media gateway;

At least one of the two units.

[13] 13. A system for acquiring a bearer status by a media gateway controller, comprising:

The media gateway is responsible for sending the bearer interface status to the media gateway controller. The media gateway controller receives and obtains the status of the bearer interface sent by the media gateway.

[14] 14. An apparatus for implementing resource scheduling, wherein the apparatus is configured to be in a media gateway controller, and includes a bearer interface state obtaining unit and a scheduling policy control unit, where: a bearer interface state acquiring unit is configured to acquire The status of the bearer interface of each bearer interface in the media gateway;

a scheduling policy control unit, configured to adjust a policy for selecting a media gateway according to the state of the bearer interface