CN106713134B - SBC disaster recovery method, system and device based on static IP longest match - Google Patents

SBC disaster recovery method, system and device based on static IP longest match Download PDF

Info

Publication number
CN106713134B
CN106713134B CN201510796111.2A CN201510796111A CN106713134B CN 106713134 B CN106713134 B CN 106713134B CN 201510796111 A CN201510796111 A CN 201510796111A CN 106713134 B CN106713134 B CN 106713134B
Authority
CN
China
Prior art keywords
sbc
disaster recovery
disaster
address
user
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.)
Active
Application number
CN201510796111.2A
Other languages
Chinese (zh)
Other versions
CN106713134A (en
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.)
China Mobile Group Zhejiang Co Ltd
Original Assignee
China Mobile Group Zhejiang Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Mobile Group Zhejiang Co Ltd filed Critical China Mobile Group Zhejiang Co Ltd
Priority to CN201510796111.2A priority Critical patent/CN106713134B/en
Publication of CN106713134A publication Critical patent/CN106713134A/en
Application granted granted Critical
Publication of CN106713134B publication Critical patent/CN106713134B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/22—Alternate routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/24—Multipath
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H04L45/745—Address table lookup; Address filtering
    • H04L45/748—Address table lookup; Address filtering using longest matching prefix

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The invention discloses a Session Border Controller (SBC) disaster recovery method based on the longest match of static IP, which comprises configuring at least one disaster recovery SBC, wherein the disaster recovery SBC is virtualized with all SBC data corresponding to each main SBC; when disaster recovery is performed on a primary SBC, a user IP address and a subnet mask are configured on a disaster recovery client side edge device (CE) on the side of the disaster recovery SBC, wherein the user IP address is the same as the user IP address of the disaster recovery primary SBC, and the number of address mask bits of the subnet mask is more than that of the address mask bit of the CE corresponding to the disaster recovery primary SBC; based on the longest static IP matching principle, the data packet of the disaster-tolerant primary SBC is routed to the disaster-tolerant CE on the side of the disaster-tolerant SBC. The invention also discloses an SBC disaster recovery system and a disaster recovery switching control device based on the longest static IP matching.

Description

SBC disaster recovery method, system and device based on static IP longest match
Technical Field
The present invention relates to a Session Border Controller (SBC) disaster recovery technology, and in particular, to a SBC disaster recovery method, system, and apparatus based on the longest static IP matching.
Background
An IP Multimedia Subsystem (IMS) is a communication system for implementing voice, video and data converged communication, and an SBC in the system is used as a first point device for a user terminal to access, and the SBC is required to have high reliability and availability. In order to enable the standby SBC device to take over quickly after any SBC in the IMS system fails, a disaster recovery architecture of the SBC needs to be established.
With the increasing of IMS network users, higher requirements are put on the service reliability of the IMS network, especially for the border control device — SBC of the IMS network. Because the SBCs are deployed in different areas, the number of SBCs is large, and if disaster recovery SBCs are newly built in each area to implement disaster recovery, the investment is large, the construction period is long, and the SBCs do not meet the practical requirements.
An existing implementation scheme for SBC disaster recovery is: the same two sets of SBC are built in the same terminal place to form an SBC pool, the same IP addresses for the terminals are configured on the two SBC in the SBC pool, and when one SBC is down or fails, the terminals can be automatically routed to the other SBC in the SBC pool. The implementation scheme has short disaster recovery switching time, but requires the construction of double SBC number, and has high cost.
Another existing implementation scheme for SBC disaster recovery is: and a set of disaster recovery SBC is built outside the SBCs of the N terminal sites to be used as disaster recovery equipment of the N SBCs. When a certain SBC is down or other faults need to switch the service to the disaster recovery SBC, the maintenance personnel urgently configures data, firstly deletes the static route related to the main SBC on the Customer side Edge device (CE, Customer Edge) corresponding to the main SBC, then adds the static route on the CE connected to the disaster recovery SBC side, and achieves the disaster recovery effect through the virtual main SBC configured on the disaster recovery SBC. Although the implementation scheme is low in implementation cost, the disaster recovery switching time is long. Specifically, when a certain SBC fails and needs to be switched, both the CE devices related to the failed SBC side and the disaster recovery SBC device themselves need to temporarily configure data, so that the disaster recovery switching involves many network elements for operation, and the operation process takes a long time; moreover, the disaster recovery switching data is temporarily configured, and the correctness and reliability of the data cannot be guaranteed.
Disclosure of Invention
In order to overcome the defects of the prior art, embodiments of the present invention are expected to provide a method, a system, and a device for SBC disaster recovery based on the longest static IP matching, which can not only realize SBC disaster recovery quickly and conveniently at low cost, but also ensure accuracy and reliability of data.
The technical scheme of the embodiment of the invention is realized as follows:
the embodiment of the invention provides an SBC disaster recovery method based on the longest static IP matching, which comprises the steps of configuring at least one disaster recovery SBC, wherein the disaster recovery SBC is virtualized with all SBC data corresponding to each main SBC; the method further comprises the following steps:
when disaster recovery is performed on a master SBC, a user IP address and a subnet mask are configured on a disaster recovery CE on the side of the disaster recovery SBC, wherein the user IP address is the same as the user IP address of the disaster recovery master SBC, and the number of address mask bits of the subnet mask is more than that of the CE corresponding to the disaster recovery master SBC;
based on the longest static IP matching principle, the data packet of the disaster-tolerant primary SBC is routed to the disaster-tolerant CE on the side of the disaster-tolerant SBC.
In the above scheme, the method further comprises: and configuring the address of the disaster recovery SBC on the disaster recovery CE as a down-hop address.
In the above scheme, the method further comprises: setting a disaster recovery switching control device, and storing a user IP address of a disaster-recovered main SBC and a subnet mask of a CE corresponding to the disaster-recovered main SBC in the disaster recovery switching control device;
the configuration of the user IP address and the subnet mask on the disaster recovery CE at the side of the disaster recovery SBC is as follows: and the disaster recovery switching control device is configured on the disaster recovery CE according to the user IP address and the subnet mask stored by the disaster recovery switching control device.
In the above scheme, the disaster recovery switching control device is configured with an instruction to release the disaster recovery CE;
the method further comprises the following steps: when releasing the disaster recovery CE, the disaster recovery switching control device imports a release instruction to the disaster recovery CE, and reroutes the data packet routed to the disaster recovery CE to the CE corresponding to the primary SBC before disaster recovery.
In the above scheme, the disaster recovery SBC virtualizes all SBC data corresponding to each primary SBC by configuring an SBC proxy mapping group; the SBC proxy mapping group includes at least two mapping groups, and SBC data of each active SBC corresponds to one SBC proxy mapping group.
The embodiment of the present invention further provides an SBC disaster recovery system based on the longest static IP matching, including: more than one primary SBC and CEs corresponding to the primary SBCs respectively; the system also comprises at least one disaster recovery SBC, a disaster recovery CE and a disaster recovery switching control device; wherein the content of the first and second substances,
the disaster recovery SBC is configured to virtualize all SBC data corresponding to each primary SBC;
the disaster recovery CE is configured to receive the user IP address and the subnet mask configured by the disaster recovery switching control device, and receive the data packet of the disaster-recovered primary SBC;
the disaster recovery switching control device is configured to configure a user IP address and a subnet mask on a disaster recovery CE on a side of the disaster recovery SBC when the primary SBC is subjected to disaster recovery, where the user IP address is the same as the user IP address of the disaster-recovered primary SBC, and the number of address mask bits of the subnet mask is greater than the number of address mask bits of the CE corresponding to the disaster-recovered primary SBC; based on the longest static IP matching principle, the data packet of the disaster-tolerant primary SBC is routed to the disaster-tolerant CE on the side of the disaster-tolerant SBC.
In the above solution, the disaster recovery switching control device is further configured to, according to the configured instruction for releasing the disaster recovery CE, introduce the release instruction into the disaster recovery CE when the disaster recovery CE is released, and reroute the data packet routed to the disaster recovery CE to the CE corresponding to the primary SBC before the disaster recovery.
In the above solution, the disaster recovery CE is further configured to receive a configuration in which an address of the disaster recovery SBC is used as a next hop address.
In the above solution, the disaster recovery switching control device is further configured to store the user IP address of the disaster-recovered primary SBC and the subnet mask of the CE corresponding to the disaster-recovered primary SBC; and configuring on the disaster tolerant CE according to the user IP address and the subnet mask stored by the CE.
In the above scheme, the disaster recovery SBC is specifically configured to virtualize all SBC data corresponding to each active SBC by configuring an SBC proxy mapping group; the SBC proxy mapping group includes at least two mapping groups, and SBC data of each active SBC corresponds to one SBC proxy mapping group.
The embodiment of the invention also provides a disaster recovery switching control device, which comprises a configuration module and a routing module; wherein the content of the first and second substances,
the configuration module is configured to configure a user IP address and a subnet mask on a disaster recovery CE on a side of the disaster recovery SBC, where the user IP address is the same as the user IP address of the disaster-recovered primary SBC, and the number of bits of the subnet mask is greater than the number of bits of the subnet mask of the CE corresponding to the disaster-recovered primary SBC;
and the routing module is used for routing the data packet of the disaster-tolerant primary SBC to the disaster-tolerant CE on the side of the disaster-tolerant SBC based on the longest matching principle of the static IP.
In the above solution, the disaster recovery switching control device further includes a storage module, configured to store a user IP address of the disaster-recovered primary SBC and a subnet mask of the CE corresponding to the disaster-recovered primary SBC;
correspondingly, the configuration module configures the disaster recovery CE according to the user IP address and the subnet mask stored in the storage module.
In the above solution, the disaster recovery switching control device further includes a release module, configured to introduce a release instruction to the disaster recovery CE when the disaster recovery CE is released according to the configured instruction for releasing the disaster recovery CE, and reroute the data packet routed to the disaster recovery CE to the CE corresponding to the primary SBC before the disaster recovery.
The SBC disaster recovery method, system and device based on the longest match of the static IP provided by the embodiment of the invention pre-configure at least one disaster recovery SBC, wherein the disaster recovery SBC is virtualized with all SBC data corresponding to each main SBC; when disaster recovery is performed on any one main SBC, configuring a user IP address and a subnet mask on a disaster recovery CE on the side of the disaster recovery SBC, wherein the number of address mask bits of the user IP address and the subnet mask is the same as that of the user IP address of the disaster recovery main SBC and is more than that of the address mask bit of the CE corresponding to the disaster recovery main SBC; then, based on the longest static IP matching principle, the data packet of the disaster-tolerant primary SBC can be routed to the disaster-tolerant CE on the side of the disaster-tolerant SBC. Because all SBC data corresponding to each main SBC is virtually provided on the disaster-tolerant SBC, and the subnet mask of the static route on the CE on the side of the disaster-tolerant SBC is longer than the subnet mask of the static route on the CE corresponding to the disaster-tolerant main SBC, the configuration of the static IP route on the CE on the side of the disaster-tolerant SBC is more accurate than that on the CE corresponding to the disaster-tolerant main SBC, so that based on the longest matching principle of static IP route routing, the disaster-tolerant CE only needs to be configured through the disaster-tolerant switching control device, and the data packet of the user terminal of the CE agent corresponding to the down machine or the maintained main SBC is routed to the disaster-tolerant CE, thereby realizing the disaster tolerance of the SBC. The embodiment of the invention can realize disaster tolerance without operation of professional maintainers, solves the problems of high construction cost of a disaster tolerance scheme of the boundary control equipment and large consumption of manpower and time for disaster tolerance switching, can conveniently, quickly and low-cost realize disaster tolerance switching of the SBC, and improves the accuracy, safety and reliability of the network and data.
Drawings
Fig. 1 is a schematic flow chart illustrating an implementation of a disaster recovery method based on the longest static IP matching according to an embodiment of the present invention;
fig. 2 is a schematic diagram of a structure of a disaster recovery system based on the longest static IP matching according to an embodiment of the present invention;
fig. 3 is a schematic diagram of a network topology applicable to a disaster recovery system based on the longest static IP matching according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a disaster recovery switching control device according to an embodiment of the present invention;
fig. 5 is a schematic functional diagram of an interface of a disaster recovery switching control device according to an embodiment of the present invention;
fig. 6 is a schematic view of a command structure of a disaster recovery switching control device according to an embodiment of the present invention.
Detailed Description
In the embodiment of the present invention, at least one disaster recovery SBC is configured, and the disaster recovery SBC virtualizes all SBC data corresponding to each active SBC; when disaster recovery is performed on any one main SBC, a user IP address which is the same as the user IP address of the main SBC subjected to disaster recovery and a subnet mask of which the number of address mask bits is more than that of the address mask bits of the CE corresponding to the main SBC subjected to disaster recovery are configured on the disaster recovery CE on the side of the SBC subjected to disaster recovery; based on the longest static IP matching principle, the data packet of the disaster-tolerant primary SBC is routed to the disaster-tolerant CE on the side of the disaster-tolerant SBC.
The present invention will be described in further detail with reference to the accompanying drawings and examples.
As shown in fig. 1, the SBC disaster recovery method based on the longest static IP matching in the embodiment of the present invention includes the following steps:
step S1: configuring at least one disaster recovery SBC, wherein the disaster recovery SBC is virtualized with all SBC data corresponding to each main SBC;
here, generally, by configuring one disaster recovery SBC, all SBC data corresponding to all primary SBCs in the IMS network can be virtualized.
Step S2: when disaster recovery is performed on a master SBC, a user IP address and a subnet mask are configured on a disaster recovery CE on the side of the disaster recovery SBC, wherein the user IP address is the same as the user IP address of the disaster recovery master SBC, and the number of address mask bits of the subnet mask is more than that of the CE corresponding to the disaster recovery master SBC;
here, when performing disaster recovery on any one of the active SBCs, the disaster recovery control can be implemented by each script, for example: configuring a user IP address which is the same as the user IP address of the disaster-tolerant main SBC on a preset script of the disaster-tolerant switching control device, and configuring a subnet mask which is at least one bit more than the subnet mask of the user IP address of the disaster-tolerant main SBC; among them, it is preferable to configure the most accurate subnet mask, such as 255.255.255.255 and the down-hop address;
and then, sending the configured script into the disaster recovery CE to realize disaster recovery.
Step S3: based on the longest static IP matching principle, the data packet of the disaster-tolerant primary SBC is routed to the disaster-tolerant CE on the side of the disaster-tolerant SBC;
here, according to the pre-configured script, the disaster recovery switching control device may route the data packet of the disaster-tolerant primary SBC to the disaster-tolerant CE on the side of the disaster-tolerant SBC; correspondingly, the disaster recovery CE receives the corresponding data packet according to the received script.
The SBC disaster recovery system based on the longest static IP matching applied by the embodiment of the invention comprises more than one main SBC and CEs respectively corresponding to the main SBCs; as shown in fig. 2, the system further includes at least one disaster recovery SBC21, a disaster recovery CE22, and a disaster recovery switching control device 23; wherein the content of the first and second substances,
the disaster recovery SBC21 is configured to virtualize all SBC data corresponding to each active SBC;
the disaster recovery CE22 is connected to the disaster recovery SBC21 and the disaster recovery switching control device 23, respectively, and is configured to receive the user IP address and the subnet mask configured by the disaster recovery switching control device 23 for itself, and receive the data packet of the disaster-recovered primary SBC;
the disaster recovery switching control device 23 is configured to configure a user IP address and a subnet mask on the disaster recovery CE22 on the side of the disaster recovery SBC21 when performing disaster recovery on the primary SBC, where the user IP address is the same as the user IP address of the disaster-recovered primary SBC, and the number of address mask bits of the subnet mask is greater than the number of address mask bits of the CE corresponding to the disaster-recovered primary SBC; based on the principle of longest static IP matching, the data packet of the disaster-tolerant primary SBC is routed to the disaster-tolerant CE22 on the side of the disaster-tolerant SBC 21.
In practical application, the disaster recovery SBC21 virtualizes all SBC data corresponding to each primary SBC according to the number of the primary SBCs in the current network, and virtualizes all the primary SBCs according to all the virtualized SBC data; in general, in an IMS network, one disaster recovery SBC21 may virtualize all the active SBCs.
The main SBC realizes the service by configuring an entity such as an SBC proxy mapping group or a similar function; specifically, the SBC configures a signaling address of an upper core network, a media address of the upper core network, a signaling address of a lower user side, and a media address of the lower user side of the SBC in an SBC proxy mapping group or a similar functional entity, so as to implement proxy and forwarding of the user IP packet to the core network device. Generally, only the above information of the area subscriber responsible for the SBC is configured on one active SBC, but of course, an SBC may also be configured with a plurality of different SBC proxy mapping groups or similar functional entities.
Similarly, the disaster recovery SBC1 virtualizes all SBC data of each active SBC by configuring a plurality of different SBC proxy mapping groups or similar functional entities; such as: the data of the SBC proxy mapping group a is configured consistently with the service data of the SBC proxy mapping group on the main SBC in hangzhou city on the disaster recovery SBC1 in zhejiang province, the data of the SBC proxy mapping group B is configured consistently with the service data of the SBC proxy mapping group on the main SBC in ningbo city on the disaster recovery SBC1, and so on, the service data of all the SBC proxy mapping groups of the main SBC in zhejiang city is configured, and the purpose of virtualizing all the service data of each main SBC in the IMS network in zhejiang province through the disaster recovery SBC1 can be achieved.
In practical application, the disaster recovery switching control device 23 and the disaster recovery CE22 implement routing control through scripts, specifically: when disaster recovery is performed, a script is imported to the disaster recovery CE22, and the content of the script is a routing command; accordingly, the disaster recovery CE22 changes or reconfigures the static routing IP through a script, including configuring the user IP address, subnet mask, and hop-down address on the disaster recovery CE 22. Wherein, the user IP address on the disaster recovery CE22 is the same as the user IP address of the down active SBC; the subnet mask is at least one more bit than the address mask bit number of the CE corresponding to the disaster-tolerant primary SBC; the down-hop address is the interface address of the disaster recovery SBC connected to the disaster recovery CE 22; at the same time, the script can configure the network element.
Here, the script configures the network element, for example, assuming that the script is ip route-static 221.131.194.146255.255.255.255172.16.2.2, the configuration shown is as follows: 221.131.194.146 is the user IP address configured on the primary SBC, which is the destination address; 172.16.2.2 is the address of the interface of the disaster-tolerant SBC connected to the disaster-tolerant CE 22.
As shown in fig. 3, since various router devices in the IP network are interconnected, the various router devices can automatically learn the routing information and perform the next-hop routing according to the longest matching rule of the routing, that is: when the routing information of the same IP address is configured on different router devices, other router devices can preferentially route the user information to the router device configured with the information of the subnet mask most accurate to the IP; furthermore, since various router devices connected to each other in the IP network can learn the routing information from each other, when the IP packets of the user are the same, if more accurate routing information, such as subnet mask, is configured on the disaster recovery CE22 on the side of the disaster recovery SBC21 than the CE device corresponding to the active SBC to be switched, other router devices will preferentially route the user information to the disaster recovery SBC21 through the disaster recovery CE22, and the IP address of the virtual SBC on the disaster recovery SBC21 is exactly the same as the IP address of the active SBC. The method includes the steps that information of all main SBCs needing disaster recovery is configured on a disaster recovery SBC, and specifically, an agent mapping group of all the main SBCs needing disaster recovery is duplicated; when the destination address of the data packet sent from the disaster CE22 matches the IP address in the proxy mapping group of which primary SBC, the data packet is automatically matched to the proxy mapping group; the IP addresses in the proxy mapping group of each active SBC are different and independent.
After the IP address of the user information enters the entire CMNET network, the IP address is preferentially routed to the disaster recovery CE22 corresponding to the side of the disaster recovery SBC21, so as to achieve the SBC21, thereby achieving the purpose of the disaster recovery primary SBC; in the whole CMNET network, the boundary route CE on the core network side and the boundary route AR on the user side are collectively equivalent to a local area network, and the whole is suitable for the static IP longest matching principle. For example: in a CMNET network, generally, a router device, such as an AR, closer to a user terminal than a CE device on the SBC side is used to learn to which CE device user information is most preferred. Here, the learning means learning based on the longest matching principle.
In this embodiment of the present invention, the disaster recovery switching control device 23 may include a configuration module and a routing module; the configuration module is configured to configure a user IP address and a subnet mask on a disaster recovery CE on a side of the disaster recovery SBC, where the user IP address is the same as the user IP address of the disaster recovery primary SBC, and the number of address mask bits of the subnet mask is greater than the number of address mask bits of the CE corresponding to the disaster recovery primary SBC; and the routing module is used for routing the data packet of the disaster-tolerant primary SBC to the disaster-tolerant CE on the side of the disaster-tolerant SBC based on the longest matching principle of the static IP.
The disaster recovery switching control device further comprises a storage module, which is used for storing the user IP address of the disaster-recovered main SBC and the subnet mask of the CE corresponding to the disaster-recovered main SBC;
correspondingly, the configuration module configures the disaster recovery CE according to the user IP address and the subnet mask stored in the storage module.
Referring to fig. 4, 5 and 6, the storage module 31 may include, according to different storage objects: the system comprises N user IP memory units, N user subnet mask memory units and a down-hop address memory unit, wherein the N user IP memory units, the N user subnet mask memory units and the down-hop address memory unit are respectively used for storing IP addresses, subnet masks and down-hop addresses of all users in a network and a main SBC;
the configuration module may further include: an address calling unit 32, an address scaling unit 33, an address script compiling unit 34, and an address script transmitting unit 35;
specifically, the address invoking unit 32 is configured to invoke a user IP address and a subnet mask of an SBC that needs disaster recovery when disaster recovery occurs; the address conversion unit 33 is configured to convert the called subnet mask into a binary number, and increase the number of bits of the address mask by at least one bit; the address script compiling unit 34 compiles the called user IP address, the converted subnet mask and the address of the disaster recovery SBC as the drop address into a script capable of reconfiguring the disaster recovery CE, and sends the script to the disaster recovery CE through the address script sending unit 35; thus, the user IP address and subnet mask can be configured on the disaster recovery CE on the side of the disaster recovery SBC.
Typically, the content of the script may include emergency scripts, such as ip route-static 221.131.194.144255.255.255.255172.16.2.2; a rewind script, Undo ip route-static 221.131.194.144255.255.255.255172.16.2.2;
accordingly, the preset configuration may be: a third party sends a channel configuration between the instruction platform and the disaster recovery CE which needs to execute the instruction; the channel configuration includes: the name of CE, such as ZJHZ-CMNET-IMS-CE03-HWNE 40E; the type of channel, such as telnet; interface IP address of CE, e.g., 10.71.91.172; port numbers, such as 23; and so on.
The disaster recovery switching control device 3 further includes a releasing module 36, configured to introduce a releasing instruction into the disaster recovery CE when the disaster recovery CE is released according to the configured instruction for releasing the disaster recovery CE, and reroute the data packet routed to the disaster recovery CE to the CE corresponding to the primary SBC before the disaster recovery.
In practical applications, as shown in fig. 3, assuming that the static routing IP address originally configured on each area disaster recovery CE22 is a 30-bit address mask, when switching disaster recovery, the static routing IP address configured on the disaster recovery CE22 on the side of the disaster recovery SBC21 is a 32-bit address mask, which is more accurate than the routing information configured on the CE of each area. Specific examples are as follows:
IP static routing commands configured on CE of the original SBC in the CMNET network in Hangzhou are iproute-static 221.131.194.144255.255.255.252172.16.1.1 or IP-static 221.131.194.144255.255.255.254172.16.1.1; the command indicates that the address masks of 221.131.194.144, 221.131.194.145, 221.131.194.146 and 221.131.194.147 are 30 bits or 31 bits, the next hop from the user IP packet routing to these IP addresses is 172.16.1.1, 172.16.1.1 is the user IP address of the primary SBC, and the routing CE selected by these four IP addresses is the CE corresponding to the primary SBC; by analogy, the length of the mask may be self-located as desired and is not limited to the length mentioned herein.
During disaster recovery switching, an operator imports the user IP information on the CE corresponding to the down active SBC into a script, and imports a script for changing the IP static routing onto the disaster recovery CE22 on the side of the disaster recovery SBC21 through the disaster recovery switching control device 23, where the configured IP static routing command is:
ip route-static 221.131.194.144 255.255.255.255 172.16.2.2；
ip route-static 221.131.194.145 255.255.255.255 172.16.2.2；
ip route-static 221.131.194.146 255.255.255.255 172.16.2.2；
ip route-static 221.131.194.147 255.255.255.255 172.16.2.2；
the four commands indicate that the address masks of 221.131.194.144, 221.131.194.145, 221.131.194.146 and 221.131.194.147 are 32 bits, and the next hop address of the user IP packet after passing through the disaster recovery CE22 on the disaster recovery side is 172.16.2.2, that is, the disaster recovery SBC 21; according to the longest matching principle of IP static routing, other router devices in the CMNET network, including CE and AR, will learn that the next hop of the most accurate routing for 221.131.194.144, 221.131.194.145, 221.131.194.146, 221.131.194.147 addresses is 172.16.2.2, so as to route the information of users of these IP addresses to the router device whose next hop is 172.16.2.2, i.e. to disaster SBC21 through disaster CE 22.
When disaster recovery switching is performed, after the script is issued to the disaster recovery CE on the side of the disaster recovery SBC through the disaster recovery switching control device 23, the AR device on the bottom layer learns the most accurate routing information 221.131.194.144, 221.131.194.145, 221.131.194.146, and 221.131.194.147, and preferentially routes the IP data packet sent by the subsequent user terminal to the disaster recovery CE on the side of the disaster recovery SBC, and the next-hop routing of the IP address of the user terminal is the disaster recovery SBC according to the configuration of the script on the disaster recovery CE on the side of the disaster recovery SBC, so that the IP data packet sent by the subsequent user terminal is routed to the disaster recovery SBC.
Similarly, when recovering from a disaster, a release command is introduced into the script of the disaster recovery switching control device 23, and the information of these routes on the disaster recovery CE22 on the side of the disaster recovery SBC21 is deleted, so that the user data is rerouted to the original host SBC.
When disaster recovery is performed, only the routing information of undoo on the disaster recovery CE22 is needed, and specific commands are as follows:
Undo ip route-static 221.131.194.144 255.255.255.255 172.16.2.2；
Undo ip route-static 221.131.194.145 255.255.255.255 172.16.2.2；
Undo ip route-static 221.131.194.146 255.255.255.255 172.16.2.2；
Undo ip route-static 221.131.194.147 255.255.255.255 172.16.2.2；
these disaster recovery switching scripts and disaster recovery scripts are all preset on the disaster recovery switching control device 23, and when used, the switching or recovery scripts are instructed by the keys corresponding to the disaster recovery switching control device 23 to control the disaster recovery CE.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.

Claims (13)

1. A Session Border Controller (SBC) disaster recovery method based on the longest match of static IP is characterized in that at least one disaster recovery SBC is configured, and the disaster recovery SBC is virtualized with all SBC data corresponding to each main SBC; the main SBC comprises all main SBCs in the IMS network; the method further comprises the following steps:
when the disaster recovery switching control device carries out disaster recovery on the main SBC, a script is led into the disaster recovery client side edge equipment CE at the side of the disaster recovery SBC, and a user IP address and a subnet mask are configured through the script, wherein the user IP address is the same as the user IP address of the disaster recovery main SBC, and the number of bits of the address mask of the subnet mask is more than that of the address mask of the CE corresponding to the disaster recovery main SBC;
based on the longest static IP matching principle, the data packet of the disaster-tolerant primary SBC is routed to the disaster-tolerant CE on the side of the disaster-tolerant SBC.
2. The method of claim 1, further comprising: and configuring the address of the disaster recovery SBC on the disaster recovery CE as a down-hop address.
3. The method of claim 1, further comprising: storing the user IP address of the disaster-tolerant master SBC and the subnet mask of the CE corresponding to the disaster-tolerant master SBC in the disaster-tolerant switching control device;
the configuration of the user IP address and the subnet mask on the disaster recovery CE at the side of the disaster recovery SBC is as follows: and the disaster recovery switching control device is configured on the disaster recovery CE according to the user IP address and the subnet mask stored by the disaster recovery switching control device.
4. The method according to claim 3, wherein the disaster recovery switching control device is configured with an instruction to release a disaster-tolerant CE;
the method further comprises the following steps: when releasing the disaster recovery CE, the disaster recovery switching control device imports a release instruction to the disaster recovery CE, and reroutes the data packet routed to the disaster recovery CE to the CE corresponding to the primary SBC before disaster recovery.
5. The method according to any one of claims 1 to 4, wherein the disaster-tolerant SBC virtualizes all SBC data corresponding to each active SBC by configuring an SBC proxy mapping group; the SBC proxy mapping group includes at least two mapping groups, and SBC data of each active SBC corresponds to one SBC proxy mapping group.
6. An SBC disaster recovery system based on the longest static IP matching comprises: more than one primary SBC and CEs corresponding to the primary SBCs respectively; the main SBC comprises all main SBCs in the IMS network; the system is characterized by also comprising at least one disaster recovery SBC, a disaster recovery CE and a disaster recovery switching control device; wherein the content of the first and second substances,
the disaster recovery SBC is configured to virtualize all SBC data corresponding to each primary SBC;
the disaster recovery CE is configured to receive the user IP address and the subnet mask configured by the disaster recovery switching control device, and receive the data packet of the disaster-recovered primary SBC;
the disaster recovery switching control device is configured to, when a disaster recovery is performed on the primary SBC, introduce a script into the disaster recovery CE on the side of the disaster recovery SBC, and configure a user IP address and a subnet mask through the script, where the user IP address is the same as the user IP address of the disaster-recovered primary SBC, and the number of address mask bits of the subnet mask is greater than the number of address mask bits of the CE corresponding to the disaster-recovered primary SBC; based on the longest static IP matching principle, the data packet of the disaster-tolerant primary SBC is routed to the disaster-tolerant CE on the side of the disaster-tolerant SBC.
7. The system according to claim 6, wherein the disaster recovery switching control device is further configured to, according to the configured instruction for releasing the disaster recovery CE, introduce a release instruction into the disaster recovery CE when the disaster recovery CE is released, and reroute the data packet routed to the disaster recovery CE to the CE corresponding to the active SBC before the disaster recovery.
8. The system according to claim 6, wherein said disaster recovery CE is further configured to receive a configuration of an address of a disaster recovery SBC as a drop-down address.
9. The system according to claim 6, wherein the disaster recovery switching control device is further configured to store the user IP address of the disaster-recovered primary SBC and the subnet mask of the CE corresponding to the disaster-recovered primary SBC; and configuring on the disaster tolerant CE according to the user IP address and the subnet mask stored by the CE.
10. The system according to any one of claims 6 to 9, wherein the disaster recovery SBC is specifically configured to virtualize all SBC data corresponding to each active SBC by configuring an SBC proxy mapping group; the SBC proxy mapping group includes at least two mapping groups, and SBC data of each active SBC corresponds to one SBC proxy mapping group.
11. A disaster recovery switching control device is characterized in that the disaster recovery switching control device comprises a configuration module and a routing module; wherein the content of the first and second substances,
the configuration module is configured to import a script to a disaster recovery CE on the side of the disaster recovery SBC, and configure a user IP address and a subnet mask through the script, where the user IP address is the same as the user IP address of the disaster-recovery primary SBC, and the number of address mask bits of the subnet mask is greater than the number of address mask bits of the CE corresponding to the disaster-recovery primary SBC;
and the routing module is used for routing the data packet of the disaster-tolerant primary SBC to the disaster-tolerant CE on the side of the disaster-tolerant SBC based on the longest matching principle of the static IP.
12. The apparatus according to claim 11, wherein the disaster recovery switching control apparatus further comprises a storage module, configured to store the user IP address of the disaster-recovered primary SBC and the subnet mask of the CE corresponding to the disaster-recovered primary SBC;
correspondingly, the configuration module configures the disaster recovery CE according to the user IP address and the subnet mask stored in the storage module.
13. The apparatus according to claim 11 or 12, wherein the disaster recovery switching control apparatus further includes a releasing module, configured to, according to the configured instruction for releasing the disaster recovery CE, introduce a release instruction into the disaster recovery CE when the disaster recovery CE is released, and reroute the data packet routed to the disaster recovery CE to the CE corresponding to the active SBC before the disaster recovery.
CN201510796111.2A 2015-11-18 2015-11-18 SBC disaster recovery method, system and device based on static IP longest match Active CN106713134B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201510796111.2A CN106713134B (en) 2015-11-18 2015-11-18 SBC disaster recovery method, system and device based on static IP longest match

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201510796111.2A CN106713134B (en) 2015-11-18 2015-11-18 SBC disaster recovery method, system and device based on static IP longest match

Publications (2)

Publication Number Publication Date
CN106713134A CN106713134A (en) 2017-05-24
CN106713134B true CN106713134B (en) 2020-06-09

Family

ID=58932670

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201510796111.2A Active CN106713134B (en) 2015-11-18 2015-11-18 SBC disaster recovery method, system and device based on static IP longest match

Country Status (1)

Country Link
CN (1) CN106713134B (en)

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100592716C (en) * 2007-09-26 2010-02-24 上海市信息网络有限公司 Method for completing circuit switch-over based on the longest address matching in ATM network
US8958282B2 (en) * 2009-12-10 2015-02-17 Verizon Patent And Licensing Inc. 1-for-N redundancy in private IP session border control networks
CN102664788B (en) * 2012-04-05 2015-07-22 中兴通讯股份有限公司 CE dual-homed link protection method in MPLS L3VPN and system thereof
CN102752209B (en) * 2012-07-09 2015-09-02 杭州华三通信技术有限公司 Realize address fast switch over method and the routing forwarding equipment of backup services
CN102932230B (en) * 2012-11-21 2015-07-15 杭州华三通信技术有限公司 Method and device for virtual router redundancy protocol backup group issuing routing
CN104717083B (en) * 2013-12-13 2018-06-26 中国移动通信集团上海有限公司 A kind of disaster tolerance switching system, the method and device of A-SBC equipment
CN104184611A (en) * 2014-07-24 2014-12-03 华为技术有限公司 Disaster tolerance site, and service message processing device and method

Also Published As

Publication number Publication date
CN106713134A (en) 2017-05-24

Similar Documents

Publication Publication Date Title
US8730793B2 (en) Method and apparatus providing network redundancy and high availability to remote network nodes
US9485172B2 (en) Data transmitting device, data transmitting method and non-transitory computer-readable storage medium
US20200169433A1 (en) Logical Router Comprising Disaggregated Network Elements
CN107078951A (en) From virtual port channel peer-to-peer fault recovery
Nguyen et al. A software-defined networking approach for disaster-resilient WANs
RU2612599C1 (en) Control device, communication system, method for controlling switches and program
CN101286922B (en) Signalling control method, system and apparatus
JP6008801B2 (en) Transmission system, transmission method, and transmission apparatus
CN104468368B (en) Configure the method and device of bgp neighbor
Kitsuwan et al. Independent transient plane design for protection in OpenFlow-based networks
CN110417665B (en) EVPN networking system and method for multiple Fabric scenes of data center
WO2016034127A1 (en) System and method for achieving dual-node interconnection pseudo-wire
CN102611618A (en) Route protection converting method and device
US20210176172A1 (en) Packet forwarding method, device and apparatus, and storage medium
CN101262407B (en) A method for virtual router to establish tunnel
CN103581025A (en) Method and system for processing routing information and equipment
CN108023800A (en) A kind of guard method of LTE bearer networks and device
CN102143060A (en) Method and device for building primary pseudowire and spare pseudowire
US11303701B2 (en) Handling failure at logical routers
CN104702498A (en) Method and device for reducing the number of optical connections through coordination protection
Sato et al. Deployment of OpenFlow/SDN technologies to carrier services
CN106713134B (en) SBC disaster recovery method, system and device based on static IP longest match
CN106209634B (en) Learning method and device of address mapping relation
JP6402078B2 (en) Network system and packet transfer method
CN109688062B (en) Routing method and routing equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant