Delivery Contacts About Support

Mobile Internet Access

Common view In details Print
 
The m.WAP platform is a feature-rich system for cellular subscriber access to WAP/WEB Internet resources, providing:
  • support for WAP 1.x and 2.x;
  • high throughput;
  • easy scalability owing to its modular architecture;
  • optimization of data sent to the mobile terminal, depending on terminal characteristics (screen resolution, media file formats, etc.);
  • high fault-tolerance owing to the use of a performance monitoring and automatic recovery system;
  • static and dynamic routing of requests;
  • assurance of security and confidentiality through the use of WTLS, HTTPS, and SSL;
  • detailed recordkeeping;
  • a capability to be integrated with existing WAP platforms from other vendors.
     
     
m.WAP - WAP Gateway
 
 
WAP request handling:
  • servicing of terminals using WAP 1.x and WAP 2.x (m.Direct, m.Proxy);
  • consideration of mobile terminal capabilities for support of content types and WAP data size (m.CA);
  • compression (compilation) of WML and XML documents into binary form for transmission to a mobile terminal (m.Direct);
  • support for secure WTLS (m.Direct) and HTTPS (m.Proxy) protocols to assure the confidentiality of transmitted traffic;
  • conversion (masquerading) of internal IP addresses.
Platform load balancing and request routing (m.Router, m.W2Router):
  • configurable routing of WAP requests using arbitrary parameters (MSISDN, IP address, requested URL, etc.);
  • dynamic routing of requests between modules that are part of the platform and external WAP platforms in order to uniformly distribute them, with due regard for throughput and current load levels;
  • monitoring of platform module performance and automatic redirection of requests.
Subscriber connection monitoring and verification:
  • maintaining access logs for each URL, IP address, and MSISDN;
  • support for access lists that manage subscriber access privileges using configurable parameters (MSISDN, IP address of terminals and WAP resources, URL, etc.);
  • storage of WTP session information together with RADIUS accounting data (when the m.Radius RADIUS server or m.VRadius are used).
Monitoring platform status (m.Check):
  • monitoring platform module performance on the software level;
  • tracking the amount of through traffic on all network interface platforms;
  • remote monitoring of platform component status via a WEB/WAP interface;
  • automatic elimination of software-level faults;
  • remote restarting of platform components;
  • an SNMP/SNMP-trap interface for notification of external SNMP managers.
Collecting, storing, and processing statistics:
  • logs maintained by each platform module, configurable levels of detail and a list of recorded events for each log;
  • a centralized storage and processing system can be used for platform component statistics (m.Stat).
Interaction with billing systems (m.Charge):
  • generation of CDR billing entry files in a format that conforms to a specified description;
  • an interface to the Comverse Network Systems prepaid system.