[go: up one dir, main page]

WO2006026929A1 - A method for monitoring the state of the media gateway controller by the media gateway - Google Patents

A method for monitoring the state of the media gateway controller by the media gateway Download PDF

Info

Publication number
WO2006026929A1
WO2006026929A1 PCT/CN2005/001442 CN2005001442W WO2006026929A1 WO 2006026929 A1 WO2006026929 A1 WO 2006026929A1 CN 2005001442 W CN2005001442 W CN 2005001442W WO 2006026929 A1 WO2006026929 A1 WO 2006026929A1
Authority
WO
WIPO (PCT)
Prior art keywords
media gateway
message
inactivity
timer
mgc
Prior art date
Application number
PCT/CN2005/001442
Other languages
English (en)
French (fr)
Inventor
Yangbo Lin
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
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=36036079&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=WO2006026929(A1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to AT05783996T priority Critical patent/ATE429751T1/de
Priority to DE200560014099 priority patent/DE602005014099D1/de
Priority to CA 2550291 priority patent/CA2550291C/en
Priority to BRPI0506457A priority patent/BRPI0506457B1/pt
Priority to US10/584,972 priority patent/US7843853B2/en
Priority to EP05783996A priority patent/EP1744488B1/en
Priority to JP2006545893A priority patent/JP4348560B2/ja
Publication of WO2006026929A1 publication Critical patent/WO2006026929A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1023—Media gateways
    • H04L65/103—Media gateways in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1033—Signalling gateways
    • H04L65/104—Signalling gateways in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1043—Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/16—Threshold monitoring

Definitions

  • the present invention relates to next generation network technologies, and more particularly to a method for implementing a media gateway to monitor the state of a media gateway controller.
  • the Media Gateway Controller (MGC) and Media Gateway (MG) are two key components in the Next Generation Network (NGN).
  • the MGC is responsible for the call control function, and the MG is responsible for the service bearer function, thereby separating the call control plane and the service bearer plane, thereby fully sharing network resources, upgrading equipment and service expansion, and greatly reducing development and maintenance costs, as shown in Figure 1 below. Show.
  • the Media Gateway Control Protocol is the main protocol for communication between the MG and the MGC.
  • H.248/MeGaCo and MGCP protocols there are two widely used H.248/MeGaCo and MGCP protocols. Among them, the MGCP agreement was formulated by the IETF in October 1999 and revised in January 2003. The H.248/MeGaCo agreement was jointly formulated by the IETF and ITU in November 2000 and was finalized on June 4, 2003.
  • Terminations various resources on the MG are abstractly represented as Terminations.
  • the terminal is further divided into physical terminals and temporary terminals.
  • the former represents some semi-permanent physical entities, such as time division multiplexing (TDM) channels, etc., and the latter represents some public resources that are temporarily applied and released after use, such as real-time transmission protocols. (RTP) stream, etc.
  • TDM time division multiplexing
  • RTP real-time transmission protocols.
  • the combination between terminals is abstracted as a context.
  • the context can contain multiple terminals, so the relationship between the terminals is described in terms of Topology.
  • the connection of the call is actually the operation of the terminal and the context. This is done through commands and responses between the MGC and the MG.
  • the parameters carried by the command also called descriptors (Descriptor) are classified into categories such as Property, Signal, Event, and Statistic.
  • Descriptor descriptors
  • the parameters with business relevance are logically aggregated into packages.
  • the MGC and the MG know each other whether the operation of the other party is normal. Very important.
  • the MG is usually in a passive position as a controlled party. Unlike the MGC, it can flexibly use the auditing method to actively query it. The MG that is controlled therefore needs the media gateway control protocol to provide an effective means to monitor the status of the MGC.
  • the Inactivity Timer packet defined in the H.248 protocol, the Inactivity Timeout event of the packet, and the Maximum Inactivity Time parameter of the event provide a way for the MG to monitor the MGC status. means.
  • the mechanism is as follows:
  • the MGC sends an Inactivity Timeout event of the Inactivity Timer packet to the root terminal of the MG on the MG, and sets the Maximum Inactivity Time parameter of the event, indicating that the MG starts detecting whether the quiet time of the message from the MGC exceeds the parameter value.
  • the MG detects all incoming messages based on this, and once this happens, the notification (Notify) message with the Inactivity Timeout event is sent from the root terminal to the MGC. If this Notify message is not responded, the MG will consider the MGC failure and initiate an exception handling process, such as initiating registration with the backup MGC.
  • the MGC In order for the MG to know that the MG is in a normal state, the MGC should ensure that the message interval sent to the MG does not exceed the value of the Maximum Inactivity Time parameter set. Therefore, once there is no service control message to be sent during this period, the MGC needs to send another test or keep it.
  • the activated message for example, sends a null Audit value message to the Root terminal on the MG.
  • the MG can detect the MMC message silence time in two ways: One way is to set a timer that is initially 0 and set the timeout limit. Each message from the MGC will trigger the timer to reset to 0, and once the timer Eventually, the Inactivity Timeout event will be reported to the MGC. Another way is to set an initial message receiving flag of 0 and a normal timeout timer. Each message from the MGC will trigger the flag to be set to 1. Once the timer expires, the flag is still 0, Inactivity Timeout event. The MGC will be reported, otherwise the MG resets the flag to 0 and restarts the timer.
  • the monitoring mechanism of the MGC status of the MGC needs to be sent by the MGC after the corresponding packet, event, and parameter are sent. If the MGC does not implement the packet, the packet is not configured to be sent, the sudden failure fails to deliver the message, or The MG does not get this information because the MG does not get the information, and the MG will lose the effective mechanism to monitor the MGC status. 2.
  • the monitoring mechanism of the MGC status of the MG depends on the MGC sending a special message of non-service control to ensure that the message interval does not time out.
  • the present invention provides the following technical solutions:
  • a method for implementing a media gateway to monitor a state of a media gateway controller includes:
  • the idle timer is set on the media gateway to monitor a silent time of the media gateway controller message.
  • a normal timer and a message receiving flag may also be set on the media gateway to monitor a quiet time of the media gateway controller message.
  • a notification message is sent to the media gateway controller that triggers the media gateway controller to return to a normal state.
  • the method also sets a timeout period for determining whether the silence time exceeds a prescribed value.
  • the timeout period of the inactivity timer or the normal timer is reset according to the maximum inactivity time.
  • the timeout period of the inactivity timer may be set to the maximum inactivity time, or the timeout period of the normal timer may be set to one-half of the maximum inactivity time.
  • the mediation controller is configured to monitor the media gateway controller on the media gateway, when the number of consecutive timeouts of the inactivity timer reaches a predetermined threshold, the media gateway initiates an exception handling process; if the media gateway sets a normal timer and a message receiving flag to monitor the media The gateway controller, when the normal timer expires and the message receiving flag still shows that the number of unreceived messages continues to occur When the threshold is set, the media gateway starts the exception handling process.
  • the pause counter is used to count the consecutive timeouts of the inactivity timer, and the idle counter is reset when the media gateway receives any message from the media gateway controller; Setting a normal timer and a message receiving flag on the media gateway to monitor the media gateway controller, using the inactivity counter to count the number of consecutive occurrences of the normal timer timeout and the message receiving flag still showing the unreceived message, and at the media gateway The inactivity counter is reset upon receipt of any message from the Media Gateway Controller.
  • the invention starts the monitoring test mechanism after the MG registers with the MGC successfully, and does not need to wait until the MGC sends the corresponding packet, event and parameters to start. Therefore, the monitoring of the MGC by the MG is no longer dependent on the state of the MGC. The problem of failure of the monitoring mechanism due to abnormal MGC is avoided.
  • the present invention makes it unnecessary for the MGC to send a similar test or keep alive message when there is no service control message to be sent, thus reducing the burden on the MGC and the network. Even if the MGC itself wants to monitor the status of the MG by sending a message like a null audit value, its control of the transmission timing is no longer limited by the above-mentioned maximum inactivity time parameter.
  • FIG. 1 is a schematic diagram of networking of MG and MGC in an NGN
  • Figure 2 is a schematic diagram of the MG monitoring MGC status.
  • call control and service bearers are implemented on separate components of the MGC and the MG, and the NGN packetized network is communicated between the MGC and the MG. Therefore, it is very important for the MGC and the MG to know each other whether the operation is normal.
  • the invention provides a single and reliable method for the MG to understand the operational status of the MGC from the application layer in real time by enhancing the processing mechanism of the corresponding packets, events and parameters in the H.248 protocol.
  • An Inactivity Timer is deployed on the MG.
  • the timeout period is preset to a configurable default value.
  • the difference between the inactivity timer and the normal timer is that the inactivity timer can be reset and automatically restarted at any time, and the normal timer will not be used anytime. Reset will continue to timeout. Both the inactivity timer and the normal timer need to be reset to restart the timer.
  • the MG After the MG successfully registers with the MGC, that is, after the MGC becomes the master MGC, the MG actively starts the inactivity timer according to the returned registration success message, and starts monitoring the MGC status.
  • the MG receives any message from the master MGC, whether it is a request message or a response message, it triggers the MG to reset the inactivity timer, and the inactivity timer automatically restarts timing.
  • the MG sends a notification (Notify) message with an Inactivity Timeout event from the root terminal to the MGC, and resets the inactivity timer. Since this is not an event that the MGC pre-requests the MG to detect, the event ID (EventID) of the event is 0.
  • the message from the master MGC includes an Inactivity Timeout event of the Inactivity Timer packet sent to the Root terminal on the MG, and the Maximum Inactivity Time parameter of the event is set
  • the MG will record the Inactivity Timeout event and its event identifier on the Root terminal, and set the duration of the above-mentioned inactivity timer to the Maximum Inactivity Time parameter value.
  • the event identifier of the event will be the event identifier detected by the MGC request and is no longer 0.
  • the Notify message sent by the MG to the MGC with the Inactivity Timeout event is similar to a heartbeat trigger, which will cause the MGC to return a response as a heartbeat reflection.
  • This response like any other message from the MGC, can be used as a normal MGC status flag and triggered.
  • the MG resets the inactivity timer. However, after the Notify message is sent, if the MG is unable to obtain any message from the MGC, including the response to the Notify message, before the cessation timer expires again, the MG may consider the MGC to be faulty and initiate an exception handling procedure, such as Initiate registration with the backed up MGC.
  • an initial idle counter (Inactivity Counter) is deployed on the MG (the principle of the rest counter is the same as the above-mentioned inactivity timer), The number of times the timer expires is counted. The count of the inactivity counter is incremented by 1 when the inactivity timer expires; whenever the MG gets from the MGC Any message, including a response to a Notify message with an Inactivity Timeout event, resets the inactivity counter to zero.
  • the current value of the inactivity counter that is, the number of consecutive timeouts of the above-mentioned inactivity timer exceeds a certain preset threshold, it can be determined that an abnormality occurs in the state of the MGC, and the MG will start an exception processing flow.
  • the MG monitors the MGC as follows:
  • the MG After receiving the registration success message returned by the MGC, the MG starts the inactivity timer and the suspend counter.
  • the timeout period of the inactivity timer is set to the default value A, and the initial value of the inactivity counter is set to 0.
  • the MG receives any request or response message sent by the MGC to reset the inactivity timer and the inactivity counter.
  • the inactivity timer timeout sends a notification message containing the inactivity timeout event to the MGC, the event flag is 0, and the inactivity counter is incremented by one.
  • the MG After receiving the MGC response message, the MG resets the inactivity timer and the inactivity counter.
  • the MG After receiving the request message that the MGC sends the suspension timer packet, the inactivity timeout event, and the maximum inactivity time parameter value B, the MG sets the timeout period of the inactivity timer to the maximum inactivity time B, and resets the inactivity timer. And the stop counter, and record the event identifier X of the rest timeout event.
  • the MG returns a response message to the MGC.
  • the MG receives any request or response message sent by the MGC to reset the inactivity timer and the inactivity counter.
  • the inactivity timer timeout sends a notification message containing the inactivity timeout event to the MGC, the event identifier is X, and the inactivity counter is incremented by one.
  • the MG receives any request or response message sent by the MGC to reset the inactivity timer and the inactivity counter.
  • Inactivity timer expires
  • the MG sends a notification message containing the inactivity timeout event to the MGC.
  • the event identifier is X and the inactivity counter is incremented by one.
  • Inactivity timer expires
  • the MG sends a notification message containing the inactivity timeout event to the MGC.
  • the event identifier is X, and the inactivity counter is incremented by 1.
  • the count value is 2.
  • the current value of the inactivity counter reaches the preset threshold n, indicating that the inactivity timer has been consecutive n
  • the timeout expires, and the notification message sent by the MG to the MGC has not received any message from the MGC. Therefore, the MG confirms the MGC failure and starts an exception handling process, such as initiating a service change.
  • the MG autonomously deploys an initial 0 message reception flag and a preset default value timeout timer to detect the silence time of the MGC message. After the MG registers with the MGC successfully, that is, after the MGC becomes the master MGC, the MG actively starts the rest timer start timing according to the returned registration success message, and starts monitoring the MGC status.
  • the flag is set to 1 whenever the MG gets a message from the MGC. Once the timer expires and the flag is still 0, the MG reports the Inactivity Timeout event to the MGC, otherwise the MG resets the flag to 0 and restarts the Timer.
  • the message from the master MGC includes an Inactivity Timeout event of the Inactivity Timer packet sent to the Root terminal on the MG, and the Maximum Inactivity Time parameter of the event is set.
  • the MG will record the Inactivity Timeout event and its event identifier on the Root terminal, and set the timeout period of the timer to one-half of the value of the Maximum Inactivity Time parameter.
  • an initial inactivity counter (Inactivity Counter) is additionally deployed on the MG (the principle of the rest counter is the same as in the first embodiment), The timer expires and the above message receiving flag still displays the number of consecutive occurrences of the unreceived message for counting. Once the current value of the inactivity counter exceeds a predetermined threshold, it can be determined that the status of the MGC is abnormal, and the MG will Start the exception handling process. Other operations are similar to those in the first embodiment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Environmental & Geological Engineering (AREA)
  • General Business, Economics & Management (AREA)
  • Business, Economics & Management (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Telephonic Communication Services (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
  • Monitoring And Testing Of Transmission In General (AREA)
  • Communication Control (AREA)
  • Computer And Data Communications (AREA)
  • Alarm Systems (AREA)
  • Selective Calling Equipment (AREA)

Description

媒体网关监测媒体网关控制器状态的实现方法
技术领域 本发明涉及下一代网络技术， 尤其涉及一种媒体网关监测媒体网关控 制器状态的实现方法。
背景技术
媒体网关控制器（MGC )和媒体网关 （MG )是下一代网络（NGN ) 中的两个关键构件。 MGC 负责呼叫控制功能, MG 负责业务承载功能， 藉此实现呼叫控制平面和业务承载平面的分离， 从而充分共享网络资源， 筒化设备升级和业务扩展， 大大降低开发和维护成本， 如下图 1所示。
媒体网关控制协议是 MG和 MGC之间通信的主要协议， 目前应用较 为广泛的有 H.248/MeGaCo和 MGCP两种协议。其中 , MGCP协议由 IETF 于 1999年 10月制订并于 2003年 1月修订， H.248/MeGaCo协议由 IETF 和 ITU于 2000年 11月共同制订并于 2003年 6月 4 订。
以 H.248 协议.为例， MG 上的各种资源被抽象表示为终端 ( Termination )。 终端又分为物理终端和临时终端， 前者代表一些具有半 永久存在性的物理实体， 例如时分复用 ( TDM )通道等, 后者代表一些临 时申请并在用后释放的公共资源， 例如实时传输协议（RTP ) 流等。 终端 之间的组合被抽象表示为上下文（Context )。 上下文可以包含多个终端， 因而以拓朴（Topology )来描述终端间的相互关系。
基于协议的这种抽象模型， 呼叫的接续实际上就是对终端和上下文的 操作。 这种操作通过 MGC和 MG之间的命令 ( Command )请求和响应来 完成。 命令所携带的参数， 也称为描述符 （Descriptor ), 被划分为属性 ( Property )、 信号（ Signal )、 事件（ Event )、 统计（Statistic )等类别。 具 有业务相关性的参数逻辑上聚合成为包 （ Package )„
因为呼叫控制和业务承载分别在 MGC和 MG这两个分离的构件上实 现 , 而 MGC和 MG之间又是基于 NGN这种分组化的网络进行通信， 所 以 MGC和 MG相互了解对方运作是否正常就非常重要。 尤其是 MG作为 受控方通常处于被动地位， 不像 MGC可以灵活使用审计方式主动查询其 所控制的 MG, 因此更需要媒体网关控制协议提供有效的手段使其可以监 测 MGC的状态。
H.248协议中定义的休止定时器（Inactivity Timer )包、 该包的休止超 时 （ Inactivity Timeout ) 事件、 以及该事件的最大休止时间 （ Maximum Inactivity Time )参数， 为 MG监测 MGC状态提供了一种手段。 其机制如 下：
MGC向 MG上代表网关整体的根（Root )终端下发 Inactivity Timer 包的 Inactivity Timeout事件, 并设置该事件的 Maximum Inactivity Time参 数，指示 MG开始检测来自 MGC的消息静默时间是否超过该参数值。 MG 据此检测所有进入的消息， 一旦出现该情况即从 Root 终端发送附带 Inactivity Timeout事件的通报 ( Notify ) 消息上报 MGC。 如果此 Notify消 息没有得到响应， MG将认为 MGC故障而启动异常处理流程， 例如向备 份的 MGC发起注册。
MGC为了让 MG了解自己状态正常， 应该确保发给 MG的消息间隔 不超出所设置的 Maximum Inactivity Time参数值， 因此一旦在此期间没有 业务控制消息需要发送时， MGC 就需要另外发送类似测试或者保持激活 的消息， 例如向 MG上的 Root终端发送空审计值（Audit Value ) 消息。
MG检测 MGC消息静默时间可以采用两种方式： 一种方式是设置一 个初始为 0并设置超时上限的定时器， 每个来自 MGC的消息都将触发该 定时器复位为 0, 而一旦该定时器最终超时， Inactivity Timeout事件就将 上报 MGC。 另一种方式是设置一个初始为 0的消息接收标志和一个普通 超时定时器， 每个来自 MGC的消息都将触发该标志设置为 1 , 一旦定时 器超时而该标志仍然为 0, Inactivity Timeout事件就将上报 MGC, 否则 MG将该标志复位为 0并重启定时器。
上述方案存在以下缺点：
I、 MG对 MGC状态的监测机制需要 MGC下发相应的包、 事件和参 数后才能启动， 如果 MGC因为没有实现该包、 没有配置下发该包、 突然 故障没能来得及下发消息、 或者下发消息意外丢掉等等可能的原因而导致 MG没有得到这些信息， MG将失去监测 MGC状态的有效机制。 2、 MG对 MGC状态的监测机制依赖 MGC发送非业务控制的特殊消 息来确保消息间隔不会超时， 这不仅给 MGC增加了额外的负担， 而且给 网络增加了额外的流量， 然而实际上这并不能确保 MG上不会出现 MGC 消息静默超时， MG最终还是要依靠 Notify消息是否有响应来做判断。 发明内容
本发明的目的在于提供一种媒体网关监测媒体网关控制器状态的实 现方法， 以解决现有技术中因 MC监测 MGC的状态需要依赖于 MGC的 配合而存在可能导致监测失效的问题。
为解决上述问题， 本发明提供以下技术方案：
一种媒体网关监测媒体网关控制器状态的实现方法， 包括：
A、 当所述媒体网关向媒体网关控制器注册后， 根据返回的注册成功 消息监测所述媒体网关控制器；
B、 根据所述媒体网关控制器消息的静默时间确定所述媒体网关控制 器的状态。
其中， 在所述媒体网关上设置休止定时器监测所述媒体网关控制器消 息的静默时间。
也可以在所述媒体网关上设置普通定时器和消息接收标志监测所述 媒体网关控制器消息的静默时间。
而且， 在静默时间超时时向媒体网关控制器发送触发媒体网关控制器 返回状态正常的通知消息。
所述方法还设置用于判断所述静默时间是否超过规定值的超时时长。 当所述媒体网关从媒体网关控制器接收到包含最大休止时间的消息 时， 将根据该最大休止时间重新设置休止定时器或普通定时器的超时时 长。 具体而言可以将休止定时器的超时时长设置为该最大休止时间， 或者 将普通定时器的超时时长设置为该最大休止时间的二分之一。
如果媒体网关上设置休止定时器监测媒体网关控制器， 当该休止定时 器连续超时的次数达到预定的阈值时， 媒体网关启动异常处理流程； 如果 媒体网关上设置普通定时器和消息接收标志监测媒体网关控制器， 当该普 通定时器超时而消息接收标志仍显示未收到消息连续出现的次数达到预 定的阔值时， 媒体网关启动异常处理流程。
如果媒体网关上设置休止定时器监测媒体网关控制器， 采用休止计数 器对所述休止定时器的连续超时次数进行计数， 并在媒体网关接收到媒体 网关控制器的任何消息时复位该休止计数器； 如果在媒体网关上设置普通 定时器和消息接收标志监测媒体网关控制器， 釆用休止计数器对所述普通 定时器超时而消息接收标志仍显示未收到消息的连续出现次数进行计数， 并在媒体网关接收到媒体网关控制器的任何消息时复位该休止计数器。
本发明具有以下有益效果：
1、 本发明在 MG向 MGC注册成功后即启动监测试机制， 而不需要等 到 MGC下发相应的包、 事件和参数后才能启动， 因此， MG对 MGC的 监测不再依赖于 MGC的状态， 避免了因 MGC不正常而导致监测机制失 效的问题。
2、本发明使得 MGC在没有业务控制消息需要发送时也不必另外发送 类似测试或者保持激活的消息， 因此降低了 MGC 和网络的负担.。 即使 MGC 自己想要通过发送类似空审计值这样的消息来监测 MG的状态， 其 对发送时机的控制也不必再受限于上述最大休止时间参数。
附图说明 图 1为 NGN中 MG和 MGC组网示意图；
图 2为 MG监测 MGC状态示意图。
具体实施方式 在 NGN中， 呼叫控制和业务承载分别在 MGC和 MG分离构件上实 现， MGC和 MG之间基于 NGN分组化的网络进行通信， 因此 MGC和 MG相互了解对方运作是否正常非常重要。 本发明通过增强 H.248协议中 相应的包、 事件和参数的处理机制， 为 MG从应用层实时了解 MGC的运 作状态提供一种筒单而可靠的方法。
实施例一
在 MG上自主部署一个休止定时器（ Inactivity Timer )， 其超时的时长 预设为一个可以配置的缺省值。 休止定时器与普通定时器的区别在于： 休 止定时器可以随时被复位并自动重新开始计时， 普通定时器则不会被随时 复位而将一直达到超时。休止定时器和普通定时器超时后都需要被复位才 能重新开始计时。
当 MG向 MGC注册成功， 即该 MGC成为主控 MGC后， MG根据返 回的注册成功消息主动启动休止定时器， 并开始对 MGC状态进行监测。 当 MG收到来自主控 MGC的任意消息， 无论是请求消息还是响应消息， 都触发 MG复位休止定时器， 该休止定时器自动重新开始计时。
每当休止定时器超时， MG 即从根（Root ) 终端发送附带休止超时 ( Inactivity Timeout )事件的通知（Notify ) 消息上报 MGC, 同时复位该 休止定时器。 由于这不是 MGC预先请求 MG检测的事件， 因此该事件的 事件标识（EventID )为 0。
如果来自主控 MGC的消息中包含下发给 MG上 Root终端的休止定时 器（ Inactivity Timer ) 包的休止超时 （ Inactivity Timeout )事件， 并设置了 该事件的最大休止时间 （ Maximum Inactivity Time )参数， MG将在 Root 终端上记录 Inactivity Timeout事件及其事件标识， 同时设置上述休止定时 器超时的时长为 Maximum Inactivity Time参数值。后续每当该休止定时器 超时， MG从 Root终端发送附带 Inactivity Timeout事件的 Notify消息上报 MGC时，该事件的事件标识将为上述 MGC请求检测的事件标识而不再为 0。
MG发往 MGC的附带 Inactivity Timeout事件的 Notify消息类似一种 心跳触发， 将促使 MGC返回响应作为一种心跳反射， 此响应与其它来自 MGC的任何消息一样都可作为 MGC状态正常的标志， 并触发 MG复位 休止定时器。 然而该 Notify消息发出之后， 在休止定时器再次超时之前， 如果 MG—直都没有能够得到来自 MGC的任何消息， 包括对该 Notify消 息的响应， 那么 MG可以认为 MGC故障而启动异常处理流程， 例如向备 份的 MGC发起注册。
为了避免由于类似网络 "闪断" 这种瞬时情况而误判， 在 MG上另外 部署一个初始为 0的休止计数器 （Inactivity Counter ) (休止计数器的原理 与前述的休止定时器相同）， 对上述休止定时器超时的次数做统计。 当休 止定时器超时时该休止计数器的计数增加 1; 每当 MG得到来自 MGC的 任何消息 , 包括对附带 Inactivity Timeout事件的 Notify消息的响应， 都将 该休止计数器复位为 0。 一旦该休止计数器的当前值， 也即上述休止定时 器连续超时的次数， 超过了某个预设的阈值， 那么就可以确定 MGC的状 态出现了异常， MG将启动异常处理流程。
参阅图 2所示， MG对 MGC的监测如下：
1、 MG接收到 MGC返回的注册成功消息后启动休止定时器和休止计 数器， 休止定时器的超时时长设置为缺省值 A， 休止计数器的初始值设置 为 0。
2、 MG接收到 MGC发送来的任何请求或应答消息复位休止定时器和 休止计数器。
3、休止定时器超时向 MGC发送包含休止超时事件的通知消息， 事件 标识为 0, 同时休止计数器加 1。
4、 MG收到 MGC的应答消息后复位休止定时器和休止计数器。
5、 MG收到 MGC下发的包含休止定时器包、休止超时事件和最大休 止时间参数值 B的请求消息后，将休止定时器的超时时长设置为该最大休 止时间 B, 并复位休止定时器和休止计数器， 同时记录下该休止超时事件 的事件标识 X。
6、 MG向 MGC返回应答消息。
7、 MG接收到 MGC发送来的任何请求或应答消息复位休止定时器和 休止计数器。
8、休止定时器超时向 MGC发送包含休止超时事件的通知消息， 事件 标识为 X, 同时休止计数器加 1。
9、 MG接收到 MGC发送来的任何请求或应答消息复位休止定时器和 休止计数器。
10、休止定时器超时 MG向 MGC发送包含休止超时事件的通知消息， 事件标识为 X, 同时休止计数器加 1。
11、休止定时器超时 MG向 MGC发送包含休止超时事件的通知消息， 事件标识为 X, 同时休止计数器加 1 , 此时计数值为 2。
12、 休止计数器当前值达到预设的阔值 n, 表示休止定时器已连续 n 次超时， 而 MG此前连续向 MGC发送的通知消息均未从 MGC收到任何 消息， 因此 MG确认 MGC故障， 启动异常处理流程， 例如发起业务改变。
实施例二
在 MG自主部署一个初始为 0的消息接收标志和一个预置缺省值的普 通超时定时器来检测 MGC消息的静默时间。 当 MG向 MGC注册成功， 即该 MGC成为主控 MGC后， MG根据返回的注册成功消息主动启动休 止定时器开始定时， 并开始对 MGC状态进行监测。
每当 MG得到来自 MGC的消息就将该标志设置为 1 , 一旦该定时器 超时而该标志仍然为 0, MG就上报 Inactivity Timeout事件给 MGC, 否则 MG将该标志复位为 0, 并重新启动该定时器。
如果来自主控 MGC的消息中包含下发给 MG上 Root终端的休止定时 器（ Inactivity Timer ) 包的休止超时（ Inactivity Timeout )事件， 并设置了 该事件的最大休止时间 （ Maximum Inactivity Time )参数， MG将在 Root 终端上记录 Inactivity Timeout事件及其事件标识， 同时设置该定时器的超 时时长为 Maximum Inactivity Time参数值的二分之一。
为了避免由于类似网络 "闪断" 这种瞬时情况而误判， 在 MG上另外 部署一个初始为 0的休止计数器（ Inactivity Counter ) (休止计数器的原理 与实施例一中的相同）， 对上述普通定时器超时而上述消息接收标志仍显 示未收到消息连续出现的次数进行统计， 一旦该休止计数器的当前值超过 了某个预设的阈值， 那么就可以确定 MGC的状态出现了异常， MG将启 动异常处理流程。 其它操作与实施例一类似。

Claims

权 利 要 求
1、 一种媒体网关监测媒体网关控制器状态的实现方法， 其特征在于， 包括：
A、 当所述媒体网关向媒体网关控制器注册后， 根据返回的注册成功 消息监测所述媒体网关控制器；
B、 才艮据所述媒体网关控制器消息的静默时间确定所述媒体网关控制 器的状态。
2、 如权利要求 1 所述的方法， 其特征在于， 在所述媒体网关上设置 休止定时器监测所述媒体网关控制器消息的静默时间。
3、 如权利要求 1 所述的方法， 其特征在于， 在所述媒体网关上设置 普通定时器和消息接收标志监测所述媒体网关控制器消息的静默时间。
4、 如权利要求 1、 2或 3所述的方法， 其特征在于， 在静默时间超时 时向媒体网关控制器发送触发媒体网关控制器返回状态正常的通知消息。
5、 如权利要求 4所述的方法， 其特征在于， 设置用于判断所述静默 时间是否超过规定值的超时时长。
6、 如权利要求 5所述的方法， 其特征在于， 当所述媒体网关从媒体 网关控制器接收到包含最大休止时间的消息时， 将根据该最大休止时间重 新设置休止定时器或普通定时器的超时时长。
7、 如权利要求 6所述的方法， 其特征在于， 将休止定时器的超时时 长设置为该最大休止时间， 或者将普通定时器的超时时长设置为该最大休 止时间的二分之一。
8、 如权利要求 6所述的方法， 其特征在于， 如果媒体网关上设置休 止定时器监测媒体网关控制器， 当该休止定时器连续超时的次数达到预定 的阈值时， 媒体网关启动异常处理流程。
9、 如权利要求 8所述的方法， 其特征在于， 采用休止计数器对所述 休止定时器的连续超时次数进行计数， 并在媒体网关接收到媒体网关控制 器的任何消息时复位该休止计数器。
10、 如权利要求 6所述的方法， 其特征在于， 如果媒体网关上设置普 通定时器和消息接收标志监测媒体网关控制器， 当该普通定时器超时而消 息接收标志仍显示未收到消息连续出现的次数达到预定的阐值时 , 媒体网 关启动异常处理流程。
11、 如权利要求 10所述的方法， 其特征在于， 采用休止计数器对所 述普通定时器超时而消息接收标志仍显示未收到消息的连续出现次数进 行计数， 并在媒体网关接收到媒体网关控制器的任何消息时复位该休止计 数器。
PCT/CN2005/001442 2004-09-10 2005-09-09 A method for monitoring the state of the media gateway controller by the media gateway WO2006026929A1 (en)

Priority Applications (7)

Application Number Priority Date Filing Date Title
AT05783996T ATE429751T1 (de) 2004-09-10 2005-09-09 Verfahren zur überwachung des zustands der media- gateway-steuerung durch das media-gateway
DE200560014099 DE602005014099D1 (de) 2004-09-10 2005-09-09 Verfahren zur überwachung des zustands der media-gateway-steuerung durch das media-gateway
CA 2550291 CA2550291C (en) 2004-09-10 2005-09-09 Method for monitoring a media gateway controller status by a media gateway
BRPI0506457A BRPI0506457B1 (pt) 2004-09-10 2005-09-09 método para implementar o monitoramento do status do controlador de porta de mídia de uma porta de mídia
US10/584,972 US7843853B2 (en) 2004-09-10 2005-09-09 Method for implementing media gateway controller status monitoring of media gateway
EP05783996A EP1744488B1 (en) 2004-09-10 2005-09-09 A method for monitoring the state of the media gateway controller by the media gateway
JP2006545893A JP4348560B2 (ja) 2004-09-10 2005-09-09 メディアゲートウェイによるメディアゲートウェイコントローラーの状態のモニタリング方法

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200410078854.8 2004-09-10
CNB2004100788548A CN1283070C (zh) 2004-09-10 2004-09-10 媒体网关监测媒体网关控制器状态的实现方法

Publications (1)

Publication Number Publication Date
WO2006026929A1 true WO2006026929A1 (en) 2006-03-16

Family

ID=36036079

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2005/001442 WO2006026929A1 (en) 2004-09-10 2005-09-09 A method for monitoring the state of the media gateway controller by the media gateway

Country Status (13)

Country Link
US (1) US7843853B2 (zh)
EP (1) EP1744488B1 (zh)
JP (1) JP4348560B2 (zh)
KR (1) KR100771797B1 (zh)
CN (1) CN1283070C (zh)
AT (1) ATE429751T1 (zh)
AU (1) AU2005282142B2 (zh)
BR (1) BRPI0506457B1 (zh)
CA (1) CA2550291C (zh)
DE (1) DE602005014099D1 (zh)
HK (1) HK1087271A1 (zh)
RU (1) RU2357367C2 (zh)
WO (1) WO2006026929A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101170772B (zh) * 2007-11-19 2010-12-08 中兴通讯股份有限公司 终端媒体模式的设置方法

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100342693C (zh) * 2005-04-15 2007-10-10 华为技术有限公司 一种媒体网关监测并上报事件的方法
CN1917506B (zh) * 2005-08-16 2010-06-30 上海贝尔阿尔卡特股份有限公司 媒体网关、媒体网关控制器及相关注册控制处理方法
CN100442727C (zh) * 2006-07-04 2008-12-10 华为技术有限公司 媒体控制设备与媒体处理设备之间的检测方法
CN101345703A (zh) * 2007-08-06 2009-01-14 华为技术有限公司 一种承载资源预留方法、系统和装置
CN101141684B (zh) * 2007-08-14 2010-12-29 中兴通讯股份有限公司 一种实现音频业务静音处理控制的系统及方法
KR101369103B1 (ko) * 2007-11-12 2014-03-04 알까뗄 루슨트 접속 해제 처리 방법 및 접속 해제 처리 장치
US8433824B2 (en) * 2008-03-25 2013-04-30 International Business Machines Corporation Thread timeout coordination method and system
JP5218085B2 (ja) * 2009-01-19 2013-06-26 日本電気株式会社 ゲートウェイ制御装置、ゲートウェイ制御方法及びプログラム
JP5218086B2 (ja) * 2009-01-19 2013-06-26 日本電気株式会社 ゲートウェイ制御装置、ゲートウェイ制御方法及びプログラム
CN101808352B (zh) * 2009-02-13 2013-02-06 上海贝尔股份有限公司 在下一代网络中实现单个中继网关双归属切换的方法
US8634349B1 (en) * 2010-01-11 2014-01-21 Google Inc. Merging for wireless access points
CN101883157A (zh) * 2010-06-28 2010-11-10 华为技术有限公司 一种实现网关接入的方法和相应装置
US8937880B2 (en) 2012-05-09 2015-01-20 Telefonaktiebolaget L M Ericsson (Publ) System and method for managing state transitions in a wireless communications network
WO2015080512A1 (ko) * 2013-11-28 2015-06-04 주식회사 케이티 컨트롤러와 네트워크 장치 간 이벤트를 처리하는 방법
IN2015CH01318A (zh) * 2015-03-18 2015-04-10 Wipro Ltd
US10750383B2 (en) * 2017-07-07 2020-08-18 Arris Enterprises Llc Method of providing management and control of hotspots with reduced messaging
US10425316B2 (en) * 2017-09-29 2019-09-24 Nokia Of America Corporation Heart beat monitoring for broadband access devices and enterprise devices
CN109257251B (zh) * 2018-09-06 2020-11-06 京信通信系统（中国）有限公司 多板卡多模块心跳检测方法、装置、系统及计算机存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100401387B1 (ko) * 2001-12-14 2003-10-17 엘지전자 주식회사 소프트스위치와 미디어 게이트웨이 간의 초기화 방법
CN1452347A (zh) * 2002-04-20 2003-10-29 深圳市中兴通讯股份有限公司 一种检测媒体网关控制器与媒体网关间链路状态的方法

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3097302B2 (ja) 1992-05-07 2000-10-10 松下電器産業株式会社 無線端末制御装置
JPH07221775A (ja) 1994-02-07 1995-08-18 Mitsubishi Electric Corp ローカルエリアネットワークにおける回線管理方式
JPH07264233A (ja) 1994-03-24 1995-10-13 Hitachi Ltd ルート高速切替方法及びルータ装置
US6680952B1 (en) * 1999-06-01 2004-01-20 Cisco Technology, Inc. Method and apparatus for backhaul of telecommunications signaling protocols over packet-switching networks
US6687251B1 (en) 1999-12-08 2004-02-03 Nortel Networks Limited Method and apparatus for distributed MTP Level 2 architecture
US7120139B1 (en) * 1999-12-30 2006-10-10 At&T Corp. Broadband cable telephony network architecture IP ITN network architecture reference model
WO2001065821A2 (en) 2000-02-29 2001-09-07 3Com Corporation Proximity-based registration on a data network telephony system
JP2002135330A (ja) 2000-08-16 2002-05-10 Nippon Telegr & Teleph Corp <Ntt> ノード間制御方式
JP2002084363A (ja) 2000-09-06 2002-03-22 Nec Corp ゲートウェイシステム及びそれに用いる回線制御方法
JP2002290551A (ja) 2001-03-28 2002-10-04 Nec Corp ゲートウェイシステム及びそれに用いる障害処理方法
US8363647B2 (en) * 2001-04-03 2013-01-29 Voxpath Networks, Inc. System and method for configuring an IP telephony device
JP4015428B2 (ja) * 2001-05-16 2007-11-28 株式会社日立コミュニケーションテクノロジー インアクティビティタイマを備えた無線基地局／無線基地局制御装置、無線端末及び状態制御方法
US7193985B1 (en) 2001-06-14 2007-03-20 Utstarcom, Inc. System and method for managing foreign agent selections in a mobile internet protocol network
US9332037B2 (en) * 2002-03-27 2016-05-03 Alcatel Lucent Method and apparatus for redundant signaling links
US7206286B2 (en) * 2002-07-24 2007-04-17 Lucent Technologies Inc. Dynamic DCH allocation methodology for packet data services in a wireless communications system
KR100448867B1 (ko) 2002-11-25 2004-09-18 엘지전자 주식회사 액세스 게이트웨이 시스템에서의 알람 처리 방법
US7630488B2 (en) * 2003-05-16 2009-12-08 Alcatel-Lucent Usa Inc. DTMF tone generation in a media gateway
CN100373898C (zh) * 2003-08-06 2008-03-05 中兴通讯股份有限公司 基于megaco协议的信令代理实现方法
CN1317873C (zh) * 2003-08-19 2007-05-23 中兴通讯股份有限公司 基于媒体网关控制协议的信令代理实现方法
US7218723B2 (en) * 2003-10-14 2007-05-15 Tellabs Petaluma, Inc. Next-generation network that reduces the effect of a service failure

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100401387B1 (ko) * 2001-12-14 2003-10-17 엘지전자 주식회사 소프트스위치와 미디어 게이트웨이 간의 초기화 방법
CN1452347A (zh) * 2002-04-20 2003-10-29 深圳市中兴通讯股份有限公司 一种检测媒体网关控制器与媒体网关间链路状态的方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Gateway control protocol: Inactivity timer package; H.248.14 (03/02)", TU-T STANDARD IN FORCE (I), INTERNATIONAL TELECOMMUNICATION UNION, GENEVA, CH, XP017401377

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101170772B (zh) * 2007-11-19 2010-12-08 中兴通讯股份有限公司 终端媒体模式的设置方法

Also Published As

Publication number Publication date
EP1744488B1 (en) 2009-04-22
CA2550291C (en) 2010-04-13
RU2357367C2 (ru) 2009-05-27
CN1747408A (zh) 2006-03-15
CA2550291A1 (en) 2006-03-16
JP2007517439A (ja) 2007-06-28
AU2005282142B2 (en) 2008-11-27
RU2006123097A (ru) 2008-10-27
JP4348560B2 (ja) 2009-10-21
BRPI0506457A8 (pt) 2018-04-03
AU2005282142A1 (en) 2006-03-16
DE602005014099D1 (de) 2009-06-04
CN1283070C (zh) 2006-11-01
US20090180390A1 (en) 2009-07-16
BRPI0506457A (pt) 2007-02-21
EP1744488A4 (en) 2007-05-16
EP1744488A1 (en) 2007-01-17
KR20070007772A (ko) 2007-01-16
KR100771797B1 (ko) 2007-10-30
US7843853B2 (en) 2010-11-30
HK1087271A1 (en) 2006-10-06
BRPI0506457B1 (pt) 2018-09-25
ATE429751T1 (de) 2009-05-15

Similar Documents

Publication Publication Date Title
WO2006026929A1 (en) A method for monitoring the state of the media gateway controller by the media gateway
US8614953B2 (en) Method for monitoring and reporting events by media gateways
Andreasen et al. Media gateway control protocol (MGCP) version 1.0
WO2007006206A1 (fr) Procédé de détection et de libération de ressource rtp anormale de passerelle multimédia
WO2009129712A1 (zh) 上报会话状态的方法、媒体网关和系统
EP2222026B1 (en) A method and apparatus for processing a disconnection-connection between a media gateway and a media gateway controller
CN100442717C (zh) 用于对预置事件进行控制的方法及其装置
EP2214343B1 (en) Method and device in response to termination service state change indication
WO2008083606A1 (fr) Procédé et dispositif de commande de communication d&#39;estampille temporelle d&#39;événement
CN108833441A (zh) 临时终结点的释放方法和系统

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KM KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NG NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM 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): GM KE LS MW MZ NA 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 IS IT LT LU LV MC NL PL 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
WWE Wipo information: entry into national phase

Ref document number: 2005783996

Country of ref document: EP

Ref document number: 2550291

Country of ref document: CA

Ref document number: 2005282142

Country of ref document: AU

WWE Wipo information: entry into national phase

Ref document number: 2006545893

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 1020067013125

Country of ref document: KR

WWE Wipo information: entry into national phase

Ref document number: 10584972

Country of ref document: US

ENP Entry into the national phase

Ref document number: 2005282142

Country of ref document: AU

Date of ref document: 20050909

Kind code of ref document: A

WWP Wipo information: published in national office

Ref document number: 2005282142

Country of ref document: AU

WWP Wipo information: published in national office

Ref document number: 1020067013125

Country of ref document: KR

WWP Wipo information: published in national office

Ref document number: 2005783996

Country of ref document: EP

ENP Entry into the national phase

Ref document number: PI0506457

Country of ref document: BR

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2006123097

Country of ref document: RU