Proxy MIP Gateway for Roaming Across Proxy Mobile IP Domains

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Establishing trust relationships between Home Agents and Proxy Mobile Agents across different Proxy MIP domains is impractical due to scalability issues and is further complicated by firewalls in closed networks, which hinder seamless roaming and traffic management.

Innovation Solution

Introducing a Proxy MIP Gateway at the interface between Home and Visited Proxy MIP domains, which emulates both Home Agent and Proxy Mobile Agent functions, allowing dynamic selection based on criteria such as trust and geographical location, and utilizing an Authentication, Authorization, and Accounting server to manage the selection and provisioning of this Gateway node.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If trust relationships are established between Home Agents and Proxy Mobile Agents across different Proxy MIP domains, then roaming between domains is enabled, but scalability becomes impractical due to the extensive trust relationships required

Engineering Contradiction:

Improveroaming capability between domainsVSAvoidtrust relationship management complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

A Gateway node is introduced as an intermediary between the Home Proxy MIP domain and Visited Proxy MIP domains. This Gateway node emulates both Home Agent and Proxy Mobile Agent functions, allowing roaming without requiring direct trust relationships between Home Agents and Proxy Mobile Agents across different domains. The Gateway acts as a mediator that simplifies the trust management complexity while enabling domain roaming.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If trust relationships are established between Home Agents and Proxy Mobile Agents in all Proxy MIP domains, then seamless roaming is enabled, but the system becomes impractical to manage due to the number of required trust relationships

Engineering Contradiction:

Improveseamless roamingVSAvoidnumber of trust relationships

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The Gateway node is designed with multi-functionality, emulating both Home Agent and Proxy Mobile Agent functions. This universal design allows a single Gateway node to handle multiple roles, reducing the number of separate trust relationships needed. The Gateway can serve multiple Visited Proxy MIP domains while maintaining reliable roaming through a simplified trust model.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Object-affected harmful factors

If firewalls are deployed in closed networks to protect Home networks, then network security is improved, but roaming and traffic management are hindered

Engineering Contradiction:

Improvenetwork security protectionVSAvoidroaming operation

Core Design Contradiction:

Object-affected harmful factorsVSEase of operation

Solution Approach 1:

The Gateway node serves as an intermediary that bridges the Home Proxy MIP domain and Visited Proxy MIP domains, including closed networks with firewalls. By emulating both Home Agent and Proxy Mobile Agent functions, the Gateway can navigate through firewall restrictions and enable roaming without compromising network security. The Gateway handles traffic management while maintaining security boundaries.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS9025589B2Method and apparatus for roaming between communication networks

Publication Date: 2015.05.05 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)

AI summary

A method and apparatus for managing roaming of a Mobile Node in a Visited network. The Mobile Node is associated with a Home network. In the Visited network, a server selects a Gateway node for use by the Mobile Node based on selection criteria. The server then sends a message to an access node in the Visited network to which the Mobile Node is attached, the message identifying the selected Gateway node. This instructs the Mobile Node to communicate with its Home network via the selected Gateway Node.