RADIUS Proxy Address Resolution for Destination Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
RADIUS messages lack a destination host parameter, making it difficult for RADIUS proxy agents to determine the intended destination, and Diameter agents face challenges in address resolution when handling inbound RADIUS or Diameter messages, especially when multiple destinations provide different services to subscriber groups.
Innovation Solution
Implementing a method for RADIUS proxy and Diameter agent address resolution in network nodes, which involves receiving inbound messages, determining if address resolution is required, performing the resolution, and routing outbound messages based on the results, using a combination of message processors and routing tables to identify correct destinations for RADIUS and Diameter messages.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If RADIUS messages are transmitted without a destination host parameter to simplify message structure, then message simplicity is improved, but the ability to determine message destination deteriorates
Solution Approach 1:
The patent introduces a RADIUS proxy agent as an intermediary component that receives RADIUS messages, performs address resolution to determine the ultimate destination, and forwards messages accordingly. This mediator resolves the contradiction by adding destination determination capability without modifying the original RADIUS message structure, maintaining simplicity while enabling proper routing through the proxy agent's resolution mechanism.
2Adaptability or versatility
If multiple destinations provide the same service for different subscriber groups to increase network versatility, then service coverage is improved, but the difficulty of determining the correct destination deteriorates
Solution Approach 1:
The patent implements preliminary address resolution by the RADIUS proxy agent before message forwarding. The proxy agent proactively determines the ultimate destination by resolving addresses based on subscriber information in the RADIUS message, even though the message itself doesn't contain destination information. This preliminary action enables the system to handle multiple destinations for different subscriber groups by pre-determining the correct routing path.
Solution Approach 2:
The system uses feedback mechanisms where the RADIUS proxy agent receives authentication requests, resolves addresses based on subscriber data, determines the appropriate destination server, and forwards messages accordingly. The destination determination is based on feedback from address resolution databases and subscriber information, enabling intelligent routing to the correct destination among multiple servers providing the same service.
Data Source
AI summary
A method for RADIUS proxy or Diameter agent address resolution is disclosed. The method may be implemented in a network node including a plurality of message processors. The method includes receiving an inbound RADIUS or Diameter message. The method further includes determining whether address resolution is required for the inbound message. The method further includes, in response to determining that address resolution is required for the inbound message, performing the address resolution. The method further includes routing an outbound message to a destination based on a result of the address resolution, where at least one of the inbound message and the outbound message comprises a RADIUS message.