|
| Session Details | |
| |
|
| |
|
| With its two editions, Classic and Connected, it's suited for all smart cards: legacy to high-end multimedia products. This session looks beyond this to envision how Java Card 3 technology can be used in the embedded systems area. The session compares this technology with existing Java™ Platform, Micro Edition (Java ME platform) technologies (CLDC, MIDp, IMP, Squawk) and embedded Linux solutions in terms of footprint, CPU requirements, execution, and application models. Some intrinsic properties of the Java Card platform make it competitive for building embedded systems: • Persistent memory model and execute-in-place: impacts on system startup, power budget • JVM™ machine on bare metal • Dynamic application downloading: not necessarily a closed system • Web server and container (unique in this memory budget) • Remotely management with open/standard protocols • Security model supporting multiple actors and trust delegation The session presents real-life use cases: • Healthcare systems (USB token French experimentation) • Sensors (value of an HTTP[s] client stack) • Digital home (value of an HTTP[s] server stack) It also suggests evolutions of the spec: • Reducing footprint with static products (fixed feature set) • Getting rid of APDUs: beyond cards, APDUs and applets are useless • Going beyond the Servlets application model |
|
| |
|
| |
|
| |
|