Ericsson launches its Enterprise WAP Gateway/Proxy 2.0, a new version of its WAP Gateway for enterprise users. The new system supports the WAP June 2000 standard, providing easier service set-up and faster access to corporate information.
Enterprise WAP Gateway/Proxy 2.0 is the first WAP gateway for enterprise customers, which is compliant with the WAP June 2000 standard. It supports push technology and user agent profiling functionality, and runs on any Windows 2000 hardware platform, making it quick and easy to install.
"Enterprise WAP Gateway/Proxy 2.0 further strengthens Ericsson's Mobile Internet portfolio, which supports our customers and end-users in the emerging Mobile Internet market," said Staffan Pehrson, General Manager Mobile Internet Enablers. "It uses our proven WAP technology, already installed at 70 operators, to provide a secure and reliable solution for mobile businesses worldwide."
The simple installation and scalability of Enterprise WAP Gateway/Proxy 2.0 makes it suitable for enterprises wanting to offer WAP services in- house independent of network operators. It is also suitable for financial institutions that need a reliable gateway through which to offer secure services to customers, and for companies who want to give employees protected access to their intranet.
By using a WAP gateway within a corporate network, a secure end-to-end connection is established from a user's WAP phone directly to information on the company intranet. With this new version, users can get instant access to information from the intranet through new functionality that "pushes" data to the user.
The client configuration functionality included in Enterprise WAP Gateway/Proxy is based on a de-facto standard called OTA. The WAP Gateway automatically transmits an SMS to a new user's handset, detailing set-up information including IP addresses, relevant passwords and bookmarks. In this way, it is easy to set up new users and using WAP services are faster and more user friendly.
[ Home | Contact | MobiChat | Experts database | Let's do it ]
Comments to the content of this page can be posted on the MobiChat discussion group