8.44 Restricted UICC logical channel access +CRLA

27.0073GPPAT command set for User Equipment (UE)Release 18TS

Table 104: +CRLA action command syntax

Command

Possible response(s)

+CRLA=<sessionid>,<command>[,<fileid>[,<P1>,<P2>,<P3>[,<data>[,<pathid>]]]]

+CRLA: <sw1>,<sw2>[,<response>]

+CME ERROR: <err>

+CRLA=?

Description

By using this command instead of Generic UICC Access +CGLA TE application has easier but more limited access to the UICC database. Set command transmits to the MT the UICC <command> and its required parameters. MT handles internally, for the selected UICC, all UICC‑MT interface locking and file selection routines. As response to the command, MT sends the actual UICC information parameters and response data. MT error result code +CME ERROR may be returned when the command cannot be passed to the UICC, but failure in the execution of the command in the UICC is reported in <sw1> and <sw2> parameters. Refer clause 9.2 for possible <err> values.

Coordination of command requests to UICC and the ones issued by GSM/UMTS application inside the MT is implementation dependent. However the TE should be aware of the precedence of the GSM/UMTS application commands to the TE commands.

Defined values

<sessionid>: integer type; this is the identifier of the session to be used in order to send the APDU commands to the UICC. It is mandatory in order to send commands to the UICC when targeting applications on the smart card using a logical channel other than the default channel (channel "0").

<command>: (command passed on by the MT to the UICC; refer 3GPP TS 31.101 [65]):

176 READ BINARY

178 READ RECORD

192 GET RESPONSE

214 UPDATE BINARY

220 UPDATE RECORD

242 STATUS

203 RETRIEVE DATA

219 SET DATA

all other values are reserved

NOTE 1: The MT internally executes all commands necessary for selecting the desired file, before performing the actual command.

<fileid>: integer type; this is the identifier of an elementary datafile on UICC. Mandatory for every command except STATUS.

NOTE 2: The range of valid file identifiers depends on the actual UICC and is defined in 3GPP TS 31.101 [65]. Optional files may not be present at all.

<P1>, <P2>, <P3>: integer type; parameters passed on by the MT to the UICC. These parameters are mandatory for every command, except GET RESPONSE and STATUS. The values are described in 3GPP TS 31.101 [65].

<data>: information which shall be written to the SIM (hexadecimal character format; refer +CSCS).

<pathid>: string type; contains the path of an elementary file on the UICC in hexadecimal format (e.g. "5F704F30" for DFSoLSA/EFSAI). The <pathid> shall only be used in the mode "select by path from current DF" as defined in ETSI TS 102 221 [60].

<sw1>, <sw2>: integer type; information from the UICC about the execution of the actual command. These parameters are delivered to the TE in both cases, on successful or failed execution of the command.

<response>: response of a successful completion of the command previously issued (hexadecimal character format; refer +CSCS). STATUS and GET RESPONSE return data, which gives information about the current elementary datafield. This information includes the type of file and its size (refer 3GPP TS 31.101 [65]). After READ BINARY, READ RECORD or RETRIEVE DATA command the requested data will be returned. <response> is not returned after a successful UPDATE BINARY, UPDATE RECORD or SET DATA command.

Implementation

Optional.