Methods, systems, and computer program products for associating a name with a network path

Patent No. US10904144 (titled "Methods, systems, and computer program products for associating a name with a network path") on May 9, 2014. The application was issued on Jan 26, 2021.

What is this patent about?

’144 is related to the field of network routing and addressing, specifically addressing the limitations of global identifier spaces like standard IPv4 and IPv6. It provides a framework for navigating complex network topologies by moving away from the rigid distinction between names, addresses, and routes. The background context involves the increasing latency and exhaustion of global address spaces, necessitating a more flexible approach to how nodes identify one another and determine the paths between them.

The underlying idea behind ’144 is the use of scope-specific and path-based identifiers that redefine how a node locates a destination based on its own position within the network topology. Instead of relying solely on a global IP address, the invention leverages identifiers that are valid only within specific regions or relative to specific nodes. By treating a protocol address as a sequence of hop or interface identifiers, the system allows for dynamic path discovery and routing that is inherently tied to the network's physical or logical structure.

The claims of ’144 focus on a current node’s ability to process a packet header—formatted according to label switching or IPv6—to identify a region scoped node identifier. This identifier exists within a space that spans a specific region and globally identifies a target node within that region. The claims specifically cover the mechanism where the current node uses this scoped identifier to select a path segment from its routing table, including multi-hop segments, to forward data toward a receiving node that resides within that defined topological region.

In practice, the invention operates by having nodes detect their immediate neighbors and determine hop identifiers, which are then reported to a topology service. This service builds a representation of the network in a metric space, allowing nodes to resolve symbolic names into path-based protocol addresses. When a packet arrives, the node evaluates the header to determine if the identifier is specific to its own region or a remote one, adjusting the address separator or bit-mask to expose the next relevant routing instruction for the subsequent segment of the journey.

This approach differentiates itself from prior art by replacing static global addressing with a nested, hierarchical, or path-relative scheme. Unlike standard CIDR or IPv6 global unicast routing, which treats the address as a fixed destination, ’144 enables source routing and scope-specific translation where the meaning of an address can change as it traverses different network zones. This reduces the reliance on a single global namespace and allows for more efficient routing through multi-hop segments by utilizing the inherent geometry of the network topology.

How does this patent fit in bigger picture?

Technical Landscape

In the early 2010s when ’144 was filed, network routing and addressing were typically implemented using global identifier spaces where protocol addresses served as static locators for nodes or interfaces. At a time when systems commonly relied on centralized or hierarchical directory services to resolve symbolic names to these fixed addresses, the distinction between a node's identity and its topological location was rigid. Hardware and software constraints of the era made the dynamic integration of path-based information into the addressing layer non-trivial, as routing logic was generally decoupled from the symbolic naming systems used at the application layer.

Prosecution Position

The disclosed invention represents a technical advancement by establishing a functional convergence between symbolic identifiers and network topology. The architectural shift involves a system that associates a node's symbolic name directly with specific network path information, such as hop identifiers, rather than relying on traditional static global addresses. This integration is achieved through a mechanism where nodes detect neighbors, determine hop-specific identifiers, and propagate these associations to a topology service to define a node's location relative to its peers. This solution overcomes the technical constraint of address space exhaustion and routing latency by enabling a topological space where addresses are derived from path information, thereby streamlining the mapping between what a node is and how it is reached within a network.

Claims

US10,904,144 contains a total of 32 claims, with claims 1, 29, and 31 serving as the independent claims. These independent claims focus on methods for configuring and storing instructions that enable a network node to identify region-scoped or scope-specific node identifiers within packet headers—specifically those following label switching or IPv6 protocols—and subsequently transmit data via path segments selected from a routing table, including multi-hop segments. The dependent claims serve to further define the network architecture, specifying variations in routing policies, the location of transmitting and receiving nodes relative to network regions, the use of symbolic identifiers, and the technical characteristics of the non-transitory memory and circuitry employed.

Key Claim Terms New

Definitions of key terms used in the patent claims.

Term (Source)Support for SpecificationInterpretation
Label switching forwarding paradigm
(Claim 1, Claim 29, Claim 31)
The specification references the OpenFlow protocol and its switch specification as a platform for building new protocols within the scope of the disclosure. It describes identifying a protocol address based on path information and routing based on path-based protocol addresses. This paradigm supports the mapping of internet addresses to local net addresses and routes as discussed in the context of IETF standards.A network routing mechanism where data is directed through the network based on path information or labels positioned in a packet header rather than traditional long network addresses.
Multi-hop path segment
(Claim 1, Claim 31)
The specification describes determining a shared identifier for a hop in a network and determining a hop identifier for a network protocol. It mentions that a network path includes a first hop included in communicatively coupling nodes. The system identifies path information identifying hops in a network path to associate symbolic identifiers with network paths.A portion of a network path that consists of multiple intermediate links or nodes between a starting node and a destination node within a region.
Region scoped node identifier
(Claim 1, Claim 29, Claim 31)
The specification describes a global identifier space for identifying nodes and their network interfaces, noting that current addresses provide another global identifier space. It challenges the distinctions in RFC 791 to establish new relationships between names, addresses, and routes. The system utilizes these identifiers to represent nodes in a topological space where locations are identified relative to other nodes.An identifier within a specific identifier space that has a scope limited to a particular region of a network, used to globally identify a specific node within that region for routing purposes.
Scope-specific node identifier
(Claim 29, Claim 31)
The specification describes methods for transmitting data via a scope-specific protocol address and identifying protocol addresses in a scope-specific address space. It notes that these addresses are used to identify a protocol address based on path information. The system allows for routing based on these scope-specific addresses to address problems of network latency and growth.An identifier in a region-specific identifier space that is unique to and only usable for routing data within at least one specific region, identifying a node that may reside outside the current node's immediate region.
Topological space
(Claim 1 (via 'region of the network' context), Summary)
The topology service includes a representation of a node in a first location in a topological space. This location is identified relative to a second node based on a hop identifier. The topology space component is operable for identifying path information identifying hops in a network path.A logical representation of network nodes where the location of a node is defined relative to another node based on hop identifiers and path information.

Litigation Cases New

US Latest litigation cases involving this patent.

Case NumberFiling DateTitle
4:24-cv-00625Jul 8, 2024Morris Routing Technologies, Llc V. T-Mobile Usa, Inc.

Patent Family

Patent Family

File Wrapper

The dossier documents provide a comprehensive record of the patent's prosecution history - including filings, correspondence, and decisions made by patent offices - and are crucial for understanding the patent's legal journey and any challenges it may have faced during examination.

  • Get instant alerts for new documents

US10904144

Application Number
US14274632A
Filing Date
May 9, 2014
Publication Date
Jan 26, 2021
External Links
Slate, USPTO , Google Patents