Address Mapping Engine for Inter-Network Communication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network communication technologies face challenges in securely enabling inter-network communication between incompatible private networks, particularly due to differences in addressing formats and protocols, which limits compatibility and security.
Innovation Solution
An address mapping system that uses an address mapping engine and gateway to translate between native addresses and system addresses, incorporating a reference value to facilitate communication across different networks, allowing for secure inter-network communication without the need for dedicated VPNs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a tunnel such as VPN is used to enable inter-network communication between private networks, then communication capability is improved, but device complexity and security management become worsened
Solution Approach 1:
The patent introduces an address mapping system as an intermediary component that sits between private networks and the public network. This system includes an address mapping engine that automatically translates private addresses to public addresses and maintains mapping tables, eliminating the need for complex VPN tunnel configurations while enabling seamless inter-network communication.
Solution Approach 2:
The address mapping system performs automatic address translation and mapping without requiring manual VPN configuration by users. The system self-manages the translation process by intercepting packets, looking up address mappings in its tables, and automatically replacing private addresses with public addresses, thereby simplifying the communication setup.
2Reliability
If native addresses are kept secretive within private networks for security, then security is improved, but address translation and inter-network communication become worsened
Solution Approach 1:
The address mapping system acts as a secure intermediary that handles all address translation operations. Private addresses remain concealed within the private network while the mapping engine externally translates them to public addresses for inter-network communication, maintaining security while enabling translation through the intermediary component.
Solution Approach 2:
The system segments the address translation function into a dedicated address mapping engine separate from the private network hosts. This segmentation allows the translation logic to be centralized and managed independently, reducing the complexity burden on individual hosts while maintaining security through the dedicated mapping component.
3Adaptability or versatility
If address mapping is implemented to translate between private and public addresses, then compatibility is improved, but processing overhead and time delay become worsened
Solution Approach 1:
The address mapping system performs preliminary actions by pre-establishing and maintaining address mapping tables that contain translation mappings between private and public addresses. When packets need translation, the system quickly looks up pre-computed mappings in these tables, significantly reducing the time delay compared to calculating translations in real-time.
Solution Approach 2:
The system uses copying by maintaining cached copies of address mappings in its translation tables. Instead of performing complex translation calculations for each packet, the system copies and reuses established mappings from its tables, thereby reducing processing overhead and time delay while maintaining compatibility.
Data Source
AI summary
Devices residing in different networks communicate with one another using inter-network communication. A host may transmit a first packet to a gateway and the gateway may transform it into a second packet. When creating the second packet, the gateway may transmit a request to an address mapper for a mapped address. The mapped address includes a native address or a system address. The system address includes another native address as well as a reference value. The reference value is associated with the host, includes an opaque binary value of an arbitrary size, and is subdivided into multiple fields associated with the host. In response to the mapped address being the system address, the address mapping engine obtains the system address. In response to the mapped address being the native address, the address mapping engine obtains the native address. The native address is determined in view of an existing network protocol.


