Performance of Mobile Web Services using WAP

Internet has helped man a lot in a variety of fields using the web-pages. We need to have an access to a computer in-order to use the internet, but this is not possible every time.
Then comes the generation of mobile phones, which were easy to carry, portable and secured. Implementing the concept of Internet and Web Pages in mobiles is actually the core of this paper.
Web pages offer the user an accessible interface using a web browser (Internet Explorer, Firefox, Opera, etc.). Presently there are web pages which are user interface independent.
Due to the hardware and bandwidth limitations such as slow CPU’s, small memories, small displays, cell phones (mobiles) which have an access to internet cannot support all the web pages. Any cell phone has to be G. P. R. S. enabled for it to get an access to the internet through its service provider and it has to be W. A. P. enabled too.
G. P. R. S. → General Packet Radio Service.
W. A. P.→ Wireless Application Protocol.
Integrating web services into mobile devices has major restrictions. Mobile communication systems like the G. P. R. S. and U. M. T. S. , imply limited bandwidth and high latency.
“This paper aims at presenting an alternative solution to access web services from mobile clients using W. A. P., as well as a performance analysis of this solution compared to access visa HTTP from java capable mobiles.”

Mobile Web Services:-
The dependencies of the different technologies used by Web Services are depicted to each other as shown in the figure above using the U. M. L. notation.
To access web services from a mobile phone, a SOAP implementation and a transport implementation are necessary. For this reason, java applications are used because most of the cell phones support JVM. “Currently, two SOAP client implementations for J2ME capable devices are known, Wingfoot SOAP and kSOAP.”
The HTTP and the TCP are not ideal solutions for mobile devices. Hence the Wireless Session Protocol has been developed and is being used.

WAP Transport Implementation :-
The WAP implementation has been mainly split into three parts:
The lower level constructs and determines the octet stream for encoded P. D. U.’s and vice versa. The layer above this sends and receives P. D. U’s to and from the network using U. D. P. packets. The top level conveys SOAP data from the application to the web service and vice versa.
Performance Analysis :-
The factors that affect the performance of a mobile application are mainly the CPU power and main memory with the network of the service provider.
In this context the performance criteria are latency, data transfer volume, memory footprint and CPU power requirements.
Conclusion :-
The performance of the mobile applications is still a main criterion and is still to be improved. The latency and CPU power are a major consideration.