Proxy Mobile IP Registration for Non-CHAP Nodes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Proxy Mobile IP registration is unsupported for nodes that do not support the Challenge Handshake Authentication Protocol (CHAP) due to the inability of network devices like PDSN to generate a CHAP challenge and response, which is required for Mobile IP registration.

Innovation Solution

A AAA server or network device, such as a PDSN or Foreign Agent, generates a CHAP challenge and response, enabling the creation of a Mobile IP registration request, even for nodes that do not support CHAP, by obtaining a password associated with the node and generating a CHAP response, which is then sent to the PDSN or Foreign Agent to compose the registration request.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If CHAP authentication is required for Mobile IP registration, then security is improved, but compatibility with nodes that do not support CHAP deteriorates

Engineering Contradiction:
Improveauthentication securityVSAvoidcompatibility with non-CHAP nodes
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a proxy entity (Foreign Agent or PDSN) as an intermediary that performs CHAP authentication on behalf of nodes that do not support CHAP. The proxy entity generates CHAP challenges and responses using the node's identity information, enabling these nodes to participate in Mobile IP registration without native CHAP support. This mediator approach maintains security requirements while extending compatibility to non-CHAP nodes.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If proxy Mobile IP registration is implemented, then roaming capability is improved, but authentication complexity increases

Engineering Contradiction:
Improveroaming capabilityVSAvoidauthentication process complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent enables proxy entities to perform self-service authentication by automatically generating CHAP challenges and responses using readily available node identity information. The Foreign Agent or PDSN can autonomously create the authentication credentials without requiring direct CHAP implementation on the mobile node itself, simplifying the overall authentication process while maintaining security.

Inventive Principle:
Principle #25Self-service

3Reliability

If CHAP challenge and response generation is centralized in AAA server, then authentication reliability is improved, but network latency increases

Engineering Contradiction:
Improveauthentication reliabilityVSAvoidauthentication latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by having the AAA server pre-generate and distribute authentication credentials (CHAP challenges and responses) to proxy entities before actual Mobile IP registration occurs. This advance preparation allows proxy entities to immediately use these pre-computed credentials when nodes need to register, eliminating the need for real-time CHAP computation during the registration process and thus reducing latency.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP1946482B1Allowing network access for proxy mobile IP cases for nodes that do not support chap authentication
Publication Date: 2020.01.29 CISCO TECHNOLOGY INC
  • EP1946482B1 patent drawingFigure 1
  • EP1946482B1 patent drawingFigure 2
  • EP1946482B1 patent drawingFigure 3

AI summary

The disclosed embodiments support proxy Mobile IP registration for nodes that do not implement CHAP. This is accomplished, in part, through the generation of a CHAP challenge and response by either a AAA server or a network device such as a PDSN or Foreign Agent. If the CHAP challenge and response is generated by the AAA server, the AAA server provides the CHAP challenge and response to the network device. In this manner, the network device may generate a Mobile IP registration request based upon the CHAP challenge and response.