Mobile Node Multi-Interface Connectivity via FQDN Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile IP technologies fail to effectively manage multiple network interfaces, leading to issues such as single interface dominance in single FQDN cases and lack of connectivity when one interface drops in multiple FQDN cases, limiting the utilization of multiple-interface capabilities.
Innovation Solution
A method for a mobile node to retrieve local IP and DNS server addresses, query home agents, perform binding updates, and maintain a list of active home agents and their associated FQDNs, allowing transparent failover and improved connectivity across multiple interfaces.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If the mobile node uses a single FQDN mapped to the lastly bound home address, then the DNS update process is simple, but only one interface is effectively utilized and other interfaces become redundant
Solution Approach 1:
The patent segments the single FQDN mapping into multiple mappings, where each home address can be independently mapped to the FQDN. This allows the system to maintain simplicity in DNS update procedures while simultaneously enabling multiple interfaces to be actively utilized, as each interface's home address can be bound to the FQDN without affecting others.
Solution Approach 2:
The FQDN is given multi-functionality by allowing it to map to multiple home addresses simultaneously. Instead of the FQDN being tied to a single home address, it can serve as a universal identifier that resolves to any of the mobile node's home addresses, thereby enabling multiple interfaces to function while maintaining a single logical identity.
2Adaptability or versatility
If the mobile node uses multiple FQDNs for multiple home addresses, then all interfaces can be utilized, but the mobile node lacks a single logical identity and connectivity may be lost when one interface drops
Solution Approach 1:
The patent segments the reliability requirement into individual home address bindings while maintaining a unified FQDN. Each home address can be independently bound to the FQDN, allowing the system to utilize multiple interfaces while ensuring that the loss of one interface does not affect the overall connectivity, as the FQDN can still resolve to other valid home addresses.
Solution Approach 2:
The system prepares for potential interface failures by maintaining multiple active home address to FQDN mappings in advance. When one interface drops, the cushioning effect is realized as the system can seamlessly continue using other interfaces with their associated home addresses, preventing connectivity loss without requiring complex real-time reconfiguration.
3Adaptability or versatility
If the mobile node maintains multiple binding updates with different home agents, then connectivity through multiple interfaces is possible, but managing the bindings and DNS updates becomes complex
Solution Approach 1:
The patent merges multiple binding updates into a unified management framework where all home addresses are bound to a single FQDN. This consolidation simplifies DNS update management, as the system only needs to maintain one FQDN mapping rather than managing multiple separate FQDNs, thereby reducing complexity while preserving multi-interface connectivity capabilities.
Solution Approach 2:
The FQDN serves as a universal identifier that handles multiple home addresses simultaneously, eliminating the need for complex management of separate bindings. Each home agent can update bindings independently, and the FQDN universally resolves to any valid home address, simplifying the overall binding update management process.
Data Source
AI summary
The invention relates to a method for connecting a mobile node (1) comprising a plurality of network connection interfaces (11a, 11b) to at least one network (3) using the mobile internet protocol with the following steps for the respective interfaces (11a, 11b): —the mobile node (1) retrieves a local IP address (CoAa, CoAb) and at least one DNS server (5, 5a, 5b) address using DHCP on the interface (11a, 11b), —the mobile node (1) stores in a list the at least one returned DNS server (5, 5a, 5b) address, —the mobile node (1) queries the at least one DNS server (5, 5a, 5b) which has its address stored in the list for home agent service and receives either a “service not supported” failure notification or the address of at least one home agent (9a, 9b) reachable on the interface (11a, 11b),—the mobile node (1) stores in the list the results of the query, either “service not available” or the home agent (9a, 9b) addresses returned for the respective DNS Servers (5, 5a, 5b) inquired, —the mobile node (1) obtains a home address (Ho Aa, Ho Ab) on the interface, _13 the mobile node (1) attempts to perform a binding update for care-of-address (Co Aa, Co Ab) and home address (HoAa, HoAb) towards the at least one home agent (9a, 9b) address stored in the previous list and updates its stored list accordingly with respective binding success or binding failure notifications, in case of success, the mobile node (1) records on the list a fully qualified domain name associated to the interface (11a, 11b). The invention also relates to the associated mobile node and DHCP unit.