Motorola MOTORAZR maxx V6 Developer's Manual page 87

Java ME Developer Guide
Chapter 12 - JSR-177 Java ME Security and Trust Services API
CLDC 1.1
MIDP 2.0
12.3 New Implementation
This article will only reference the APDU package of JSR 177, SATSA-APDU since it is
the only one implemented on Motorola JSR 177 compliant devices.
The smart card communication API is based on the Generic Connection Framework in
the
municate with ISO 7816-4 compliant smart cards.
12.3.1 javax.microedition.apdu Optional
Package
The SATSA-APDU optional package supports the following functions:
A MIDlet can create an APDUConnection to communicate with a smart
card application identified by an AID.
An APDUConnection supports exchange of APDU commands encoded in
the format, which conforms to ISO 7816-4.
Each APDUConnection has a logical channel reserved exclusively for it.
Logical channel management is handled by the API implementation,
which requests the smart card to allocate an unused logical channel.
More than one APDUConnection can be created to communicate
simultaneously with smart card applications on one (via logical
channels) or multiple smart cards.
An APDUConnection can be created to communicate with (U)SAT
applications on channel 0 of a smart card. The APDUConnection has
limited capabilities when communicating with a (U)SAT application.
Only ENVELOPE APDUs may be sent by a MIDlet to trigger a (U)SAT
application.
Proactive sessions and commands are not supported by the
APDUConnection. It is the MIDlet's responsibility to not send an
envelope to the (U)SAT application that would result in a proactive
session being initiated via the APDUConnection interface.
The optional package SATSA-APDU includes two components to support communica-
tion with ISO 7816-4 compliant smart cards using the APDU protocol:
DRAFT - Subject to Change
package. The APDUConnection interface is used to com-
[87/201]