Sec re elemen archi ec s for oda s genera ion Device Implementation Guidelines 18

7. Card Application Toolkit

This chapter does not intend to duplicate the standard, but rather to focus on key requirements
related to Card Application Toolkit and to provide additional implementation guidelines to ensure
the most adapted device behavior according to the market use cases.

Widely supported commands are mentioned in the Basic commands sub-chapter while other
commands requiring more clarification on the expected device implementations are described with
a dedicated sub-chapter per command.

This document does not integrate specific LTE requirements which are described in chapter 10:
LTE device implementation guidelines.

7.1 Basic qualifiers

The following qualifiers or parameters related to basic commands are mandatory and SHALL be
supported by the device whenever applicable:
DCS 7 bits, 8 bits and UCS2 for Text String
SMS default Alphabet or Digit only
Normal & High Priority for Get Input
Clear after delay & Wait for user to clear message for Get Input
Automatic Scrolling supported and indicated in the Terminal Profile for each command with
display function (Select Item, Get Input, Display Text…)

UCS2 shall be supported for languages using 2 bytes encoding (Chinese, Russian, etc. alphabets).

7.2 Alpha Identifier Management

The Alpha identifier field is used in a large set of proactive commands. It holds text that could be
displayed on the device screen if the end user needs to be notified of the device action within a
Toolkit procedure. The standard specifies three attributes of the Alpha Identifier management:
If the Alpha Identifier is provided by the UICC and is not a NULL data object, the ME shall
use it to inform the user of the ongoing action.
If the Alpha Identifier is provided by the UICC and is a NULL data object (i.e. length = '00'
and no value), this is an indication that the ME SHALL NOT display any information on the
ongoing actions.
If the Alpha Identifier is not provided by the UICC, it is recommended that the device
behaves in the same way as with a NULL Alpha Identifier.

Device SHALL support the 3 modes:

Alpha Identifier Tag provided by the UICC
NULL data object for Alpha Identifier
No Alpha Identifier Tag provided by the UICC

Security, Identity, Mobility

Sec re elemen archi ec s for oda s genera ion Device Implementation Guidelines 19

7.3 Transparent mode

Several applications need to work in a transparent mode in order to avoid any unnecessary
confirmation or information message that can be confusing for the end-user.

Such applications are always under the strict control of the mobile network operators as the UICC
security ensures that only an authorized entity (i.e. the operator) is able to install Toolkit
applications in the UICC.

Transparent mode is defined by the Alpha Identifier coding with the NULL length for each
command using an Alpha Identifier Tag. For commands without Alpha Identifier or if the Alpha
Identifier is omitted in a command supporting it, the action SHALL be performed transparently for
the end-user. Transparent mode SHALL be implemented for the following proactive commands
requiring an Alpha Identifier field:
Set Up Call command
Send SMS command
Send USSD command
Refresh
Launch Browser command
BIP commands (Open Channel / Close Channel / Send Data / Receive Data)
Call Control by SIM envelope
SMS MO Control by SIM envelope
Set Up Event List command
Timer Management
And in other commands like Play Tone, Set Up Menu, Run AT Command, Send DTMF.

To avoid confusing the end-user (the message will not be seen), when receiving an Envelope
SMS-PP Download with TP-PID=7Fh, the device SHALL NOT notify the end-user (no text
displayed, no ring) of the reception of this message.

The events related to the Set Up Event List command SHALL be sent by the device to the UICC in
a transparent way for the end user.

7.4 Basic Commands

All commands below are defined in the first release of the Toolkit specification and are quite well
implemented in devices. This chapter only mentions specific modes and parameters that were
either included later in the specification or that are currently requested by the market and are not
always well supported.

Display Text
» Sustained text (or Immediate Response) shall be supported
» Duration (variable timeout) should be supported
» Maximum number of characters that can be displayed: 200 characters
» Displayed on top of other applications (browser for instance)
Get Inkey
» Binary Choice (Yes or No Response) shall be supported
» Duration (variable timeout) should be supported
» Help Information should be supported
Get Input

Security, Identity, Mobility

Sec re elemen archi ec s for oda s genera ion Device Implementation Guidelines 20

» Maximum number of characters displayed (for the question): 60 characters

» Maximum number of characters that can be used: 100 Characters
» Help Information should be supported
Select Item
» Order given by the SIM shall be supported
» Maximum number of characters (for title or for each item): 60 characters
» Number of items supported: at least 10 items
» Help Information should be supported
» SoftKey should be supported
Set Up Menu
» Quick access to the SIM Menu (3 click max) and first position
» Help Information should be supported
» SoftKey should be supported
Send Short Message
» Management of concatenated SMS shall be supported
» No user confirmation
» Support of Packing by ME required
Set Up Call
More Time
Play Tone
» Audible (via speaker)
» Not blocking in case of Silent mode (ex Terminal Response 09 instead of TR 2x or
3x)
Envelope Menu Selection
SMS Point to Point Data Download (PID = 0x7F & DCS = 0xF6)
Send SS

7.5 Terminal Profile

The Terminal Profile gives the capabilities of the device. It is very important to have accurate
information in this command as several Toolkit applications are using it to define the way they
behave and to assess whether or not they are able to run on the targeted device.

All supported commands and parameters SHALL be indicated in the Terminal Profile command. If
a feature is not supported it SHALL NOT be indicated as supported in the Terminal Profile.

7.6 Terminal Response

The device SHALL provide the appropriated Terminal Response answer for all proactive
commands requested by the UICC. The maximum delay for a TR=12; No Response from user
SHALL NOT exceed 2 minutes.

7.7 Refresh command

The REFRESH command is used by Toolkit applications whenever it is important to have the
device re-reading a file or repeating a specific action (like a network attachment). The following
parameters/qualifiers are requested:
Refresh Init + Full File Change Notification shall be supported

Security, Identity, Mobility

Sec re elemen archi ec s for oda s genera ion Device Implementation Guidelines 21

Refresh File Change Notification shall be supported

Refresh Init + File Change Notification shall be supported
Refresh Init shall be supported
Refresh Reset shall be supported
Refresh NAA Reset, only applicable for 3G platform shall be supported
Refresh Session Reset, only applicable for 3G platform shall be supported
Refresh Steering of Roaming should be supported

Thanks to remote administration, UICC behavior can be modified Over the Air. It is thus very
important that the device respects the following recommendations when applicable.

In the case of a UICC REFRESH request in reset mode, the network attachment parameters may
have changed, so it is mandatory to set-up new connections (voice and data) according to these
parameters:
Check again all the SIM capabilities (2G/3G, etc.)
If applicable ask for a PIN code presentation from the end-user, not using a stored one
Perform a network de-attachment and full attachment (using freshly read PLMN files,
EFLoci and EFIMSI)
Cut all data connections (internet, BIP, etc.) and DO NOT answer with "Terminal busy" or
similar Terminal Response to active Toolkit applications

In the case of a UICC REFRESH request with parameters other than reset mode, the device
shall:
Cut all data connections (internet, BIP, etc.) and DO NOT answer with "Terminal busy" or
similar Terminal Response to active Toolkit applications
Based on the Command Qualifier perform a network de-attachment and full attachment
(using freshly read PLMN files,EFLoci and EFIMSI)
Shall not send a TERMINAL PROFILE while executing the REFRESH procedure; not
before and not after sending the TERMINAL RESPONSE to the REFRESH command
Shall not update any Files on the UICC between reception of the REFRESH command
and executing the REFRESH procedure (e.g. to avoid updating of network related EFs)
Send a Terminal-Response to indicate a successful REFRESH procedure

7.8 Send USSD command

Send USSD is used for mobile network operator services relying on dynamic Toolkit application.

The Data Coding Scheme used in the USSD String field is coded as for Cell Broadcast Data
Download command defined in ETSI TS 23.038. The coding of DCS for 7 bits and 8 bit is different
from DCS commonly used for SMS. Most of application using USSD server from mobile network
operator uses a packet message with the associated DCS=0x0F.

Some USSD services request the network to send back some data, within the Terminal Response.
This data SHALL be forwarded to the UICC and SHALL NOT be displayed on the screen by the
device.

7.9 Provide Local Information command

Security, Identity, Mobility