Host Identification via Unique Identifier Lookup Tables

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Networking protocols cannot identify hosts without unique identifiers, leading to challenges in establishing reliable packet delivery paths, especially in networks like TCP/IP where pre-calculated paths are not determined, and there is a risk of single-point failures due to reliance on hosts without identifiers.

Innovation Solution

Assigning a unique host identifier that can be recognized at OSI Layers 1, 2, or 3, paired with network interface identifiers, and storing these pairs in a host/guest lookup table to build diverse packet delivery paths that avoid common hosts, extending or modifying existing protocols like MPLS to incorporate this host/guest relationship.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If networking protocols are used without unique host identifiers, then network operation is simple, but host identification and reliable packet delivery fail

Engineering Contradiction:
Improvepacket delivery reliabilityVSAvoidprotocol complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the identification system into two parts: existing network interface identifiers (handled by current protocols) and new host-level unique identifiers. This segmentation allows protocols to remain relatively simple while adding host identification capability, resolving the contradiction between reliability and complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary assignment of unique host identifiers to all hosts before network operation begins. This pre-configuration enables reliable packet delivery from the start without requiring complex runtime identification mechanisms, thus improving reliability while keeping protocol complexity manageable.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If pre-calculated packet delivery paths are not determined, then network flexibility is maintained, but single-point failures cannot be prevented

Engineering Contradiction:
Improvenetwork resilienceVSAvoidpath calculation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent performs preliminary path calculation to identify and avoid common hosts in diverse paths before packet transmission begins. By pre-calculating paths that avoid single points of failure, the system achieves network resilience without requiring complex dynamic path recalculation during operation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces host/guest lookup tables as an intermediary mechanism that stores pre-calculated host identification information. This intermediary enables path calculation systems to efficiently query and avoid common hosts without implementing complex real-time analysis, thus improving reliability while managing complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If host/guest lookup tables are implemented, then diverse packet delivery paths can be built, but information storage requirements increase

Engineering Contradiction:
Improvepacket delivery reliabilityVSAvoiddata storage requirement
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent segments the lookup table data into manageable host/guest identifier pairs that can be stored efficiently. By organizing data in this segmented format, the system achieves reliable path diversity while optimizing storage requirements through structured data organization.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8694673B2Systems and methods for host identification
Publication Date: 2014.04.08 VERIZON PATENT & LICENSING INC
  • US8694673B2 patent drawing
  • US8694673B2 patent drawing
  • US8694673B2 patent drawing

AI summary

A system and process may include assigning a unique host identifier to a host that is a node of a network. The host is adapted to host at least one network interface. The system and process may further include creating a host/guest relationship for each hosted network interface by associating a network interface identifier of the hosted network interface with the unique host identifier.