CN116260796A

CN116260796A - Service disaster recovery method and device

Info

Publication number: CN116260796A
Application number: CN202111506951.2A
Authority: CN
Inventors: 任中岗
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Group Shandong Co Ltd
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Group Shandong Co Ltd
Priority date: 2021-12-10
Filing date: 2021-12-10
Publication date: 2023-06-13

Abstract

The embodiment of the invention provides a service disaster recovery method and a device, wherein in the method, first route information from an S-CSCF to a first target ISBC is acquired; transmitting the call request to a first SIP call center node corresponding to the first target ISBC through the first target ISBC; receiving fault information of the first target ISBC to the first SIP call center node; acquiring second routing information from the S-CSCF to a second target ISBC; transmitting the call request to a second SIP call center node corresponding to the second target ISBC through the second target ISBC; receiving fault information of the second target ISBC to the second SIP call center node; and the call request is jumped to the CS domain call center node through the MGCF. Thus, the problem of call service interruption caused by faults is avoided, and the call success rate is effectively improved.

Description

Service disaster recovery method and device

[ field of technology ]

The present invention relates to the field of communications, and in particular, to a service disaster recovery method and apparatus.

[ background Art ]

The IMS (IP Multimedia Subsystem, IP multimedia system) is used as a network architecture which is based on IP packet transmission and is irrelevant to access, and can realize fixed-mobile fusion, multi-service fusion of voice, data, video and the like, and fusion of IT and CT. The IMS converged communication product, however, may also present some problems while providing a rich multimedia service (e.g., voice) experience for the user.

The SIP (Session Initiation Protocol ) call center accessing IMS domain is called, S-CSCF initiates NAPTR, SRV and A query to ENUMDNS, returns the address of core side ISBC (Session Border Controller, session boundary controller), S-CSCF routes the call to SIP call center through ISBC. If the SIP call center fails or the ISBC fails the route analysis due to the local data configuration, the S-CSCF cannot perceive it. So the IMS core network still sends every subsequent call to the ISBC, the core side ISBC returns an error (assuming that 500 is wrong), and after receiving the 500 is wrong, the calling terminal determines that the call fails or the CS (Circuit Switched) domain drops to initiate the call.

Therefore, how to dredge the service by other ways under the condition that one or a plurality of ISBC (integrated service control blocks) fail to all call centers, so that the service is not affected, and the important problem to be solved is urgently needed at present.

[ invention ]

The embodiment of the invention provides a method and a device for realizing service disaster recovery, which effectively improve the success rate of calling.

In a first aspect, an embodiment of the present invention provides a service disaster recovery method, which is applied to a service call session control network element S-CSCF in an IMS domain, where the S-CSCF is disposed in a service disaster recovery system, and the service disaster recovery system further includes: the method comprises the steps of calling terminals, at least two session border controllers (ISBC) and SIP call center nodes corresponding to each ISBC, wherein the method comprises the following steps: acquiring first route information from the S-CSCF to a first target ISBC; transmitting the call request to the first target ISBC so that the call request is transmitted to a first SIP call center node corresponding to the first target ISBC, wherein the first SIP call center node is one of all SIP call center nodes connected with the first target ISBC;

Receiving fault information of the first target ISBC to the first SIP call center node; acquiring second routing information from the S-CSCF to a second target ISBC; and sending the call request to the second target ISBC corresponding to the second target ISBC so as to enable the call request to be sent to a second SIP call center node, wherein the second SIP call center node is one of all SIP call center nodes connected with the second target ISBC.

In the embodiment of the invention, under the condition that a plurality of ISBCs are interconnected with the SIP call center node, if one or a plurality of ISBCs fail to the call center, the S-CSCF can dredge the call through other normal ISBCs, complete the call, ensure that the service is not influenced, and simultaneously control the call simply and conveniently.

In one possible implementation manner, the CSCF presets a routing table, where the routing table stores routing information from the S-CSCF to the ISBC and then to the target SIP call center node, and the obtaining the first routing information from the S-CSCF to the ISBC includes: and inquiring the preset routing table according to the call request, and acquiring the first routing information, wherein the first routing information comprises the routing information from the S-CSCF to the first target ISBC.

In one possible implementation manner, the acquiring the first routing information from the S-CSCF to the ISBC further includes: when the first routing information is not queried in the preset routing table, generating first routing information from the S-CSCF to the first target ISBC;

the method further comprises the steps of: and adding the first routing information to the preset routing table.

In one possible implementation manner, the service disaster recovery system further includes: the media gateway controls a network element (MGCF), the MGCF is directly or indirectly connected with a circuit CS domain call center node, disaster recovery route information for jumping to the CS domain via the MGCF is set in the preset route table, and the method further comprises: receiving fault information fed back by the second target ISBC; inquiring a preset routing table to obtain third routing information, wherein the third routing information comprises disaster recovery routing information for jumping the call request to the CS domain through the MGCF; and sending the call request to the MGCF, so that the call request is sent to the circuit CS domain call center node through the MGCF.

In one possible implementation manner, the S-CSCF presets a white list of the called party, and the called party of the disaster recovery routing information is the called party corresponding to the white list.

In one possible implementation manner, the preset routing table includes state information corresponding to each piece of routing information, where the state information is used to characterize that the routing state is failure or normal or disaster recovery, and the aging time corresponding to the routing information in which the state information is failure or disaster recovery is 0.

In a second aspect, an embodiment of the present invention provides a service disaster recovery device, configured for a service call session control network element S-CSCF in an IMS domain, where the S-CSCF is disposed in a service disaster recovery system, where the service disaster recovery system further includes: a calling terminal, at least two session border controllers, ISBC, and a SIP call center node corresponding to each ISBC, the apparatus includes:

the acquisition module is used for: the method comprises the steps of acquiring first routing information from the S-CSCF to a first target ISBC; and a sending module: the method comprises the steps of sending the call request to a first target ISBC, so that the call request is sent to a first SIP call center node corresponding to the first target ISBC, wherein the first SIP call center node is one of all SIP call center nodes connected with the first target ISBC; a receiving module, configured to receive failure information from the first target ISBC to the first SIP call center node; the acquisition module is further used for acquiring second routing information from the S-CSCF to a second target ISBC; the sending module is further configured to send the call request to the second target ISBC, so that the call request is sent to a second SIP call center node corresponding to the second target ISBC, where the second SIP call center node is one of all SIP call center nodes connected to the second target ISBC.

In one possible implementation manner, the S-CSCF presets a routing table, where the routing table stores routing information from the S-CSCF to the ISBC and then to the target SIP call center node, and the obtaining module includes: and a query sub-module: the routing table is used for inquiring the preset routing table according to the call request; and (3) an acquisition sub-module: and the first routing information is used for acquiring the first routing information, and the first routing information comprises the routing information from the S-CSCF to the first target ISBC.

In one possible implementation manner, the acquiring module further includes: a generating sub-module, configured to generate first routing information from the S-CSCF to the first target ISBC when the first routing information is not queried in the preset routing table;

the apparatus further comprises: and the adding module is used for adding the first routing information to the preset routing table.

In one possible implementation manner, the service disaster recovery system further includes: the media gateway controls a network element (MGCF), the MGCF is directly or indirectly connected with a circuit CS domain call center node, disaster recovery route information for jumping to the CS domain via the MGCF is set in the preset route table, and the device further comprises:

The receiving module is used for receiving the fault information fed back by the second target ISBC; the obtaining module is further configured to query a preset routing table to obtain third routing information, where the third routing information includes disaster recovery routing information for skipping the call request to the CS domain via the MGCF; the sending module is configured to send the call request to the MGCF, so that the call request is sent to the circuit CS domain call center node through the MGCF.

In a third aspect, an embodiment of the present invention provides a service disaster recovery system, including at least one processor, and at least one memory communicatively connected to the processor, where: the memory stores program instructions executable by the processor, the processor invoking the program instructions capable of performing the method provided in the first aspect.

In a fourth aspect, embodiments of the present invention provide a non-transitory computer-readable storage medium storing computer instructions that cause a computer to perform the method provided in the first aspect.

It should be understood that, the second to fourth aspects of the embodiments of the present application are consistent with the technical solutions of the first aspect of the embodiments of the present application, and the beneficial effects obtained by each aspect and the corresponding possible implementation manner are similar, and are not repeated.

[ description of the drawings ]

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a diagram of a network topology according to an embodiment of the present invention;

FIG. 2 is a schematic diagram of a prior art failure scenario I in an embodiment of the present invention;

FIG. 3 is a flow chart of a first prior art failure scenario in an embodiment of the present invention;

FIG. 4 is a schematic diagram of a scenario of a prior art failure scenario two in an embodiment of the present invention;

FIG. 5 is a flow chart of a business disaster recovery method according to an embodiment of the present invention;

FIG. 6 is a schematic diagram of a business improvement flow in an embodiment of the present invention;

FIG. 7 is a schematic diagram of an ISBC detection flow in accordance with an embodiment of the present invention;

FIG. 8 is a schematic diagram of a service disaster recovery device according to an embodiment of the present invention;

fig. 9 is a schematic structural diagram of a service disaster recovery system according to an embodiment of the present invention.

[ detailed description ] of the invention

In order to make the objects, technical solutions and advantages of the embodiments of the present invention more clear, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. It will be apparent that the described embodiments are some, but not all, embodiments of the invention. Other embodiments, which are derived from the described embodiments of the invention by a person skilled in the art, are within the scope of the invention.

The embodiment of the invention can be applied to voice communication service, and the most important characteristic of the voice communication service is to ensure the accuracy, reliability and timeliness of service communication. The embodiment of the invention automatically dredges the call when the call service fails, ensures that the service is not affected, further reduces the problem of service hysteresis caused by the failure in the call process, and improves the instantaneity of the call service.

With the progress and development of networks, at present, communication networks are divided into two types, namely a mobile network and a fixed network, and in the development process, the technology transformation of the third generation of 2G, 3G and 4G is experienced, and the 5G era is currently going to. Conventional 2G, 3G, etc. expose a number of drawbacks such as: qoS (Quality of Service ) guarantees cannot be provided, etc., IMS (IP Multimedia Subsystem, IP multimedia system) is a product of the convergence of the internet with cellular mobile communication networks. IMS is a new form of multimedia service that can meet the needs of more novel and diversified multimedia services for end users. IMS is considered as a core technology of a new generation network, and is also an important way to solve the problem of integration of mobile and fixed networks and introduce differentiated services such as triple integration of voice, data and video. The S-CSCF (Serving-CSCF) is the core of IMS domain, and is attached to the registration authentication, session control and service triggering of the terminal.

When we use the mobile phone to make a call anytime and anywhere, it is CS (Circuit Switching Domain, circuit switched) network that provides call services to us. When we talk through the CS network, the CS network can allocate a fixed channel for both parties of the talk, and in the whole talk process, we can occupy the dedicated channel all the time, and other people can not occupy the dedicated channel any more. At the end of the call, the CS network releases the one channel for the next allocation to other users for the call. The circuit switched CS domain is a technology used in TDM time slot switching, and is generally used for 2G and 3G telephony voice services and video telephony services.

Referring to fig. 1, in the present technical solution, a calling terminal initiates a call request, a SIP call center node accessing an IMS domain is called, an S-CSCF initiates NAPTR, SRV and a query to an ENUMDNS, returns an address of an ISBC on a core side, and generates a routing table, and the S-CSCF routes a call to the SIP call center node through the ISBC.

If the SIP call center node fails or the ISBC fails the route analysis due to the local data configuration, the S-CSCF cannot perceive it. So the IMS core network still sends the following calls to ISBC, the core side ISBC returns 500 errors, and the calling terminal judges the call failure after receiving 500 errors. That is, in the prior art, when a call request fails, either the call is directly determined to fail or the call is dropped back to the low-level 2G network to make a call again, both of which may cause a service terminal or service delay.

Referring to fig. 2 and 3, the calling terminal initiates a call request, at this time, the S-CSCF obtains the ISBC-1 and ISBC-2 addresses by querying through NAPTR, SRV and a, and the S-CSCF sends the call request to the SIP call center node through the ISBC-1, but the lines between the ISBC-1 and the SIP call center node 2 are all interrupted, and since the S-CSCF cannot perceive the fault message, the call request still will be sent to the ISBC-1. The ISBC-1 judges that the line between the SIP call center node 1 and the SIP call center node 2 is totally interrupted, returns 500 mistakes to the S-CSCF, and the S-CSCF returns 500 mistakes to the calling terminal. Since in the current state of the art the S-CSCF does not choose to send the call to the SIP call centre node through ISBC-2 after the path through ISBC-1 to the SIP call centre node has been interrupted.

Referring to fig. 4, the calling terminal initiates a call request, and ISBC-1 and ISBC-2 are all interrupted with SIP call center node 1 and SIP call center node 2, and as S-CSCF is not aware, there is still a call request sent to ISBC-1 and ISBC-2.ISBC-1/ISBC-2 judges that all the

call center nodes

1 and 2 are interrupted, returns 500 errors to S-CSCF, and S-CSCF returns 500 errors to the calling terminal. Since in the current prior art, after all paths from ISBC-1/ISBC-2 to the SIP call center are broken, the S-CSCF does not choose to unblock the call through the circuit domain, i.e., does not choose the CS domain.

In view of the above problems, embodiments of the present invention provide a service disaster recovery method and system, by which, in the case that there are multiple ISBC and SIP call center nodes interconnected, if one or several ISBC fails to the SIP call center node, the S-CSCF dredges the call through other normal ISBC, so that the service is not affected; or under the condition that all ISBC to SIP call center nodes are totally failed, if a disaster recovery node of the call center node exists in a CS domain, the S-CSCF automatically dredges the service to the disaster recovery node without manual intervention.

Referring to fig. 5, fig. 5 is a flow chart of a service disaster recovery method provided by an embodiment of the present invention, where the service disaster recovery method is applied to a service call session control network element S-CSCF in an IMS domain, and the service call session control network element S-CSCF is disposed in a service disaster recovery system, and the service disaster recovery system further includes: the system comprises a calling terminal, at least two session border controllers (ISBC) and a Session Initiation Protocol (SIP) call center node corresponding to each ISBC. The call service is automatically dredged through the S-CSCF, the real-time performance of the call service is ensured, and the service disaster recovery method comprises the following steps:

step S101: acquiring first route information from the S-CSCF to a first target ISBC;

step S102: transmitting the call request to the first target ISBC so as to enable the call request to be transmitted to a first SIP call center node corresponding to the first target ISBC;

step S103: receiving fault information of the first target ISBC to the first SIP call center node;

step S104: acquiring second routing information from the S-CSCF to a second target ISBC;

step S105: and sending the call request to the second target ISBC so as to enable the call request to be sent to a second SIP call center node corresponding to the second target ISBC.

According to the service disaster recovery method provided by the embodiment of the invention, the S-CSCF automatically dredges the call service, and when the first target ISBC fails to all SIP call center nodes, the second target ISBC is automatically selected for dredging, so that the instantaneity of the call service is ensured, and the call service is not influenced by the failure.

In some preferred embodiments of the invention, the calling terminal initiates a call request, and the called party is a SIP call center node accessing the IMS domain, for example: the number crown of the called party is 95ABC, the S-CSCF of the calling side initiates NAPTR, SRV and A query to the ENUM, obtains the IP addresses of ISBC-1 and ISBC-2, and then generates corresponding routing information. Assuming that the address of ISBC-1 is IP1 and the address of ISBC-2 is IP2, comparing the corresponding relation between the word crown and the address with a preset routing table according to a caching rule.

Referring to table 1, if the obtained routing information of ISBC-1 and ISBC-2 already exists in the preset routing table, the preset routing table is queried according to the "prefix", if there are multiple records, the routing record with the highest priority in the record with the "normal" matching state is matched, if the matched routing record is multiple, one of the routing records is randomly selected or the routing with the highest weight is selected according to the weight value. The ISBC-1, S-CSCF, which randomly selects 95ABC+IP1, sends the call request to ISBC-1 such that the call request is sent to a first SIP call center node corresponding to the ISBC-1, wherein the first SIP call center node is one of all the SIP call center nodes to which the ISBC-1 is connected. In the embodiment of the present invention, the first SIP call center node is a call center node 1 or a call center node 2.

Table 1 CSCF routing table

Referring to fig. 6, when ISBC-1 detects all failures between call center node 1 and call center node 2, the failures include: ISBC-1 to call center node 1 and call center node 2. Since the S-CSCF is unaware that the call will still be sent to ISBC-1, ISBC-1 finds that the call should be sent to SIP call center node 1 or SIP call center node 2 by analyzing the called number 95ABC, and since these two nodes have failed, ISBC-1 replies 404 an error message to the S-CSCF and carries the reason: route failure or next hop unreachable.

After receiving the error message fed back by the ISBC-1, the S-CSCF sets the routing state to the ISBC-1 in the routing table as 'fault', and sets the aging time as '0'. The routing table is re-queried according to the word crown '95 ABC', and the routing record with higher priority in the records with the other states of normal is selected according to the state and the priority of the returned record, namely: 95abc+ip2 ISBC-2. The S-CSCF sends the call request to the ISBC-2 so that the call request is sent to a second SIP call center node corresponding to the ISBC-2, wherein the second SIP call center node is one of all the SIP call center nodes connected with the ISBC-2. In the embodiment of the present invention, the second SIP call center node is a call center node 1 or a call center node 2.

The S-CSCF sends a SUBSCRIBER subscription message to the ISBC-1 while selecting the ISBC-2 to send a call request, wherein the SUBSCRIBER subscription message carries a prefix "95ABC", and when the ISBC-1 detects that the next hop of the route analysis of the "95ABC" is reachable, the S-CSCF is informed to set the ISBC-1 record corresponding to the prefix as a normal state. Calls for this crown in subsequent call flows may be forwarded to the SIP call center node through ISBC-1.

Under the condition that a plurality of ISBCs are interconnected with the SIP call center node, if one or a plurality of ISBCs fail to the call center node, the S-CSCF can dredge the call through other normal ISBCs, so that the call service is not affected by the failure.

The S-CSCF presets a routing table, the routing table stores routing information from the S-CSCF to the ISBC and then to the target SIP call center node, and the obtaining the first routing information from the S-CSCF to the ISBC comprises the following steps: and inquiring the preset routing table according to the call request, and acquiring the first routing information, wherein the first routing information comprises the routing information from the S-CSCF to the first target ISBC.

In some preferred embodiments of the present invention, the S-CSCF initiates NAPTR, SRV and a queries to ENUM, obtains routing information for the ISBC to which the S-CSCF sends the call request, the routing information comprising: route number, called number word crown, ISBC address information, ISBC priority, ISBC status information, and aging time of the ISBC routing information, as shown in table 1 above. After the S-CSCF obtains the routing information of the ISBC-1, the S-CSCF judges whether 95ABC can be sent to the SIP call center node through the ISBC-1 according to the call number word crown information sent by the S-CSCF. Then, according to the obtained priority information, selecting one ISBC-1 route with a normal state and a high priority, wherein the route information comprises the route information from S-CSCF to ISBC1, and the method comprises the following steps: the number is 1, the prefix is 95ABC, the address is IP1, the priority is 1, the state is normal, and the aging time is 600s.

Acquiring first routing information from the S-CSCF to the ISBC, and further comprising: when the first routing information is not queried in the preset routing table, generating first routing information from the S-CSCF to the first target ISBC; the method further comprises the steps of: and adding the first routing information to the preset routing table.

In some preferred embodiments of the invention, the calling terminal initiates a call request, and the called party is a SIP call center node that is accessed in the IMS domain, for example: the number crown of the called party is 95ABC, and the S-CSCF of the calling side initiates NAPTR, SRV and A inquiry to the ENUM to acquire the IP addresses of ISBC-4 and ISBC-5. Assuming that the address of ISBC-4 is IP4 and the address of ISBC-5 is IP5, comparing the corresponding relation between the word crown and the address with a preset routing table according to a cache rule.

If the obtained routing information of the ISBC-4 and the ISBC-5 does not exist in the preset routing table, the routing information from the S-CSCF to the ISBC-4 and the ISBC-5 needs to be generated, and the routing information of the ISBC-4 and the ISBC-5 is automatically added into the preset routing table. As shown in table 2 below:

table 2S-CSCF routing table

Numbering device

Word crown

Address of

Priority level

Status of

Aging time

1

95ABC

IP1

1

Normal state

600s

2

95ABC

IP2

1

Normal state

600s

3

95ABC

IP3

65535

Normal state

0 (non-aging)

4

95ABC

IP4

1

Normal state

600s

5

95ABC

IP5

1

Normal state

600s

The service disaster recovery system further comprises: the media gateway controls a network element MGCF, which is a gateway enabling communication between IMS users and CS users. Call control signaling from the CS user to the IMS user is directed to the MGCF, which is responsible for protocol conversion between the ISDN user part or bearer independent call control and the SIP protocol and forwarding the session to the IMS. Similarly, all IMS-side user initiated sessions to CS-side users go through MGCF.

The MGCF is connected with the call center node of the circuit CS domain, the preset routing table is provided with disaster recovery routing information for jumping to the CS domain through the MGCF, and the method further comprises the following steps: receiving fault information fed back by the second target ISBC; inquiring a preset routing table to obtain third routing information, wherein the third routing information comprises disaster recovery routing information for jumping the call request to the CS domain through the MGCF; and sending the call request to the MGCF, so that the call request is sent to the circuit CS domain call center node through the MGCF.

In some preferred embodiments of the present invention, if the SIP call center node has a disaster recovery platform in the CS domain, in the case of a complete failure of the IMS domain route, the call may be routed to the CS domain for connection through the MGCF with an address of IP 3. The MGCF route information is disaster tolerant data route, the disaster tolerant data is static data with lowest priority, the rest data is dynamic data, the static data needs to be manually configured, and the dynamic data system can be automatically maintained.

Under the condition that all ISBC to SIP call center nodes are in full fault, if a disaster recovery node of the call center exists in a CS domain, the S-CSCF automatically dredges the service to the disaster recovery node without manual intervention.

In order to avoid the problem that the data volume is too huge caused by maintaining the routing table for all the crowns by the S-CSCF, the S-CSCF can set a white list, and disaster recovery is carried out by adopting the method for some specific crowns.

The S-CSCF presets a called party white list, and the called party of the disaster recovery routing information is the called party corresponding to the white list.

In some preferred embodiments of the present invention, as shown in table 3 below, the calling terminal initiates a call "95ABC", when all the ISBC to SIP call center node paths of the IMS domain fail, since "95ABC" exists in the white list, indicating that "95ABC" exists in the CS domain as a disaster tolerant platform, the S-CSCF may send a call request to the MGCF so that the call request is sent to the CS domain call center node through the MGCF. When the calling terminal initiates a call of 96ABC, when all paths from ISBC to SIP call center nodes in IMS domain are totally failed, the 96ABC is not in white list, which means that 96ABC has no disaster tolerant platform in CS domain, and the call request can not be sent to CS domain call center nodes through MGCF, at this time, 96ABC call fails. But if late "96ABC" has disaster recovery requirements, it can be added to the whitelist by manual configuration.

TABLE 3 white list

Numbering device	Word crown
			1	95ABC
2	96ABC
		3	95XYZ

The crowns with disaster tolerance service requirements are manually added into the white list, the crowns without disaster tolerance service requirements are not required to be added, and the control is carried out through the white list, so that the method is simple and convenient.

The preset routing table comprises state information corresponding to each piece of routing information, the state information is used for representing that the routing state is fault or normal or disaster tolerance, and the aging time corresponding to the routing information of which the state information is fault or disaster tolerance is 0.

In some preferred embodiments of the invention, the aging time in the routing information corresponds to the routing state. When the routing state is normal, the aging time is a normal value, generally 600s; when the routing state is a fault, the aging time is set to 0; when the routing state is disaster recovery, the aging time is set to 0. The disaster recovery route is added manually, and the state of the disaster recovery route is permanent disaster recovery. The system can automatically maintain the dynamic record data with the state of normal, and the system can automatically delete the dynamic record data after the aging time is reached, and the system can not automatically delete the dynamic record data with the state of fault.

The aging time in the routing information varies with the routing state, for example: when ISBC-1 detects all failures to call center node 1 and call center node 2, ISBC-1 replies 404 an error message to S-CSCF and carries the reason: route failure or next hop unreachable. After receiving 404 the error, S-CSCF updates the routing table, sets the state of the record of ISBC-1 corresponding to '95 ABC' in the routing table as 'failure', and correspondingly changes the aging time from '600S' to '0'. When ISBC-1 detects that the call to SIP call center node 1 or SIP call center node 2 is reachable, phase S-CSCF sends NOTIFY message and carries a prefix of '95 ABC', and informs S-CSCF that subsequent calls aiming at '95 ABC' can be sent to ISBC-1. The S-CSCF updates the routing table, updates the state from 'failure' to 'normal', updates the aging time to 600S as a normal value, changes the record from 'failure' state to 'normal' state, and is automatically deleted by the system after the aging time is reached.

Referring to fig. 7, in order to avoid the situation that after the ISBC-1 detects that the SIP call center node 1 or the SIP call center node 2 is reachable, a NOTIFY message is not sent to the S-CSCF, the S-CSCF may send a request message to the ISBC in the "failure" state in each aging period, and carry a prefix "95ABC", ask whether the next hop of the prefix route analysis is reachable, and if so, reply the detection result to the S-CSCF, and the S-CSCF updates the local routing table.

After the SIP call center node is detected to be reachable in real time through the fault ISBC, the S-CSCF updates the routing table, so that the real-time performance of service communication is ensured.

Referring to fig. 8, the embodiment shown in fig. 8 further provides a technical solution for implementing the above-mentioned method embodiment, where in the embodiment of the present invention, the service disaster recovery device includes: a sending module 801, an obtaining module 802, a receiving module 803, and an adding module 804; wherein, the acquiring module 802 is configured to acquire first routing information from the S-CSCF to a first target ISBC; a sending module 801, configured to send the call request to the first target ISBC, so that the call request is sent to a first SIP call center node corresponding to the first target ISBC, where the first SIP call center node is one of all SIP call center nodes connected to the first target ISBC; a receiving module 803, configured to receive failure information from the first target ISBC to the first SIP call center node; the acquiring module 802 is further configured to acquire second routing information from the S-CSCF to a second target ISBC; the sending module 801 is further configured to send the call request to the second target ISBC, so that the call request is sent to a second SIP call center node corresponding to the second target ISBC, where the second SIP call center node is one of all SIP call center nodes connected to the second target ISBC.

In an alternative manner, the acquiring module includes: and a query sub-module: the routing table is used for inquiring the preset routing table according to the call request; and (3) an acquisition sub-module: and the first routing information is used for acquiring the first routing information, and the first routing information comprises the routing information from the S-CSCF to the first target ISBC.

In an alternative manner, the acquiring module further includes: and the generating sub-module is used for generating the first routing information from the S-CSCF to the first target ISBC when the first routing information is not queried in the preset routing table.

In an alternative, the apparatus further comprises: the receiving module is used for receiving the fault information fed back by the second target ISBC; the obtaining module is further configured to query a preset routing table to obtain third routing information, where the third routing information includes disaster recovery routing information for skipping the call request to the CS domain via the MGCF; the sending module is configured to send the call request to the MGCF, so that the call request is sent to the circuit CS domain call center node through the MGCF.

Fig. 9 is a schematic structural diagram of a service disaster recovery system provided by an embodiment of the present invention, where the service disaster recovery system 900 includes a processor 901, a memory 902, and a computer program stored in the memory 902 and capable of running on the processor 901, where the steps in the foregoing method embodiments are implemented when the processor 901 executes the program, and the electronic terminal device provided by the embodiment may be used to execute the technical solutions of the foregoing method embodiments, and the principle and technical effects of the implementation may be further referred to the related descriptions in the method embodiments and are not repeated herein.

The embodiment of the invention provides a non-transitory computer readable storage medium, which stores computer instructions for causing a computer to execute a service disaster recovery method provided by the embodiments shown in fig. 5 to 7 of the specification.

The non-transitory computer readable storage media described above may employ any combination of one or more computer readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (erasable programmable read only memory, EPROM) or flash memory, an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

The computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, radio Frequency (RF), etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for the present specification may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a local area network (local area network, LAN) or a wide area network (wide area network, WAN), or may be connected to an external computer (e.g., connected via the internet using an internet service provider).

The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present specification. In this specification, schematic representations of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.

Furthermore, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include at least one such feature. In the description of the present specification, the meaning of "plurality" means at least two, for example, two, three, etc., unless explicitly defined otherwise.

Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and additional implementations are included within the scope of the preferred embodiment of the present specification in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the embodiments of the present specification.

Depending on the context, the word "if" as used herein may be interpreted as "at … …" or "at … …" or "in response to a determination" or "in response to detection". Similarly, the phrase "if determined" or "if detected (stated condition or event)" may be interpreted as "when determined" or "in response to determination" or "when detected (stated condition or event)" or "in response to detection (stated condition or event), depending on the context.

It should be noted that, the terminals according to the embodiments of the present invention may include, but are not limited to, a personal computer (persona l computer, PC), a personal digital assistant (persona l d igita l ass i stant, PDA), a wireless handheld device, a tablet computer (tab l et computer), a mobile phone, an MP3 player, an MP4 player, and the like.

In the several embodiments provided in this specification, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some interface, indirect coupling or communication connection of devices or units, electrical, mechanical, or other form.

In addition, each functional unit in each embodiment of the present specification may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in hardware plus software functional units.

The integrated units implemented in the form of software functional units described above may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium, and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) to perform part of the steps of the methods described in the embodiments of the present specification. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a read-only memory (ROM), a random-access memory (RAM), a magnetic disk, or an optical disk, etc.

The foregoing description of the preferred embodiments is provided for the purpose of illustration only, and is not intended to limit the scope of the disclosure, since any modifications, equivalents, improvements, etc. that fall within the spirit and principles of the disclosure are intended to be included within the scope of the disclosure.

Claims

1. The service disaster recovery method is characterized in that the service call session control network element S-CSCF applied to the IMS domain is arranged in a service disaster recovery system, and the service disaster recovery system further comprises: the method comprises the steps of calling terminals, at least two session border controllers (ISBC) and SIP call center nodes corresponding to each ISBC, wherein the method comprises the following steps:

Acquiring first route information from the S-CSCF to a first target ISBC;

sending the call request to the first target ISBC so as to enable the call request to be sent to a first SIP call center node corresponding to the first target ISBC, wherein the first SIP call center node is one of all SIP call center nodes connected with the first target ISBC;

receiving fault information of the first target ISBC to the first SIP call center node;

acquiring second routing information from the S-CSCF to a second target ISBC;

and sending the call request to the second target ISBC so as to enable the call request to be sent to a second SIP call center node corresponding to the second target ISBC, wherein the second SIP call center node is one of all SIP call center nodes connected with the second target ISBC.

2. The method of claim 1, wherein the S-CSCF presets a routing table, the routing table storing routing information of the S-CSCF to the ISBC and to the destination SIP call center node, the obtaining the first routing information of the S-CSCF to the ISBC comprising:

And inquiring the preset routing table according to the call request, and acquiring the first routing information, wherein the first routing information comprises the routing information from the S-CSCF to the first target ISBC.

3. The method of claim 2, wherein the obtaining the first routing information of the S-CSCF to the ISBC further comprises:

when the first routing information is not queried in the preset routing table, generating first routing information from the S-CSCF to the first target ISBC;

the method further comprises the steps of:

and adding the first routing information to the preset routing table.

4. A method according to any one of claims 1-3, wherein the service disaster recovery system further comprises: the media gateway controls a network element (MGCF), the MGCF is directly or indirectly connected with a circuit CS domain call center node, disaster recovery route information for jumping to the CS domain via the MGCF is set in the preset route table, and the method further comprises:

receiving fault information fed back by the second target ISBC;

inquiring a preset routing table to obtain third routing information, wherein the third routing information comprises disaster recovery routing information for jumping the call request to the CS domain through the MGCF;

And sending the call request to the MGCF, so that the call request is sent to the circuit CS domain call center node through the MGCF.

5. The method according to claim 4, wherein the S-CSCF presets a white list of called parties, and the called party of the disaster tolerant routing information is the called party corresponding to the white list.

6. The method of claim 4, wherein the preset routing table includes status information corresponding to each piece of routing information, the status information is used for representing that the routing status is failure or normal or disaster recovery, and the aging time corresponding to the routing information of which the status information is failure or disaster recovery is 0.

7. The service disaster recovery device is characterized in that the service call session control network element S-CSCF applied to an IMS domain is arranged in a service disaster recovery system, and the service disaster recovery system further comprises: a calling terminal, at least two session border controllers, ISBC, and a SIP call center node corresponding to each ISBC, the apparatus includes:

the acquisition module is used for: the method comprises the steps of acquiring first routing information from the S-CSCF to a first target ISBC;

And a sending module: the method comprises the steps of sending the call request to a first target ISBC, so that the call request is sent to a first SIP call center node corresponding to the first target ISBC, wherein the first SIP call center node is one of all SIP call center nodes connected with the first target ISBC;

a receiving module, configured to receive failure information from the first target ISBC to the first SIP call center node;

the acquisition module is further used for acquiring second routing information from the S-CSCF to a second target ISBC;

the sending module is further configured to send the call request to the second target ISBC, so that the call request is sent to a second SIP call center node corresponding to the second target ISBC, where the second SIP call center node is one of all SIP call center nodes connected to the second target ISBC.

8. The apparatus of claim 7, wherein the S-CSCF presets a routing table storing routing information for the S-CSCF to the ISBC and to the destination SIP call center node, and wherein the obtaining module comprises:

And a query sub-module: the routing table is used for inquiring the preset routing table according to the call request;

and (3) an acquisition sub-module: and the first routing information is used for acquiring the first routing information, and the first routing information comprises the routing information from the S-CSCF to the first target ISBC.

9. A business disaster recovery system, comprising:

at least one processor, and at least one memory communicatively coupled to the processor, wherein:

the memory stores program instructions executable by the processor, the processor invoking the program instructions to perform the method of any of claims 1-6.

10. A non-transitory computer readable storage medium storing computer instructions that cause the computer to perform the method of any one of claims 1 to 6.