Broker-Based Name Routing Across Firewalled Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional network routing techniques rely on IP addresses, which are limited in number, leading to IP conflicts and a need for more robust and scalable solutions.
Innovation Solution
Implement name-based routing through networks using primary and secondary broker managers to establish connections and manage pub/sub channels based on device names and network identifiers, enabling secure routing across firewalls without requiring port openings.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If IP address-based routing is used, then network routing can be implemented, but the limited number of IP addresses leads to conflicts and scalability issues
Solution Approach 1:
The patent changes the routing parameter from IP address to device name. Instead of relying on the limited numerical IP address space, the system uses human-readable device names that can be arbitrarily assigned, effectively removing the constraint on the number of addressable devices and eliminating IP address conflicts.
Solution Approach 2:
The patent introduces a name resolution intermediary (similar to DNS) that maps device names to network locations. This intermediary layer decouples the naming scheme from the actual network addressing, allowing devices to be identified by names while routing still occurs through network addresses, thus resolving the scalability issue without breaking existing routing infrastructure.
2Adaptability or versatility
If name-based routing is implemented, then scalability and robustness are improved, but system complexity increases due to broker managers and pub/sub channels
Solution Approach 1:
The broker manager is designed as a universal component that handles multiple functions: name resolution, connection management, message routing, and subscription handling. By consolidating these functions into a single multi-functional component, the patent reduces the number of separate system elements needed, thereby managing complexity while providing scalable name-based routing.
Solution Approach 2:
The pub/sub mechanism enables automatic message distribution without requiring explicit routing configurations. When a device publishes a message, the broker automatically delivers it to all subscribed devices based on their name-based subscriptions, eliminating the need for manual route setup and reducing operational complexity.
3Reliability
If traditional routing through firewalls is used, then network security is maintained, but port openings are required which reduce security
Solution Approach 1:
The broker manager acts as an intermediary that establishes secure connections through the firewall on behalf of devices. Instead of requiring direct device-to-device connections through open ports, the broker mediates all communications, maintaining firewall security while enabling reliable name-based routing through its authorized connection channels.
Data Source
AI summary
Novel tools and techniques are provided for implementing name-based routing through networks. In various embodiments, a broker manager in each of a plurality of networks may receive a subscription request for a network device from a client device, each device being locally accessible or disposed in an upstream or downstream network. The broker manager uses its client broker to communicate with a locally accessible client device, and uses its mediator broker (and, sometimes, an intermediate device(s)) to communicate with a locally accessible network device. The broker manager otherwise uses its messaging brokers to communicate with control channels of one or more networks. Once subscription with the network device has been established, any commands and responses between the client device and the network device may be routed over pub/sub channels via the broker managers and their brokers using name-based routing, without routing based on IP address of the network device.