SYSTEMS AND METHODS FOR PROVIDING A RENAT COMMUNICATION ENVIRONMENT

Abstract

System for providing Redundant Network Address Translation (ReNAT) communication, which includes a Network Operations Center (NOC), wherein the NOC includes: a computing device comprising a processor and a memory for storing logic, and comprising at least the following: a first private network component that initiates communication with a private network; a ReNAT Twin Network Address Translation (NAT) coupled with the first private network component, wherein the ReNAT Twin NAT translates between a customer-assigned private Internet Protocol (IP) address and a Unique Private IP (UPIP) address, the UPIP overlapping with a customer-assigned private IP address space and the UPIP being unique in the NOC; a private ReNAT network component coupled with the ReNAT Twin NAT, wherein the private ReNAT network component provides a source IP address to the ReNAT Twin NAT; and a communication logic that enables the system to support communication with a workstation that has a ReNAT Twin NAT client, wherein the address translation is performed by the ReNAT Twin NAT client, wherein the ReNAT Twin NAT addresses in the data are mapped to customer-defined private addresses, and wherein the private ReNAT network component transmits the data to the private network.

Claims

[1] System for providing Redundant Network Address Translation (ReNAT) communication, which includes a Network Operations Center (NOC), wherein the NOC includes: a computing device comprising a processor and a memory for storing logic, and comprising at least the following: a first private network component that initiates communication with a private network; a ReNAT Twin Network Address Translation (NAT) coupled with the first private network component, wherein the ReNAT Twin NAT translates between a customer-assigned private Internet Protocol (IP) address and a Unique Private IP (UPIP) address, the UPIP overlapping with a customer-assigned private IP address space and the UPIP being unique in the NOC; a private ReNAT network component coupled with the ReNAT Twin NAT, wherein the private ReNAT network component provides a source IP address to the ReNAT Twin NAT; and a communication logic that enables the system to support communication with a workstation that has a ReNAT Twin NAT client, wherein the address translation is performed by the ReNAT Twin NAT client, wherein the ReNAT Twin NAT addresses in the data are mapped to customer-defined private addresses, and wherein the private ReNAT network component transmits the data to the private network. [2] System according to claim 1, further comprising the private network comprising a remote computing device and a gateway device. [3] System according to claim 1, wherein the logic further comprises a login manager which causes the system to provide a user login option for logging into the private network. [4] System according to claim 1, wherein the logic further comprises a plaintext component that manages IP addresses of a plurality of computing devices in a plurality of user organizations and ensures that each of the plurality of computing devices has a unique IP address. [5] System according to claim 1, further comprising a session manager which provides data for identifying a remote computing device with which communication is to be performed. [6] System according to claim 1, wherein the ReNAT Twin NAT client and the ReNAT Twin NAT are coordinated to translate between customer-assigned private IP addresses and ReNAT-assigned UPIP, such that the only IP addresses available for communication between the workstation and the private network that the workstation has are the respective internal private IP addresses. [7] Network Operations Center (NOC), which features: a computing device comprising a processor and a memory component that stores logic, and comprising at least the following: a ReNAT Twin Network Address Translation (NAT) that translates between a customer-assigned private Internet Protocol (IP) address and a Unique Private IP (UPIP) address, where the UPIP overlaps with a customer-assigned private IP address space that contains the customer-assigned private IP address, and where the UPIP is unique in the NOC; a Redundant Network Address Translation (ReNAT) private network component coupled with the ReNAT Twin NAT, wherein the ReNAT private network component provides a source IP address to the ReNAT Twin NAT; and A communication logic that enables the NOC to support communication between a workstation in a private network and a remote computing device, wherein address translation is performed by a ReNAT Twin NAT client at the workstation; wherein the ReNAT Twin NAT maps addresses in the data to customer-defined private addresses, and wherein the ReNAT private network component encrypts the data and transmits the data to the private network. [8] NOC according to claim 7, further comprising the private network comprising the remote computing device and a gateway device. [9] NOC according to claim 7, wherein the logic further comprises a login manager which causes the computing device to provide a user login option for logging into the private network. [10] NOC according to claim 7, wherein the logic further comprises a plaintext component that manages IP addresses of a plurality of computing devices in a plurality of user organizations and ensures that each of the plurality of computing devices has a unique IP address. [11] NOC according to claim 7, further comprising a session manager which provides data for identifying the remote computing device with which communication is to be performed. [12] NOC according to claim 7, wherein the ReNAT Twin NAT client and the ReNAT Twin NAT are coordinated to translate between customer-assigned private IP addresses and ReNAT-assigned UPIP, such that the only IP addresses available for communication between the workstation and the private network that the workstation has are the respective internal private IP addresses. [13] Non-volatile computer-readable medium storing logic which, when executed by a processor of a computing device, causes the computing device to perform at least the following: Initiating private network communication with a private network; Translation between a customer-assigned private Internet Protocol (IP) address and a Unique Private IP (UPIP) address, where the UPIP overlaps with a customer-assigned private IP address space and where the UPIP is unique in the NOC; Providing a source IP address for a Redundant Network Address Translation (ReNAT) Twin Network Address Translation (NAT); and Supporting communication with a workstation, where address translation was performed by a ReNAT Twin NAT client on the workstation; Mapping addresses in the data to customer-defined private addresses; and Transferring the data to the private network. [14] Non-volatile computer-readable medium according to claim 13, further comprising a login manager which causes the computing device to provide a user login option for logging into the private network. [15] Non-volatile computer-readable medium according to claim 13, further comprising a plaintext component that manages IP addresses of a plurality of computing devices in a plurality of user organizations and ensures that each of the plurality of computing devices has a unique IP address. [16] Non-volatile computer-readable medium according to claim 13, further comprising a session manager which provides data for identifying a remote computing device with which communication is to be performed. [17] Non-volatile computer-readable medium according to claim 13, wherein the ReNAT Twin NAT client and the ReNAT Twin NAT are coordinated to translate between customer-assigned private IP addresses and ReNAT-assigned UPIP, such that the only IP addresses available for communication between the workstation and the private network that the workstation has are the respective internal private IP addresses. [18] Methods for providing Redundant Network Address Translation (ReNAT) communication, comprising: Initiating, through a computing device, a connection to a private network; Translation, by the computing device, between a customer-assigned private Internet Protocol (IP) address and a Unique Private IP (UPIP) address, wherein the UPIP overlaps with a customer-assigned private IP address space and wherein the UPIP is unique in a Network Operations Center (NOC) where the UPIP is used; Supporting, through the computing device, the communication between the computing device, which has a ReNAT Twin NAT client, and the private network, wherein the address translation was performed by the ReNAT Twin NAT client; Mapping addresses in the data to customer-defined IP addresses; and Transferring the data to the private network. [19] The method of claim 18, further comprising the translation, by the computing device, between the customer-assigned private IP address and the ReNAT-assigned UPIP, such that the only IP addresses available for communication between the computing device and the private network that the computing device has are respective internal private IP addresses. [20] The method of claim 18, further comprising managing, by the computing device, the IP addresses of a plurality of different computing devices in a plurality of user organizations and ensuring that each of the plurality of different computing devices has a unique IP address.