RADIUS Diameter Message Translation for Prepaid Services

Solution Overview

Problem

The existing RADIUS protocol has limitations that hinder its ability to support prepaid services for next-generation charging architectures, particularly in transitioning from RADIUS-based systems to Diameter-based systems, due to the lack of backward compatibility for prepaid service authentication and authorization.

Innovation Solution

A methodology for translating RADIUS messages into Diameter messages and vice versa, specifically tailored for the IS-835 RADIUS standard, allowing for a smooth transition from RADIUS-based CDMA prepaid packet data services to Diameter online architectures, including the translation of access request, credit control, and disconnect messages.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If mechanical translation of RADIUS messages to Diameter messages is implemented according to RFC 4006, then backward compatibility with RADIUS is improved, but prepaid service authentication and authorization functionality is lost because it falls out of scope

Engineering Contradiction:

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a translation mechanism that acts as an intermediary between RADIUS and Diameter protocols. This translator converts RADIUS messages into Diameter messages while preserving prepaid service authentication and authorization functionality, which the standard mechanical translation in RFC 4006 fails to maintain. The translator bridges the two protocols specifically for prepaid services.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent modifies the translation approach by changing parameters and attributes during message conversion. Instead of simple mechanical translation, it transforms RADIUS message parameters into appropriate Diameter AVP (Attribute Value Pair) structures, ensuring that prepaid service-specific parameters are properly mapped and preserved in the Diameter protocol format.

Inventive Principle:

Principle #35Parameter changes

2Adaptability or versatility

If vendors support both RADIUS and Diameter based online/prepaid charging, then functionality coverage is improved, but device complexity increases

Engineering Contradiction:

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The translation mechanism serves as an intermediary layer that allows vendors to support RADIUS-based prepaid services while transitioning to Diameter architecture. Instead of maintaining full dual-protocol support, the translator enables RADIUS messages to be converted to Diameter format, reducing the need for separate RADIUS-specific prepaid service implementations.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The translation mechanism provides multi-functionality by handling multiple message types (Access-Request, Accounting-Request, Disconnect-Request) and converting them to appropriate Diameter messages (Credit-Control-Request, Accounting-Request, Abort-Session-Request). This universal translation approach reduces vendor complexity by using a single translation framework for various prepaid service scenarios.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS8170055B2Method of converting between radius message and diameter messages

Publication Date: 2012.05.01

AI summary

In one embodiment of a method of translating a RADIUS message to a Diameter message, an access request message in RADIUS is translated to a credit control request message in Diameter. In one embodiment of a method of translating a Diameter message to a RADIUS message, a credit control answer message is translated to an access accept message.