![]() | |||||||||||
|
Architecture Managing Mobile Code August 23, 1999 A variety of networks are available for mobile communications. But which communications architectures that make the most sense? There are two fundamental ones to look at. One we call a traditional communications architecture. The other we refer to as a mobile communications architecture, an architecture more well-suited for handheld computers and wireless networks.
Traditional Communications Architecture
![]() Figure 7: Traditional communications using wireline modems.
Mobile Communications Architecture
![]() Figure 8: Mobile communications using a wireless network. The gateway can perform a variety of functions. One is to use protocols optimized for wireless networks, such as WAP, to communicate with mobile devices, while using standard networking protocols to communicate with back-end services. Another is to format information for the smaller screen sizes of a mobile device. An interesting question is about the location of the gateway because there are a number of possibilities. In some cases, the wireless carrier themselves will operate the gateway. This is the case today for AT&T's smartphone, the PocketNet. Alternatively, an organization could deploy their own gateway as part of a wireless-middleware solution. Finally, there are third-party organizations beginning to specialize in this kind of service. See the Services section for a list of such providers. Note that there are security implications of this new architecture. Since the gateway acts as a proxy for the mobile user, the corporate network may need to authenticate the gateway in addition to the mobile system. In certain instances the gateway will communicate with corporate systems across the Internet, in which case, secure tunnels using VPN protocols may need to be employed.
| |||||||||||
|
PAGE: 1 I 2 I 3 I 4 I 5 I 6 I NEXT PAGE |
|||||||||||














