KR20050084711A - Method for management of aaa server and system using heartbeat message - Google Patents

Abstract

The present invention relates to a method and management system for managing AAA servers in a PDSN, and more particularly, to a method and management system for managing AAA servers in a PDSN using heartbeat messages. A method for managing an AAA server according to the present invention may include generating a heartbeat request message from a PDSN and transmitting it to an AAA server; Generating and sending a heartbeat response message to the PDSN at the AAA server in response to the heartbeat request message; And determining whether the AAA server has failed according to the transmitted heartbeat response message, wherein the heartbeat request message and the heartbeat response message use an unused code among the code fields of the data format of the Radius protocol. The heartbeat request message is periodically transmitted to the AAA server. The method for managing the AAA server in the PDSN according to the present invention comprising the above steps reduces the load on the IP network by checking the state of the AAA server using a heartbeat message to efficiently manage the traffic of the AAA server. It is possible to improve the quality of service by reducing the service request delay time by using the AAA secondary server by checking the failure state due to congestion.

Description

Method for Management of AAA Server and System Using Heartbeat Message}

The present invention relates to a method and management system for managing an AAA server in a CDMA 2000 1x system or a CDMA 2000 1x EV-DO system. More specifically, the present invention relates to a method and management system for managing an AAA server by generating a heartbeat message.

CDMA 2000 1x (MC1X) is a 2.5th generation mobile communication method that supports up to 144 kbps transmission speed. CDMA 2000 1x EV-DO (Evolution Data Only) is a third generation mobile communication technology that provides data such as text, video or music. Can transmit at speeds up to 2.54Mbps. In case of communication technology based on CDMA 2000 1x EV-DO, various terminals can be used for high-speed internet access and data communication, and will be used for services for reliable email transmission, web search, and e-commerce in mobile environments. It is a prospect. Both communication standards use a packet data service method as a data processing method.

FIG. 1 schematically illustrates a process of processing packet data requested by a user in a mobile IP environment.

In general, a user connects to a PPP or PPP session via a Packet Data Service Node (PDSN) connected to an Authentication Authorization Accounting (AAA) server through a mobile station, such as a PCS phone with Internet access. To establish. Using the PPP connection thus established, the user transmits and receives a data packet through an IP network. The PDSN is a system that processes a Point to Point Protocol (PPP) protocol and becomes an access point for accessing the Internet by a mobile user. In general, the PDSN queries the AAA server for user authentication, generates user accounting information, and delivers it to the AAA server. In addition, the PDSN functions as a foreign agent (FA) of mobile IP. The AAA server is a server that handles authentication, authorization, and accounting, and is generally implemented as a Radius server. PDSN transmits Authentication and Accounting Request Message using AAA server and Radius protocol to provide data service to user terminal. AAA server is client / server type that responds appropriately. It works. This process will be described in detail with reference to FIG. 1.

A user who wants to connect to the IP network 104 connects to the IP network via a RN (Radio Network) using a mobile station (MS) having a function of transmitting and receiving packet data. The mobile station (MS) 101 may be a cellophone, a PCS phone or any known wireless terminal. The connection request of the MS 101 is communicated to the packet data service node (PDSN) 103 via the RN 102. The PDSN 103 generally includes a control process, a network packet switch, an RN interface, and an IP network interface (not shown), so that a connection request from the RN 102, transmission and reception of packet data, and the IP network 103 are performed. Connection to a network, etc. In order for the PDSN 103 to send and receive data packets to and from the IP network 104, a PPP (Point to Point Protocol) interrupt must first be established. The establishment of such a PPP instance includes authentication, authorization, and accounting for user messages. Authentication refers to a security procedure in which the system verifies log-on information in a multi-user system or network operation system. This authentication verifies whether the user who accesses the system via the network is a registered user. And to check whether the transmitted message has been tampered with. Authorization means being given access to specific data or system services. In addition, the account means a kind of identification / billing account used by the service provider as a means for recording / managing usage for the purpose of identifying and charging each subscriber in communication. This authentication, authorization, and accounting process is performed by sending and receiving the necessary message from the PDSN 103 to the AAA server 106, which mainly uses the Remote Authentication Dial-In User Services (RADIUS) protocol. The AAA server 106 is a server for authentication, authentication, and accounting, and the Radius protocol enables communication with a central server to authenticate remote access users and to grant access rights. Client / server protocol. This Radius protocol maintains a user's profile in a central database that can be shared by all remote servers, providing better security and, in fact, the Internet Engineering Task Force (IETF) as an industry standard. It is proposed as a standard. Message transmission and reception between the PSDN 103 and the AAA server 106 using the Radius protocol is performed in a packet data method. First, the PSDN 103 sends an Access-Request message made of packet data to the AAA server 106 based on the Radius protocol by using an arbitrarily generated Authenticator as a foreign agent (FA). send. Typically, the PDSN 103 sets up several AAA servers with different priorities. This is to prepare for unexpected failures in interworking between the PDSN 103 and the AAA server 106 so that the PDSN 103 needs to manage the state of the AAA server 106. In this specification, FA is used as a concept including both the MS 101 and the PDSN 103. The access request message is encrypted with the user secret key made of the authentication value, AAA server 106 serves to decrypt the encrypted user secret key using the authentication value. The AAA server 106 determines whether to authenticate the access request message using a mobile IP authentication scheme such as Challenge Handshake Authentication Protocol (CHAP), and transmits an Access Accept message to the FA, thereby transmitting packet data. A PPP protocol for transmitting and receiving is established. During the establishment of the above PPP protocol, according to the Radius protocol, if a response message from the AAA server 106 for the access request message is not received at the FA, the access request message continues to the AAA server 106 a predetermined number of times. Is to be sent. This access request message is first sent to the AAA primary server 116, and if a response message for the access request message cannot be obtained by the allowed number of times, the AAA secondary server 126 (AAA secondary server). Will send an access request message. Similarly, if a response to an access request according to a predetermined number from the AAA secondary server 126 cannot be obtained, the access request message is transmitted to the AAA provisional server 136 (AAA provisional sever) again. As described above, when the request for access to the AAA server 106 fails to obtain a response message after transmitting the access request message a predetermined number of times, an access attempt is made to a second server and a spare server. According to the Radius protocol, the predetermined number of access attempts are made regardless of the state of the AAA server 106. This access request message is sent to the AAA server 106 via the IP network 104 as shown in FIG. However, if the AAA main server 116 fails due to traffic congestion or the like due to the concentration of data packets for a short time, or the physical failure of the server itself occurs, the FA or PDSN 103 may determine the AAA main server ( Despite the failure of 116, the access request message is transmitted a predetermined number of times. Only when the response cannot be obtained according to the predetermined number of times, the access request message is sent back to the AAA secondary server 126. This situation is the same in the case of the AAA spare server 136. When a failure occurs in the AAA server 106, a predetermined number of access request messages further exacerbate the traffic congestion situation and increase the load on the IP network 104 itself. However, according to the Radius protocol, the FA does not have an algorithm for knowing the AAA server 106 status. As noted above, according to the current Radius protocol, the PDSN 103 must transmit the actual Radius message in order to identify the failure between the PDSN 103 and the AAA server 106, and the PDSN 103 can also use the AAA server ( In order to determine the failure of 106), it is generally necessary to retransmit the set number of times. Accordingly, when the failure is confirmed, the radio request message is transmitted to the AAA server having a different priority. However, if the above scheme is followed, if there are a large number of data sessions already connected to or attempting to connect to the PDSN 103, the radio request message re-transmitted due to the failure of the AAA server 106 is transmitted on the PDSN and the IP network. To bring a significant load. The problem with the AAA server 106 state management method in the current PDSN 103 is that the AAA server state is managed by the Radius request message corresponding to the actual data session. That is, if the PDSN 103 does not send the actual Radius message to the AAA server 106, there is no way to check the state of the AAA server. This state increases the likelihood of causing a transfer state of the bursted Radius message between the transfer of the Radius request message to the AAA server with the next priority after retransmission for AAA server 106 failure confirmation. The present invention is proposed to solve the deepening of traffic congestion due to the continuous transmission of the access request message in the FA when the AAA server 106 has a failure as described above. In addition, when a physical failure occurs in the AAA primary server 116, it is proposed to solve the service delay problem by sending an access request message directly to the AAA secondary server 126. Therefore, the present invention has the following object.

Reference numeral 105, which is not described in FIG. 1, is a home agent (HA) and is responsible for IP allocation or management function of a user in mobile IP.

It is a first object of the present invention to provide a method for knowing the status of an AAA server in a FA or PDSN. According to the AAA server management method of the present invention, in case of a failure between the PDSN and the AAA server, the occurrence of the bursted Radius request message for state management can be eliminated early and the AAA server can be managed more effectively. According to the Radius protocol, the access request message from the FA to the AAA server is transmitted a predetermined number of times regardless of the state of the AAA server. Since the FA does not have any algorithm for knowing the state of the AAA server, if the response cannot be obtained by a predetermined number of transmissions, the secondary server transfers to the spare server as a next step. This process is the same when a physical failure occurs in the AAA server. In order to solve this problem, the present invention generates a heartbeat message according to the Radius protocol in the FA or PDSN. The heartbeat message thus generated is transmitted to the AAA server via the IP network. The AAA server generates a response message for the received heartbeat message and sends it to the FA or PDSN. Using the response message, the PDSN checks the status of the AAA server and if the traffic congestion occurs in the AAA server, the PDSN no longer sends an access request message to the AAA main server. The heartbeat message is generated according to the Radius protocol and may be generated using an unused code as described in detail below.

It is a second object of the present invention to provide a method for effectively managing an AAA server in a FA or PDSN. The heartbeat message generated at the PDSN may be sent to the PDSN at or immediately before the user access request, but may be sent periodically to the AAA server without or without the user access request. The AAA server generates a response heartbeat message in response to the access request heartbeat message sent from the PDSN. The response heartbeat message generated by the AAA server may include information on the number of access requests, delay time according to the processing of the access request, in the current AAA server. The PDSN may determine the state of the AAA server using the response heartbeat message sent from the AAA server. Accordingly, if there is a user access request, the PDSN can decide whether to send the access request message to the AAA primary server or the AAA secondary server. If the access heartbeat message is periodically sent to the AAA server and accordingly the response heartbeat message is periodically sent to the PDNS, the FA can check the AAA server status by updating the information on the status of the AAA server at regular intervals. do. The update of the information on the AAA server state is made by installing a storage space for storing the AAA server state in the PDSN and updating the information stored in this storage space. In addition, the frequency of updating the information may be determined in consideration of the physical device and the expected number of users of the FA. As described above, the AAA server management method in the PDSN according to the present invention periodically transmits a Radius heartbeat request message using a kind of heartbeat message using an unused code in a code field in the Radius protocol. And by receiving a Radius heartbeat response message. The PDSN is a Radius Access Request message for the actual data session. It does not need to check the AAA server status and also does not generate burst Radius messages due to retransmission in case of AAA server failure, thereby effectively managing the AAA server.

It is a third object of the present invention to provide an AAA server management system in a PDSN that can provide higher quality of service (QoS) for a user. If there is a failure in the AAA server, if there is a user's access request. According to the conventional system, the FA continuously transmits an access request message to the AAA server a predetermined number of times despite the failure. The transmission of this continuous access request message not only causes a serious failure but also increases the load of the entire IP network. And this means a delay for the user access request, and acts as a major factor that brings about a deterioration in the quality of packet data service provision. In the system according to the present invention, it is possible to always detect the failure of the AAA server, thereby minimizing such service delays, thereby improving the overall quality of service.

Hereinafter, a method for managing an AAA server in a PDSN according to the present invention and a system capable of executing the method will be described.

In the following the invention is disclosed in detail according to the accompanying drawings. However, the embodiments presented in the accompanying drawings are given as an example and the scope of the present invention is not limited thereto. In addition, known techniques in the drawings are omitted or briefly described as necessary, but this does not mean that these are excluded from the present invention.

FIG. 2A illustrates a delay state from when a failure occurs in an AAA server having a first priority to a transition to an AAA server having a second priority. In FIG. 2A, T represents the time axis (Time). When there is an Internet connection request from the mobile user, the PDSN (not shown) generates an access request message according to the Radius protocol as a FA and transmits it to an AAA server (not shown). If you fail in the AAA server has the first priority at T _s PDSN will not Despite the transmission of the access request message and receive a response message from the AAA server. However, since the PDSN has no way of checking the status of the AAA server, regardless of whether there is a failure, the PDSN will continuously re-send the Radius request message to the first AAA server a fixed number of times and if the PDSN cannot continue to respond. Will check for failure of the AAA server. At time T _t , the PDSN transmits a Radius access request message to the AAA server having the second priority. As a result, a time delay corresponding to P occurs until authentication is obtained from the AAA server. However, this interval P may cause a delay in traffic congestion due to a number of ongoing data session establishment requests and new data session establishment requests due to retransmission of the access request message in the PDSN. It can be longer. Accordingly, a new AAA server management method is requested.

2b illustrates a message format according to a conventional Radius protocol. As shown in FIG. 2B, the Radius protocol message format 20 has a Code 201, an Identifier 202, a Length 203, an Authentication 204 and an Attribute, respectively. (Attribute) 205 field. The code 201 and the identifier 201 have a size of 1 byte (1 byte or 1 octet) and are used to distinguish the type (type) of the message and the various messages, respectively. The length 203 is used to indicate the length of a field having a size of 2 bytes and including a code 201, an identifier 202, and the like of a protocol message. In addition, the authentication value 204 has a size of 16 bytes and is used for authentication, and the remaining attributes 205 indicate attributes of the main data. Since the present invention relates to generating a heartbeat message using code 201, code 201 will be described in more detail.

Since the code 201 has a length of one byte or one octet, theoretically 256 code values may be used. Currently, the Radius packet data format uses nine of them, and these code values are as follows.

Current usage value of code 201 of the Radius packet data format

1 Access Request;

2 Access Accept;

3 Access Reject;

4 Accounting Request;

5 Accounting Response;

11 Access Challenge;

12 Status Server (experimental);

13 Status Client (experimental);

255 reserved.

As described above, the code 201 having a field size of 1 byte in the packet data format according to the Radius protocol for determining a message type uses only 9 values and 247 values are not used. The management method of the AAA server according to the present invention is made using this unused code. First, a heartbeat message is a message generally used in the following cases.

Commercial services provided on the Internet must be maintained without interruption. This feature is called high-availability, and this high-availability is made possible by deploying redundant physical devices or software. For example, if you use a primary serve and a standby server as your web server, the primary server will usually perform the functions of the web server. And, if the main server fails, the spare server acts as a web server instead of the main server. However, if the main server fails, the spare server must be able to know the facts on the main server so that if the user connects to the web server, the spare server can function as a web server and immediately connect to the spare server. To make this possible, the main and spare servers periodically exchange messages. The messages sent and received are called heartbeats. If no message arrives from the main server for more than a certain period of time, the spare server assumes that the main server has failed. When used in practice, the spare server not only exchanges messages with the main server, but also includes a function for providing a service provided by the main server when the main server is considered to have failed.

As a method of generating the above heartbeat message according to the Radius protocol, it is most convenient to use the code 201 having a size of 1 byte. A heartbeat message is generated with an unused code in the Radius packet data and transmitted to the AAA server as a Radius heartbeat request message. The sent message is used for generation of a heartbeat response message at the AAA server and this heartbeat response message is sent back to the PDSN or FA. The PDSN can check the status of the AAA server by using the received heartbeat response message, and thus can appropriately handle the user access request. A heartbeat message exchange process between the PDSN and the AAA server made in this manner will be described in detail with reference to FIG. 3.

3 illustrates a process of exchanging heartbeat messages between a PDSN and an AAA server and managing the AAA server accordingly.

As shown in FIG. 3, first, a heartbeat request message is generated in the PDSN (S301). As described with reference to FIG. 2, the heartbeat request message is generated according to the Radius protocol and is generated using an unused code among codes having a size of 1 byte. That is, it is generated by selecting any one value except 1, 2, 3, 4, 5, 11, 12, and 13 among the values of 0 to 255 that the code may have. The generated heartbeat message is transmitted to the AAA server (S302). Transmission to the AAA server (S302) may be made when there is a connection request from the user, but may always be done at regular intervals. If the heartbeat request message is generated by the access request from the user, the heartbeat request message may be transmitted to the AAA server in two ways. First, the heartbeat message may be included in the access request message and transmitted to the AAA server. In other words, the code of the packet data format includes a value representing a heartbeat message. In this case, the AAA server should check the heartbeat message and send a response to the PDSN. However, in this case, since the size of the data packet to be transmitted itself is increased and the connection itself to the AAA server will be difficult in a traffic congestion state, there is no particular advantage. Another method is to send a heartbeat request message to the AAA server immediately before sending an access request message. In this case, the AAA server may be useful when the heartbeat request message is processed in preference to the processing of other data packets, or when a separate physical device for processing the heartbeat request message is provided. However, given that bursts or traffic congestion or physical failures of AAA primary servers generally do not last for only a short time, this approach also has no particular advantage. The most suitable embodiment is to send a heartbeat request message to the AAA server at regular intervals, for example at intervals of 1 minute, 5 minutes or 10 minutes. Even in this case, it is advantageous for the AAA server to preferentially process such heartbeat request messages or to process received heartbeat request messages using other physical devices or software. When the heartbeat request message generated by the PDSN or FA is received by the AAA server by any method described above, the AAA server generates a Radius Heartbeat Response Message (S303). Heartbeat response messages are also generated using unused codes according to the Radius protocol. In other words, it is generated using an unused code like a heartbeat request message. However, unlike the heartbeat request message, the heartbeat response message may include other information related to the AAA server. Such information may include information about the current state of the AAA server, that is, the amount of processing requests, the current delay estimated time, and whether the processing requests are decreasing or increasing. There are two ways to generate and process heartbeat response messages in the AAA server: using a separate physical device or processing only in software without adding these physical devices. If a separate physical device is added, the AAA server may include information about a failure. This additional information is also generated using code not described above. The heartbeat response message generated in this manner is sent back to the PDSN (304). However, transmission of such heartbeat response messages is not necessarily guaranteed. That is, when the AAA server fails, such a heartbeat response message may not be transmitted. If a heartbeat response message is not sent from the AAA server, the PDSN can immediately assume that the AAA primary server is in a failed state. Alternatively, a failure of the AAA primary server may be assured by re-transmission of a certain number of heartbeat request messages or by re-transmission after a certain time. Once a heartbeat response message containing certain information transmitted from the AAA server is received at the PDSN, the information on the AAA server status is updated accordingly (S305). While it would be advantageous for an AAA server to have a separate physical device associated with the heartbeat message, such a heartbeat message would be sufficient for the PDSN to be processed in software. When the information on the AAA server is updated in the PDSN, the Radius heartbeat request message is transmitted to the AAA server again (S306). In this manner, the Radius heartbeat request message is transmitted from the PDSN to the AAA server at regular intervals, and the AAA server is managed by using information included in the heartbeat response message or not. The PDSN responds to the user's IP access request according to the stored AAA server information. In implementing the method according to the present invention as described above, regardless of whether a new physical device is installed or software-processed in the AAA server or the PDSN, the AAA server and the PDSN must include the rules for the heartbeat message in advance. That is, according to the conventional Radius protocol, if a code field has a value different from a predetermined code, the data packet is specified to be discarded. Therefore, for the implementation of the method according to the invention, a processing rule for the heartbeat message must be included between the AAA server and the FA.

4A illustrates a process of transmitting and receiving a heartbeat message between a PDSN and an AAA server.

As shown in FIG. 4A, the PDSN 401 generates a heartbeat request message and periodically sends it to the AAA server 402. The transmission of the heartbeat request message is generated and transmitted separately from the actual data session. When the AAA server 402 receives the Radius heartbeat request message from the PDSN 401, the AAA server 402 transmits the Radius heartbeat response message to the PDSN 401 in response. At this time, the AAA server 401 does not need to process any data with respect to the Radius heartbeat request message, and only checks for an abnormality of an authentication value (authenticator). The PDSN 401 may check the state of the AAA server 402 using the received heartbeat response message, thereby effectively managing the AAA server 402. Figure 4b shows one such embodiment.

FIG. 4B shows the transition process to the AAA secondary server (second priority AAA server) due to a failure in the AAA primary server (first priority AAA server).

As shown in FIG. 4B, when the Radius Heartbeat Request Message P11 generated by the PDSN 401 is transmitted to the AAA main server 412, and thus, the AAA main server has not failed. A Radius Heartbeat Request Message R11 is transmitted. Since the PDSN 401 has confirmed that the AAA main server 412 is intact, a data packet for establishing a PPP instance is transmitted, and accordingly, transmission and reception of a Radius request / response message PR11 for a burst data session is performed. Is done. When the Radius heartbeat request message P12 is sent from the PDSN 401 to the AAA main server 412 again and the status of the AAA main server 412 is confirmed upon receipt of the heartbeat response message R12, the burst radius The request / response message PR12 is transmitted and received. However, if no response can be obtained from the AAA primary server 412 for the Radius heartbeat request message R13 sent from the PDSN 401, then the PDSN 401 confirms that the AAA primary server has failed. Accordingly, the PDSN transmits the heartbeat request message P21 to the AAA secondary server 422 without transmitting the Radius message for the bursted data session to the IP network. When the PDSN 401 transmits a Radius heartbeat response message R21 from the AAA secondary server 422, the bursted data session over the IP network between the PDSN 401 and the AAA secondary server 422 is thus performed. Send / receive a Radius request / response message to PR21. Radius heartbeat request message P22 is sent from PDSN 401 back to AAA secondary server 422 and the Radius request / response message for the bursted data session in accordance with the transmission of heartbeat response message R22. The transmission and reception of the PR22 are made between the PDSN 401 and the AAA secondary server 422 via the IP network. In this process, the transmission of the Radius heartbeat request message to the AAA main server 411 is performed at regular intervals. If the Radius heartbeat response message is sent from the AAA primary server 401 again, the PDSN 401 transmits and receives a Radius request / response message for the burst session to the AAA primary server 401. In this way, the PDSN 401 can effectively manage the AAA server 402.

5 shows in a flow chart the method according to the invention presented in FIG. 4B.

As shown in FIG. 5, first, a heartbeat request message generated in the PDSN is transmitted to the AAA main server (S501). If a heartbeat response message is sent to the PDSN (S503), a request / response session burst according to the Radius protocol is established between the PDSN and the AAA server (S504). However, if no response is received from the AAA primary server, the PDSN transmits the heartbeat request message to the AAA secondary server again while still buffering the bursted message (S512). If a heartbeat response message is received from the AAA secondary server (S513), a bursted request / response message session is established (S514). However, if the heartbeat response message is not received (S513), the PDSN sends a heartbeat request message to the AAA spare server if the AAA spare server exists, but if the AAA spare server does not exist, the heartbeat request is sent back to the AAA primary server. The message is transmitted (S502). As described above, the PDSN manages the AAA server efficiently using the heartbeat message while only buffering the burst message.

The invention above has been described in detail by the embodiments in accordance with the accompanying drawings. However, it will be apparent to those skilled in the art that modifications and variations can be made to the disclosed embodiments without departing from the spirit of the invention. Therefore, the technical scope of the present invention is not limited by these embodiments but only by the claims appended below.

The AAA server management method in the PDSN according to the present invention and the AAA server management system in the PDSN in which such a management method is made are described in detail. Such AAA server management method and system according to the present invention to enable AAA server management according to the Radius protocol. That is, according to the conventional Radius protocol, there was no method for checking the state of the AAA server in the PDSN, but it is possible to check the state of the AAA server in the PDSN using a heartbeat message by the method and system according to the present invention. It became. In addition, by checking the AAA server status in the PDSN, the bursting message is not transmitted when a failure occurs, thereby reducing the load on the IP network and maintaining the service to the user. In addition, by effectively using the AAA primary server and the secondary server, it is possible to improve the quality of service (QoS) by minimizing the delay for user access requests.

FIG. 1 schematically illustrates the process of establishing a PPP session by connecting from a mobile station (MS) to an IP network in a CDMA 2001 1x or CDMA 2000 1x EV-DO system.

2A illustrates a delay state that may occur from transmission and reception of an access request message according to a conventional Radius protocol.

FIG. 2B shows the data format of a packet according to the conventional Radius protocol.

3 illustrates a process of processing data according to a process of generating a heartbeat message according to the present invention.

4A illustrates a message processing procedure between a PDSN and an AAA server according to the present invention.

Figure 4b illustrates an embodiment of a server management method according to the present invention when a failure occurs in the AAA server.

5 is a flowchart illustrating an embodiment of a method for managing an AAA server in a PDSN according to the present invention.

※ Explanation of Main References

101: mobile station 102: RN 103: PDSN

104: IP network 105: HA 106: AAA server

116: primary server 126: secondary server 136: spare server

20: packet data format 201: code

202: identifier 223: length 204: authentication value

205: Property 401: PDSN 402: AAA Server

412: AAA primary server 422: AAA secondary server

Claims (12)

In the method of managing an AAA server consisting of a primary server and a secondary server in the PDSN according to the Radius protocol, Generating a heartbeat request message from the PDSN to the AAA server; Generating and sending a heartbeat response message to the PDSN at the AAA server in response to the heartbeat request message; Determining whether an AAA server has failed according to the transmitted heartbeat response message; The heartbeat request message and the heartbeat response message are generated using an unused code in the code field of the Radius protocol, and the heartbeat request message is periodically transmitted. How to manage. The method of claim 1, The heartbeat response message is a management method of the AAA server, characterized in that it contains information about the status of the AAA server. The method of claim 2, The AAA server state information may be a number of request sessions, a scheduled delay time or whether the request is increased or decreased. The method of claim 1, The generation and transmission of the heartbeat response message is managed using a separate physical device. The method of claim 1, The generation and transmission of the heartbeat response message is performed in software only by using a separate processing algorithm. The method of claim 1, A storage space for storing information about the state of the AAA server is installed, and the PDSN, by receiving the heartbeat response message, the information on the state of the AAA server further comprises the step of updating the information at regular intervals. . The method of claim 1, Determination of failure of the AAA server management method of the AAA server, characterized in that the PDSN does not transmit a heartbeat response message. The method of claim 1, If it is determined that the AAA server has failed, further comprising the step of sending a heartbeat request message to the AAA secondary server or a spare server. The method of claim 6, And determining whether to transmit a heartbeat request message to the AAA primary server and the AAA secondary server based on the updated information. The method of claim 1, The AAA server management method, characterized in that the processing of the Radius heartbeat request message in the AAA server only confirms whether there is an abnormality of the authentication (authenticator). The method of claim 1, And continuously sending a heartbeat request message to the AAA primary server at regular intervals after the failure of the AAA primary server has been confirmed. The method of claim 11, AAA including transmitting a heartbeat request message to the AAA primary server, transmitting a heartbeat response message accordingly, and processing the response message in the PDSN when failure removal is confirmed by transmission to the AAA primary server. How to manage your server.