Remote Hosting Network Architecture Without NAT
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The complexity in managing networks for remote hosting is increased due to overlapping local subnet addresses, requiring the use of Network Address Translation (NAT) devices, which adds management burdens and costs.
Innovation Solution
Implementing a system that uses multipoint Generic Routing Encapsulation (mGRE) protocol, dynamic multipoint virtual private network (DMVPN) technology, and policy-based routing (PBR) in combination with service level agreement (SLA) tracking to support remote hosting without relying on NAT, by establishing redundant tunnel end points and selecting optimal routes for data traffic.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If NAT devices are used to support communication between hub and spoke sites with overlapping local subnet addresses, then communication compatibility is improved, but device complexity and management burden increase
Solution Approach 1:
The patent extracts and removes the NAT device from the network architecture by implementing direct routing between hub and spoke sites. The overlapping subnet addresses are resolved through careful route configuration and policy-based routing that allows direct communication without requiring NAT translation, thereby eliminating the complexity and management burden of NAT devices while maintaining communication compatibility.
Solution Approach 2:
The patent introduces a tunneling mechanism as an intermediary layer between hub and spoke sites. By encapsulating traffic in tunnels with unique routing identifiers, the system mediates communication between sites with overlapping subnets, allowing direct connectivity without NAT while resolving address conflicts through the tunneling layer.
2Reliability
If NAT devices are deployed to enable spoke site communication, then network connectivity is improved, but the number of computing devices and infrastructure costs increase
Solution Approach 1:
The patent removes NAT devices from the network architecture by implementing direct routing between hub and spoke sites. Through careful route configuration and policy-based routing, the system enables communication without requiring NAT translation, thereby reducing the number of computing devices needed while maintaining network connectivity.
Solution Approach 2:
The patent combines multiple functions into the existing router infrastructure. Instead of adding separate NAT devices, the routing and address resolution functions are integrated directly into the router's routing table and policy-based routing capabilities, eliminating the need for additional computing devices while maintaining connectivity.
3Reliability
If redundant tunnel end points are implemented with mGRE and DMVPN, then reliability is improved, but device complexity increases
Solution Approach 1:
The patent configures multiple tunnel end points in advance as redundant paths before failures occur. By pre-establishing backup tunnels and configuring failover policies, the system ensures automatic switching to redundant paths when primary tunnels fail, improving reliability while using policy-based routing to manage the complexity of multiple tunnel configurations.
Solution Approach 2:
The patent implements monitoring and tracking mechanisms that provide feedback on tunnel status and performance. This feedback enables automatic selection of optimal tunnel end points based on current network conditions, reliability metrics, and policy requirements, managing the complexity of redundant tunnel configurations through intelligent automated selection rather than manual management.
Data Source
AI summary
Methods, apparatuses, and computer program products are provided for supporting remote hosting without using network address translation. A method may include supporting, at a hub, a plurality of redundant tunnel end points for each of a plurality of spokes using a technology based at least in part on multipoint generic routing encapsulation protocol. The method may further include using policy based routing to determine a destination spoke for outgoing data traffic. The method may additionally include using service level agreement tracking to select a tunnel end point from the plurality of redundant tunnel end points for the determined destination spoke. The method may also include causing the outgoing data traffic to be routed to the determined destination spoke via the selected tunnel end point. Corresponding systems, apparatuses and computer program products are also provided.