1. Enhanced mobile services in Java 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. Java 2 Platform Mobile Information Device Profile (MIDP) Optional Packages Java 2 Micro Edition (J2ME) Core APIs Java 2 Enterprise Edition (J2EE) Core APIs JavaCard APIs JVMKVMCardVM Java 2 Standard Edition (J2SE) Core APIs Optional Packages Personal Profile PDA Profile Other CDC Profile Connected Device Configuration (CDC) Connected Limited Device Configuration (CLDC) Other CDLC Profile CVM Java Programming Language Foundation Profile

5. Java 2 Micro Edition Java Virtual Machine Host Operating System Configuration APIs Applications Profile APIs 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. Mobile Information Device Profile (MIDP) MIDP environment Resources JVM Java Application Manager MIDlet Network IO JAR & app-desc. RMS 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. Application distribution Java Application Manager Browser (Discovery Application) Origin ServerWAP GW (optional) 1 2 3 4

9. Proof of concept: Email client 123 456 789 BC Email menu Inbox [2 new] Folders Write new mail Options SelectExit Folder list Inbox [2 new] Sent Unsent SelectBack Inbox #121 Testing client #120 Another test mess… #119 This is a subject line : SelectBack Mail entry To: Cc: Message: SendBack 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 ReplyBack Communicating Abort Communicating Network not available… Send later? OKAbort Communicating Unsent message found. Send now? OK Abort Sending message.. Email Client OnlineOffline Options Connection: Timeout [sec]: 60 SelectBack Always ask When needed Offline Communicating Message(s) sent successfully! Continue A Communicating Connect to network? OK Abort

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