F02/F03 AT Command User Guide: Release Date: July, 2019
F02/F03 AT Command User Guide: Release Date: July, 2019
F02/F03 AT Command User Guide: Release Date: July, 2019
User Guide
Version: V1.0.0
No part of this manual may be reproduced copied, or transmitted in any form or by any means without
prior written consent of China Mobile IoT Co., Ltd.
The products described in this manual may contain software copyrighted by China Mobile IoT Co., Ltd. and
its potential licensors. No one may in any manner reproduce, distribute, modify, decompile, disassemble,
decrypt, extract, reverse engineer, lease, assign, or sublicense the said software, unless such restrictions are
prohibited by applicable laws or such actions are approved by respective copyright holders.
Trademark Statement
Notice
Some features and functions of the product described in this manual and its accessories depend on the
design and performance of your local network and the software you install. Some features and functionality
may not be available due to local network operators or ISPs, or due to local network settings, or if your
installed software does not support it. Therefore, the descriptions in this manual may not correspond
exactly to the products you purchased or their accessories.
China Mobile IoT Co., Ltd. reserves the right to modify any information in this manual, without prior notice
and does not assume any responsibility.
Limitation of Liability
The contents of this manual are provided "as is" and shall not provide any express or implied warranties,
express or implied, with respect to the contents of this manual, except as may be required by applicable
law, including but not limited to the merchantability or fitness for a particular Specific purpose of the
guarantee.
To the extent permitted by applicable law, China Mobile IoT Co., Ltd. shall in no event be liable for any
special, incidental, indirect, consequential or incidental damages arising from the use of the contents of this
manual and the products described in this manual of any damages, nor will any profit, loss of data, goodwill
or expected savings be compensated.
The maximum liability (this limitation shall not apply to liability for personal injury to the extent applicable
law prohibits such a limitation) of China Mobile IoT arising from the use of the product described in this
manual shall be limited to the amount paid by customers for the purchase of this product.
To export, re-export or import the products (including but not limited to the software and technical data in
the products) described in this manual, customers shall comply with applicable import and export control
laws and regulations.
Privacy Protection
To understand how we protect your personal information, please read our privacy policy.
1
China Mobile IoT Co, Ltd.
Revision History
Version Release Date Author Summary of Change
2
China Mobile IoT Co, Ltd.
Content
REVISION HISTORY .................................................................................................................................. 2
CONTENT................................................................................................................................................... 3
1 INTRODUCTION .................................................................................................................................... 6
3
China Mobile IoT Co, Ltd.
4
China Mobile IoT Co, Ltd.
5
China Mobile IoT Co, Ltd.
1 Introduction
This document provides AT command set supported by 5G F02/F03 Module (Rig). AT commands are
used to configure modem module functionalities according to 3GPP specifications. All those AT
commands in this document are derived from 3GPP TS 27.007, 3GPP TS 27.005, ITU-T V.25ter and also
China Mobile Proprietary Commands.
“AT” / “at” prefix must be set at the beginning of each command line or repeat previous command line
by the characters "A/" or "a/". Default termination character is “Enter <CR>”.
In general cases, commands are followed by a response that includes “<CR> <LF> <response> <CR>
<LF>”. In this document, <CR><LF> are intentionally omitted in the command syntax.
<CR> Carriage Return character, which value is specified with command S3.
<LF> Linefeed character, which value is specified with command S4.
Name enclosed in angle brackets is a syntactical element. Brackets themselves do not appear
<…>
in the command line.
Optional sub-parameter of a command or an optional part of TA information response is
enclosed in square brackets. Brackets themselves do not appear in the command line. When
[…] sub-parameter is not given in parameter type commands, new value equals to its previous
value. In action type commands, action should be done on the basis of the recommended
default setting of the sub-parameter.
6
China Mobile IoT Co, Ltd.
7
China Mobile IoT Co, Ltd.
2 General Commands
2.1 ATI: Request Details Product Information
This command delivers product information.
ATI
Syntax
Possible Response:
Manufacture: <manufacture>
Model:<model>
ATI Revision:<revision>
SVN:<svn>
IMEI:<imei>
+GCAP: <Capability>
Description
Get device manufacture information
Parameter
N/A
Example
ATI
Manufacturer: CMCC
Model: F02
Revision: 2233-2928_30.1.B.10.15
SVN: 15
IMEI: 004400123456789
OK
8
China Mobile IoT Co, Ltd.
AT+GMI
Syntax
Possible Response:
AT+GMI <manufacturer>
+CME ERROR: <err>
AT+GMI=?
Description
Get device manufacture information
Parameter
N/A
Example
AT+GMI
CMCC
OK
AT+GMM
Syntax
Possible Response:
AT+GMM <model>
+CME ERROR: <err>
AT+GMM=?
Description
Get device model information
Parameter
N/A
Example
AT+GMM
F02
OK
9
China Mobile IoT Co, Ltd.
AT+GMR
Syntax
Possible Response:
AT+GMR <Revision>
+CME ERROR: <err>
AT+GMR=?
Description
Get device software information
Parameter
N/A
Example
AT+GMR
2233-2928_30.1.B.10.15
OK
AT+GSN
Syntax
Possible Response:
AT+GSN <IMEI>
+CME ERROR: <err>
AT+GSN=?
Description
Get device IMEI
Parameter
N/A
Example
AT+GSN
004400123456789
OK
10
China Mobile IoT Co, Ltd.
AT+GCAP
Syntax
Possible Response:
AT+GCAP <Capability>
+CME ERROR: <err>
AT+GCAP=?
Description
Get device capability
Parameter
N/A
Example
AT+GCAP
OK
AT/
Syntax
Possible Response:
A/
Re-execute previous command
Parameter
N/A
11
China Mobile IoT Co, Ltd.
AT+CFUN
Syntax
Possible Response:
+CFUN=[<fun>[,<rst>]]
+CME ERROR: <err>
Possible Response:
AT+CFUN? +CFUN: <fun>
+CME ERROR: <err>
Possible Response:
+CFUN=? +CFUN: (list of supported <fun>s),(list of supported <rst>s)
+CME ERROR: <err>
Parameter
<fun> Integer type
0 Minimum functionality
1 Full functionality.
4 Disable both MT transmit and receive RF circuits
5 Factory Test Mode
6 Reset
7 Offline
<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
Example
AT+CFUN=0
OK
AT+CFUN=?
+CFUN: (0-1,4-7),(0-1)
OK
12
China Mobile IoT Co, Ltd.
AT&F
Syntax
AT&F<n>
Parameter
<n>
0 Reset parameters to factory default values
ATE
Syntax
ATE<n>
Description
Enable/disable echo
Parameter
13
China Mobile IoT Co, Ltd.
3 (U)SIM Related
Commands
3.1 AT+CIMI: Request International Mobile Subscriber
Identity (IMSI)
This command is used to query the international Mobile Subscriber Identity (IMSI) which is intended
to permit the TE to identify the individual SIM card or active application in the UICC (GSM or USIM)
that is attached to the MT.
AT+CIMI
Syntax
Possible Response:
AT+CIMI <IMSI>
+CME ERROR: <err>
AT+CIMI
Parameter
N/A
Example
AT+CIMI
466011201613864
OK
14
China Mobile IoT Co, Ltd.
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.
AT+CPIN
Syntax
Possible Response:
AT+CPIN=<pin>[,<newpin>]
+CME ERROR: <err>
Possible Response:
AT+CPIN? +CPIN: <code>
+CME ERROR: <err>
AT+CPIN=?
Parameter
<pin>
String type values
<newpin>
String type values
<code>
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
MT is waiting SIM PIN2 to be given (this <code> is recommended to be
returned only
SIM PIN2 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)
MT is waiting SIM PUK2 to be given (this <code> is recommended to be
returned only when the last executed command resulted in PUK2
SIM 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
MT is waiting network subset personalization unblocking password to be
PH-NETSUB PUK
given
15
China Mobile IoT Co, Ltd.
AT+CPIN
Parameter
<code>(Continued.)
PH-SP PIN MT is waiting service provider personalization password to be given
MT is waiting service provider personalization unblocking password to be
PH-SP PUK
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
Example
AT+CPIN?
+CPIN: SIM PIN
AT+CPIN=8888
OK
16
China Mobile IoT Co, Ltd.
AT+CPWD
Syntax
AT+CPWD=<fac>,<oldpwd>, Possible Response:
<newpwd> +CME ERROR: <err>
Possible Response:
AT+CPWD=? +CPWD: list of supported (<fac>,<pwdlength>)s
+CME ERROR: <err>
Parameter
<fac>
All barring services (refer to 3GPP TS 22.030, applicable only for
“AB”
<mode>=0)
All incoming barring services (refer to 3GPP TS 22.030, applicable only
“AC
for <mode>=0)
All outgoing barring services (refer to 3GPP TS 22.030, applicable only
“AG”
for <mode>=0)
“AI” BAIC (Bar All Incoming Calls, refer to 3GPP TS 22.088 clause 2)
“AO” BAOC (Bar All Outgoing Calls, refer to 3GPP TS 22.088 clause 1)
BIC-Roam (Bar Incoming Calls when Roaming outside the home
“IR”
country, refer to 3GPP TS 22.088 clause 2)
BOIC (Bar Outgoing International Calls, refer to 3GPP TS 22.088 clause
“OI”
1)
BOIC-exHC (Bar Outgoing International Calls except to Home Country,
“OX”
refer to 3GPP TS 22.088 clause 1)
(U)SIM (lock SIM/UICC card) (SIM/UICC asks password in MT power-
“SC”
up and when this lock command is issued)
“P2” (U)SIM PIN2
<oldpwd>, <newpwd>
String type
<pwdlength>
Integer type maximum length of the password for the facility.
17
China Mobile IoT Co, Ltd.
AT+CRSM
Syntax
AT+CRSM=<command>
Possible Response:
[,<fileid>[,<P1>,<P2>,<P3>
+CRSM: <sw1>,<sw2>[,<response>]
[,<data>[,<pathid>]]]]
AT+CRSM=?
Parameter
<command>
176 READ BINARY
178 READ RECORD
192 GET RESPONSE
214 UPDATE BINARY
220 UPDATE RECORD
242 STATUS
203 RETRIEVE DATA
219 SET DATA
<fileid>
Integer type; this is the identifier of a elementary datafile on SIM.
<P1>, <P2>, <P3>
Integer type
18
China Mobile IoT Co, Ltd.
AT+ICCID
Syntax
AT+ICCID=?
Possible Response:
AT+ICCID
<ICCID>
Description
Query ICCID
Parameter
N/A
Example
AT+ICCID
ICCID: 89886012137811234567
OK
AT+CSIM
Syntax
Possible Response:
AT+CSIM=?
OK
Possible Response:
AT+CSIM=
+CSIM: <length>,<response>
<length>,<command>
+CME ERROR: <err>
Parameter
<length>
Integer type; length of the characters that are sent to TE in <command> or <response>
<command>
Command passed on by the MT to the SIM in the format as described in 3GPP TS 51.011. The default format
is “IRA”.
Example
AT+CSIM=14,"A0A40000027F20"
+CSIM: 4,"6E00"
OK
19
China Mobile IoT Co, Ltd.
4 Network Service
Commands
4.1 AT+CREG: Network Registration Status
Set command is used to controls the presentation of an unsolicited result code.
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.
AT+CREG
Syntax
Possible Response:
AT+CREG=<n>
+CME ERROR: <err>
Possible Response:
AT+CREG? +CREG: <n>,<stat>[,[<lac>],[<ci>],[<AcT>]
[,<cause_type>,<reject_cause>]]
Possible Response:
AT+CREG=?
+CREG: (list of supported <n>s)
Parameter
20
China Mobile IoT Co, Ltd.
Read command returns the current mode, the currently selected operator and the current Access
Technology.
AT+COPS
Syntax
AT+COPS=[<mode>[,<format> Possible Response:
[,<oper>[,<AcT>]]]] +CME ERROR: <err>
Possible Response:
+COPS: <mode>[,<format>,<oper>[,<AcT>]]
AT+COPS?
or
21
China Mobile IoT Co, Ltd.
AT+COPS
Parameter
<AcT> Integer type; access technology selected
0 GSM
1 GSM Compact
2 UTRAN
3 GSM w/EGPRS
4 UTRAN w/HSDPA
5 UTRAN w/HSUPA
6 UTRAN w/HSDPA and HSUPA
7 E-UTRAN
Example
AT+COPS=?
+COPS: (1,"Far EasTone","FET","46601",7),(2,"Far EasTone","FET","46601",2),(3,"TWN
APT","APT","46605",0),(1,"TW Mobile","TWM","46697",2),(3,"Chunghwa
Telecom","Chunghwa","46692",2),(1,"T Star","T Star","46689",2),(1,"TW
Mobile","TWM","46697",7),(3,"Chunghwa Telecom","Chunghwa","46692",7),(1,"T Star","T
Star","46689",7),(3,"TWN APT","APT","46605",7),,(0,1,2,3,4),(0,1,2)
OK
AT+COPS?
+COPS: 0,0,"Far EasTone",2
OK
22
China Mobile IoT Co, Ltd.
AT+CSQ
Syntax
Possible Response:
+CSQ: <rssi>,<ber>
AT+CSQ
or
<rssi>
0 -113 dBm or less
1 -111 dBm
2...30 -109... -53 dBm
31 -51 dBm or greater
99 Not known or not acceptable
<ber>
0...7 As RXQUAL values in the table in 3GPP TS 45.008 [20] subclause 8.2.4
99 Not known or not detectable
Example
AT+CSQ
+CSQ: 17,99
OK
AT+CSQ=?
+CSQ: (0-31,99),(0-7,99)
23
China Mobile IoT Co, Ltd.
Read command returns the selected PLMN selector list from the SIM/USIM
Test command returns the whole index range supported lists by the SIM/USIM as a compound value.
AT+CPLS
Syntax
Possible Response:
AT+CPLS=[<list>]
+CME ERROR: <err>
Possible Response:
+CPLS: <list>
AT+CPLS?
or
<list>
The device will read the user controlled PLMN list from different EFs
based on the following priority:
0
1. EFPLMNwACT
2. EFPLMNsel
Operator controlled PLMN selector with Access Technology
1
EFOPLMNwAcT
2 HPLMN selector with Access Technology EFHPLMNwAcT
Example
AT+CPLS=?
+CPLS: 0,1,2
OK
AT+CPLS=1
OK
AT+CPLS?
+CPLS: 1
OK
24
China Mobile IoT Co, Ltd.
Execute command writes an entry in the SIM/USIM list of preferred PLMNs, previously selected by the
command +CPLS. If no list has been previously selected, the User controlled PLMN selector with
Access Technology, is the one accessed by default.
AT+CPOL
Syntax
AT +CPOL=[<index>] [,<for
mat> [,<oper>[,<GSM_Ac
T>,<GSM_Compact_AcT>, Possible Response:
<UTRAN_AcT>, <E- +CME ERROR: <err>
UTRAN_AcT>,<NG-
RAN_AcT>]]]
Possible Response:
+CPOL: <index1>,<format>,<oper1>[,<GSM_AcT1>,<
GSM_Compact_AcT1>,<UTRAN_AcT1>,<E-
UTRAN_AcT1>,<NG-RAN_AcT1>]
AT+CPOL? [<CR><LF>+CPOL: <index2>,<format>,<oper2>[,<GS
M_AcT2>,<GSM_Compact_AcT2>,<UTRAN_AcT2>,<E-
UTRAN_AcT2,<NG-RAN_AcT2>>]
[...]]
+CME ERROR: <err>
Possible Response:
+CPOL: (list of supported <index>s),(list of supported
AT+CPOL=?
<format>s)
+CME ERROR: <err>
Parameter
25
China Mobile IoT Co, Ltd.
AT+CPOL
Parameter
<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
<NG-RAN_AcTn> Integer type; NG-RAN access technology
0 Access technology not selected
1 Access technology selected
26
China Mobile IoT Co, Ltd.
AT+COPN
Syntax
Possible Response:
+COPN: <numeric1>,<alpha1>
[<CR><LF>+COPN: <numeric2>,<alpha2>
AT+COPN [...]]
or
27
China Mobile IoT Co, Ltd.
AT+WS46
Syntax
Possible Response:
AT+WS46=[<n>]
OK
Possible Response:
AT+WS46?
<n>
Possible Response:
AT+WS46=?
(list of supported <n>s)
Parameter
28
China Mobile IoT Co, Ltd.
ATA
Syntax
Possible Response:
ATA
OK
Parameter
N/A
Example
RING
ATA
OK
ATD
Syntax
Possible Response:
ATD<number>[;]
OK
Parameter
<number>
Valid phone digits are 0 1 2 3 4 5 6 7 8 9 * # +
Semicolon(;)
Valid phone digits are 0 1 2 3 4 5 6 7 8 9 * # +
12 GSM Digital Cellular Systems (GERAN only)
22 UTRAN only
25 3GPP Systems (GERAN, UTRAN and E-UTRAN)
28 E-UTRAN only
29 GERAN and UTRAN
Example
ATD0912345678; //Voice Call
OK
29
China Mobile IoT Co, Ltd.
ATH
Syntax
Possible Response:
ATH
OK
Parameter
N/A
Example
ATD0912345678;
OK
ATH
OK
AT+CVHU
Syntax
Possible Response:
ATD<number>[;]
OK
Parameter
<mode>
0 ATH disconnect
1 ATH ignored
Example
AT+CVHU=0
OK
AT+CVHU?
+CVHU:0
OK
RING
ATH
OK
30
China Mobile IoT Co, Ltd.
AT+CHUP
Syntax
AT+CHUP
AT+CVHU=?
Parameter
N/A
Example
AT+CVHU=0
OK
AT+CVHU?
+CVHU:0
OK
31
China Mobile IoT Co, Ltd.
AT+CLCC
Syntax
Possible Response:
[+CLCC: <ccid1>,<dir>,<stat>,<mode>,<mpty>[,<number>
,<type>[,<alpha>[,<priority>[,<CLI validity>]]]]
AT+CLCC
[<CR><LF>+CLCC: <ccid2>,<dir>,<stat>,<mode>,<mpty>[,
<number>,<type>[,<alpha>[,<priority>[,<CLI validity>]]]] [...]]]
+CME ERROR: <err>
AT+CLCC?
Parameter
<ccidx>
Integer type, call identification number.
<dir> Integer type
0 Mobile originated (MO) call
1 Mobile terminated (MO) call
<stat> Integer type, state of the call.
0 Active
1 Held
2 Dialing (MO call)
3 Alerting (MO call)
4 Incoming (MT call)
5 Waiting (MT call)
<mode> Integer type, bearer/Teleservice.
0 Voice
1 Data
<mpty> Integer type
0 Call is not one of multiparty (conference) call parties
1 Call is one of multiparty (conference) call parties
<number>
String type. Phone number in format specified by <type>.
<type>
Type of address octet in integer format.
<alpha>
String type. Alphanumeric representation of <number> corresponding to the entry found in phonebook.
32
China Mobile IoT Co, Ltd.
AT+CEER
Syntax
Possible Response:
AT+CEER
+CEER: <report>
AT+CEER=?
Parameter
N/A
Example
AT+CEER
+CEER: Client ended call
OK
33
China Mobile IoT Co, Ltd.
AT+CSMS
Syntax
Possible Response:
AT+CSMS=<service> +CSMS: <mt>,<mo>,<bm>
+CMS ERROR: <err>
Possible Response:
AT+CSMS?
+CSMS: <service>,<mt>,<mo>,<bm>
Possible Response:
AT+CSMS=?
+CSMS: (list of supported <service>s)
Parameter
34
China Mobile IoT Co, Ltd.
AT+CMGF
Syntax
AT+CMGF=[<mode>]
Possible Response:
AT+CMGF?
+CMGF: <mode>
Possible Response:
AT+CMGF=?
+CMGF: (list of supported <mode>s)
Parameter
AT+CSCA
Syntax
AT+CSCA=<sca>[,<tosca>]
Possible Response:
AT+CSCA?
+CSCA: <sca>,<tosca>
AT+CSCA=?
Parameter
<sca>
Service address, GPP TS 24.011 RP SC address Address-Value field in string format. BCD numbers (or GSM 7
bit default alphabet characters) are converted to characters of the currently selected TE character set (refer to
command AT+CSCS in 3GPP TS 27.007); type of address is given by <tosca>.
<tosca>
Type of service center address. 3GPP TS 24.011 RP SC address Type-of-Address octet in integer format
(default refer to <toda>).
Example
AT+CSCA=?
+CSCA: "+886931000099",145
35
China Mobile IoT Co, Ltd.
AT+CPMS
Syntax
Possible Response:
AT+CPMS=<mem1>[,<me
+CPMS: <used1>,<total1>,<used2>,<total2>,<used3>,<total3>
m2>[,<mem3>]]
+CMS ERROR: <err>
Possible Response:
+CPMS: <mem1>,<used1>,<total1>,<mem2>,<used2>,<total2>,
AT+CPMS?
<mem3>,<used3>,<total3>
+CMS ERROR: <err>
Possible Response:
AT+CPMS=? +CPMS: (list of supported <mem1>s),(list of supported <mem2>s),
(list of supported <mem3>s)
Parameter
36
China Mobile IoT Co, Ltd.
AT+CMGD
Syntax
AT+CMGD=<index> Possible Response:
[,<delflag>] +CMS ERROR: <err>
Possible Response:
AT+CMGD=?
+CMGD: (list of supported <index>s)[,(list of supported <delflag>s)]
Parameter
37
China Mobile IoT Co, Ltd.
AT+CMGL
Syntax
Possible Response:
If PDU mode (+CMGF=0) and command successful:
+CMGL: <index>,<stat>,[<alpha>],<length><CR><LF><pdu>
[<CR><LF>+CMGL:<index>,<stat>,[<alpha>],<length><CR><LF><pdu>
AT+CMGL[=<stat>]
[...]]
otherwise
38
China Mobile IoT Co, Ltd.
AT+CMGR
Syntax
Possible Response:
If PDU mode (+CMGF=0) and command successful:
+CMGR: <stat>,[<alpha>],<length><CR><LF><pdu>
AT+CMGR=<index>
otherwise
<index>
Integer type. Index in the associated memory.
39
China Mobile IoT Co, Ltd.
AT+CMGS
Syntax
Possible Response:
If PDU mode (AT+CMGF=0): If PDU mode (+CMGF=0) and sending successful:
+CMGS=<length><CR> +CMGS: <mr>[,<ackpdu>]
PDU is given<ctrl-Z/ESC>
If text mode (+CMGF=1) and sending successfully:
If text mode (AT+CMGF=1): +CMGS: <mr>
AT+CMGS=<da>[,<toda>]<CR>
text is entered <Ctrl+Z/ESC> If sending fails:
+CMS ERROR: <err>
AT+CMGS=?
Parameter
<length>
Message length, integer type. Indicating in the text mode (AT+CMGF=1) the length of the message body
<data> (or <cdata>) in characters, or in PDU mode (AT+CMGF=0), the length of the actual TP data unit in
octets (i.e. the RP layer SMSC address octets are not counted in the length).
<mr>
Message reference. 3GPP TS 23.040 TP-Message-Reference in integer format.
<da>
Destination address. 3GPP TS 23.040 TP-Destination-Address Address-Value field in string format. BCD
numbers are converted to characters of the currently selected TE character set (refer to command AT+CSCS
in 3GPP TS 27.007). The type of address is given by <toda>.
<toda>
Type of recipient address. 3GPP TS 24.011 TP-Recipient-Address Type-of-Address octet in integer format.
40
China Mobile IoT Co, Ltd.
AT+CMMS
Syntax
AT+CMMS=[<n>]
Possible Response:
AT+CMMS?
+CMMS: <n>
Possible Response:
AT+CMMS=?
+CMMS: (list of supported <n>s)
Parameter
<n>
0 Disable
Keep enabled until the time between the response of the latest message
send command (+CMGS, +CMSS, etc.) and the next send command
1
exceeds 1-5 seconds (the exact value is up to ME implementation), then
ME shall close the link and TA switches <n> automatically back to 0.
Enable (if the time between the response of the latest message send
command and the next send command exceeds 1-5 seconds (the exact
2
value is up to ME implementation), ME shall close the link but TA shall not
witch automatically back to <n>=0).
Type of recipient address. 3GPP TS 24.011 TP-Recipient-Address Type-of-
3
Address octet in integer format.
41
China Mobile IoT Co, Ltd.
AT+CMGW
Syntax
If PDU mode (AT+CMGF=0):
AT+CMGW=<length>[,<stat>]<CR>
PDU is given<ctrl-Z/ESC> Possible Response:
+CMGW: <index>
If text mode (AT+CMGF=1):
AT+CMGW=<oa/da>[,<tooa/toda> or
<da>
Destination address. 3GPP TS 23.040 TP-Destination-Address Address-Value field in string format. BCD
numbers (or GSM 7 bit default alphabet characters) are converted to characters of the currently selected TE
character set (refer to AT+CSCS command in 3GPP TS 27.007). The type of address is given by <toda>.
<oa>
Originating address. 3GPP TS 23.040 TP-Originating-Address Address-Value field in string format. BCD
numbers (or GSM 7 bit default alphabet characters) are converted to characters of the currently selected TE
character set (refer to AT+CSCS command in 3GPP TS 27.007). The type of address is given by <tooa>.
<tooa>
Type of originating address. 3GPP TS 24.011 TP-Originating-Address Type-of-Address octet in integer format
(default refer to <toda>).
<stat> In text mode:
“REC UNREAD” Received unread messages
“REC READ” Received read messages
“STO UNSENT” Stored unsent messages
“STO SENT” Stored sent messages
“ALL” All messages
<stat> In PDU mode:
0 Received unread messages
1 Received read messages
2 Stored unsent messages
3 Stored sent messages
4 All messages
<toda>
Type of recipient address. 3GPP TS 24.011 TP-Recipient-Address Type-of-Address octet in integer format.
42
China Mobile IoT Co, Ltd.
AT+CMGW
Parameter
<length>
Message length, integer type. Indicating in the text mode (AT+CMGF=1) the length of the message body
<data> (or <cdata>) in characters, or in PDU mode (AT+CMGF=0), the length of the actual TP data unit in
octets (i.e. the RP layer SMSC address octets are not counted in the length).
<pdu>
In the case of SMS: 3GPP TS 24.011 SC address followed by 3GPP TS 23.04 TPDU in hexadecimal format:
ME/TA converts each octet of TP data unit into two IRA character long hexadecimal number (e.g. octet with
integer value 42 is presented to TE as two characters 2A (IRA 50 and 65)).
<index>
Index of message in selected storage <mem2>.
43
China Mobile IoT Co, Ltd.
AT+CMSS
Syntax
Possible Response:
If PDU mode (+CMGF=0) and sending successful:
+CMSS: <mr>[,<ackpdu>]
AT+CMSS=<index>[,<da>
If text mode (AT+CMGF=1) and sending successful:
[,<toda>]]
+CMSS: <mr>[,<scts>]
If sending fails:
+CMS ERROR: <err>
AT+CMSS=?
Parameter
<index>
Integer type. In the range of location numbers supported by the associated memory.
<da>
Destination Address. 3GPP TS 23.040 TP-Destination-Address Address-Value field in string format. BCD
numbers (or GSM 7 bit default alphabet characters) are converted to characters of the currently selected TE
character set (refer to AT+CSCS command in 3GPP TS 27.007). The type of address is given by <toda>.
<toda>
Type of recipient address. 3GPP TS 24.011 TP-Recipient-Address Type-of-Address octet in integer format.
<mr>
Message reference. 3GPP TS 23.040 TP-Message-Reference in integer format.
<scts>
Service center time stamp. 3GPP TS 23.040 TP-Service-Centre-Time-Stamp in time-string format (refer to
<dt>).
<ackpdu>
The format is same as <pdu> in case of SMS, but without 3GPP TS 24.011 SC address field and parameter
shall be bounded by double quote characters like a normal string type parameter.
44
China Mobile IoT Co, Ltd.
AT+CSDH
Syntax
AT+CSDH=[<show>]
Possible Response:
AT+CSDH?
+CSDH: <show>
Possible Response:
AT+CSDH=?
+CSDH: (list of supported <show>s)
Parameter
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,
0 +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>
1 show the values in result codes
Example
AT+CSDH=?
+CPMS: (0-1)
OK
AT+CSDH?
+CSDH: 0
OK
45
China Mobile IoT Co, Ltd.
AT+CSMP
Syntax
AT+CSMP=[<fo>[,<vp>
[,<pid>[,<dcs>]]]]
Possible Response:
AT+CSMP?
+CSMP: <fo>,<vp>,<pid>,<dcs>
AT+CSMP=?
Parameter
<fo>
First octet. Depending on the command or result code: First octet of 3GPP TS 23.040 SMS-DELIVER, SMS-
SUBMIT (default 17), SMS-STATUS-REPORT, SMS-COMMAND in integer format. If a valid value has been
entered once, the parameter can be omitted.
<vp>
Validity period. Depending on SMS-SUBMIT <fo> setting: 3GPP TS 23.040 TP-Validity-Period either in
integer format or in time-string format (refer to <dt>).
<pid>
Protocol identifier. 3GPP TS 23.040 TP-Protocol-Identifier in integer format (default 0).
<dcs>
Data coding scheme. Depending on the command or result code: 3GPP TS 23.038 SMS Data Coding Scheme
(default 0), or Cell Broadcast Data Coding Scheme in integer format.
46
China Mobile IoT Co, Ltd.
AT+CRES
Syntax
Possible Response:
AT+CRES[=<profile>]
+CMS ERROR: <err>
Possible Response:
AT+CRES=?
+CRES: (list of supported <profile>s)
Parameter
AT+CSCB
Syntax
AT+CSCB=[<mode>[,<mids>
[,<dcss>]]]
Possible Response:
AT+CSCB?
+CSCB: <mode>,<mids>,<dcss>
Possible Response:
AT+CSCB=?
+CSCB: (list of supported <mode>s)
Parameter
47
China Mobile IoT Co, Ltd.
7 Packet Domain
Commands
7.1 AT+CGATT: PS Attach or Detach
The execution command is used to attach the MT to, or detach the MT from, the Packet Domain
service. The read command returns the current Packet Domain service state. The test command is
used for requesting information on the supported Packet Domain service states.
AT+CGATT
Syntax
Possible Response:
AT+CGATT=<state>
+CME ERROR: <err>
Possible Response:
AT+CGATT?
+CGATT: <state>
Possible Response:
AT+CGATT =?
+CGATT: (list of supported <state>s)
Parameter
0 Detached
1 Attached
Example
AT+CGATT=1
OK
AT+CGATT?
+CGATT: 1
48
China Mobile IoT Co, Ltd.
The read command returns the current settings for each defined context.
AT+CGDCONT
Syntax
AT+CGDCONT=[<cid>[,<PDP_type>
[,<APN>[,<PDP_addr>[,<d_comp>
[,<h_comp>[,<IPv4AddrAlloc>
[,<request_type>[,<P-CSCF_discovery>
[,<IM_CN_Signalling_Flag_Ind>[,<NSLPI>
[,<securePCO>[,<IPv4_MTU_discovery>
Possible Response:
[,<Local_Addr_Ind>
+CME ERROR: <err>
[,<Non-IP_MTU_discovery>
[,<Reliable_Data_Service>
[,<SSC_mode>[,<S-NSSAI>
[,<Pref_access_type>[,<RQoS_ind>
[,<MH6-PDU>[,<Always-
on_ind> ]]]]]]]]]]]]]]]]]]]]]]
Possible Response:
[+CGDCONT:<cid>,<PDP_type>,<APN>,<PDP_addr>,
<d_comp>,<h_comp>[,<IPv4AddrAlloc>[,<request_type>[,<P-
CSCF_discovery>[,<IM_CN_Signalling_Flag_Ind>
[,<NSLPI>[,<securePCO>[,<IPv4_MTU_discovery>
[,<Local_Addr_Ind>[,<Non-IP_MTU_discovery>
[,<Reliable_Data_Service>[,<SSC_mode>[,<S-NSSAI>
[,<Pref_access_type>[,<RQoS_ind>[,<MH6-PDU>
[,<Always-on_ind>]]]]]]]]]]]]]]]]]
AT+CGDCONT?
[<CR><LF>+CGDCONT:
<cid>,<PDP_type>,<APN>,<PDP_addr>,<d_comp>,
<h_comp>[,<IPv4AddrAlloc>[,<request_type>[,<P-
CSCF_discovery>[,<IM_CN_Signalling_Flag_Ind>[,<NSLPI>
[,<securePCO>[,<IPv4_MTU_discovery>[,<Local_Addr_Ind>
[,<Non-IP_MTU_discovery>[,<Reliable_Data_Servi
ce>[,<SSC_mode>[,<S-NSSAI>[,<Pref_access_type>
[,<RQoS_ind>[,<MH6-PDU>[,<Always-on_ind>]]]]]]]]]]]]]]]]
[...]]
49
China Mobile IoT Co, Ltd.
AT+CGDCONT
Syntax
Possible Response:
+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),
(list of supported <NSLPI>s),(list of supported <securePCO>s),
(list of supported <IPv4_MTU_discovery>s),
(list of supported <Local_Addr_Ind>s),
(list of supported <Non-IP_MTU_discovery>s),
(list of supported <Reliable_Data_Service>s),
(list of supported <SSC_mode>s),,
(list of supported <Pref_access_type>s),
(list of supported <RQoS_ind>s),
(list of supported <MH6-PDU>s),
(list of supported <Always-on_ind>s)[<CR><LF>
+CGDCONT: (range of supported <cid>s),<PDP_type>,,,
AT+CGDCONT=?
(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),
(list of supported <NSLPI>s),(list of supported <securePCO>s),
(list of supported <IPv4_MTU_discovery>s),
(list of supported <Local_Addr_Ind>s),
(list of supported <Non-IP_MTU_discovery>s),
(list of supported <Reliable_Data_Service>s),
(list of supported <SSC_mode>s),,
(list of supported <Pref_access_type>s),
(list of supported <RQoS_ind>s),
(list of supported <MH6-PDU>s),
(list of supported <Always-on_ind>s)
[...]]
50
China Mobile IoT Co, Ltd.
AT+CGDCONT
Parameter
<cid>
Integer type; specifies a particular PDP context definition.
<PDP_type> String type; specifies the type of packet data protocol.
IP Internet Protocol
IPV6 Internet Protocol, version 6
Virtual <PDP_type> introduced to handle dual IP stack UE
IPV4V6
capability.
PPP Point to Point Protocol
Non-IP Transfer of Non-IP data to external packet data network
Ethernet Ethernet protocol (IEEE 802.3)
Unstructured Transfer of Unstructured data to the Data Network via N6
<APN>
String type; a logical name that is used to select the GGSN or the external packet data network.
<PDP_addr>
String type; identifies the MT in the address space applicable to the PDP.
<d_comp> Integer type; controls PDP data compression (applicable for SNDCP only)
0 Off
1 On
2 V.42bis
3 V.44
<h_comp> Integer type; controls PDP header compression
0 Off
1 On
2 RFC 1144(applicable for SNDCP only)
3 RFC 2507
4 RFC 3095(applicable for PDCP only)
<IPv4AddrAlloc> Integer type; controls how the MT/TA requests to get the IPv4 address information
0 IPv4 address allocation through NAS signaling
1 IPv4 address allocated through DHCP
<request_type> Integer type; indicates the type of PDP context activation request for the PDP context
PDP context is for new PDP context establishment or for
0
handover from a non-3GPP access network
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
PDP context is for handover of emergency (bearer) services
4
from a non-3GPP access network
51
China Mobile IoT Co, Ltd.
AT+CGDCONT
Parameter
<P-CSCF_discovery> Integer type; influences how the MT/TA requests to get the P-CSCF address
Preference of P-CSCF address discovery not influenced by
0
+CGDCONT
1 Preference of P-CSCF address discovery through NAS signaling
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 signaling only or not.
UE indicates that the PDP context is not for IM CN subsystem-
0
related signaling only
UE indicates that the PDP context is for IM CN subsystem-
1
related signaling only
<NSLPI> Integer type; indicates the NAS signaling priority requested for this PDP context
Indicates that this PDP context is to be activated with the value
0
for the low priority indicator configured in the MT.
Indicates that this PDP context is to be activated with the value
for the low
1
priority indicator set to "MS is not configured for NAS
signaling low priority"
<securePCO> Integer type. Specifies if security protected transmission of PCO is requested or not
(applicable for PS only, see 3GPP TS 23.401)
0 Security protected transmission of PCO is not requested
1 Security protected transmission of PCO is requested
<IPv4_MTU_discovery> Integer type; influences how the MT/TA requests to get the IPv4 MTU size
Preference of IPv4 MTU size discovery not influenced by
0
+CGDCONT
1 Preference of IPv4 MTU size discovery through NAS signaling
<Local_Addr_Ind> Integer type; indicates to the network whether or not the MS supports local IP address in
TFTs
0 Indicates that the MS does not support local IP address in TFTs
1 Indicates that the MS supports local IP address in TFTs
<Non-IP_MTU_discovery> Integer type; influences how the MT/TA requests to get the Non-IP MTU size
Preference of Non-IP MTU size discovery not influenced by
0
+CGDCONT
Preference of Non-IP MTU size discovery through NAS
1
signaling
<Reliable_Data_Service> Integer type; indicates whether the UE is using Reliable Data Service for a PDN
connection or not
0 Reliable Data Service is not being used for the PDN connection
1 Reliable Data Service is being used for the PDN connection
52
China Mobile IoT Co, Ltd.
AT+CGDCONT
Parameter
<SSC_mode> Integer type; indicates the session and service continuity (SSC) mode for the PDU session in
5GS.
0 Indicates that the PDU session is associated with SSC mode 1
1 Indicates that the PDU session is associated with SSC mode 2
2 Indicates that the PDU session is associated with SSC mode 3
<S-NSSAI>
String type; indicates the S-NSSAI associated with the PDU session for identifying a network slice in 5GS.
<Pref_access_type> Integer type; indicates the preferred access type for the PDU session in 5GS.
0 Indicates that the preferred access type is 3GPP access
1 Indicates that the preferred access type is non-3GPP access
<RQoS_ind> Integer type; indicates whether the UE supports reflective QoS for the PDU session.
Indicates that reflective QoS is not supported for the PDU
0
session
1 Indicates that reflective QoS is supported for the PDU session
<MH6-PDU> Integer type; indicates whether the UE supports IPv6 multi-homing for the PDU session.
Indicates that IPv6 multi-homing is not supported for the PDU
0
session
Indicates that IPv6 multi-homing is supported for the PDU
1
session
<Always-on_ind> Integer type; indicates whether the PDU session is an always-on PDU session.
0 Indicates that the PDU session is not an always-on PDU session
1 Indicates that the PDU session is an always-on PDU session
53
China Mobile IoT Co, Ltd.
AT+CGQREQ
Syntax
AT+CGQREQ=[<cid>
[,<precedence>[,<delay>
[,<reliability>[,<peak>
[,<mean>]]]]]]
Possible Response:
[+CGQREQ: <cid>,<precedence>,<delay>,<reliability>,<peak>,<mean>]
AT+CGQREQ? [<CR><LF>+CGQREQ:<cid>,<precedence>,<delay>,<reliability>,
<peak>,<mean>
[...]]
Possible Response:
+CGQREQ: <PDP_type>,(list of supported <precedence>s),
(list of supported <delay>s),(list of supported <reliability>s),
(list of supported <peak>s),
AT+CGQREQ=? (list of supported <mean>s) [<CR><LF>+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)
[...]]
Parameter
<cid>
Integer type; specifies a particular PDP context definition
<PDP_type>
String type; specifies the type of packet data protocol
<precedence>
Integer type; specifies the precedence class
<delay>
Integer type; specifies the delay class
<reliability>
Integer type; specifies the reliability class
<peak>
Integer type; specifies the peak throughput class
<mean>
Integer type; specifies the mean throughput class
54
China Mobile IoT Co, Ltd.
AT+CGQMIN
Syntax
AT+CGQMIN=[<cid>
[,<precedence>[,<delay>
[,<reliability>[,<peak>
[,<mean>]]]]]]
Possible Response:
[+CGQMIN:<cid>,<precedence>,<delay>,<reliability>,<peak>,<mean>]
AT+CGQMIN? [<CR><LF>+CGQMIN:<cid>,<precedence>,<delay>,<reliability>,<peak>,
<mean>
[...]]
Possible Response:
+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)
AT+CGQMIN=?
[<CR><LF>+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)
[...]]
Parameter
<cid>
Integer type; specifies a particular PDP context definition
<PDP_type>
String type; specifies the type of packet data protocol
<precedence>
Integer type; specifies the precedence class
<delay>
Integer type; specifies the delay class
<reliability>
Integer type; specifies the reliability class
<peak>
Integer type; specifies the peak throughput class
<mean>
Integer type; specifies the mean throughput class
55
China Mobile IoT Co, Ltd.
AT+CGACT
Syntax
AT+CGACT=[<state>[,<cid> Possible Response:
[,<cid>[,...]]]] +CME ERROR: <err>
Possible Response:
[+CGACT: <cid>,<state>]
AT+CGACT?
[<CR><LF>+CGACT: <cid>,<state>
[...]]
Possible Response:
AT+CGACT=?
+CGACT: (list of supported <state>s)
Parameter
Commands following +CGDATA command in the AT command line shall not be processed by the MT.
AT+CGDATA
Syntax
Possible Response:
AT+CGDATA[=<L2P> CONNECT
[,<cid>[,<cid>[,...]]]] ERROR
+CME ERROR: <err>
Possible Response:
AT+CGDATA=?
+CGDATA: (list of supported <L2P>s)
Parameter
<L2P>
String type; indicates the layer 2 protocol to be used between the TE and MT PPP Point-to-point protocol for
a PDP such as IP.
<cid>
Integer type; specifies a particular PDP context definition.
56
China Mobile IoT Co, Ltd.
AT+CGPADDR
Syntax
Possible Response:
AT+CGPADDR[=<cid>[,<cid> [+CGPADDR: <cid>[,<PDP_addr_1>[,<PDP_addr_2>]]]
[,...]]] [<CR><LF>+CGPADDR: <cid>,[<PDP_addr_1>[,<PDP_addr_2>]]
[...]]
Possible Response:
AT+CGPADDR =?
+CGPADDR: (list of defined <cid>s)
Parameter
<cid>
Integer type; specifies a particular PDP context definition.
57
China Mobile IoT Co, Ltd.
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 Test command returns values
supported as a compound value.
AT+CGREG
Syntax
Possible Response:
AT+CGREG=[<n>]
+CME ERROR: <err>
Possible Response:
When <n>=0, 1, 2 or 3 and command successful:
+CGREG:
<n>,<stat>[,[<lac>],[<ci>],[<AcT>],[<rac>][,<cause_type>,<reject_cause>]]
AT+CGREG?
When <n>=4 or 5 and command successful:
+CGREG:
<n>,<stat>[,[<lac>],[<ci>],[<AcT>],[<rac>][,[<cause_type>],[<reject_cause>][,[<A
ctive-Time>],[<Periodic-RAU>],[<GPRS-READY-timer>]]]]
Possible Response:
AT+CGREG=?
+CGREG: (list of supported <n>s)
Parameter
58
China Mobile IoT Co, Ltd.
AT+CGREG
Parameter
<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
Not registered, but MT is currently trying to attach or searching an operator to
2
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
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.
<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
4 UTRAN w/HSDPA
5 UTRAN w/HSUPA
6 UTRAN w/HSDPA and HSUPA
7 E-UTRAN (not applicable)
8 EC-GSM-IoT (A/Gb mode)
9 E-UTRAN (NB-S1 mode)(not applicable)
10 E-UTRA connected to a 5GCN(not applicable)
11 NR connected to a 5GCN
12 NR connected to an EPS core
13 NG-RAN (not applicable)
14 E-UTRA-NR dual connectivity(not applicable)
<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
1 Indicates that <reject_cause> contains a manufacturer-specific cause.
59
China Mobile IoT Co, Ltd.
AT+CGREG
Parameter
<reject_cause>
Integer type; contains the cause of the failed registration. The value is of type as defined by <cause_type>.
<Active-Time>
String type; one byte in an 8 bit format. Indicates the Active Time value (T3324).
<Periodic-RAU>
String type; one byte in an 8 bit format. Indicates the extended periodic RAU value (T3312).
<GPRS-READY-timer>
String type; one byte in an 8 bit format. Indicates the GPRS READY timer value (T3314).
60
China Mobile IoT Co, Ltd.
The test command is used for requesting information on the currently available services and service
preferences as a compound value.
AT+CGSMS
Syntax
+CGSMS=[<service>]
Possible Response:
AT+CGSMS?
+CGSMS: <service>
Possible Response:
AT+CGSMS=?
+CGSMS: (list of currently available <service>s)
Parameter
61
China Mobile IoT Co, Ltd.
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.
AT+CEREG
Syntax
Possible Response:
+CEREG=[<n>]
+CME ERROR: <err>
Possible Response:
+CEREG?
+CEREG: <n>,<stat>[,[<tac>],[<ci>],[<AcT>[,<cause_type>,<reject_cause>]]]
Possible Response:
+CEREG=?
+CEREG: (list of supported <n>s)
Parameter
62
China Mobile IoT Co, Ltd.
AT+CEREG
Parameter
<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
Not registered, but MT is currently trying to attach or searching an operator
2
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
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.
<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
1 GSM Compact
2 UTRAN
3 GSM w/EGPRS
4 UTRAN w/HSDPA
5 UTRAN w/HSUPA
6 UTRAN w/HSDPA and HSUPA
7 E-UTRAN (not applicable)
8 EC-GSM-IoT (A/Gb mode)
9 E-UTRAN (NB-S1 mode)(not applicable)
10 E-UTRA connected to a 5GCN(not applicable)
11 NR connected to a 5GCN
12 NR connected to an EPS core
13 NG-RAN (not applicable)
14 E-UTRA-NR dual connectivity(not applicable)
<cause_type> Integer type; indicates the type of <reject_cause>.
0 Indicates that <reject_cause> contains a GMM cause value
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>.
63
China Mobile IoT Co, Ltd.
If no <cid>s are specified the activation form of the command modifies all active contexts.
The test command returns a list of <cid>s associated with active contexts.
AT+CGMOD
Syntax
AT+CGDSCONT=[<cid>,
<p_cid>[,<d_comp>[,<h_comp>
[,<IM_CN_Signalling_Flag_Ind>]]]]
Possible Response:
[+CGDSCONT:<cid>,<p_cid>,<d_comp>,<h_comp>,
AT+CGDSCONT?
<IM_CN_Signaling_Flag_Ind>][<CR><LF>+CGDSCONT:<cid>,
<p_cid>,<d_comp>,<h_comp>,<IM_CN_Signaling_Flag_Ind>[...]]
Possible Response:
+CGDSCONT: (range of supported <cid>s),
AT+CGDSCONT=? (list of <p_cid>s for active primary contexts),
(list of supported <d_comp>s),(list of supported <h_comp>s),
(list of supported <IM_CN_Signaling_Flag_Ind>s)
Parameter
<cid>
Integer type; specifies a particular PDP context definition.
64
China Mobile IoT Co, Ltd.
In 5GS the command is used to define QoS flows of non-default QoS rule.
The read command returns the current settings for each defined context.
AT+CGDSCONT
Syntax
AT+CGDSCONT=[<cid>,<p_cid>
[,<d_comp>[,<h_comp>[,
<IM_CN_Signalling_Flag_Ind>]]]]
Possible Response:
[+CGDSCONT: <cid>,<p_cid>,<d_comp>,<h_co
AT+CGDSCONT? mp>,<IM_CN_Signaling_Flag_Ind>]
[<CR><LF>+CGDSCONT: <cid>,<p_cid>,<d_com
p>,<h_comp>,<IM_CN_Signaling_Flag_Ind>[...]]
Possible Response:
+CGDSCONT: (range of supported <cid>s),(list of <p_cid>s
AT+CGDSCONT=? for active primary contexts),(list of supported <d_comp>s),
(list of supported <h_comp>s),(list of supported
<IM_CN_Signaling_Flag_Ind>s)
Parameter
<cid>
Integer type; specifies a particular PDP context definition
<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
0 Off
1 On
2 V.42bis
3 V.44
<h_comp> Integer type; controls PDP header compression
0 Off
1 On
2 RFC 1144(applicable for SNDCP only)
3 RFC 2507
4 RFC 3095(applicable for PDCP only)
65
China Mobile IoT Co, Ltd.
AT+CGDSCONT
Parameter
<IM_CN_Signaling_Flag_Ind> Integer type; indicates to the network whether the PDP context is for IM
CN subsystem-related signaling only or not.
UE indicates that the PDP context is not for IM CN subsystem-related
0
signaling only.
UE indicates that the PDP context is for IM CN subsystem-related
1
signaling only.
66
China Mobile IoT Co, Ltd.
AT+CGDSCONT
Syntax
AT+CGEQREQ=[<cid>[,<Traffic
class>[,<Maximum bitrate
UL>[,<Maximum bitrate
DL>[,<Guaranteed bitrate
UL>[,<Guaranteed bitrate
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>[,<Signalling
indication>]]]]]]]]]]]]]]]
Possible Response:
[+CGEQREQ: <cid>,<Traffic class>,<Maximum bitrate UL>,<Maximum
bitrate DL>, <Guaranteed bitrate UL>,<Guaranteed bitrate
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:
AT+CGEQREQ?
<cid>,<Traffic class>,<Maximum bitrate UL>,<Maximum
bitrate DL>,<Guaranteed bitrate UL>,<Guaranteed bitrate
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>
[...]]
67
China Mobile IoT Co, Ltd.
AT+CGDSCONT
Syntax
Possible Response:
+CGEQREQ: <PDP_type>,(list of supported
<Traffic class>s),(list of supported <Maximum bitrate UL>s),(list of
supported <Maximum bitrate DL>s),(list of supported <Guaranteed
bitrate UL>s),(list of supported <Guaranteed
bitrate 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
AT+CGEQREQ=? <Signaling indication>s) [<CR><LF>+CGEQREQ: <PDP_type>,(list of
supported <Traffic class>s),(list of supported <Maximum bitrate
UL>s),(list of supported <Maximum bitrate DL>s),(list of supported
<Guaranteed bitrate UL>s),(list of supported <Guaranteed bitrate
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)
[...]]
Parameter
<cid>
Integer type; specifies a particular PDP context definition.
<PDP_type>
String type; specifies the type of packet data protocol.
<Traffic class> Integer type; indicates the type of application for which UMTS bearer service is
0 Conversational
1 Streaming
2 Interactive
3 Background
4 Subscribed value
<Maximum bitrate UL>
Integer type; indicates the maximum number of kbits/s delivered to UMTS (up-link traffic) at a SAP.
<Maximum bitrate DL>
Integer type; indicates the maximum number of kbits/s delivered by UMTS (down-link traffic) at a SAP.
<Guaranteed bitrate UL>
Integer type; indicates the guaranteed number of kbits/s delivered to UMTS (up-link traffic) at a SAP.
<Guaranteed bitrate DL>
Integer type; indicates the guaranteed number of kbits/s delivered by UMTS (down-link traffic) at a SAP.
68
China Mobile IoT Co, Ltd.
AT+CGDSCONT
Parameter
<Delivery order>
Integer type; indicates whether the UMTS bearer shall provide in-sequence SDU delivery or not.
<IM_CN_Signaling_Flag_Ind> Integer type; indicates to the network whether the PDP context is for IM CN
subsystem-related signaling only or not.
0 No
1 Yes
2 Subscribed value
<Maximum SDU size>
Integer type; (1,2,3,…) indicates the maximum allowed SDU size in octets.
<SDU error ratio>
String type; indicates the target value for the fraction of SDUs lost or detected as erroneous.
<Delivery of erroneous SDUs> Integer type; indicates whether SDUs detected as erroneous shall be
delivered or not.
0 No
1 Yes
2 No detect
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.
<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.
0 Characteristics of SDUs is unknown
1 Characteristics of SDUs corresponds to a speech source
<Signalling Indication> Integer type; indicates signaling content of submitted SDUs for a PDP context.
0 PDP context is not optimized for signaling
1 PDP context is optimized for signaling<PDP_type>
69
China Mobile IoT Co, Ltd.
AT+CGTFT
Syntax
AT+CGTFT=[<cid>,[<packet
filter identifier>,<evaluation
precedence index>[,<remote
address and subnet mask>
[,<protocol number (ipv4) /
next header (ipv6)>[,<local port
range>[,<remote port range>
Possible Response:
[,<ipsec security parameter
+CME ERROR: <err>
index (spi)>[,<type of service
(tos) (ipv4) and mask /
traffic class (ipv6) and mask>
[,<flow label (ipv6)>[,
<direction>[,<local address
and subnet mask>[,<QRI>
]]]]]]]]]]]]
Possible Response:
[+CGTFT: <cid>,<packet filter identifier>,<evaluation precedence
index>,<remote address and subnet mask>,<protocol number (ipv4) /
next header (ipv6)>,<local port range>,<remote port range>,<ipsec
security parameter index (spi)>,<type of service (tos) (ipv4) and mask /
traffic class (ipv6) and mask>,<flow label (ipv6)>,<direction>,<local
AT+CGTFT? address and subnet mask>,<QRI>] [<CR><LF>+CGTFT: <cid>,<packet
filter identifier>,<evaluation precedence index>,<remote address and
subnet mask>,<protocol number (ipv4) / next header (ipv6)>,<local
port range>,<remote port range>,<ipsec security parameter index
(spi)>,<type of service (tos) (ipv4) and mask / traffic class (ipv6) and
mask>,<flow label (ipv6)>,<direction>,<local address and subnet
mask>,<QRI> [...]]
70
China Mobile IoT Co, Ltd.
AT+CGTFT
Syntax
Possible Response:
+CGTFT: <PDP_type>,(list of supported <packet filter identifier>s),(list
of supported <evaluation precedence index>s),(list of supported
<remote address and subnet mask>s),(list of supported <protocol
number (ipv4) / next header (ipv6)>s),(list of supported <local port
range>s),(list of supported <remote 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),(list of
supported <local address and subnet mask>s),(range of supported
AT+CGTFT=?
<QRI>s) [<CR><LF>+CGTFT: <PDP_type>,(list of supported <packet
filter identifier>s),(list of supported <evaluation precedence index>s),
(list of supported <remote address and subnet mask>s),(list of
supported <protocol number (ipv4) / next header (ipv6)>s),(list of
supported <local port range>s),(list of supported <remote 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),(list of supported <local address and subnet
mask>s),(range of supported <QRI>s) [...]]
Parameter
<cid>
Integer type; specifies a particular PDP context definition.
<PDP_type>
String type; specifies the type of packet data protocol.
<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).
<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".
71
China Mobile IoT Co, Ltd.
AT+CGTFT
Parameter
<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.
<Delivery order> Integer type; indicates whether the UMTS bearer shall provide in-sequence SDU delivery
or not.
0 Pre-Release 7 TFT filter
1 Uplink
2 Downlink
3 Bidirectional (Up & Downlink)
<local address and subnet mask>
String type. The string is given as dot-separated numeric (0-255).
<QRI>
Integer type. Identifies the QoS rule.
72
China Mobile IoT Co, Ltd.
AT+CGEQMIN
Syntax
AT+CGEQMIN=[<cid>[,<Traffic
class> [,<Maximum bitrate
UL>[,<Maximum
bitrate DL>[,<Guaranteed
bitrate UL>[,<Guaranteed
bitrate 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>[,<Signalling
indication>]]]]]]]]]]]]]]]
Possible Response:
[+CGEQMIN: <cid>,<Traffic class>,<Maximum bitrate UL>,<Maximum
bitrate DL>,<Guaranteed bitrate
UL>,<Guaranteed bitrate DL>,<Delivery order>, <Maximum SDU
size>,<SDU error ratio>,<Residual bit error ratio>,<Delivery of
erroneous SDUs>,<Transfer delay>,<Traffic handling priority>, <Source
AT+CGEQMIN? statistics descriptor>,<Signaling indication>] [<CR><LF>+CGEQMIN:
<cid>,<Traffic class>,<Maximum bitrate UL>,<Maximum bitrate
DL>,<Guaranteed bitrateUL>,<Guaranteed bitrate 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>
[...]]
73
China Mobile IoT Co, Ltd.
AT+CGEQMIN
Syntax
Possible Response:
+CGEQMIN: <PDP_type>,(list of supported <Traffic class>s),(list of
supported <Maximum bitrate UL>s),(list of supported <Maximum
bitrate DL>s),(list of supported <Guaranteed bitrate UL>s),(list of
supported <Guaranteed
bitrate 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
AT+CGEQMIN =? supported <Signaling indication>s)
[<CR><LF>+CGEQMIN: <PDP_type>,(list of supported <Traffic
class>s),(list of supported <Maximum bitrate UL>s),(list of supported
<Maximum bitrate DL>s),(list of supported <Guaranteed bitrate
UL>s),(list of supported
<Guaranteed bitrate 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) [...]]
Parameter
<cid>
Integer type; specifies a particular PDP context definition.
<PDP_type>
String type; specifies the type of packet data protocol.
<Traffic class> Integer type; indicates the type of application for which the UMTS bearer service is
optimized
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.
<Maximum bitrate DL>
Integer type; indicates the maximum number of kbits/s delivered by UMTS (down-link traffic) at a SAP.
<Guaranteed bitrate UL>
Integer type; indicates the guaranteed number of kbits/s delivered to UMTS (up-link traffic) at a SAP.
<Guaranteed bitrate DL>
Integer type; indicates the guaranteed number of kbits/s delivered by UMTS (down-link traffic) at a SAP.
74
China Mobile IoT Co, Ltd.
AT+CGEQMIN
Parameter
<Delivery order> Integer type; indicates whether the UMTS bearer shall provide in-sequence SDU delivery
or not.
0 No
1 Yes
<Maximum SDU size>
Integer type; (1,2,3,…) indicates the maximum allowed SDU size in octets.
<SDU error ratio>
String type; indicates the target value for the fraction of SDUs lost or detected as erroneous.
<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".
<Delivery of erroneous SDUs> Integer type; indicates whether SDUs detected as erroneous shall be
delivered or not.
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.
<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.
<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.
0 Characteristics of SDUs is unknown
1 Characteristics of SDUs corresponds to a speech source
<Signaling Indication> Integer type; indicates signaling content of submitted SDUs for a PDP context.
0 PDP context is not optimized for signaling
1 PDP context is optimized for signaling<PDP_type>
75
China Mobile IoT Co, Ltd.
AT+CGEQOS
Syntax
AT+CGEQOS=[<cid>[,<QCI>
Possible Response:
[,<DL_GBR>,<UL_GBR
+CME ERROR: <err>
>[,<DL_MBR>,<UL_MBR]]]]
Possible Response:
[+CGEQOS: <cid>,<QCI>,[<DL_GBR>,<UL_GBR
AT+CGEQOS? >],[<DL_MBR>,<UL_MBR>]]
[<CR><LF>+CGEQOS: <cid>,<QCI>,[<DL_GBR>
,<UL_GBR>],[<DL_MBR>,<UL_MBR>] [...]]
Possible Response:
+CGEQOS: (range of supported <cid>s),(list of
AT+CGEQOS =? supported <QCI>s),(list of supported
<DL_GBR>s),(list of supported <UL_GBR>s),(list of
supported <DL_MBR>s),(list of supported <UL_MBR>s)
Parameter
<cid>
Integer type; specifies a particular EPS Traffic Flows definition and a PDP Context definition.
<QCI> Integer type; specifies a class of EPS QoS
0 QCI is selected by network
[1 – 4] Value range for guaranteed bit rate Traffic Flows
75 Value for guaranteed bit rate Traffic Flows
[5 – 9] Value range for non-guaranteed bit rate Traffic Flows
79 Value for non-guaranteed bit rate Traffic Flows
[128 – 254] Value range for Operator-specific QCIs
65, 66, 67, 69, 70 Are not allowed to be requested by the UE
<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.
<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.
<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.
<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.
76
China Mobile IoT Co, Ltd.
AT+CGCONTRDP
Syntax
Possible Response:
[+CGCONTRDP: <cid>,<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_Signaling_Flag>
[,<LIPA_indication>[,<IPv4_MTU>[,<WLAN_Offload>[,<Local_Addr_Ind>
[,<Non-IP_MTU>[,<Serving_PLMN_rate_control_value>
[,<Reliable_Data_Service>[,<PS_Data_Off_Support>[,<PDU_session_id>,
AT+CGCONTRDP[=<cid>] <QFI>[,<SSC_mode>[,<S-NSSAI>[,<Access_type>[,<RQ_timer>]
]]]]]]]]]]]]]]]]]]]][<CR><LF>+CGCONTRDP:<cid>,<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_Signaling_Flag>[,<LIPA_indication>[,<IPv4_MTU>
[,<WLAN_Offload>[,<Local_Addr_Ind>[,<Non-IP_MTU>
[,<Serving_PLMN_rate_control_value>[,<Reliable_Data_Service>
[,<PS_Data_Off_Support>[,<PDU_session_id>,<QFI>[,<SSC_mode>[,<S-
NSSAI>[,<Access_type>[,<RQ_timer>]]]]]]]]]]]]]]]]]]]] [...]]
Possible Response:
AT+CGCONTRDP=?
+CGCONTRDP: (list of <cid>s associated with active contexts)
Parameter
<cid>
Integer type; specifies a particular non secondary PDP context definition.
<bearer_id>
Integer type; identifies the bearer, i.e. the EPS bearer and the NSAPI.
<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.
77
China Mobile IoT Co, Ltd.
AT+CGCONTRDP
Parameter
<gw_addr>
String type; shows the Gateway Address of the MT. The string is given as dot-separated numeric (0-255)
parameters.
<DNS_prim_addr>
String type; shows the IP address of the primary DNS server.
<DNS_sec_addr>
String type; shows the IP address of the secondary DNS server.
<P_CSCF_prim_addr>
String type; shows the IP address of the primary P-CSCF server.
<P_CSCF_sec_addr>
String type; shows the IP address of the secondary P-CSCF server.
<IM_CN_Signaling_Flag> Integer type; shows whether the PDP context is for IM CN subsystem-related
signaling only or not.
0 PDP context is not for IM CN subsystem-related signaling only
1 PDP context is for IM CN subsystem-related signaling only
<IPv4_MTU>
Integer type; shows the IPv4 MTU size in octets.
<WLAN_Offload> Integer type; indicates whether traffic can be offloaded using the specified PDN
connection via a WLAN or not. This refers to bits 1 and 2 of the WLAN offload acceptability IE.
Offloading the traffic of the PDN connection via a WLAN when in S1
0
mode or when in Iu mode is not acceptable.
Offloading the traffic of the PDN connection via a WLAN when in S1
1
mode is acceptable, but not acceptable in Iu mode.
Offloading the traffic of the PDN connection via a WLAN when in Iu
2
mode is acceptable, but not acceptable in S1 mode.
Offloading the traffic of the PDN connection via a WLAN when in S1
3
mode or when in Iu mode is acceptable.
<Local_Addr_Ind> Integer type; indicates whether or not the MS and the network support local IP address in
TFTs.
Indicates that the MS or the network or both do not support local IP
0
address in TFTs.
1 Indicates that the MS and the network support local IP address in TFTs.
<Non-IP_MTU>
Integer type; shows the Non-IP MTU size in octets.
<Serving_PLMN_rate_control_value>
Integer type; indicates the maximum number of uplink messages the UE is allowed to send in a 6-minute
interval.
<Reliable_Data_Service> Integer type; indicates whether the UE is using Reliable Data Service for a PDN
connection or not.
0 Reliable Data Service is not being used for the PDN connection
1 Reliable Data Service is being used for the PDN connection
78
China Mobile IoT Co, Ltd.
AT+CGCONTRDP
Parameter
<PS_Data_Off_Support> Integer type; indicates whether the network supports PS data off or not.
0 Indicates that the network does not support PS data off
1 Indicates that the network supports PS data off
<PDU_session_id>
Integer type; identifies the PDU session.
<QFI>
Integer type; identifies the QoS flow.
<SSC_mode> Integer type; indicates the session and service continuity (SSC) mode for the PDU session in
5GS.
0 Indicates that the PDU session is associated with SSC mode 1
1 Indicates that the PDU session is associated with SSC mode 2
2 Indicates that the PDU session is associated with SSC mode 3
<S-NSSAI>
String type; indicates the S-NSSAI associated with the PDU session for identifying a network slice in 5GS
<Access_type> Integer type; indicates the access type over which the PDU session is established in 5GS
0 Indicates that the preferred access type is 3GPP access
1 Indicates that the preferred access type is non-3GPP access
<RQ_timer>
Integer type; indicates the timer for reflective QoS.
79
China Mobile IoT Co, Ltd.
AT+CGSCONTRDP
Syntax
AT+CGEQOS=[<cid>[,<QCI>
Possible Response:
[,<DL_GBR>,<UL_GBR
+CME ERROR: <err>
>[,<DL_MBR>,<UL_MBR]]]]
Possible Response:
[+CGEQOS: <cid>,<QCI>,[<DL_GBR>,<UL_GBR
AT+CGEQOS? >],[<DL_MBR>,<UL_MBR>]]
[<CR><LF>+CGEQOS: <cid>,<QCI>,[<DL_GBR>
,<UL_GBR>],[<DL_MBR>,<UL_MBR>] [...]]
Possible Response:
+CGEQOS: (range of supported <cid>s),(list of
AT+CGEQOS =? supported <QCI>s),(list of supported
<DL_GBR>s),(list of supported <UL_GBR>s),(list of
supported <DL_MBR>s),(list of supported <UL_MBR>s)
Parameter
<cid>
Integer type; specifies a particular active secondary PDP context or Traffic Flows definition.
<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.
<bearer_id>
Integer type; identifies the bearer, EPS Bearer and NSAPI.
<IM_CN_Signalling_Flag> Integer type; shows whether the PDP context is for IM CN subsystem-related
signaling only or not.
0 PDP context is for IM CN subsystem-related signaling only
1 PDP context is for IM CN subsystem-related signaling only
<WLAN_Offload> Integer type; indicates whether traffic can be offloaded using the specified PDN
connection via a WLAN or not. This refers to bits 1 and 2 of the WLAN offload acceptability IE.
Offloading the traffic of the PDN connection via a WLAN when in S1
0
mode or when in Iu mode is not acceptable.
Offloading the traffic of the PDN connection via a WLAN when in S1
1
mode is acceptable, but not acceptable in Iu mode.
Offloading the traffic of the PDN connection via a WLAN when in Iu
2
mode is acceptable, but not acceptable in S1 mode.
Offloading the traffic of the PDN connection via a WLAN when in S1
3
mode or when in Iu mode is acceptable.
80
China Mobile IoT Co, Ltd.
AT+CGSCONTRDP
Parameter
<PDU_session_id>
Integer type; identifies the PDU session.
<QFI>
Integer type; identifies the QoS flow.
81
China Mobile IoT Co, Ltd.
Parameters of both network and MT/TA initiated PDP contexts will be returned. The test command
returns a list of <cid>s associated with active secondary and non-secondary contexts.
AT+CGTFTRDP
Syntax
Possible Response:
[+CGTFTRDP: <cid>,<packet filter
identifier>,<evaluation precedence index>,<remote
address and subnet mask>,<protocol number (ipv4) /
next header (ipv6)>,<local port range>,<remote
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
AT+CGTFTRDP[=<cid>] Identifier>,<local address and subnet mask>,<QRI>]
[<CR><LF>+CGTFTRDP: <cid>,<packet filter
identifier>,<evaluation precedence index>,<remote
address and subnet mask>,<protocol number (ipv4) /
next header (ipv6)>,<local port range>, <remote
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>,<local address and subnetmask>,<QRI>
[...]]
Possible Response:
AT+CGTFTRDP =?
+CGTFTRDP: (list of <cid>s associated with active contexts)
Parameter
<cid>
Integer type; Specifies a particular secondary or non-secondary PDP context definition or Traffic Flows
definition.
<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).
82
China Mobile IoT Co, Ltd.
AT+CGTFTRDP
Parameter
<protocol number (ipv4) / next header (ipv6)>
Integer type. The 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
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.
<local address and subnet mask>
String type. The string is given as dot-separated numeric (0-255).
<QRI>
Integer type; identifies the QoS rule.
83
China Mobile IoT Co, Ltd.
AT+CGEQSRDP
Syntax
Possible Response:
[+CGEQOSRDP: <cid>,<QCI>,[<DL_GBR>,<UL_GBR>]
AT+CGEQOSRDP[=<cid>]
,[<DL_MBR>,<UL_MBR>][,<DL_AMBR>,<UL_AMBR>]][<CR><LF>
+CGEQOSRDP: <cid>,<QCI>,[<DL_GBR>,<UL_GBR>],[<DL_MBR>,
<UL_MBR>][,<DL_AMBR>,<UL_AMBR>] [...]]
Possible Response:
AT+ CGEQOSRDP =?
+CGEQOSRDP: (list of <cid>s associated with active contexts)
Parameter
<cid>
Integer type; specifies a particular Traffic Flows definition and a PDP Context definition.
<QCI> Integer type; specifies a class of EPS QoS.
0 QCI is selected by network
[1 – 4] Value range for guaranteed bit rate Traffic Flows
65, 66, 67, 69, 70 Values for guaranteed bit rate Traffic Flows
[5 – 9] Value range for non-guaranteed bit rate Traffic Flows
69, 70, 79 Values for non-guaranteed bit rate Traffic Flows
[128 – 254] Value range for Operator-specific QCIs
<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.
<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.
<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.
<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.
<DL_AMBR>
Integer type; indicates DL APN aggregate MBR (see 3GPP TS 24.301 [83]). The value is in kbit/s.
<UL_AMBR>
Integer type; indicates UL APN aggregate MBR (see 3GPP TS 24.301 [83]). The value is in kbit/s.
84
China Mobile IoT Co, Ltd.
8 Vendor Specific
Commands
8.1 AT$QCSIMSTAT: Display SIM Status
Disables/enables the display of the status of the SIM. Upon enabling, SIM status is sent as an
unsolicited result code onto the terminal.
AT$QCSIMSTAT
Syntax
AT$QCSIMSTAT=<n>
Possible Response:
AT$QCSIMSTAT?
$QCSIMSTAT: <n>,<sim status>
Possible Response:
AT$QCSIMSTAT=?
$QCSIMSTAT: (list of supported <n>s)
Parameter
<n>
0 Disables the feature
1 Enables the feature
<sim status>
SIM INIT
SIM ERROR
UNKNOWN
AT$QCDNSP
Syntax
AT$QCDNSP=<address>
Possible Response:
AT$QCDNSP?
$QCDNSP: (primary DNS configured by this command)
Parameter
<address>
IP address
85
China Mobile IoT Co, Ltd.
AT$QCDNSP
Syntax
AT$QCDNSS=<address>
Possible Response:
AT$QCDNSS?
$QCDNSS: (primary DNS configured by this command)
Parameter
<address>
IP address
AT$QCSQ
Syntax
Possible Response:
AT$QCSQ
$QCSQ: <rscp>,<ecio>,<sir>,<pathloss>,<rssi>
Possible Response:
AT$QCSQ
$QCSQ: (list of supported range of parameters)
Parameter
N/A
AT$QCPINSTAT
Syntax
Possible Response:
AT$QCPINSTAT?
$QCPINSTAT: all PIN status
Parameter
N/A
86
China Mobile IoT Co, Ltd.
AT$QCPDPP
Syntax
AT$QCPDPP=<cid>,<auth_type>,
<password>,<username>
Possible Response:
AT$QCPDPP?
$QCPDPP: <username> of each <cid>
Parameter
<cid>
Integer type; specifies a particular PDP context definition.
<auth_type> Determines what extra parameters are required
0 None (Neither username nor password accepted)
1 PAP (Username and password accepted)
2 CHAP (Only password)
AT$QCPWRDN
Syntax
AT$QCPWRDN
Parameter
N/A
AT$QCDGEN
Syntax
AT$QCDGEN=<cid>,<data_length>
Parameter
<cid>
Integer type; specifies a particular PDP context definition.
<data_length>
Data length to be sent.
87
China Mobile IoT Co, Ltd.
AT^CARDMODE
Syntax
Possible Response:
AT^CARDMODE
^CARDMODE:<card_mode>
Parameter
<card_mode>
0 Unknown mode
1 SIM card
2 USIM card
3 CSIM card
4 RUIM card
Example
AT^CARDMODE
^CARDMODE: 2
AT$QCPDPIMSCFGE
Syntax
Possible Response:
AT$QCPDPIMSCFGE=? $QCPDPIMSCFGE: (1-24),(0-1),(01),(0-1)
OK
Possible Response:
$QCPDPIMSCFGE: <Profile ID>,
<P-CSCF Address Flag>,
AT$QCPDPIMSCFGE?
<DHCP Flag>,
<CN Flag>
OK
AT$QCPDPIMSCFGE=<ProfileID>,
Possible Response:
<P-CSCF Address Flag>,
OK
<DHCP Flag>,<CN Flag>
Parameter
<Profile ID >
PDP profile ID 1 to 24.
<Address Flag> Flag to enable P-CSCF address
0 Disable
1 Enable
88
China Mobile IoT Co, Ltd.
AT$QCNSP
Syntax
AT$QCNSP=<mode_pref>,
<net_sel_pref>,<acq_order_pref>
Possible Response:
AT$QCNSP? $QCNSP: current configuration of <mode_pref>,
<net_sel_pref>,<acq_order_pref>
Possible Response:
AT$QCNSP=? $QCNSP: (list of supported <mode_pref>, <net_sel_pref>,
<acq_order_pref>)
Parameter
1 GSM
2 WCDMA
6 LTE
1 Manual
2 Limited
1 GSM
2 WCDMA
3 LTE
Example
AT$QCNSP=?
$QCNSP: (0,1,2,6),(0-2),(0-3)
89
China Mobile IoT Co, Ltd.
AT$QCVOIPM
Syntax
AT$QCNSP=<mode_pref>,
<net_sel_pref>,<acq_order_pref>
Possible Response:
AT$QCNSP? $QCNSP: current configuration of <mode_pref>,
<net_sel_pref>,<acq_order_pref>
Possible Response:
AT$QCNSP=? $QCNSP: (list of supported <mode_pref>, <net_sel_pref>,
<acq_order_pref>)
Parameter
<session_expires>
90 to 65535
<min_session_expiry>
90 to 65535
<rtp_rtcp_inactivity_timer>
0 to 20
<ringing_timer>
30 to 45
<ringback_timer>
35 to 50
<amr_wb_enable>
0 Disable
1 Enable
<scr_amr_enable>
0 Disable
1 Enable
<scr_amr_wb_enable>
0 Disable
1 Enable
<amr_mode_str>
String type
<amr_wb_mode_str>
String type
90
China Mobile IoT Co, Ltd.
AT$QCPCOLIST
Syntax
Possible Response:
AT$QCPCOLIST =<APN>
+QCPCOLIST:<PCO info>
Possible Response:
AT$QCPCOLIST?
OK
Possible Response:
AT$QCPCOLIST=?
OK
Parameter
<APN>
APN name should be quoted
AT$QCMSISDN
Syntax
Possible Response:
AT$QCMSISDN =<APN>
+QCMSISDN:<MSISDN info>
Possible Response:
AT$QCMSISDN =?
OK
Possible Response:
AT$QCMSISDN ?
OK
Parameter
<APN>
APN name should be quoted
91
China Mobile IoT Co, Ltd.
AT$QCPCOMSISDN
Syntax
AT$QCPCOMSISDN Possible Response:
=<profile_ID>,<>,<PCO> +QCPCOMSISDN:<n>
Possible Response:
AT$QCPCOMSISDN?
+QCPCOMSISDN: <profile_ID>,<MSISDN_flag>,<PCO>
Possible Response:
AT$QCPCOMSISDN =?
+QCPCOMSISDN: <1-42>,<0-1>,<65280-65536>
Parameter
<Profile_ID>
1 to 42
<MSISDN_flag>
0 to 1
<PCO>
65280 to 65535
AT$QCIMSSRV
Syntax
Possible Response:
AT$QCIMSSRV=<n>
+QCIMSSRV:<n>
Possible Response:
AT$QCIMSSRV?
+QCIMSSRV:<n>
Parameter
<n>
0 Disable
1 Enable
92