WO2011120282A1 - 一种应急切换的方法和系统 - Google Patents

一种应急切换的方法和系统 Download PDF

Info

Publication number
WO2011120282A1
WO2011120282A1 PCT/CN2010/076986 CN2010076986W WO2011120282A1 WO 2011120282 A1 WO2011120282 A1 WO 2011120282A1 CN 2010076986 W CN2010076986 W CN 2010076986W WO 2011120282 A1 WO2011120282 A1 WO 2011120282A1
Authority
WO
WIPO (PCT)
Prior art keywords
processing subsystem
service processing
address
service
network device
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2010/076986
Other languages
English (en)
French (fr)
Inventor
王国才
夏星欣
张浩军
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to EP10848741.4A priority Critical patent/EP2523480B1/en
Priority to US13/517,390 priority patent/US20130013955A1/en
Priority to JP2013501598A priority patent/JP5767309B2/ja
Priority to CA2789794A priority patent/CA2789794C/en
Publication of WO2011120282A1 publication Critical patent/WO2011120282A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06Management of faults, events, alarms or notifications
    • H04L41/0654Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0659Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities
    • H04L41/0661Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities by reconfiguring faulty entities
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06Management of faults, events, alarms or notifications
    • H04L41/0654Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0668Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/50Address allocation
    • H04L61/5076Update or notification mechanisms, e.g. DynDNS
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/04Arrangements for maintaining operational condition
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/50Address allocation
    • H04L61/5007Internet protocol [IP] addresses

Definitions

  • the present invention relates to communication technologies, and more particularly to a method and system for emergency handover in communication technology. Background technique
  • each service processing subsystem is relatively independent.
  • the MMS interworking gateway service processing subsystem is used, and each operator and any other operator have an interworking gateway service processing subsystem. Therefore, each operator has at least two sets of interworking gateway service processing subsystems.
  • each business processing subsystem plays an important role in the communication process, important equipment is usually backed up in order to avoid equipment failure in the business processing subsystem.
  • the commonly used backup technology is dual-system hot backup technology.
  • the dual-system hot backup technology has the following disadvantages: 1) When a rack of a server cannot work due to power failure, etc., both the original device and the backup device may be powered off due to power failure of the rack, and cannot be operated. Switching; 2) When the handover fails, the normal operation of the service cannot be guaranteed. If these two situations occur, you need to manually enable the standby device to carry the services carried by the device in question. This usually takes at least 1 to 2 hours, and the manual switching process is time-consuming and error-prone. Summary of the invention
  • a method for emergency handover includes: after a problem occurs in a device in the first service processing subsystem, the network device responsible for address mapping is modified to map to the first service.
  • the processing, by the second service processing subsystem, the service of the first service processing subsystem includes: the second service processing subsystem enabling a preset connection for communication with the first service processing subsystem. a first emergency account, and establishing a connection with the communication object of the first service processing subsystem by using the first emergency account.
  • the processing, by the second service processing subsystem, the service of the first service processing subsystem includes: the second service processing subsystem enabling a preset connection for connecting with a peripheral device of the first service processing subsystem. And a second emergency account, and establishing a connection with the peripheral device of the first service processing subsystem by using the second emergency account.
  • the method further includes: after the device fault in the first service processing subsystem is removed, the network device restores the mapping relationship; The second service processing subsystem disconnects from the communication object and the peripheral device of the first service processing subsystem, and the first service processing subsystem establishes a connection with the communication object and the peripheral device.
  • the network device responsible for the address mapping modifies the mapping relationship of the IP address mapped to the first service processing subsystem, specifically: the second service processing subsystem runs a preset network device script, and controls the responsible address mapping.
  • the network device modifies the mapping relationship mapped to the IP address of the first service processing subsystem or restores the mapping relationship of the IP address of the first service processing subsystem.
  • An emergency switching system including a first service processing subsystem, a second service processing subsystem, and a network device for performing address mapping, where the network device for performing address mapping is used in the first service processing After the device in the subsystem has a problem, modifying the mapping relationship mapped to the IP address of the first service processing subsystem, so that the IP address mapped to the first service processing subsystem is mapped to the second service processing subsystem; a second service processing subsystem, configured to process, according to the pre-stored processing, the service of the first service processing subsystem after the network device is mapped to the mapping relationship of the IP address of the first service processing subsystem The required data, processing the business of the first business processing subsystem.
  • the second service processing subsystem is specifically configured to: after the network device modifies a mapping relationship mapped to an IP address of the first service processing subsystem, enable a preset communication that connects the first service processing subsystem And a first emergency account of the object, and establishing a connection with the communication object of the first service processing subsystem by using the first emergency account.
  • the second service processing subsystem is specifically configured to: after the network device modifies a mapping relationship mapped to an IP address of the first service processing subsystem, enable a preset second emergency account of the connected peripheral device, and pass the The second emergency account establishes a connection with a peripheral device of the first service processing subsystem.
  • the network device is further configured to restore a mapping relationship of an IP address of the first service processing subsystem after the device in the first service processing subsystem is faulty; the second service processing subsystem further Disabling a connection with a communication object and a peripheral device of the first service processing subsystem after the device in the first service processing subsystem is faulty; the first service processing subsystem is configured to be used for troubleshooting After that, re-establish the connection with the communication object and peripheral devices.
  • the second service processing subsystem is further configured to: run a preset network device script in the second service processing subsystem, and control the network device responsible for address mapping to modify an IP mapped to the first service processing subsystem.
  • the mapping relationship of the addresses or the mapping relationship of the IP addresses of the first service processing subsystem is restored.
  • the embodiment of the present invention provides a method and system for emergency handover. By configuring a mapping IP address in a network device capable of address mapping in the previous stage, the corresponding devices in each service processing subsystem are mutually backup devices, and a service is used.
  • the IP address mapped to the network device in the previous-level network device is mapped to the corresponding device of another service processing subsystem, and the corresponding device of another service processing subsystem is used as a backup.
  • the device can handle the business of the device in question, so that the standby device can be started quickly and easily when there is a problem with the original device.
  • FIG. 1 is a schematic flowchart 1 of a method for emergency handover according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart 2 of a method for emergency handover according to an embodiment of the present invention
  • FIG. 3 is a schematic structural diagram of a system for emergency handover according to an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of a system for emergency switching of a multimedia message service in a connected network according to an embodiment of the present invention. detailed description
  • the embodiment of the present invention provides a method and system for emergency handover. Since a network element for performing address mapping exists in a general system, the network element may be a router, and more cases are used for security management and address. Mapped firewall.
  • the embodiment of the present invention can use the network element that can perform address mapping to modify the address mapping relationship after the device in a service processing subsystem has a problem, and forward the information to the service processing subsystem that is in question.
  • the data is forwarded to other service processing subsystems as the standby service processing subsystem, and the standby service processing subsystem temporarily processes the service of the problematic service processing subsystem, thereby quickly starting the standby device, and at the same time, since the two services are not limited Handling the distance between subsystems is therefore more flexible.
  • the method for emergency handover includes the following steps: Step 101: After the device in the first service processing subsystem has a problem, the network device responsible for the address mapping in the communication system modifies the mapping relationship mapped to the IP address of the first service processing subsystem, so as to be mapped to the first service processing subsystem. The IP address is mapped to the second service processing subsystem; Step 102, the second service processing subsystem processes the service of the first service processing subsystem, and the second service processing subsystem pre-stores the service for processing the first service processing subsystem The required data.
  • the IP address mapped to the first service processing subsystem is directly modified to be mapped to the second service processing subsystem, and the first service processor is stored and processed in the second service processing subsystem in advance.
  • the data required by the service of the system may cause the second service processing subsystem to serve as a backup service processing subsystem of the first service processing subsystem, and temporarily process the first service processor when the first service processing subsystem is unable to work normally.
  • the service of the system, the switching process is fast and convenient, and because the method of modifying the address mapping relationship is used, there is no requirement for the positional relationship between the first service processing subsystem and the second service processing subsystem, and the first service processing subsystem and The second service processing subsystem can be located in two cities that are far away from each other. Therefore, even if there is an accident such as a regional power outage, the emergency handover method provided by the embodiment of the present invention can be used for emergency processing.
  • the network device used for address mapping may be a router, a switch, or a firewall capable of performing security management and address mapping.
  • each service processing subsystem needs to establish a connection through an account and a communication object and a peripheral device, and implement communication and related service processing on the basis of the connection.
  • it is also necessary to set an emergency account on the second service processing subsystem how many communication objects and peripheral devices need to be established, and how many emergency accounts are set.
  • the network device modifies the mapping relationship mapped to the IP address of the first service processing subsystem
  • the second service processing subsystem starts to enable the preset first emergency account for connecting with the communication object of the first service processing subsystem.
  • the second service processing subsystem also needs to enable a preset second emergency account for connecting with the peripheral device of the first service processing subsystem, and The second emergency account establishes a connection with the peripheral device of the first service processing subsystem.
  • the embodiment of the present invention further configures a corresponding network device script on each service processing subsystem.
  • the service processing subsystem runs the corresponding network device.
  • the script can control the address mapping of the network device to modify the address mapping relationship, so that the network device forwards the data forwarded to the faulty service processing subsystem to the service processing subsystem; when the fault is eliminated, the corresponding script is run.
  • the network device that controls the address mapping restores the address mapping relationship, so that the network device forwards the data to the service processing subsystem that has been eliminated. It is very convenient to modify and restore the mapped address.
  • the method for emergency handover in the embodiment of the present invention further includes:
  • Step 103 After the device in the first service processing subsystem is faulty, the network device restores the mapping relationship.
  • Step 104 The second service processing subsystem disconnects the first emergency account and the second emergency account, and the first service processing subsystem establishes a connection with the communication object and the peripheral device.
  • the second service processing subsystem can be quickly and easily disconnected from the communication object and the peripheral device of the first service processing subsystem, and the second service processing subsystem can be switched back to the first service processing subsystem.
  • the embodiment of the present invention further provides an emergency handover system, as shown in FIG. 3, including: a first service processing subsystem 301, a second service processing subsystem 302, and a network device 303 for performing address mapping, where:
  • the network device 303 for performing address mapping is used to: in the first service processing subsystem 301 After the problem occurs in the device, the mapping to the IP address mapping of the first service processing subsystem 301 is modified, so that the IP address mapped to the first service processing subsystem 301 is mapped to the second service processing subsystem 302;
  • the second service processing subsystem 302 is configured to: after the network device modifies the mapping relationship mapped to the IP address of the first service processing subsystem 301, according to the pre-stored data required for processing the service of the first service processing subsystem 301, The business of the second business processing subsystem 302 is processed.
  • the network device 303 can be a router, a switch, or a firewall.
  • the second service processing subsystem 302 is specifically configured to: modify the mapping of the IP address mapped to the first service processing subsystem 301 at the network device. After the relationship, the preset first emergency account that is connected to the communication object of the first service processing subsystem 301 is enabled, and the connection is established with the communication object of the first service processing subsystem 301 through the first emergency account.
  • the second service processing subsystem 302 is specifically configured to: modify the IP address mapped to the first service processing subsystem 301 at the network device. After mapping the relationship, a preset second emergency account of the connected peripheral device is enabled, and a connection is established with the peripheral device of the first service processing subsystem 301 through the second emergency account.
  • the network device 303 is further configured to: after the device fault in the first service processing subsystem 301 is removed, restore the first service processing subsystem 301. Mapping of IP addresses;
  • the second service processing subsystem 302 is further configured to: when the device in the first service processing subsystem is faulty, disconnect the connection between the first emergency account and the second emergency account, that is, disconnect from the first service processing subsystem. a connection between a communication object and a peripheral device;
  • the first service processing subsystem 301 is configured to re-establish a connection with the communication object and the peripheral device after the fault is eliminated.
  • the following is a specific example:
  • the communication system used in the Unicom network is different from the mobile network and the telecommunication network. Therefore, in order to implement the inter-network service, the Unicom network needs to be set to the mobile interworking gateway system 401 and to the telecommunications.
  • the interworking gateway system 402 takes the MMS service as an example, and the mobile interworking gateway system 401 and the interworking gateway system 402 to the telecommunications will process their respective MMS messages without mutual message interaction.
  • the IP address of the mobile interworking gateway system 401 is IP2a, which establishes a connection through the firewall 405 and the interworking gateway system 403 in the mobile network, and the IP address set by the firewall 405 for the connection is IPla, when interworking in the mobile network
  • the gateway system 403 communicates with the mobile interworking gateway system 401
  • the interworking gateway system 403 in the mobile network transmits data to the address IPla
  • the firewall 405 maps the IPla address to IP2a, actually in the mobile network.
  • the interworking gateway system 403 sends the data to the IPla address, but due to the mapping of the firewall 405, the interworking gateway system 403 in the mobile network actually transmits the data to the mobile interworking gateway system 401 with the IP address IP2a.
  • the IP address of the interworking gateway system 402 to the telecommunications is IP2b, which establishes a connection through the firewall 405 and the interworking gateway system 404 in the telecommunications network.
  • the IP address set by the firewall 405 for the connection is IPlb, when the telecommunications network
  • the interworking gateway system 404 and the interworking gateway system 402 of the telecommunications communicate, although the interworking gateway system 404 in the telecommunications network transmits data to the IPlb address, the interworking gateway system 404 in the telecommunications network due to the mapping of the firewall 405 In fact, the data is sent to the interworking gateway system 402 to the telecommunications with IP address IP2b.
  • the emergency handover method provided by the embodiment of the present invention can perform a predetermined firewall script or menu operation on the mobile interworking gateway system 401 after an abnormality in the interworking gateway system 402 of the telecommunications is unavailable, and the mobile communication is performed.
  • the gateway system 401 takes over traffic to the interworking gateway system 402 of the telecommunications.
  • the control firewall 405 changes the mapping address of the IPlb from IP2b to IP2a.
  • Messages sent by the interworking gateway system 404 in the telecommunications network to the interworking gateway system 402 of the telecommunications are directly sent to the mobile interworking gateway system 401 according to the address mapping relationship, and such handover takes less time, minimizing service loss. .
  • the recovery can be performed at the mobile interworking gateway system 401.
  • the firewall 405 restores the mapped address of the IPlb to IP2b, and switches the service.
  • the interworking gateway system 402 to the telecommunications can also be used as the standby service processing subsystem.
  • emergency switching can be performed in the form of active and standby transmission links, and each link uses a unified bandwidth.
  • account data to the interworking gateway system 402 of the telecommunications such as the interworking gateway system 402 of the telecommunications and the interworking device and the communication object of the interworking gateway system 404 in the telecommunication network, are required.
  • the password is the emergency account.
  • the service data of the interworking gateway system 402 of the telecommunications such as the network number and the number segment, needs to be configured to ensure that the interworking gateway system 401 after the takeover can process the authentication normally.
  • the account data and service data to the mobile interworking gateway system 401 are also required to be provided to the interworking gateway system 402 of the telecommunications.
  • the account of the interworking gateway system 402 configured to the telecommunications interworking gateway system 401 and the interworking gateway system 404 in the telecommunications network is the first emergency account
  • the account number of the interworking gateway system 402 and the multimedia messaging center configured to the telecommunications is The second emergency account
  • the account of the interworking gateway system 401 to the mobile interworking gateway system 401 and the interworking gateway system 403 in the mobile network is the first emergency account, and is configured to the mobile interworking gateway system 401.
  • the account of the MMS center is the second emergency account;
  • Two firewall scripts are configured in the configuration interface to the mobile interworking gateway system 401.
  • One is a firewall script that takes over the telecommunications service: mapping IPlb to IP2a, and the other is restoring the telecommunications service to the original telecommunications interworking gateway system 402.
  • Firewall script Map IPlb to IP2b.
  • two firewall scripts are configured in the configuration interface on the interworking gateway system 402 of the telecommunications: Take over the mobile service and resume the mobile service script. According to different actual situations, the configured firewall scripts are different, but all pass the address.
  • the firewall in the solution may also be a router or a layer 4 switch, as long as the mapping of the IP address can be modified;
  • the corresponding operation can be performed in the interworking gateway system 401 to the mobile, after the mobile interworking gateway system 401 receives the takeover command, or based on the mobile interworking gateway system 401.
  • the firewall script for taking over the telecommunication service is automatically executed, so that the firewall 405 maps the IPlb to the IP2a, and when the IP2a accesses the interworking gateway system 404 in the telecommunication network, the opposite end sees It is also IPlb, which ensures that the peers see the same IP address before and after the switch, so that no communication object coordination is required during the handover; the mobile interworking gateway system 401 automatically enables all emergency accounts, including the telecommunication network.
  • the message sent by the MMS center to the telecommunication user is automatically sent to the mobile Interworking gateway system 401, interworking in a telecommunications network
  • the message sent by the gateway system 404 to the Unicom network is also automatically sent to the mobile interworking gateway system 401 to complete the takeover of the telecommunication service.
  • Firewall 405 maps IPlb to IP2b, automatically disabling all emergency accounts, including interworking gateway systems with MMS and telecommunications networks
  • the connection of these emergency accounts is automatically disconnected, and after the interworking gateway system 402 of the telecommunications is started, the related account connection is automatically established, and the telecommunication service is successfully restored.
  • the method and system for emergency handover configureds a mapping IP address in a network device capable of address mapping in the previous stage, so that corresponding devices in each service processing subsystem are mutually backup devices, when a service is processed.
  • the IP address mapped to the network device in the previous-level network device is mapped to the corresponding device of another service processing subsystem, and the corresponding device of the other service processing subsystem is used as the backup device.
  • the business of the device in question can be processed, so that the standby device can be started quickly and easily when there is a problem with the original device.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本发明公开了一种应急切换的方法和系统,涉及通信技术。本发明实施例通过在前一级能够进行地址映射的网络设备中配置映射IP地址,实现各个业务处理子系统中对应的设备互为备份设备,当一个业务处理子系统的设备出现问题时,只要将前一级网络设备中映射到该网络设备的IP地址映射到另一个业务处理子系统的相应设备中,由另一业务处理子系统的相应设备作为备用设备处理出现问题的设备的业务即可,从而实现在原设备出现问题时简便快速的启动备用设备。

Description

一种应急切换的方法和系统 技术领域
本发明涉及通信技术, 尤其涉及通信技术中一种应急切换的方法和系 统。 背景技术
目前, 很多通信系统中都存在多个业务处理子系统, 各个业务处理子 系统是相对独立的。 例如, 运营商网间的点到点彩信消息的转发服务系统 中, 用到了彩信互通网关业务处理子系统, 而每个运营商与其他任一个运 营商之间都具备互通网关业务处理子系统, 因此每个运营商至少有两套互 通网关业务处理子系统。
由于各个业务处理子系统都在通信过程中起到重要的作用, 因此, 为 避免业务处理子系统中的设备出现故障, 通常会对重要的设备进行备份。 目前, 普遍釆用的备份技术是双机热备份技术。
但双机热备份技术存在如下缺点: 1 ) 当一个服务器的机架因为断电等 原因不能工作时, 原设备和备份设备都会因机架的断电而断电, 均无法运 行, 不能实现及时切换; 2 ) 当切换失败时, 仍不能保证业务的正常运行。 如果出现这两种情况, 则需要手动启用备用设备, 使其能够承载出现问题 的设备所承载的业务, 通常这个时间至少需要花费 1到 2小时, 且手动切 换的过程费时费力, 也容易出错。 发明内容
有鉴于此, 本发明实施例的主要目的在于提供一种应急切换的方法和 系统, 以实现在原设备出现问题时简便快速的启动备用设备。 为了解决上述技术问题, 本发明的技术方案是这样实现的: 一种应急切换的方法, 包括: 第一业务处理子系统中的设备出现问题 后, 负责地址映射的网络设备修改映射到第一业务处理子系统的 IP地址的 映射关系, 使得所述映射到第一业务处理子系统的 IP地址映射到第二业务 处理子系统; 由所述第二业务处理子系统处理所述第一业务处理子系统的 业务, 所述第二业务处理子系统中预先存储了处理所述第一业务处理子系 统的业务所需的数据。
所述由第二业务处理子系统处理第一业务处理子系统的业务, 包括: 所述第二业务处理子系统启用预先设定的用于与所述第一业务处理子系统 的通信对象连接的第一应急账号, 并通过所述第一应急账号与所述第一业 务处理子系统的通信对象建立连接。
所述由第二业务处理子系统处理第一业务处理子系统的业务, 包括: 所述第二业务处理子系统启用预先设定的用于与所述第一业务处理子系统 的外围设备连接的第二应急账号, 并通过所述第二应急账号与所述第一业 务处理子系统的外围设备建立连接。
所述由第二业务处理子系统处理第一业务处理子系统的业务之后, 进 一步包括: 当所述第一业务处理子系统中的设备故障排除后, 所述网络设 备还原映射关系; 所述第二业务处理子系统断开与第一业务处理子系统的 通信对象和外围设备的连接, 所述第一业务处理子系统建立与所述通信对 象和外围设备的连接。
所述负责地址映射的网络设备修改映射到第一业务处理子系统的 IP地 址的映射关系, 具体为: 所述第二业务处理子系统运行预先设定的网络设 备脚本, 控制所述负责地址映射的网络设备修改映射到第一业务处理子系 统的 IP地址的映射关系或还原所述第一业务处理子系统的 IP地址的映射关 系。 一种应急切换系统, 包括第一业务处理子系统、 第二业务处理子系统 和用于进行地址映射的网络设备, 所述用于进行地址映射的网络设备, 用 于在所述第一业务处理子系统中的设备出现问题后, 修改映射到第一业务 处理子系统的 IP地址的映射关系, 使得所述映射到第一业务处理子系统的 IP地址映射到第二业务处理子系统; 所述第二业务处理子系统, 用于在所 述网络设备^ ί 改映射到第一业务处理子系统的 IP地址的映射关系后, 才艮据 预先存储的处理所述第一业务处理子系统的业务所需的数据, 处理所述第 一业务处理子系统的业务。
所述第二业务处理子系统具体用于: 在所述网络设备修改映射到第一 业务处理子系统的 IP地址的映射关系后, 启用预先设定的连接所述第一业 务处理子系统的通信对象的第一应急账号, 并通过所述第一应急账号与所 述第一业务处理子系统的通信对象建立连接。
所述第二业务处理子系统具体用于: 在所述网络设备修改映射到第一 业务处理子系统的 IP地址的映射关系后, 启用预先设定的连接外围设备的 第二应急账号, 并通过所述第二应急账号与所述第一业务处理子系统的外 围设备建立连接。
所述网络设备, 还用于当所述第一业务处理子系统中的设备故障排除 后, 还原所述第一业务处理子系统的 IP地址的映射关系; 所述第二业务处 理子系统, 还用于当所述第一业务处理子系统中的设备故障排除后, 断开 与第一业务处理子系统的通信对象和外围设备的连接; 所述第一业务处理 子系统, 用于当故障排除后, 重新建立与通信对象和外围设备的连接。
所述第二业务处理子系统还用于: 运行所述第二业务处理子系统中预 先设定的网络设备脚本, 控制所述负责地址映射的网络设备修改映射到第 一业务处理子系统的 IP地址的映射关系或还原所述第一业务处理子系统的 IP地址的映射关系。 本发明实施例提供一种应急切换的方法和系统, 通过在前一级能够进 行地址映射的网络设备中配置映射 IP地址, 实现各个业务处理子系统中对 应的设备互为备份设备, 当一个业务处理子系统的设备出现问题时, 只要 将前一级网络设备中映射到该网络设备的 IP地址映射到另一个业务处理子 系统的相应设备中, 由另一业务处理子系统的相应设备作为备用设备处理 出现问题的设备的业务即可, 从而实现在原设备出现问题时简便快速地启 动备用设备。 附图说明
图 1为本发明实施例提供的应急切换的方法流程示意图一;
图 2为本发明实施例提供的应急切换的方法流程示意图二;
图 3为本发明实施例提供的应急切换的系统结构示意图;
图 4为本发明实施例提供的联通网络中彩信业务应急切换的系统结构 示意图。 具体实施方式
本发明实施例提供一种应急切换的方法和系统, 由于在一般的系统中 都存在用于进行地址映射的网元, 该网元可以是路由器, 更多的情况是用 来进行安全管理和地址映射的防火墙。 本发明实施例利用该可以进行地址 映射的网元, 通过事先的配置, 在一个业务处理子系统中的设备出现问题 后, 可以修改地址映射关系, 将本应转发给出现问题的业务处理子系统的 数据转发给作为备用业务处理子系统的其它业务处理子系统, 由备用业务 处理子系统来临时处理出现问题的业务处理子系统的业务, 从而快捷地启 动备用设备, 同时由于不限制两个业务处理子系统之间的距离, 所以灵活 性更高。
如图 1所示, 本发明实施例提供的应急切换的方法包括如下几个步骤: 步骤 101、 第一业务处理子系统中的设备出现问题后, 通信系统中负责 地址映射的网络设备修改映射到第一业务处理子系统的 IP 地址的映射关 系,使得映射到第一业务处理子系统的 IP地址映射到第二业务处理子系统; 步骤 102、 第二业务处理子系统处理第一业务处理子系统的业务, 第二 业务处理子系统中预先存储了处理第一业务处理子系统的业务所需的数 据。
这样, 只要根据预先的设定, 将映射到第一业务处理子系统的 IP地址 直接修改为映射到第二业务处理子系统, 并事先在第二业务处理子系统中 存储处理第一业务处理子系统的业务所需要的数据, 即可使得第二业务处 理子系统作为第一业务处理子系统的备份业务处理子系统, 在第一业务处 理子系统不能正常工作时, 临时处理第一业务处理子系统的业务, 切换过 程快捷方便, 并且由于釆用的是修改地址映射关系的方法, 对第一业务处 理子系统和第二业务处理子系统的位置关系没有任何要求, 第一业务处理 子系统和第二业务处理子系统甚至可以位于距离遥远的两个城市, 因此, 即使出现区域停电等事故, 仍可以釆用本发明实施例提供的应急切换方法 进行应急处理。
其中, 用于进行地址映射的网络设备可以是路由器、 交换机, 也可以 是既能进行安全管理又能进行地址映射的防火墙。
通常, 为了保证通信过程的安全, 各个业务处理子系统都需要通过账 号和通信对象以及外围设备建立连接, 并在该连接的基础上实现通信和相 关业务的处理。 此时, 还需要在第二业务处理子系统上设置应急账号, 需 要与多少个通信对象和外围设备建立连接, 就设置多少应急账号。 第二业 务处理子系统在网络设备修改映射到第一业务处理子系统的 IP地址的映射 关系后, 开始启用预先设定的用于与第一业务处理子系统的通信对象连接 的第一应急账号, 并通过第一应急账号与第一业务处理子系统的通信对象 建立连接, 如果第一业务处理子系统有外围设备, 那么第二业务处理子系 统还需要启用预先设定的用于与第一业务处理子系统的外围设备连接的第 二应急账号, 并通过第二应急账号与第一业务处理子系统的外围设备建立 连接。
并且, 本发明实施例进一步在各个业务处理子系统上配置了相应的网 络设备脚本, 当需要由一个业务处理子系统接管其它业务处理子系统的业 务时, 该业务处理子系统运行相应的网络设备脚本, 即可控制进行地址映 射的网络设备修改地址映射关系, 使网络设备将转发给出现故障的业务处 理子系统的数据转发给该业务处理子系统; 当故障排除后, 再运行相应的 脚本, 控制进行地址映射的网络设备恢复地址映射关系, 使网络设备正常 转发数据给已经排除故障的业务处理子系统。 映射地址的修改和恢复都非 常方便。
进一步, 如图 2 所示, 本发明实施例的应急切换的方法中还进一步包 括:
步骤 103、 当第一业务处理子系统中的设备故障排除后, 网络设备还原 映射关系;
步骤 104、第二业务处理子系统断开第一应急账号和第二应急账号的连 接, 第一业务处理子系统建立与通信对象和外围设备的连接。
这样即可方便快捷的使第二业务处理子系统断开与第一业务处理子系 统的通信对象和外围设备的的连接, 实现从第二业务处理子系统切换回第 一业务处理子系统。
本发明实施例还提供一种应急切换系统, 如图 3 所示, 包括: 第一业 务处理子系统 301、第二业务处理子系统 302和用于进行地址映射的网络设 备 303 , 其中:
用于进行地址映射的网络设备 303 用于: 在第一业务处理子系统 301 中的设备出现问题后, 修改映射到第一业务处理子系统 301的 IP地址的映 射关系, 使得映射到第一业务处理子系统 301的 IP地址映射到第二业务处 理子系统 302;
第二业务处理子系统 302用于, 在网络设备修改映射到第一业务处理 子系统 301的 IP地址的映射关系后, 根据预先存储的处理第一业务处理子 系统 301的业务所需的数据, 处理第二业务处理子系统 302的业务。
其中, 网络设备 303可以为路由器、 交换机, 还可以为防火墙。
进一步地, 当需要使用账号与第一业务处理子系统的通信对象建立连 接时, 第二业务处理子系统 302具体用于: 在网络设备修改映射到第一业 务处理子系统 301的 IP地址的映射关系后, 启用预先设定的连接第一业务 处理子系统 301 的通信对象的第一应急账号, 并通过第一应急账号与第一 业务处理子系统 301的通信对象建立连接。
当第一业务处理子系统 301 有外围设备时, 为实现与外围设备的安全 通信, 第二业务处理子系统 302具体用于: 在网络设备修改映射到第一业 务处理子系统 301的 IP地址的映射关系后, 启用预先设定的连接外围设备 的第二应急账号, 并通过第二应急账号与第一业务处理子系统 301 的外围 设备建立连接。
进一步地, 为便于在第一业务处理子系统排除故障后恢复原状态, 网 络设备 303还用于: 当第一业务处理子系统 301 中的设备故障排除后, 还 原第一业务处理子系统 301的 IP地址的映射关系;
第二业务处理子系统 302还用于, 当第一业务处理子系统中的设备故 障排除后, 断开第一应急账号和第二应急账号的连接, 即断开与第一业务 处理子系统的通信对象和外围设备的的连接;
第一业务处理子系统 301 用于, 当故障排除后, 重新建立与通信对象 和外围设备的连接。 下面以一个具体实例进行说明:
如图 4所示, 以联通网络为例, 联通网络中釆用的通信制式与移动网 络和电信网络不同, 所以为了实现网间业务, 联通网络需要设置到移动的 互通网关系统 401和到电信的互通网关系统 402, —般情况下, 以彩信业务 为例, 到移动的互通网关系统 401和到电信的互通网关系统 402会处理各 自的彩信消息, 互相之间不会有消息交互。
4叚定到移动的互通网关系统 401的 IP地址为 IP2a, 它通过防火墙 405 和移动网络中的互通网关系统 403建立连接, 防火墙 405为该连接设置的 IP地址为 IPla, 当移动网络中的互通网关系统 403和到移动的互通网关系 统 401进行通信时, 移动网络中的互通网关系统 403发送数据至 IPla这一 地址, 由防火墙 405将 IPla这一地址映射为 IP2a, 实际上虽然移动网络中 的互通网关系统 403发送数据至 IPla这一地址,但由于防火墙 405的映射, 移动网络中的互通网关系统 403事实上是将数据发送到了 IP地址为 IP2a的 到移动的互通网关系统 401。 同样道理, 4叚定到电信的互通网关系统 402的 IP地址为 IP2b , 它通过防火墙 405和电信网络中的互通网关系统 404建立 连接, 防火墙 405为该连接设置的 IP地址为 IPlb, 当电信网络中的互通网 关系统 404和到电信的互通网关系统 402进行通信时, 虽然电信网络中的 互通网关系统 404发送数据至 IPlb这一地址, 但由于防火墙 405的映射, 电信网络中的互通网关系统 404事实上是将数据发送到了 IP地址为 IP2b 的到电信的互通网关系统 402。
通过本发明实施例提供的应急切换方法,在到电信的互通网关系统 402 出现异常无法提供服务后, 可在到移动的互通网关系统 401 上执行预定的 防火墙脚本或菜单操作, 由到移动的互通网关系统 401 接管到电信的互通 网关系统 402的业务。 到移动的互通网关系统 401上执行预定的防火墙脚 本或菜单操作后, 控制防火墙 405将 IPlb的映射地址由 IP2b修改为 IP2a, 电信网络中的互通网关系统 404发送给到电信的互通网关系统 402的消息 会直接根据地址映射关系发送给到移动的互通网关系统 401 ,而且这种切换 费时较少, 最大程度地降低了业务损失。 在到电信的互通网关系统 402恢 复正常后, 可以在到移动的互通网关系统 401 处进行恢复, 执行预定的防 火墙脚本或菜单操作后, 使得防火墙 405将 IPlb的映射地址恢复为 IP2b, 将业务切换回到电信的互通网关系统 402。 同理, 当到移动的互通网关系统 401出现异常无法提供服务后,也可以由到电信的互通网关系统 402作为备 用业务处理子系统。
进一步, 还可以在网络层面, 以主备传输链路的方式进行应急切换, 每条链路使用统一的带宽。
在到移动的互通网关系统 401 中需要配置到电信的互通网关系统 402 的账号数据, 如到电信的互通网关系统 402与彩信中心、 电信网络中的互 通网关系统 404等外围设备和通信对象的账号、 密码等, 该账号即应急账 号, 另外还需要配置到电信的互通网关系统 402 的业务数据, 如网号、 号 段等信息, 保证接管后到移动的互通网关系统 401 能够正常处理鉴权等业 务; 同样, 到电信的互通网关系统 402 中也需要配置到移动的互通网关系 统 401的账号数据和业务数据。
还可以在操作系统中增加 "一键式接管" 和 "一键式恢复" 功能按钮 或选项, 触发后会直接调用接管或恢复时需要使用的防火墙脚本, 便于工 作人员操作。
例如,在到移动的互通网关系统 401上配置到电信的互通网关系统 402 与电信网络中的互通网关系统 404 的账号为第一应急账号, 配置到电信的 互通网关系统 402与彩信中心的账号为第二应急账号; 同理, 到电信的互 通网关系统 402上也配置到移动的互通网关系统 401与移动网络中的互通 网关系统 403的账号为第一应急账号, 配置到移动的互通网关系统 401与 彩信中心的账号为第二应急账号;
在到移动的互通网关系统 401 上的配置界面中配置两个防火墙脚本, 一个是接管电信业务的防火墙脚本: 把 IPlb映射到 IP2a, 另外一个是把电 信业务恢复到原到电信的互通网关系统 402的防火墙脚本: 把 IPlb映射到 IP2b。 同理,在到电信的互通网关系统 402上的配置界面中配置两个防火墙 脚本: 接管移动业务以及恢复移动业务的脚本, 根据不同的实际情况, 所 配置的防火墙脚本不同, 但都是通过地址的映射关系来实现业务的接管和 恢复。 当然方案中的防火墙, 也可以是路由器或四层交换机, 只要能够实 现 IP地址的映射修改即可;
当到电信的互通网关系统 402 中的设备异常时, 则可以在到移动的互 通网关系统 401进行相应操作, 到移动的互通网关系统 401接收到接管命 令后, 或者到移动的互通网关系统 401 基于握手协议发现到电信的互通网 关系统 402 中的设备异常时, 自动执行接管电信业务的防火墙脚本, 使得 防火墙 405将 IPlb映射到 IP2a, 从 IP2a访问电信网络中的互通网关系统 404时对端看到的也是 IPlb,这样可以确保对端在切换前后看到的都是同一 个 IP地址,这样在切换时无需通信对象的配合;到移动的互通网关系统 401 自动启用所有应急账号, 包括与到电信网络中的互通网关系统 404 的和到 彩信中心等外围设备的; 由于到移动的互通网关系统 401 自动继承了原有 的账号和路由数据, 因此彩信中心发给电信用户的消息自动发给到移动的 互通网关系统 401 ,电信网络中的互通网关系统 404发给联通网络的消息也 自动发给到移动的互通网关系统 401上, 完成电信业务的接管。
当到电信的互通网关系统 402 恢复正常时, 则在到移动的互通网关系 统 401上执行恢复的操作, 到移动的互通网关系统 401接收到恢复命令后, 自动执行恢复电信业务的防火墙脚本,使得防火墙 405将 IPlb映射到 IP2b, 自动禁用所有应急账号, 包括与彩信中心和与电信网络中的互通网关系统 404的,自动断开这些应急账号的连接 ,到电信的互通网关系统 402启动后 , 自动建立相关账号连接, 电信业务恢复成功。
本发明实施例提供的应急切换的方法和系统, 通过在前一级能够进行 地址映射的网络设备中配置映射 IP地址, 实现各个业务处理子系统中对应 的设备互为备份设备, 当一个业务处理子系统的设备出现问题时, 只要将 前一级网络设备中映射到该网络设备的 IP地址映射到另一个业务处理子系 统的相应设备中, 由另一业务处理子系统的相应设备作为备用设备处理出 现问题的设备的业务即可, 从而实现在原设备出现问题时简便快速的启动 备用设备。 本发明的精神和范围。 这样, 倘若本发明的这些修改和变型属于本发明权 利要求及其等同技术的范围之内, 则本发明也意图包含这些改动和变型在 内。

Claims

权利要求书
1、 一种应急切换的方法, 其特征在于, 包括:
第一业务处理子系统中的设备出现问题后, 负责地址映射的网络设备 修改映射到第一业务处理子系统的 IP地址的映射关系, 使得所述映射到第 一业务处理子系统的 IP地址映射到第二业务处理子系统;
由所述第二业务处理子系统处理所述第一业务处理子系统的业务, 所 述第二业务处理子系统中预先存储了处理所述第一业务处理子系统的业务 所需的数据。
2、 如权利要求 1所述的方法, 其特征在于, 所述由第二业务处理子系 统处理第一业务处理子系统的业务, 包括: 所述第二业务处理子系统启用 预先设定的用于与所述第一业务处理子系统的通信对象连接的第一应急账 号, 并通过所述第一应急账号与所述第一业务处理子系统的通信对象建立 连接。
3、 如权利要求 1所述的方法, 其特征在于, 所述由第二业务处理子系 统处理第一业务处理子系统的业务, 包括: 所述第二业务处理子系统启用 预先设定的用于与所述第一业务处理子系统的外围设备连接的第二应急账 号, 并通过所述第二应急账号与所述第一业务处理子系统的外围设备建立 连接。
4、 如权利要求 1、 2或 3所述的方法, 其特征在于, 所述由第二业务 处理子系统处理第一业务处理子系统的业务之后, 进一步包括:
当所述第一业务处理子系统中的设备故障排除后, 所述网络设备还原 映射关系;
所述第二业务处理子系统断开与第一业务处理子系统的通信对象和外 围设备的连接, 所述第一业务处理子系统建立与所述通信对象和外围设备 的连接。
5、 如权利要求 4所述的方法, 其特征在于, 所述负责地址映射的网络 设备修改映射到第一业务处理子系统的 IP地址的映射关系, 具体为: 所述 第二业务处理子系统运行预先设定的网络设备脚本, 控制所述负责地址映 射的网络设备修改映射到第一业务处理子系统的 IP地址的映射关系或还原 所述第一业务处理子系统的 IP地址的映射关系。
6、 一种应急切换系统, 包括第一业务处理子系统、 第二业务处理子系 统和用于进行地址映射的网络设备, 其特征在于,
所述用于进行地址映射的网络设备, 用于在所述第一业务处理子系统 中的设备出现问题后, 修改映射到第一业务处理子系统的 IP地址的映射关 系, 使得所述映射到第一业务处理子系统的 IP地址映射到第二业务处理子 系统;
所述第二业务处理子系统, 用于在所述网络设备修改映射到第一业务 处理子系统的 IP地址的映射关系后, 根据预先存储的处理所述第一业务处 理子系统的业务所需的数据, 处理所述第一业务处理子系统的业务。
7、 如权利要求 6所述的系统, 其特征在于, 所述第二业务处理子系统 具体用于: 在所述网络设备修改映射到第一业务处理子系统的 IP地址的映 射关系后, 启用预先设定的连接所述第一业务处理子系统的通信对象的第 一应急账号, 并通过所述第一应急账号与所述第一业务处理子系统的通信 对象建立连接。
8、 如权利要求 6所述的系统, 其特征在于, 所述第二业务处理子系统 具体用于: 在所述网络设备修改映射到第一业务处理子系统的 IP地址的映 射关系后, 启用预先设定的连接外围设备的第二应急账号, 并通过所述第 二应急账号与所述第一业务处理子系统的外围设备建立连接。
9、 如权利要求 6、 7或 8所述的系统, 其特征在于,
所述网络设备, 还用于当所述第一业务处理子系统中的设备故障排除 后, 还原所述第一业务处理子系统的 IP地址的映射关系;
所述第二业务处理子系统, 还用于当所述第一业务处理子系统中的设 备故障排除后, 断开与第一业务处理子系统的通信对象和外围设备的连接; 所述第一业务处理子系统, 用于当故障排除后, 重新建立与通信对象 和外围设备的连接。
10、 如权利要求 9所述的系统, 其特征在于, 所述第二业务处理子系 统还用于: 运行所述第二业务处理子系统中预先设定的网络设备脚本, 控 制所述负责地址映射的网络设备修改映射到第一业务处理子系统的 IP地址 的映射关系或还原所述第一业务处理子系统的 IP地址的映射关系。
PCT/CN2010/076986 2010-04-02 2010-09-16 一种应急切换的方法和系统 Ceased WO2011120282A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP10848741.4A EP2523480B1 (en) 2010-04-02 2010-09-16 Method and system for emergency switching
US13/517,390 US20130013955A1 (en) 2010-04-02 2010-09-16 Method and system for emergency switching
JP2013501598A JP5767309B2 (ja) 2010-04-02 2010-09-16 緊急時用切り替え方法及びそのシステム
CA2789794A CA2789794C (en) 2010-04-02 2010-09-16 Method and system for emergency switching

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010142717.1A CN102215272B (zh) 2010-04-02 2010-04-02 一种应急切换的方法和系统
CN201010142717.1 2010-04-02

Publications (1)

Publication Number Publication Date
WO2011120282A1 true WO2011120282A1 (zh) 2011-10-06

Family

ID=44711329

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/076986 Ceased WO2011120282A1 (zh) 2010-04-02 2010-09-16 一种应急切换的方法和系统

Country Status (6)

Country Link
US (1) US20130013955A1 (zh)
EP (1) EP2523480B1 (zh)
JP (1) JP5767309B2 (zh)
CN (1) CN102215272B (zh)
CA (1) CA2789794C (zh)
WO (1) WO2011120282A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2842156B1 (en) 2012-04-23 2020-06-03 Lawrence Livermore National Security, LLC Localized atmospheric laser chemical vapor deposition
CN110351128A (zh) * 2019-06-27 2019-10-18 北京大米科技有限公司 一种业务处理方法、装置、存储介质及服务器
CN113610483A (zh) * 2021-07-01 2021-11-05 北京思特奇信息技术股份有限公司 一种应急快速开机实现的系统及实现方法

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060120396A1 (en) * 2004-12-02 2006-06-08 Kddi Corporation Communication system, delay insertion server, backup server and communication control apparatus
EP1679842A1 (en) * 2005-01-06 2006-07-12 AT&T Corp. Bandwidth management for MPLS fast rerouting
JP2006268687A (ja) * 2005-03-25 2006-10-05 Mitsubishi Electric Corp コンピュータウィルス監視プログラム及びこれを用いたコンピュータ端末装置
US20080020759A1 (en) * 2006-07-20 2008-01-24 Symbol Technologies, Inc. Techniques for home wireless switch redundancy and stateful switchover in a network of wireless switches supporting layer 3 mobility within a mobility domain
CN101150436A (zh) * 2007-11-06 2008-03-26 中国移动通信集团江苏有限公司 爱立信oss rc系统n+1容灾备份方法
CN101616385A (zh) * 2008-06-24 2009-12-30 中国移动通信集团公司 通信业务切换的方法、系统及地址解析服务器

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH08186618A (ja) * 1994-12-28 1996-07-16 Hitachi Ltd 情報処理装置の切り替え装置
US5936936A (en) * 1997-04-11 1999-08-10 International Business Machines Corporation Redundancy mechanisms for classical internet protocol over asynchronous transfer mode networks
US6108300A (en) * 1997-05-02 2000-08-22 Cisco Technology, Inc Method and apparatus for transparently providing a failover network device
US6728780B1 (en) * 2000-06-02 2004-04-27 Sun Microsystems, Inc. High availability networking with warm standby interface failover
JP4393032B2 (ja) * 2002-03-27 2010-01-06 富士通株式会社 障害時の経路切替え機能を備えた情報処理システム及びその情報端末
US7647427B1 (en) * 2002-10-18 2010-01-12 Foundry Networks, Inc. Redundancy support for network address translation (NAT)
JP2006253900A (ja) * 2005-03-09 2006-09-21 Hitachi Ltd Ipアドレス引き継ぎ方法、ipアドレスアドレス引き継ぎプログラム、サーバおよびネットワークシステム
CN101150439A (zh) * 2007-09-25 2008-03-26 华为技术有限公司 一种实现主备切换的方法、系统及设备
US9032240B2 (en) * 2009-02-24 2015-05-12 Hewlett-Packard Development Company, L.P. Method and system for providing high availability SCTP applications

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060120396A1 (en) * 2004-12-02 2006-06-08 Kddi Corporation Communication system, delay insertion server, backup server and communication control apparatus
EP1679842A1 (en) * 2005-01-06 2006-07-12 AT&T Corp. Bandwidth management for MPLS fast rerouting
JP2006268687A (ja) * 2005-03-25 2006-10-05 Mitsubishi Electric Corp コンピュータウィルス監視プログラム及びこれを用いたコンピュータ端末装置
US20080020759A1 (en) * 2006-07-20 2008-01-24 Symbol Technologies, Inc. Techniques for home wireless switch redundancy and stateful switchover in a network of wireless switches supporting layer 3 mobility within a mobility domain
CN101150436A (zh) * 2007-11-06 2008-03-26 中国移动通信集团江苏有限公司 爱立信oss rc系统n+1容灾备份方法
CN101616385A (zh) * 2008-06-24 2009-12-30 中国移动通信集团公司 通信业务切换的方法、系统及地址解析服务器

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
US20130013955A1 (en) 2013-01-10
CN102215272B (zh) 2014-03-12
EP2523480A1 (en) 2012-11-14
EP2523480B1 (en) 2020-10-21
CA2789794C (en) 2019-01-15
CN102215272A (zh) 2011-10-12
EP2523480A4 (en) 2017-06-21
JP5767309B2 (ja) 2015-08-19
CA2789794A1 (en) 2011-10-06
JP2013527648A (ja) 2013-06-27

Similar Documents

Publication Publication Date Title
CN102439903B (zh) 实现容灾备份的方法、设备及系统
CN102098201B (zh) 一种实现l2tp用户接入备份的方法及网络系统
CN102006189B (zh) 用于双机冗余备份的主用接入服务器确定方法及装置
JP5366177B2 (ja) スロットインターフェースアクセス装置、その方法及びそのプログラム並びに主装置の冗長構成及び代替方法
JP2006013827A (ja) パケット転送装置
JP2013519268A (ja) データ転送方法、データ転送装置及びデータ転送システム
CN101841432A (zh) 一种业务接入路由器的端口备份方法、装置和系统
JP2013030190A (ja) スロットインターフェースアクセス装置、その方法及びそのプログラム並びに主装置の冗長構成及び代替方法
WO2021098806A1 (zh) 报文传输路径的切换方法、设备和系统
CN110324375A (zh) 一种信息备份方法及相关设备
US8935564B2 (en) Method for backing up user information and apparatus in standby service node for backing up user information
WO2011120282A1 (zh) 一种应急切换的方法和系统
CN104125079B (zh) 一种确定双机热备份配置信息的方法及装置
JP2009218727A (ja) 通信管理システム、通信管理方法及び通信装置
CN107395424B (zh) 一种实现tcp连接备份的方法
CN104917689A (zh) 一种实现按需智能拨号的方法、系统和接入路由器
CN102255741B (zh) 用户业务信息备份方法和装置
CN102255716B (zh) 一种对协议状态的设备间备份的方法及系统
CN103684831A (zh) L2tp网络的保护方法、装置及系统
CN109120520B (zh) 一种故障处理方法和设备
WO2012097604A1 (zh) 网关故障时的消息处理方法、系统和网关
CN100488148C (zh) 在基于以太网的点对点协议会话时实现出接口备份的方法
CN108418626B (zh) 用于DPoE网络中的光链路保护的方法和设备
WO2015180277A1 (zh) Pw双归保护倒换方法及系统
CN102946359B (zh) 一种流量转发方法和设备

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2010848741

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2013501598

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 13517390

Country of ref document: US

ENP Entry into the national phase

Ref document number: 2789794

Country of ref document: CA

NENP Non-entry into the national phase

Ref country code: DE