WO2015067094A1 - 基于h.248终端的通信链路异常保护方法 - Google Patents

基于h.248终端的通信链路异常保护方法 Download PDF

Info

Publication number
WO2015067094A1
WO2015067094A1 PCT/CN2014/086512 CN2014086512W WO2015067094A1 WO 2015067094 A1 WO2015067094 A1 WO 2015067094A1 CN 2014086512 W CN2014086512 W CN 2014086512W WO 2015067094 A1 WO2015067094 A1 WO 2015067094A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
mgc
registration
detection timer
communication link
Prior art date
Application number
PCT/CN2014/086512
Other languages
English (en)
French (fr)
Inventor
李裴
何昆鹏
张涛
孙阳
孙成芳
张兆亮
Original Assignee
烽火通信科技股份有限公司
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 烽火通信科技股份有限公司 filed Critical 烽火通信科技股份有限公司
Publication of WO2015067094A1 publication Critical patent/WO2015067094A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/08Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10Architectures or entities
    • H04L65/102Gateways
    • H04L65/1023Media gateways
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066Session management
    • H04L65/1073Registration or de-registration

Definitions

  • the present invention relates to the field of communications, and in particular, to a communication link exception protection method based on an H.248 terminal.
  • the H.248 Media Gateway Control Protocol is an interface protocol used between media gateway controllers and media gateway terminals. It is also one of the most active communication protocols in the industry.
  • the heartbeat is generally controlled only by the MGC between the Media Gateway Controller (MGC) and the terminal.
  • MGC Media Gateway Controller
  • the specific implementation is as follows.
  • the MGC uses the audit parameter value to command the AuditValue message. As a heartbeat message, it is sent periodically to the terminal. When the heartbeat message retransmission does not receive the response message of the terminal, it is judged that the terminal is faulty, that is, the link between the MGC and the terminal is interrupted. That is to say, the heartbeat detection mode of the H.248 type communication terminal is generally controlled.
  • the terminal device does not actively send a heartbeat to the MGC by default.
  • the MGC controls the heartbeat, and does not actively perform route detection to the original active MGC after the handover. .
  • the terminal does not enable the active heartbeat message, and the MGC sends the heartbeat message and must be subject to the terminal.
  • the MGC server cannot send a heartbeat message or send a heartbeat.
  • the message cannot reach the gateway terminal.
  • the H.248 communication terminal will remain offline on the MGC, affecting the user's use.
  • To detect link anomalies due to the complex networking environment, H.248 communication terminal equipment manufacturers are different, often require multiple manufacturers to cooperate, the inspection period is long, and it consumes a large number of people. Force and material. Therefore, relying on the current heartbeat method alone, it is impossible to ensure that the gateway terminal accurately and timely detects and restores the link interruption in the abnormal link condition.
  • the present invention provides an H.248 terminal-based communication link abnormality protection method capable of accurately detecting link anomalies in time and recovering link interruption.
  • a communication link abnormality protection method based on an H.248 terminal is configured to detect a communication link abnormality between a terminal and a Media Gateway Controller (MGC), and the protection method includes the following steps:
  • the cold start registration is initiated to cause the terminal to request registration from the primary MGC and the multiple standby MGCs in sequence until the registration is successful.
  • the present invention provides a timing detection to determine whether a link is interrupted, so that the communication terminal device can discover the survival state of the server in time, and adopt a pre-customized policy according to the state change of the server, and is not affected at the same time. Terminal type restrictions, easy to operate, timely and efficient.
  • 1 is a method for protecting an abnormality of a communication link based on an H.248 terminal provided by the present invention.
  • System diagram is a method for protecting an abnormality of a communication link based on an H.248 terminal provided by the present invention.
  • FIG. 2 is a flowchart of a method for protecting an abnormality of a communication link based on an H.248 terminal provided by the present invention.
  • FIG. 3 is a flow chart of setting the detection timer in FIG.
  • FIG. 4 is a flow chart of initiating a cold start registration in FIG.
  • FIG. 2 is a method for protecting an abnormality of a communication link based on an H.248 terminal according to the present invention, where the protection method is used to detect a terminal and a media gateway controller (Media Gateway Controller) in FIG.
  • the communication link between the MGCs is abnormal and measures are taken to protect the normal communication between the terminal and the MGC.
  • the protection method includes the following steps:
  • step S300 determining whether the detection timer expires and determining whether the detection timer is restarted according to the determination result, and whether the primary MGC sends a message to the terminal, and if yes, proceeding to step S400;
  • step S500 determining whether the terminal receives the message sent by the primary MGC within the time set by the detection timer, and determining whether to initiate the cold start registration according to the determination result; if not, proceeding to step S600;
  • S600 Start cold start registration to enable the terminal to request registration to the primary MGC and the multiple standby MGCs in sequence until the registration is successful.
  • the softswitch platform provides primary backup server information on the configuration list, and optionally provides a list of candidate MGCs, generally through an Integrated Terminal Management System (ITMS) platform before the terminal is opened. Issued to the terminal. It can be understood that the number of standby MGCs can be set according to actual needs.
  • ITMS Integrated Terminal Management System
  • step S200 the following steps are included in step S200:
  • S220 Set a detection switch and the detection timer according to the configuration data.
  • the detection timer determines whether to start according to whether the detection switch is turned on, and if so, starts a detection timer; if not, does not start a detection timer.
  • the configuration data of the detection switch and detection time is set according to the needs before the H.248 process starts. Generally, the detection switch is turned on. If the detection switch is enabled and the detection interval is changed after the process is started, the configuration data is reset and sent to the H.248 terminal to take effect. It does not need to be restarted. After the configuration data is reset, the detection timer restarts.
  • the length of time set in the detection timer is determined based on the configuration data.
  • the detection switch is turned on to determine whether the communication between the terminal and the MGC is activated. If the detection switch flag is set to "0", it means that the detection switch is turned off, the communication link detection is not enabled, and the detection timer is not started; if the detection switch flag is set If it is "1", it means that the detection switch is enabled, link detection is enabled, and the detection timer is started.
  • the interval time set by the detection timer indicates the interval from the start of the detection timer to the re-initiation of registration by the H.248 terminal.
  • step S210 and step S220 the configuration data is acquired by the terminal and the detection switch and the detection timer are set.
  • step S300 and step S400 if it is determined that the detection timer expires, the detection timer is restarted, and the primary MGC sends a heartbeat or other signaling message to the terminal.
  • step S500 if the terminal is not within the time interval set by the detection timer If any message sent by the primary MGC is received, the terminal is set to the unregistered state and the cold start ServiceChange registration is initiated.
  • the cold start registration process includes the following steps:
  • step S610 After the detection timer expires, the terminal registers with the primary MGC registration packet and determines whether the registration is successful according to whether the primary MGC sends a message. If yes, the process proceeds to step S650. If not, the registration fails, and the process proceeds to step S620.
  • S620 The terminal sequentially registers with each standby MGC.
  • step S630 determining whether the terminal initiates a registration silence period according to whether the terminal successfully registers with the standby MGC, if yes, proceeding to step S650, if not, starting the silent period, that is, proceeding to step S640;
  • S650 The terminal registers successfully and resets the detection timer.
  • step S610 the terminal sends a ServiceChange registration packet of 901 (Cold Boot) to the primary MGC to register, and the TerminationId in the ServiceChange packet is Root. If the terminal does not receive the primary MGC return registration within the time interval of detecting the timer. A successful Reply message determines that registration with the primary MGC failed. If the terminal is successfully registered, the terminal resets the detection timer, the detection timer restarts, and the time interval set by the detection timer is determined by the configuration data acquired in step S210.
  • a ServiceChange registration packet of 901 Cold Boot
  • the TerminationId in the ServiceChange packet is Root.
  • step S620 after the terminal detects that the link disconnection fails to register with the primary MGC, the terminal sends a ServiceChange registration packet of 901 to the standby MGC device to register, and the TerminationId in the ServiceChange packet is Root, and the follow-up registration time can be customized. No more than 60 seconds. Unable to receive MGC from the main use within 60 seconds of the detection interval Any message is initiated to register with the alternate MGC device.
  • the terminal generally switches from the primary MGC device to the standby MGC device with a switching period of less than 60 seconds, that is, the terminal fails to register with the primary MGC device, and the registration period to the standby MGC is less than 120 seconds.
  • step S630 after the terminal fails to register with the primary MGC device, the terminal switches to each standby MGC device to register. Once the registration to the standby MGC fails, the terminal will enable the registration silence period. It can be understood that, if the terminal is successfully registered, the terminal receives the message sent by the MGC, and resets the detection timer at this time. In the present embodiment, the duration of the silence period is less than 120 seconds.
  • step S640 the terminal again registers the ServiceChange registration packet of the 901 with the primary MGC after starting the silence period, that is, enters the next round of registration, and repeats steps S610 to S640 until the registration is successful, and then re-orders to the primary MGC. Registration with the standby MGC until registration is successful. If the terminal is successfully registered, the terminal resets the detection timer.
  • step S650 if the terminal successfully registers with the primary MGC or the standby MGC, the detection timer is reset every time the terminal receives the MGC message, and the reset timing is determined by the configuration data acquired in step S210.
  • the time interval set by the detection timer is greater than the time interval of the passive heartbeat of the terminal, that is, the time when the terminal returns the MGC message.
  • step S100 and step S200 can be mutually.
  • the H.248 terminal-based communication link abnormality protection method sends a registration message to the active/standby MGC actively when the link disconnection between the terminal and the MGC exceeds a preset detection interval. Automatically activate the signaling link, so that when the link is abnormally interrupted, it detects the abnormality in time, and uses the active sending registration of the terminal. When the link is abnormal, the communication can be resumed in time.
  • the setting of each message and the related operations of sending and receiving use the H.248 protocol itself, which is not limited by the terminal type, and does not need to increase the performance consumption of the device, and the operation is simple. Efficient and feasible.

Landscapes

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

Abstract

本发明提供一种基于H.248终端的通信链路异常保护方法,其用于检测终端与媒体网关控制器(Media Gateway Controller,MGC)之间的通信链路异常并进行恢复,所述方法包括以下步骤:设置主用MGC及一组备用MGC;设置并启动检测定时器;判断检测定时器是否超时并根据判断结果确定检测定时器是否重启及主用MGC是否向终端发送消息;判断终端在检测定时器设置的时间内是否收到主用MGC发送的消息并根据判断结果确定是否启动冷启动注册;启动冷启动注册以使终端依次向主用MGC及多个备用MGC请求注册直至注册成功。该方法通过定时检测来判断链路是否中断,以使通讯终端设备能及时发现MGC的存活状态,根据MGC的状态变化及时采取预先定制的策略,同时不受终端类型的限制,操作简单,及时高效。

Description

基于H.248终端的通信链路异常保护方法 技术领域
本发明涉及通信领域,尤其涉及一种基于H.248终端的通信链路异常保护方法。
背景技术
H.248媒体网关控制协议是一种应用于媒体网关控制器和媒体网关终端之间的接口协议,也是目前业界最为活跃的通信协议之一。目前,在使用H.248协议的软交换网络中,一般在媒体网关控制器(Media Gateway Controller,MGC)和终端之间只由MGC来控制心跳,具体实现如下,MGC采用审计参数值命令AuditValue消息作为心跳消息,周期性向终端发送。当心跳消息重传都没有收到终端的响应消息时,则判断终端故障,即MGC和终端的链路中断。也就是说,H.248类型通讯终端的心跳检测方式一般采用受控方式,终端设备默认情况下不主动向MGC发送心跳,由MGC来控制心跳,包括切换后不主动向原主用MGC做路由检测。
然而,在这种方式下,终端不开启主动心跳消息,而MGC发送心跳消息又必须受制于终端,当MGC发生故障或当网络出现故障时,导致MGC服务器端无法发送心跳消息,或发送的心跳消息无法到达网关终端,即使一段时间后MGC故障消除或网络故障消除,网络恢复,H.248通讯终端在MGC上也将一直处于离线状态,影响用户使用。若要查出链路异常问题,因组网环境复杂,使用H.248通讯终端设备厂家各异,往往需要多个厂家配合,检查周期长,且耗费大量人 力物力。因此仅依靠现在的这种心跳方法,无法保证链路异常情况下网关终端准确及时检测并恢复链路中断。
发明内容
有鉴于此,本发明提供一种能准确及时检测链路异常并恢复链路中断的基于H.248终端的通信链路异常保护方法。
一种基于H.248终端的通信链路异常保护方法,其用于检测终端与媒体网关控制器(Media Gateway Controller,MGC)之间的通信链路异常,所述保护方法包括以下步骤:
设置一个主用MGC及一组备用MGC;
设置并启动一个检测定时器;
判断所述检测定时器是否超时并根据判断结果确定所述检测定时器是否重启及所述主用MGC是否向终端发送消息;
判断终端在所述检测定时器设置的时间内是否收到主用MGC发送的消息并根据判断结果确定是否启动冷启动注册;
启动冷启动注册以使终端依次向主用MGC及多个备用MGC请求注册直至注册成功。
与现有技术相比,本发明提供的通过定时检测来判断链路是否中断,以使通讯终端设备能够及时发现服务器的存活状态,根据服务器的状态变化及时采取预先定制的策略,同时也不受终端类型的限制,操作简单,及时高效。
附图说明
图1是本发明提供的基于H.248终端的通信链路异常保护方法中 的系统示意图。
图2是本发明提供的基于H.248终端的通信链路异常保护方法的流程图。
图3是图2中设置检测定时器的流程图。
图4是图2中启动冷启动注册的流程图。
如下具体实施方式将结合上述附图进一步说明本发明。
具体实施方式
请结合图1及图2,图2为本发明提供的一种基于H.248终端的通信链路异常保护方法,所述保护方法用于检测图1中终端与媒体网关控制器(Media Gateway Controller,MGC)之间的通信链路异常并采取措施保护终端与MGC之间正常通信,所述保护方法包括以下步骤:
S100:设置一个主用MGC及一组备用MGC;
S200:设置并启动一个检测定时器;
S300:判断所述检测定时器是否超时并根据判断结果确定所述检测定时器是否重启及所述主用MGC是否向终端发送消息,若是,进入步骤S400;
S400:检测定时器重启且主用MGC向终端发送消息;
S500:判断终端在所述检测定时器设置的时间内是否收到主用MGC发送的消息并根据判断结果确定是否启动冷启动注册,若否,则进入步骤S600;
S600:启动冷启动注册以使终端依次向主用MGC及多个备用MGC请求注册直至注册成功。
在步骤S100中,软交换平台提供配置列表上的主备用服务器信息,并可选地提供一组备选MGC的列表,一般在终端开通前通过终端综合管理系统(Integrated Terminal Management System,ITMS)平台下发给终端。可以理解,备用MGC的数量可依实际需要设定。
请参阅图3,在步骤S200中包括以下步骤:
S210:获取配置数据;
S220:根据所述配置数据设置一个检测开关及所述检测定时器;
S230:所述检测定时器根据所述检测开关是否开启来确定是否启动,若是,则启动检测定时器;若否,则不启动检测定时器。
检测开关及检测时间的配置数据在H.248进程启动前根据需要自行设定,一般开启检测开关。在进程启动后若需更改检测开关使能和检测间隔时间,重新设置相关配置数据后下发到H.248终端即可生效,不需要重启,重新设置配置数据后检测定时器重新开始计时。
本实施方式中,检测定时器内设置的时间长短根据所述配置数据确定。检测开关的开启确定是否在终端与MGC的通信启动保护方法若检测开关标志位设置为“0”,表示关闭检测开关,不启用通信链路检测,检测定时器不启动;若检测开关标志位设置为“1”,表示开启检测开关,启用链路检测,检测定时器启动。检测定时器设置的间隔时间表示从检测定时器启动至H.248终端重新发起注册的间隔时间。
在步骤S210及步骤S220中,由终端获取配置数据并设置检测开关及检测定时器。
在步骤S300与步骤S400中:若判断所述检测定时器超时,则所述检测定时器重启,同时主用MGC向终端发送心跳或其他信令消息。
在步骤S500中,若终端在所述检测定时器设置的时间间隔内没 有收到主用MGC发送的任何消息,则将终端设置为未注册状态并启动冷启动ServiceChange注册。
请参阅图4,在步骤S600中启动,冷启动注册流程包括以下步骤:
S610:在检测定时器超时后终端向主用MGC注册包进行注册并根据主用MGC是否发送消息来确定是否注册成功,若是,则进入步骤S650,若否,则注册失败,进入步骤S620。
S620:终端依次向所述各备用MGC进行注册;
S630:根据终端是否向所述备用MGC注册成功来确定终端是否启动一个注册沉默周期,若是,则进入步骤S650,若否,则启动沉默周期,也即进入步骤S640;
S640:注册沉默周期过后终端重新依次向主用MGC及备用MGC进行注册直至注册成功,也即返回步骤S610。
S650:终端注册成功并重置检测定时器。
在步骤S610中,终端向主用MGC发送901(Cold Boot)的ServiceChange注册包进行注册,ServiceChange包中的TerminationId为Root,若终端在检测定时器的时间间隔内一直未收到主用MGC回送注册成功的Reply消息,判断向主用MGC注册失败。若终端注册成功,终端将重置检测定时器,检测定时器重新开始计时,检测定时器设置的时间间隔为步骤S210中获取的配置数据来确定。
在步骤S620中,当终端检测到链路断开向主用MGC注册失败后,向备用MGC设备发送901的ServiceChange注册包进行注册,ServiceChange包中TerminationId为Root其跟进注册时间可自定义,一般不超过60秒。在检测间隔时间60秒内无法收到来自主用MGC 的任何消息,则启动向备用MGC设备注册。本实施方式中,终端一般从主用MGC设备切换到备用MGC设备的切换周期小于60秒,即终端向主用MGC设备注册失败启动向备用MGC注册周期时长应小于120秒。
在步骤S630中,终端向主用MGC设备注册失败后转向各备用MGC设备注册,一旦向备用MGC进行注册失败,终端将启用注册沉默周期。可以理解,若终端注册成功,则终端收到MGC发送的消息,此时重新设置检测定时器。本实施方式中,沉默周期时长小于120秒。
在步骤S640中,终端在启动沉默周期后再一次向主用MGC发送901的ServiceChange注册包进行注册,也即进入下一轮注册,重复步骤S610至步骤S640直至注册成功,重新依次向主用MGC与备用MGC进行注册直至注册成功,若终端注册成功,则终端重置检测定时器。
在步骤S650中,若终端向主用MGC或备用MGC注册成功,检测定时器会在终端每次收到MGC的消息后重新设置,重新设置的定时时长为步骤S210中获取的配置数据来确定
本实施方式中,所述检测定时器设置的时间间隔大于终端被动心跳也即终端回复MGC消息的时间间隔。
可以理解,步骤S100与步骤S200的顺序可以互相。
本发明提供的基于H.248终端的通信链路异常保护方法在终端与MGC之间的链路断开超过预先设定的检测间隔时间时,H.248终端主动向主备MGC发送注册消息,自动激活信令链路,从而使链路出现异常中断时及时检测发现异常,同时利用终端的主动发送注册消 息使链路异常消失时能及时恢复通信,各项消息的设置及其发送、接收的相关操作步骤均利用H.248协议本身,不受终端类型的限制,无需增加设备的性能消耗,操作简单、高效可行。
可以理解的是,对于本领域的普通技术人员来说,可以根据本发明的技术构思做出其他各种相应的改变与变形,而所有这些改变与变形都应属于本发明权利要求的保护范围。

Claims (10)

  1. 一种基于H.248终端的通信链路异常保护方法,其用于检测终端与媒体网关控制器(Media Gateway Controller,MGC)之间的通信链路异常,所述保护方法包括以下步骤:
    设置一个主用MGC及一组备用MGC;
    设置并启动一个检测定时器;
    判断所述检测定时器是否超时并根据判断结果确定所述检测定时器是否重启及所述主用MGC是否向终端发送消息;
    判断终端在所述检测定时器设置的时间内是否收到主用MGC发送的消息并根据判断结果确定是否启动冷启动注册;
    启动冷启动注册以使终端依次向主用MGC及多个备用MGC请求注册直至注册成功。
  2. 如权利要求1所述的基于H.248终端的通信链路异常保护方法,其特征在于,在判断检测定时器是否超时步骤中:若所述检测定时器超时,则所述检测定时器重启同时主用MGC向终端发送消息。
  3. 如权利要求1所述的基于H.248终端的通信链路异常保护方法,其特征在于,在判断终端是否收到主用MGC发送的消息步骤中:若终端在所述检测定时器设置的时间内没有收到主用MGC发送的任何消息,则启动冷启动注册。
  4. 如权利要求1所述的基于H.248终端的通信链路异常保护方法,其特征在于,所述设置并启动所述检测定器的步骤中包括以下步骤:
    获取配置数据;
    根据所述配置数据设置一个检测开关及所述检测定时器;
    所述检测定时器根据所述检测开关是否开启来确定是否启动。
  5. 如权利要求1所述的基于H.248终端的通信链路异常保护方法,其特征在于,在启动冷启动注册步骤中包括以下步骤:
    若所述检测定时器超时,终端向主用MGC发送注册包进行注册并根据主用MGC是否发送消息来确定是否注册成功。
    根据终端向主用MGC注册是否成功来确定是否向所述各备用MGC进行注册;
    根据终端是否向所述备用MGC注册成功来确定终端是否启动一个注册沉默周期;
    根据终端是否启动所述注册沉默周期来确定终端是否重新依次向主用MGC及备用MGC进行注册。
  6. 如权利要求5所述的基于H.248终端的通信链路异常保护方法,其特征在于,在确定是否终端向主用MGC注册是否成功步骤中:若否,则终端向主用MGC注册失败。
  7. 如权利要求5所述的基于H.248终端的通信链路异常保护方法,其特征在于,在确定终端是否向所述各备用MGC注册步骤中:若终端向主用MGC注册失败,则终端依次向所述备用MGC进行注册。
  8. 如权利要求5所述的基于H.248终端的通信链路异常保护方法,其特征在于,在确定是否启动注册沉默周期步骤中,若终端向所述各备用MGC注册均失败,则终端启动所述沉默周期。
  9. 如权利要求5所述的基于H.248终端的通信链路异常保护方法,其特征在于,在确定是否重新向主备MGC进行注册步骤中,若终端启动所述沉默周期,则沉默周期过后终端依次依次向主用MGC 及备用MGC进行注册直至注册成功。
  10. 如权利要求1所述的基于H.248终端的通信链路异常保护方法,所述检测定时器内设置的时间间隔大于终端回复MGC消息的时间间隔。
PCT/CN2014/086512 2013-11-08 2014-09-15 基于h.248终端的通信链路异常保护方法 WO2015067094A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310553782.7A CN103546491B (zh) 2013-11-08 2013-11-08 基于h.248终端的通信链路异常保护方法
CN201310553782.7 2013-11-08

Publications (1)

Publication Number Publication Date
WO2015067094A1 true WO2015067094A1 (zh) 2015-05-14

Family

ID=49969538

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/086512 WO2015067094A1 (zh) 2013-11-08 2014-09-15 基于h.248终端的通信链路异常保护方法

Country Status (2)

Country Link
CN (1) CN103546491B (zh)
WO (1) WO2015067094A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103546491B (zh) * 2013-11-08 2017-01-11 烽火通信科技股份有限公司 基于h.248终端的通信链路异常保护方法
CN105024833A (zh) * 2015-07-03 2015-11-04 上海斐讯数据通信技术有限公司 基于语音协议的通信方法、系统、服务端及客户端

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1791031A (zh) * 2004-12-14 2006-06-21 华为技术有限公司 媒体网关监测媒体网关控制器状态的实现方法
CN1901483A (zh) * 2006-07-04 2007-01-24 华为技术有限公司 媒体控制设备与媒体处理设备之间的检测方法
CN103546491A (zh) * 2013-11-08 2014-01-29 烽火通信科技股份有限公司 基于h.248终端的通信链路异常保护方法

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100342693C (zh) * 2005-04-15 2007-10-10 华为技术有限公司 一种媒体网关监测并上报事件的方法
CN101039313A (zh) * 2006-03-17 2007-09-19 广东省电信有限公司研究院 一种网络实体分别独立控制协议心跳的实现方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1791031A (zh) * 2004-12-14 2006-06-21 华为技术有限公司 媒体网关监测媒体网关控制器状态的实现方法
CN1901483A (zh) * 2006-07-04 2007-01-24 华为技术有限公司 媒体控制设备与媒体处理设备之间的检测方法
CN103546491A (zh) * 2013-11-08 2014-01-29 烽火通信科技股份有限公司 基于h.248终端的通信链路异常保护方法

Also Published As

Publication number Publication date
CN103546491B (zh) 2017-01-11
CN103546491A (zh) 2014-01-29

Similar Documents

Publication Publication Date Title
US8212396B2 (en) Apparatus power restart method in response to network connection status
WO2018028132A1 (zh) Wifi异常自动重连装置、系统及方法
CN106603261B (zh) 热备份方法、第一主用设备、备用设备和通信系统
WO2016062008A1 (zh) 一种容灾方法及网元、服务器、存储介质
US10375178B2 (en) Information processing apparatus that transmits a packet a predetermined period of time after detecting link-up , method of controlling the same, and storage medium
CN110072244B (zh) 一种无线链路失败定时器的控制方法及设备
CN104683188A (zh) 快速检测家庭路由器ip通道连通的方法
WO2016101457A1 (zh) 一种终端及终端呼叫软切换的方法
CN104901834A (zh) 一种网络服务器自动切换的方法及系统
US10841344B1 (en) Methods, systems and apparatus for efficient handling of registrations of end devices
WO2015067094A1 (zh) 基于h.248终端的通信链路异常保护方法
CN114143911B (zh) 基于Android平台无线投屏断网自动重连的方法
WO2021259362A1 (zh) 一种数据传输异常恢复方法、装置及终端设备
JP2012510200A (ja) ソフトステート・シグナリングにおけるリフレッシュ要求
WO2017000438A1 (zh) 一种提高交换网链路中业务检测可靠性的方法及装置
JP2009003491A (ja) クラスタシステムにおけるサーバ切り替え方法
JP4883487B2 (ja) 中継装置、ネットワークシステム及び中継処理プログラム
CN106302077B (zh) 一种容灾倒回方法及设备
JP4102060B2 (ja) データ受信装置
JP6612475B2 (ja) ゲートウェイ装置
TWI394402B (zh) 網路偵測設備及其主動偵測網路品質的方法
WO2016082343A1 (zh) 故障检测方法及装置
JP4692419B2 (ja) ネットワーク装置及びそれに用いる冗長切替え方法並びにそのプログラム
CN104811426A (zh) 用户代理客户端发送注册请求的方法及用户代理客户端
WO2019187202A1 (ja) 制御装置、車両内通信システム、監視方法及びプログラム

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14860484

Country of ref document: EP

Kind code of ref document: A1