DHCP Protocol Emulating PPP Authentication Functions

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current approaches to migrate PPP functions to IP over Ethernet infrastructure face drawbacks, such as increased network resource consumption and inability to emulate PPP interactions with AAA servers, leading to inefficiencies in user authentication and service authorization.

Innovation Solution

Implementing modified DHCP processes and DHCP option types to emulate PPP interactions with AAA servers, allowing DHCP to replace PPP functionality between customer premises nodes and provider remote access servers, thereby integrating authentication, authorization, and keep-alive mechanisms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If PPP functions are migrated to IP over Ethernet infrastructure using conventional approaches, then the transition to IP-based systems is achieved, but network resource consumption increases and authentication efficiency deteriorates

Engineering Contradiction:

Improvetransition to IP-based systemsVSAvoidnetwork resource consumption

Core Design Contradiction:

Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The patent creates a DHCP-based copy of PPP functionality that replicates authentication, authorization, and keep-alive mechanisms. Instead of directly implementing PPP over Ethernet, the invention uses DHCP protocol messages to emulate PPP control plane functions, thereby reducing network resource consumption while maintaining compatibility with existing IP-based infrastructure.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The patent changes the protocol parameters from PPP to DHCP, utilizing DHCP option types to carry authentication and authorization information. By modifying how these functions are implemented (using DHCP instead of PPP), the system achieves the same adaptability benefits while reducing network resource consumption through more efficient IP-based messaging.

Inventive Principle:

Principle #35Parameter changes

2Device complexity

If PPP functions are replaced with conventional IP-based approaches, then the system simplifies to pure IP protocols, but the ability to emulate PPP interactions with AAA servers is lost

Engineering Contradiction:

Improveprotocol stack simplicityVSAvoidemulation of PPP interactions

Core Design Contradiction:

Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent makes the DHCP protocol multi-functional by extending it to perform not only address assignment but also authentication, authorization, and PPP-like control plane functions. Through customized DHCP option types, a single protocol (DHCP) handles multiple functions that would traditionally require separate PPP implementation, maintaining AAA server compatibility while simplifying the overall protocol stack.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent uses DHCP as an intermediary protocol to bridge between IP-based infrastructure and AAA server interactions. Instead of direct PPP interactions, DHCP messages serve as the intermediary carrier for authentication and authorization data, enabling PPP emulation over IP networks without requiring actual PPP protocol support in the network stack.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Use of energy by moving object

If PPP is completely replaced by DHCP, then network resource consumption is reduced, but authentication and authorization mechanisms must be reimplemented

Engineering Contradiction:

Improvenetwork resource consumptionVSAvoidauthentication implementation

Core Design Contradiction:

Use of energy by moving objectVSDevice complexity

Solution Approach 1:

The patent performs preliminary action by defining standardized DHCP option types and authentication mechanisms in advance. These pre-defined options (such as DHCP option 61 for host name, and custom options for authentication) are established beforehand, allowing DHCP to handle authentication and authorization without requiring complex runtime implementations. The authentication logic is prepared and integrated into the DHCP protocol framework prior to actual user connections.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS7853708B2Techniques for replacing point to point protocol with dynamic host configuration protocol

Publication Date: 2010.12.14 CISCO TECHNOLOGY INC

AI summary

Techniques for providing remote access to a service provider network include exchanging multiple Dynamic Host Configuration Protocol (DHCP) formatted messages instead of any Point to Point Protocol (PPP) message to provide all PPP functions for accessing a service provider network from a customer node. The service provider network is on provider premises and the customer node is on customer premises different from the provider premises. The DHCP format is used to exchange authentication messages, user profile data on Authentication, Authorization and Accounting (AAA) servers, or session keep-alive echo messages, alone or in some combination. When all are message types are combined, these techniques provide a remote access server (RAS) with the capability to perform all functions presently provided by PPP processes. In some combinations, these techniques allow a modified DHCP server to replace a legacy AAA server.