WO2011157146A2 - 通信设备间的主备倒换方法、通信设备和***及服务请求设备 - Google Patents

通信设备间的主备倒换方法、通信设备和***及服务请求设备 Download PDF

Info

Publication number
WO2011157146A2
WO2011157146A2 PCT/CN2011/075057 CN2011075057W WO2011157146A2 WO 2011157146 A2 WO2011157146 A2 WO 2011157146A2 CN 2011075057 W CN2011075057 W CN 2011075057W WO 2011157146 A2 WO2011157146 A2 WO 2011157146A2
Authority
WO
WIPO (PCT)
Prior art keywords
standby
primary
communication device
service
address
Prior art date
Application number
PCT/CN2011/075057
Other languages
English (en)
French (fr)
Other versions
WO2011157146A3 (zh
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 华为技术有限公司
Priority to CN201180000978.2A priority Critical patent/CN102265556B/zh
Priority to PCT/CN2011/075057 priority patent/WO2011157146A2/zh
Publication of WO2011157146A2 publication Critical patent/WO2011157146A2/zh
Publication of WO2011157146A3 publication Critical patent/WO2011157146A3/zh

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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5019—Ensuring fulfilment of SLA
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/2002—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where interconnections or communication control functionality are redundant
    • G06F11/2005—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where interconnections or communication control functionality are redundant using redundant communication controllers

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to an active/standby switching method, a communication device and system, and a service requesting device between communication devices. Background technique
  • the packet gateway device provides a series of important services when the user accesses the Internet, such as: assigning an IP address, authentication, charging, and service control to the terminal. Since packet gateway devices and other types of communication devices are located at important network locations and have the ability to serve a large number of users, communication systems have high reliability requirements for these devices.
  • a real-time backup gateway device is required to quickly take over the services of the primary gateway device.
  • the prior art is used to establish a backup synchronization channel and a heartbeat message channel between the active and standby gateway devices.
  • the backup synchronization channel is used to perform data hot backup between the active and standby gateway devices, and the heartbeat message channel is used to detect faults.
  • the master/slave gateway device performs the master/slave switchover, that is, the backup gateway device takes over the service provided by the master gateway device.
  • the active and standby gateway devices in the communication system will use the shared resources to provide bearers.
  • This phenomenon is called "double live".
  • the "double live” phenomenon may cause abnormal network behavior, such as address conflicts, routing conflicts, etc., causing the peripheral network element of the gateway device to be abnormally determined. If the network address or destination address of the packet cannot be correctly judged, the source address or destination address of the packet is incorrect. Whether the primary gateway device or the standby gateway device is pointed to, the surrounding network elements may deactivate a large number of online users, causing user service interruption and increasing users. Business loss. Summary of the invention
  • the embodiments of the present invention provide an active/standby switching method, a communication device, a system, and a service requesting device between communication devices, which are used to reduce the probability of user service interruption when performing active/standby switching between communication devices.
  • An embodiment of the present invention provides an active/standby switchover method between communication devices, including:
  • the primary communications device And receiving an active/standby switching negotiation request that is sent by the primary communications device and carrying the fault information, where the fault information includes: a service load and a current loss amount of the primary communications device;
  • the active/standby switching indication is used to instruct the service requesting device to switch its signaling communication pointer from the primary signaling interaction interface address of the primary communication device to the standby communication The standby signaling interface address of the device;
  • the embodiment of the present invention further provides another active/standby switching method between the communication devices, including: acquiring support capability information of the service request device connected to the primary communication device, where the support capability information is used to indicate that the service request device supports
  • the primary and secondary address pairs include: a primary signaling interaction interface address of the primary communication device, and a standby signaling interaction interface address of the secondary communication device;
  • the embodiment of the present invention further provides an active/standby switching method between the communication devices, including: reporting the support capability information of the service requesting device to the primary communication device; and the supporting capability information is used to indicate that the service requesting device supports the active and standby devices.
  • Receiving the primary and secondary address pairs sent by the primary communication device where the primary and secondary address pairs include: Decoding the primary signaling interaction interface address of the primary communication device and the standby signaling interaction interface address of the standby communication device; pointing the signaling communication pointer of the service requesting device to the primary signaling interaction interface address, and receiving the When the active/standby switching indication sent by the communications device is described, the signaling communication pointer is switched from the primary signaling interaction interface address to the standby signaling interaction interface address.
  • the embodiment of the invention further provides a communication device, including:
  • the negotiation fault information obtaining module is configured to receive an active/standby switching negotiation request that is sent by the primary communications device and that carries the fault information, where the fault information includes: a service load of the primary communications device and a current loss amount;
  • An expected loss determination module configured to determine, according to a local state, a capacity, and a load condition of the communication device, and a service load of the primary communication device, an expected loss amount of the service after the switching;
  • a switching evaluation module configured to When the expected loss of the service is less than the current loss, it is determined that an active/standby switchover is required;
  • the active/standby switchover indication module is configured to send an active/standby switchover indication to the service requesting device; and the active/standby switchover indication is used to indicate the service
  • the requesting device switches its signaling communication pointer from the primary signaling interaction interface address of the primary communication device to the standby signaling interaction ⁇ address of the communication device;
  • a switching execution module configured to take over the service provided by the primary communication device.
  • the embodiment of the invention further provides another communication device, including:
  • the capability information obtaining module is configured to obtain the support capability information of the service requesting device that is connected to the primary communication device, where the support capability information is used to indicate that the service requesting device supports the primary and secondary address pairs; Decoding the primary signaling interaction interface address of the primary communication device and the standby signaling interaction interface address of the secondary communication device;
  • the address indication module is configured to send the primary and secondary address pairs to the service requesting device, and instruct the service requesting device to point its signaling communication pointer to the primary signaling interaction interface address.
  • the embodiment of the invention further provides a service requesting device, including:
  • the capability information reporting module is configured to report the support capability information of the service requesting device to the primary communication device, where the support capability information is used to indicate that the service requesting device supports the primary and secondary address pairs.
  • the primary and secondary address pairs include: a primary signaling interaction interface address of the primary communication device and a backup signaling interaction interface address of the secondary communication device;
  • An address information obtaining module configured to receive the primary and secondary address pairs sent by the primary communication device
  • a communication pointer processing module configured to point, by the signaling request pointer of the service requesting device, the primary signaling interaction interface address And, when receiving the active/standby switching indication sent by the standby communication device, switching the signaling communication pointer from the primary signaling interaction interface address to the standby signaling interaction connection ⁇ address.
  • An embodiment of the present invention further provides a communication system, including: a primary communication device, a backup communication device communicatively coupled to the primary communication device, and a service request for communication connection with the primary communication device and the standby communication device, respectively device.
  • the service requesting device when the standby communication device performs the active/standby switchover, switches its signaling communication pointer from the address of the primary signaling interaction interface to the address of the standby signaling interaction interface; thus, when the communication system has appeared When the active/standby communication device is "double live", the service requesting device filters out the service packets related to the address that the signaling communication pointer does not point to, thereby reducing the probability of the service requesting device being abnormal, thereby reducing the user service. The probability of interruption.
  • FIG. 1 is a flowchart of a method for performing active/standby switchover between communication devices according to Embodiment 1 of the present invention
  • FIG. 2 is a flowchart of a method for performing active/standby switchover between communication devices according to Embodiment 2 of the present invention
  • FIG. 4 is a schematic structural diagram of the networking of the application scenario according to the embodiment of the present invention.
  • FIG. 5 is a schematic diagram of a communication model of a GGSN in an application scenario according to an embodiment of the present invention
  • FIG. FIG. 6 is a diagram showing an IP address correspondence relationship between a master and a backup GGSN control plane module according to an embodiment of the present invention
  • FIG. 8 is an application example of an active/standby GGSN user plane module according to an embodiment of the present invention
  • FIG. 9 is an interaction diagram of an SGSN support capability information reporting method according to Embodiment 4 of the present invention
  • FIG. 10 is a schematic diagram of a method for performing active/standby consistency switching according to Embodiment 5 of the present invention; ;
  • FIG. 11 is a schematic diagram of a module for collecting a fault state of a primary GGSN according to an embodiment of the present invention
  • FIG. 12 is an interaction diagram of a method for performing a switching negotiation between a primary and a secondary GGSN according to Embodiment 6 of the present invention
  • Schematic diagram of the structure of the communication device
  • FIG. 14 is a schematic structural diagram of a communication device according to Embodiment 8 of the present invention.
  • FIG. 15 is a schematic structural diagram of a service requesting device according to Embodiment 9 of the present invention.
  • FIG. 16 is a schematic structural diagram of a communication device according to Embodiment 10 of the present invention. detailed description
  • FIG. 1 is a flowchart of an active/standby switchover method between communication devices according to Embodiment 1 of the present invention.
  • the execution body of this embodiment may be: a standby communication device corresponding to a certain primary communication device.
  • the method provided in this embodiment includes:
  • Step 11 Receiving an active/standby switchover negotiation request that is sent by the primary communication device and carrying the fault information, where the fault information includes: a service load and a current loss amount of the primary communication device.
  • the method for obtaining the fault information of the master communication device is also not limited.
  • the standby communication device can obtain the fault information of the master communication device by receiving the master/slave switchover negotiation request sent by the master communication device and carrying the fault information.
  • Step 12 Determine, according to the local state, capacity, and load status of the standby communication device, and the service load of the primary communication device, the expected expected loss of the service after the switching, and the expected loss in the service is less than the current loss. When it is determined, an active/standby switchover is required.
  • Step 13 Send an active/standby switchover indication to the service requesting device.
  • the active/standby switchover indication is used to instruct the service requesting device to switch its signaling communication pointer to the primary signaling interaction interface address of the primary communication device. The address of the alternate signaling interface of the communication device is described.
  • the service requesting device in this step has the capability of supporting the primary and secondary address pairs, that is, supporting the opposite signaling interface addresses of the active and standby communication devices, and interacting with the primary communication device respectively.
  • the address of the signaling interaction interface can be specifically as follows:
  • the primary communication device and the standby communication device have independent IP addresses for signaling interaction, which may be referred to as a primary IP address and a standby IP address.
  • the service requesting device supports the use of the primary IP address to exchange signaling with the primary communication device, and also supports the use of the standby IP address to exchange signaling with the standby communication device.
  • the manner in which the backup communication device obtains the support capability information of the service requesting device is not limited, and may be pre-configured on the active/standby communication device, or may be acquired by the primary communication device and the support capability information is synchronized to the standby communication device.
  • Step 14 Take over the service provided by the primary communication device.
  • the standby communication device preempts the shared resources of the active and standby communication devices, and provides bearers for the services provided by the primary communication device, so that the user services served by the primary communication device are not interrupted.
  • the standby communication device When the standby communication device performs the active/standby switchover, it can determine that any module on the standby communication device acts as the trigger point for the active/standby switchover, triggers each module on the standby communication device, and takes over the services provided by the peer communication module.
  • the service requesting device when the standby communication device sends an active/standby switchover indication to the service requesting device, the service requesting device instructs the device to switch its signaling communication pointer from the primary signaling interaction interface address to the standby signaling interaction interface address;
  • the active/standby communication device has been dual-active in the system.
  • the service requesting device filters out the service packets related to the address that the signaling communication pointer does not point to, thereby reducing the probability of the service requesting device being abnormal. This reduces the chance of user service interruption.
  • FIG. 2 is a flowchart of an active/standby switchover method between communication devices according to Embodiment 2 of the present invention.
  • Real The executive body of the embodiment is the primary communication device.
  • the method provided in this embodiment includes: Step 21: Obtain support capability information of a service request device connected to a primary communication device, where the support capability information is used to indicate that the service request device supports a primary and secondary address pair.
  • the master/slave address pair includes: a primary signaling interaction interface address of the primary communication device, and a backup signaling interaction interface address of the secondary communication device.
  • the manner in which the main communication device obtains the service request device support capability information is not limited, and may be pre-configured on the main communication device, or actively reported by the service request device.
  • the primary communication device can synchronize the support capability information to the standby communication device.
  • Step 22 Send the primary and secondary address pairs to the service requesting device, and instruct the service requesting device to point its signaling communication pointer to the primary signaling interaction interface address.
  • the primary communication device may also obtain the fault information, and send an active/standby switchover negotiation request to the standby communication device corresponding to the primary communication device when the fault information meets the first preset condition.
  • the fault information includes: a type of a fault that has occurred in the home network related to the primary communication device, a capacity loss amount, and a service loss amount.
  • the first preset condition includes: the type of the fault is a physical interface/link fault, and the capacity loss amount is between a preset first capacity loss threshold and a second capacity loss threshold, the service The amount of the loss is between the preset first service loss threshold and the second service loss threshold.
  • the master/slave switch negotiation request includes the fault information, and is used to request the standby communication device to determine whether to perform an active/standby switchover.
  • the primary communication device may further receive an active/standby switching negotiation response sent by the secondary communication device, and the active/standby switching negotiation response indicates the standby communication device
  • the backup communication device takes over the service provided by the primary communication device.
  • the fault information meets the second preset condition or the third preset condition, sending an active/standby switchover request to the standby communication device, where the active/standby switchover request is used to trigger the standby communication device to start.
  • the second preset condition includes: the type of the fault is a physical interface/link failure, the capacity loss amount is greater than or equal to the second capacity loss threshold, and the service loss amount is greater than or Equal to the second service loss threshold;
  • the third preset condition includes: the faulty class The type is a device module failure. And/or, when the fault information indicates that an existing fault has occurred, the alarm prompt information is output.
  • the primary communication device may send an active/standby switchover request to the standby communication device to perform the active/standby switchover when the primary communication device detects that the critical module is faulty.
  • the primary communication device when it learns the support capability information of the service requesting device, it sends a primary and secondary address pair to the service requesting device, and instructs the service requesting device to point its signaling communication pointer to the primary signaling interaction interface address, thereby
  • the service message related to the address that the signaling communication pointer does not point to can be filtered out, thereby reducing the probability that the service requesting device is abnormally determined, thereby reducing the probability
  • the probability of interruption of the user service is further provided.
  • the negotiation mechanism of the active/standby switchover can also be introduced:
  • the primary communication device determines the current active/standby switchover based on the collected fault state information, and the current communication device
  • the capacity loss and the service loss are sent to the backup communication device, and the backup communication device determines whether to accept the negotiation for the active/standby switchover.
  • the active/standby switchover mechanism performs the switchover, which avoids the takeover of the communication device after the switchover. Limited capacity and greater loss to the user, which in turn benefits Reduce the risk due to the switchover does not apply to business interruption caused by the user.
  • FIG. 3 is a flowchart of an active/standby switchover method between communication devices according to Embodiment 3 of the present invention.
  • the execution subject of this embodiment may be a service requesting device connected to the primary communication device.
  • the method provided in this embodiment includes:
  • Step 31 Reporting the support capability information of the service requesting device to the primary communication device; the support capability information is used to indicate that the service requesting device supports the primary and secondary address pairs.
  • Step 32 Receive the primary and secondary address pairs sent by the primary communication device; the primary and secondary address pairs include: a primary signaling interaction interface address of the primary communication device and a standby signaling interaction sigma address of the standby communication device .
  • Step 33 Point the signaling communication pointer of the service requesting device to the primary signaling interaction interface address, and when receiving the primary/standby switching indication sent by the standby communication device, the signaling communication pointer is The primary signaling interaction interface address is switched to the standby signaling interaction interface address.
  • the method further includes: detecting a link status between the service requesting device and the primary communication device; detecting the service requesting device When the link between the primary communication device and the primary communication device fails, the active/standby switching request is sent to the standby communication device for requesting the standby communication device to perform the active/standby switchover.
  • the method further includes: receiving a link test indication sent by the backup communication device, and testing the service request device and the device according to the link test indication Describe the link status between the primary communication devices; send the link test result to the standby communication device.
  • the service requesting device supports the master/slave address pair
  • the capability information of the master/slave address pair is reported to the master/slave communication device, and the master/slave address pair is received, and the master/slave switchover indication is received. And switching the signaling communication pointer from the primary signaling interaction interface address to the standby signaling interaction interface address.
  • the service request packet may be filtered out, and the service requesting device may point to the signaling communication pointer.
  • the primary signaling interface address is received, and the first service packet from the address of the standby signaling interface is received, the first service packet is discarded; and/or the service requesting device is in the signaling
  • the communication pointer points to the address of the standby signaling interaction interface and receives the second service packet from the address of the primary signaling interaction interface, the second service packet is discarded.
  • the service requesting device can filter out the service packets related to the address that the signaling communication pointer does not point to. Therefore, the probability of the service requesting device being abnormal is reduced, thereby reducing the probability of user service interruption.
  • the active/standby communication device may be a packet gateway with high reliability requirements in the communication system; the service requesting device may be a service support node connected to the packet gateway, and the like.
  • the following is a general wireless packet service/General Mobile Radio Service (General Packet Radio Service)
  • the application scenario of the active/standby switchover of the Gateway GPRS Support Node (GGSN) in the networking of the GPRS/UMTS (referred to as GPRS/UMTS for short) is taken as an example to describe the technical solution of the embodiment of the present invention. It should be noted that the following application scenarios are not to be construed as limiting the technical scope of the present invention.
  • the service requesting device in the application scenario is: a Serving GPRS Support Node (SGSN).
  • SGSN Serving GPRS Support Node
  • FIG. 4 is a schematic structural diagram of a networking of an application scenario according to an embodiment of the present invention.
  • the two GGSNs are mutually active and active: the primary GGSN and the standby GGSN; and the SGSNs in the home network, such as SGSN1, SGSN2, and SGSN3, are interconnected through the entire IP backbone network.
  • the SGSN is a service requesting device relative to the GGSN
  • the GGSN is a service providing device with respect to the SGSN. It can be understood that the service requesting device and the service providing device are relative concepts of different network status.
  • the networking shown in Figure 4 is simple, easy to deploy and maintain, and easy to implement.
  • FIG. 5 is a schematic diagram of a communication model of a GGSN in an application scenario according to an embodiment of the present invention.
  • the communication model of the GGSN includes two communication planes: the control plane and the user plane.
  • the control plane includes: a control plane input interface unit (abbreviated as: In-c), a Gn interface control plane unit (abbreviated as: Gn-c), and a Gi interface control plane unit (abbreviated as: Gi-c) And the control plane out interface unit (abbreviated as: Out-c).
  • In-c control plane input interface unit
  • Gn-c Gn interface control plane unit
  • Gi-c Gi interface control plane unit
  • Out-c the control plane out interface unit
  • the user plane includes: a user interface interface unit (denoted as: abbreviated as: In-u), a Gn interface user plane unit (abbreviated as: Gn-u), and a Gi interface user plane unit (abbreviated as: Gi-u ) and the user interface interface unit (abbreviated as: Out-u ).
  • a user interface interface unit denoted as: abbreviated as: In-u
  • Gn-u Gn interface user plane unit
  • Gi-u Gi interface user plane unit
  • Out-u the user interface interface unit
  • each module of the GGSN control plane and the user plane has its own independent IP address, which is related to
  • FIG. 6 is a schematic diagram of an IP address corresponding to an active/standby GGSN control plane module according to an embodiment of the present disclosure
  • FIG. 7 is a primary and a backup provided by an embodiment of the present invention.
  • the IP address correspondence of the GGSN user plane module is improved.
  • the primary and secondary GGSNs control the IP address correspondence of the modules to be equal to: the primary control plane inbound interface unit and the standby control plane inbound interface unit, each with its own independent IP address: IP-In-c(a) And IP-In-c(s); the primary Gn interface control plane unit and the standby Gn interface control plane unit have their own independent IP addresses and share the first floating IP address: IP-Gn-c(a), IP- Gn-c(s) and IP-Gn-c(c), where IP-Gn-c(a) can also be expressed as GTP-C(a), which is the signaling interaction interface address of the primary GGSN and the SGSN, ie The address of the primary signaling interaction interface in the embodiment of the present invention; IP-Gn-c(s) can also be expressed as: GTP-C(s), which is the signaling interaction interface address of the GGSN and the SGSN, that is, the implementation of the present invention The standby signaling interface address as described in the example;
  • the IP address corresponding to the modules of the active and standby GGSN users is:
  • the primary user inbound interface unit and the secondary user inbound interface unit have their own independent IP addresses: IP-In-u(a) And the IP-In-u(s);
  • the primary Gn interface user plane unit and the standby Gn interface user plane unit share the third floating IP address: IP-Gn-u(c);
  • the user plane unit shares the fourth floating IP address: IP-pool-Gi-u(c);
  • the primary user interface interface unit and the standby user interface interface unit have their own independent IP addresses: IP-Out-u (a ) and IP-Out-u(s).
  • the mechanism for performing hot backup between devices in the application scenario of the embodiment of the present invention is as follows:
  • FIG. 8 is an interaction diagram of performing hot backup of the active and standby GGSNs in the application scenario according to the embodiment of the present invention. As shown in Figure 8, the methods for performing hot backup between devices by the active and standby GGSNs include:
  • Step 81 The heartbeat detection message is sent between the primary GGSN and the standby GGSN to detect whether the other party has a fault.
  • Heartbeat is a periodic signal.
  • the communication device at one end sends a heartbeat to the peer communication device, if the peer communication device works normally, it will return a heartbeat response to it.
  • the heartbeat detection message may be used to detect whether the primary and secondary GGSNs are faulty.
  • Step 82 The primary GGSN sends batch backup information to the standby GGSN.
  • the primary GGSN may send batch backup information to the standby GGSN periodically or when the preset conditions are met.
  • the backup information may include: Packet Data Protocol (PDP) context information, such as General Packet Radio Service (GPRS) transport protocol (GPRS Tunneling Protocol, GTP) information, quality of service ( Quality of Service (QoS), Policy and Charging Control (PCC) rules, etc.; routing information; Virtual Private Network (VPN) information, such as IPSec/IKE VPN, L2TP VPN, etc. Firewall policy, Network Address Translation (NAT) information, etc.
  • PDP Packet Data Protocol
  • GTP General Packet Radio Service
  • QoS Quality of Service
  • PCC Policy and Charging Control
  • VPN Virtual Private Network
  • the primary GGSN may send the backup GGSN two changes to the backup information during the backup.
  • Step 83 The GGSN starts the pre-processing process, and the modules of the GGSN are in the standby state before the active/standby switchover.
  • the GGSN starts the pre-processing process, that is, synchronizes the backup information sent by the primary GGSN to each peer module on the standby GGSN.
  • the standby GGSN receives the change content of the backup information during the two backups sent by the primary GGSN, and corresponds the changes to the peer module of the standby GGSN as shown in FIG. 6 and FIG. 7.
  • the GGSN After the GGSN completes the pre-processing process, it enters the standby state of the active/standby switchover, that is, it notifies the modules on the GGSN to create an instance, and stores related parameter information of the service to be taken over, but does not send packets.
  • the modules on the standby GGSN receive the active/standby switchover indication, the packets can be sent out immediately to implement the fast takeover of the primary GGSN service.
  • the method for performing the hot backup between the devices in the embodiment of the present invention is not limited.
  • the method shown in FIG. 8 is only an example, and should not be construed as limiting the technical solutions of the embodiments of the present invention.
  • the support capability of the SGSN may be different. For example, some SGSNs support the primary and secondary address pairs of the active and standby GGSNs, and some SGSNs do not support the primary and secondary address pairs of the active and standby GGSNs.
  • the master-slave address pair of the active and standby GGSNs is specifically: GTP-C address of the primary GGSN: GTP-C(a), and GTP-C address of the standby GGSN: GTP-C(s).
  • GTP-C address of the primary GGSN GTP-C(a)
  • GTP-C address of the standby GGSN GTP-C(s)
  • the embodiment of the present invention can deploy the SGSN that supports the primary and secondary address pair capabilities of the active and standby GGSNs in the home network; and deploy the masters that do not support the active and standby GGSNs in the roaming network.
  • the address-to-capability SGSN may also be deployed in the home network.
  • the SGSN support capability information may be pre-registered on the primary GGSN and/or the standby GGSN, or may be reported to the primary GGSN by the SGSN and synchronized by the primary GGSN to the standby GGSN.
  • FIG. 9 is an interaction diagram of an SGSN support capability information reporting method according to Embodiment 4 of the present invention. As shown in Figure 9, the SGSN support capability information reporting method includes:
  • Step 91 The SGSN sends a Create PDP Context Request message to the primary GGSN, where the PDP context request message carries the SGSN support capability information, where the support capability information is used to indicate that the SGSN supports the GTP control plane of the active and standby GGSNs.
  • the address pair (Support active & hot-standby CTP-C) supports the active and standby GTP-C address pairs.
  • the PDP Context Request message in this step is an extended Gn interface message, that is, the first active/standby switchover request according to the embodiment of the present invention.
  • the SGSN can report its own support capability information to the primary GGSN through the PDP context request message.
  • the primary GGSN may synchronize the information with the standby GGSN.
  • Step 92 The primary GGSN sends a Create PDP Context Response message to the SGSN, where the PDP context response message carries the GTP-C address pair of the active and standby GGSNs (CTP-C(a), CTP-C(s) )).
  • the master GGSN learns that the SGSN supports the GTP-C address pair of the active and standby GGSNs according to the received PDP context request message that carries the SGSN support capability information, and therefore carries the GTP-C address pair of the active and standby GGSNs in the PDP context response message. And sent to the SGSN.
  • Step 93 The SGSN receives a Create PDP Context Response message, and saves the GTP-C address pair (CTP-C(a), CTP-C(s)) of the active and standby GGSNs carried in the message, and The signaling communication pointer of the SGSN points to the GTP-C address of the primary GGSN: CTP-C(a).
  • the SGSN when acquiring the GTP-C address pair (CTP-C(a), CTP-C(s)) of the active and standby GGSNs, the SGSN points the signaling communication pointer to the GTP-C address of the primary GGSN: CTP- C(a).
  • the advantage of this processing is that when the active and standby GGSN "double live" phenomenon has occurred in the communication system, since the signaling communication pointer of the SGSN points to the GTP-C address of the primary GGSN: CTP-C(a), the SGSN can In the received packet, the GTP-C address including the address of the standby GGSN is filtered out: the service-related packet except the link test indication and the active/standby switchover indication of the CTP-C(s), that is, the included address is filtered.
  • the service packet of the CTP-C(s) reduces the probability of the SGSN being judged abnormally, thereby reducing the probability of user service interruption.
  • the primary GGSN needs to report its own support capability information, and the first floating IP address shared by the active and standby Gn interface control planes of the active and standby GGSNs is used to perform signaling interaction with the active and standby GGSNs.
  • the embodiment of the present invention further introduces a consistency switching mechanism, that is, a module is determined in each module on the standby GGSN as a trigger point for the active/standby switchover, and a switching instruction is issued by the The modules on the standby GGSN perform the active/standby switchover at the same time. That is, the consistency switchover is performed.
  • a consistency switching mechanism that is, a module is determined in each module on the standby GGSN as a trigger point for the active/standby switchover, and a switching instruction is issued by the The modules on the standby GGSN perform the active/standby switchover at the same time. That is, the consistency switchover is performed.
  • FIG. 10 is a schematic diagram of a method for performing active/standby consistency switching according to Embodiment 5 of the present invention.
  • the Gn-c(s) module on the GGSN is the trigger point for the active/standby switchover.
  • the Gn-c(s) module sends a consistent switching indication to other modules on the standby GGSN; the consistent switching indication is used to trigger each module on the standby GGSN, and the primary GGSN is started. The takeover of the services provided by each peer module.
  • Each module on the GGSN preempts the shared resources occupied by the primary GGSN peer module to take over the services provided by the primary GGSN peer module.
  • the In-c(s) module refreshes the route of the In-c(a) module by means of a broadcast message
  • the Gn-c(s) module preempts itself and shares with the Gn-c(a) module.
  • the first floating address, the Gi-c(s) module preempts itself with the second floating IP address shared by the Gi-c(a) module, and the Out-c(s) module refreshes the Out-c by broadcasting messages, etc. )
  • the routing of the module is described by the Gi-c(s) module.
  • the In-u(s) module refreshes the route of the In-u(a) module by means of a broadcast message, and the Gn-u(s) module preempts itself and the third shared by the Gn-u(a) module.
  • the Gi-u(s) module preempts the fourth floating IP address shared by itself with the Gi-u(a) module
  • the Out-u(s) module refreshes the Out-u(a) module by means of broadcast messages. routing. If the shared resource is occupied by the primary GGSN peer module, the primary GGSN peer module releases the corresponding resource when each module on the standby GGSN preempts the shared resource.
  • the synchronous switching mechanism is implemented to complete the synchronous switching of the modules on the active and standby GGSNs, so that some modules on the active and standby GGSNs have been switched, and some modules are not.
  • the network anomaly caused by the active/standby switchover is beneficial to reduce the probability of user service interruption caused by these network abnormalities.
  • FIG. 11 is a schematic diagram of a module for collecting a fault state by a primary GGSN according to an embodiment of the present invention.
  • the Gn-c(a) module in the primary GGSN can be used as a collection module of a fault state, and the module collects various faults related to the primary GGSN, such as physical interface faults, link faults, and Module failure, etc.
  • the main GGSN collects its own related faults, it can perform an overall evaluation based on the collected fault information to determine whether to perform an active/standby switchover.
  • the primary GGSN can collect and collect fault status.
  • the fault types can include: physical interface fault, Link failure and device module failure.
  • the primary GGSN may also preset a capacity loss threshold and a service loss threshold according to actual needs, where the capacity loss is a loss indicating a configuration amount, and the service loss indicates a change amount of the traffic volume before and after the fault.
  • the corresponding threshold can be set according to the redundant configuration amount of the operator network planning and the service traffic of the network statistics. For example: preset the first capacity loss threshold x% and the second capacity loss threshold w%, and 0 ⁇ X% ⁇ W% ⁇ 1; preset the first service loss threshold % and the second service loss threshold v %, and 0 ⁇ y% ⁇ % ⁇ 1.
  • the primary GGSN may further determine the conditions in consideration of the fault type, the current capacity loss of the primary GGSN, and the traffic loss, so that the primary GGSN determines the action that needs to be performed according to the decision condition.
  • the primary GGSN may also perform a decision condition corresponding to the "negotiation” and “immediate switchover” actions according to the degree of impact of the collected fault on the service.
  • the pre-set decision conditions are as follows:
  • the first preset condition is: the type of the fault is a physical interface/link failure, and the current capacity loss amount is between a preset first capacity loss threshold and a second capacity loss threshold, that is, [x%, w% ), and the current business loss amount is between the preset first service loss threshold and the second service loss threshold, that is, [y%, v%).
  • the second preset condition is: the type of the fault is a physical interface/link failure, the current capacity loss amount is greater than or equal to the second capacity loss threshold w%, and the current service loss is greater than or equal to the second service loss. Loss value ⁇ %;
  • the third preset condition The type of the fault is a device module fault.
  • the primary GGSN When the fault status information collected by the primary GGSN meets the first preset condition, the primary GGSN performs a "negotiation" action, that is, initiates an active/standby negotiation switching process to the standby GGSN; and the fault status information collected by the primary GGSN satisfies the second preset condition. Or the third preset condition, the primary GGSN performs an "immediate switching" action, that is, the primary GGSN triggers the active/standby switching. It can be seen that the primary communication device can automatically determine whether switching needs to be performed based on the collected fault status and pre-set decision conditions, thereby improving the convenience of system management and maintenance. In the following, the main GGSN triggers the active/standby switchover and the active/standby GGSN negotiation switchover, which are respectively described with reference to the accompanying drawings.
  • FIG. 12 is an interaction diagram of a method for performing a switching negotiation between an active and standby GGSN according to Embodiment 6 of the present invention. As shown in Figure 12, the method for performing the switching negotiation between the active and standby GGSNs includes:
  • Step 121 The primary GGSN determines that the active/standby switchover needs to be performed according to the fault state information.
  • the way the primary GGSN collects its own fault status information is not limited.
  • the Gn-c(a) module is used as a collection module of the fault state to collect fault status information.
  • the master GGSN determines to perform the "negotiation" action.
  • Step 122 The primary GGSN sends a Switch Negotiation Request to the standby GGSN to request the standby GGSN to determine whether to perform an active/standby switchover.
  • the Switch Negotiation Request carries a Failure Report.
  • the fault report includes: the current capacity loss (Capacity Loss) and the service loss (Service Loss) of the primary GGSN.
  • Step 123 The GGSN determines the expected loss of the service after the switching, and compares the expected loss of the service with the current capacity loss and the service loss in the fault report to determine whether to agree to perform the active/standby switchover.
  • the standby GGSN can determine the expected loss of its own business after the switching, combined with the current capacity loss and service loss of the primary GGSN in the fault report, and the local state, capacity, and load status of the standby GGSN.
  • the expected loss of the business, and the current capacity loss and business loss in the fault report Compare. If the expected loss of the service is less than the current capacity loss and service loss of the primary GGSN, the master/slave switchover is agreed; otherwise, the master/slave switchover is refused.
  • Step 124 The GGSN sends a Switch Negotiation Response to the primary GGSN to notify the primary GGSN whether to agree to perform the active/standby switchover.
  • the Reject parameter is carried in the active/standby switchover negotiation response, and the available capacity (Capacity available) information and the reject cause (Cause) of the standby GGSN are carried;
  • Step 125a-Step 126 is performed.
  • Steps 125a-125c The standby GGSN sends an active/standby switchover indication (Switch) to the SGSN1, the SGSN2, and the SGSN3, respectively.
  • the indication may carry the active and standby GTP-C address pairs (GTP-C(a), GTP-C(s). )), for respectively instructing SGSN1, SGSN2 and SGSN3 to switch their signaling communication pointers from GTP-C(a) to GTP-C(s).
  • Step 126 The standby GGSN takes over the service provided by the primary GGSN.
  • the primary GGSN introduces an active/standby switchover negotiation mechanism:
  • the primary GGSN sends the current capacity loss and service loss of the primary GGSN to the backup when it determines that it is necessary to perform the active/standby switchover according to the collected fault state information.
  • the GGSN is evaluated by the standby GGSN in conjunction with the local status, capacity, and load conditions to determine whether to accept the negotiation for the active/standby switchover. It can be seen that, in this embodiment, the switching is performed based on the active/standby switching negotiation mechanism, which can avoid the loss of the GGSN takeover capability and cause more loss to the user, which is beneficial to reducing the probability of user service interruption caused by the active/standby switching discomfort.
  • the modules on the GGSN can perform the active/standby switchover at the same time, that is, perform the consistent switchover.
  • the detailed description of the implementation method and the effect is shown in the corresponding description of the corresponding embodiment in FIG. 10, and details are not described herein again. .
  • FIG. 13 is a schematic structural diagram of a communication device according to Embodiment 7 of the present invention.
  • the communication device provided in this embodiment includes: a negotiation failure information obtaining module 131, an expected loss amount determining module 132, a switching evaluation module 133, an active/standby switching indication module 134, and a switching execution module 135.
  • the manner of acquiring fault information such as the traffic load and the current loss amount of the main communication device is not limited.
  • the negotiation fault information obtaining module 131 may be configured to receive an active/standby switching negotiation request that is sent by the primary communications device and that carries the fault information, where the fault information includes: the primary communications device Business load and current loss.
  • the expected loss determination module 132 can be configured to determine the amount of expected traffic loss after the handover according to the local state, capacity, and load conditions of the communication device, and the traffic load of the primary communication device.
  • the reverse evaluation module 133 can be used in the When the expected loss of the service is less than the current loss, it is determined that an active/standby switchover is required.
  • the active/standby switch indication module 134 is configured to send a primary/standby switchover indication to the service requesting device, where the active/standby switchover indication is used to indicate that the service requesting device sends its signaling communication pointer by the primary signaling interaction of the primary communication device.
  • the interface address is switched to the alternate signaling interaction interface address of the communication device.
  • the switching execution module 135 can be used to take over the services provided by the primary communication device.
  • the service requesting device When the communication device provided by the present invention sends an active/standby switching indication to the service requesting device, the service requesting device is instructed to switch its signaling communication pointer from the primary signaling interaction interface address to the standby signaling interaction interface address; thus, in the communication system
  • the active/standby communication device is dual-active, it is beneficial for the service requesting device to filter out the service packets related to the address that the signaling communication pointer does not point to, thereby reducing the probability that the service requesting device will determine the abnormality, thereby reducing the probability.
  • the device type of the communication device provided by the embodiment of the present invention is not limited, such as a packet gateway device that can be specifically used for backup between devices.
  • the working mechanism can be seen in FIG. 1 , FIG. 4 to FIG. 12 . Corresponding descriptions of the standby communication device or the standby GGSN in the embodiment are not described herein again.
  • FIG. 14 is a schematic structural diagram of a communication device according to Embodiment 8 of the present invention.
  • the communication device provided in this embodiment includes: a capability information acquiring module 141 and an address indicating module 142.
  • the capability information obtaining module 141 is configured to obtain the support capability information of the service requesting device that is connected to the primary communication device, where the support capability information is used to indicate that the service requesting device supports the primary and secondary address pairs; The primary signaling interaction interface address of the primary communication device and the standby signaling interaction interface address of the secondary communication device.
  • the address indication module 142 is configured to send the primary and secondary address pairs to the service requesting device, and instruct the service requesting device to point its signaling communication pointer to the primary signaling interaction interface address.
  • the communications device provided in this embodiment may further include: a fault information collecting module 143, a switch negotiation requesting module 144, and a negotiation response obtaining module 145.
  • the fault information collection module 143 can be configured to obtain fault information, where the fault information includes: a type of fault that has occurred related to the primary communication device, a capacity loss amount, and a service loss amount.
  • the switching negotiation requesting module 144 is configured to: when the fault information meets the first preset condition, send an active/standby switching negotiation request including the fault information to the standby communication device corresponding to the primary communications device;
  • the condition includes: the type of the fault is a physical interface/link fault, and the capacity loss amount is between a preset first capacity loss threshold and a second capacity loss threshold, where the service loss is preset Between the first business loss threshold and the second business loss threshold.
  • the negotiation response obtaining module 145 is configured to receive an active/standby switching negotiation response sent by the standby communication device, and take over by the standby communication device when the active/standby switching negotiation response indicates that the standby communication device agrees to perform an active/standby switching Carrying the services provided by the communication device.
  • the communications device provided in this embodiment may further include: a switching request module 146, and/or an alerting module 147.
  • the switching requesting module 146 is configured to send an active/standby switching request to the standby communication device when the fault information meets the second preset condition or the third preset condition, where the active/standby switching request is used to trigger the
  • the standby communication device initiates an active/standby switchover;
  • the second preset condition includes: the type of the fault is a physical interface/link failure, the capacity loss amount is greater than or equal to the second capacity loss threshold, and the service is The amount of loss is greater than or equal to the second service loss threshold;
  • the third preset condition includes: the type of the fault is a device module fault.
  • the alarm module 147 is configured to output alarm prompt information when the fault information indicates that an existing fault has occurred.
  • the primary communication device learns the support capability information of the service requesting device, it sends a primary and secondary address pair to the service requesting device, and instructs the service requesting device to point its signaling communication pointer to the primary signaling interaction interface address, thereby
  • the service message related to the address that the signaling communication pointer does not point to can be filtered out, thereby reducing the probability that the service requesting device is abnormally determined, thereby reducing the probability
  • the communication device of the present embodiment can also perform switching based on the active/standby switching negotiation mechanism, thereby avoiding more loss to the user due to limited takeover capability of the standby communication device after the switching, and further
  • the device type of the communication device in this embodiment is not limited, and may be specifically a packet gateway device.
  • the working mechanism can be seen in the embodiment of FIG. 2, FIG. 4 to FIG. The corresponding description of the
  • FIG. 15 is a schematic structural diagram of a service requesting device according to Embodiment 9 of the present invention.
  • the service requesting device provided in this embodiment includes: a capability information reporting module 151, an address information obtaining module 152, and a communication pointer processing module 153.
  • the capability information reporting module 151 is configured to report the support capability information of the service requesting device to the primary communication device, where the support capability information is used to indicate that the service request device supports the primary and secondary address pairs, where the primary and secondary address pairs include: The primary signaling interaction interface address of the primary communication device and the standby signaling interaction interface address of the standby communication device.
  • the address information obtaining module 152 is configured to receive the primary and secondary address pairs sent by the primary communication device.
  • the communication pointer processing module 153 is configured to point the signaling communication pointer of the service requesting device to the address of the primary signaling interaction interface, and when the primary/standby switching indication sent by the standby communication device is received, the The communication pointer is switched from the address of the primary signaling interaction interface to the address of the standby signaling interaction interface.
  • the service requesting device may further include: a first service packet discarding module 154, and/or a second service packet discarding module 155.
  • the first service packet discarding module 154 can be configured to point to the main signaling at the signaling communication pointer When the interface address is received, and the first service packet is received from the address of the standby signaling interface, the first service packet is discarded.
  • the second service packet discarding module 155 can be configured to discard the signaling communication pointer when it points to the standby signaling interaction interface address and receives the second service packet from the primary signaling interaction interface address. The second service packet.
  • the service requesting device supports the master/slave address pair
  • the capability information of the master/slave address pair is reported to the master/slave communication device, and the master/slave address pair is received, and the master/slave switchover indication is received.
  • the device type of the communication device in this embodiment is not limited, and may be specifically a service request device connected to the packet gateway device.
  • a service request device connected to the packet gateway device.
  • FIG. 3 For the specific implementation mechanism, refer to FIG. 3, FIG. 4 to FIG. 12 for the service request device or The corresponding records of the SGSN are not described here.
  • FIG. 16 is a schematic structural diagram of a communication device according to Embodiment 10 of the present invention.
  • the communication system provided in this embodiment includes: a primary communication device 161, a backup communication device 162, and a service requesting device 163.
  • the service requesting device 163 is communicably connected to the primary communication device 161 and the standby communication device 162, respectively, and the number of the service requesting devices 163 may be one or more, and the case where the plurality of service requesting devices 163 are included in the communication system is shown in FIG. .
  • the structure of the main communication device refer to the corresponding description of the corresponding embodiment of FIG. 14.
  • the working mechanism can be referred to the corresponding description of the main communication device or the main GGSN in the embodiment of FIG.
  • FIG. 13 corresponds to the corresponding description of the embodiment, and the working mechanism thereof can be referred to the corresponding description of the standby communication device or the standby GGSN in the embodiment of FIG. 1 and FIG. 4 to FIG. 12; the structure of the service requesting device can be referred to the corresponding embodiment of FIG.
  • the working mechanism refer to the corresponding descriptions about the service requesting device or the SGSN in the embodiment of FIG. 3 and FIG. 4 to FIG. 12, and details are not described herein again.
  • the communication system provided in this embodiment has a simple structure, is easy to deploy and maintain, and is easy to implement. It will be understood by those of ordinary skill in the art that the drawings are only a schematic representation of one embodiment, and the modules or processes in the drawings are not necessarily required to practice the invention.
  • modules in the apparatus in the embodiments may be distributed in the apparatus of the embodiment according to the embodiment, or may be correspondingly changed in one or more apparatuses different from the embodiment.
  • the modules of the above embodiments may be combined into one module, or may be further split into a plurality of sub-modules.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Hardware Redundancy (AREA)
  • Telephonic Communication Services (AREA)

Description

通信设备间的主备倒换方法、 通信设备和***及服务请求设备 技术领域
本发明涉及通信技术领域，特别是涉及一种通信设备间的主备倒换方法、 通信设备和***及服务请求设备。 背景技术
随着移动互联网的蓬勃发展， 越来越多的人们通过智能终端享受着移动 互联网提供的各种业务， 如： 网页浏览、 VoIP ( Voice over Internet Protocol )、 视频、 社交网络、 即时通讯等。 分组网关设备在用户上网的时候提供了一系 列重要的服务， 如： 为终端分配 IP地址、 鉴权、 计费、 业务控制等。 由于分 组网关设备及其他类型的通信设备， 位于重要的网络位置及其具有服务于大 量用户的能力， 通信***对这些设备的可靠性要求很高。
为了在发生故障时， 主网关设备正在服务的用户业务不中断以减小其业 务损失， 需要有一个实时备网关设备能够迅速接管主网关设备的业务。 现有 技术釆用在主备网关设备之间建立备份同步通道和心跳消息通道。 其中， 备 份同步通道用于进行主备网关设备之间进行数据热备， 心跳消息通道用于检 测故障。 当备网关设备根据心跳检测结果推测主设备发生故障时， 主备网关 设备之间则进行主备倒换，即由备网关设备接管承载主网关设备提供的业务。 如果备网关设备的推测结果不正确， 即主网关设备实际没有发生故障， 则通 信***中会出现主备网关设备抢用共享资源提供承载， 该现象称为 "双活 "现 发明人在实践现有技术的过程中发现： "双活 "现象会造成网络行为异常， 如地址冲突、 路由冲突等， 从而引发网关设备的周边网元判决异常， 如无法 正确判断， 报文的源地址或目标地址究竟指向的是主网关设备还是备网关设 备， 因而周边网元可能去活大量在线用户， 造成用户业务中断， 增加了用户 的业务损失。 发明内容
本发明实施例提供一种通信设备间的主备倒换方法、 通信设备和***及 服务请求设备， 用以降低通信设备间进行主备倒换时用户业务中断的几率。
本发明实施例提供了一种通信设备间的主备倒换方法， 包括：
接收主通信设备发送的、 携带有故障信息的主备倒换协商请求， 所述故 障信息包括： 所述主通信设备的业务负载和当前损失量；
根据备通信设备的本机状态、 容量和负载情况， 以及所述主通信设备的 业务负载， 确定倒换后的业务预期损失量， 并在所述业务预期损失量小于所 述当前损失量时， 确定需要进行主备倒换；
向服务请求设备发送主备倒换指示； 所述主备倒换指示用于指示所述服 务请求设备将其信令通讯指针， 由所述主通信设备的主信令交互接口地址切 换到所述备通信设备的备信令交互接口地址；
接管承载所述主通信设备提供的业务。
本发明实施例还提供了另一种通信设备间的主备倒换方法， 包括： 获取与主通信设备连接的服务请求设备的支持能力信息， 所述支持能力 信息用于表示所述服务请求设备支持主备地址对； 所述主备地址对包括： 所 述主通信设备的主信令交互接口地址、 以及备通信设备的备信令交互接口地 址；
向所述服务请求设备发送所述主备地址对， 并指示所述服务请求设备将 其信令通讯指针指向所述主信令交互接口地址。
本发明实施例还提供了又一种通信设备间的主备倒换方法， 包括： 向主通信设备上报服务请求设备的支持能力信息； 所述支持能力信息用 于表示所述服务请求设备支持主备地址对；
接收所述主通信设备发送的所述主备地址对， 所述主备地址对包括： 所 述主通信设备的主信令交互接口地址和备通信设备的备信令交互接口地址； 将所述服务请求设备的信令通讯指针， 指向所述主信令交互接口地址， 且在接收到所述备通信设备发送的主备倒换指示时， 将所述信令通讯指针由 所述主信令交互接口地址， 切换到所述备信令交互接口地址。
本发明实施例还提供了一种通信设备， 包括：
协商故障信息获取模块， 用于接收主通信设备发送的、 携带有故障信息 的主备倒换协商请求， 所述故障信息包括： 所述主通信设备的业务负载和当 前损失量；
预期损失量确定模块， 用于根据所述通信设备的本机状态、 容量和负载 情况， 以及所述主通信设备的业务负载， 确定倒换后的业务预期损失量； 倒换评估模块， 用于在所述业务预期损失量小于所述当前损失量时， 确 定需要进行主备倒换； 主备倒换指示模块， 用于向服务请求设备发送主备倒 换指示； 所述主备倒换指示用于指示所述服务请求设备将其信令通讯指针， 由所述主通信设备的主信令交互接口地址切换到所述通信设备的备信令交互 接 σ地址；
倒换执行模块， 用于接管承载所述主通信设备提供的业务。
本发明实施例还提供了另一种通信设备， 包括：
能力信息获取模块， 用于获取与主通信设备连接的服务请求设备的支持 能力信息， 所述支持能力信息用于表示所述服务请求设备支持主备地址对； 所述主备地址对包括： 所述主通信设备的主信令交互接口地址、 以及备通信 设备的备信令交互接口地址；
地址指示模块， 用于向所述服务请求设备发送所述主备地址对， 并指示 所述服务请求设备将其信令通讯指针指向所述主信令交互接口地址。
本发明实施例还提供了一种服务请求设备， 包括：
能力信息上报模块， 用于向主通信设备上报所述服务请求设备的支持能 力信息； 所述支持能力信息用于表示所述服务请求设备支持主备地址对， 所 述主备地址对包括： 所述主通信设备的主信令交互接口地址和备通信设备的 备信令交互接口地址；
地址信息获取模块， 用于接收所述主通信设备发送的所述主备地址对； 通讯指针处理模块， 用于将所述服务请求设备的信令通讯指针， 指向所 述主信令交互接口地址，且在接收到所述备通信设备发送的主备倒换指示时， 将所述信令通讯指针由所述主信令交互接口地址， 切换到所述备信令交互接 σ地址。
本发明实施例还提供了一种通信***， 包括： 主通信设备， 与所述主通 信设备通信连接的备通信设备， 以及分别与所述主通信设备和所述备通信设 备通信连接的服务请求设备。
本发明实施例中， 当备通信设备进行主备倒换时， 服务请求设备将其信 令通讯指针由主信令交互接口地址， 切换到备信令交互接口地址； 从而在当 通信***中已经出现主备通信设备"双活"现象时， 有利于服务请求设备过滤 掉信令通讯指针没有指向的地址相关的业务报文， 从而降低服务请求设备发 生判断异常的几率， 也就因而降低了用户业务中断的几率。 附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案， 下面将对实 施例或现有技术描述中所需要使用的附图作简单地介绍， 显而易见地， 下面 描述中的附图仅仅是本发明的一些实施例， 对于本领域普通技术人员来讲， 在不付出创造性劳动性的前提下， 还可以根据这些附图获得其他的附图。
图 1为本发明实施例一提供的通信设备间的主备倒换方法流程图； 图 2为本发明实施例二提供的通信设备间的主备倒换方法流程图； 图 3为本发明实施例三提供的通信设备间的主备倒换方法流程图； 图 4为本发明实施例应用场景的组网结构示意图；
图 5为本发明实施例应用场景中 GGSN的通讯模型示意图； 图 6为本发明实施例提供的主备 GGSN控制面模块的 IP地址对应关系； 图 7为本发明实施例提供的主备 GGSN用户面模块的 IP地址对应关系； 图 8为本发明实施例应用场景中进行主备 GGSN热备份的交互图； 图 9为本发明实施例四提供的 SGSN支持能力信息上报方法的交互图； 图 10为本发明实施例五提供的主备一致性倒换的方法示意图；
图 11为本发明实施例提供的主 GGSN集中收集故障状态的模块示意图; 图 12为本发明实施例六提供的主备 GGSN进行倒换协商方法的交互图; 图 13为本发明实施例七提供的通信设备的结构示意图；
图 14为本发明实施例八提供的通信设备的结构示意图；
图 15为本发明实施例九提供的服务请求设备的结构示意图；
图 16为本发明实施例十提供的通信设备的结构示意图。 具体实施方式
下面将结合本发明实施例中的附图， 对本发明实施例中的技术方案进行 清楚、 完整地描述， 显然， 所描述的实施例仅仅是本发明一部分实施例， 而 不是全部的实施例。 基于本发明中的实施例， 本领域普通技术人员在没有付 出创造性劳动前提下所获得的所有其他实施例， 都属于本发明保护的范围。
本发明以下实施例的序号仅仅为了描述， 不代表实施例的优劣。
图 1为本发明实施例一提供的通信设备间的主备倒换方法流程图。 本实 施例的执行主体可为： 某一主通信设备对应的备通信设备。 如图 1所示， 本 实施例提供的方法包括：
步骤 11 : 接收主通信设备发送的、携带有故障信息的主备倒换协商请求， 所述故障信息包括： 所述主通信设备的业务负载和当前损失量。
主通信设备的故障信息的获取方式也不受限制， 例如： 备通信设备可通 过接收主通信设备发送、 携带有上述故障信息的主备倒换协商请求的方式， 获取主通信设备的故障信息。 步骤 12: 根据备通信设备的本机状态、 容量和负载情况， 以及所述主通 信设备的业务负载， 确定倒换后的业务预期损失量， 并在所述业务预期损失 量小于所述当前损失量时， 确定需要进行主备倒换。
步骤 13 : 向服务请求设备发送主备倒换指示； 所述主备倒换指示用于指 示所述服务请求设备将其信令通讯指针， 由所述主通信设备的主信令交互接 口地址切换到所述备通信设备的备信令交互接口地址。
本步骤中的服务请求设备具有主备地址对的支持能力， 即支持釆用主备 通信设备各自对立的信令交互接口地址， 分别与主通信设备交互。 例如： 信 令交互接口地址可具体为： 主通信设备和备通信设备具有独立的、 用于信令 交互的 IP地址， 不妨称为主 IP地址和备 IP地址。服务请求设备则支持釆用主 IP 地址与主通信设备交互信令， 也支持釆用备 IP地址与备通信设备交互信令。
备通信设备获取服务请求设备的支持能力信息的方式不受限制， 如可预 先配置在主备通信设备上， 也可由主通信设备获取并将该支持能力信息同步 到备通信设备。
步骤 14: 接管承载所述主通信设备提供的业务。
在主备倒换过程中， 备用通信设备抢占主备通信设备的共享资源， 并对 主通信设备提供的业务提供承载， 以使主通信设备服务的用户业务不中断。
当备通信设备进行主备倒换时， 可确定备通信设备上的任一模块作为主 备倒换的触发点， 触发备通信设备上的各模块， 分别接管承载主通信设备对 等模块提供的业务。
本实施例中， 当备通信设备向服务请求设备发送主备倒换指示， 指示服 务请求设备将其信令通讯指针由主信令交互接口地址， 切换到备信令交互接 口地址； 从而在当通信***中已经出现主备通信设备"双活，，现象时， 有利于 服务请求设备过滤掉信令通讯指针没有指向的地址相关的业务报文， 从而降 低服务请求设备发生判断异常的几率，也就因而降低了用户业务中断的几率。
图 2为本发明实施例二提供的通信设备间的主备倒换方法流程图。 本实 施例的执行主体为主通信设备。 如图 2所示， 本实施例提供的方法包括： 步骤 21 : 获取与主通信设备连接的服务请求设备的支持能力信息， 所述 支持能力信息用于表示所述服务请求设备支持主备地址对； 所述主备地址对 包括： 所述主通信设备的主信令交互接口地址、 以及备通信设备的备信令交 互接口地址。
主通信设备获取服务请求设备支持能力信息的获取方式不受限制， 如可 预先配置在主通信设备上， 或由服务请求设备主动上报等。 主通信设备可将 该支持能力信息同步到备通信设备上。
步骤 22: 向所述服务请求设备发送所述主备地址对， 并指示所述服务请 求设备将其信令通讯指针指向所述主信令交互接口地址。
可选的， 主通信设备还可获取故障信息， 在所述故障信息满足第一预设 条件时， 向与所述主通信设备对应的备通信设备发送主备倒换协商请求。 其 中， 所述故障信息包括： 归属网中与主通信设备相关的已发生故障的类型、 容量损失量和业务损失量。 所述第一预设条件包括： 所述故障的类型为物理 接口 /链路故障、 所述容量损失量介于预设的第一容量损失阈值和第二容量损 失阔值之间， 所述业务损失量介于预设的第一业务损失阔值和第二业务损失 阔值之间； 所述主备倒换协商请求包括所述故障信息， 用于请求所述备通信 设备确定是否进行主备倒换。 在主通信设备向备通信设备发送主备倒换协商 请求之后， 主通信设备还可接收所述备通信设备发送的主备倒换协商响应， 且在所述主备倒换协商响应表示所述备通信设备同意进行主备倒换时， 由所 述备通信设备接管承载所述主通信设备提供的业务。
可选的， 在所述故障信息满足第二预设条件或第三预设条件时， 向所述 备通信设备发送主备倒换请求， 所述主备倒换请求用于触发所述备通信设备 启动主备倒换； 所述第二预设条件包括： 所述故障的类型为物理接口 /链路故 障、 所述容量损失量大于或等于所述第二容量损失阈值、 且所述业务损失量 大于或等于所述第二业务损失阔值； 所述第三预设条件包括： 所述故障的类 型为设备模块故障。 和 /或， 在所述故障信息表示已有故障发生时， 输出告警 提示信息。
可选的， 主通信设备在检测到自身关键模块发生故障时， 可向所述备通 信设备发送主备倒换请求， 用于请求所述备通信设备进行主备倒换。
本实施例中， 主通信设备在获知服务请求设备的支持能力信息时， 向服 务请求设备发送主备地址对， 并指示服务请求设备将其信令通讯指针指向主 信令交互接口地址， 从而在当通信***中已经出现主备通信设备"双活，，现象 时， 可过滤掉信令通讯指针没有指向的地址相关的业务报文， 从而降低服务 请求设备发生判断异常的几率， 也就因而降低了用户业务中断的几率。 进一 步的， 本实施例还可引入主备倒换的协商机制： 主通信设备根据收集到的故 障状态信息， 自身确定有必要进行主备倒换时， 将主通信设备当前的容量损 失量和业务损失量发送给备通信设备， 由备通信设备确定是否接受协商以进 行主备倒换。 可见， 本实施例基于主备倒换协商机制进行倒换， 可避免倒换 后因备通信设备接管能力受限而给用户造成更大损失， 进而有利于降低因主 备倒换不适造成用户业务中断的几率。
图 3为本发明实施例三提供的通信设备间的主备倒换方法流程图。本实施 例的执行主体可为与主通信设备连接的服务请求设备。 如图 3所示， 本实施例 提供的方法包括：
步骤 31 : 向主通信设备上报服务请求设备的支持能力信息； 所述支持能 力信息用于表示所述服务请求设备支持主备地址对。
步骤 32: 接收所述主通信设备发送的所述主备地址对； 所述主备地址对 包括： 所述主通信设备的主信令交互接口地址和备通信设备的备信令交互接 σ地址。
步骤 33 : 将所述服务请求设备的信令通讯指针， 指向所述主信令交互接 口地址， 且在接收到所述备通信设备发送的主备倒换指示时， 将所述信令通 讯指针由所述主信令交互接口地址， 切换到所述备信令交互接口地址。 在接收所述主通信设备发送的所述主备地址对之后， 所述方法还包括： 检测所述服务请求设备与所述主通信设备之间的链路状况； 在检测到所述服 务请求设备与所述主通信设备之间的链路发生故障时， 向所述备通信设备发 送主备倒换请求， 用于请求所述备通信设备进行主备倒换。
在接收所述主通信设备发送的所述主备地址对之后， 所述方法还包括： 接收所述备通信设备发送的链路测试指示， 根据链路测试指示， 测试所述服 务请求设备与所述主通信设备之间的链路状况； 将链路测试结果发送给所述 备通信设备。
本实施例中， 当服务请求设备支持主备地址对的能力时， 将其支持主备 地址对的能力信息上报给主备通信设备， 接收主备地址对， 并在接收到主备 倒换指示时， 将所述信令通讯指针由所述主信令交互接口地址， 切换到所述 备信令交互接口地址。
本实施例中， 当服务请求设备获取主备地址对之后， 可过滤掉信令通讯 指针没有指向的地址相关的业务报文， 具体可包括： 服务请求设备在所述信 令通讯指针指向所述主信令交互接口地址、 且接收到来自所述备信令交互接 口地址的第一业务报文时， 则丟弃所述第一业务报文； 和 /或， 服务请求设备 在所述信令通讯指针指向所述备信令交互接口地址、 且接收到来自所述主信 令交互接口地址的第二业务报文时， 丟弃所述第二业务报文。
由此可见， 在当通信***中已经出现主备通信设备"双活"现象时， 釆用 本实施例提供的方法， 服务请求设备可过滤掉信令通讯指针没有指向的地址 相关的业务报文， 从而降低服务请求设备发生判断异常的几率， 也就因而降 低了用户业务中断的几率。
本发明实施例中的主备通信设备的类型、 以及与之连接的服务请求设备 类型， 均不受限制。 例如： 主备通信设备可为通信***中可靠性要求高的分 组网关等； 服务请求设备可为与分组网关连接的服务支持节点等。 下面不妨 以通用无线分组业务 /通用移动通信*** （ General Packet Radio Service /Universal Mobile Telecommunications System, 简称 GPRS/UMTS )组网中网关 GPRS支持节点（ Gateway GPRS Support Node , 简称 GGSN )主备倒换的应用 场景为例， 详细说明本发明实施例的技术方案。 需要说明的是， 以下应用场 景不应理解为对本发明技术实质的限制， 该应用场景中的服务请求设备为： GPRS服务支持节点 （ Serving GPRS Support Node, 简称 SGSN ) 。
首先， 说明 GGSN主备倒换的应用场景的组网结构。
图 4为本发明实施例应用场景的组网结构示意图。 如图 4所示的 GPRS/UMTS网络中， 两个 GGSN互为主备： 即主 GGSN和备 GGSN; 与归属 地网络内的 SGSN, 如 SGSN1、 SGSN2和 SGSN3 , 通过 IP骨干网全网互联。 以 SGSN和 GGSN的网络地位来看， SGSN相对 GGSN而言是服务请求设备， GGSN相对 SGSN而言是服务提供设备。 可以理解， 服务请求设备和服务提供 设备是个不同网络地位的相对概念。 如图 4所示的组网结构简单， 便于部署和 维护， 易于实现。
接下来， 举例说明本发明实施例应用场景中的 GGSN的通讯模型。
图 5为本发明实施例应用场景中 GGSN的通讯模型示意图。 如图 5所示， GGSN的通讯模型包括两个通讯平面： 控制面和用户面。 控制面包括： 控制 面入接口单元（缩略表示为： In-c )、 Gn接口控制面单元（缩略表示为： Gn-c )、 Gi接口控制面单元（缩略表示为： Gi-c ) 以及控制面出接口单元 （缩略表示 为： Out-c )。 用户面包括： 用户面入接口单元（表示为： 缩略表示为： In-u )、 Gn接口用户面单元（缩略表示为： Gn-u ) 、 Gi接口用户面单元（缩略表示为： Gi-u ) 以及用户面出接口单元（缩略表示为： Out-u ) 。 控制面和用户面中的 任一单元都可包括多个模块， 具体模块参见图 5。
通常， GGSN控制面和用户面的各模块都拥有各自独立的 IP地址， 与相关
GGSN各对等模块之间的 IP地址对应关系进行改进。 图 6为本发明实施例提供 的主备 GGSN控制面模块的 IP地址对应关系， 图 7为本发明实施例提供的主备 GGSN用户面模块的 IP地址对应关系。
为便于描述技术方案， 不妨将主 GGSN的各模块名称加以"主"字， 其缩略 表示中加以" (a)，，符； 备 GGSN的各模块名称加以"备，，字， 其缩略表示中加以 "(s)，，符； 主备 GGSN共享资源名称的缩略表示中加以 "(c)"符。
如图 6所示， 主备 GGSN控制面对等模块的 IP地址对应关系为： 主控制面 入接口单元和备控制面入接口单元， 拥有各自独立的 IP地址： IP-In-c(a)和 IP-In-c(s); 主 Gn接口控制面单元与备 Gn接口控制面单元， 拥有各自独立的 IP 地址、 且共享第一浮动 IP地址： IP-Gn-c(a)、 IP-Gn-c(s)和 IP-Gn-c(c) , 其中， IP-Gn-c(a)也可表示为 GTP-C(a),是主 GGSN与 SGSN的信令交互接口地址， 即 本发明实施例所述的主信令交互接口地址； IP-Gn-c(s)也可表示为： GTP-C(s) , 是备 GGSN与 SGSN的信令交互接口地址， 即本发明实施例所述 的备信令交互接口地址； 主 Gi接口控制面单元和备 Gi接口控制面单元， 共享 第二浮动 IP地址： IP-Gi-c(c); 主控制面出接口单元与备控制面出接口单元， 拥有各自独立的 IP地址： IP-Out-c(a)和 IP-Out-c(s)。
如图 7所示， 主备 GGSN用户面对等模块的 IP地址对应关系为： 主用户面 入接口单元和备用户面入接口单元， 拥有各自独立的 IP地址： IP-In-u(a)和 IP-In-u(s); 主 Gn接口用户面单元与备 Gn接口用户面单元， 共享第三浮动 IP地 址： IP-Gn-u(c); 主 Gi接口用户面单元和备 Gi接口用户面单元， 共享第四浮动 IP地址： IP-pool-Gi-u(c); 主用户面出接口单元与备用户面出接口单元， 拥有 各自独立的 IP地址： IP-Out-u(a)和 IP-Out-u(s)。
再者， 举例说明本发明实施例应用场景中的主备 GGSN进行设备间热备 份的机制：
图 8为本发明实施例应用场景中进行主备 GGSN热备份的交互图。 如图 8 所示， 主备 GGSN进行设备间热备份的方法包括：
步骤 81 : 主 GGSN和备 GGSN之间通过发送心跳检测消息， 检测对方是否 发生故障。 心跳是一种周期性发出信号。 当位于一端的通信设备向对端通信设备发 送心跳时， 如果对端通信设备正常工作， 则会向其返回心跳应答。 本发明实 施例可釆用心跳检测消息， 检测主备 GGSN是否故障。
步骤 82: 主 GGSN向备 GGSN发送批量备份信息。
主 GGSN可周期性或满足预设条件时， 向备 GGSN发送批量备份信息。 该 备份信息可包括： 分组报文协议 ( Packet Data Protocol , 简称 PDP )上下文信 息， 如通用分组无线业务（ General Packet Radio Service, 简称 GPRS )传输协 议 （GPRS Tunnelling Protocol,简称 GTP)信息、服务质量（ Quality of Service , 简称 QoS ) 、 策略和计费控制 （ Policy And Charging Control , 简称 PCC )规 则等； 路由信息； 虚拟专用网络（ Virtual Private Network , 简称 VPN )信息， 如 IPSec/IKE VPN, L2TP VPN等；防火墙策略、网络地址转换 (Network Address Translation , 简称 NAT)信息等。 主 GGSN可向备 GGSN发送两次备份期间备份 信息的变化内容。
步骤 83: 备 GGSN启动预处理流程， 且备 GGSN的各模块处于主备倒换前 的预备状态。
备 GGSN启动预处理流程， 即： 将主 GGSN发送的备份信息， 同步到备 GGSN上的各对等模块。 备 GGSN接收主 GGSN发送的两次备份期间备份信息 的变化内容， 并将这些变化内容对应到如图 6和图 7所示的备 GGSN的对等模 块。
备 GGSN完成上述预处理流程后进入主备倒换的预备状态， 即： 通知备 GGSN上的各模块创建实例， 存储需接管业务的相关参数信息， 但不对外发 送报文。 一旦备 GGSN上的各模块接收到主备倒换指示时， 可立即对外发送 报文， 以实现主 GGSN业务的快速接管承载。
可以理解， 本发明实施例中主备通信设备进行设备间热备份的方法不受 限制， 图 8所示的方法仅为一个示例， 不应理解为对本发明实施例技术方案的 限制。 本发明实施例中， SGSN的支持能力可以不同， 如： 有的 SGSN支持主备 GGSN的主备地址对， 有的 SGSN不支持主备 GGSN的主备地址对。 其中， 主 备 GGSN的主备地址对具体为： 主 GGSN的 GTP-C地址： GTP-C(a) , 以及备 GGSN的 GTP-C地址： GTP-C(s)。 在实际通信***中， GGSN提供服务的用户 绝大多数为归属地用户， 少数为漫游地用户。 考虑多数用户服务的需要及设 备升级的成本， 本发明实施例可将归属地网内， 部署支持主备 GGSN的主备 地址对能力的 SGSN; 在漫游地网内部署不支持主备 GGSN的主备地址对能力 的 SGSN。 当然， 归属地网内也可部署不支持主备 GGSN的主备地址对能力的 SGSN。
SGSN的支持能力信息可预先登记在主 GGSN和 /或备 GGSN上， 也可由 SGSN主动上报给主 GGSN、 并由主 GGSN同步到备 GGSN上。
以下图 9和图 12对应的流程， 可基于扩展的 Gn接口消息实现， 其方法简 单， ***升级维护成本较低； 下面分别予以说明。
图 9为本发明实施例四提供的 SGSN支持能力信息上报方法的交互图。 如 图 9所示， SGSN支持能力信息上报方法包括：
步骤 91： SGSN向主 GGSN发送创建 PDP上下文请求（ Create PDP Context Request )消息， 该 PDP上下文请求消息中携带有 SGSN的支持能力信息， 该支 持能力信息用于表示 SGSN支持主备 GGSN的 GTP控制面地址对 （ Support active & hot-standby CTP-C ) , 即支持主备 GTP-C地址对。
本步骤中的 PDP上下文请求消息是一种扩展后的 Gn接口消息， 即为本发 明实施例所述的第一主备倒换请求。 SGSN可通过 PDP上下文请求消息向主 GGSN上报自身的支持能力信息。 主 GGSN在获取 SGSN的支持能力信息时， 可向备 GGSN同步该信息。
步骤 92: 主 GGSN向 SGSN发送创建 PDP上下文响应 （ Create PDP Context Response )消息， 该 PDP上下文响应消息中携带有主备 GGSN的 GTP-C地址对 ( CTP-C(a), CTP-C(s) ) 。 主 GGSN根据接收到的携带有 SGSN支持能力信息的创建 PDP上下文请求 消息， 获知 SGSN支持主备 GGSN的 GTP-C地址对， 因而在 PDP上下文响应消 息中携带主备 GGSN的 GTP-C地址对， 并发送给 SGSN。
步骤 93： SGSN接收创建 PDP上下文响应 （ Create PDP Context Response ) 消息，保存该消息中携带的主备 GGSN的 GTP-C地址对（ CTP-C(a) , CTP-C(s) ) , 并将 SGSN的信令通讯指针指向主 GGSN的 GTP-C地址： CTP-C(a)。
本实施例中， SGSN在获取主备 GGSN的 GTP-C地址对 （ CTP-C(a) , CTP-C(s) )时， 将信令通讯指针指向主 GGSN的 GTP-C地址： CTP-C(a)。 如此 处理的好处在于，当通信***中已经出现主备 GGSN"双活"现象时，由于 SGSN 的信令通讯指针指向主 GGSN的 GTP-C地址： CTP-C(a), 因此， SGSN可在接 收到的报文中， 过滤掉包括地址为备 GGSN的 GTP-C地址： CTP-C(s)的除了链 路测试指示和主备倒换指示之外的业务相关报文，即过滤掉包括地址 CTP-C(s) 的业务报文，从而降低 SGSN发生判断异常的几率， 也就因而降低了用户业务 中断的几率。 需要向主 GGSN上报其自身的支持能力信息， 而是釆用主备 GGSN的主备 Gn 接口控制面单元共享的第一浮动 IP地址， 分别与主备 GGSN进行信令交互。
通常，在主备倒换过程中，主 GGSN上各模块提供的业务，都需由备 GGSN 上各对等模块接管承载。 如果主备 GGSN上部分模块已进行主备倒换、 而部 分模块没有进行主备倒换， 即"部分倒换"， 则会造成网络异常， 甚至引发大 面积网络故障。 为了避免出现 "部分倒换"问题， 本发明实施例进一步引入了 一致性倒换机制， 即在备 GGSN上的各模块中确定一模块， 作为主备倒换的 触发点， 由其下发倒换指示， 以使得备 GGSN上的各模块同时进行主备倒换， 即进行一致性倒换。 下面结合图 10详细说明本发明实施例提供的主备一致性 倒换的方法。
图 10为本发明实施例五提供的主备一致性倒换的方法示意图。 如图 10所 示， 备 GGSN上的 Gn-c(s)模块为主备倒换的触发点。 在备 GGSN确定进行主备 倒换时， 由 Gn-c(s)模块向备 GGSN上的其他模块下发一致性倒换指示； 该一 致性倒换指示用于触发备 GGSN上的各模块，启动主 GGSN各对等模块提供的 业务的接管承载。
备 GGSN上的各模块分别抢占主 GGSN对等模块占用的共享资源， 以接管 承载主 GGSN对等模块提供的业务。 具体的， 对于控制面而言， In-c(s)模块以 广播消息等方式刷新 In-c(a)模块的路由， Gn-c(s)模块抢占自身与 Gn-c(a)模块 共享的第一浮动地址， Gi-c(s)模块抢占自身与 Gi-c(a)模块共享的第二浮动 IP 地址， 而 Out-c(s)模块以广播消息等方式刷新 Out-c(a)模块的路由。 对于用户 面而言， In-u(s)模块以广播消息等方式刷新 In-u(a)模块的路由， Gn-u(s)模块 抢占自身与 Gn-u(a) 模块共享的第三浮动 IP地址， Gi-u(s)模块抢占自身与 Gi-u(a) 模块共享的第四浮动 IP地址， Out-u(s)模块以广播消息等方式刷新 Out-u(a)模块的路由。 如果共享资源被主 GGSN对等模块占用， 则在备 GGSN 上的各模块抢占共享资源时， 主 GGSN对等模块会释放相应资源。
由此可见， 本实施例在进行主备倒换时， 通过引入一致性倒换机制， 完 成主备 GGSN上各模块的同步倒换，避免发生主备 GGSN上部分模块已进行主 备倒换、 而部分模块没有进行主备倒换所引发的网络异常， 从而有利于降低 因这些网络异常造成用户业务中断的几率。
为了提高故障状态收集的准确性， 可在主 GGSN上设置故障状态收集点， 并以主 GGSN作为主备倒换判决的触发点。 图 11为本发明实施例提供的主 GGSN集中收集故障状态的模块示意图。 如图 11所示， 可将主 GGSN中的 Gn-c(a)模块作为故障状态的收集模块， 由该模块集中收集主 GGSN相关的各 类故障， 如： 物理接口故障、 链路故障、 及模块故障等。 在主 GGSN集中收 集自身相关的各类故障之后， 可基于收集到的这些故障信息进行整体评估， 以判决是否进行主备倒换。
表 1： 主 GGSN故障整体评估和倒换判决规则示例 故障类型 容量损失 业务损失 执行动作 物理接口 /链路故障 (0,x%) (0,y%) 土藝 物理接口 /链路故障 [x%, w%) [y%, v%) 协商 +告警 物理接口 /链路故障 >=w% >=v% 立即倒换 +告警 模块故障 1 1 立即倒换 +告警 如表 1所示， 主 GGSN可分类收集故障状态， 故障类型可包括： 物理接口 故障、 链路故障和设备模块故障。 此外， 主 GGSN还可根据实际需要预设容 量损失阔值和业务损失阔值， 其中， 容量损失是表示配置量的损失， 业务损 失表示故障前后业务流量的变化量。 在实际应用中， 可根据运营商网络规划 时的冗余配置量和网络统计的业务流量， 来设定相应阔值。 例如： 预先设置 第一容量损失阔值 x%和第二容量损失阔值w%, 且 0< X%< W%<1 ; 预先设置 第一业务损失阔值 %和第二业务损失阔值v%, 且 0< y%< ν%<1。
在主 GGSN收集到故障状态信息时， 均可执行"告警"的动作， 即输出告警 提示信息， 以提示主 GGSN当前发生了故障。 此外， 主 GGSN还可结合考虑故 障类型、 主 GGSN当前的容量损失和业务损失， 预先判决条件， 以便主 GGSN 根据判决条件确定当前需要执行的动作。 具体的， 可根据收集到的故障对业 务的影响程度， 主 GGSN还可执行"协商"和"立即倒换 "动作对应的判决条件。 预先设置的判决条件例如：
第一预设条件： 故障的类型为物理接口 /链路故障、 当前的容量损失量介 于预设的第一容量损失阔值和第二容量损失阔值之间， 即 [x%, w%), 且当前 的业务损失量介于预设的第一业务损失阔值和第二业务损失阔值之间， 即 [y%, v%)。
第二预设条件： 故障的类型为物理接口 /链路故障、 当前的容量损失量大 于或等于第二容量损失阔值w%、且当前的业务损失量大于或等于第二业务损 失阔值¥%；
第三预设条件： 故障的类型为设备模块故障。
当主 GGSN收集到的故障状态信息满足第一预设条件时， 主 GGSN执行 "协商"动作， 即向备 GGSN发起主备协商倒换的流程； 当主 GGSN收集到的故 障状态信息满足第二预设条件或第三预设条件时， 主 GGSN执行"立即倒换" 的动作， 即由主 GGSN触发主备倒换。 由此可见， 主通信设备可基于收集到 的故障状态和预先设置的判决条件， 自动判断是否需要进行倒换， 从而提高 了***管理和维护的方便性。 下面结合附图， 对主 GGSN触发主备倒换以及 主备 GGSN协商倒换等两种情形， 分别予以说明。
图 12为本发明实施例六提供的主备 GGSN进行倒换协商方法的交互图。 如图 12所示， 主备 GGSN进行倒换协商的方法包括：
步骤 121 : 主 GGSN根据自身故障状态信息， 确定需要进行主备倒换。 主 GGSN收集自身故障状态信息的方式不受限制。 可选的， 以 Gn-c(a)模 块作为故障状态的收集模块， 收集故障状态信息。 当收集到的故障状态信息 满足上述第一预设条件时， 主 GGSN确定执行 "协商 "的动作。
步骤 122: 主 GGSN向备 GGSN发送主备倒换协商请求（ Switch Negotiation Request ) , 用于请求备 GGSN确定是否进行主备倒换。
主备倒换协商请求 （Switch Negotiation Request ) 中携带有故障报告 ( Failure Report ) ,该故障报告中包括： 主 GGSN的当前容量损失量（ Capacity Loss )和业务损失量 ( Service Loss ) 。
步骤 123: 备 GGSN确定倒换后的自身的业务预期损失量， 并将业务预期 损失量， 与故障报告中的当前容量损失量和业务损失量进行比较， 确定是否 同意进行主备倒换。
备 GGSN可结合故障报告中主 GGSN当前的容量损失量和业务损失量、以 及备 GGSN的本机状态、 容量和负载情况， 确定倒换后的自身的业务预期损 失量。 将该业务预期损失量， 与故障报告中的当前容量损失量和业务损失量 进行比较。 如该业务预期损失量， 小于主 GGSN当前的容量损失量和业务损 失量， 则同意进行主备倒换； 否则， 拒绝进行主备倒换。
步骤 124:备 GGSN向主 GGSN发送主备倒换协商响应（ Switch Negotiation Response ) , 用于通知主 GGSN是否同意进行主备倒换。
如果备 GGSN拒绝进行主备倒换， 则在主备倒换协商响应中携带"拒绝" ( Reject )参数， 并可携带备 GGSN的可用容量（ Capacity available )信息和拒 绝原因 （Cause ) ； 结束本流程。
如果备 GGSN同意进行主备倒换， 则在主备倒换协商响应中携带"接受" ( Accept )参数; 执行步骤 125a-步骤 126。 .
步骤 125a-步骤 125c: 备 GGSN分别向 SGSN1、 SGSN2和 SGSN3分别发送 主备倒换指示 （Switch ) , 该指示中可携带主备 GTP-C地址对 （GTP-C(a), GTP-C(s) ) , 用于分别指示 SGSN1、 SGSN2和 SGSN3将其信令通讯指针， 由 GTP-C(a)切换指向 GTP-C(s)。
步骤 126: 备 GGSN接管承载主 GGSN提供的业务。
本实施中， 主 GGSN引入了主备倒换的协商机制： 主 GGSN根据收集到的 故障状态信息， 自身确定有必要进行主备倒换时， 将主 GGSN当前的容量损 失量和业务损失量发送给备 GGSN, 由备 GGSN结合本机状况、 容量和负载情 况进行评估， 以确定是否接受协商以进行主备倒换。 可见， 本实施例基于主 备倒换协商机制进行倒换， 可避免倒换后因备 GGSN接管能力受限而给用户 造成更大损失， 进而有利于降低因主备倒换不适造成用户业务中断的几率。 此外， 上述步骤 126中， 备 GGSN上的各模块可同时进行主备倒换， 即进行一 致性倒换， 其实现方法和效果的详细描述， 参见图 10对应实施例的相应记载， 在此不再赘述。
可以理解， 本发明实施例提供的技术方案可应用于各种通信设备的主备 倒换中， 其中， 主通信设备的实现方式和机理， 与上文的主 GGSN相似； 备 通信设备的实现方式和机理， 与上文的备 GGSN相似； 服务请求设备的实现 方式和机理， 与上文的 SGSN相似； 在此不再赘述。
图 13为本发明实施例七提供的通信设备的结构示意图。 如图 13所示， 本 实施例提供的通信设备包括： 协商故障信息获取模块 131、预期损失量确定模 块 132、 倒换评估模块 133、 主备倒换指示模块 134和倒换执行模块 135。
主通信设备的业务负载和当前损失量等故障信息的获取方式不受限制。 根据故障信息获取方式的不同，协商故障信息获取模块 131可用于接收所述主 通信设备发送的、 携带有所述故障信息的主备倒换协商请求， 所述故障信息 包括： 所述主通信设备的业务负载和当前损失量。
预期损失量确定模块 132可用于根据所述通信设备的本机状态、容量和负 载情况， 以及所述主通信设备的业务负载， 确定倒换后的业务预期损失量. 倒换评估模块 133可用于在所述业务预期损失量小于所述当前损失量时， 确定需要进行主备倒换。
主备倒换指示模块 134可用于向服务请求设备发送主备倒换指示；所述主 备倒换指示用于指示所述服务请求设备将其信令通讯指针， 由所述主通信设 备的主信令交互接口地址切换到所述通信设备的备信令交互接口地址。
倒换执行模块 135可用于接管承载所述主通信设备提供的业务。
本发明提供的通信设备向服务请求设备发送主备倒换指示时， 指示服务 请求设备将其信令通讯指针由主信令交互接口地址， 切换到备信令交互接口 地址； 从而在当通信***中已经出现主备通信设备"双活，，现象时， 有利于服 务请求设备过滤掉信令通讯指针没有指向的地址相关的业务报文， 从而降低 服务请求设备发生判断异常的几率， 也就因而降低了用户业务中断的几率。 本发明实施例提供的通信设备的设备类型不受限制， 如可具体用于设备间备 份的分组网关设备等， 其工作机理， 可参见图 1、 图 4〜图 12实施例中关于备通 信设备或备 GGSN的相应记载， 在此不再赘述。
图 14为本发明实施例八提供的通信设备的结构示意图。 如图 14所示， 本 实施例提供的通信设备包括： 能力信息获取模块 141和地址指示模块 142。 能力信息获取模块 141可用于获取与主通信设备连接的服务请求设备的 支持能力信息， 所述支持能力信息用于表示所述服务请求设备支持主备地址 对； 所述主备地址对包括： 所述主通信设备的主信令交互接口地址、 以及备 通信设备的备信令交互接口地址。
地址指示模块 142可用于向所述服务请求设备发送所述主备地址对，并指 示所述服务请求设备将其信令通讯指针指向所述主信令交互接口地址。
可选的， 本实施例提供的通信设备还可包括： 故障信息收集模块 143、 倒 换协商请求模块 144和协商响应获取模块 145。
故障信息收集模块 143可用于获取故障信息， 所述故障信息包括： 与主通 信设备相关的已发生故障的类型、 容量损失量和业务损失量。
倒换协商请求模块 144可用于在所述故障信息满足第一预设条件时，向与 所述主通信设备对应的备通信设备发送包括所述故障信息的主备倒换协商请 求； 所述第一预设条件包括： 所述故障的类型为物理接口 /链路故障、 所述容 量损失量介于预设的第一容量损失阈值和第二容量损失阈值之间， 所述业务 损失量介于预设的第一业务损失阔值和第二业务损失阔值之间。
协商响应获取模块 145可用于接收所述备通信设备发送的主备倒换协商 响应，且在所述主备倒换协商响应表示所述备通信设备同意进行主备倒换时， 由所述备通信设备接管承载所述通信设备提供的业务。
可选的， 本实施例提供的通信设备还可包括： 倒换请求模块 146, 和 /或， 告警模块 147。 其中， 倒换请求模块 146用于在所述故障信息满足第二预设条 件或第三预设条件时， 向所述备通信设备发送主备倒换请求， 所述主备倒换 请求用于触发所述备通信设备启动主备倒换； 所述第二预设条件包括： 所述 故障的类型为物理接口 /链路故障、 所述容量损失量大于或等于所述第二容量 损失阈值、 且所述业务损失量大于或等于所述第二业务损失阈值； 所述第三 预设条件包括： 所述故障的类型为设备模块故障。 告警模块 147用于在所述故 障信息表示已有故障发生时， 输出告警提示信息。 本实施例中， 主通信设备在获知服务请求设备的支持能力信息时， 向服 务请求设备发送主备地址对， 并指示服务请求设备将其信令通讯指针指向主 信令交互接口地址， 从而在当通信***中已经出现主备通信设备"双活，，现象 时， 可过滤掉信令通讯指针没有指向的地址相关的业务报文， 从而降低服务 请求设备发生判断异常的几率， 也就因而降低了用户业务中断的几率。 进一 步的， 本实施例通信设备还可基于主备倒换协商机制进行倒换， 由此可避免 倒换后因备通信设备接管能力受限而给用户造成更大损失， 进而有利于降低 因主备倒换不适造成用户业务中断的几率。 本实施例通信设备的设备类型不 受限制， 如可具体为分组网关设备等， 其工作机理可参见图 2、 图 4〜图 12实施 例中关于主通信设备或主 GGSN的相应记载， 在此不再赘述。
图 15为本发明实施例九提供的服务请求设备的结构示意图。如图 15所示， 本实施例提供的服务请求设备包括： 能力信息上报模块 151、地址信息获取模 块 152和通讯指针处理模块 153。
能力信息上报模块 151可用于向主通信设备上报所述服务请求设备的支 持能力信息；所述支持能力信息用于表示所述服务请求设备支持主备地址对， 所述主备地址对包括： 所述主通信设备的主信令交互接口地址和所述备通信 设备的备信令交互接口地址。
地址信息获取模块 152可用于接收所述主通信设备发送的所述主备地址 对。
通讯指针处理模块 153可用于将所述服务请求设备的信令通讯指针，指向 所述主信令交互接口地址， 且在接收到所述备通信设备发送的主备倒换指示 时， 将所述信令通讯指针由所述主信令交互接口地址， 切换到所述备信令交 互接口地址。
可选的， 本实施例提供的服务请求设备还可包括： 第一业务报文丟弃模 块 154, 和 /或， 第二业务报文丟弃模块 155。
第一业务报文丟弃模块 154可用于在所述信令通讯指针指向所述主信令 交互接口地址、 且接收到来自所述备信令交互接口地址的第一业务报文时， 丟弃所述第一业务报文。
第二业务报文丟弃模块 155可用于在所述信令通讯指针指向所述备信令 交互接口地址、 且接收到来自所述主信令交互接口地址的第二业务报文时， 丟弃所述第二业务报文。
本实施例中， 当服务请求设备支持主备地址对的能力时， 将其支持主备 地址对的能力信息上报给主备通信设备， 接收主备地址对， 并在接收到主备 倒换指示时， 将所述信令通讯指针由所述主信令交互接口地址， 切换到所述 备信令交互接口地址。 从而在当通信***中已经出现主备通信设备"双活"现 象时， 可过滤掉信令通讯指针没有指向的地址相关的业务报文， 从而降低服 务请求设备发生判断异常的几率， 也就因而降低了用户业务中断的几率。 本 实施例通信设备的设备类型不受限制， 如可具体为与分组网关设备连接的服 务请求设备等， 其具体实现机理， 可参见图 3、 图 4〜图 12实施例中关于服务请 求设备或 SGSN的相应记载， 在此不再赘述。
图 16为本发明实施例十提供的通信设备的结构示意图。 如图 16所示， 本 实施例提供的通信***包括： 主通信设备 161、 备通信设备 162和服务请求设 备 163。 服务请求设备 163分别与主通信设备 161和备通信设备 162通信连接， 且服务请求设备 163的数量可为一个或多个，图 16中示出了通信***中包括多 个服务请求设备 163的情形。主通信设备的结构可参见图 14对应实施例的相应 记载， 其工作机理可参见图 2、 图 4〜图 12实施例中关于主通信设备或主 GGSN 的相应记载； 备通信设备的结构可参见图 13对应实施例的相应记载， 其工作 机理可参见图 1、 图 4〜图 12实施例中关于备通信设备或备 GGSN的相应记载； 服务请求设备的结构可参见图 15对应实施例的相应记载， 其工作机理可参见 图 3、 图 4〜图 12实施例中关于关于服务请求设备或 SGSN的相应记载， 在此不 再赘述。 本实施例提供的通信***组网结构简单， 便于部署和维护， 易于实 现。 本领域普通技术人员可以理解： 附图只是一个实施例的示意图， 附图中 的模块或流程并不一定是实施本发明所必须的。
本领域普通技术人员可以理解： 实施例中的装置中的模块可以按照实施 例描述分布于实施例的装置中， 也可以进行相应变化位于不同于本实施例的 一个或多个装置中。 上述实施例的模块可以合并为一个模块， 也可以进一步 拆分成多个子模块。
本领域普通技术人员可以理解： 实现上述方法实施例的全部或部分步骤 可以通过程序指令相关的硬件来完成， 前述的程序可以存储于一计算机可读 取存储介质中， 该程序在执行时， 执行包括上述方法实施例的步骤； 而前述 的存储介质包括： ROM, RAM, 磁碟或者光盘等各种可以存储程序代码的介 最后应说明的是： 以上实施例仅用以说明本发明的技术方案， 而非对其 限制； 尽管参照前述实施例对本发明进行了详细的说明， 本领域的普通技术 人员应当理解： 其依然可以对前述实施例所记载的技术方案进行 ^ί'爹改， 或者 对其中部分技术特征进行等同替换； 而这些修改或者替换， 并不使相应技术 方案的本质脱离本发明实施例技术方案的精神和范围。

Claims

权 利 要 求 书
1、 一种通信设备间的主备倒换方法， 其特征在于， 包括：
接收主通信设备发送的、 携带有故障信息的主备倒换协商请求， 所述故 障信息包括： 所述主通信设备的业务负载和当前损失量；
根据备通信设备的本机状态、 容量和负载情况， 以及所述主通信设备的 业务负载， 确定倒换后的业务预期损失量， 并在所述业务预期损失量小于所 述当前损失量时， 确定需要进行主备倒换；
向服务请求设备发送主备倒换指示； 所述主备倒换指示用于指示所述服 务请求设备将其信令通讯指针， 由所述主通信设备的主信令交互接口地址切 换到所述备通信设备的备信令交互接口地址；
接管承载所述主通信设备提供的业务。
2、 根据权利要求 1所述的方法， 其特征在于， 所述接管承载所述主通信 设备提供的业务， 包括：
所述备通信设备上的任一模块， 触发所述备通信设备上的各模块， 分别 接管承载所述主通信设备对等模块提供的业务。
3、 根据权利要求 2所述的方法， 其特征在于，
所述备通信设备具体为备 GGSN， 所述主通信设备具体为主 GGSN; 所述备通信设备上的任一模块， 触发所述备通信设备上的各模块， 分别 接管承载所述主通信设备对等模块提供的业务， 包括： 所述备 GGSN上的备 Gn接口控制面单元， 向所述备 GGSN上的其他模块下发一致性倒换指示； 所 述备 GGSN上的各模块根据所述一致性倒换指示，分别接管承载所述主 GGSN 对等模块提供的业务。
4、 一种通信设备间的主备倒换方法， 其特征在于， 包括：
获取与主通信设备连接的服务请求设备的支持能力信息， 所述支持能力 信息用于表示所述服务请求设备支持主备地址对； 所述主备地址对包括： 所 述主通信设备的主信令交互接口地址、 以及备通信设备的备信令交互接口地 址；
向所述服务请求设备发送所述主备地址对， 并指示所述服务请求设备将 其信令通讯指针指向所述主信令交互接口地址。
5、 根据权利要求 4所述的方法， 其特征在于， 所述方法还包括： 获取故障信息， 所述故障信息包括： 与所述主通信设备相关的已发生故 障的类型、 容量损失量和业务损失量；
在所述故障信息满足第一预设条件时， 向所述备通信设备发送包括所述 故障信息的主备倒换协商请求； 所述第一预设条件包括： 所述故障的类型为 物理接口 /链路故障、 所述容量损失量介于预设的第一容量损失阔值和第二容 量损失阔值之间， 所述业务损失量介于预设的第一业务损失阔值和第二业务 损失阔值之间；
接收所述备通信设备发送的主备倒换协商响应， 且在所述主备倒换协商 响应表示所述备通信设备同意进行主备倒换时， 由所述备通信设备接管承载 所述主通信设备提供的业务。
6、 根据权利要求 5所述的方法， 其特征在于， 所述方法还包括： 在所述故障信息满足第二预设条件或第三预设条件时， 向所述备通信设 备发送主备倒换请求， 所述主备倒换请求用于触发所述备通信设备启动主备 倒换； 所述第二预设条件包括： 所述故障的类型为物理接口 /链路故障、 所述 容量损失量大于或等于所述第二容量损失阈值、 且所述业务损失量大于或等 于所述第二业务损失阔值； 所述第三预设条件包括： 所述故障的类型为设备 模块故障；
和 /或，
在所述故障信息表示已有故障发生时， 输出告警提示信息。
7、 一种通信设备间的主备倒换方法， 其特征在于，
向主通信设备上报服务请求设备的支持能力信息； 所述支持能力信息用 于表示所述服务请求设备支持主备地址对； 接收所述主通信设备发送的所述主备地址对， 所述主备地址对包括： 所 述主通信设备的主信令交互接口地址和备通信设备的备信令交互接口地址； 将所述服务请求设备的信令通讯指针， 指向所述主信令交互接口地址， 且在接收到所述备通信设备发送的主备倒换指示时， 将所述信令通讯指针由 所述主信令交互接口地址， 切换到所述备信令交互接口地址。
8、 根据权利要求 7所述的方法， 其特征在于， 在接收所述主通信设备发 送的所述主备地址对之后， 所述方法还包括：
在所述信令通讯指针指向所述主信令交互接口地址、 且接收到来自所述 备信令交互接口地址的第一业务报文时， 丟弃所述第一业务报文；
和 /或，
在所述信令通讯指针指向所述备信令交互接口地址、 且接收到来自所述 主信令交互接口地址的第二业务报文时， 丟弃所述第二业务报文。
9、 一种通信设备， 其特征在于， 包括：
协商故障信息获取模块， 用于接收主通信设备发送的、 携带有故障信息 的主备倒换协商请求， 所述故障信息包括： 所述主通信设备的业务负载和当 前损失量；
预期损失量确定模块， 用于根据所述通信设备的本机状态、 容量和负载 情况， 以及所述主通信设备的业务负载， 确定倒换后的业务预期损失量； 倒换评估模块， 用于在所述业务预期损失量小于所述当前损失量时， 确 定需要进行主备倒换；
主备倒换指示模块， 用于向服务请求设备发送主备倒换指示； 所述主备 倒换指示用于指示所述服务请求设备将其信令通讯指针， 由所述主通信设备 的主信令交互接口地址切换到所述通信设备的备信令交互接口地址；
倒换执行模块， 用于接管承载所述主通信设备提供的业务。
10、 一种通信设备， 其特征在于， 包括：
能力信息获取模块， 用于获取与主通信设备连接的服务请求设备的支持 能力信息， 所述支持能力信息用于表示所述服务请求设备支持主备地址对； 所述主备地址对包括： 所述主通信设备的主信令交互接口地址、 以及备通信 设备的备信令交互接口地址；
地址指示模块， 用于向所述服务请求设备发送所述主备地址对， 并指示 所述服务请求设备将其信令通讯指针指向所述主信令交互接口地址。
11、 根据权利要求 10所述的通信设备， 其特征在于， 所述通信设备还包 括：
故障信息收集模块， 用于获取故障信息， 所述故障信息包括： 与所述主 通信设备相关的已发生故障的类型、 容量损失量和业务损失量；
倒换协商请求模块， 用于在所述故障信息满足第一预设条件时， 向与所 述通信设备对应的备通信设备发送包括所述故障信息的主备倒换协商请求； 所述第一预设条件包括： 所述故障的类型为物理接口 /链路故障、 所述容量损 失量介于预设的第一容量损失阈值和第二容量损失阈值之间， 所述业务损失 量介于预设的第一业务损失阔值和第二业务损失阔值之间；
协商响应获取模块，用于接收所述备通信设备发送的主备倒换协商响应， 且在所述主备倒换协商响应表示所述备通信设备同意进行主备倒换时， 由所 述备通信设备接管承载所述通信设备提供的业务。
12、 根据权利要求 11所述的通信设备， 其特征在于， 所述通信设备还包 括：
倒换请求模块， 用于在所述故障信息满足第二预设条件或第三预设条件 时， 向所述备通信设备发送主备倒换请求， 所述主备倒换请求用于触发所述 备通信设备启动主备倒换； 所述第二预设条件包括： 所述故障的类型为物理 接口 /链路故障、 所述容量损失量大于或等于所述第二容量损失阔值、 且所述 业务损失量大于或等于所述第二业务损失阈值； 所述第三预设条件包括： 所 述故障的类型为设备模块故障；
和 /或， 告警模块， 用于在所述故障信息表示已有故障发生时， 输出告警提示信息。
13、 一种服务请求设备， 其特征在于， 包括：
能力信息上报模块， 用于向主通信设备上报所述服务请求设备的支持能 力信息； 所述支持能力信息用于表示所述服务请求设备支持主备地址对， 所 述主备地址对包括： 所述主通信设备的主信令交互接口地址和备通信设备的 备信令交互接口地址；
地址信息获取模块， 用于接收所述主通信设备发送的所述主备地址对； 通讯指针处理模块， 用于将所述服务请求设备的信令通讯指针， 指向所 述主信令交互接口地址，且在接收到所述备通信设备发送的主备倒换指示时， 将所述信令通讯指针由所述主信令交互接口地址， 切换到所述备信令交互接 σ地址。
14、 根据权利要求 13所述的服务请求设备， 其特征在于， 所述服务请求 设备还包括：
第一业务报文丟弃模块， 用于在所述信令通讯指针指向所述主信令交互 接口地址、 且接收到来自所述备信令交互接口地址的第一业务报文时， 丟弃 所述第一业务报文；
和 /或，
第二业务报文丟弃模块， 用于在所述信令通讯指针指向所述备信令交互 接口地址、 且接收到来自所述主信令交互接口地址的第二业务报文时， 丟弃 所述第二业务报文。
15、 一种通信***， 其特征在于， 包括：
主通信设备， 为如权利要求 10〜12任一所述的通信设备；
备通信设备， 为如权利要求 9所述的通信设备， 与所述主通信设备通信连接； 以及服务请求设备， 为如权利要求 13或 14所述的服务请求设备， 分别与 所述主通信设备和所述备通信设备通信连接。
PCT/CN2011/075057 2011-05-31 2011-05-31 通信设备间的主备倒换方法、通信设备和***及服务请求设备 WO2011157146A2 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201180000978.2A CN102265556B (zh) 2011-05-31 2011-05-31 通信设备间的主备倒换方法、通信设备和***及服务请求设备
PCT/CN2011/075057 WO2011157146A2 (zh) 2011-05-31 2011-05-31 通信设备间的主备倒换方法、通信设备和***及服务请求设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/075057 WO2011157146A2 (zh) 2011-05-31 2011-05-31 通信设备间的主备倒换方法、通信设备和***及服务请求设备

Publications (2)

Publication Number Publication Date
WO2011157146A2 true WO2011157146A2 (zh) 2011-12-22
WO2011157146A3 WO2011157146A3 (zh) 2012-04-26

Family

ID=45010618

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/075057 WO2011157146A2 (zh) 2011-05-31 2011-05-31 通信设备间的主备倒换方法、通信设备和***及服务请求设备

Country Status (2)

Country Link
CN (1) CN102265556B (zh)
WO (1) WO2011157146A2 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102638369B (zh) * 2012-03-29 2015-05-27 华为技术有限公司 一种主备倒换的仲裁方法、装置和***
CN102710457B (zh) * 2012-05-07 2015-11-25 浙江宇视科技有限公司 一种跨网段的n+1备份方法及装置
CN102739453B (zh) * 2012-07-03 2015-07-29 华为软件技术有限公司 主备切换方法、设备及***
CN103607310A (zh) * 2013-11-29 2014-02-26 华为技术有限公司 一种异地容灾的仲裁方法
CN104239548B (zh) * 2014-09-23 2018-07-31 中电长城网际***应用有限公司 数据库容灾***和数据库容灾方法
CN104301140B (zh) * 2014-10-08 2019-07-30 广州华多网络科技有限公司 业务请求响应方法、装置和***
CN107846294B (zh) * 2016-09-19 2021-01-26 北京京东尚科信息技术有限公司 一种主备服务切换方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101060391A (zh) * 2007-05-16 2007-10-24 华为技术有限公司 主备服务器切换方法及***及主用服务器、备用服务器
US20080175142A1 (en) * 2007-01-19 2008-07-24 Fujitsu Limited Network apparatus, redundant network method, and computer product
CN101583144A (zh) * 2009-07-07 2009-11-18 杭州华三通信技术有限公司 无线控制器业务信息的备份方法和设备
CN102006268A (zh) * 2009-08-28 2011-04-06 华为技术有限公司 主备接口切换方法、设备及***

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080175142A1 (en) * 2007-01-19 2008-07-24 Fujitsu Limited Network apparatus, redundant network method, and computer product
CN101060391A (zh) * 2007-05-16 2007-10-24 华为技术有限公司 主备服务器切换方法及***及主用服务器、备用服务器
CN101583144A (zh) * 2009-07-07 2009-11-18 杭州华三通信技术有限公司 无线控制器业务信息的备份方法和设备
CN102006268A (zh) * 2009-08-28 2011-04-06 华为技术有限公司 主备接口切换方法、设备及***

Also Published As

Publication number Publication date
WO2011157146A3 (zh) 2012-04-26
CN102265556B (zh) 2014-01-08
CN102265556A (zh) 2011-11-30

Similar Documents

Publication Publication Date Title
WO2011157145A2 (zh) 通信设备间的主备倒换方法、通信设备和***及服务请求设备
WO2011157149A2 (zh) 通信设备间的主备倒换方法、通信设备和***及服务请求设备
EP3398068B1 (en) Network redundancy and failure detection
JP5113684B2 (ja) アクセスゲートウェイ装置の制御方法及び通信システム
EP2832060B1 (en) Inter-chassis redundancy with coordinated traffic direction
WO2011157146A2 (zh) 通信设备间的主备倒换方法、通信设备和***及服务请求设备
US10992570B2 (en) Packet forwarding method and device for a virtual private wire service (VPWS) pseudo wire (PW) network using traffic balancing
CN101197733A (zh) 网络连通性的自动检测方法及装置
CN111447101B (zh) 链路检测方法、装置、计算机设备及存储介质
KR20150033681A (ko) 연결 실패 시에 홈 네트워크에 대한 재라우팅을 인에이블시키는 방법 및 시스템
CN106603261A (zh) 热备份方法、第一主用设备、备用设备和通信***
WO2013078671A1 (zh) 一种故障检测方法、网关、用户设备及通信***
WO2014146541A1 (zh) Cdn与网络融合***、调度模块选定方法及计算机存储介质
AU2011229566A1 (en) Load sharing method and apparatus
CN107222883B (zh) 无线控制器备份方法、备份切换方法、装置及***
CN104869118B (zh) 一种基于动态隧道技术实现DDoS防御的方法及***
WO2022252874A1 (zh) 信令风暴抑制方法、移动终端、电子设备及存储介质
WO2022007861A1 (zh) 通知故障的方法和电子设备
WO2015135280A1 (zh) 一种实现按需智能拨号的方法、***和接入路由器
US9900234B2 (en) Direct link quality monitoring method, communications device, and system
JPH11296396A (ja) 切替隠蔽機能付き高可用性システム
CN105553864B (zh) 降低lmp中消息数量的方法及装置
CN114697373B (zh) 一种用于会话保护的方法及***
EP4207843A1 (en) Communication system and method for recovering faults therein
EP2506626B1 (en) Method and system for monitoring quality based on ip bearer in a mobile network

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201180000978.2

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11795112

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase in:

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11795112

Country of ref document: EP

Kind code of ref document: A2