Methods, systems, and computer program products for routing using headers including a sequence of node scope-specific identifiers

Patent No. US10382327 (titled "Methods, systems, and computer program products for routing using headers including a sequence of node scope-specific identifiers") on Aug 10, 2018. The application was issued on Aug 13, 2019.

What is this patent about?

’327 is related to the field of network routing and packet forwarding, specifically within Multiprotocol Label Switching (MPLS) environments. It addresses the limitations of traditional global addressing schemes, such as IPv4 and IPv6, which face scalability issues and increasing latency as networks expand. The invention proposes a shift from identifying 'where' a node is located to defining 'how' to reach it by utilizing path-based information rather than fixed global addresses.

The underlying idea behind ’327 is the use of a path-based protocol address composed of a sequence of identifiers that are specific to the local context of each node along a route. Instead of a single global identifier, the system uses a chain of node scope-specific identifiers, where each segment of the address only needs to be meaningful to the node currently processing the packet. This allows for a highly efficient, source-routed approach where the path is baked into the packet header itself, reducing the need for complex global routing tables at every intermediate hop.

The claims of ’327 focus on a current node in an MPLS network that identifies a specific sequence of these scope-specific identifiers to reach a destination. The node extracts the first identifier in the sequence to determine the immediate next hop and then generates a modified header containing only the remaining identifiers. By transmitting the data with this truncated sequence, the current node ensures that the next node in the path receives a header where its own relevant local identifier is now at the front of the queue.

In practice, this mechanism functions like a self-navigating map where each instruction is discarded once followed. When a packet arrives at a router, the device looks at the leading scope-specific identifier, which might simply be a local port number or a short index unique to that router's neighborhood. Because the identifier is local to that specific node's address space, the same bit pattern could represent entirely different physical paths when encountered by a different router later in the sequence, allowing for massive address reuse across the network.

This approach differentiates itself from prior art by effectively merging the concepts of naming, addressing, and routing into a single nested protocol address. Unlike standard MPLS which relies on label distribution protocols to set up paths in advance, this invention allows for dynamic path selection based on policy or real-time network conditions at the source. By utilizing interface-based identifiers that are optimized for size and processing speed, the system minimizes header overhead and eliminates the lookup latency associated with massive global routing databases.

How does this patent fit in bigger picture?

Technical Landscape

In the early 2010s when ’327 was filed, network routing was typically implemented using global addressing schemes where a distinction was maintained between a node's identity and the path used to reach it. At a time when systems commonly relied on centralized or hierarchical address allocation to ensure global uniqueness, hardware and software constraints made the dynamic resolution of multi-hop paths non-trivial without significant routing table overhead. In these environments, packet forwarding generally required each intermediate router to perform independent lookups against large, globally-synchronized routing tables, as protocol addresses were decoupled from the underlying network topology.

Prosecution Position

The disclosed invention represents a technical advancement through an architectural shift from global destination-based routing to path-based protocol addressing within a Multiprotocol Label Switching (MPLS) environment. By integrating a sequence of node scope-specific identifiers directly into the packet header, the system enables a source node to define a specific multi-hop trajectory where each identifier is valid only within the local context of a corresponding node in the path. This structural solution overcomes the technical constraints of traditional global address resolution by allowing intermediate nodes to identify the next hop using localized identifier spaces, thereby reducing the reliance on global routing state and enabling more granular control over network paths based on specific policies or node-level constraints.

Claims

This patent contains 58 claims, with claims 1, 28, 29, and 31 serving as the independent claims. The independent claims focus on an apparatus, a computer-readable medium, and methods for routing data in a Multiprotocol Label Switching network by identifying a sequence of node scope-specific identifiers that correspond to specific identifier spaces for each node along a path to a receiving node. The dependent claims serve to further define the specific types of network interfaces identified, the methods for mapping and receiving identifier information from controllers or other nodes, the selection criteria for the identifier sequences, and the physical or logical characteristics of the network nodes and paths involved.

Key Claim Terms New

Definitions of key terms used in the patent claims.

Term (Source)Support for SpecificationInterpretation
Multiprotocol Label Switching (MPLS) network
(Claim 1, Claim 28, Claim 29, Claim 31)
An apparatus is provided, comprising: a current node configured to be positioned in a Multiprotocol Label Switching (MPLS) network. Methods and systems are described for routing based on a path-based protocol address. The current node includes at least one non-transitory memory configured to store instructions, and one or more processors in communication with the at least one non-transitory memory.A specific network environment that utilizes labels to direct data from one node to the next, serving as the deployment context for the path-based routing method.
Node scope-specific identifiers
(Claim 1, Claim 28, Claim 29, Claim 31)
The specification describes these as identifiers where each is in one of a plurality of node scope-specific identifier spaces specific to a corresponding node in a path. Each identifier identifies, for that specific node, a corresponding next node in the path toward the receiving node.Identifiers that are unique or valid only within the context or 'scope' of a specific network node, used to designate a subsequent hop or next node in a transmission path.
Node scope-specific identifier spaces
(Claim 1, Claim 28, Claim 29, Claim 31)
Each of the node scope-specific identifiers of the sequence is in one of a plurality of node scope-specific identifier spaces that is specific to a corresponding one of a plurality of nodes in a path from the current node toward the receiving node. The internet module maps internet addresses to local net addresses. The subject matter described herein challenges the distinctions asserted in RFC 791 between and among names, addresses, and routes.A collection of addressing domains where each domain is unique or specific to a particular node, rather than being part of a single global address space.
Remaining of the node scope-specific identifiers
(Claim 1, Claim 28, Claim 29, Claim 31)
Generate a first header including at least a remaining of the node scope-specific identifiers of the sequence other than the first one, for use in transmitting the first data along the path toward the receiving node. Transmit, based on the first one of the node scope-specific identifiers of the sequence, the first data and the first header along the path from the current node to the next node.The portion of the identifier sequence that persists in the packet header after the current node has used the first identifier to determine the immediate next hop.
Sequence of node scope-specific identifiers
(Claim 1, Claim 28, Claim 29, Claim 31)
The subject matter described herein challenges the distinctions asserted in RFC 791 between and among names, addresses, and routes. Methods and systems are described for routing based on a path-based protocol address. Each of the node scope-specific identifiers identifies, for the corresponding one of the plurality of nodes, a corresponding next node in the path from the current node toward the receiving node.An ordered set of identifiers where each identifier is valid within the local context of a specific node in a network path and points to the subsequent node in that path.

Litigation Cases New

US Latest litigation cases involving this patent.

Case NumberFiling DateTitle
4:25-cv-00853Aug 7, 2025Morris Routing Technologies, LLC v. Comcast Business Communications, LLC et al

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

US10382327

Application Number
US16101382A
Filing Date
Aug 10, 2018
Publication Date
Aug 13, 2019
External Links
Slate, USPTO , Google Patents