Motorola MOTORAZR maxx V6 Developer's Manual page 89

Java ME Developer Guide
Chapter 12 - JSR-177 Java ME Security and Trust Services API
channel is acquired for the APDU connection, the implementation establishes an
APDU connection with the specified application and returns the resulting connection
object to the MIDlet.
The implementation uses method
to be used in opening an APDU connection.
The value returned is a comma-separated list of the smart card slots which can be
used in the
cific smart card slot. The logical slot names include the slot number and a descriptor
indicating the type of the slot. For cold-swappable slots the letter 'C' is appended to
the slot number. For hot-swappable slots the letter 'H' is appended to the slot
number. The slot descriptors (the letter 'C' and 'H' appended to the slot number)
cannot be passed as part of the URI to open a connection to the smart card applica-
tion. The Java ME application MUST remove the descriptor from the logical slot name
and only use the slot number in the URI to identify the specific smart card slot. The
(U)SIM card will by default always be in slot (name) 0.
If the opening of the APDU connection fails, the implementation releases the logical
channel established between the handset and the smart card for the APDU connec-
tion.
The URI used in method
the following BNF syntax:
URI Format Description
<APDU_connection_string>
<targetAddress>
<slot>
<target>
<AID>
DRAFT - Subject to Change
(with key
) to obtain the name of the smart card slots
string to identify the spe-
BNF Syntax
::= "apdu:"<targetAddress>
::= [slot];target
::= smart card slot number.
(optional. Hexadecimal
number identifying the smart
card slot. Default slot
assumed if left empty)
::= "target="<AID>|"SAT"
::=< 5 - 16 bytes >
An AID uniquely identifies
a smart card application. It is
represented by 5 to 16
hexadecimal bytes where each
conforms to
[89/201]