Download Enhanced mobile services in Java enabled phones

Enhanced mobile services in
Java enabled phones
Björn Hjelt
Sonera zed ltd
Supervisor: Professor Jorma Jormakka
Table of Contents
•
•
•
•
•
•
Background
Java 2 Micro Edition
Mobile Information Device Profile
Technology limitations
Project implementation
Conclusions
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.
Java 2 Platform
Optional
Packages
Optional
Packages
Personal
Profile
Java 2
Enterprise
Edition
(J2EE)
Core APIs
Java 2
Standard
Edition
(J2SE)
Core APIs
Other
CDC
Profile
Foundation
Profile
Connected Device
Configuration (CDC)
Mobile
Information
Device Profile
(MIDP)
PDA
Profile
Other
CDLC
Profile
Connected Limited Device
Configuration (CLDC)
Java 2 Micro Edition (J2ME) Core APIs
JavaCard
APIs
Java Programming Language
JVM
CVM
KVM
CardVM
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
Applications
Profile APIs
Configuration APIs
Java Virtual Machine
Host Operating System
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
MIDP environment
Java
Application
Manager
JVM
– 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
MIDlet
Resources
RMS
JAR &
app-desc.
Network
IO
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.
Application distribution
Java
Application
Manager
Browser
(Discovery
Application)
1
2
3
4
WAP GW
(optional)
Origin Server
Proof of concept: Email client
Folder list
1
Inbox [2 new]
Sent
Unsent
Back
Inbox
2
#121 Testing client
#120 Another test mess…
#119 This is a subject line
:
:
Select
4
Back
Select
Email menu
5
Inbox [2 new]
Folders
Write new mail
Options
Email Client
Offline Online
Options
7
Exit
Select
Communicating 8
Connection:
Always ask
When needed
Offline
Sending message..
Mail view
3
From: [email protected]
To: [email protected]
Subject: Testing client
This is a message to test
the MIDP mail client and
Back
Reply
Mail entry
6
To: < >
Cc: < >
Message:
<text entry>
Back
Send
Communicating 9
Network not
available…
Send later?
Timeout [sec]: 60
Back
Select
Communicating A
Connect to
network?
Abort
OK
Abort
Communicating B
Unsent message
found. Send now?
Abort
OK
Abort
OK
Communicating C
Message(s) sent
successfully!
Continue
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.
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
Thank you!
[email protected]