Routing methods, systems, and computer program products using a region scoped outside-scope identifier

Patent No. US10397100 (titled "Routing methods, systems, and computer program products using a region scoped outside-scope identifier") on Oct 5, 2018. The application was issued on Aug 27, 2019.

What is this patent about?

’100 is related to the field of network routing and packet forwarding, specifically addressing the limitations of traditional Internet Protocol (IP) addressing. It background context involves the exhaustion of global IP address spaces and the increasing latency in large-scale networks, proposing a shift from standard interface-based addressing to a more flexible, path-oriented approach.

The underlying idea behind ’100 is the use of a region scoped outside-scope identifier that allows a node to route data toward an entire network region rather than a specific terminal interface. By decoupling the routing information from fixed IP interface identifiers, the system can navigate data through complex, multi-hop path segments based on localized policies and metrics, effectively treating a distant network region as a single reachable entity from the perspective of the current node.

The claims of ’100 focus on a method and apparatus for identifying network path information within an IP packet header that utilizes these specialized identifiers. The independent claims specifically cover the mechanism where a node in a first region identifies a second region via an identifier that lacks a standard IP network interface portion, subsequently selecting a multi-hop path segment to reach a border node that bridges the two regions.

In practice, the invention functions by having a current node evaluate a packet's header to extract path information governed by a specific policy. Instead of looking up a specific destination host, the node identifies a target region and selects the best available path segment—which may span multiple intermediate hops—to deliver the data to a border node. This selection process is dynamic, utilizing routing metrics or lookup tables to choose between various potential path segments that connect the current node's region to the target region.

This approach differs from prior art by moving away from the rigid distinction between names, addresses, and routes defined in early IP specifications. By using path-based protocol addresses and region-scoped identifiers, the system reduces the reliance on massive global routing tables. It allows for more efficient data transmission across regional boundaries by enabling nodes to make forwarding decisions based on the topological relationship between network zones rather than individual device endpoints.

How does this patent fit in bigger picture?

Technical Landscape

In the early 2010s when ’100 was filed, global networking was characterized by a reliance on the Internet Protocol (IP) as the primary mechanism for both addressing and routing. At a time when network architectures were typically implemented using 32-bit or 128-bit fixed-length address spaces, systems commonly relied on a strict functional separation where names identified entities, addresses identified locations, and routing tables determined the path between them. Hardware and software constraints of this era made the dynamic integration of path-specific information directly into protocol addresses non-trivial, as standard routing logic was optimized for hierarchical, interface-based prefix matching rather than variable-scope or path-based identifiers.

Prosecution Position

The disclosed invention represents a meaningful technical advancement through an architectural shift from interface-centric addressing to path-based and scope-specific routing. By integrating region-scoped outside-scope identifiers into a packet header—identifiers that lack a standard IP network interface portion—the system enables a node to identify and route data to a second network region based on a specific policy, table, or metric. This integration allows for the selection of multi-hop path segments that are decoupled from traditional global IP address constraints. The technical effect achieved is a more flexible routing capability that overcomes the limitations of fixed address spaces and rigid name-address-route distinctions, allowing for path selection and network traversal based on localized or policy-driven regional identifiers.

Claims

This patent contains 58 claims, with independent claims 1, 28, 29, 30, and 31 focusing on a system and method for routing data through a network using region-scoped identifiers that specify path segments and regions without relying on standard Internet Protocol network interface identifiers. These independent claims describe receiving packets, identifying path information based on specific policies, and selecting multi-hop path segments to transmit data to border nodes of subsequent network regions. The dependent claims further refine these operations by specifying the use of topology nodes for path customization, defining the scope and location of transmitting and receiving nodes across different network domains, and detailing the selection criteria for path segments based on metrics, tables, or network states.

Key Claim Terms New

Definitions of key terms used in the patent claims.

Term (Source)Support for SpecificationInterpretation
Border node
(Claim 1, Claim 28, Claim 29, Claim 30, Claim 31)
The border node is described as having a first network interface in the first region and having a second network interface in the second region. Data is transmitted from a current node to this border node via a selected path segment to reach the second region. It serves as the gateway for the network path to transition from the first region to the second region.A network device positioned at the boundary of two regions, possessing at least one network interface in a first region and at least one network interface in a second region to facilitate inter-region data transfer.
First path segment
(Claim 1, Claim 28, Claim 29, Claim 30, Claim 31)
The network path includes a first path segment that communicatively couples the current node and the second region. This segment is selected from a plurality of path segments based on a policy, table, or metric. It represents the immediate routing path used to reach the border node of the next region.A specific communicative coupling or link selected to transport data from a node in a first region toward a second region.
Multi-hop path segment
(Claim 1, Claim 28, Claim 29, Claim 30, Claim 31)
The summary describes transmitting data via a first path segment selected from a plurality of path segments, including at least one multi-hop path segment. These segments are capable of communicatively coupling the current node and the second region. The selection is based on at least one of a policy, a table, or a metric.A portion of a network path that spans multiple intermediate nodes or links between a current node and a target region or border node.
Network path information
(Claim 1, Claim 28, Claim 29, Claim 30, Claim 31)
The specification indicates that network path information is identified from a header of a first packet and is based on a first policy. This information includes the region scoped outside-scope identifier used to direct data transmission. The disclosure challenges the distinctions in RFC 791 by integrating routing and addressing through this path-based information.Data contained within a packet header, determined by a specific policy, that defines the route or segments (such as region identifiers) through which data is to be transmitted.
Region scoped outside-scope identifier
(Claim 1, Claim 28, Claim 29, Claim 30, Claim 31)
The summary describes a region scoped outside-scope identifier that is in an identifier space having a scope that spans a first region of the network. It does not include a network interface identifier portion specified by the IP network protocol for identifying any network interface. It identifies, in the first region, a second region of the network to facilitate routing across path segments.An identifier within a specific identifier space that spans a first network region, used to identify a second network region rather than a specific network interface, and which does not follow standard IP network interface identifier formats.

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
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

US10397100

Application Number
US16153196A
Filing Date
Oct 5, 2018
Publication Date
Aug 27, 2019
External Links
Slate, USPTO , Google Patents