Device Level Addressing for Unnumbered Network Interfaces

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional computer networks face challenges in efficiently managing unique network addresses, particularly with IPv4's limited address availability and difficulties in deploying network devices due to the need for numerous address assignments, which complicates remote access and administration when underlying routing protocols fail.

Innovation Solution

Implementing a device-level addressing system where each network device is assigned a single, persistent address stored in nonvolatile memory, allowing communication through unnumbered interfaces by announcing and storing device-level addresses with neighboring devices, enabling access even in the absence of higher-level routing protocols.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If unique interface addresses are assigned to each network device interface, then data routing is enabled, but address management complexity increases and remote access becomes difficult when routing protocols fail

Engineering Contradiction:
Improveremote access reliabilityVSAvoidaddress management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the essential identifying function from interface-level addresses and consolidates it into a single device-level address. This removes the complexity of managing multiple interface addresses while preserving the ability to uniquely identify and access network devices, even when routing protocols fail.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The device-level address serves multiple functions: it identifies the device for routing purposes, enables remote access, and maintains functionality during routing protocol failures. This multi-functional address eliminates the need for separate interface addresses, simplifying management while improving reliability.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If IPv4 addressing scheme is used, then network devices can be addressed, but the limited number of unique addresses reduces scalability

Engineering Contradiction:
Improvenetwork scalabilityVSAvoidnumber of unique addresses
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent merges the identification function of multiple interface addresses into a single device-level address. This consolidation reduces the total number of addresses needed from the perspective of remote access and administration, while the underlying routing protocols continue to manage interface-level routing information.

Inventive Principle:
Principle #5Merging (Combining)

3Device complexity

If unnumbered interfaces are used, then address management is simplified, but remote access becomes impossible when routing protocols fail

Engineering Contradiction:
Improveaddress management complexityVSAvoidremote access reliability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent implements preliminary action by pre-configuring device-level addresses to be persistent and stored in non-volatile memory. These addresses are announced to neighboring devices during normal operation and stored in routing tables, ensuring that remote access remains possible even if routing protocols fail, as the device-level addresses provide a fallback mechanism.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8732335B2Device communications over unnumbered interfaces
Publication Date: 2014.05.20 JUNIPER NETWORKS INC
  • US8732335B2 patent drawing
  • US8732335B2 patent drawing
  • US8732335B2 patent drawing

AI summary

A method and a network device for enabling communication between unnumbered interfaces are provided. A device level address may be assigned to a network device. The network device may announce the assigned device level address to a neighboring network device over a link. A corresponding device level address associated with the neighboring network device may be received over the link. A route may be stored including the received device level address associated with the neighboring network device and the link. In some implementations, the announcement of the assigned device level address is performed during protocol configuration.