WO2010139220A1

WO2010139220A1 - Method and system for realizing cross-protocol failover

Info

Publication number: WO2010139220A1
Application number: PCT/CN2010/072375
Authority: WO
Inventors: 宋大猛; 甘斌; 陈刚; 徐键
Original assignee: 中兴通讯股份有限公司
Priority date: 2009-06-01
Filing date: 2010-04-30
Publication date: 2010-12-09
Also published as: CN101594602A; CN101594602B

Abstract

A method for realizing cross-protocol failover comprises the following steps that: a work state of a diameter server (22) is detected; and when the diameter server (22) is in normal work state, an authentication, authorization and accounting (AAA) system (21) executes accounting operation between itself and the diameter server (22); when the diameter server (22) fails to work, the AAA system (21) executes accounting operation between itself and a radius server (23). A system for realizing cross-protocol failover is provided. The method and the system can improve the stability of the accounting system, avoid system unavailability due to occurrence of failure in a new accounting system in the initial update stage and improve the user experience.

Description

Method and system for implementing failover across protocols

The present invention relates to the field of network communication technologies, and in particular, to a method and system for implementing failover between a Diameter protocol and a Radius protocol. Background technique

Since the birth of network communication technology, the authentication, authorization, and accounting (AAA, Authentication, Authorization, Accounting) system has become the basis of communication network operations. In the traditional communication network, the Radius protocol is used to implement the AAA technology, and the AAA system and the prepaid system (PPS, PrePaid System) use the Radius protocol to transmit the charging messages to each other.

At present, with the evolution of the third-generation mobile communication system to the all-IP-based network architecture, the Diameter protocol has become a new generation of AAA technology, and has attracted much attention due to the powerful scalability and security of the Diameter protocol. International standards organizations such as the Alliance (3C), 3rd Generation Partnership Project (3GPP) and 3rd Generation Partnership Project 2 (3GPP2) have officially adopted the Diameter protocol as Next Generation Network (NGN), Wideband Code Division Multiple Access (WCDMA). The preferred AAA protocol for future communication networks such as Code Division Multiple Access (CDMA) 2000. In the new prepaid specification, the cost calculation and quota allocation of prepaid users will be completed by the online charging system (OCS) instead of the traditional PPS. Therefore, the traditional telecommunication equipment has an upgrade requirement.

Traditional telecommunications equipment, such as packet data switching nodes (PDSNs) and PPS and AAA systems, use the Radius protocol, and the interaction between OCS and AAA systems uses the Diameter protocol. Therefore, the AAA system needs to implement the Radius protocol to the Diameter protocol. Conversion. 1 is a conventional charging system implemented by the Radius protocol, and FIG. 2 is a charging system after the introduction of the Diameter protocol. The existing charging system generally replaces the traditional charging with the charging system shown in FIG. System, ie: replace the traditional AAA system with an AAA system with protocol conversion; meanwhile, Replace the traditional PPS with OCS. However, the existing billing system has certain defects, as follows: First, replacing the traditional billing system directly into the existing billing system will result in waste of certain resources; secondly, in the initial stage of the existing billing system, due to the system If the stability is not high, the service is not available, and the user experience is not good. For example, when the OCS fails or the link between the AAA system and the OCS is abnormal, the existing billing system cannot continue to provide services for the user, and Since the Failover mechanism cannot be applied to the existing billing system, the billing operation will not be possible once the existing billing system fails until the system returns to normal. Summary of the invention

In view of this, the main object of the present invention is to provide a method and system for implementing Failover across protocols, so that the billing system can still provide services for users from the time of failure to failure recovery.

In order to achieve the above object, the technical solution of the present invention is achieved as follows:

The present invention provides a system for implementing failover across protocols, the system comprising:

AAA system, used to detect the working status of the Diameter server (Server), determine the accounting operation between the Diameter Server and the Diameter Server when determining that the Diameter Server is in normal working state; Fee operation

The Radius Server is configured to exchange charging messages with the AAA system to perform charging operations. The Diameter Server is configured to exchange charging messages with the AAA system to perform charging operations. The AAA system is further configured to perform a charging operation between the Diameter Server and the Diameter Server when the faulty Diameter Server returns to the normal working state.

The Radius Server further includes a protocol conversion module, configured to convert between a user data message of a Radius protocol update between the Diameter Server and the Radius Server and a user data message updated by the Diameter protocol;

The Radius Server, for further converted into the Diameter protocol update user data upload message sent or received the Diameter Server _¾ the Diameter Diameter Server Updated user data message for the protocol;

The Diameter Server is further configured to receive an updated user data message of a Diameter protocol uploaded by the Radius Server, or send an updated user data message of the Diameter protocol to the Radius Server.

The present invention also provides a method for implementing failover across protocols, the method comprising: detecting a working state of a Diameter Server, and when the Diameter Server is in a normal working state, the AAA system performs a charging operation between itself and the Diameter Server; When the Diameter Server fails, the AAA system performs its own accounting operation with the Radius Server.

The method further includes:

When the faulty Diameter Server returns to normal working state, the AAA system performs

Billing operations between Diameter Servers.

In the present invention, the AAA system performs a charging operation between itself and the Radius Server, which is specifically:

The AAA system sends the received Radius charging request message to the Radius Server, and the Radius Server replies to the charging response message to the AAA system; or,

After the AAA system converts the Diameter Accounting Request message that is not processed by the Diameter Server into a Radius Accounting Request message, it sends it to the Radius Server, and the Radius Server replies with the charging response message to the AAA system; after that, the AAA system will receive the Radius charging request. The message is sent to the Radius Server, and the Radius Server replies to the accounting response message to the AAA system.

In the present invention, the AAA system performs a charging operation between itself and the Diameter Server, specifically:

The AAA system converts the charging operation between itself and the Radius Server to the charging operation between itself and the Diameter Server, converts the received Radius charging request message into a Diameter charging request message, and sends it to the Diameter Server, and then sends it to the Diameter Server. The Diameter Server replies to the Diameter Accounting Response message to the AAA system. The method further includes:

When the Diameter Server fails, the Radius Server receives and processes the charging request message sent by the AAA system, and stores the updated user data message of the Radius protocol. After the Diameter Server returns to normal, the Radius Server converts the updated user data message of the Radius protocol. The updated user data message of the Diameter protocol is uploaded to the Diameter Server;

When the Diameter Server is restored, the Diameter Server sends the updated user data message of the Diameter protocol to the Radius Server. The Radius Server converts the updated user data message into the updated user data message of the Radius protocol and stores it.

In the present invention, the detecting is specifically:

The AAA system detects the working status of the Diameter Server through the link handshake message DWR/DWA of the Diameter protocol or the heartbeat detection mechanism in the flow control transmission protocol SCTP.

Further, the method further includes:

When the Diameter Server is in the normal working state, the Diameter Server sends the updated user data message of the Diameter protocol to the Radius Server, and the Radius Server converts the updated user data message into the updated user data message of the Radius protocol and stores it.

The method and system for implementing Failover across protocols are provided, and two modules of Diameter Server and Radius Server are proposed, and the translation agent function in the Diameter protocol is combined with the Failover mechanism, and the AAA system detects the working state of the Diameter Server, when Diameter When the server is in normal working state, the AAA system performs the charging operation between itself and the Diameter Server; when the Diameter Server fails, enters the Failover process, and the AAA system performs the charging operation between itself and the Radius Server; therefore, the present invention improves The stability of the billing system can avoid the problem that the system is unavailable due to the failure of the new billing system in the initial stage of the upgrade, and the user experience is improved. The invention can add only one processing node of the Diameter protocol, such as OCS, based on the Radius protocol charging system, and the Radius protocol module uses the traditional PPS, and only needs to add a protocol conversion module to the PPS, thereby saving Capital Source.

Further, the translation proxy function in the Diameter protocol is combined with the Failback mechanism. When the faulty Diameter Server returns to the normal working state, the Failback process is entered, and the AAA system performs the charging operation with the Diameter Server again, further improving. Utilization of the Diameter Server using the new Diameter protocol.

The invention also proposes a data synchronization method between the Diameter Server and the Radius Server, which ensures the consistency of the user data messages in the Diameter Server and the Radius Server before and after the Diameter Server failure recovery, and further improves the security and reliability of the charging system. DRAWINGS

Figure 1 shows a conventional billing system implemented by the Radius protocol;

Figure 2 shows the charging system after the introduction of the Diameter protocol;

3 is a schematic structural view of a system of the present invention;

FIG. 4 is a schematic diagram showing the implementation process of the Failover method of the present invention. detailed description

The basic idea of the present invention is: Two functional modules of Diameter Server and Radius Server are proposed, and the translation proxy function in the Diameter protocol is combined with the Failover mechanism; the AAA system detects the working state of the Diameter Server, and the Diameter Server is in a normal working state. The AAA system performs the charging operation between itself and the Diameter Server; when the Diameter Server fails, enters the Failover process, and the AAA system performs the charging operation between itself and the Radius Server;

Further, the translation proxy function in the Diameter protocol is combined with the Failback mechanism, and when the failed Diameter Server returns to the normal working state, the Failback processing process is entered, and the AAA system performs the charging operation with the Diameter Server again;

The invention also proposes a data synchronization method between the Diameter Server and the Radius Server. Used to ensure the consistency of user data messages in Diameter Server and Radius Server.

The present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

FIG. 3 is a schematic structural diagram of a charging system according to the present invention. As shown in FIG. 3, the system includes: a related network element 20, an AAA system 21, a Diameter Server 22, and a Radius Server 23, where the related network element 20 is used to pass The Radius protocol sends a Radius charging request message to the AAA system 21 or receives a Radius charging response message returned by the AAA system 21;

Here, the related network element 20 may be a PDSN or a Gateway GPRS Support Node (GGSN) or the like.

The AAA system 21 is configured to detect the working status of the Diameter Server 22, determine that the Diameter Server 22 is working normally, convert the Radius charging request message sent by the related network element 20 into a Diameter charging request message, and send the message to the Diameter Server 22 or The Diameter charging response message returned by the Diameter Server 22 is converted into a Radius charging response message and sent to the relevant network element 20; when the Diameter Server 22 is determined to be faulty, the Radius charging request message sent by the related network element 20 is sent to the Radius Server. 23 or send the Radius charging response message returned by the Radius Server 23 to the relevant network element 20; when it is determined that the Diameter Server 22 is restored to normal, the subsequent information is transmitted again with the Diameter Server 22;

Here, the AAA system 21 transmits the charging message to the Diameter Server 22 through the Diameter protocol, and transmits the charging message to the Radius Server 23 through the Radius protocol;

The Diameter Server 22 is configured to receive a Diameter Accounting Request message sent by the AAA system 21, and reply the Diameter Accounting Response message to the AAA system 21 according to the locally stored user quota information;

The Radius Server 23 is configured to receive a Radius charging request message sent by the AAA system 21, and reply the Radius charging response message to the AAA system 21 according to the locally stored user quota information;

In the present invention, the Radius Server 23 may be a PPS, and the Diameter Server 22 may For OCS; Diameter Server 22 and Radius Server 23 provide users with services such as authentication, authorization, and billing;

The Radius Server 23 further includes a protocol conversion module 24 for converting between an updated user data message of the Radius protocol between the Diameter Server 22 and the Radius Server 23 and an updated user data message of the Diameter protocol;

The Diameter Server 22 is further configured to receive an updated user data message of the Diameter protocol uploaded by the Radius Server 23, or send the updated user data message of the Diameter protocol to the Radius Server 23;

The Radius Server 23 is further configured to upload an updated user data message converted to the Diameter protocol to the Diameter Server 22, or receive an updated user data message of the Diameter protocol delivered by the Diameter Server 22, specifically,

When the Diameter Server 22 is working normally, receiving the updated user data message of the Diameter protocol delivered by the Diameter Server 22, the protocol conversion module 24 converts the updated user data message into an updated user data message of the Radius protocol and stores it; Diameter Server 22 When a fault occurs, the charging request message sent by the AAA system 21 is received and processed, and the updated user data message of the Radius protocol is stored. After the Diameter Server 22 returns to normal, the protocol conversion module 24 converts the updated user data message of the Radius protocol. The updated user data message of the Diameter protocol is uploaded to the Diameter Server 22;

Here, since the user data message stored locally by the Diameter Server 22 or the Radius Server 23 during the running of the system will change after each processing of the charging request message,

The Diameter Server 22 or the Radius Server 23 will replace the original user data messages stored locally with the new user data messages. The updated user data messages described here are: Diameter Server 22 fails to Diameter Server 22 to resume normal operation. A changed user data message; the updated user data message of the Radius protocol is: a user data message that is stored locally by the Radius Server 23. The implementation method of the present invention will be described in detail based on the above system.

FIG. 4 is a schematic flowchart of a method for implementing a Failover between a Diameter and a Radius protocol according to the present invention. As shown in FIG. 4, the method includes the following steps:

Step 401: The AAA system 21 is powered on and initialized, and establishes a connection with the Diameter Server 22;

Here, the establishing the connection process is specifically: the AAA system 21 first establishes a bearer link with the Diameter Server 22 through a bearer protocol, such as a flow control transport protocol (SCTP) or a transport control protocol (TCP), and then passes the capability. The exchange message (CER/CEA) establishes a Diameter connection with the Diameter Server 22.

Step 402: The related network element 20 sends a charging request message to the AAA system 21;

Specifically, the related network element 20 sends a charging request message to the AAA system 21 in the form of a Radius protocol message.

Step 403: The AAA system 21 receives the charging request message.

Specifically, the AAA system 21 receives the Radius charging request message sent by the related network element 20. Step 404: The AAA system 21 detects the working status of the Diameter Server 22, and performs a corresponding charging operation according to different detection results.

Specifically, if the Diameter Server 22 is in a normal working state, step 405a is performed; if the Diameter Server 22 is faulty, step 405b is executed to enter the Failover process; if the Diameter Server 22 is restored to the normal working state, step 405c is performed to enter Fallback process;

Here, the AAA system 21 continuously detects the Diameter Server 22 during the operation of the charging system of the present invention, that is, when the charging system is running, the detecting operation is also performed simultaneously; the detecting is specifically: the AAA system 21 passes the Diameter The link handshake message D WR/D WA of the protocol or the heartbeat detection mechanism in the SCTP detects whether the working state of the Diameter Server 22 is normal; in the present invention, the AAA system 21 ensures the user datagram with the Radius Server 23. The protocol (UDP) connection is smooth, and the purpose is: The billing system can still operate normally during the failure of Diameter Server 22.

Step 405a: The AAA system 21 sends the received charging request message to the Diameter Server 22, and the Diameter Server 22 replies to the charging response message to the AAA system 21;

Specifically, the AAA system 21 converts the received Radius charging request message into a Diameter charging request message and sends it to the Diameter Server 22, and then the Diameter Server 22 replies to the AAA system 21 according to the locally stored user quota information.

Here, the AAA system 21 caches the converted Diameter Accounting Request message before sending the Diameter Accounting Request message to the Diameter Server 22. The purpose of the AAA system 21 is to prevent the Diameter Accounting Request message from being lost if the Diameter Server 22 fails. The subsequent operations are affected by: When the Diameter Server 22 fails, the AAA system 21 first scans the cached Diameter charging request message before performing the charging operation with the Radius Server 23, if the buffered charging request message has been received. The reply of the Diameter Server 22 sends the Radius charging request message sent by the subsequent related network element 20 to the Radius Server 23 for processing; if the buffered charging request message does not receive the reply from the Diameter Server 22, that is: has not been processed yet. Then, the Diameter Accounting Request message is converted into a Radius Accounting Request message and sent to the Radius Server 23 for processing.

Step 405b: The AAA system 21 sends the charging request message sent by the related network element 20 to the Radius Server 23, and the Radius Server 23 returns the charging response message to the AAA system 21; specifically: when the AAA system 21 detects that the Diameter Server 22 is faulty. , enter

The Failover process is as follows: The AAA system 21 first scans the cached Diameter Accounting Request message. If the AAA system 21 has received a reply from the Diameter Server 22, ie, the Diameter Accounting Request message has been processed by the Diameter Server 22, The received Radius charging request message is directly sent to the Radius Server 23, and then the Radius Server 23 replies to the Radius charging response message to the AAA system 21 according to the locally stored user quota information; The system 21 has not received a reply from the Diameter Server 22, that is, the Diameter Accounting Request message has not been processed by the Diameter Server 22, and the AAA system 21 first converts the Diameter Accounting Request message into a Radius Accounting Request message and sends it to the Radius. Server 23, Radius Server 23 replies to the Radius charging response message to the AAA system 21 according to the locally stored user quota information, and then sends the received Radius charging request message to the Radius Server 23, according to the locally stored user quota. The information replies to the Radius Accounting Response message to the AAA system 21.

This step also includes the following steps:

After detecting the Diameter Server 22 failure, the AAA system 21 attempts to re-establish a connection with the Diameter Server 22 to detect whether the Diameter Server 22 is available, that is, whether the Diameter Server 22 is restored to the normal working state.

Here, the AAA system 21 in this step continuously attempts to re-establish the connection with the Diameter Server 22 through the underlying bearer according to the characteristics of the Diameter protocol. Once the link is re-established, the capability negotiation is performed to ensure that the Diameter Server 22 is available. The characteristics of the Diameter protocol are: The Dia meter protocol uses SCTP or TCP as the bearer protocol to provide secure and reliable connectivity.

Step 405c: The AAA system 21 sends the received charging request message to the Diameter Server.

22, Diameter Server 22 replies to the charging response message to the AAA system 21;

Specifically, when the AAA system 21 detects that the Diameter Server 22 returns to the normal working state, it enters the Fallback process, and the AAA system 21 converts the charging operation performed with the Radius Server to the charging operation with the Diameter Server 22 again. The received Radius charging request message is converted into a Diameter charging request message and sent to the Diameter Server 22, and then the Diameter Server 22 replies to the AAA system 21 according to the locally stored user quota information.

Step 406: The AAA system 21 returns the received charging response message to the relevant network element 20; specifically: the AAA system 21 converts the received Diameter charging response message into a Radius charging response message, and returns it to the relevant network element 20 Or return the received Radius charging response message. The relevant network element 20 is given.

Step 407: Step 402 to step 406 are repeated until the current charging operation is completed. Here, the current charging operation process is: processing only a single charging request message or processing a plurality of charging request messages.

The invention further proposes a data synchronization method between the Diameter Server and the Radius Server, and the method steps are as follows:

When the Diameter Server 22 is working normally, the Radius Server 23 receives the updated user data message delivered by the Diameter Server 22 in the form of a Diameter protocol message, and the protocol conversion module 24 converts the updated user data message into the form of a Radius protocol message and stores it. The sending process is: After the system processes one charging request message, the user data message stored locally by the Diameter Server 22 changes accordingly. At this time, the Diameter Server 22 sends an updated user data message to the Radius Server 23. That is, the Diameter Server 22 sends an updated user data message to the Radius Server 23 after the system processes one accounting request message;

When the Diameter Server 22 fails, the Radius Server 23 receives and processes the charging request message sent by the AAA system 21, and stores the updated user data message of the Radius protocol. After the Diameter Server 22 returns to normal, the protocol conversion module 24 will use the Radius protocol. The updated user data message is converted to the updated user data message of the Diameter protocol and uploaded to the Dia meter Server 22.

Here, because the user data message stored locally by the Diameter Server 22 or the Radius Server 23 will change after each processing of the charging request message, the Diameter Server 22 or the Radius Server 23 will use the new user data message. Replacing the original user data message stored in the local area, the updated user data message described herein is: the user data message that the Diameter Server 22 fails to change during the normal recovery process of the Diameter Server 22; the update of the Radius protocol User data message, for: Radius Server 23 Stored user data messages that have changed.

In the present invention, after the Diameter Server 22 or the Radius Server 23 and the AAA system 21 perform the charging operation and the information is updated, that is, after the user data message is updated, the updated user data message needs to be sent to the counterpart server, that is: If Diameter The server 22 and the AAA system 21 perform the charging operation, and the Diameter Server 22 needs to send the updated user data message stored locally by the Diameter Server 22 to the Radius Server 23; if the Radius Ser ver 23 and the AAA system 21 perform the charging operation, The Radius Server 23 then needs to send updated user data messages stored locally by the Radius Server 23 to the Diameter Server 22.

The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included. Within the scope of protection of the present invention.

Claims

Claim

A system for implementing failover across protocols, the system comprising: an authentication, authorization, and accounting AAA system, configured to detect a working state of a diameter server Diameter Server, and determine when the Diameter Server is in a normal working state, execute The charging operation between itself and the Diameter Server; when determining the failure of the Diameter Server, performing the charging operation between itself and the radius server Radius Server;

The Radius Server is configured to exchange charging messages with the AAA system to perform charging operations. The Diameter Server is configured to exchange charging messages with the AAA system to perform charging operations.

The system for implementing failover across protocols according to claim 1, wherein the AAA system is further configured to perform charging between the Diameter Server and the Diameter Server when the faulty Diameter Server is restored to the normal working state. operating.

The system for implementing failover across protocols according to claim 1 or 2, wherein the Radius Server further comprises a protocol conversion module, and a user data message for updating the Radius protocol between the Diameter Server and the Radius Server. Conversion between user data messages updated by the Diameter protocol;

Correspondingly, the Radius Server is further configured to upload the updated user data message converted to the Diameter protocol to the Diameter Server, or receive the updated user data message of the Diameter protocol delivered by the Diameter Server;

A method for implementing failover across protocols, the method comprising: detecting a working state of a Diameter Server, and when the Diameter Server is in a normal working state, the AAA system performs a charging operation between the self and the Diameter Server; When the Diameter Server fails, the AAA system performs its own accounting operation with the Radius Server.

The method for implementing a failover across a protocol according to claim 4, wherein the method further comprises:

When the failed Diameter Server returns to normal operation, the AAA system performs charging operations with the Diameter Server.

The method for implementing a failover across protocols according to claim 4 or 5, wherein the AAA system performs a charging operation between itself and the Radius Server, specifically:

The method for implementing the failover by using the cross-protocol according to claim 4 or 5, wherein the AAA system performs a charging operation between the AAA system and the Diameter Server, specifically: the AAA system performs the operation between itself and the Radius Server. Billing operation again turns itself into

The accounting operation performed between the Diameter Servers converts the received Radius Accounting Request message into a Diameter Accounting Request message and sends it to the Diameter Server. The Diameter Server then replies to the Diameter Accounting Response message to the AAA system.

The method for implementing failover across protocols according to claim 4 or 5, wherein the method further comprises:

When the Diameter Server returns to normal, the Diameter Server will update the Diameter protocol. The user data message is sent to the Radius Server, and the Radius Server converts the updated user data message into an updated user data message of the Radius protocol and stores it.

The method for implementing failover across protocols according to claim 4 or 5, wherein the detecting is specifically:

The method for implementing a failover across a protocol according to claim 8, wherein the method further comprises: