Working method of multiple SDP controllers
By grouping SDP clients in the SDP system and updating the controller list using arrangement and combination methods, the resource waste and single point failure problems in the coordination work of multiple SDP controllers are solved, load balancing and system resilience are achieved, and system stability is improved. and responsiveness.
Patent Information
- Application Number
- CN202411235725.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-04
- Publication Date
- 2024-12-06
AI Technical Summary
In a software-defined boundary (SDP) system, multiple SDP controllers coordinate working modes have waste of resources and complex configuration management problems, and face the problems of single point of failure and poor performance, especially when bursts of large number of authentication requests .
By grouping SDP clients and setting a different SDP controller list for each group, the controller list is updated in a permutation combination manner, synchronous updates when adding or deleting controllers, and setting counters and thresholds to manage load balancing and failover , and a timeout retransmission mechanism is performed if necessary to ensure connection reliability.
It realizes full utilization of resources, avoids resource waste, improves system resilience and load balancing capabilities, alleviates the risk of single point failure, and improves the stability and response capabilities of the system, solving the problems of poor performance and DoS attacks.
Smart Images

Figure CN119094352A_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the technical field of network security, and in particular relates to a multi-SDP controller working method. Background Art
[0002] Software Defined Perimeter (SDP) is a security framework that creates a security boundary based on policies to isolate services from unsafe networks. It replaces traditional physical boundary defense devices through logical dynamic control. It is designed to provide on-demand, dynamic security isolation networks. Before authorizing access, users and devices are authenticated first so that users and devices can safely connect to isolated services. Unauthorized users and devices cannot connect to protected resources. The core idea of SDP is to hide core network assets and facilities through the SDP architecture so that they are not directly exposed to the Internet, thereby protecting network assets and facilities from external security threats.
[0003] SDP consists of three major components: SDP client, SDP gateway, and SDP controller. The SDP controller is the brain of SDP, mainly responsible for host authentication and policy delivery. It can also be used to authenticate and authorize SDP clients and configure connections to SDP gateways.
[0004] However, when the SDP controller faces a sudden and large number of authentication requests, the SDP system will have performance degradation and system paralysis. To solve this problem, multiple SDP controllers are often deployed in the application to monitor and process SPA packets. However, when multiple SDP controllers are deployed, there is the problem of coordinating the working mode of multiple SDP controllers. Summary of the invention
[0005] In order to overcome the above-mentioned shortcomings of the prior art, the object of the present invention is to provide a multi-SDP controller working method, so as to enable multiple SDP controllers to work in coordination, promote load balancing, enhance the overall system resilience, and alleviate the risk of single point of failure (SPoF).
[0006] In order to achieve the above object, the technical solution adopted by the present invention is:
[0007] A multi-SDP controller working method, the implementation of which includes:
[0008] The SDP clients in the SDP system are grouped, and a different SDP controller list is set for each SDP client group, wherein the list is in a permutation and combination manner; when a new SDP controller is added or an old SDP controller is deleted, the SDP controller lists of all SDP client groups in the SDP system are updated accordingly;
[0009] All SDP controllers in the SDP system have the same SDP gateway IP address list. When a new SDP gateway is added or an old SDP gateway is deleted, each SDP controller synchronously updates the SDP gateway IP address list.
[0010] In one embodiment, the SDP client groups refer to that under the same grouping condition, each SDP client belongs to and only belongs to one SDP client group.
[0011] In one embodiment, a different SDP controller list is set for each SDP client group, and the list is arranged in a permutation and combination manner, and the implementation method is as follows:
[0012] For an SDP system with M SDP controllers and N SDP client groups, for each SDP client group, the M SDP controllers are arranged and combined, and the list obtained by each arrangement and combination is used as the SDP controller list of an SDP client group, and the first SDP controller in the list is used as the default controller of the current SDP client group. In the same SDP client group, all SDP clients send requests to the default controller by default first.
[0013] For example, in the SDP system, the number of SDP controllers and the number of SDP client groups may be the same, that is, M may be equal to N.
[0014] In one embodiment, when a new SDP controller is added or an old SDP controller is deleted, the controller list of all SDP client groups in the SDP system is updated accordingly, and the implementation method is as follows:
[0015] Add the IP address of the new SDP controller or delete the IP address of the old SDP controller in the controller list of all SDP client groups.
[0016] In one embodiment, each of the SDP controllers is provided with a counter and a threshold, wherein the counter is used to record the number of received single-packet authorized SPA data packets; the threshold is used to set a critical value for the working content of the SDP controller; only when the count value of the counter is less than the threshold, the SDP controller can continue to receive SPA data packets from the SDP client.
[0017] In one embodiment, the threshold is a maximum value of a SPA data packet from an SDP client that the SDP controller can receive while ensuring its performance.
[0018] In one embodiment, a timeout retransmission mechanism is set for the SDP client; a timer and a time threshold are set on the SDP client, and the SDP system uses single-packet authorization and authentication SPA (usually UDP data packet) technology. After the SDP client sends a SPA data packet, its timer is started. When the value of the timer is equal to the time threshold, and the SDP client has not received the SDP gateway list sent by the SDP controller, the SDP client resends the SPA data packet to the SDP controller until it is sent successfully.
[0019] In one embodiment, for a connection request, the SDP client adjusts its access to the SDP controller; a counter and a threshold are set on the SDP client; the counter is used to record the number of times the SDP client sends a SPA data packet to the same SDP controller, and the SDP client first sends a SPA data packet to a default controller in a controller list, and if no response data packet is received from the SDP controller, the SDP client sends a SPA data packet to the default controller again; if the counter is greater than the threshold and the SDP client does not receive a response data packet from the SDP controller, the SDP client sends a SPA data packet to the second SDP controller in the controller list, and so on.
[0020] In one embodiment, when a new SDP gateway is added or an SDP gateway is deleted, each SDP controller synchronously updates the SDP gateway IP address list, and the implementation method is as follows:
[0021] Add the IP address of a new SDP gateway or delete the IP address of an old SDP gateway for all SDP gateways in the SDP system.
[0022] Compared with the prior art, the present invention has the following beneficial effects:
[0023] At present, the working modes of multiple SDP controllers include active-standby mode and cluster mode. In the active-standby mode, the role of the standby machine is backup. If the standby machine is always in standby state, it will cause a waste of resources. For the cluster mode, its configuration and management are relatively complex. Since cluster service technology can only be performed on one server, the cluster mode still has a single point of failure problem. Due to the separation of read and write, the cluster mode may affect data consistency. In the multi-SDP controller working method proposed in this paper, multiple SDP controllers work in coordination, which can make full use of resources and avoid resource waste. This method can also promote load balancing and comprehensive system resilience, and alleviate the risk of single point of failure (SPoF). In addition, the coordinated work of multiple SDP controllers proposed in this paper can solve the problem of sudden and large number of authentication requests causing poor performance of SDP controllers and alleviate Dos attacks. BRIEF DESCRIPTION OF THE DRAWINGS
[0024] In order to more clearly illustrate the technical solutions in the present application or the prior art, a brief introduction will be given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.
[0025] Figure 1 Schematic diagram of an SDP system according to an embodiment of the present invention. DETAILED DESCRIPTION
[0026] In order to make the purpose, technical solutions and advantages of this application clearer, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0027] The present invention is a multi-SDP controller working method. In an SDP system, each SDP client is grouped, and a different SDP controller list is set for each SDP client group, wherein the list adopts a permutation and combination method. When a new SDP controller is added or an old SDP controller is deleted, the SDP controller lists of all SDP client groups in the SDP system are updated accordingly; and all SDP controllers have the same SDP gateway IP address list, which includes the IP addresses of all available SDP gateways. When a new SDP gateway is added or an old SDP gateway is deleted, each SDP controller also needs to synchronously update the SDP gateway IP address list.
[0028] By the above means, each SDP client group has a specific SDP controller list, and different combinations can be selected from a group of SDP controllers to provide services for each client group, thereby allowing the system to flexibly adjust according to the needs of the clients and the availability of SDP controllers.
[0029] When a new SDP controller is added, the IP address of the new SDP controller is added to the SDP system, and the SDP system arranges and combines the IP address of the newly added SDP controller with the IP address of the existing SDP controller, and sends the arranged and combined SDP controller list to the SDP client group. When an SDP controller IP address is deleted, the SDP system arranges and combines the IP addresses of the existing SDP controllers, and sends the arranged and combined SDP controller list to the SDP client group.
[0030] In addition, when a new SDP gateway is added, the IP address of the new SDP gateway is added to the SDP system, and the SDP system adds the IP address of the newly added SDP gateway to the SDP gateway list of all SDP controllers. When an SDP gateway is deleted, the SDP system deletes the IP address of the SDP gateway from the gateway list of all SDP controllers.
[0031] When a new SDP controller is added to the system or an existing SDP controller needs to be deleted, first identify which SDP controllers are newly added and which are deleted. Regenerate the SDP controller list for each SDP client group based on the newly identified controller changes. After the update is complete, the system needs to notify all affected SDP clients of the new SDP controller list, which can be done by sending an updated SDP message. After the SDP client receives the new controller list, it can use the new controller for communication.
[0032] At the same time, when a new SDP gateway is added to the system or an existing SDP gateway is deleted, the newly added or deleted SDP gateway is first detected and their IP addresses are obtained, and then the SDP gateway IP address list is updated, including adding new IP addresses or removing no longer needed IP addresses from the list. The updated SDP gateway IP address list is then synchronized to all SDP controllers. After receiving the new IP address list, the SDP controller updates the routing table or communication configuration to communicate through the correct SDP gateway.
[0033] Through the above design, the system has a high degree of flexibility and scalability, allowing the system to dynamically adjust resource allocation according to actual needs.
[0034] The SDP client grouping of the present invention means that under the same grouping condition, each SDP client belongs to and only belongs to one SDP client group. That is, the SDP clients can be grouped according to different conditions, for example, the SDP clients can be grouped according to the different subsidiaries to which the users belong, and one subsidiary user is one SDP client group. The SDP clients can also be grouped in a balanced manner according to the number of users. For example, a company has 10,000 people, and the users are divided into two SDP client groups, each with 5,000 users.
[0035] The present invention sets a different SDP controller list for each SDP client group, and the list adopts a permutation and combination method, specifically referring to:
[0036] For ease of description, in the present invention, for an SDP system having M SDP controllers and N SDP client groups, for each SDP client group, the M SDP controllers are arranged and combined, and a list obtained by each arrangement and combination is used as an SDP controller list of an SDP client group, and the first SDP controller in the list is used as the default controller of the current SDP client group. In the same SDP client group, all SDP clients send requests to the default controller by default first.
[0037] The method can be specifically described as:
[0038] Perform full permutations of the M SDP controllers to generate M! different permutations. Each permutation represents a possible SDP controller list. Assign these permutations to different SDP client groups. Each group will get a unique permutation as its SDP controller list to ensure that different groups have different controller orders, thereby achieving load balancing and failover. In the SDP controller list of each SDP client group, the first controller in the list is set as the default controller for the group. This means that the SDP client in the group will first send requests to this default controller.
[0039] When an SDP client wants to access a resource, it sends a request to its default controller. If the default controller does not respond, the SDP client can send requests to subsequent controllers in the order in the list until an available controller is found.
[0040] At the same time, the system of the present invention has the ability to dynamically update the SDP controller list, that is, when a new controller joins or an existing controller exits, the controller list of all affected SDP client groups is rearranged and updated.
[0041] In this way, the SDP system can flexibly manage controller resources while providing high availability and load balancing.
[0042] For example, the working method of a multi-SDP controller of the present invention can refer to Figure 1In the embodiment shown, the number of SDP controllers is the same as the number of SDP client groups, that is, M=N=3. The three SDP controllers are SDP controller 1, SDP controller 2 and SDP controller 3, and the SDP client groups are client-group 1, client-group 2 and client-group 3, respectively, and there are two gateways, SDP gateway 1 and SDP gateway 2. The controller list of client-group 1 is SDP controller 1, SDP controller 2 and SDP controller 3, and SDP controller 1 is its default controller; the controller list of client-group 2 is SDP controller 2, SDP controller 1 and SDP controller 3, and SDP controller 2 is its default controller; the controller list of client-group 3 is SDP controller 3, SDP controller 2 and SDP controller 1, and SDP controller 3 is its default controller.
[0043] Furthermore, in the SDP system, when a new SDP controller is added or an existing controller is removed, the system needs to ensure that the controller list of all SDP client groups is kept up to date to maintain the efficiency and reliability of the system. Specifically, the IP address of the new SDP controller is added or the IP address of the old SDP controller is deleted from the controller list of all SDP client groups. The method can be described as follows:
[0044] The SDP system maintains a list of SDP controllers. When a new SDP controller is added, the IP address of the new SDP controller is added to the SDP system. The SDP system arranges and combines the IP address of the newly added SDP controller with the IP address of the existing SDP controller, and sends the arranged and combined SDP controller list to the SDP client group. When the SDP controller IP address is deleted, the SDP system arranges and combines the IP addresses of the existing SDP controllers, and sends the arranged and combined SDP controller list to the SDP client group.
[0045] The system first detects the addition of a new SDP controller or the removal of an existing SDP controller, which can be achieved by monitoring the system status or configuration updates received. The system can maintain a global SDP controller library containing the IP addresses of all available SDP controllers. The IP addresses of new controllers are added to the library and the IP addresses of old controllers are removed from the library. When the list of controllers changes, the system needs to recalculate all possible permutations to ensure that each SDP client group can obtain an updated and valid list of controllers.
[0046] Based on the recalculated permutations, the system assigns a new SDP controller list to each SDP client group. The new list will contain the IP addresses of newly added controllers, or, where appropriate, exclude the IP addresses of deleted controllers. In addition, for each SDP client group, a new default controller needs to be determined and all SDP client groups are notified of the new controller list and default controller by sending a system update message or using a configuration server. After receiving the new controller list, the SDP client updates its configuration and begins communicating with the new default controller. When updating the controller list, the system needs to ensure compliance with security protocols to prevent unauthorized modifications and protect the controller IP addresses from being disclosed. All changes to the controller list should also be recorded, including the time, reason, and executor of the change.
[0047] Through the above steps, the SDP system can effectively manage the addition and removal operations of SDP controllers, ensuring that the controller lists of all SDP client groups are always kept up to date while maintaining the stability and performance of the system.
[0048] In an embodiment of the present invention, in order to effectively manage network traffic and resources, a counter and a threshold are set for each SDP controller, wherein the counter is used to record the number of received single-packet authorized SPA data packets, and its initial value can be set to zero; the threshold is used to set the critical value of the working content of the SDP controller, and the setting of the threshold can be based on a variety of factors, such as network capacity, controller performance, service quality requirements, etc. For example, this embodiment sets the threshold as the maximum value of the SPA data packet that the SDP controller can receive from the SDP client while ensuring its performance. This embodiment defines the rule: the SDP controller can continue to receive SPA data packets from the SDP client only when the count value of the counter is less than the threshold. Once the value of the counter reaches the threshold, the SDP controller will enter the flow control state and stop receiving new SPA data packets, thereby preventing the controller from being overloaded and ensuring that existing sessions are not affected.
[0049] Furthermore, in this embodiment, a timeout retransmission mechanism is set in the SDP client, and a timer and a threshold are set. When the timer is equal to or exceeds the threshold, the SDP client does not receive a response data packet from the SDP controller, and the SDP client resends the SPA data packet to the SDP controller.
[0050] Furthermore, in this embodiment, the threshold in the timeout retransmission mechanism can be dynamically adjusted according to the network environment status and service requirements to adapt to different network environments and requirements.
[0051] Through the above mechanisms, the SDP system can manage network resources more intelligently and efficiently, improve system stability and responsiveness, and enhance user experience.
[0052] In an embodiment of the present invention, the SDP client sends a SPA data packet (usually a UDP data packet) to the SDP controller and the SDP gateway. In order to alleviate the problems of resource waste, time waste, and service quality degradation caused by the infinite waiting of the SDP client, it is very important to set a timeout retransmission mechanism in the SDP client. Based on this, this embodiment sets a timer and a time threshold (for example, 5 seconds) for the SDP client. The timer is used to calculate the waiting time after the SDP client sends a SPA data packet. The time threshold is the maximum waiting time after the SDP client sends a SPA data packet.
[0053] The SDP client sends a SPA packet to the SDP controller or SDP gateway to apply for access. After the SDP client completes the sending, the timer is started immediately. The SDP client waits for a response packet from the SDP controller while the timer value is equal to or greater than the time threshold. During the entire process of the timer running, the SDP client periodically checks whether the timer value has equaled or exceeded the set time threshold. When the timer value is equal to the time threshold, and the SDP client has not received a response packet sent by the SDP controller or SDP gateway, the SDP client believes that the sent SPA packet may have been lost or failed to be successfully delivered. The SDP client resends the SPA packet to the SDP controller or SDP gateway and resets the timer. Until the sending is successful. If the SDP client receives a response packet from the SDP controller or SDP gateway before the timer is equal to or before the time threshold, the timer stops.
[0054] Furthermore, in order to prevent the SDP client from waiting and retransmitting indefinitely, wasting time and network resources, and causing the SDP system performance to deteriorate, this embodiment sets a limit on the number of retransmissions on the SDP client. Set a counter and a threshold. The counter records the number of retransmissions by the SDP client, and the threshold is the maximum number of retransmissions. For example, the client can set the number of retransmissions to no more than 3 times.
[0055] Furthermore, in order to reduce network congestion, the SDP client in this embodiment may use an exponential backoff algorithm to increase the retransmission time interval each time it retransmits.
[0056] Furthermore, the SDP client can dynamically adjust the timeout threshold according to network conditions and historical data to optimize transmission efficiency.
[0057] Furthermore, if the number of retransmissions reaches the upper limit and still no response is received, the SDP client may take error handling measures, such as recording a log or using a backup SDP controller in the SDP controller list of the SDP client.
[0058] By implementing a timeout retransmission mechanism, the SDP system can improve the reliability of data transmission and ensure that even when network conditions are poor or temporary failures occur, the SDP client can successfully connect to the SDP controller and SDP gateway, thereby maintaining the normal operation of the SDP system.
[0059] In an embodiment of the present invention, in order to ensure the reliability of the connection request and the robustness of the system, the SDP client can use a counter and threshold mechanism to adjust its behavior of accessing the SDP controller. Based on this, in this embodiment, for the connection request, the SDP client adjusts its access to the SDP controller; a counter and a threshold are set at the SDP client; the counter is used to record the number of times the SDP client sends a SPA data packet to the same SDP controller, and the threshold is a preset number used to determine the upper limit of the retry operation when no response is received. The SDP client first sends a SPA data packet to the default controller in the controller list to request access to resources. After the SDP client sends the SPA data packet, the SDP client enters a waiting state, waiting for a response data packet from the default controller. If the response data packet of the SDP controller is not received within a certain period of time, the SDP client resets the counter and increases the count, and the SDP client sends a SPA data packet to the default controller again; after each retry, the SDP client updates the value of the counter. The SDP client checks the value of the counter after each retry. If the counter is greater than the threshold and the SDP client does not receive a response packet from the SDP controller, the SDP client sends a SPA packet to the next SDP controller in its controller list (usually means turning to the second controller in the list), and so on. That is, if the second controller also fails to respond within the specified number of times, the SDP client will continue to traverse its controller list and send SPA packets to each controller in sequence until an available controller is found.
[0060] Furthermore, the SDP client in this embodiment can dynamically adjust the threshold according to the network status and historical data to adapt to different network environments and improve efficiency.
[0061] Through this mechanism, the SDP client can process connection requests in an orderly and controllable manner, and can effectively find available controllers even when faced with network instability or controller unavailability, thereby improving the connection success rate and the overall stability of the system.
[0062] In an embodiment of the present invention, the server is protected by an isolation mechanism of single packet authorization (SPA) technology, making unauthorized users and devices invisible and unable to access the server. Single Packet Authorization (SPA) technology is a network security mechanism that aims to complete the identity authentication process through a single encrypted data packet, thereby improving security and efficiency. SPA technology can enhance the security of the server by reducing the visibility of the server to unauthorized users. Specifically, SPA technology has a port hiding effect, that is, in the SDP system, the server's firewall is set to discard all data packets, so unauthorized users cannot scan the server port. That is, the SDP client must first send a SPA data packet to the SDP controller. This data packet contains authentication information (such as user name, password, target service identifier). After receiving the SPA data packet, the SDP controller verifies the authentication information in the data packet. After the SDP client is authenticated, the SDP controller determines the list of SDP gateways that the SDP client is authorized to connect to. The SDP controller notifies the SDP gateway to accept communications from the SDP client. The SDP controller sends the SDP gateway list to the SDP client. The SDP client sends a SPA data packet to the authorized SDP gateways, and then the SDP client and these SDP gateways create a two-way encrypted connection (two-way TLS authentication). The SDP gateway does not accept any access request packets from unauthorized SDP clients. SPA technology follows the principle of minimum authorization, that is, the system will only open the relevant ports of the corresponding resources for client access authorization, and non-essential access ports will remain closed. After the SDP client is verified, the access rights are only authorized for a period of time, and the established connection is not permanent. Therefore, SPA technology mitigates the threats brought by port scanning and related reconnaissance technologies, significantly reducing the attack surface of the entire SDP system. SPA makes the service visible only to authenticated users, mitigating DDoS attacks.
[0063] In an embodiment of the present invention, before the SDP client establishes a TCP connection with the SDP controller and the SDP gateway, a single packet authorization SPA authentication is performed to ensure that only legitimate clients can continue to establish subsequent connections. The SDP client sends a SPA request data packet to the SDP controller and the SDP gateway. This data packet usually contains the client's user name, password, target service identifier, etc. Before the SDP client passes the identity authentication authorization, the SDP controller and the SDP gateway will not respond to any connection request, thereby preventing unauthorized access.
[0064] When the SDP gateway changes, all SDP controllers must update their respective SDP gateway IP address lists in a timely manner. Therefore, in an embodiment of the present invention, when a new SDP gateway is added or an SDP gateway is deleted, each SDP controller synchronously updates the SDP gateway IP address list, and the specific method may be:
[0065] The system maintains an SDP gateway IP address list, which contains the IP addresses of all SDP gateways. When changes occur, the system will update this list, including adding the IP address of a new gateway or removing the IP address of an old gateway that is no longer in use from the list. After updating the SDP gateway IP address list, all SDP controllers need to be notified of the change. After each SDP controller receives the change notification, it updates its internal SDP gateway IP address list to ensure consistency with the global list.
[0066] Through this synchronous update mechanism, the SDP system can ensure that all SDP controllers use the latest SDP gateway IP address list, thereby maintaining system stability and performance.
[0067] Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. Such modifications or replacements that do not depart from the technical solution of the present invention should all be included in the scope of the technical solution for which protection is sought in the present invention.
Claims
1. A multi-SDP controller working method, characterized in that: Its implementation includes: The SDP clients in the SDP system are grouped, and a different SDP controller list is set for each SDP client group, wherein the list is in a permutation and combination manner; when a new SDP controller is added or an old SDP controller is deleted, the SDP controller lists of all SDP client groups in the SDP system are updated accordingly; All SDP controllers in the SDP system have the same SDP gateway IP address list. When a new SDP gateway is added or an old SDP gateway is deleted, each SDP controller synchronously updates the SDP gateway IP address list.
2. The multi-SDP controller working method according to claim 1, characterized in that: The SDP client groups refer to that under the same grouping condition, each SDP client belongs to and only belongs to one SDP client group.
3. The multi-SDP controller working method according to claim 1, characterized in that: A different SDP controller list is set for each SDP client group, and the list is arranged in a permutation and combination manner, and the implementation method is as follows: For an SDP system with M SDP controllers and N SDP client groups, for each SDP client group, the M SDP controllers are arranged and combined, and the list obtained by each arrangement and combination is used as the SDP controller list of an SDP client group, and the first SDP controller in the list is used as the default controller of the current SDP client group. In the same SDP client group, all SDP clients send requests to the default controller by default first.
4. The multi-SDP controller working method according to claim 1, characterized in that: When a new SDP controller is added or an old SDP controller is deleted, the controller list of all SDP client groups in the SDP system is updated accordingly. This is achieved as follows: Add the IP address of the new SDP controller or delete the IP address of the old SDP controller in the controller list of all SDP client groups.
5. The multi-SDP controller working method according to claim 1, characterized in that: Each of the SDP controllers is provided with a counter and a threshold, wherein the counter is used to record the number of received single-packet authorized SPA data packets; the threshold is used to set a critical value for the working content of the SDP controller; only when the count value of the counter is less than the threshold, the SDP controller can continue to receive SPA data packets from the SDP client.
6. The multi-SDP controller working method according to claim 5, characterized in that: The threshold is the maximum value of the SPA data packet from the SDP client that the SDP controller can receive while ensuring its performance.
7. The multi-SDP controller working method according to claim 5 or 6, characterized in that: A timeout retransmission mechanism is set for the SDP client; a timer and a time threshold are set on the SDP client. The SDP system uses the single-packet authorization and authentication SPA technology. The SDP client starts its timer after sending a SPA data packet. When the timer value is equal to the time threshold, and the SDP client has not received the SDP gateway list sent by the SDP controller, the SDP client resends the SPA data packet to the SDP controller until it is sent successfully.
8. The multi-SDP controller working method according to claim 1, characterized in that: For a connection request, the SDP client adjusts its access to the SDP controller; a counter and a threshold are set on the SDP client; the counter is used to record the number of times the SDP client sends a SPA data packet to the same SDP controller. The SDP client first sends a SPA data packet to the default controller in the controller list. If no response data packet is received from the SDP controller, the SDP client sends a SPA data packet to the default controller again; if the counter is greater than the threshold and the SDP client does not receive a response data packet from the SDP controller, the SDP client sends a SPA data packet to the second SDP controller in the controller list, and so on.
9. The multi-SDP controller working method according to claim 1, characterized in that: When a new SDP gateway is added or an SDP gateway is deleted, each SDP controller synchronously updates the SDP gateway IP address list, and the implementation method is as follows: Add the IP address of a new SDP gateway or delete the IP address of an old SDP gateway for all SDP gateways in the SDP system.
