WO2008086720A1 - Procédé, matériel et système de sélection de trajet et de commande de flux - Google Patents

Procédé, matériel et système de sélection de trajet et de commande de flux Download PDF

Info

Publication number
WO2008086720A1
WO2008086720A1 PCT/CN2007/071220 CN2007071220W WO2008086720A1 WO 2008086720 A1 WO2008086720 A1 WO 2008086720A1 CN 2007071220 W CN2007071220 W CN 2007071220W WO 2008086720 A1 WO2008086720 A1 WO 2008086720A1
Authority
WO
WIPO (PCT)
Prior art keywords
call
office
flow control
gateway
pair
Prior art date
Application number
PCT/CN2007/071220
Other languages
English (en)
French (fr)
Inventor
Taizhou Chen
Wengang Tian
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to EP07871768A priority Critical patent/EP2037638A4/en
Publication of WO2008086720A1 publication Critical patent/WO2008086720A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/302Route determination based on requested QoS
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/11Identifying congestion
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/12Avoiding congestion; Recovering from congestion
    • H04L47/122Avoiding congestion; Recovering from congestion by diverting traffic away from congested entities
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/24Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2416Real-time traffic
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/25Flow control; Congestion control with rate being modified by the source upon detecting a change of network conditions
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066Session management
    • H04L65/1069Session establishment or de-establishment
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80Responding to QoS
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/08Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters

Definitions

  • the present invention relates to the field of network communications, and in particular, to a method, device and system for routing and flow control. Background technique
  • Softswitch is the core technology of NGN (Next Generation Network), which provides call control and connection control functions for NGN services with real-time requirements.
  • NGN Next Generation Network
  • the core network implements the separation of the load and control, implements call state management through the MGC (Media Gateway Controller), and controls the media gateway to carry resources, and completes the call control function, while the MGW (Media) Gateway, media gateway) is used to implement the bearer, complete the establishment, modification, release and resource management of the media stream.
  • the MGC controls the MGW to establish a bearer through a media gateway control protocol (such as H.248).
  • FIG. 1 shows the networking diagram of the IP (Internet Protocol) bearer network in the softswitch architecture.
  • the MGC is generally deployed in the central city, and the MGW is deployed in various places.
  • the MGC controls the MGW to establish bearers through the IP core network. Users between the areas communicate, and their voice flows through the IP core network.
  • IP bearer type is introduced.
  • TDM Time Division Multiplex
  • ATM Asynchronous Transfer Mode
  • IP bearer type is introduced.
  • IP bearers use a "best effort" strategy, but do not reserve bandwidth or guarantee QoS.
  • the bearer quality is poor, the QoS of the voice call will also decrease. Therefore, in the softswitch architecture, when the voice call bearer path includes an IP bearer, the bearer quality needs to be monitored.
  • the route is re-selected or the call volume is reduced to ensure QoS.
  • MGCs In a large-scale network, there are usually multiple MGCs. Each MGC manages a certain number of MGWs. As shown in Figure 2, there are three MGCs in the network, and two MGWs are managed under each MGC. . It is assumed that the user of the MGC1 calls the user of the MGC2, and the office point MGC1 is called the local office, and the office point MGC2 is called the opposite office. In the case of an IP bearer, in order to ensure the quality of the call, the local office needs to perform the outbound routing according to the QoS of the IP bearer network.
  • the outgoing routing is generally performed in the order of the office route, the IP trunk group, and the MGW.
  • Office direction information is usually configured in this office.
  • the office direction of the called party can be determined.
  • multiple IP trunk groups IP bearer path sets
  • the local office obtains the routing information of the office, and then selects the IP trunk group and the MGW corresponding to the trunk group according to the routing information, for example, selecting MGW2 to be out.
  • FIG. 3 it is a schematic diagram of routing and flow control according to IP bearer QoS in CDMA (Code Division Multi-Passing) 2000, MSCe (Mobile Switching Center, Mobile Switching Center) according to QoS
  • the information is routed and it is determined whether the flow (call volume) needs to be controlled, that is, flow control.
  • the MSCe starts the flow control and gradually reduces the call volume.
  • the MSCe gradually increases the call volume until the flow control is no longer performed. If the user under BSC (Base Station Controller) 1 calls the user under BSC2, the process of MSCel routing and flow control based on QoS is as follows:
  • the user in the BSC1 initiates the call, and the MSCel selects the MGW2 to be out in the order of the office route, the IP relay, the MGW, and the MGW2, and requests the MGW2 to establish a bearer through the H.248 message.
  • the QoS sampling information is carried, that is, the QoS of the call is requested to be detected; then the call is established by the SIP (Session Initiated Protocol) or the Bearer Independent Call Control (BICC).
  • SIP Session Initiated Protocol
  • BICC Bearer Independent Call Control
  • the MGW2 will determine the current QoS according to the delay, packet loss and jitter of the IP flow of the call; if the QoS is worse, the MGW2 reports to the MSCel through the 39/xx interface and the H.248 message; After the information is received, the QoS information of the corresponding trunk group in the QoS information table is updated. If the current QoS does not meet the call quality requirement, the flow control is started for the trunk group, and the call volume is gradually reduced.
  • the MGW2 passes the 39/xx interface and the H.248
  • the QoS recovery information is reported to the MSCel; after receiving the recovery information, the MSCel stops the flow control and gradually releases the call volume of the trunk group.
  • the QoS routing and flow control in the IP trunk group in the larger network, there may be multiple MGWs in the IP trunk group, and one of the MGWs will report the QoS degradation message.
  • IP trunk group flow control but the actual situation may be that the QoS of another MGW corresponding to the trunk group is normal. For example, after the MGW2 reports the QoS degradation message to the MSCel, it performs flow control on the corresponding IP trunk group. If the IP trunk group is also associated with the MGW1, it is also flow-controlled, but the QoS on the MGW1 is normal. Therefore, the QoS is misjudged, and the other MGWs with normal QoS associated with the IP trunk group are also flow-controlled, which affects the call completion rate of the system.
  • the embodiment of the present invention provides a method for routing and flow control, which specifically includes:
  • the pre-configured office gateway pair includes a pre-configured office according to the office gateway controller to the office media gateway controller To the gateway pair;
  • the embodiment of the present invention further provides a device for routing and flow control, where the device specifically includes: a call setup module, configured to select, from a configured office gateway pair, an office gateway pair that allows a call to be established to establish a call;
  • the flow control module is configured to determine, according to the reported QoS information of the office gateway pair, whether to control the call volume of the office gateway pair after the call setup module establishes a call.
  • the embodiment of the invention further provides a system for routing and flow control, the system comprising a local media gateway controller and a correspondent media gateway controller:
  • the local media gateway controller is configured to select an office gateway pair that allows a call to be established from a pre-configured office gateway pair to establish a call; after the call is established, determine, according to the reported QoS information, whether the office gateway pair is The amount of calls is flow controlled;
  • the correspondent media gateway controller is configured to receive a call setup of the local media gateway controller After the request is made, the call is established.
  • the embodiment of the present invention further provides another method for routing and flow control, where the method specifically includes: selecting an IP trunk group gateway pair to establish a call from a pre-configured IP trunk group gateway pair; the IP relay The group gateway pair includes a pre-configured IP trunk group gateway pair according to the office direction of the local media gateway controller to the correspondent media gateway controller;
  • the embodiment of the present invention further provides another device for routing and flow control, where the device specifically includes: a call setup module, configured to establish a call from a selected IP trunk group gateway to select an IP trunk group gateway pair;
  • the flow control module is configured to: after the call setup module establishes a call, determine, according to the reported QoS information, whether to control the call volume of the IP trunk group in the IP trunk group gateway pair.
  • the embodiment of the present invention further provides another system for routing and flow control, where the system specifically includes a local media gateway controller and a correspondent media gateway controller;
  • the local media gateway controller is configured to establish a call from the configured IP trunk group gateway pair to select an IP trunk group gateway pair; after the call setup module establishes a call, determine, according to the reported QoS information of the office gateway pair Whether to control the call volume of the IP trunk group in the IP trunk group gateway pair;
  • the correspondent media gateway controller is configured to establish a call after receiving the call setup request of the local media gateway controller.
  • FIG. 1 is a schematic diagram of an IP bearer networking in a prior art softswitch architecture
  • FIG. 2 is a schematic diagram of inter-office calls in a prior art softswitch architecture
  • 3 is a schematic diagram of an IP bearer networking in the prior art CDMA2000; 4 is a schematic diagram of an IP bearer networking based on an office gateway pair in the embodiment of the present invention;
  • FIG. 5 is a flow chart of a method for routing and flow control according to an embodiment of the present invention.
  • FIG. 6 is a structural diagram of a device for routing and flow control according to an embodiment of the present invention.
  • FIG. ⁇ is a system structural diagram of a routing and a flow control according to an embodiment of the present invention.
  • the embodiment of the present invention defines that the associated office route and the gateway are office gateway pairs, and one office direction can be associated with multiple MGWs, and an MGW can also be associated with multiple office routes.
  • the embodiment of the present invention further defines that the associated IP trunk group and the gateway are IP trunk group gateway pairs, and an IP trunk group can be associated with multiple MGWs, and an MGW can also be associated with multiple IP trunk groups.
  • the embodiment of the present invention is based on the office gateway pair or the IP trunk group gateway, and performs the QoS sampling, and determines whether the call amount of the office gateway pair or the IP trunk group gateway pair is determined according to the QoS sampling information. For flow control, when the QoS is degraded, the call volume is gradually reduced, and after the QoS is restored, the call volume is gradually released.
  • the embodiments of the present invention can be applied to a telecommunication network based on a softswitch architecture, including an NGN network.
  • CDMA2000 and UMTS Universal Mobile Telecommunication System
  • the embodiment of the present invention provides a method for routing and flow control, which specifically includes the following steps:
  • Step 101 First, configure and save the information of the two office gateway pairs in the office direction of the MGC 2 on the office MGC1, that is, add two records in the QoS information table on the MGC1, and record two office gateway pairs: MGC2, MGW1) and (MGC2, MGW2).
  • Step 102 When a new call is established, for example, when the user under the local office MGC1 initiates a call to the user under the MGC2, the MGC1 pre-configures two office gateways from the QoS information table according to the office direction to the MGC2.
  • the pairing office gateway pair (MGC2, MGW2) that allows the call to be established is selected, that is, MGC1 is selected to be outgoing. Allowing a call to be established means that the sum of the newly added call volume and the existing call volume on the selected office gateway pair does not reach or exceed the preset threshold.
  • the actual call volume before starting flow control is 100
  • the actual call volume after flow control cannot be More than 95
  • the current time needs to create a new call, and the actual call volume after the flow control is 90
  • Step 103 The MGC1 sends a request for establishing a bearer to the MGW2, where the request usually carries QoS sampling request information, requests sampling of the QoS of the call, and requests the MGC2 through the interoffice signaling (such as SIP or BICC). Establish a call.
  • the interoffice signaling such as SIP or BICC
  • Step 104 After the call is established, the MGW2 determines the current QoS according to the delay, packet loss, and jitter of the IP flow of the current call; if the current QoS is worse, the call quality requirement is not met, the MGW2 sets the QoS message. Reported to MGCl.
  • Step 105 After receiving the QoS degradation information reported by the MGW2, the MGC1 updates the QoS information of the office gateway pair where the MGW2 is located in the QoS information table saved in the MGC1. Because the current QoS is poor, the MGC1 is directed to the office gateway. To initiate flow control, the number of calls to the gateway pair is restricted by the office, that is, the call volume is gradually reduced. While the flow control is started, an alarm can be reported to the alarm station, indicating that the office is in a flow control state to the gateway pair. After the flow control is started, a minimum value can be preset. When the flow control volume reaches the minimum value, the flow control is stopped.
  • Step 106 After the QoS of the IP stream of the call is restored, the MGW2 reports the QoS recovery information to the MGC1.
  • Step 107 After receiving the QoS recovery information reported by the MGW2, the MGC1 searches for the record of the office gateway pair saved in the QoS information table, and updates the QoS information of the office gateway pair in the record, stops the flow control, and gradually Release the amount of calls made by the office to the gateway pair. After the flow control is stopped, the alarm recovery can be reported to the alarm station, indicating that the office has stopped flow control to the gateway pair.
  • the embodiment of the present invention further provides a device for routing and flow control, which specifically includes:
  • a configuration module configured to pre-configure an office gateway pair by the local media gateway controller according to the office direction to the correspondent media gateway controller;
  • two office gateways configured and saved to the office direction of the MGC2 in the local office MGC1
  • two records are added to the QoS information table on MGC1, and two office gateway pairs are recorded: (MGC2, MGW1) and (MGC2, MGW2).
  • a call setup module configured to: when establishing a new call, select, by the local media gateway controller, an office gateway pair that allows a call to be established from the office gateway pair configured by the configuration module; and then The local media gateway in the gateway sends a bearer setup request, and requests the correspondent media gateway controller to establish a call;
  • the MGC1 selects a station that allows the call to be established from the two office gateway pairs pre-configured in the QoS information table according to the office direction to the MGC2.
  • the MGW2 is selected to be sent to the gateway (MGC2, MGW2), that is, the MGC1.
  • the MGC1 then sends a request for establishing a bearer to the MGW2.
  • the request usually carries the QoS sampling request information, and requests the QoS of the new call to be sampled; Signaling (such as SIP or BICC, etc.) requests the host MGC2 to establish a call.
  • the flow control module is configured to determine, by the local media gateway controller, whether to control the call volume of the selected office gateway pair according to the information reported by the media gateway of the local office after the call setup module establishes the call.
  • the above call setup module includes:
  • the selection unit is configured to select an office gateway pair that does not meet or exceed a preset threshold value between the added call volume and the existing call volume, that is, only the office gateway pair that meets the condition is allowed to establish a call. .
  • the above flow control module includes:
  • the traffic limiting unit when the message reported by the local media gateway is a QoS degradation message, the flow control is started by the media gateway controller of the local office, and the call volume of the selected office gateway pair is gradually reduced.
  • the MGW2 determines the current QoS according to the delay, packet loss, and jitter of the IP stream of the current call. If the current QoS is degraded and the call quality is not met, the MGW2 reports the QoS message to the MGC1. After receiving the information about the QoS degradation reported by the MGW2, the MGC1 starts the flow control on the selected office gateway pair (MGC2, MGW2), and limits the call volume of the office to the gateway, that is, gradually reduces the call volume. While the flow control is started, an alarm can be reported to the alarm station, indicating that the office is in a flow control state to the gateway pair. After the flow control is started, a minimum value can be preset.
  • the flow control is stopped.
  • the traffic release unit when the message reported by the local media gateway is a QoS recovery message, the media gateway controller of the local office stops the flow control, and gradually releases the call volume of the selected office gateway pair.
  • the MGW2 reports the QoS recovery information to the MGC1.
  • the MGC1 stops the flow control and gradually releases the selected office gateway pair (MGC2, MGW2). Call volume.
  • the alarm recovery can be reported to the alarm station, indicating that the office has stopped flow control to the gateway pair.
  • the above device for routing and flow control further includes:
  • the QoS information update module is configured to record, by the local media gateway controller, the pre-configured office gateway pair in the QoS information table, and after receiving the QoS information reported by the local media gateway, update the corresponding office direction in the QoS information table. QoS information of the gateway pair.
  • the MGC1 updates the QoS information of the office gateway pair where the MGW2 is located in the QoS information table stored in the MGC1.
  • the MGC1 searches for the QoS information. The record of the office to the gateway pair saved in advance in the table, and updating the QoS information of the office gateway pair in the record.
  • an embodiment of the present invention further provides a system for routing and flow control, including a local media gateway controller MGC1 and a correspondent media gateway controller MGC2;
  • the above media gateway controller MGC1 includes:
  • a configuration module configured to pre-configure an office gateway pair according to an office direction of the media gateway controller of the opposite office
  • a call setup module configured to: when establishing a new call, select an office gateway pair that allows the call to be established from the office gateway pair configured by the configuration module; and then send the local media gateway to the gateway to the gateway Sending a bearer request and requesting a peer media gateway controller to establish a call;
  • the MGC1 selects an office gateway pair (MGC2, MGW2) that allows the call to be established, and then sends a request for establishing a bearer to the MGW2, and carries the QoS in the request.
  • MSC2, MGW2 office gateway pair
  • Sampling request information then requesting the office MGC2 to establish a call through interoffice signaling (such as SIP or BICC, etc.).
  • the above-mentioned game media gateway controller MGC2 includes:
  • a call setup module is configured to establish a call after receiving a call setup request from the local media gateway controller.
  • the above flow control module includes:
  • a traffic limiting unit configured to start flow control when the message reported by the local media gateway is a QoS degradation message, and gradually reduce the call volume of the selected office gateway pair;
  • the MGW2 reports the QoS message to the MGC1.
  • the MGW1 starts the flow control on the selected office gateway pair (MGC2, MGW2), and limits the call volume of the office gateway pair. , that is, gradually reduce the amount of calls.
  • MGC2 selected office gateway pair
  • MGW2 limits the call volume of the office gateway pair. , that is, gradually reduce the amount of calls.
  • an alarm can be reported to the alarm station, indicating that the office is in a flow control state to the gateway pair.
  • a minimum value can be preset. When the flow control volume reaches the minimum value, the flow control is stopped.
  • the traffic release unit when the message reported by the local media gateway is a QoS recovery message, stops the flow control, and gradually releases the call volume of the selected office gateway pair;
  • the MGW2 reports the QoS recovery information to the MGC1.
  • the MGC1 stops the flow control and gradually releases the call volume of the selected office gateway pair (MGC2, MGW2).
  • MGC2, MGW2 the call volume of the selected office gateway pair
  • the alarm recovery can be reported to the alarm station, indicating that the office has stopped flow control to the gateway pair.
  • the above media gateway controller also includes:
  • the QoS information update module is configured to record the pre-configured office gateway pair in the QoS information table, and after receiving the QoS information reported by the local media gateway, update the QoS information of the corresponding office gateway pair in the QoS information table.
  • the MGC1 adds two records in the QoS information table in advance, and records the two office gateway pairs configured: (MGC2, MGW1) and (MGC2, MGW2); after receiving the information of the QoS degradation reported by the MGW2, the MGC1 receives the information.
  • the QoS information table stored in the MGC1 updates the QoS information of the office gateway pair where the MGW2 is located.
  • the MGC1 searches for the record of the office gateway pair previously saved in the QoS information table, and updates the record. The QoS information of the office to the gateway pair in the record.
  • the manner of routing and flow control based on the office gateway pair may be replaced by a manner of routing and flow control based on the IP trunk group gateway.
  • the process is as follows: The IP trunk group gateway pair is configured in advance on the MGC of the local office. When the IP trunk group gateway pair mode is adopted, the routing process is the same as the prior art process. The difference is that when performing flow control, according to the pre-configured The IP trunk group gateway pair performs flow control only on the IP trunk group associated with the media gateway reporting the QoS degradation message, and the flow control is not performed on the IP trunk group that is not associated.
  • IP trunk group 1, MGW1 and IP trunk group 1, MGW2 For example, suppose that two IP trunk group gateway pairs are preset, (IP trunk group 1, MGW1) and (IP trunk group 1, MGW2), that is, both MGW1 and MGW2 are associated with IP trunk group 1, if MGW1 If the QoS degradation information is reported, only the IP trunk group associated with the MGW1 in the IP trunk group 1 is flow-controlled, and the IP trunk group associated with the MGW2 in the IP trunk group 1 is not flow-controlled.
  • the prior art performs flow control on all IP trunk groups. Compared with the prior art, the accuracy of the flow control is improved, the flow control is more refined, and the misjudgment of QoS is avoided.
  • an alarm may be sent to the alarm station to indicate that the QoS of the office gateway pair or the IP trunk group gateway is changed.
  • the MGC can also be several calls simultaneously QoS samples, respectively, to record and save all samples QoS information in the QoS table Information, thereby improving the accuracy of QoS sampling and avoiding the occurrence of QoS misjudgment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Telephonic Communication Services (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Description

选路及流控的方法、 装置和系统
本申请要求于 2006 年 12 月 13 日 日提交中国专利局、 申请号为 200610165838.1、 发明名称为"选路及流控的方法、 装置和系统"的中国专利申 请的优先权, 其全部内容通过引用结合在本申请中。
技术领域
本发明涉及网络通讯领域,特别涉及一种选路及流控的方法、装置和系统。 背景技术
软交换作为 NGN ( Next generation network, 下一代网络) 的核心技术, 为 NGN具有实时性要求的业务提供呼叫控制和连接控制功能。 在软交换架构 下, 核心网络实现 载和控制分离, 通过 MGC ( Media Gateway Controller, 媒体网关控制器)实现呼叫状态的管理, 以及对媒体网关承载资源的控制, 完 成呼叫控制功能, 而 MGW ( Media Gateway, 媒体网关)用来实现承载, 完 成媒体流的建立、 修改、 释放和资源管理等。 MGC通过媒体网关控制协议 (如 H.248)控制 MGW建立承载。目前的传统电信网络,包括 PSTN( Public Switched Telephone Network, 公共交换电话网) 网络和 PLMN ( Public Land Mobile Network, 公共陆地移动通信网) 网络, 其核心网正逐步向软交换架构演进。 如图 1所示为软交换架构下 IP ( Internet Protocol , 网际协议 )承载网组网示意 图, MGC—般布置在中心城市, 而 MGW布置在各地, MGC通过 IP核心网 控制 MGW建立承载, 使不同地区之间的用户进行通信, 其语音流经 IP核心 网传送。
在传统的电信网络中, 语音呼叫一般承载在 TDM ( Time Division Multiplex, 时分多路复用)及 ATM ( Asynchronous Transfer Mode, 异步传输 模式)上, 而在软交换架构下, 引入 IP承载类型的概念, 即用于承载 IP分组 的物理实体类型。 对于 TDM, 为每一呼叫都分配固定的带宽, 对于 ATM, 通 过预留带宽来保证一定的 QoS ( Quality of Service, 服务质量)。 而 IP承载, 采用 "尽力而为"的策略,但并不预留带宽, 也不保证 QoS,存在固有的延迟、 丢包和抖动的问题。 当承载质量较差时, 语音呼叫的 QoS也将下降。 因此, 在软交换架构中, 当语音呼叫承载通路包括 IP承载的情况下, 需对承载质量 进行监测。当承载质量变差时,重新选取路由或者减少呼叫量,从而保证 QoS。 在较大规模的组网中, 一般存在多个 MGC, 每一 MGC下管理一定数量 的 MGW, 如图 2所示, 该组网中存在 3个 MGC,每个 MGC下又管理着两个 MGW。 现假设 MGC1的用户呼叫 MGC2的用户, 则局点 MGC1称为本局 , 局点 MGC2称为对局。 在 IP承载的情况下, 为了保证通话质量, 本局需要根 据 IP承载网的 QoS进行出局选路, 出局选路一般是按照局向一路由一 IP中继 群一 MGW的顺序进行。 通常在本局上会配置局向信息。 在呼叫时, 通过对被 叫号码的分析, 可以确定该被叫所在的局向。 在一个局向上, 可以配置有多个 IP中继群(IP承载通路集合), 相当于在两个局点中有多个连接路径。 本局会 根据局向, 获得该局向的路由信息, 然后根据路由信息选取 IP中继群及该中 继群对应的 MGW , 如选取 MGW2出局。
如图 3所示, 为现有技术 CDMA ( Code Division Multipe Addressing, 码 分多址 ) 2000中根据 IP承载的 QoS进行选路及流控的示意图, MSCe ( Mobile Switching Center, 移动交换中心)根据 QoS信息进行选路, 并确定是否需要 对流量(呼叫量)进行控制, 即流控。 当 QoS变差时, MSCe启动流控, 逐步 减少呼叫量; 当 QoS恢复后, MSCe逐步增加呼叫量, 直到不再进行流控。 假 设 BSC ( Base Station Controller, 基站控制器) 1下的用户呼叫 BSC2下的用 户, 则 MSCel根据 QoS进行选路及流控的过程如下:
1、 BSC1下的用户发起呼叫, MSCel按照局向一路由一 IP中继^ ~MGW 的顺序选择 MGW2 出局 (也可选择 MGW1 出局), 并通过 H.248消息请求 MGW2建立承载, 该请求消息中携带有 QoS采样信息, 即请求对呼叫的 QoS 进行检测;然后通过 SIP ( Session Initiated Protocol , 会话初始化协议 )或 BICC ( Bearer Independent Call Control, 承载无关呼叫控制协议 )请求对局 MSCe2 建立呼叫。
2、 呼叫开始后, MGW2将根据呼叫的 IP流的延迟, 丢包和抖动情况, 确定当前的 QoS; 若 QoS变差, 则 MGW2通过 39/xx接口和 H.248消息上报 给 MSCel; MSCel收到该信息后, 更新 QoS信息表中对应中继群的 QoS信 息, 若当前的 QoS达不到呼叫质量的要求, 则针对该中继群启动流控, 逐步 减少呼叫量。
3、 当该呼叫的 IP流的 QoS恢复后 , MGW2通过 39/xx接口和 H.248消 息上报 QoS恢复信息给 MSCel; MSCel收到恢复信息后, 停止流控, 逐步放 开该中继群的呼叫量。
上述现有技术的缺点如下:
根据 QoS进行选路及流控 于 IP中继群, 在较大 ¾f莫组网中 , IP中继 群下可能配置有多个 MGW, 其中一个 MGW上报 QoS变差的消息时, 将造 成对该 IP中继群流控, 而实际情况可能该中继群对应的另一个 MGW的 QoS 是正常的。 例如, MGW2上报 QoS变差消息给 MSCel后, 对相应 IP中继群 进行流控,如果该 IP中继群还和 MGW1关联, 则也被流控,但实际上 MGW1 上的 QoS是正常的。 因此会对 QoS产生误判, 造成对该 IP中继群所关联的其 他 QoS正常的 MGW也进行流控, 影响系统的呼叫接通率。
发明内容
为了解决现有技术中选路及流控时可能对 QoS产生误判并影响系统呼叫 接通率的问题, 本发明实施例提供了一种选路及流控的方法, 具体包括:
从预先配置的局向网关对中选取允许建立呼叫的局向网关对建立呼叫;所 述预先配置的局向网关对包括根据本局网关控制器到对局媒体网关控制器的 局向预先配置的局向网关对;
所述呼叫建立后, 根据上报的所述局向网关对的 QoS信息决定是否对所 述局向网关对的呼叫量进行流控。
本发明实施例还提供了一种选路及流控的装置, 所述装置具体包括: 呼叫建立模块,用于从配置的局向网关对中选取允许建立呼叫的局向网关 对建立呼叫;
流控模块, 用于在所述呼叫建立模块建立呼叫后,根据上报的该局向网关 对的 QoS信息决定是否对所述局向网关对的呼叫量进行流控。
本发明实施例还提供了一种选路及流控的系统,所述系统包括本局媒体网 关控制器和对局媒体网关控制器:
所述本局媒体网关控制器用于从预先配置的局向网关对中选取允许建立 呼叫的局向网关对建立呼叫; 在所述呼叫建立后, 根据上报的 QoS信息决定 是否对所述局向网关对的呼叫量进行流控;
所述对局媒体网关控制器用于在收到所述本局媒体网关控制器的呼叫建 立请求后, 建立呼叫。
本发明实施例还提供了另外一种选路及流控的方法, 所述方法具体包括: 从预先配置的 IP中继群网关对中选取 IP中继群网关对建立呼叫;所述 IP 中继群网关对包括根据本局媒体网关控制器到对局媒体网关控制器的局向预 先配置 IP中继群网关对;
所述呼叫建立后, 根据上报的所述局向网关对的 QoS信息决定是否对所 述 IP中继群网关对内的 IP中继群的呼叫量进行流控。
本发明实施例还提供了另外一种选路及流控的装置 , 所述装置具体包括: 呼叫建立模块, 用于从配置的 IP中继群网关对选取 IP中继群网关对建立 呼叫;
流控模块, 用于在所述呼叫建立模块建立呼叫后, 根据上报的 QoS信息 决定是否对所述 IP中继群网关对内的 IP中继群的呼叫量进行流控。
本发明实施例还提供了另外一种选路及流控的系统,所述系统具体包括本 局媒体网关控制器和对局媒体网关控制器;
所述本局媒体网关控制器用于从配置的 IP中继群网关对选取 IP中继群网 关对建立呼叫; 在所述呼叫建立模块建立呼叫后,根据上报的所述局向网关对 的 QoS信息决定是否对所述 IP中继群网关对内的 IP中继群的呼叫量进行流 控;
所述对局媒体网关控制器用于在收到所述本局媒体网关控制器的呼叫建 立请求后, 建立呼叫。
本发明实施例的有益效果主要表现在:
基于局向网关对或 IP中继群网关对进行选路和 QoS采样,并根据 QoS采 样信息对局向网关对或 IP中继群网关对的呼叫量进行流控, 不仅保证了服务 质量, 提高了流控的精度, 使流控更加细化, 而且有利于提高系统的呼叫接通 率。
附图说明
图 1是现有技术软交换架构下 IP承载组网示意图;
图 2是现有技术软交换架构下局间呼叫示意图;
图 3是现有技术 CDMA2000中 IP承载组网示意图; 图 4是本发明实施例基于局向网关对的 IP承载组网示意图;
图 5是本发明实施例选路及流控的方法流程图;
图 6是本发明实施例选路及流控的装置结构图;
图 Ί是本发明实施例选路及流控的系统结构图。
具体实施方式
下面结合附图和具体实施例对本发明作进一步说明,但本发明不局限于下 面的实施例。
本发明实施例定义相关联的局向和网关为局向网关对,某一局向可以和多 个 MGW关联,某一 MGW也可以和多个局向关联。本发明实施例还定义相关 联的 IP中继群和网关为 IP中继群网关对, 某一 IP中继群可以和多个 MGW 关联, 某一 MGW也可以和多个 IP中继群关联。 本发明实施例基于局向网关 对或 IP中继群网关对选 目应的 MGW出局, 并进行 QoS采样,根据 QoS采 样信息决定是否对该局向网关对或 IP中继群网关对的呼叫量进行流控,在 QoS 变差时, 逐步减少呼叫量, 在 QoS恢复后, 逐步放开呼叫量。
本发明实施例可以应用于基于软交换架构的电信网络中,包括 NGN网络,
CDMA2000及 UMTS ( Universal Mobile Telecommunication System, 通用移动 通信系统) 的核心网络电路域等。
参见图 4, 该组网中有 MGC1及 MGC2两个局点, 在 MGC1上配置有到 MGC2的局向, 和该局向关联的网关有 MGW1和 MGW2, 即与到 MGC2的 局向相关联的局向网关对有两个: (MGC2, MGW1 )和(MGC2, MGW2 )。 在本实施例中假设 MGC1下的用户呼叫 MGC2下的用户, 参见图 5, 本发明 实施例提供了一种选路及流控的方法, 具体包括以下步骤:
步骤 101 : 首先在局点 MGC1上配置并保存到 MGC2的局向的两个局向 网关对的信息, 即在 MGC1上的 QoS信息表中增加两条记录, 记录两个局向 网关对: ( MGC2, MGW1 )和(MGC2, MGW2 )。
步骤 102: 当建立一个新的呼叫时, 例如当本局 MGC1 下的用户向对局 MGC2下的用户发起呼叫时, MGC1根据到 MGC2的局向从 QoS信息表中预 先配置好的两个局向网关对中选取出一个允许建立呼叫的局向网关对 ( MGC2 , MGW2 ) , 即 MGC 1选取 MGW2出局。 允许建立呼叫是指在选取的局向网关对上新增的呼叫量与已有的呼叫量 之和没有达到或超过了预设的阔值。 例如, 启动流控前的实际呼叫量为 100, 则按照一定的百分比设置一个流控的阔值,如 95 % , 即阔值为 100*95 % = 95, 则流控后的实际呼叫量不能超过 95; 如果当前时刻需要新建一个呼叫, 而流 控后的实际呼叫量为 90, 则新建立的呼叫量与实际呼叫量之和为 90+1 = 91 , 仍然没有超过阔值 95, 所以可以选择该局向网关对建立该新的呼叫。
步骤 103: MGC1向 MGW2下发建立承载的请求, 该请求中通常携带有 QoS采样请求信息, 请求对该呼叫的 QoS进行采样; 并通过局间信令(如 SIP 或 BICC等 )请求对局 MGC2建立呼叫。
步骤 104: 呼叫建立后, MGW2将根据当前呼叫的 IP流的延迟, 丢包和 抖动情况, 确定当前的 QoS; 如果当前的 QoS变差, 达不到呼叫质量的要求, 则 MGW2将该 QoS消息上报给 MGCl。
步骤 105: MGC1收到 MGW2上报的 QoS变差的信息后, 在 MGC1中保 存的 QoS信息表中更新 MGW2所在的局向网关对的 QoS信息, 由于当前的 QoS较差, MGC1针对该局向网关对启动流控,对该局向网关对的呼叫量进行 限制, 即逐步减少呼叫量。 在启动流控的同时, 可以向告警台上报告警, 提示 该局向网关对处于流控状态。 启动流控后, 可以预设一个最小值, 当流控后的 呼叫量达到最小值后, 则停止进行流控。
步骤 106: 当呼叫的 IP流的 QoS恢复后, MGW2上报 QoS恢复信息给 MGC1。
步骤 107: MGC1收到 MGW2上报的 QoS恢复信息后, 查找 QoS信息表 中事先保存的该局向网关对的记录, 并更新该条记录中该局向网关对的 QoS 信息, 停止流控, 逐步放开该局向网关对的呼叫量。 停止流控后, 可以向告警 台上报告警恢复, 提示该局向网关对已停止流控。
参见图 4和图 6, 本发明实施例还提供了一种选路及流控的装置, 具体包 括:
( 1 ) 配置模块, 用于由本局媒体网关控制器根据到对局媒体网关控制器 的局向预先配置局向网关对;
例如, 在本局 MGC1上配置并保存到对局 MGC2的局向的两个局向网关 对的信息, 即在 MGC1上的 QoS信息表中增加两条记录, 记录两个局向网关 对: ( MGC2, MGW1 )和 ( MGC2, MGW2 )。
( 2 )呼叫建立模块, 用于当建立一个新的呼叫时, 由本局媒体网关控制 器从上述配置模块配置的局向网关对中选取一个允许建立呼叫的局向网关对; 然后向该局向网关对内的本局媒体网关下发建立承载请求,并请求对局媒体网 关控制器建立呼叫;
例如,当本局 MGC1下的用户向对局 MGC2下的用户发起呼叫时, MGC1 根据到 MGC2的局向从 QoS信息表中预先配置好的两个局向网关对中选取出 一个允许建立呼叫的局向网关对 ( MGC2, MGW2 ), 即 MGC1 选取 MGW2 出局; 然后 MGC1向 MGW2下发建立承载的请求, 该请求中通常携带有 QoS 采样请求信息, 请求对新建呼叫的 QoS进行采样; 并通过局间信令(如 SIP 或 BICC等 )请求对局 MGC2建立呼叫。
( 3 )流控模块, 用于在上述呼叫建立模块建立呼叫后, 由本局媒体网关 控制器根据本局媒体网关上报的信息决定是否对选取的局向网关对的呼叫量 进行流控。
上述呼叫建立模块包括:
选取单元,用于选取新增的呼叫量与已有的呼叫量之和没有达到或超过一 个预设的阔值的局向网关对,即认为只有符合该条件的局向网关对才允许建立 呼叫。
上述流控模块包括:
1 ) 流量限制单元, 用于在本局媒体网关上报的消息为 QoS变差消息时, 由本局媒体网关控制器启动流控, 逐步减少选取的局向网关对的呼叫量。
例如, MGW2将根据当前呼叫的 IP流的延迟, 丢包和抖动情况, 确定当 前的 QoS; 如果当前的 QoS变差, 达不到呼叫质量的要求, 则 MGW2将该 QoS消息上报给 MGC1。 MGC1收到 MGW2上报的 QoS变差的信息后, 会对 选取的局向网关对(MGC2, MGW2 )启动流控, 对该局向网关对的呼叫量进 行限制, 即逐步减少呼叫量。 在启动流控的同时, 可以向告警台上报告警, 提 示该局向网关对处于流控状态。 启动流控后, 可以预设一个最小值, 当流控后 的呼叫量达到最小值后, 则停止进行流控。 2 )流量放开单元, 用于在本局媒体网关上报的消息为 QoS恢复消息时, 由本局媒体网关控制器停止流控, 逐步放开选取的局向网关对的呼叫量。
例如,当呼叫的 IP流的 QoS恢复后, MGW2上报 QoS恢复信息给 MGC1; MGC1收到 MGW2上报的 QoS恢复信息后, 停止流控, 逐步放开选取的局向 网关对(MGC2, MGW2 )的呼叫量。 停止流控后, 可以向告警台上报告警恢 复, 提示该局向网关对已停止流控。
上述选路及流控的装置还包括:
QoS信息更新模块,用于由本局媒体网关控制器将预先配置的局向网关对 记录在 QoS信息表中, 在接收到本局媒体网关上报的 QoS信息后, 在 QoS信 息表中更新对应的局向网关对的 QoS信息。
例如, MGC1收到 MGW2上报的 QoS变差的信息后, 在 MGC1中保存 的 QoS信息表中更新 MGW2所在的局向网关对的 QoS信息; MGC1 收到 MGW2上报的 QoS恢复信息后,查找 QoS信息表中事先保存的该局向网关对 的记录, 并更新该条记录中该局向网关对的 QoS信息。
参见图 4和图 7, 本发明实施例还提供了一种选路及流控的系统, 包括本 局媒体网关控制器 MGC1和对局媒体网关控制器 MGC2;
上述本局媒体网关控制器 MGC1包括:
( 1 ) 配置模块, 用于 据到对局媒体网关控制器的局向预先配置局向网 关对;
例如,配置到 MGC2的局向的两个( MGC2 , MGW1 )和( MGC2 , MGW2 )。
( 2 )呼叫建立模块, 用于当建立一个新的呼叫时, 从配置模块配置的局 向网关对中选取一个允许建立呼叫的局向网关对;然后向该局向网关对内的本 局媒体网关下发建立承载请求, 并请求对局媒体网关控制器建立呼叫;
例如, 当 MGC1下的用户向 MGC2下的用户发起呼叫时, MGC1选取出 一个允许建立呼叫的局向网关对(MGC2, MGW2 )后, 向 MGW2下发建立 承载的请求, 并在请求中携带 QoS采样请求信息; 然后通过局间信令(如 SIP 或 BICC等 )请求对局 MGC2建立呼叫。
( 3 ) 流控模块, 用于在呼叫建立模块建立呼叫后, 根据本局媒体网关上 报的信息决定是否对局向网关对的呼叫量进行流控; 上述对局媒体网关控制器 MGC2包括:
呼叫建立模块, 用于在收到本局媒体网关控制器的呼叫建立请求后, 建立 呼叫。
上述流控模块包括:
1 )流量限制单元, 用于在本局媒体网关上报的消息为 QoS变差消息时, 启动流控, 逐步减少选取的局向网关对的呼叫量;
例如, MGW2在当前的 QoS变差时将该 QoS消息上报给 MGC1, MGC1 收到后, 对选取的局向网关对( MGC2 , MGW2 )启动流控 , 对该局向网关对 的呼叫量进行限制, 即逐步减少呼叫量。 在启动流控的同时, 可以向告警台上 报告警,提示该局向网关对处于流控状态。启动流控后,可以预设一个最小值, 当流控后的呼叫量达到最小值后 , 则停止进行流控。
2 ) 流量放开单元, 用于在本局媒体网关上报的消息为 QoS恢复消息时, 停止流控, 逐步放开选取的局向网关对的呼叫量;
例如, 当 QoS恢复后, MGW2上报 QoS恢复信息给 MGC1, MGC1收到 后, 停止流控, 逐步放开选取的局向网关对(MGC2, MGW2 )的呼叫量。 停 止流控后, 可以向告警台上报告警恢复, 提示该局向网关对已停止流控。
上述本局媒体网关控制器还包括:
QoS信息更新模块, 用于将预先配置的局向网关对记录在 QoS信息表中 , 在接收到本局媒体网关上报的 QoS信息后, 在 QoS信息表中更新对应的局向 网关对的 QoS信息。
例如, MGC1预先在 QoS信息表中增加两条记录, 记录配置的两个局向 网关对: (MGC2, MGW1 )和(MGC2, MGW2 ); MGC1收到 MGW2上报 的 QoS变差的信息后, 在 MGC1中保存的 QoS信息表中更新 MGW2所在的 局向网关对的 QoS信息; MGC1收到 MGW2上报的 QoS恢复信息后, 查找 QoS信息表中事先保存的该局向网关对的记录,并更新该条记录中该局向网关 对的 QoS信息。
上述实施例中选路及流控的方法、装置或系统中基于局向网关对进行选路 及流控的方式, 可以由基于 IP中继群网关对进行选路及流控的方式来替换, 具体过程如下: 预先在本局 MGC上配置 IP中继群网关对, 当采用 IP中继群网关对方式 时, 选路的过程同现有技术的过程一样, 不同之处是在进行流控时, 根据预先 配置的 IP中继群网关对,只对上报 QoS变差消息的媒体网关所关联的 IP中继 群进行流控, 没有关联的 IP中继群则不进行流控。
例如 , 假设预设了两个 IP中继群网关对 , ( IP中继群 1, MGW1 )和( IP 中继群 1 , MGW2 ), 即 MGW1和 MGW2均和 IP中继群 1关联, 如果 MGW1 上报 QoS变差信息, 则只对 IP中继群 1中和 MGW1关联的 IP中继群进行流 控, 而对 IP中继群 1中和 MGW2关联的 IP中继群不进行流控。 现有技术则 对全部 IP中继群进行流控。 与现有技术相比提高了流控的精度, 使流控更加 细化, 避免了对 QoS误判的情况发生。
本发明实施例中当 QoS变化(变差或恢复) 时, 还可以向告警台上 4艮告 警, 提示该局向网关对或 IP中继群网关对的 QoS发生变化。 考虑到只针对一 个呼叫进行 QoS采样, 可能产生 QoS误判的情况, 进一步地, MGC还可以同 时进行若干个呼叫的 QoS采样, 相应地, 在 QoS信息表中记录并保存所有采 样到的 QoS信息, 从而提高了 QoS采样的准确性, 避免了 QoS误判的情况发 生。
以上所述的实施例, 只是本发明较优选的具体实施方式的几种,本领域的 技术人员在本发明技术方案范围内进行的通常变化和替换都应包含在本发明 的保护范围内。

Claims

权 利 要 求
1. 一种选路及流控的方法, 其特征在于, 该方法包括:
从预先配置的局向网关对中选取允许建立呼叫的局向网关对建立呼叫;所 述预先配置的局向网关对包括根据本局网关控制器到对局媒体网关控制器的 局向预先配置的局向网关对;
所述呼叫建立后, 根据上报的所述局向网关对的 QoS信息决定是否对所 述局向网关对的呼叫量进行流控。
2. 根据权利要求 1所述的选路及流控的方法, 其特征在于, 所述从预先 配置的局向网关对中选取允许建立呼叫的局向网关对建立呼叫包括:
从预先配置的局向网关对中选取局向网关对,所述选取的局向网关对上满 足新增的呼叫量与已有的呼叫量之和没有达到或没有超过预设的阔值,在所述 局向网关对上建立呼叫。
3. 根据权利要求 1所述的选路及流控的方法, 其特征在于, 所述决定是 否对所述局向网关对的呼叫量进行流控的步骤具体为:
如果所述上报的信息为 QoS变差, 启动流控, 减少所述局向网关对的呼 叫量; 如果所述上报的信息为 QoS恢复, 停止流控, 增加所述局向网关对的 呼叫量。
4. 根据权利要求 1所述的选路及流控的方法, 其特征在于, 所述根据上 报的 QoS信息决定是否对所述局向网关对的呼叫量进行流控包括:
根据上报的所述局向网关对上至少一个呼叫的 QoS信息决定是否对所述 局向网关对的呼叫量进行流控。
5. 一种选路及流控的装置, 其特征在于, 包括:
呼叫建立模块,用于从配置的局向网关对中选取允许建立呼叫的局向网关 对建立呼叫;
流控模块, 用于在所述呼叫建立模块建立呼叫后,根据上报的该局向网关 对的 QoS信息决定是否对所述局向网关对的呼叫量进行流控。
6. 如权利要求 5所述的装置, 其特征在于, 还包括配置模块, 用于根据 本局媒体网关控制器到对局媒体网关控制器的局向配置局向网关对。
7. 根据权利要求 5所述的选路及流控的装置, 其特征在于, 所述允许建 立呼叫的局向网关对包括:
满足新增的呼叫量与已有的呼叫量之和没有达到或没有超过预设阔值的 局向网关对。
8. 根据权利要求 5所述的选路及流控的装置, 其特征在于, 所述流控模 块包括:
流量限制单元, 用于当所述信息为 QoS变差时, 启动流控, 减少所述局 向网关对的呼叫量;
流量放开单元, 用于当所述信息为 QoS恢复时, 停止流控, 增加所述局 向网关对的呼叫量。
9. 根据权利要求 5所述的选路及流控的装置, 其特征在于, 所述上报的 所述局向网关对的 QoS 信息包括上报的所述局向网关对上至少一个呼叫的 QoS信息。
10. 一种选路及流控的系统, 其特征在于, 所述系统包括本局媒体网关控 制器和对局媒体网关控制器:
所述本局媒体网关控制器用于从预先配置的局向网关对中选取允许建立 呼叫的局向网关对建立呼叫; 在所述呼叫建立后, 根据上报的 QoS信息决定 是否对所述局向网关对的呼叫量进行流控;
所述对局媒体网关控制器用于在收到所述本局媒体网关控制器的呼叫建 立请求后, 建立呼叫。
11. 一种选路及流控的方法, 其特征在于, 所述方法具体包括: 从预先配置的 IP中继群网关对中选取 IP中继群网关对建立呼叫;所述 IP 中继群网关对包括根据本局媒体网关控制器到对局媒体网关控制器的局向预 先配置 IP中继群网关对;
所述呼叫建立后, 根据上报的所述局向网关对的 QoS信息决定是否对所 述 IP中继群网关对内的 IP中继群的呼叫量进行流控。
12. 一种选路及流控的装置, 其特征在于, 所述装置具体包括: 呼叫建立模块, 用于从配置的 IP中继群网关对选取 IP中继群网关对建立 呼叫;
流控模块, 用于在所述呼叫建立模块建立呼叫后, 根据上报的 QoS信息 决定是否对所述 IP中继群网关对内的 IP中继群的呼叫量进行流控。
13、 如权利要求 12所述的装置, 其特征在于, 还包括配置模块, 用于根 据本局媒体网关控制器到对局媒体网关控制器的局向配置 IP中继群网关对。
14. 一种选路及流控的系统, 其特征在于, 所述系统具体包括本局媒体网 关控制器和对局媒体网关控制器;
所述本局媒体网关控制器用于从配置的 IP中继群网关对选取 IP中继群网 关对建立呼叫; 在所述呼叫建立模块建立呼叫后,根据上报的所述局向网关对 的 QoS信息决定是否对所述 IP中继群网关对内的 IP中继群的呼叫量进行流 控;
所述对局媒体网关控制器用于在收到所述本局媒体网关控制器的呼叫建 立请求后, 建立呼叫。
PCT/CN2007/071220 2006-12-13 2007-12-12 Procédé, matériel et système de sélection de trajet et de commande de flux WO2008086720A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP07871768A EP2037638A4 (en) 2006-12-13 2007-12-12 METHOD, EQUIPMENT AND SYSTEM FOR PATH SELECTION AND FLUX CONTROL

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200610165838.1 2006-12-13
CN200610165838.1A CN100563212C (zh) 2006-12-13 2006-12-13 选路及流控的方法、装置和系统

Publications (1)

Publication Number Publication Date
WO2008086720A1 true WO2008086720A1 (fr) 2008-07-24

Family

ID=38693023

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/071220 WO2008086720A1 (fr) 2006-12-13 2007-12-12 Procédé, matériel et système de sélection de trajet et de commande de flux

Country Status (3)

Country Link
EP (1) EP2037638A4 (zh)
CN (1) CN100563212C (zh)
WO (1) WO2008086720A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115348208A (zh) * 2021-04-27 2022-11-15 中移(苏州)软件技术有限公司 一种流量控制方法、装置、电子设备和存储介质

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100563212C (zh) * 2006-12-13 2009-11-25 华为技术有限公司 选路及流控的方法、装置和系统
CN102244605B (zh) * 2010-05-10 2014-11-12 大唐移动通信设备有限公司 一种业务面ip地址的选择方法及设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1716870A (zh) * 2004-06-30 2006-01-04 华为技术有限公司 媒体流服务质量上报方法
CN1798364A (zh) * 2004-12-27 2006-07-05 华为技术有限公司 一种在ip承载网中转发业务流的方法
CN1816024A (zh) * 2005-02-01 2006-08-09 中兴通讯股份有限公司 一种在软交换网络中保证通信服务质量的方法
CN101001208A (zh) * 2006-12-13 2007-07-18 华为技术有限公司 选路及流控的方法、装置和系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6744768B2 (en) * 1999-07-14 2004-06-01 Telefonaktiebolaget Lm Ericsson Combining narrowband applications with broadband transport
US7088677B1 (en) * 2002-03-01 2006-08-08 Bellsouth Intellectual Property Corporation System and method for delay-based congestion detection and connection admission control
EP1850541B1 (en) * 2004-09-29 2011-08-31 Sonus Networks, Inc. Controlling time-sensitive data in a packet-based network

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1716870A (zh) * 2004-06-30 2006-01-04 华为技术有限公司 媒体流服务质量上报方法
CN1798364A (zh) * 2004-12-27 2006-07-05 华为技术有限公司 一种在ip承载网中转发业务流的方法
CN1816024A (zh) * 2005-02-01 2006-08-09 中兴通讯股份有限公司 一种在软交换网络中保证通信服务质量的方法
CN101001208A (zh) * 2006-12-13 2007-07-18 华为技术有限公司 选路及流控的方法、装置和系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2037638A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115348208A (zh) * 2021-04-27 2022-11-15 中移(苏州)软件技术有限公司 一种流量控制方法、装置、电子设备和存储介质
CN115348208B (zh) * 2021-04-27 2024-04-09 中移(苏州)软件技术有限公司 一种流量控制方法、装置、电子设备和存储介质

Also Published As

Publication number Publication date
CN101001208A (zh) 2007-07-18
EP2037638A1 (en) 2009-03-18
CN100563212C (zh) 2009-11-25
EP2037638A4 (en) 2009-06-10

Similar Documents

Publication Publication Date Title
JP4988338B2 (ja) 会話型ベアラネゴシエーション
JP4571618B2 (ja) 会話型ベアラの交渉
US7746849B2 (en) Providing packet-based multimedia services via a circuit bearer
US8804532B2 (en) Method and arrangement for adapting to variations in an available bandwidth to a local network
EP2757766B1 (en) Processing method for bearer control
CN101084659B (zh) 用于为移动订户提供专有语音呼叫服务的方法和系统以及用于其的无线软切换设备
JP4758478B2 (ja) 回線交換ドメインとパケット交換ドメインとを相互接続する技術
WO2006063536A1 (fr) Procede et systeme pour maintenir la continuite d'une session
US20010024438A1 (en) Internet telephone system ensuring communication quality and path setting method
JP2006526297A (ja) VoIPシステムにおける呼承認制御
WO2009018744A1 (fr) Procédé d'implémentation, système, passerelle multimédia et contrôleur de passerelle multimédia pour contrôle de routage
EP1266531B1 (en) Method, system and terminal device for activating a packet data subscriber context for packet data
WO2006105732A1 (fr) Procede de transfert de connexion d’appel par commutation de circuit
JP2003324472A (ja) VoIPネットワークシステム
WO2009012665A1 (fr) Procédé pour assurer une continuité d'appel multimédia, équipement et système associés
WO2007025429A1 (fr) Procede evitant la derivation du flux media et dispositif correspondant
WO2009148173A1 (ja) 移動体通信システム、ノード装置及び網間移行制御方法
EP2217015B1 (en) Method, system and device for call forwarding
JP2007506295A (ja) Sipハンドオーバー時に割り当てられた資源を開放する方法
WO2009149667A1 (zh) 被叫接入的方法、装置和系统
EP1436963A1 (en) Method for selecting a media gateway control function based on the monitoring of resources of media gateway functions
GB2410855A (en) Telecommunication system communication sessions
WO2008086720A1 (fr) Procédé, matériel et système de sélection de trajet et de commande de flux
WO2010133185A1 (zh) 一种单模业务连续性实现方法及单模业务连续性系统
WO2006089491A1 (fr) Méthode pour réaliser la fonction de passerelle de média, équipement de contrôle d’accès sans fil et système d’accès

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07871768

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2007871768

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE