FIBOCOM AT Commands

User Manual For L850

X Reproduction forbidden without Fibocom Wireless Inc. written authorization – All Rights Reserved.
L8-Family AT Commands User Manual Page 1 of 165
Copyright
Copyright ©2019 Fibocom Wireless Inc. All rights reserved.

Without the prior written permission of the copyright holder, any company or individual is prohibited to
excerpt, copy any part of or the entire document, or transmit the document in any form.

Attention
The document is subject to update from time to time owing to the product version upgrade or other
reasons. Unless otherwise specified, the document only serves as the user guide. All the statements,
information and suggestions contained in the document do not constitute any explicit or implicit
guarantee.

Trademark
The trademark is registered and owned by Fibocom Wireless Inc.

Versions
Version Author Date Remarks
V1.0 yanghaitao 2019-02-18 Initial version

V1.1 Yanghaitao 2019-02-23 Some commands do not support test commands. eg:ATE.

Applicability Type
No. Type Note

Page 2 of 165
Contents
1 Preface............................................................................................................................... 8
1.1 Manual Scope ...................................................................................................................... 8
1.2 Target Audience ................................................................................................................... 8
2 Introduction to AT Commands ........................................................................................ 8
2.1 AT Commands Overview ...................................................................................................... 8
2.2 General System Abbreviations ............................................................................................. 8
2.3 AT Commands Protocol ........................................................................................................ 9
2.4 AT Commands Structure .................................................................................................... 10
2.4.1 General Symbols Used in AT Commands Description........................................................10
2.4.2 Command Structure ............................................................................................................10
2.4.3 Results Code Structure ....................................................................................................... 11
2.5 Command Syntax............................................................................................................... 11
3 Modem Information ........................................................................................................ 12
3.1 General information ............................................................................................................ 12
3.1.1 +CGMI, Request Manufacturer ID .......................................................................................12
3.1.2 +GMI, Request Manufacturer ID .........................................................................................12
3.1.3 +CGMM, Request Model ID ................................................................................................13
3.1.4 +GMM, Request Model ID ...................................................................................................14
3.1.5 +CGMR, Request Revision .................................................................................................14
3.1.6 +GMR, Request Revision ....................................................................................................15
3.1.7 +CGSN, Request Product Serial Number Identification .....................................................16
3.1.8 +GSN, Request Product Serial Number Identification ........................................................17
3.1.9 +CFSN, Request Factory Serial Number ............................................................................18
3.1.10 +CIMI, Request IMSI .........................................................................................................18
3.1.11 +CNUM, Request MSISDN(s) ...........................................................................................19
3.1.12 +CCID Request Integrate Circuit Card Identity .................................................................20
3.1.13 +CLAC, List of All Available AT Commands ......................................................................21
4 Modem Control and Status ............................................................................................ 22
4.1 Modem control Commands ................................................................................................ 22
4.1.1 V, Modem Response Format ...............................................................................................22
4.1.2 Q, Result Code Suppression ...............................................................................................23
4.1.3 E, Command Echo...............................................................................................................24

Page 3 of 165
 4.1.4 X, Result Code Selection and Call Progress Monitoring Control ........................................25
4.1.5 S, Bit Map Registers ............................................................................................................26
4.1.6 &F, Set to Factory Defined Configuration ............................................................................27
4.1.7 Z, Reset to User Profile .......................................................................................................27
4.1.8 +CBC, Battery Charger Connection ....................................................................................28
4.1.9 +MTSM, Temperature Sensor Measurement ......................................................................29
4.1.10 +MSMPD, Enable/Disable SIM card hot plug ...................................................................30
4.1.11 +CMUX, MUX Start up Command .....................................................................................31
4.1.12 +CPWROFF Switch off MS ...............................................................................................33
4.1.13 +CFUN, Set Phone Functionality ......................................................................................33
4.1.14 +MSTART, Start message notification ...............................................................................35
5 Phone Book and Clock................................................................................................... 36
5.1 Directory Access Commands - Phone Book ....................................................................... 36
5.1.1 +CPBS, Select Phone Book Memory ..................................................................................36
5.1.2 +CPBR, Read Phone Book Entries .....................................................................................38
5.1.3 +CPBF, Find Phone Book Entries .......................................................................................39
5.1.4 +CPBW, Write Phone Book Entry .......................................................................................41
6 System Date and Time Access Commands .................................................................. 43
6.1 General command.............................................................................................................. 43
6.1.1 +CCLK, Read/Set System Date and Time ..........................................................................43
6.1.2 +CTZU, Automatic Time Zone Update ................................................................................44
6.1.3 +CTZR, Time Zone Reporting .............................................................................................45
7 SMS .................................................................................................................................. 46
7.1 SMS Commands ................................................................................................................ 46
7.1.1 +CSCS, Select Terminal Character Set ..............................................................................46
7.1.2 +CSMS, Select Message Service .......................................................................................47
7.1.3 +CPMS, Preferred Message Storage..................................................................................48
7.1.4 +CMGF, Message Format ...................................................................................................49
7.1.5 +CSCA, Service Center Address ........................................................................................50
7.1.6 +CSMP, Set Text Mode Parameters ....................................................................................52
7.1.7 +CSDH, Show Text Mode Parameters ................................................................................53
7.1.8 +CNMI, New Message Indications to Terminal ...................................................................54
7.1.9 +CNMA, New Message Acknowledgment ..........................................................................57
7.1.10 +CMGL, List Messages .....................................................................................................59

Page 4 of 165
 7.1.11 +CMGR, Read Message....................................................................................................61
7.1.12 +CMSS, Send Message from Storage ..............................................................................63
7.1.13 +CMGW, Write Message to Memory.................................................................................64
7.1.14 +CMGD, Delete Message .................................................................................................65
7.1.15 +CGSMS, Select Service for MO SMS Messages............................................................66
7.1.16 +CMGS, Send SMS to Network ........................................................................................67
7.1.17 +CSCB, Cell Broadcast Messages ...................................................................................68
7.1.18 +CSVM, Set Voice Mail Server .........................................................................................69
8 SIM TOOL KIT Raw Mode Commands........................................................................... 70
8.1 Raw Mode Commands Lists............................................................................................... 70
8.1.1 +CUSATR, Read USAT Profile ............................................................................................70
8.1.2 CUSATW, Write USAT Profile .............................................................................................71
8.1.3 +CUSATD, Profile download upon start-up .........................................................................72
8.1.4 +CUSATA, Activate USAT profile ........................................................................................74
8.1.5 +CUSATT, Send USAT terminal response ..........................................................................76
8.1.6 +CUSATE, Send USAT envelope command .......................................................................77
8.1.7 +STKPROF, Reading and changing the terminal profile .....................................................77
9 Access and security ....................................................................................................... 78
9.1 Commands......................................................................................................................... 78
9.1.1 A/, Repeat Last Command ..................................................................................................78
9.1.2 AT, Check AT Communication .............................................................................................79
9.1.3 +CPIN, Enter PIN for Unlocking SIM or Enter PUK for Unblocking SIM ............................79
9.1.4 +TPIN, Query Number of Remaining SIM PIN/PUK Entering Attempts .............................82
9.1.5 +CPWD, Change Password ................................................................................................82
9.1.6 +CLCK, Facility Lock ...........................................................................................................84
9.1.7 +CPINR, Remaining PIN Retries.........................................................................................86
9.1.8 +CSIM, Generic SIM Access ...............................................................................................87
9.1.9 +CRSM, Restricted SIM Access..........................................................................................88
10 Network ......................................................................................................................... 90
10.1 Network Commands ......................................................................................................... 90
10.1.1 +CSQ, Signal Strength ......................................................................................................90
10.1.2 +CESQ, Extended Signal Quality ......................................................................................91
10.1.3 +CRLP, Radio Link Protocol ..............................................................................................93
10.1.4 +CREG, Network Registration Status ...............................................................................94

Page 5 of 165
 10.1.5 +CGREG, GPRS Network Registration ............................................................................96
10.1.6 +CEREG, EPS Network Registration status .....................................................................99
10.1.7 +WS46, Select Wireless Network .................................................................................. 101
10.1.8 +COPS, Operator Selection ........................................................................................... 102
10.1.9 +CPLS, Selection of Preferred PLMN List ..................................................................... 104
10.1.10 +CPOL, Preferred Operators........................................................................................ 105
10.1.11 +COPN, Read Operator Names ................................................................................... 106
10.1.12 +CEMODE, UE modes of operation for EPS ............................................................... 107
11 Hardware Information ................................................................................................. 108
11.1 UART Parameter Commands ......................................................................................... 108
11.1.1 +IPR, Fixed DTE Rate .................................................................................................... 108
11.1.2 &C, Circuit 109 Behavior ................................................................................................ 109
11.1.3 &D, Circuit 108 (Data Terminal Ready) behaviour .......................................................... 110
11.2 Clock Configuration ......................................................................................................... 111
11.2.1 +CLK26M, 26MHz Clock Output From CLK26M ............................................................. 111
12 GPRS ........................................................................................................................... 112
12.1 GPRS Functionality ........................................................................................................ 112
12.2 GPRS Commands .......................................................................................................... 113
12.2.1 +CGCLASS, GPRS Mobile Station Class ....................................................................... 113
12.2.2 +CGDCONT, Define PDP Context .................................................................................. 114
12.2.3 +CGQMIN, Quality of Service Profile (Min Acceptable) .................................................. 117
12.2.4 +CGQREQ, Quality of Service Profile (Requested) ........................................................ 119
12.2.5 +CGATT, Packet Domain Attach or Detach ................................................................... 120
12.2.6 D*99, Request GPRS Service "D" .................................................................................. 121
12.2.7 +CGACT, PDP Context Activate or Deactivate .............................................................. 122
12.2.8 +CGPADDR, GPRS Addresses...................................................................................... 124
12.2.9 +CGANS, Manual response to a network request for PDP context activation .............. 125
12.2.10 +CGAUTO, Automatic Response to a Network Request for PDP Context Activation . 125
12.2.11 +CGEQMIN，3G Quality of Service Profile (Minimum acceptable) ............................ 127
12.2.12 +CGEQREQ，3G Quality of Service Profile (Requested) ........................................... 130
12.2.13 +CGEQNEG，3G Quality of Service Profile (Negotiated) ........................................... 134
12.2.14 +CGCMOD，PDP Context Modify ............................................................................... 136
12.2.15 +CGDATA，Enter Data State....................................................................................... 137
12.2.16 +CGDSCONT，Define Secondary PDP Context ........................................................ 138

Page 6 of 165
 12.2.17 +CGEREP，Packet Domain Event Reporting ............................................................. 140
12.2.18 +CGTFT Traffic Flow Template .................................................................................... 142
12.2.19 +CGPIAF , Printing IP Address Format ........................................................................ 144
12.2.20 +CGCONTRDP, PDP Context Read Dynamic Parameters ......................................... 146
12.2.21 +CGSCONTRDP, Secondary PDP Context Read Dynamic Parameters .................... 148
12.2.22 +CGTFTRDP, Traffic Flow Template Read Dynamic Parameters ............................... 149
12.2.23 +CSCON, Signalling Connection Status ...................................................................... 151
12.2.24 +CGEQOS, Define EPS Quality Of Service ................................................................. 153
13 Fibocom Proprietary Commands .............................................................................. 154
13.1 Set Profile Commands ................................................................................................... 154
13.1.1 +GTUSBMODE, Set USB Configuration Profile ............................................................ 154
14 Error Handing and Error Code................................................................................... 156
14.1 Error Handling Commands ............................................................................................. 156
14.1.1 +CMEE, Report Mobile Equipment Error ....................................................................... 156
14.1.2 +CEER, Extended Error Report ..................................................................................... 157
14.2 CME Error ...................................................................................................................... 158
14.3 CMS Error ...................................................................................................................... 162

Page 7 of 165
1 Preface
1.1 Manual Scope

This manual introduces the AT commands of Fibocom’s product L850-GL, and describes how the users
can communicate with the devices using these commands. It describes the specification of syntax and
parameters of the listed AT commands.

1.2 Target Audience

This manual is intended for the developers who need to communicate with the L850-GL devices using the
AT commands.

2 Introduction to AT Commands
2.1 AT Commands Overview

AT commands are sets of commands used for communication with the cellular modem. AT commands are
comprised of assemblies of ASCII characters which start with the "AT" prefix (except the commands A/
and +++). The AT prefix is derived from the word Attention, which asks The modem to pay attention to the
current request (command).
AT commands are used to request services from the cellular modem, such as:
 Call services: dial, answer and hang up
 Cellular utilities: send/receive SMS
 Modem profiles: Auto Answer
 Cellular Network queries: GSM signal quality

2.2 General System Abbreviations

The basic system configuration contains a modem and a terminal.

The Fibocom family is the modem unit and may be referred to as the DCE or TA, such as the phone, the
mobile or the radio.
The terminal (PC or MCU) may be referred to as the DTE or the TE.

Page 8 of 165
2.3 AT Commands Protocol
The AT commands interface is basically a Modem Services upon Request.
Communication (almost) always begins from the TE side. This means that any service should be
requested from the TE. Thus a request is called a "Command".
Each command must be answered by a "Results code" from the TA. The results code reports the
command status to the TE. Some commands may include several "Results code" to send data back to the
TE. Some commands may initiate a mode in which, when specified events are generated in the modem,
"Indicator" messages are sent data asynchronously. The “indicators” can be called “Unsolicited results
code”.
The Modem can echo characters received from the TE (commands) back to the TE.

TE TA
Command

Results code

TE TA
Command

Results code

TE TA

Unsolicited results code

Page 9 of 165
2.4 AT Commands Structure
2.4.1General Symbols Used in AT Commands Description
The following syntax definitions apply in this chapter:

Syntax Definition

<CR> Carriage returns character, specified by the value of the S3-register.

<LF> Line-feed character, specified by the value of the S4-register.

<…> Name enclosed in angle brackets is a syntax element. The brackets themselves
do not appear in the command line.

[...] Optional sub-parameter of a command or an optional part of terminal information

response, enclosed in square brackets. The brackets themselves do not appear
in the command line. When the sub-parameter is not provided in the parameter
type commands, the new value equals its previous value. In action type
commands, the action should be performed on the basis of the recommended
default setting of the sub-parameter.

// Denotes a comment, and should not be included in the command.

2.4.2Command Structure
Each AT command has the "AT" or “at” prefix string (except the commands A/ and +++).
Each AT command has the suffix <CR> (except the commands A/ and +++).
Example:

AT+CSQ<CR>
ATS24?<CR>
An AT command line may contain one or more commands. Delimiters are used to separate the
commands from each other. The delimiter is either a semicolon ";" or none, meaning space (basic
commands).
Example:

ATS0=1V1Q0E0<CR>
AT+IFC=0,0;+ICF=3,4;+CNMI=2,1,0,0,0<CR>

Page 10 of 165
 2.4.3Results Code Structure
By default, the Modem responds with verbose response codes. The results code prefix is <CR><LF>. The
results code suffix is <CR><LF>.
Example:

<CR><LF>+CSQ: 99,99<CR><LF>
<CR><LF>OK<CR><LF>

The unsolicited results code is same as the Results code.

Note:
 The <CR> and <LF> characters are not explicitly presented in the response format in this
document.
 To reduce the print length the empty line in actual response may be removed in the
examples.

2.5 Command Syntax

Execute command syntax AT+xxx
ATxxx
ATxxx;
Parameter set command syntax AT+xxx=<Value>
ATxxx=<Value>
Parameter read Command syntax AT+xxx?
ATxxx?
Parameter test Command syntax AT+xxx=?
ATxxx=?
<Value> consists of either a numeric constant or a string constant. <compound_value> consist of several
<value> parameters separated by commas.
Example of compound_value: <value1>, <value2>,…,<valueN>
 Numeric Constants
Numeric constants are expressed in decimal, hexadecimal, or binary form. In the Modem, the definition
of each command specifies which form is used for values associated with that command.
 String Constants
String constants consist of a sequence of characters, bounded at the beginning and end by the
double-quote character (").

Page 11 of 165
3 Modem Information
These commands allow user to query the type of device that is attached, the technology used in the
device, as well as basic operating information about the modem unit.

3.1 General information

3.1.1 +CGMI, Request Manufacturer ID

Description

This command displays the manufacturer identification. The modem unit outputs a string containing
manufacturer identification information

Syntax

Command Possible response(s)

+CGMI +CGMI: "<manufacturer>"

OK

+CGMI? +CGMI: "<manufacturer>"

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<manufacturer>: string type;

3.1.2+GMI, Request Manufacturer ID

Description

This command displays manufacturer identification. The modem unit outputs a string containing
manufacturer identification information.

Page 12 of 165
Syntax

Command Possible response(s)

+GMI +GMI: "<manufacturer>"
OK

+GMI? +GMI: "<manufacturer>"

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<manufacturer>: string type;

3.1.3+CGMM, Request Model ID

Description

This command requests the model identification. The modem outputs a string containing information
about the specific model, including a list of the supported technology used, and the particular model
number.

Syntax

Command Possible response(s)

+CGMM +CGMM: "<model>","<model abrev>"

OK

+CGMM? +CGMM: "<model>","<model abrev>"

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Page 13 of 165
Defined Values

<model>: string type;

<model abrev>: string type;

3.1.4+GMM, Request Model ID

Description

This command requests the model identification. The modem outputs a string containing information
about the specific model, including a list of the supported technology used, and the particular model
number.

Syntax

Command Possible response(s)

+GMM +GMM: "<model>","<model abrev>"

OK

+GMM? +GMM: "<model>","<model abrev>"

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<model>: string type;

<model abrev>: string type;

3.1.5+CGMR, Request Revision

Description

This command requests the revision identification. The modem outputs a string containing the revision

Page 14 of 165
identification information of the software running in the device.

Syntax

Command Possible response(s)

+CGMR +CGMR: "<revision>"
OK

+CGMR? +CGMR: "<revision>"

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<revision>: string type;

3.1.6+GMR, Request Revision

Description

These commands request the revision identification. The modem outputs a string containing the revision
identification information of the software version contained within the device.

Syntax

Command Possible response(s)

+GMR +GMR: "<revision>"
OK

+GMR? +GMR: "<revision>"

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Page 15 of 165
 No No Yes Yes < 1s

Defined Values

<revision>: string type;

3.1.7+CGSN, Request Product Serial Number Identification

Description

This command displays the product serial number identification IMEI (International Mobile Equipment
Identification). It can be used even when the SIM card is not inserted.

Syntax

Command Possible response(s)

+CGSN[=<snt>] When <snt>=0 (or omitted) and command successful:

<imei>
When <snt>=1 and command successful:

+CGSN: "<imei>"

When <snt>=2 and command successful:

+CGSN: "<imeisv>"

When <snt>=3 and command successful:

+CGSN: "<svn>"
Or

+CME ERROR: <err>

+CGSN? +CGSN: "<imei>"

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values
<snt>: integer type indicating the serial number type that has been requested.
0 returns the IMEI (International Mobile station Equipment Identity)
1 returns the IMEI (International Mobile station Equipment Identity)

Page 16 of 165
 2 returns the IMEISV (International Mobile station Equipment Identity and Software Version number)
3 returns the SVN (Software Version Number)
<imei>: string type in decimal format indicating the IMEI; IMEI is composed of Type Allocation Code (TAC) (8
digits), Serial Number (SNR) (6 digits) and the Check Digit (CD) (1 digit). Character set used in <imei> is as
specified by command Select TE Character Set +CSCS.

<imeisv>: string type in decimal format indicating the IMEISV; The 16 digits of IMEISV are composed of Type
Allocation Code (TAC) (8 digits), Serial Number (SNR) (6 digits) and the software version (SVN) (2 digits).

<svn>: string type in decimal format indicating the current SVN which is a part of IMEISV; This allows identifying
different software versions of a given mobile.

3.1.8+GSN, Request Product Serial Number Identification

Description

This command displays the product serial number identification IMEI (International Mobile Equipment
Identification). It can be used even when the SIM card is not inserted.

Syntax

Command Possible response(s)

+GSN +GSN: "<imei>"

OK

+GSN? +GSN: "<imei>"

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<imei>: string type in decimal format indicating the IMEI; IMEI is composed of Type Allocation Code (TAC) (8 digits),
Serial Number (SNR) (6 digits) and the Check Digit (CD) (1 digit). Character set used in <imei> is as specified by
command Select TE Character Set +CSCS.

Page 17 of 165
 3.1.9+CFSN, Request Factory Serial Number
Description

This command is used to read the factory serial number.

Syntax

Command Possible response(s)

+CFSN
+CFSN: "<FSN>"

OK

or

ERROR

+CFSN?
+CFSN: "<FSN>"

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No Yes Yes Yes < 1s

Defined Values

<FSN>: string type with 10-char string that can be <A-Z> or <0-9> characters or both; e,g. "1234567890"

3.1.10+CIMI, Request IMSI

Description

This command displays the International Mobile Subscriber Identity number.

Syntax

Command Possible response(s)

+CIMI <IMSI>
OK
or:

Page 18 of 165
 ERROR
+CIMI? +CIMI: <IMSI>
OK
or:

ERROR

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes < 1s

Defined Values

<IMSI>: string type; International Mobile Subscriber Identity (string without double quotes); e,g. 314566320021400

3.1.11+CNUM, Request MSISDN(s)

Description

This command displays up to 2 strings of text information that identify the modem. The output string
contains double quotes.On SIM cards that have EFmsisdn file, the string(s) returned are the MSISDN
numbers and their associated data.On SIM cards that don't have EFmsisdn file, the strings returned are
the MSISDN numbers and their associated data stored in Modem NVM.

Syntax

Command Possible response(s)

+CNUM +CNUM: [<alpha1>],<number1>,<type1>[,<speed>,<service>[,<itc>]]

[<CR><LF>+CNUM: [<alpha2>],<number2>,<type2>[,<speed>,<service>[,<itc>]]
[...]]
or
ERROR
+CNUM=? OK

Page 19 of 165
Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes < 1s

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>; e,g, 19912345011
<typex>: integer type;
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 3GPP TS 24.008 subclause 10.5.4.7
<speed>: integer type, same as <speed> defined in CBST commands

<service>: integer type (service related to the phone number)

0 asynchronous modem

1 synchronous modem

2 PAD Access (asynchronous)

3 Packet Access (synchronous)

4 voice

5 fax
all other values below 128 are reserved by the present document
<itc>: integer type (information transfer capability)

0 3,1 kHz

1 UDI

3.1.12 +CCID Request Integrate Circuit Card Identity

Description

This command returns the card identification number in SIM (SIM file EFICCID, see GSM 11.11
Chap.10.1.1) as string type.

Page 20 of 165
Syntax
Command Possible response(s)

+CCID +CCID: <ID>

OK
or
ERROR
+CCID? +CCID: <ID>
OK
or
ERROR
+CCID=? OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<ID>: string type; e,g, 89860018190839008096

3.1.13+CLAC, List of All Available AT Commands

Description

This command prints out all AT Commands supported by the Modem.

Syntax

Command Possible response(s)

+CLAC <ATx>
OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 2s

Page 21 of 165
Defined Values

<ATx>: string type and to list available AT commands; e,g ATS or ATD or ATA and so on

4 Modem Control and Status

4.1 Modem control Commands
The modem holds certain data items in selected memory space, named Software Registers (S-registers)
and Modem Registers. Some of these registers are used as bitmaps, where one register holds more than
one data item.All S-registers can be accessed using the S command, described in “S, Bit Map Registers”.
Some registers can also be accessed using dedicated commands, detailed below.

4.1.1 V, Modem Response Format

Description

This command determines the response format of the data adapter and the contents of the header and
trailer transmitted with the result codes and information responses. This command also determines
whether the result codes are transmitted in a numeric or an alphabetic ("verbose") form. The text portion
of information responses is not affected by this setting.
The following table shows the effect that setting this parameter has on the format of information text and
result codes.

Syntax

Command Possible response(s)

ATV[<value>] If <value>=0:

<numeric code>
or

If <value>=1 or without parameter:

<verbose code>

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Page 22 of 165
 No No Yes Yes < 1s

Defined Values

<value>: integer type

0 Transmits limited headers and trailers, and numeric text.
1Transmits full headers and trailers, and verbose response text. Default value.
<numeric code>: integer type
0 OK
1 CONNECT
2 RING
3 NO CARRIER
4 ERROR
5 RESERVED
6 NO DIALTONE
7 BUSY
8 NO ANSWER
<verbose code>: string type; And supported verbose code as below:
OK
CONNECT
RING
NO CARRIER
ERROR
RESERVED
NO DIALTONE
BUSY
NO ANSWER

4.1.2 Q, Result Code Suppression

Description

This command determines whether to output the result codes. Information text transmitted in response to
commands is not affected by the setting of this parameter.

Syntax

Command Possible response(s)

ATQ[<value>] OK

Page 23 of 165
 Command Possible response(s)

or:
+CME ERROR: <err>
Or
No result return if <value>=1

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<value>: integer type

0 Transmit result codes. Default value.
1 Suppress result codes.

4.1.3 E, Command Echo

Description

This command defines whether input characters are echoed to output. If so, these characters are echoed
at the same rate, parity and format at which they were received.

Syntax

Command Possible response(s)

ATE<n> OK
or:
+CME ERROR: <err>

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Page 24 of 165
Defined Values

<n>: integer type

0 Does not echo characters
1 Echoes characters
Note: if without parameter, it means n=0.

4.1.4 X, Result Code Selection and Call Progress Monitoring

Control
Description

This command defines the CONNECT result code format. It determines whether or not the Modem
transmits particular result codes to the user. It also controls whether the Modem verifies the presence of
dial tone when it first goes off-hook to begin dialing, and whether the engaged tone (busy signal) detection
is enabled.

Syntax

Command Possible response(s)

ATX<n> OK

or:

+CME ERROR: <err>

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<n>: integer type;

0 CONNECT result code given upon entering online data state:

Dial tone detection - Disabled

Busy detection - Disabled

1 CONNECT <text> result code given upon entering online data state:
Dial tone detection - Disabled

Busy detection - Disabled

Page 25 of 165
 2 CONNECT <text> result code given upon entering online data state:

Dial tone detection - Enabled

Busy detection - Disabled

3 CONNECT<text> result code given upon entering online data state:

Dial tone detection - Disabled

Busy detection - Enabled

4 CONNECT <text> result code given upon entering online data state;Default value.

Dial tone detection - Enabled

Busy detection – Enabled

<text>: string type and it is manufacturer-specific text that may specify DTE speed, line speed, error control, data

compression, or other status

4.1.5 S, Bit Map Registers

Description

This command reads/writes values of the S-registers. The Modem supports this command for various S
values, according to official specifications (ITU-I, ETSI, or manufacturer specific).

Syntax

Command Possible response(s)

ATS<n>=<value> OK

or:

+CME ERROR: <err>

ATS<n>? <current value of S-register n>

OK

or:

+CME ERROR: <err>

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

The following table shows the different S-registers and their associated values

Page 26 of 165
 <n> Description Min Max Default

0 Sets/gets number of rings before auto answer. 000 255 000

4 Sets/gets line feed code character. 000 127 010

7 Sets/get no carrier timeout 000 255 255

Note:
 - Default value 000 means disabled.
 - For ATS0,the duration time to perform expected ring should be not over the allowed time by
network

4.1.6 &F, Set to Factory Defined Configuration

Description

This command is used to set factory defined configuration.

Syntax

Command Possible response(s)

AT&F[<value>] OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<value>: integer type and range is 0-255. And<value>=0 if without specifying parameter
0 Restore factory defined profile.

other Reserved

4.1.7 Z, Reset to User Profile

Description

This command drops the current call, and resets the values to default configuration.

Page 27 of 165
Syntax

Command Possible response(s)

ATZ[<value>] OK

or:

+CME ERROR: <err>

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes No < 1s

Defined Values

<value>: integer type; <value>=0 if without parameter

0 Reset to user profile 0

1 Reset to user profile 1

Other Reserved

4.1.8 +CBC, Battery Charger Connection

Description

This command intends to query the battery voltage level.

Syntax

Command Possible response(s)

AT+CBC
+CBC: <bcs>,<bcl>
OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Page 28 of 165
Defined Values

<bcs>: integer type

0 MT is powered by the battery (default)

<bcl>: integer type; Voltage with mV

4.1.9 +MTSM, Temperature Sensor Measurement

Description

This command measures the current temperature sensor value in Celsius degrees.
This temperature is taken from a thermistor internally.
Note:
All the parameters restore to default values when Modem restart and the default value is 0.

Syntax

Command Possible response(s)

AT+MTSM=<Report>[,<Rate>][,<Low
If <Report>=0:
>,<High>]
OK

If <Report>=1,6,7

+MTSM: <Temp>

OK

If <Report>=2 or 3:

OK

+MTSM: <Temp>

+MTSM: <Temp>

or:
ERROR: <error code>

AT+MTSM?
+MTSM: <Report>[,<Rate>][,<Low>,<High>]

OK

AT+MTSM=?
+MTSM: (range of <Report>),(range of <Rate>),(range of

Page 29 of 165
 Command Possible response(s)
<Low>/<High>)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<Report>: integer type;

0 Deactivate unsolicited report.

1 Report once the current temperature.

2 Activate unsolicited report.

3 Activate unsolicited report only for out-off boundaries events.

6 Report the temperature of BBIC

7 Report the temperature of RF

<Rate>: integer type and range 1-255; Select the time interval in seconds between the unsolicited reports. And default

value: 1

<Low>: integer type and range 0-125; The lowest boundary level of the temperature value in Celsius for unsolicited

report. And Default value: 0

<High>: integer type and range 0-125; The Highest boundary level of the temperature value in Celsius for unsolicited

report. And Default value: 0

Note:<Low>,<High> parameters are valid only when <Report>=3

4.1.10+MSMPD, Enable/Disable SIM card hot plug

Description

This command can Enable/Disable SIM card hot plug feature. The default status is enable this feature.
The parameter will be saved in NVM and can restore at power cycle.

Page 30 of 165
Syntax

Command Possible response(s)

AT+MSMPD=<status> OK
Or:

+CME ERROR: <err>

AT+MSMPD? +MSMPD: <status>

OK

AT+MSMPD=? +MSMPD: (list of supported <status>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No Yes Yes No < 1s

4.1.14.4 Defined Values

<status>: integer type;

0 Disable the SIM card hot plug feature

1 Enable the SIM card hot plug feature. Default value.

4.1.11+CMUX, MUX Start up Command

Description

This command is used to start the GSM MUX multiplexing protocol stack. When the Modem received a
valid +CMUX command, it returns OK and changes its state to MUX-Init. If the parameters are left out, the
default value is used.

Syntax

Command Possible response(s)

AT+CMUX=<mode>[,<subset>[,< OK
port_speed>[,<N1>[,<T1>[,<N or

2>[,<T2>[,<T3>[,<k>]]]]]]]] +CME ERROR: <err>

AT+CMUX? +CMUX:
<mode>,[<subset>],<port_speed>,<N1>,<T1>,<N2>,<T2>,<T3>,<K>

Page 31 of 165
 Command Possible response(s)
OK

or
+CME ERROR: <err>

AT+CMUX=? +CMUX: (list of supported <mode>s),(list of supported<subset>s),[(list

of supported <port_speed>s)],(list of supported <N1>s),(list of

supported <T1>s),(list of supported <N2>s),(list of supported

<T2>s),(list of supported <T3>s),(list of supported <k>s)

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<mode>: integer type; MUX mode:

0 Basic

<subset>: integer type; Defines how the MUX control channel is set up. The virtual channel is set up according to this
setting.

0 UIH frames used only

<port_speed>: integer type;

1 9600 bit/sec

2 19200 bit/sec

3 38400 bit/sec
4 57600 bit/sec

5 115200 bit/sec(default)

6 230400 bit/sec
<N1>: integer type and range 1-1509; Maximum frame size. Default value is 31 in Basic mode.

<T1>: integer type and range 1-255; Acknowledgement timer (in units of 10 ms). Default value is 10

<N2>: integer type and range 0-5; Maximum number of re-transmissions. Default value is 3.
<T2>: integer type and range 2-255; Response timer for the DLC0 (in unit of 10 ms). Default value is 30

Note:<T2> must be longer than <T1>.

<T3>: integer type and range 1-255;Wake up response timer (in seconds). Default value is 10.

Page 32 of 165
<k>: Reserve for Advanced operation with Error Recovery options.

4.1.12+CPWROFF Switch off MS

Description

This command is used to switch off the Modem and make detach procedure

Syntax

Command Possible response(s)

AT+CPWROFF OK

or
+CME ERROR: <err>

AT+CPWROFF=? OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes <2s

4.1.13+CFUN, Set Phone Functionality

Description

This command is used to select the level of functionality <fun> in the modem.

Syntax

Command Possible response(s)

AT+CFUN=<fun>[,<rst>] OK
Or:

+CME ERROR: <err>

AT+CFUN? +CFUN: <power mode>,<STK_mode>

OK
or

+CME ERROR: <err>

Page 33 of 165
 AT+CFUN=? +CFUN: (list of supported <fun>s),(list of supported<rst>s)

OK

or

+CME ERROR: <err>

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<fun>: integer type;

0 Minimum functionality (Switch off MS and make detach procedure).

1 Full functionality. Enable the transmit and receive RF circuits for all supported radio access technologies (Online

mode).

4 Disable both MT transmit and receive RF circuits (Airplane mode).

5 Factory Test Mode

6 Enable SIM STK and Fetching of proactive Commands.

7 Disable SIM STK and enable Fetching of proactive Commands.

8 Disable Fetching of proactive Commands.

15 Reset

16 Normal reset

27 SIM recovery hidden reset

31 Single stack off

32 All stack off

33 Single stack on sim reset

34 All stack on sim reset

35 Single sim on or off

36 All sim on or off

37 Single stack reset

38 All stack reset

Note 1: <rst> is not supported when <fun> = 15

Note 2: When <fun> value are 0 or 15, the OK response may be missed due to race condition

Note 3: The <fun> value whether is persistent or not depends on the implementation of target products.

Page 34 of 165
<rst>: integer type;

0 Do not reset the MT before setting it to <fun> power level

1 Reset the MT before setting it to <fun> power level

<power_mode>: integer type;

1 MS is switched on.
2 Invalid Mode.

4 Airplane Mode.

<STK_mode>: integer type

0 Inactive state (default).

6 Enable SIM STK and Fetching of proactive Commands.

7 Disable SIM STK and enable Fetching of proactive Commands

8 Disable Fetching of proactive Commands.

4.1.14+MSTART, Start message notification

Description

This command is used to enable/disable module outputting starting message when power up.

Syntax

Command Possible response(s)

AT+MSTART=<at ready>,<sim ready> OK

Or:
ERROR

AT+MSTART? +MSTART: <at ready>,<sim ready>

OK

AT+MSTART=? +MSTART: (list of supported <at ready>s),(list of supported <sim

read>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No Yes Yes Yes < 1s

Page 35 of 165
Defined Values

<at ready>: integer type;

0 Do not output “AT command ready” from UART

1 Output “AT command ready” from UART (default value)

<sim ready>: integer type;

0 Do not output “+SIM READY” after phonebook initialize completely

1 Output “+SIM READY” after phonebook initialize completely (default value)

Note: “AT command ready” is not allowed to be output from USB port even if set to 1. “+SIM READY” can output
from UART and USB port according to setting.

5 Phone Book and Clock

5.1 Directory Access Commands - Phone Book

This set of commands enables read/write access to the phone book contained within the Modem,
including both the numeric and the alpha information contained in the location. The presentation is
according to GSM 07.07.
In some cases, it may be possible to use these commands to access the dialed and received call stacks.
However, as these phone books cannot be edited, the +CPBW command does not work on them.

5.1.1 +CPBS, Select Phone Book Memory

Description

This command handles the selection of the memory to be used for reading and writing entries in the
Modem’s phone books’ memory.

Syntax

Command Possible response(s)

AT+CPBS=<storage>[,<password>] OK
or:

+CME ERROR: <err>

Page 36 of 165
 Command Possible response(s)
AT+CPBS?
+CPBS: <storage> [,<used>,<total>]

OK

AT+CPBS=?
+CPBS: (list of supported <storage>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes < 1s

Defined Values

<storage> values reserved by the present document:

"EN" SIM/USIM (or MT) emergency number (+CPBW is not be applicable for this storage)

"ON" SIM (or MT) own numbers (MSISDNs) list (reading of this storage may be available through +CNUM also).

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 in EFMSISDN under DFTelecom is selected. If a UICC with an active

USIM application is present, the information in EFMSISDN under ADFUSIM is selected.

"LD" SIM/UICC last-dialling-phonebook

"SN" SDN phonebook

"BL" Blacklist in stack

"SM" SIM/UICC phonebook. In the currently selected card slot, if a SIM card is present or if a UICC with an

active GSM application is present, the EFADN under DFTelecom is selected. If a UICC with an active

USIM application is present, the global phonebook, DFPHONEBOOK under DFTelecom is selected.
<password>: string type value representing the PIN2-code required when selecting PIN2-code locked <storage>s above,

e.g. "FD" or the hidden key to be verified in order to access to the hidden phonebook entries in the

UICC/USIM or any other phonebook with hidden entries. If the combined phonebook is selected, "MT", the
<password> will correspond to the hidden key of the USIM phonebook.

<used>: integer type value indicating the number of used locations in selected memory

<total>: integer type value indicating the total number of locations in selected memory

Note: SM is the default storage.

Page 37 of 165
 5.1.2 +CPBR, Read Phone Book Entries
Description

This command recalls phone book entries from a specific entry number or from a range of entries. If only
one entry is specified, and that entry is empty, OK is returned. If a range of entries is requested, all entries
that contain data within that range are returned. If a listing fails in a Modem error, +CME ERROR: <err> is
returned.
This command can also be used to obtain information about the number of entries and the maximum size
of a phone number and alpha tag fields in the phone book.
This command acts on the currently active phone book, as selected with the +CPBS command.

Syntax

Command Possible response(s)

AT+CPBR=<index1>[,<index2>] [+CPBR: <index1>,<number>,<type>,<text>[,<hidden>][,<group>][,

<adnumber>][,<adtype>][,<secondtext>][,<email>][,<sip_uri>][,<tel

_uri>]][[...][<CR><LF>+CPBR: <index2>,<number>,<type>,<text>[
,<hidden>][,<group>][,<adnumber>][,<adtype>][,<secondtext>][,<e

mail>][,<sip_uri>][,<tel_uri>]]]

OK

or:

+CME ERROR: <err>

AT+CPBR=? +CPBR: (list of supported <index>s),[<nlength>],[<tlength>],

[<glength>],[<slength>],[<elength>],[<siplength>],[<tellength>]

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes <5s

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>

Page 38 of 165
<type>: type of address octet in integer format

<text>: string type field of maximum length <tlength>;

<group>: string type field of maximum length <glength>;

<adnumber>: string type phone number of format <adtype>

<adtype>: type of address octet in integer format

<secondtext>: string type field of maximum length <slength>;

<email>: string type field of maximum length <elength>;

<sip_uri>: string type field of maximum length <siplength>;

<tel_uri>: string type phone number of maximum length <tellength>;

<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>

<siplength>: integer type value indicating the maximum length of field <sip_uri>

<tellength>: integer type value indicating the maximum length of field <tel_uri>

<hidden>: integer type value indicates if the entry is hidden or not

0 phonebook entry not hidden

1 phonebook entry hidden

5.1.3 +CPBF, Find Phone Book Entries

Description

This execution command enables the user to search for a particular entry, by name, in the currently active
phone book. If no matching entry is found, the command returns OK. If multiple matches are found, all are
returned.

Syntax

Command Possible response(s)

AT+CPBF=<findtext> [+CPBF: <index1>,<number>,<type>,<text>[,<hidden>][,<group>][,
<adnumber>][,<adtype>][,<secondtext>][,<email>][,<sip_uri>][,<tel

_uri>]][<CR><LF>+CBPF: <index2>,<number>,<type>,<text>[,<hi

dden>][,<group>][,<adnumber>][,<adtype>][,<secondtext>][,<email

Page 39 of 165
 >][,<sip_uri>][,<tel_uri>][...]]

OK

or:

+CME ERROR: <err>

AT+CPBF=? +CPBF: [<nlength>],[<tlength>],[<glength>],[<slength>],[<elength>

],[<siplength>],[<tellength>]

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes <5s

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

<group>: string type field of maximum length <glength>;

<adnumber>: string type phone number of format <adtype>

<adtype>: type of address octet in integer format

<secondtext>: string type field of maximum length <slength>;

<email>: string type field of maximum length <elength>;

<findtext>, <text>: string type field of maximum length <tlength>;

<sip_uri>: string type field of maximum length <siplength>;

<tel_uri>: string type phone number of maximum length <tellength>;

<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>

<siplength>: integer type value indicating the maximum length of field <sip_uri>

<tellength>: integer type value indicating the maximum length of field <tel_uri>

Page 40 of 165
<hidden>: integer type value indicates if the entry is hidden or not

0 phonebook entry not hidden

1 phonebook entry hidden

5.1.4 +CPBW, Write Phone Book Entry

Description

Set command writes phone book entry in location number<index> in the current phone book memory storage selected

with +CPBS. Entry fields written are phone number<number> in format<type> and <text> associated with the number. If

all fields except <index> are omitted, the corresponding entry is deleted. If the <index> is left out, but <number> is given,

entry is written to the first free location in the phone book.

Read command returns the last <written_index> value, or -1 if information about previous value is not available.

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>, the maximum length of <email>, the maximum length of <sip_uri> and

the maximum length of <tel_uri>.

In case of SIM storage, the lengths may not be available.

Syntax

Command Possible response(s)

+CPBW=[<index>][,<number>[,<type>[,<text>[,<g
+CPBW: <written_index>
roup>[,<adnumber>[,<adtype>[,<secondtext>[,<ema
OK
il>[,<sip_uri>[,<tel_uri>[,<hidden>]]]]]]]]]]]
or:

+CME ERROR: <err>

AT+CPBW?
+CPBW: <written_index>

OK

AT+CPBW=? +CPBW: (list of supported <index>s),[<nlength>],

(list of supported <type>s),[<tlength>],[<glength>],
[<slength>],[<elength>],[<siplength>],[<tellength>]
OK

Page 41 of 165
Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes < 2s

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

<group>: string type field of maximum length <glength>;

<adnumber>: string type phone number of format <adtype>

<adtype>: type of address octet in integer format

<secondtext>: string type field of maximum length <slength>;

<email>: string type field of maximum length <elength>;

<findtext>, <text>: string type field of maximum length <tlength>;

<sip_uri>: string type field of maximum length <siplength>;

<tel_uri>: string type phone number of maximum length <tellength>;

<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>

<siplength>: integer type value indicating the maximum length of field <sip_uri>

<tellength>: integer type value indicating the maximum length of field <tel_uri>

<hidden>: integer type value indicates if the entry is hidden or not

0 phonebook entry not hidden

1 phonebook entry hidden

<written_index>: integer type value indicating the last location number <index> of the written phonebook

Page 42 of 165
6 System Date and Time Access Commands
6.1 General command
6.1.1 +CCLK, Read/Set System Date and Time
Description

This command reads and sets the Modem current date, time and time zone.

Syntax

Command Possible response(s)

AT+CCLK=<time> OK

or:

+CME ERROR: <err>

AT+CCLK?
+CCLK: <time>

OK

or:

+CME ERROR: <err>

AT+CCLK=? OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<time>: string type value; format is "yy/MM/dd,hh:mm:sszz", 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"
yy 2-digit year[00-99]

MM 2-digit month [01-12]

Page 43 of 165
 dd 2-digit day of month [00-31]

hh 2-digit hour [00-23]

mm 2-digit minute [00-59]

ss 2-digit seconds [00-59]

zz (optional) time zone offset from GMT, in quarter-hours [-47...+48]. If this value is not specified, the time zone
offset will be 0.

6.1.2 +CTZU, Automatic Time Zone Update

Description

This command enable/disable (on/off) the automatic update of the time zone via NITZ.

Syntax

Command Possible response(s)

AT+CTZU=<onoff> OK

or:
+CME ERROR: <err>

AT+CTZU?
+CTZU: <onoff>

OK

AT+CTZU=? +CTZU: (list of supported <onoff>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes < 1s

Defined Values

<onoff>: integer type value indicating

0 Disable automatic time zone update via NITZ; Default value.

1 Enable automatic time zone update via NITZ.

Note: The Default value for L810-GL-06 is 1

Page 44 of 165
 6.1.3 +CTZR, Time Zone Reporting
Description

This command enable/disable the time zone change event and Daylight saving time reporting. If reporting
is enabled the MT returns the unsolicited result code +CTZV: <tz>, or +CTZE: <tz>,<dst>,[<time>].

Syntax

Command Possible response(s)

AT+CTZR=[<reporting>] OK

or:
+CME ERROR: <err>

AT+CTZR?
+CTZR: <reporting>

OK

AT+CTZR=? +CTZR: (list of supported <reporting>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes < 1s

Defined Values

<reporting>:integer type value indicating:

0 Disable time zone change event reporting.Default value.

1 Enable time zone change event reporting by unsolicited result code +CTZV: <tz>.

2 Enable extended time zone and local time reporting by unsolicited result code +CTZE: <tz>,<dst>,[<time>].
<tz>:integer value indicating the time zone.

<time>: string type value; format is "yy/MM/dd,hh:mms" ,wherein characters indicates year,month, day, hour, minutes,

seconds
<dst>:integer value;daylight savings time:

0 No adjustment for Daylight Saving Time

1 +1 hour adjustment for Daylight Saving Time

2 +2 hours adjustment for Daylight Saving Time

Page 45 of 165
7 SMS
7.1 SMS Commands

Modem supports SMS PDU and SMS TEXT mode according to ETSI specifications 3GPP TS 27.005 &
3GPP TS 03.40/23.0400.

7.1.1 +CSCS, Select Terminal Character Set

Description

This command selects the Modem character set. The modem supports the following character sets:
"IRA","GSM","UCS2","HEX". The default value is “IRA”.

Syntax

Command Possible response(s)

AT+CSCS=<chset> OK

or:

+CME ERROR: <err>

AT+CSCS? +CSCS: <chset>

OK

AT+CSCS=? +CSCS: (list of supported <chset>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<chset>: string type; Character Set

“IRA” International Reference Alphabet (ITU-T T.50)

Page 46 of 165
 “GSM” GSM default alphabet (GSM 03.38 subclause 6.2.1)

"UCS2" 2-byte Universal Character Set, Unicode (ISO/IEC 10646 [32])

“HEX” Character strings consist only of hexadecimal numbers from 00 to FF

“8859-1” ISO-8859-1; And it only be supported in G5 series products.

7.1.2 +CSMS, Select Message Service

Description

This command handles the selection of the messaging service. It returns the types of messages that are
supported by the Modem.

Syntax

Command Possible response(s)

AT+CSMS=<service>
+CSMS: <mt>,<mo>,<bm>

OK

or:

+CMS ERROR: <err>

AT+CSMS?
+CSMS: <service>,<mt>,<mo>,<bm>

OK

AT+CSMS=?
+CSMS: (list of supported <service>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<service>:integer type;

0 SMS AT command grammar is compatible with GSM Phase 2

1 SMS AT command grammar is compatible with GSM Phase 2+

<mt>: integer type; Mobile terminated messages

Page 47 of 165
 0 Not supported by the Modem

1 Supported by the Modem

<mo>:integer type; Mobile originated messages

0 Not supported by the Modem

1 Supported by the Modem

<bm>:integer type; Broadcast type messages

0 Not supported by the Modem

1 Supported by the Modem

7.1.3 +CPMS, Preferred Message Storage

Description

This command handles the selection of the preferred message storage area. The message storage area
is divided into three parts, mem1, mem2 and mem3.

Syntax

Command Possible response(s)

AT+CPMS=<mem1>[,<mem2>[,<mem3>]]
+CPMS: <used1>,<total1>,<used2>,<total2>,<used3>,<total3>

OK

or:

+CMS ERROR: <err>

AT+CPMS?
+CPMS:
<mem1>,<used1>,<total1>,<mem2>,<used2>,<total2>,

<mem3>,<used3>,<total3>

OK

or:

+CMS ERROR: <err>

AT+CPMS=? +CPMS: (list of supported<mem1>s),(list of supported <mem2>s),(list

of supported <mem3>s)
OK

or:

Page 48 of 165
 Command Possible response(s)
+CMS ERROR: <err>

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes < 1s

Defined Values

<mem1>: string type; Memory from which messages are read and deleted.

<mem2>: string type; Memory to which writing operation is made.

<mem3>: string type; Memory to which received SMS are stored (unless forwarded directly to TE).

Note: Supported values for <mem1>,<mem2>,<mem3> may be:

"BM" Broadcast message storage

"SM" (U)SIM message storage

"ME" ME message storage

"SR" Status report storage

Note:

- <mem1>,<mem2>,<mem3>may be restored to “SM” after power cycle device

- L8 family products only support “SM” storage for<mem1>,<mem2>,<mem3>

- L7family products support as below combinations:

<mem1> :“BM”,“SM”,”SR”,”ME”

<mem2> and <mem3> : “SM”, ”ME”

7.1.4 +CMGF, Message Format

Description

This command is a basic command.

The Set command handles the selection of the message format used with send, list, read and write
commands, as well as the format of unsolicited result codes resulting from message receipts.

The Modem supports both PDU mode (where entire TP data units are used) and text mode (where the
body of the message and its headers are given as separate parameters).

Page 49 of 165
Syntax

Command Possible response(s)

AT+CMGF=<mode> OK
or:
+CME ERROR: <err>

AT+CMGF?
+CMGF: <mode>

OK

AT+CMGF=?
+CMGF: (list of supported <mode>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes < 1s

Defined Values

<mode>: integer type; Message format:

0 PDU mode (default)

1 Text mode

7.1.5 +CSCA, Service Center Address

Description

This command enables to write/read SCA to/from SIM. In SMS text mode, SCA stored in SIM is added to
any stored and sent SMS.In SMS pdu mode, SCA stored in SIM is added to stored SMS and send SMS
only when SCA address length coded in PDU equals zero.

Syntax

Command Possible response(s)

AT+CSCA=<sca>[,<tosca>] OK
or:
+CME ERROR: <err>

Page 50 of 165
 Command Possible response(s)
AT+CSCA?
+CSCA: <sca>,<tosca>

OK

AT+CSCA=? OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes < 1s

Defined Values

<sca>: string type and range is 1-20; Service Center Address."+" character prefix of <sca> indicates <tosca> of 145. Each

character is represented by semi octets (excluding ‘+’ character). If <sca> contains an odd number of digits, bits 4

to 7 of the last octet shall be filled with an end mark coded “1111".

<tosca>: type of service center address.

<tosca> of 129 is mostly use for local number and 145 for International.

<tosca> of 129 is default value.

<tosca> values are in range of 0-255.Valid values are defined according to:GSM03.40 v7.4.0 section 9.1.2.5 as follow:
Bit 7 is 1

Bits 6,5–4 - Present Type of number as follow:

Bits 6 5 4
0 0 0 Unknown

0 0 1 International number

0 1 0 National number
0 1 1 Network specific number

1 0 0 Subscriber number

1 0 1 Alphanumeric, (coded according to GSM TS 03.38 7-bit default alphabet)

1 1 0 Abbreviated number

1 1 1 Reserved for extension

Numbering-plan-identification (applies for Type-of-number = 000,001,010)

Bits 3 2 1 0

0 0 0 0 Unknown

0 0 0 1 ISDN/telephone numbering plan (E.164/E.163)

Page 51 of 165
 0 0 1 1 Data numbering plan (X.121)

0 1 0 0 Telex numbering plan

1 0 0 0 National numbering plan

1 0 0 1 Private numbering plan

1 0 1 0 ERMES numbering plan (ETSI DE/PS 3 01-3)

1 1 1 1 Reserved for extension.

All other values are reserved.

7.1.6 +CSMP, Set Text Mode Parameters

Description

This command is a basic command and is used to select values for additional parameters needed when
SMS is sent to the network or placed in storage when TEXT mode is selected.

Syntax

Command Possible response(s)

AT+CSMP=[<fo>[,<vp>[,<pid>[,<dcs>]]]] OK
or:
+CME ERROR: <err>

AT+CSMP?
+CSMP: <fo>,<vp>,<pid>,<dcs>

OK

AT+CSMP=? OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes < 1s

Defined Values

<fo>:integer type;Depending on the command or result code: first octet of 3GPP TS 23.040 [3] SMS-DELIVER,
SMS-SUBMIT(default 17), SMS-STATUS-REPORT, or SMS-COMMAND(default 2) in integer format.

<vp>:integer type; Validity Period, depending on SMS-SUBMIT <fo>,TP-Validity-Period-Format bits setting. If there is

Page 52 of 165
 no correlation between the VPF and the VP value. an error message will be returned. Either in integer format

(see Table) or in time-string format ("yy/MM/dd, hh:mm:ss±zz"). If in integer format the vp will write to
SIM EF and read form SIM EF when use it.

Note: The following table shows the VP format.

<Parameter> Description

0 to 143 (TP-VP + 1) x 5 minutes (i.e. 5 minutes intervals up to 12 hours)

144 to 167 12 hours + ((TP-VP - 143) x 30 minutes)

168 to 196 (TP-VP - 166) x 1 day

197 to 255 (TP-VP - 192) x 1 week

<pid>:integer type; Protocol-Identifier. The one octet information element by which the SM-TL either refers to the higher
layer protocol being used, or indicates interworking with a certain type of telematic device.

"0 - no interworking, SME-to-SME protocol (default) "Any value between 0-255 will be accepted.

The SC may reject messages with a TP-Protocol-Identifier containing a reserved value or one, which is not
supported.

<dcs>: integer type; One octet of Data Coding Scheme, indicates the data coding scheme of the DATA, and may indicate

a message class; Default value is 0

7.1.7+CSDH, Show Text Mode Parameters

Description

This command controls whether detailed header information is shown in text mode result codes.

Syntax

Command Possible response(s)

AT+CSDH=[<show>] OK
or:
+CME ERROR: <err>

AT+CSDH? +CSDH: <show>

OK

AT+CSDH=? +CSDH: (list of supported <show>s)

OK

Page 53 of 165
Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes < 1s

Defined Values

<show>: integer type

0 do not show header values defined in commands +CSCA and +CSMP (<sca>, <tosca>, <fo>, <vp>, <pid> and

<dcs>) nor <length>, <toda> or <tooa> in +CMT, +CMGL, +CMGR result codes for SMS-DELIVERs and

SMS-SUBMITs in text mode; for SMS-COMMANDs in +CMGR result code, do not show <pid>, <mn>,
<da>, <toda>, <length> or <cdata>; Default value.

1 show the values in result codes

7.1.8+CNMI, New Message Indications to Terminal

Description

This command handles enabling of unsolicited notifications to the terminal when an SMS is received by
the Modem.
After sending an unsolicited response to the TE, the Modem will expect a +CNMA (new message
acknowledgement) from the TE within a predefined timeout of 15 seconds. Within the timeout the Modem
will not send another unsolicited response to the TE before the previous one is acknowledgement. If the
Modem does not receive acknowledgment within the required time, CNMI parameters will NOT be reset
automatically and the unsolicited response will send to the TE again.

Syntax

Command Possible response(s)

AT+CNMI=[<mode>[,<mt>[,<bm>[,<ds>[, OK

<bfr>]]]]] or:
+CME ERROR: <err>

AT+CNMI? +CNMI: <mode>,<mt>,<bm>,<ds>,<bfr>

OK

AT+CNMI=? +CNMI: (list of supported <mode>s),(list of supported <mt>s),(list of

supported <bm>s),(list of supported <ds>s),(list of

Page 54 of 165
 Command Possible response(s)
supported <bfr>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes < 1s

Defined Values

<mode>: integer type, Default value is 1.

0 Buffer unsolicited result codes in the TA. If TA result code buffer is full, indications can be buffered in some
other place or the oldest indications may be discarded and replaced with the new received indications.

1 Discard indication and reject new received message unsolicited result codes when TA-TE link is reserved

(e.g. in on-line data mode). Otherwise forward them directly to the TE.
2 Buffer unsolicited result codes in the TA when TA-TE link is reserved (e.g. in on-line data mode) and flush

them to the TE after reservation. Otherwise forward them directly to the TE.

<mt>: integer type (the rules for storing received SMs depend on its data coding scheme (refer 3GPP TS 23.038 [2]),

preferred memory storage (+CPMS) setting and this value; refer table 8.1.8-1; Default value is 1.

0 No SMS-DELIVER indications are routed to the TE.

1 If SMS-DELIVER is stored into ME/TA, indication of the memory location is routed to the TE using
unsolicited result code:

+CMTI: <mem>,<index>

2 SMS-DELIVERs (except class 2 messages and messages in the message waiting indication group (store
message)) are routed directly to the TE using unsolicited result code:

+CMT: [<alpha>],<length><CR><LF><pdu> (PDU mode enabled); or

+CMT: <oa>,[<alpha>],<scts>[,<tooa>,<fo>,<pid>,<dcs>,<sca>,<tosca>,<length>]<CR><LF><data>(text
mode enabled; about parameters in italics, refer command Show Text Mode Parameters +CSDH)

If ME has its own display device then class 0 messages and messages in the message waiting indication

group (discard message) may be copied to both ME display and to TE. In this case, ME shall send the
acknowledgement to the network.

Class 2 messages and messages in the message waiting indication group (store message) result in indication

as defined in <mt>=1.
0 Class 3 SMS-DELIVERs are routed directly to TE using unsolicited result codes defined in <mt>=2.

Page 55 of 165
 Messages of other data coding schemes result in indication as defined in <mt>=1

Table 7.1.8-1: <mt> parameter

<mt> Receiving procedure for different message data coding schemes (refer 3GPP TS 23.038 [2])
0 no class: as in 3GPP TS 23.038 [2], but use <mem3> as preferred memory
class 0: as in 3GPP TS 23.038 [2], but use <mem3> as preferred memory if message is tried to be
stored
class 1: as in 3GPP TS 23.038 [2], but use <mem3> as preferred memory
class 2: as in 3GPP TS 23.038 [2]
class 3: as in 3GPP TS 23.038 [2], but use <mem3> as preferred memory
message waiting indication group (discard message): as in 3GPP TS 23.038 [2], but use <mem3> as
preferred memory if message is tried to be stored
message waiting indication group (store message): as in 3GPP TS 23.038 [2], but use <mem3> as
preferred memory
1 as <mt>=0 but send indication if message stored successfully
2 no class: route message to TE
class 0: as in 3GPP TS 23.038 [2], but also route message to TE and do not try to store it in memory
class 1: route message to TE
class 2: as <mt>=1
class 3: route message to TE
message waiting indication group (discard message): as in 3GPP TS 23.038 [2], but also route message
to TE and do not try to store it in memory
message waiting indication group (store message): as <mt>=1
3 class 3: route message to TE
others: as <mt>=1

<bm> integer type (the rules for storing received CBMs depend on its data coding scheme (refer 3GPP TS 23.038 [2]),

the setting of Select CBM Types (+CSCB) and this value; refer table 8.1.8-2); Default value is 0.

0 No CBM indications are routed to the TE.

1 If CBM is stored into ME/TA, indication of the memory location is routed to the TE using unsolicited result

code:

+CBMI: <mem>,<index>
2 New CBMs are routed directly to the TE using unsolicited result code:

+CBM: <length><CR><LF><pdu> (PDU mode enabled); or

+CBM: <sn>,<mid>,<dcs>,<page>,<pages><CR><LF><data> (text mode enabled)

If ME supports data coding groups which define special routing also for messages other than class 3 (e.g.

(U)SIM specific messages), ME may choose not to route messages of such data coding schemes into TE

(indication of a stored CBM may be given as defined in <bm>=1).

3 Class 3 CBMs are routed directly to TE using unsolicited result codes defined in <bm>=2. If CBM storage is

supported, messages of other classes result in indication as defined in <bm>=1.

Page 56 of 165
 Table 7.1.8-2: <bm> parameter

<bm> Receiving procedure for different message data coding schemes (refer 3GPP TS 23.038 [2])
0 all schemes: as in 3GPP TS 23.038 [2]; if CBM storage is supported, store message to "BM" (or
some manufacturer or data coding scheme specific memory)
1 all schemes: as<bm>=0 but send indication if message stored successfully
2 all schemes: route message to TE unless ME has detected a special routing to somewhere else
(e.g. to (U)SIM; an indication may be sent if message stored successfully)
3 class 3: route message to TE
others: as <bm>=1 (if CBM memory storage is supported)

<ds>: integer type; Default value is 0.

0 No SMS-STATUS-REPORTs are routed to the TE.

1 SMS-STATUS-REPORTs are routed to the TE using unsolicited result code:

+CDS: <length><CR><LF><pdu> (PDU mode enabled); or

+CDS: <fo>,<mr>,[<ra>],[<tora>],<scts>,<dt>,<st> (text mode enabled)

2 If SMS-STATUS-REPORT is stored into ME/TA, indication of the memory location is routed to the TE

using unsolicited result code:

+CDSI: <mem>,<index>
Table 7.1.8-3: SMS-STATUS-REPORT result code and acknowledgement summary
<ds> result codes and commands
1 +CDS & +CNMA1)
2 +CDSI
1) acknowledgement command must be sent when +CSMS
<service> value equals 1

<bfr>: integer type; Default value is 0.

0 TA buffer of unsolicited result codes defined within this command is flushed to the TE when <mode> 1...3 is
entered (OK response shall be given before flushing the codes).

1 TA buffer of unsolicited result codes defined within this command is cleared when <mode> 1...3 is entered.

7.1.9+CNMA, New Message Acknowledgment

Description

This command acknowledge the receipt of a +CMT and +CDS response from the terminal to the Modem.
A +CMT response receipt confirms the correct reception of a new SMS-DELIVER message, which was
routed directly to the terminal. A +CDS response receipt confirms the correct reception of a new
SMS-STATUS-REPORT message, which was routed directly to the terminal.

When the Modem sends a +CDS response to the terminal, it waits a predefined timeout of 15 seconds for

Page 57 of 165
the +CNMA acknowledgment. The Modem will not send another +CDS result code to the terminal before
the previous one is acknowledged, or the timeout expires.

When the Modem sends a +CMT response to the terminal, it waits a predefined timeout of 15 seconds for
the +CNMA acknowledgment. The Modem will not send another +CMT result code to the terminal before
the previous one is acknowledged, or the timeout expires. Upon receipt of the +CNMA command, the
Modem sends RP-ACK to the network. The acknowledged SMS will not be saved in message storage. If
the command is executed but no acknowledgment is expected, or some other Modem related error occurs,
the final result code +CMS ERROR: <err> is returned.

Syntax

Command Possible response(s)

For text mode (+CMGF=1) OK

AT+CNMA or:

For PDU mode (+CMGF=0) +CME ERROR: <err>

AT+CNMA[=<n>[,<length>[<CR>PDU<ctr
l-Z/ESC>]]]

AT+CNMA=? OK in text mode

or:
+CNMA: (list of supported <n>s) in PDU mode

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes < 1s

Defined Values

<n>: integer type

0 command operates similarly as defined for the text mode

1 send RP-ACK

2 send RP-ERROR

<length>: integer type; Length of the PDU in PDU mode

Page 58 of 165
 7.1.10 +CMGL, List Messages
Description

These commands display a list of all SMS with the status value <stat>, from the Modem message storage
<mem1> (selected using the +CPMS command). The command returns a series of responses, one per
message, each item containing the message index, status, and data. If the status of a message is
"RECEIVED UNREAD", execution of the +CMGL command changes the status of the message to
"RECEIVED READ".

Syntax

Command Possible response(s)

AT+CMGL[=<stat>] if text mode (+CMGF=1), command successful and SMS-SUBMITs

and/or SMS-DELIVERs:
+CMGL: <index>,<stat>,<oa/da>,[<alpha>],[<scts>][,<tooa/toda>,

<length>]<CR><LF><data>[<CR><LF>

+CMGL: <index>,<stat>,<da/oa>,[<alpha>],[<scts>][,<tooa/toda>,
<length>]<CR><LF><data>[...]]

if text mode (+CMGF=1), command successful and

SMS-STATUS-REPORTs:

+CMGL:

<index>,<stat>,<fo>,<mr>,[<ra>],[<tora>],<scts>,<dt>,

<st>
[<CR><LF>

+CMGL:

<index>,<stat>,<fo>,<mr>,[<ra>],[<tora>],<scts>,<dt>,
<st>

[...]]

if text mode (+CMGF=1), command successful and

SMS-COMMANDs:

+CMGL: <index>,<stat>,<fo>,<ct>[<CR><LF>

+CMGL: <index>,<stat>,<fo>,<ct>[...]]
if text mode (+CMGF=1), command successful and CBM storage:

+CMGL: <index>,<stat>,<sn>,<mid>,<page>,<pages>

<CR><LF><data>[<CR><LF>

Page 59 of 165
 Command Possible response(s)
+CMGL: <index>,<stat>,<sn>,<mid>,<page>,<pages>

<CR><LF><data>[...]]
otherwise:

+CMS ERROR: <err>

AT+CMGL=? +CMGL: (list of supported <stat>s)

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes <5s

Defined Values

<index> 1-352 Index of message in storage.

<stat> Status of message in memory:

PDU mode Text mode Description

0 “REC UNREAD” Received unread messages (default)

1 “REC READ” Received read messages

2 “STO UNSENT” Stored unsent messages

3 “STO SENT” Stored sent message

4 “ALL” All messages

For fault tolerance, two mode can be trade off

<oa/da> Original/destination address.

<data> Message contents in text mode

<length> In PDU mode: Size of message, in octets, excluding SMSC data. InTEXT mode: Number of characters

included in <data>.

<pdu> Message header and contents in PDU mode format. See description in “+CMGR, Read Message”.
<toda/toda> Type of origination address / destination address

<fo> First octet of the SMS

<mr> Message Reference

<ra> Recipient-Address

<tora> Type of Recipient address

<scts> Service center time stamp

Page 60 of 165
<ct> Command type

<sn> Message serial number

<mid> Message ID

<page> Current page number

<pages> Total number of pages

<dt> Discharge-Time

<st> Status

7.1.11 +CMGR, Read Message

Description

These commands handle the reading of SMS. The command displays the message in location <index> of
the preferred message storage <mem1> (selected using the +CPMS command). If the status of the
message is "RECEIVED UNREAD", the +CMGR command changes the status to "RECEIVED READ".

Syntax

Command Possible response(s)

AT+CMGR=<index> if text mode (+CMGF=1), command successful and SMS-DELIVER:

+CMGR:

<stat>,<oa>,[<alpha>],<scts>[,<tooa>,<fo>,<pid>,<dcs>

,<sca>,<tosca>,<length>]<CR><LF><data>

if text mode (+CMGF=1), command successful and SMS-SUBMIT:

+CMGR:

<stat>,<da>,[<alpha>][,<toda>,<fo>,<pid>,<dcs>,[<vp>

],<sca>,<tosca>,<length>]<CR><LF><data>
if text mode (+CMGF=1), command successful and

SMS-STATUS-REPORT:

+CMGR: <stat>,<fo>,<mr>,[<ra>],[<tora>],<scts>,<dt>,<st>
if text mode (+CMGF=1), command successful and

SMS-COMMAND:

+CMGR: <stat>,<fo>,<ct>[,<pid>,[<mn>],[<da>],[<toda>],<length>
<CR><LF><cdata>]

if text mode (+CMGF=1), command successful and CBM storage:

Page 61 of 165
 Command Possible response(s)
+CMGR:

<stat>,<sn>,<mid>,<dcs>,<page>,<pages><CR><LF><
data>

otherwise:

+CMS ERROR: <err>

AT+CMGR=? OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes <2s

Defined Values

<index> Integer type and value starts from 1; Index in storage of the message to be retrieved.

<stat> Status of message in memory:

PDU mode Text mode Description

0 “REC UNREAD” Received unread messages (default)

1 “REC READ” Received read messages

2 “STO UNSENT” Stored unsent messages

3 “STO SENT” Stored sent message

4 “ALL” All messages

<alpha> Alpha ID of message (not present).

<length> In PDU mode: Size of message, in octets, excluding SMSC data.In TEXT mode: Number of characters
included in <data>.

<pdu> Message header and contents in PDU mode format. See description in the table below.

<oa/da> Original/destination address.

<data> Message contents in text mode

<toda/toda> Type of origination address / destination address

<fo> First octet of the SMS

<pid> Protocol Identifer

<dcs> Data Coding Scheme

<sca> Service Center Address

Page 62 of 165
<tosca> Type of Service Center Address

<vp> Validity Period. Either in integer format or in time-string format (“yy/MM/dd,hh: mm: ss±zz”)
<mr> Message reference

<scts> Service center time stamp

<ct> Command type

<sn> Message serial number

<mn> Message Number

<cdata> Command-Data
<mid> Message ID

<page> Current page number

<pages> Total number of pages

<mr> Message reference

<ra> Message Recipient address

<tora> Type of Recipient address

<scts> Service center time stamp

<dt> Discharge-Time

<st> Status

7.1.12 +CMSS, Send Message from Storage

Description

This command sends a pre-stored message, written previously using the +CMGW command. The <da>,
<toda> parameters are optional. If a DA is given, the message is sent to that address. Otherwise the
message is sent to the DA it was stored with (if any was entered). If no DA is found, an error occurs.
When the given index is an incoming message index the header settings will be as follows:
 <first-octet> will be SMS-SUBMIT and VPF - relative.
 The TP-RP and TP-UDHI settings will be taken from the incoming message's first octet.
 <vp> - will be set to the default value -167 - as defined in 03.40.
 <sca>,<tosca>, <pid> and <dcs> will be set according the incoming message parameters.
 If <da> and/or <toda> are not given by the command, the <oa> and <tooa> will be set instead.

Syntax

Command Possible response(s)

Page 63 of 165
 AT+CMSS=<index>[,<da>[,<toda>]] +CMSS: <mr>

or:

+CMS ERROR: <err>

AT+CMSS=? OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes <60s

Defined Values

<index>:integer type; Index in storage of the message to be sent.

<da>:string type; Destination address in quoted string. This field contains a single phone number.

<toda>: string type; Type of DA. Value between 128-255 (according to GSM 03.40, 9.1.2.5). If this field is not given and

first character of <da> is '+' ,<toda> will be 145, otherwise 129.

<mr>: integer type; Sent message reference number.

7.1.13 +CMGW, Write Message to Memory

Description

This command sends a pre-stored message, written previously using the +CMGW command. The <da>,
<toda> parameters are optional. If a DA is given, the message is sent to that address. Otherwise the
message is sent to the DA it was stored with (if any was entered). If no DA is found, an error occurs.
When the given index is an incoming message index the header settings will be as follows:
 <first-octet> will be SMS-SUBMIT and VPF - relative.
 The TP-RP and TP-UDHI settings will be taken from the incoming message's first octet.
 <vp> - will be set to the default value -167 - as defined in 03.40.
 <sca>,<tosca>, <pid> and <dcs> will be set according the incoming message parameters.
 If <da> and/or <toda> are not given by the command, the <oa> and <tooa> will be set instead.

Syntax

Command Possible response(s)

If text mode (+CMGF=1): +CMGW: <index>

Page 64 of 165
 AT+CMGW[=<da>[,<toda>[,<stat>]]]<CR> or:

text is entered<ctrl-Z/ESC> +CMS ERROR: <err>

if PDU mode (+CMGF=0):

AT+CMGW=<length>[,<stat>]<CR> PDU

is given<ctrl-Z/ESC>

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes <2s

Defined Values

<da>:string type; destination address, string type represented in the currently selected character set.

<toda>:integer type; type of destination address.

129 number in national format

145 number in international format (contains the "+")

<stat>:string type; message status.

"REC UNREAD" new received message unread (default for DELIVER messages)

"REC READ" received message read

"STO UNSENT" message stored not yet sent (default for SUBMIT messages)

"STO SENT" message stored already sent

7.1.14 +CMGD, Delete Message

Description

This command handles deletion of a single message from memory location <index>, or multiple
messages according to <delflag>. If the optional parameter <delflag> is entered, and is greater than 0, the
<index> parameter is practically ignored. If deletion fails, result code +CMS ERROR: <err> is returned.

Syntax

Command Possible response(s)

Page 65 of 165
 AT+CMGD=<index>[,<delflag>] OK
or:
+CME ERROR: <err>

AT+CMGD=? +CMGD: (list of valid<index>s),(list of valid<deflag>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes <5s

Defined Values

<index>: integer type;Index in the SMS memory of the message to be deleted.

<delflag>: integer type, indicating multiple message deletion request as follows:

0 Delete the message specified in <index>

1 Delete all read messages from preferred message storage, leaving unread messages and stored mobile

originated messages (whether sent or not) untouched

2 Delete all read messages from preferred message storage and sent mobile originated messages, leaving unread

messages and unsent mobile originated messages untouched

3 Delete all read messages from preferred message storage, sent and unsent mobile originated messages leaving

unread messages untouched.

4 Delete all messages from preferred message storage including unread messages.

7.1.15 +CGSMS, Select Service for MO SMS Messages

Description

This command handles the selection of the service or service preference used by the Modem to send
mobile-originated SMS messages.

Syntax

Command Possible response(s)

AT+CGSMS=[<service>] OK
or:
+CME ERROR: <err>

Page 66 of 165
 AT+CGSMS? +CGSMS: <service>

OK

AT+CGSMS=? +CGSMS: (list of currently available <service>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes < 1s

Defined Values

<service>: integer type; indicates the service or service preference to be used. The default value is manufacturer specific.
0 Packet Domain

1 Circuit switched; Note: Suggest use this one as Default setting

2 Packet Domain preferred (use circuit switched if GPRS not available)

3 Circuit switched preferred (use Packet Domain if circuit switched not available)

7.1.16 +CMGS, Send SMS to Network

Description

This command sends an SMS from the Modem to the network. The message reference value <mr> is
returned to the Modem upon successful delivery of the message.
Valid <toda> will be any value between 128-255.
The header parameters in TEXT mode will be set according to CSMP settings.

Syntax

Command Possible response(s)

If text mode (+CMGF=1): if text mode (+CMGF=1) and sending successful:

AT+CMGS=<da>[,<toda>]<CR>text is +CMGS: <mr>[,<scts>]

entered<ctrl-Z/ESC> OK

If PDU mode (+CMGF=0): if PDU mode (+CMGF=0) and sending successful:

AT+CMGS=<length><CR> +CMGS: <mr>

PDU is entered<ctrl-Z/ESC> OK

Page 67 of 165
 Command Possible response(s)
if sending fails:

+CMS ERROR: <err>

AT+CMGS=? OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes <60s

Defined Values

<da>: string type;Destination address in quoted string. This field contains a single MIN number.
<toda>: integer type; Type of DA. Value between 128-255 (according to GSM 03.40, 9.1.2.5). If this field is not given

and first character of <da> is '+' ,<toda> will be 145, otherwise 129.

<length>: integer type; Size of message in PDU mode format, in octets, excluding SMSC data.

<mr>: integer type; Sent message reference number.

7.1.17 +CSCB, Cell Broadcast Messages

Description

This command handles the selection of cell broadcast message types and data coding schemes received
by the Modem.

Syntax

Command Possible response(s)

AT+CSCB=[<mode>[,<mids>[,<dcss>]]] If mode=0 and <mids>is not specified, then no channels are
accepted, and the Modem channel/mid list is cleared.

OK

or:
+CMS ERROE: <err>

AT+CSCB? +CSCB: <mode>,<mids>,<dcss>

OK

AT+CSCB=? +CSCB: (list of supported <mode>s)

Page 68 of 165
 Command Possible response(s)
OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes < 1s

Defined Values

<mode>: integer type

0 message types specified in <mids> and <dcss> are accepted

1 message types specified in <mids> and <dcss> are not accepted; Default value

<mids>: string type and range is 0-65535; all different possible combinations of CBM message identifiers (refer <mid>)

(default is empty string); e.g. "0,1,5,320-478,922"

<dcss>: string type and range is 0-255; all different possible combinations of CBM data coding schemes (refer <dcs>)

(default is empty string); e.g. "0-3,5"

7.1.18 +CSVM, Set Voice Mail Server

Description

This command handles the selection of the number to the voice mail server. The new value should also
remain after power cycle.

Syntax

Command Possible response(s)

AT+CSVM=<mode>[,<number>[,<type>]] OK

or:

+CME ERROR: <err>

AT+CSVM=? +CSVM: (list of supported <mode>s),(list of supported <type>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Page 69 of 165
 Yes No Yes Yes < 1s

Defined Values

<mode>: integer type;

0 Disable the voice mail number; Default value

1 Enable the voice mail number.

<number>: string type; Character string <0..9,+>

<type>: integer type; Type of address octet in integer format (refer 3GPP TS 24.008 subclause 10.5.4.7); default 145

when dialling string includes international access code character "+", otherwise 129.
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 3GPP TS 24.008 sub clause 10.5.4.7

8 SIM TOOL KIT Raw Mode Commands

8.1 Raw Mode Commands Lists

8.1.1+CUSATR, Read USAT Profile

Description

This command is used to read USAT profile.

Syntax

Command Possible response(s)

AT+CUSATR[=<profile_storage>] +CUSATR: <profile_storage>,<profile>[<CR><LF>+CUSATR:

profile_storage>,<profile>[...]]

or

+CME ERROR: <err>

AT+CUSATR=? +CUSATR: (list of supported <profile_storage>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Page 70 of 165
 No Yes Yes Yes < 1s

Defined Values

<profile_storage>:integer type

0 TE profile that can be set with +CUSATW.

1 MT profile that can be set with +CUSATW.

2 MT default profile that reflects the inherent, default supported facilities of the MT.

3 UICC profile that reflects the currently active UICC profile that was sent to the UICC in the last TERMINAL

PROFILE command
4 UICC EFUST. The elementary file that indicates services available in the USIM.

5 List of MT only facilities (facilities that are not allowed to be assigned to the TE, see 3GPP TS 31.111 [92]).

<profile>: string type with hexadecimal character format. The profile describing the supported facilities of the referenced
<profile_storage> as specified for the Terminal Profile in 3GPP TS 31.111 [92] or for the related EF in 3GPP

TS 31.102 [59].

8.1.2CUSATW, Write USAT Profile

Description

This command is used to write USAT profile.

Upon an attempt to store or reset a profile that conflicts with an already stored profile or the list of MT only
facilities, the operation fails and the profile referred to by command parameter <profile_storage> remains
unchanged. The MT responds with +CUSATW :<profile_storage>,<conflict_profile> where
<profile_storage> refers the conflicting profile followed by the final result code +CME ERROR: 3
(Operation not allowed). The rules for detecting conflicts are defined in 3GPP TS 31.111 [92].
Successful execution of the command does not result in any information response.

Syntax

Command Possible response(s)

AT+CUSATW[=<profile_storage>[,<profile>]] +CUSATW: <profile_storage>,<conflict_profile>[<CR><LF>

+CUSATW: <profile_storage>,<conflict_profile>
[...]]

or

+CME ERROR: <err>

AT+CUSATW=? +CUSATW: (list of supported <profile_storage>s)

Page 71 of 165
 Command Possible response(s)
OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<profile_storage>: integer type

0 TE. Refers profile storage for the facilities supported by the TE. Default value is a blank profile with all bits set
to zero.

1 MT. Refers profile storage for the facilities to be supported by MT, which can be a subset of the default MT

facilities (see +CUSATW). TheTE can choose to register a subset of the MT default profile, typically
omitting facilitiesalso supported by the TE profile. Default value is the MT default profile.

5 Refers to a conflict between the TE profile and the list of MT only facilities.

Note: Value 5 for <profile_storage> will be supported only in response direction.

<profile>: string type with hexadecimal character format. The profile describing the supported USAT facilities of the

referenced <profile_storage> as specified for the Terminal Profile in 3GPP TS 31.111 [92].

<conflict_profile>: string type with hexadecimal character format. A bitwise AND of two profiles, showing the conflicts,

that is, USAT facilities supported by both profiles. See description ofTerminal Profile in 3GPP TS 31.111

8.1.3+CUSATD, Profile download upon start-up

Description

This command is used to determine to download which USAT profile during next bootup.
This command determines if, and optionally which profile should be downloaded to the UICC
automatically upon startup. If, prior to a restart/start-up, the +CUSATD settings have not been altered,
then the default settings determine the behaviour upon start-up.
However, if the parameters of +CUSATD has been set to other than default and then a restart is
performed (e.g. by +CFUN), these values determine the behaviour. This is true for one restart only after
altering +CUSATD parameters as they are always reset to default at the end of the next UICC start-up (i.e.
when the USIM initialisation as specified in 3GPP TS 31.102 [98] has been completed).
The command without parameters resets the parameters to their default values.

Page 72 of 165
The command can be used if the UICC is already in active state upon +CUSATA and the UICC does not
support the "Additional TERMINAL PROFILE after UICC activation" feature (see 3GPP TS 31.111 [92]).
+CUSATD=<download>,1 also enables the unsolicited result code +CUSATS: <UICC_state>. The MT
uses this unsolicited result code to indicate that a profile download is performed (setting +CUSATD=0,1 or
+CUSATD=1,1) or that it is ready for profile download (setting +CUSATD=2,1). In both cases, the MT also
indicates the end of UICC start-up by the unsolicited result code +CUSATS: 4. If the UICC is awaiting PIN
verification during start-up, this is also reported.
When using +CUSATD=1, the +CUSATA=1 command has to be used to enable TE profile facility handling
after restart. In the time between profile download and issuance of +CUSATA=1, the UICC may already
attempt to issue proactive commands. The MT will not send these to the TE, but rather give the UICC the
response "terminal currently unable to process command" autonomously. The UICC may implement only
a limited number of retries, which can potentially leave USAT in an unwanted state if the +CUSATA=1
command arrives late.

Syntax

Command Possible response(s)

AT+CUSATD=[<download>[,<reporting>]] OK

or

+CME ERROR: <err>

AT+CUSATD=? +CUSATD: (list of supported <download>s),(list of supported

<reporting>s)
OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes <3s

Defined Values

<download>:integer type. Parameter decides when/if to perform a profile download to UICC and which profile to
download. The default value is implementation specific.

0 Download MT default profile automatically during next start-up.

1 Download the combined TE and MT profile (merger of the profiles written by +CUSATW) automatically during

Page 73 of 165
 next start-up. The rules for merging profiles are defined in 3GPP TS 31.111 [92].

2 Halt next UICC start-up when ready for profile download. Profile to download will be selected and download
will be triggered by +CUSATA.

<reporting>:integer type. Parameter enables unsolicited result code +CUSATS: <UICC_state> to notify the TE about a

new state during start-up.

0 Disable +CUSATS, i.e. no notification.

1 Enable +CUSATS, i.e. notify TE.

<UICC_state>:integer type. Parameter reports that the UICC entered a new state during start-up or that the UICC ended
startup and entered active state.

1 UICC start-up halted and ready for profile download. This state is reached if +CUSATD=2 was issued before

restart. UICC start-up will continue upon +CUSATA=2 or +CUSATA=3.

2 Profile download completed, UICC startup continuing.

3 UICC awaiting PIN verification.

4 UICC active.

8.1.4+CUSATA, Activate USAT profile

Description

This command is used to activate USAT profile.

A positive result upon a +CUSATA=1 or +CUSATA=3 command (also) enables TE profile facility handling
via unsolicited result codes +CUSATP: <proactive_command> and +CUSATEND. The MT uses the
unsolicited result code +CUSATP: <proactive_command> to forward to the TE proactive commands
issued by the UICC. The unsolicited result code +CUSATEND is issued by the MT when the UICC
indicates that the proactive command session is terminated, i.e. in response to a USAT terminal response,
the UICC indicates that no other USAT proactive command is pending. Lastly, terminal responses to the
proactive commands can now be issued with +CUSATT=<terminal_response> and envelope commands
can be issued with +CUSATE=<envelope_command>.

If the action requested by the +CUSATA command can not be performed, the information response
+CUSATA: <UICC_state>,[<additional_profile_support>] is returned with appropriate values, followed by
the final result code +CME ERROR: 4 (Operation not supported) in case the UICC does not support USAT
at all, or the final result code +CME ERROR: 3 (Operation not allowed) in all other cases.

If the UICC is already in active state and the UICC does not support the "Additional TERMINAL PROFILE
after UICC activation" feature (see 3GPP TS 31.111 [92]), the TE has the option to perform a reset of the

Page 74 of 165
UICC or use +CFUN to get back to an initial non-active UICC state. The +CUSATD command can be
used to set profile handling upon the next restart.

All USAT proactive commands that the MT does not process itself and all terminal responses from the TE
are transparently forwarded by the MT. The routing mechanism for USAT commands supported by both
entities is specified in 3GPP TS 31.111 [92].

Syntax

Command Possible response(s)

AT+CUSATA[=<activation>] +CUSATA: <UICC_state>[,<additional_profile_support>]
OK

or

+CME ERROR: <err>

AT+CUSATA=? +CUSATA: (list of supported <activation>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes <3s

Defined Values

<activation>: integer type.

0 Return status information only, in information

response:+CUSATA:<UICC_state>[,<additional_profile_support>].

1 Enable TE profile facility handling only, no profile download. This action can only be used if the combined TE

and MT profile was downloaded during start-up (setting +CUSATD=1).

2 Download MT default profile.

3 Download the combined TE and MT profile (merger of the profiles written by +CUSATW) an enable TE profile

facility handling. The rules for merging profiles are defined in3GPP TS 31.111 [92].
<UICC_state>:integer type. Parameter reports that the UICC entered a new state during start-up or that the UICC ended

startup and entered active state.

1 UICC start-up halted and ready for profile download. This state is reached if +CUSATD=2 was issued before

Page 75 of 165
 restart. UICC start-up will continue upon +CUSATA=2 or+CUSATA=3.

2 Profile download completed, UICC startup continuing.

3 UICC awaiting PIN verification.

4 UICC active.

<additional_profile_support>:integer type. Indicates whether the UICC supports the "Additional TERMINAL PROFILE
after UICC activation" feature (see 3GPP TS 31.111 [92]). The value may not be available during early

phases of start-up.

0 No support.
1 Supported.

<proactive_command>: string type with hexadecimal character format. Proactive command as defined in 3GPPTS 31.111

[92], consisting of the full BER-TLV data object.

8.1.5+CUSATT, Send USAT terminal response

Description

This command is used to send Terminal Profile.

Syntax

Command Possible response(s)

AT+CUSATT=<terminal_response> OK

or

+CME ERROR: <err>

AT+CUSATT=? OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes <2s

Defined Values

<terminal_response>: string type with hexadecimal character format. Terminal response to a proactive command as
defined in 3GPP TS 31.111 [92], consisting of the full BER-TLV data object.

Page 76 of 165
 8.1.6+CUSATE, Send USAT envelope command
Description

This command is used to send USAT envelope command.

Syntax

Command Possible response(s)

AT+CUSATE=<envelope_command> +CUSATE: <envelope_response>[,<busy>]
OK

or

+CME ERROR: <err>

AT+CUSATE=? OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes <2s

Defined Values

<envelope_command>: string type with hexadecimal character format. Envelope command as defined in 3GPPTS 31.111

[92], consisting of the full BER-TLV data object.

<envelope_response>: string type in hexadecimal character format. Response to the envelope command as defined in

3GPP TS 31.111 [92], consisting of the full BER-TLV data object. Empty if the UICC does not

provide response data.

<busy>: integer type.

0 UICC indicated normal ending of the command.

1 UICC responded with USAT is busy, no retry by the MT.

2 UICC responded with USAT is busy even after one or more retries by the MT.

8.1.7+STKPROF, Reading and changing the terminal profile

Description

This command allows reading and changing the terminal profile data. The terminal profile sent by external
STK client states the facilities relevant to SIM Application Toolkit that is supported.

Page 77 of 165
Syntax

Command Possible response(s)

AT+STKPROF=<length>,<data> OK
or

+CME ERROR: <err>

AT+STKPROF? +STKPROF: <length>,<data>

e.g. +STKPROF=4,"1F7F"

OK

AT+STKPROF=? OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes <2s

Defined Values

<length>: integer type; length of the characters that are sent to TE in <data>

Note: <length> set to 0 forces a reset to the default terminal profile stored in the ME.

<data>: string type with hex format; terminal profile data.

9 Access and security

9.1 Commands

9.1.1A/, Repeat Last Command

Description

This command repeats the last command. It is not necessary to press <Enter> after this command.

Syntax

Command Possible response(s)

Page 78 of 165
 A/
Repeats last command

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

None

9.1.2AT, Check AT Communication

Description

This command only returns OK.

Syntax

Command Possible response(s)

AT OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

None

9.1.3+CPIN, Enter PIN for Unlocking SIM or Enter PUK for

Unblocking SIM
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

Page 79 of 165
PIN request is pending, no action is taken towards MT and an error message, +CME ERROR, is returned
to TE. Refer CME ERROR 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 the currently selected UICC should be a USIM and the SIM PIN then
represents the PIN of the selected USIM. See 3GPP 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, +CPINR, +CDIS (read and test command only), and +CIND (read and test command
only). It is implementation specific whether additional commands can be accepted when MT is
pending SIM PIN, SIM PUK, or PH-SIM.
Read command returns an alphanumeric string indicating whether some password is required or not.

Syntax

Command Possible response(s)

AT+CPIN=<pin>[,<newpin>] OK

or

+CME ERROR: <err>

AT+CPIN?
+CPIN: <code>

OK

or:

+CME ERROR: <err>

AT+CPIN=? OK

Page 80 of 165
Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes < 1s

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

Page 81 of 165
 9.1.4+TPIN, Query Number of Remaining SIM PIN/PUK
Entering Attempts
Description

This command returns the number of remaining attempts of entering the PIN and PUK for the SIM card in
use. The command returns the number of remaining attempts for PIN1 (CHV1), PIN2 (CHV2), PUK1
(unblock CHV1) and PUK2 (unblock CHV2).

Number of available attempts is provider dependant. Typically it is 3 attempts for PIN, 10 attempts for
PUK.

This command will return error if SIM is not inserted.

Syntax

Command Possible response(s)

AT+TPIN?
+TPIN: <chv1>,<unb1_chv1>,<chv2>,<unb1_chv2>

or:

+CME ERROR: <err>

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes < 1s

Defined Values

<chv1>: integer ype; number of remaining PIN attempts

<chv2>: integer ype; number of remaining PIN2 attempts

<unbl_chv1>: integer ype; number of remaining PUK attempts

<unbl_chv2>: integer ype; number of remaining PUK2 attempts

9.1.5+CPWD, Change Password

Description

This command sets a new password for the facility lock. The password can only be changed once the
required facility is enabled by the +CLCK command.
A password can be changed only if the provided password <oldpwd> has been verified. The entered

Page 82 of 165
password <newpwd> must also comply to the password rules. The facility value <fac> is not
case-sensitive. In the password value, letters are not allowed.

Syntax

Command Possible response(s)

AT+CPWD=<fac>,<oldpwd>,<newpwd>
OK

or:

+CME ERROR: <err>

AT+CPWD=?
+CPWD: list of Supported (<fac>,<pwdlength>)s

OK

or:

+CME ERROR: <err>

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes < 1s

Defined Values

<fac>: string type

"SC" SIM (lock SIM/UICC card installed in the currently selected card slot) (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 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 clause 2)
"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)
"P2" SIM PIN2

Page 83 of 165
<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

9.1.6+CLCK, Facility Lock

Description

This command locks, unlocks or interrogates a Modem or a network facility <fac> (any kind of call barring
program).

A password is mandatory for performing locking and unlocking actions, but not for querying. The features
of the Modem that are affected by this are fixed dialing list.

When querying the status of a single call barring program <mode>=2, the <status> for each call type will
be returned.

For <fac>="SC", SIM Card PIN setting and for <fac>="FD", SIM Fixed Dialing memory setting, the
<class>is irrelevant (For more information about <class>, refer to the following table shows the +CLCK
parameters.). For “SC”, the <passwd> is SIM PIN. For “FD”, the <passwd> is SIM PIN2.

Syntax

Command Possible response(s)

AT+CLCK=<fac>,<mode>[,<passwd>[,<classx +CME ERROR: <err>
>]] when <mode>=2 and command successful:

+CLCK: <status>[,<class1>

[<CR><LF>+CLCK: <status>,<class2>

[...]]

OK

AT+CLCK=? +CLCK: (list of supported <fac>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes < 1s

Page 84 of 165
Defined Values

<fac>: string type

"SC" SIM (lock SIM/UICC card installed in the currently selected card slot) (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 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 clause 2)

"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)

"PS" PH-SIM (lock PHone to SIM/UICC card installed in the currently selected card slot) (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)

"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>: integer type

0 unlock

1 lock

2 query status

<status>: integer type

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 - voice, data and fax):
1 voice (telephony)

Page 85 of 165
 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

9.1.7+CPINR, Remaining PIN Retries

Description

Set command cause the MT to return the number of remaining PIN retries for the MT passwords with
intermediate result code +CPINR: <cod>,<retries>[,<default_retries>] for standard PINs. One line with
one intermediate result code is returned for every <cod> selected by <sel_code>. When execution
command is issued without the optional parameter <sel_code>, intermediate result codes are returned for
all <cod>s. In the intermediate result codes, the parameter <default_retries> is an optional (manufacturer
specific) parameter, per <cod>.

Syntax

Command Possible response(s)

AT+CPINR[=<sel_code>] OK
Or

+CME ERROR: <err>

AT+CPINR=? OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes < 1s

Defined Values

<retries>: integer type. Number of remaining retries per PIN.

Page 86 of 165
<default_retries>: integer type. Number of default/initial retries per PIN.

<code>: Type of PIN. All values listed under the description of the AT+CPIN command, <code> parameter, except
'READY'.

<ext_code>: Extended, manufacturer specific codes.

<sel_code>: String type. Same values as for the <code> and <ext_code> parameters. These values are strings and shall be
indicated within double quotes. It is optional to support wildcard match by '*', meaning match any

(sub-)string.

Example: AT+CPINR="SIM*" will return the lines:

+CPINR: SIM PIN,<retries>,<default_retries>

+CPINR: SIM PUK,<retries>,<default_retries>

+CPINR: SIM PIN2,<retries>,<default_retries>

+CPINR: SIM PUK2,<retries>,<default_retries>

9.1.8+CSIM, Generic SIM Access

Description

This command allows a direct control of the SIM by a distant application on the TE.

Syntax

Command Possible response(s)

AT+CSIM=<length>,<command> +CSIM: <length>,<response>

OK
Or

+CME ERROR: <error>

AT+CSIM=? OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes <2s

Defined Values

<length>: integer type; length of the characters that are sent to TE in <command> or <response> (two times the actual

Page 87 of 165
 length of the command or response)

<command>: command passed on by the MT to the SIM in the format as described in 3GPP TS 51.011 (hexadecimal
character format; refer +CSCS)

<response>: response to the command passed on by the SIM to the MT in the format as described in

3GPP TS 51.011 (hexadecimal character format; refer +CSCS)

9.1.9+CRSM, Restricted SIM Access

Description

This command provides limited access to the Elementary Files on the SIM. Access to the SIM database is
restricted to the commands which are listed at <command>. All parameters of AT+CRSM are used as
specified by 3GPP TS 51.011(2G) and TS 31.101(3G). As response to the command, the Modem sends
the actual SIM information parameters and response data. Error result code "+CME ERROR" may be
returned if the command cannot be transferred to the SIM, e.g. if the SIM is not inserted, or defected, or
PIN1/PUK authentication required, or required input parameters not present. However, failure in the
execution of the command in the SIM is reported in <sw1> and <sw2> parameters.
Some of the AT+CRSM commands require PIN/PIN2 authentication.

Syntax

Command Possible response(s)

AT+CRSM=<command>[,<file_id>[,<P1>,<P2 +CRSM: <sw1>,<sw2>[,<response>]

>,<P3>[,<data>[,<pathid>]]]] OK
or:

+CME ERROR: <err>

AT+CRSM=? OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes <2s

Defined Values

<command>: (command passed on by the MT to the SIM; refer 3GPP TS 51.011 [28]):

Page 88 of 165
 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 3GPP TS 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 3GPP TS 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. They can be refer

TS102.221

<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 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.

Page 89 of 165
10 Network
10.1 Network Commands

10.1.1 +CSQ, Signal Strength

Description

This command displays the received signal strength indication <rssi> and channel bit error rate <ber>
from the Modem.

Syntax

Command Possible response(s)

AT+CSQ
+CSQ: <rssi>,<ber>

OK

AT+CSQ?
+CSQ: <rssi>,<ber>

OK

AT+CSQ=?
+CSQ: (list of supported <rssi>s),(list of supported <ber>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<rssi>: integer type

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>: integer type; channel bit error rate (in percent)

Page 90 of 165
 0...7 as RXQUAL values in the table in 3GPP TS 45.008 subclause 8.2.4

99 not known or not detectable

10.1.2 +CESQ, Extended Signal Quality

Description

Execution command returns received signal quality parameters. If the current serving cell is not a GERAN
cell, <rxlev> and <ber> are set to value 99. If the current serving cell is not a UTRA FDD or UTRA TDD
cell, <rscp> is set to 255. If the current serving cell is not a UTRA FDD cell, <ecno> is set to 255. If the
current serving cell is not an E-UTRA cell, <rsrq> and <rsrp> are set to 255.

Syntax

Command Possible response(s)

AT+CESQ +CESQ: <rxlev>,<ber>,<rscp>,<ecno>,<rsrq>,<rsrp>
OK

or

CME ERROR: <error>

AT+CESQ=? +CESQ: (list of supported <rxlev>s),(list of supported

<ber>s),(list of supported <rscp>s),(list of supported

<ecno>s),(list of supported <rsrq>s),(list of

supported <rsrp>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<rxlev>: integer type, received signal strength level (see 3GPP TS 45.008 subclause 8.1.4).

0 rssi< -110 dBm

1 -110 dBm  rssi < -109 dBm

2 -109 dBm  rssi < -108 dBm

: : : :

Page 91 of 165
 61 -50 dBm  rssi < -49 dBm

62 -49 dBm  rssi < -48 dBm

63 -48 dBm  rssi

99 not known or not detectable

<ber>: integer type; channel bit error rate (in percent)

0...7 as RXQUAL values in the table in 3GPP TS 45.008 subclause 8.2.4

99 not known or not detectable

<rscp>: integer type, received signal code power (see 3GPP TS 25.133 subclause 9.1.1.3 and
3GPP TS 25.123 subclause 9.1.1.1.3).

0 rscp < -120 dBm

1 -120 dBm  rscp < -119 dBm

2 -119 dBm  rscp < -118 dBm

: : : :

94 -27 dBm  rscp < -26 dBm

95 -26 dBm  rscp < -25 dBm

96 -25 dBm  rscp

255 not known or not detectable

<ecno>: integer type, ratio of the received energy per PN chip to the total received power spectral density (see

3GPP TS 25.133 subclause).

0 Ec/Io < -24 dB

1 -24 dB  Ec/Io < -23.5 dB

2 -23.5 dB  Ec/Io < -23 dB

: : : :
47 -1 dB  Ec/Io < -0.5 dB

48 -0.5 dB  Ec/Io < 0 dB

49 0 dB  Ec/Io

255 not known or not detectable

<rsrq>: integer type, reference signal received quality (see 3GPP TS 36.133 subclause 9.1.7).

0 rsrq < -19.5 dB

1 -19.5 dB  rsrq < -19 dB

2 -19 dB  rsrq < -18.5 dB

: : : :
32 -4 dB  rsrq < -3.5 dB

33 -3.5 dB  rsrq < -3 dB

Page 92 of 165
 34 -3 dB  rsrq

255 not known or not detectable

<rsrp>: integer type, reference signal received power (see 3GPP TS 36.133 subclause 9.1.4).

0 rsrp < -140 dBm

1 -140 dBm  rsrp < -139 dBm

2 -139 dBm  rsrp < -138 dBm

: : : :

95 -46 dBm  rsrp < -45 dBm

96 -45 dBm  rsrp < -44 dBm

97 -44 dBm  rsrp

255 not known or not detectable

10.1.3 +CRLP, Radio Link Protocol

Description

This command is used to change the Radio Link Protocol(RLP) parameters used when non-transparent
data calls are originated.

Syntax

Command Possible response(s)

AT+CRLP=[<iws>[,<mws>[,<T1>[,<N2>[, OK

<ver>[,<T4>]]]]]] or:
+CME ERROR: <err>

AT+CRLP? +CRLP: <iws>,<mws>,<T1>,<N2>[,<ver1>[,<T4>]][<CR><LF>

+CRLP: <iws>,<mws>,<T1>,<N2>[,<ver2>[,<T4>]][...]]

OK

AT+CRLP=? +CRLP: (list of supported <iws>s),(list of supported <mws>s),

(list of supported <T1>s),(list of supported <N2>s)[,<ver1>

[,(list of supported <T4>s)]][<CR><LF>

+CRLP: (list of supported <iws>s),(list of supported

<mws>s),(list of supported <T1>s),(list of supported <N2>s)

[,<ver2>[,(list of supported <T4>s)]]

[...]]

Page 93 of 165
 OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<ver>, <verx>: RLP version number in integer format; when version indication is not present it shall equal 0

NOTE: Version 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>: integer type; IWF to MS window size. Default value is 61 when RLP<ver0> and RLP<ver1>. Default value is
240 when RLP<ver2>

<mws>: integer type; MS to IWF window size. Default value is 61 when RLP<ver0> and RLP<ver1>. Default value is

240 when RLP<ver2>

<T1>: integer type; Acknowledgement timer T1.Default value is48when RLP<ver0> and RLP<ver1>. Default value is 52

when RLP<ver2>

<N2>: integer type; Retransmission attempts N2 in integer format (refer to GSM 04.22 subclause5.4.3) . Default: 6

<T4>: integer type; re-sequencing period T4. T1 and T4 are in units of 10ms

10.1.4 +CREG, Network Registration Status

Description

Set command controls the presentation of an unsolicited result code as below:

+CREG: <stat> when <n>=1 and there is a change in the MT’s circuit mode network registration status
in GERAN/UTRAN/E-UTRAN.
or
+CREG: <stat>[,[<lac>],[<ci>],[<AcT>]] when <n>=2 and there is a change of the network
cell in GERAN/UTRAN/E-UTRAN. The parameters <AcT>, <lac> and <ci> are sent only if available.
or
+CREG: <stat> [, <lac>,<ci>[,<AcT>[,<reject type>[,<reject cause>]]]] when <n>=3,when available, when
the value of <stat> changes.

Read command returns the status of result code presentation and an integer <stat> which shows

Page 94 of 165
whether the network has currently indicated the registration of the MT. Location information elements
<lac>, <ci> and <AcT>, if available, are returned only when <n>=2 and MT is registered in the network.
The parameters [,<cause_type>,<reject_cause>], if available, are returned when <n>=3.

Syntax

Command Possible response(s)

AT+CREG=[<n>] OK
or:

+CME ERROR: <err>

AT+CREG? +CREG: <n>,<stat> [,<lac>,<ci>[,<AcT>[,<reject_type>

[,<reject_cause>]]]]

OK

AT+CREG=? +CREG: (list of supported <n>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<n>: integer type; It is only applicable to L850 with <n>=3

0 disable network registration unsolicited result code; Default value

1 enable network registration unsolicited result code +CREG: <stat>

2 enable network registration and location information unsolicited result code

+CREG: <stat>[,[<lac>],[<ci>],[<AcT>]]

3 enable network registration, location information and cause value information unsolicited result code

+CREG: <stat>[,[<lac>],[<ci>],[<AcT>][,<cause_type>,<reject_cause>]];

<stat>: integer type; circuit mode 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 (e.g. out of GERAN/UTRAN/E-UTRAN coverage)

Page 95 of 165
 5 registered, roaming

6 registered for "SMS only", home network (applicable only when <AcT> indicates E-UTRAN)
7 registered for "SMS only", roaming (applicable only when <AcT> indicates E-UTRAN)

8 attached for emergency bearer services only(see NOTE 2) (not applicable)

9 registered for "CSFB not preferred", home network (applicable only when <AcT> indicates E-UTRAN)
10 registered for "CSFB not preferred", roaming (applicable only when <AcT> indicates E-UTRAN)

<lac>: string type; two byte location area code (when <AcT> indicates value 0 to 6), or tracking area code (when
<AcT>indicates value 7). In hexadecimal format (e.g. "00C3" equals 195 in decimal).

<ci>: string type; four byte GERAN/UTRAN/E-UTRAN cell ID in hexadecimal format.

<AcT>: integer type; access technology of the serving cell

0 GSM

1 GSM Compact

2 UTRAN
3 GSM w/EGPRS (see NOTE 3)

4 UTRAN w/HSDPA (see NOTE 4)

5 UTRAN w/HSUPA (see NOTE 4)

6 UTRAN w/HSDPA and HSUPA (see NOTE 4)

7 E-UTRAN

NOTE 3: 3GPP TS 44.060 [71] specifies the System Information messages which give the information about

whether the serving cell supports EGPRS.

NOTE 4: 3GPP TS 25.331 [74] specifies the System Information blocks which give the information about whether

the serving cell supports HSDPA or HSUPA.

<reject_type>: integer type; indicates the type of <reject_cause>.

0 Indicates that <reject_cause> contains an MM cause value, see 3GPP TS 24.008 [8] Annex G.

1 Indicates that <reject_cause> contains a manufacturer specific cause.

<reject_cause>: integer type; contains the cause of the failed registration. The value is of type as defined by

<cause_type>.

10.1.5 +CGREG, GPRS Network Registration

Description

The set command controls the presentation of an unsolicited result code +CGREG: <stat> when <n>=1
and there is a change in the MT's GPRS network registration status in GERAN/UTRAN, or unsolicited

Page 96 of 165
result code +CGREG: <stat>[,[<lac>],[<ci>],[<AcT>],[<rac>]] when <n>=2 and there is a
change of the network cell in GERAN/UTRAN. The parameters <AcT>, <lac>, <rac> and <ci> are
provided only if available. The value <n>=3 further extends the unsolicited result code with
[,<cause_type>,<reject_cause>], when available, when the value of <stat> changes.
The 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>, <AcT> and <rac>, if available, are returnedonly when <n>=2 and MT is registered in the
network.
Test command returns the range of supported network registration mode (i.e. <n>).

Syntax

Command Possible response(s)

AT+CGREG=[<n>] OK

or:

+CME ERROR: <err>

AT+CGREG? +CGREG: <n>,<stat>[,[<lac>],[<ci>],[<AcT>],[<rac>][,<cause_t

ype>,<reject_cause>]]

OK

AT+CGREG=?
+CGREG: (list of supported <n>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<n>: integer type

0 disable network registration unsolicited result code; Default value

1 enable network registration unsolicited result code +CGREG: <stat>

2 enable network registration and location information unsolicited result code

+CGREG: <stat>[,<[lac>,]<[ci>],[<AcT>],[<rac>]]

Page 97 of 165
 3 enable network registration, location information and GMM cause value information unsolicited result code

+CGREG: <stat>[,[<lac>],[<ci>],[<AcT>],[<rac>][,<cause_type>,<reject_cause>]]
<stat>: integer type; indicates the GPRS registration status

0 not registered, MT is not currently searching an operator to register to

1 registered, home network

2 not registered, but MT is currently trying to attach or searching an operator to register to

3 registration denied

4 unknown (e.g. out of GERAN/UTRAN coverage)

5 registered, roaming

6 registered for "SMS only", home network (not applicable)

7 registered for "SMS only", roaming (not applicable)

8 attached for emergency bearer services only (see NOTE 2) (applicable only when <AcT> indicates 2,4,5,6)

9 registered for "CSFB not preferred", home network (not applicable)

10 registered for "CSFB not preferred", roaming (not applicable)

<lac>: string type; two byte location area code in hexadecimal format (e.g. "00C3" equals 195 in decimal)

<ci>: string type; four byte GERAN/UTRAN cell ID in hexadecimal format

<AcT>: integer type; indicates the access technology of the serving cell

0 GSM

1 GSM Compact

2 UTRAN

3 GSM w/EGPRS (see NOTE 3)

4 UTRAN w/HSDPA (see NOTE 4)

5 UTRAN w/HSUPA (see NOTE 4)

6 UTRAN w/HSDPA and HSUPA (see NOTE 4)

7 E-UTRAN (not applicable)

NOTE 3: 3GPP TS 44.060 [71] specifies the System Information messages which give the information about

whether the serving cell supports EGPRS.

NOTE 4: 3GPP TS 25.331 [74] specifies the System Information blocks which give the information about whether
the serving cell supports HSDPA or HSUPA.

<rac>: string type; one byte routing area code in hexadecimal format

<cause_type>: integer type; indicates the type of <reject_cause>.

0 Indicates that <reject_cause> contains a GMM cause value, see 3GPP TS 24.008 [8] Annex G.

1 Indicates that <reject_cause> contains a manufacturer-specific cause.

Page 98 of 165
<reject_cause>: integer type; contains the cause of the failed registration. The value is of type as defined by

<cause_type>.

10.1.6 +CEREG, EPS Network Registration status

Description

The set command controls the presentation of an unsolicited result code +CEREG:<stat> when <n>=1
and there is a change in the MT's EPS network registration status,or code +CEREG:
<stat>[,<tac>,<ci>[,<AcT>]] when <n>=2 and there is a change of the network cell, code +CEREG:
<stat>[,<tac>[,<ci>[,<AcT>[,<reject type>[,<reject cause>]]]]] when <n>=3.

Syntax

Command Possible response(s)

AT+CEREG=[<n>] OK

or:

+CME ERROR: <err>

AT+CEREG? +CEREG: <n>,<stat>[,[<tac>],[<ci>],[<AcT>[,<cause_type>,<rej

ect_cause>]]]

OK

AT+CEREG=? +CEREG: (list of supported <n>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<n>: integer type

0 disable network registration unsolicited result code; Default value

1 enable network registration unsolicited result code +CEREG: <stat>

2 enable network registration and location information unsolicited result code

+CEREG: <stat>[,[<tac>],[<ci>],[<AcT>]]

Page 99 of 165
 3 enable network registration, location information and EMM cause value information unsolicited result code

+CEREG: <stat>[,[<tac>],[<ci>],[<AcT>][,<cause_type>,<reject_cause>]]
<stat>: integer type; indicates the EPS registration status

0 not registered, MT is not currently searching an operator to register to

1 registered, home network

2 not registered, but MT is currently trying to attach or searching an operator to register to

3 registration denied

4 unknown (e.g. out of E-UTRAN coverage)

5 registered, roaming

6 registered for "SMS only", home network (not applicable)

7 registered for "SMS only", roaming (not applicable)

8 attached for emergency bearer services only (See NOTE 2)

9 registered for "CSFB not preferred", home network (not applicable)

10 registered for "CSFB not preferred", roaming (not applicable)

<tac>: string type; two byte tracking area code in hexadecimal format (e.g. "00C3" equals 195 in decimal)

<ci>: string type; four byte E-UTRAN cell ID in hexadecimal format

<AcT>: integer type; indicates the access technology of the serving cell
0 GSM (not applicable)

1 GSM Compact (not applicable)

2 UTRAN (not applicable)

3 GSM w/EGPRS (see NOTE 3) (not applicable)

4 UTRAN w/HSDPA (see NOTE 4) (not applicable)

5 UTRAN w/HSUPA (see NOTE 4) (not applicable)

6 UTRAN w/HSDPA and HSUPA (see NOTE 4) (not applicable)

7 E-UTRAN

NOTE 3: 3GPP TS 44.060 [71] specifies the System Information messages which give the information about

whether the serving cell supports EGPRS.

NOTE 4: 3GPP TS 25.331 [74] specifies the System Information blocks which give the information about whether

the serving cell supports HSDPA or HSUPA.

<cause_type>: integer type; indicates the type of <reject_cause>.

0 Indicates that <reject_cause> contains an EMM cause value, see 3GPP TS 24.301 [83] Annex A.

1 Indicates that <reject_cause> contains a manufacturer-specific cause.

<reject_cause>: integer type; contains the cause of the failed registration. The value is of type as defined by

<cause_type>.

Page 100 of 165

 10.1.7 +WS46, Select Wireless Network
Description

This command is used to configure the RAT.

Syntax

Command Possible response(s)

AT+WS46=[<n>] OK

or:

+CME ERROR: <err>

AT+WS46? <n>

OK

AT+WS46=? (list of supported <n>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes <2s

Defined Values

<n>: integer type

If<n> value of set command

22 3GPP System (GERAN, UTRAN and E-UTRAN) for triple mode stack. Preferred Network selection will be
based on the highest network generation, in the order of E-UTRAN, UTRAN and GERAN.

28 same as 22

31 same as 22

If<n> value for read command

22 UTRAN only

28 E-UTRAN only
31 UTRAN and E-UTRAN

Page 101 of 165

 10.1.8 +COPS, Operator Selection
Description

This command enables accessories to access the network registration information, and the selection and
registration of the GSM/UMTS network operator.
The Modem is registered in the Home network.
The Enhanced Operator Name String (EONS) feature enables the Modem to return the operator name
displayed on the handset.
This feature allows the SIM card to store a mapping of MCC/MNC code pairs to the displayed operator
name. As a result, several operators can share a single network while having their handsets display their
own name as the network operator.
Testing the enhanced ONS feature requires a "SIM ONS" SIM card.

Syntax

Command Possible response(s)

AT+COPS=[<mode>[,<format>[,<oper>[,< OK
AcT>]]]] or:

+CME ERROR: <err>

AT+COPS? +COPS: <mode>[,<format>,<oper>[,< AcT>]]

OK

Or

+CME ERROR: <err>

AT+COPS=? +COPS: [list of supported (<stat>,long alphanumeric <oper>,short

alphanumeric <oper>,numeric <oper>[,<AcT>])s][,,(list of

supported <mode>s),(list of supported <format>s)]

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 3Min

Page 102 of 165

Defined Values

<mode>: integer type

0 automatic (<oper> field is ignored); Default value

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>: integer type

0 long format alphanumeric <oper>; Default value

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 3GPP TS 24.008 subclause 10.5.1.3) which consists of a

three BCD digit country code coded as in ITU-T Recommendation E.212 [10] Annex A, 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>: integer type

0 unknown

1 available
2 current

3 forbidden

<AcT>: integer type; access technology selected

0 GSM

1 GSM Compact

2 UTRAN
3 GSM w/EGPRS (see NOTE 1)

4 UTRAN w/HSDPA (see NOTE 2)

5 UTRAN w/HSUPA (see NOTE 2)

6 UTRAN w/HSDPA and HSUPA (see NOTE 2)

7 E-UTRAN

Page 103 of 165

 8 CDMA

9 CDMA&EVDO
10 EVDO

11eMTC

12NB-IoT
NOTE 1: 3GPP TS 44.060 [71] specifies the System Information messages which give the information about

whether the serving cell supports EGPRS.

NOTE 2: 3GPP TS 25.331 [74] specifies the System Information blocks which give the information about whether
the serving cell supports HSDPA or HSUPA.

10.1.9 +CPLS, Selection of Preferred PLMN List

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.

Syntax

Command Possible response(s)

AT+CPLS=[<list>] OK

or:

+CME ERROR: <err>

AT+CPLS? +CPLS: <list>

OK

AT+CPLS=? +CPLS: (list of supported <list>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes < 1s

Defined Values

<list>: integer type

0 User controlled PLMN selector with Access Technology EFPLMNwAcT, if not found in the SIM/UICC then

Page 104 of 165

 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

2 HPLMN selector with Access Technology EFHPLMNwAcT

10.1.10 +CPOL, Preferred Operators

Description

This command is used to edit the PLMN selector lists in the SIM card or active application in the UICC
(GSM or USIM).

If no list has been previously selected, the EFPLMNwAcT - user controlled PLMN selector with Access
Technology list, is the one accessed by default.

Syntax

Command Possible response(s)

AT+CPOL=[<index>][,<format>[,<oper>[ OK

,<GSM_AcT>,<GSM_Compa or:

ct_AcT>,<UTRAN_AcT>,<E +CME ERROR: <err>

UTRAN_AcT>]]]

AT+CPOL? +CPOL: <index1>,<format>,<oper1>[,<GSM_AcT1>,<GSM_Compac

t_AcT1>,<UTRAN_AcT1>,<E-UTRAN_AcT1>]

[<CR><LF>+CPOL: <index2>,<format>,<oper2>[,<GSM_AcT2>,<G

SM_Compact_AcT2>,<UTRAN_AcT2>,<E-UTRAN_AcT2>]

[...]]

OK

or

+CME ERROR: <err>

AT+CPOL=? +CPOL: (list of supported <index>s),(list of supported<format>s)

OK

or:

+CME ERROR: <err>

Page 105 of 165

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes < 1s

Defined Values

<indexn>: integer type; the order number of operator in the SIM/USIM preferred operator list

<format>: integer type

0 long format alphanumeric <oper>; Default value

1 short format alphanumeric <oper>

2 numeric <oper>

<opern>: string type; <format> indicates if the format is alphanumeric or numeric (see +COPS)

<GSM_AcTn>: integer type; GSM access technology:

0 access technology not selected

1 access technology selected

<GSM_Compact_AcTn>: integer type; GSM compact access technology

0 access technology not selected

1 access technology selected

<UTRAN_AcTn>: integer type; UTRAN access technology

0 access technology not selected

1 access technology selected

<E-UTRAN_AcTn>: integer type; E-UTRAN access technology

0 access technology not selected

1 access technology selected

10.1.11 +COPN, Read Operator Names

Description

This Execution command returns the list of operator names from the ME. Each operator code
<numeric_n> that has an alphanumeric equivalent <alpha_n> in the ME memory shall be returned.

Page 106 of 165

Syntax

Command Possible response(s)

AT+COPN +COPN: <numeric1>,<alpha1>

[<CR><LF>+COPN: <numeric2>,<alpha2>

[...]]

OK
or

CME ERROR: <error>

AT+COPN=? OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Yes No Yes Yes < 1s

Defined Values

<numericn>:string type;operator in numeric format (see +COPS)

<alphan>: string type;operator in long alphanumeric format (see +COPS)

Note : If matching PLMN name is not found then numeric PLMN id (MCCMNC) will be displayed

10.1.12 +CEMODE, UE modes of operation for EPS

Description

This command is used to set the MT to operate according to the specified mode of operation for EPS.

Syntax

Command Possible response(s)

AT+CEMODE=[<mode>] OK

or

CME ERROR: <error>

AT+CEMODE? +CEMODE: <mode>

OK

AT+CEMODE=? +CEMODE: (list of supported <mode>s)

Page 107 of 165

 OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<mode>: integer type; indicates the mode of operation. The default value is depended on the target products.

0 PS mode 2 of operation

1 CS/PS mode 1 of operation.

2 CS/PS mode 2 of operation.

3 PS mode 1 of operation

NOTE: The definition for UE modes of operation can be found in 3GPP TS 24.301 [83]

11 Hardware Information
11.1 UART Parameter Commands
11.1.1 +IPR, Fixed DTE Rate
Description

This command specifies the data rate at which the DCE will accept commands. The full range of data rate
values may be reduced dependent on HW or other criteria.

Syntax

Command Possible response(s)

AT+IPR=<baud_rate> OK

or

+CME ERROR: <error>

AT+IPR? +IPR: <baud_rate>

OK

Page 108 of 165

 AT+IPR=? +IPR: (list of supported <baud_rate>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No Yes Yes Yes < 1s

Defined Values

<baud_rate>: integer type; e,g, 0 (default),300, 1200, 2400, 4800, 9600, 19200, 38400, 57600,115200,230400, 460800,

500000, 750000, 921600, 1843200, 3250000, 6000000.

Note: <baud_rate>=0 means automatic detection. And the supported auto baudrate detect as following: 9600,

19200, 38400, 57600, 115200

Note: the supported baud rate depends on the target.

11.1.2 &C, Circuit 109 Behavior

Description

This parameter determines how the state of the DCD line relates to the detection of the received line
signal from the distant end. Changing the parameters will take effect immediately in both the command
and online command states.
The DCD line is an output line that indicates the following:
In Circuit Switch Data mode an active (low) indicates that a valid carrier (data signal) was detected by the
modem (CONNECT message is received), and inactive (high) indicates idle. The AT&C command always
puts the DCD command ON, when set to 0. If the AT&C command is set to 1 then the "+++" escape
command sets the DCD signal to an inactive state and the ATO command is set to active. AT&C set to 2
sets the DCD signal OFF.
In GPRS mode, the DCD line indicates the PDP context status. PDP context active sets the DCD to active
(low); PDP context inactive sets the DCD to inactive (high). DCD is activated only when the PDP context
is achieved. DCD is de-activated when the PDP context is off.
In Local Link mode, the DCD line indicates the Local Link data status.
When AT&C is set to 0, the DCD signal is always ON. When AT&C is set to 1, the DCD is activated in
online mode. When AT&C is set to 2, the DCD is activated only when the PDP context is achieved
(temporary IP address is received).

Page 109 of 165

Syntax

Command Possible response(s)

AT&C<param> OK

or:

+CME ERROR: <err>

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<param>: integer type; And the default value is 1.

0 DCD is forced ON at all times.

1 DCD is set to ON when a CSD carrier is detected or a GPRS external session is being established or the

modementers PPP mode TE is about to send an LCP configure-request to the modem (GPRS connection is not yet

established).

DCD is set to OFF when No CSD carrier is detected or the modem has lost its GPRS connection with the

network (PDP context was deactivated and the IP address is cancelled).

2 DCD is set to ON when the modem establishes a GPRS connection with the network (PDP context is activated
and the IP address is received from the network).

DCD is set to OFF when the modem has lost its GPRS connection with the network (PDP context was

deactivated and the IP address is cancelled).

11.1.3 &D, Circuit 108 (Data Terminal Ready) behaviour

Description
This parameter determines how the DCE responds when circuit 108/2 is changed from the ON to
the OFF condition during online data state.

Syntax

Command Possible response(s)

AT&D[<value>] OK

Page 110 of 165

 or:

+CME ERROR: <err>

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<value>: integer type

0 DCE ignores circuit 108/2.Default value

1 Upon an on-to-off transition of circuit 108/2, the DCE enters online command state andissues an OK result code;

The call remains connected.

2 Upon an on-to-off transition of circuit 108/2, the DCE instructs the underlying DCE toperform an orderly

cleardown of the call.

The disposition of any data in the DCE pending transmission to the remote DCE is controlled by the +ETBM

parameter (see6.5.6) if implemented; otherwise, this data is sent before the call is cleared, unless the

remote DCE clears the call first (in which case pending data is discarded). The DCE disconnects from the line.

Automatic answer is disabled while circuit 108/2 remains off.

For MUX and MUX_INIT case:

0-3 Ignores DTR changes

4 Drops the MUX application and returns to PRE_MUX state

11.2 Clock Configuration

11.2.1 +CLK26M, 26MHz Clock Output From CLK26M
Description

This command is used to control the 26MHz clock output from CLK26M.

Syntax

Command Possible response(s)

AT+CLK26M=<n> OK

Page 111 of 165

 Command Possible response(s)
or:

+CME ERROR: <err>

AT+CLK26M? + CLK26M: <n>

OK

AT+CLK26M=? +CLK26M: (list of supported <n>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<n>: integer type

0 disable 26MHz clock output. Default value.

1 enable 26MHz clock output.

12 GPRS
12.1 GPRS Functionality

GSM 07.07 defines commands that a TE may use to control a GPRS ME via a non-multiplexed
character-stream interface. This places certain limitations on the functionality of the interface. For
example, it is not possible for the ME to send control information to the TE or for the TE to send
commands to the ME whilst the interface is in the online data state, unless the layer 2 protocol itself
supports this feature (GSM 07.60-12). However, Modem-specific escape mechanism (DTR) is provided to
enable the TE to switch the Modem into limited online command state.
The use of a multiplexed interface, (GSM 07.10), is not considered here (See “Multiplexer Feature”). The
Modem-specific escape mechanism use DTR as an escape signal (following &D parameters) and
designed for limited non network related commands. This specific mechanism purpose is to give the user
a way to retrieve the signal strength. The time limit of consecutive DTR toggles is a minimum of 90
seconds. The Modem-specific is not designed to support online command and data states both at the

Page 112 of 165

same time, therefore any wrong or extreme usage can cause unexpected behaviors. The basic GPRS
concept is be “always connected” and there is no charge for being connected (only per real data
transferred).

12.2 GPRS Commands

This section defines commands that a terminal may use to control a GPRS ME. GPRS MTs vary widely in
functionality. A class A ME might support multiple PDP-types as well as circuit-switched data, and use
multiple external networks QoS profiles. At the other extreme, a class C ME might support only a single
PDP-type using a single external network, and rely on the HLR to contain the PDP context definition. A
comprehensive set of GPRS-specific commands is defined below to provide the flexibility needed by the
more complex ME. The commands are designed to be expandable to accommodate new PDP types and
interface protocols, merely by defining new values for many of the parameters. Multiple contexts may be
activated if the interface link-layer protocol is able to support them. The commands use the extended
information and error message capabilities described in this specification. For MTs of intermediate
complexity, most commands have simplified forms where certain parameters may be omitted. For the
simplest MTs, and for backwards compatibility with existing communications software, it is possible to
control access to the GPRS using existing modem-compatible commands. This "modem compatible"
mode of operation is described below.

12.2.1 +CGCLASS, GPRS Mobile Station Class

Description

This command is used to set the Modem to operate according to the specified GPRS mobile class.
If the requested class is not supported, an ERROR or +CME ERROR response is returned. Extended
error responses are enabled by the +CMEE command.

Syntax

Command Possible response(s)

AT+CGCLASS=<class> OK

or:

+CME ERROR: <err>

AT+CGCLASS? +CGCLASS: <class>

Page 113 of 165

 OK

AT+CGCLASS=? +CGCLASS: (list of supported <class>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No Yes Yes No < 1s

Defined Values

<class>: string type; indicates the mode of operation. The default value is manufacturer specific.

A Class-A mode of operation (A/Gb mode), or CS/PS mode of operation (Iu mode) (highest mode of operation)
B Class-B mode of operation (A/Gb mode), or CS/PS mode of operation (Iu mode)

CG Class-C mode of operation in PS only mode (A/Gb mode), or PS mode of operation (Iu mode)

CC Class-C mode of operation in CS only mode (A/Gb mode), or CS (Iu mode) (lowest mode of operation)

NOTE:
<class> A means that the MT would operate simultaneous PS and CS service
<class> B means that the MT would operate PS and CS services but not simultaneously in A/Gb
mode
<class> CG means that the MT would only operate PS services
<class> CC means that the MT would only operate CS services
If the MT is attached to the PS domain when the set command is issued with a <class> = CC specified, a
PS detach shall be performed by the MT.

12.2.2 +CGDCONT, Define PDP Context

Description

The set command specifies PDP context parameter values for a PDP context identified by the (local)
context identification parameter, <cid>and also allows the TE to specify whether security protected
transmission of ESM information is requested, because the PCO can include information that requires
ciphering. There can be other reasons for the UE to use security protected transmission of ESM
information, e.g. if the UE needs to transfer an APN. 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.

Page 114 of 165

For EPS the PDN connection and its associated EPS default bearer is identified herewith.
A special form of the set command, +CGDCONT=<cid> causes the values for context number <cid> to
become undefined.
The read command returns the current settings for each defined context.
The test command returns values supported as compound values. If the MT supports several PDP types,
<PDP_type>, the parameter value ranges for each <PDP_type> are returned on a separate line.

Syntax

Command Possible response(s)

+CGDCONT=[<cid>[,<PDP_type>[,<APN>[,< OK
PDP_addr>[,<d_comp>[,<h_comp>[,<IPv4Ad or:

drAlloc>[,<request_type>[,<P-CSCF_discover +CME ERROR: <err>

y>[,<IM_CN_Signalling_Flag_Ind>]]]]]]]]]]

AT+CGDCONT? +CGDCONT: <cid>,<PDP_type>,<APN>,<PDP_addr>,<d_comp

>,<h_comp>[,<IPv4AddrAlloc>[,<request_type>[,<P-CSCF_disc

overy>[,<IM_CN_Signalling_Flag_Ind>]]]][<CR><LF>+CGDCO

NT: <cid>,<PDP_type>,<APN>,<PDP_addr>,<d_comp>,<h_com

p>[,<IPv4AddrAlloc>[,<request_type>[,<P-CSCF_discovery>[,<I

M_CN_Signalling_Flag_Ind>]]]]
[...]]

AT+CGDCONT=? +CGDCONT: (range of supported <cid>s),<PDP_type>,,,(list of

supported <d_comp>s),(list of supported <h_comp>s),(list of

supported <IPv4AddrAlloc>s),(list of supported

<request_type>s),(list of supported <P-CSCF_discovery>s),(list of

supported <IM_CN_Signalling_Flag_Ind>s)[<CR><LF>

+CGDCONT: (range of supported <cid>s),<PDP_type>,,,(list of

supported <d_comp>s),(list of supported <h_comp>s),(list of

supported <IPv4AddrAlloc>s),(list of supported

<request_type>s),(list of supported <P-CSCF_discovery>s),(list of

supported <IM_CN_Signalling_Flag_Ind>s)

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Page 115 of 165

No Yes Yes Yes < 1s

Defined Values

<cid>: integer type; 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 is returned by the test form of the

command.
NOTE 1: The <cid>s for network-initiated PDP contexts will have values outside the ranges indicated for the <cid>

in the test form of the commands +CGDCONT and +CGDSCONT.

<PDP_type>: string type; specifies the type of packet data protocol. The default value is manufacturer specific.
X.25 ITU-T/CCITT X.25 layer 3 (Obsolete)

IP Internet Protocol (IETF STD 5 [103])

IPV6 Internet Protocol, version 6 (see RFC 2460 [106])

IPV4V6 Virtual <PDP_type> introduced to handle dual IP stack UE capability. (See 3GPP TS 24.301 [83])

OSPIH Internet Hosted Octect Stream Protocol (Obsolete)

PPP Point to Point Protocol (IETF STD 51 [104])

NOTE 2: Only IP, IPV6 and IPV4V6 values are supported for EPS services.

<APN>: string type; a logical name that is used to select the GGSN or the external packet data network.If the value is

null or omitted, then the subscription value will be requested.

<PDP_addr>: string type; identifies the MT in the address space applicable to the PDP.When +CGPIAF is supported, its

settings can influence the format of this parameter returned with the read form of +CGDCONT.

NOTE 3: The value of this parameter is ignored with the set command. The parameter is included in the set
command for backwards compatibility reasons only.

<d_comp>: integer type; controls PDP data compression (applicable for SNDCP only) (refer 3GPP TS 44.065 [61])

0 off
1 on (manufacturer preferred compression)

2 V.42bis

3 V.44
<h_comp>: integer type; controls PDP header compression (refer 3GPP TS 44.065 [61] and 3GPP TS 25.323 [62])

0 off

1 on (manufacturer preferred compression)

2 RFC 1144 [105] (applicable for SNDCP only)

3 RFC 2507 [107]

4 RFC 3095 [108] (applicable for PDCP only)

Page 116 of 165

<IPv4AddrAlloc>: integer type; controls how the MT/TA requests to get the IPv4 address information

0 IPv4 address allocation through NAS signalling

1 IPv4 address allocated through DHCP

<request_type>: integer type; indicates the type of PDP context activation request for the PDP context, see

3GPP TS 24.301 (subclause 6.5.1.2) and 3GPP TS 24.008 (subclause 10.5.6.17). According to
3GPP TS 24.008 (subclause 4.2.4.2.2 and subclause 4.2.5.1.4) and

3GPP TS 24.301 (subclause 5.2.2.3.3 and subclause 5.2.3.2.2), a separate PDP context must be

established for emergency bearer services.

NOTE 4: If the PDP context for emergency bearer services is the only activated context, only emergency calls

are allowed, see 3GPP TS 23.401 subclause 4.3.12.9.

0 PDP context is for new PDP context establishment or for handover from a non-3GPP access network (how the
MT decides whether the PDP context is for new PDP context establishment or for handover is implementation

specific)

1 PDP context is for emergency bearer services

2 PDP context is for new PDP context establishment

3 PDP context is for handover from a non-3GPP access network

<P-CSCF_discovery>: integer type; influences how the MT/TA requests to get the P-CSCF address, see
3GPP TS 24.229 annex B and annex L.

0 Preference of P-CSCF address discovery not influenced by +CGDCONT

1 Preference of P-CSCF address discovery through NAS signalling

2 Preference of P-CSCF address discovery through DHCP

<IM_CN_Signalling_Flag_Ind>: integer type; indicates to the network whether the PDP context is for IM CN

subsystem-related signalling only or not.

0 UE indicates that the PDP context is not for IM CN subsystem-related signalling only

1 UE indicates that the PDP context is for IM CN subsystem-related signalling only

12.2.3 +CGQMIN, Quality of Service Profile (Min Acceptable)

Description

This command enables the terminal to specify the minimum acceptable profile which is checked by the
ME against the negotiated profile returned in the Activate PDP Context Accept message.

Page 117 of 165

Syntax

Command Possible response(s)

AT+CGQMIN=<cid>[,<precedence>[,<delay>[ OK
,<reliability.>[,<peak>[,<mean>]]]]] or:

+CME ERROR: <err>

AT+CGQMIN? +CGQMIN:

<cid>,<precedence>,<delay>,<reliability>,<peak>,<mean>[<CR>

<LF>

+CGQMIN:
<cid>,<precedence>,<delay>,<reliability.>,<peak>,<mean>[...]]

OK

or:
+CME ERROR: <err>

AT+CGQMIN=? +CGQMIN: <PDP_type>,(list of supported <precedence>s),(list

of

supported <delay>s),(list of supported <reliability>s),(list of

supported <peak>s),(list of supported <mean>s)

OK

or:

+CME ERROR: <err>

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<cid>: integer type; specifies a particular PDP context definition (see the +CGDCONT and +CGDSCONT commands).
<PDP_type>: string type; specifies the type of packet data protocol (see the +CGDCONT command). The following

parameters are defined in 3GPP TS 23.107 [46]:

<precedence>: integer type; specifies the precedence class

<delay>: integer type; specifies the delay class

<reliability>: integer type; specifies the reliability class

Page 118 of 165

<peak>: integer type; specifies the peak throughput class

<mean>: integer type; specifies the mean throughput class

12.2.4 +CGQREQ, Quality of Service Profile (Requested)

Description

This command enables the terminal to specify a Quality of Service Profile that is used when the ME sends
an Activate PDP Context Request message to the network.

Syntax

Command Possible response(s)

AT+CGQREQ=<cid>[,<precedence>[,<delay>[ OK

,<reliability>[,<peak>[,<mean>]]]]] or:

+CME ERROR: <err>

AT+CGQREQ? +CGQREQ:

<cid>,<precedence>,<delay>,<reliability>,<peak>,<mean>

OK

AT+CGQREQ=? +CGQREQ: <PDP_type>,(list of supported<precedence>s),(list of

supported <delay>s),(list of supported <reliability>s),(list of

supported <peak>s),(list of supported <mean>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<cid>: integer type; specifies a particular PDP context definition (see the +CGDCONT and +CGDSCONT commands).

<PDP_type>: string type; specifies the type of packet data protocol (see the +CGDCONT command).The following
parameters are defined in 3GPP TS 23.107 [46]:

<precedence>: integer type; specifies the precedence class

<delay>: integer type; specifies the delay class

<reliability>: integer type; specifies the reliability class

Page 119 of 165

<peak>: integer type; specifies the peak throughput class

<mean>: integer type; specifies the mean throughput class

12.2.5 +CGATT, Packet Domain Attach or Detach

Description

The execution command is used to attach the MT to, or detach the MT from, the Packet Domain service.
After the command has completed, the MT remains in V.250 command state. If the MT is already in the
requested state, the command is ignored and the OK response is returned. If the requested state cannot
be achieved, an ERROR or +CME ERROR response is returned. Extended error responses are enabled by
the +CMEE command.

Syntax

Command Possible response(s)

AT+CGATT=<state> OK

or:

+CME ERROR: <err>

AT+CGATT? +CGATT: <state>

OK

AT+CGATT=? +CGATT: (list of supported <state>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes <15s

Defined Values

<state>: integer type; indicates the state of PS attachment

0 detached
1 attached

Page 120 of 165

 12.2.6 D*99, Request GPRS Service "D"
Description

This command enables the ME to perform the actions necessary for establishing communication between
the terminal and the external Packet Data Network (PDN).
The ITU V.25ter 'D' (Dial) command causes the ME to enter the ITU V.25ter Online Data state and
together with the terminal, to start the specified layer 2 protocol. The ME returns CONNECT to confirm
acceptance of the command prior to entering the ITU V.25ter Online Data state. No further commands
may follow on the AT command line.
The detailed behavior after the Online Data state has been entered is dependent on the PDP type, and is
described briefly. GPRS attachment and PDP context activation procedures may take place prior to, or
during the PDP startup if they have not already been performed using the +CGATT and +CGACT
commands.
When the layer 2 protocols have terminated, either as a result of an orderly shut down of the PDP or an
error, the ME enters the ITU V.25ter command state and returns the NO CARRIER final result code.
If <called address> is supported and provided, the ME automatically sets up a virtual call to the specified
address after the PDP context has been activated.
If <L2P> and <cid> are supported, the +CGDCONT, +CGQREQ and other such commands may then be
used in The modem initialization AT command string to set values for PDP type, APN, QoS and so on.
If <L2P> is not supported, or is supported but omitted, the ME uses a layer 2 protocol appropriate to the
PDP type.
If <cid> is not supported, or is supported but omitted, the ME attempts to activate the context using one of
the following:
Any information provided by the terminal during the PDP start up procedure. For example, the terminal
may provide a PDP type and/or PDP address to the ME.
A prior knowledge, for example, the ME may implement only one PDP type.
Using the "Empty PDP type" No PDP address or APN is sent in this case and only one PDP context
subscription record is present in the HLR for this subscriber.
This command may be used in both normal and modem compatibility modes.

Syntax

Command Possible response(s)

ATD*<GPRS_SC>[* [<called_address>] CONNECT

[*[<L2P>][*[<cid>]]]]# or:

Page 121 of 165

 ERROR

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes <30s

Defined Values

<GPRS_SC>: string type; GPRS Service Code to identify a request to use GPRS.

<called_address>: string type; to identify the called party in the address space applicable to the PDP. For communications

software that does not support arbitrary characters in the dial string, a numeric equivalent may be used.
Also, the comma character "," may be used as a substitute for the period character ".".

For PDP type OSP: IHOSS, the following syntax may be used for

<called_address>: string type; [<host>] [@[<port>] [@[<protocol>]]] where <host>, <port> and <protocol> are defined

in “+CGDCONT,Define PDP Context”.

For communications software that does not support arbitrary characters in the dial string, a numeric

value equivalent to the host name may be used. However, this should be avoided if at all possible.

<L2P>: string type; to indicate the layer 2 protocol to be used.

For communications software that does not support arbitrary characters in the dial string, the following numeric

equivalents are used:

0 NULL

1 PPP

2 PAD
3 X25

9 yyyy M-xxxx

Other values are reserved and result in an ERROR response to the Set command.

Note: V.250 (and certain communications software) do not permit arbitrary characters in the dial string. The <L2P>

and <called_address> strings are therefore specified as containing digits (0-9) only.

<cid>: integer type; to specify a particular PDP context definition (See “+CGDCONT, Define PDP Context”).

12.2.7 +CGACT, PDP Context Activate or Deactivate

Description

The execution command is used to activate or deactivate the specified PDP context (s). After the

Page 122 of 165

command has completed, the MT remains in V.250 command state. If any PDP context is already in the
requested state, the state for that context remains unchanged. If the requested state for any specified
context cannot be achieved, an ERROR or +CME ERROR response is returned. Extended error responses
are enabled by the +CMEE command. If the MT is not PS attached when the activation form of the
command is executed, the MT first performs a PS attach and then attempts to activate the specified
contexts. If the attach fails then the MT responds with ERROR or, if extended error responses are enabled,
with the appropriate failure-to-attach error message.
For EPS, if an attempt is made to disconnect the last PDN connection, then the MT responds with ERROR
or, if extended error responses are enabled, a +CME ERROR.

Syntax

Command Possible response(s)

AT+CGACT=[<state>[,<cid>[,<cid>[,]]]] OK

or:

NO CARRIER
or:

+CME ERROR: <err>

AT+CGACT? +CGACT: <cid>,<state><CR><LF>

+CGACT: <cid>,<state><CR><LF>

+CGACT: <cid>,<state>

OK

AT+CGACT=? +CGACT: (list of supported <state>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes <30s

Defined Values

<state>: integer type; indicates the state of PDP context activation. The default value is manufacturer specific.
0 deactivated

1 activated

Page 123 of 165

<cid>: integer type; specifies a particular PDP context definition (see the +CGDCONT and +CGDSCONT commands).

12.2.8 +CGPADDR, GPRS Addresses

Description

The execution command returns a list of PDP addresses for the specified context identifiers. If no <cid> is specified, the
addresses for all defined contexts are returned.

Syntax

Command Possible response(s)

AT+CGPADDR[=<cid>[,<cid>[,]]] +CGPADDR: <cid>[,<PDP_addr_1>[,<PDP_addr_2>] ]
[<CR><LF>+CGPADDR: cid>[,<PDP_addr_1>[,<PDP_addr_2>]]][...]]

OK

AT+CGPADDR=? +CGPADDR: (list of defined <cid>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<cid>: integer type; specifies a particular PDP context definition (see the +CGDCONT and +CGDSCONT commands).
<PDP_addr_1> and <PDP_addr_2>: each is a string type that identifies the MT in the address space applicable to the

PDP. The address may be static or dynamic. For a static address, it will be the one set by the +CGDCONT and

+CGDSCONT commands when the context was defined.

For a dynamic address it will be the one assigned during the last PDP context activation that used the context

definition referred to by <cid>. Both <PDP_addr_1> and <PDP_addr_2>are omitted if none is available. Both

<PDP_addr_1> and <PDP_addr_2> are included when both IPv4 and IPv6 addresses are assigned, with
<PDP_addr_1> containing the IPv4 address and <PDP_addr_2> containing the IPv6 address.

The string is given as dot-separated numeric (0-255) parameter of the form: a1.a2.a3.a4 for IPv4 and a1.a2.a3.a4.

a5.a6.a7.a8.a9.a10.a11.a12.a13.a14.a15.a16 for IPv6.

When +CGPIAF is supported, its settings can influence the format of the IPv6 address in parameter

<PDP_addr_1> or <PDP_addr_2> returned with the execute form of +CGPADDR.

Page 124 of 165

 12.2.9 +CGANS, Manual response to a network request for
PDP context activation
Description

This command requests the MT to respond to a network request for Packet Domain PDP context
activation which has been signaled to the TE by the RING or +CRING unsolicited result code

Syntax

Command Possible response(s)

AT+CGANS=[<response>,[<L2P>,[<cid>]]] OK
Or

CME ERROR: <error>

AT+CGANS=? +CGANS: (list of supported <response>s),(list of supported

<L2P>s)

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<response>: integer type; 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.

<L2P>: string type; indicates the layer 2 protocol to be used (see +CGDATA command).

<cid>: integer type; specifies a particular PDP context definition (see the +CGDCONT and +CGDSCONT commands).

12.2.10 +CGAUTO, Automatic Response to a Network

Request for PDP Context Activation
Description

The set command disable or enable an automatic positive or negative response (auto-answer) to the

Page 125 of 165

receipt of a NW initiated Request PDP Context Activation message from the network in UMTS/GPRS and
a NW-initiated Request EPS Bearer Activation/ Modification Request messages in EPS. 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.

Syntax

Command Possible response(s)

AT+CGAUTO=[<n>] OK

Or

CME ERROR: <error>

AT+CGAUTO? +CGAUTO: <n>

OK

AT+CGAUTO=? +CGAUTO: (list of supported <n>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<n>: integer type; indicates the setting for the auto-answer to be used

0 Turn off automatic response for Packet Domain only Packet Domains network requests are manually accepted or
rejected by the +CGANS command.

1 Turn on automatic response for Packet Domain only Packet Domain network requests are automatically accepted

according to the description above.

2 Modem compatibility mode, Packet Domain only 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.

3 Modem compatibility mode, Packet Domain and circuit switched calls (default) 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.

Page 126 of 165

 4 Turn on automatic negative response for Packet Domain only Packet Domain network requests are automatically

rejected.

12.2.11 +CGEQMIN，3G Quality of Service Profile (Minimum

acceptable)
Description

This command allows the TE to specify a minimum acceptable profile, which is checked by the MT
against the negotiated profile returned in the PDP context establishment and PDP contect modification
procedures.

Syntax

Command Possible response(s)

AT+CGEQMIN=[<cid>[,<Traffic OK

class>[,<Maximum Bit rate UL>[,<Maximum Or

bit rate DL>[,<Guaranteed Bit rate CME ERROR : <error>

UL>[,<Guaranteed bit rate DL>[,<Delivery

order>[,<Maximum SDU size>[,<SDU error

ratio>[,<Residual bit error ratio>[,<Delivery of

erroneous SDUs>[,<Transfer delay>[,<Traffic

handling priority>[,<Source statistics

descriptor>[,<Signaling
indication>]]]]]]]]]]]]]]]

AT+CGEQMIN? +CGEQMIN: <cid>,<Traffic class>,<Maximum bit rate

UL>,<Maximum bit rate DL>,<Guaranteed bit rate

UL>,<Guaranteed bit rate DL>,<Delivery order>,<Maximum

SDU size>,<SDU error ratio>,<Residual bit error ratio>,<Delivery

of erroneous SDUs>,<Transfer delay>,<Traffic handling priority>

[,<Source statistics descriptor>,<Signaling indication>]

[<CR><LF>+CGEQMIN: <cid>,<Traffic class>,<Maximum bit

rate UL>,<Maximum bit rate DL>,<Guaranteed bit rate

UL>,<Guaranteed bit rate DL>,<Delivery order>,<Maximum

Page 127 of 165

Command Possible response(s)
SDU size>,<SDU error ratio>,<Residual bit error ratio>,<Delivery

of erroneous SDUs>,<Transfer delay>,<Traffic handling priority>

[,<Source statistics descriptor>,<Signaling indication>] […]]

AT+CGEQMIN=? +CGEQMIN: <PDP_type>,(list of supported <Traffic class>s),(list

of supported <Maximum bit rate UL>s),(list of supported

<Maximum bit rate DL>s),(list of supported <Guaranteed bit rate

UL>s),(list of supported

<Guaranteed bit rate DL>s),(list of supported <Delivery

order>s),(list of supported <Maximum SDU size>s),(list of

supported <SDU error ratio>s),(list of supported <Residual bit

error ratio>s),(list of supported <Delivery of erroneous

SDUs>s),(list of supported <Transfer delay>s),(list of supported

<Traffic handling priority>s)[,(list of supported <Source statistics

descriptor>s),(list of supported <Signaling indication>s)]

[<CR><LF>+CGEQMIN: <PDP_type>,(list of supported <Traffic

class>s),(list of supported <Maximum bit rate UL>s),(list of

supported <Maximum bit rate DL>s),(list of supported

<Guaranteed bit rate UL >s),(list of supported<Guaranteed bit rate

DL >s),(list of supported <Delivery

order>s),(list of supported <Maximum SDU size>s),(list of

supported <SDU error ratio>s),(list of supported <Residual bit

error ratio>s),(list of supported <Delivery of erroneous

SDUs>s),(list of supported <Transfer delay>s),(list of supported

<Traffic handling priority>s)[,(list of supported <Source statistics

descriptor>s),(list of supported <Signaling indication>s)] […]]

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Page 128 of 165

Defined Values

<cid>: integer type; specifies a particular PDP context definition (see +CGDCONT and +CGDSCONT commands).
<PDP_type>: string type; specifies the type of packet data protocol (see the +CGDCONT command).

For the following parameters, see also 3GPP TS 23.107 [46].

<Traffic class>: integer type; indicates the type of application for which the UMTS bearer service is optimised (refer
3GPP TS 24.008 subclause 10.5.6.5).

0 conversational

1 streaming

2 interactive

3 background

<Maximum bitrate UL>: integer type; indicates the maximum number of kbits/s delivered to UMTS (up-link traffic) at a
SAP. As an example a bitrate of 32kbit/s would be specified as '32' (e.g. AT+CGEQMIN=…,32, …) (refer 3GPP TS

24.008 subclause 10.5.6.5).

<Maximum bitrate DL>: integer type; indicates the maximum number of kbits/s delivered by UMTS (down-link traffic)
at a SAP. As an example a bitrate of 32kbit/s would be specified as '32' (e.g. AT+CGEQMIN=…,32, …) (refer 3GPP

TS 24.008 subclause 10.5.6.5).

<Guaranteed bitrate UL>: integer type; indicates the guaranteed number of kbits/s delivered to UMTS (up-link traffic) at

a SAP (provided that there is data to deliver). As an example a bitrate of 32kbit/s would be specified as '32' (e.g.

AT+CGEQMIN=…,32, …) (refer 3GPP TS 24.008 subclause 10.5.6.5).

<Guaranteed bitrate DL>: integer type; indicates the guaranteed number of kbits/s delivered by UMTS (down-link traffic)

at a SAP (provided that there is data to deliver). As an example a bitrate of 32kbit/s would be specified as '32' (e.g.

AT+CGEQMIN=…,32, …) (refer 3GPP TS 24.008 subclause 10.5.6.5).

<Delivery order>: integer type; indicates whether the UMTS bearer shall provide in-sequence SDU delivery or not (refer
3GPP TS 24.008 subclause 10.5.6.5).

0 no

1 yes

<Maximum SDU size>: integer type; (1,2,3,…) indicates the maximum allowed SDU size in octets (refer 3GPP TS

24.008 subclause 10.5.6.5).

<SDU error ratio>: string type; indicates the target value for the fraction of SDUs lost or detected as erroneous. SDU
error ratio is defined only for conforming traffic. The value is specified as "mEe". As an example a target SDU error

ratio of 5•10-3 would be specified as "5E3" (e.g. AT+CGEQMIN=…,"5E3",…) (refer 3GPP TS 24.008 subclause

10.5.6.5).
<Residual bit error ratio>: string type; indicates the target value for the undetected bit error ratio in the delivered SDUs.

If no error detection is requested, Residual bit error ratio indicates the bit error ratio in the delivered SDUs. The

Page 129 of 165

 value is specified as "mEe". As an example a target residual bit error ratio of 5•10-3 would be specified as "5E3"

(e.g. AT+CGEQMIN=…,"5E3",…) (refer 3GPP TS 24.008 subclause 10.5.6.5).

<Delivery of erroneous SDUs>: integer type; indicates whether SDUs detected as erroneous shall be delivered or not

(refer 3GPP TS 24.008 subclause 10.5.6.5).

0 no
1 yes

2 no detect

<Transfer delay>: integer type; (0,1,2,…) indicates the targeted time between request to transfer an SDU at one SAP to
its delivery at the other SAP, in milliseconds (refer 3GPP TS 24.008 subclause 10.5.6.5).

<Traffic handling priority>: integer type; (1,2,3,…) specifies the relative importance for handling of all SDUs belonging

to the UMTS bearer compared to the SDUs of other bearers (refer 3GPP TS 24.008 subclause 10.5.6.5).
<Source Statistics Descriptor>: integer type; specifies characteristics of the source of the submitted SDUs for a PDP

context. This parameter should be provided if the Traffic class is specified as conversational or streaming (refer

3GPP TS 24.008 subclause 10.5.6.5).

0 Characteristics of SDUs is unknown

1 Characteristics of SDUs corresponds to a speech source

<Signalling Indication>: integer type; indicates signalling content of submitted SDUs for a PDP context. This parameter
should be provided if the Traffic class is specified as interactive (refer 3GPP TS 24.008 subclause 10.5.6.5).

0 PDP context is not optimized for signalling

1 PDP context is optimized for signaling

12.2.12 +CGEQREQ，3G Quality of Service Profile

(Requested)
Description

This command allows the TE to specify a UMTS Quality of Service Profile that is used when the MT
activates a PDP context.

Syntax

Command Possible response(s)

AT+CGEQREQ=[<cid>[,<Traffic OK

class>[,<Maximum bit rate UL>[,<Maximum or

bit rate DL>[,<Guaranteed bit rate ERROR

UL>[,<Guaranteed bit rate DL>[,<Delivery

Page 130 of 165

Command Possible response(s)
order>[,<Maximum SDU size>[,<SDU error

ratio>[,<Residual bit error ratio>

[,<Delivery of erroneous SDUs>[,<Transfer

delay>[,<Traffic handling priority>[,<Source

statistics descriptor>[,<Signaling
indication>]]]]]]]]]]]]]]]

AT+CGEQREQ? +CGEQREQ: <cid>,<Traffic class>,<Maximum bit rate

UL>,<Maximum bit rate DL>,<Guaranteed bit rate

UL>,<Guaranteed bit rate DL>,<Delivery order>,<Maximum

SDU size>,<SDU error ratio>,<Residual bit error

ratio>,<Delivery of erroneous SDUs>,<Transfer

delay>,<Traffic handling priority>[,<Source statistics

descriptor>,<Signaling indication>] [<CR><LF>+CGEQREQ:

<cid>,<Traffic class>,<Maximum bit rate UL>,<Maximum bit

rate DL>,<Guaranteed bit rate UL>,<Guaranteed bit rate

DL>,<Delivery order>,<Maximum SDU size>,<SDU error

ratio>,<Residual bit error ratio>,<Delivery of erroneous

SDUs>,<Transfer delay>,<Traffic handling priority>[,<Source

Statistics Descriptor>,<Signaling Indication>] […]]

AT+CGEQREQ=? +CGEQREQ: <PDP_type>,(list of supported <Traffic

class>s),(list of supported <Maximum bit rate UL>s),(list of

supported <Maximum bit rate DL>s),(list of supported

<Guaranteed bit rate UL>s),(list of supported <Guaranteed bit

rate DL>s),(list of supported <Delivery order>s),(list of

supported <Maximum SDU size>s),(list of supported <SDU

error ratio>s),(list of supported <Residual bit error ratio>s),(list

of supported <Delivery of erroneous SDUs>s),(list of

supported <Transfer delay>s),(list of supported <Traffic

handling priority>s) [,(list of supported <Source statistics

descriptor>s),(list of supported <Signaling indication>s)]

[<CR><LF>+CGEQREQ: <PDP_type>,(list of supported

<Traffic class>s),(list of supported <Maximum bit rate

Page 131 of 165

 Command Possible response(s)
UL>s),(list of supported <Maximum bit rate DL>s),(list of

supported <Guaranteed bit rate UL>s),(list of supported

<Guaranteed bit rate DL>s),(list of supported <Delivery

order>s),(list of supported <Maximum SDU size>s),(list of

supported <SDU error ratio>s),(list of supported <Residual bit

error ratio>s),(list of supported <Delivery of erroneous

SDUs>s),(list of supported <Transfer delay>s),(list of

supported <Traffic handling priority>s) ] [,(list of supported

<Source statistics descriptor>s),(list of supported <Signaling

indication>s)]

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<cid>: integer type; specifies a particular PDP context definition (see +CGDCONT and +CGDSCONT commands).

<PDP_type>: string type; specifies the type of packet data protocol (see the +CGDCONT command).

For the following parameters, see also 3GPP TS 23.107 [46].

<Traffic class>: integer type; indicates the type of application for which the UMTS bearer service is optimised (refer

3GPP TS 24.008 subclause 10.5.6.5).

0 conversational
1 streaming

2 interactive

3 background
4 subscribed value

If the Traffic class is specified as conversational or streaming, then the Guaranteed and Maximum bitrate parameters

should also be provided.

<Maximum bitrate UL>: integer type; indicates the maximum number of kbits/s delivered to UMTS (up-link traffic) at a

SAP. As an example a bitrate of 32kbit/s would be specified as '32' (e.g. AT+CGEQREQ=…,32, …). This parameter

should be provided if the Traffic class is specified as conversational or streaming (refer

3GPP TS 24.008 subclause 10.5.6.5).

Page 132 of 165

<Maximum bitrate DL>: integer type; indicates the maximum number of kbits/s delivered by UMTS (down-link traffic)

at a SAP. As an example a bitrate of 32kbit/s would be specified as '32' (e.g. AT+CGEQREQ=…,32, …). If the
parameter is set to '0' the subscribed value will be requested. This parameter should be provided if the Traffic class is

specified as conversational or streaming (refer 3GPP TS 24.008 subclause 10.5.6.5).

<Guaranteed bitrate UL>: integer type; indicates the guaranteed number of kbits/s delivered to UMTS (up-link traffic) at
a SAP (provided that there is data to deliver). As an example a bitrate of 32kbit/s would be specified as '32' (e.g.

AT+CGEQREQ=…,32, …). If the parameter is set to '0' the subscribed value will be requested. This parameter

should be provided if the Traffic class is specified as conversational or streaming (refer

3GPP TS 24.008 subclause 10.5.6.5).

<Guaranteed bitrate DL>: integer type; indicates the guaranteed number of kbits/s delivered by UMTS (down-link traffic)

at a SAP (provided that there is data to deliver). As an example a bitrate of 32kbit/s would be specified as '32' (e.g.
AT+CGEQREQ=…,32, …). If the parameter is set to '0' the subscribed value will be requested. This parameter

should be provided if the Traffic class is specified as conversational or streaming (refer 3GPP TS 24.008

subclause 10.5.6.5).
<Delivery order>: integer type; indicates whether the UMTS bearer shall provide in-sequence SDU delivery or not (refer

3GPP TS 24.008 subclause 10.5.6.5).

0 no
1 yes

2 subscribed value

<Maximum SDU size>: integer type; (1,2,3,…) indicates the maximum allowed SDU size in octets. If the parameter is

set to '0' the subscribed value will be requested (refer 3GPP TS 24.008 subclause 10.5.6.5).

<SDU error ratio>: string type; indicates the target value for the fraction of SDUs lost or detected as erroneous. SDU

error ratio is defined only for conforming traffic. The value is specified as 'mEe'. As an example a target SDU error
ratio of 5•10-3 would be specified as "5E3" (e.g. AT+CGEQREQ=…,"5E3",…). "0E0" means subscribed value

(refer 3GPP TS 24.008 subclause 10.5.6.5).

<Residual bit error ratio>: string type; indicates the target value for the undetected bit error ratio in the delivered SDUs.

If no error detection is requested, Residual bit error ratio indicates the bit error ratio in the delivered SDUs. The

value is specified as "mEe". As an example a target residual bit error ratio of 5•10-3 would be specified as "5E3"

(e.g. AT+CGEQREQ=…,"5E3",…). "0E0" means subscribed value (refer 3GPP TS 24.008 subclause 10.5.6.5).
<Delivery of erroneous SDUs>: integer type; indicates whether SDUs detected as erroneous shall be delivered or not

(refer 3GPP TS 24.008 subclause 10.5.6.5).

0 no
1 yes

2 no detect

Page 133 of 165

 3 subscribed value

<Transfer delay>: integer type; (0,1,2,…) indicates the targeted time between request to transfer an SDU at one SAP to
its delivery at the other SAP, in milliseconds. If the parameter is set to '0' the subscribed value will be requested

(refer 3GPP TS 24.008 subclause 10.5.6.5).

<Traffic handling priority>: integer type; (1,2,3,…) specifies the relative importance for handling of all SDUs belonging
to the UMTS bearer compared to the SDUs of other bearers. If the parameter is set to '0' the subscribed value will

be requested (refer 3GPP TS 24.008 subclause 10.5.6.5).

<Source Statistics Descriptor>: integer type; specifies characteristics of the source of the submitted SDUs for a PDP
context. This parameter should be provided if the Traffic class is specified as conversational or streaming (refer

3GPP TS 24.008 subclause 10.5.6.5).

0 Characteristics of SDUs is unknown

1 Characteristics of SDUs corresponds to a speech source

<Signalling Indication>: integer type; indicates signalling content of submitted SDUs for a PDP context. This parameter

should be provided if the Traffic class is specified as interactive (refer 3GPP TS 24.008 subclause 10.5.6.5).
0 PDP context is not optimized for signalling

1 PDP context is optimized for signalling<PDP_type> (see +CGDCONT and +CGDSCONT commands).

12.2.13 +CGEQNEG，3G Quality of Service Profile

(Negotiated)
Description

This command allows the TE to retrieve the negotiated QoS profiles returned in the PDP context
establishment procedure.

Syntax

Command Possible response(s)

AT+CGEQNEG=[<cid>[,<cid>[,…]]] +CGEQNEG: <cid>,<Traffic class>,<Maximum bit rate

UL>,<Maximum bit rate DL>,<Guaranteed bit rate

UL>,<Guaranteed

bit rate DL>,<Delivery order>,<Maximum SDU size>,<SDU error

ratio>,<Residual bit error ratio>,<Delivery of erroneous

SDUs>,<Transfer delay>,<Traffic handling priority>

[<CR><LF>+CGEQNEG: <cid>,<Traffic class>,<Maximum bit

Page 134 of 165

 Command Possible response(s)
rate UL>,<Maximum bit rate DL>,<Guaranteed bit rate

UL>,<Guaranteed bit rate DL>,<Delivery order>,<Maximum

SDU size>,<SDU error ratio>,<Residual bit error ratio>,<Delivery

of erroneous SDUs>,<Transfer delay>,<Traffic handling priority>

[…]]

AT+CGEQNEG=? +CGEQNEG: (list of <cid>s associated with active contexts)

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<cid>: integer type; specifies a particular PDP context definition (see +CGDCONT and +CGDSCONT commands).

For the following parameters, see also 3GPP TS 23.107 [46].

<Traffic class>: integer type; indicates the type of application for which the UMTS bearer service is optimised (refer

3GPP TS 24.008 subclause 10.5.6.5).

0 conversational

1 streaming

2 interactive
3 background

<Maximum bitrate UL>: integer type; indicates the maximum number of kbits/s delivered to UMTS (up-link traffic) at a

SAP. As an example a bitrate of 32kbit/s would be specified as '32' (e.g. +CGEQNEG:…,32, …) (refer
3GPP TS 24.008 subclause 10.5.6.5).

<Maximum bitrate DL>: integer type; indicates the maximum number of kbits/s delivered by UMTS (down-link traffic)

at a SAP As an example a bitrate of 32kbit/s would be specified as '32' (e.g. +CGEQNEG:…,32, …) (refer
3GPP TS 24.008 subclause 10.5.6.5).

<Guaranteed bitrate UL>: integer type; indicates the guaranteed number of kbits/s delivered to UMTS (up-link traffic) at

a SAP (provided that there is data to deliver). As an example a bitrate of 32kbit/s would be specified as '32' (e.g.
+CGEQNEG:…,32, …) (refer 3GPP TS 24.008 subclause 10.5.6.5).

<Guaranteed bitrate DL>: integer type; indicates the guaranteed number of kbits/s delivered by UMTS (down-link traffic)

at a SAP (provided that there is data to deliver). As an example a bitrate of 32kbit/s would be specified as '32' (e.g.

Page 135 of 165

 +CGEQNEG:…,32, …) (refer 3GPP TS 24.008 subclause 10.5.6.5).

<Delivery order>: integer type; indicates whether the UMTS bearer shall provide in-sequence SDU delivery or not (refer
3GPP TS 24.008 subclause 10.5.6.5).

0 no

1 yes
<Maximum SDU size>: integer type; (1,2,3,…) indicates the maximum allowed SDU size in octets (refer

3GPP TS 24.008 subclause 10.5.6.5).

<SDU error ratio>: string type; indicates the target value for the fraction of SDUs lost or detected as erroneous. SDU
error ratio is defined only for conforming traffic. The value is specified as "mEe". As an example a target SDU error

ratio of 5•10-3 would be specified as "5E3" (e.g. +CGEQNEG:…, "5E3",…) (refer

3GPP TS 24.008 subclause 10.5.6.5).

<Residual bit error ratio>: string type; indicates the target value for the undetected bit error ratio in the delivered SDUs.

If no error detection is requested, Residual bit error ratio indicates the bit error ratio in the delivered SDUs. The

value is specified as "mEe". As an example a target residual bit error ratio of 5•10-3 would be specified as "5E3"
(e.g. +CGEQNEG:…,"5E3",…) (refer 3GPP TS 24.008 subclause 10.5.6.5).

<Delivery of erroneous SDUs>: integer type; indicates whether SDUs detected as erroneous shall be delivered or not

(refer 3GPP TS 24.008 subclause 10.5.6.5).

0 no

1 yes

2 no detect

<Transfer delay>: integer type; (0,1,2,…) indicates the targeted time between request to transfer an SDU at one SAP to

its delivery at the other SAP, in milliseconds (refer 3GPP TS 24.008 subclause 10.5.6.5).

<Traffic handling priority>: integer type; (1,2,3,…) specifies the relative importance for handling of all SDUs belonging
to the UMTS bearer compared to the SDUs of other bearers (refer 3GPP TS 24.008 subclause 10.5.6.5).

12.2.14 +CGCMOD，PDP Context Modify

Description

This command is used to modify the specified PDP context (s) with respect to QoS profiles and TFTs.

Syntax

Command Possible response(s)

AT+CGCMOD=[<cid>[,<cid>[,…]]] OK

Page 136 of 165

 Or

CME ERROR: <error>

AT+CGCMOD=? +CGCMOD: (list of <cid>s associated with active contexts)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<cid>: integer type; specifies a particular PDP context definition (see the +CGDCONT and +CGDSCONT commands).

12.2.15 +CGDATA，Enter Data State

Description

This execution command causes the MT to perform whatever actions are necessary to establish
communication between the TE and the network using one or more GPRS PDP types. This may include
performing a GPRS attach and one or more PDP context activation. If the parameters are accepted, MT
displays the intermediate result code CONNECT on TE and enters the online data state; thereafter data
transfer may proceed. No other commands following +CGDATA in the command line will be processed.

Syntax

Command Possible response(s)

AT+CGDATA=[<L2P>,[<cid>[,<cid>[,…]]]] CONNECT

It follows data transfer

or

CME ERROR: <error>

AT+CGDATA=? +CGDATA: (list of supported <L2P>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Page 137 of 165

 No No Yes Yes < 1s

Defined Values

<L2P>: string type; indicates the layer 2 protocol to be used between the TE and MT

NULL none, for PDP type OSP:IHOSS (Obsolete)

PPP Point-to-point protocol for a PDP such as IP

PAD character stream for X.25 character (triple X PAD) mode (Obsolete)

X25 X.25 L2 (LAPB) for X.25 packet mode (Obsolete)

M-xxxx manufacturer-specific protocol (xxxx is an alphanumeric string)

Note: If the value is omitted, the layer 2 protocol is unspecified. Other values are reserved and will result in an

ERROR response.

<cid>: integer type; specifies a particular PDP context definition (see the +CGDCONT and +CGDSCONT commands).

12.2.16 +CGDSCONT，Define Secondary PDP Context

Description

This command is used to define a secondary PDP context by specifying the PDP context parameter
values for a <cid> (local context identification parameter). If the command is used only with the one
parameter <cid>, it means that the corresponding PDP context becomes undefined.

Syntax

Command Possible response(s)

AT+CGDSCONT=[<cid>,<p_cid> OK

[,<d_comp>[,<h_comp> Or
[,<IM_CN_Signaling_Flag_Ind>] ERROR

]]]

AT+CGDSCONT? +CGDSCONT: <cid>,<p_cid>,<d_comp>,<h_comp>

[,<IM_CN_Signaling_Flag_Ind>]

[<CR><LF>+CGDSCONT: <cid>,<p_cid>,<d_comp>,<h_comp>

[,<IM_CN_Signaling_Flag_Ind>] [...]]
OK

AT+CGDSCONT=? +CGDSCONT: (range of supported <cid>s),(list of <p_cid>s for

active primary contexts),(list of supported <d_comp>s),(list of

supported <h_comp>s),(list of supported

Page 138 of 165

 Command Possible response(s)
<IM_CN_Signalling_Flag_Ind>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No Yes Yes Yes < 1s

Defined Values

<cid>: integer type; 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.

NOTE: The <cid>s for network-initiated PDP contexts will have values outside the ranges indicated for the <cid> in

the test form of the commands +CGDCONT and +CGDSCONT.

<p_cid>: integer type; 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>: integer type; controls PDP data compression (applicable for SNDCP only) (refer 3GPP TS 44.065 [61])

0 off

1 on (manufacturer preferred compression)

2 V.42bis
3 V.44

<h_comp>: integer type; controls PDP header compression (refer 3GPP TS 44.065 [61] and 3GPP TS 25.323 [62])

0 off
1 on (manufacturer preferred compression)

2 RFC 1144 [105] (applicable for SNDCP only)

3 RFC 2507 [107]

4 RFC 3095 [108] (applicable for PDCP only)

<IM_CN_Signalling_Flag_Ind>: integer type; indicates to the network whether the PDP context is for IM CN

subsystem-related signalling only or not.

0 UE indicates that the PDP context is not for IM CN subsystem-related signalling only

1 UE indicates that the PDP context is for IM CN subsystem-related signalling only

Page 139 of 165

 12.2.17 +CGEREP，Packet Domain Event Reporting
Description

This command is used to enable or disable sending of unsolicited result codes, +CGEV: XXX from MT to
TE in the case of events occurring in the Packet Domain.

Syntax

Command Possible response(s)

AT+CGEREP=[<mode>[,<bfr>]] OK

AT+CGEREP? +CGEREP: <mode>,<bfr>

OK

AT+CGEREP=? +CGEREP: (list of supported <mode>s),(list of supported <bfr>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<mode>: integer type

0 buffer unsolicited result codes in the MT; if MT result code buffer is full, the oldest ones can be discarded. No

codes are forwarded to the TE.

1 discard unsolicited result codes when MT-TE link is reserved (e.g. in on-line data mode); otherwise forward

them directly to the TE

2 buffer unsolicited result codes in the MT when MT-TE link is reserved (e.g. in on-line data mode) and flush

them to the TE when MT-TE link becomes available; otherwise forward them directly to the TE

<bfr>: integer type

0 MT buffer of unsolicited result codes defined within this command is cleared when <mode> 1 or 2 is entered
1 MT buffer of unsolicited result codes defined within this command is flushed to the TE when <mode> 1 or 2 is

entered (OK response shall be given before flushing the codes)

Page 140 of 165

Defined events

The events are valid for GPRS/UMTS and LTE unless explicitly mentioned.
For network attachment, the following unsolicited result codes and the corresponding events are defined:

+CGEV: NW DEACT <PDP_type>, <PDP_addr>, [<cid>]

The network has forced a context deactivation. The <cid> that was used to activate the context is provided if
known to the MT

+CGEV: ME DEACT <PDP_type>, <PDP_addr>, [<cid>]

The mobile termination has forced a context deactivation. The <cid> that was used to activate the context is

provided if known to the MT.

+CGEV: NW DETACH

The network has forced a PS detach. This implies that all active contexts have been deactivated. These are not
reported separately. ETSI 3GPP TS 27.007 version 7.6.0 Release 7 147 ETSI TS 127 007 V7.6.0 (2010-04)

+CGEV: ME DETACH

The mobile termination has forced a PS detach. This implies that all active contexts have been deactivated.
These are not reported separately.

+CGEV: NW CLASS <class>

The network has forced a change of MT class. The highest available <class> is reported (see +CGCLASS).

+CGEV: ME CLASS <class>

The mobile termination has forced a change of MT class. The highest available <class> is reported (see

+CGCLASS).

+CGEV: ME PDN ACT <cid>[,<reason>[,<cid_other>]]

The mobile termination has activated a context. The context represents a PDN connection in LTE or a Primary

PDP context in GSM/UMTS. The <cid> for this context is provided to the TE. This event is sent either in result
of explicit context activation request (+CGACT), or in result of implicit context activation request associated to

attach request (+CGATT=1). The format of the parameters <cid>, <cid_other> are found in command

+CGDCONT.

<reason> integer type parameter indicates the reason why the context activation request for PDP type IPv4v6 was

not granted. This parameter is only included if the requested PDP type associated with <cid> is IPv4v6, and the

PDP type assigned by the network for <cid> is either IPv4 or IPv6.
0 IPv4 only allowed

1 IPv6 only allowed

2 single address bearers only allowed.

3 single address bearers only allowed and MT initiated context activation for a second address type bearer was

not successful.

Page 141 of 165

 12.2.18 +CGTFT Traffic Flow Template
Description

This command allows the TE to specify a Packet Filter – PF for a Traffic Flow Template – TFT that is
used in the GGSN for routing of down-link packets onto different QoS flows towards the TE.

Syntax

Command Possible response(s)

+CGTFT=[<cid>,[<packet filter OK

identifier>,<evaluation precedence index> or

[,<source address and subnet mask> [,<protocol ERROR

number (ipv4) / next header (ipv6)>

[,<destination port range> [,<source port

range> [,<ipsec security parameter index (spi)>

[,<type of service (tos) (ipv4) and mask / traffic

class (ipv6) and mask> [,<flow label (ipv6)>

[,<direction>] ]]]]]]]]]

AT+CGTFT? +CGTFT: <cid>,<packet filter identifier>,<evaluation precedence

index>,<source address and subnet mask>,<protocol number

(ipv4) / next header (ipv6)>,<destination port range>,<source port

range>,<ipsec security parameter index (spi)>,<type of service

(tos) (ipv4) and mask / traffic class (ipv6) and mask>,<flow label

(ipv6)> ,<direction> [<CR><LF>

+CGTFT: <cid>,<packet filter identifier>,<evaluation precedence

index>,<source address and subnet mask>,<protocol number

(ipv4) / next header (ipv6)>,<destination port range>,<source port

range>,<ipsec security parameter index (spi)>,<type of service

(tos)

(ipv4) and mask / traffic class (ipv6) and mask>,<flow label

(ipv6)> ,<direction> […]]

AT+CGTFT=? +CGTFT: <PDP_type>,(list of supported <packet filter

identifier>s),(list of supported <evaluation precedence

index>s),(list of supported <source address and subnet

Page 142 of 165

 Command Possible response(s)
mask>s),(list of supported <protocol number (ipv4) / next header

(ipv6)>s),(list of supported <destination port range>s),(list of

supported <source port range>s),(list of supported <ipsec security

parameter index (spi)>s),(list of supported <type of service (tos)

(ipv4) and mask / traffic class (ipv6) and mask>s),(list of

supported <flow label (ipv6)>s),(list of supported <direction>s)

[<CR><LF>+CGTFT: <PDP_type>,(list of supported <packet

filter identifier>s),(list of supported <evaluation precedence

index>s),(list of supported <source address and subnet

mask>s),(list of supported <protocol number (ipv4) / next header

(ipv6)>s),(list of supported <destination port range>s),(list of

supported <source port range>s),(list of supported <ipsec security

parameter index (spi)>s),(list of supported <type of service (tos)

(ipv4) and mask / traffic class (ipv6) and mask>s),(list of

supported <flow label (ipv6)>s),(list of sup-

ported <direction>s)

[…]]

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<cid>: integer type. Specifies a particular PDP context definition (see the +CGDCONT and +CGDSCONT commands).

<PDP_type>: string type. Specifies the type of packet data protocol (see the +CGDCONT command).
<packet filter identifier>: integer type. Value range is from 1 to 16.

<evaluation precedence index>: integer type. The value range is from 0 to 255.

<remote address and subnet mask>: string type. The string is given as dot-separated numeric (0-255) parameters on the
form:"a1.a2.a3.a4.m1.m2.m3.m4" for IPv4 or

"a1.a2.a3.a4.a5.a6.a7.a8.a9.a10.a11.a12.a13.a14.a15.a16.m1.m2.m3.m4.m5.m6.m7.m8.m9.m10.m11.m12.m13.m14

.m15.m16", for IPv6. When +CGPIAF is supported, its settings can influence the format of this parameter returned
with the read form of +CGTFT.

Page 143 of 165

<protocol number (ipv4) / next header (ipv6)>: integer type. Value range is from 0 to 255.

<local port range>: string type. The string is given as dot-separated numeric (0-65535) parameters on the form "f.t".
<remote port range>: string type. The string is given as dot-separated numeric (0-65535) parameters on the form "f.t".

<ipsec security parameter index (spi)>: numeric value in hexadecimal format. The value range is from 00000000 to

FFFFFFFF.
<type of service (tos) (ipv4) and mask / traffic class (ipv6) and mask>: string type. The string is given as dot-separated

numeric (0-255) parameters on the form "t.m".

<flow label (ipv6)>: numeric value in hexadecimal format. The value range is from 00000 to FFFFF. Valid for IPv6 only.
<direction>: integer type. Specifies the transmission direction in which the packet filter shall be applied.

0 Pre-Release 7 TFT filter (see 3GPP TS 24.008 [8], table 10.5.162)

1 Uplink
2 Downlink

3 Birectional (Up & Downlink); Default value if not set

12.2.19 +CGPIAF , Printing IP Address Format

Description

This command decides what format to print IPV6 address parameters of other AT commands. See RFC
4291 [88] for details of the IPv6 address format.
The +CGPIAF parameters <IPv6_AddressFormat>, <IPv6_SubnetNotation>, <IPv6_LeadingZeros> and
<IPv6_CompressedZeros> affect the following commands and parameters:
ˆ in +CGTFT and +CGTFTRDP, the <remote address and subnet mask >;
ˆ in +CGDCONT, the <PDP_addr>;
ˆ in +CGPADDR, the <PDP_addr_1> and <PDP_addr_2>;
ˆ in +CGCONTRDP, the <local address and subnet mask>, <DNS_prim_addr>, <DNS_sec_addr>,
<P_CSCF_prim_addr> and <P_CSCF_sec_addr>;
ˆ in +CRC, the <PDP_addr> of unsolicited result code GPRS <PDP_type>, <PDP_addr>[,[<L2P>]
[,<APN>]].
ˆ in +XDNS, the <primary_DNS>, <secondary_DNS> of XDNS Read response.

Syntax

Command Possible response(s)

AT+CGPIAF=[<IPv6_AddressFormat>[,<IPv6
OK

Page 144 of 165

 Command Possible response(s)
_SubnetNotation>[,<IPv6 or:

_LeadingZeros>[,<IPv6_CompressZeros>]]]]
+CME ERROR: <err>

AT+CGPIAF? +CGPIAF:

<IPv6_AddressFormat>,<IPv6_SubnetNotation>,<IPv6_LeadingZ

eros>,<IPv6_CompressZeros>

AT+CGPIAF=? +CGPIAF: (list of supported <IPv6_AddressFormat>s),(list of

supported <IPv6_SubnetNotation>s),(list of supported

<IPv6_LeadingZeros>s),(list of supported
<IPv6_CompressZeros>s)

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<IPv6_AddressFormat>: integer type, decides the IPv6 address format. Relevant for all AT command parameters that can

hold an IPv6 address.

0 Use IPv4-like dot-notation. IP address, and subnetwork mask if applicable, are dot-separated.

Example: For <remote address and subnet mask>:

"32.1.13.184.0.0.205.48.0.0.0.0.0.0.0.0.255.255.255.255.255.255.255.240.0.0.0.0.0.0.0.0"

For other IP address parameters:"32.1.13.184.0.0.205.48.0.0.0.0.0.0.0.0"

1 Use IPv6-like colon-notation. IP address, and subnetwork mask if applicable and when given explicitly, are
separated by a space.

Example: For <remote address and subnet mask>: "2001:0DB8:0000:CD30:0000:0000:0000:0000

FFFF:FFFF:FFFF:FFF0:0000:0000:0000:0000"
For other IP address parameters:"2001:0DB8:0000:CD30:0000:0000:0000:0000"

<IPv6_SubnetNotation>: integer type, decides the subnet-notation for <remote address and subnet mask. Setting does not

apply if <IPv6_AddressFormat> = 0.
0 Both IP Address and subnet mask are stated explicitly, separated by a space.

Example: "2001:0DB8:0000:CD30:0000:0000:0000:0000 FFFF:FFFF:FFFF:FFF0:0000:0000:0000:0000"

Page 145 of 165

 1 The printout format is applying / (forward slash) subnet-prefix Classless Inter-Domain Routing (CIDR) notation.

Example: "2001:0DB8:0000:CD30:0000:0000:0000:0000/60"
<IPv6_LeadingZeros>: integer type, decides whether leading zeros are omitted or not. Setting does not apply if

<IPv6_AddressFormat> = 0.

0 Leading zeros are omitted. Example: "2001:DB8:0:CD30:0:0:0:0"

1 Leading zeros are included. Example: "2001:0DB8:0000:CD30:0000:0000:0000:0000"

<IPv6_CompressZeros>: integer type, decides whether 1-n instances of 16-bit zero-values are replaced by only '::'. This

applies only once. Setting does not apply if <IPv6_AddressFormat> = 0.

0 No zero compression. Example: "2001:DB8:0:CD30:0:0:0:0"

1 Use zero compression. Example: "2001:DB8:0:CD30::"

12.2.20 +CGCONTRDP, PDP Context Read Dynamic

Parameters
Description

The execution command returns the relevant information <bearer_id>, <apn>, <local_addr and subnet_mask>,

<gw_addr>, <DNS_prim_addr>, <DNS_sec_addr>, <P-CSCF_prim_addr>, <P-CSCF_sec_addr>,

<IM_CN_Signalling_Flag>, <LIPA_indication>, <IPv4_MTU> and <WLAN_Offload> for an active non secondary PDP

context with the context identifier <cid>.

If the MT indicates more than two IP addresses of P-CSCF servers or more than two IP addresses of DNS servers,

multiple lines of information per <cid> will be returned.

If the MT has dual stack capabilities, at least one pair of lines with information is returned per <cid>. First one line with

the IPv4 parameters followed by one line with the IPv6 parameters. If this MT with dual stack capabilities indicates more

than two IP addresses of P-CSCF servers or more than two IP addresses of DNS servers, multiple of such pairs of lines
are returned.

NOTE:
If the MT doesn't have all the IP addresses to be included in a line, e.g. in case the UE received
four IP addresses of DNS servers and two IP addresses of P-CSCF servers, the parameter
value representing an IP address that can not be populated is set to an empty string or an absent
string.
If the parameter <cid> is omitted, the relevant information for all active non secondary PDP contexts is
returned.
The test command returns a list of <cid>s associated with active non secondary contexts.

Page 146 of 165

Syntax

Command Possible response(s)

AT+CGCONTRDP=[<cid>] +CGCONTRDP: <cid>,<bearer_id>,<apn>[,<source_addr and
subnet_mask>[,<gw_addr>[,<DNS_prim_addr>[,<DNS_sec_addr

>[,<PCSCF_prim_addr>[,<P-CSCF_sec_addr>[,<IM_CN_Signall

ing_Flag>]]]]]]]
[<CR><LF>+CGCONTRDP: <cid>,<bearer_id>,<apn>

[,<source_addr and subnet

mask>[,<gw_addr>[,<DNS_prim_addr>[,<DNS_sec_addr>[,<P-C
SCF_prim_addr>[,<P-CSCF_sec_addr>[,<IM_CN_Signalling_Fla

g>]]]]]]]

[...]]

AT+CGCONTRDP=? +CGCONTRDP: (list of <cid>s associated with active contexts)

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<cid>: integer type; specifies a particular non secondary PDP context definition. The parameter is local to the TE-MT

interface and is used in other PDP context-related commands (see the +CGDCONT and +CGDSCONT commands).

<bearer_id>: integer type; identifies the bearer, i.e. the EPS bearer in EPS and the NSAPI in UMTS/GPRS.
<apn>: string type; a logical name that was used to select the GGSN or the external packet data network.

<local_addr and subnet_mask>: string type; shows the IP address and subnet mask of the MT. The string is given as

dot-separated numeric (0-255) parameters on the form: "a1.a2.a3.a4.m1.m2.m3.m4" for IPv4 or

"a1.a2.a3.a4.a5.a6.a7.a8.a9.a10.a11.a12.a13.a14.a15.a16.m1.m2.m3.m4.m5.m6.m7.m8.m9.m10.m11.m12.m13.m14

.m15.m16" for IPv6. When +CGPIAF is supported, its settings can influence the format of this parameter returned

with the execute form of +CGCONTRDP.

<gw_addr>: string type; shows the Gateway Address of the MT. The string is given as dot-separated numeric (0-255)

parameters. When +CGPIAF is supported, its settings can influence the format of this parameter returned with the

execute form of +CGCONTRDP.

Page 147 of 165

<DNS_prim_addr>: string type; shows the IP address of the primary DNS server.

When +CGPIAF is supported, its settings can influence the format of this parameter returned with the execute form
of +CGCONTRDP.

<DNS_sec_addr>: string type; shows the IP address of the secondary DNS server.

When +CGPIAF is supported, its settings can influence the format of this parameter returned with the execute form
of +CGCONTRDP.

<P_CSCF_prim_addr>: string type; shows the IP address of the primary P-CSCF server.

When +CGPIAF is supported, its settings can influence the format of this parameter returned with the execute form
of +CGCONTRDP.

<P_CSCF_sec_addr>: string type; shows the IP address of the secondary P-CSCF server.

When +CGPIAF is supported, its settings can influence the format of this parameter returned with the execute form
of +CGCONTRDP.

<IM_CN_Signalling_Flag>: integer type; shows whether the PDP context is for IM CN subsystem-related signalling

onlyor not.
0 PDP context is not for IM CN subsystem-related signalling only

1 PDP context is for IM CN subsystem-related signalling only

12.2.21 +CGSCONTRDP, Secondary PDP Context Read

Dynamic Parameters
Description

The execution command returns <p_cid>, <bearer_id>, <IM_CN_Signalling_Flag> and <WLAN_Offload>

for an active secondary PDP context with the context identifier <cid>.
If the parameter <cid> is omitted, the <cid>, <p_cid>, <bearer_id> and <IM_CN_Signalling_Flag> are
returned for all active secondary PDP contexts.
In EPS, the Traffic Flow parameters are returned.
NOTE: Parameters for UE initiated and network initiated PDP contexts are returned.
The test command returns a list of <cid>s associated with active secondary PDP contexts.

Syntax

Command Possible response(s)

AT+CGSCONTRDP=[<cid>] +CGSCONTRDP:

<cid>,<p_cid>,<bearer_id>[,<IM_CN_Signalling_Flag>][<CR><

Page 148 of 165

 Command Possible response(s)
LF>+CGSCONTRDP:

<cid>,<p_cid>,<bearer_id>[,<IM_CN_Signalling_Flag>][...]]

AT+CGSCONTRDP=? +CGSCONTRDP: (list of <cid>s associated with active contexts)

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<cid>: integer type; specifies a particular active secondary PDP context or Traffic Flows definition. The parameter is

local to the TE-MT interface and is used in other PDP context-related commands (see the +CGDCONT and

+CGDSCONT commands).

<p_cid>: integer type; specifies a particular PDP context definition or default EPS context Identifier which has been

specified by use of the +CGDCONT command. The parameter is local to the TE-MT interface (see the

+CGDSCONT command).

<bearer_id>: integer type; identifies the bearer, EPS Bearer in EPS and NSAPI in UMTS/GPRS.

<IM_CN_Signalling_Flag>: integer type; shows whether the PDP context is for IM CN subsystem-related signalling only
or not.

0 PDP context is not for IM CN subsystem-related signalling only

1 PDP context is for IM CN subsystem-related signalling only

12.2.22 +CGTFTRDP, Traffic Flow Template Read Dynamic

Parameters
Description

This command returns the relevant information about Traffic Flow Template of <cid> together with the
additional network assigned values when established by the network.

Syntax

Command Possible response(s)

AT+CGTFTRDP=[<cid>] +CGTFTRDP: <cid>,<packet filter identifier>,<evaluation

Page 149 of 165

 Command Possible response(s)
vailable index>,<source address and vaila mask>,<protocol vaila

(ipv4) / next header(ipv6)>,<destination port range>,<source

port range>,<ipsec security parameter index (spi)>,<type of

service (tos) (ipv4) and mask / traffic class (ipv6) and

mask>,<flow label (ipv6)>,<direction>,<NW packet filter

Identifier>[<CR><LF>+CGTFTRDP: <cid>,<packet filter

identifier>,<evaluation vailable index>,<source address and

vaila mask>,<protocol vaila (ipv4) / next header

(ipv6)>,<destination port range>,<source port range>,<ipsec

security parameter index (spi)>,<type of service (tos) (ipv4) and

mask / traffic class (ipv6) and mask>,<flow label

(ipv6)>,<direction>,<NW packet filter Identifier> [...]]

AT+CGTFTRDP=? +CGTFTRDP: (list of <cid>s associated with active contexts)

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<cid>: integer type; Specifies a particular secondary or non secondary PDP context definition or Traffic Flows definition

(see +CGDCONT and +CGDSCONT commands).

For the following parameters, see also 3GPP TS 23.060 [47]

<packet filter identifier>: integer type. The value range is from 1 to 16.

<evaluation precedence index>: integer type. The value range is from 0 to 255.
<remote address and subnet mask>: string type. The string is given as dot-separated numeric (0-255) parameters on the

form:"a1.a2.a3.a4.m1.m2.m3.m4" for IPv4 or

"a1.a2.a3.a4.a5.a6.a7.a8.a9.a10.a11.a12.a13.a14.a15.a16.m1.m2.m3.m4.m5.m6.m7.m8.m9.m10.m11.m12.m13.m
14.m15.m16" for IPv6. When +CGPIAF is supported, its settings can influence the format of this parameter

returned with the execute form of +CGTFTRDP.

<protocol number (ipv4) / next header (ipv6)>: integer type. The value range is from 0 to 255.

Page 150 of 165

<local port range>: string type. The string is given as dot-separated numeric (0-65535) parameters on the form "f.t".

<remote port range>: string type. The string is given as dot-separated numeric (0-65535) parameters on the form "f.t".
<ipsec security parameter index (spi)>: numeric value in hexadecimal format. The value range is from 00000000 to

FFFFFFFF.

<type of service (tos) (ipv4) and mask / traffic class (ipv6) and mask>: string type. The string is given as dot-separated
numeric (0-255) parameters on the form "t.m".

<flow label (ipv6)>: numeric value in hexadecimal format. The value range is from 00000 to FFFFF. Valid for IPv6 only.

<direction> integer type. Specifies the transmission direction in which the Packet Filter shall be applied.
0 Pre Release 7 TFT Filter (see 3GPP TS 24.008 [8], table 10.5.162)

1 Uplink

2 Downlink
3 Bidirectional (Used for Uplink and Downlink)

<NW packet filter Identifier> integer type. The value range is from 1 to 16. In EPS the value is assigned by the network

when established

12.2.23 +CSCON, Signalling Connection Status

Description

The set command controls the presentation of an unsolicited result code +CSCON.
If<n>=1,+CSCON:<mode>is sent from the MT when the connection mode of the MT ischanged. If <n>=2
and there is a state within the current mode, +CSCON:<mode>[,<state>] is sent from the MT.When the
MT is in UTRAN or E-UTRAN, the mode of the MT refers to idle when no PSsignalling connection and to
connected mode when a PS signalling connection betweenUE and network is setup. When the UE is in
GERAN, the mode refers to idle when theMT is in either the IDLE state or the STANDBY state and to
connected mode when theMT is in READY state. The <state>value indicates the state of the MT when the
MT is inUTRAN connected mode.
The read command returns the status of result code presentation and an integer<mode>which shows
whether the MT is currently in idle mode or connected mode.State information <state>is returned only
when <n>=2.
Test command returns supported values as compound value.

Syntax

Command Possible response(s)

Page 151 of 165

 AT+CSCON=[<n>] OK

or

+CME ERROR: <err>

AT+CSCON? +CSCON: <n>,<mode>[,<state>]

OK

AT+CSCON=? +CSCON: (list of supported <n>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<n>:integer type

0 disable unsolicited result code; Default value

1 enable unsolicited result code +CSCON: <mode>

2 enable unsolicited result code +CSCON: <mode>[,<state>]

<mode>:integer type; indicates the signalling connection status

0 idle

1 connected
<state>: integer type; indicates the CS or PS state while in GERAN and the RRC state information if the MT is in

connected Mode while in UTRAN and E-UTRAN.

0 UTRAN URA_PCH state

1 UTRAN Cell_PCH state

2 UTRAN Cell_FACH state

3 UTRAN Cell_DCH state

4 GERAN CS connected state

5 GERAN PS connected state

6 GERAN CS and PS connected state

7 E-UTRAN connected state

Page 152 of 165

 12.2.24 +CGEQOS, Define EPS Quality Of Service
Description

The set command allows the TE to specify the EPS Quality of Service parameters <cid>, <QCI>,
[<DL_GBR> and <UL_GBR>] and [<DL_MBR> and <UL_MBR>] for a PDP context or Traffic Flows (see
3GPP TS 24.301 [83] and 3GPP TS 23.203 [85]). When in UMTS/GPRS the MT applies a mapping
function to UTMS/GPRS Quality of Service.
A special form of the set command, +CGEQOS= <cid> causes the values for context number <cid> to
become undefined.
The read command returns the current settings for each defined QoS.
The test command returns the ranges of the supported parameters as compound values.

Syntax

Command Possible response(s)

AT+CGEQOS=[<cid>[,<QCI>[,<DL_GBR>,< OK

UL_GBR>[,<DL_MBR>,<UL_MBR]]]] or

+CME ERROR: <err>

AT+CGEQOS? +CGEQOS: <cid>,<QCI>,

[<DL_GBR>,<UL_GBR>],[<DL_MBR>,<UL_MBR>]

[<CR>>LF>+CGEQOS: <cid>,<QCI>,

[<DL_GBR>,<UL_GBR>],[<DL_MBR>,<UL_MBR>]

[...]]

AT+CGEQOS=? +CGEQOS: (range of supported <cid>s),(list of supported

<QCI>s),(list of supported <DL_G

BR>s),(list of supported <UL_GBR>s),(list of supported <DL

_MBR>s),(list of supported <UL_MBR>s)

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Defined Values

<cid>: integer type; specifies a particular EPS Traffic Flows definition in EPS and a PDP Context definition in

Page 153 of 165

 UMTS/GPRS (see the +CGDCONT and +CGDSCONT commands).

<QCI>: integer type; specifies a class of EPS QoS (see 3GPP TS 23.203 [85] and 3GPP TS 24.301 [83]).
0 QCI is selected by network

[1 – 4] value range for guaranteed bit rate Traffic Flows

[5 – 9] value range for non-guarenteed bit rate Traffic Flows

[128 – 254] value range for Operator-specific QCIs

The QCI values 65, 66, 69 and 70 are not allowed to be requested by the UE. If the TE requests a QCI parameter 65,

66, 69 or 70, the MT responds with result code +CME ERROR: 181 (unsupported QCI value).
<DL_GBR>: integer type; indicates DL GBR in case of GBR QCI. The value is in kbit/s. This parameter is omitted for a

non-GBR QCI (see 3GPP TS 24.301 [83]).

<UL_GBR>: integer type; indicates UL GBR in case of GBR QCI. The value is in kbit/s. This parameter is omitted for a
non-GBR QCI (see 3GPP TS 24.301 [83]).

<DL_MBR>: integer type; indicates DL MBR in case of GBR QCI. The value is in kbit/s. This parameter is omitted for a

non-GBR QCI (see 3GPP TS 24.301 [83]).

<UL_MBR>: integer type; indicates UL MBR in case of GBR QCI. The value is in kbit/s. This parameter is omitted for a

non-GBR QCI (see 3GPP TS 24.301 [83]).

13 Fibocom Proprietary Commands

13.1 Set Profile Commands
13.1.1 +GTUSBMODE, Set USB Configuration Profile
Description

This command change the USB configuration profile of the module. There are two main profiles: AT+NCM
profile for legacy AT command and MBIM profile for Windows 8.1/Windows 10 supporting. The new profile
is activated after a reset or power cycle.

Syntax

Command Possible response(s)

AT+GTUSBMODE=<mode> OK

or:

+CME ERROR: <err>

AT+GTUSBMODE? +GTUSBMODE: <mode>

OK

Page 154 of 165

 AT+GTUSBMODE=? +GTUSBMODE: (list of supported <mode>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No Yes Yes No < 1s

Defined Values

<mode>: integer type and supported mode depends on the target device and they may be as below:

0 Reserve

1 Reserve
2 ECM+5ACM(2EP)

3 MBIM

4 MBIM+2ACM

5 MBIM+3ACM

6 MBIM+GNSS

7 MBIM+GNSS+2ACM

8 NCM+3ACM

9 NCM+ACM(2EP)

10 NCM+2ACM(2EP)
11 3ACM+3NCM

12 4ACM

13 7ACM
14 2ACM(2EP)+ACM

15 ACM(2EP)+ACM

Page 155 of 165

14 Error Handing and Error Code
14.1 Error Handling Commands

14.1.1 +CMEE, Report Mobile Equipment Error

Description

The Set command disable or enable the use of result code +CME ERROR: <err> as an indication of an
error relating to the functionality of the MODEM. When enabled, Modem -related errors cause a +CME
ERROR: <err> final result code instead of the regular ERROR final result code. Usually, ERROR is
returned when the error is related to syntax, invalid parameters or terminal functionality.
For all Accessory AT commands besides SMS commands, the +CMEE set command disable or enable
the use of result code +CME ERROR: <err> as an indication of an error relating to the functionality of the
Modem. When enabled, Modem related errors cause a +CME ERROR: <err> final result code instead of
the regular ERROR result code.
For all SMS AT commands that are derived from GSM 07.05, the +CMEE Set command disable or enable
the use of result code +CMS ERROR: <err> as an indication of an error relating to the functionality of the
modem. When enabled, modem -related errors cause a +CMS ERROR: <err> final result code instead of
the regular ERROR final result.

Syntax

Command Possible response(s)

AT+CMEE=[<n>] OK

or:

+CME ERROR: <err>

Note: the original setting is not changed if

AT+CMEE=

AT+CMEE? +CMEE: <n>

OK

AT+CMEE=? +CMEE: (list of supported <n>s)

OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

Page 156 of 165

 No No Yes Yes < 1s

Defined Values

<n>: integer type

0 Disable the +CME ERROR: <err> result code and use ERROR. Default value

1 Enable the +CME ERROR: <err> or +CMS ERROR: <err> result codes and use numeric <err> values or
+STK ERROR: <err> result codes and use numeric <err> values.

2 Enable the +CME ERROR: <err> or +CMS ERROR: <err> result codes and use verbose <err> values or

+STK ERROR: <err> result codes and use numeric <err> values.

14.1.2 +CEER, Extended Error Report

Description

This execution command returns an extended error report containing one or more lines of information text
<report>, determined by the manufacturer, providing reasons for the following errors:
 Failure in the last unsuccessful call setup (originating or answering) or the in-call modification.
 Last call release.
Typically, the text consists of a single line containing the reason for the error according to information
given by GSM network, in textual format.

Syntax

Command Possible response(s)

AT+CEER +CEER: <category>[,<cause>,<description>]
OK

AT+CEER=? OK

Attributes

Pin Restricted Persistent Sync Mode Effect Immediately Time of duration

No No Yes Yes < 1s

Page 157 of 165

Defined Values

<category>: string type

“No report available”

“CC setup error”

“CC modification error”

“CC release”

“SM attach error”

“SM detach”

“SM activation error”

“SM deactivation”

“SS – network error cause”

“SS – network reject cause”

“SS – network GSM cause”

<cause> : string type; contains a digit representing the error cause sent by network or internally
<description>:string type; contains the textual representation of the Cause

14.2 CME Error

Parameter Description

<Err> 0, "phone failure"

1, "no connection to phone"

2, "phone-adapter link reserved"

3, "operation not allowed"

4, "operation not supported"

5, "PH-SIM PIN required"

6, "PH-FSIM PIN required"

7, "PH-FSIM PUK required"

10, "SIM not inserted"

11, "SIM PIN required"

12, "SIM PUK required"

13, "SIM failure"

14, "SIM busy"

15, "SIM wrong"

Page 158 of 165

Parameter Description

16, "incorrect password"

17, "SIM PIN2 required"

18, "SIM PUK2 required"

19, "incorrect PUK1"

20, "memory full"

21, "invalid index"

22, "not found"

23, "memory failure"

24, "text string too long"

25, "invalid characters in text string"

26, "dial string too long"

27, "invalid characters in dial string"

30, "no network service"

31, "network timeout"

32, "network not allowed - emergency calls only"

40, "network personalisation PIN required"

41, "network personalisation PUK required"

42, "network subset personalisation PIN required"

43, "network subset personalisation PUK required"

44, "service provider personalisation PIN required"

45, "service provider personalisation PUK required"

46, "corporate personalisation PIN required"

47, "corporate personalisation PUK required"

48, "hidden key required"

Note:

This key is required when accessinghidden phonebook entries.)

49, "EAP method not supported"

50, "Incorrect parameters"

100, "unknown"

103, "Illegal MS"

106, "Illegal ME"

107, "GPRS services not allowed"

111, "PLMN not allowed"

Page 159 of 165

Parameter Description

112, "location area not allowed"

113, "roaming not allowed in this location area"

114, "GPRS services not allowed in this PLMN"

116, "MSC temporarily not reachable"

117, "Network failure"

132, "Service not supported"

133, "Service not subscribed"

134, "service option temporarily out of order"

135, "NS-api already used"

148, "Unspecified GPRS error"

149, "PDP authentication error"

150, "invalid mobile class"

244, "Attach failure"

257, "Invalid error mapping"

258, "APN not listed in APN Control List (ACL)"

701, "incorrect security code"

702, "max attempts reached"

1001, "Unassigned (unallocated) number"

1003, "No route to destination"

1006, "Channel unacceptable"

1008, "Operator determined barring"

1016, "Normal call clearing"

1017, "User busy"

1018, "No user responding"

1019, "User alerting, no answer"

1021, "Call rejected"

1022, "Number changed"

1026, "Non selected user clearing"

1027, "Destination out of order"

1028, "Invalid number format (incomplete number)"

1029, "Facility rejected"

1030, "Response to STATUS ENQUIRY"

1031, "Normal, unspecified"

Page 160 of 165

Parameter Description

1034, "No circuit/channel available"

1038, "Network out of order"

1041, "Temporary failure"

1042, "Switching equipment congestion"

1043, "Access information discarded"

1044, "requested circuit/channel not available"

1047, "Resources unavailable, unspecified"

1049, "Quality of service unavailable"

1050, "Requested facility not subscribed"

1055, "Incoming calls barred within the CUG"

1057, "Bearer capability not authorized"

1058, "Bearer capability not presently available"

1063, "Service or option not available, unspecified"

1065, "Bearer service not implemented"

1068, "ACM equal to or greater than ACMmax"

1069, "Requested facility not implemented"

1070, "Only restr. digital information bearer capability"

1079, "Service or option not implemented, unspecified"

1081, "Invalid transaction identifier value"

1087, "User not member of CUG"

1088, "Incompatible destination"

1091, "Invalid transit network selection"

1095, "Semantically incorrect message"

1096, "Invalid mandatory information"

1097, "Message type non-existent or not implemented"

1098, "Message type not compatible with protocol state"

1099, "Information element non-existent or not implemented"

1100, "Conditional IE error"

1101, "Message not compatible with protocol state"

1102, "Recovery on timer expiry"

1111, "Protocol error, unspecified"

1127, "Interworking, unspecified"

1279, "Number not allowed"

Page 161 of 165

Parameter Description

1283, "CCBS possible"

Note: L710、G500、G510 use respectively other error cause instead of above one with below

value:

50, “Execute command failure”

100, NA

14.3 CMS Error

Parameter Description

<Err> 1, "Unassigned (unallocated) number"

8, "Operator determined barring"

10, "Call barred"

17, "Network failure"

21, "Short message transfer rejected"

22, "Memory capacity exceeded"

27, "Destination out of service"

28, "Unidentified subscriber"

29, "Facility rejected"

30, "Unknown Subscriber"

38, "Network out of order"

41, "Temporary failure"

42, "Congestion"
47, "Resources unavailable, unspecified"

50, "Requested facility not subscribed"

69, "Requested facility not implemented"

81, "Invalid short message reference value"

95, "Invalid message, unspecified"

96, "Invalid mandatory information"

97, "Message type non-existent or not implemented"

98, "Message not compatible with short message protocol state"

99, "Information element non-existent or not implemented"

Page 162 of 165

Parameter Description

111, "Protocol error, unspecified"

127, "Interworking unspecified"

128, "Telematic interworking not supported"

129, "Short message type 0 not supported"

130, "Cannot replace short message"

143, "Unspecified TP-PID error"

144, "Data coding scheme (alphabet) not supported"

145, "Message class not supported"

159, "Unspecified TP-DCS error"

160, "Command cannot be action"

161, "Command unsupported"

175, "Unspecified TP-Command error"

176, "TPDU not supported"

192, "SC busy"

193, "No SC subscription"

194, "SC system failure"

195, "Invalid SME address"

196, "Destination SME barred"

197, "SM Rejected-Duplicate SM"

198, "TP-VPF not supported"

199, "TP-VP not supported"

208, "SIM SMS storage full"

209, "No SMS storage capability in SIM"

210, "Error in MS"

211, "Memory Capacity Exceeded"

212, "SIM Application Toolkit Busy"

213, "SIM data download error"

224, "TP_FCS_APPL_ERR_START"

254, "TP_FCS_APPL_ERR_STOP"

255, "TP_FCS_UNSPECIFIED"

300, "ME failure"

301, "SMS service of ME reserved"

302, "operation not allowed"

Page 163 of 165

Parameter Description

303, "operation not supported"

304, "Invalid PDU mode param"

305, "invalid text mode parameter"

310, "SIM not inserted"

311, "SIM PIN required"

312, "PH-SIM PIN necessary"

313, "SIM failure"

314, "SIM busy"

315, "SIM wrong"

317, "SIM PIN2 required"

318, "SIM PUK2 required"

319, "incorrect PUK1"

320, "memory failure"

321, "invalid memory index"

322, "memory full"

330, "SMSC address unknown"

331, "no network service"

332, "network timeout"

340, "no +CNMA acknowledgement expected"

512, "MN_SMS_RP_ACK"

513, "MN_SMS_TIMER_EXPIRED"

514, "MN_SMS_FORW_AVAIL_FAILED"

515, "MN_SMS_FORW_AVAIL_ABORTED"

516, "MS invalid TP-Message-Type-Indicator"

517, "MS no TP-Status-Report in Phase 1"

518, "MS no TP-Reject-Duplicate in Phase 1"

519, "MS no TP-Reply-Path in Phase 1"

520, "MS no TP-User-Data-Header in Phase 1"

521, "MS missing TP-Validity-Period"

522, "MS invalid TP-Service-Centre-Time-Stamp"

523, "MS missing TP-Destination-Address"

524, "MS invalid TP-Destination-Address"

525, "MS missing Service-Centre-Address"

Page 164 of 165

Parameter Description

526, "MS invalid Service-Centre-Address"

527, "MS invalid alphabet"

528, "MS invalid TP-User-Data-Length"

529, "MS missing TP-User-Data"

530, "MS TP-User-Data too long"

531, "MS no Command-Request in Phase 1"

532, "MS Cmd-Req invalid TP-Destination-Address"

533, "MS Cmd-Req invalid TP-User-Data-Length"

534, "MS Cmd-Req invalid TP-User-Data"

535, "MS Cmd-Req invalid TP-Command-Type"

536, "MN MNR creation failed"

537, "MS CMM creation failed"

538, "MS network connection lost"

539, "MS pending MO SM transfer"

540, "RP-Error OK"

541, "RP-Error OK no icon display"

542, "SMS-PP Unspecified"

543, "SMS rejected By SMS CONTROL"

Note: L710、G500、G510 use respectively other error cause instead of above one with below

value:

513, “Unable to store”

514, “Invalid status”

515, “Invalid character in address string”

516, “Invalid length”

517, “Invalid character in pdu”

518, “Invalid parameter”

519, “Invalid length or character”

520, “Invalid character in text”

Page 165 of 165