Remote Application Access provides access to web servers (applications) with dynamic IP addresses. The normal situation exists in the case of corporate web servers with static IP addresses. In this case the static IP address is associated with a URL. The fact that the web server is at a static address allows the URL or even the IP address to be published and reliably used for access.

It is becoming more common for individuals and small businesses to run applications that exist as small web servers within a local area network. Web cameras are an example of such an application, to access the camera the user surfs to an an address on the LAN. Most home automation and many small business applications operate in the same way.

These applications are not generally accessible from a remote location for two reasons; (1) the home or small business network operates with a dynamic IP address from the broadband service provider, and (2) the application exists on a device that is behind a NAT router. There are significant economic and practical difficulties in overcoming these problems. Fixed IP addresses, when available from the broadband service provider, are often expensive. Managing the port forwarding rules in a NAT router with standad issue tools is beyond the interest and/or expertise of most people.

Remote Application Access offers a convenient solution. Part of the solution resides in the CPE (gateway) and part in a server operated by the service provider.

Remote Application Access is installed in the CPE (gateway) to register the public IP address of the CPE with the server component on startup and then every time a change of public IP address occurs. This component also sets port forwarding rules in response to simple pull-down menu selections made by the end user.

The part of Remote Application Access installed in the service provider's server maintains a register of the last known public IP address of each CPE (gateway). Users access the remote application by: (1) surfing to the server using a well known URL, at this point a userid and password can be required; (2) identifying the target network; (3) identifying the target application; (4) being transferred to the target application.

The target network is identified using the name recognized by the service provider, usually the formal name of the CPE an arbitrary username linked to the formal name.