WO2007112689A1 - Procédé et dispositif de commande d'un événement prédéfini - Google Patents

Procédé et dispositif de commande d'un événement prédéfini Download PDF

Info

Publication number
WO2007112689A1
WO2007112689A1 PCT/CN2007/001053 CN2007001053W WO2007112689A1 WO 2007112689 A1 WO2007112689 A1 WO 2007112689A1 CN 2007001053 W CN2007001053 W CN 2007001053W WO 2007112689 A1 WO2007112689 A1 WO 2007112689A1
Authority
WO
WIPO (PCT)
Prior art keywords
preset event
event
media gateway
setting
preset
Prior art date
Application number
PCT/CN2007/001053
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
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to EP07720627A priority Critical patent/EP2003816A4/en
Publication of WO2007112689A1 publication Critical patent/WO2007112689A1/zh
Priority to US12/242,095 priority patent/US20090028136A1/en

Links

Classifications

    • 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
    • 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/1066—Session management
    • H04L65/1076—Screening of IP real time communications, e.g. spam over Internet telephony [SPIT]

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and apparatus for controlling preset events. Background of the invention
  • Figure 1 shows a related art packet network MG (Media Gateway) and MGC (Media)
  • MGC16 and MG14 are two key components in a packet network.
  • the MGC 16 is responsible for the call control function
  • the MG 14 is responsible for the service bearer function, thereby separating the call control plane and the service bearer plane, thereby fully sharing network resources, simplifying equipment upgrades and service expansion, and greatly reducing development and maintenance costs.
  • (Media) Gateway Control Protocol is the main protocol for communication between MG and MGC.
  • H. 284/MeGaCo Gateway Control Protocol
  • MGCP Media Gateway Control Protocol
  • the MGCP protocol version 1 was developed by the Internet Engineering Task Force (IETF) in October 1999 and revised in January 2003.
  • the H. 284/MeGaCo protocol version 1 is composed of the IETF and the ITU (International Telecommunications Union, The International Telecommunication Union (ITU) was jointly developed in November 2000 and revised in June 2003.
  • the H.284 protocol version 2 was developed by the ITU in May 2002 and revised in March 2004.
  • the H.284 protocol version 3 is Released in September 2005.
  • terminals are further divided into physical terminals and temporary (Ephemeral) terminals, the former representing some semi-permanent physical entities, such as TDM. (Time Division Multiplex) channel, etc., which represents common resources released after temporary application, such as RTP (Real-time Transport Protocol), etc.
  • TDM Time Division Multiplex
  • RTP Real-time Transport Protocol
  • Another root terminal represents MG.
  • the combination between terminals is abstracted as a context (Context) o
  • the context can contain multiple terminals, so the relationship between the terminals is described by Topology.
  • a special context called a null (Null) context is included.
  • the connection of the call is actually the operation of the terminal and the context. This operation is done by a Command request and a Reply between the MGC and the MG.
  • Command types include Add, Modify, Subtract s Move, Audit Value, Audit Capability, Notify, and Service Change. , also known as a descriptor (Descriptor), is classified as a property, a signal, Event (Event), Statistics (Statistic). The parameters with business relevance are logically aggregated into packets (Packag e ).
  • the event is defined by the MGC and sent to the MG to indicate the need to monitor.
  • the status change along with the request ID (Request ID), and the parameters that may be needed.
  • This kind of issued event is also called a Requested event.
  • the MG detects some of these changes, it reports the corresponding event to the MGC with the same request identifier as above, as well as the parameters that may be needed. This reported event is also called an Observed event.
  • Request events and observation events are associated by the same request identifier. The parameters accompanying the request and observation events are independent of each other. Events that are subsequently issued for a terminal will completely replace the previously issued events.
  • the event may not be suitable for the MGC to be sent to the MG.
  • an MGC manages a large number of MGs at the same time. If an event is sent one by one, it may have a negative impact on the performance of the MGC; or an MG. Depending on the MGC issuing an event to start the business operation, but the MGC may suddenly fail and it is too late to issue the event.
  • the H.284 protocol introduces an event preset mechanism in version 3, that is, the event can be set on the MG before the MGC sends the MG to the terminal as the setting object. Automatically initiate monitoring of a certain state.
  • the event preset is based on the consensus between the MGC and the MG, including the same request identifier and any possible parameters, so that the MGC will not respond incorrectly to the event escalation received on the MG.
  • the event that is set on the MG before the MGC is sent to the MG is called a preset event.
  • the present invention is directed to a method and apparatus for controlling preset events, thereby overcoming the prior art in which preset events are set by whom and by whom, and preset events are preset. Dealing with these problems such as lack of solutions.
  • a method for controlling a preset event comprising:
  • a preset event control device includes:
  • a determining module configured to determine whether the preset event needs to be continuously monitored on the setting object
  • a control module configured to: when the determining module determines that the preset event needs to be continuously monitored on the setting object And keeping the preset event active on the setting object.
  • the undoing module is configured to: when the determining module determines that the preset event does not need to be continuously monitored on the setting object, does not keep the preset event in an active state on the terminal.
  • the present invention achieves the following technical effects: the present invention provides a complete and effective solution for the control of preset events, such that the media gateway controller, the media gateway, and the setter of preset events, such as O&M (Operation Maintenance) System, operation and maintenance systems) can be better matched to meet the different needs of the business.
  • O&M Opera Maintenance
  • O&M Opera Maintenance
  • FIG. 1 is a schematic diagram showing a MG and MGC networking in a packet network of the related art
  • FIG. 2 shows a flow chart of a preset event control method in accordance with the principles of the present invention
  • FIG. 3 shows a block diagram of a preset event control apparatus in accordance with the principles of the present invention
  • Figure 4 shows a flow chart in accordance with a first embodiment of the present invention
  • Figure 5 shows a flow chart in accordance with a second embodiment of the present invention
  • FIG. 6 shows a flow chart in accordance with a third embodiment of the present invention. Mode for Carrying Out the Invention The present invention will be described in detail below with reference to the accompanying drawings.
  • Event presets are usually performed by 0&M, such as console operations or network management operations.
  • 0&M sets the same preset event on the MGC and the MG according to the service requirements, including the same request identifier and any possible parameters, to ensure that the preset events reported by the MG are not responded by the MGC error.
  • the preset event can be set for the MG as a whole or for a resource in the MG.
  • Preset events can be set at any time during the lifecycle of their set object (ie set object).
  • Preset event in it The set object activation is activated at the same time. For example, when the MG as a whole starts to operate normally, the preset event set on the root terminal is started to be monitored; when a terminal on the MG is created, the event set on the terminal starts to be monitored.
  • Preset events can be divided into two categories based on whether they are continuously monitored, one that needs to be continuously monitored, and the other that is the opposite.
  • FIG. 2 shows a flow chart of a preset event control method in accordance with the principles of the present invention.
  • a preset event control method in accordance with the principles of the present invention includes the following steps:
  • step S10 the setting device sets a preset event to the terminal on the media gateway controller and the media gateway; in step S20, it is determined whether the preset event needs to be continuously monitored on the terminal;
  • step S30 if it is determined in step S20 that it is necessary, it is necessary to keep the preset event active on the terminal, and then return to step S20 until it is determined that it is no longer needed;
  • step S40 if it is determined in step S20 that it is not necessary, it is not necessary to keep the preset event activated on the terminal.
  • FIG. 3 shows a block diagram of a preset event control device in accordance with the principles of the present invention.
  • a preset event control apparatus 100 in accordance with the principles of the present invention includes:
  • the preset event setting module 102 is configured to enable the setting device to set a preset event to the terminal on the media gateway controller and the media gateway;
  • the determining module 104 is configured to determine that the preset event is required to be continuously monitored on the terminal;
  • the control module 106 is configured to: if the determining module determines that it is necessary, keep the preset event activated on the terminal, and then return to the execution determining module until it is determined that it is no longer needed;
  • the revocation module 108 is configured to stop the preset event from being activated on the terminal if the judging module judges that it is not needed.
  • Figure 4 shows a flow chart in accordance with a first embodiment of the present invention.
  • the first embodiment is controlled by the MGC, that is, the O&M only sets a preset event to a terminal on the MGC and the MG, and the MGC determines whether the event needs to be continuously monitored on the terminal according to the service requirement, and if yes, the MGC will The event is included in an event descriptor that is subsequently sent to the terminal on the MG to keep it activated on the terminal until the MGC determines that the event no longer needs to be continuously monitored on the terminal according to the service requirement. Otherwise, the MGC does not need to include the event in the event descriptor that is subsequently sent to the terminal on the MG. The MG monitors the preset event from being activated until the event descriptor sent by the MGC does not contain the event.
  • the embodiment begins,
  • step S102 0&M sets a preset event to a terminal on the MGC and the MG.
  • step S104 the MGC determines whether the event needs to be continuously monitored on the terminal according to the service requirement, and if yes, proceeds to step S106, otherwise proceeds to step S108;
  • step S106 the MGC includes the event in an event descriptor that is subsequently sent to the terminal on the MG to keep it activated on the terminal until the MGC determines that the event is no longer needed on the terminal according to the service requirement. Continued to be monitored, and then proceeds to step S110;
  • step S108 the MGC does not need to include the event in the event descriptor that is subsequently sent to the terminal on the MG, and then proceeds to step S110;
  • step S110 the MG monitors the preset event from being activated until the event descriptor sent by the MGC does not include the event;
  • Figure 5 shows a flow chart in accordance with a second embodiment of the present invention.
  • the second embodiment is indicated by the O&M and is controlled by the MGC. That is, the O&M sets a preset event to a terminal on the MGC and the MG, and indicates whether the MGC needs to be continuously monitored on the terminal. If necessary, the MGC includes the event in an event descriptor that is subsequently sent to the terminal on the MG to keep it activated on the terminal until the OM indicates that the MGC event no longer needs to be continuously monitored on the terminal. , or cancel the event on the terminal for monitoring. If not required, the 0&M needs to further indicate whether the event of the MGC needs to be reported at least once on the terminal.
  • the MGC needs to include the event in the event descriptor that is subsequently sent to the terminal on the MG before the event is reported by the terminal. , if not needed otherwise.
  • the MG monitors the preset event from being activated until the event descriptor sent by the MGC does not include the event.
  • the embodiment begins,
  • step S202 0&M sets a preset event to a terminal on the MGC and the MG.
  • step S204 0&M indicates whether the event of the MGC needs to be continuously monitored on the terminal, if necessary, proceeding to step S206, otherwise proceeding to step S208;
  • step S206 the MGC includes the event in the event descriptor that is subsequently sent to the terminal on the MG to keep it activated on the terminal until the O&M indicates that the event is no longer needed to be continuously on the terminal. Monitoring, or canceling the event monitoring on the terminal, and then proceeding to step S212;
  • step S208 0&M further instructs the MGC whether the event needs to be reported at least once on the terminal.
  • step S210 if yes, the MGC needs to include the event in the event descriptor that is subsequently sent to the terminal on the MG before the event is reported by the terminal, if not (S214), and then proceeds to step S212; as well as
  • step S212 the MG monitors the preset event from being activated until the event descriptor sent by the MGC does not include the event;
  • Figure 6 shows a flow chart in accordance with a third embodiment of the present invention.
  • the MGC will treat the event from the terminal as the MG has been legal until 0 cancels the Set the preset event on the terminal.
  • G monitors the preset event from its activation until 0 cancels the preset event on the terminal.
  • the method according to the first aspect includes the following steps:
  • This embodiment begins,
  • step S302 0&M sets a preset event to a terminal on the MGC and the MG.
  • step S304 the MGC treats the event reported by the MG from the terminal as legal until the setting of the preset event on the terminal is cancelled by the O&M;
  • step S306 the MG monitors the preset event from being activated until the 0&M cancels setting the preset event on the terminal.
  • the object to which the preset event is set may be either the MG as a whole or a resource in the MG.
  • the preset event can be set at any time during the life cycle of the object it is set to; and, the preset event can be activated while its set object is active.
  • the above scenario is illustrated by the example of the Inactivity Timeout event used by the MG to monitor the MGC status and the Off Hook event used by the MG to monitor the user operation.
  • the O&M pre-sets the event to the root terminal on the MGC and the MG.
  • the MG can start monitoring the event.
  • the MGC determines that the event needs to be continuously performed on the root terminal according to the service requirement. Monitoring, so the event is included in the event descriptor of the Root terminal that is subsequently sent to the MG.
  • the event is preset to the root terminal on the MGC and the MG, and the 0 leg indicates that the MGC needs to be continuously monitored on the root terminal according to the service requirement. Therefore, after the MG successfully registers with the MGC, the MG can operate normally. The event is monitored and the MGC includes the event in the event descriptor of the Root terminal that is subsequently sent to the MG.
  • the O&M pre-sets the event to the root terminal on the MGC and the MG. After the MG successfully registers with the MGC, the MG starts monitoring the event, and the MGC treats the event reported by the MG from the root terminal as legal.
  • the 0&M presets the event to a physical terminal on the MGC and the MG, and the MG starts monitoring the event after the terminal is activated (into the service state). If the MGC needs to send an event descriptor to the terminal before the terminal detects that the user is off-hook and reports, the MGC determines that the event needs to be monitored on the terminal according to the service requirement, and the event descriptor is sent to the terminal. The event is included in the event; if the terminal has detected that the user is off-hook and reports, the MGC determines that the event does not need to continue to be monitored on the terminal according to the service requirement, and is not included in the event descriptor sent to the terminal subsequently. The event, until the service demand needs to monitor the event again on the terminal, for example, the terminal monitors that the user hangs up and reports.
  • the 0&M pre-resets the event to the physical terminal on the MGC and the MG, and the OMC instructs the MGC to report the event at least once on the terminal according to the service requirement, so the MG is activated at the terminal (entering the service state).
  • the MGC needs to include the event in the event descriptor sent to the terminal before the terminal detects that the user picks up the phone and reports it.
  • MGC The event is not required to be included in the event descriptor that is subsequently sent to the terminal until the service requirement needs to be monitored on the terminal again. For example, the terminal monitors that the user hangs up and reports.
  • the O&M pre-sets the event to a physical terminal on the MGC and the MG, and the MG starts monitoring the event after the terminal is activated (into the service state), and the MGC reports the event reported by the MG from the terminal. It is considered legal until 0 or 0 cancels the preset event on the terminal.
  • the present invention provides a complete and effective solution for the control of preset events, so that MGC, MG and 0&M can better match the preset events to meet the different needs of the service.

Landscapes

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

Description

用于对预置事件进行控制的方法及其装置
技术领域
本发明涉及通讯领域， 尤其涉及一种用于对预置事件进行控制的方法及其装置。 发明背景
图 1示出了相关技术的分组网络中 MG (Media Gateway, 媒体网关）和 MGC (Media
Gateway Controller, 媒体网关控制器） 组网的示意图。 如图 1所示， MGC16和 MG14 是分组网络中的两个关键构件。 MGC 16负责呼叫控制功能， MG 14负责业务承载功能， 藉此实现呼叫控制平面和业务承载平面的分离， 从而充分共享网络资源， 简化设备升级 和业务扩展， 大大降低开发和维护成本。
(媒体） 网关控制协议是 MG和 MGC之间通信的主要协议， 目前应用较为广泛的有
H. 284/MeGaCo (Gateway Control Protocol, 网关控制协议）和 MGCP (Media Gateway Control Protocol, 媒体网关控制协议）两种协议。 其中， MGCP协议版本 1 由 IETF (Internet Engineering Task Force, 互联网工程任务组）于 1999年 10月制订并于 2003 年 1 月修订， H. 284/MeGaCo 协议版本 1 由 IETF 和 ITU ( International Telecommunications Union, 国际电信联盟）于 2000年 11月共同制订并于 2003年 6 月修订， H. 284协议版本 2由 ITU于 2002年 5月制订并于 2004年 3月修订， H. 284协 议版本 3由 ITU于 2005年 9月发布。
以 H. 284协议为例， MG上的各种资源被抽象表示为终端（Terminations 终端又分 为物理 （Physical ) 终端和临时 （Ephemeral )终端， 前者代表一些具有半永久存在性 的物理实体， 例如 TDM (Time Division Multiplex, 时分复用）通道等， 后者代表一些 临时申请用后释放的公共资源， 例如 RTP (Real-time Transport Protocol , 实时传输 协议）流等。 另以根（Root)终端代表 MG整体。 终端之间的组合被抽象表示为上下文 (Context) o 上下文可以包含多个终端， 因而以拓扑 （Topology)来描述终端间的相互 关系。 对于还未与其它终端发生关联的终端， 由一个称为空（Null )上下文的特殊上下 文来包含。
基于协议的这种抽象模型， 呼叫的接续实际上就是对终端和上下文的操作。 这种操 作通过 MGC和 MG之间的命令（Command)请求（Request )和响应（Reply)来完成。 命 令类型包括添加（Add)、修改（Modify),删减（Subtract s移动（Move)、审计值（Audit Value ) 审计能力 (Audit Capability)^通报 (Notify),服务改变 (Service Change )。 命令参数， 也称为描述符（Descriptor), 被分类为属性（Property)、 信号 （Signal )、 事件（Event )、统计（Statistic )。具有业务相关性的参数逻辑上聚合成为包（Package)。 为了监测状态变化， 例如用户摘机、挂机、拨号、 拍叉， 或者网络故障、质量告警、 定时器超时等，在 H. 284协议中， 定义了事件由 MGC下发给 MG, 以指示需要监测的状态 变化， 并附带有请求标识 （Request ID), 以及可能需要的参数。 这种下发的事件也称 请求（Requested)事件。 一旦 MG监测到这些状态中某些发生变化， 就将相应的事件上 报给 MGC， 并附带有上述相同的请求标识， 以及可能需要的参数。 这种上报的事件也称 观测（Observed)事件。 请求事件和观测事件通过相同的请求标识来关联。 请求事件和 观测事件附带的参数相互独立。针对某个终端后续下发的事件将完全替代先前下发的事 件。
在一些特定情况下， 事件可能并不适宜必须由 MGC下发给 MG， 例如一个 MGC同时管 理着大量 MG， 若逐一去下发某个事件将可能给 MGC的性能带来负面影响； 或者一个 MG 依赖 MGC下发某个事件才能开始业务运作，但 MGC却可能突然故障而来不及下发该事件。
因此， 为适应上述特定情况， H. 284协议在版本 3中新引入了事件预置机制， 即事 件可以在 MGC下发给 MG之前就在 MG上对某个作为设置对象的终端进行设置， 以自动启 动对某种状态的监测。 事件预置基于 MGC和 MG之间达成的共识， 包括相同的请求标识 和任何可能的参数， 这样 MGC就不会对收到预置在 MG上的事件上报做出错误的响应。 在 MGC下发给 MG之前就被在 MG上对某个作为设置对象的终端设置的事件称为预置事件。
然而， 预置事件由谁来设置又由谁来取消、 预置事件在被预置之后如何处理等这些 问题的解决方案在现有技术中并没有确定， 换而言之， 目前在例如 H. 284等网关控制协 议中还缺乏对预置事件进行控制的完整有效的机制。 发明内容
本发明旨在提供一种用于对预置事件进行控制的方法及其装置，从而克服了现有技 术中预置事件由谁来设置又由谁来取消、预置事件在被预置之后如何处理等缺乏解决方 案的这些问题。
一种预置事件的控制方法， 包括：
分别在媒体网关控制器和媒体网关上对设置对象设置预置事件；
判断所述预置事件是否需要在所述设置对象上持续被监控； 如果是， 则保持所述预 置事件在所述设置对象上处于激活状态； 否则， 不再保持所述预置事件在所述设置对象 上处于激活状态。 一种预置事件的控制装置， 包括：
判断模块， 用于判断所述预置事件是否需要在所述设置对象上持续被监控； 控制模块， 用于当所述判断模块判断所述预置事件需要在所述设置对象上持续被监 控时， 保持所述预置事件在所述设置对象上处于激活状态。；
撤销模块， 用于当所述判断模块判断所述预置事件不需要在所述设置对象上持续被 监控时， 不保持所述预置事件在所述终端上处于激活状态。
通过上述技术方案，本发明实现了如下技术效果：本发明为预置事件的控制提供了 完整有效的解决方案， 使得媒体网关控制器、 媒体网关和预置事件的设置者， 例如 0&M (Operation Maintenance System, 运行和维护系统）在预置事件上可以更好地配合 以满足业务的不同需求。
本发明的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得 显而易见， 或者通过实施本发明而了解。本发明的目的和其他优点可通过在所写的说明 书、 权利要求书、 以及附图中所特别指出的结构来实现和获得。 附图简要说明
图 1示出了相关技术的分组网络中 MG和 MGC组网的示意图；
图 2示出了根据本发明的原理的预置事件控制方法的流程图；
图 3示出了根据本发明的原理的预置事件控制装置的方框图；
图 4示出了根据本发明的第一实施例的流程图；
图 5示出了根据本发明的第二实施例的流程图；
图 6示出了根据本发明的第三实施例的流程图。 实施本发明的方式 下面将参考附图详细说明本发明。
通常由 0&M来进行事件的预置，例如控制台操作或网管操作等。 0&M根据业务需求 同时在 MGC和 MG上设置相同的预置事件， 包括相同的请求标识和任何可能的参数， 以 确保 MG上报的预置事件不会被 MGC错误响应。
预置事件既可以针对 MG整体进行设置，也可以针对 MG中的某个资源进行设置。预 置事件可以在其设置的对象（即设置对象） '的生命周期的任何时刻设置。预置事件在其 设置的对象激活同时被激活。例如 MG整体开始正常运作同时， 设置在 Root终端上的预 置事件开始被监测； MG上的某个终端被创建同时， 设置在该终端上的事件开始被监测。
预置事件根据其是否霈要持续被监测可以分为两类，一类是需要持续被监测的，另 一类则反之。
根据以上的分析来设计本发明。 下面将参照图 2和图 3来说明本发明的原理。 图 2示出了根据本发明的原理的预置事件控制方法的流程图。
如图 2所示， 根据本发明的原理的预置事件控制方法包括以下步骤：
在步骤 S10中， 由设置装置在媒体网关控制器和媒体网关上对终端设置预置事件； 在步骤 S20中， 判断预置事件是否需要在终端上持续被监控；
在步骤 S30中，如果步骤 S20判断为需要，则将需要保持预置事件一直在终端上激 活， 然后回到步骤 S20， 直到判断为不再需要为止； 以及
在步骤 S40中，如果步骤 S20判断为不需要，则无需保持所述预置事件在所述终端 上激活。
图 3示出了根据本发明的原理的预置事件控制装置的方框图。
如图 3所示， 根据本发明的原理的预置事件控制装置 100包括：
预置事件设置模块 102，用于使设置装置在媒体网关控制器和媒体网关上对终端设 置预置事件；
判断模块 104， 用于判断预置事件是^需要在终端上持续被监控；
控制模块 106， 用于如果判断模块判断为需要， 则保持预置事件在终端上激活， 然 后回到执行判断模块， 直到判断为不再需要为止； 以及
撤销模块 108， 用于如果判断模块判断为不需要， 则不再保持预置事件在终端上激 活。
图 4示出了根据本发明的第一实施例的流程图。
第一实施例、 由 MGC控制， 即 0&M只是在 MGC和 MG上对某个终端设置某个预置事 件， 由 MGC根据业务需求决定该事件是否需要在该终端上持续被监控， 若是则 MGC将该 事件包含在后续下发给 MG上该终端的事件描述符中， 以保持其一直在该终端上激活， 直到 MGC根据业务需求判断该事件不再需要在该终端上持续被监控为止。 否则， MGC无 需将该事件包含在后续下发给 MG上该终端的事件描述符中。 MG从该预置事件被激活开 始对其进行监测， 直到 MGC下发的事件描述符不包含该事件为止。
具体而言， 如图 4所示， 根据第一实施例包括以下步骤： 该实施例开始，
在步骤 S102中， 0&M在 MGC和 MG上对某个终端设置某个预置事件；
在步骤 S104中，由 MGC根据业务需求决定该事件是否需要在该终端上持续被监控， 若是则进行到步骤 S106, 否则进行到步骤 S108;
在步骤 S106中， MGC将该事件包含在后续下发给 MG上该终端的事件描述符中， 以 保持其一直在该终端上激活，直到 MGC根据业务需求判断该事件不再需要在该终端上持 续被监控为止， 然后进行到步骤 S110;
在步骤 S108中， MGC无需将该事件包含在后续下发给 MG上该终端的事件描述符中， 然后进行到步骤 S110; 以及
在步骤 S110中， MG从该预置事件被激活开始对其进行监测， 直到 MGC下发的事件 描述符不包含该事件为止；
然后， 结束该实施例。
图 5示出了根据本发明的第二实施例的流程图。
第二实施例、 由 0&M指示并由 MGC执行控制， 即 0&M在 MGC和 MG上对某个终端设 置某个预置事件同时，指示 MGC该事件是否需要在该终端上持续被监测。如果需要， MGC 就将该事件包含在后续下发给 MG上该终端的事件描述符中， 以保持其一直在该终端上 激活， 直到 0&M指示 MGC该事件不再需要在该终端上持续被监测， 或者取消该事件该终 端上的监测为止。 如果不需要， 0&M需要进一步指示 MGC该事件在该终端上是否需要至 少上报一次， 若是则 MGC在该终端上报该事件之前需要将该事件包含在后续下发给 MG 上该终端的事件描述符中， 若否则不需要。 MG从该预置事件被激活开始对其进行监测， 直到 MGC下发的事件描述符不包含该事件为止。
具体而言， 如图 5所示， 根据第二实施例包括以下步骤：
该实施例开始，
在步骤 S202中， 0&M在 MGC和 MG上对某个终端设置某个预置事件；
在步骤 S204中， 0&M指示 MGC该事件是否需要在该终端上持续被监测， 如果需要， 则进行到步骤 S206, 否则进行到步骤 S208;
在步骤 S206中， MGC将该事件包含在后续下发给 MG上该终端的事件描述符中， 以 保持其一直在该终端上激活，直到 0&M指示 iGC该事件不再需要在该终端上持续被监测， 或者取消该事件该终端上的监测为止， 然后进行到步骤 S212;
在步骤 S208中， 0&M进一步指示 MGC该事件在该终端上是否需要至少上报一次； 在步骤 S210中， 若是， 则 MGC在该终端上报该事件之前需要将该事件包含在后续 下发给 MG上该终端的事件描述符中， 若否则不需要（S214), 然后进行到步骤 S212; 以 及
在步骤 S212中， MG从该预置事件被激活开始对其进行监测， 直到 MGC下发的事件 描述符不包含该事件为止；
然后， 结束该实施例。
图 6示出了根据本发明的第三实施例的流程图。
第三实施例， 由 0&M控制， 即从 0 在 MGC和 MG上对某个终端设置了某个预置事 件起， MGC将视 MG从该终端上报该事件一直是合法的，直到 0 取消在该终端上设置该 预置事件为止。 G从该预置事件被激活开始对其进行监测，直到 0 取消在该终端上设 置该预置事件为止。
具体而言， 如图 6所示， 根据第一方案的方法包括以下步骤：
本实施例开始，
在步骤 S302中， 0&M在 MGC和 MG上对某个终端设置某个预置事件；
在步骤 S304中， MGC将 MG从该终端上报的该事件一直视为合法， 直到 0&M取消在 该终端上设置该预置事件为止； '
在步骤 S306中， MG从该预置事件被激活开始对其进行监测， 直到 0&M取消在该终 端上设置该预置事件为止。
然后， 结束本实施例。
值得特别注意的是，在根据本发明的上述三个实施例中，对于本领域的技术人员而 言， 显然， 预置事件被设置的对象既可以是 MG整体也可以是 MG中的某个资源； 预置事 件可以在其被设置的对象的生命周期的任何时刻设置； 以及， 预置事件可以在其被设置 的对象激活同时被激活。
下面将详细说明本发明的实施例。
以 MG用于监测 MGC状态的休止超时（Inactivity Timeout )事件和 MG用于监测用 户操作的摘机 （Off Hook)事件为例说明上述方案如下：
对于需要持续在 MG (Root终端）上进行监测的休止超时事件而言，
根据实施例一、 0&M在 MGC和 MG上对 Root终端预置该事件， MG在向 MGC注册成功 可以正常运作之后就幵始监测该事件， MGC根据业务需求判定该事件需要在 Root终端上 持续被监测， 因此在后续下发给 MG的 Root终端的事件描述符中均包含该事件。 根据实施例二、 0碰在 MGC和 MG上对 Root终端预置该事件， 同时 0腿根据业务需 求指示 MGC该事件需要在 Root终端上持续被监测， 因此 MG在向 MGC注册成功可以正常 运作之后就开始监测该事件，并且 MGC在后续下发给 MG的 Root终端的事件描述符中均 包含该事件。
根据实施例三、 0&M在 MGC和 MG上对 Root终端预置该事件， MG在向 MGC注册成功 可以正常运作之后就开始监测该事件， MGC将 MG从 Root终端上报的该事件都视为合法。
对于无需持续在某个物理终端上进行监测的摘机事件而言，
根据实施例一、 0&M在 MGC和 MG上对某个物理终端预置该事件， MG在该终端激活 (进入服务状态）后就开始监测该事件。若在该终端监测到用户摘机并上报之前 MGC需 要给该终端下发事件描述符， 则 MGC根据业务需求判定该事件还需在该终端上被监测， 就在下发给该终端的事件描述符中包含该事件； 若该终端已监测到用户摘机并上报， 则 MGC根据业务需求判定该事件无需继续在该终端上被监测， 则在后续下发给该终端的事 件描述符中不再包含该事件， 直到业务需求重新需要在该终端上监测该事件为止， 例如 该终端监测到用户挂机并上报。
根据实施例二、 0&M在 MGC和 MG上对'某个物理终端预置该事件， 同时 0&M根据业 务需求指示 MGC该事件在该终端上至少需要上报一次， 因此 MG在该终端激活（进入服 务状态）后就开始监测该事件， 而 MGC在该终端监测到用户摘机并上报之前， 需要在下 发给该终端的事件描述符中包含该事件， 一旦该终端监测到用户摘机并上报之后， MGC 在后续下发给该终端的事件描述符中就无需再包含该事件，直到业务需求重新需要在该 终端上监测该事件为止， 例如该终端监测到用户挂机并上报。
根据实施例三、 0&M在 MGC和 MG上对某个物理终端预置该事件， MG在该终端激活 (进入服务状态） 后就开始监测该事件， 而 MGC将 MG从该终端上报的该事件都视为合 法， 直到 0&M取消在该终端上设置该预置事件为止。
从以上的描述中， 可以看出， 本发明实现了如下技术效果：
本发明为预置事件的控制提供了完整有效的解决方案，使得 MGC、 MG和 0&M在预置 事件上可以更好地配合以满足业务的不同需求。
以上所述， 仅为本发明较佳的具体实施方式， 但本发明的保护范围并不局限于此， 任何熟悉本技术领域的技术人员在本发明揭露的技术范围内， 可轻易想到的变化或替 换， 都应涵盖在本发明的保护范围之内。 因此， 本发明的保护范围应该以权利要求的保 护范围为准。

Claims

权利要求
1、 一种预置事件的控制方法， 其特征在于， 包括- 分别在媒体网关控制器和媒体网关上对设置对象设置预置事件；
判断所述预置事件是否需要在所述设置对象上持续被监控； 如果是， 则保持所述予 置事件在所述设置对象上处于激活状态； 否则， 不再保持所述预置事件在所述设置对 上处于激活状态。
2、根据权利要求 1所述的预置事件控制方法，其特征在于， 所述分别在媒体网关 制器和媒体网关上对设置对象设置预置事件具体包括：分别在所述媒体网关控制器和 述媒体网关上对所述设置对象设置相同的预置事件及其参数。
3、根据权利要求 1所述的预置事件控制方法， 其特征在于， 所述设置对象包括： β 述媒体网关整体或者所述媒体网关中的资源。
4、根据权利要求 3所述的预置事件控制方法，其特征在于， 所述分别在媒体网关 制器和媒体网关上对设置对象设置预置事件具体包括：
当所述设置对象为所述媒体网关整体时， 所述预置事件被设置在所述媒体网关的†l 终端上; 当所述设置对象为所述媒体网关的资源时， 所述预置事件被设置在所述媒体 关的物理终端或临时终端上。
5、根据权利要求 1所述的预置事件控制方法，其特征在于， 所述分别在媒体网关 制器和媒体网关上对设置对象设置预置事件具体包括- 在所述设置对象的生命周期中的任何时刻设置所述预置事件。
6、根据权利要求 1所述的预置事件控制方法， 其特征在于， 所述分别在媒体网关 制器和媒体网关上对设置对象设置预置事件具体包括：
运行和维护系统分别在媒体网关控制器和媒体网关上对设置对象设置预置事件。
7、根据权利要求 1、 2、 3、 4、 5或 6所述的预置事件控制方法， 其特征在于， 所 i 判断所述预置事件是否需要在所述设置对象上持续被监控具体包括- 所述媒体网关控制器判断所述预置事件'是否需要在所述设置对象上持续被监控； 者， 所述预置事件的设置装置判断所述预置事件是否需要在所述设置对象上持续被 控， 并将判断结果指示给所述媒体网关控制器。
8、 根据权利要求 7所述的预置事件控制方法， 其特征在于， 所述方法具体包括： 当所述判断结果为是时， 通过所述媒体网关控制器将所述预置事件包含于后续下 给设置对象的事件描述符中， 来保持所述预置事件在所述设置对象上处于激活状态； 当所述判断结果为否时， 通过所述媒体俩关控制器不将所述预置事件包含于后续下 发给所述设置对象的事件描述符中或者所述预置事件的设置装置在所述设置对象上取 消所述预置事件， 来不保持所述预置事件在所述设置对象上处于激活状态。
9、 根据权利要求 1、 2、 3、 4、 5或 6所述的预置事件控制方法， 其特征在于， 所述 方法还包括- 所述媒体网关从所述预置事件被激活开始对所述预置事件进行监测， 直到所述预置 事件的设置装置取消在所述设置对象上设置所述预置事件为止；
所述媒体网关控制器对所述媒体网关从所述设置对象上报的所述预置事件一直视为 合法， 直到所述预置事件的设置装置取消在所述设置对象上设置所述预置事件为止。
10.根据权利要求 1、 2、 3、 4、 5或 6所述的预置事件控制方法， 其特征在于， 所述 方法还包括：
当所述预置事件的设置装置或媒体网关控制器判断所述预置事件在所述设置对象上 至少需要上报一次时， 在所述设置对象上报所述预置事件一次之前， 保持所述预置事件 在所述设置对象上处于激活状态。
11、 一种预置事件的控制装置， 其特征在于， 包括- 判断模块， 用于判断所述预置事件是否需要在所述设置对象上持续被监控； 控制模块， 用于当所述判断模块判断所述预置事件需要在所述设置对象上持续被监 控时， 保持所述预置事件在所述设置对象上处于激活状态。；
撤销模块， 用于当所述判断模块判断所述预置事件不需要在所述设置对象上持续被 监控时， 不保持所述预置事件在所述终端上处于激活状态。
12、 根据权利要求 11所述的预置事件的控制装置， 其特征在于， 所述装置还包括- 预置事件设置模块， 用于使预置事件的设置装置通过该模块分别在所述媒体网关控 制器和所述媒体网关上对所述设置对象设置预置事件。
PCT/CN2007/001053 2006-04-03 2007-03-30 Procédé et dispositif de commande d'un événement prédéfini WO2007112689A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP07720627A EP2003816A4 (en) 2006-04-03 2007-03-30 METHOD AND DEVICE FOR CONTROLLING A PRESET EVENT
US12/242,095 US20090028136A1 (en) 2006-04-03 2008-09-30 Method And Apparatus For Controlling Preset Events

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNB2006100665890A CN100442717C (zh) 2006-04-03 2006-04-03 用于对预置事件进行控制的方法及其装置
CN200610066589.0 2006-04-03

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/242,095 Continuation US20090028136A1 (en) 2006-04-03 2008-09-30 Method And Apparatus For Controlling Preset Events

Publications (1)

Publication Number Publication Date
WO2007112689A1 true WO2007112689A1 (fr) 2007-10-11

Family

ID=38166219

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/001053 WO2007112689A1 (fr) 2006-04-03 2007-03-30 Procédé et dispositif de commande d'un événement prédéfini

Country Status (4)

Country Link
US (1) US20090028136A1 (zh)
EP (1) EP2003816A4 (zh)
CN (1) CN100442717C (zh)
WO (1) WO2007112689A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8971336B2 (en) * 2008-04-30 2015-03-03 Telefonaktiebolaget L M Ericsson (Publ) Circuit allocation within a communication core network
US9691200B2 (en) 2009-11-03 2017-06-27 Honeywell International Inc. Energy saving security system

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20050029590A (ko) * 2003-09-23 2005-03-28 엘지전자 주식회사 인터넷을 이용하는 개방형시스템의 신호처리방법
US20050105495A1 (en) * 2001-09-06 2005-05-19 Mark Hollis Decomposed switching node and method of operating the same

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB0005426D0 (en) * 2000-03-08 2000-04-26 Ericsson Telefon Ab L M Signalling in a telecommunications network
FR2814624A1 (fr) * 2000-09-22 2002-03-29 Cit Alcatel Procede de controle d'une passerelle media
US7353269B2 (en) * 2000-12-21 2008-04-01 Fujitsu Limited Network monitoring system
US7305550B2 (en) * 2000-12-29 2007-12-04 Intel Corporation System and method for providing authentication and verification services in an enhanced media gateway
ATE375654T1 (de) * 2001-04-04 2007-10-15 Nokia Corp Trassierungsverfahren und -system
JP4346898B2 (ja) * 2002-12-09 2009-10-21 Ｎｅｃインフロンティア株式会社 クライアント・サーバ型分散システムにおける保守インタフェース利用者認証方法および装置
EP1388998A1 (de) * 2003-04-03 2004-02-11 Siemens Aktiengesellschaft Verfahren und Netzzugangsknoten zur Übertragung von modulierten Trägersignalen in paketorientierten Kommunikationsnetzen
US20050038992A1 (en) * 2003-05-22 2005-02-17 Pelaez Mariana Benitez Method for sending multiple ephemeral terminations in a single service change message
CN100463404C (zh) * 2003-06-25 2009-02-18 中兴通讯股份有限公司 利用媒体资源服务器实现电话会议业务的方法
CN1330132C (zh) * 2003-09-02 2007-08-01 华为技术有限公司 一种实时监听业务控制过程的实现方法
US7092493B2 (en) * 2003-10-01 2006-08-15 Santera Systems, Inc. Methods and systems for providing lawful intercept of a media stream in a media gateway

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050105495A1 (en) * 2001-09-06 2005-05-19 Mark Hollis Decomposed switching node and method of operating the same
KR20050029590A (ko) * 2003-09-23 2005-03-28 엘지전자 주식회사 인터넷을 이용하는 개방형시스템의 신호처리방법

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
See also references of EP2003816A4 *
WANG Z. AND SU S.: "Comparison between the Existing two Media Gateway Control Protocols for Next Generation Network", COMPUTER ENGINEERING AND APPLICATION, 31 January 2004 (2004-01-31), pages 20 - 23, XP008075198 *

Also Published As

Publication number Publication date
EP2003816A4 (en) 2009-08-19
EP2003816A1 (en) 2008-12-17
CN100442717C (zh) 2008-12-10
CN1983964A (zh) 2007-06-20
US20090028136A1 (en) 2009-01-29

Similar Documents

Publication Publication Date Title
CA2542088C (en) Method for monitoring and reporting events by media gateways
KR100771797B1 (ko) 미디어 게이트웨이에 의하여 미디어 게이트웨이 제어기의 상태를 모니터링 하는 방법
WO2006002597A1 (fr) Procede permettant l'acquisition periodique de la qos d'un flux de donnees multimedia
WO2007006206A1 (fr) Procédé de détection et de libération de ressource rtp anormale de passerelle multimédia
WO2007073679A1 (fr) Passerelle multimedia et procede pour presenter une valeur de parametre statistique de terminal
WO2007054011A1 (fr) Procede de commutation de l'etat de terminaison dans une passerelle media
WO2007112689A1 (fr) Procédé et dispositif de commande d'un événement prédéfini
WO2008083586A1 (fr) Procédé de communication de statistiques et passerelle multimédia
WO2007073666A1 (fr) Procede et dispositif utilisant un parametre de comptage pour regler une valeur
WO2009129712A1 (zh) 上报会话状态的方法、媒体网关和系统
KR101369103B1 (ko) 접속 해제 처리 방법 및 접속 해제 처리 장치
WO2008019610A1 (fr) Passerelle mutlimédia et procédé de rapport statistique
WO2008151559A1 (fr) Procédé, système et appareil pour sélectionner une passerelle de médias virtuels
EP2214343B1 (en) Method and device in response to termination service state change indication
WO2008083606A1 (fr) Procédé et dispositif de commande de communication d'estampille temporelle d'événement
KR101486100B1 (ko) 음성 및 데이터 통합 관리 시스템
Xiaojian et al. Design of media gateway controller in 3G softswitch

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: 07720627

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2007720627

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE