A method for dynamic scaling up and down of SIP calls based on route consistency detection

Abstract

This invention relates to a method for dynamically scaling up and down SIP calls based on route consistency detection. By executing route activation and deactivation synchronization processes based on route consistency detection between the SIP signaling processing module and the SIP load balancer, and by using a dedicated message channel to accelerate information exchange, reliable scaling up and down of the SIP signaling processing module is achieved, reducing the scaling time to within seconds. The route activation and deactivation synchronization processes complete information exchange via messages, with messages being quickly sent, received, or retransmitted through the dedicated message channel, enabling lossless dynamic scaling up and down of the SIP signaling processing module within one second and at the level of hundreds of milliseconds. This invention is applicable to both non-SingleIP and SingleIP modes of the SIP load balancer; it can be applied to various SIP call scenarios, such as SIP signaling processing for services like 5G new calls, intelligent networks, anti-fraud and anti-harassment, and video ringback tones.

Description

Technical Field

[0001] This invention relates to a method for dynamically scaling up and down SIP calls based on route consistency detection. Background Technology

[0002] SIP (Session Initialization Protocol) technology is currently widely used in communication systems, especially in various value-added service systems that use SIP signaling to process services. These systems have a wide variety of services, are developing rapidly, and have a high number of concurrent SIP signaling processing channels, often requiring scaling up or down the SIP signaling processing module. At the same time, for network stability, the SIP signaling processing module is generally connected to the IMS (IP Multimedia Subsystem) core network through a SIP load balancer.

[0003] In existing systems, routing detection between SIP signaling processing modules and SIP load balancers is often achieved through Ping (Packet Internet Groper). Ping detection uses the ICMP (Internet Control Message Protocol) protocol, probing route reachability through the interaction of ICMP Echo Request and ICMP Echo Reply. However, this method often takes more than a second to complete. More importantly, due to the lack of routing detection between the SIP signaling processing module and the SIP load balancer, it cannot be confirmed whether the routing of the SIP signaling processing module to be scaled up or down is completely consistent with other modules. For example, routing changes or anomalies caused by configuration errors, configuration adjustments, or network anomalies cannot be guaranteed. Therefore, it cannot be assured that the load will be evenly distributed after scaling up or down, or even that the remaining SIP signaling processing modules after scaling down can fully handle the workload. Therefore, current networks often use static scaling up and down: scaling up or down is achieved by modifying configurations and restarting all modules during periods of low traffic, such as at night. This undoubtedly increases the difficulty of operation and maintenance, and limits the rapid deployment and adjustment of services.

[0004] Therefore, how to reliably, quickly, losslessly, and online scale up and down the SIP signaling processing module to adapt to the rapid updates and changes in services, and how to apply it to different networking environments, such as non-SingleIP networking and SingleIP networking, are important issues that SIP technology needs to address in the development of value-added communication services. Summary of the Invention

[0005] To address the problems existing in the prior art, the purpose of this invention is to provide a technical solution for a method of dynamically scaling up and down SIP calls based on route consistency detection.

[0006] The method for dynamic scaling up and down of SIP calls based on route consistency detection is characterized by executing route activation synchronization and route deactivation synchronization processes based on route consistency detection between the SIP signaling processing module and the SIP load balancer, and using a dedicated message channel to accelerate information interaction, thereby achieving reliable scaling up and down of the SIP signaling processing module and reducing the scaling up and down time to within seconds; when the SIP signaling processing module scales up, it executes a route activation synchronization process, including a five-step process: route activation synchronization request, route activation synchronization response, route consistency query, route consistency query response, and route activation confirmation; SI When the SIP signaling processing module scales down, it executes a route deactivation synchronization process, which includes five steps: route deactivation synchronization request, route deactivation synchronization response, route consistency query request, route consistency query response, and route deactivation confirmation. The route activation synchronization process and the route deactivation synchronization process exchange information via messages, sending and receiving messages quickly or retransmitting them through a dedicated message channel, enabling lossless dynamic scaling up and down of the SIP signaling processing module within 1 second and at the level of hundreds of milliseconds. Through the verification and confirmation mechanism of routing information between the SIP signaling processing module and the SIP load balancer, reliable dynamic scaling up and down of the SIP signaling processing module is achieved.

[0007] The method for dynamically scaling up and down SIP calls based on route consistency detection is characterized in that the route activation synchronization process and route deactivation synchronization process based on route consistency detection can be used in both the non-SingleIP mode and the SingleIP mode of the SIP load balancer.

[0008] The method for dynamically scaling up and down SIP calls based on route consistency detection is characterized in that the message content of the route activation synchronization process and the route deactivation synchronization process based on route consistency detection includes the following information: the total number of configured routes, the total number of reachable routes, the route sequence number, the internal network port address of the SIP load balancer, the internal network address of the SIP signaling processing module, the IP version, and the route status.

[0009] The method for dynamically scaling up and down SIP calls based on route consistency detection is characterized in that both the SIP signaling processing module and the SIP load balancer use dedicated message channels to establish a dedicated message queue for message transmission between the network card and the application layer of the process; at the same time, they use UDP ports different from those used for SIP signaling messages to transmit interactive messages, enabling the SIP signaling processing module and the SIP load balancer to quickly identify, forward, and process messages.

[0010] The method for dynamically scaling up and down SIP calls based on route consistency detection is characterized in that the SIP signaling processing module periodically sends detection message packets through a dedicated message channel. The default message sending interval is set to 20ms, and the default detection timeout multiple can be set to 3 times. If the detection timeout multiple is exceeded, an anomaly is reported, and the network management policy is used to select to re-detect or investigate the relevant configuration and network of the route that failed detection. By adopting the strategy of using a dedicated message channel and periodically sending detection packets, route detection between the SIP signaling processing module and the SIP load balancer can be achieved within 1 second and at the level of hundreds of milliseconds.

[0011] The method for dynamically scaling up and down SIP calls based on route consistency detection is characterized in that, in the non-SingleIP mode, each SIP load balancer is configured with a different external IP address, while in the SingleIP mode, each SIP load balancer is configured with the same external IP address; in the SingleIP mode, SIP messages can be received on any SIP load balancer; in order to synchronize SIP session information, the SIP load balancer can synchronize SIP session information between SIP load balancers through the SIP flow table synchronization function;

[0012] The SIP flow table synchronization function includes synchronizing the creation, updating, and deletion of SIP flow tables. The content of the flow table synchronization message includes the configuration flow table identifier and the Call-Id field of the SIP protocol. In the SingleIP mode of the SIP load balancer, the combination of route consistency detection and SIP flow table synchronization enables the SIP signaling processing module to achieve fast and lossless dynamic scaling.

[0013] If the routing consistency test result is normal during expansion, the SIP load balancer will forward new SIP calls to the newly added SIP signaling processing module; if the routing consistency test result is normal during scaling down, the SIP load balancer will no longer forward newly initiated SIP calls to the scaled-down SIP signaling processing module, but will still forward subsequent SIP messages of previously online calls so that previously online calls can end normally.

[0014] The route activation synchronization process and route deactivation synchronization process based on route consistency detection are initiated by the network management system notifying the SIP signaling processing module, and each SIP load balancer responds.

[0015] The method for dynamically scaling up and down SIP calls based on route consistency detection is characterized by the following process for dynamically scaling up the non-SingleIP mode SIP signaling processing module:

[0016] (2.1): The network management system triggers the expansion of the SIP signaling processing module. The SIP signaling processing module to be expanded sends a route activation synchronization request to each SIP load balancer in parallel. The SIP signaling processing module n+1 to be expanded sends a route activation synchronization request message to SIP load balancer 1.

[0017] (2.2): The SIP signaling processing module n+1 to be expanded sends a route activation synchronization request message to the SIP load balancer 2;

[0018] (2.3): The SIP signaling processing module n+1 to be expanded sends a route activation synchronization request message to the SIP load balancer 3;

[0019] (2.4): After receiving the route activation synchronization request, SIP load balancer 1 starts route consistency detection to check whether the routes are consistent with those of other SIP load balancers: it sends route consistency query requests to other SIP load balancers respectively. The request message contains the route information of SIP load balancer 1 and all SIP signaling processing modules. The route information includes the IP version of the SIP signaling processing module and the IP address of the corresponding IP version, and whether the route status is available; SIP load balancer 1 sends a route consistency query request message to SIP load balancer 2.

[0020] (2.5): SIP load balancer 1 sends a routing consistency query request message to SIP load balancer 3;

[0021] (2.6): After receiving the route consistency query request message from SIP load balancer 1, SIP load balancer 2 parses the routing information in the message and compares it with the current routing information of this load balancer. If they are consistent, it returns success; otherwise, it returns failure and sends a route consistency query response message to feed back the route consistency detection result to SIP load balancer 1.

[0022] (2.7): SIP load balancer 3 sends a route consistency query response message and feeds back the route consistency detection result to SIP load balancer 1;

[0023] (2.8): SIP load balancer 1 receives the route consistency detection results from SIP load balancer 2 and SIP load balancer 3. If both are successful, it returns a successful route activation synchronization confirmation to the SIP signaling processing module n+1 to be expanded; otherwise, it returns a failure confirmation.

[0024] (2.9): SIP load balancer 2 sends a route consistency query request message to SIP load balancer 1;

[0025] (2.10): SIP load balancer 2 sends a routing consistency query request message to SIP load balancer 3;

[0026] (2.11): SIP load balancer 1 sends a route consistency query response message and feeds back the route consistency detection result to SIP load balancer 2;

[0027] (2.12): SIP load balancer 3 sends a route consistency query response message and feeds back the route consistency detection result to SIP load balancer 2;

[0028] (2.13): SIP load balancer 2 receives the route consistency detection results from SIP load balancer 1 and SIP load balancer 3. If both are successful, it returns a successful route activation synchronization confirmation to the SIP signaling processing module n+1 to be expanded; otherwise, it returns a failure confirmation.

[0029] (2.14): SIP load balancer 3 sends a routing consistency query request message to SIP load balancer 1;

[0030] (2.15): SIP load balancer 3 sends a routing consistency query request message to SIP load balancer 2;

[0031] (2.16): SIP load balancer 1 sends a route consistency query response message and feeds back the route consistency detection result to SIP load balancer 3;

[0032] (2.17): SIP load balancer 2 sends a route consistency query response message and feeds back the route consistency detection result to SIP load balancer 3;

[0033] (2.18): SIP load balancer 3 receives the route consistency detection results from SIP load balancer 1 and SIP load balancer 2. If both are successful, it returns a successful route activation synchronization confirmation to the SIP signaling processing module n+1 to be expanded; otherwise, it returns a failure confirmation.

[0034] (2.19): The SIP signaling processing module n+1 to be expanded receives route activation synchronization confirmations from SIP load balancer 1, SIP load balancer 2 and SIP load balancer 3. If all are successful, it sends route activation confirmation messages to SIP load balancer 1, SIP load balancer 2 and SIP load balancer 3 in parallel; otherwise, it does not send any. SIP signaling processing module n+1 sends a route activation confirmation message to SIP load balancer 1.

[0035] (2.20): SIP signaling processing module n+1 sends a route activation confirmation message to SIP load balancer 2;

[0036] (2.21): SIP signaling processing module n+1 sends a route activation confirmation message to SIP load balancer 3;

[0037] (2.22): After SIP load balancers 1, 2 and 3 receive the route activation confirmation message, it means that the expansion of SIP signaling processing module n+1 is successful. After that, each SIP load balancer distributes SIP signaling flow according to the expanded routing table, including sending SIP signaling flow to SIP signaling processing module n+1. After receiving the SIP signaling flow, SIP signaling processing module n+1 continues to process the signaling message.

[0038] If the routes of each SIP load balancer are inconsistent with the SIP signaling processing module n+1 to be expanded, the route activation process will fail and an error log needs to be output. On-site engineers need to check whether the configuration and network are abnormal.

[0039] The method for dynamically scaling up and down SIP calls based on route consistency detection is characterized by the following process for dynamically scaling down the non-SingleIP mode SIP signaling processing module:

[0040] (3.1): The network management system triggers the downsizing of the SIP signaling processing module. The SIP signaling processing module to be downsized sends a route deactivation synchronization request to each SIP load balancer in parallel. The SIP signaling processing module n+1 to be downsized sends a route deactivation synchronization request message to SIP load balancer 1.

[0041] (3.2): The SIP signaling processing module n+1 to be scaled up sends a route deactivation synchronization request message to the SIP load balancer 2;

[0042] (3.3): The SIP signaling processing module n+1 to be scaled up sends a route deactivation synchronization request message to the SIP load balancer 3;

[0043] (3.4): After receiving the route deactivation synchronization request, SIP load balancer 1 starts route consistency detection to check whether the routes are consistent with those of other SIP load balancers: it sends route consistency query requests to other SIP load balancers respectively. The request message contains the route information of SIP load balancer 1 and all SIP signaling processing modules. The route information includes the IP version of the SIP signaling processing module and the IP address of the corresponding IP version, and whether the route status is available; SIP load balancer 1 sends a route consistency query request message to SIP load balancer 2.

[0044] (3.5): SIP load balancer 1 sends a routing consistency query request message to SIP load balancer 3;

[0045] (3.6): After receiving the route consistency query request message from SIP load balancer 1, SIP load balancer 2 parses the routing information in the message and compares it with the current routing information of this load balancer. If they are consistent, it returns success; otherwise, it returns failure and sends a route consistency query response message to feed back the route consistency detection result to SIP load balancer 1.

[0046] (3.7): SIP load balancer 3 sends a route consistency query response message and feeds back the route consistency detection result to SIP load balancer 1;

[0047] (3.8): SIP load balancer 1 receives the route consistency detection results from SIP load balancers 2 and 3. If both are successful, it returns a successful route deactivation synchronization confirmation to the SIP signaling processing module n+1 to be scaled down; otherwise, it returns a failure confirmation.

[0048] (3.9): SIP load balancer 2 sends a routing consistency query request message to SIP load balancer 1;

[0049] (3.10): SIP load balancer 2 sends a routing consistency query request message to SIP load balancer 3;

[0050] (3.11): SIP load balancer 1 sends a route consistency query response message and feeds back the route consistency detection result to SIP load balancer 2;

[0051] (3.12): SIP load balancer 3 sends a route consistency query response message and feeds back the route consistency detection result to SIP load balancer 2;

[0052] (3.13): SIP load balancer 2 receives the route consistency detection results from SIP load balancers 1 and 3. If both are successful, it returns a successful route deactivation synchronization confirmation to the SIP signaling processing module n+1 to be scaled down; otherwise, it returns a failure confirmation.

[0053] (3.14): SIP load balancer 3 sends a routing consistency query request message to SIP load balancer 1;

[0054] (3.15): SIP load balancer 3 sends a routing consistency query request message to SIP load balancer 2;

[0055] (3.16): SIP load balancer 1 sends a route consistency query response message and feeds back the route consistency detection result to SIP load balancer 3;

[0056] (3.17): SIP load balancer 2 sends a route consistency query response message and feeds back the route consistency detection result to SIP load balancer 3;

[0057] (3.18): SIP load balancer 3 receives the route consistency detection results from SIP load balancers 1 and 2. If both are successful, it returns a successful route deactivation synchronization confirmation to the SIP signaling processing module n+1 to be scaled down; otherwise, it returns a failure confirmation.

[0058] (3.19): The SIP signaling processing module n+1 to be scaled down receives the route deactivation synchronization confirmation from SIP load balancer 1, SIP load balancer 2 and SIP load balancer 3. If all are successful, it sends route deactivation confirmation messages to SIP load balancer 1, SIP load balancer 2 and SIP load balancer 3 in parallel; otherwise, it does not send any. The SIP signaling processing module n+1 sends a route deactivation confirmation message to SIP load balancer 1.

[0059] (3.20): SIP signaling processing module n+1 sends a route deactivation confirmation message to SIP load balancer 2;

[0060] (3.21): SIP signaling processing module n+1 sends a route deactivation confirmation message to SIP load balancer 3;

[0061] (3.22): After SIP load balancers 1, SIP load balancer 2 and SIP load balancer 3 receive the route deactivation confirmation message, it means that the SIP signaling processing module n+1 has been successfully scaled down. After that, each SIP load balancer distributes SIP signaling flow according to the scaled-down routing table, that is, it no longer sends new SIP call initiation messages to SIP signaling processing module n+1, but forwards subsequent SIP signaling messages that have already been online.

[0062] Wait for SIP signaling processing module n+1 to report that the session resources have been released; then, through the network management system, delete the routing configuration of the scaled-down SIP signaling processing module n+1; and delete the routing configuration to the scaled-down SIP signaling processing module n+1 from each SIP load balancer.

[0063] If the routes of each SIP load balancer and the SIP signaling processing module n+1 to be scaled down are inconsistent, the routing deactivation process will fail and an error log needs to be output. On-site engineers need to check whether the configuration and network are abnormal.

[0064] The method for dynamically scaling up and down SIP calls based on route consistency detection is characterized by the following process for dynamically scaling up the SingleIP mode SIP signaling processing module:

[0065] (4.1): SIP load balancer 1, SIP load balancer 2 and SIP load balancer 3 communicate with SIP signaling processing module n+1 to send and receive SIP signaling streams, but SIP signaling processing module n+1 has not yet received and processed SIP messages.

[0066] (4.2): The SIP signaling processing module n+1 to be expanded and each SIP load balancer perform a route activation synchronization process based on route consistency detection.

[0067] (4.3): The CSCF sends a SIP initiation message to the SIP load balancer 3;

[0068] (4.4): After receiving the SIP call initiation message, SIP load balancer 3 sends SIP flow table synchronization requests to SIP load balancer 1 and SIP load balancer 2 in parallel. The request message contains the SIP flow table identifier and SIP Call-Id; SIP load balancer 3 sends SIP flow table synchronization request to SIP load balancer 1.

[0069] (4.5): SIP load balancer 3 sends a SIP flow table synchronization request to SIP load balancer 2;

[0070] (4.6): If the SIP flow table synchronization is completed, each SIP load balancer will then distribute SIP signaling flows according to the expanded routing table, including the ability to send SIP signaling flows to SIP signaling processing module n+1, including SIP initiation messages;

[0071] (4.7): SIP signaling processing module n+1 receives and processes SIP signaling messages.

[0072] The method for dynamically scaling up and down SIP calls based on route consistency detection is characterized by the following process for dynamically scaling down the SingleIP mode SIP signaling processing module:

[0073] (5.1): SIP signaling streams are sent and received between the SIP load balancer and the SIP signaling processing module n+1. The SIP signaling processing module n+1 to be scaled up processes SIP signaling messages normally.

[0074] (5.2): The SIP signaling processing module n+1 to be scaled down and each SIP load balancer perform a route deactivation synchronization process based on route consistency detection.

[0075] (5.3): The CSCF sends a SIP initiation message to the SIP load balancer 3;

[0076] (5.4): After receiving the SIP call initiation message, SIP load balancer 3 sends SIP flow table synchronization requests to SIP load balancer 1 and SIP load balancer 2 in parallel. The request message contains the SIP flow table identifier and SIP Call-Id; SIP load balancer 3 sends SIP flow table synchronization request to SIP load balancer 1.

[0077] (5.5): SIP load balancer 3 sends a SIP flow table synchronization request to SIP load balancer 2;

[0078] (5.6): After the routing consistency test is completed, each SIP load balancer distributes SIP signaling flow according to the reduced routing table, no longer sends SIP initiation message to SIP signaling processing module n+1, but forwards subsequent SIP signaling messages that have been online before.

[0079] (5.7): SIP load balancer 1, SIP load balancer 2 and SIP load balancer 3 communicate with SIP signaling processing module n+1 to send and receive SIP streams;

[0080] (5.8): Wait for the SIP signaling processing module n+1 to report that the session resource release is complete;

[0081] Then, through the network management system, delete the routing configuration of the scaled-down SIP signaling processing module n+1, and delete the routing configuration of each SIP load balancer to the scaled-down SIP signaling processing module n+1.

[0082] This invention proposes a method for route consistency detection, which can reliably and losslessly realize the online dynamic scaling up and down of the SIP signaling processing module. At the same time, it adopts a dedicated message channel to quickly transmit and process interactive messages, reducing the dynamic scaling up and down time to within 1 second or hundreds of milliseconds. It is applicable to both the non-SingleIP mode and SingleIP mode of the SIP load balancer. Attached Figure Description

[0083] Figure 1 A schematic diagram of the network topology of the SIP signaling processing modules described in this invention;

[0084] Figure 2 Flowchart of dynamic expansion of the non-SingleIP mode SIP signaling processing module described in this invention;

[0085] Figure 3 Flowchart of the dynamic scaling-up process of the non-SingleIP mode SIP signaling processing module described in this invention;

[0086] Figure 4 Flowchart of dynamic expansion of SingleIP mode SIP signaling processing module as described in this invention;

[0087] Figure 5 The flowchart of the dynamic scaling down of the SingleIP mode SIP signaling processing module described in this invention. Detailed Implementation

[0088] The present invention will be further described below with reference to the accompanying drawings:

[0089] This invention relates to IMS applications, 5G new calling applications, and various SIP call-based value-added communication service applications.

[0090] This invention takes the networking of AS (Application Server) in an IMS network as an example, referring to the appendix. Figure 1 The network includes a SIP service module, a SIP signaling processing module, and a SIP load balancer. The SIP signaling processing module and the SIP load balancer adopt the implementation method of this invention to achieve reliable, fast, and lossless dynamic scaling of the SIP signaling processing module, and are applicable to two scenarios: non-SingleIP mode and SingleIP mode of the SIP load balancer.

[0091] 1) Reference Appendix Figure 1 The network topology diagram of each SIP signaling processing module is shown below:

[0092] CSCF: Call Session Control Function is a key component of the IMS system, primarily responsible for handling signaling control during multimedia call sessions;

[0093] SIP load balancer: responsible for SIP signaling access and distribution;

[0094] SIP signaling processing module: responsible for SIP protocol parsing, SIP session management, etc.

[0095] SIP service module: performs specific service control, such as establishing connections between the calling and called parties, playing audio, recording audio, etc.

[0096] There is a fully cross-networked structure between the SIP load balancer and the SIP signaling processing module, and between the SIP signaling processing module and the SIP service module. The number of SIP load balancers generally remains constant, while the SIP signaling processing module may need to be expanded or scaled down depending on changes in service requirements.

[0097] 2) Reference Appendix Figure 2 The flowchart for the dynamic expansion of the non-SingleIP mode SIP signaling processing module is as follows:

[0098] Pre-configuration: Through the network management system, the SIP signaling processing module to be expanded (numbered n+1) (the module number will be directly explained after the module name in this document, such as SIP signaling processing module (numbered n+1) being referred to as SIP signaling processing module n+1) completes process loading and routing configuration to each SIP load balancer; each SIP load balancer is configured with a route to the SIP signaling processing module n+1 to be expanded.

[0099] (2.1)-(2.21) are the route activation and synchronization processes based on route consistency detection, initiated by the network management system and can be started automatically or manually according to the policy. After the route activation and synchronization process is successful, SIP calls are automatically connected, and call load balancing is achieved.

[0100] (2.1): The network management system triggers the expansion of the SIP signaling processing module. The SIP signaling processing module to be expanded sends route activation synchronization requests in parallel to each SIP load balancer. The message shown in the figure is the route activation synchronization request message sent by the SIP signaling processing module n+1 to SIP load balancer 1;

[0101] (2.2): The SIP signaling processing module n+1 to be expanded sends a route activation synchronization request message to the SIP load balancer 2;

[0102] (2.3): The SIP signaling processing module n+1 to be expanded sends a route activation synchronization request message to the SIP load balancer 3;

[0103] (2.4): After receiving the route activation synchronization request, SIP load balancer 1 starts route consistency detection to check whether the routes are consistent with those of other SIP load balancers: it sends route consistency query requests to other SIP load balancers respectively. The request message contains the route information of SIP load balancer 1 and all SIP signaling processing modules, such as the IP version of the SIP signaling processing module and the IP address of the corresponding IP version, whether the route status is available, etc.; the message shown in the figure is SIP load balancer 1 sending a route consistency query request message to SIP load balancer 2.

[0104] (2.5): Similar to (2.4), SIP load balancer 1 sends a route consistency query request message to SIP load balancer 3;

[0105] (2.6): After receiving the route consistency query request message from SIP load balancer 1, SIP load balancer 2 parses the routing information in the message and compares it with the current routing information of this load balancer. If they are consistent, it returns success; otherwise, it returns failure and sends a route consistency query response message to feed back the route consistency detection result to SIP load balancer 1.

[0106] (2.7): Similar to (2.6), SIP load balancer 3 sends a route consistency query response message and feeds back the route consistency detection result to SIP load balancer 1;

[0107] (2.8): SIP load balancer 1 receives the route consistency test results from SIP load balancer 2 and SIP load balancer 3. If both are successful, it returns a successful route activation synchronization confirmation to the SIP signaling processing module n+1 to be expanded. Otherwise, it returns a failure confirmation.

[0108] (2.1), (2.4)-(2.7) and (2.8) are the routing consistency detection process from the SIP signaling processing module to be expanded to a SIP load balancer. If it is not completed within one detection cycle (the sending interval in the routing consistency detection message), the request needs to be resent.

[0109] (2.9)-(2.12) and (2.13): The process is similar to (2.4)-(2.7) and (2.8).

[0110] (2.9): SIP load balancer 2 sends a route consistency query request message to SIP load balancer 1;

[0111] (2.10): SIP load balancer 2 sends a routing consistency query request message to SIP load balancer 3;

[0112] (2.11): SIP load balancer 1 sends a route consistency query response message and feeds back the route consistency detection result to SIP load balancer 2;

[0113] (2.12): SIP load balancer 3 sends a route consistency query response message and feeds back the route consistency detection result to SIP load balancer 2;

[0114] (2.13): SIP load balancer 2 receives the route consistency detection results from SIP load balancers 1 and 3. If both are successful, it returns a successful route activation synchronization confirmation to the SIP signaling processing module n+1 to be expanded. Otherwise, it returns a failure confirmation.

[0115] (2.14)-(2.17) and (2.18): The process is similar to (2.4)-(2.7) and (2.8).

[0116] (2.14): SIP load balancer 3 sends a routing consistency query request message to SIP load balancer 1;

[0117] (2.15): SIP load balancer 3 sends a routing consistency query request message to SIP load balancer 2;

[0118] (2.16): SIP load balancer 1 sends a route consistency query response message and feeds back the route consistency detection result to SIP load balancer 3;

[0119] (2.17): SIP load balancer 2 sends a route consistency query response message and feeds back the route consistency detection result to SIP load balancer 3;

[0120] (2.18): SIP load balancer 3 receives the route consistency detection results from SIP load balancer 1 and SIP load balancer 2. If both are successful, it returns a successful route activation synchronization confirmation to the SIP signaling processing module n+1 to be expanded; otherwise, it returns a failure confirmation.

[0121] (2.19): The SIP signaling processing module n+1 to be expanded receives route activation synchronization confirmations from SIP load balancer 1, SIP load balancer 2 and SIP load balancer 3. If all are successful, it sends route activation confirmation messages to SIP load balancer 1, SIP load balancer 2 and SIP load balancer 3 in parallel; otherwise, it does not send any. The message shown in the figure is the route activation confirmation message sent by SIP signaling processing module n+1 to SIP load balancer 1.

[0122] (2.20): SIP signaling processing module n+1 sends a route activation confirmation message to SIP load balancer 2;

[0123] (2.21): SIP signaling processing module n+1 sends a route activation confirmation message to SIP load balancer 3;

[0124] (2.22): After SIP load balancers 1, 2 and 3 receive the route activation confirmation message, it means that the expansion of SIP signaling processing module n+1 is successful. After that, each SIP load balancer distributes SIP signaling flow according to the expanded routing table, including the SIP signaling flow that can be sent to SIP signaling processing module n+1, such as SIP Invite message, etc. After receiving it, SIP signaling processing module n+1 continues to process the signaling message.

[0125] Other: If the routes of each SIP load balancer are inconsistent with the SIP signaling processing module n+1 to be expanded, the route activation process will fail and an error log needs to be output. On-site engineers need to check whether the configuration and network are abnormal.

[0126] 3) Reference Appendix Figure 3 The flowchart for the dynamic scaling down of the non-SingleIP mode SIP signaling processing module is as follows:

[0127] (3.1)-(3.21) are the route deactivation synchronization processes based on route consistency detection, initiated by the network management system and can be started automatically or manually according to the policy. After the route consistency detection is successful, access to SIP calls is automatically stopped.

[0128] (3.1): The network management system triggers the downsizing of the SIP signaling processing module. The SIP signaling processing module to be downsized sends a route deactivation synchronization request to each SIP load balancer in parallel. The message shown in the figure is the route deactivation synchronization request message sent by the SIP signaling processing module n+1 to the SIP load balancer 1.

[0129] (3.2): The SIP signaling processing module n+1 to be scaled up sends a route deactivation synchronization request message to the SIP load balancer 2;

[0130] (3.3): The SIP signaling processing module n+1 to be scaled up sends a route deactivation synchronization request message to the SIP load balancer 3;

[0131] (3.4): After receiving the route deactivation synchronization request, SIP load balancer 1 starts route consistency detection to check whether the routes are consistent with those of other SIP load balancers: it sends route consistency query requests to other SIP load balancers respectively. The request message contains the route information of SIP load balancer 1 and all SIP signaling processing modules, such as the IP version of the SIP signaling processing module and the IP address of the corresponding IP version, whether the route status is available, etc.; the message shown in the figure is SIP load balancer 1 sending a route consistency query request message to SIP load balancer 2.

[0132] (3.5): Similar to (3.4), SIP load balancer 1 sends a route consistency query request message to SIP load balancer 3;

[0133] (3.6): After receiving the route consistency query request message from SIP load balancer 1, SIP load balancer 2 parses the routing information in the message and compares it with the current routing information of this load balancer. If they are consistent, it returns success; otherwise, it returns failure and sends a route consistency query response message to feed back the route consistency detection result to SIP load balancer 1.

[0134] (3.7): Similar to (3.6), SIP load balancer 3 sends a route consistency query response message to feed back the route consistency detection result to SIP load balancer 1;

[0135] (3.8): SIP load balancer 1 receives the route consistency detection results from SIP load balancer 2 and SIP load balancer 3. If both are successful, it returns a successful route deactivation synchronization confirmation to the SIP signaling processing module n+1 to be scaled down; otherwise, it returns a failure confirmation.

[0136] (3.1), (3.4)-(3.7) and (3.8) are the routing consistency detection process from the SIP signaling processing module to be scaled down to a SIP load balancer. If it is not completed within one detection cycle (the sending interval in the routing consistency detection message), the request needs to be resent.

[0137] (3.9)-(3.12) and (3.13): The process is similar to (3.4)-(3.7) and (3.8).

[0138] (3.9): SIP load balancer 2 sends a routing consistency query request message to SIP load balancer 1;

[0139] (3.10): SIP load balancer 2 sends a routing consistency query request message to SIP load balancer 3;

[0140] (3.11): SIP load balancer 1 sends a route consistency query response message and feeds back the route consistency detection result to SIP load balancer 2;

[0141] (3.12): SIP load balancer 3 sends a route consistency query response message and feeds back the route consistency detection result to SIP load balancer 2;

[0142] (3.13): SIP load balancer 2 receives the route consistency detection results from SIP load balancers 1 and 3. If both are successful, it returns a successful route deactivation synchronization confirmation to the SIP signaling processing module n+1 to be scaled down; otherwise, it returns a failure confirmation.

[0143] (3.14)-(3.17) and (3.18): The process is similar to (3.4)-(3.7) and (3.8).

[0144] (3.14): SIP load balancer 3 sends a routing consistency query request message to SIP load balancer 1;

[0145] (3.15): SIP load balancer 3 sends a routing consistency query request message to SIP load balancer 2;

[0146] (3.16): SIP load balancer 1 sends a route consistency query response message and feeds back the route consistency detection result to SIP load balancer 3;

[0147] (3.17): SIP load balancer 2 sends a route consistency query response message and feeds back the route consistency detection result to SIP load balancer 3;

[0148] (3.18): SIP load balancer 3 receives the route consistency detection results from SIP load balancer 1 and SIP load balancer 2. If both are successful, it returns a successful route deactivation synchronization confirmation to the SIP signaling processing module n+1 to be scaled down; otherwise, it returns a failure confirmation.

[0149] (3.19): The SIP signaling processing module n+1 to be scaled down receives the route deactivation synchronization confirmation from SIP load balancer 1, SIP load balancer 2 and SIP load balancer 3. If all are successful, it sends route deactivation confirmation messages to SIP load balancer 1, SIP load balancer 2 and SIP load balancer 3 in parallel; otherwise, it does not send any. The message shown in the figure is the route deactivation confirmation message sent by SIP signaling processing module n+1 to SIP load balancer 1.

[0150] (3.20): SIP signaling processing module n+1 sends a route deactivation confirmation message to SIP load balancer 2;

[0151] (3.21): SIP signaling processing module n+1 sends a route deactivation confirmation message to SIP load balancer 3;

[0152] (3.22): After SIP load balancers 1, 2 and 3 receive the route deactivation confirmation message, it means that the SIP signaling processing module n+1 has been successfully scaled down. After that, each SIP load balancer distributes SIP signaling flow according to the scaled-down routing table. That is, it no longer sends new SIP initiation messages to SIP signaling processing module n+1, but forwards subsequent SIP signaling messages that have already been online.

[0153] Subsequent steps: Wait for SIP signaling processing module n+1 to report that the session resources have been released; then, through the network management system, delete the routing configuration of the scaled-down SIP signaling processing module n+1; and delete the routing configuration to the scaled-down SIP signaling processing module n+1 from each SIP load balancer.

[0154] Other: If the routes of each SIP load balancer and the SIP signaling processing module n+1 to be scaled down are inconsistent, the routing deactivation process will fail and an error log needs to be output. On-site engineers need to check whether the configuration and network are abnormal.

[0155] 4) See Appendix Figure 4 The flowchart for the dynamic expansion of the SingleIP mode SIP signaling processing module is as follows:

[0156] Pre-configuration: Through the network management system, the SIP signaling processing module n+1 to be expanded completes process loading and routing configuration to each SIP load balancer; each SIP load balancer is configured with a route to the SIP signaling processing module n+1 to be expanded.

[0157] (4.1)-(4.7): When the SIP load balancer operates in the SingleIP scenario, the dynamic expansion function of the SIP signaling processing module is based on the routing consistency detection function and the SIP flow table synchronization function. After successful execution, it can automatically access SIP calls and achieve call load balancing, etc.

[0158] (4.1): SIP load balancer 1, SIP load balancer 2 and SIP load balancer 3 communicate with SIP signaling processing modules (numbered 1 to n) to send and receive SIP signaling streams, but SIP signaling processing module n+1 has not yet received and processed SIP messages.

[0159] (4.2): The SIP signaling processing module n+1 to be expanded and each SIP load balancer (numbered 1, 2 and 3) perform a route activation synchronization process based on route consistency detection;

[0160] (4.3): The CSCF (Call Session Control Function) sends a SIP call initiation message to the SIP load balancer (number 3 in the diagram);

[0161] (4.4): After receiving the SIP initiation call message, SIP load balancer 3 sends SIP flow table synchronization requests to SIP load balancers (numbered 1 and 2) in parallel. The request message contains the SIP flow table identifier, SIP Call-Id, etc. The illustrated message shows SIP load balancer 3 sending a SIP flow table synchronization request to SIP load balancer 1.

[0162] (4.5): Similar to (4.4), SIP load balancer 3 sends a SIP flow table synchronization request to SIP load balancer 2;

[0163] (4.6): If the SIP flow table synchronization is completed, each SIP load balancer will then distribute SIP signaling flows according to the expanded routing table, including the ability to send SIP signaling flows to SIP signaling processing module n+1, such as SIP initiation messages, etc.

[0164] (4.7): SIP signaling processing module n+1 receives and processes SIP signaling messages;

[0165] (4.4) and (4.5) are the SIP flow table synchronization procedures. If the synchronization is not completed within one synchronization cycle (the flow table sending interval in the flow table synchronization message, default 30MS), a resend request is required. During capacity expansion, the SIP flow table synchronization process still needs to be executed, but during expansion, the routes are distributed according to the routes before expansion. After receiving the route activation confirmation message based on route consistency detection, the routes are distributed according to the routes after expansion.

[0166] 5) See Appendix Figure 5 The flowchart for the dynamic scaling down of the SingleIP mode SIP signaling processing module is as follows:

[0167] (5.1)-(5.7): When the SIP load balancer operates in the SingleIP scenario, the dynamic scaling function of the SIP signaling processing module is also based on the routing consistency detection function and the SIP flow table synchronization function. After successful execution, it automatically stops accessing SIP calls.

[0168] (5.1): SIP signaling streams are sent and received between the SIP load balancers (numbered 1, 2 and 3) and the SIP signaling processing modules (numbered 1 to n+1). The SIP signaling processing module n+1, which is to be scaled down, processes SIP signaling messages normally.

[0169] (5.2): The SIP signaling processing module n+1 to be scaled down and each SIP load balancer (numbered 1, 2 and 3) perform a route deactivation synchronization process based on route consistency detection;

[0170] (5.3): The CSCF sends a SIP initiation message to the SIP load balancer (number 3 in the diagram);

[0171] (5.4): After receiving the SIP initiation message, SIP load balancer 3 sends SIP flow table synchronization requests to SIP load balancers (numbered 1 and 2) in parallel. The request message contains the SIP flow table identifier, SIP Call-Id, etc. The diagram shows SIP load balancer 3 sending a SIP flow table synchronization request to SIP load balancer 1;

[0172] (5.5): Similar to (5.4), SIP load balancer 3 sends a SIP flow table synchronization request to SIP load balancer 2;

[0173] (5.6): After the routing consistency test is completed, each SIP load balancer distributes SIP signaling flow according to the scaled-down routing table and no longer sends SIP initiation message to SIP signaling processing module n+1, as shown by the dotted line in the figure, but forwards subsequent SIP signaling messages that have already been online.

[0174] (5.7): SIP stream transmission and reception between SIP load balancers (numbered 1, 2 and 3) and SIP signaling processing modules (numbered 1 to n);

[0175] (5.8): Wait for the SIP signaling processing module n+1 to report that the session resource release is complete.

[0176] (5.4) and (5.5) are the SIP flow table synchronization procedures. If the process is not completed within one synchronization cycle (the flow table sending interval in the flow table synchronization message), a resend request is required. Meanwhile, the SIP flow table synchronization process still needs to be executed during the scaling-down period, but during scaling-down, the routes are distributed according to the routes before scaling-down. After successful scaling-down based on route consistency checks, the routes are distributed according to the routes after scaling-down.

[0177] Subsequent steps: Then, through the network management system, delete the routing configuration of the scaled-down SIP signaling processing module n+1; and delete the routing configuration to the scaled-down SIP signaling processing module n+1 from each SIP load balancer.

Claims

1. A method for dynamically scaling up and down SIP calls based on route consistency detection, characterized in that... By executing route activation synchronization and route deactivation synchronization processes based on route consistency detection between the SIP signaling processing module and the SIP load balancer, and by using a dedicated message channel to accelerate information interaction, the SIP signaling processing module can be reliably scaled up and down, and the scaling up and down time can be reduced to within seconds. When the SIP signaling processing module is expanded, a route activation synchronization process is executed, which includes five steps: route activation synchronization request, route activation synchronization response, route consistency query, route consistency query response, and route activation confirmation. When the SIP signaling processing module is scaled down, it executes a route deactivation synchronization process, which includes five steps: route deactivation synchronization request, route deactivation synchronization response, route consistency query request, route consistency query response, and route deactivation confirmation. The route activation synchronization process and the route deactivation synchronization process complete information exchange through messages. The messages are sent, received, or retransmitted quickly through a dedicated message channel, enabling lossless dynamic scaling of the SIP signaling processing module within 1 second and at the level of hundreds of milliseconds. Through the verification and confirmation mechanism of routing information between the SIP signaling processing module and the SIP load balancer, reliable dynamic scaling of the SIP signaling processing module is achieved.

2. The method for dynamically scaling up and down SIP calls based on route consistency detection according to claim 1, characterized in that... The route activation synchronization process and route deactivation synchronization process based on route consistency detection can be used in both the non-SingleIP mode and the SingleIP mode of the SIP load balancer.

3. The method for dynamically scaling up and down SIP calls based on route consistency detection according to claim 1, characterized in that... The message content of the route activation synchronization process and route deactivation synchronization process based on route consistency detection includes the following information: the total number of configured routes, the total number of reachable routes, the route sequence number, the internal network port address of the SIP load balancer, the internal network address of the SIP signaling processing module, the IP version, and the route status.

4. The method for dynamically scaling up and down SIP calls based on route consistency detection according to claim 1, characterized in that... Both the SIP signaling processing module and the SIP load balancer use dedicated message channels to establish a dedicated message queue for message transmission between the network card and the application layer of the process. At the same time, they use UDP ports different from those used for SIP signaling messages to transmit interactive messages, enabling the SIP signaling processing module and the SIP load balancer to quickly identify, forward, and process messages.

5. A method for dynamically scaling up and down SIP calls based on route consistency detection according to claim 4, characterized in that... The SIP signaling processing module periodically sends detection message packets through a dedicated message channel. The default packet sending interval is set to 20MS, and the default detection timeout multiple can be set to 3 times. If the detection timeout exceeds the limit, an anomaly is reported, and the network management policy is used to select whether to re-detect or investigate the relevant configuration and network of the route that failed the detection. By adopting a dedicated message channel and a strategy of periodically sending detection messages, the route detection between the SIP signaling processing module and the SIP load balancer can be achieved within 1 second or within hundreds of milliseconds.

6. A method for dynamically scaling up and down SIP calls based on route consistency detection according to claim 2, characterized in that... In the non-SingleIP mode, each SIP load balancer is configured with a different external IP address, while in the SingleIP mode, each SIP load balancer is configured with the same external IP address. In SingleIP mode, SIP messages can be received on any SIP load balancer; in order to synchronize SIP session information, SIP load balancers can synchronize SIP session information between SIP load balancers through the SIP flow table synchronization function. The SIP flow table synchronization function includes synchronizing the creation, updating, and deletion of SIP flow tables. The content of the flow table synchronization message includes the configuration flow table identifier and the Call-Id field of the SIP protocol. In the SingleIP mode of the SIP load balancer, the combination of route consistency detection and SIP flow table synchronization enables the SIP signaling processing module to achieve fast and lossless dynamic scaling. If the routing consistency test result is normal during expansion, the SIP load balancer will forward new SIP calls to the newly added SIP signaling processing module; if the routing consistency test result is normal during scaling down, the SIP load balancer will no longer forward newly initiated SIP calls to the scaled-down SIP signaling processing module, but will still forward subsequent SIP messages of previously online calls so that previously online calls can end normally. The route activation synchronization process and route deactivation synchronization process based on route consistency detection are initiated by the network management system notifying the SIP signaling processing module, and each SIP load balancer responds.

7. A method for dynamically scaling up and down SIP calls based on route consistency detection according to claim 2, characterized in that... The process for dynamically expanding the non-SingleIP mode SIP signaling processing module is as follows: (2.1): The network management system triggers the expansion of the SIP signaling processing module. The SIP signaling processing module to be expanded sends a route activation synchronization request to each SIP load balancer in parallel. The SIP signaling processing module n+1 to be expanded sends a route activation synchronization request message to SIP load balancer 1. (2.2): The SIP signaling processing module n+1 to be expanded sends a route activation synchronization request message to the SIP load balancer 2; (2.3): The SIP signaling processing module n+1 to be expanded sends a route activation synchronization request message to the SIP load balancer 3; (2.4): After receiving the route activation synchronization request, SIP load balancer 1 starts route consistency detection to check whether the routes are consistent with those of other SIP load balancers: it sends route consistency query requests to other SIP load balancers respectively. The request message contains the route information of SIP load balancer 1 and all SIP signaling processing modules. The route information includes the IP version of the SIP signaling processing module and the IP address of the corresponding IP version, and whether the route status is available; SIP load balancer 1 sends a route consistency query request message to SIP load balancer 2. (2.5): SIP load balancer 1 sends a routing consistency query request message to SIP load balancer 3; (2.6): After receiving the route consistency query request message from SIP load balancer 1, SIP load balancer 2 parses the routing information in the message and compares it with the current routing information of this load balancer. If they are consistent, it returns success; otherwise, it returns failure and sends a route consistency query response message to feed back the route consistency detection result to SIP load balancer 1. (2.7): SIP load balancer 3 sends a route consistency query response message and feeds back the route consistency detection result to SIP load balancer 1; (2.8): SIP load balancer 1 receives the route consistency detection results from SIP load balancer 2 and SIP load balancer 3. If both are successful, it returns a successful route activation synchronization confirmation to the SIP signaling processing module n+1 to be expanded; otherwise, it returns a failure confirmation. (2.9): SIP load balancer 2 sends a route consistency query request message to SIP load balancer 1; (2.10): SIP load balancer 2 sends a routing consistency query request message to SIP load balancer 3; (2.11): SIP load balancer 1 sends a route consistency query response message and feeds back the route consistency detection result to SIP load balancer 2; (2.12): SIP load balancer 3 sends a route consistency query response message and feeds back the route consistency detection result to SIP load balancer 2; (2.13): SIP load balancer 2 receives the route consistency detection results from SIP load balancer 1 and SIP load balancer 3. If both are successful, it returns a successful route activation synchronization confirmation to the SIP signaling processing module n+1 to be expanded; otherwise, it returns a failure confirmation. (2.14): SIP load balancer 3 sends a routing consistency query request message to SIP load balancer 1; (2.15): SIP load balancer 3 sends a routing consistency query request message to SIP load balancer 2; (2.16): SIP load balancer 1 sends a route consistency query response message and feeds back the route consistency detection result to SIP load balancer 3; (2.17): SIP load balancer 2 sends a route consistency query response message and feeds back the route consistency detection result to SIP load balancer 3; (2.18): SIP load balancer 3 receives the route consistency detection results from SIP load balancer 1 and SIP load balancer 2. If both are successful, it returns a successful route activation synchronization confirmation to the SIP signaling processing module n+1 to be expanded; otherwise, it returns a failure confirmation. (2.19): The SIP signaling processing module n+1 to be expanded receives the route activation synchronization confirmation from SIP load balancer 1, SIP load balancer 2 and SIP load balancer 3. If all are successful, the module sends the route activation confirmation message to SIP load balancer 1, SIP load balancer 2 and SIP load balancer 3 in parallel. Otherwise, it does not send the message. SIP signaling processing module n+1 sends a route activation confirmation message to SIP load balancer 1; (2.20): SIP signaling processing module n+1 sends a route activation confirmation message to SIP load balancer 2; (2.21): SIP signaling processing module n+1 sends a route activation confirmation message to SIP load balancer 3; (2.22): After SIP load balancers 1, 2 and 3 receive the route activation confirmation message, it means that the expansion of SIP signaling processing module n+1 is successful. After that, each SIP load balancer distributes SIP signaling flow according to the expanded routing table, including sending SIP signaling flow to SIP signaling processing module n+1. After receiving the SIP signaling flow, SIP signaling processing module n+1 continues to process the signaling message. If the routes of each SIP load balancer are inconsistent with the SIP signaling processing module n+1 to be expanded, the route activation process will fail and an error log needs to be output. On-site engineers need to check whether the configuration and network are abnormal.

8. A method for dynamically scaling up and down SIP calls based on route consistency detection according to claim 2, characterized in that... The process for dynamically scaling down the non-SingleIP mode SIP signaling processing module is as follows: (3.1): The network management system triggers the downsizing of the SIP signaling processing module. The SIP signaling processing module to be downsized sends a route deactivation synchronization request to each SIP load balancer in parallel. The SIP signaling processing module n+1 to be downsized sends a route deactivation synchronization request message to SIP load balancer 1. (3.2): The SIP signaling processing module n+1 to be scaled up sends a route deactivation synchronization request message to the SIP load balancer 2; (3.3): The SIP signaling processing module n+1 to be scaled up sends a route deactivation synchronization request message to the SIP load balancer 3; (3.4): After receiving the route deactivation synchronization request, SIP load balancer 1 starts route consistency detection to check whether the routes are consistent with those of other SIP load balancers: it sends route consistency query requests to other SIP load balancers respectively. The request message contains the route information of SIP load balancer 1 and all SIP signaling processing modules. The route information includes the IP version of the SIP signaling processing module and the IP address of the corresponding IP version, and whether the route status is available; SIP load balancer 1 sends a route consistency query request message to SIP load balancer 2. (3.5): SIP load balancer 1 sends a routing consistency query request message to SIP load balancer 3; (3.6): After receiving the route consistency query request message from SIP load balancer 1, SIP load balancer 2 parses the routing information in the message and compares it with the current routing information of this load balancer. If they are consistent, it returns success; otherwise, it returns failure and sends a route consistency query response message to feed back the route consistency detection result to SIP load balancer 1. (3.7): SIP load balancer 3 sends a route consistency query response message and feeds back the route consistency detection result to SIP load balancer 1; (3.8): SIP load balancer 1 receives the route consistency detection results from SIP load balancers 2 and 3. If both are successful, it returns a successful route deactivation synchronization confirmation to the SIP signaling processing module n+1 to be scaled down; otherwise, it returns a failure confirmation. (3.9): SIP load balancer 2 sends a routing consistency query request message to SIP load balancer 1; (3.10): SIP load balancer 2 sends a routing consistency query request message to SIP load balancer 3; (3.11): SIP load balancer 1 sends a route consistency query response message and feeds back the route consistency detection result to SIP load balancer 2; (3.12): SIP load balancer 3 sends a route consistency query response message and feeds back the route consistency detection result to SIP load balancer 2; (3.13): SIP load balancer 2 receives the route consistency detection results from SIP load balancers 1 and 3. If both are successful, it returns a successful route deactivation synchronization confirmation to the SIP signaling processing module n+1 to be scaled down; otherwise, it returns a failure confirmation. (3.14): SIP load balancer 3 sends a routing consistency query request message to SIP load balancer 1; (3.15): SIP load balancer 3 sends a routing consistency query request message to SIP load balancer 2; (3.16): SIP load balancer 1 sends a route consistency query response message and feeds back the route consistency detection result to SIP load balancer 3; (3.17): SIP load balancer 2 sends a route consistency query response message and feeds back the route consistency detection result to SIP load balancer 3; (3.18): SIP load balancer 3 receives the route consistency detection results from SIP load balancers 1 and 2. If both are successful, it returns a successful route deactivation synchronization confirmation to the SIP signaling processing module n+1 to be scaled down; otherwise, it returns a failure confirmation. (3.19): The SIP signaling processing module n+1 to be scaled up receives the route deactivation synchronization confirmation from SIP load balancer 1, SIP load balancer 2 and SIP load balancer 3. If all are successful, the module sends the route deactivation confirmation message to SIP load balancer 1, SIP load balancer 2 and SIP load balancer 3 in parallel; otherwise, it does not send the message. SIP signaling processing module n+1 sends a route deactivation confirmation message to SIP load balancer 1; (3.20): SIP signaling processing module n+1 sends a route deactivation confirmation message to SIP load balancer 2; (3.21): SIP signaling processing module n+1 sends a route deactivation confirmation message to SIP load balancer 3; (3.22): After SIP load balancers 1, SIP load balancer 2 and SIP load balancer 3 receive the route deactivation confirmation message, it means that the SIP signaling processing module n+1 has been successfully scaled down. After that, each SIP load balancer distributes SIP signaling flow according to the scaled-down routing table, that is, it no longer sends new SIP call initiation messages to SIP signaling processing module n+1, but forwards subsequent SIP signaling messages that have already been online. Waiting for the SIP signaling processing module n+1 to report that session resources have been released; Then, through the network management system, delete the routing configuration of the scaled-down SIP signaling processing module n+1; and delete the routing configuration of each SIP load balancer to the scaled-down SIP signaling processing module n+1. If the routes of each SIP load balancer and the SIP signaling processing module n+1 to be scaled down are inconsistent, the routing deactivation process will fail and an error log needs to be output. On-site engineers need to check whether the configuration and network are abnormal.

9. A method for dynamically scaling up and down SIP calls based on route consistency detection according to claim 2, characterized in that... The process for dynamically expanding the SingleIP mode SIP signaling processing module is as follows: (4.1): SIP load balancer 1, SIP load balancer 2 and SIP load balancer 3 communicate with SIP signaling processing module n+1 to send and receive SIP signaling streams, but SIP signaling processing module n+1 has not yet received and processed SIP messages. (4.2): The SIP signaling processing module n+1 to be expanded and each SIP load balancer perform a route activation synchronization process based on route consistency detection. (4.3): The CSCF sends a SIP initiation message to the SIP load balancer 3; (4.4): After receiving the SIP call initiation message, SIP load balancer 3 sends SIP flow table synchronization requests to SIP load balancer 1 and SIP load balancer 2 in parallel. The request message contains the SIP flow table identifier and SIP Call-Id. SIP load balancer 3 sends a SIP flow table synchronization request to SIP load balancer 1. (4.5): SIP load balancer 3 sends a SIP flow table synchronization request to SIP load balancer 2; (4.6): If the SIP flow table synchronization is completed, each SIP load balancer will then distribute SIP signaling flows according to the expanded routing table, including the SIP signaling flows that can be sent to the SIP signaling processing module n+1, including SIP initiation messages. (4.7): SIP signaling processing module n+1 receives and processes SIP signaling messages.

10. A method for dynamically scaling up and down SIP calls based on route consistency detection according to claim 2, characterized in that... The process for dynamically scaling down the SingleIP mode SIP signaling processing module is as follows: (5.1): SIP signaling streams are sent and received between the SIP load balancer and the SIP signaling processing module n+1. The SIP signaling processing module n+1 to be scaled up processes SIP signaling messages normally. (5.2): The SIP signaling processing module n+1 to be scaled down and each SIP load balancer perform a route deactivation synchronization process based on route consistency detection. (5.3): The CSCF sends a SIP initiation message to the SIP load balancer 3; (5.4): After receiving the SIP call initiation message, SIP load balancer 3 sends SIP flow table synchronization requests to SIP load balancer 1 and SIP load balancer 2 in parallel. The request message contains the SIP flow table identifier and SIP Call-Id. SIP load balancer 3 sends a SIP flow table synchronization request to SIP load balancer 1. (5.5): SIP load balancer 3 sends a SIP flow table synchronization request to SIP load balancer 2; (5.6): After the routing consistency test is completed, each SIP load balancer distributes SIP signaling flow according to the reduced routing table, no longer sends SIP initiation message to SIP signaling processing module n+1, but forwards subsequent SIP signaling messages that have been online before. (5.7): SIP load balancer 1, SIP load balancer 2 and SIP load balancer 3 communicate with SIP signaling processing module n+1 to send and receive SIP streams; (5.8): Wait for the SIP signaling processing module n+1 to report that the session resource release is complete; Then, through the network management system, delete the routing configuration of the scaled-down SIP signaling processing module n+1, and delete the routing configuration of each SIP load balancer to the scaled-down SIP signaling processing module n+1.

Images