Wireless Java Possibilities, Services, Limitations, and Competitors.Wireless Java
About this presentation l Show you what you can do with Java today, and tomorrow Overview of Wireless Java Why Java? Possibilities, limitations, and future expectations
What about wireless services? Market penetration of mobile Internet expected to reach 25% within 4 years (Forrester) Mobile Commerce in Europe alone is worth US $ 23 billion within 2003 (Durlacher)
What is Wireless Java? l Java on the terminal – J2ME/MIDP l Server-side Java creating content for a terminal
Java 2 Micro Edition JavaCardJ2ME CLDC J2EE Application Server Enterprise Services Standard Library J2SE JVM (HotSpot) JavaCard API JCRE CDC CLDC Core API CVM KVM PDA Profile Mobile Internet Device Other Profile Person Profile Foundatio n Profile Java Language
Example of MIDP applications MasterMindJava Fly ByReport SheetSnake Screenshots from Sun’s Wireless Toolkit
What can MIDP do? l Standard programming tasks Calculations, threads, string handling, etc. l Display UI and handle input Low-level (control pixel drawing, input events) High-level (forms, fields, etc) l Store data l Simple network usage (http) l Limited functionality: Easy to learn Screenshot of Nokia’s Wireless Java SDK
Usage scenario: Enterprise Applications Mobilize your workforce!
Usage scenario: Games
Why Java on the Terminal? l Unique possibilities Offline usage Client-intensive computations Complex graphics and animations l Find and develop added value propositions
Why Java? Availability and platform independence l The promise of platform independence is suddenly extremely valuable l The promise of network deployment is suddenly even more valuable l JCP: Process controlled by handset manufacturers l Availability: 2 pieces of good news, one piece of bad Image copyright Sarah Brodwall
Good news: 25 million Java Phones!
Bad news: million of these in Asia
Good news: More are coming l Sun is estimating million Java phones by the end of 2002 l Vendors are announcing more Java phones in 2 nd half of 2002 l From forum.nokia.com: “Nokia alone intends to deliver tens of millions of terminals with Java technology by the end of the year (2002).”
New Phones (
MIDP 1.0 Limitations Hard to make low-level GUI (games) – limited support for colors, transparent images High-level GUI only at about same level as WAP 1.1 l No standard for communicating with phone functionality Cannot handle incoming communication (server sockets or messages) Only recommendations for provisioning/deployment
MIDP 2.0 l JSR 118, led by Motorola l Release: Q3 2002? Phones: Q2 2003? l Adds Game UI classes (spites, layers), UI Media classes (can play files or streams) Security: Trusted MIDlets and HTTPS Push message reception OTA deployment is required l
Other interesting specs l JSR-75: PDA Profile (public review) l JSR-82: Bluetooth (final release March) l JSR-120: Wireless Messaging (final release Aug) l JSR-135: Mobile Media API (final release Jun) l JSR-139: CLDC 1.1 (public review) l JSR-172: J2ME Web Services (just started)
Competition l Browsing (WAP): Only applicable for some uses l Pocket PC/.NET Compact Framework/Wince: Targets high-end devices, enterprise apps. But more powerful than MIDP. l Symbian/Palm OS/BREW/Motorola MIX: Device-specific; may be harder to deploy. But more powerful than MIDP. Source: ESRI
MIDP: Conclusion l MIDP 1.0 will be available on many devices l MIDP offers device independence and code download l MIDP 1.0 has many limitations, MIDP 2.0 will address most l MIDP is easy to master
Server Side Wireless Applications Browsing (WAP)Messaging (SMS, MMS) Voice (VoiceXML)
Server side applications
Mobile Browser Overview Java 2 Enterprise Edition WAP Gateway 3. WML 4. Compiled WML 1. OTA Request 2. HTTP Request Simple for the content provider!
Mobile Browser Overview Source:
WAP’s Failure l Too little, too late l Too slow l Limited service potential (billing) l Expensive to use! l Heterogeneous devices
WAP’s Comeback l Faster networks (GPRS) l Cheaper networks (GPRS) l Faster phones/browsers l Better browsers l Third party “multi-channel” software l WAP is having a renaissance
Typical Browser Services: l Information services Online address-book News l Product/company presentation l m-Commerce l m-Banking l Application download
Messaging l SMS, MMS, and WAP Push l SMS-interfaces not standardized l SMS still successful l MMS is standardized Based on SMTP or HTTP for transport, SMIL for presentation l Modern terminals support WAP push
MMS architecture Java 2 Enterprise Edition MMS Gateway 1. SMIL over HTTP or SMTP 2. Notification over SMS 3. Request and response over WAP Simple for the content provider!
Messaging Services l Configuration messages, pictures, ring-tones (Browsing services are better for this, though) l Alerts! Weather, traffic, news, stocks, Surveillance alarms: Control systems, cameras, panic-buttons Service Announcements l Chatting Can be enhanced with images
Messaging – Surveillance Alarm
Messaging – Service Announcement
Voice: What is It? l Voice was first phone killer app! l Most systems today: IVRs Recorded messages DTMF keys l On the horizon: VoiceXML Adds: Text-to-speech, voice command Provides an easy interface for service provider Metaphor: Filling out forms
Voice Architecture J2EE Server HTTP/ VoiceXML Voice Voice Browser Simple for the content provider!
Voice Services l Can be used with regular phones, pay-phones, and mobile phones l Challenging to design good UI Imagine a two-level menu with 5*10 options Imagine call-center maze syndrome l May be very powerful and user friendly l Killer app: Yellow pages, ticket ordering, directions
VoiceXML FAQ l Yes, it is available now! l Yes, it works! l Yes, it is available in Norwegian!
Comparison l J2ME/MIDP Offline use, graphics, games l Browsing (WAP) Information search and viewing l Messaging User-to-user, alerts, news, service announcement l Voice Broad user base, appropriate end-user usage
Will Java Lead to a Breakthrough in Wireless Services? l Terminal: MIDP 1.0 (J2ME) l Server side: HTTP services (J2EE) l The data services marked will increase l Data services will become ubiquitous l Find the added value propositions! l Java is positioned for the present and the future