WO2005025143A1 - Procede de detection d'etat de controleur de passerelle media par une passerelle media - Google Patents
Procede de detection d'etat de controleur de passerelle media par une passerelle media Download PDFInfo
- Publication number
- WO2005025143A1 WO2005025143A1 PCT/CN2003/000754 CN0300754W WO2005025143A1 WO 2005025143 A1 WO2005025143 A1 WO 2005025143A1 CN 0300754 W CN0300754 W CN 0300754W WO 2005025143 A1 WO2005025143 A1 WO 2005025143A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- media gateway
- gateway controller
- protocol
- controller
- media
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
- H04M7/1205—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
- H04M7/125—Details of gateway equipment
- H04M7/1255—Details of gateway equipment where the switching fabric and the switching logic are decomposed such as in Media Gateway Control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
Definitions
- the present invention generally relates to the field of communication technology, and more particularly, to a method for detecting a state of a media gateway controller by a media gateway in a next generation network.
- the functions or services provided to user terminals are directly related to the switch.
- the control signaling shown in dotted lines
- voice / data bearer shown in solid lines
- the traditional switch 1 constitutes the switching core of the traditional switching network. It can be seen from the figure that, for each user terminal 2, the traditional "call and control" function is integrated with the service, and the call control function for different service requirements is different. This traditional switch cannot separate control from voice / data bearer.
- NGN next-generation networks
- PSTN public switched telephone network
- NGN uses softswitch technology.
- Softswitch is a functional entity that provides real-time service call control and connection control functions for NGN. It is the core of next-generation network call and control.
- softswitches separate the functional modules of traditional switches into Independent network components, each component is divided according to the corresponding function, using business and call control separation, call control and bearer separation technology, to achieve an open network structure, making services independent of the network.
- NGN mainly separates the signaling control part and the voice / data bearer part of the traditional switch, and uses a standard media gateway control protocol such as H.248 / Megaco for interaction.
- FIG. 2 shows a schematic diagram of NGN internal networking.
- User terminal 2 such as an IP phone and SoftPhone
- network 3 usually an IP network
- control signaling shown in dashed lines
- soft switch 4 also called a media gateway controller
- the voice / data bearer (shown as a solid line) is connected to the media gateway 1.
- Softswitch is the control core of NGN. It is responsible for all call processing under its jurisdiction and controls media gateway resources.
- the media gateway converts the media in one network into the media format required by another network. For example, the voice / data bearer is exchanged according to the media gateway control signaling sent by the softswitch.
- the basic structure of NGN is generally divided into: service layer, control layer, transmission layer and access layer.
- the control layer mainly completes functions such as succession control and resource management, and its core is a softswitch, also called a media gateway controller (MGC).
- MSC media gateway controller
- the media gateway controller performs bearer control, resource control, and management on the media gateway (MG).
- the interface between the media gateway controller and the media gateway uses, for example, the Media Gateway Control Protocol (MGCP) or the H.248 / Megaco protocol.
- the MGCP protocol is an earlier media gateway control protocol defined by the IETF (Internet Engineering Task Force).
- the H.248 / Megaco protocol is a media gateway control protocol developed by the IETF, ITU-T, and is used for communication between the media gateway controller and the media gateway.
- the H.248 / Megaco protocol cooperates with other protocols to complete various NGN services.
- Each message in the H.248 / Megaco protocol contains one or more transactions.
- a "Transaction” is constituted by “request” and "response”.
- Each transaction contains one or more contexts.
- Each context contains one or more commands.
- the context defines the connection between some terminals.
- the context is Parameters describing the topology and media mixing / exchange between the terminals can be made, for example, by
- H.248 / Megaco contains several commands, such as Add, Subtract, Move, Modify, Audit Value, Audit Capability, Notify, Service Change commands.
- Various commands implement various services through the parameters they carry. Commands under the H.248 / Megaco protocol are independent of the underlying transport protocol.
- next generation network there are many media gateways (MG) based on the media gateway control protocol H.248 / Megaco protocol. These gateways are distributed in the homes of enterprises or users. They have the characteristics of wide area, large volume, and dynamic IP. .
- the H.248 / Megaco protocol is mainly used for transmission over the user datagram protocol (UDP) in the fixed network
- the UDP protocol does not have the link detection function of the transport layer
- H.248 / Megaco The protocol also does not define whether the media gateway can initiate a message to detect the link state of the softswitch, so that after the media gateway controller fails and restarts, the media gateway cannot know the media gateway control in time without the user actively calling
- the status of the device, the relevant user as the called party will be affected. In this case, for example, it will prevent others from calling the affected user. Summary of the invention
- An object of the present invention is to solve the existing problems in the prior art that the media gateway cannot detect the link state of the media gateway controller because the protocol for communication between the media gateway controller and the media gateway has nothing to do with the underlying transmission protocol. defect.
- Another object of the present invention is to add a detection function of a media gateway controller to a media gateway based on the H.248 / Megaco protocol.
- a method for detecting a state of a media gateway controller by a media gateway is provided, which is characterized in that a protocol extension package is added to an interface protocol for communication between the media gateway and the media gateway controller, The method includes the following steps: a) the media gateway sends the protocol extension package to the media gateway controller; b) the media gateway controller receives the protocol extension package and completes the authentication of the media gateway according to the parameters carried in the protocol extension package;
- the step of authenticating the media gateway by the media gateway controller includes: checking whether the IP address in the protocol extension packet sent by the media gateway is consistent with the data configured in the media gateway controller.
- the protocol extension package includes a request event and a result event, wherein the result event further includes a result of the media gateway controller's legality detection of the media gateway.
- the Notify command in the H.248 / Megaco protocol carries the parameters in the protocol extension package to complete the detection of the status of the media gateway controller by the media gateway.
- the media gateway controller communicates with the media gateway through
- the method further includes starting a timer while the media gateway sends a protocol extension packet to the media gateway controller, or after a delay interval.
- the timer is reset after detecting a successful response from the media gateway controller.
- an alarm message is sent and registered with the standby gateway.
- the media gateway controller After detecting that the media gateway controller fails to respond more than a predetermined number of times, or after the timer time is set to exceed a predetermined time period, sending an alarm message and registering with the standby gateway.
- the media gateway can actively detect the connection and communication status of the media to the gateway controller.
- the media gateway controller fails, Registering with the backup media gateway controller, this feature can well support the network home function in the event of a disaster.
- the media gateway can immediately learn the information that the current media gateway controller has failed, and immediately register the information with the backup media gateway controller, thereby registering the impact caused thereby. Reduced to a minimum.
- Figure 1 shows a schematic diagram of the internal networking of a traditional switch
- Figure 2 shows a schematic diagram of the internal networking of the NGN
- FIG. 3 shows a flowchart of a method for detecting the status of a media gateway controller by a media gateway according to the present invention.
- FIG. 3 shows a flowchart of a method for detecting a state of a media gateway controller by a media gateway according to the present invention.
- Specific embodiments of the present invention are described based on the H.248 / Megaco protocol, but the present invention is not limited thereto.
- the present invention is also applicable to other networks using a protocol similar to the H.248 / Megaco protocol between the media gateway and the media gateway controller, for example, in a network using the MGCP protocol.
- each message includes one or more transactions, each transaction includes one or more contexts, and each context includes one or more commands.
- a "request” and "response” constitute a transaction.
- the connection between terminals is defined by the context.
- the media gateway detects the status of the media gateway controller.
- the basic idea of the present invention is: In the interface protocol for communication between the media gateway controller and the media gateway, a new protocol extension package is defined, for example, when using H.248 / In the case of the egaco protocol as an interface protocol, a H.248 / Megaco protocol extension package is newly defined, which is referred to as the H.248 protocol heartbeat packet HeartBeat in this article.
- the Notify command in the H.248 / Megaco protocol is used to carry the extended protocol extension.
- Each parameter in the HeartBeat is included, and the parameters are authenticated to implement the detection of the state of the media gateway controller by the media gateway.
- the embodiment is described based on the H.248 / Megaco protocol.
- a parameter defined as the H.248 / Megaco protocol heartbeat packet HeartBeat is added to the Notify command under the H.248 / Megaco protocol.
- the H.248 / Megaco protocol heartbeat packet defined here is a request-response type protocol extension packet, which is a collection of heartbeat request events and heartbeat result events.
- the content defined in the heartbeat packet is used as a parameter of the Notify command. Parameter to complete the function of detecting the status of the media gateway controller by the media gateway.
- Heartbeat packet HeartBeat can be defined as follows:
- Protocol extension package name HeartBeat; Protocol extension package version: 1;
- Heartbeat request event (This parameter type is Event):
- Heartbeat request event ID hrtbtreq (0x0001)
- Heartbeat result event identifier hrtbtrlt (0x0001) This parameter is mainly used to obtain the result of detecting the validity of the heartbeat packet sent by the media gateway by the media gateway controller.
- enum is an enumerated type, which is a data structure that defines the various possible outcomes of the resulting event.
- This value is the detection result given by the media gateway controller based on the legality detection of the heartbeat packet. Then, the determined detection result is sent to the media gateway. As follows, the detection results returned by the media gateway controller to the media gateway include:
- 0x01 Failed-InvalidMGW, indicating that the current media gateway is an illegal media gateway
- 0x02 Failed-OtherReason, indicating that the current media gateway rejected the heartbeat request event for other reasons.
- the authentication process based on the add-on protocol extension package that is, by checking whether the IP address in the protocol extension package matches the data configured on the softswitch, the necessary steps used are (general example of communication between MGC and MG):
- step 1
- the MG initiates a heartbeat packet request message to the MGC:
- the MG sends a Notify command requesting an event to the MGC, allocates a transaction identifier 100 and an event request identifier 300 for this, requests the MGC to perform a legality check and returns a heartbeat result event (HeartBeat / hrtbtrit).
- the MG starts a timer T1.
- the timer may be, for example, a software timer, which may be directly called by software through an interface function of an operating system (such as VxWORKS, etc.).
- the period of the timer can be configured by the maintenance station, for example.
- step 1 The operation of step 1 can be programmed as follows:
- the protocol used is "MEGACO", and the version number of the protocol is "1".
- Softswitch IP address 123.123.123.4; port number: 55555.
- the transaction ID is "100”.
- the ID of the request event is "300", which represents the ID of the event "HeartBeat / hrtbtreq”.
- the Notify command sets the identity endpoint ID to "root", which represents the entire gateway.
- the MGC When the MGC receives the Notify command sent by the MG, it starts to verify the validity of the gateway. That is, it checks whether the IP address in the heartbeat packet matches the data configured on the softswitch. After the validity verification is completed, the MGC returns a corresponding response result to the MG, and the response result is sent back to the MG by using the Notify command of the response type.
- the event parameter In the Notify command of this response type, the event parameter is the gateway legality authentication result.
- the transaction ID 100 in the Notify command of the response type is consistent with the Notify transaction ID sent by M0, and the event ID 300 is also consistent with the event ID of the request message.
- step 2 can be programmed as follows: MEGACO / 1 [125.125.125.111 ⁇ : 55555
- Step 3 represents the response message, whose transaction ID is "100”, which is the same as the transaction ID in the request message; the event ID is "300”, which represents the "heartbeat result event HeartBeat / hrtbtrlt”, and It is the same as the event ID in the heartbeat request message.
- the MG After receiving the heartbeat response, the MG checks the returned heartbeat response result. If the response is successful, for example, the value of the heartbeat result event is "0x00", which indicates that the gateway authentication is successful, and the status of the media gateway controller is normal. In this case, Reset the timer. If it is a failure response, for example, the value of the heartbeat result event is "0x01", or the value of the heartbeat result event is "0X02", the background maintenance personnel should be notified to solve the problem. At the same time, the current gateway is notified to register with the standby gateway.
- the above steps can be repeated periodically by setting a timer to achieve the real-time detection of the MGC status by the MG.
- the timer interval setting can be manually configured.
- the timer is set with reference to network traffic in a manner that does not increase too much traffic load as much as possible.
- step 1 The operation of step 1 can be programmed as follows:
- the protocol used is "MEGACO", and the version number of the protocol is "1".
- Softswitch IP address 123.123.123.4; port number: 55555.
- the transaction ID is "100”.
- the ID of the request event is "300", which represents the ID of the event "HeartBeat / hrtbtreq”.
- the Notify command sets the identity endpoint ID to "root”, which represents the entire gateway.
- Step 2 The timer expires and the MG does not receive a response from the Notify message. Retransmit the message from step 1, reset the timer at the same time, and increment the retransmission counter.
- Step 3 Repeat Step 2 to check the retransmission counter.
- the media gateway actively sends a message to the media gateway controller, such as a heartbeat packet message. Therefore, after the media gateway controller fails, the status of the media gateway controller can be known in time, and it can be timely sent to the standby gateway. registered.
- This feature can well support the dual-homing function of the network in the event of a disaster.
- the dual-homing function is a network self-healing design concept and is designed to provide protection to a certain network node after a failure.
- the so-called “attribution” refers to the superior office to which an end office belongs.
- “Dual-homing” refers to assigning two superior offices to an end office, so this office has two entrances to other offices, and its business requirements are also divided into two. Generally, the traffic in the office is divided into two. When one office fails, 50% of the traffic in the other office is still not affected. Although the dual-homing structure itself does not have recovery capabilities, after it is used with digital cross-connect equipment, if the office-to-backup optical fiber line has sufficient capacity, it can generally recover more than 50% of traffic through the backup superior office. Thereby, the media gateway and the user terminal are connected to two softswitches at the same time, such as softswitch1 and softswitch2.
- Softswitch When one of the softswitches, such as Softswitch1, fails, the user terminal and the media gateway can obtain the information and register with the standby softswitch, such as Softswitch2, so as to minimize the impact on the result.
- the standby softswitch such as Softswitch2
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU2003261630A AU2003261630A1 (en) | 2003-09-05 | 2003-09-05 | Method of detecting the status of a media gateway controller by a media gateway |
CNB03826949XA CN100394744C (zh) | 2003-09-05 | 2003-09-05 | 由媒体网关检测媒体网关控制器状态的方法 |
PCT/CN2003/000754 WO2005025143A1 (fr) | 2003-09-05 | 2003-09-05 | Procede de detection d'etat de controleur de passerelle media par une passerelle media |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2003/000754 WO2005025143A1 (fr) | 2003-09-05 | 2003-09-05 | Procede de detection d'etat de controleur de passerelle media par une passerelle media |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2005025143A1 true WO2005025143A1 (fr) | 2005-03-17 |
Family
ID=34230867
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2003/000754 WO2005025143A1 (fr) | 2003-09-05 | 2003-09-05 | Procede de detection d'etat de controleur de passerelle media par une passerelle media |
Country Status (3)
Country | Link |
---|---|
CN (1) | CN100394744C (fr) |
AU (1) | AU2003261630A1 (fr) |
WO (1) | WO2005025143A1 (fr) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN100459738C (zh) * | 2005-06-21 | 2009-02-04 | 华为技术有限公司 | 控制和承载分离网络中的双归属实现方法 |
WO2009121273A1 (fr) * | 2008-04-01 | 2009-10-08 | 华为技术有限公司 | Procédé d'application, équipement et système pour la relation de la base et de l'extension des paquets |
US8571546B2 (en) | 2004-08-29 | 2013-10-29 | Huawei Technologies Co., Ltd. | Method for implementing dual-homing |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2011061577A1 (fr) * | 2009-11-23 | 2011-05-26 | Alcatel Lucent | Système et procédé de transfert intercellulaire en cas de maintenance |
CN102577483A (zh) * | 2011-12-23 | 2012-07-11 | 华为技术有限公司 | 一种媒体网关控制器故障时实现业务的方法、设备及系统 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2001015487A1 (fr) * | 1999-08-23 | 2001-03-01 | Nortel Networks Limited | Procede et appareil permettant d'associer un identificateur de communication de bout en bout a une connexion dans un reseau multimedia a commutation de paquets |
EP1109368A2 (fr) * | 1999-12-15 | 2001-06-20 | Nortel Networks Corporation | Dispositif, procédé et produit de programme informatique pour supporter des services de chemin porteur dans un réseau de contrôle distribué |
JP2002271399A (ja) * | 2001-03-09 | 2002-09-20 | Nec Corp | 電話システム及び電話接続監視方法 |
JP2002325101A (ja) * | 2001-04-26 | 2002-11-08 | Hitachi Ltd | パケット通信網およびその異常検出方法 |
-
2003
- 2003-09-05 AU AU2003261630A patent/AU2003261630A1/en not_active Abandoned
- 2003-09-05 WO PCT/CN2003/000754 patent/WO2005025143A1/fr active Application Filing
- 2003-09-05 CN CNB03826949XA patent/CN100394744C/zh not_active Expired - Fee Related
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2001015487A1 (fr) * | 1999-08-23 | 2001-03-01 | Nortel Networks Limited | Procede et appareil permettant d'associer un identificateur de communication de bout en bout a une connexion dans un reseau multimedia a commutation de paquets |
EP1109368A2 (fr) * | 1999-12-15 | 2001-06-20 | Nortel Networks Corporation | Dispositif, procédé et produit de programme informatique pour supporter des services de chemin porteur dans un réseau de contrôle distribué |
JP2002271399A (ja) * | 2001-03-09 | 2002-09-20 | Nec Corp | 電話システム及び電話接続監視方法 |
JP2002325101A (ja) * | 2001-04-26 | 2002-11-08 | Hitachi Ltd | パケット通信網およびその異常検出方法 |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8571546B2 (en) | 2004-08-29 | 2013-10-29 | Huawei Technologies Co., Ltd. | Method for implementing dual-homing |
CN100459738C (zh) * | 2005-06-21 | 2009-02-04 | 华为技术有限公司 | 控制和承载分离网络中的双归属实现方法 |
WO2009121273A1 (fr) * | 2008-04-01 | 2009-10-08 | 华为技术有限公司 | Procédé d'application, équipement et système pour la relation de la base et de l'extension des paquets |
US8750318B2 (en) | 2008-04-01 | 2014-06-10 | Huawei Technologies Co., Ltd. | Method, apparatus and system for applying relations between package base and extension |
Also Published As
Publication number | Publication date |
---|---|
CN100394744C (zh) | 2008-06-11 |
AU2003261630A1 (en) | 2005-03-29 |
CN1820466A (zh) | 2006-08-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
Andreasen et al. | Media gateway control protocol (MGCP) version 1.0 | |
RU2386219C2 (ru) | Способ обработки отказов в представлении обслуживания | |
US7894410B2 (en) | Method and system for implementing backup based on session border controllers | |
JP4001813B2 (ja) | テレコミュニケーションシステムにおけるユーザターミナルへの接続の監視 | |
JP3753316B2 (ja) | 呼詳細記録の生成方法 | |
WO2004032421A1 (fr) | Procede d'adjonction de dispositifs a un systeme de gestion | |
WO2007003094A1 (fr) | Procede et systeme de realisation d'un acces de terminal conventionnel au domaine ims | |
JP2007504758A (ja) | 遠隔通信ネットワークシステムおよびセッション開始プロトコルを使用する通信サービス方法 | |
US20100074100A1 (en) | Proxy server, communication system, communication method and program | |
CN101416468A (zh) | 通信系统中由网络发起的ims注册 | |
WO2009070999A1 (fr) | Procédé et dispositif pour ajuster l'état de relais | |
RU2513760C2 (ru) | Способ и система для доступа абонентов традиционной стационарной сети к домену ims | |
US7257111B2 (en) | Method and system of managing a call in a telecommunication system | |
WO2008025257A1 (fr) | Procédé d'intercommunication et système de communication entre différents réseaux | |
US20050180396A1 (en) | Managing routing path of voice over internet protocol (VoIP) system | |
US7539178B2 (en) | Connection of users in hybrid communication networks | |
JP3746713B2 (ja) | インターネット電話システムおよび情報処理装置 | |
WO2005025143A1 (fr) | Procede de detection d'etat de controleur de passerelle media par une passerelle media | |
WO2008049346A1 (fr) | Dispositif, procédé et système pour enregistrer un dispositif | |
JP2001516531A (ja) | 登録プロトコル | |
Cisco | Commands: debug ppp bap through debug sdllc | |
Cisco | Cisco BTS 10200 Softswitch Release Notes for Release 3.1V6 | |
JP2001517385A (ja) | 着信呼ルーティング | |
Loughney et al. | Signalling connection control part user adaptation layer (SUA) | |
Cisco | FastPAD Events |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 03826949.X Country of ref document: CN |
|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
122 | Ep: pct application non-entry in european phase | ||
NENP | Non-entry into the national phase |
Ref country code: JP |