Motorola E680 Technical Manual - Page 12

The Motorola J2ME Platform, Resources and API's Available

Get Motorola E680 - Smartphone - GSM PDF manuals and user guides View all Motorola E680 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 12 highlights

The Configuration Layer used in the Motorola E680 handset is the Connected Limited Device Configuration 1.1 (CLDC 1.1) and the Profile Layer used is the Mobile Information Device Profile 2.0 (MIDP 2.0). Together, the CLDC and MIDP provide common APIs for I/O, simple math functionality, UI, and more. For more information on J2ME, see the Sun™ J2ME documentation (http://java.sun.com/j2me/). The Motorola J2ME Platform Functionality not covered by the CLDC and MIDP APIs is left for individual OEMs to implement and support. By adding to the standard APIs, manufacturers can allow developers to access and take advantage of the unique functionality of their handsets. The Motorola E680 handset contain OEM APIs for extended functionality ranging from enhanced UI to advanced data security. While the Motorola E680 handset can run any application written in standard MIDP, it can also run applications that take advantage of the unique functionality provided by these APIs. These OEM APIs are described in this guide. Resources and API's Available MIDP 2.0 will provide support to the following functional areas on the Motorola E680 handset: MIDP 2.0 • Application delivery and billing • Application lifecycle • Application signing model and privileged security model • End-to-end transactional security (HTTPS) • MIDlet push registration (server push model) • Networking • Persistent storage • Sounds • Timers • User Interface • File Image Support (.PNG, .JPEG, .GIF) 12

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
12
The Configuration Layer used in the Motorola E680 handset is the Connected Limited
Device Configuration 1.1 (CLDC 1.1) and the Profile Layer used is the Mobile Information
Device Profile 2.0 (MIDP 2.0).
Together, the CLDC and MIDP provide common APIs for
I/O, simple math functionality, UI, and more.
For more information on J2ME, see the Sun™ J2ME documentation
(
).
The Motorola J2ME Platform
Functionality not covered by the CLDC and MIDP APIs is left for individual OEMs to
implement and support.
By adding to the standard APIs, manufacturers can allow
developers to access and take advantage of the unique functionality of their handsets.
The Motorola E680 handset contain OEM APIs for extended functionality ranging from
enhanced UI to advanced data security.
While the Motorola E680 handset can run any
application written in standard MIDP, it can also run applications that take advantage of
the unique functionality provided by these APIs. These OEM APIs are described in this
guide.
Resources and API’s Available
MIDP 2.0 will provide support to the following functional areas on the Motorola E680
handset:
MIDP 2.0
•
Application delivery and billing
•
Application lifecycle
•
Application signing model and privileged security model
•
End-to-end transactional security (HTTPS)
•
MIDlet push registration (server push model)
•
Networking
•
Persistent storage
•
Sounds
•
Timers
•
User Interface
•
File Image Support (.PNG, .JPEG, .GIF)