User authentication method, system and device based on load balancer and RADIUS server and readable medium

Abstract

The invention provides a user authentication method, system and device based on a load balancer and an RADIUS server and a readable medium, and the user authentication method comprises the steps: receiving a user authentication request by any load balancer, and carrying out the preliminary evaluation and classification of the user authentication request according to a preset load balancing strategy; the request distribution strategy is dynamically adjusted according to the RADIUS server performance indexes collected in real time, and then the user authentication request is sent to any RADIUS server to be processed; if any selected RADIUS server operates normally, the RADIUS server processes the user authentication request and returns an authentication result; otherwise, the user authentication request is automatically returned to any load balancer, and any load balancer sends the user authentication request to other RADIUS servers again for processing; according to the method, the load balancer is introduced and the request processing process of the RADIUS server is optimized, so that the processing capability and the fault tolerance of the RADIUS server are improved, and the high availability and the load balance of the RADIUS server are realized.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of information security and network access technology, and particularly relates to a user authentication method, system and device based on a load balancer and a Remote Authentication Dial In User Service (RADIUS) server and a readable medium. BACKGROUND

[0002] This section is intended to provide background information to facilitate a better understanding of embodiments of the present application. It is not admitted that any of the information provided in this section is prior art.

[0003] With the rapid development of Internet services, the RADIUS server plays an important role in network access control and identity verification. However, the traditional RADIUS server has performance bottlenecks, single point of failure and load imbalance, which affects the stability and reliability of network services.

[0004] Therefore, a solution is needed to solve the technical defects of the traditional RADIUS server (such as a single point of failure rate of more than 30%), improve the processing capacity and fault tolerance of the RADIUS server, and realize the high availability and load balancing of the RADIUS server to ensure the stability and reliability of network services. SUMMARY

[0005] Based on the above technical defects, the purpose of the present application is to provide a user authentication method based on a load balancer and a RADIUS server to solve the performance bottleneck and single point of failure problems of the traditional RADIUS server.

[0006] Aspects of the present application provide a user authentication method, system, device and readable medium based on a load balancer and a RADIUS server to realize the high availability and load balancing of the RADIUS server to ensure the stability and reliability of network services.

[0007] In one aspect of the present application, a user authentication method based on a load balancer and a RADIUS server is provided. The method comprises: any load balancer receiving a user authentication request, and performing preliminary evaluation and classification on the user authentication request according to a preset load balancing strategy, and dynamically adjusting a request distribution strategy according to real-time collected RADIUS server performance indicators, and then sending the user authentication request to any RADIUS server for processing; if the selected any RADIUS server is in normal operation, the selected any RADIUS server processes the user authentication request and returns an authentication result; if the selected any RADIUS server is not in normal operation, the selected any RADIUS server automatically returns to the any load balancer, and the any load balancer re-sends the user authentication request to other RADIUS servers for processing.

[0008] Further, the preset load balancing strategy comprises: the load balancer classifies the user authentication request by traffic type, and matches a differentiated load strategy based on the classification result.

[0009] Further, the traffic type comprises user identity priority, request service type, and source geographical location.

[0010] Further, the real-time collected RADIUS server performance indicators comprise CPU utilization, memory usage, and current load condition.

[0011] Further, a health check mechanism of the RADIUS server is arranged on the any load balancer, wherein the any load balancer periodically sends a health check request to the any RADIUS server, the any RADIUS server responds to the health check request and returns its own health information, and the any load balancer determines whether the any RADIUS server is in normal operation according to the returned health information.

[0012] Further, the health information comprises response delay time, error rate, and service availability.

[0013] Further, if it is determined that the any RADIUS server is not in normal operation, the any load balancer removes the any RADIUS server from a request distribution list, and sends updated request distribution list information to all load balancers.

[0014] Further, data is synchronized and backed up between the plurality of RADIUS servers, wherein the data comprises: load conditions and state information of the plurality of RADIUS servers.

[0015] In another aspect of the present application, a user authentication system based on load balancer and RADIUS server is provided, which comprises: a plurality of RADIUS servers for processing user authentication requests; and a plurality of load balancers connected to the plurality of RADIUS servers for receiving the user authentication requests and distributing the requests to the plurality of RADIUS servers according to the load conditions of the RADIUS servers.

[0016] Further, any of the load balancers further comprises: a traffic analysis module for analyzing network traffic and dynamically adjusting a load balancing strategy of the load balancer; a strategy distribution module for preliminarily evaluating and classifying the user authentication requests according to the load balancing strategy; a health monitoring module for periodically monitoring the health status of the plurality of RADIUS servers and removing an abnormal RADIUS server from a request distribution list; and an automatic recovery module for automatically rejoining an abnormal RADIUS server to the request distribution list after the abnormal RADIUS server is recovered.

[0017] Further, the strategy distribution module of any of the load balancers supports a round robin, a weighted least connections and a geo-based routing strategy.

[0018] Further, any of the RADIUS servers further comprises: a monitoring module for monitoring the overall performance of the system and the status of each component; an alarm module for issuing an alarm when the performance of the system is degraded or a component is abnormal; and a data storage module for synchronizing data and backing up data among the plurality of RADIUS servers.

[0019] Further, any of the RADIUS servers is deployed at a central node and an edge node, and the authentication requests received by the edge node are transmitted back to the central node for processing.

[0020] In another aspect of the present application, an electronic device is provided, which comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the user authentication method based on load balancer and RADIUS server as described above.

[0021] In another aspect of the present application, a computer readable storage medium is provided, which stores computer program instructions executable by a processor to implement the user authentication method based on load balancer and RADIUS server.

[0022] Another aspect of this application provides a computer program product, including a computer program that, when executed by a processor, implements the user authentication method based on a load balancer and a RADIUS server.

[0023] The purpose of this application is to propose a user authentication method based on a load balancer and a RADIUS server to address the performance bottlenecks and single points of failure issues of traditional RADIUS servers. The specific implementation includes: First, by introducing a load balancer, the processing capacity of the RADIUS server is improved, while simultaneously enhancing its fault tolerance, thus achieving high availability. Second, by optimizing the request processing process, request processing latency is reduced, improving the stability of the RADIUS server. This addresses the limitations of existing technologies in handling real-time requests. Third, by rationally distributing requests through load balancing, load balancing is achieved across multiple servers, reducing the load on individual servers, improving overall performance and stability, thereby enhancing user experience and network service quality. This also addresses the limitations of existing technologies in handling dynamic load adjustments. Attached Figure Description

[0024] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0025] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings: Figure 1 A flowchart illustrating a user authentication method provided in an embodiment of this application; Figure 2 A flowchart illustrating a user authentication method provided in another embodiment of this application; Figure 3 This is a schematic diagram of the system architecture of this application; Figure 4 This is a schematic diagram of the system business process of this application; Figure 5 This is a schematic diagram of the load balancer for the subsystem of this application; Figure 6 This is a schematic diagram of the RADIUS server, a subsystem of this application; Figure 7 This is a schematic diagram of the structure of an electronic device suitable for implementing the solutions in the embodiments of this application. Detailed Implementation

[0026] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0027] In a typical configuration of this application, the terminal and the service network devices each include one or more processors, input / output interfaces, network interfaces, and memory.

[0028] Memory may include non-persistent storage in computer-readable media, random access memory, and / or non-volatile memory, such as read-only memory or flash memory. Memory is an example of computer-readable media.

[0029] Computer-readable media include permanent and non-permanent, removable and non-removable media, which can store information by any method or technology. Information can be computer program instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory, static random access memory, dynamic random access memory, other types of random access memory, read-only memory, electrically erasable programmable read-only memory, flash memory or other memory technologies, read-only optical discs, digital versatile optical discs or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transfer medium that can be used to store information accessible by a computing device.

[0030] In practical scenarios, the execution entity of this method can be a user device, or a device formed by integrating a user device and a network device through a network, or it can be an application running on the aforementioned devices. The user device includes, but is not limited to, various terminal devices such as computers, mobile phones, tablets, smartwatches, and smart bands. The network device includes, but is not limited to, network hosts, single network servers, multiple network server sets, or cloud computing-based computer sets, and can be used to implement some processing functions when setting an alarm clock. Here, the cloud consists of a large number of hosts or network servers based on cloud computing. Cloud computing is a type of distributed computing, consisting of a virtual computer composed of a group of loosely coupled computer sets.

[0031] Example 1

[0032] This application provides a user authentication method based on a load balancer and a RADIUS server by introducing a load balancer. Figure 1 This application illustrates a processing flow of a user authentication method according to an embodiment; combined with Figure 3This is a system architecture diagram of this application, and Figure 4 This is a schematic diagram of the system business process of this application, which provides a user authentication system based on a load balancer and a RADIUS server. The system includes: multiple RADIUS servers for processing user authentication requests; and multiple load balancers connected to the multiple RADIUS servers for receiving the user authentication requests and distributing the requests to the multiple RADIUS servers according to their load conditions. The method includes at least the following processing steps: Step S101: Any load balancer first receives the user authentication request.

[0033] Specifically, when a user accesses the authentication system and initiates an authentication request, the request first passes through a load balancer located at the front end of the system. By introducing a load balancer in front of the RADIUS server, the load balancer prioritizes receiving all user authentication requests and then distributes the requests appropriately based on the load of the RADIUS server.

[0034] In step S102, any load balancer will perform a preliminary evaluation and classification of user authentication requests according to the preset load balancing strategy, and dynamically adjust the request allocation strategy based on the real-time collected RADIUS server performance indicators.

[0035] Furthermore, the preliminary evaluation and classification of the user authentication requests includes: the load balancer classifies the user authentication requests by traffic type and matches differentiated load strategies based on the classification results. The traffic type includes user identity priority, request service type, and originating geographical location. The real-time collected RADIUS server performance metrics include CPU utilization, memory utilization, and current load status.

[0036] Specifically, the preset load balancing strategy includes different load balancing strategy designs and implementations to ensure that requests are intelligently distributed to idle or lightly loaded RADIUS servers, avoiding overloading of individual RADIUS servers and improving system efficiency and performance. Policies that can be referenced include: a policy engine that supports three load distribution modes: round-robin, weighted least connections, and geographic location-based optimal routing. Simultaneously, the load balancer can dynamically adjust the load balancing strategy based on real-time monitoring data to adapt to different request loads and traffic patterns. By distinguishing between high-priority user requests and ordinary user requests, it ensures low-latency response for critical business operations. Traffic types include user identity priority, request business type, and origin geographic location.

[0037] Step S103: Send the user authentication request to any RADIUS server for processing.

[0038] Specifically, the load balancer distributes requests to one of the servers in a cluster of multiple RADIUS servers.

[0039] Step S104: Output the result (e.g., error / authentication failure, authentication success).

[0040] The process is further divided into steps S1041, where if any selected RADIUS server is operating normally, it processes the user authentication request and returns the authentication result. Alternatively, in step S1042, if any selected RADIUS server is not operating normally, the request is automatically redirected to any load balancer, which then resends the user authentication request to another RADIUS server for processing. This process is repeated, and the result is output.

[0041] Furthermore, the authentication process is optimized within the RADIUS server to improve the efficiency and performance of request processing, including optimizing authentication, authorization, and accounting processes.

[0042] Furthermore, data is synchronized and backed up across multiple RADIUS servers. This data includes the load and status information of each RADIUS server. Data consistency and backup are ensured between the multiple RADIUS servers through the system's data storage module; alternatively, multi-node data consistency synchronization based on data synchronization protocols such as Raft is used to improve system reliability and disaster recovery capabilities.

[0043] This application is applied to the user authentication scenario of RADIUS server. By introducing a load balancer and based on the interaction process between the load balancer and the working status of the RADIUS server: according to different load balancing strategies (traffic classification, dynamic strategy adjustment), the load balancer can intelligently distribute requests to different RADIUS servers, avoid overloading a single RADIUS server, thereby optimizing the RADIUS server request processing process, improving the processing capacity and fault tolerance of the RADIUS server, and achieving high availability and load balancing of the RADIUS server.

[0044] Example 2

[0045] This application provides a user authentication method based on a load balancer and a RADIUS server by introducing a load balancer and further optimizing the load balancer request processing procedure. Figure 2 This application illustrates a processing flow of a user authentication method according to another embodiment; combined with Figure 3 This is a system architecture diagram of this application, and Figure 4This is a schematic diagram of the system business process of this application, which provides a user authentication system based on a load balancer and a RADIUS server. The system includes: multiple RADIUS servers for processing user authentication requests; and multiple load balancers connected to the multiple RADIUS servers for receiving the user authentication requests and distributing the requests to the multiple RADIUS servers according to their load conditions. The method includes at least the following processing steps: Step S201: Any load balancer first receives the user authentication request.

[0046] In step S202, any load balancer will perform a preliminary evaluation and classification of user authentication requests according to the preset load balancing strategy, and dynamically adjust the request allocation strategy based on the real-time collected RADIUS server performance indicators.

[0047] Since steps S201 and S202 are the same as steps S101 and S102 in the above embodiment, they will not be described in detail.

[0048] In step S203, any load balancer periodically sends a health check request to any RADIUS server. The RADIUS server responds to the health check request and returns its own health information. It also removes any malfunctioning RADIUS servers from the request allocation list. The health information includes response latency, error rate, and service availability indicators.

[0049] Specifically, the system collects performance metrics of each RADIUS server in real time (including CPU utilization, memory usage, and current connection count); allocates authentication requests based on a dynamic weighting algorithm (e.g., the real-time weighting calculation formula based on CPU utilization and connection count: weight = (1 / CPU utilization) × connection count coefficient); performs proactive health checks and sets the check frequency, etc.

[0050] Furthermore, if a server is detected to be operating abnormally or malfunctioning, the load balancer removes it from the request allocation list and records the abnormality information. The load balancer then sends this abnormality information to the monitoring and analysis system for further analysis and alerting. The monitoring and analysis system generates an abnormality report based on the abnormality information and notifies the operations and maintenance personnel to handle the situation.

[0051] By establishing a health check mechanism on the load balancer, the health status of each RADIUS server is monitored regularly, and abnormal servers are promptly identified and removed to ensure system stability.

[0052] Step S204: Send the user authentication request to any RADIUS server for processing.

[0053] Specifically, the load balancer distributes requests to one of the servers in a cluster of multiple RADIUS servers.

[0054] Furthermore, the load balancer distributes the requests to one of the servers in the RADIUS server cluster according to preset strategies and algorithms.

[0055] Step S205: Output the result (e.g., error / authentication failure, authentication success).

[0056] The process is further divided into steps S2051, where if any selected RADIUS server is operating normally, it processes the user authentication request and returns the authentication result; or, in step S2052, if any selected RADIUS server is not operating normally, the request is automatically redirected to any load balancer, and the load balancer resends the user authentication request to another RADIUS server for processing. This process is repeated, and the result is output.

[0057] Furthermore, the authentication process is optimized within the RADIUS server to improve the efficiency and performance of request processing, including optimizing authentication, authorization, and accounting processes.

[0058] Furthermore, data is synchronized and backed up across multiple RADIUS servers. This data includes the load and status information of each RADIUS server. The data synchronization mechanism among the multiple RADIUS servers ensures data consistency and backup, improving system reliability and disaster recovery capabilities.

[0059] This application is applied to user authentication scenarios using RADIUS servers. By introducing technologies such as load balancers, multi-server clusters, and health check mechanisms, it achieves advantages such as high availability, fault tolerance, load balancing, performance optimization, and scalability. This further improves the processing power and fault tolerance of the RADIUS server, realizing high availability and load balancing.

[0060] Example 3

[0061] This application provides a user authentication method based on load balancer and RADIUS server by introducing a load balancer and further optimizing the RADIUS server request processing. Figure 3 This is a system architecture diagram of this application, and Figure 4This is a schematic diagram of the system business process of this application, which provides a user authentication system based on a load balancer and a RADIUS server. The system includes: multiple RADIUS servers for processing user authentication requests; and multiple load balancers connected to the multiple RADIUS servers for receiving the user authentication requests and distributing the requests to the multiple RADIUS servers according to their load conditions. The method includes at least the following processing steps: Since the content of steps S201 to S205 in Embodiment 3 is the same as that in Embodiment 2 above, the steps will not be described in detail.

[0062] However, Example 3 deploys a hybrid cloud scenario. Combined with... Figure 3 This is a system architecture diagram for this application. For example, the architecture design can be adjusted: the central node adopts the scheme of this application, and the edge sites send back authentication requests. Alternatively, since multiple RADIUS servers are deployed in the system, these servers can be distributed in different geographical locations or on different nodes in the same location, allowing for special optimization based on geographical location. Or, to mitigate disaster recovery risks: simulating a data center outage, the edge sites complete autonomous switching within milliseconds. Edge nodes receive requests from the nearest node, and the central node performs unified authentication, reducing network transmission overhead.

[0063] This application is applied to user authentication scenarios using RADIUS servers. Besides introducing technologies such as load balancers, multi-server clusters, and health check mechanisms, it achieves advantages such as high availability, fault tolerance, load balancing, performance optimization, and scalability. This further improves the processing power and fault tolerance of the RADIUS server, achieving high availability and load balancing. It also fully utilizes the load balancing, automatic scaling, and monitoring functions of the cloud platform.

[0064] Example 4

[0065] like Figure 4 As shown, this application proposes a user authentication system based on a load balancer and a RADIUS server. The system includes: multiple RADIUS servers for processing user authentication requests; and multiple load balancers connected to the multiple RADIUS servers for receiving the user authentication requests and distributing the requests to the multiple RADIUS servers according to the load of the RADIUS servers.

[0066] Specifically, first, multiple RADIUS servers are deployed in the system. These servers can be distributed across different geographical locations or different nodes in the same location. Second, a load balancer is introduced in front of the RADIUS servers. The load balancer receives all user authentication requests and distributes them appropriately based on the load of the RADIUS servers. Third, optimizations are performed within the RADIUS servers to improve the efficiency and performance of request processing, including optimizing authentication, authorization, and accounting processes. Fourth, a health check mechanism is established on the load balancer to regularly monitor the health status of each RADIUS server, promptly identifying and removing abnormal servers to ensure system stability. Fifth, the load balancer intelligently distributes requests to idle or lightly loaded servers according to pre-defined load balancing strategies, such as round-robin, weighted round-robin, and response time, achieving load balancing. Simultaneously, the load balancer can dynamically adjust the load balancing strategy based on real-time monitoring data to adapt to different request loads and traffic patterns.

[0067] This system enables load balancing and failover across multiple RADIUS servers, improving system reliability and availability. The overall architecture is more stable, resolving the performance bottlenecks and single points of failure inherent in traditional RADIUS servers, thereby enhancing user experience and network service quality.

[0068] in, Figure 5 This is a schematic diagram of a subsystem load balancer in this application. Each load balancer further includes: a traffic analysis module, used to analyze network traffic and dynamically adjust the load balancing strategy of any load balancer; a strategy allocation module, used to perform preliminary evaluation and classification of the user authentication requests according to the load balancing strategy; a health monitoring module, used to periodically monitor the health status of the multiple RADIUS servers and remove them from the request allocation list when abnormality is detected; and an abnormal recovery module, used to automatically add abnormal RADIUS servers back to the request allocation list after recovery.

[0069] Furthermore, the policy allocation module of any load balancer supports round-robin, weighted least connections, and geolocation-based routing policies.

[0070] in, Figure 6 This is a schematic diagram of the RADIUS server subsystem of this application. Each RADIUS server further includes: a monitoring module for monitoring the overall performance of the system and the status of each component; an alarm module for issuing alarms when the system performance deteriorates or a component malfunctions; and a data storage module for synchronizing and backing up data among multiple RADIUS servers.

[0071] Furthermore, any RADIUS server is deployed at both the central node and the edge node, and authentication requests received by the edge node are sent back to the central node for processing.

[0072] The purpose of this application is to propose a user authentication system based on a load balancer and a RADIUS server to address the performance bottlenecks and single points of failure issues of traditional RADIUS servers. The specific implementation includes: First, by introducing a load balancer, the processing capacity of the RADIUS server is improved, while simultaneously enhancing its fault tolerance, thus achieving high availability. Second, by optimizing the request processing process, request processing latency is reduced, improving the stability of the RADIUS server. This overcomes the limitations of existing technologies in handling real-time requests. Third, by rationally distributing requests through load balancing, load balancing is achieved across multiple servers, reducing the load on individual servers, improving overall performance and stability, thereby enhancing user experience and network service quality. This also overcomes the limitations of existing technologies in handling dynamic load adjustments.

[0073] Example 5

[0074] Based on the same inventive concept, this application also provides an electronic device. The method corresponding to this electronic device can be the user authentication method based on a load balancer and a RADIUS server as described in the foregoing embodiments, and its problem-solving principle is similar to that method. The electronic device provided in this application includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the methods and / or technical solutions of the various embodiments of this application described above.

[0075] The electronic device can be a user device, or a device formed by integrating user devices and network devices through a network, or it can be an application running on the aforementioned devices. The user device includes, but is not limited to, various terminal devices such as computers, mobile phones, tablets, smartwatches, and smart bands. The network device includes, but is not limited to, network hosts, single network servers, multiple network server clusters, or cloud-based computer clusters, and can be used to implement some processing functions when setting an alarm. Here, the cloud consists of a large number of hosts or network servers based on cloud computing.

[0076] Figure 7The diagram illustrates the structure of an electronic device suitable for implementing the methods and / or technical solutions in the embodiments of this application. The device 700 includes a central processing unit 701, which can perform various appropriate actions and processes based on a program stored in a read-only memory 702 or a program loaded from a storage section 708 into a random access memory 703. The random access memory 703 also stores various programs and data required for system operation. The central processing unit 701, the read-only memory 702, and the random access memory 703 are interconnected via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0077] The following components are connected to I / O interface 705: an input section 706 including a keyboard, mouse, touchscreen, microphone, infrared sensor, etc.; an output section 707 including a cathode ray tube, liquid crystal display, LED display, OLED display, etc., and a speaker, etc.; a storage section 708 including one or more computer-readable media such as hard disk, optical disk, magnetic disk, semiconductor memory, etc.; and a communication section 709 including a network interface card such as a local area network card, modem, etc. The communication section 709 performs communication processing via a network such as the Internet.

[0078] Specifically, the methods and / or embodiments in this application can be implemented as computer software programs. For example, the embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowchart. When the computer program is executed by the central processing unit 701, it performs the functions defined in the methods of this application.

[0079] Example 6

[0080] Another embodiment of this application provides a computer-readable storage medium having computer program instructions stored thereon, which can be executed by a processor to implement the methods and / or technical solutions of any one or more embodiments of this application described above.

[0081] Specifically, this embodiment may employ any combination of one or more computer-readable media. A computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. A computer-readable storage medium may be, for example—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access memory, a read-only memory, an erasable programmable read-only memory, an optical fiber, a portable compact disk read-only memory, an optical storage device, a magnetic storage device, or any suitable combination thereof. In this document, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in connection with an instruction execution system, apparatus, or device.

[0082] The program code contained on a computer-readable medium may be transmitted using any suitable medium, including—but not limited to—wireless, wire, optical fiber, radio frequency, etc., or any suitable combination thereof.

[0083] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including local area networks (LANs) or wide area networks (WANs), or it can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0084] The flowcharts or block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of devices, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-specific system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0085] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0086] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or page components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection between devices or units through some interfaces, and may be electrical, mechanical, or other forms.

[0087] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0088] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or in a combination of hardware and software functional units.

[0089] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

[0090] Furthermore, it is clear that the word "comprising" does not exclude other units or steps, and the singular does not exclude the plural. Multiple units or devices recited in a device claim may also be implemented by a single unit or device through software or hardware. The terms "first," "second," etc., are used to indicate names and do not indicate any specific order.

Claims

1. A user authentication method based on a load balancer and a RADIUS server, the method comprising: Any load balancer first receives the user authentication request, performs a preliminary evaluation and classification of the user authentication request according to the preset load balancing strategy, dynamically adjusts the request allocation strategy according to the real-time collected RADIUS server performance indicators, and then sends the user authentication request to any RADIUS server for processing. If any of the selected RADIUS servers is functioning normally, it will process the user authentication request and return the authentication result; If any of the selected RADIUS servers is not operating normally, the request will automatically be redirected to any of the load balancers, and the load balancers will resend the user authentication request to other RADIUS servers for processing.

2. The method according to claim 1, wherein the preliminary evaluation and classification of the user authentication request includes: The load balancer classifies the user authentication requests by traffic type and matches differentiated load strategies based on the classification results.

3. The method according to claim 2, wherein the traffic type includes user identity priority, requested service type, and source geographical location.

4. The method according to claim 1, wherein the real-time collected RADIUS server performance indicators include CPU utilization, memory utilization, and current load.

5. The method according to claim 1, further comprising: A health check mechanism for the RADIUS server is configured on any of the load balancers, wherein any load balancer periodically sends a health check request to any of the RADIUS servers, any of the RADIUS servers responds to the health check request and returns its own health information, and any load balancer determines whether any of the RADIUS servers are operating normally based on the returned health information.

6. The method according to claim 5, wherein the health information includes response latency, error rate, and service availability indicators.

7. The method according to claim 5, further comprising: If any of the RADIUS servers is determined to be malfunctioning, any load balancer removes it from the request allocation list and sends the updated request allocation list information to all load balancers.

8. The method according to claim 1, further comprising: Data is synchronized and backed up among the multiple RADIUS servers, wherein the data includes: the load status and health information of the multiple RADIUS servers.

9. A user authentication system based on a load balancer and a RADIUS server, the system comprising: Multiple RADIUS servers are used to handle user authentication requests; Multiple load balancers are connected to the multiple RADIUS servers to receive the user authentication request and distribute the user request to the multiple RADIUS servers according to the load status of the RADIUS servers.

10. The system according to claim 9, wherein any load balancer further comprises: The traffic analysis module is used to analyze network traffic and dynamically adjust the load balancing strategy of any of the load balancers. The strategy allocation module is used to perform preliminary evaluation and classification of the user authentication requests according to the load balancing strategy; The health monitoring module is used to periodically monitor the health status of the multiple RADIUS servers and remove them from the request allocation list when abnormalities are detected. The automatic recovery module is used to automatically re-add RADIUS servers that were not operating normally to the request allocation list after they have recovered from a normal operation.

11. The system according to claim 10, wherein the policy allocation module of any load balancer supports round-robin, weighted least connections and location-based routing policies.

12. The system according to claim 9, wherein any RADIUS server further comprises: The monitoring module is used to monitor the overall performance of the system and the status of its various components. An alarm module is used to issue alarms when system performance degrades or components malfunction. The data storage module is used to synchronize and back up data among the multiple RADIUS servers.

13. The system according to claim 12, wherein any RADIUS server is deployed at a central node and an edge node, and the authentication request received by the edge node is sent back to the central node for processing.

14. An electronic device, the electronic device comprising: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1 to 8.

15. A computer-readable medium having stored thereon computer program instructions that can be executed by a processor to implement the method as claimed in any one of claims 1 to 8.

16. A computer program product comprising a computer program that, when executed by a processor, implements the method as described in any one of claims 1 to 8.

Images