Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 27.007  Word version:  17.6.0

Top   Top   Up   Prev   Next
1…   4…   5…   6…   6.10…   6.20…   7…   7.10…   7.20…   7.30…   7.40…   8…   8.10…   8.20…   8.30…   8.40…   8.50…   8.55   8.56…   8.60…   8.70…   8.80…   9…   10…   10.1.3…   10.1.10…   10.1.20…   10.1.30…   10.1.40…   10.1.50…   10.1.60…   10.1.70…   10.2…   11…   12…   13…   14…   15…   16…   17…   18…   A   B   C…   E   F   G…

 

8.40  Automatic time zone update +CTZUWord‑p. 150

Command Possible response(s)
+CTZU=[<onoff>] +CME ERROR: <err>
+CTZU? +CTZU: <onoff>
+CME ERROR: <err>
+CTZU=? +CTZU: (list of supported <onoff>s)
+CME ERROR: <err>
Description
Set command enables and disables automatic time zone update via NITZ. If setting fails in an MT error, +CME ERROR: <err> is returned. Refer 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.
Defined values
<onoff>
integer type value indicating
0 (default)
Disable automatic time zone update via NITZ.
1
Enable automatic time zone update via NITZ.
Implementation
Optional.
Up

8.41  Time zone reporting +CTZRWord‑p. 151

Command Possible response(s)
+CTZR=[<reporting>] +CME ERROR: <err>
+CTZR? +CTZR:<reporting>
+CME ERROR: <err>
+CTZR=? +CTZR: (list of supported <reporting>s)
+CME ERROR: <err>
Description
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 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.
Defined values
<reporting>
integer type value indicating:
0 (default)
disable time zone change event reporting.
1
Enable time zone change event reporting by unsolicited result code +CTZV: <tz>.
2
Enable extended time zone and local time reporting by unsolicited result code +CTZE: <tz>,<dst>,[<time>].
3
Enable extended time zone and universal time reporting by unsolicited result code +CTZEU: <tz>,<dst>,[<utime>].
<tz>
string type value representing the sum of the local time zone (difference between the local time and GMT expressed in quarters of an hour) plus daylight saving time. The format is "±zz", expressed as a fixed width, two digit integer with the range -48 ... +56. To maintain a fixed width, numbers in the range -9 ... +9 are expressed with a leading zero, e.g. "-09", "+00" and "+09".
<dst>
integer type value indicating whether <tz> includes daylight savings adjustment;
0 (default)
<tz> includes no adjustment for Daylight Saving Time
1
<tz> includes +1 hour (equals 4 quarters in <tz>) adjustment for daylight saving time
2
<tz> includes +2 hours (equals 8 quarters in <tz>) adjustment for daylight saving time
<time>
string type value representing the local time. The format is "YYYY/MM/DD,hh:mm:ss", expressed as integers representing year (YYYY), month (MM), date (DD), hour (hh), minute (mm) and second (ss). The local time can be derived by the MT from information provided by the network at the time of delivering time zone information and will be present in the unsolicited result code for extended time zone and local time reporting if the universal time is provided by the network.
<utime>
string type value representing the universal time. The format is "YYYY/MM/DD,hh:mm:ss", expressed as integers representing year (YYYY), month (MM), date (DD), hour (hh), minute (mm) and second (ss). The universal time can be provided by the network at the time of delivering time zone information and will be present in the unsolicited result code for extended time zone and universal time reporting if provided by the network.
Implementation
Optional.
Up

8.42  Enter protocol mode+CPROTWord‑p. 152

Command Possible response(s)
+CPROT=<proto>[,<version>[,<lsap1>[,...[<lsapN>]]]]CONNECT
NO CARRIER
OK
ERROR
+CME ERROR: <err>
+CPROT=? +CPROT: <proto1>[,(list of supported <version>s)[,(list of supported <lsap1>s)[,...[,(list of supported <lsapN>s)]]]]
[<CR><LF>+CPROT: <proto2>[,(list of supported <version>s)[,(list of supported <lsap1>s)[,...[,(list of supported <lsapN>s)]]]]
[...]]
Description
Set 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 clause 9.2 for possible <err> values.
Test command returns values supported as compound values.
Defined values
<proto>
integer type
0
OBEX (refer IrDA Object Exchange Protocol [44]).
…15
reserved by the present document
16...
manufacturer specific
<version>
version number of <proto>: string type
<lsap1>
integer type; defines a level of service or application protocol on the top of <proto> layer. It may refer to services or protocols defined in other standards development organizations (SDOs).
1
IrMC level 1 (Minimum Level) Only .(refer [43] clause 2.9.4)
2
IrMC level 1 and 2 (Minimum and Access Levels) Only. .(refer [43] clause 2.9.4)
4
IrMC level 1, 2 and 3 (Minimum, Access, Index Levels) Only- implies static index support. .(refer [43] clause 2.9.4)
8
IrMC level 1, 2 and 4 (Minimum, Access and Sync Levels) Only-implies unique index support. .(refer [43] clause 2.9.4)
10
IrMC level 1, 2, 3 and 4 (Minimum, Access, Index and Sync Levels)-implies support of static and unique index. .(refer [43] clause 2.9.4)
…15 reserved by the present document
16...
manufacturer specific
<lsap2>...<lsapN>
integer type
In case <lsapN>,<lsapN+1> received in the +CPROT command identifies protocol layers, the protocol identified by N+1 shall be on the top of the protocol identified by N on a framework point of view.
0…15
reserved by the present document
16...
manufacturer specific
Implementation
Optional.
Up

8.43  Generic UICC logical channel access +CGLA |R5|Word‑p. 153

Command Possible response(s)
+CGLA=<sessionid>,<length>,<command> +CGLA: <length>,<response>
+CME ERROR: <err>
+CGLA=?
Description
Set 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 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.
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 manadatory 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").
<length>
integer type; length of the characters that are sent to TE in <command> or <response> (two times the actual length of the command or response).
<command>
command passed on by the MT to the UICC in the format as described in TS 31.101 (hexadecimal character format; refer +CSCS).
<response>
response to the command passed on by the UICC to the MT in the format as described in TS 31.101 (hexadecimal character format; refer +CSCS).
Implementation
Optional.
Up

8.44  Restricted UICC logical channel access +CRLA |R6|Word‑p. 154

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 TS 31.101):
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
<fileid>
integer type; this is the identifier of an elementary datafile on UICC. Mandatory for every command except STATUS.
<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 TS 31.101.
<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 TS 31.101). 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.
Up

8.45  Open logical channel +CCHO |R6|Word‑p. 156

Command Possible response(s)
+CCHO=<dfname><sessionid>
+CME ERROR: <err>
+CCHO=?
Description
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 clause 9.2 for possible <err> values.
Defined values
<dfname>
all selectable applications in the UICC are referenced by a DF name coded on 1 to 16 bytes
<sessionid>
integer type; a session Id to be used in order to target a specific application on the smart card (e.g. (U)SIM, WIM, ISIM) using logical channels mechanism
See TS 31.101 for more information about defined values.
Implementation
Optional.
Up

8.46  Close logical channel +CCHC |R6|Word‑p. 156

Command Possible response(s)
+CCHC=<sessionid> +CCHC
+CME ERROR: <err>
+CCHC=?
Description
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 clause 9.2 for possible <err> values.
Defined values
<sessionid>
integer type; a session Id to be used in order to target a specific application on the smart card (e.g. (U)SIM, WIM, ISIM) using logical channels mechanism
Implementation
Optional.
Up

8.47  EAP authentication +CEAP |R6|Word‑p. 157

Command Possible response(s)
+CEAP=<dfname>,<EAPMethod>,<EAP packet data>[,<DFeap>] +CEAP: <EAPsessionid>, <EAP packet response>
+CME ERROR: <err>
+CEAP=?
Description
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 clause 9.2 for possible <err> values.
Defined values
<dfname>
string type in hexadecimal character format. All selectable applications are represented in the UICC by an AID coded on 1 to 16 bytes.
<EAPMethod>
string type in hexadecimal character format. This is the EAP Method Type as defined in RFC 3748 in 1 byte format or 8 bytes expanded format. The value range for 1 byte format and for 8 bytes expanded format is defined in RFC 3748.
<EAP packet data>
string type in hexadecimal character format. This is the EAP packet data in hexadecimal character as defined in ETSI TS 102 310 [66].
<DFeap>
string type in hexadecimal character format. Contains the DF(EAP) associated with the specified <EAPMethod> on the SIM/UICC as defined in ETSI TS 102 310 [66] (e.g. "6D34").
<EAPsessionid>
integer type. This is the identifier of the EAP session to be used in order to retrieve the EAP parameters with EAP Retreive Parameters +CERP command. Value range is from 1 to 4294967295.
<EAP packet response>
string type in hexadecimal character format. Defined in ETSI TS 102 310 [66].
Implementation
Optional.
Up

8.48  EAP retrieve parameters +CERP |R6|Word‑p. 159

Command Possible response(s)
+CERP=<EAPsessionid>,<EAPparameter> +CERP: <EAP parameter response>
+CME ERROR: <err>>
+CERP=?
Description
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 clause 9.2 for possible <err> values.
Defined values
<EAPparameter>
integer type.
1
Keys
2
Status
3
Identity
4
Pseudonym
<EAPsessionid>
integer type; this is the identifier of the EAP session to be used in order to retrieve the EAP parameters corresponding to an active EAP session. Value range is from 1 to 4294967295.
<EAP parameter response>
string type in hexadecimal character format. The format of the parameter is defined in ETSI TS 102 310 [66]. The <EAP parameter response> depends on the value of the <EAPparameter>.
Implementation
Optional.
Up

8.49  UICC application discovery +CUAD |R6|Word‑p. 159

Command Possible response(s)
+CUAD[=<option>] +CUAD: <response>[,<active_application>[,<AID>]]
+CME ERROR: <err>
+CUAD=? +CUAD: (list of supported <option>s)
Description
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 clause 9.2 for possible <err> values.
Test command returns the supported option values as a compound value.
Defined values
<response>
string type in hexadecimal character format. The response is the content of the EFDIR.
<option>
integer type.
0 (default)
no parameters requested in addition to <response>.
1
include <active_application>.
<active_application>
integer type.
0
no SIM or USIM active.
1
active application is SIM.
2
active application is USIM, followed by <AID>.
<AID>
string type in hexadecimal character format. AID of active USIM.
Implementation
Optional.
Up

Up   Top   ToC