| <gsm> |
| <spec> |
| <command>AT+CGMI</command> |
| <profile>Request manufacturer identification </profile> |
| <description>Execution command causes the TA to return one or more lines of information text [manufacturer], determined by the MT manufacturer, which is intended to permit the user of the TA to identify the manufacturer of the MT to which it is connected to. Typically, the text will consist of a single line containing the name of the manufacturer, but manufacturers may choose to provide more information if desired. Refer subclause 9.2 for possible [err] values. |
| Defined values |
| [manufacturer]: the total number of characters, including line terminators, in the information text shall not exceed 2048 characters. |
| Text shall not contain the sequence 0[CR] or OK[CR] |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CGMI=?</command> |
| <profile>Request manufacturer identification (Query all)</profile> |
| <description>Execution command causes the TA to return one or more lines of information text [manufacturer], determined by the MT manufacturer, which is intended to permit the user of the TA to identify the manufacturer of the MT to which it is connected to. Typically, the text will consist of a single line containing the name of the manufacturer, but manufacturers may choose to provide more information if desired. Refer subclause 9.2 for possible [err] values. |
| Defined values |
| [manufacturer]: the total number of characters, including line terminators, in the information text shall not exceed 2048 characters. |
| Text shall not contain the sequence 0[CR] or OK[CR] |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CGMM</command> |
| <profile>Request model identification </profile> |
| <description>Execution command causes the TA to return one or more lines of information text [model], determined by the MT manufacturer, which is intended to permit the user of the TA to identify the specific model of the MT to which it is connected to. Typically, the text will consist of a single line containing the name of the product, but manufacturers may choose to provide more information if desired. Refer to subclause 9.2 for possible [err] values. |
| Defined values |
| [model]: the total number of characters, including line terminators, in the information text shall not exceed 2048 characters. |
| Text shall not contain the sequence 0[CR] or OK[CR] |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CGMM=?</command> |
| <profile>Request model identification (Query all)</profile> |
| <description>Execution command causes the TA to return one or more lines of information text [model], determined by the MT manufacturer, which is intended to permit the user of the TA to identify the specific model of the MT to which it is connected to. Typically, the text will consist of a single line containing the name of the product, but manufacturers may choose to provide more information if desired. Refer to subclause 9.2 for possible [err] values. |
| Defined values |
| [model]: the total number of characters, including line terminators, in the information text shall not exceed 2048 characters. |
| Text shall not contain the sequence 0[CR] or OK[CR] |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CGMR</command> |
| <profile>Request revision identification </profile> |
| <description>Execution command causes the TA to return one or more lines of information text [revision], determined by the MT manufacturer, which is intended to permit the user of the TA to identify the version, revision level or date, or other pertinent information of the MT to which it is connected to. Typically, the text will consist of a single line containing the version of the product, but manufacturers may choose to provide more information if desired. Refer subclause 9.2 for possible [err] values. |
| Defined values |
| [revision]: the total number of characters, including line terminators, in the information text shall not exceed 2048 characters. |
| Text shall not contain the sequence 0[CR] or OK[CR] |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CGMR=?</command> |
| <profile>Request revision identification (Query all)</profile> |
| <description>Execution command causes the TA to return one or more lines of information text [revision], determined by the MT manufacturer, which is intended to permit the user of the TA to identify the version, revision level or date, or other pertinent information of the MT to which it is connected to. Typically, the text will consist of a single line containing the version of the product, but manufacturers may choose to provide more information if desired. Refer subclause 9.2 for possible [err] values. |
| Defined values |
| [revision]: the total number of characters, including line terminators, in the information text shall not exceed 2048 characters. |
| Text shall not contain the sequence 0[CR] or OK[CR] |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CGSN</command> |
| <profile>Request product serial number identification </profile> |
| <description>Execution command causes the TA to return one or more lines of information text [sn], determined by the MT manufacturer, which is intended to permit the user of the TA to identify the individual MT to which it is connected to. Typically, the text will consist of a single line containing the IMEI (International Mobile station Equipment Identity; refer 3GPP TS 23.003 [7]) number of the MT, but manufacturers may choose to provide more information if desired. Refer subclause 9.2 for possible [err] values. |
| Defined values |
| [sn]: the total number of characters, including line terminators, in the information text shall not exceed 2048 characters. |
| Text shall not contain the sequence 0[CR] or OK[CR] |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CGSN=?</command> |
| <profile>Request product serial number identification (Query all)</profile> |
| <description>Execution command causes the TA to return one or more lines of information text [sn], determined by the MT manufacturer, which is intended to permit the user of the TA to identify the individual MT to which it is connected to. Typically, the text will consist of a single line containing the IMEI (International Mobile station Equipment Identity; refer 3GPP TS 23.003 [7]) number of the MT, but manufacturers may choose to provide more information if desired. Refer subclause 9.2 for possible [err] values. |
| Defined values |
| [sn]: the total number of characters, including line terminators, in the information text shall not exceed 2048 characters. |
| Text shall not contain the sequence 0[CR] or OK[CR] |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSCS=</command> |
| <profile>Select TE character set (Assign)</profile> |
| <description>Set command informs TA which character set [chset] is used by the TE. TA is then able to convert character strings correctly between TE and MT character sets. |
| When TA‑TE interface is set to 8‑bit operation and used TE alphabet is 7‑bit, the highest bit shall be set to zero. |
| NOTE 1: It is manufacturer specific how the internal alphabet of MT is converted to/from the TE alphabet. |
| Read command shows current setting and test command displays conversion schemes implemented in the TA. |
| Defined values |
| [chset] (conversion schemes not listed here can be defined by manufacturers): |
| 'GSM' GSM 7 bit default alphabet (3GPP TS 23.038 [25]); this setting causes easily software flow control (XON/XOFF) problems. |
| 'HEX' Character strings consist only of hexadecimal numbers from 00 to FF; e.g. '032FE6' equals three 8-bit characters with decimal values 3, 47 and 230; no conversions to the original MT character set shall be done. |
| NOTE 2: If MT is using GSM 7 bit default alphabet, its characters shall be padded with 8th bit (zero) before converting them to hexadecimal numbers (i.e. no SMS‑style packing of 7‑bit alphabet). |
| 'IRA' International reference alphabet (ITU‑T T.50 [13]). |
| 'PCCPxxx' PC character set Code Page xxx |
| 'PCDN' PC Danish/Norwegian character set |
| 'UCS2' 16-bit universal multiple-octet coded character set (ISO/IEC10646 [32]); UCS2 character strings are converted to hexadecimal numbers from 0000 to FFFF; e.g. '004100620063' equals three 16-bit characters with decimal values 65, 98 and 99. |
| 'UTF-8' Octet (8-bit) lossless encoding of UCS characters (RFC 3629 [69]); UTF-8 encodes each UCS character as a variable number of octets, where the number of octets depends on the integer value assigned to the UCS character. The input format shall be a stream of octets. It shall not be converted to hexadecimal numbers as in 'HEX' or 'UCS2'. This character set requires an 8-bit TA – TE interface. |
| '8859-n' ISO 8859 Latin n (1‑6) character set |
| '8859-C' ISO 8859 Latin/Cyrillic character set |
| '8859-A' ISO 8859 Latin/Arabic character set |
| '8859-G' ISO 8859 Latin/Greek character set |
| '8859-H' ISO 8859 Latin/Hebrew character set |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSCS?</command> |
| <profile>Select TE character set (Query)</profile> |
| <description>Set command informs TA which character set [chset] is used by the TE. TA is then able to convert character strings correctly between TE and MT character sets. |
| When TA‑TE interface is set to 8‑bit operation and used TE alphabet is 7‑bit, the highest bit shall be set to zero. |
| NOTE 1: It is manufacturer specific how the internal alphabet of MT is converted to/from the TE alphabet. |
| Read command shows current setting and test command displays conversion schemes implemented in the TA. |
| Defined values |
| [chset] (conversion schemes not listed here can be defined by manufacturers): |
| 'GSM' GSM 7 bit default alphabet (3GPP TS 23.038 [25]); this setting causes easily software flow control (XON/XOFF) problems. |
| 'HEX' Character strings consist only of hexadecimal numbers from 00 to FF; e.g. '032FE6' equals three 8-bit characters with decimal values 3, 47 and 230; no conversions to the original MT character set shall be done. |
| NOTE 2: If MT is using GSM 7 bit default alphabet, its characters shall be padded with 8th bit (zero) before converting them to hexadecimal numbers (i.e. no SMS‑style packing of 7‑bit alphabet). |
| 'IRA' International reference alphabet (ITU‑T T.50 [13]). |
| 'PCCPxxx' PC character set Code Page xxx |
| 'PCDN' PC Danish/Norwegian character set |
| 'UCS2' 16-bit universal multiple-octet coded character set (ISO/IEC10646 [32]); UCS2 character strings are converted to hexadecimal numbers from 0000 to FFFF; e.g. '004100620063' equals three 16-bit characters with decimal values 65, 98 and 99. |
| 'UTF-8' Octet (8-bit) lossless encoding of UCS characters (RFC 3629 [69]); UTF-8 encodes each UCS character as a variable number of octets, where the number of octets depends on the integer value assigned to the UCS character. The input format shall be a stream of octets. It shall not be converted to hexadecimal numbers as in 'HEX' or 'UCS2'. This character set requires an 8-bit TA – TE interface. |
| '8859-n' ISO 8859 Latin n (1‑6) character set |
| '8859-C' ISO 8859 Latin/Cyrillic character set |
| '8859-A' ISO 8859 Latin/Arabic character set |
| '8859-G' ISO 8859 Latin/Greek character set |
| '8859-H' ISO 8859 Latin/Hebrew character set |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSCS=?</command> |
| <profile>Select TE character set (Query all)</profile> |
| <description>Set command informs TA which character set [chset] is used by the TE. TA is then able to convert character strings correctly between TE and MT character sets. |
| When TA‑TE interface is set to 8‑bit operation and used TE alphabet is 7‑bit, the highest bit shall be set to zero. |
| NOTE 1: It is manufacturer specific how the internal alphabet of MT is converted to/from the TE alphabet. |
| Read command shows current setting and test command displays conversion schemes implemented in the TA. |
| Defined values |
| [chset] (conversion schemes not listed here can be defined by manufacturers): |
| 'GSM' GSM 7 bit default alphabet (3GPP TS 23.038 [25]); this setting causes easily software flow control (XON/XOFF) problems. |
| 'HEX' Character strings consist only of hexadecimal numbers from 00 to FF; e.g. '032FE6' equals three 8-bit characters with decimal values 3, 47 and 230; no conversions to the original MT character set shall be done. |
| NOTE 2: If MT is using GSM 7 bit default alphabet, its characters shall be padded with 8th bit (zero) before converting them to hexadecimal numbers (i.e. no SMS‑style packing of 7‑bit alphabet). |
| 'IRA' International reference alphabet (ITU‑T T.50 [13]). |
| 'PCCPxxx' PC character set Code Page xxx |
| 'PCDN' PC Danish/Norwegian character set |
| 'UCS2' 16-bit universal multiple-octet coded character set (ISO/IEC10646 [32]); UCS2 character strings are converted to hexadecimal numbers from 0000 to FFFF; e.g. '004100620063' equals three 16-bit characters with decimal values 65, 98 and 99. |
| 'UTF-8' Octet (8-bit) lossless encoding of UCS characters (RFC 3629 [69]); UTF-8 encodes each UCS character as a variable number of octets, where the number of octets depends on the integer value assigned to the UCS character. The input format shall be a stream of octets. It shall not be converted to hexadecimal numbers as in 'HEX' or 'UCS2'. This character set requires an 8-bit TA – TE interface. |
| '8859-n' ISO 8859 Latin n (1‑6) character set |
| '8859-C' ISO 8859 Latin/Cyrillic character set |
| '8859-A' ISO 8859 Latin/Arabic character set |
| '8859-G' ISO 8859 Latin/Greek character set |
| '8859-H' ISO 8859 Latin/Hebrew character set |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CIMI</command> |
| <profile>Request international mobile subscriber identity </profile> |
| <description>Execution command causes the TA to return [IMSI], which is intended to permit the TE to identify the individual SIM card or active application in the UICC (GSM or USIM) which is attached to MT. Refer subclause 9.2 for possible [err] values. |
| Defined values |
| [IMSI]: International Mobile Subscriber Identity (string without double quotes) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CIMI=?</command> |
| <profile>Request international mobile subscriber identity (Query all)</profile> |
| <description>Execution command causes the TA to return [IMSI], which is intended to permit the TE to identify the individual SIM card or active application in the UICC (GSM or USIM) which is attached to MT. Refer subclause 9.2 for possible [err] values. |
| Defined values |
| [IMSI]: International Mobile Subscriber Identity (string without double quotes) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CMUX=</command> |
| <profile>Multiplexing mode (Assign)</profile> |
| <description>This command is used to enable/disable the 3GPP TS 27.010 [45] multiplexing protocol control channel. Refer to subclause 9.2 for possible [err] values. The AT command sets parameters for the Control Channel. If the parameters are left out, the default value is used. |
| Read command returns the current mode and the settings. |
| Test command returns the supported modes and parameters. |
| It is recommended that the MT/TA/TE should autobaud to the +CMUX command up to and including an interface speed of 9600 bits/s. |
| The OK or +CME ERROR: [err] response is returned at the speed of the +CMUX command prior to entering [mode]. |
| It is recommended that whenever the multiplexer control channel is released the MT/TA/TE should assume an interface rate of up to and including 9600 bits/s for auto bauding purposes irrespective of any previous higher speed having been selected. |
| If a +CMUX command is issued whilst in any multiplexer mode then that +CMUX command shall be ignored and the MT/TA shall return an +CME ERROR: [err] response. |
| Defined values |
| [operation] (multiplexer Transparency Mechanism) |
| 0 Basic option |
| 1 Advanced option |
| [subset]: |
| This parameter defines the way in which the multiplexer control channel is set up. A virtual channel may subsequently be set up differently but in the absence of any negotiation for the settings of a virtual channel, the virtual channel shall be set up according to the control channel [subset] setting. |
| 0 UIH frames used only |
| 1 UI frames used only |
| 2 I frames used only |
| Default value: 0 |
| [port_speed] (transmission rate): |
| 1 9 600 bit/s |
| 2 19 200 bit/s |
| 3 38 400 bit/s |
| 4 57 600 bit/s |
| 5 115 200 bit/s |
| 6 230 400 bits/s |
| [N1] (maximum frame size): |
| 1- 32768 |
| default Value : 31 (64 if Advanced option is used) |
| [T1] (acknowledgement timer in units of ten milliseconds): |
| 1-255, where 10 is default (100 ms) |
| [N2] (maximum number of re-transmissions): |
| 0-100, where 3 is default |
| [T2] (response timer for the multiplexer control channel in units of ten milliseconds): |
| 2-255, where 30 is default (300 ms) |
| NOTE: T2 must be longer than T1. |
| [T3] (wake up response timer in seconds): |
| 1-255, where 10 is default |
| [k] (window size, for Advanced operation with Error Recovery options): |
| 1-7, where 2 is default |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CMUX?</command> |
| <profile>Multiplexing mode (Query)</profile> |
| <description>This command is used to enable/disable the 3GPP TS 27.010 [45] multiplexing protocol control channel. Refer to subclause 9.2 for possible [err] values. The AT command sets parameters for the Control Channel. If the parameters are left out, the default value is used. |
| Read command returns the current mode and the settings. |
| Test command returns the supported modes and parameters. |
| It is recommended that the MT/TA/TE should autobaud to the +CMUX command up to and including an interface speed of 9600 bits/s. |
| The OK or +CME ERROR: [err] response is returned at the speed of the +CMUX command prior to entering [mode]. |
| It is recommended that whenever the multiplexer control channel is released the MT/TA/TE should assume an interface rate of up to and including 9600 bits/s for auto bauding purposes irrespective of any previous higher speed having been selected. |
| If a +CMUX command is issued whilst in any multiplexer mode then that +CMUX command shall be ignored and the MT/TA shall return an +CME ERROR: [err] response. |
| Defined values |
| [operation] (multiplexer Transparency Mechanism) |
| 0 Basic option |
| 1 Advanced option |
| [subset]: |
| This parameter defines the way in which the multiplexer control channel is set up. A virtual channel may subsequently be set up differently but in the absence of any negotiation for the settings of a virtual channel, the virtual channel shall be set up according to the control channel [subset] setting. |
| 0 UIH frames used only |
| 1 UI frames used only |
| 2 I frames used only |
| Default value: 0 |
| [port_speed] (transmission rate): |
| 1 9 600 bit/s |
| 2 19 200 bit/s |
| 3 38 400 bit/s |
| 4 57 600 bit/s |
| 5 115 200 bit/s |
| 6 230 400 bits/s |
| [N1] (maximum frame size): |
| 1- 32768 |
| default Value : 31 (64 if Advanced option is used) |
| [T1] (acknowledgement timer in units of ten milliseconds): |
| 1-255, where 10 is default (100 ms) |
| [N2] (maximum number of re-transmissions): |
| 0-100, where 3 is default |
| [T2] (response timer for the multiplexer control channel in units of ten milliseconds): |
| 2-255, where 30 is default (300 ms) |
| NOTE: T2 must be longer than T1. |
| [T3] (wake up response timer in seconds): |
| 1-255, where 10 is default |
| [k] (window size, for Advanced operation with Error Recovery options): |
| 1-7, where 2 is default |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CMUX=?</command> |
| <profile>Multiplexing mode (Query all)</profile> |
| <description>This command is used to enable/disable the 3GPP TS 27.010 [45] multiplexing protocol control channel. Refer to subclause 9.2 for possible [err] values. The AT command sets parameters for the Control Channel. If the parameters are left out, the default value is used. |
| Read command returns the current mode and the settings. |
| Test command returns the supported modes and parameters. |
| It is recommended that the MT/TA/TE should autobaud to the +CMUX command up to and including an interface speed of 9600 bits/s. |
| The OK or +CME ERROR: [err] response is returned at the speed of the +CMUX command prior to entering [mode]. |
| It is recommended that whenever the multiplexer control channel is released the MT/TA/TE should assume an interface rate of up to and including 9600 bits/s for auto bauding purposes irrespective of any previous higher speed having been selected. |
| If a +CMUX command is issued whilst in any multiplexer mode then that +CMUX command shall be ignored and the MT/TA shall return an +CME ERROR: [err] response. |
| Defined values |
| [operation] (multiplexer Transparency Mechanism) |
| 0 Basic option |
| 1 Advanced option |
| [subset]: |
| This parameter defines the way in which the multiplexer control channel is set up. A virtual channel may subsequently be set up differently but in the absence of any negotiation for the settings of a virtual channel, the virtual channel shall be set up according to the control channel [subset] setting. |
| 0 UIH frames used only |
| 1 UI frames used only |
| 2 I frames used only |
| Default value: 0 |
| [port_speed] (transmission rate): |
| 1 9 600 bit/s |
| 2 19 200 bit/s |
| 3 38 400 bit/s |
| 4 57 600 bit/s |
| 5 115 200 bit/s |
| 6 230 400 bits/s |
| [N1] (maximum frame size): |
| 1- 32768 |
| default Value : 31 (64 if Advanced option is used) |
| [T1] (acknowledgement timer in units of ten milliseconds): |
| 1-255, where 10 is default (100 ms) |
| [N2] (maximum number of re-transmissions): |
| 0-100, where 3 is default |
| [T2] (response timer for the multiplexer control channel in units of ten milliseconds): |
| 2-255, where 30 is default (300 ms) |
| NOTE: T2 must be longer than T1. |
| [T3] (wake up response timer in seconds): |
| 1-255, where 10 is default |
| [k] (window size, for Advanced operation with Error Recovery options): |
| 1-7, where 2 is default |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSTA=</command> |
| <profile>Select type of address (Assign)</profile> |
| <description>Set command selects the type of number for further dialling commands (D) according to GSM/UMTS specifications. Test command returns values supported a compound value. |
| Defined values |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7); default 145 when dialling string includes international access code character '+', otherwise 129 |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSTA?</command> |
| <profile>Select type of address (Query)</profile> |
| <description>Set command selects the type of number for further dialling commands (D) according to GSM/UMTS specifications. Test command returns values supported a compound value. |
| Defined values |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7); default 145 when dialling string includes international access code character '+', otherwise 129 |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSTA=?</command> |
| <profile>Select type of address (Query all)</profile> |
| <description>Set command selects the type of number for further dialling commands (D) according to GSM/UMTS specifications. Test command returns values supported a compound value. |
| Defined values |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7); default 145 when dialling string includes international access code character '+', otherwise 129 |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CMOD=</command> |
| <profile>Call mode (Assign)</profile> |
| <description>Set command selects the call mode of further dialling commands (D) or for next answering command (A). Mode can be either single or alternating (in the present document, terms 'alternating mode' and 'alternating call' refer to all GSM/UMTS bearer and teleservices that incorporate more than one basic service (voice, data, fax) within one call). When single mode is selected the call originating and hangup procedures are similar to procedures specified in ITU‑T Recommendations V.250 [14], T.31 [11] and T.32 [12]. In GSM/UMTS there can be voice followed by data (refer 3GPP TS 22.002 [1]), alternating voice/data (refer 3GPP TS 22.002 [1]) and alternating voice/fax calls (refer 3GPP TS 22.003 [2]). Refer next two subclauses for alternating call control methods. |
| Test command returns values supported as a compound value. |
| NOTE: +CMOD shall be set to zero after a successfully completed alternating mode call. It shall be set to zero also after a failed answering. The power‑up, factory (:F) and user resets (Z) shall also set the value to zero. This reduces the possibility that alternating mode calls are originated or answered accidentally. |
| Defined values |
| [mode]: |
| 0 single mode |
| 1 alternating voice/fax (teleservice 61) |
| 2 alternating voice/data (bearer service 61) |
| 3 voice followed by data (bearer service 81) |
| also all other values below 128 are reserved by the present document |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CMOD?</command> |
| <profile>Call mode (Query)</profile> |
| <description>Set command selects the call mode of further dialling commands (D) or for next answering command (A). Mode can be either single or alternating (in the present document, terms 'alternating mode' and 'alternating call' refer to all GSM/UMTS bearer and teleservices that incorporate more than one basic service (voice, data, fax) within one call). When single mode is selected the call originating and hangup procedures are similar to procedures specified in ITU‑T Recommendations V.250 [14], T.31 [11] and T.32 [12]. In GSM/UMTS there can be voice followed by data (refer 3GPP TS 22.002 [1]), alternating voice/data (refer 3GPP TS 22.002 [1]) and alternating voice/fax calls (refer 3GPP TS 22.003 [2]). Refer next two subclauses for alternating call control methods. |
| Test command returns values supported as a compound value. |
| NOTE: +CMOD shall be set to zero after a successfully completed alternating mode call. It shall be set to zero also after a failed answering. The power‑up, factory (:F) and user resets (Z) shall also set the value to zero. This reduces the possibility that alternating mode calls are originated or answered accidentally. |
| Defined values |
| [mode]: |
| 0 single mode |
| 1 alternating voice/fax (teleservice 61) |
| 2 alternating voice/data (bearer service 61) |
| 3 voice followed by data (bearer service 81) |
| also all other values below 128 are reserved by the present document |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CMOD=?</command> |
| <profile>Call mode (Query all)</profile> |
| <description>Set command selects the call mode of further dialling commands (D) or for next answering command (A). Mode can be either single or alternating (in the present document, terms 'alternating mode' and 'alternating call' refer to all GSM/UMTS bearer and teleservices that incorporate more than one basic service (voice, data, fax) within one call). When single mode is selected the call originating and hangup procedures are similar to procedures specified in ITU‑T Recommendations V.250 [14], T.31 [11] and T.32 [12]. In GSM/UMTS there can be voice followed by data (refer 3GPP TS 22.002 [1]), alternating voice/data (refer 3GPP TS 22.002 [1]) and alternating voice/fax calls (refer 3GPP TS 22.003 [2]). Refer next two subclauses for alternating call control methods. |
| Test command returns values supported as a compound value. |
| NOTE: +CMOD shall be set to zero after a successfully completed alternating mode call. It shall be set to zero also after a failed answering. The power‑up, factory (:F) and user resets (Z) shall also set the value to zero. This reduces the possibility that alternating mode calls are originated or answered accidentally. |
| Defined values |
| [mode]: |
| 0 single mode |
| 1 alternating voice/fax (teleservice 61) |
| 2 alternating voice/data (bearer service 61) |
| 3 voice followed by data (bearer service 81) |
| also all other values below 128 are reserved by the present document |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CHUP</command> |
| <profile>Hangup call </profile> |
| <description>Execution command causes the TA to hangup the current GSM/UMTS call of the MT. |
| NOTE: The purpose of this command is not to replace the V.250 [14] command H, but to give an assured procedure to terminate an alternating mode call. Refer next subclause. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CHUP=?</command> |
| <profile>Hangup call (Query all)</profile> |
| <description>Execution command causes the TA to hangup the current GSM/UMTS call of the MT. |
| NOTE: The purpose of this command is not to replace the V.250 [14] command H, but to give an assured procedure to terminate an alternating mode call. Refer next subclause. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CBST=</command> |
| <profile>Select bearer service type (Assign)</profile> |
| <description>Set command selects the bearer service [name] with data rate [speed], and the connection element [ce] to be used when data calls are originated (refer 3GPP TS 22.002 [1]). Values may also be used during mobile terminated data call setup, especially in case of single numbering scheme calls (refer +CSNS). |
| Test command returns values supported as compound values. |
| Defined values |
| NOTE: The default values of the subparameters are manufacturer specific since they depend on the purpose of the device and data services provided by it. Not all combinations of these subparameters are supported by GSM/UMTS (refer 3GPP TS 22.002 [1]). |
| [speed]: |
| 0 autobauding (automatic selection of the speed; this setting is possible in case of 3.1 kHz modem and non-transparent service) |
| 1 300 bps (V.21) |
| 2 1200 bps (V.22) |
| 3 1200/75 bps (V.23) |
| 4 2400 bps (V.22bis) |
| 5 2400 bps (V.26ter) |
| 6 4800 bps (V.32) |
| 7 9600 bps (V.32) |
| 12 9600 bps (V.34) |
| 14 14400 bps (V.34) |
| 15 19200 bps (V.34) |
| 16 28800 bps (V.34) |
| 17 33600 bps (V.34) |
| 34 1200 bps (V.120) |
| 36 2400 bps (V.120) |
| 38 4800 bps (V.120) |
| 39 9600 bps (V.120) |
| 43 14400 bps (V.120) |
| 47 19200 bps (V.120) |
| 48 28800 bps (V.120) |
| 49 38400 bps (V.120) |
| 50 48000 bps (V.120) |
| 51 56000 bps (V.120) |
| 65 300 bps (V.110) |
| 66 1200 bps (V.110) |
| 68 2400 bps (V.110 or X.31 flag stuffing) |
| 70 4800 bps (V.110 or X.31 flag stuffing) |
| 71 9600 bps (V.110 or X.31 flag stuffing) |
| 75 14400 bps (V.110 or X.31 flag stuffing) |
| 79 19200 bps (V.110 or X.31 flag stuffing) |
| 80 28800 bps (V.110 or X.31 flag stuffing) |
| 81 38400 bps (V.110 or X.31 flag stuffing) |
| 82 48000 bps (V.110 or X.31 flag stuffing) |
| 83 56000 bps (V.110 or X.31 flag stuffing; this setting can be used in conjunction with asynchronous non-transparent UDI or RDI service in order to get FTM) |
| 84 64000 bps (X.31 flag stuffing; this setting can be used in conjunction with asynchronous non-transparent UDI service in order to get FTM) |
| 115 56000 bps (bit transparent) |
| 116 64000 bps (bit transparent) |
| 120 32000 bps (PIAFS32k) |
| 121 64000 bps (PIAFS64k) |
| 130 28800 bps (multimedia) |
| 131 32000 bps (multimedia) |
| 132 33600 bps (multimedia) |
| 133 56000 bps (multimedia) |
| 134 64000 bps (multimedia) |
| |
| also all other values below 128 are reserved by the present document. |
| [name]: |
| 0 data circuit asynchronous (UDI or 3.1 kHz modem) |
| 1 data circuit synchronous (UDI or 3.1 kHz modem) |
| 2 PAD Access (asynchronous) (UDI) |
| 3 Packet Access (synchronous) (UDI) |
| 4 data circuit asynchronous (RDI) |
| 5 data circuit synchronous (RDI) |
| 6 PAD Access (asynchronous) (RDI) |
| 7 Packet Access (synchronous) (RDI) |
| also all other values below 128 are reserved by the present document. |
| [ce]: |
| 0 transparent |
| 1 non-transparent |
| 2 both, transparent preferred |
| 3 both, non-transparent preferred |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CBST?</command> |
| <profile>Select bearer service type (Query)</profile> |
| <description>Set command selects the bearer service [name] with data rate [speed], and the connection element [ce] to be used when data calls are originated (refer 3GPP TS 22.002 [1]). Values may also be used during mobile terminated data call setup, especially in case of single numbering scheme calls (refer +CSNS). |
| Test command returns values supported as compound values. |
| Defined values |
| NOTE: The default values of the subparameters are manufacturer specific since they depend on the purpose of the device and data services provided by it. Not all combinations of these subparameters are supported by GSM/UMTS (refer 3GPP TS 22.002 [1]). |
| [speed]: |
| 0 autobauding (automatic selection of the speed; this setting is possible in case of 3.1 kHz modem and non-transparent service) |
| 1 300 bps (V.21) |
| 2 1200 bps (V.22) |
| 3 1200/75 bps (V.23) |
| 4 2400 bps (V.22bis) |
| 5 2400 bps (V.26ter) |
| 6 4800 bps (V.32) |
| 7 9600 bps (V.32) |
| 12 9600 bps (V.34) |
| 14 14400 bps (V.34) |
| 15 19200 bps (V.34) |
| 16 28800 bps (V.34) |
| 17 33600 bps (V.34) |
| 34 1200 bps (V.120) |
| 36 2400 bps (V.120) |
| 38 4800 bps (V.120) |
| 39 9600 bps (V.120) |
| 43 14400 bps (V.120) |
| 47 19200 bps (V.120) |
| 48 28800 bps (V.120) |
| 49 38400 bps (V.120) |
| 50 48000 bps (V.120) |
| 51 56000 bps (V.120) |
| 65 300 bps (V.110) |
| 66 1200 bps (V.110) |
| 68 2400 bps (V.110 or X.31 flag stuffing) |
| 70 4800 bps (V.110 or X.31 flag stuffing) |
| 71 9600 bps (V.110 or X.31 flag stuffing) |
| 75 14400 bps (V.110 or X.31 flag stuffing) |
| 79 19200 bps (V.110 or X.31 flag stuffing) |
| 80 28800 bps (V.110 or X.31 flag stuffing) |
| 81 38400 bps (V.110 or X.31 flag stuffing) |
| 82 48000 bps (V.110 or X.31 flag stuffing) |
| 83 56000 bps (V.110 or X.31 flag stuffing; this setting can be used in conjunction with asynchronous non-transparent UDI or RDI service in order to get FTM) |
| 84 64000 bps (X.31 flag stuffing; this setting can be used in conjunction with asynchronous non-transparent UDI service in order to get FTM) |
| 115 56000 bps (bit transparent) |
| 116 64000 bps (bit transparent) |
| 120 32000 bps (PIAFS32k) |
| 121 64000 bps (PIAFS64k) |
| 130 28800 bps (multimedia) |
| 131 32000 bps (multimedia) |
| 132 33600 bps (multimedia) |
| 133 56000 bps (multimedia) |
| 134 64000 bps (multimedia) |
| |
| also all other values below 128 are reserved by the present document. |
| [name]: |
| 0 data circuit asynchronous (UDI or 3.1 kHz modem) |
| 1 data circuit synchronous (UDI or 3.1 kHz modem) |
| 2 PAD Access (asynchronous) (UDI) |
| 3 Packet Access (synchronous) (UDI) |
| 4 data circuit asynchronous (RDI) |
| 5 data circuit synchronous (RDI) |
| 6 PAD Access (asynchronous) (RDI) |
| 7 Packet Access (synchronous) (RDI) |
| also all other values below 128 are reserved by the present document. |
| [ce]: |
| 0 transparent |
| 1 non-transparent |
| 2 both, transparent preferred |
| 3 both, non-transparent preferred |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CBST=?</command> |
| <profile>Select bearer service type (Query all)</profile> |
| <description>Set command selects the bearer service [name] with data rate [speed], and the connection element [ce] to be used when data calls are originated (refer 3GPP TS 22.002 [1]). Values may also be used during mobile terminated data call setup, especially in case of single numbering scheme calls (refer +CSNS). |
| Test command returns values supported as compound values. |
| Defined values |
| NOTE: The default values of the subparameters are manufacturer specific since they depend on the purpose of the device and data services provided by it. Not all combinations of these subparameters are supported by GSM/UMTS (refer 3GPP TS 22.002 [1]). |
| [speed]: |
| 0 autobauding (automatic selection of the speed; this setting is possible in case of 3.1 kHz modem and non-transparent service) |
| 1 300 bps (V.21) |
| 2 1200 bps (V.22) |
| 3 1200/75 bps (V.23) |
| 4 2400 bps (V.22bis) |
| 5 2400 bps (V.26ter) |
| 6 4800 bps (V.32) |
| 7 9600 bps (V.32) |
| 12 9600 bps (V.34) |
| 14 14400 bps (V.34) |
| 15 19200 bps (V.34) |
| 16 28800 bps (V.34) |
| 17 33600 bps (V.34) |
| 34 1200 bps (V.120) |
| 36 2400 bps (V.120) |
| 38 4800 bps (V.120) |
| 39 9600 bps (V.120) |
| 43 14400 bps (V.120) |
| 47 19200 bps (V.120) |
| 48 28800 bps (V.120) |
| 49 38400 bps (V.120) |
| 50 48000 bps (V.120) |
| 51 56000 bps (V.120) |
| 65 300 bps (V.110) |
| 66 1200 bps (V.110) |
| 68 2400 bps (V.110 or X.31 flag stuffing) |
| 70 4800 bps (V.110 or X.31 flag stuffing) |
| 71 9600 bps (V.110 or X.31 flag stuffing) |
| 75 14400 bps (V.110 or X.31 flag stuffing) |
| 79 19200 bps (V.110 or X.31 flag stuffing) |
| 80 28800 bps (V.110 or X.31 flag stuffing) |
| 81 38400 bps (V.110 or X.31 flag stuffing) |
| 82 48000 bps (V.110 or X.31 flag stuffing) |
| 83 56000 bps (V.110 or X.31 flag stuffing; this setting can be used in conjunction with asynchronous non-transparent UDI or RDI service in order to get FTM) |
| 84 64000 bps (X.31 flag stuffing; this setting can be used in conjunction with asynchronous non-transparent UDI service in order to get FTM) |
| 115 56000 bps (bit transparent) |
| 116 64000 bps (bit transparent) |
| 120 32000 bps (PIAFS32k) |
| 121 64000 bps (PIAFS64k) |
| 130 28800 bps (multimedia) |
| 131 32000 bps (multimedia) |
| 132 33600 bps (multimedia) |
| 133 56000 bps (multimedia) |
| 134 64000 bps (multimedia) |
| |
| also all other values below 128 are reserved by the present document. |
| [name]: |
| 0 data circuit asynchronous (UDI or 3.1 kHz modem) |
| 1 data circuit synchronous (UDI or 3.1 kHz modem) |
| 2 PAD Access (asynchronous) (UDI) |
| 3 Packet Access (synchronous) (UDI) |
| 4 data circuit asynchronous (RDI) |
| 5 data circuit synchronous (RDI) |
| 6 PAD Access (asynchronous) (RDI) |
| 7 Packet Access (synchronous) (RDI) |
| also all other values below 128 are reserved by the present document. |
| [ce]: |
| 0 transparent |
| 1 non-transparent |
| 2 both, transparent preferred |
| 3 both, non-transparent preferred |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CRLP=</command> |
| <profile>Radio link protocol (Assign)</profile> |
| <description>Radio link protocol (RLP) parameters used when non-transparent data calls are originated may be altered with set command. Available command subparameters depend on the RLP versions implemented by the device (e.g. [ver] may not be available if device supports only versions 0 and 1). |
| NOTE 1: If radio link protocol is not used, but some other error correcting protocol (for transparent data calls), V.250 [14] Error Control Selection test command +ES=? may be used to indicate the presence of the protocol. |
| Read command returns current settings for each supported RLP version [verx]. Only RLP parameters applicable to the corresponding [verx] are returned. |
| Test command returns values supported as a compound value. If MT/TA supports several RLP versions [verx], the RLP parameter value ranges for each [verx] are returned in a separate line. |
| Defined values |
| [ver], [verx]: RLP version number in integer format; when version indication is not present it shall equal 0 |
| NOTE 2: Versions 0 and 1 share the same parameter set. Read and test commands shall return only one line for this set (where [verx] is not present). |
| [iws], [mws], [T1], [N2], [T4]: IWF to MS window size, MS to IWF window size, acknowledgement timer T1, retransmission attempts N2, re-sequencing period T4 in integer format (default values and value ranges depend on RLP version; refer 3GPP TS 24.022 [18]): T1 and T4 are in units of 10 ms. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CRLP?</command> |
| <profile>Radio link protocol (Query)</profile> |
| <description>Radio link protocol (RLP) parameters used when non-transparent data calls are originated may be altered with set command. Available command subparameters depend on the RLP versions implemented by the device (e.g. [ver] may not be available if device supports only versions 0 and 1). |
| NOTE 1: If radio link protocol is not used, but some other error correcting protocol (for transparent data calls), V.250 [14] Error Control Selection test command +ES=? may be used to indicate the presence of the protocol. |
| Read command returns current settings for each supported RLP version [verx]. Only RLP parameters applicable to the corresponding [verx] are returned. |
| Test command returns values supported as a compound value. If MT/TA supports several RLP versions [verx], the RLP parameter value ranges for each [verx] are returned in a separate line. |
| Defined values |
| [ver], [verx]: RLP version number in integer format; when version indication is not present it shall equal 0 |
| NOTE 2: Versions 0 and 1 share the same parameter set. Read and test commands shall return only one line for this set (where [verx] is not present). |
| [iws], [mws], [T1], [N2], [T4]: IWF to MS window size, MS to IWF window size, acknowledgement timer T1, retransmission attempts N2, re-sequencing period T4 in integer format (default values and value ranges depend on RLP version; refer 3GPP TS 24.022 [18]): T1 and T4 are in units of 10 ms. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CRLP=?</command> |
| <profile>Radio link protocol (Query all)</profile> |
| <description>Radio link protocol (RLP) parameters used when non-transparent data calls are originated may be altered with set command. Available command subparameters depend on the RLP versions implemented by the device (e.g. [ver] may not be available if device supports only versions 0 and 1). |
| NOTE 1: If radio link protocol is not used, but some other error correcting protocol (for transparent data calls), V.250 [14] Error Control Selection test command +ES=? may be used to indicate the presence of the protocol. |
| Read command returns current settings for each supported RLP version [verx]. Only RLP parameters applicable to the corresponding [verx] are returned. |
| Test command returns values supported as a compound value. If MT/TA supports several RLP versions [verx], the RLP parameter value ranges for each [verx] are returned in a separate line. |
| Defined values |
| [ver], [verx]: RLP version number in integer format; when version indication is not present it shall equal 0 |
| NOTE 2: Versions 0 and 1 share the same parameter set. Read and test commands shall return only one line for this set (where [verx] is not present). |
| [iws], [mws], [T1], [N2], [T4]: IWF to MS window size, MS to IWF window size, acknowledgement timer T1, retransmission attempts N2, re-sequencing period T4 in integer format (default values and value ranges depend on RLP version; refer 3GPP TS 24.022 [18]): T1 and T4 are in units of 10 ms. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CR=</command> |
| <profile>Service reporting control (Assign)</profile> |
| <description>Set command controls whether or not intermediate result code +CR: [serv] is returned from the TA to the TE. If enabled, the intermediate result code is transmitted at the point during connect negotiation at which the TA has determined which speed and quality of service will be used, before any error control or data compression reports are transmitted, and before the intermediate result code CONNECT is transmitted. |
| NOTE: This command replaces V.250 [14] command Modulation Reporting Control +MR, which is not appropriate for use in the GSM/UMTS network. Possible error control (other than radio link protocol) and data compression reporting can be enabled with V.250 commands Error Control Reporting +ER and Data Compression Reporting +DR. |
| Test command returns values supported as a compound value. |
| Defined values |
| [mode]: |
| 0 disables reporting |
| 1 enables reporting |
| [serv]: |
| ASYNC asynchronous transparent |
| SYNC synchronous transparent |
| REL ASYNC asynchronous non‑transparent |
| REL SYNC synchronous non‑transparent |
| GPRS [[L2P]] GPRS |
| The optional [L2P] proposes a layer 2 protocol to use between the MT and the TE. It is defined in the Enter GPRS Data Mode (+CGDATA) command. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CR?</command> |
| <profile>Service reporting control (Query)</profile> |
| <description>Set command controls whether or not intermediate result code +CR: [serv] is returned from the TA to the TE. If enabled, the intermediate result code is transmitted at the point during connect negotiation at which the TA has determined which speed and quality of service will be used, before any error control or data compression reports are transmitted, and before the intermediate result code CONNECT is transmitted. |
| NOTE: This command replaces V.250 [14] command Modulation Reporting Control +MR, which is not appropriate for use in the GSM/UMTS network. Possible error control (other than radio link protocol) and data compression reporting can be enabled with V.250 commands Error Control Reporting +ER and Data Compression Reporting +DR. |
| Test command returns values supported as a compound value. |
| Defined values |
| [mode]: |
| 0 disables reporting |
| 1 enables reporting |
| [serv]: |
| ASYNC asynchronous transparent |
| SYNC synchronous transparent |
| REL ASYNC asynchronous non‑transparent |
| REL SYNC synchronous non‑transparent |
| GPRS [[L2P]] GPRS |
| The optional [L2P] proposes a layer 2 protocol to use between the MT and the TE. It is defined in the Enter GPRS Data Mode (+CGDATA) command. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CR=?</command> |
| <profile>Service reporting control (Query all)</profile> |
| <description>Set command controls whether or not intermediate result code +CR: [serv] is returned from the TA to the TE. If enabled, the intermediate result code is transmitted at the point during connect negotiation at which the TA has determined which speed and quality of service will be used, before any error control or data compression reports are transmitted, and before the intermediate result code CONNECT is transmitted. |
| NOTE: This command replaces V.250 [14] command Modulation Reporting Control +MR, which is not appropriate for use in the GSM/UMTS network. Possible error control (other than radio link protocol) and data compression reporting can be enabled with V.250 commands Error Control Reporting +ER and Data Compression Reporting +DR. |
| Test command returns values supported as a compound value. |
| Defined values |
| [mode]: |
| 0 disables reporting |
| 1 enables reporting |
| [serv]: |
| ASYNC asynchronous transparent |
| SYNC synchronous transparent |
| REL ASYNC asynchronous non‑transparent |
| REL SYNC synchronous non‑transparent |
| GPRS [[L2P]] GPRS |
| The optional [L2P] proposes a layer 2 protocol to use between the MT and the TE. It is defined in the Enter GPRS Data Mode (+CGDATA) command. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CEER</command> |
| <profile>Extended error report </profile> |
| <description>Execution command causes the TA to return one or more lines of information text [report], determined by the MT manufacturer, which should offer the user of the TA an extended report of the reason for |
| - the failure in the last unsuccessful call setup (originating or answering) or in‑call modification; |
| - the last call release; |
| - the last unsuccessful GPRS attach or unsuccessful PDP context activation; |
| - the last GPRS detach or PDP context deactivation. |
| Typically, the text will consist of a single line containing the cause information given by GSM/UMTS network in textual format. |
| Defined values |
| [report]: the total number of characters, including line terminators, in the information text shall not exceed 2041 characters. |
| Text shall not contain the sequence 0[CR] or OK[CR]. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CEER=?</command> |
| <profile>Extended error report (Query all)</profile> |
| <description>Execution command causes the TA to return one or more lines of information text [report], determined by the MT manufacturer, which should offer the user of the TA an extended report of the reason for |
| - the failure in the last unsuccessful call setup (originating or answering) or in‑call modification; |
| - the last call release; |
| - the last unsuccessful GPRS attach or unsuccessful PDP context activation; |
| - the last GPRS detach or PDP context deactivation. |
| Typically, the text will consist of a single line containing the cause information given by GSM/UMTS network in textual format. |
| Defined values |
| [report]: the total number of characters, including line terminators, in the information text shall not exceed 2041 characters. |
| Text shall not contain the sequence 0[CR] or OK[CR]. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CRC=</command> |
| <profile>Cellular result codes (Assign)</profile> |
| <description>Set command controls whether or not the extended format of incoming call indication or GPRS network request for PDP context activation or notification for VBS/VGCS calls is used. When enabled, an incoming call is indicated to the TE with unsolicited result code +CRING: [type] instead of the normal RING. |
| Test command returns values supported as a compound value. |
| NOTE: Similar command may be found in TIA IS‑99 [15] and TIA IS‑135 [16]. |
| Defined values |
| [mode]: |
| 0 disables extended format |
| 1 enables extended format |
| [type]: |
| ASYNC [,[priority][,[subaddr],[satype]]] asynchronous transparent |
| SYNC [,[priority][,[subaddr],[satype]]] synchronous transparent |
| REL ASYNC [,[priority][,[subaddr],[satype]]] asynchronous non‑transparent |
| REL SYNC [,[priority][,[subaddr],[satype]]] synchronous non‑transparent |
| FAX [,[priority][,[subaddr],[satype]]] facsimile (TS 62) |
| VOICE [,[priority][,[subaddr],[satype]]] normal voice (TS 11) |
| VOICE/XXX [,[priority][,[subaddr],[satype]]] voice followed by data (BS 81) (XXX is ASYNC, SYNC, REL ASYNC or REL SYNC) |
| ALT VOICE/XXX [,[priority][,[subaddr],[satype]]] alternating voice/data, voice first (BS 61) |
| ALT XXX/VOICE [,[priority][,[subaddr],[satype]]] alternating voice/data, data first (BS 61) |
| ALT VOICE/FAX [,[priority][,[subaddr],[satype]]] alternating voice/fax, voice first (TS 61) |
| ALT FAX/VOICE [,[priority][,[subaddr],[satype]]] alternating voice/fax, fax first (TS 61) |
| GPRS [PDP_type], [PDP_addr][, [[L2P]][,[APN]]] GPRS network request for PDP context activation |
| VGC [GCA], [GId], [ackflag] [,[priority]] voice group call (TS 91) |
| VBC [GCA], [GId], [ackflag] [,[priority]] voice broadcast call (TS 92) |
| The optional [priority] indicates the eMLPP priority level of the incoming call by paging, notification or setup message. The priority level values are as defined in eMLPP specification 3GPP TS 22.067 [54]. |
| [subaddr]: string type subaddress of format specified by [satype] |
| [satype]: type of subaddress octet in integer format (refer 3GPP TS 24.008 [8] subclause 10.5.4.8) |
| [PDP_type] ,[PDP_addr] and [APN] are as defined in the Define PDP Context (+CGDCONT) command. The optional [L2P] proposes a layer 2 protocol to use between the MT and the TE. It is defined in the Enter GPRS Data Mode (+CGDATA) command. If the MT is unable to announce to the TE the network's request (for example it is in V.250 online data state) the MT shall reject the request. No corresponding unsolicited result code shall be issued when the MT returns to a command state. |
| [GCA] is a part of the group call reference as specified in 3GPP TS 23.003 [7] and indicates group call area. |
| [GId] is a part of the group call reference as specified in 3GPP TS 23.003 [7] and indicates group call identification.The [ackflag]=1 proposes that a predefined confirmation procedure is to be used after the call is ended. For [ackflag]=0 no confirmation procedure is required. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CRC?</command> |
| <profile>Cellular result codes (Query)</profile> |
| <description>Set command controls whether or not the extended format of incoming call indication or GPRS network request for PDP context activation or notification for VBS/VGCS calls is used. When enabled, an incoming call is indicated to the TE with unsolicited result code +CRING: [type] instead of the normal RING. |
| Test command returns values supported as a compound value. |
| NOTE: Similar command may be found in TIA IS‑99 [15] and TIA IS‑135 [16]. |
| Defined values |
| [mode]: |
| 0 disables extended format |
| 1 enables extended format |
| [type]: |
| ASYNC [,[priority][,[subaddr],[satype]]] asynchronous transparent |
| SYNC [,[priority][,[subaddr],[satype]]] synchronous transparent |
| REL ASYNC [,[priority][,[subaddr],[satype]]] asynchronous non‑transparent |
| REL SYNC [,[priority][,[subaddr],[satype]]] synchronous non‑transparent |
| FAX [,[priority][,[subaddr],[satype]]] facsimile (TS 62) |
| VOICE [,[priority][,[subaddr],[satype]]] normal voice (TS 11) |
| VOICE/XXX [,[priority][,[subaddr],[satype]]] voice followed by data (BS 81) (XXX is ASYNC, SYNC, REL ASYNC or REL SYNC) |
| ALT VOICE/XXX [,[priority][,[subaddr],[satype]]] alternating voice/data, voice first (BS 61) |
| ALT XXX/VOICE [,[priority][,[subaddr],[satype]]] alternating voice/data, data first (BS 61) |
| ALT VOICE/FAX [,[priority][,[subaddr],[satype]]] alternating voice/fax, voice first (TS 61) |
| ALT FAX/VOICE [,[priority][,[subaddr],[satype]]] alternating voice/fax, fax first (TS 61) |
| GPRS [PDP_type], [PDP_addr][, [[L2P]][,[APN]]] GPRS network request for PDP context activation |
| VGC [GCA], [GId], [ackflag] [,[priority]] voice group call (TS 91) |
| VBC [GCA], [GId], [ackflag] [,[priority]] voice broadcast call (TS 92) |
| The optional [priority] indicates the eMLPP priority level of the incoming call by paging, notification or setup message. The priority level values are as defined in eMLPP specification 3GPP TS 22.067 [54]. |
| [subaddr]: string type subaddress of format specified by [satype] |
| [satype]: type of subaddress octet in integer format (refer 3GPP TS 24.008 [8] subclause 10.5.4.8) |
| [PDP_type] ,[PDP_addr] and [APN] are as defined in the Define PDP Context (+CGDCONT) command. The optional [L2P] proposes a layer 2 protocol to use between the MT and the TE. It is defined in the Enter GPRS Data Mode (+CGDATA) command. If the MT is unable to announce to the TE the network's request (for example it is in V.250 online data state) the MT shall reject the request. No corresponding unsolicited result code shall be issued when the MT returns to a command state. |
| [GCA] is a part of the group call reference as specified in 3GPP TS 23.003 [7] and indicates group call area. |
| [GId] is a part of the group call reference as specified in 3GPP TS 23.003 [7] and indicates group call identification.The [ackflag]=1 proposes that a predefined confirmation procedure is to be used after the call is ended. For [ackflag]=0 no confirmation procedure is required. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CRC=?</command> |
| <profile>Cellular result codes (Query all)</profile> |
| <description>Set command controls whether or not the extended format of incoming call indication or GPRS network request for PDP context activation or notification for VBS/VGCS calls is used. When enabled, an incoming call is indicated to the TE with unsolicited result code +CRING: [type] instead of the normal RING. |
| Test command returns values supported as a compound value. |
| NOTE: Similar command may be found in TIA IS‑99 [15] and TIA IS‑135 [16]. |
| Defined values |
| [mode]: |
| 0 disables extended format |
| 1 enables extended format |
| [type]: |
| ASYNC [,[priority][,[subaddr],[satype]]] asynchronous transparent |
| SYNC [,[priority][,[subaddr],[satype]]] synchronous transparent |
| REL ASYNC [,[priority][,[subaddr],[satype]]] asynchronous non‑transparent |
| REL SYNC [,[priority][,[subaddr],[satype]]] synchronous non‑transparent |
| FAX [,[priority][,[subaddr],[satype]]] facsimile (TS 62) |
| VOICE [,[priority][,[subaddr],[satype]]] normal voice (TS 11) |
| VOICE/XXX [,[priority][,[subaddr],[satype]]] voice followed by data (BS 81) (XXX is ASYNC, SYNC, REL ASYNC or REL SYNC) |
| ALT VOICE/XXX [,[priority][,[subaddr],[satype]]] alternating voice/data, voice first (BS 61) |
| ALT XXX/VOICE [,[priority][,[subaddr],[satype]]] alternating voice/data, data first (BS 61) |
| ALT VOICE/FAX [,[priority][,[subaddr],[satype]]] alternating voice/fax, voice first (TS 61) |
| ALT FAX/VOICE [,[priority][,[subaddr],[satype]]] alternating voice/fax, fax first (TS 61) |
| GPRS [PDP_type], [PDP_addr][, [[L2P]][,[APN]]] GPRS network request for PDP context activation |
| VGC [GCA], [GId], [ackflag] [,[priority]] voice group call (TS 91) |
| VBC [GCA], [GId], [ackflag] [,[priority]] voice broadcast call (TS 92) |
| The optional [priority] indicates the eMLPP priority level of the incoming call by paging, notification or setup message. The priority level values are as defined in eMLPP specification 3GPP TS 22.067 [54]. |
| [subaddr]: string type subaddress of format specified by [satype] |
| [satype]: type of subaddress octet in integer format (refer 3GPP TS 24.008 [8] subclause 10.5.4.8) |
| [PDP_type] ,[PDP_addr] and [APN] are as defined in the Define PDP Context (+CGDCONT) command. The optional [L2P] proposes a layer 2 protocol to use between the MT and the TE. It is defined in the Enter GPRS Data Mode (+CGDATA) command. If the MT is unable to announce to the TE the network's request (for example it is in V.250 online data state) the MT shall reject the request. No corresponding unsolicited result code shall be issued when the MT returns to a command state. |
| [GCA] is a part of the group call reference as specified in 3GPP TS 23.003 [7] and indicates group call area. |
| [GId] is a part of the group call reference as specified in 3GPP TS 23.003 [7] and indicates group call identification.The [ackflag]=1 proposes that a predefined confirmation procedure is to be used after the call is ended. For [ackflag]=0 no confirmation procedure is required. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CHSD</command> |
| <profile>HSCSD device parameters </profile> |
| <description>Execution command returns information about HSCSD features (refer 3GPP TS 22.034 [29]) supported by the MT/TA. Refer subclause 9.2 for possible [err] values. |
| The return information is only applicable in GERAN. |
| Defined values |
| [mclass]: integer type; multislot class |
| [maxRx]: integer type; maximum number of receive timeslots that MT can use |
| [maxTx]: integer type; maximum number of transmit timeslots that MT can use |
| [sum]: integer type; total number of receive and transmit timeslots that MT can use at the same time (per TDMA frame). The following applies in a HSCSD call: 1 (receive slots) + (transmit slots) [sum] |
| [codings] is a sum of integers each representing a supported channel coding (e.g. value 5 indicates that 4,8k and 9,6k channel codings are supported): |
| 1 4,8k full rate data traffic channel |
| 4 9,6k full rate data traffic channel |
| 8 14,4k full rate data traffic channel |
| 16 28,8k full rate data traffic channel (only possible when 14.4k is supported) |
| 32 32,0k full rate data traffic channel (only possible in a two-timeslot configuration) |
| 64 43,2k full rate data traffic channel (only possible when 14.4k is supported) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CHSD=?</command> |
| <profile>HSCSD device parameters (Query all)</profile> |
| <description>Execution command returns information about HSCSD features (refer 3GPP TS 22.034 [29]) supported by the MT/TA. Refer subclause 9.2 for possible [err] values. |
| The return information is only applicable in GERAN. |
| Defined values |
| [mclass]: integer type; multislot class |
| [maxRx]: integer type; maximum number of receive timeslots that MT can use |
| [maxTx]: integer type; maximum number of transmit timeslots that MT can use |
| [sum]: integer type; total number of receive and transmit timeslots that MT can use at the same time (per TDMA frame). The following applies in a HSCSD call: 1 (receive slots) + (transmit slots) [sum] |
| [codings] is a sum of integers each representing a supported channel coding (e.g. value 5 indicates that 4,8k and 9,6k channel codings are supported): |
| 1 4,8k full rate data traffic channel |
| 4 9,6k full rate data traffic channel |
| 8 14,4k full rate data traffic channel |
| 16 28,8k full rate data traffic channel (only possible when 14.4k is supported) |
| 32 32,0k full rate data traffic channel (only possible in a two-timeslot configuration) |
| 64 43,2k full rate data traffic channel (only possible when 14.4k is supported) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CHST=</command> |
| <profile>HSCSD transparent call configuration (Assign)</profile> |
| <description>Set command controls parameters for transparent HSCSD calls in GERAN. Changing them during a call does not affect the current call. |
| NOTE: In UTRAN, values set with this command are not needed. The only applicable parameter is [SPEED], which is set with +CBST command. |
| Defined values |
| [wRx]: integer type; wanted amount of receive timeslots. Default value 0 indicates that TA shall calculate a proper value from currently selected fixed network user rate ([speed] subparameter from +CBST command) and [codings] |
| [codings]: a sum of integers each representing a channel coding that is accepted for transparent HSCSD calls. Default value 0 indicates that all supported codings are accepted (refer +CHSD command for other values) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CHST?</command> |
| <profile>HSCSD transparent call configuration (Query)</profile> |
| <description>Set command controls parameters for transparent HSCSD calls in GERAN. Changing them during a call does not affect the current call. |
| NOTE: In UTRAN, values set with this command are not needed. The only applicable parameter is [SPEED], which is set with +CBST command. |
| Defined values |
| [wRx]: integer type; wanted amount of receive timeslots. Default value 0 indicates that TA shall calculate a proper value from currently selected fixed network user rate ([speed] subparameter from +CBST command) and [codings] |
| [codings]: a sum of integers each representing a channel coding that is accepted for transparent HSCSD calls. Default value 0 indicates that all supported codings are accepted (refer +CHSD command for other values) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CHST=?</command> |
| <profile>HSCSD transparent call configuration (Query all)</profile> |
| <description>Set command controls parameters for transparent HSCSD calls in GERAN. Changing them during a call does not affect the current call. |
| NOTE: In UTRAN, values set with this command are not needed. The only applicable parameter is [SPEED], which is set with +CBST command. |
| Defined values |
| [wRx]: integer type; wanted amount of receive timeslots. Default value 0 indicates that TA shall calculate a proper value from currently selected fixed network user rate ([speed] subparameter from +CBST command) and [codings] |
| [codings]: a sum of integers each representing a channel coding that is accepted for transparent HSCSD calls. Default value 0 indicates that all supported codings are accepted (refer +CHSD command for other values) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CHSC</command> |
| <profile>HSCSD current call parameters </profile> |
| <description>Execution command returns information about current HSCSD call. If no HSCSD call is active, all parameters returned shall equal zero. If HSCSD call is active in UTRAN, all non-applicable parameters returned shall be equal to zero. (It is manufacturer specific whether non-zero information is returned in case of an active normal single-slot data call.) |
| Defined values |
| [rx]: integer type; number of receive timeslots currently in use. This parameter is not applicable in UTRAN. |
| [tx]: integer type; number of transmit timeslots currently in use. This parameter is not applicable in UTRAN. |
| [aiur]: integer type; current air interface user rate (in case of transparent service this equals fixed network user rate) (refer +CHSN command for possible values). For the two-timeslot ECSD bit transparent configuration the following additional values apply: |
| 8 56000 bps |
| 9 64000 bps |
| [coding]: current channel coding (refer +CHSD command for possible values). This parameter is not applicable in UTRAN. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CHSC=?</command> |
| <profile>HSCSD current call parameters (Query all)</profile> |
| <description>Execution command returns information about current HSCSD call. If no HSCSD call is active, all parameters returned shall equal zero. If HSCSD call is active in UTRAN, all non-applicable parameters returned shall be equal to zero. (It is manufacturer specific whether non-zero information is returned in case of an active normal single-slot data call.) |
| Defined values |
| [rx]: integer type; number of receive timeslots currently in use. This parameter is not applicable in UTRAN. |
| [tx]: integer type; number of transmit timeslots currently in use. This parameter is not applicable in UTRAN. |
| [aiur]: integer type; current air interface user rate (in case of transparent service this equals fixed network user rate) (refer +CHSN command for possible values). For the two-timeslot ECSD bit transparent configuration the following additional values apply: |
| 8 56000 bps |
| 9 64000 bps |
| [coding]: current channel coding (refer +CHSD command for possible values). This parameter is not applicable in UTRAN. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CHSR=</command> |
| <profile>HSCSD parameters report (Assign)</profile> |
| <description>Enabled command returns intermediate result code +CHSR: [type] from the TA to the TE when an HSCSD call is being set up. The result code represents the current (negotiated or renegotiated) HSCSD parameters. If enabled, the intermediate result code is transmitted at the point of the call setup negotiation where the TA has determined what type of an HSCSD connection will be used. Result code transmission is done after possible service (+CR), error control (+ER), and/or compression (+DR) reporting but before possible TE-TA rate (+ILRR) reporting and before the intermediate result code CONNECT is transmitted. The format of the intermediate result code is: |
| +CHSR: [rx],[tx],[aiur],[coding] |
| For the value definitions, refer to +CHSN and +CHSC commands. For instance, for a non-transparent HSCSD call, result code '+CHSR: 2,2,4,8' means that the call has two timeslots in both up- and downlink, the air interface user rate is 28800 bps, and the used channel coding TCH/F14.4. |
| In UTRAN, all non-applicable parameters returned shall be equal to zero. |
| Defined values |
| [mode]: |
| 0 disables reporting |
| 1 enables reporting |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CHSR?</command> |
| <profile>HSCSD parameters report (Query)</profile> |
| <description>Enabled command returns intermediate result code +CHSR: [type] from the TA to the TE when an HSCSD call is being set up. The result code represents the current (negotiated or renegotiated) HSCSD parameters. If enabled, the intermediate result code is transmitted at the point of the call setup negotiation where the TA has determined what type of an HSCSD connection will be used. Result code transmission is done after possible service (+CR), error control (+ER), and/or compression (+DR) reporting but before possible TE-TA rate (+ILRR) reporting and before the intermediate result code CONNECT is transmitted. The format of the intermediate result code is: |
| +CHSR: [rx],[tx],[aiur],[coding] |
| For the value definitions, refer to +CHSN and +CHSC commands. For instance, for a non-transparent HSCSD call, result code '+CHSR: 2,2,4,8' means that the call has two timeslots in both up- and downlink, the air interface user rate is 28800 bps, and the used channel coding TCH/F14.4. |
| In UTRAN, all non-applicable parameters returned shall be equal to zero. |
| Defined values |
| [mode]: |
| 0 disables reporting |
| 1 enables reporting |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CHSR=?</command> |
| <profile>HSCSD parameters report (Query all)</profile> |
| <description>Enabled command returns intermediate result code +CHSR: [type] from the TA to the TE when an HSCSD call is being set up. The result code represents the current (negotiated or renegotiated) HSCSD parameters. If enabled, the intermediate result code is transmitted at the point of the call setup negotiation where the TA has determined what type of an HSCSD connection will be used. Result code transmission is done after possible service (+CR), error control (+ER), and/or compression (+DR) reporting but before possible TE-TA rate (+ILRR) reporting and before the intermediate result code CONNECT is transmitted. The format of the intermediate result code is: |
| +CHSR: [rx],[tx],[aiur],[coding] |
| For the value definitions, refer to +CHSN and +CHSC commands. For instance, for a non-transparent HSCSD call, result code '+CHSR: 2,2,4,8' means that the call has two timeslots in both up- and downlink, the air interface user rate is 28800 bps, and the used channel coding TCH/F14.4. |
| In UTRAN, all non-applicable parameters returned shall be equal to zero. |
| Defined values |
| [mode]: |
| 0 disables reporting |
| 1 enables reporting |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSNS=</command> |
| <profile>Single numbering scheme (Assign)</profile> |
| <description>Set command selects the bearer or teleservice to be used when mobile terminated single numbering scheme call is established. Parameter values set with +CBST command shall be used when [mode] equals to a data service. |
| Test command returns values supported as compound values. |
| Defined values |
| [mode]: |
| 0 voice |
| 1 alternating voice/fax, voice first (TS 61) |
| 2 fax (TS 62) |
| 3 alternating voice/data, voice first (BS 61) |
| 4 data |
| 5 alternating voice/fax, fax first (TS 61) |
| 6 alternating voice/data, data first (BS 61) |
| 7 voice followed by data (BS 81) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSNS?</command> |
| <profile>Single numbering scheme (Query)</profile> |
| <description>Set command selects the bearer or teleservice to be used when mobile terminated single numbering scheme call is established. Parameter values set with +CBST command shall be used when [mode] equals to a data service. |
| Test command returns values supported as compound values. |
| Defined values |
| [mode]: |
| 0 voice |
| 1 alternating voice/fax, voice first (TS 61) |
| 2 fax (TS 62) |
| 3 alternating voice/data, voice first (BS 61) |
| 4 data |
| 5 alternating voice/fax, fax first (TS 61) |
| 6 alternating voice/data, data first (BS 61) |
| 7 voice followed by data (BS 81) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSNS=?</command> |
| <profile>Single numbering scheme (Query all)</profile> |
| <description>Set command selects the bearer or teleservice to be used when mobile terminated single numbering scheme call is established. Parameter values set with +CBST command shall be used when [mode] equals to a data service. |
| Test command returns values supported as compound values. |
| Defined values |
| [mode]: |
| 0 voice |
| 1 alternating voice/fax, voice first (TS 61) |
| 2 fax (TS 62) |
| 3 alternating voice/data, voice first (BS 61) |
| 4 data |
| 5 alternating voice/fax, fax first (TS 61) |
| 6 alternating voice/data, data first (BS 61) |
| 7 voice followed by data (BS 81) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CVHU=</command> |
| <profile>Voice Hangup Control (Assign)</profile> |
| <description>Set command selects whether ATH or 'drop DTR' shall cause a voice connection to be disconnected or not. By voice connection is also meant alternating mode calls that are currently in voice mode. (See subclause 6.6). |
| NOTE: When [mode] = 2, this command must be seen in conjunction with the V.250 [14] command :D. Else :D shall be ignored. |
| Defined values |
| [mode]: |
| 0 'Drop DTR' ignored but OK response given. ATH disconnects. |
| 1 'Drop DTR' and ATH ignored but OK response given. |
| 2 'Drop DTR' behaviour according to :D setting. ATH disconnects. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CVHU?</command> |
| <profile>Voice Hangup Control (Query)</profile> |
| <description>Set command selects whether ATH or 'drop DTR' shall cause a voice connection to be disconnected or not. By voice connection is also meant alternating mode calls that are currently in voice mode. (See subclause 6.6). |
| NOTE: When [mode] = 2, this command must be seen in conjunction with the V.250 [14] command :D. Else :D shall be ignored. |
| Defined values |
| [mode]: |
| 0 'Drop DTR' ignored but OK response given. ATH disconnects. |
| 1 'Drop DTR' and ATH ignored but OK response given. |
| 2 'Drop DTR' behaviour according to :D setting. ATH disconnects. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CVHU=?</command> |
| <profile>Voice Hangup Control (Query all)</profile> |
| <description>Set command selects whether ATH or 'drop DTR' shall cause a voice connection to be disconnected or not. By voice connection is also meant alternating mode calls that are currently in voice mode. (See subclause 6.6). |
| NOTE: When [mode] = 2, this command must be seen in conjunction with the V.250 [14] command :D. Else :D shall be ignored. |
| Defined values |
| [mode]: |
| 0 'Drop DTR' ignored but OK response given. ATH disconnects. |
| 1 'Drop DTR' and ATH ignored but OK response given. |
| 2 'Drop DTR' behaviour according to :D setting. ATH disconnects. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSDF=</command> |
| <profile>Settings date format (Assign)</profile> |
| <description>This command sets the date format via MMI of the date information presented to the user, which is specified by use of the [mode] parameter. The [mode] affects the date format on the phone display and doesn't affect the date format of the AT command serial interface. The command also sets the date format of the TE-TA interface, which is specified by use of the [auxmode] parameter (e.g. the [auxmode] affects the [time] of +CCLK and +CALA). If the parameter is omitted ('+CSDF =','+CSDF =[mode]','+CSDF=,[auxmode]'),then this sets the default value. |
| Defined values |
| [mode]: |
| NOTE: It is manufacturer specific which modes that are supported. |
| 1 DD-MMM-YYYY |
| NOTE: Presentation of MMM is language dependent. |
| 2 DD-MM-YY |
| 3 MM/DD/YY |
| 4 DD/MM/YY |
| 5 DD.MM.YY |
| 6 YYMMDD |
| 7 YY-MM-DD |
| 8-255 Manufacturer specific |
| [auxmode]: |
| 1yy/MM/dd (default) |
| 2 yyyy/MM/dd |
| also all other values are reserved by the present document |
| NOTE: The [time] format of +CCLK and +CALA 'yy/MM/dd,hh:mm:sszz' when [auxmode]=1 and it is 'yyyy/MM/dd,hh:mm:sszz' when [auxmode]=2. If the MT does not support time zone information then the three last characters may be omitted (see +CCLK command). |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSDF?</command> |
| <profile>Settings date format (Query)</profile> |
| <description>This command sets the date format via MMI of the date information presented to the user, which is specified by use of the [mode] parameter. The [mode] affects the date format on the phone display and doesn't affect the date format of the AT command serial interface. The command also sets the date format of the TE-TA interface, which is specified by use of the [auxmode] parameter (e.g. the [auxmode] affects the [time] of +CCLK and +CALA). If the parameter is omitted ('+CSDF =','+CSDF =[mode]','+CSDF=,[auxmode]'),then this sets the default value. |
| Defined values |
| [mode]: |
| NOTE: It is manufacturer specific which modes that are supported. |
| 1 DD-MMM-YYYY |
| NOTE: Presentation of MMM is language dependent. |
| 2 DD-MM-YY |
| 3 MM/DD/YY |
| 4 DD/MM/YY |
| 5 DD.MM.YY |
| 6 YYMMDD |
| 7 YY-MM-DD |
| 8-255 Manufacturer specific |
| [auxmode]: |
| 1yy/MM/dd (default) |
| 2 yyyy/MM/dd |
| also all other values are reserved by the present document |
| NOTE: The [time] format of +CCLK and +CALA 'yy/MM/dd,hh:mm:sszz' when [auxmode]=1 and it is 'yyyy/MM/dd,hh:mm:sszz' when [auxmode]=2. If the MT does not support time zone information then the three last characters may be omitted (see +CCLK command). |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSDF=?</command> |
| <profile>Settings date format (Query all)</profile> |
| <description>This command sets the date format via MMI of the date information presented to the user, which is specified by use of the [mode] parameter. The [mode] affects the date format on the phone display and doesn't affect the date format of the AT command serial interface. The command also sets the date format of the TE-TA interface, which is specified by use of the [auxmode] parameter (e.g. the [auxmode] affects the [time] of +CCLK and +CALA). If the parameter is omitted ('+CSDF =','+CSDF =[mode]','+CSDF=,[auxmode]'),then this sets the default value. |
| Defined values |
| [mode]: |
| NOTE: It is manufacturer specific which modes that are supported. |
| 1 DD-MMM-YYYY |
| NOTE: Presentation of MMM is language dependent. |
| 2 DD-MM-YY |
| 3 MM/DD/YY |
| 4 DD/MM/YY |
| 5 DD.MM.YY |
| 6 YYMMDD |
| 7 YY-MM-DD |
| 8-255 Manufacturer specific |
| [auxmode]: |
| 1yy/MM/dd (default) |
| 2 yyyy/MM/dd |
| also all other values are reserved by the present document |
| NOTE: The [time] format of +CCLK and +CALA 'yy/MM/dd,hh:mm:sszz' when [auxmode]=1 and it is 'yyyy/MM/dd,hh:mm:sszz' when [auxmode]=2. If the MT does not support time zone information then the three last characters may be omitted (see +CCLK command). |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSIL=</command> |
| <profile>Silence Command (Assign)</profile> |
| <description>Set command enables/disables the silent mode. When the phone is in silent mode, all sounds from MT are suppressed except voice. |
| Read command reads the current setting. |
| Test command lists the supported modes. |
| Defined values |
| [mode]: |
| 0 Silent mode off |
| 1 Silent mode on |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSIL?</command> |
| <profile>Silence Command (Query)</profile> |
| <description>Set command enables/disables the silent mode. When the phone is in silent mode, all sounds from MT are suppressed except voice. |
| Read command reads the current setting. |
| Test command lists the supported modes. |
| Defined values |
| [mode]: |
| 0 Silent mode off |
| 1 Silent mode on |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSIL=?</command> |
| <profile>Silence Command (Query all)</profile> |
| <description>Set command enables/disables the silent mode. When the phone is in silent mode, all sounds from MT are suppressed except voice. |
| Read command reads the current setting. |
| Test command lists the supported modes. |
| Defined values |
| [mode]: |
| 0 Silent mode off |
| 1 Silent mode on |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSTF=</command> |
| <profile>Settings time format (Assign)</profile> |
| <description>Set command sets the time format of the time information presented to the user. |
| Read commands reads the current setting. |
| Test commands reads the supported [modes]s. |
| Defined values |
| [mode]: |
| 1 HH:MM (24 hour clock) |
| 2 HH:MM a.m./p.m. |
| 3-7 Manufacturer specific |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSTF?</command> |
| <profile>Settings time format (Query)</profile> |
| <description>Set command sets the time format of the time information presented to the user. |
| Read commands reads the current setting. |
| Test commands reads the supported [modes]s. |
| Defined values |
| [mode]: |
| 1 HH:MM (24 hour clock) |
| 2 HH:MM a.m./p.m. |
| 3-7 Manufacturer specific |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSTF=?</command> |
| <profile>Settings time format (Query all)</profile> |
| <description>Set command sets the time format of the time information presented to the user. |
| Read commands reads the current setting. |
| Test commands reads the supported [modes]s. |
| Defined values |
| [mode]: |
| 1 HH:MM (24 hour clock) |
| 2 HH:MM a.m./p.m. |
| 3-7 Manufacturer specific |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CNUM</command> |
| <profile>Subscriber number </profile> |
| <description>Action command returns the MSISDNs related to the subscriber (this information can be stored in the SIM/UICC or in the MT). When storing information in the SIM/UICC, if a SIM card is present or if a UICC with an active GSM application is present, the information is stored in the EFMSISDN under DFTelecom. If a UICC with an active USIM application is present, the information is stored in the EFMSISDN under ADFUSIM). If subscriber has different MSISDN for different services, each MSISDN is returned in a separate line. Refer subclause 9.2 for possible [err] values. |
| Defined values |
| [alphax]: optional alphanumeric string associated with [numberx]; used character set should be the one selected with command Select TE Character Set +CSCS |
| [numberx]: string type phone number of format specified by [typex] |
| [typex]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7) |
| [speed]: as defined in subclause 6.7 |
| [service] (service related to the phone number): |
| 0 asynchronous modem |
| 1 synchronous modem |
| 2 PAD Access (asynchronous) |
| 3 Packet Access (synchronous) |
| 4 voice |
| 5 fax |
| also all other values below 128 are reserved by the present document |
| [itc] (information transfer capability): |
| 0 3,1 kHz |
| 1 UDI |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CNUM=?</command> |
| <profile>Subscriber number (Query all)</profile> |
| <description>Action command returns the MSISDNs related to the subscriber (this information can be stored in the SIM/UICC or in the MT). When storing information in the SIM/UICC, if a SIM card is present or if a UICC with an active GSM application is present, the information is stored in the EFMSISDN under DFTelecom. If a UICC with an active USIM application is present, the information is stored in the EFMSISDN under ADFUSIM). If subscriber has different MSISDN for different services, each MSISDN is returned in a separate line. Refer subclause 9.2 for possible [err] values. |
| Defined values |
| [alphax]: optional alphanumeric string associated with [numberx]; used character set should be the one selected with command Select TE Character Set +CSCS |
| [numberx]: string type phone number of format specified by [typex] |
| [typex]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7) |
| [speed]: as defined in subclause 6.7 |
| [service] (service related to the phone number): |
| 0 asynchronous modem |
| 1 synchronous modem |
| 2 PAD Access (asynchronous) |
| 3 Packet Access (synchronous) |
| 4 voice |
| 5 fax |
| also all other values below 128 are reserved by the present document |
| [itc] (information transfer capability): |
| 0 3,1 kHz |
| 1 UDI |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CREG=</command> |
| <profile>Network registration (Assign)</profile> |
| <description>Set command controls the presentation of an unsolicited result code +CREG: [stat] when [n]=1 and there is a change in the MT network registration status, or code +CREG: [stat][,[lac],[ci][,[AcT]]] when [n]=2 and there is a change of the network cell. |
| Read command returns the status of result code presentation and an integer [stat] which shows whether the network has currently indicated the registration of the MT. Location information elements [lac], [ci] and [AcT]are returned only when [n]=2 and MT is registered in the network. Refer subclause 9.2 for possible [err] values. |
| Defined values |
| [n]: |
| 0 disable network registration unsolicited result code |
| 1 enable network registration unsolicited result code +CREG: [stat] |
| 2 enable network registration and location information unsolicited result code +CREG: [stat][,[lac],[ci][,[AcT]]] |
| [stat]: registration status |
| 0 not registered, MT is not currently searching a new operator to register to |
| 1 registered, home network |
| 2 not registered, but MT is currently searching a new operator to register to |
| 3 registration denied |
| 4 unknown |
| 5 registered, roaming |
| [lac]: string type; two byte location area code in hexadecimal format (e.g. '00C3' equals 195 in decimal) |
| [ci]: string type; four byte UTRAN/GERAN cell ID in hexadecimal format |
| [AcT]: access technology of the registered network |
| 0 GSM |
| 1 GSM Compact |
| 2 UTRAN |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CREG?</command> |
| <profile>Network registration (Query)</profile> |
| <description>Set command controls the presentation of an unsolicited result code +CREG: [stat] when [n]=1 and there is a change in the MT network registration status, or code +CREG: [stat][,[lac],[ci][,[AcT]]] when [n]=2 and there is a change of the network cell. |
| Read command returns the status of result code presentation and an integer [stat] which shows whether the network has currently indicated the registration of the MT. Location information elements [lac], [ci] and [AcT]are returned only when [n]=2 and MT is registered in the network. Refer subclause 9.2 for possible [err] values. |
| Defined values |
| [n]: |
| 0 disable network registration unsolicited result code |
| 1 enable network registration unsolicited result code +CREG: [stat] |
| 2 enable network registration and location information unsolicited result code +CREG: [stat][,[lac],[ci][,[AcT]]] |
| [stat]: registration status |
| 0 not registered, MT is not currently searching a new operator to register to |
| 1 registered, home network |
| 2 not registered, but MT is currently searching a new operator to register to |
| 3 registration denied |
| 4 unknown |
| 5 registered, roaming |
| [lac]: string type; two byte location area code in hexadecimal format (e.g. '00C3' equals 195 in decimal) |
| [ci]: string type; four byte UTRAN/GERAN cell ID in hexadecimal format |
| [AcT]: access technology of the registered network |
| 0 GSM |
| 1 GSM Compact |
| 2 UTRAN |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CREG=?</command> |
| <profile>Network registration (Query all)</profile> |
| <description>Set command controls the presentation of an unsolicited result code +CREG: [stat] when [n]=1 and there is a change in the MT network registration status, or code +CREG: [stat][,[lac],[ci][,[AcT]]] when [n]=2 and there is a change of the network cell. |
| Read command returns the status of result code presentation and an integer [stat] which shows whether the network has currently indicated the registration of the MT. Location information elements [lac], [ci] and [AcT]are returned only when [n]=2 and MT is registered in the network. Refer subclause 9.2 for possible [err] values. |
| Defined values |
| [n]: |
| 0 disable network registration unsolicited result code |
| 1 enable network registration unsolicited result code +CREG: [stat] |
| 2 enable network registration and location information unsolicited result code +CREG: [stat][,[lac],[ci][,[AcT]]] |
| [stat]: registration status |
| 0 not registered, MT is not currently searching a new operator to register to |
| 1 registered, home network |
| 2 not registered, but MT is currently searching a new operator to register to |
| 3 registration denied |
| 4 unknown |
| 5 registered, roaming |
| [lac]: string type; two byte location area code in hexadecimal format (e.g. '00C3' equals 195 in decimal) |
| [ci]: string type; four byte UTRAN/GERAN cell ID in hexadecimal format |
| [AcT]: access technology of the registered network |
| 0 GSM |
| 1 GSM Compact |
| 2 UTRAN |
| </description> |
| </spec> |
| <spec> |
| <command>AT+COPS=</command> |
| <profile>PLMN selection (Assign)</profile> |
| <description>Set command forces an attempt to select and register the GSM/UMTS network operator. [mode] is used to select whether the selection is done automatically by the MT or is forced by this command to operator [oper] (it shall be given in format [format]) to a certain access technology, indicated in [AcT]. If the selected operator is not available, no other operator shall be selected (except [mode]=4). If the selected access technology is not available, then the same operator shall be selected in other access technology. The selected operator name format shall apply to further read commands (+COPS?) also. [mode]=2 forces an attempt to deregister from the network. The selected mode affects to all further network registration (e.g. after [mode]=2, MT shall be unregistered until [mode]=0 or 1 is selected). Refer subclause 9.2 for possible [err] values. This command should be abortable when registration/deregistration attempt is made. |
| Read command returns the current mode, the currently selected operator and the current Access Technology. If no operator is selected, [format], [oper] and [ AcT] are omitted. |
| Test command returns a set of five parameters, each representing an operator present in the network. A set consists of an integer indicating the availability of the operator [stat], long and short alphanumeric format of the name of the operator, numeric format representation of the operator and access technology. Any of the formats may be unavailable and should then be an empty field. The list of operators shall be in order: home network, networks referenced in SIM or active application in the UICC (GSM or USIM) in the following order: HPLMN selector, User controlled PLMN selector, Operator controlled PLMN selector and PLMN selector (in the SIM or GSM application), and other networks. |
| It is recommended (although optional) that after the operator list TA returns lists of supported [mode]s and [format]s. These lists shall be delimited from the operator list by two commas. |
| NOTE: The access technology selected parameters, [AcT], should only be used in terminals capable to register to more than one access technology. Selection of [AcT] does not limit the capability to cell reselections, even though access technology is selected, the phone may still re-select a cell in other access technology. |
| Defined values |
| [mode]: |
| 0 automatic ([oper] field is ignored) |
| 1 manual ([oper] field shall be present, and [AcT] optionally) |
| 2 deregister from network |
| 3 set only [format] (for read command +COPS?), do not attempt registration/deregistration ([oper] and [ AcT] fields are ignored); this value is not applicable in read command response |
| 4 manual/automatic ([oper] field shall be present); if manual selection fails, automatic mode ([mode]=0) is entered |
| [format]: |
| 0 long format alphanumeric [oper] |
| 1 short format alphanumeric [oper] |
| 2 numeric [oper] |
| [oper]: string type; [format] indicates if the format is alphanumeric or numeric; long alphanumeric format can be upto 16 characters long and short format up to 8 characters (refer GSM MoU SE.13 [9]); numeric format is the GSM Location Area Identification number (refer TS 24.008 [8] subclause 10.5.1.3) which consists of a three BCD digit country code coded as in ITU‑T E.212 Annex A [10], plus a two BCD digit network code, which is administration specific; returned [oper] shall not be in BCD format, but in IRA characters converted from BCD; hence the number has structure: (country code digit 3)(country code digit 2)(country code digit 1)(network code digit 3)(network code digit 2)(network code digit 1) |
| [stat]: |
| 0 unknown |
| 1 available |
| 2 current |
| 3 forbidden |
| [AcT] access technology selected: |
| 0 GSM |
| 1 GSM Compact |
| 2 UTRAN |
| </description> |
| </spec> |
| <spec> |
| <command>AT+COPS?</command> |
| <profile>PLMN selection (Query)</profile> |
| <description>Set command forces an attempt to select and register the GSM/UMTS network operator. [mode] is used to select whether the selection is done automatically by the MT or is forced by this command to operator [oper] (it shall be given in format [format]) to a certain access technology, indicated in [AcT]. If the selected operator is not available, no other operator shall be selected (except [mode]=4). If the selected access technology is not available, then the same operator shall be selected in other access technology. The selected operator name format shall apply to further read commands (+COPS?) also. [mode]=2 forces an attempt to deregister from the network. The selected mode affects to all further network registration (e.g. after [mode]=2, MT shall be unregistered until [mode]=0 or 1 is selected). Refer subclause 9.2 for possible [err] values. This command should be abortable when registration/deregistration attempt is made. |
| Read command returns the current mode, the currently selected operator and the current Access Technology. If no operator is selected, [format], [oper] and [ AcT] are omitted. |
| Test command returns a set of five parameters, each representing an operator present in the network. A set consists of an integer indicating the availability of the operator [stat], long and short alphanumeric format of the name of the operator, numeric format representation of the operator and access technology. Any of the formats may be unavailable and should then be an empty field. The list of operators shall be in order: home network, networks referenced in SIM or active application in the UICC (GSM or USIM) in the following order: HPLMN selector, User controlled PLMN selector, Operator controlled PLMN selector and PLMN selector (in the SIM or GSM application), and other networks. |
| It is recommended (although optional) that after the operator list TA returns lists of supported [mode]s and [format]s. These lists shall be delimited from the operator list by two commas. |
| NOTE: The access technology selected parameters, [AcT], should only be used in terminals capable to register to more than one access technology. Selection of [AcT] does not limit the capability to cell reselections, even though access technology is selected, the phone may still re-select a cell in other access technology. |
| Defined values |
| [mode]: |
| 0 automatic ([oper] field is ignored) |
| 1 manual ([oper] field shall be present, and [AcT] optionally) |
| 2 deregister from network |
| 3 set only [format] (for read command +COPS?), do not attempt registration/deregistration ([oper] and [ AcT] fields are ignored); this value is not applicable in read command response |
| 4 manual/automatic ([oper] field shall be present); if manual selection fails, automatic mode ([mode]=0) is entered |
| [format]: |
| 0 long format alphanumeric [oper] |
| 1 short format alphanumeric [oper] |
| 2 numeric [oper] |
| [oper]: string type; [format] indicates if the format is alphanumeric or numeric; long alphanumeric format can be upto 16 characters long and short format up to 8 characters (refer GSM MoU SE.13 [9]); numeric format is the GSM Location Area Identification number (refer TS 24.008 [8] subclause 10.5.1.3) which consists of a three BCD digit country code coded as in ITU‑T E.212 Annex A [10], plus a two BCD digit network code, which is administration specific; returned [oper] shall not be in BCD format, but in IRA characters converted from BCD; hence the number has structure: (country code digit 3)(country code digit 2)(country code digit 1)(network code digit 3)(network code digit 2)(network code digit 1) |
| [stat]: |
| 0 unknown |
| 1 available |
| 2 current |
| 3 forbidden |
| [AcT] access technology selected: |
| 0 GSM |
| 1 GSM Compact |
| 2 UTRAN |
| </description> |
| </spec> |
| <spec> |
| <command>AT+COPS=?</command> |
| <profile>PLMN selection (Query all)</profile> |
| <description>Set command forces an attempt to select and register the GSM/UMTS network operator. [mode] is used to select whether the selection is done automatically by the MT or is forced by this command to operator [oper] (it shall be given in format [format]) to a certain access technology, indicated in [AcT]. If the selected operator is not available, no other operator shall be selected (except [mode]=4). If the selected access technology is not available, then the same operator shall be selected in other access technology. The selected operator name format shall apply to further read commands (+COPS?) also. [mode]=2 forces an attempt to deregister from the network. The selected mode affects to all further network registration (e.g. after [mode]=2, MT shall be unregistered until [mode]=0 or 1 is selected). Refer subclause 9.2 for possible [err] values. This command should be abortable when registration/deregistration attempt is made. |
| Read command returns the current mode, the currently selected operator and the current Access Technology. If no operator is selected, [format], [oper] and [ AcT] are omitted. |
| Test command returns a set of five parameters, each representing an operator present in the network. A set consists of an integer indicating the availability of the operator [stat], long and short alphanumeric format of the name of the operator, numeric format representation of the operator and access technology. Any of the formats may be unavailable and should then be an empty field. The list of operators shall be in order: home network, networks referenced in SIM or active application in the UICC (GSM or USIM) in the following order: HPLMN selector, User controlled PLMN selector, Operator controlled PLMN selector and PLMN selector (in the SIM or GSM application), and other networks. |
| It is recommended (although optional) that after the operator list TA returns lists of supported [mode]s and [format]s. These lists shall be delimited from the operator list by two commas. |
| NOTE: The access technology selected parameters, [AcT], should only be used in terminals capable to register to more than one access technology. Selection of [AcT] does not limit the capability to cell reselections, even though access technology is selected, the phone may still re-select a cell in other access technology. |
| Defined values |
| [mode]: |
| 0 automatic ([oper] field is ignored) |
| 1 manual ([oper] field shall be present, and [AcT] optionally) |
| 2 deregister from network |
| 3 set only [format] (for read command +COPS?), do not attempt registration/deregistration ([oper] and [ AcT] fields are ignored); this value is not applicable in read command response |
| 4 manual/automatic ([oper] field shall be present); if manual selection fails, automatic mode ([mode]=0) is entered |
| [format]: |
| 0 long format alphanumeric [oper] |
| 1 short format alphanumeric [oper] |
| 2 numeric [oper] |
| [oper]: string type; [format] indicates if the format is alphanumeric or numeric; long alphanumeric format can be upto 16 characters long and short format up to 8 characters (refer GSM MoU SE.13 [9]); numeric format is the GSM Location Area Identification number (refer TS 24.008 [8] subclause 10.5.1.3) which consists of a three BCD digit country code coded as in ITU‑T E.212 Annex A [10], plus a two BCD digit network code, which is administration specific; returned [oper] shall not be in BCD format, but in IRA characters converted from BCD; hence the number has structure: (country code digit 3)(country code digit 2)(country code digit 1)(network code digit 3)(network code digit 2)(network code digit 1) |
| [stat]: |
| 0 unknown |
| 1 available |
| 2 current |
| 3 forbidden |
| [AcT] access technology selected: |
| 0 GSM |
| 1 GSM Compact |
| 2 UTRAN |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CLCK=</command> |
| <profile>Facility lock (Assign)</profile> |
| <description>Execute command is used to lock, unlock or interrogate a MT or a network facility [fac]. Password is normally needed to do such actions. When querying the status of a network service ([mode]=2) the response line for 'not active' case ([status]=0) should be returned only if service is not active for any [class]. Refer subclause 9.2 for possible [err] values. This command should be abortable when network facilities are set or interrogated. |
| Call barring facilities are based on GSM/UMTS supplementary services (refer 3GPP TS 22.088 [6]). The interaction of these with other commands based on other GSM/UMTS supplementary services is described in the GSM/UMTS standard. |
| Test command returns facility values supported as a compound value. |
| Defined values |
| [fac] values reserved by the present document: |
| 'CS' CNTRL (lock CoNTRoL surface (e.g. phone keyboard)) |
| 'PS' PH‑SIM (lock PHone to SIM/UICC card) (MT asks password when other than current SIM/UICC card inserted; MT may remember certain amount of previously used cards thus not requiring password when they are inserted) |
| 'PF' lock Phone to the very First inserted SIM/UICC card (also referred in the present document as PH-FSIM) (MT asks password when other than the first SIM/UICC card is inserted) |
| 'SC' SIM (lock SIM/UICC card) (SIM/UICC asks password in MT power‑up and when this lock command issued) |
| 'AO' BAOC (Barr All Outgoing Calls) (refer 3GPP TS 22.088 [6] clause 1) |
| 'OI' BOIC (Barr Outgoing International Calls) (refer 3GPP TS 22.088 [6] clause 1) |
| 'OX' BOIC‑exHC (Barr Outgoing International Calls except to Home Country) (refer 3GPP TS 22.088 [6] clause 1) |
| 'AI' BAIC (Barr All Incoming Calls) (refer 3GPP TS 22.088 [6] clause 2) |
| 'IR' BIC‑Roam (Barr Incoming Calls when Roaming outside the home country) (refer 3GPP TS 22.088 [6] clause 2) |
| 'NT' barr incoming calls from numbers Not stored to TA memory |
| 'NM' barr incoming calls from numbers Not stored to MT memory |
| 'NS' barr incoming calls from numbers Not stored to SIM/UICC memory |
| 'NA' barr incoming calls from numbers Not stored in Any memory |
| 'AB' All Barring services (refer 3GPP TS 22.030 [19]) (applicable only for [mode]=0) |
| 'AG' All outGoing barring services (refer 3GPP TS 22.030 [19]) (applicable only for [mode]=0) |
| 'AC' All inComing barring services (refer 3GPP TS 22.030 [19]) (applicable only for [mode]=0) |
| 'FD' SIM card or active application in the UICC (GSM or USIM) fixed dialling memory feature (if PIN2 authentication has not been done during the current session, PIN2 is required as [passwd]) |
| 'PN' Network Personalization (refer 3GPP TS 22.022 [33]) |
| 'PU' network sUbset Personalization (refer 3GPP TS 22.022 [33]) |
| 'PP' service Provider Personalization (refer 3GPP TS 22.022 [33]) |
| 'PC' Corporate Personalization (refer 3GPP TS 22.022 [33]) |
| [mode]: |
| 0 unlock |
| 1 lock |
| 2 query status |
| [status]: |
| 0 not active |
| 1 active |
| [passwd]: string type; shall be the same as password specified for the facility from the MT user interface or with command Change Password +CPWD |
| [classx] is a sum of integers each representing a class of information (default 7): |
| 1 voice (telephony) |
| 2 data (refers to all bearer services; with [mode]=2 this may refer only to some bearer service if TA does not support values 16, 32, 64 and 128) |
| 4 fax (facsimile services) |
| 8 short message service |
| 16 data circuit sync |
| 32 data circuit async |
| 64 dedicated packet access |
| 128 dedicated PAD access |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CLCK=?</command> |
| <profile>Facility lock (Query all)</profile> |
| <description>Execute command is used to lock, unlock or interrogate a MT or a network facility [fac]. Password is normally needed to do such actions. When querying the status of a network service ([mode]=2) the response line for 'not active' case ([status]=0) should be returned only if service is not active for any [class]. Refer subclause 9.2 for possible [err] values. This command should be abortable when network facilities are set or interrogated. |
| Call barring facilities are based on GSM/UMTS supplementary services (refer 3GPP TS 22.088 [6]). The interaction of these with other commands based on other GSM/UMTS supplementary services is described in the GSM/UMTS standard. |
| Test command returns facility values supported as a compound value. |
| Defined values |
| [fac] values reserved by the present document: |
| 'CS' CNTRL (lock CoNTRoL surface (e.g. phone keyboard)) |
| 'PS' PH‑SIM (lock PHone to SIM/UICC card) (MT asks password when other than current SIM/UICC card inserted; MT may remember certain amount of previously used cards thus not requiring password when they are inserted) |
| 'PF' lock Phone to the very First inserted SIM/UICC card (also referred in the present document as PH-FSIM) (MT asks password when other than the first SIM/UICC card is inserted) |
| 'SC' SIM (lock SIM/UICC card) (SIM/UICC asks password in MT power‑up and when this lock command issued) |
| 'AO' BAOC (Barr All Outgoing Calls) (refer 3GPP TS 22.088 [6] clause 1) |
| 'OI' BOIC (Barr Outgoing International Calls) (refer 3GPP TS 22.088 [6] clause 1) |
| 'OX' BOIC‑exHC (Barr Outgoing International Calls except to Home Country) (refer 3GPP TS 22.088 [6] clause 1) |
| 'AI' BAIC (Barr All Incoming Calls) (refer 3GPP TS 22.088 [6] clause 2) |
| 'IR' BIC‑Roam (Barr Incoming Calls when Roaming outside the home country) (refer 3GPP TS 22.088 [6] clause 2) |
| 'NT' barr incoming calls from numbers Not stored to TA memory |
| 'NM' barr incoming calls from numbers Not stored to MT memory |
| 'NS' barr incoming calls from numbers Not stored to SIM/UICC memory |
| 'NA' barr incoming calls from numbers Not stored in Any memory |
| 'AB' All Barring services (refer 3GPP TS 22.030 [19]) (applicable only for [mode]=0) |
| 'AG' All outGoing barring services (refer 3GPP TS 22.030 [19]) (applicable only for [mode]=0) |
| 'AC' All inComing barring services (refer 3GPP TS 22.030 [19]) (applicable only for [mode]=0) |
| 'FD' SIM card or active application in the UICC (GSM or USIM) fixed dialling memory feature (if PIN2 authentication has not been done during the current session, PIN2 is required as [passwd]) |
| 'PN' Network Personalization (refer 3GPP TS 22.022 [33]) |
| 'PU' network sUbset Personalization (refer 3GPP TS 22.022 [33]) |
| 'PP' service Provider Personalization (refer 3GPP TS 22.022 [33]) |
| 'PC' Corporate Personalization (refer 3GPP TS 22.022 [33]) |
| [mode]: |
| 0 unlock |
| 1 lock |
| 2 query status |
| [status]: |
| 0 not active |
| 1 active |
| [passwd]: string type; shall be the same as password specified for the facility from the MT user interface or with command Change Password +CPWD |
| [classx] is a sum of integers each representing a class of information (default 7): |
| 1 voice (telephony) |
| 2 data (refers to all bearer services; with [mode]=2 this may refer only to some bearer service if TA does not support values 16, 32, 64 and 128) |
| 4 fax (facsimile services) |
| 8 short message service |
| 16 data circuit sync |
| 32 data circuit async |
| 64 dedicated packet access |
| 128 dedicated PAD access |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CPWD=</command> |
| <profile>Change password (Assign)</profile> |
| <description>Action command sets a new password for the facility lock function defined by command Facility Lock +CLCK. Refer subclause 9.2 for possible [err] values. |
| Test command returns a list of pairs which present the available facilities and the maximum length of their password. |
| Defined values |
| [fac]: |
| 'P2' SIM PIN2 |
| refer Facility Lock +CLCK for other values |
| [oldpwd], [newpwd]: string type; [oldpwd] shall be the same as password specified for the facility from the MT user interface or with command Change Password +CPWD and [newpwd] is the new password; maximum length of password can be determined with [pwdlength] |
| [pwdlength]: integer type maximum length of the password for the facility |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CPWD=?</command> |
| <profile>Change password (Query all)</profile> |
| <description>Action command sets a new password for the facility lock function defined by command Facility Lock +CLCK. Refer subclause 9.2 for possible [err] values. |
| Test command returns a list of pairs which present the available facilities and the maximum length of their password. |
| Defined values |
| [fac]: |
| 'P2' SIM PIN2 |
| refer Facility Lock +CLCK for other values |
| [oldpwd], [newpwd]: string type; [oldpwd] shall be the same as password specified for the facility from the MT user interface or with command Change Password +CPWD and [newpwd] is the new password; maximum length of password can be determined with [pwdlength] |
| [pwdlength]: integer type maximum length of the password for the facility |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CLIP=</command> |
| <profile>Calling line identification presentation (Assign)</profile> |
| <description>This command refers to the GSM/UMTS supplementary service CLIP (Calling Line Identification Presentation) that enables a called subscriber to get the calling line identity (CLI) of the calling party when receiving a mobile terminated call. Set command enables or disables the presentation of the CLI at the TE. It has no effect on the execution of the supplementary service CLIP in the network. |
| When the presentation of the CLI at the TE is enabled (and calling subscriber allows), +CLIP: [number],[type][,[subaddr],[satype][,[[alpha]][,[CLI validity]]]] response is returned after every RING (or +CRING: [type]; refer subclause 'Cellular result codes +CRC') result code sent from TA to TE. It is manufacturer specific if this response is used when normal voice call is answered. |
| Read command gives the status of [n], and also triggers an interrogation of the provision status of the CLIP service according 3GPP TS 22.081 [3] (given in [m]).Test command returns values supported as a compound value. |
| Defined values |
| [n] (parameter sets/shows the result code presentation status to the TE): |
| 0 disable |
| 1 enable |
| [m] (parameter shows the subscriber CLIP service status in the network): |
| 0 CLIP not provisioned |
| 1 CLIP provisioned |
| 2 unknown (e.g. no network, etc.) |
| [number]: string type phone number of format specified by [type] |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7) |
| [subaddr]: string type subaddress of format specified by [satype] |
| [satype]: type of subaddress octet in integer format (refer TS 24.008 [8] subclause 10.5.4.8) |
| [alpha]: optional string type alphanumeric representation of [number] corresponding to the entry found in phonebook; used character set should be the one selected with command Select TE Character Set +CSCS |
| [CLI validity]: |
| 0 CLI valid |
| 1 CLI has been withheld by the originator. |
| 2 CLI is not available due to interworking problems or limitations of originating network. |
| When CLI is not available ( [CLI validity]=2), [number] shall be an empty string ('') and [type] value will not be significant. Nevertheless, TA may return the recommended value 128 for [type] ((TON/NPI unknown in accordance with TS 24.008 [8] subclause 10.5.4.7). |
| When CLI has been withheld by the originator, ([CLI validity]=1) and the CLIP is provisioned with the 'override category' option (refer 3GPP TS 22.081[3] and 3GPP TS 23.081[40]), [number] and [type] is provided. Otherwise, TA shall return the same setting for [number] and [type] as if the CLI was not available. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CLIP?</command> |
| <profile>Calling line identification presentation (Query)</profile> |
| <description>This command refers to the GSM/UMTS supplementary service CLIP (Calling Line Identification Presentation) that enables a called subscriber to get the calling line identity (CLI) of the calling party when receiving a mobile terminated call. Set command enables or disables the presentation of the CLI at the TE. It has no effect on the execution of the supplementary service CLIP in the network. |
| When the presentation of the CLI at the TE is enabled (and calling subscriber allows), +CLIP: [number],[type][,[subaddr],[satype][,[[alpha]][,[CLI validity]]]] response is returned after every RING (or +CRING: [type]; refer subclause 'Cellular result codes +CRC') result code sent from TA to TE. It is manufacturer specific if this response is used when normal voice call is answered. |
| Read command gives the status of [n], and also triggers an interrogation of the provision status of the CLIP service according 3GPP TS 22.081 [3] (given in [m]).Test command returns values supported as a compound value. |
| Defined values |
| [n] (parameter sets/shows the result code presentation status to the TE): |
| 0 disable |
| 1 enable |
| [m] (parameter shows the subscriber CLIP service status in the network): |
| 0 CLIP not provisioned |
| 1 CLIP provisioned |
| 2 unknown (e.g. no network, etc.) |
| [number]: string type phone number of format specified by [type] |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7) |
| [subaddr]: string type subaddress of format specified by [satype] |
| [satype]: type of subaddress octet in integer format (refer TS 24.008 [8] subclause 10.5.4.8) |
| [alpha]: optional string type alphanumeric representation of [number] corresponding to the entry found in phonebook; used character set should be the one selected with command Select TE Character Set +CSCS |
| [CLI validity]: |
| 0 CLI valid |
| 1 CLI has been withheld by the originator. |
| 2 CLI is not available due to interworking problems or limitations of originating network. |
| When CLI is not available ( [CLI validity]=2), [number] shall be an empty string ('') and [type] value will not be significant. Nevertheless, TA may return the recommended value 128 for [type] ((TON/NPI unknown in accordance with TS 24.008 [8] subclause 10.5.4.7). |
| When CLI has been withheld by the originator, ([CLI validity]=1) and the CLIP is provisioned with the 'override category' option (refer 3GPP TS 22.081[3] and 3GPP TS 23.081[40]), [number] and [type] is provided. Otherwise, TA shall return the same setting for [number] and [type] as if the CLI was not available. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CLIP=?</command> |
| <profile>Calling line identification presentation (Query all)</profile> |
| <description>This command refers to the GSM/UMTS supplementary service CLIP (Calling Line Identification Presentation) that enables a called subscriber to get the calling line identity (CLI) of the calling party when receiving a mobile terminated call. Set command enables or disables the presentation of the CLI at the TE. It has no effect on the execution of the supplementary service CLIP in the network. |
| When the presentation of the CLI at the TE is enabled (and calling subscriber allows), +CLIP: [number],[type][,[subaddr],[satype][,[[alpha]][,[CLI validity]]]] response is returned after every RING (or +CRING: [type]; refer subclause 'Cellular result codes +CRC') result code sent from TA to TE. It is manufacturer specific if this response is used when normal voice call is answered. |
| Read command gives the status of [n], and also triggers an interrogation of the provision status of the CLIP service according 3GPP TS 22.081 [3] (given in [m]).Test command returns values supported as a compound value. |
| Defined values |
| [n] (parameter sets/shows the result code presentation status to the TE): |
| 0 disable |
| 1 enable |
| [m] (parameter shows the subscriber CLIP service status in the network): |
| 0 CLIP not provisioned |
| 1 CLIP provisioned |
| 2 unknown (e.g. no network, etc.) |
| [number]: string type phone number of format specified by [type] |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7) |
| [subaddr]: string type subaddress of format specified by [satype] |
| [satype]: type of subaddress octet in integer format (refer TS 24.008 [8] subclause 10.5.4.8) |
| [alpha]: optional string type alphanumeric representation of [number] corresponding to the entry found in phonebook; used character set should be the one selected with command Select TE Character Set +CSCS |
| [CLI validity]: |
| 0 CLI valid |
| 1 CLI has been withheld by the originator. |
| 2 CLI is not available due to interworking problems or limitations of originating network. |
| When CLI is not available ( [CLI validity]=2), [number] shall be an empty string ('') and [type] value will not be significant. Nevertheless, TA may return the recommended value 128 for [type] ((TON/NPI unknown in accordance with TS 24.008 [8] subclause 10.5.4.7). |
| When CLI has been withheld by the originator, ([CLI validity]=1) and the CLIP is provisioned with the 'override category' option (refer 3GPP TS 22.081[3] and 3GPP TS 23.081[40]), [number] and [type] is provided. Otherwise, TA shall return the same setting for [number] and [type] as if the CLI was not available. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CLIR=</command> |
| <profile>Calling line identification restriction (Assign)</profile> |
| <description>This command refers to CLIR‑service according to 3GPP TS 22.081 [3] that allows a calling subscriber to enable or disable the presentation of the CLI to the called party when originating a call. |
| Set command overrides the CLIR subscription (default is restricted or allowed) when temporary mode is provisioned as a default adjustment for all following outgoing calls. This adjustment can be revoked by using the opposite command.. If this command is used by a subscriber without provision of CLIR in permanent mode the network will act according 3GPP TS 22.081 [3]. |
| Read command gives the default adjustment for all outgoing calls (given in [n]), and also triggers an interrogation of the provision status of the CLIR service (given in [m]). Test command returns values supported as a compound value. |
| NOTE: On a per call base CLIR functionality is explained in subclause 'ITU‑T V.250 [14] dial command'. |
| Defined values |
| [n] (parameter sets the adjustment for outgoing calls): |
| 0 presentation indicator is used according to the subscription of the CLIR service |
| 1 CLIR invocation |
| 2 CLIR suppression |
| [m] (parameter shows the subscriber CLIR service status in the network): |
| 0 CLIR not provisioned |
| 1 CLIR provisioned in permanent mode |
| 2 unknown (e.g. no network, etc.) |
| 3 CLIR temporary mode presentation restricted |
| 4 CLIR temporary mode presentation allowed |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CLIR?</command> |
| <profile>Calling line identification restriction (Query)</profile> |
| <description>This command refers to CLIR‑service according to 3GPP TS 22.081 [3] that allows a calling subscriber to enable or disable the presentation of the CLI to the called party when originating a call. |
| Set command overrides the CLIR subscription (default is restricted or allowed) when temporary mode is provisioned as a default adjustment for all following outgoing calls. This adjustment can be revoked by using the opposite command.. If this command is used by a subscriber without provision of CLIR in permanent mode the network will act according 3GPP TS 22.081 [3]. |
| Read command gives the default adjustment for all outgoing calls (given in [n]), and also triggers an interrogation of the provision status of the CLIR service (given in [m]). Test command returns values supported as a compound value. |
| NOTE: On a per call base CLIR functionality is explained in subclause 'ITU‑T V.250 [14] dial command'. |
| Defined values |
| [n] (parameter sets the adjustment for outgoing calls): |
| 0 presentation indicator is used according to the subscription of the CLIR service |
| 1 CLIR invocation |
| 2 CLIR suppression |
| [m] (parameter shows the subscriber CLIR service status in the network): |
| 0 CLIR not provisioned |
| 1 CLIR provisioned in permanent mode |
| 2 unknown (e.g. no network, etc.) |
| 3 CLIR temporary mode presentation restricted |
| 4 CLIR temporary mode presentation allowed |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CLIR=?</command> |
| <profile>Calling line identification restriction (Query all)</profile> |
| <description>This command refers to CLIR‑service according to 3GPP TS 22.081 [3] that allows a calling subscriber to enable or disable the presentation of the CLI to the called party when originating a call. |
| Set command overrides the CLIR subscription (default is restricted or allowed) when temporary mode is provisioned as a default adjustment for all following outgoing calls. This adjustment can be revoked by using the opposite command.. If this command is used by a subscriber without provision of CLIR in permanent mode the network will act according 3GPP TS 22.081 [3]. |
| Read command gives the default adjustment for all outgoing calls (given in [n]), and also triggers an interrogation of the provision status of the CLIR service (given in [m]). Test command returns values supported as a compound value. |
| NOTE: On a per call base CLIR functionality is explained in subclause 'ITU‑T V.250 [14] dial command'. |
| Defined values |
| [n] (parameter sets the adjustment for outgoing calls): |
| 0 presentation indicator is used according to the subscription of the CLIR service |
| 1 CLIR invocation |
| 2 CLIR suppression |
| [m] (parameter shows the subscriber CLIR service status in the network): |
| 0 CLIR not provisioned |
| 1 CLIR provisioned in permanent mode |
| 2 unknown (e.g. no network, etc.) |
| 3 CLIR temporary mode presentation restricted |
| 4 CLIR temporary mode presentation allowed |
| </description> |
| </spec> |
| <spec> |
| <command>AT+COLP=</command> |
| <profile>Connected line identification presentation (Assign)</profile> |
| <description>This command refers to the GSM/UMTS supplementary service COLP (Connected Line Identification Presentation) that enables a calling subscriber to get the connected line identity (COL) of the called party after setting up a mobile originated call. The command enables or disables the presentation of the COL at the TE. It has no effect on the execution of the supplementary service COLR in the network. |
| When enabled (and called subscriber allows), +COLP: |
| [number],[type][,[subaddr],[satype] [,[alpha]]] intermediate result code is returned from TA to TE before any +CR or V.250 [14] responses. It is manufacturer specific if this response is used when normal voice call is established. |
| Read command gives the status of [n], and also triggers an interrogation of the provision status of the COLP service according 3GPP TS 22.081 [3] (given in [m]). |
| Test command returns values supported as a compound value. |
| Defined values |
| [n] (parameter sets/shows the result code presentation status to the TE): |
| 0 disable |
| 1 enable |
| [m] (parameter shows the subscriber COLP service status in the network): |
| 0 COLP not provisioned |
| 1 COLP provisioned |
| 2 unknown (e.g. no network, etc.) |
| [number], [type], [subaddr], [satype], [alpha]: refer +CLIP |
| </description> |
| </spec> |
| <spec> |
| <command>AT+COLP?</command> |
| <profile>Connected line identification presentation (Query)</profile> |
| <description>This command refers to the GSM/UMTS supplementary service COLP (Connected Line Identification Presentation) that enables a calling subscriber to get the connected line identity (COL) of the called party after setting up a mobile originated call. The command enables or disables the presentation of the COL at the TE. It has no effect on the execution of the supplementary service COLR in the network. |
| When enabled (and called subscriber allows), +COLP: |
| [number],[type][,[subaddr],[satype] [,[alpha]]] intermediate result code is returned from TA to TE before any +CR or V.250 [14] responses. It is manufacturer specific if this response is used when normal voice call is established. |
| Read command gives the status of [n], and also triggers an interrogation of the provision status of the COLP service according 3GPP TS 22.081 [3] (given in [m]). |
| Test command returns values supported as a compound value. |
| Defined values |
| [n] (parameter sets/shows the result code presentation status to the TE): |
| 0 disable |
| 1 enable |
| [m] (parameter shows the subscriber COLP service status in the network): |
| 0 COLP not provisioned |
| 1 COLP provisioned |
| 2 unknown (e.g. no network, etc.) |
| [number], [type], [subaddr], [satype], [alpha]: refer +CLIP |
| </description> |
| </spec> |
| <spec> |
| <command>AT+COLP=?</command> |
| <profile>Connected line identification presentation (Query all)</profile> |
| <description>This command refers to the GSM/UMTS supplementary service COLP (Connected Line Identification Presentation) that enables a calling subscriber to get the connected line identity (COL) of the called party after setting up a mobile originated call. The command enables or disables the presentation of the COL at the TE. It has no effect on the execution of the supplementary service COLR in the network. |
| When enabled (and called subscriber allows), +COLP: |
| [number],[type][,[subaddr],[satype] [,[alpha]]] intermediate result code is returned from TA to TE before any +CR or V.250 [14] responses. It is manufacturer specific if this response is used when normal voice call is established. |
| Read command gives the status of [n], and also triggers an interrogation of the provision status of the COLP service according 3GPP TS 22.081 [3] (given in [m]). |
| Test command returns values supported as a compound value. |
| Defined values |
| [n] (parameter sets/shows the result code presentation status to the TE): |
| 0 disable |
| 1 enable |
| [m] (parameter shows the subscriber COLP service status in the network): |
| 0 COLP not provisioned |
| 1 COLP provisioned |
| 2 unknown (e.g. no network, etc.) |
| [number], [type], [subaddr], [satype], [alpha]: refer +CLIP |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CDIP=</command> |
| <profile>Called line identification presentation (Assign)</profile> |
| <description>This command related to a network service that provides 'multiple called numbers (called line identifications) service' to an MT. This command enables a called subscriber to get the called line identification of the called party when receiving a mobile terminated call. Set command enables or disables the presentation of the called line identifications at the TE. |
| When the presentation of the called line identification at the TE is enabled, +CDIP:[number],[type][,[subaddr],[satype]] response is returned after every RING (or +CRING: [type]; refer subclause 'Cellular result codes +CRC') result code sent from TA to TE. It is manufacturer specific if this response is used when normal voice call is answered. |
| Read command gives the status of [n], and also triggers an interrogation of the provision status of the 'multiple called numbers' service. Test command returns values supported as a compound value. |
| Defined values |
| [n] (parameter sets/shows the result code presentation status to the TE): |
| 0 disable |
| 1 enable |
| [m] (parameter shows the subscriber 'multiple called numbers' service status in the network): |
| 0 'multiple called numbers service' is not provisioned |
| 1 'multiple called numbers service' is provisioned |
| 2 unknown (e.g. no network, etc.) |
| [number]: string type phone number of format specified by [type] |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7) |
| [subaddr]: string type subaddress of format specified by [satype] |
| [satype]: type of subaddress octet in integer format (refer TS 24.008 [8] subclause 10.5.4.8) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CDIP?</command> |
| <profile>Called line identification presentation (Query)</profile> |
| <description>This command related to a network service that provides 'multiple called numbers (called line identifications) service' to an MT. This command enables a called subscriber to get the called line identification of the called party when receiving a mobile terminated call. Set command enables or disables the presentation of the called line identifications at the TE. |
| When the presentation of the called line identification at the TE is enabled, +CDIP:[number],[type][,[subaddr],[satype]] response is returned after every RING (or +CRING: [type]; refer subclause 'Cellular result codes +CRC') result code sent from TA to TE. It is manufacturer specific if this response is used when normal voice call is answered. |
| Read command gives the status of [n], and also triggers an interrogation of the provision status of the 'multiple called numbers' service. Test command returns values supported as a compound value. |
| Defined values |
| [n] (parameter sets/shows the result code presentation status to the TE): |
| 0 disable |
| 1 enable |
| [m] (parameter shows the subscriber 'multiple called numbers' service status in the network): |
| 0 'multiple called numbers service' is not provisioned |
| 1 'multiple called numbers service' is provisioned |
| 2 unknown (e.g. no network, etc.) |
| [number]: string type phone number of format specified by [type] |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7) |
| [subaddr]: string type subaddress of format specified by [satype] |
| [satype]: type of subaddress octet in integer format (refer TS 24.008 [8] subclause 10.5.4.8) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CDIP=?</command> |
| <profile>Called line identification presentation (Query all)</profile> |
| <description>This command related to a network service that provides 'multiple called numbers (called line identifications) service' to an MT. This command enables a called subscriber to get the called line identification of the called party when receiving a mobile terminated call. Set command enables or disables the presentation of the called line identifications at the TE. |
| When the presentation of the called line identification at the TE is enabled, +CDIP:[number],[type][,[subaddr],[satype]] response is returned after every RING (or +CRING: [type]; refer subclause 'Cellular result codes +CRC') result code sent from TA to TE. It is manufacturer specific if this response is used when normal voice call is answered. |
| Read command gives the status of [n], and also triggers an interrogation of the provision status of the 'multiple called numbers' service. Test command returns values supported as a compound value. |
| Defined values |
| [n] (parameter sets/shows the result code presentation status to the TE): |
| 0 disable |
| 1 enable |
| [m] (parameter shows the subscriber 'multiple called numbers' service status in the network): |
| 0 'multiple called numbers service' is not provisioned |
| 1 'multiple called numbers service' is provisioned |
| 2 unknown (e.g. no network, etc.) |
| [number]: string type phone number of format specified by [type] |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7) |
| [subaddr]: string type subaddress of format specified by [satype] |
| [satype]: type of subaddress octet in integer format (refer TS 24.008 [8] subclause 10.5.4.8) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CCUG=</command> |
| <profile>Closed user group (Assign)</profile> |
| <description>This command allows control of the Closed User Group supplementary service (refer 3GPP TS 22.085 [21]). Set command enables the served subscriber to select a CUG index, to suppress the Outgoing Access (OA), and to suppress the preferential CUG. |
| Set command with [n]=1 enables to control the CUG information on the air interface as a default adjustment for all following outgoing calls. The interaction of this command with other commands based on other GSM/UMTS supplementary services is described in the GSM/UMTS standard. |
| NOTE: On a per call base CUG functionality is explained in subclause 'ITU‑T V.250 [14] dial command'. |
| Defined values |
| [n]: |
| 0 disable CUG temporary mode |
| 1 enable CUG temporary mode |
| [index]: |
| 0...9 CUG index |
| 10 no index (preferred CUG taken from subscriber data) |
| [info]: |
| 0 no information |
| 1 suppress OA |
| 2 suppress preferential CUG |
| 3 suppress OA and preferential CUG |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CCUG?</command> |
| <profile>Closed user group (Query)</profile> |
| <description>This command allows control of the Closed User Group supplementary service (refer 3GPP TS 22.085 [21]). Set command enables the served subscriber to select a CUG index, to suppress the Outgoing Access (OA), and to suppress the preferential CUG. |
| Set command with [n]=1 enables to control the CUG information on the air interface as a default adjustment for all following outgoing calls. The interaction of this command with other commands based on other GSM/UMTS supplementary services is described in the GSM/UMTS standard. |
| NOTE: On a per call base CUG functionality is explained in subclause 'ITU‑T V.250 [14] dial command'. |
| Defined values |
| [n]: |
| 0 disable CUG temporary mode |
| 1 enable CUG temporary mode |
| [index]: |
| 0...9 CUG index |
| 10 no index (preferred CUG taken from subscriber data) |
| [info]: |
| 0 no information |
| 1 suppress OA |
| 2 suppress preferential CUG |
| 3 suppress OA and preferential CUG |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CCUG=?</command> |
| <profile>Closed user group (Query all)</profile> |
| <description>This command allows control of the Closed User Group supplementary service (refer 3GPP TS 22.085 [21]). Set command enables the served subscriber to select a CUG index, to suppress the Outgoing Access (OA), and to suppress the preferential CUG. |
| Set command with [n]=1 enables to control the CUG information on the air interface as a default adjustment for all following outgoing calls. The interaction of this command with other commands based on other GSM/UMTS supplementary services is described in the GSM/UMTS standard. |
| NOTE: On a per call base CUG functionality is explained in subclause 'ITU‑T V.250 [14] dial command'. |
| Defined values |
| [n]: |
| 0 disable CUG temporary mode |
| 1 enable CUG temporary mode |
| [index]: |
| 0...9 CUG index |
| 10 no index (preferred CUG taken from subscriber data) |
| [info]: |
| 0 no information |
| 1 suppress OA |
| 2 suppress preferential CUG |
| 3 suppress OA and preferential CUG |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CCFC=</command> |
| <profile>Call forwarding number and conditions (Assign)</profile> |
| <description>This command allows control of the call forwarding supplementary service according to 3GPP TS 22.082 [4]. Registration, erasure, activation, deactivation, and status query are supported. When querying the status of a network service ([mode]=2) the response line for 'not active' case ([status]=0) should be returned only if service is not active for any [class]. |
| Test command returns reason values supported as a compound value. |
| Defined values |
| [reason]: |
| 0 unconditional |
| 1 mobile busy |
| 2 no reply |
| 3 not reachable |
| 4 all call forwarding (refer 3GPP TS 22.030 [19]) |
| 5 all conditional call forwarding (refer 3GPP TS 22.030 [19]) |
| [mode]: |
| 0 disable |
| 1 enable |
| 2 query status |
| 3 registration |
| 4 erasure |
| [number]: string type phone number of forwarding address in format specified by [type] |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7); default 145 when dialling string includes international access code character '+', otherwise 129 |
| [subaddr]: string type subaddress of format specified by [satype] |
| [satype]: type of subaddress octet in integer format (refer TS 24.008 [8] subclause 10.5.4.8); default 128 |
| [classx] is a sum of integers each representing a class of information (default 7): |
| 1 voice (telephony) |
| 2 data (refers to all bearer services; with [mode]=2 this may refer only to some bearer service if TA does not support values 16, 32, 64 and 128) |
| 4 fax (facsimile services) |
| 8 short message service |
| 16 data circuit sync |
| 32 data circuit async |
| 64 dedicated packet access |
| 128 dedicated PAD access |
| [time]: |
| 1...30 when 'no reply' is enabled or queried, this gives the time in seconds to wait before call is forwarded, default value 20 |
| [status]: |
| 0 not active |
| 1 active |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CCFC=?</command> |
| <profile>Call forwarding number and conditions (Query all)</profile> |
| <description>This command allows control of the call forwarding supplementary service according to 3GPP TS 22.082 [4]. Registration, erasure, activation, deactivation, and status query are supported. When querying the status of a network service ([mode]=2) the response line for 'not active' case ([status]=0) should be returned only if service is not active for any [class]. |
| Test command returns reason values supported as a compound value. |
| Defined values |
| [reason]: |
| 0 unconditional |
| 1 mobile busy |
| 2 no reply |
| 3 not reachable |
| 4 all call forwarding (refer 3GPP TS 22.030 [19]) |
| 5 all conditional call forwarding (refer 3GPP TS 22.030 [19]) |
| [mode]: |
| 0 disable |
| 1 enable |
| 2 query status |
| 3 registration |
| 4 erasure |
| [number]: string type phone number of forwarding address in format specified by [type] |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7); default 145 when dialling string includes international access code character '+', otherwise 129 |
| [subaddr]: string type subaddress of format specified by [satype] |
| [satype]: type of subaddress octet in integer format (refer TS 24.008 [8] subclause 10.5.4.8); default 128 |
| [classx] is a sum of integers each representing a class of information (default 7): |
| 1 voice (telephony) |
| 2 data (refers to all bearer services; with [mode]=2 this may refer only to some bearer service if TA does not support values 16, 32, 64 and 128) |
| 4 fax (facsimile services) |
| 8 short message service |
| 16 data circuit sync |
| 32 data circuit async |
| 64 dedicated packet access |
| 128 dedicated PAD access |
| [time]: |
| 1...30 when 'no reply' is enabled or queried, this gives the time in seconds to wait before call is forwarded, default value 20 |
| [status]: |
| 0 not active |
| 1 active |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CCWA=</command> |
| <profile>Call waiting (Assign)</profile> |
| <description>This command allows control of the Call Waiting supplementary service according to 3GPP TS 22.083 [5]. Activation, deactivation and status query are supported. When querying the status of a network service ([mode]=2) the response line for 'not active' case ([status]=0) should be returned only if service is not active for any [class]. Parameter [n] is used to disable/enable the presentation of an unsolicited result code +CCWA: [number],[type],[class],[[alpha]][,[CLI validity][,[subaddr],[satype] [,[priority] ]]] to the TE when call waiting service is enabled. Command should be abortable when network is interrogated. |
| The interaction of this command with other commands based on other GSM/UMTS supplementary services is described in the GSM/UMTS standards. |
| Test command returns values supported as a compound value. |
| Defined values |
| [n] (sets/shows the result code presentation status to the TE): |
| 0 disable |
| 1 enable |
| [mode] (when [mode] parameter is not given, network is not interrogated): |
| 0 disable |
| 1 enable |
| 2 query status |
| [classx] is a sum of integers each representing a class of information (default 7): |
| 1 voice (telephony) |
| 2 data (refers to all bearer services; with [mode]=2 this may refer only to some bearer service if TA does not support values 16, 32, 64 and 128) |
| 4 fax (facsimile services) |
| 8 short message service |
| 16 data circuit sync |
| 32 data circuit async |
| 64 dedicated packet access |
| 128 dedicated PAD access |
| [status]: |
| 0 not active |
| 1 active |
| [number]: string type phone number of calling address in format specified by [type] |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7) |
| [alpha]: optional string type alphanumeric representation of [number] corresponding to the entry found in phonebook; used character set should be the one selected with command Select TE Character Set +CSCS |
| [CLI validity]: |
| 0 CLI valid |
| 1 CLI has been withheld by the originator. |
| 2 CLI is not available due to interworking problems or limitations of originating network. |
| When CLI is not available ([CLI validity]=2), [number] shall be an empty string ('') and [type] value will not be significant. Nevertheless, TA may return the recommended value 128 for [type] ((TON/NPI unknown in accordance with TS 24.008 [8] subclause 10.5.4.7). |
| When CLI has been withheld by the originator, ([CLI validity]=1) and the CLIP is provisioned with the 'override category' option (refer 3GPP TS 22.081[3] and 3GPP TS 23.081[40]), [number] and [type] is provided. Otherwise, TA shall return the same setting for [number] and [type] as if the CLI was not available. |
| [subaddr]: string type subaddress of format specified by [satype] |
| [satype]: type of subaddress octet in integer format (refer TS 24.008 [8] subclause 10.5.4.8) |
| [priority]: optional digit type parameter indicating that the eMLPP priority level of the incoming call. The priority level values are as defined in eMLPP specification 3GPP TS 22.067 [54]. |
| |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CCWA?</command> |
| <profile>Call waiting (Query)</profile> |
| <description>This command allows control of the Call Waiting supplementary service according to 3GPP TS 22.083 [5]. Activation, deactivation and status query are supported. When querying the status of a network service ([mode]=2) the response line for 'not active' case ([status]=0) should be returned only if service is not active for any [class]. Parameter [n] is used to disable/enable the presentation of an unsolicited result code +CCWA: [number],[type],[class],[[alpha]][,[CLI validity][,[subaddr],[satype] [,[priority] ]]] to the TE when call waiting service is enabled. Command should be abortable when network is interrogated. |
| The interaction of this command with other commands based on other GSM/UMTS supplementary services is described in the GSM/UMTS standards. |
| Test command returns values supported as a compound value. |
| Defined values |
| [n] (sets/shows the result code presentation status to the TE): |
| 0 disable |
| 1 enable |
| [mode] (when [mode] parameter is not given, network is not interrogated): |
| 0 disable |
| 1 enable |
| 2 query status |
| [classx] is a sum of integers each representing a class of information (default 7): |
| 1 voice (telephony) |
| 2 data (refers to all bearer services; with [mode]=2 this may refer only to some bearer service if TA does not support values 16, 32, 64 and 128) |
| 4 fax (facsimile services) |
| 8 short message service |
| 16 data circuit sync |
| 32 data circuit async |
| 64 dedicated packet access |
| 128 dedicated PAD access |
| [status]: |
| 0 not active |
| 1 active |
| [number]: string type phone number of calling address in format specified by [type] |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7) |
| [alpha]: optional string type alphanumeric representation of [number] corresponding to the entry found in phonebook; used character set should be the one selected with command Select TE Character Set +CSCS |
| [CLI validity]: |
| 0 CLI valid |
| 1 CLI has been withheld by the originator. |
| 2 CLI is not available due to interworking problems or limitations of originating network. |
| When CLI is not available ([CLI validity]=2), [number] shall be an empty string ('') and [type] value will not be significant. Nevertheless, TA may return the recommended value 128 for [type] ((TON/NPI unknown in accordance with TS 24.008 [8] subclause 10.5.4.7). |
| When CLI has been withheld by the originator, ([CLI validity]=1) and the CLIP is provisioned with the 'override category' option (refer 3GPP TS 22.081[3] and 3GPP TS 23.081[40]), [number] and [type] is provided. Otherwise, TA shall return the same setting for [number] and [type] as if the CLI was not available. |
| [subaddr]: string type subaddress of format specified by [satype] |
| [satype]: type of subaddress octet in integer format (refer TS 24.008 [8] subclause 10.5.4.8) |
| [priority]: optional digit type parameter indicating that the eMLPP priority level of the incoming call. The priority level values are as defined in eMLPP specification 3GPP TS 22.067 [54]. |
| |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CCWA=?</command> |
| <profile>Call waiting (Query all)</profile> |
| <description>This command allows control of the Call Waiting supplementary service according to 3GPP TS 22.083 [5]. Activation, deactivation and status query are supported. When querying the status of a network service ([mode]=2) the response line for 'not active' case ([status]=0) should be returned only if service is not active for any [class]. Parameter [n] is used to disable/enable the presentation of an unsolicited result code +CCWA: [number],[type],[class],[[alpha]][,[CLI validity][,[subaddr],[satype] [,[priority] ]]] to the TE when call waiting service is enabled. Command should be abortable when network is interrogated. |
| The interaction of this command with other commands based on other GSM/UMTS supplementary services is described in the GSM/UMTS standards. |
| Test command returns values supported as a compound value. |
| Defined values |
| [n] (sets/shows the result code presentation status to the TE): |
| 0 disable |
| 1 enable |
| [mode] (when [mode] parameter is not given, network is not interrogated): |
| 0 disable |
| 1 enable |
| 2 query status |
| [classx] is a sum of integers each representing a class of information (default 7): |
| 1 voice (telephony) |
| 2 data (refers to all bearer services; with [mode]=2 this may refer only to some bearer service if TA does not support values 16, 32, 64 and 128) |
| 4 fax (facsimile services) |
| 8 short message service |
| 16 data circuit sync |
| 32 data circuit async |
| 64 dedicated packet access |
| 128 dedicated PAD access |
| [status]: |
| 0 not active |
| 1 active |
| [number]: string type phone number of calling address in format specified by [type] |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7) |
| [alpha]: optional string type alphanumeric representation of [number] corresponding to the entry found in phonebook; used character set should be the one selected with command Select TE Character Set +CSCS |
| [CLI validity]: |
| 0 CLI valid |
| 1 CLI has been withheld by the originator. |
| 2 CLI is not available due to interworking problems or limitations of originating network. |
| When CLI is not available ([CLI validity]=2), [number] shall be an empty string ('') and [type] value will not be significant. Nevertheless, TA may return the recommended value 128 for [type] ((TON/NPI unknown in accordance with TS 24.008 [8] subclause 10.5.4.7). |
| When CLI has been withheld by the originator, ([CLI validity]=1) and the CLIP is provisioned with the 'override category' option (refer 3GPP TS 22.081[3] and 3GPP TS 23.081[40]), [number] and [type] is provided. Otherwise, TA shall return the same setting for [number] and [type] as if the CLI was not available. |
| [subaddr]: string type subaddress of format specified by [satype] |
| [satype]: type of subaddress octet in integer format (refer TS 24.008 [8] subclause 10.5.4.8) |
| [priority]: optional digit type parameter indicating that the eMLPP priority level of the incoming call. The priority level values are as defined in eMLPP specification 3GPP TS 22.067 [54]. |
| |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CHLD=</command> |
| <profile>Call related supplementary services (Assign)</profile> |
| <description>This command allows the control of the following call related services: |
| - a call can be temporarily disconnected from the MT but the connection is retained by the network; |
| - multiparty conversation (conference calls); |
| - the served subscriber who has two calls (one held and the other either active or alerting) can connect the other parties and release the served subscriber's own connection. |
| Calls can be put on hold, recovered, released, added to conversation, and transferred similarly as defined in 3GPP TS 22.030 [19]. Refer subclause 9.2 for possible [err] values. |
| This is based on the GSM/UMTS supplementary services HOLD (Call Hold; refer 3GPP TS 22.083 [5] clause 2), MPTY (MultiParty; refer 3GPP TS 22.084 [22]) and ECT (Explicit Call Transfer; refer 3GPP TS 22.091 [29]). The interaction of this command with other commands based on other GSM/UMTS supplementary services is described in the GSM/UMTS standards. |
| NOTE: Call Hold, MultiParty and Explicit Call Transfer are only applicable to teleservice 11. |
| It is recommended (although optional) that test command returns a list of operations which are supported. The call number required by some operations shall be denoted by 'x' (e.g. +CHLD: (0,1,1x,2,2x,3)). |
| Defined values |
| [n]: integer type; equals to numbers entered before SEND button in 3GPP TS 22.030 [19] subclause 6.5.5.1 |
| NOTE: The 'directory number' case shall be handled with dial command D, and the END case with hangup command H (or +CHUP). The 4*'directory number' case is handled with +CTFR command. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CHLD=?</command> |
| <profile>Call related supplementary services (Query all)</profile> |
| <description>This command allows the control of the following call related services: |
| - a call can be temporarily disconnected from the MT but the connection is retained by the network; |
| - multiparty conversation (conference calls); |
| - the served subscriber who has two calls (one held and the other either active or alerting) can connect the other parties and release the served subscriber's own connection. |
| Calls can be put on hold, recovered, released, added to conversation, and transferred similarly as defined in 3GPP TS 22.030 [19]. Refer subclause 9.2 for possible [err] values. |
| This is based on the GSM/UMTS supplementary services HOLD (Call Hold; refer 3GPP TS 22.083 [5] clause 2), MPTY (MultiParty; refer 3GPP TS 22.084 [22]) and ECT (Explicit Call Transfer; refer 3GPP TS 22.091 [29]). The interaction of this command with other commands based on other GSM/UMTS supplementary services is described in the GSM/UMTS standards. |
| NOTE: Call Hold, MultiParty and Explicit Call Transfer are only applicable to teleservice 11. |
| It is recommended (although optional) that test command returns a list of operations which are supported. The call number required by some operations shall be denoted by 'x' (e.g. +CHLD: (0,1,1x,2,2x,3)). |
| Defined values |
| [n]: integer type; equals to numbers entered before SEND button in 3GPP TS 22.030 [19] subclause 6.5.5.1 |
| NOTE: The 'directory number' case shall be handled with dial command D, and the END case with hangup command H (or +CHUP). The 4*'directory number' case is handled with +CTFR command. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CTFR=</command> |
| <profile>Call deflection (Assign)</profile> |
| <description>This refers to a service that causes an incoming alerting call to be forwarded to a specified number. Action command does this. Refer subclause 9.2 for possible [err] values. |
| This is based on the GSM/UMTS supplementary service CD (Call Deflection; refer 3GPP TS 22.072 [30]). The interaction of this command with other commands based on other GSM/UMTS supplementary services is described in the GSM/UMTS standards. |
| NOTE: Call Deflection is only applicable to teleservice 11. |
| Defined values |
| [number]: string type phone number of format specified by [type] |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7); default 145 when dialling string includes international access code character '+', otherwise 129 |
| [subaddr]: string type subaddress of format specified by [satype] |
| [satype]: type of subaddress octet in integer format (refer TS 24.008 [8] subclause 10.5.4.8); default 128 |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CTFR=?</command> |
| <profile>Call deflection (Query all)</profile> |
| <description>This refers to a service that causes an incoming alerting call to be forwarded to a specified number. Action command does this. Refer subclause 9.2 for possible [err] values. |
| This is based on the GSM/UMTS supplementary service CD (Call Deflection; refer 3GPP TS 22.072 [30]). The interaction of this command with other commands based on other GSM/UMTS supplementary services is described in the GSM/UMTS standards. |
| NOTE: Call Deflection is only applicable to teleservice 11. |
| Defined values |
| [number]: string type phone number of format specified by [type] |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7); default 145 when dialling string includes international access code character '+', otherwise 129 |
| [subaddr]: string type subaddress of format specified by [satype] |
| [satype]: type of subaddress octet in integer format (refer TS 24.008 [8] subclause 10.5.4.8); default 128 |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CUSD=</command> |
| <profile>Unstructured supplementary service data (Assign)</profile> |
| <description>This command allows control of the Unstuctured Supplementary Service Data (USSD) according to 3GPP TS 22.090 [23]. Both network and mobile initiated operations are supported. Parameter [n] is used to disable/enable the presentation of an unsolicited result code (USSD response from the network, or network initiated operation) +CUSD: [m][,[str],[dcs]] to the TE. In addition, value [n]=2 is used to cancel an ongoing USSD session. |
| When [str] is given, a mobile initiated USSD‑string or a response USSD‑string to a network initiated operation is sent to the network. The response USSD‑string from the network is returned in a subsequent unsolicited +CUSD result code. |
| NOTE: In case of successful mobile initiated operation, TA implemented according to a version prior to 6 of this standard, waits the USSD response from the network and sends it to the TE before the final result code. This will block the AT command interface for the period of the operation. Such TA does not support [n] value 2. |
| The interaction of this command with other commands based on other GSM/UMTS supplementary services is described in the GSM/UMTS standards. |
| Test command returns values supported as a compound value. |
| Defined values |
| [n]: |
| 0 disable the result code presentation to the TE |
| 1 enable the result code presentation to the TE |
| 2 cancel session (not applicable to read command response) |
| [str]: string type USSD‑string (when [str] parameter is not given, network is not interrogated): |
| ‑ if [dcs] indicates that 3GPP TS 23.038 [25] 7 bit default alphabet is used: |
| ‑ if TE character set other than 'HEX' (refer command Select TE Character Set +CSCS): MT/TA converts GSM alphabet into current TE character set according to rules of 3GPP TS 27.005 [24] Annex A |
| ‑ if TE character set is 'HEX': MT/TA converts each 7‑bit character of GSM alphabet into two IRA character long hexadecimal number (e.g. character (GSM 23) is presented as 17 (IRA 49 and 55)) |
| ‑ if [dcs] indicates that 8‑bit data coding scheme is used: MT/TA converts each 8‑bit octet into two IRA character long hexadecimal number (e.g. octet with integer value 42 is presented to TE as two characters 2A (IRA 50 and 65)) |
| [dcs]: 3GPP TS 23.038 [25] Cell Broadcast Data Coding Scheme in integer format (default 0) |
| [m]: |
| 0 no further user action required (network initiated USSD‑Notify, or no further information needed after mobile initiated operation) |
| 1 further user action required (network initiated USSD‑Request, or further information needed after mobile initiated operation) |
| 2 USSD terminated by network |
| 3 other local client has responded |
| 4 operation not supported |
| 5 network time out |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CUSD?</command> |
| <profile>Unstructured supplementary service data (Query)</profile> |
| <description>This command allows control of the Unstuctured Supplementary Service Data (USSD) according to 3GPP TS 22.090 [23]. Both network and mobile initiated operations are supported. Parameter [n] is used to disable/enable the presentation of an unsolicited result code (USSD response from the network, or network initiated operation) +CUSD: [m][,[str],[dcs]] to the TE. In addition, value [n]=2 is used to cancel an ongoing USSD session. |
| When [str] is given, a mobile initiated USSD‑string or a response USSD‑string to a network initiated operation is sent to the network. The response USSD‑string from the network is returned in a subsequent unsolicited +CUSD result code. |
| NOTE: In case of successful mobile initiated operation, TA implemented according to a version prior to 6 of this standard, waits the USSD response from the network and sends it to the TE before the final result code. This will block the AT command interface for the period of the operation. Such TA does not support [n] value 2. |
| The interaction of this command with other commands based on other GSM/UMTS supplementary services is described in the GSM/UMTS standards. |
| Test command returns values supported as a compound value. |
| Defined values |
| [n]: |
| 0 disable the result code presentation to the TE |
| 1 enable the result code presentation to the TE |
| 2 cancel session (not applicable to read command response) |
| [str]: string type USSD‑string (when [str] parameter is not given, network is not interrogated): |
| ‑ if [dcs] indicates that 3GPP TS 23.038 [25] 7 bit default alphabet is used: |
| ‑ if TE character set other than 'HEX' (refer command Select TE Character Set +CSCS): MT/TA converts GSM alphabet into current TE character set according to rules of 3GPP TS 27.005 [24] Annex A |
| ‑ if TE character set is 'HEX': MT/TA converts each 7‑bit character of GSM alphabet into two IRA character long hexadecimal number (e.g. character (GSM 23) is presented as 17 (IRA 49 and 55)) |
| ‑ if [dcs] indicates that 8‑bit data coding scheme is used: MT/TA converts each 8‑bit octet into two IRA character long hexadecimal number (e.g. octet with integer value 42 is presented to TE as two characters 2A (IRA 50 and 65)) |
| [dcs]: 3GPP TS 23.038 [25] Cell Broadcast Data Coding Scheme in integer format (default 0) |
| [m]: |
| 0 no further user action required (network initiated USSD‑Notify, or no further information needed after mobile initiated operation) |
| 1 further user action required (network initiated USSD‑Request, or further information needed after mobile initiated operation) |
| 2 USSD terminated by network |
| 3 other local client has responded |
| 4 operation not supported |
| 5 network time out |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CUSD=?</command> |
| <profile>Unstructured supplementary service data (Query all)</profile> |
| <description>This command allows control of the Unstuctured Supplementary Service Data (USSD) according to 3GPP TS 22.090 [23]. Both network and mobile initiated operations are supported. Parameter [n] is used to disable/enable the presentation of an unsolicited result code (USSD response from the network, or network initiated operation) +CUSD: [m][,[str],[dcs]] to the TE. In addition, value [n]=2 is used to cancel an ongoing USSD session. |
| When [str] is given, a mobile initiated USSD‑string or a response USSD‑string to a network initiated operation is sent to the network. The response USSD‑string from the network is returned in a subsequent unsolicited +CUSD result code. |
| NOTE: In case of successful mobile initiated operation, TA implemented according to a version prior to 6 of this standard, waits the USSD response from the network and sends it to the TE before the final result code. This will block the AT command interface for the period of the operation. Such TA does not support [n] value 2. |
| The interaction of this command with other commands based on other GSM/UMTS supplementary services is described in the GSM/UMTS standards. |
| Test command returns values supported as a compound value. |
| Defined values |
| [n]: |
| 0 disable the result code presentation to the TE |
| 1 enable the result code presentation to the TE |
| 2 cancel session (not applicable to read command response) |
| [str]: string type USSD‑string (when [str] parameter is not given, network is not interrogated): |
| ‑ if [dcs] indicates that 3GPP TS 23.038 [25] 7 bit default alphabet is used: |
| ‑ if TE character set other than 'HEX' (refer command Select TE Character Set +CSCS): MT/TA converts GSM alphabet into current TE character set according to rules of 3GPP TS 27.005 [24] Annex A |
| ‑ if TE character set is 'HEX': MT/TA converts each 7‑bit character of GSM alphabet into two IRA character long hexadecimal number (e.g. character (GSM 23) is presented as 17 (IRA 49 and 55)) |
| ‑ if [dcs] indicates that 8‑bit data coding scheme is used: MT/TA converts each 8‑bit octet into two IRA character long hexadecimal number (e.g. octet with integer value 42 is presented to TE as two characters 2A (IRA 50 and 65)) |
| [dcs]: 3GPP TS 23.038 [25] Cell Broadcast Data Coding Scheme in integer format (default 0) |
| [m]: |
| 0 no further user action required (network initiated USSD‑Notify, or no further information needed after mobile initiated operation) |
| 1 further user action required (network initiated USSD‑Request, or further information needed after mobile initiated operation) |
| 2 USSD terminated by network |
| 3 other local client has responded |
| 4 operation not supported |
| 5 network time out |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CAOC[=</command> |
| <profile>Advice of Charge (Assign)</profile> |
| <description>This refers to Advice of Charge supplementary service (3GPP TS 22.024 [26] and 3GPP TS 22.086 [27]) that enables subscriber to get information about the cost of calls. With [mode]=0, the execute command returns the current call meter value from the MT. |
| The command also includes the possibility to enable an unsolicited event reporting of the CCM information. The unsolicited result code +CCCM: [ccm] is sent when the CCM value changes, but not more that every 10 seconds. Deactivation of the unsolicited event reporting is made with the same command. |
| Refer subclause 9.2 for possible [err] values. |
| NOTE: Advice of Charge values stored in the SIM card or in the active application in the UICC (GSM or USIM) (ACM, ACMmax, PUCT) can be accessed with generic or restricted SIM access command (+CSIM or +CRSM)).Those values can be more readily accessed with commands +CACM, +CAMM and +CPUC. |
| The Read command indicates whether the unsolicited reporting is activated or not. Read command is available when the unsolicited result code is supported. |
| It is recommended (although optional) that the test command returns the supported mode values. |
| Defined values |
| [mode]: |
| 0 query CCM value |
| 1 deactivate the unsolicited reporting of CCM value |
| 2 activate the unsolicited reporting of CCM value |
| [ccm]: string type; three bytes of the current call meter value in hexadecimal format (e.g. '00001E' indicates decimal value 30); value is in home units and bytes are similarly coded as ACMmax value in the SIM card or in the active application in the UICC (GSM or USIM) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CAOC?</command> |
| <profile>Advice of Charge (Query)</profile> |
| <description>This refers to Advice of Charge supplementary service (3GPP TS 22.024 [26] and 3GPP TS 22.086 [27]) that enables subscriber to get information about the cost of calls. With [mode]=0, the execute command returns the current call meter value from the MT. |
| The command also includes the possibility to enable an unsolicited event reporting of the CCM information. The unsolicited result code +CCCM: [ccm] is sent when the CCM value changes, but not more that every 10 seconds. Deactivation of the unsolicited event reporting is made with the same command. |
| Refer subclause 9.2 for possible [err] values. |
| NOTE: Advice of Charge values stored in the SIM card or in the active application in the UICC (GSM or USIM) (ACM, ACMmax, PUCT) can be accessed with generic or restricted SIM access command (+CSIM or +CRSM)).Those values can be more readily accessed with commands +CACM, +CAMM and +CPUC. |
| The Read command indicates whether the unsolicited reporting is activated or not. Read command is available when the unsolicited result code is supported. |
| It is recommended (although optional) that the test command returns the supported mode values. |
| Defined values |
| [mode]: |
| 0 query CCM value |
| 1 deactivate the unsolicited reporting of CCM value |
| 2 activate the unsolicited reporting of CCM value |
| [ccm]: string type; three bytes of the current call meter value in hexadecimal format (e.g. '00001E' indicates decimal value 30); value is in home units and bytes are similarly coded as ACMmax value in the SIM card or in the active application in the UICC (GSM or USIM) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CAOC=?</command> |
| <profile>Advice of Charge (Query all)</profile> |
| <description>This refers to Advice of Charge supplementary service (3GPP TS 22.024 [26] and 3GPP TS 22.086 [27]) that enables subscriber to get information about the cost of calls. With [mode]=0, the execute command returns the current call meter value from the MT. |
| The command also includes the possibility to enable an unsolicited event reporting of the CCM information. The unsolicited result code +CCCM: [ccm] is sent when the CCM value changes, but not more that every 10 seconds. Deactivation of the unsolicited event reporting is made with the same command. |
| Refer subclause 9.2 for possible [err] values. |
| NOTE: Advice of Charge values stored in the SIM card or in the active application in the UICC (GSM or USIM) (ACM, ACMmax, PUCT) can be accessed with generic or restricted SIM access command (+CSIM or +CRSM)).Those values can be more readily accessed with commands +CACM, +CAMM and +CPUC. |
| The Read command indicates whether the unsolicited reporting is activated or not. Read command is available when the unsolicited result code is supported. |
| It is recommended (although optional) that the test command returns the supported mode values. |
| Defined values |
| [mode]: |
| 0 query CCM value |
| 1 deactivate the unsolicited reporting of CCM value |
| 2 activate the unsolicited reporting of CCM value |
| [ccm]: string type; three bytes of the current call meter value in hexadecimal format (e.g. '00001E' indicates decimal value 30); value is in home units and bytes are similarly coded as ACMmax value in the SIM card or in the active application in the UICC (GSM or USIM) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSSN=</command> |
| <profile>Supplementary service notifications (Assign)</profile> |
| <description>This command refers to supplementary service related network initiated notifications. The set command enables/disables the presentation of notification result codes from TA to TE. |
| When [n]=1 and a supplementary service notification is received after a mobile originated call setup, intermediate result code +CSSI: [code1][,[index]] is sent to TE before any other MO call setup result codes presented in the present document or in V.250 [14]. When several different [code1]s are received from the network, each of them shall have its own +CSSI result code. |
| When [m]=1 and a supplementary service notification is received during a mobile terminated call setup or during a call, or when a forward check supplementary service notification is received, unsolicited result code +CSSU: [code2][,[index][,[number],[type][,[subaddr],[satype]]]] is sent to TE. In case of MT call setup, result code is sent after every +CLIP result code (refer command 'Calling line identification presentation +CLIP') and when several different [code2]s are received from the network, each of them shall have its own +CSSU result code. |
| Test command returns values supported as a compound value. |
| Defined values |
| [n] (parameter sets/shows the +CSSI result code presentation status to the TE): |
| 0 disable |
| 1 enable |
| [m] (parameter sets/shows the +CSSU result code presentation status to the TE): |
| 0 disable |
| 1 enable |
| [code1] (it is manufacturer specific, which of these codes are supported): |
| 0 unconditional call forwarding is active |
| 1 some of the conditional call forwardings are active |
| 2 call has been forwarded |
| 3 call is waiting |
| 4 this is a CUG call (also [index] present) |
| 5 outgoing calls are barred |
| 6 incoming calls are barred |
| 7 CLIR suppression rejected |
| 8 call has been deflected |
| [index]: refer 'Closed user group +CCUG' |
| [code2] (it is manufacturer specific, which of these codes are supported): |
| 0 this is a forwarded call (MT call setup) |
| 1 this is a CUG call (also [index] present) (MT call setup) |
| 2 call has been put on hold (during a voice call) |
| 3 call has been retrieved (during a voice call) |
| 4 multiparty call entered (during a voice call) |
| 5 call on hold has been released (this is not a SS notification) (during a voice call) |
| 6 forward check SS message received (can be received whenever) |
| 7 call is being connected (alerting) with the remote party in alerting state in explicit call transfer operation (during a voice call) |
| 8 call has been connected with the other remote party in explicit call transfer operation (also number and subaddress parameters may be present) (during a voice call or MT call setup) |
| 9 this is a deflected call (MT call setup) |
| 10 sdditional incoming call forwarded |
| [number]: string type phone number of format specified by [type] |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7) |
| [subaddr]: string type subaddress of format specified by [satype] |
| [satype]: type of subaddress octet in integer format (refer TS 24.008 [8] subclause 10.5.4.8) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSSN?</command> |
| <profile>Supplementary service notifications (Query)</profile> |
| <description>This command refers to supplementary service related network initiated notifications. The set command enables/disables the presentation of notification result codes from TA to TE. |
| When [n]=1 and a supplementary service notification is received after a mobile originated call setup, intermediate result code +CSSI: [code1][,[index]] is sent to TE before any other MO call setup result codes presented in the present document or in V.250 [14]. When several different [code1]s are received from the network, each of them shall have its own +CSSI result code. |
| When [m]=1 and a supplementary service notification is received during a mobile terminated call setup or during a call, or when a forward check supplementary service notification is received, unsolicited result code +CSSU: [code2][,[index][,[number],[type][,[subaddr],[satype]]]] is sent to TE. In case of MT call setup, result code is sent after every +CLIP result code (refer command 'Calling line identification presentation +CLIP') and when several different [code2]s are received from the network, each of them shall have its own +CSSU result code. |
| Test command returns values supported as a compound value. |
| Defined values |
| [n] (parameter sets/shows the +CSSI result code presentation status to the TE): |
| 0 disable |
| 1 enable |
| [m] (parameter sets/shows the +CSSU result code presentation status to the TE): |
| 0 disable |
| 1 enable |
| [code1] (it is manufacturer specific, which of these codes are supported): |
| 0 unconditional call forwarding is active |
| 1 some of the conditional call forwardings are active |
| 2 call has been forwarded |
| 3 call is waiting |
| 4 this is a CUG call (also [index] present) |
| 5 outgoing calls are barred |
| 6 incoming calls are barred |
| 7 CLIR suppression rejected |
| 8 call has been deflected |
| [index]: refer 'Closed user group +CCUG' |
| [code2] (it is manufacturer specific, which of these codes are supported): |
| 0 this is a forwarded call (MT call setup) |
| 1 this is a CUG call (also [index] present) (MT call setup) |
| 2 call has been put on hold (during a voice call) |
| 3 call has been retrieved (during a voice call) |
| 4 multiparty call entered (during a voice call) |
| 5 call on hold has been released (this is not a SS notification) (during a voice call) |
| 6 forward check SS message received (can be received whenever) |
| 7 call is being connected (alerting) with the remote party in alerting state in explicit call transfer operation (during a voice call) |
| 8 call has been connected with the other remote party in explicit call transfer operation (also number and subaddress parameters may be present) (during a voice call or MT call setup) |
| 9 this is a deflected call (MT call setup) |
| 10 sdditional incoming call forwarded |
| [number]: string type phone number of format specified by [type] |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7) |
| [subaddr]: string type subaddress of format specified by [satype] |
| [satype]: type of subaddress octet in integer format (refer TS 24.008 [8] subclause 10.5.4.8) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSSN=?</command> |
| <profile>Supplementary service notifications (Query all)</profile> |
| <description>This command refers to supplementary service related network initiated notifications. The set command enables/disables the presentation of notification result codes from TA to TE. |
| When [n]=1 and a supplementary service notification is received after a mobile originated call setup, intermediate result code +CSSI: [code1][,[index]] is sent to TE before any other MO call setup result codes presented in the present document or in V.250 [14]. When several different [code1]s are received from the network, each of them shall have its own +CSSI result code. |
| When [m]=1 and a supplementary service notification is received during a mobile terminated call setup or during a call, or when a forward check supplementary service notification is received, unsolicited result code +CSSU: [code2][,[index][,[number],[type][,[subaddr],[satype]]]] is sent to TE. In case of MT call setup, result code is sent after every +CLIP result code (refer command 'Calling line identification presentation +CLIP') and when several different [code2]s are received from the network, each of them shall have its own +CSSU result code. |
| Test command returns values supported as a compound value. |
| Defined values |
| [n] (parameter sets/shows the +CSSI result code presentation status to the TE): |
| 0 disable |
| 1 enable |
| [m] (parameter sets/shows the +CSSU result code presentation status to the TE): |
| 0 disable |
| 1 enable |
| [code1] (it is manufacturer specific, which of these codes are supported): |
| 0 unconditional call forwarding is active |
| 1 some of the conditional call forwardings are active |
| 2 call has been forwarded |
| 3 call is waiting |
| 4 this is a CUG call (also [index] present) |
| 5 outgoing calls are barred |
| 6 incoming calls are barred |
| 7 CLIR suppression rejected |
| 8 call has been deflected |
| [index]: refer 'Closed user group +CCUG' |
| [code2] (it is manufacturer specific, which of these codes are supported): |
| 0 this is a forwarded call (MT call setup) |
| 1 this is a CUG call (also [index] present) (MT call setup) |
| 2 call has been put on hold (during a voice call) |
| 3 call has been retrieved (during a voice call) |
| 4 multiparty call entered (during a voice call) |
| 5 call on hold has been released (this is not a SS notification) (during a voice call) |
| 6 forward check SS message received (can be received whenever) |
| 7 call is being connected (alerting) with the remote party in alerting state in explicit call transfer operation (during a voice call) |
| 8 call has been connected with the other remote party in explicit call transfer operation (also number and subaddress parameters may be present) (during a voice call or MT call setup) |
| 9 this is a deflected call (MT call setup) |
| 10 sdditional incoming call forwarded |
| [number]: string type phone number of format specified by [type] |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7) |
| [subaddr]: string type subaddress of format specified by [satype] |
| [satype]: type of subaddress octet in integer format (refer TS 24.008 [8] subclause 10.5.4.8) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CLCC</command> |
| <profile>List current calls </profile> |
| <description>Returns list of current calls of MT. If command succeeds but no calls are available, no information response is sent to TE. Refer subclause 9.2 for possible [err] values. |
| Defined values |
| [idx]: integer type; call identification number as described in 3GPP TS 22.030 [19] subclause 4.5.5.1; this number can be used in +CHLD command operations |
| [dir]: |
| 0 mobile originated (MO) call |
| 1 mobile terminated (MT) call |
| [stat] (state of the call): |
| 0 active |
| 1 held |
| 2 dialing (MO call) |
| 3 alerting (MO call) |
| 4 incoming (MT call) |
| 5 waiting (MT call) |
| [mode] (bearer/teleservice): |
| 0 voice |
| 1 data |
| 2 fax |
| 3 voice followed by data, voice mode |
| 4 alternating voice/data, voice mode |
| 5 alternating voice/fax, voice mode |
| 6 voice followed by data, data mode |
| 7 alternating voice/data, data mode |
| 8 alternating voice/fax, fax mode |
| 9 unknown |
| [mpty]: |
| 0 call is not one of multiparty (conference) call parties |
| 1 call is one of multiparty (conference) call parties |
| [number]: string type phone number in format specified by [type] |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7) |
| [alpha]: string type alphanumeric representation of [number] corresponding to the entry found in phonebook; used character set should be the one selected with command Select TE Character Set +CSCS |
| [priority]: optional digit type parameter indicating the eMLPP priority level of the call, values specified in 3GPP TS 22.067 [54] |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CLCC=?</command> |
| <profile>List current calls (Query all)</profile> |
| <description>Returns list of current calls of MT. If command succeeds but no calls are available, no information response is sent to TE. Refer subclause 9.2 for possible [err] values. |
| Defined values |
| [idx]: integer type; call identification number as described in 3GPP TS 22.030 [19] subclause 4.5.5.1; this number can be used in +CHLD command operations |
| [dir]: |
| 0 mobile originated (MO) call |
| 1 mobile terminated (MT) call |
| [stat] (state of the call): |
| 0 active |
| 1 held |
| 2 dialing (MO call) |
| 3 alerting (MO call) |
| 4 incoming (MT call) |
| 5 waiting (MT call) |
| [mode] (bearer/teleservice): |
| 0 voice |
| 1 data |
| 2 fax |
| 3 voice followed by data, voice mode |
| 4 alternating voice/data, voice mode |
| 5 alternating voice/fax, voice mode |
| 6 voice followed by data, data mode |
| 7 alternating voice/data, data mode |
| 8 alternating voice/fax, fax mode |
| 9 unknown |
| [mpty]: |
| 0 call is not one of multiparty (conference) call parties |
| 1 call is one of multiparty (conference) call parties |
| [number]: string type phone number in format specified by [type] |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7) |
| [alpha]: string type alphanumeric representation of [number] corresponding to the entry found in phonebook; used character set should be the one selected with command Select TE Character Set +CSCS |
| [priority]: optional digit type parameter indicating the eMLPP priority level of the call, values specified in 3GPP TS 22.067 [54] |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CPOL=</command> |
| <profile>Preferred PLMN list (Assign)</profile> |
| <description>This command is used to edit the PLMN selector with Access Technology lists in the SIM card or active application in the UICC(GSM or USIM). |
| Execute command writes an entry in the SIM/USIM list of preferred PLMNs, previously selected by the command +CPLS. If no list has been previously selected, the User controlled PLMN selector with Access Technology, EFPLMNwAcT, is the one accessed by default. If [index] is given but [oper] is left out, entry is deleted. If [oper] is given but [index] is left out, [oper] is put in the next free location. If only [format] is given, the format of the [oper] in the read command is changed. The Access Technology selection parameters, [GSM_AcT], [GSM_Compact_AcT] and [UTRAN_AcT], are required when writing User controlled PLMN selector with Access Technology, EF EFPLMNwAcT, Operator controlled PLMN selector with Access Technology EFOPLMNwAcT and HPLMN selector with Access Technology EFHPLMNwAcT, see TS 31.102. Refer subclause 9.2 for possible [err] values. |
| NOTE1: MT may also update the User controlled PLMN selector with Access Technology, EFPLMNwAcT, automatically when new networks are selected. |
| NOTE2: The Operator controlled PLMN selector with Access Technology EFOPLMNwAcT, can only be written if the write access condition in the SIM/USIM has been previously verified. |
| Read command returns all used entries from the SIM/USIM list of preferred PLMNs, previously selected by the command +CPLS, with the Access Technologies for each PLMN in the list. |
| Test command returns the whole index range supported by the SIM. |
| Defined values |
| [indexn]: integer type; the order number of operator in the SIM/USIM preferred operator list |
| [format]: |
| 0 long format alphanumeric [oper] |
| 1 short format alphanumeric [oper] |
| 2 numeric [oper] |
| [opern]: string type; [format] indicates if the format is alphanumeric or numeric (see +COPS) |
| [GSM_AcTn]: GSM access technology: |
| 0 access technology not selected |
| 1access technology selected |
| [GSM_Compact_AcTn]: GSM compact access technology: |
| 0 access technology not selected |
| 1access technology selected |
| [UTRA_AcTn]: UTRA access technology: |
| 0 access technology not selected |
| 1 access technology selected |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CPOL?</command> |
| <profile>Preferred PLMN list (Query)</profile> |
| <description>This command is used to edit the PLMN selector with Access Technology lists in the SIM card or active application in the UICC(GSM or USIM). |
| Execute command writes an entry in the SIM/USIM list of preferred PLMNs, previously selected by the command +CPLS. If no list has been previously selected, the User controlled PLMN selector with Access Technology, EFPLMNwAcT, is the one accessed by default. If [index] is given but [oper] is left out, entry is deleted. If [oper] is given but [index] is left out, [oper] is put in the next free location. If only [format] is given, the format of the [oper] in the read command is changed. The Access Technology selection parameters, [GSM_AcT], [GSM_Compact_AcT] and [UTRAN_AcT], are required when writing User controlled PLMN selector with Access Technology, EF EFPLMNwAcT, Operator controlled PLMN selector with Access Technology EFOPLMNwAcT and HPLMN selector with Access Technology EFHPLMNwAcT, see TS 31.102. Refer subclause 9.2 for possible [err] values. |
| NOTE1: MT may also update the User controlled PLMN selector with Access Technology, EFPLMNwAcT, automatically when new networks are selected. |
| NOTE2: The Operator controlled PLMN selector with Access Technology EFOPLMNwAcT, can only be written if the write access condition in the SIM/USIM has been previously verified. |
| Read command returns all used entries from the SIM/USIM list of preferred PLMNs, previously selected by the command +CPLS, with the Access Technologies for each PLMN in the list. |
| Test command returns the whole index range supported by the SIM. |
| Defined values |
| [indexn]: integer type; the order number of operator in the SIM/USIM preferred operator list |
| [format]: |
| 0 long format alphanumeric [oper] |
| 1 short format alphanumeric [oper] |
| 2 numeric [oper] |
| [opern]: string type; [format] indicates if the format is alphanumeric or numeric (see +COPS) |
| [GSM_AcTn]: GSM access technology: |
| 0 access technology not selected |
| 1access technology selected |
| [GSM_Compact_AcTn]: GSM compact access technology: |
| 0 access technology not selected |
| 1access technology selected |
| [UTRA_AcTn]: UTRA access technology: |
| 0 access technology not selected |
| 1 access technology selected |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CPOL=?</command> |
| <profile>Preferred PLMN list (Query all)</profile> |
| <description>This command is used to edit the PLMN selector with Access Technology lists in the SIM card or active application in the UICC(GSM or USIM). |
| Execute command writes an entry in the SIM/USIM list of preferred PLMNs, previously selected by the command +CPLS. If no list has been previously selected, the User controlled PLMN selector with Access Technology, EFPLMNwAcT, is the one accessed by default. If [index] is given but [oper] is left out, entry is deleted. If [oper] is given but [index] is left out, [oper] is put in the next free location. If only [format] is given, the format of the [oper] in the read command is changed. The Access Technology selection parameters, [GSM_AcT], [GSM_Compact_AcT] and [UTRAN_AcT], are required when writing User controlled PLMN selector with Access Technology, EF EFPLMNwAcT, Operator controlled PLMN selector with Access Technology EFOPLMNwAcT and HPLMN selector with Access Technology EFHPLMNwAcT, see TS 31.102. Refer subclause 9.2 for possible [err] values. |
| NOTE1: MT may also update the User controlled PLMN selector with Access Technology, EFPLMNwAcT, automatically when new networks are selected. |
| NOTE2: The Operator controlled PLMN selector with Access Technology EFOPLMNwAcT, can only be written if the write access condition in the SIM/USIM has been previously verified. |
| Read command returns all used entries from the SIM/USIM list of preferred PLMNs, previously selected by the command +CPLS, with the Access Technologies for each PLMN in the list. |
| Test command returns the whole index range supported by the SIM. |
| Defined values |
| [indexn]: integer type; the order number of operator in the SIM/USIM preferred operator list |
| [format]: |
| 0 long format alphanumeric [oper] |
| 1 short format alphanumeric [oper] |
| 2 numeric [oper] |
| [opern]: string type; [format] indicates if the format is alphanumeric or numeric (see +COPS) |
| [GSM_AcTn]: GSM access technology: |
| 0 access technology not selected |
| 1access technology selected |
| [GSM_Compact_AcTn]: GSM compact access technology: |
| 0 access technology not selected |
| 1access technology selected |
| [UTRA_AcTn]: UTRA access technology: |
| 0 access technology not selected |
| 1 access technology selected |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CPLS=</command> |
| <profile>Selection of preferred PLMN list (Assign)</profile> |
| <description>This command is used to select one PLMN selector with Access Technology list in the SIM card or active application in the UICC(GSM or USIM), that is used by +CPOL command. |
| Execute command selects a list in the SIM/USIM. Refer subclause 9.2 for possible [err] values. |
| Read command returns the selected PLMN selector list from the SIM/USIM |
| Test command returns the whole index range supported lists by the SIM./USIM |
| Defined values |
| [list]: |
| 0 User controlled PLMN selector with Access Technology EFPLMNwAcT, if not found in the SIM/UICC then PLMN preferred list EFPLMNsel (this file is only available in SIM card or GSM application selected in UICC) |
| 1 Operator controlled PLMN selector with Access Technology EFOPLMNwAcT |
| 2HPLMN selector with Access Technology EFHPLMNwAcT |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CPLS?</command> |
| <profile>Selection of preferred PLMN list (Query)</profile> |
| <description>This command is used to select one PLMN selector with Access Technology list in the SIM card or active application in the UICC(GSM or USIM), that is used by +CPOL command. |
| Execute command selects a list in the SIM/USIM. Refer subclause 9.2 for possible [err] values. |
| Read command returns the selected PLMN selector list from the SIM/USIM |
| Test command returns the whole index range supported lists by the SIM./USIM |
| Defined values |
| [list]: |
| 0 User controlled PLMN selector with Access Technology EFPLMNwAcT, if not found in the SIM/UICC then PLMN preferred list EFPLMNsel (this file is only available in SIM card or GSM application selected in UICC) |
| 1 Operator controlled PLMN selector with Access Technology EFOPLMNwAcT |
| 2HPLMN selector with Access Technology EFHPLMNwAcT |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CPLS=?</command> |
| <profile>Selection of preferred PLMN list (Query all)</profile> |
| <description>This command is used to select one PLMN selector with Access Technology list in the SIM card or active application in the UICC(GSM or USIM), that is used by +CPOL command. |
| Execute command selects a list in the SIM/USIM. Refer subclause 9.2 for possible [err] values. |
| Read command returns the selected PLMN selector list from the SIM/USIM |
| Test command returns the whole index range supported lists by the SIM./USIM |
| Defined values |
| [list]: |
| 0 User controlled PLMN selector with Access Technology EFPLMNwAcT, if not found in the SIM/UICC then PLMN preferred list EFPLMNsel (this file is only available in SIM card or GSM application selected in UICC) |
| 1 Operator controlled PLMN selector with Access Technology EFOPLMNwAcT |
| 2HPLMN selector with Access Technology EFHPLMNwAcT |
| </description> |
| </spec> |
| <spec> |
| <command>AT+COPN</command> |
| <profile>Read operator names </profile> |
| <description>Execute command returns the list of operator names from the MT. Each operator code [numericn] that has an alphanumeric equivalent [alphan] in the MT memory shall be returned. Refer subclause 9.2 for possible [err] values. |
| Defined values |
| [numericn]: string type; operator in numeric format (see +COPS) |
| [alphan]: string type; operator in long alphanumeric format (see +COPS) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+COPN=?</command> |
| <profile>Read operator names (Query all)</profile> |
| <description>Execute command returns the list of operator names from the MT. Each operator code [numericn] that has an alphanumeric equivalent [alphan] in the MT memory shall be returned. Refer subclause 9.2 for possible [err] values. |
| Defined values |
| [numericn]: string type; operator in numeric format (see +COPS) |
| [alphan]: string type; operator in long alphanumeric format (see +COPS) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CFCS=</command> |
| <profile>Fast call setup conditions (Assign)</profile> |
| <description>The set command is used to edit the status of the priority level for fast call set-up stored on the SIM card or in the active application in the UICC (GSM or USIM) EFeMLPP. If the user has no subscription to the priority level status he wants to edit, an ERROR or +CME ERROR result code is returned. |
| The read command returns all enabled priority levels for fast call set-up stored on the SIM card or in the active application in the UICC (GSM or USIM) EFeMLPP. If no priority level is enabled for fast call set-up, the result code OK is returned. |
| |
| Defined values |
| [priority]: integer type, eMLPP fast call set-up priority level {0,1,..,4} as defined in 3GPP TS 22.067 [45] |
| [status]: integer type |
| 0 disable [priority] for fast call set-up |
| 1 enable [priority] for fast call set-up |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CFCS?</command> |
| <profile>Fast call setup conditions (Query)</profile> |
| <description>The set command is used to edit the status of the priority level for fast call set-up stored on the SIM card or in the active application in the UICC (GSM or USIM) EFeMLPP. If the user has no subscription to the priority level status he wants to edit, an ERROR or +CME ERROR result code is returned. |
| The read command returns all enabled priority levels for fast call set-up stored on the SIM card or in the active application in the UICC (GSM or USIM) EFeMLPP. If no priority level is enabled for fast call set-up, the result code OK is returned. |
| |
| Defined values |
| [priority]: integer type, eMLPP fast call set-up priority level {0,1,..,4} as defined in 3GPP TS 22.067 [45] |
| [status]: integer type |
| 0 disable [priority] for fast call set-up |
| 1 enable [priority] for fast call set-up |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CFCS=?</command> |
| <profile>Fast call setup conditions (Query all)</profile> |
| <description>The set command is used to edit the status of the priority level for fast call set-up stored on the SIM card or in the active application in the UICC (GSM or USIM) EFeMLPP. If the user has no subscription to the priority level status he wants to edit, an ERROR or +CME ERROR result code is returned. |
| The read command returns all enabled priority levels for fast call set-up stored on the SIM card or in the active application in the UICC (GSM or USIM) EFeMLPP. If no priority level is enabled for fast call set-up, the result code OK is returned. |
| |
| Defined values |
| [priority]: integer type, eMLPP fast call set-up priority level {0,1,..,4} as defined in 3GPP TS 22.067 [45] |
| [status]: integer type |
| 0 disable [priority] for fast call set-up |
| 1 enable [priority] for fast call set-up |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CAAP=</command> |
| <profile>Automatic answer for eMLPP Service (Assign)</profile> |
| <description>The set command is used to edit the status of the priority level for automatic answering for eMLPP stored on the SIM card or in the active application in the UICC (GSM or USIM) EFAAeM. If the user has no subscription to the priority level status he wants to edit, an ERROR or +CME ERROR result code is returned. |
| The read command returns all enabled priority levels for automatic answering for eMLPP stored on the SIM card or in the active application in the UICC (GSM or USIM) EFAAeM. If no priority level is enabled for automatic answering for eMLPP, the result code OK is returned. |
| Defined values |
| [priority]: eMLPP automatic answer priority level value {A,B,0,1,..,4} as defined in 3GPP TS 22.067 [45] |
| [status]: integer type |
| 0 disable eMLPP [priority] for automatic answering |
| 1 enable eMLPP [priority] for automatic answering |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CAAP?</command> |
| <profile>Automatic answer for eMLPP Service (Query)</profile> |
| <description>The set command is used to edit the status of the priority level for automatic answering for eMLPP stored on the SIM card or in the active application in the UICC (GSM or USIM) EFAAeM. If the user has no subscription to the priority level status he wants to edit, an ERROR or +CME ERROR result code is returned. |
| The read command returns all enabled priority levels for automatic answering for eMLPP stored on the SIM card or in the active application in the UICC (GSM or USIM) EFAAeM. If no priority level is enabled for automatic answering for eMLPP, the result code OK is returned. |
| Defined values |
| [priority]: eMLPP automatic answer priority level value {A,B,0,1,..,4} as defined in 3GPP TS 22.067 [45] |
| [status]: integer type |
| 0 disable eMLPP [priority] for automatic answering |
| 1 enable eMLPP [priority] for automatic answering |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CAAP=?</command> |
| <profile>Automatic answer for eMLPP Service (Query all)</profile> |
| <description>The set command is used to edit the status of the priority level for automatic answering for eMLPP stored on the SIM card or in the active application in the UICC (GSM or USIM) EFAAeM. If the user has no subscription to the priority level status he wants to edit, an ERROR or +CME ERROR result code is returned. |
| The read command returns all enabled priority levels for automatic answering for eMLPP stored on the SIM card or in the active application in the UICC (GSM or USIM) EFAAeM. If no priority level is enabled for automatic answering for eMLPP, the result code OK is returned. |
| Defined values |
| [priority]: eMLPP automatic answer priority level value {A,B,0,1,..,4} as defined in 3GPP TS 22.067 [45] |
| [status]: integer type |
| 0 disable eMLPP [priority] for automatic answering |
| 1 enable eMLPP [priority] for automatic answering |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CPAS</command> |
| <profile>Phone activity status </profile> |
| <description>Execution command returns the activity status [pas] of the MT. It can be used to interrogate the MT before requesting action from the phone. Refer subclause 9.2 for possible [err] values. |
| Test command returns values supported by the MT as a compound value. |
| Defined values |
| [pas]: |
| 0 ready (MT allows commands from TA/TE) |
| 1 unavailable (MT does not allow commands from TA/TE) |
| 2 unknown (MT is not guaranteed to respond to instructions) |
| 3 ringing (MT is ready for commands from TA/TE, but the ringer is active) |
| 4 call in progress (MT is ready for commands from TA/TE, but a call is in progress) |
| 5 asleep (MT is unable to process commands from TA/TE because it is in a low functionality state) |
| also all other values below 128 are reserved by the present document. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CPAS=?</command> |
| <profile>Phone activity status (Query all)</profile> |
| <description>Execution command returns the activity status [pas] of the MT. It can be used to interrogate the MT before requesting action from the phone. Refer subclause 9.2 for possible [err] values. |
| Test command returns values supported by the MT as a compound value. |
| Defined values |
| [pas]: |
| 0 ready (MT allows commands from TA/TE) |
| 1 unavailable (MT does not allow commands from TA/TE) |
| 2 unknown (MT is not guaranteed to respond to instructions) |
| 3 ringing (MT is ready for commands from TA/TE, but the ringer is active) |
| 4 call in progress (MT is ready for commands from TA/TE, but a call is in progress) |
| 5 asleep (MT is unable to process commands from TA/TE because it is in a low functionality state) |
| also all other values below 128 are reserved by the present document. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CFUN=</command> |
| <profile>Set phone functionality (Assign)</profile> |
| <description>Set command selects the level of functionality [fun] in the MT. Level 'full functionality' is where the highest level of power is drawn. 'Minimum functionality' is where minimum power is drawn. Level of functionality between these may also be specified by manufacturers. When supported by manufacturers, MT resetting with [rst] parameter may be utilized. Refer subclause 9.2 for possible [err] values. |
| NOTE: It is manufacturer specific does this command affect network registration. Command Operator Selection +COPS is used to force registration/deregistration. |
| Test command returns values supported by the MT as a compound value. |
| Defined values |
| [fun]: |
| 0 minimum functionality |
| 1 full functionality |
| 2 disable phone transmit RF circuits only |
| 3 disable phone receive RF circuits only |
| 4 disable phone both transmit and receive RF circuits |
| 5...127 reserved for manufacturers as intermediate states between full and minimum functionality |
| [rst]: |
| 0 do not reset the MT before setting it to [fun] power level |
| NOTE: This shall be always default when [rst] is not given. |
| 1 reset the MT before setting it to [fun] power level |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CFUN?</command> |
| <profile>Set phone functionality (Query)</profile> |
| <description>Set command selects the level of functionality [fun] in the MT. Level 'full functionality' is where the highest level of power is drawn. 'Minimum functionality' is where minimum power is drawn. Level of functionality between these may also be specified by manufacturers. When supported by manufacturers, MT resetting with [rst] parameter may be utilized. Refer subclause 9.2 for possible [err] values. |
| NOTE: It is manufacturer specific does this command affect network registration. Command Operator Selection +COPS is used to force registration/deregistration. |
| Test command returns values supported by the MT as a compound value. |
| Defined values |
| [fun]: |
| 0 minimum functionality |
| 1 full functionality |
| 2 disable phone transmit RF circuits only |
| 3 disable phone receive RF circuits only |
| 4 disable phone both transmit and receive RF circuits |
| 5...127 reserved for manufacturers as intermediate states between full and minimum functionality |
| [rst]: |
| 0 do not reset the MT before setting it to [fun] power level |
| NOTE: This shall be always default when [rst] is not given. |
| 1 reset the MT before setting it to [fun] power level |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CFUN=?</command> |
| <profile>Set phone functionality (Query all)</profile> |
| <description>Set command selects the level of functionality [fun] in the MT. Level 'full functionality' is where the highest level of power is drawn. 'Minimum functionality' is where minimum power is drawn. Level of functionality between these may also be specified by manufacturers. When supported by manufacturers, MT resetting with [rst] parameter may be utilized. Refer subclause 9.2 for possible [err] values. |
| NOTE: It is manufacturer specific does this command affect network registration. Command Operator Selection +COPS is used to force registration/deregistration. |
| Test command returns values supported by the MT as a compound value. |
| Defined values |
| [fun]: |
| 0 minimum functionality |
| 1 full functionality |
| 2 disable phone transmit RF circuits only |
| 3 disable phone receive RF circuits only |
| 4 disable phone both transmit and receive RF circuits |
| 5...127 reserved for manufacturers as intermediate states between full and minimum functionality |
| [rst]: |
| 0 do not reset the MT before setting it to [fun] power level |
| NOTE: This shall be always default when [rst] is not given. |
| 1 reset the MT before setting it to [fun] power level |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CPIN=</command> |
| <profile>Enter PIN (Assign)</profile> |
| <description>Set command sends to the MT a password which is necessary before it can be operated (SIM PIN, SIM PUK, PH‑SIM PIN, etc.). If the PIN is to be entered twice, the TA shall automatically repeat the PIN. If no PIN request is pending, no action is taken towards MT and an error message, +CME ERROR, is returned to TE. Refer subclause 9.2 for possible [err] values. |
| NOTE: SIM PIN, SIM PUK, PH-SIM PIN, PH-FSIM PIN, PH-FSIM PUK, SIM PIN2 and SIM PUK2 refer to the PIN of the selected application on the UICC. For example, in an UTRAN context, the selected application on a UICC should be a USIM and the SIM PIN then represents the PIN of the selected USIM. See TS 31.101 [65] for further details on application selection on the UICC. |
| If the PIN required is SIM PUK or SIM PUK2, the second pin is required. This second pin, [newpin], is used to replace the old pin in the SIM. |
| NOTE: Commands which interact with MT that are accepted when MT is pending SIM PIN, SIM PUK, or PH‑SIM are: +CGMI, +CGMM, +CGMR, +CGSN, D112; (emergency call), +CPAS, +CFUN, +CPIN, +CDIS (read and test command only), and +CIND (read and test command only). |
| Read command returns an alphanumeric string indicating whether some password is required or not. |
| Defined values |
| [pin], [newpin]: string type values |
| [code] values reserved by the present document: |
| READY MT is not pending for any password |
| SIM PIN MT is waiting SIM PIN to be given |
| SIM PUK MT is waiting SIM PUK to be given |
| PH-SIM PIN MT is waiting phone‑to‑SIM card password to be given |
| PH-FSIM PIN MT is waiting phone-to-very first SIM card password to be given |
| PH-FSIM PUK MT is waiting phone-to-very first SIM card unblocking password to be given |
| SIM PIN2 MT is waiting SIM PIN2 to be given (this [code] is recommended to be returned only when the last executed command resulted in PIN2 authentication failure (i.e. +CME ERROR: 17); if PIN2 is not entered right after the failure, it is recommended that MT does not block its operation) |
| SIM PUK2 MT is waiting SIM PUK2 to be given (this [code] is recommended to be returned only when the last executed command resulted in PUK2 authentication failure (i.e. +CME ERROR: 18); if PUK2 and new PIN2 are not entered right after the failure, it is recommended that MT does not block its operation) |
| PH-NET PIN MT is waiting network personalization password to be given |
| PH-NET PUK MT is waiting network personalization unblocking password to be given |
| PH-NETSUB PIN MT is waiting network subset personalization password to be given |
| PH-NETSUB PUK MT is waiting network subset personalization unblocking password to be given |
| PH-SP PIN MT is waiting service provider personalization password to be given |
| PH-SP PUK MT is waiting service provider personalization unblocking password to be given |
| PH-CORP PIN MT is waiting corporate personalization password to be given |
| PH-CORP PUK MT is waiting corporate personalization unblocking password to be given |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CPIN?</command> |
| <profile>Enter PIN (Query)</profile> |
| <description>Set command sends to the MT a password which is necessary before it can be operated (SIM PIN, SIM PUK, PH‑SIM PIN, etc.). If the PIN is to be entered twice, the TA shall automatically repeat the PIN. If no PIN request is pending, no action is taken towards MT and an error message, +CME ERROR, is returned to TE. Refer subclause 9.2 for possible [err] values. |
| NOTE: SIM PIN, SIM PUK, PH-SIM PIN, PH-FSIM PIN, PH-FSIM PUK, SIM PIN2 and SIM PUK2 refer to the PIN of the selected application on the UICC. For example, in an UTRAN context, the selected application on a UICC should be a USIM and the SIM PIN then represents the PIN of the selected USIM. See TS 31.101 [65] for further details on application selection on the UICC. |
| If the PIN required is SIM PUK or SIM PUK2, the second pin is required. This second pin, [newpin], is used to replace the old pin in the SIM. |
| NOTE: Commands which interact with MT that are accepted when MT is pending SIM PIN, SIM PUK, or PH‑SIM are: +CGMI, +CGMM, +CGMR, +CGSN, D112; (emergency call), +CPAS, +CFUN, +CPIN, +CDIS (read and test command only), and +CIND (read and test command only). |
| Read command returns an alphanumeric string indicating whether some password is required or not. |
| Defined values |
| [pin], [newpin]: string type values |
| [code] values reserved by the present document: |
| READY MT is not pending for any password |
| SIM PIN MT is waiting SIM PIN to be given |
| SIM PUK MT is waiting SIM PUK to be given |
| PH-SIM PIN MT is waiting phone‑to‑SIM card password to be given |
| PH-FSIM PIN MT is waiting phone-to-very first SIM card password to be given |
| PH-FSIM PUK MT is waiting phone-to-very first SIM card unblocking password to be given |
| SIM PIN2 MT is waiting SIM PIN2 to be given (this [code] is recommended to be returned only when the last executed command resulted in PIN2 authentication failure (i.e. +CME ERROR: 17); if PIN2 is not entered right after the failure, it is recommended that MT does not block its operation) |
| SIM PUK2 MT is waiting SIM PUK2 to be given (this [code] is recommended to be returned only when the last executed command resulted in PUK2 authentication failure (i.e. +CME ERROR: 18); if PUK2 and new PIN2 are not entered right after the failure, it is recommended that MT does not block its operation) |
| PH-NET PIN MT is waiting network personalization password to be given |
| PH-NET PUK MT is waiting network personalization unblocking password to be given |
| PH-NETSUB PIN MT is waiting network subset personalization password to be given |
| PH-NETSUB PUK MT is waiting network subset personalization unblocking password to be given |
| PH-SP PIN MT is waiting service provider personalization password to be given |
| PH-SP PUK MT is waiting service provider personalization unblocking password to be given |
| PH-CORP PIN MT is waiting corporate personalization password to be given |
| PH-CORP PUK MT is waiting corporate personalization unblocking password to be given |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CPIN=?</command> |
| <profile>Enter PIN (Query all)</profile> |
| <description>Set command sends to the MT a password which is necessary before it can be operated (SIM PIN, SIM PUK, PH‑SIM PIN, etc.). If the PIN is to be entered twice, the TA shall automatically repeat the PIN. If no PIN request is pending, no action is taken towards MT and an error message, +CME ERROR, is returned to TE. Refer subclause 9.2 for possible [err] values. |
| NOTE: SIM PIN, SIM PUK, PH-SIM PIN, PH-FSIM PIN, PH-FSIM PUK, SIM PIN2 and SIM PUK2 refer to the PIN of the selected application on the UICC. For example, in an UTRAN context, the selected application on a UICC should be a USIM and the SIM PIN then represents the PIN of the selected USIM. See TS 31.101 [65] for further details on application selection on the UICC. |
| If the PIN required is SIM PUK or SIM PUK2, the second pin is required. This second pin, [newpin], is used to replace the old pin in the SIM. |
| NOTE: Commands which interact with MT that are accepted when MT is pending SIM PIN, SIM PUK, or PH‑SIM are: +CGMI, +CGMM, +CGMR, +CGSN, D112; (emergency call), +CPAS, +CFUN, +CPIN, +CDIS (read and test command only), and +CIND (read and test command only). |
| Read command returns an alphanumeric string indicating whether some password is required or not. |
| Defined values |
| [pin], [newpin]: string type values |
| [code] values reserved by the present document: |
| READY MT is not pending for any password |
| SIM PIN MT is waiting SIM PIN to be given |
| SIM PUK MT is waiting SIM PUK to be given |
| PH-SIM PIN MT is waiting phone‑to‑SIM card password to be given |
| PH-FSIM PIN MT is waiting phone-to-very first SIM card password to be given |
| PH-FSIM PUK MT is waiting phone-to-very first SIM card unblocking password to be given |
| SIM PIN2 MT is waiting SIM PIN2 to be given (this [code] is recommended to be returned only when the last executed command resulted in PIN2 authentication failure (i.e. +CME ERROR: 17); if PIN2 is not entered right after the failure, it is recommended that MT does not block its operation) |
| SIM PUK2 MT is waiting SIM PUK2 to be given (this [code] is recommended to be returned only when the last executed command resulted in PUK2 authentication failure (i.e. +CME ERROR: 18); if PUK2 and new PIN2 are not entered right after the failure, it is recommended that MT does not block its operation) |
| PH-NET PIN MT is waiting network personalization password to be given |
| PH-NET PUK MT is waiting network personalization unblocking password to be given |
| PH-NETSUB PIN MT is waiting network subset personalization password to be given |
| PH-NETSUB PUK MT is waiting network subset personalization unblocking password to be given |
| PH-SP PIN MT is waiting service provider personalization password to be given |
| PH-SP PUK MT is waiting service provider personalization unblocking password to be given |
| PH-CORP PIN MT is waiting corporate personalization password to be given |
| PH-CORP PUK MT is waiting corporate personalization unblocking password to be given |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CBC</command> |
| <profile>Battery charge </profile> |
| <description>Execution command returns battery connection status [bcs] and battery charge level [bcl] of the MT. Refer subclause 9.2 for possible [err] values. |
| Test command returns values supported as compound values. |
| Defined values |
| [bcs]: |
| 0 MT is powered by the battery |
| 1 MT has a battery connected, but is not powered by it |
| 2 MT does not have a battery connected |
| 3 Recognized power fault, calls inhibited |
| [bcl]: |
| 0 battery is exhausted, or MT does not have a battery connected |
| 1...100 battery has 1‑100 percent of capacity remaining |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CBC=?</command> |
| <profile>Battery charge (Query all)</profile> |
| <description>Execution command returns battery connection status [bcs] and battery charge level [bcl] of the MT. Refer subclause 9.2 for possible [err] values. |
| Test command returns values supported as compound values. |
| Defined values |
| [bcs]: |
| 0 MT is powered by the battery |
| 1 MT has a battery connected, but is not powered by it |
| 2 MT does not have a battery connected |
| 3 Recognized power fault, calls inhibited |
| [bcl]: |
| 0 battery is exhausted, or MT does not have a battery connected |
| 1...100 battery has 1‑100 percent of capacity remaining |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSQ</command> |
| <profile>Signal quality </profile> |
| <description>Execution command returns received signal strength indication [rssi] and channel bit error rate [ber] from the MT. Refer subclause 9.2 for possible [err] values. |
| Test command returns values supported as compound values. |
| Defined values |
| [rssi]: |
| 0 ‑113 dBm or less |
| 1 ‑111 dBm |
| 2...30 ‑109... ‑53 dBm |
| 31 ‑51 dBm or greater |
| 99 not known or not detectable |
| [ber] (in percent): |
| 0...7 as RXQUAL values in the table in TS 45.008 [20] subclause 8.2.4 |
| 99 not known or not detectable |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSQ=?</command> |
| <profile>Signal quality (Query all)</profile> |
| <description>Execution command returns received signal strength indication [rssi] and channel bit error rate [ber] from the MT. Refer subclause 9.2 for possible [err] values. |
| Test command returns values supported as compound values. |
| Defined values |
| [rssi]: |
| 0 ‑113 dBm or less |
| 1 ‑111 dBm |
| 2...30 ‑109... ‑53 dBm |
| 31 ‑51 dBm or greater |
| 99 not known or not detectable |
| [ber] (in percent): |
| 0...7 as RXQUAL values in the table in TS 45.008 [20] subclause 8.2.4 |
| 99 not known or not detectable |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CIND=</command> |
| <profile>Indicator control (Assign)</profile> |
| <description>Set command is used to set the values of MT indicators. [ind] value 0 means that the indicator is off (or in state which can be identified as 'off'‑state), 1 means that indicator is on (or in a state which is more substantial than 'off'‑state), 2 is more substantial than 1, and so on. If the indicator is a simple on/off style element, it has values 0 and 1. The number of elements is MT specific. If MT does not allow setting of indicators or MT is not currently reachable, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. If certain indicator is not writable, setting of it should be ignored. If parameter is empty field, indicator shall remain in the previous value. |
| Read command returns the status of MT indicators. If MT is not currently reachable, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Test command returns pairs, where string value [descr] is a maximum 16 character description of the indicator and compound value is the allowed values for the indicator. If MT is not currently reachable, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| NOTE: MT manufacturer should offer the description of supported indicators not listed here and their value ranges and default values. |
| Defined values |
| [ind]: integer type value, which shall be in range of corresponding [descr] |
| [descr] values reserved by the present document and their [ind] ranges: |
| 'battchg' battery charge level (0‑5) |
| 'signal' signal quality (0‑5) |
| 'service' service availability (0‑1) |
| 'sounder' sounder activity (0‑1) |
| 'message' message received (0‑1) |
| 'call' call in progress (0‑1) |
| 'vox' transmit activated by voice activity (0‑1) |
| 'roam' roaming indicator (0‑1) |
| 'smsfull' a short message memory storage in the MT has become full and a short message has been rejected (2), has become full (1), or memory locations are available (0); i.e. the range is (0‑2) |
| |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CIND?</command> |
| <profile>Indicator control (Query)</profile> |
| <description>Set command is used to set the values of MT indicators. [ind] value 0 means that the indicator is off (or in state which can be identified as 'off'‑state), 1 means that indicator is on (or in a state which is more substantial than 'off'‑state), 2 is more substantial than 1, and so on. If the indicator is a simple on/off style element, it has values 0 and 1. The number of elements is MT specific. If MT does not allow setting of indicators or MT is not currently reachable, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. If certain indicator is not writable, setting of it should be ignored. If parameter is empty field, indicator shall remain in the previous value. |
| Read command returns the status of MT indicators. If MT is not currently reachable, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Test command returns pairs, where string value [descr] is a maximum 16 character description of the indicator and compound value is the allowed values for the indicator. If MT is not currently reachable, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| NOTE: MT manufacturer should offer the description of supported indicators not listed here and their value ranges and default values. |
| Defined values |
| [ind]: integer type value, which shall be in range of corresponding [descr] |
| [descr] values reserved by the present document and their [ind] ranges: |
| 'battchg' battery charge level (0‑5) |
| 'signal' signal quality (0‑5) |
| 'service' service availability (0‑1) |
| 'sounder' sounder activity (0‑1) |
| 'message' message received (0‑1) |
| 'call' call in progress (0‑1) |
| 'vox' transmit activated by voice activity (0‑1) |
| 'roam' roaming indicator (0‑1) |
| 'smsfull' a short message memory storage in the MT has become full and a short message has been rejected (2), has become full (1), or memory locations are available (0); i.e. the range is (0‑2) |
| |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CIND=?</command> |
| <profile>Indicator control (Query all)</profile> |
| <description>Set command is used to set the values of MT indicators. [ind] value 0 means that the indicator is off (or in state which can be identified as 'off'‑state), 1 means that indicator is on (or in a state which is more substantial than 'off'‑state), 2 is more substantial than 1, and so on. If the indicator is a simple on/off style element, it has values 0 and 1. The number of elements is MT specific. If MT does not allow setting of indicators or MT is not currently reachable, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. If certain indicator is not writable, setting of it should be ignored. If parameter is empty field, indicator shall remain in the previous value. |
| Read command returns the status of MT indicators. If MT is not currently reachable, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Test command returns pairs, where string value [descr] is a maximum 16 character description of the indicator and compound value is the allowed values for the indicator. If MT is not currently reachable, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| NOTE: MT manufacturer should offer the description of supported indicators not listed here and their value ranges and default values. |
| Defined values |
| [ind]: integer type value, which shall be in range of corresponding [descr] |
| [descr] values reserved by the present document and their [ind] ranges: |
| 'battchg' battery charge level (0‑5) |
| 'signal' signal quality (0‑5) |
| 'service' service availability (0‑1) |
| 'sounder' sounder activity (0‑1) |
| 'message' message received (0‑1) |
| 'call' call in progress (0‑1) |
| 'vox' transmit activated by voice activity (0‑1) |
| 'roam' roaming indicator (0‑1) |
| 'smsfull' a short message memory storage in the MT has become full and a short message has been rejected (2), has become full (1), or memory locations are available (0); i.e. the range is (0‑2) |
| |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CPBR=</command> |
| <profile>Read phonebook entries (Assign)</profile> |
| <description>Execution command returns phonebook entries in location number range [index1]... [index2] from the current phonebook memory storage selected with +CPBS. If [index2] is left out, only location [index1] is returned. Entry fields returned are location number [indexn], phone number stored there [number] (of format [type]), text [text] associated with the number, if the selected phonebook supports hidden entries, [hidden] indicating if the entry is hidden, [group] indicating a group the entry may belong to, [adnumber] an additional number (of format [adtype]), [secondtext] a second text field associated with the number and [email] an email field. If all queried locations are empty (but available), no information text lines may be returned. If listing fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Test command returns location range supported by the current storage as a compound value and the maximum lengths of [number], [text], [group], [secondtext] and [email] fields. In case of (U)SIM storage, the lengths may not be available. If MT is not currently reachable, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Defined values |
| [index1], [index2], [index]: integer type values in the range of location numbers of phonebook memory |
| [number]: string type phone number of format [type] |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7) |
| [text]: string type field of maximum length [tlength]; character set as specified by command Select TE Character Set +CSCS |
| [group]: string type field of maximum length [glength]; character set as specified by command Select TE Character Set +CSCS |
| [adnumber]: string type phone number of format [adtype] |
| [adtype]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7) |
| [secondtext]: string type field of maximum length [slength]; character set as specified by command Select TE Character Set +CSCS |
| [email]: string type field of maximum length [elength]; character set as specified by command Select TE Character Set +CSCS |
| [nlength]: integer type value indicating the maximum length of field [number] |
| [tlength]: integer type value indicating the maximum length of field [text] |
| [glength]: integer type value indicating the maximum length of field [group] |
| [slength]: integer type value indicating the maximum length of field [secondtext] |
| [elength]: integer type value indicating the maximum length of field [email] |
| [hidden]: indicates if the entry is hidden or not |
| 0: phonebook entry not hidden |
| 1: phonebook entry hidden |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CPBR=?</command> |
| <profile>Read phonebook entries (Query all)</profile> |
| <description>Execution command returns phonebook entries in location number range [index1]... [index2] from the current phonebook memory storage selected with +CPBS. If [index2] is left out, only location [index1] is returned. Entry fields returned are location number [indexn], phone number stored there [number] (of format [type]), text [text] associated with the number, if the selected phonebook supports hidden entries, [hidden] indicating if the entry is hidden, [group] indicating a group the entry may belong to, [adnumber] an additional number (of format [adtype]), [secondtext] a second text field associated with the number and [email] an email field. If all queried locations are empty (but available), no information text lines may be returned. If listing fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Test command returns location range supported by the current storage as a compound value and the maximum lengths of [number], [text], [group], [secondtext] and [email] fields. In case of (U)SIM storage, the lengths may not be available. If MT is not currently reachable, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Defined values |
| [index1], [index2], [index]: integer type values in the range of location numbers of phonebook memory |
| [number]: string type phone number of format [type] |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7) |
| [text]: string type field of maximum length [tlength]; character set as specified by command Select TE Character Set +CSCS |
| [group]: string type field of maximum length [glength]; character set as specified by command Select TE Character Set +CSCS |
| [adnumber]: string type phone number of format [adtype] |
| [adtype]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7) |
| [secondtext]: string type field of maximum length [slength]; character set as specified by command Select TE Character Set +CSCS |
| [email]: string type field of maximum length [elength]; character set as specified by command Select TE Character Set +CSCS |
| [nlength]: integer type value indicating the maximum length of field [number] |
| [tlength]: integer type value indicating the maximum length of field [text] |
| [glength]: integer type value indicating the maximum length of field [group] |
| [slength]: integer type value indicating the maximum length of field [secondtext] |
| [elength]: integer type value indicating the maximum length of field [email] |
| [hidden]: indicates if the entry is hidden or not |
| 0: phonebook entry not hidden |
| 1: phonebook entry hidden |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CPBF=</command> |
| <profile>Find phonebook entries (Assign)</profile> |
| <description>Execution command returns phonebook entries (from the current phonebook memory storage selected with +CPBS) which alphanumeric field start with string [findtext]. Entry fields returned are location number [indexn], phone number stored there [number] (of format [type]), text [text] associated with the number, if the selected phonebook supports hidden entries, [hidden] indicating if the entry is hidden, [group] indicating a group the entry may belong to, [adnumber] an additional number (of format [adtype]), [secondtext] a second text field associated with the number and [email] an email field. If listing fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Test command returns the maximum lengths of [number], [text], [group], [secondtext] and [email] fields. In case of (U)SIM storage, the lengths may not be available. If MT is not currently reachable, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| |
| Defined values |
| [index1], [index2]: integer type values in the range of location numbers of phonebook memory |
| [number]: string type phone number of format [type] |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7) |
| [group]: string type field of maximum length [glength]; character set as specified by command Select TE Character Set +CSCS |
| [adnumber]: string type phone number of format [adtype] |
| [adtype]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7) |
| [secondtext]: string type field of maximum length [slength]; character set as specified by command Select TE Character Set +CSCS |
| [email]: string type field of maximum length [elength]; character set as specified by command Select TE Character Set +CSCS |
| [findtext], [text]: string type field of maximum length [tlength]; character set as specified by command Select TE Character Set +CSCS |
| [nlength]: integer type value indicating the maximum length of field [number] |
| [tlength]: integer type value indicating the maximum length of field [text] |
| [glength]: integer type value indicating the maximum length of field [group] |
| [slength]: integer type value indicating the maximum length of field [secondtext] |
| [elength]: integer type value indicating the maximum length of field [email] |
| [hidden]: indicates if the entry is hidden or not |
| 0: phonebook entry not hidden |
| 1: phonebook entry hidden |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CPBF=?</command> |
| <profile>Find phonebook entries (Query all)</profile> |
| <description>Execution command returns phonebook entries (from the current phonebook memory storage selected with +CPBS) which alphanumeric field start with string [findtext]. Entry fields returned are location number [indexn], phone number stored there [number] (of format [type]), text [text] associated with the number, if the selected phonebook supports hidden entries, [hidden] indicating if the entry is hidden, [group] indicating a group the entry may belong to, [adnumber] an additional number (of format [adtype]), [secondtext] a second text field associated with the number and [email] an email field. If listing fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Test command returns the maximum lengths of [number], [text], [group], [secondtext] and [email] fields. In case of (U)SIM storage, the lengths may not be available. If MT is not currently reachable, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| |
| Defined values |
| [index1], [index2]: integer type values in the range of location numbers of phonebook memory |
| [number]: string type phone number of format [type] |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7) |
| [group]: string type field of maximum length [glength]; character set as specified by command Select TE Character Set +CSCS |
| [adnumber]: string type phone number of format [adtype] |
| [adtype]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7) |
| [secondtext]: string type field of maximum length [slength]; character set as specified by command Select TE Character Set +CSCS |
| [email]: string type field of maximum length [elength]; character set as specified by command Select TE Character Set +CSCS |
| [findtext], [text]: string type field of maximum length [tlength]; character set as specified by command Select TE Character Set +CSCS |
| [nlength]: integer type value indicating the maximum length of field [number] |
| [tlength]: integer type value indicating the maximum length of field [text] |
| [glength]: integer type value indicating the maximum length of field [group] |
| [slength]: integer type value indicating the maximum length of field [secondtext] |
| [elength]: integer type value indicating the maximum length of field [email] |
| [hidden]: indicates if the entry is hidden or not |
| 0: phonebook entry not hidden |
| 1: phonebook entry hidden |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CPBW=</command> |
| <profile>Write phonebook entry (Assign)</profile> |
| <description>Execution command writes phonebook entry in location number [index] in the current phonebook memory storage selected with +CPBS. Entry fields written are phone number [number] (in the format [type]), text [text] associated with the number, if the selected phonebook supports hidden entries, [hidden] parameter, which indicates if the entry is hidden or not, [group] indicating a group the entry may belong to, [adnumber] an additional number (of format [adtype]), [secondtext] a second text field associated with the number and [email] an email field. If those fields are omitted, phonebook entry is deleted. If [index] is left out, but [number] is given, entry is written to the first free location in the phonebook (the implementation of this feature is manufacturer specific). If writing fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Test command returns location range supported by the current storage as a compound value, the maximum length of [number] field, supported number formats of the storage, the maximum length of [text] field, the maximum length of [group], the maximum length of [secondtext], and the maximum length of [email]. In case of SIM storage, the lengths may not be available. If MT is not currently reachable, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. If storage does not offer format information, the format list should be empty parenthesis |
| Defined values |
| [index]: integer type values in the range of location numbers of phonebook memory |
| [number]: string type phone number of format [type] |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7) ; default 145 when dialling string includes international access code character '+', otherwise 129 |
| [text]: string type field of maximum length [tlength]; character set as specified by command Select TE Character Set +CSCS |
| [group]: string type field of maximum length [glength]; character set as specified by command Select TE Character Set +CSCS |
| [adnumber]: string type phone number of format [adtype] |
| [adtype]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7) |
| [secondtext]: string type field of maximum length [slength]; character set as specified by command Select TE Character Set +CSCS |
| [email]: string type field of maximum length [elength]; character set as specified by command Select TE Character Set +CSCS |
| [nlength]: integer type value indicating the maximum length of field [number] |
| [tlength]: integer type value indicating the maximum length of field [text] |
| [glength]: integer type value indicating the maximum length of field [group] |
| [slength]: integer type value indicating the maximum length of field [secondtext] |
| [elength]: integer type value indicating the maximum length of field [email] |
| [hidden]: indicates if the entry is hidden or not |
| 0: phonebook entry not hidden |
| 1: phonebook entry hidden |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CPBW=?</command> |
| <profile>Write phonebook entry (Query all)</profile> |
| <description>Execution command writes phonebook entry in location number [index] in the current phonebook memory storage selected with +CPBS. Entry fields written are phone number [number] (in the format [type]), text [text] associated with the number, if the selected phonebook supports hidden entries, [hidden] parameter, which indicates if the entry is hidden or not, [group] indicating a group the entry may belong to, [adnumber] an additional number (of format [adtype]), [secondtext] a second text field associated with the number and [email] an email field. If those fields are omitted, phonebook entry is deleted. If [index] is left out, but [number] is given, entry is written to the first free location in the phonebook (the implementation of this feature is manufacturer specific). If writing fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Test command returns location range supported by the current storage as a compound value, the maximum length of [number] field, supported number formats of the storage, the maximum length of [text] field, the maximum length of [group], the maximum length of [secondtext], and the maximum length of [email]. In case of SIM storage, the lengths may not be available. If MT is not currently reachable, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. If storage does not offer format information, the format list should be empty parenthesis |
| Defined values |
| [index]: integer type values in the range of location numbers of phonebook memory |
| [number]: string type phone number of format [type] |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7) ; default 145 when dialling string includes international access code character '+', otherwise 129 |
| [text]: string type field of maximum length [tlength]; character set as specified by command Select TE Character Set +CSCS |
| [group]: string type field of maximum length [glength]; character set as specified by command Select TE Character Set +CSCS |
| [adnumber]: string type phone number of format [adtype] |
| [adtype]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7) |
| [secondtext]: string type field of maximum length [slength]; character set as specified by command Select TE Character Set +CSCS |
| [email]: string type field of maximum length [elength]; character set as specified by command Select TE Character Set +CSCS |
| [nlength]: integer type value indicating the maximum length of field [number] |
| [tlength]: integer type value indicating the maximum length of field [text] |
| [glength]: integer type value indicating the maximum length of field [group] |
| [slength]: integer type value indicating the maximum length of field [secondtext] |
| [elength]: integer type value indicating the maximum length of field [email] |
| [hidden]: indicates if the entry is hidden or not |
| 0: phonebook entry not hidden |
| 1: phonebook entry hidden |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CCLK=</command> |
| <profile>Clock (Assign)</profile> |
| <description>Set command sets the real‑time clock of the MT. If setting fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Read command returns the current setting of the clock. |
| Defined values |
| [time]: string type value; format is 'yy/MM/dd,hh:mm:sszz', where characters indicate year (two last digits), month, day, hour, minutes, seconds and time zone (indicates the difference, expressed in quarters of an hour, between the local time and GMT; range -96...+96). E.g. 6th of May 1994, 22:10:00 GMT+2 hours equals to '94/05/06,22:10:00+08' |
| NOTE: If MT does not support time zone information then the three last characters of [time] are not returned by +CCLK?. The format of [time] is specified by use of the +CSDF command. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CCLK?</command> |
| <profile>Clock (Query)</profile> |
| <description>Set command sets the real‑time clock of the MT. If setting fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Read command returns the current setting of the clock. |
| Defined values |
| [time]: string type value; format is 'yy/MM/dd,hh:mm:sszz', where characters indicate year (two last digits), month, day, hour, minutes, seconds and time zone (indicates the difference, expressed in quarters of an hour, between the local time and GMT; range -96...+96). E.g. 6th of May 1994, 22:10:00 GMT+2 hours equals to '94/05/06,22:10:00+08' |
| NOTE: If MT does not support time zone information then the three last characters of [time] are not returned by +CCLK?. The format of [time] is specified by use of the +CSDF command. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CCLK=?</command> |
| <profile>Clock (Query all)</profile> |
| <description>Set command sets the real‑time clock of the MT. If setting fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Read command returns the current setting of the clock. |
| Defined values |
| [time]: string type value; format is 'yy/MM/dd,hh:mm:sszz', where characters indicate year (two last digits), month, day, hour, minutes, seconds and time zone (indicates the difference, expressed in quarters of an hour, between the local time and GMT; range -96...+96). E.g. 6th of May 1994, 22:10:00 GMT+2 hours equals to '94/05/06,22:10:00+08' |
| NOTE: If MT does not support time zone information then the three last characters of [time] are not returned by +CCLK?. The format of [time] is specified by use of the +CSDF command. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CALA=</command> |
| <profile>Alarm (Assign)</profile> |
| <description>Set command sets an alarm time in the MT. There can be an array of different types of alarms, and each alarm may cause different text to be displayed in the MT display. If setting fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| To set up a recurrent alarm for one or more days in the week, the [recurr]-parameter may be used. |
| When an alarm is timed out and executed, the unsolicited result code +CALV: [n] is always returned, even if the alarm is set up to be silent. |
| Read command returns the list of current active alarm settings in the MT. |
| Test command returns supported array index values, alarm types, and maximum length of the text to be displayed. |
| Defined values |
| [time]: refer +CCLK,+CSDF |
| NOTE: If the [recurr]-parameter is used, the [time]-parameter must not contain a date. |
| [n], [n1], [n2]: integer type value indicating the index of the alarm; default is manufacturer specific |
| [type]: integer type value indicating the type of the alarm (e.g. sound, volume, LED); values and default are manufacturer specific |
| [text]: string type value indicating the text to be displayed when alarm time is reached; maximum length [tlength] |
| [tlength]: integer type value indicating the maximum length of [text] |
| [recurr]: string type value indicating day of week for the alarm in one of the following formats: |
| |
| '[1..7][,[1..7][…]]' – Sets a recurrent alarm for one or more days in the week. The digits 1 to 7 corresponds to the days in the week, Monday (1), …, Sunday (7). |
| Example: The string '1,2,3,4,5' may be used to set an alarm for all weekdays. |
| |
| '0' – Sets a recurrent alarm for all days in the week. |
| [rlength]: integer type value indicating the maximum length of [recurr] |
| [silent]: Integer type value indicating if the alarm is silent or not. If set to 1 the alarm will be silent and the only result from the alarm is the unsolicited result code +CALV. If set to 0 the alarm will not be silent. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CALA?</command> |
| <profile>Alarm (Query)</profile> |
| <description>Set command sets an alarm time in the MT. There can be an array of different types of alarms, and each alarm may cause different text to be displayed in the MT display. If setting fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| To set up a recurrent alarm for one or more days in the week, the [recurr]-parameter may be used. |
| When an alarm is timed out and executed, the unsolicited result code +CALV: [n] is always returned, even if the alarm is set up to be silent. |
| Read command returns the list of current active alarm settings in the MT. |
| Test command returns supported array index values, alarm types, and maximum length of the text to be displayed. |
| Defined values |
| [time]: refer +CCLK,+CSDF |
| NOTE: If the [recurr]-parameter is used, the [time]-parameter must not contain a date. |
| [n], [n1], [n2]: integer type value indicating the index of the alarm; default is manufacturer specific |
| [type]: integer type value indicating the type of the alarm (e.g. sound, volume, LED); values and default are manufacturer specific |
| [text]: string type value indicating the text to be displayed when alarm time is reached; maximum length [tlength] |
| [tlength]: integer type value indicating the maximum length of [text] |
| [recurr]: string type value indicating day of week for the alarm in one of the following formats: |
| |
| '[1..7][,[1..7][…]]' – Sets a recurrent alarm for one or more days in the week. The digits 1 to 7 corresponds to the days in the week, Monday (1), …, Sunday (7). |
| Example: The string '1,2,3,4,5' may be used to set an alarm for all weekdays. |
| |
| '0' – Sets a recurrent alarm for all days in the week. |
| [rlength]: integer type value indicating the maximum length of [recurr] |
| [silent]: Integer type value indicating if the alarm is silent or not. If set to 1 the alarm will be silent and the only result from the alarm is the unsolicited result code +CALV. If set to 0 the alarm will not be silent. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CALA=?</command> |
| <profile>Alarm (Query all)</profile> |
| <description>Set command sets an alarm time in the MT. There can be an array of different types of alarms, and each alarm may cause different text to be displayed in the MT display. If setting fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| To set up a recurrent alarm for one or more days in the week, the [recurr]-parameter may be used. |
| When an alarm is timed out and executed, the unsolicited result code +CALV: [n] is always returned, even if the alarm is set up to be silent. |
| Read command returns the list of current active alarm settings in the MT. |
| Test command returns supported array index values, alarm types, and maximum length of the text to be displayed. |
| Defined values |
| [time]: refer +CCLK,+CSDF |
| NOTE: If the [recurr]-parameter is used, the [time]-parameter must not contain a date. |
| [n], [n1], [n2]: integer type value indicating the index of the alarm; default is manufacturer specific |
| [type]: integer type value indicating the type of the alarm (e.g. sound, volume, LED); values and default are manufacturer specific |
| [text]: string type value indicating the text to be displayed when alarm time is reached; maximum length [tlength] |
| [tlength]: integer type value indicating the maximum length of [text] |
| [recurr]: string type value indicating day of week for the alarm in one of the following formats: |
| |
| '[1..7][,[1..7][…]]' – Sets a recurrent alarm for one or more days in the week. The digits 1 to 7 corresponds to the days in the week, Monday (1), …, Sunday (7). |
| Example: The string '1,2,3,4,5' may be used to set an alarm for all weekdays. |
| |
| '0' – Sets a recurrent alarm for all days in the week. |
| [rlength]: integer type value indicating the maximum length of [recurr] |
| [silent]: Integer type value indicating if the alarm is silent or not. If set to 1 the alarm will be silent and the only result from the alarm is the unsolicited result code +CALV. If set to 0 the alarm will not be silent. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSIM=</command> |
| <profile>Generic SIM access (Assign)</profile> |
| <description>Set command transmits to the MT the [command] it then shall send as it is to the SIM. In the same manner the SIM [response] shall be sent back by the MT to the TA as it is. Refer subclause 9.2 for [err] values. |
| This command allows a direct control of the SIM by an distant application on the TE. The TE shall then take care of processing SIM information within the frame specified by GSM/UMTS. |
| NOTE: Compared to Restricted SIM Access command +CRSM, the definition of +CSIM allows TE to take more control over the SIM‑MT interface. The locking and unlocking of the interface may be done by a special [command] value or automatically by TA/MT (by interpreting [command] parameter). In case that TE application does not use the unlock command (or does not send a [command] causing automatic unlock) in a certain timeout value, MT may release the locking. |
| Defined values |
| [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 SIM in the format as described in GSM 51.011 [28] (hexadecimal character format; refer +CSCS) |
| [response] : response to the command passed on by the SIM to the MT in the format as described in GSM 51.011 [28] (hexadecimal character format; refer +CSCS) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSIM=?</command> |
| <profile>Generic SIM access (Query all)</profile> |
| <description>Set command transmits to the MT the [command] it then shall send as it is to the SIM. In the same manner the SIM [response] shall be sent back by the MT to the TA as it is. Refer subclause 9.2 for [err] values. |
| This command allows a direct control of the SIM by an distant application on the TE. The TE shall then take care of processing SIM information within the frame specified by GSM/UMTS. |
| NOTE: Compared to Restricted SIM Access command +CRSM, the definition of +CSIM allows TE to take more control over the SIM‑MT interface. The locking and unlocking of the interface may be done by a special [command] value or automatically by TA/MT (by interpreting [command] parameter). In case that TE application does not use the unlock command (or does not send a [command] causing automatic unlock) in a certain timeout value, MT may release the locking. |
| Defined values |
| [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 SIM in the format as described in GSM 51.011 [28] (hexadecimal character format; refer +CSCS) |
| [response] : response to the command passed on by the SIM to the MT in the format as described in GSM 51.011 [28] (hexadecimal character format; refer +CSCS) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CRSM=</command> |
| <profile>Restricted SIM access (Assign)</profile> |
| <description>By using this command instead of Generic SIM Access +CSIM TE application has easier but more limited access to the SIM database. Set command transmits to the MT the SIM [command] and its required parameters. MT handles internally all SIM‑MT interface locking and file selection routines. As response to the command, MT sends the actual SIM information parameters and response data. MT error result code +CME ERROR may be returned when the command cannot be passed to the SIM, but failure in the execution of the command in the SIM is reported in [sw1] and [sw2] parameters. Refer to subclause 9.2 for [err] values. |
| Coordination of command requests to SIM 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 |
| [command] (command passed on by the MT to the SIM; refer GSM 51.011 [28]): |
| 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 a elementary datafile on SIM. Mandatory for every command except STATUS |
| NOTE 2: The range of valid file identifiers depends on the actual SIM and is defined in GSM 51.011 [28]. Optional files may not be present at all. |
| [P1], [P2], [P3]: integer type; parameters passed on by the MT to the SIM. These parameters are mandatory for every command, except GET RESPONSE and STATUS. The values are described in GSM 51.011 [28] |
| [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 SIM/UICC in hexadecimal format as defined in ETSI TS 102 221 [60] (e.g. '7F205F70' in SIM and UICC case). The [pathid] shall only be used in the mode 'select by path from MF' as defined in ETSI TS 102 221 [60]. |
| NOTE 3: Since valid elementary file identifiers may not be unique over all valid dedicated file identifiers the [pathid] indicates the targeted UICC/SIM directory path in case of ambiguous file identifiers. For earlier versions of this specification or if [pathid] is omitted, it could be implementation specific which one will be selected. |
| [sw1], [sw2]: integer type; information from the SIM 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 GSM 51.011 [28]). 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 |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CRSM=?</command> |
| <profile>Restricted SIM access (Query all)</profile> |
| <description>By using this command instead of Generic SIM Access +CSIM TE application has easier but more limited access to the SIM database. Set command transmits to the MT the SIM [command] and its required parameters. MT handles internally all SIM‑MT interface locking and file selection routines. As response to the command, MT sends the actual SIM information parameters and response data. MT error result code +CME ERROR may be returned when the command cannot be passed to the SIM, but failure in the execution of the command in the SIM is reported in [sw1] and [sw2] parameters. Refer to subclause 9.2 for [err] values. |
| Coordination of command requests to SIM 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 |
| [command] (command passed on by the MT to the SIM; refer GSM 51.011 [28]): |
| 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 a elementary datafile on SIM. Mandatory for every command except STATUS |
| NOTE 2: The range of valid file identifiers depends on the actual SIM and is defined in GSM 51.011 [28]. Optional files may not be present at all. |
| [P1], [P2], [P3]: integer type; parameters passed on by the MT to the SIM. These parameters are mandatory for every command, except GET RESPONSE and STATUS. The values are described in GSM 51.011 [28] |
| [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 SIM/UICC in hexadecimal format as defined in ETSI TS 102 221 [60] (e.g. '7F205F70' in SIM and UICC case). The [pathid] shall only be used in the mode 'select by path from MF' as defined in ETSI TS 102 221 [60]. |
| NOTE 3: Since valid elementary file identifiers may not be unique over all valid dedicated file identifiers the [pathid] indicates the targeted UICC/SIM directory path in case of ambiguous file identifiers. For earlier versions of this specification or if [pathid] is omitted, it could be implementation specific which one will be selected. |
| [sw1], [sw2]: integer type; information from the SIM 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 GSM 51.011 [28]). 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 |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSCC=</command> |
| <profile>Secure control command (Assign)</profile> |
| <description>This command is used to enable/disable access to commands protected by security mechanism. This enables/disables access to command sets designated as 'secure' such as programming of MT. Refer subclause 9.2 for possible [err] values. |
| The TE asks for a [challenge] with [mode]=1 and one specific command set ([cmd_set]), the MT replies with the [challenge], which should be inserted into the identification algorithm in both entities (TE and MT). The algorithm output [token] is sent to the MT with [mode]=2 to enable the specified command set. [mode]=3 is used to disable the command set. |
| The read command returns the status ([mode] 2 or 3) of each supported command set. |
| Defined values |
| [mode]: |
| 1 request challenge token to enable access to specified command set |
| 2 enable access to specified command set ([token] required) |
| 3 disable access to specified command set |
| [cmd_set], [cmd_set1], [cmd_set2]: |
| 0 MT/TA code re-programming command set. |
| other values below 128 are reserved by the present document |
| [token]: string type; a variable length bit string represented with IRA characters 0 - 9 and A - F, each character representing a nibble; e.g. bit string '0110 1100 1001 1010' is represented by the IRA string '6C9A'. The length of the required bit string varies depending on the value of [cmd_set]. |
| [challenge]: same format as token |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSCC?</command> |
| <profile>Secure control command (Query)</profile> |
| <description>This command is used to enable/disable access to commands protected by security mechanism. This enables/disables access to command sets designated as 'secure' such as programming of MT. Refer subclause 9.2 for possible [err] values. |
| The TE asks for a [challenge] with [mode]=1 and one specific command set ([cmd_set]), the MT replies with the [challenge], which should be inserted into the identification algorithm in both entities (TE and MT). The algorithm output [token] is sent to the MT with [mode]=2 to enable the specified command set. [mode]=3 is used to disable the command set. |
| The read command returns the status ([mode] 2 or 3) of each supported command set. |
| Defined values |
| [mode]: |
| 1 request challenge token to enable access to specified command set |
| 2 enable access to specified command set ([token] required) |
| 3 disable access to specified command set |
| [cmd_set], [cmd_set1], [cmd_set2]: |
| 0 MT/TA code re-programming command set. |
| other values below 128 are reserved by the present document |
| [token]: string type; a variable length bit string represented with IRA characters 0 - 9 and A - F, each character representing a nibble; e.g. bit string '0110 1100 1001 1010' is represented by the IRA string '6C9A'. The length of the required bit string varies depending on the value of [cmd_set]. |
| [challenge]: same format as token |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSCC=?</command> |
| <profile>Secure control command (Query all)</profile> |
| <description>This command is used to enable/disable access to commands protected by security mechanism. This enables/disables access to command sets designated as 'secure' such as programming of MT. Refer subclause 9.2 for possible [err] values. |
| The TE asks for a [challenge] with [mode]=1 and one specific command set ([cmd_set]), the MT replies with the [challenge], which should be inserted into the identification algorithm in both entities (TE and MT). The algorithm output [token] is sent to the MT with [mode]=2 to enable the specified command set. [mode]=3 is used to disable the command set. |
| The read command returns the status ([mode] 2 or 3) of each supported command set. |
| Defined values |
| [mode]: |
| 1 request challenge token to enable access to specified command set |
| 2 enable access to specified command set ([token] required) |
| 3 disable access to specified command set |
| [cmd_set], [cmd_set1], [cmd_set2]: |
| 0 MT/TA code re-programming command set. |
| other values below 128 are reserved by the present document |
| [token]: string type; a variable length bit string represented with IRA characters 0 - 9 and A - F, each character representing a nibble; e.g. bit string '0110 1100 1001 1010' is represented by the IRA string '6C9A'. The length of the required bit string varies depending on the value of [cmd_set]. |
| [challenge]: same format as token |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CALM=</command> |
| <profile>Alert sound mode (Assign)</profile> |
| <description>This command is used to select the general alert sound mode of the MT. Refer subclause 9.2 for possible [err] values. |
| Test command returns supported values as compound value. |
| Defined values |
| [mode]: |
| 0 normal mode |
| 1 silent mode (all sounds from MT are prevented) |
| 2… manufacturer specific |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CALM?</command> |
| <profile>Alert sound mode (Query)</profile> |
| <description>This command is used to select the general alert sound mode of the MT. Refer subclause 9.2 for possible [err] values. |
| Test command returns supported values as compound value. |
| Defined values |
| [mode]: |
| 0 normal mode |
| 1 silent mode (all sounds from MT are prevented) |
| 2… manufacturer specific |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CALM=?</command> |
| <profile>Alert sound mode (Query all)</profile> |
| <description>This command is used to select the general alert sound mode of the MT. Refer subclause 9.2 for possible [err] values. |
| Test command returns supported values as compound value. |
| Defined values |
| [mode]: |
| 0 normal mode |
| 1 silent mode (all sounds from MT are prevented) |
| 2… manufacturer specific |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CRSL=</command> |
| <profile>Ringer sound level (Assign)</profile> |
| <description>This command is used to select the incoming call ringer sound level of the MT. Refer subclause 9.2 for possible [err] values. |
| Test command returns supported values as compound value. |
| Defined values |
| [level]: integer type value with manufacturer specific range (smallest value represents the lowest sound level) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CRSL?</command> |
| <profile>Ringer sound level (Query)</profile> |
| <description>This command is used to select the incoming call ringer sound level of the MT. Refer subclause 9.2 for possible [err] values. |
| Test command returns supported values as compound value. |
| Defined values |
| [level]: integer type value with manufacturer specific range (smallest value represents the lowest sound level) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CRSL=?</command> |
| <profile>Ringer sound level (Query all)</profile> |
| <description>This command is used to select the incoming call ringer sound level of the MT. Refer subclause 9.2 for possible [err] values. |
| Test command returns supported values as compound value. |
| Defined values |
| [level]: integer type value with manufacturer specific range (smallest value represents the lowest sound level) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CVIB=</command> |
| <profile>Vibrator mode (Assign)</profile> |
| <description>This command is used to enable and disable the vibrator alert feature of the MT. It is manufacturer specific how this interacts with +CALM command. Refer subclause 9.2 for possible [err] values. |
| Test command returns supported values as compound value. |
| Defined values |
| [mode]: |
| 0 disable |
| 1 enable |
| ...15 reserved by the present document |
| 16… manufacturer specific |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CVIB?</command> |
| <profile>Vibrator mode (Query)</profile> |
| <description>This command is used to enable and disable the vibrator alert feature of the MT. It is manufacturer specific how this interacts with +CALM command. Refer subclause 9.2 for possible [err] values. |
| Test command returns supported values as compound value. |
| Defined values |
| [mode]: |
| 0 disable |
| 1 enable |
| ...15 reserved by the present document |
| 16… manufacturer specific |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CVIB=?</command> |
| <profile>Vibrator mode (Query all)</profile> |
| <description>This command is used to enable and disable the vibrator alert feature of the MT. It is manufacturer specific how this interacts with +CALM command. Refer subclause 9.2 for possible [err] values. |
| Test command returns supported values as compound value. |
| Defined values |
| [mode]: |
| 0 disable |
| 1 enable |
| ...15 reserved by the present document |
| 16… manufacturer specific |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CLVL=</command> |
| <profile>Loudspeaker volume level (Assign)</profile> |
| <description>This command is used to select the volume of the internal loudspeaker of the MT. Refer subclause 9.2 for possible [err] values. |
| Test command returns supported values as compound value. |
| Defined values |
| [level]: integer type value with manufacturer specific range (smallest value represents the lowest sound level) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CLVL?</command> |
| <profile>Loudspeaker volume level (Query)</profile> |
| <description>This command is used to select the volume of the internal loudspeaker of the MT. Refer subclause 9.2 for possible [err] values. |
| Test command returns supported values as compound value. |
| Defined values |
| [level]: integer type value with manufacturer specific range (smallest value represents the lowest sound level) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CLVL=?</command> |
| <profile>Loudspeaker volume level (Query all)</profile> |
| <description>This command is used to select the volume of the internal loudspeaker of the MT. Refer subclause 9.2 for possible [err] values. |
| Test command returns supported values as compound value. |
| Defined values |
| [level]: integer type value with manufacturer specific range (smallest value represents the lowest sound level) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CMUT=</command> |
| <profile>Mute control (Assign)</profile> |
| <description>This command is used to enable and disable the uplink voice muting during a voice call. Refer subclause 9.2 for possible [err] values. |
| Test command returns supported values as compound value. |
| Defined values |
| [n]: |
| 0 mute off |
| 1 mute on |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CMUT?</command> |
| <profile>Mute control (Query)</profile> |
| <description>This command is used to enable and disable the uplink voice muting during a voice call. Refer subclause 9.2 for possible [err] values. |
| Test command returns supported values as compound value. |
| Defined values |
| [n]: |
| 0 mute off |
| 1 mute on |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CMUT=?</command> |
| <profile>Mute control (Query all)</profile> |
| <description>This command is used to enable and disable the uplink voice muting during a voice call. Refer subclause 9.2 for possible [err] values. |
| Test command returns supported values as compound value. |
| Defined values |
| [n]: |
| 0 mute off |
| 1 mute on |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CACM=</command> |
| <profile>Accumulated call meter (Assign)</profile> |
| <description>Set command resets the Advice of Charge related accumulated call meter value in SIM card or in the active application in the UICC (GSM or USIM) file EFACM. ACM contains the total number of home units for both the current and preceding calls. SIM PIN2 is usually required to reset the value. If setting fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Read command returns the current value of ACM. |
| Defined values |
| [passwd]: string type; SIM PIN2 |
| [acm]: string type; accumulated call meter value similarly coded as [ccm] under +CAOC |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CACM?</command> |
| <profile>Accumulated call meter (Query)</profile> |
| <description>Set command resets the Advice of Charge related accumulated call meter value in SIM card or in the active application in the UICC (GSM or USIM) file EFACM. ACM contains the total number of home units for both the current and preceding calls. SIM PIN2 is usually required to reset the value. If setting fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Read command returns the current value of ACM. |
| Defined values |
| [passwd]: string type; SIM PIN2 |
| [acm]: string type; accumulated call meter value similarly coded as [ccm] under +CAOC |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CACM=?</command> |
| <profile>Accumulated call meter (Query all)</profile> |
| <description>Set command resets the Advice of Charge related accumulated call meter value in SIM card or in the active application in the UICC (GSM or USIM) file EFACM. ACM contains the total number of home units for both the current and preceding calls. SIM PIN2 is usually required to reset the value. If setting fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Read command returns the current value of ACM. |
| Defined values |
| [passwd]: string type; SIM PIN2 |
| [acm]: string type; accumulated call meter value similarly coded as [ccm] under +CAOC |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CAMM=</command> |
| <profile>Accumulated call meter maximum (Assign)</profile> |
| <description>Set command sets the Advice of Charge related accumulated call meter maximum value in SIM card or in the active application in the UICC (GSM or USIM) file EFACMmax. ACMmax contains the maximum number of home units allowed to be consumed by the subscriber. When ACM (refer +CACM) reaches ACMmax calls are prohibited (see also 3GPP TS 22.024 [26]). SIM PIN2 is usually required to set the value. If setting fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Read command returns the current value of ACMmax. |
| Defined values |
| [acmmax]: string type; accumulated call meter maximum value similarly coded as [ccm] under +CAOC; value zero disables ACMmax feature |
| [passwd]: string type; SIM PIN2 |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CAMM?</command> |
| <profile>Accumulated call meter maximum (Query)</profile> |
| <description>Set command sets the Advice of Charge related accumulated call meter maximum value in SIM card or in the active application in the UICC (GSM or USIM) file EFACMmax. ACMmax contains the maximum number of home units allowed to be consumed by the subscriber. When ACM (refer +CACM) reaches ACMmax calls are prohibited (see also 3GPP TS 22.024 [26]). SIM PIN2 is usually required to set the value. If setting fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Read command returns the current value of ACMmax. |
| Defined values |
| [acmmax]: string type; accumulated call meter maximum value similarly coded as [ccm] under +CAOC; value zero disables ACMmax feature |
| [passwd]: string type; SIM PIN2 |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CAMM=?</command> |
| <profile>Accumulated call meter maximum (Query all)</profile> |
| <description>Set command sets the Advice of Charge related accumulated call meter maximum value in SIM card or in the active application in the UICC (GSM or USIM) file EFACMmax. ACMmax contains the maximum number of home units allowed to be consumed by the subscriber. When ACM (refer +CACM) reaches ACMmax calls are prohibited (see also 3GPP TS 22.024 [26]). SIM PIN2 is usually required to set the value. If setting fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Read command returns the current value of ACMmax. |
| Defined values |
| [acmmax]: string type; accumulated call meter maximum value similarly coded as [ccm] under +CAOC; value zero disables ACMmax feature |
| [passwd]: string type; SIM PIN2 |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CPUC=</command> |
| <profile>Price per unit and currency table (Assign)</profile> |
| <description>Set command sets the parameters of Advice of Charge related price per unit and currency table in SIM card or in the active application in the UICC (GSM or USIM) file EFPUCT. PUCT information can be used to convert the home units (as used in +CAOC, +CACM and +CAMM) into currency units. SIM PIN2 is usually required to set the parameters. If setting fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Read command returns the current parameters of PUCT. |
| Defined values |
| [currency]: string type; three-character currency code (e.g. 'GBP', 'DEM'); character set as specified by command Select TE Character Set +CSCS |
| [ppu]: string type; price per unit; dot is used as a decimal separator (e.g. '2.66') |
| [passwd]: string type; SIM PIN2 |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CPUC?</command> |
| <profile>Price per unit and currency table (Query)</profile> |
| <description>Set command sets the parameters of Advice of Charge related price per unit and currency table in SIM card or in the active application in the UICC (GSM or USIM) file EFPUCT. PUCT information can be used to convert the home units (as used in +CAOC, +CACM and +CAMM) into currency units. SIM PIN2 is usually required to set the parameters. If setting fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Read command returns the current parameters of PUCT. |
| Defined values |
| [currency]: string type; three-character currency code (e.g. 'GBP', 'DEM'); character set as specified by command Select TE Character Set +CSCS |
| [ppu]: string type; price per unit; dot is used as a decimal separator (e.g. '2.66') |
| [passwd]: string type; SIM PIN2 |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CPUC=?</command> |
| <profile>Price per unit and currency table (Query all)</profile> |
| <description>Set command sets the parameters of Advice of Charge related price per unit and currency table in SIM card or in the active application in the UICC (GSM or USIM) file EFPUCT. PUCT information can be used to convert the home units (as used in +CAOC, +CACM and +CAMM) into currency units. SIM PIN2 is usually required to set the parameters. If setting fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Read command returns the current parameters of PUCT. |
| Defined values |
| [currency]: string type; three-character currency code (e.g. 'GBP', 'DEM'); character set as specified by command Select TE Character Set +CSCS |
| [ppu]: string type; price per unit; dot is used as a decimal separator (e.g. '2.66') |
| [passwd]: string type; SIM PIN2 |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CCWE=</command> |
| <profile>Call Meter maximum event (Assign)</profile> |
| <description>Shortly before the ACM (Accumulated Call Meter) maximum value is reached, an unsolicited result code +CCWV will be sent, if enabled by this command. The warning is issued approximately when 30 seconds call time remains. It is also issued when starting a call if less than 30 s call time remains. If setting fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Read command returns the current setting. |
| Test command returns supported settings. |
| Defined values |
| [mode]: |
| 0 Disable the call meter warning event |
| 1 Enable the call meter warning event |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CCWE?</command> |
| <profile>Call Meter maximum event (Query)</profile> |
| <description>Shortly before the ACM (Accumulated Call Meter) maximum value is reached, an unsolicited result code +CCWV will be sent, if enabled by this command. The warning is issued approximately when 30 seconds call time remains. It is also issued when starting a call if less than 30 s call time remains. If setting fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Read command returns the current setting. |
| Test command returns supported settings. |
| Defined values |
| [mode]: |
| 0 Disable the call meter warning event |
| 1 Enable the call meter warning event |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CCWE=?</command> |
| <profile>Call Meter maximum event (Query all)</profile> |
| <description>Shortly before the ACM (Accumulated Call Meter) maximum value is reached, an unsolicited result code +CCWV will be sent, if enabled by this command. The warning is issued approximately when 30 seconds call time remains. It is also issued when starting a call if less than 30 s call time remains. If setting fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Read command returns the current setting. |
| Test command returns supported settings. |
| Defined values |
| [mode]: |
| 0 Disable the call meter warning event |
| 1 Enable the call meter warning event |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CPWC=</command> |
| <profile>Power class (Assign)</profile> |
| <description>This command is used to set the preferred MT power class for each GSM frequency band supported. The interaction of this setting with the selected bearer service (+CBST and HSCSD commands) is manufacturer specific (for example, selecting a multislot operation might reduce the power class automatically). If setting fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Read command returns the currently selected output power class and default output power class for each supported frequency band (as defined by MT manufacturer). Parameter [band1] and its associated power class parameters refer to the currently used frequency band. For example, +CPWC: 2,1,1,5,4,0 in case of a dual-band MT currently using band GSM1800, for which the power class is currently set to 2, the default being class 1, and for which the currently set power class value for GSM900 is class 5 the default being class 4. |
| Test command returns supported bands and their power classes. For example, |
| +CPWC: (0,(0,4,5)),(1,(0-2)) in case of a dual-band handheld MT. |
| Defined values |
| [class], [curr_classn]s, [def_classn]s: |
| 0 default (not applicable to [curr_class]s or [def_classn]s) |
| 1… MT output power class as in GSM 45.005 [38] |
| [band], [bandn]s: |
| 0 GSM900 |
| 1 GSM1800 |
| 2 reserved for GSM1900 |
| 3 GSM 400 |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CPWC?</command> |
| <profile>Power class (Query)</profile> |
| <description>This command is used to set the preferred MT power class for each GSM frequency band supported. The interaction of this setting with the selected bearer service (+CBST and HSCSD commands) is manufacturer specific (for example, selecting a multislot operation might reduce the power class automatically). If setting fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Read command returns the currently selected output power class and default output power class for each supported frequency band (as defined by MT manufacturer). Parameter [band1] and its associated power class parameters refer to the currently used frequency band. For example, +CPWC: 2,1,1,5,4,0 in case of a dual-band MT currently using band GSM1800, for which the power class is currently set to 2, the default being class 1, and for which the currently set power class value for GSM900 is class 5 the default being class 4. |
| Test command returns supported bands and their power classes. For example, |
| +CPWC: (0,(0,4,5)),(1,(0-2)) in case of a dual-band handheld MT. |
| Defined values |
| [class], [curr_classn]s, [def_classn]s: |
| 0 default (not applicable to [curr_class]s or [def_classn]s) |
| 1… MT output power class as in GSM 45.005 [38] |
| [band], [bandn]s: |
| 0 GSM900 |
| 1 GSM1800 |
| 2 reserved for GSM1900 |
| 3 GSM 400 |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CPWC=?</command> |
| <profile>Power class (Query all)</profile> |
| <description>This command is used to set the preferred MT power class for each GSM frequency band supported. The interaction of this setting with the selected bearer service (+CBST and HSCSD commands) is manufacturer specific (for example, selecting a multislot operation might reduce the power class automatically). If setting fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Read command returns the currently selected output power class and default output power class for each supported frequency band (as defined by MT manufacturer). Parameter [band1] and its associated power class parameters refer to the currently used frequency band. For example, +CPWC: 2,1,1,5,4,0 in case of a dual-band MT currently using band GSM1800, for which the power class is currently set to 2, the default being class 1, and for which the currently set power class value for GSM900 is class 5 the default being class 4. |
| Test command returns supported bands and their power classes. For example, |
| +CPWC: (0,(0,4,5)),(1,(0-2)) in case of a dual-band handheld MT. |
| Defined values |
| [class], [curr_classn]s, [def_classn]s: |
| 0 default (not applicable to [curr_class]s or [def_classn]s) |
| 1… MT output power class as in GSM 45.005 [38] |
| [band], [bandn]s: |
| 0 GSM900 |
| 1 GSM1800 |
| 2 reserved for GSM1900 |
| 3 GSM 400 |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CLAN=</command> |
| <profile>Set Language (Assign)</profile> |
| <description>This command sets the language in the MT. The set-command must confirm the selected language with the MMI-module in the MT. If setting fails, a MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| The [code]-parameter is a two-letter abbreviation of the language. The language codes, as defined in ISO 639, consists of two characters, e.g. 'sv', 'en' etc. |
| The complete set of language codes to be used are manufacturer specific and should all be possible to use with the command. Some examples are described under [code]. For a complete list see ISO 639. |
| The read command gives the current language as output. If the language has been set to 'AUTO', the read command returns the current language set from the SIM-card /UICC. Hence, the 'AUTO'-code is never returned by the read-command. |
| Test command returns supported [code]s. |
| Defined values |
| [code]: (not all language codes are present in this list) |
| 'AUTO' Read language from SIM-card /UICC. 'Auto' is not returned by the read-command. |
| 'sw' Swedish |
| 'fi' Finnish |
| 'da' Danish |
| 'no' Norwegian |
| 'de' German |
| 'fr' French |
| 'es' Spanish |
| 'it' Italian |
| 'en' English |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CLAN?</command> |
| <profile>Set Language (Query)</profile> |
| <description>This command sets the language in the MT. The set-command must confirm the selected language with the MMI-module in the MT. If setting fails, a MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| The [code]-parameter is a two-letter abbreviation of the language. The language codes, as defined in ISO 639, consists of two characters, e.g. 'sv', 'en' etc. |
| The complete set of language codes to be used are manufacturer specific and should all be possible to use with the command. Some examples are described under [code]. For a complete list see ISO 639. |
| The read command gives the current language as output. If the language has been set to 'AUTO', the read command returns the current language set from the SIM-card /UICC. Hence, the 'AUTO'-code is never returned by the read-command. |
| Test command returns supported [code]s. |
| Defined values |
| [code]: (not all language codes are present in this list) |
| 'AUTO' Read language from SIM-card /UICC. 'Auto' is not returned by the read-command. |
| 'sw' Swedish |
| 'fi' Finnish |
| 'da' Danish |
| 'no' Norwegian |
| 'de' German |
| 'fr' French |
| 'es' Spanish |
| 'it' Italian |
| 'en' English |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CLAN=?</command> |
| <profile>Set Language (Query all)</profile> |
| <description>This command sets the language in the MT. The set-command must confirm the selected language with the MMI-module in the MT. If setting fails, a MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| The [code]-parameter is a two-letter abbreviation of the language. The language codes, as defined in ISO 639, consists of two characters, e.g. 'sv', 'en' etc. |
| The complete set of language codes to be used are manufacturer specific and should all be possible to use with the command. Some examples are described under [code]. For a complete list see ISO 639. |
| The read command gives the current language as output. If the language has been set to 'AUTO', the read command returns the current language set from the SIM-card /UICC. Hence, the 'AUTO'-code is never returned by the read-command. |
| Test command returns supported [code]s. |
| Defined values |
| [code]: (not all language codes are present in this list) |
| 'AUTO' Read language from SIM-card /UICC. 'Auto' is not returned by the read-command. |
| 'sw' Swedish |
| 'fi' Finnish |
| 'da' Danish |
| 'no' Norwegian |
| 'de' German |
| 'fr' French |
| 'es' Spanish |
| 'it' Italian |
| 'en' English |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CLAE=</command> |
| <profile>Language Event (Assign)</profile> |
| <description>This command is used to enable/disable unsolicited result code +CLAV: [code]. If [mode]=1, +CLAV: [code ] is sent from the MT when the language in the MT is changed. If setting fails, a MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Read command returns the current status for [mode]. |
| Test command returns supported [mode]s. |
| Defined values |
| [mode]: |
| 0 Disable unsolicited result code +CLAE |
| 1 Enable unsolicited result code +CLAE |
| [code]: For description see +CLAN. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CLAE?</command> |
| <profile>Language Event (Query)</profile> |
| <description>This command is used to enable/disable unsolicited result code +CLAV: [code]. If [mode]=1, +CLAV: [code ] is sent from the MT when the language in the MT is changed. If setting fails, a MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Read command returns the current status for [mode]. |
| Test command returns supported [mode]s. |
| Defined values |
| [mode]: |
| 0 Disable unsolicited result code +CLAE |
| 1 Enable unsolicited result code +CLAE |
| [code]: For description see +CLAN. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CLAE=?</command> |
| <profile>Language Event (Query all)</profile> |
| <description>This command is used to enable/disable unsolicited result code +CLAV: [code]. If [mode]=1, +CLAV: [code ] is sent from the MT when the language in the MT is changed. If setting fails, a MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Read command returns the current status for [mode]. |
| Test command returns supported [mode]s. |
| Defined values |
| [mode]: |
| 0 Disable unsolicited result code +CLAE |
| 1 Enable unsolicited result code +CLAE |
| [code]: For description see +CLAN. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSGT=</command> |
| <profile>Set Greeting Text (Assign)</profile> |
| <description>This command sets and activates the greeting text in the MT. The greeting text is shown in the MT display when the MT is turned on. The command can also be used to deactivate a text. If setting fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| The read command queries the current [text] and the status of the [mode] parameter |
| Test command returns supported [mode]s and the maximum number of characters in [text]. For example, |
| +CSGT: (0-1),20 |
| Defined values |
| [text]: string type; A free text that shall be displayed. The text can not include [CR] |
| [mode]: |
| 0 Turn off greeting text. |
| 1 Turn on greeting text |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSGT?</command> |
| <profile>Set Greeting Text (Query)</profile> |
| <description>This command sets and activates the greeting text in the MT. The greeting text is shown in the MT display when the MT is turned on. The command can also be used to deactivate a text. If setting fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| The read command queries the current [text] and the status of the [mode] parameter |
| Test command returns supported [mode]s and the maximum number of characters in [text]. For example, |
| +CSGT: (0-1),20 |
| Defined values |
| [text]: string type; A free text that shall be displayed. The text can not include [CR] |
| [mode]: |
| 0 Turn off greeting text. |
| 1 Turn on greeting text |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSGT=?</command> |
| <profile>Set Greeting Text (Query all)</profile> |
| <description>This command sets and activates the greeting text in the MT. The greeting text is shown in the MT display when the MT is turned on. The command can also be used to deactivate a text. If setting fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| The read command queries the current [text] and the status of the [mode] parameter |
| Test command returns supported [mode]s and the maximum number of characters in [text]. For example, |
| +CSGT: (0-1),20 |
| Defined values |
| [text]: string type; A free text that shall be displayed. The text can not include [CR] |
| [mode]: |
| 0 Turn off greeting text. |
| 1 Turn on greeting text |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSVM=</command> |
| <profile>Set Voice Mail Number (Assign)</profile> |
| <description>The number to the voice mail server is set with this command. The parameters [number] and [type] can be left out if the parameter [mode] is set to 0. If setting fails, an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Read command returns the currently selected voice mail number and the status (i.e. enabled/disabled). |
| Test command returns supported [mode]s and [type]s. |
| Defined values |
| [mode]: |
| 0 Disable the voice mail number. |
| 1 Enable the voice mail number. |
| [number]: string type; Character string [0..9,+] |
| [type]: integer type; Type of address octet. (refer TS 24.008 subclause 10.5.4.7) |
| 129 ISDN / telephony numbering plan, national / international unknown |
| 145 ISDN / telephony numbering plan, international number |
| 161 ISDN / telephony numbering plan, national number |
| 128 - 255 Other values refer TS 24.008 section 10.5.4.7 |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7); default 145 when dialling string includes international access code character '+', otherwise 129 |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSVM?</command> |
| <profile>Set Voice Mail Number (Query)</profile> |
| <description>The number to the voice mail server is set with this command. The parameters [number] and [type] can be left out if the parameter [mode] is set to 0. If setting fails, an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Read command returns the currently selected voice mail number and the status (i.e. enabled/disabled). |
| Test command returns supported [mode]s and [type]s. |
| Defined values |
| [mode]: |
| 0 Disable the voice mail number. |
| 1 Enable the voice mail number. |
| [number]: string type; Character string [0..9,+] |
| [type]: integer type; Type of address octet. (refer TS 24.008 subclause 10.5.4.7) |
| 129 ISDN / telephony numbering plan, national / international unknown |
| 145 ISDN / telephony numbering plan, international number |
| 161 ISDN / telephony numbering plan, national number |
| 128 - 255 Other values refer TS 24.008 section 10.5.4.7 |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7); default 145 when dialling string includes international access code character '+', otherwise 129 |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CSVM=?</command> |
| <profile>Set Voice Mail Number (Query all)</profile> |
| <description>The number to the voice mail server is set with this command. The parameters [number] and [type] can be left out if the parameter [mode] is set to 0. If setting fails, an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Read command returns the currently selected voice mail number and the status (i.e. enabled/disabled). |
| Test command returns supported [mode]s and [type]s. |
| Defined values |
| [mode]: |
| 0 Disable the voice mail number. |
| 1 Enable the voice mail number. |
| [number]: string type; Character string [0..9,+] |
| [type]: integer type; Type of address octet. (refer TS 24.008 subclause 10.5.4.7) |
| 129 ISDN / telephony numbering plan, national / international unknown |
| 145 ISDN / telephony numbering plan, international number |
| 161 ISDN / telephony numbering plan, national number |
| 128 - 255 Other values refer TS 24.008 section 10.5.4.7 |
| [type]: type of address octet in integer format (refer TS 24.008 [8] subclause 10.5.4.7); default 145 when dialling string includes international access code character '+', otherwise 129 |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CRMC=</command> |
| <profile>Ring Melody Control (Assign)</profile> |
| <description>Write command causes the MT to set a specific ring melody and volume for the selected call type and profile. The default values for the optional parameters are defined by the manufacturer. |
| Read command queries the settings for the ring melody. If call types and profiles are available the corresponding ring melodies are listed. Starting with call type1 and profile1 the ring melody settings for each available profile and call type is issued. |
| Test command returns the list of available ring melodies, volumes, call types and profiles. |
| Defined values: |
| [index]: integer type; manufacturer specific number to identify a certain ring melody |
| [volume]: integer type value with manufacturer specific range (smallest value represents the lowest sound level) |
| [call typex]: integer type; manufacturer specific number for a call type |
| [profilex]: integer type; manufacturer specific number for a profile |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CRMC?</command> |
| <profile>Ring Melody Control (Query)</profile> |
| <description>Write command causes the MT to set a specific ring melody and volume for the selected call type and profile. The default values for the optional parameters are defined by the manufacturer. |
| Read command queries the settings for the ring melody. If call types and profiles are available the corresponding ring melodies are listed. Starting with call type1 and profile1 the ring melody settings for each available profile and call type is issued. |
| Test command returns the list of available ring melodies, volumes, call types and profiles. |
| Defined values: |
| [index]: integer type; manufacturer specific number to identify a certain ring melody |
| [volume]: integer type value with manufacturer specific range (smallest value represents the lowest sound level) |
| [call typex]: integer type; manufacturer specific number for a call type |
| [profilex]: integer type; manufacturer specific number for a profile |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CRMC=?</command> |
| <profile>Ring Melody Control (Query all)</profile> |
| <description>Write command causes the MT to set a specific ring melody and volume for the selected call type and profile. The default values for the optional parameters are defined by the manufacturer. |
| Read command queries the settings for the ring melody. If call types and profiles are available the corresponding ring melodies are listed. Starting with call type1 and profile1 the ring melody settings for each available profile and call type is issued. |
| Test command returns the list of available ring melodies, volumes, call types and profiles. |
| Defined values: |
| [index]: integer type; manufacturer specific number to identify a certain ring melody |
| [volume]: integer type value with manufacturer specific range (smallest value represents the lowest sound level) |
| [call typex]: integer type; manufacturer specific number for a call type |
| [profilex]: integer type; manufacturer specific number for a profile |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CRMP=</command> |
| <profile>Ring Melody Playback (Assign)</profile> |
| <description>Execution command causes the MT to playback a specific ring type. The default values for the optional parameters are the current selected in the MT. |
| Test command returns the available ring melodies. |
| Defined values: |
| [call type]: integer type; manufacturer specific |
| [volume]: integer type value with manufacturer specific range (smallest value represents the lowest sound level) |
| [type]: |
| 0 Manufacturer defined |
| 1 User defined |
| [index]: integer type; |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CRMP=?</command> |
| <profile>Ring Melody Playback (Query all)</profile> |
| <description>Execution command causes the MT to playback a specific ring type. The default values for the optional parameters are the current selected in the MT. |
| Test command returns the available ring melodies. |
| Defined values: |
| [call type]: integer type; manufacturer specific |
| [volume]: integer type value with manufacturer specific range (smallest value represents the lowest sound level) |
| [type]: |
| 0 Manufacturer defined |
| 1 User defined |
| [index]: integer type; |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CMAR=</command> |
| <profile>Master Reset (Assign)</profile> |
| <description>This command requests the MT to reset user data. The user data in the phone will be reset to default values. If setting fails, a MT error, +CME ERROR: [err], is returned. Refer subclause 9.2 for [err] values. |
| If the MT is locked and this command is used, then the MT will be unlocked after the master reset. |
| Test command returns OK |
| Defined values |
| [phone lock code ] string type; Security code (Phone Lock code) must be verified before performing the master reset. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CMAR=?</command> |
| <profile>Master Reset (Query all)</profile> |
| <description>This command requests the MT to reset user data. The user data in the phone will be reset to default values. If setting fails, a MT error, +CME ERROR: [err], is returned. Refer subclause 9.2 for [err] values. |
| If the MT is locked and this command is used, then the MT will be unlocked after the master reset. |
| Test command returns OK |
| Defined values |
| [phone lock code ] string type; Security code (Phone Lock code) must be verified before performing the master reset. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CLAC</command> |
| <profile>List all available AT commands </profile> |
| <description>Execution command causes the MT to return one or more lines of AT Commands. |
| Note: This command only returns the AT commands that are available for the user. |
| Defined values |
| [AT Command ]: |
| Defines the AT command including the prefix AT. Text shall not contain the sequence 0[CR] or OK[CR] |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CLAC=?</command> |
| <profile>List all available AT commands (Query all)</profile> |
| <description>Execution command causes the MT to return one or more lines of AT Commands. |
| Note: This command only returns the AT commands that are available for the user. |
| Defined values |
| [AT Command ]: |
| Defines the AT command including the prefix AT. Text shall not contain the sequence 0[CR] or OK[CR] |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CALD=</command> |
| <profile>Delete alarm (Assign)</profile> |
| <description>Action command deletes an alarm in the MT. If the command fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Test command returns supported array index values. |
| Defined values |
| [n]: integer type value indicating the index of the alarm; default is manufacturer specific |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CALD=?</command> |
| <profile>Delete alarm (Query all)</profile> |
| <description>Action command deletes an alarm in the MT. If the command fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Test command returns supported array index values. |
| Defined values |
| [n]: integer type value indicating the index of the alarm; default is manufacturer specific |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CAPD=</command> |
| <profile>Postpone or dismiss an alarm (Assign)</profile> |
| <description>Set command postpones or dismisses a currently active alarm. If the command fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Test command returns supported [sec]-parameter values. |
| Defined values |
| [sec]: integer type value indicating the number of seconds to postpone the alarm. If [sec] is set to 0 (default), the alarm is dismissed. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CAPD=?</command> |
| <profile>Postpone or dismiss an alarm (Query all)</profile> |
| <description>Set command postpones or dismisses a currently active alarm. If the command fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Test command returns supported [sec]-parameter values. |
| Defined values |
| [sec]: integer type value indicating the number of seconds to postpone the alarm. If [sec] is set to 0 (default), the alarm is dismissed. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CTZU=</command> |
| <profile>Automatic Time Zone Update (Assign)</profile> |
| <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 subclause 9.2 for [err] values. |
| Read command returns the current settings in the MT. |
| Test command returns supported on- and off-values. |
| Defined values |
| [onoff]: integer type value indicating: |
| 0 – Disable automatic time zone update via NITZ (default). |
| 1 – Enable automatic time zone update via NITZ. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CTZU?</command> |
| <profile>Automatic Time Zone Update (Query)</profile> |
| <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 subclause 9.2 for [err] values. |
| Read command returns the current settings in the MT. |
| Test command returns supported on- and off-values. |
| Defined values |
| [onoff]: integer type value indicating: |
| 0 – Disable automatic time zone update via NITZ (default). |
| 1 – Enable automatic time zone update via NITZ. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CTZU=?</command> |
| <profile>Automatic Time Zone Update (Query all)</profile> |
| <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 subclause 9.2 for [err] values. |
| Read command returns the current settings in the MT. |
| Test command returns supported on- and off-values. |
| Defined values |
| [onoff]: integer type value indicating: |
| 0 – Disable automatic time zone update via NITZ (default). |
| 1 – Enable automatic time zone update via NITZ. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CTZR=</command> |
| <profile>Time Zone Reporting (Assign)</profile> |
| <description>This set command enables and disables the time zone change event reporting. If the reporting is enabled the MT returns the unsolicited result code +CTZV: [tz] whenever the time zone is changed. If setting fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Read command returns the current reporting settings in the MT. |
| Test command returns supported [onoff]-values. |
| NOTE: The Time Zone reporting is not affected by the Automatic Time Zone setting command, +CTZU. |
| Defined values |
| [onoff]: integer type value indicating: |
| 0 – disable time zone change event reporting (default). |
| 1 – Enable time zone change event reporting. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CTZR?</command> |
| <profile>Time Zone Reporting (Query)</profile> |
| <description>This set command enables and disables the time zone change event reporting. If the reporting is enabled the MT returns the unsolicited result code +CTZV: [tz] whenever the time zone is changed. If setting fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Read command returns the current reporting settings in the MT. |
| Test command returns supported [onoff]-values. |
| NOTE: The Time Zone reporting is not affected by the Automatic Time Zone setting command, +CTZU. |
| Defined values |
| [onoff]: integer type value indicating: |
| 0 – disable time zone change event reporting (default). |
| 1 – Enable time zone change event reporting. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CTZR=?</command> |
| <profile>Time Zone Reporting (Query all)</profile> |
| <description>This set command enables and disables the time zone change event reporting. If the reporting is enabled the MT returns the unsolicited result code +CTZV: [tz] whenever the time zone is changed. If setting fails in an MT error, +CME ERROR: [err] is returned. Refer subclause 9.2 for [err] values. |
| Read command returns the current reporting settings in the MT. |
| Test command returns supported [onoff]-values. |
| NOTE: The Time Zone reporting is not affected by the Automatic Time Zone setting command, +CTZU. |
| Defined values |
| [onoff]: integer type value indicating: |
| 0 – disable time zone change event reporting (default). |
| 1 – Enable time zone change event reporting. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CPROT=</command> |
| <profile>Enter protocol mode(Assign)</profile> |
| <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 subclause 9.2 for possible [err] values. |
| Test command returns values supported as a compound value. |
| Defined values |
| [proto] |
| 0 OBEX (refer.[44]) |
| …15 reserved by the present document |
| 16... manufacturer specific |
| [version]: version number of [proto]: string type |
| [lsap1]: 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] subclause 2.9.4) |
| 2 IrMC level 1 and 2 (Minimum and Access Levels) Only. .(refer [43] subclause 2.9.4) |
| 4IrMC level 1, 2 and 3 (Minimum, Access, Index Levels) Only- implies static index support. .(refer [43] subclause 2.9.4) |
| 8IrMC level 1, 2 and 4 (Minimum, Access and Sync Levels) Only-implies unique index support. .(refer [43] subclause 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] subclause 2.9.4) |
| …15 reserved by the present document |
| 16... manufacturer specific |
| [lsap2]...[lsapN] |
| 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 |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CPROT=?</command> |
| <profile>Enter protocol mode(Query all)</profile> |
| <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 subclause 9.2 for possible [err] values. |
| Test command returns values supported as a compound value. |
| Defined values |
| [proto] |
| 0 OBEX (refer.[44]) |
| …15 reserved by the present document |
| 16... manufacturer specific |
| [version]: version number of [proto]: string type |
| [lsap1]: 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] subclause 2.9.4) |
| 2 IrMC level 1 and 2 (Minimum and Access Levels) Only. .(refer [43] subclause 2.9.4) |
| 4IrMC level 1, 2 and 3 (Minimum, Access, Index Levels) Only- implies static index support. .(refer [43] subclause 2.9.4) |
| 8IrMC level 1, 2 and 4 (Minimum, Access and Sync Levels) Only-implies unique index support. .(refer [43] subclause 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] subclause 2.9.4) |
| …15 reserved by the present document |
| 16... manufacturer specific |
| [lsap2]...[lsapN] |
| 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 |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CGLA=</command> |
| <profile>Generic UICC Logical Channel access (Assign)</profile> |
| <description>Set command transmits to the MT the [command] it then shall send as it is to the UICC. In the same manner the UICC [response] shall be sent back by the MT to the TA as it is. Refer subclause 9.2 for [err] values. |
| This command allows a direct control of the 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 [59] for USIM authenticate command definition. |
| NOTE: Compared to Restricted UICC Access command +CRLA, the definition of +CGLA allows TE to take more control over the UICC‑MT interface. The locking and unlocking of the interface may be done by a special [command] value or automatically by TA/MT (by interpreting [command] parameter). In case that TE application does not use the unlock command (or does not send a [command] causing automatic unlock) in a certain timeout value, MT may release the locking. |
| 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 3GPP TS 31.101 [65] (hexadecimal character format; refer +CSCS) |
| [response] : response to the command passed on by the UICC to the MT in the format as described in 3GPP TS 31.101 [65] (hexadecimal character format; refer +CSCS) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CGLA=?</command> |
| <profile>Generic UICC Logical Channel access (Query all)</profile> |
| <description>Set command transmits to the MT the [command] it then shall send as it is to the UICC. In the same manner the UICC [response] shall be sent back by the MT to the TA as it is. Refer subclause 9.2 for [err] values. |
| This command allows a direct control of the 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 [59] for USIM authenticate command definition. |
| NOTE: Compared to Restricted UICC Access command +CRLA, the definition of +CGLA allows TE to take more control over the UICC‑MT interface. The locking and unlocking of the interface may be done by a special [command] value or automatically by TA/MT (by interpreting [command] parameter). In case that TE application does not use the unlock command (or does not send a [command] causing automatic unlock) in a certain timeout value, MT may release the locking. |
| 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 3GPP TS 31.101 [65] (hexadecimal character format; refer +CSCS) |
| [response] : response to the command passed on by the UICC to the MT in the format as described in 3GPP TS 31.101 [65] (hexadecimal character format; refer +CSCS) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CRLA=</command> |
| <profile>Restricted UICC Logical Channel access (Assign)</profile> |
| <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 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 subclause 9.2 for [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 a 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 |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CRLA=?</command> |
| <profile>Restricted UICC Logical Channel access (Query all)</profile> |
| <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 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 subclause 9.2 for [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 a 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 |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CCHO=</command> |
| <profile>Open Logical Channel (Assign)</profile> |
| <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 UICC, which is attached to ME. The 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. |
| Note that the logical channel number is contained in the CLASS byte of an APDU command, thus implicitly contained in all APDU commands sent to a UICC. In this case it will be up to the MT to manage the logical channel part of the APDU CLASS byte and to ensure that the chosen logical channel is relevant to the [sessionid] indicated in the AT command. See 3GPP TS 31.101 [65] for further information on logical channels in APDU commands protocol. |
| Refer subclause 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]: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 (string without double quotes that represents a decimal value) |
| See 3GPP TS 31.101 [65] for more information about defined values. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CCHO=?</command> |
| <profile>Open Logical Channel (Query all)</profile> |
| <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 UICC, which is attached to ME. The 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. |
| Note that the logical channel number is contained in the CLASS byte of an APDU command, thus implicitly contained in all APDU commands sent to a UICC. In this case it will be up to the MT to manage the logical channel part of the APDU CLASS byte and to ensure that the chosen logical channel is relevant to the [sessionid] indicated in the AT command. See 3GPP TS 31.101 [65] for further information on logical channels in APDU commands protocol. |
| Refer subclause 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]: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 (string without double quotes that represents a decimal value) |
| See 3GPP TS 31.101 [65] for more information about defined values. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CCHC=</command> |
| <profile>Close Logical Channel (Assign)</profile> |
| <description>This command asks the ME to close a communication session with the 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 subclause 9.2 for possible [err] values. |
| Defined values |
| [sessionid]: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 (string without double quotes that represents a decimal value) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CCHC=?</command> |
| <profile>Close Logical Channel (Query all)</profile> |
| <description>This command asks the ME to close a communication session with the 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 subclause 9.2 for possible [err] values. |
| Defined values |
| [sessionid]: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 (string without double quotes that represents a decimal value) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CEAP=</command> |
| <profile>EAP authentication (Assign)</profile> |
| <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. |
| If the targeted application on the UICC does support the requested EAP method, the MT shall derive the directory file identifier (see ETSI TS 102 310 [66]) from [dfname] and [EAPMethod], 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 'EAP method not supported'. |
| Refer subclause 9.2 for possible [err] values. |
| Defined values |
| [dfname]: string type; all selectable applications represented in the UICC by an AID are referenced by a DF name coded on 1 to 16 bytes. |
| [EAPMethod]: octet type; this is the EAP Method Type as defined in [68] |
| [EAP packet data]: as defined in ETSI TS 102 310 [66] |
| [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. |
| [EAP packet response]: as defined in ETSI TS 102 310 [66] |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CEAP=?</command> |
| <profile>EAP authentication (Query all)</profile> |
| <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. |
| If the targeted application on the UICC does support the requested EAP method, the MT shall derive the directory file identifier (see ETSI TS 102 310 [66]) from [dfname] and [EAPMethod], 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 'EAP method not supported'. |
| Refer subclause 9.2 for possible [err] values. |
| Defined values |
| [dfname]: string type; all selectable applications represented in the UICC by an AID are referenced by a DF name coded on 1 to 16 bytes. |
| [EAPMethod]: octet type; this is the EAP Method Type as defined in [68] |
| [EAP packet data]: as defined in ETSI TS 102 310 [66] |
| [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. |
| [EAP packet response]: as defined in ETSI TS 102 310 [66] |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CERP=</command> |
| <profile>EAP Retrieve Parameters (Assign)</profile> |
| <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 'Incorrect parameters'. |
| Refer subclause 9.2 for possible [err] values. |
| Defined values |
| [EAPparameter]: |
| 1Keys |
| 2Status |
| 3Identity |
| 4Pseudonym |
| [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 with EAP Retreive Parameters +CERP command. |
| [EAP parameter response]: depends on the value of [EAPparameter]; format of the parameter retrieved is as defined in ETSI TS 102 310 [66]. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CERP=?</command> |
| <profile>EAP Retrieve Parameters (Query all)</profile> |
| <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 'Incorrect parameters'. |
| Refer subclause 9.2 for possible [err] values. |
| Defined values |
| [EAPparameter]: |
| 1Keys |
| 2Status |
| 3Identity |
| 4Pseudonym |
| [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 with EAP Retreive Parameters +CERP command. |
| [EAP parameter response]: depends on the value of [EAPparameter]; format of the parameter retrieved is as defined in ETSI TS 102 310 [66]. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CUAD=</command> |
| <profile>UICC Application Discovery (Assign)</profile> |
| <description>This command asks the MT to discover what applications are available for selection on the UICC. According to 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. |
| Defined values |
| [response]:the response is the content of the EFDIR. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CUAD=?</command> |
| <profile>UICC Application Discovery (Query all)</profile> |
| <description>This command asks the MT to discover what applications are available for selection on the UICC. According to 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. |
| Defined values |
| [response]:the response is the content of the EFDIR. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CMEE=</command> |
| <profile>Report Mobile Termination error (Assign)</profile> |
| <description>Set command disables or enables the use of result code +CME ERROR: [err] as an indication of an error relating to the functionality of the MT. When enabled, MT related errors cause +CME ERROR: [err] final result code instead of the regular ERROR final result code. ERROR is returned normally when error is related to syntax, invalid parameters, or TA functionality. |
| Test command returns values supported as a compound value. |
| Defined values |
| [n]: |
| 0 disable +CME ERROR: [err] result code and use ERROR instead |
| 1 enable +CME ERROR: [err] result code and use numeric [err] values (refer next subclause) |
| 2 enable +CME ERROR: [err] result code and use verbose [err] values (refer next subclause) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CMEE?</command> |
| <profile>Report Mobile Termination error (Query)</profile> |
| <description>Set command disables or enables the use of result code +CME ERROR: [err] as an indication of an error relating to the functionality of the MT. When enabled, MT related errors cause +CME ERROR: [err] final result code instead of the regular ERROR final result code. ERROR is returned normally when error is related to syntax, invalid parameters, or TA functionality. |
| Test command returns values supported as a compound value. |
| Defined values |
| [n]: |
| 0 disable +CME ERROR: [err] result code and use ERROR instead |
| 1 enable +CME ERROR: [err] result code and use numeric [err] values (refer next subclause) |
| 2 enable +CME ERROR: [err] result code and use verbose [err] values (refer next subclause) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CMEE=?</command> |
| <profile>Report Mobile Termination error (Query all)</profile> |
| <description>Set command disables or enables the use of result code +CME ERROR: [err] as an indication of an error relating to the functionality of the MT. When enabled, MT related errors cause +CME ERROR: [err] final result code instead of the regular ERROR final result code. ERROR is returned normally when error is related to syntax, invalid parameters, or TA functionality. |
| Test command returns values supported as a compound value. |
| Defined values |
| [n]: |
| 0 disable +CME ERROR: [err] result code and use ERROR instead |
| 1 enable +CME ERROR: [err] result code and use numeric [err] values (refer next subclause) |
| 2 enable +CME ERROR: [err] result code and use verbose [err] values (refer next subclause) |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CGDSCONT=</command> |
| <profile>Define Secondary PDP Context (Assign)</profile> |
| <description>The set command specifies PDP context parameter values for a Secondary PDP context identified by the (local) context identification parameter, [cid]. The number of PDP contexts that may be in a defined state at the same time is given by the range returned by the test command. |
| A special form of the set command, +CGDSCONT= [cid] causes the values for context number [cid] to become undefined. |
| The read command returns the current settings for each defined context. |
| Defined values |
| [cid]: (PDP Context Identifier) a numeric parameter which specifies a particular PDP context definition. The parameter is local to the TE-MT interface and is used in other PDP context-related commands. The range of permitted values (minimum value = 1) is returned by the test form of the command. |
| [p_cid]: (Primary PDP Context Identifier) a numeric parameter which specifies a particular PDP context definition which has been specified by use of the +CGDCONT command. The parameter is local to the TE-MT interface. The list of permitted values is returned by the test form of the command. |
| [d_comp]: a numeric parameter that controls PDP data compression (applicable for SNDCPonly) (refer 3GPP TS 44.065 [61]) |
| 0 - off (default if value is omitted) |
| 1 - on (manufacturer preferred compression) |
| 2 - V.42bis |
| 3 - V.44 |
| Other values are reserved. |
| [h_comp]: a numeric parameter that controls PDP header compression (refer 3GPP TS 44.065 [61] and 3GPP TS 25.323 [62]) |
| 0 - off (default if value is omitted) |
| 1 - on (manufacturer preferred compression) |
| 2 - RFC1144 (applicable for SNDCP only) |
| 3 - RFC2507 |
| 4 - RFC3095 (applicable for PDCP only) |
| Other values are reserved. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CGDSCONT?</command> |
| <profile>Define Secondary PDP Context (Query)</profile> |
| <description>The set command specifies PDP context parameter values for a Secondary PDP context identified by the (local) context identification parameter, [cid]. The number of PDP contexts that may be in a defined state at the same time is given by the range returned by the test command. |
| A special form of the set command, +CGDSCONT= [cid] causes the values for context number [cid] to become undefined. |
| The read command returns the current settings for each defined context. |
| Defined values |
| [cid]: (PDP Context Identifier) a numeric parameter which specifies a particular PDP context definition. The parameter is local to the TE-MT interface and is used in other PDP context-related commands. The range of permitted values (minimum value = 1) is returned by the test form of the command. |
| [p_cid]: (Primary PDP Context Identifier) a numeric parameter which specifies a particular PDP context definition which has been specified by use of the +CGDCONT command. The parameter is local to the TE-MT interface. The list of permitted values is returned by the test form of the command. |
| [d_comp]: a numeric parameter that controls PDP data compression (applicable for SNDCPonly) (refer 3GPP TS 44.065 [61]) |
| 0 - off (default if value is omitted) |
| 1 - on (manufacturer preferred compression) |
| 2 - V.42bis |
| 3 - V.44 |
| Other values are reserved. |
| [h_comp]: a numeric parameter that controls PDP header compression (refer 3GPP TS 44.065 [61] and 3GPP TS 25.323 [62]) |
| 0 - off (default if value is omitted) |
| 1 - on (manufacturer preferred compression) |
| 2 - RFC1144 (applicable for SNDCP only) |
| 3 - RFC2507 |
| 4 - RFC3095 (applicable for PDCP only) |
| Other values are reserved. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CGDSCONT=?</command> |
| <profile>Define Secondary PDP Context (Query all)</profile> |
| <description>The set command specifies PDP context parameter values for a Secondary PDP context identified by the (local) context identification parameter, [cid]. The number of PDP contexts that may be in a defined state at the same time is given by the range returned by the test command. |
| A special form of the set command, +CGDSCONT= [cid] causes the values for context number [cid] to become undefined. |
| The read command returns the current settings for each defined context. |
| Defined values |
| [cid]: (PDP Context Identifier) a numeric parameter which specifies a particular PDP context definition. The parameter is local to the TE-MT interface and is used in other PDP context-related commands. The range of permitted values (minimum value = 1) is returned by the test form of the command. |
| [p_cid]: (Primary PDP Context Identifier) a numeric parameter which specifies a particular PDP context definition which has been specified by use of the +CGDCONT command. The parameter is local to the TE-MT interface. The list of permitted values is returned by the test form of the command. |
| [d_comp]: a numeric parameter that controls PDP data compression (applicable for SNDCPonly) (refer 3GPP TS 44.065 [61]) |
| 0 - off (default if value is omitted) |
| 1 - on (manufacturer preferred compression) |
| 2 - V.42bis |
| 3 - V.44 |
| Other values are reserved. |
| [h_comp]: a numeric parameter that controls PDP header compression (refer 3GPP TS 44.065 [61] and 3GPP TS 25.323 [62]) |
| 0 - off (default if value is omitted) |
| 1 - on (manufacturer preferred compression) |
| 2 - RFC1144 (applicable for SNDCP only) |
| 3 - RFC2507 |
| 4 - RFC3095 (applicable for PDCP only) |
| Other values are reserved. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CGAUTO=</command> |
| <profile>Automatic response to a network request for PDP context activation (Assign)</profile> |
| <description>The set command disables or enables an automatic positive response (auto-answer) to the receipt of a Request PDP Context Activation message from the network. It also provides control over the use of the V.250 basic commands 'S0', 'A and 'H' for handling network requests for PDP context activation. The setting does not affect the issuing of the unsolicited result code RING or +CRING. |
| The test command returns the values of [n] supported by the MT as a compound value. |
| When the +CGAUTO=0 command is received, the MT shall not perform a PS detach if it is attached. Subsequently, when the MT announces a network request for PDP context activation by issuing the unsolicited result code RING or +CRING, the TE may manually accept or reject the request by issuing the +CGANS command or may simply ignore the network request. |
| When the +CGAUTO=1 command is received, the MT shall attempt to perform a PS attach if it is not already attached. Failure will result in ERROR or, if enabled, +CME ERROR being returned to the TE. Subsequently, when the MT announces a network request for PDP context activation by issuing the unsolicited result code RING or +CRING to the TE, this is followed by the intermediate result code CONNECT. The MT then enters V.250 online data state and follows the same procedure as it would after having received a +CGANS=1 with no [L2P] or [cid] values specified. |
| Defined values |
| [n]: |
| 0 turn off automatic response for Packet Domain only |
| 1 turn on automatic response for Packet Domain only |
| 2 modem compatibility mode, Packet Domain only |
| 3 modem compatibility mode, Packet Domain and circuit switched calls (default) |
| For [n] = 0 Packet DomainS network requests are manually accepted or rejected by the +CGANS command. |
| For [n] = 1 Packet Domain network requests are automatically accepted according to the description above. |
| For [n] = 2, automatic acceptance of Packet Domain network requests is controlled by the 'S0' command. Manual control uses the 'A' and 'H' commands, respectively, to accept and reject Packet Domain requests. (+CGANS may also be used.) Incoming circuit switched calls can be neither manually nor automatically answered. |
| For [n] = 3, automatic acceptance of both Packet Domain network requests and incoming circuit switched calls is controlled by the 'S0' command. Manual control uses the 'A' and 'H' commands, respectively, to accept and reject Packet Domain requests. (+CGANS may also be used.) Circuit switched calls are handled as described elsewhere in this specification. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CGAUTO?</command> |
| <profile>Automatic response to a network request for PDP context activation (Query)</profile> |
| <description>The set command disables or enables an automatic positive response (auto-answer) to the receipt of a Request PDP Context Activation message from the network. It also provides control over the use of the V.250 basic commands 'S0', 'A and 'H' for handling network requests for PDP context activation. The setting does not affect the issuing of the unsolicited result code RING or +CRING. |
| The test command returns the values of [n] supported by the MT as a compound value. |
| When the +CGAUTO=0 command is received, the MT shall not perform a PS detach if it is attached. Subsequently, when the MT announces a network request for PDP context activation by issuing the unsolicited result code RING or +CRING, the TE may manually accept or reject the request by issuing the +CGANS command or may simply ignore the network request. |
| When the +CGAUTO=1 command is received, the MT shall attempt to perform a PS attach if it is not already attached. Failure will result in ERROR or, if enabled, +CME ERROR being returned to the TE. Subsequently, when the MT announces a network request for PDP context activation by issuing the unsolicited result code RING or +CRING to the TE, this is followed by the intermediate result code CONNECT. The MT then enters V.250 online data state and follows the same procedure as it would after having received a +CGANS=1 with no [L2P] or [cid] values specified. |
| Defined values |
| [n]: |
| 0 turn off automatic response for Packet Domain only |
| 1 turn on automatic response for Packet Domain only |
| 2 modem compatibility mode, Packet Domain only |
| 3 modem compatibility mode, Packet Domain and circuit switched calls (default) |
| For [n] = 0 Packet DomainS network requests are manually accepted or rejected by the +CGANS command. |
| For [n] = 1 Packet Domain network requests are automatically accepted according to the description above. |
| For [n] = 2, automatic acceptance of Packet Domain network requests is controlled by the 'S0' command. Manual control uses the 'A' and 'H' commands, respectively, to accept and reject Packet Domain requests. (+CGANS may also be used.) Incoming circuit switched calls can be neither manually nor automatically answered. |
| For [n] = 3, automatic acceptance of both Packet Domain network requests and incoming circuit switched calls is controlled by the 'S0' command. Manual control uses the 'A' and 'H' commands, respectively, to accept and reject Packet Domain requests. (+CGANS may also be used.) Circuit switched calls are handled as described elsewhere in this specification. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CGAUTO=?</command> |
| <profile>Automatic response to a network request for PDP context activation (Query all)</profile> |
| <description>The set command disables or enables an automatic positive response (auto-answer) to the receipt of a Request PDP Context Activation message from the network. It also provides control over the use of the V.250 basic commands 'S0', 'A and 'H' for handling network requests for PDP context activation. The setting does not affect the issuing of the unsolicited result code RING or +CRING. |
| The test command returns the values of [n] supported by the MT as a compound value. |
| When the +CGAUTO=0 command is received, the MT shall not perform a PS detach if it is attached. Subsequently, when the MT announces a network request for PDP context activation by issuing the unsolicited result code RING or +CRING, the TE may manually accept or reject the request by issuing the +CGANS command or may simply ignore the network request. |
| When the +CGAUTO=1 command is received, the MT shall attempt to perform a PS attach if it is not already attached. Failure will result in ERROR or, if enabled, +CME ERROR being returned to the TE. Subsequently, when the MT announces a network request for PDP context activation by issuing the unsolicited result code RING or +CRING to the TE, this is followed by the intermediate result code CONNECT. The MT then enters V.250 online data state and follows the same procedure as it would after having received a +CGANS=1 with no [L2P] or [cid] values specified. |
| Defined values |
| [n]: |
| 0 turn off automatic response for Packet Domain only |
| 1 turn on automatic response for Packet Domain only |
| 2 modem compatibility mode, Packet Domain only |
| 3 modem compatibility mode, Packet Domain and circuit switched calls (default) |
| For [n] = 0 Packet DomainS network requests are manually accepted or rejected by the +CGANS command. |
| For [n] = 1 Packet Domain network requests are automatically accepted according to the description above. |
| For [n] = 2, automatic acceptance of Packet Domain network requests is controlled by the 'S0' command. Manual control uses the 'A' and 'H' commands, respectively, to accept and reject Packet Domain requests. (+CGANS may also be used.) Incoming circuit switched calls can be neither manually nor automatically answered. |
| For [n] = 3, automatic acceptance of both Packet Domain network requests and incoming circuit switched calls is controlled by the 'S0' command. Manual control uses the 'A' and 'H' commands, respectively, to accept and reject Packet Domain requests. (+CGANS may also be used.) Circuit switched calls are handled as described elsewhere in this specification. |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CGANS=</command> |
| <profile>Manual response to a network request for PDP context activation (Assign)</profile> |
| <description>The execution command requests the MT to respond to a network request for Packet Domain PDP context activation which has been signalled to the TE by the RING or +CRING: unsolicited result code. The [response] parameter allows the TE to accept or reject the request. |
| If [response] is 0, the request is rejected and the MT returns OK to the TE. |
| If [response] is 1, the following procedure is followed by the MT. |
| Commands following the +CGANS command in the AT command line shall not be processed by the MT. |
| If the [L2P] parameter value is unacceptable to the MT, the MT shall return an ERROR or +CME ERROR response. Otherwise, the MT issues the intermediate result code CONNECT and enters V.250 online data state. |
| The detailed behaviour after the online data state has been entered is dependent on the PDP type. It is described briefly in 3GPP TS 27.060[34] and in more detail in 3GPP TS 29.061[39] and the specifications for the relevant PDPs. PDP context activation procedures shall take place prior to or during the PDP startup. |
| One or more [cid]s may be specified in order to provide the values needed for the context activation request. |
| During the PDP startup procedure the MT has the PDP type and the PDP address provided by the network in the Request PDP Context Activation message. The MT may also have some or all of the following information - |
| The MT may have a priori knowledge, for example, it may implement only one PDP type. |
| The command may have provided an [L2P] parameter value. |
| The TE may provide one or both of PDP type and PDP address to the MT in the PDP startup. |
| If any of this information is in conflict, the command will fail. |
| If one or more [cid] is given then an attempt shall be made to identify an appropriate context definition by matching the PDP type and PDP address in the network request with the PDP type and PDP address in each of the specified context definitions (in the order in which their [cid]s appear in the command) as follows - |
| The PDP type must match exactly. |
| The PDP addresses are considered to match if they are identical or if the address in the context definition is unspecified. |
| The context shall be activated using the values for PDP type and PDP address provided by the network, together with the other information found in the PDP context definition. An APN may or may not re required, depending on the application. |
| If no [cid] is given or if there is no matching context definition, the MT will attempt to activate the context using the values for PDP type and PDP address provided by the network, together with any other relevant information known to the MT. The other context parameters will be set to their default values. |
| If the activation is successful, data transfer may proceed. |
| After data transfer is complete, and the layer 2 protocol termination procedure has completed successfully, the V.250 command state is re-entered and the MT returns the final result code OK |
| In the event of an erroneous termination or a failure to startup, the V.250 command state is re-entered and the MT returns the final result code NO CARRIER or, if enabled, +CME ERROR. Attach, activate and other errors may be reported. It is also an error to issue the +CGANS command when there is no outstanding network request. |
| NOTE: This is not the same as if the MT issues a +CGDATA (or +CGACT) command after receiving a +CRING unsolicited result code. A +CGDATA (or +CGACT) does not command the MT to acknowledge the network request but rather to make a new request for context activation. The network request would be ignored. |
| The test command returns the values of [response] and [L2P] supported by the MT as compound values. |
| This command may be used in both normal and modem compatibility modes. |
| Defined values |
| [response]: is a numeric parameter which specifies how the request should be responded to. |
| 0 reject the request |
| 1 accept and request that the PDP context be activated |
| If [response] is omitted it is assumed to be 0. Other values are reserved and will result in the ERROR response. |
| [L2P]: a string parameter which indicates the layer 2 protocol to be used (see +CGDATA command). |
| [cid]: a numeric parameter which specifies a particular PDP context definition (see the +CGDCONT and +CGDSCONT commands). |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CGANS=?</command> |
| <profile>Manual response to a network request for PDP context activation (Query all)</profile> |
| <description>The execution command requests the MT to respond to a network request for Packet Domain PDP context activation which has been signalled to the TE by the RING or +CRING: unsolicited result code. The [response] parameter allows the TE to accept or reject the request. |
| If [response] is 0, the request is rejected and the MT returns OK to the TE. |
| If [response] is 1, the following procedure is followed by the MT. |
| Commands following the +CGANS command in the AT command line shall not be processed by the MT. |
| If the [L2P] parameter value is unacceptable to the MT, the MT shall return an ERROR or +CME ERROR response. Otherwise, the MT issues the intermediate result code CONNECT and enters V.250 online data state. |
| The detailed behaviour after the online data state has been entered is dependent on the PDP type. It is described briefly in 3GPP TS 27.060[34] and in more detail in 3GPP TS 29.061[39] and the specifications for the relevant PDPs. PDP context activation procedures shall take place prior to or during the PDP startup. |
| One or more [cid]s may be specified in order to provide the values needed for the context activation request. |
| During the PDP startup procedure the MT has the PDP type and the PDP address provided by the network in the Request PDP Context Activation message. The MT may also have some or all of the following information - |
| The MT may have a priori knowledge, for example, it may implement only one PDP type. |
| The command may have provided an [L2P] parameter value. |
| The TE may provide one or both of PDP type and PDP address to the MT in the PDP startup. |
| If any of this information is in conflict, the command will fail. |
| If one or more [cid] is given then an attempt shall be made to identify an appropriate context definition by matching the PDP type and PDP address in the network request with the PDP type and PDP address in each of the specified context definitions (in the order in which their [cid]s appear in the command) as follows - |
| The PDP type must match exactly. |
| The PDP addresses are considered to match if they are identical or if the address in the context definition is unspecified. |
| The context shall be activated using the values for PDP type and PDP address provided by the network, together with the other information found in the PDP context definition. An APN may or may not re required, depending on the application. |
| If no [cid] is given or if there is no matching context definition, the MT will attempt to activate the context using the values for PDP type and PDP address provided by the network, together with any other relevant information known to the MT. The other context parameters will be set to their default values. |
| If the activation is successful, data transfer may proceed. |
| After data transfer is complete, and the layer 2 protocol termination procedure has completed successfully, the V.250 command state is re-entered and the MT returns the final result code OK |
| In the event of an erroneous termination or a failure to startup, the V.250 command state is re-entered and the MT returns the final result code NO CARRIER or, if enabled, +CME ERROR. Attach, activate and other errors may be reported. It is also an error to issue the +CGANS command when there is no outstanding network request. |
| NOTE: This is not the same as if the MT issues a +CGDATA (or +CGACT) command after receiving a +CRING unsolicited result code. A +CGDATA (or +CGACT) does not command the MT to acknowledge the network request but rather to make a new request for context activation. The network request would be ignored. |
| The test command returns the values of [response] and [L2P] supported by the MT as compound values. |
| This command may be used in both normal and modem compatibility modes. |
| Defined values |
| [response]: is a numeric parameter which specifies how the request should be responded to. |
| 0 reject the request |
| 1 accept and request that the PDP context be activated |
| If [response] is omitted it is assumed to be 0. Other values are reserved and will result in the ERROR response. |
| [L2P]: a string parameter which indicates the layer 2 protocol to be used (see +CGDATA command). |
| [cid]: a numeric parameter which specifies a particular PDP context definition (see the +CGDCONT and +CGDSCONT commands). |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CGCS=</command> |
| <profile>VGCS subscriptions and GId status (Assign)</profile> |
| <description>This command works with SIM Card and when the GSM Application is selected in UICC. Function with USIM is for further study. The set command is used to edit the status of the GId EFVGCSS on the SIM. The read command returns all subscribed GIds in EFVGCS and their status in EFVGCSS from the SIM. |
| |
| Defined values |
| [GId] integer type, group Id as specified in 3GPP TS 22.030 [19] |
| [status]: integer type, value |
| 0 deactivated |
| 1 activated |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CGCS?</command> |
| <profile>VGCS subscriptions and GId status (Query)</profile> |
| <description>This command works with SIM Card and when the GSM Application is selected in UICC. Function with USIM is for further study. The set command is used to edit the status of the GId EFVGCSS on the SIM. The read command returns all subscribed GIds in EFVGCS and their status in EFVGCSS from the SIM. |
| |
| Defined values |
| [GId] integer type, group Id as specified in 3GPP TS 22.030 [19] |
| [status]: integer type, value |
| 0 deactivated |
| 1 activated |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CGCS=?</command> |
| <profile>VGCS subscriptions and GId status (Query all)</profile> |
| <description>This command works with SIM Card and when the GSM Application is selected in UICC. Function with USIM is for further study. The set command is used to edit the status of the GId EFVGCSS on the SIM. The read command returns all subscribed GIds in EFVGCS and their status in EFVGCSS from the SIM. |
| |
| Defined values |
| [GId] integer type, group Id as specified in 3GPP TS 22.030 [19] |
| [status]: integer type, value |
| 0 deactivated |
| 1 activated |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CBCS=</command> |
| <profile>VBS subscriptions and GId status (Assign)</profile> |
| <description>This command works with SIM Card and when the GSM Application is selected in UICC. Function with USIM is for further study. The set command is used to edit the status of the GId EFVBSS on the SIM. The read command returns all subscribed GIds in EFVBS and their status in EFVBSS from the SIM. |
| |
| Defined values |
| [GId] integer type, group Id as specified in 3GPP TS 22.030 [19] |
| [status]: integer type, value |
| 0 deactivated |
| 1 activated |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CBCS?</command> |
| <profile>VBS subscriptions and GId status (Query)</profile> |
| <description>This command works with SIM Card and when the GSM Application is selected in UICC. Function with USIM is for further study. The set command is used to edit the status of the GId EFVBSS on the SIM. The read command returns all subscribed GIds in EFVBS and their status in EFVBSS from the SIM. |
| |
| Defined values |
| [GId] integer type, group Id as specified in 3GPP TS 22.030 [19] |
| [status]: integer type, value |
| 0 deactivated |
| 1 activated |
| </description> |
| </spec> |
| <spec> |
| <command>AT+CBCS=?</command> |
| <profile>VBS subscriptions and GId status (Query all)</profile> |
| <description>This command works with SIM Card and when the GSM Application is selected in UICC. Function with USIM is for further study. The set command is used to edit the status of the GId EFVBSS on the SIM. The read command returns all subscribed GIds in EFVBS and their status in EFVBSS from the SIM. |
| |
| Defined values |
| [GId] integer type, group Id as specified in 3GPP TS 22.030 [19] |
| [status]: integer type, value |
| 0 deactivated |
| 1 activated |
| </description> |
| </spec> |
| </gsm> |
