RADIUS Proxy Agent Injects Connection Parameters into HTTP Headers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Application Service Providers (ASPs) face challenges in accessing connection parameters such as identification, speed, and bandwidth across different access networks, which are not provided at the application level, affecting service quality, especially for media distribution, and existing solutions are hindered by proxies and firewalls.

Innovation Solution

A system comprising a RADIUS Client Agent (RCA) and a Provisioning Proxy Agent (PPA) that collects connection information using the RADIUS protocol and adds it to user requests, enabling automatic logon and service adaptation by intercepting and modifying HTTP requests with session parameters through a proxy server.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If connection parameters are retrieved from RADIUS server session table using client IP address, then connection information can be obtained, but this solution does not work when there is a proxy or firewall between the user and the web application

Engineering Contradiction:
Improveconnection information retrievalVSAvoidcompatibility with proxy/firewall configurations
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a RADIUS Proxy Agent as an intermediary component that sits between the web application and the RADIUS server. This agent intercepts authentication requests, retrieves connection parameters from the RADIUS server session table, and injects them into the HTTP headers of subsequent user requests. This mediator approach solves the problem by providing connection information through a different path that bypasses the proxy/firewall issue affecting direct RADIUS access.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary action by retrieving and storing connection parameters during the authentication phase before the user accesses the web application. The RADIUS Proxy Agent obtains connection information (such as connection type, speed, bandwidth) from the RADIUS server during login, and this information is then made available in HTTP headers for subsequent use without needing to query RADIUS again.

Inventive Principle:
Principle #10Preliminary action

2Loss of information

If connection parameters are requested from the user, then information about speed or bandwidth can be obtained, but the user is not able to answer or determine the speed negotiated by the modem

Engineering Contradiction:
Improveconnection parameter informationVSAvoiduser ability to provide information
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The system implements self-service by automatically retrieving connection parameters from the RADIUS server without requiring user input. The RADIUS Proxy Agent autonomously queries the RADIUS server using the user's authentication credentials and IP address to obtain connection type, speed, and bandwidth information, eliminating the need for users to manually provide this technical information.

Inventive Principle:
Principle #25Self-service

3Reliability

If the RADIUS server provides authentication and authorization, then user connection control is achieved, but the RADIUS server has no open interface to provide connection information in real time to third party application

Engineering Contradiction:
Improveauthentication and authorization controlVSAvoidinterface availability for third party applications
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the RADIUS server functionality by introducing a separate RADIUS Proxy Agent component. This agent handles the interaction with third-party web applications, while the core RADIUS server maintains its authentication and authorization functions. The Proxy Agent acts as an interface layer that translates RADIUS internal data into web-compatible HTTP headers, solving the interface availability problem without modifying the core RADIUS server.

Inventive Principle:
Principle #1Segmentation

4Adaptability or versatility

If application service providers adapt services according to access network type, then service quality can be improved, but connection parameters such as identification, speed or bandwidth are not provided at the application level

Engineering Contradiction:
Improveservice adaptation to access networkVSAvoidconnection parameters at application level
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The RADIUS Proxy Agent serves as an intermediary that bridges the gap between the RADIUS server's connection information and the web application's need for this data. It retrieves connection parameters (connection type, speed, bandwidth, identification) from the RADIUS server and injects them into HTTP headers, making this information available at the application level for service adaptation purposes.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent transports connection information from the traditional RADIUS protocol dimension to the web application dimension by embedding it in HTTP headers. This dimensional change allows connection parameters to be accessed within the web application ecosystem without requiring direct RADIUS protocol support in the application layer.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS7698384B2Information collecting system for providing connection information to an application in an IP network
Publication Date: 2010.04.13 X CORP
  • US7698384B2 patent drawing
  • US7698384B2 patent drawing
  • US7698384B2 patent drawing

AI summary

Information collecting system wherein at least an Application Service Provider (ASP) provides services to a user through an Internet network and wherein there are at least an access network to which is connected the user and an Internet Service Provider (ISP) network connected to each access network by a RADIUS client, the Internet network being connected to the ISP network by a proxy. This system comprises a RADIUS Client Agent (RCA) connected to the ISP network and adapted to collect information about parameters of the connection of the user to the system, and at least a Provisioning Proxy Agent (PPA) adapted to receive the information from the RCA and to add this information in the request sent by the user to the ASP.