Routing methods, systems, and computer program products

Patent No. US10587505 (titled "Routing methods, systems, and computer program products") on Apr 24, 2018. The application was issued on Mar 10, 2020.

What is this patent about?

’505 is related to the field of network routing and data transmission, specifically addressing the limitations of traditional global addressing schemes in large-scale networks. It provides a framework for navigating complex topologies by utilizing path-based and scope-specific identifiers within a label switching forwarding paradigm, such as MPLS, to reduce latency and manage the exhaustion of global address spaces.

The underlying idea behind ’505 is the transition from rigid, global destination addresses to a flexible, hierarchical system of scope-specific identifiers that describe the path to be taken. By embedding a sequence of identifiers—ranging from broad regional node IDs to specific local interface IDs—directly into the packet header, the invention allows each node to make forwarding decisions based on its own local context and the specific segment of the path it is responsible for.

The claims of ’505 focus on a current node’s ability to identify and utilize different types of identifiers from a packet header to transmit data along a network path. These identifiers include region-scoped node identifiers for routing within a specific area, scope-specific node identifiers for reaching nodes in external regions, and node-scoped network interface identifiers for direct transmission via a specific physical or logical interface.

In practice, the system operates by having a node detect path information in a packet header and select the appropriate identifier based on a pre-defined policy or schema. If a regional identifier is chosen, the node uses its internal routing table to select a path segment, which may involve multiple hops, to reach a target node within that same region. Conversely, if a scope-specific identifier is used, the node identifies a target in a different region and forwards the data through a segment that bridges the two areas, effectively treating the external node as a reachable endpoint within its own region-specific identifier space.

This approach differs from prior solutions by moving away from the strict distinction between names, addresses, and routes. Instead of relying solely on a global lookup to find a destination, the invention uses path-based protocol addresses that essentially contain the 'map' to the destination. This allows for more efficient routing in segmented networks, as nodes only need to understand the identifiers relevant to their immediate scope or region, rather than maintaining exhaustive knowledge of the entire global network topology.

How does this patent fit in bigger picture?

Technical Landscape

In the early 2010s when ’505 was filed, network routing was typically implemented using global addressing schemes where a clear 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 manage growing global networks, the exhaustion of traditional 32-bit address spaces made the efficient scaling of routing tables and the reduction of network latency non-trivial. During this era, hardware and software constraints often required routers to perform complex lookups to map static addresses to dynamic routes, as protocol architectures generally treated names, addresses, and routes as discrete functional entities rather than integrated components of a path-based forwarding mechanism.

Prosecution Position

The disclosed invention represents a technical advancement through the integration of path-based information directly into protocol headers to facilitate more flexible and efficient routing. By utilizing a plurality of identifiers—including region-scoped, scope-specific, and node-scoped interface identifiers—within a packet header, the architecture enables a node to select and execute forwarding decisions based on localized or regional network contexts. This structural shift allows for the selection of multi-hop path segments based on specific metrics or policies, effectively overcoming the constraints of traditional global addressing. The technical effect achieved is a more granular control over data transmission paths, enabling the network to resolve routing at different levels of scope and reducing the reliance on global mapping tables for every hop in a network path.

Claims

US Patent 10,587,505 contains 60 claims, with claims 1, 11, 16, 26, 31, 41, 46, and 56 serving as the independent claims. The independent claims focus on systems and methods for network data transmission using label switching, specifically identifying and utilizing various types of scoped identifiers—such as region-scoped, scope-specific, or node-scoped interface identifiers—to route data through specific network path segments or regions based on defined policies. The dependent claims serve to further refine these routing mechanisms by specifying various identifier configurations, detailing the selection of path segments based on routing metrics or tables, and defining the operational environments, such as Multiprotocol Label Switching networks, in which these identifiers are applied.

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 11, Claim 16, Claim 26, Claim 31, Claim 41, Claim 46, Claim 56)
The network path information is in a header of a first packet that is specified according to a label switching forwarding paradigm, such as a Multiprotocol Label Switching (MPLS) network protocol. The network path information in the header is for use by the current node in transmitting data from the transmitting node to the receiving node. The header is configured for use in identifying a plurality of different identifiers.A network transport mechanism, such as Multiprotocol Label Switching (MPLS), where data is directed through the network based on path information contained in a packet header rather than long network addresses.
Node scoped network interface identifier
(Claim 1, Claim 16, Claim 31, Claim 46)
The node scoped network interface identifier identifies a network interface of the current node for transmitting the first data. In the event that the node scoped network interface identifier is utilized, the current node transmits the first data via the network interface to the receiving node along the network path. This identifier is used when the current node is included in a hop in the network path segment.A local identifier that uniquely specifies a particular physical or logical egress port or interface on the current node itself.
Region scoped node identifier
(Claim 1, Claim 11, Claim 16, Claim 26, Claim 31, Claim 41, Claim 46, Claim 56)
The region scoped node identifier is in an identifier space having a scope that spans a first particular region of the network and identifies a first particular node of a plurality of nodes including the current node in the first particular region of the network. The first data is transmitted to the first particular node via a path segment selected from multiple path segments, including at least one multi-hop path segment. This allows for routing within a specific region of the network using a routing table of the current node.An identifier within a specific address space that is valid across a defined geographic or logical area of the network, used to identify a specific node within that area for multi-hop routing.
Schema of the header
(Claim 16, Claim 26, Claim 46, Claim 56)
The current node utilizes the network path information to select identifiers based on a schema of the header of the first packet. This selection process allows the node to determine whether to use a region scoped node identifier, a region scope-specific node identifier, or a node scoped network interface identifier. The schema defines how the plurality of different identifiers are identified and processed for routing.The structural format or organizational rules of the packet header that dictate how the plurality of identifiers are arranged and interpreted by a node.
Scope-specific node identifier
(Claim 1, Claim 11, Claim 31, Claim 41)
The first scope-specific node identifier is in a region-specific identifier space that is specific to, and thus is only useable for data routing in, a first specific region that includes the current node. It identifies, for the current node, a second particular node in a second particular region where the current node is not located. Transmission occurs via a path segment selected from multiple path segments, including at least one multi-hop path segment, that couple the current node and the node in the other region.A routing identifier belonging to a region-specific address space that allows a node in one region to identify and route data to a node located in a different, non-overlapping region.

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

US10587505

Application Number
US15961828A
Filing Date
Apr 24, 2018
Publication Date
Mar 10, 2020
External Links
Slate, USPTO , Google Patents