Enhanced mobile services in Java enabled phones

1. Enhanced mobile services inJava enabled phones Björn Hjelt Sonera zed ltd Supervisor: Professor Jorma Jormakka

2. Table of Contents • Background • Java 2 Micro Edition • Mobile Information Device Profile • Technology limitations • Project implementation • Conclusions

3. Background • Java enabled handsets • Nokia: 50 milj. in 2002 100 milj. in 2003 • Enhancing currently available services should be possible using Java technology available in clients! – How? • Gartner: Java will enhance or replace WAP in 90% of mobile services with complex user interfaces.

4. Optional Packages Java 2 Enterprise Edition (J2EE) Core APIs Optional Packages Java 2 Standard Edition (J2SE) Core APIs Personal Profile Other CDC Profile Mobile Information Device Profile (MIDP) PDA Profile Other CDLC Profile Foundation Profile Connected Device Configuration (CDC) Connected Limited Device Configuration (CLDC) JavaCard APIs Java 2 Micro Edition (J2ME) Core APIs Java Programming Language JVM CVM KVM CardVM Java 2 Platform

5. Applications Profile APIs Configuration APIs Java Virtual Machine Host Operating System Java 2 Micro Edition • Configurations • Core runtime environment for a broad device category. • APIs and a specialized Java Virtual Machine • Profiles • Additional APIs for a particular family of consumer devices

6. MIDP environment Java Application Manager MIDlet JVM Resources RMS JAR & app-desc. Network IO Mobile Information Device Profile (MIDP) • Profile for mobile phones and other small wireless devices. • Based on the J2ME Connected Limited Device Configuration • Persistent storage • Two-way, wireless networking • Required protocol: HTTP • Minimum screen size 96x54 (B/W) • Minimum memory capacity 168 KB • 128 KB of ROM/flash • 8 KB persistent storage • 32 KB for Java runtime

7. MIDP Limitations • Device limitations • Memory • Processor • Display and input • Implementation bugs(?) • MIDP security related limitations • Applications can share resources only within same application package (“MIDlet suite”) • Only restricted access to resources available • Device specific resources may be accessible through OEM libraries.

8. Java Application Manager Browser (Discovery Application) WAP GW (optional) Origin Server 1 2 3 4 Application distribution

9. 1 2 3 4 5 6 Always ask When needed Mail entry To: < > Cc: < > Message: <text entry> Email menu Inbox [2 new] Folders Write new mail Options Communicating Message(s) sent successfully! Email Client Communicating Network not available… Send later? Communicating Unsent message found. Send now? Communicating Options Connection: Timeout [sec]: 60 Inbox #121 Testing client #120 Another test mess… #119 This is a subject line : : Mail view From: bh@iki.fi To: bjorn.hjelt@iki.fi Subject: Testing client This is a message to test the MIDP mail client and Folder list Inbox [2 new] Sent Unsent Offline Exit Abort Back Offline Back Back Abort Back Back Select OK Select Send Continue Select Reply Online OK Select Abort 7 8 9 Sending message.. Communicating Connect to network? A B C Abort OK Proof of concept: Email client

10. Conclusions (1) • Services can be improved using Java • Off-line operation • Improved network utilization • More interactive user interface • MIDP brings mobile phones nearer to PDA functionality. • Wireless distribution of applications easy. • Methods still heterogeneous.

11. Conclusions (2) • Important to keep limitations in mind while developing. • Devices are limited: Optimization required. • Device implementations are not ready yet. • Platform independence promising • Even OEM features can be implemented without breaking platform independence • Look and feel device implementation dependent

13. Thank you! Bjorn.Hjelt@sonera.com