MPLS Micro-Mobility Protocol Eliminates Static Home Agent

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing mobile IPv6 solutions require significant signaling overhead and rely on static home agents for mobility management, which limits efficiency and flexibility, especially in micro-mobility scenarios within networks.

Innovation Solution

Implementing a network-based micro-mobility protocol using Multi-Protocol Label Switching (MPLS) that establishes a bidirectional Label Switch Path (LSP) between a mobility anchor point and the mobile node's access router, eliminating the need for a static home agent and reducing signaling and tunneling overhead by separating identifiers and locators, allowing dynamic setup of dedicated paths for traffic engineering.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If mobile IPv6 uses a static home agent node with IP in IP tunneling for mobility management, then mobility can be maintained, but signaling overhead and tunneling overhead increase significantly

Engineering Contradiction:
Improvemobility maintenanceVSAvoidsignaling overhead
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts and removes the static home agent component from the mobility management system. Instead of using a dedicated home agent node, the mobile node itself assumes the home agent functionality, eliminating the need for separate home agent signaling and reducing overall signaling overhead in the network.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces a foreign agent as an intermediary component that assists in mobility management when the mobile node is in a foreign network. The foreign agent handles local mobility management tasks, reducing the need for direct signaling between the mobile node and home agent, thereby reducing signaling overhead.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If mobile IPv6 uses a static home agent node with IP in IP tunneling, then mobility management is possible, but the system complexity increases due to tunneling requirements

Engineering Contradiction:
Improvemobility managementVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent removes the IP in IP tunneling mechanism from the system. By allowing the mobile node to assume home agent functionality and using direct routing with care-of addresses, the complex tunneling infrastructure is eliminated, reducing system complexity while maintaining mobility management capabilities.

Inventive Principle:
Principle #2Taking out (Extraction)

3Adaptability or versatility

If variations of mobile IPv6 (FMIP, HMIP, RMIP) are used for local micro mobility, then mobility within domains is enabled, but significant signaling overhead is generated

Engineering Contradiction:
Improvelocal micro mobilityVSAvoidsignaling overhead
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent implements self-service mobility management where the mobile node autonomously manages its own mobility without requiring complex signaling to external mobility management entities. The mobile node uses its care-of address to directly route packets, eliminating the need for signaling overhead associated with FMIP, HMIP, or RMIP variations.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8503416B2Method and system for efficient homeless MPLS micro-mobility
Publication Date: 2013.08.06 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US8503416B2 patent drawing
  • US8503416B2 patent drawing
  • US8503416B2 patent drawing

AI summary

A method performed by a network element for providing micro-mobility in a network to a mobile node including the steps of receiving a registration request message at the mobility anchor point from an access router that is currently coupled to the mobile node, wherein the registration request message includes an endpoint identifier of the mobile node and a local care-of address of the mobile node, establishing a label switch path (LSP) between the mobility anchor point and the access router, storing the endpoint identifier in a binding entry along with the local care-of address, a regional care-of address, the label switch path and an egress interface, advertising the endpoint identifier with associated regional or local care-of address of the mobile node, and forwarding data packets, received at the mobility anchor point from a corresponding node that have the regional or local care-of address, to the mobile node using the LSP.