Content for  TS 27.007  Word version:  19.0.0

Set command enables and disables automatic time zone update via NITZ. If setting fails in an MT error, +CME ERROR: <err> is returned. Refer to clause 9.2 for possible <err> values. Read command returns the current settings in the MT. Test command returns supported on- and off-values as a compound value.

<onoff>

Optional.

This set command controls the time zone change event reporting. If reporting is enabled the MT returns the unsolicited result code +CTZV: <tz>, +CTZE: <tz>,<dst>,[<time>], or +CTZEU: <tz>,<dst>,[<utime>] whenever the time zone is changed. The MT also provides the time zone upon network registration if provided by the network. If setting fails in an MT error, +CME ERROR: <err> is returned. Refer to clause 9.2 for possible <err> values. Read command returns the current reporting settings in the MT. Test command returns supported <reporting>-values as a compound value.

<reporting> <tz> <dst> <time> <utime>

Optional.

Execution command informs TA that TE wants to establish a peer-to-peer protocol <proto> or upper layer connection (indicating by the <lsap>s setting) with the MT on the link from which the command was received. This command can be used in case the link between TE and MT does not provide itself such a mechanism. If MT has succeeded in establishing a logical link between application protocols and external interface, it will send CONNECT message to the TE. Otherwise, the NO CARRIER response will be returned. If the CONNECT response is received, TE can start sending <proto> or upper layer frames. The connection shall always return for <proto> mode when the protocol session is ended. When the MT receives a disconnect request from its peer entity, it will process it and send OK response to the TE indicating its capability for receiving new AT commands. Since <proto> or upper layers can be accessed in other ways, TA must have pre-knowledge of the fact that connection is initiated with AT+CPROT command. This means that switch to <proto> mode must include some sort of notification to the protocol entity. This command can be aborted by sending a <proto> or upper layer disconnection frame. In that case, MT will return in command mode by sending the OK response. Refer to clause 9.2 for possible <err> values. Test command returns values supported as compound values.

<proto> <version> <lsap1> <lsap2>...<lsapN>

Optional.

Execution command transmits to the MT the <command> it then shall send as it is to the selected UICC. In the same manner the UICC <response> shall be sent back by the MT to the TA as it is. Refer to clause 9.2 for possible <err> values. This command allows a direct control of the currently selected UICC by a distant application on the TE. The TE shall then take care of processing UICC information within the frame specified by GSM/UMTS. Although Generic UICC Logical Channel Access command +CGLA allows TE to take control over the UICC-MT interface, there are some functions of the UICC-MT interface that logically do not need to be accessed from outside the TA/MT. Moreover, for security reason the GSM network authentication should not be handled outside the TA/MT. Therefore it shall not be allowed to execute a Run GSM Algorithm command or an Authenticate command in GSM context from the TE using +CGLA at all time whether the +CGLA is locked or unlocked. This shall not forbid the TE to send Authenticate commands in other security contexts (e.g. EAP security context). For example, the TA/MT shall forbid the transfer of the Authenticate command to a USIM application when parameters P2 = 0 (GSM security context). See TS 31.102 for USIM authenticate command definition.

<sessionid> <length> <command> <response>

Optional.

By using this command instead of Generic UICC Access +CGLA TE application has easier but more limited access to the UICC database. Execution 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 to 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.

<sessionid> <fileid> <P1>, <P2>, <P3> <data> <pathid> <sw1>, <sw2> <response>

Optional.

Execution of the command causes the MT to return <sessionid> to allow the TE to identify a channel that is being allocated by the currently selected UICC, which is attached to ME. The currently selected UICC will open a new logical channel; select the application identified by the <dfname> received with this command and return a session Id as the response. The ME shall restrict the communication between the TE and the UICC to this logical channel. This <sessionid> is to be used when sending commands with Restricted UICC Logical Channel access +CRLA or Generic UICC Logical Channel access +CGLA commands. Refer to clause 9.2 for possible <err> values.

<dfname> <sessionid> See TS 31.101 for more information about defined values.

Optional.

This command asks the ME to close a communication session with the active UICC. The ME shall close the previously opened logical channel. The TE will no longer be able to send commands on this logical channel. The UICC will close the logical channel when receiving this command. Refer to clause 9.2 for possible <err> values.

<sessionid>

Optional.

This command allows a TE to exchange EAP packets with the UICC or the ME. Prior to the execution of this command, the TE shall retrieve the available AIDs using the +CUAD command. The TE shall select one appropriate AID to be addressed. Selection may include asking the user, and considering EAP methods supported by the AIDs. The TE shall set the <dfname> value using the selected AID and shall set the <EAPMethod> value to the requested EAP method. The TE may set the <DFeap> value to the directory file identifier that is applicable to the <EAPMethod>; which is derived from the discretionary data returned by +CUAD. The parameter is mandatory for EAP terminated in UICC. If the targeted application on the UICC does support the requested EAP method, the MT shall use the value provided in <DFeap>, and it shall transmit the <EAP packet data> to the UICC application using the Authenticate APDU command as defined in ETSI TS 102 310 [66]. The appropriate DFEAP in the ADF must be selected prior to the submission of an EAP Authenticate command with the <EAP packet data>. Then the EAP Response data sent by the UICC application in its response to the Authenticate command shall be provided to the TE in <EAP packet response>. If the targeted application on the UICC does not support the requested EAP method and if the MT does support this method then the <EAP packet data> shall be handled by the MT. During the handling of the EAP method, the MT shall run the authentication algorithm on the SIM or USIM, respectively. Also the MT has to allocate an <EAPsessionid> in order to identify an EAP session and its corresponding keys and parameters. If neither the MT nor the appropriate UICC application support the requested EAP method, the MT shall respond with +CME ERROR: 49 (EAP method not supported). Refer to clause 9.2 for possible <err> values.

<dfname> <EAPMethod> <EAP packet data> <DFeap> <EAPsessionid> <EAP packet response>

Optional.

This command allows a TE to retrieve EAP session parameters / derived keys after a run of the +CEAP command. If the EAP session is handled by the UICC then the MT shall return the content of the elementary file corresponding to the indicated <EAPparameter>. Those EFs are defined in ETSI TS 102 310 [66]. If the MT handles the EAP session then the MT shall return the corresponding parameter encoded as defined for EAP files, see ETSI TS 102 310 [66]. For example, the keys shall be retrieved in the TLV format described in ETSI TS 102 310 [66]. If neither the MT nor the appropriate UICC application can provide the requested information (e.g. because the requested EAP session ID does not exist), the MT shall respond with +CME ERROR: 50 (Incorrect parameters). Refer to clause 9.2 for possible <err> values.

<EAPparameter> <EAPsessionid> <EAP parameter response>

Optional.

This command asks the MT to discover what applications are available for selection on the UICC. According to ETSI TS 102 221 [60], the ME shall access and read the EFDIR file in the UICC and return the values that are stored in its records. Each record contains the AID and optionally application parameters of one of the applications available on the UICC. If optional parameter(s) are requested and the EFDIR file is not present in the UICC, <response> shall be empty. Refer to clause 9.2 for possible <err> values. Test command returns the supported option values as a compound value.

<response> <option> <active_application> <AID>

Optional.