[SIM/USIM] Common elements in proactive UICC commands

1      Command number 

The command number is to cater for the future possibility of multiple ongoing commands (i.e. when the UICC issues further commands before receiving the response to the ongoing command). The implications of such multiple ongoing commands have not been elaborated at this stage of the toolkit specification. 

Each command issued by a proactive UICC during a card session shall have its own command number. Command numbers may take any hexadecimal value between "01" and "FE". The command number is held in the command details data object. 

The UICC is responsible for assigning the command number. 

The terminal shall keep a record of the status of each command and its command number, until the terminal gives the result of the command to the UICC, using TERMINAL RESPONSE. After this, the terminal may erase all internal records concerning this command. The command number is then free for allocation by the UICC to a new command. 

When the terminal is powered off and on, the details of any ongoing command shall be reset. The terminal shall not be expected to know the status of commands issued in a previous card session. 

2      Device identities 

This data object gives the devices which are the source and destination for the instruction. Only certain combinations of source and destination devices are allowed for each proactive command. These are given in clause 10. 

3      Alpha identifier 

Many of the commands include an alpha identifier data object. The text it contains shall be displayed on screen by the terminal at the same time as the UICC command is performed. 

4      Icon identifiers 

Some commands may provide an icon identifier. Icons are intended to enhance the MMI by providing graphical information to the user. The display of icons is optional for the terminal. If icons are provided by the UICC, the related alpha identifier or text string shall be present and not a null string. 

The UICC indicates to the terminal whether the icon replaces an alpha identifier or text string, or whether it accompanies it (see clause 8.32). 

If both an alpha identifier or text string, and an icon are provided with a proactive command, and both are requested to be displayed, but the terminal is not able to display both together on the screen, then the alpha identifier or text string takes precedence over the icon. 

If the UICC provides an icon identifier with a proactive command, then the terminal shall inform the UICC if the icon could not be displayed by sending the general result "Command performed successfully, but requested icon could not be displayed". 

If the terminal receives an icon, and either an empty or no alpha identifier/text string is given by the UICC, than the terminal shall reject the command with general result "Command data not understood by terminal". 

NOTE:     Application designers should be aware that icons provided by the application may not be displayed by the terminal. 

5      Text Attribute 

Some commands may provide a text attribute. Text attributes are intended to enhance the MMI when providing information to the user. The display of various text formats as described in TS 123 040 [27] are optional for the ME. 

6      Frame identifier 

Some commands may provide a frame identifier. Frames are intended to enhance the MMI by dividing the terminal's screen into several rectangular regions (frames). The display of frames is optional for the terminal. 

If the UICC provides a frame identifier with a proactive command, then the terminal supporting the frames feature shall display the command proactive information (e.g. text string, alpha identifier, icon, etc.) in the corresponding frame. If the user terminates a proactive session, this shall only affect the frame in which the proactive command is executed. 

If the screen is split into frames and no frame identifier is given in a proactive command or the frame identifier is invalid, the default frame shall be used. 

If the terminal does not support the frames feature or the screen is not split into frames, it shall ignore the frame identifier data object.