Application: The Basic Application

External
Router

External
B5
DNS Server
80.96.151.0

Zapp Mobile Portal

Internal
Router
B4 Internet

A3 w w w .zappmobile.ro Firew all

172.16.x.0 performing
B3
NAT

A1

1
ns.zappmobile.ro

2
A2 Internal DNS
IWF Server

Mobile Client

1 Mobile Client initiates a Dial-up Netw orking Connection w ith ZappNet

2 IWF provides the Mobile Client w ith a Dynamic IP Address from a Private Pool of IP Addresses (e.g. 172.16.x.y)
and w ith the (static) IP Address of ZappNet DNS Server

Mobile Client w ants to access the Zapp Mobile Portal and, therefore, is pointing the brow ser to w w w .zappmobile.ro

A1 w w w .zappmobile.ro is sent by the Mobile Client to the DNS Server for address resolution
A2 DNS Server resolves the request and sends back to the Mobile Client the corresponding IP Address
A3 Mobile Client is using the IP Address provided by the DNS Server in order to make the desired contact directly

Mobile Client w ants to access an Internet resource (e.g. Yahoo!) and is pointing the brow ser correspondingly (e.g.
w w w .yahoo.com)

B1 w w w .yahoo.com is sent by the Mobile Client to the DNS Server for address resolution
B2 DNS Server resolves the request and sends back to the Mobile Client the corresponding IP Address
B3 Mobile Client is using the IP Address provided by the DNS Server and sends it to the Internal Router for
appropriate routing
B4 Internal Router recognizes the destination as being non-local and sends it through the Firew all to an External
Router for appropriate Internet Routing.
B5 Firew all is translating the Private IP Address of the Mobile Client (e.g. 172.16.x.y) into a Public IP Address (e.g.
80.96.151.z). This process is called NAT (Netw ork Address Translation) and is performed in order to be able to
send / receive information to / from the Internet.
Application: Dynamic DNS for Workgroups
Note: Mobile Clients must run a DDNS Client Application in the background in order to register themselves into the
DDNS Server
External
Router

External
DNS Server
80.96.151.0

Zapp Mobile Portal

Internal
Router
Internet

w w w .zappmobile.ro Firew all

172.16.x.0 performing
NAT
3

Mobile Client dyn.zappmobile.ro ns.zappmobile.ro

1
running DDNS A2
Client
Application
2 IWF
3 A3
A1 Internal
Internal
DDNS DNS
1
Server Server
breeze.dyn.zappmobile.ro 2
A4

A5

Mobile Client
running DDNS
air.dyn.zappmobile.ro Client
Application

1 Mobile Clients initiate a Dial-up Netw orking Connection w ith ZappNet

2 IWF provides the Mobile Clients w ith Dynamic IP Addresses from a Private Pool of IP Addresses (e.g. 172.16.x.y)
and w ith the (static) IP Address of ZappNet DNS Server
3 DDNS Client Applications running on the Mobile Clients inform the DDNS Server that the fixed names registered
previously (e.g. air.dyn.zappmobile.ro and breeze.dyn.zappmobile.ro) w ith ZappNet Administration are now linked
to the Dynamic IP Addresses just received

Mobile Client air.dyn.zappmobile.ro w ants to access Mobile Client breeze.dyn.zappmobile.ro

A1 breeze.dyn.zappmobile.ro is sent by the Mobile Client to the DNS Server for address resolution
A2 DNS Server delegates the task to the DDNS Server as dyn.zappmobile.ro is under its jurisdiction
A3 DDNS solves the query and sends the response back to the DNS Server
A4 In turn, DNS Server sends back to the Mobile Client the corresponding IP Address

A5 Mobile Client is using the IP Address provided by the DNS Server in order to make the desired contact directly
Application: VPN over CDMA
Notes: VPN Server must maintain a quasi-permanent connection w ith ZappNet in order to be available at all times
VPN Server must run a DDNS Client Application in the background in order to register itself into the DDNS Server
External
Router

External
DNS Server
80.96.151.0

Zapp Mobile Portal

Internal
Router
Internet

w w w .zappmobile.ro Firew all

172.16.x.0 performing
NAT
3

‘Mobile’ VPN dyn.zappmobile.ro ns.zappmobile.ro

1
Server running A2
DDNS Client
Application
2 IWF
A3
A1 Internal
Internal
DDNS DNS
1
Server Server
earth.dyn.zappmobile.ro
2
A4

A5 Mobile Client

1 Mobile Client / Server initiates a Dial-up Netw orking Connection w ith ZappNet
2 IWF provides the Mobile Client / Server w ith a Dynamic IP Address from a Private Pool of IP Addresses (e.g.
172.16.x.y) and w ith the (static) IP Address of ZappNet DNS Server
3 DDNS Client Application running on the 'Mobile' VPN Server informs the DDNS Server that the fixed name
registered previously (e.g. earth.dyn.zappmobile.ro) w ith ZappNet Administration is now linked to the Dynamic IP
Address just received

Mobile Client w ants to access the Mobile Server w ater.dyn.zappmobile.ro

A1 w ater.dyn.zappmobile.ro is sent by the Mobile Client to the DNS Server for address resolution
A2 DNS Server delegates the task to the DDNS Server as dyn.zappmobile.ro is under its jurisdiction
A3 DDNS solves the query and sends the response back to the DNS Server
A4 In turn, DNS Server sends back to the Mobile Client the corresponding IP Address

A5 w ater.dyn.zappmobile.ro is finally reached and, after proper authentication, the Mobile Client is tunneled into
the Server. Subsequent traffic betw een the Mobile Client and the Server is encrypted.
 Application: VPN over Internet
External
Router

External 7
DNS Server
80.96.151.0

Zapp Mobile Portal

Internal
Router
6 Internet
8

vpn.company.ro
w w w .zappmobile.ro Firew all
5 172.16.x.0 performing
NAT Client
Internet VPN
3
Server
1 ns.zappmobile.ro

2
Internal DNS Client Company
4 IWF Server LAN

Mobile Client

VPN Tunnel 8

1 Mobile Client initiates a Dial-up Netw orking Connection w ith ZappNet

2 IWF provides the Mobile Client w ith a Dynamic IP Address from a Private Pool of IP Addresses (e.g. 172.16.x.y)
and w ith the (static) IP Address of ZappNet DNS Server

Mobile Client w ants to access his company LAN and therefore initiates a connection w ith the company VPN
Server (e.g. vpn.company.ro) located on the Internet

3 vpn.company.ro is sent by the Mobile Client to the DNS Server for address resolution
4 DNS Server resolves the request and sends back to the Mobile Client the corresponding IP Address

5 Mobile Client is using the IP Address provided by the DNS Server and sends it to the Internal Router for
appropriate routing
6 Internal Router recognizes the destination as being non-local and sends it through the Firew all to an External
Router for appropriate Internet Routing.
7 Firew all is translating the Private IP Address of the Mobile Client (e.g. 172.16.x.y) into a Public IP Address (e.g.
80.96.151.z). This process is called NAT (Netw ork Address Translation) and is performed in order to be able to
send / receive information to / from the Internet.
8 vpn.company.ro is finally reached and, after proper authentication, the Mobile Client is tunneled into his
company LAN. Subsequent traffic betw een the Mobile Client and the company LAN is encrypted.
Application: ZappVPN for Workgroups
Notes: VPN Services are offered by Zapp Mobile to w orkgroups of subscribers as a Value Added Service
External
A Chat Server should be immediately available to the VPN Users. Connected Router
users w ill automatically show up in each others lists

External
DNS Server
80.96.151.0

Zapp Mobile Portal

Internal
Router
Internet

w w w .zappmobile.ro Firew all

3 performing
172.16.x.0
NAT
5
3
vpn.zappmobile.ro ns.zappmobile.ro
1

2 IWF
Mobile Client 5 Internal
4 DNS
1 Zapp VPN Server
Concentrator
2

VPN Tunnel
Mobile Client

1 Mobile Clients initiate a Dial-up Netw orking Connection w ith ZappNet

2 IWF provides the Mobile Clients w ith a Dynamic IP Addresses from a Private Pool of IP Addresses (e.g.
172.16.x.y) and w ith the (static) IP Address of ZappNet DNS Server

Mobile Clients w ant to communicate securely amongst themselves, therefore they initiate a connection w ith the
Zapp VPN Concentrator (e.g. vpn.zappmobile.ro)

3 vpn.zappmobile.ro is sent by the Mobile Clients to the DNS Server for address resolution
4 DNS Server resolves the request and sends back to the Mobile Clients the corresponding IP Address

5 Mobile Clients are using the IP Address provided by the DNS Server in order to make the desired contact directly
6 vpn.zappmobile.ro is finally reached and, after proper authentication, the Mobile Clients are tunneled togheter.
Subsequent traffic betw een the Mobile Clients is encrypted.
Application: Professional ZappVPN for Small Offices
Notes: VPN Services are offered by Zapp Mobile to Small Offices as a Value Added Service External
Small Offices must maintain a quasi-permanent connection w ith ZappNet in Router
order to be available at all times

External
DNS Server
80.96.151.0

Zapp Mobile Portal

Internal
Router
Internet

w w w .zappmobile.ro Firew all

172.16.x.0 performing
NAT
Small Office
3

vpn.zappmobile.ro ns.zappmobile.ro
1

2 IWF
3 Internal
DNS
1 Zapp VPN Server
Concentrator
‘Mobile’ Router 2

Small Office
3

VPN Tunnel
‘Mobile’ Router

1 ‘Mobile’ Routers initiate a Dial-up Netw orking Connection w ith ZappNet

2 IWF provides the ‘Mobile’ Routers w ith Dynamic IP Addresses from a Private Pool of IP Addresses (e.g.
172.16.x.y)

‘Mobile’ Routers w ant to communicate securely amongst themselves, therefore they initiate a connection w ith the
Zapp VPN Concentrator (e.g. 172.16.11.254)

3 After proper authentication, the ‘Mobile’ Routers are tunneled togheter. Subsequent traffic among the ‘Mobile
Routers’ (including the LANs behind) is encrypted.
Application: Professional VPN over CDMA
Note: Solution available for Business Partners / Major Accounts only: Revenue equal or greater than
10,000 USD per month
External
Router

External
DNS Server
80.96.151.0

Zapp Mobile Portal

Internal
Router
Internet

Client Company
LAN
w w w .zappmobile.ro Firew all
performing
172.16.x.0
NAT

3 ns.zappmobile.ro
Client VPN
Server
Dedicated High
IWF
Speed Link
company.vpn.zappmobile.ro InternalD
1 NS
Server
2 4

6 5
VPN Tunnel
Mobile Client

1 Mobile Client initiates a Dial-up Netw orking Connection w ith ZappNet

2 IWF provides the Mobile Client w ith a Dynamic IP Address from a Private Pool of IP Addresses (e.g. 172.16.x.y)
and w ith the (static) IP Address of ZappNet DNS Server

Mobile Client w ants to access his company LAN and therefore initiates a connection w ith the company VPN
Server (e.g. company.vpn.zappmobile.ro) linked by a dedicated link to ZappNet

3 company.vpn.zappmobile.ro is sent by the Mobile Client to the DNS Server for address resolution
4 DNS Server resolves the request and sends back to the Mobile Client the corresponding IP Address

5 Mobile Client is using the IP Address provided by the DNS Server in order to make the desired contact directly
6 company.vpn.zappmobile.ro is finally reached and, after proper authentication, the Mobile Client is tunneled into
his company LAN. Subsequent traffic betw een the Mobile Client and the company LAN is encrypted.
Application: ZappMax - Ultimate Performance and Security
Note: Solution available for Key Accounts only: Revenue equal or greater than 25,000 USD per month

Zapp RBS Site

(nearby A)
n x 64 Kbps
Router
RF
or
Terrestrial

Last Mile Access Drop-Insert

Solution to nearest
Client LAN Zapp RBS Site

Client Site A

Zapp RF
Backbone

n x 64 Kbps
Router
RF
or
Terrestrial

Drop-Insert Last Mile Access

Solution to nearest
Zapp RBS Site Client LAN

Zapp RBS Site Client Site B

(nearby B)