Routing methods, systems, and computer program products using multiple outside-scope identifiers

What is this patent about?

’583 is related to the field of network routing and packet forwarding, specifically addressing the limitations of traditional Internet Protocol (IP) addressing. In standard IP networking, addresses are typically global or subnet-specific, identifying a fixed location or interface. This often leads to complex routing tables and latency as the network scales. The invention context involves a shift toward path-based or scope-specific addressing where identifiers are relative to the node or region currently processing the data.

The underlying idea behind ’583 is the use of hierarchical, region-based identifiers that do not explicitly name a specific network interface, but rather identify a target region or scope. By using an outside-scope identifier, a node can determine how to forward data based on the relationship between its current region and a target region. This allows for a more fluid routing mechanism where the path is determined by the relative scope of the destination rather than a static, global map of every individual interface in the network.

The claims of ’583 focus on a method and apparatus for receiving a packet at a current node using a first identifier that links a previous node's region to the current node's region. The node then extracts a second outside-scope identifier from the packet header, which identifies a third region where the current node is not located. Based on this second identifier, the node selects a forwarding path from a plurality of options—including multi-hop path segments—to reach a next node that is part of that target third region.

In practice, the invention functions by treating the network as a series of nested or adjacent scopes. When a packet arrives, the current node recognizes it through an identifier that defines the communicative coupling between the previous region and its own. Instead of looking up a global IP address in a massive routing table, the node looks for the next 'scope' or region identified in the header. It then selects an appropriate path segment to bridge the gap between its current location and the boundary of the next identified region.

This approach differs from prior solutions by decoupling the routing logic from specific hardware interface addresses. Traditional IP routing requires every hop to know the specific next-hop interface for a destination. In contrast, ’583 utilizes region-based forwarding, where the node only needs to know how to reach the next region. This enables the use of path-based protocol addresses that can be processed more efficiently, as the routing decision is simplified into a series of scope transitions rather than global address resolutions.