SARA-R4 Series AT Commands Manual Datasheet by U-Blox

View All Related Products | Download PDF Datasheet
SARA-R4 series
Size-optimized LTE Cat M1 / NB1 / GPRS modules
AT commands manual
Abstract
Description of standard and proprietary AT commands used with u-blox
cellular modules.
UBX-17003787 - R20
C1-Public www.u-blox.com
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
Page 2 of 425
Document information
Title SARA-R4 series
Subtitle Size-optimized LTE Cat M1 / NB1 / GPRS modules
Document type AT commands manual
Document number UBX-17003787
Revision and date R20 05-Mar-2021
Disclosure restriction C1-Public
u-blox reserves all rights to this document and the information contained herein. Products, names, logos and designs
described herein may in whole or in part be subject to intellectual property rights. Reproduction, use, modification or
disclosure to third parties of this document or any part thereof without the express permission of u-blox is strictly
prohibited.
The information contained herein is provided “as is” and u-blox assumes no liability for the use of the information. No
warranty, either express or implied, is given, including but not limited, with respect to the accuracy, correctness, reliability
and fitness for a particular purpose of the information. This document may be revised by u-blox at any time. For most
recent documents, visit www.u-blox.com.
Copyright © 2018, u-blox AG
u-blox is a registered trademark of u-blox Holding AG in the EU and other countries.
BL.)
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
Preface Page 3 of 425
Preface
Applicable products
This document applies to the following products:
Name Type number Modem version Application version PCN reference
SARA-R404M-00B-00 K0.0.00.00.07.06 N.A. UBX-17047084SARA-R404M
SARA-R404M-00B-01 K0.0.00.00.07.08 N.A. UBX-18053670
SARA-R410M-01B-00 L0.0.00.00.02.03 N.A. UBX-17051617
SARA-R410M-02B-00 L0.0.00.00.05.06 A02.01 UBX-18010263
SARA-R410M-02B-01 L0.0.00.00.05.08 02.04 UBX-19024506
SARA-R410M-02B-02 L0.0.00.00.05.11 A.02.16 UBX-20033274
SARA-R410M-02B-03 L0.0.00.00.05.12 A.02.19 UBX-20058104
SARA-R410M-52B-00 L0.0.00.00.06.05 A02.06 UBX-18045915
SARA-R410M-52B-01 L0.0.00.00.06.08 A02.11 UBX-19011338
SARA-R410M-52B-02 L0.0.00.00.06.11 A.02.16 UBX-20033274
SARA-R410M-63B-00 L0.08.12 A.01.11 UBX-20013231
SARA-R410M-63B-01 L0.08.12 A.01.12 UBX-20053055
SARA-R410M-73B-00 L0.08.12 A.01.11 UBX-19047632
SARA-R410M-73B-01 L0.08.12 A.01.12 UBX-20049254
SARA-R410M-83B-00 L0.08.12 A.01.11 UBX-20027231
SARA-R410M
SARA-R410M-83B-01 L0.08.12 A.01.12 UBX-20049255
SARA-R412M-02B-00 M0.09.00 A.02.11 UBX-19004091
SARA-R412M-02B-01 M0.10.00 A.02.14 UBX-19016568
SARA-R412M-02B-02 M0.11.01 A.02.17 UBX-20031249
SARA-R412M
SARA-R412M-02B-03 M0.12.00 A.02.19 UBX-20058105
SARA-N410 SARA-N410-02B-00 L0.0.00.00.07.07 A02.09 UBX-18057459
How to use this manual
The u-blox Cellular Modules AT Commands Manual provides the necessary information to successfully design
in and configure the applicable u-blox cellular modules.
This manual has a modular structure. It is not necessary to read it from the beginning to the end.
The following symbols are used to highlight important information within the manual:
An index finger points out key information pertaining to module integration and performance.
A warning symbol indicates actions that could negatively impact or damage the module.
Summary table
The summary table on the top of each command section is a quick reference for the user.
command_name
TOBY-L2 MPCI-L2
LISA-U110 LISA-U120 LISA-U130 LISA-U2
Modules
LEON-G1 SARA-G3
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full No No No - -
It is composed of two sections:
Modules: lists all the modules that support the command. The modules are grouped in rows by cellular
standard (i.e. L for LTE high data rate (Cat 3 and above), R for LTE low data rate (Cat 1 and below), U
for UMTS/HSPA, G for GSM/GPRS, N for NB-IoT (LTE Cat NB1 / LTE Cat NB2)). In each row the modules
are grouped by: form factor (i.e. SARA, LISA), platform technology (e.g. SARA-G), platform generation
(e.g. SARA-G3), product name (e.g. SARA-G350) and ordering code (e.g. SARA-G350-00S). In example: if
blox
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
Preface Page 4 of 425
'LISA-U2' is reported, the command applies to all the modules having LISA form factor, second chipset
version provided with any release of firmware.
Attributes
oSyntax
-full: the command syntax is fully compatible among all the products listed in the "Modules" section
-partial: the products support different syntaxes (usually backward compatible with respect to
previous cellular standards)
oPIN required
-Yes: it is necessary to insert the PIN before the set and/or read command execution
-No: the PIN insertion is not needed to execute the command
oSettings saved
-Profile: the command setting can be saved in a personal profile as specified in Chapter 1.4
-NVM: the command setting is saved in the non-volatile memory as specified in Chapter 1.4
-<command_name>: the parameter values set with the command are volatile, but the whole profile
can be stored in NVM with <command_name> AT command.
-OP: the command setting can be overwritten by the Mobile Network Operator (MNO) profile set with
the +UMNOPROF or +UMNOCONF AT commands (if supported)
-No: the current command setting is volatile and cannot be saved
oCan be aborted
-Yes: the command execution can be aborted if a character is sent to the DCE during the command
execution
-No: the command cannot be aborted during the command execution
oResponse time: estimated maximum time to get the final result code for the AT command execution.
More precisely, the command response time measures the time from the complete acquisition of the
command line to the issuing of the command result code. This kind of response time is generally lower
than the time measured by the application on the DTE, because the issuing of the command on the
DTE is influenced by the AT interface characteristics (e.g. the synchronous/asynchronous transfer type,
the selected baudrate, etc.), by power saving and flow control, which introduce a variable latency in the
command acquisition by the DCE.
For example, the maximum expected response time shall be extended if the communication with the
module is carried out on a MUX virtual port, because in this case the command line and the result code
are transferred via a specific protocol running on the physical port, that might introduce additional
communication delay due to framing and retransmissions.
Similarly, the maximum expected response time of AT commands accessing the SIM shall be extended
if the module is using a remote SIM card via SAP instead of the local SIM card.
If the response time for a command is left blank (actually "-"), it is an "immediate" response. It means
that the command is executed without asynchronous requests to the protocol stack or the internal
applications, which usually require time to be answered: the command execution is synchronous
(implying that no long blocking processing is done) and lasts a negligible time (the command response
is issued by the module in typically less than 10 ms, and in any case less than 1 s).
The response time shall be extended if the issued AT command triggers a service that cannot be served
immediately due to concurrent access to the same service or resource via AT commands issued on a
different communication port or from internal applications; typical examples are registration commands
and SIM access, that can be also autonomously triggered by the module (e.g. auto-COPS) and can
therefore postpone the execution of the AT commands issued by the user.
oError reference: reference to the error result codes listed in the Appendix A
The attributes listed in the summary table apply by default to all u-blox modules supporting the specific
AT command. If a u-blox module or module series does not comply to the default behavior, the exception is
highlighted in Chapter 1.4 for the saving of settings, in Chapter 1.3.4 for the abortability, and in a product
specific note in the AT command description for the PIN check.
u-blox technical documentation
As part of our commitment to customer support, u-blox maintains an extensive volume of technical
documentation for our products. In addition to our product-specific technical data sheets, the following
manuals are available to assist u-blox customers in product design and development.
blox
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
Preface Page 5 of 425
AT Commands Manual: This document provides the description of the AT commands supported by u-blox
cellular modules.
System Integration Manual: This document describes u-blox cellular modules from the hardware and the
software point of view. It provides hardware design guidelines for the optimal integration of the cellular module
in the application device and it provides information on how to set up production and final product tests on
application devices integrating the cellular module.
Application Notes: These documents provide guidelines and information on specific u-blox cellular module
hardware or software topics.
For some guidelines when developing applications for LTE Cat M1 technologies, see the SARA-R4 series
application development guide [16] or the SARA-R5 series application development guide [12].
For some guidelines when developing applications for NB-IoT technologies, see the SARA-N3 series
application development guide [32] or the NB-IoT application development guide [29].
For more examples of typical scenarios when developing application for LTE Cat 4, LTE Cat 1, UMTS/HSPA
and GSM/GPRS technologies, see the AT commands examples application note [34].
See Related documents for application notes related to your cellular module.
Questions
If you have any questions about u-blox Cellular Hardware Integration, please:
Read this manual carefully
Contact our information service on our homepage www.u-blox.com
Read the questions and answers on our FAQ database
Technical Support
Worldwide Web
Our website (www.u-blox.com) is a rich pool of information. Product information, technical documents and
helpful FAQ can be accessed 24h a day.
By email
If you have technical problems or cannot find the required information in the provided documents, contact
the nearest of the Technical Support offices by email. Use our service pool email addresses rather than any
personal email address of our staff. This makes sure that your request is processed as soon as possible. You
will find the contact details at the end of the document.
Helpful Information when Contacting Technical Support
When contacting Technical Support please have the following information ready:
Module type (e.g. SARA-G350-00S-00) and firmware version (e.g. 08.49)
Module configuration
Clear description of your question or the problem
A short description of the application
Your complete contact details
blox
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
Contents Page 6 of 425
Contents
1AT command settings..................................................................................................... 12
1.1Definitions.......................................................................................................................................................... 12
1.2Operational mode of the AT interface........................................................................................................ 12
1.3Command description.................................................................................................................................... 13
1.4Storing of AT commands setting................................................................................................................ 16
1.5S-parameters....................................................................................................................................................16
1.6+UDCONF AT command.................................................................................................................................17
2General operation.............................................................................................................18
2.1Start up and initialization..............................................................................................................................18
2.2AT commands types...................................................................................................................................... 19
3IPC - Inter Processor Communication........................................................................21
3.1Multiplexing mode +CMUX............................................................................................................................ 21
4General................................................................................................................................23
4.1Manufacturer identification +CGMI............................................................................................................23
4.2Manufacturer identification +GMI..............................................................................................................23
4.3Model identification +CGMM.......................................................................................................................23
4.4Model identification +GMM......................................................................................................................... 24
4.5Firmware version identification +CGMR................................................................................................... 24
4.6Firmware version identification +GMR......................................................................................................25
4.7Request product serial number identification +CGSN........................................................................... 25
4.8IMEI identification +GSN.............................................................................................................................. 27
4.9Identification information I...........................................................................................................................27
4.10TE character set configuration +CSCS................................................................................................... 28
4.11International mobile subscriber identification +CIMI.............................................................................29
4.12Card identification +CCID........................................................................................................................... 29
4.13Repeat last command A/............................................................................................................................30
5Mobile equipment control and status....................................................................... 31
5.1Phone activity status +CPAS........................................................................................................................31
5.2Module switch off +CPWROFF.................................................................................................................... 31
5.3Set module functionality +CFUN................................................................................................................32
5.4Indicator control +CIND................................................................................................................................ 33
5.5Configuration of indicator control +UCIND.............................................................................................. 35
5.6Mobile termination event reporting +CMER............................................................................................ 36
5.7Clock +CCLK....................................................................................................................................................37
5.8Set greeting text +CSGT..............................................................................................................................38
5.9Automatic time zone update +CTZU.........................................................................................................39
5.10Time zone reporting +CTZR.......................................................................................................................39
5.11Report mobile termination error +CMEE.................................................................................................. 41
6Call control........................................................................................................................ 42
6.1Dial command D.............................................................................................................................................. 42
6.2Call answer A.................................................................................................................................................. 43
7Network service............................................................................................................... 44
7.1Network parameters definition....................................................................................................................44
7.2Subscriber number +CNUM......................................................................................................................... 46
7.3Signal quality +CSQ....................................................................................................................................... 46
7.4Extended signal quality +CESQ...................................................................................................................48
7.5Operator selection +COPS............................................................................................................................49
7.6Radio Access Technology (RAT) selection +URAT.................................................................................. 51
7.7CIoT Configuration - iRAT timer +URATSCAN.........................................................................................53
blox
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
Contents Page 7 of 425
7.8MAC QoS inactivity timer(s) +UMACQOSTMR........................................................................................53
7.9Network registration status +CREG.......................................................................................................... 54
7.10Read operator names +COPN.................................................................................................................... 57
7.11Network selection control +PACSP........................................................................................................... 58
7.12Channel and network environment description +UCGED.....................................................................59
7.13Edit Verizon wireless APN table +VZWAPNE.........................................................................................62
7.14Read RSRP values +VZWRSRP................................................................................................................. 63
7.15Read RSRQ values +VZWRSRQ................................................................................................................ 64
7.16Signalling connection status +CSCON.................................................................................................... 65
7.17eDRX setting +CEDRXS...............................................................................................................................66
7.18eDRX read dynamic parameters +CEDRXRDP....................................................................................... 68
7.19Set MNO profile +UMNOPROF.................................................................................................................. 69
7.20Band selection bitmask +UBANDMASK..................................................................................................72
7.21Device service domain configuration +USVCDOMAIN.......................................................................... 73
7.22CIoT optimization configuration +CCIOTOPT........................................................................................ 74
7.23NB-IoT band scan tuning +UDCONF=77..................................................................................................76
8Device lock......................................................................................................................... 77
8.1Enter PIN +CPIN.............................................................................................................................................. 77
8.2Facility lock +CLCK........................................................................................................................................ 78
8.3Change password +CPWD........................................................................................................................... 79
9Short Messages Service................................................................................................ 81
9.1Introduction.......................................................................................................................................................81
9.2Select message service +CSMS.................................................................................................................. 81
9.3Preferred message storage +CPMS.......................................................................................................... 82
9.4Preferred message format +CMGF............................................................................................................84
9.5Save settings +CSAS....................................................................................................................................84
9.6Restore settings +CRES...............................................................................................................................85
9.7Show text mode parameters +CSDH.........................................................................................................85
9.8New message indication +CNMI.................................................................................................................86
9.9Read message +CMGR................................................................................................................................. 89
9.10New message acknowledgement to MT +CNMA................................................................................... 91
9.11List message +CMGL...................................................................................................................................92
9.12Send message +CMGS................................................................................................................................95
9.13Write message to memory +CMGW.........................................................................................................96
9.14Send message from storage +CMSS.......................................................................................................97
9.15Set text mode parameters +CSMP...........................................................................................................97
9.16Delete message +CMGD............................................................................................................................. 98
9.17Service center address +CSCA..................................................................................................................99
9.18Read concatenated message +UCMGR.................................................................................................100
9.19List concatenated message +UCMGL....................................................................................................102
9.20Send concatenated message +UCMGS................................................................................................105
9.21Write concatenated message to memory +UCMGW.......................................................................... 106
9.22More messages to send +CMMS............................................................................................................107
9.23Sending of originating data via the control plane +CSODCP............................................................108
9.24Terminating data reporting via control plane +CRTDCP................................................................... 109
10V24 control and V25ter.............................................................................................. 110
10.1Introduction................................................................................................................................................... 110
10.2Circuit 109 behavior &C.............................................................................................................................. 110
10.3Circuit 108/2 behavior &D.......................................................................................................................... 110
10.4DSR override &S........................................................................................................................................... 111
10.5Flow control &K............................................................................................................................................112
10.6DTE-DCE character framing +ICF............................................................................................................ 112
10.7DTE-DCE local flow control +IFC.............................................................................................................. 113
10.8Set flow control \Q...................................................................................................................................... 114
10.9UART data rate configuration +IPR.........................................................................................................115
10.10Return to on-line data state O................................................................................................................116
10.11Escape character S2.................................................................................................................................. 117
10.12Command line termination character S3..............................................................................................117
blox
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
Contents Page 8 of 425
10.13Response formatting character S4........................................................................................................118
10.14Command line editing character S5...................................................................................................... 118
10.15Pause before blind dialling S6................................................................................................................. 119
10.16Connection completion timeout S7........................................................................................................119
10.17Command dial modifier time S8............................................................................................................ 120
10.18Automatic disconnect delay S10............................................................................................................120
10.19Escape prompt delay (EPD) S12..............................................................................................................121
10.20Command echo E......................................................................................................................................122
10.21Result code suppression Q......................................................................................................................122
10.22DCE response format V...........................................................................................................................123
10.23Result code selection and call progress monitoring control X........................................................ 123
10.24Reset to default configuration Z...........................................................................................................124
10.25Set to factory defined configuration &F..............................................................................................124
10.26Display current configuration &V..........................................................................................................125
11SIM management..........................................................................................................126
11.1Generic SIM access +CSIM.........................................................................................................................126
11.2Restricted SIM access +CRSM.................................................................................................................126
11.3Read the SIM language +CLAN................................................................................................................ 128
11.4SIM states reporting +USIMSTAT........................................................................................................... 129
12SIM toolkit...................................................................................................................... 131
12.1Introduction....................................................................................................................................................131
12.2Bearer Independent Protocol status indication +UBIP.........................................................................131
12.3Read the USAT profile +CUSATR............................................................................................................132
12.4Write the USAT profile +CUSATW..........................................................................................................133
12.5Enable USAT terminal URCs +UCUSATA.............................................................................................. 134
13Packet switched data services................................................................................135
13.1PDP contexts and parameter definition................................................................................................. 135
13.2PPP LCP handshake behaviour................................................................................................................136
13.3Printing IP address format +CGPIAF...................................................................................................... 137
13.4PDP context definition +CGDCONT........................................................................................................ 138
13.5Packet switched data configuration +UPSD.........................................................................................142
13.6GPRS attach or detach +CGATT............................................................................................................. 144
13.7PDP context activate or deactivate +CGACT........................................................................................144
13.8Enter PPP state/GPRS dial-up D*............................................................................................................ 147
13.9Show PDP address +CGPADDR............................................................................................................... 148
13.10Packet switched event reporting +CGEREP........................................................................................148
13.11GPRS network registration status +CGREG......................................................................................... 151
13.12UE modes of operation for EPS +CEMODE......................................................................................... 153
13.13EPS network registration status +CEREG...........................................................................................154
13.14Delete non-active PDP contexts +CGDEL............................................................................................ 157
13.15Configure the authentication parameters of a PDP/EPS bearer +UAUTHREQ.............................157
13.16PDP context read dynamic parameters +CGCONTRDP.................................................................... 158
13.17Initial PDP context activation +CIPCA...................................................................................................160
13.18PDP IP configuration when roaming +UDCONF=75............................................................................161
13.19Disable data when roaming +UDCONF=76.......................................................................................... 162
14System features...........................................................................................................163
14.1Firmware installation +UFWINSTALL..................................................................................................... 163
14.2Firmware update Over AT (FOAT) +UFWUPD...................................................................................... 164
14.3Antenna detection +UANTR.....................................................................................................................164
14.4Production test +UTEST........................................................................................................................... 165
14.5Internal temperature monitor +UTEMP................................................................................................. 176
14.6Back up the file system +UBKUPDATA.................................................................................................. 177
14.7Cancel FOTA download +UFOTA............................................................................................................. 178
14.8Sets FOTA status URCs +UFOTASTAT.................................................................................................178
14.9uFOTA configuration +UFOTACONF.......................................................................................................181
14.10Last gasp configuration +ULGASP....................................................................................................... 182
14.11RING line configuration +URINGCFG......................................................................................................184
blox
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
Contents Page 9 of 425
15Power management.................................................................................................... 185
15.1Power saving control (Power SaVing) +UPSV........................................................................................185
15.2Power Saving Mode Setting +CPSMS....................................................................................................186
15.3Power Saving Mode assigned values +UCPSMS..................................................................................189
15.4Power Saving Mode indication +UPSMR............................................................................................... 190
16GPIO..................................................................................................................................192
16.1Introduction...................................................................................................................................................192
16.2GPIO select configuration command +UGPIOC.................................................................................... 197
16.3GPIO read command +UGPIOR................................................................................................................ 199
16.4GPIO set command +UGPIOW................................................................................................................ 200
17File System.................................................................................................................... 201
17.1File tags..........................................................................................................................................................201
17.2Download file +UDWNFILE....................................................................................................................... 203
17.3List files information +ULSTFILE........................................................................................................... 204
17.4Read file +URDFILE....................................................................................................................................205
17.5Partial read file +URDBLOCK...................................................................................................................206
17.6Delete file +UDELFILE............................................................................................................................... 207
17.7Partial download file +UDWNBLOCK...................................................................................................... 207
17.8File system limits....................................................................................................................................... 208
18DNS..................................................................................................................................209
18.1Resolve name / IP number through DNS +UDNSRN............................................................................209
19Internet protocol transport layer.............................................................................211
19.1Introduction....................................................................................................................................................211
19.2IPv4/IPv6 addressing...................................................................................................................................211
19.3Create Socket +USOCR............................................................................................................................. 212
19.4SSL/TLS/DTLS mode configuration on TCP/UDP socket +USOSEC............................................... 213
19.5Set socket option +USOSO.......................................................................................................................214
19.6Get Socket Option +USOGO..................................................................................................................... 216
19.7Close Socket +USOCL................................................................................................................................ 217
19.8Get Socket Error +USOER.........................................................................................................................218
19.9Connect Socket +USOCO..........................................................................................................................218
19.10Write socket data +USOWR................................................................................................................... 219
19.11SendTo command (UDP only) +USOST.................................................................................................221
19.12Read Socket Data +USORD....................................................................................................................223
19.13Receive From command (UDP only) +USORF.....................................................................................224
19.14Set Listening Socket +USOLI................................................................................................................ 226
19.15HEX mode configuration +UDCONF=1..................................................................................................227
19.16Set socket in Direct Link mode +USODL.............................................................................................227
19.17UDP Direct Link Packet Size configuration +UDCONF=2.................................................................230
19.18UDP Direct Link Sending timer configuration +UDCONF=3............................................................230
19.19Timer Trigger configuration for Direct Link +UDCONF=5................................................................ 231
19.20Data Length Trigger configuration for Direct Link +UDCONF=6....................................................231
19.21Character trigger configuration for Direct Link +UDCONF=7..........................................................232
19.22Congestion timer configuration for Direct Link +UDCONF=8........................................................ 232
19.23Direct Link disconnect DSR line handling +UDCONF=10.................................................................233
19.24Socket control +USOCTL....................................................................................................................... 234
19.25Configure Dormant Close Socket Behavior +USOCLCFG................................................................235
20Device and data security..........................................................................................236
20.1Introduction................................................................................................................................................. 236
20.2Device security........................................................................................................................................... 236
20.3Data security.............................................................................................................................................. 239
21FTP................................................................................................................................... 265
21.1FTP service configuration +UFTP............................................................................................................265
21.2FTP command +UFTPC............................................................................................................................ 268
21.3FTP error +UFTPER.................................................................................................................................... 271
blox
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
Contents Page 10 of 425
22HTTP............................................................................................................................... 272
22.1HTTP control +UHTTP...............................................................................................................................272
22.2HTTP advanced control+UHTTPAC....................................................................................................... 275
22.3HTTP command +UHTTPC......................................................................................................................276
22.4HTTP protocol error +UHTTPER.............................................................................................................279
23Positioning....................................................................................................................280
23.1NMEA............................................................................................................................................................280
23.2AssistNow services...................................................................................................................................280
23.3GNSS.............................................................................................................................................................281
23.4CellLocate® and hybrid positioning....................................................................................................... 295
24I2C....................................................................................................................................304
24.1Introduction................................................................................................................................................. 304
24.2I2C open logical channel +UI2CO............................................................................................................304
24.3I2C write to peripheral +UI2CW.............................................................................................................. 305
24.4I2C read from peripheral +UI2CR............................................................................................................306
24.5I2C read from peripheral register +UI2CREGR.....................................................................................306
24.6I2C close logical channel +UI2CC............................................................................................................307
25MQTT..............................................................................................................................308
25.1  Introduction................................................................................................................................................. 308
25.2MQTT profile configuration +UMQTT...................................................................................................308
25.3MQTT will topic configuration +UMQTTWTOPIC................................................................................313
25.4MQTT will message configuration +UMQTTWMSG........................................................................... 314
25.5Save/Restore MQTT profile from NVM +UMQTTNV.......................................................................... 315
25.6MQTT command +UMQTTC....................................................................................................................315
25.7MQTT error +UMQTTER........................................................................................................................... 321
26Lightweight M2M....................................................................................................... 322
26.1LwM2M Objects management................................................................................................................ 322
26.2LwM2M connectivity................................................................................................................................. 327
AAppendix: Error result codes..................................................................................... 341
A.1Mobile termination error result codes +CME ERROR........................................................................... 341
A.2Message service error result codes +CMS ERROR.............................................................................. 347
A.3Firmware install final result codes...........................................................................................................351
A.4FOAT error result codes............................................................................................................................. 351
A.5Internal TCP/UDP/IP stack class error codes.........................................................................................351
A.6Internet suite error classes.......................................................................................................................353
BAppendix: AT Commands List.................................................................................. 362
B.1Parameters stored in profiles....................................................................................................................383
B.2Parameters stored in non volatile memory............................................................................................384
B.3Saving AT commands configuration.......................................................................................................387
B.4Estimated command response time....................................................................................................... 387
B.5Multiple AT command interfaces............................................................................................................ 388
CMobile Network Operator profiles...........................................................................390
C.1SARA-R4 Introduction.................................................................................................................................390
C.2SARA-R410M-02B Americas MNO profile tables.................................................................................. 391
C.3SARA-R410M-02B APAC MNO profiles table........................................................................................ 394
C.4SARA-R410M-02B EMEA MNO profiles table....................................................................................... 396
C.5SARA-R410M-52B Americas MNO profiles table..................................................................................398
C.6SARA-R410M-63B / SARA-R410M-73B / SARA-R410M-83B Americas MNO profiles table......... 400
C.7SARA-R410M-63B / SARA-R410M-73B / SARA-R410M-83B APAC MNO profiles table................ 402
C.8SARA-R410M-83B EMEA MNO profile table......................................................................................... 404
C.9SARA-R412M Americas MNO profiles table.......................................................................................... 405
C.10SARA-R412M EMEA profiles table.........................................................................................................408
DAppendix: UDP Direct Link workflow...................................................................... 410
blox
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
Contents Page 11 of 425
D.1Data from the IP network to the external port.......................................................................................410
D.2Data from the external port to the IP network...................................................................................... 410
EAppendix: Glossary........................................................................................................412
Related documentation.......................................................................................................416
Revision history..................................................................................................................... 421
Contact.................................................................................................................................... 425
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
1AT command settings Page 12 of 425
1AT command settings
u-blox cellular modules provide at least one physical serial interface that is compliant to V.24 [188]. When the
module is powered on, it enters the command mode. For more details on command mode, see Chapter 1.1.
For module and hyper terminal connection and settings see the corresponding evaluation kit user guide.
1.1Definitions
In this document the following naming conventions are used:
MT (Mobile Terminal) or DCE (Data Communications Equipment): u-blox cellular module
TE (Terminal Equipment) or DTE (Data Terminal Equipment): terminal that issues the command to the
module
TA (Terminal Adaptor): the function, integrated in the MT, of supporting AT command interface according
to the applicable standards
ME (Mobile Equipment): equivalent to MT, it is used to refer to the device itself regardless of the inserted
SIM card
The terms DCE and DTE are used in the serial interface context.
SARA-R4 / SARA-N4
u-blox cellular modules can implement more than one interface between the DTE and the DCE, either
virtual interfaces (multiplexer channels) or physical interfaces (UART, USB, SPI, etc., when available). Each
interface works as specified by the followings definitions. If not differently stated, all the subsequent
descriptions are applicable to each interface. Appendix
B.5 describes the different behaviour among the interfaces in reference to the AT command interface.
See the corresponding module data sheet for the list of available AT command interfaces.
1.2Operational mode of the AT interface
The DCE/MT interface can operate in these modes:
Command mode: the DCE waits for AT command instructions. The DCE interprets all the characters
received as commands to execute. The DCE may send responses back to the DTE indicating the outcome
of the command or further information without having received any commands by the DTE (e.g. unsolicited
response code - URC). Any communication in the command mode (in both directions) is terminated by the
command line termination character.
Data mode: the DCE transfers data after having sent the "CONNECT" string; all the characters sent to the
DCE are intended to be transmitted to the remote party. Any further characters received over the serial link
are deemed to be from the remote party, and any characters sent are transmitted to the remote party. The
DCE enters data mode immediately after it makes a Circuit Switched Data (CSD) or Packet Switched Data
(PSD) connection (PPP or DUN connection).
Online command mode: the DCE has a data connection established with a remote party, but treats signals
from the DTE as command lines and sends back responses and unsolicited indications to the DTE.
Direct link mode: intermediate state where the DCE transfers data transparently over a connected TCP/
UDP socket (e.g. by means of +USODL), after reporting the "CONNECT" string.
SMS mode: AT commands for writing or sending SMSs lead the AT interface into an intermediate state
indicated by the ">" (greater-than sign) where SMS text/PDU can be entered (DCD signal shall be in ON
state during this operation). <Ctrl-Z> indicates that the SMS editing is completed, while <ESC> indicates
aborting of the edited SMS.
Raw mode: special AT commands lead the AT interface into intermediate state where raw data is being
exchanged (e.g. during file transfer).
AT commands over an IP connection: the DCE is accepting a TCP connection on a specific TCP port. The
DTE can connect via TCP protocol to the port and can send commands over this TCP connection. The DCE
may send responses back to the DTE via the same TCP connection. The communication over IP connection
is denoted by a set of two ports:
o AT command port;
o binary data port. The binary data port is used for the exchange of binary data between the DCE and DTE.
For more details, on the configuration of the TCP ports see +UIFCONF.
RM?
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
1AT command settings Page 13 of 425
SARA-R4 / SARA-N4
The AT commands over IP connection is not supported.
1.2.1Switch from data mode to online command mode
When a data connection is established it is possible to switch from data mode to online command mode (OLCM)
in the following ways:
with the escape sequence: for more details, see the S2 AT command description
via a DTR transition: during data mode, the current DTR state is not important, but only its transition.
Furthermore, only the DTR transition from ON to OFF is detected; it can be used to control the switch to
OLCM, or to command mode (the data connection is released). For more details, see the &D AT command
description
To switch back to data mode from OLCM the O AT command is used. For more details, see also the &D AT
command.
When using the multiplexer and PPP combined, toggling the DTR line (of the physical serial interface where the
multiplexer protocol is started) from ON to OFF state does not terminate the PPP session and return the device
to the command mode. In this configuration, it is recommended that the host terminates the PPP session,
which can be done by sending LCP_TERM REQ or deasserting the DTR virtual line (sending of specific MUX
MSC command).
SARA-R4 / SARA-N4 - For more details, see the SARA-R4 series application development guide [16]).
SARA-R4 / SARA-N4
The DTR transition is ignored if the DCE is in online command mode during a PPP call. To tear down the
PPP call, switch back to data mode by means of the O AT command and then toggle the DTR from ON
to OFF state.
1.3Command description
The AT commands configure and enable the cellular module functionalities according to 3GPP normative and
u-blox specifications. The AT commands are issued to the module via a hyper terminal through a command
line and are described in the following sections. A general description of each command is provided including
the functionalities, the correct syntax to be provided by the TE/DTE, the allowed responses and an example.
The command description defines each named parameter with its type, its range (valid / acceptable values),
the default value (when available) and the factory-programmed value (when applicable).
For default value it is intended the value automatically set if the parameter is omitted and at the module
power-on (if the command setting is not stored in NVM/profile). For factory-programmed value it is intended
the value set at the module power-on when the setting is not modified respect with the manufacturer setting;
it is valid for the commands that store the setting in NVM/profile.
The summary table on the top of each command section and the Appendix B lists all the u-blox cellular modules
that support that command.
The example provided in the command description refers only to the handling provided by the command.
It may be not valid for all the products which the document is applied to. The list of allowed values for a
specific product is provided in the corresponding "Defined values" section.
In this document <CR><LF> are intentionally omitted in the command syntax.
If a parameter is omitted, no value will be inserted between the two commas indicating the interested
parameter in the command line sent by the DTE.
1.3.1Default values
If the command parameters are optional, they can be left out in the command line. If not otherwise specified,
the default values are assumed as follows:
For parameters of type Number, the default value is 0
For parameters of type String, the default value is an empty string
1.3.2Command line
The AT commands are typically issued to the cellular modules using a command line with the following generic
syntax:
(«PEP
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
1AT command settings Page 14 of 425
"AT"<command_name><string><S3_character>
Where:
"AT": prefix to be set at the beginning of each command line
<command_name>: command name string; it can have a "+" character as prefix
<string>: string consisting of the parameters value following the syntax provided in this manual
The following rules are used when describing the command syntax:
o <...>: the name in angle brackets is a parameter. The brackets themselves do not appear in the command
line
o [...]: the square brackets represent the optional parameters of a command or an optional part of the DCE
information text response. Brackets themselves do not appear in the command line. When a parameter
is not given, the value will be set to the default value provided in the command description
Parameter types:
o Number: positive and negative counting numbers, as well as zero {..., -2, -1, 0, 1, 2,...}.
o String: sequence of characters enclosed within quotation marks (" ").
<S3_character>: command line termination character; the factory-programmed termination character is
<CR>
The maximum length of the command line is the maximum number of characters which can be accepted
on a single command line (including the command line termination character).
SARA-R4 / SARA-N4
The command line is not case sensitive unless autobauding is enabled; in this case the prefix "AT" must
be typed either as "AT" or "at"; other combinations ("aT" or "Ta") are not allowed.
When writing or sending an SMS, Ctrl-Z or ESC terminates the command; <CR> is used between the two
parts of the SMS (address and text).
The serial interface driver generally does not allow a new command until the previous one has been terminated
by "OK" final result code or by an error result code. In specific cases (see the abortability attribute), the
command execution may be aborted if a character is sent to DCE before the command has ended.
1.3.2.1Concatenation of AT commands
More than one AT command can be entered on the same command line. The "AT" prefix must be provided only
at the beginning of the command line. Each command must be separated by using a semicolon as delimiter
only if the command has a "+" character as prefix.
Example: ATI;+CGATT?;+COPS?<CR>
If a command in the command line causes an error, or is not recognized as a valid command, then the execution
is terminated, the remaining commands in the command line are ignored and an error result code is returned.
If all the commands are correctly executed, only the "OK" final result code of the last command is returned.
SARA-R4 / SARA-N4
Not all the commands can be entered with other commands on the same command line: +CMGW, +CMGS,
+USOWR, +USOST, +UDWNFILE must be used by themselves.
1.3.3Notes
SARA-R410M-02B / SARA-R410M-52B / SARA-R410M-63B / SARA-R410M-73B / SARA-R410M-83B
The maximum length of the command line is 2600 characters.
String parameter type limitations - The following characters are not allowed in the parameter string:
o 0x00 (NUL)
o 0x0D (CR)
o 0x15 (NAK)
o 0x22 (")
o 0x2C (,)
SARA-R410M-02B / SARA-R410M-52B / SARA-R412M
On SARA-R410M-02B-00, SARA-R410M-02B-01, SARA-R410M-52B-00, SARA-R410M-52B-01,
SARA-R412M-02B-00, SARA-R412M-02B-01 the maximum length of the command line is 1600
characters.
RPM
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
1AT command settings Page 15 of 425
SARA-R404M / SARA-R410M-01B / SARA-N4
The maximum length of the command line is 1600 characters.
String parameter type limitations - The following characters are not allowed in the parameter string:
o 0x00 (NUL)
o 0x0D (CR)
o 0x15 (NAK)
o 0x22 (")
o 0x2C (,)
1.3.4Information text responses and result codes
The AT command response comprises an optional information text string and a final result code that can
assume the format as follows:
Verbose format:
Information text response(s): <S3_character><S4_character><text><S3_character><S4_character>
Final result code: <S3_character><S4_character><verbose code><S3_character><S4_character>
Numerical format:
Information text response(s): <text><S3_character><S4_character>
Final result code: <numerical_code><S3_character>
where
<S3_character> is the command line termination character
<S4_character> is the linefeed character
SARA-R4 / SARA-N4
The V AT command configures the result code in numeric or verbose format.
The command line termination character can be set with S3 AT command.
The linefeed character can be set with S4 AT command.
Table 1 lists the allowed result codes.
Verbose Numeric Result code type Description
OK 0 Final Command line successfully processed and the command is
correctly executed
CONNECT 1 Intermediate Data connection established
RING 2 Unsolicited Incoming call signal from the network
NO CARRIER 3 Final Connection terminated from the remote part or attempt to
establish a connection failed
ERROR 4 Final General failure. The AT+CMEE command configures the error
result format
NO DIALTONE 6 Final No dialtone detected
BUSY 7 Final Engaged signal detected (the called number is busy)
NO ANSWER 8 Final No hang up detected after a fixed network timeout
CONNECT<data rate> 9 Intermediate Same as CONNECT including also the data rate (data call).
NOT SUPPORT 10 Final Operation not supported
INVALID COMMAND LINE 11 Final Invalid command line
CR 12 Final Carriage return
SIM DROP 13 Final SIM not inserted
Command aborted 3000 Final Command execution aborted issuing a character to the DCE
DISCONNECT 14 Final Data connection disconnected
ABORTED 18 Final Aborted terminal
Table 1: Allowed result codes
SARA-R4 / SARA-N4
The DISCONNECT result code is not supported.
SARA-R4 / SARA-N4
The ABORTED result code is not supported.
SARA-R4 / SARA-N4
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
1AT command settings Page 16 of 425
These result codes are not supported: NOT SUPPORT, INVALID COMMAND LINE, CR, SIM DROP.
As already stated in the Preface section (see the "Can be aborted" attribute), some AT commands can be
aborted after having issued them.
SARA-R4 / SARA-N4
The AT commands cannot be aborted, except if explicitly stated in the corresponding AT command
description.
Intermediate outputs as well as descriptive outputs of a command are formatted as information text
responses; if more than one string has to be printed out (see for example the +CGDCONT command
description), additional command line termination and linefeed characters may be inserted for sake of
readability.
If the command is not accepted by the MT an error result code will be displayed. The AT+CMEE command
configures the error result code format as follows:
"+CMS ERROR: <err>" for SMS-related AT commands
"+CME ERROR: <err>" for any other AT commands
where <err> represents the verbose or numeric error result code depending on the +CMEE AT command
setting.
The most typical error result codes are the following:
If the command is not supported or unknown, either "+CME ERROR: unknown" or "+CME ERROR: operation
not supported" is sent
If the command syntax is wrong, "+CME ERROR: operation not supported" is sent ("+CMS ERROR: operation
not supported" for SMS related commands)
The list of all the possible error result codes is available in Appendix A.1 and Appendix A.2. For some commands
only the "ERROR" final result code is displayed and is documented in the command description.
The proprietary AT commands supporting the following features implement a different error management and
provide different error result codes:
SARA-R4 / SARA-N4 - Firmware update Over The Air: see the Appendix A.3
SARA-R4 / SARA-N4 - Firmware update Over AT command: see the Appendix A.4
SARA-R4 / SARA-N4 - DNS: see the Appendix A.5
SARA-R4 / SARA-N4 - TCP and UDP connections: see the Appendix A.5, Appendix A.6
SARA-R4 / SARA-N4 - FTP: see the Appendix A.6.1
SARA-R4 / SARA-N4 - HTTP: see the Appendix A.6.2
SARA-R4 / SARA-N4 - MQTT: see the Appendix A.6.4
The corresponding sections provide more details for retrieving the error result codes for these operations.
1.4Storing of AT commands setting
Several user settings may be stored in the cellular module's memory. Some are directly stored in the non volatile
memory (NVM), while the others are organized into two personal profiles.
Appendix B.2 lists the complete settings that can be directly stored in NVM and the corresponding commands.
SARA-R4 / SARA-N4
The module does not store the AT commands setting in the personal profiles.
1.5S-parameters
The S-parameters, as specified in ITU-T recommendation V250 [184], constitute a group of commands that
begin with the string "ATS". They are generally indicated as S registers and are used to configure the way the
module operates. Their syntax is:
ATS<parameter_number>?
ATS<parameter_number>=<value>
The number following the "ATS" is the referenced S parameter.
u-blox cellular modules support the following set of S-parameters (<parameter_number>):
AT command S Number Description
S2 2 Escape character setting
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
1AT command settings Page 17 of 425
AT command S Number Description
S3 3 Command line termination character setting
S4 4 Response formatting character setting
S5 5 Command line editing character setting
S6 6 Pause before blind dialling setting
S7 7 Connection completion timeout setting
S8 8 Command dial modifier time setting
S10 10 Automatic disconnect delay setting
S12 12 Escape prompt delay setting
If a <parameter_number> other than those listed above is introduced, the S command returns an error
result code (+CME ERROR: operation not supported).
1.6+UDCONF AT command
The UDCONF AT commands constitute a group of u-blox proprietary AT commands that allow to configure
some features beloging to i.e network services, internet suite, etc. They are indicated by the "+UDCONF=" string
followed by an <op_code> (i.e. +UDCONF=20). The allowed <op_code> values depend on the module series.
The generic set command syntax is:
AT+UDCONF=<op_code>,<param1>,<param2>,....
while the generic read command syntax is
AT+UDCONF=<op_code>
The test command syntax is defined as follows:
+UDCONF: <op_code1>,(supported <op_code1_param1>),(supported <op_code1_param2>),..
+UDCONF: <op_code2>,(supported <op_code2_param1>),(supported <op_code2_param2>),..
+UDCONF: <op_code3>,(supported <op_code3_param1>),(supported <op_code3_param2>),..
OK
The test command syntax for <op_code>=110 (NVM RAM mode management) differs respect with the other
<op_code> values:
+UDCONF: 110,"audio","+CLVL,+CRSL,+UMGC,+USGC,+UMSEL,+UMAFE,+USAFE,+UI2S,+USPM"
The string after the <at_group> parameter (i.e. "audio") lists the commands that are impacted by the
corresponding "command class". The allowed values for the <at_group> parameter (i.e. AT+UDCONF=110,
"audio") are provided by means of the corresponding read command.
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
2General operation Page 18 of 425
2General operation
2.1Start up and initialization
The characteristics of the boot of the cellular device vary from module to module and are described in the
corresponding system integration manual. During the boot phase the module might not respond to the AT
interface until all necessary SW modules have been installed (e.g. USB drivers). Monitoring of the greeting text,
where supported, can help in detecting the successful end of the boot phase.
A complete start up including cellular network operation can only take place with a SIM card.
SARA-R4
If the SIM card has enabled the PIN check, some commands answer with "+CME ERROR: SIM PIN required"
and most cellular functionalities are not started. After entering the required PIN via the +CPIN command,
or if booting with a SIM with disabled PIN check, SIM initialization is carried out and a lot of SIM files are
read: it is possible that some commands (e.g. phonebook AT commands) are affected by this preliminary
phase, resulting in a temporary error response.
2.1.1Auto-registration
If the +COPS <mode> parameter in the profiles or in NVM is left to its factory-programmed value 0 or set to 1,
after SIM initialization, all u-blox modules will automatically perform PLMN selection and registration for circuit
switched/non EPS services as well as packet switched/EPS services. Auto-registration (sometimes called also
"auto-COPS", not to be confused with automatic <mode>=0) will be triggered also at SIM insertion, for modules
supporting SIM hot insertion, or at SIM driver recovery, occurring when the communication with the SIM card
is re-established by the module after an unrecoverable error, caused e.g. by mechanical vibrations or electrical
interference.
SARA-R4 / SARA-N4
If no SIM is inserted in the module, the module will not start cell selection even if it is in automatic PLMN
selection mode.
SARA-R4 / SARA-N4
During the auto-registration any further network request (by means of AT+COPS=0 or AT+COPS=1) will
be queued and processed at the end of the auto-COPS.
SARA-R4 / SARA-N4
The radio access technology selected by the module at start up is defined by the <1stAcT> parameter
of the +URAT command; afterwards the module will reselect the RAT based on the requirements of the
cellular standards it complies with and it is not possible to force it to remain in a given RAT unless it is
locked on it via +URAT.
The user can retrieve the result of the auto-registration by polling the registration status commands (e.g.
+CREG/+CGREG/+CEREG/+CIREG) or enabling their unsolicited notifications. If auto-COPS is running, at boot
time or at SIM insertion, network service commands issued by the user might have a longer response time than
expected; this is particularly visible when the module is switched on in a jammed condition, or with a roaming
SIM card that shall perform several registration attempts before gaining access to a VPLMN. In case of failures
of the automatic registration whose cause cannot be retrieved via +CEER, it is suggested to disable auto-COPS
starting the module in +COPS: 2 or in airplane mode +CFUN: 4 and trigger registration with AT commands.
2.1.2Operational restrictions
Operational restrictions may derive from several settings: PIN required, SIM lock, invalidation of the IMEI
or SIM credentials by the Mobile Network Operator (MNO) during the registration procedure, FDN enabled.
Restrictions to access the network are also applied by the module in any one of these conditions:
In eCall only state (for all modules supporting the eCall feature)
In minimum functionality power modes (+CFUN: 0, +CFUN: 4, +CFUN: 19, +CFUN: 127), and even if the
module is restarted in +CFUN: 4 or +CFUN: 19 modes, because they are persistent
In case the module is in operational restricted state, it may reject all or specific service requests (e.g. operator
selection, connection establishment).
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
2General operation Page 19 of 425
2.2AT commands types
2.2.1Action command
An action command forces the DCE to print information text or execute a specific action for the command.
A typical example of this command type is the provision of the factory-programmed settings of the DCE like
manufacturer name, firmware version, etc.
2.2.2Set command
A set command configures the preferred settings for the specified command. The set command is the only
way to set the preferred settings in the DCE. For some commands it is possible to store the current settings
in the profile or in the non volatile memory and retrieve them in another connection.
2.2.3Read command
A read command provides the current setting of the command parameters. It is used to find out the current
command configuration.
2.2.4Test command
A test command provides the list of the values allowed by each parameter of the command.
2.2.5Unsolicited Result Code (URC)
An unsolicited result code is a string message (provided by the DCE) that is not triggered as a information
text response to a previous AT command and can be output, when enabled, at any time to inform the DTE of
a specific event or status change.
The URC can have the same name of the command that enables it (e.g. +CREG) or can be enabled by another
command (e.g. the +CMTI URC must be enabled by AT+CNMI AT command).
2.2.5.1URCs presentation deferring
Since the URCs are text responses issued by the DCE without being requested by the DTE, their occurrence
is completely uncorrelated to an AT command execution. Therefore, a collision between a URC and an AT
command response might occur and it may lead the DTE to misunderstand the URC as part of the AT
command's text response or viceversa.
The module avoids this collision by delaying the URCs presentation in case the AT command interface is busy.
The AT command interface can be busy in the following cases:
During a data call (data mode)
During the execution of an AT command in command or online command mode
The command execution starts when the command line is completed by the command line termination
character and the AT interpreter in the module accepts it; the command execution ends when the final result
code for the command is sent out. Inside this period, the module is not allowed to send the not buffered URCs.
For most of the messages, the DCE needs to be configured whether or not to send a URC. After enabling, for
most of the URCs, if the AT command interface is busy, the pending URCs are buffered and their sending to
the DCE is deferred. The RING indication is always generated as an unsolicited result code. The NO CARRIER
indication is generated as an unsolicited result code when it has not to be considered the final response for
the executing command (e.g.: ATH); in case it is handled as an unsolicited result code, it follows the rule of the
other URCs.
Generally, the buffered URCs are sent to the terminal as soon as the terminal exits the data mode or the
command execution is terminated. An exception to this behavior is implemented for the following URCs
classes:
Class AT command to configure the class
Reception of a new SMS related URCs AT+CNMI AT command
+CIEV URCs AT+CMER AT command
For the above classes, it is possible to select the presentation strategy in case of AT interface busy according
the 3GPP TS 27.007 [58]; the buffering or discarding are the two possible choices (URCs are lost in the latter
case). This is done by means of the corresponding AT command (see the AT command listed in the table above).
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
2General operation Page 20 of 425
If the URCs are enabled or for the three described classes of URCs, the buffered URCs are sent out only when
the AT interface is in idle again; this occurs as soon as:
The data mode is released (the data call is disconnected)
The final result code for an AT command is issued
The DTE should wait some time (the recommended value is at least 20 ms) after the reception of an AT
command final result code or URC before issuing a new AT command to give the DCE the opportunity to
transmit the buffered URCs. Otherwise the collision of the URCs with the subsequent AT command is
still possible.
In case multiple AT interfaces are available, it should be advisable to use one of the different AT interfaces
to manage all the user enabled URCs, while use the others ones to send AT commands and receive their
responses.
Anyway URCs related to external causes (e.g. RING) are issued on all interfaces.
2.2.6Intermediate Result Code (IRC)
An intermediate result code is a string message (provided by the DCE) which provides to the DTE some
information about the processing status of the pending AT command.
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
3IPC - Inter Processor Communication Page 21 of 425
3IPC - Inter Processor Communication
3.1Multiplexing mode +CMUX
+CMUX
Modules All products
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
partial No No No - +CME Error
3.1.1Description
Enables the multiplexing protocol control channel as defined in 3GPP TS 27.010 [87]. The command sets the
parameters for the control channel. The result code is returned using the old interface speed. The parameters
become active only after sending the OK result code.
The usage of +CMUX command during the multiplexing is not allowed.
The multiplexer configuration is as follows:
Modules Control channel AT commands / data
connection
GNSS tunneling SAP (SIM Access
Profile)
SARA-R404M / SARA-R410M-01B Channel 0 Channel 1 - 3
SARA-R410M-02B /
SARA-R410M-52B /
SARA-R410M-63B /
SARA-R410M-73B /
SARA-R410M-83B / SARA-R412M
Channel 0 Channel 1 - 2 Channel 3
SARA-N4 Channel 0 Channel 1 - 2 Channel 3
Table 2: Multiplexer configuration
3.1.2Syntax
Type Syntax Response Example
Set AT+CMUX=<mode>[,<subset>[,
<port_speed>[,<N1>[,<T1>[,<N2>[,
<T2>[,<T3>[,<k>]]]]]]]
OK AT+CMUX=0,0,,1500,50,3,90
OK
Read AT+CMUX? +CMUX: <mode>,[<subset>],<port_
speed>,<N1>,<T1>,<N2>,<T2>,
<T3>[,<k>]
OK
+CMUX: 0,0,0,1500,253,3,254,0,0
OK
Test 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)
OK
+CMUX: (0),(0),,(1-1509),(1-255),(0-
5),(2-255),,
OK
3.1.3Defined values
Parameter Type Description
<mode> Number Multiplexer transparency mechanism:
0: basic option
<subset> Number The way in which the multiplexer control channel is set up:
0 (default value): UIH frames used only
1: UI frames used only
See Notes for the parameter applicability.
<port_speed> Number Transmission rate. The allowed range is 0-7.
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
3IPC - Inter Processor Communication Page 22 of 425
Parameter Type Description
This parameter is ignored and the value 0 is always displayed in case of read
command.
<N1> Number Maximum frame size:
Allowed range is 1-1509.
The default value is 31.
<T1> Number Acknowledgement timer in units of ten milliseconds. The allowed range is 1-255.
This parameter is ignored and the value 253 is always set.
<N2> Number Maximum number of re-transmissions:
Allowed range is 0-5.
The default value is 3.
<T2> Number Response timer for the multiplexer control channel in units of ten milliseconds. The
allowed range is 2-255.
This parameter is ignored and the value 254 is always set.
<T3> Number Wake up response timer. The allowed range is 0-255.
This parameter is ignored and the value 0 is always displayed in case of the read
command.
<k> Number Window size, for advanced operation with Error Recovery options. The allowed range
is 0-255.
This parameter is ignored and the value 0 is always displayed in case of the read
command.
3.1.4Notes
If the multiplexer protocol is not started (the +CMUX set command has not been issued or returned an
error result code) and AT+CMEE is set to 2, the +CMUX read command returns the following error result
code: +CME ERROR: operation not allowed.
For complete compatibility between u-blox products, leave the unsupported/unused parameters blank
(which are reported as blank by the +CMUX test command).
<T1> must be lower than or equal to <T2>.
SARA-R4 / SARA-N4
<subset> can only assume the value 0.
<T1>, <T2>, <N2> values are ignored, since the related timers are not implemented.
The command is only supported on the UART interface. It cannot be used on the USB interface.
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
4General Page 23 of 425
4General
4.1Manufacturer identification +CGMI
+CGMI
Modules All products
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full No No No - +CME Error
4.1.1Description
Text string identifying the manufacturer.
4.1.2Syntax
Type Syntax Response Example
Action AT+CGMI <manufacturer>
OK
u-blox
OK
Test AT+CGMI=? OK
4.1.3Defined values
Parameter Type Description
<manufacturer> String Manufacturer name
4.2Manufacturer identification +GMI
+GMI
Modules All products
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full No No No - +CME Error
4.2.1Description
Text string identifying the manufacturer.
4.2.2Syntax
Type Syntax Response Example
Action AT+GMI <manufacturer>
OK
u-blox
OK
4.2.3Defined values
Parameter Type Description
<manufacturer> String Manufacturer name
4.3Model identification +CGMM
+CGMM
Modules All products
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full No No No - +CME Error
4.3.1Description
Text string identifying the model identification.
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
4General Page 24 of 425
4.3.2Syntax
Type Syntax Response Example
Action AT+CGMM <model>
OK
LISA-U200
OK
Test AT+CGMM=? OK
4.3.3Defined values
Parameter Type Description
<model> String Name of model
4.3.4Notes
SARA-R4 / SARA-N4
The action command returns the product ordering code instead of the name of model.
4.4Model identification +GMM
+GMM
Modules All products
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full No No No - +CME Error
4.4.1Description
Text string identifying the model identification.
4.4.2Syntax
Type Syntax Response Example
Action AT+GMM <model>
OK
LISA-U120
OK
4.4.3Defined values
Parameter Type Description
<model> String Name of model
4.4.4Notes
SARA-R4 / SARA-N4
The action command returns the product ordering code instead of the name of model.
4.5Firmware version identification +CGMR
+CGMR
Modules All products
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full No No No - +CME Error
4.5.1Description
Returns the firmware version of the module.
4.5.2Syntax
Type Syntax Response Example
Action AT+CGMR <version>
OK
11.40
OK
Test AT+CGMR=? OK
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
4General Page 25 of 425
4.5.3Defined values
Parameter Type Description
<version> String Firmware version
SARA-R4 / SARA-N4
The firmware version is returned together with its release date reported within
square brackets.
4.6Firmware version identification +GMR
+GMR
Modules All products
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full No No No - +CME Error
4.6.1Description
Returns the firmware version of the module.
4.6.2Syntax
Type Syntax Response Example
Action AT+GMR <version>
OK
11.40
OK
4.6.3Defined values
Parameter Type Description
<version> String Firmware version
SARA-R4 / SARA-N4
The firmware version is returned together with its release date reported within
square brackets.
4.7Request product serial number identification +CGSN
+CGSN
Modules All products
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
partial No No No - +CME Error
4.7.1Description
Returns the International Mobile station Equipment Identity (IMEI) number and related information to identify
the MT that the TE is connected to.
4.7.2Syntax
Type Syntax Response Example
Generic syntax
Set AT+CGSN[=<snt>] [+CGSN: ]<param_val>
OK
AT+CGSN=0
357520070120767
OK
Serial number request
Set AT+CGSN[=0] <sn>
OK
AT+CGSN
357520070120767
OK
IMEI request
Set AT+CGSN=1 +CGSN: <imei>
OK
AT+CGSN=1
+CGSN: "357520070120767"
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
4General Page 26 of 425
Type Syntax Response Example
OK
IMEISV request
Set AT+CGSN=2 +CGSN: <imeisv>
OK
AT+CGSN=2
+CGSN: "3575200701207601"
OK
SVN request
Set AT+CGSN=3 +CGSN: <svn>
OK
AT+CGSN=3
+CGSN: "01"
OK
Full IMEI and SVN request
Set AT+CGSN=255 <imei_full>
OK
AT+CGSN=255
35752007012076701
OK
Test AT+CGSN=? +CGSN: (list of supported <snt>s)
OK
+CGSN: (0-3,255)
OK
4.7.3Defined values
Parameter Type Description
<snt> Number It indicates the requested serial number type. Depending on <snt> value, the
<param_val> parameter in the information text response provides different
information:
0 (default value): MT serial number, typically the International Mobile station
Equipment Identity (IMEI)
1: International Mobile station Equipment Identity (IMEI)
2: International Mobile station Equipment Identity and Software Version Number
(IMEISV)
3: Software Version Number (SVN)
255: IMEI (not including the spare digit), the check digit and the SVN
<sn> Number MT serial number, typically the International Mobile station Equipment Identity (IMEI)
<imei> String International Mobile station Equipment Identity (IMEI). IMEI is composed of Type
Allocation Code (TAC) (8 digits), Serial Number (SNR) (6 digits) and the Check Digit
(CD) (1 digit).
<imeisv> String International Mobile station Equipment Identity and Software Version Number
(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 Software Version Number (SVN) which is a part of IMEISV.
<imei_full Number International Mobile station Equipment Identity (IMEI), Check Digit and Software
Version Number.
<param_val> Number/
String
Type and supported content depend on related <snt> (details are given above)
4.7.4Notes
SARA-R4 / SARA-N4
The <snt> parameter is not supported.
The response to the test command does not provide the information text response.
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
4General Page 27 of 425
4.8IMEI identification +GSN
+GSN
Modules All products
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full No No No - +CME Error
4.8.1Description
The commands handling is the same of +CGSN.
4.8.2Syntax
Type Syntax Response Example
Action AT+GSN[=<snt>] <sn>
OK
004999010640000
OK
Test AT+GSN=? OK
4.8.3Defined values
See +CGSN AT command.
4.9Identification information I
I
Modules All products
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
partial No No No - +CME Error
4.9.1Description
Returns some module information as the module type number and some details about the firmware version.
The information text response of ATI9 contains the modem version and the application version of the
module where applicable; it returns "Undefined" where not applicable.
4.9.2Syntax
Type Syntax Response Example
Module information request
ATI
Manufacturer: <manufacturer>
Model: <ordering_code>
Revision: <modem_version> [<FW_
rel_date>]
SVN: <SVN>
IMEI: <IMEI>
OK
ATI
Manufacturer: u-blox
Model: SARA-R412M-02B
Revision: M0.05.00 [Jul 06 2018 10:0
1:55]
SVN: 02
IMEI: 354679090015846
OK
Type number request
ATI0
<type_number>
OK
ATI0
SARA-R410M-63B-00
OK
Action
Modem and application version
request
ATI9
<modem_version>,<applications_
version>
OK
ATI9
M0.09.00,A.02.11
OK
4.9.3Defined values
Parameter Type Description
<manufacturer> String Manufacturer name
EFL}
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
4General Page 28 of 425
Parameter Type Description
<type_number> String Product type number
<ordering_code> String Product ordering code
<modem_version> String Module modem version
<FW_rel_date> String Firmware release date and time
<applications_
version>
String Module application version. Where not applicable the module provides "Undefined"
<SVN> String Software Version Number
<IMEI> String International Mobile Equipment Identity (IMEI) of the MT
<module_boot_
sequence_version>
Number Module boot sequence version. Where not applicable the module provides
"Undefined"
4.9.4Notes
SARA-R404M / SARA-R410M-01B / SARA-R410M-02B / SARA-R410M-52B / SARA-R412M / SARA-N4
The ATI and ATI0 commands return the product ordering code instead of the product type number.
4.10TE character set configuration +CSCS
+CSCS
Modules All products
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full No Profile No - +CME Error
4.10.1Description
Selects the TE character set.
The selected character set is used for encoding/decoding of only the AT commands' string type
parameters whose description explicitly references the +CSCS setting itself.
SARA-R4 / SARA-N4
The command setting is not stored in the profile.
4.10.2Syntax
Type Syntax Response Example
Set AT+CSCS=<chset> OK AT+CSCS="IRA"
OK
Read AT+CSCS? +CSCS: <chset>
OK
+CSCS: "IRA"
OK
Test AT+CSCS=? +CSCS: (list of supported <chset>'s)
OK
+CSCS: ("IRA","GSM","PCCP437",
"8859-1","UCS2","HEX", "PCCP936")
OK
4.10.3Defined values
Parameter Type Description
<chset> String Allowed characters set:
"IRA" (factory-programmed value): International Reference Alphabet (ITU-T T.50)
"GSM": GSM default alphabet (3GPP TS 23.038)
"PCCP437": PC character set Code Page 437
"8859-1": ISO 8859 Latin 1 character set
"UCS2": 16-bit universal multiple-octet coded character set (USO/IEC10646); UCS2
character strings are converted to hexadecimal numbers from 0000 to FFFF; e.g.
"004100620063" equals three 16-bit characters with decimal values 65, 98 and 99
"HEX": character strings consist only of hexadecimal numbers from 00 to FF; e.g.
"032FE6" equals three 8-bit characters with decimal values 3, 47 and 230; no
conversions to the original MT character set shall be done
"PCCP936": Chinese character set
Allowed values:
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
4General Page 29 of 425
Parameter Type Description
SARA-R4 / SARA-N4 - "IRA" (factory-programmed value), "GSM"
4.10.4Notes
SARA-R4 / SARA-N4
The command setting is not stored in the personal profile.
4.11International mobile subscriber identification +CIMI
+CIMI
Modules All products
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full Yes No No - +CME Error
4.11.1Description
Request the IMSI (International Mobile Subscriber Identity).
4.11.2Syntax
Type Syntax Response Example
Action AT+CIMI <IMSI>
OK
222107701772423
OK
Test AT+CIMI=? OK
4.11.3Defined values
Parameter Type Description
<IMSI> Number International Mobile Subscriber Identity
4.12Card identification +CCID
+CCID
Modules All products
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full No No No - +CME Error
4.12.1Description
Returns the ICCID (Integrated Circuit Card ID) of the SIM-card. ICCID is a serial number identifying the SIM.
4.12.2Syntax
Type Syntax Response Example
Action AT+CCID +CCID: <ICCID>
OK
+CCID: 8939107800023416395
OK
Read AT+CCID? +CCID: <ICCID>
OK
+CCID: 8939107900010087330
OK
Test AT+CCID=? OK
4.12.3Defined values
Parameter Type Description
<ICCID> String ICCID of the SIM card
4.12.4Notes
The command needs of the SIM to correctly work.
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
4General Page 30 of 425
4.13Repeat last command A/
A/
Modules All products
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full No No No - +CME Error
4.13.1Description
Repeats the previously executed command again. Only the A/ command cannot be repeated.
If autobauding is active, the MT is not able to recognize the command and the command A/ cannot be
used.
4.13.2Syntax
Type Syntax Response Example
Action A/
LMJ
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
5Mobile equipment control and status Page 31 of 425
5Mobile equipment control and status
5.1Phone activity status +CPAS
+CPAS
Modules All products
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full No No No - +CME Error
5.1.1Description
Returns the activity status <pas> of the MT.
5.1.2Syntax
Type Syntax Response Example
Action AT+CPAS +CPAS: <pas>
OK
+CPAS: 0
OK
Test AT+CPAS=? +CPAS: (list of supported <pas>s)
OK
+CPAS: (0-5)
OK
5.1.3Defined values
Parameter Type Description
<pas> Number MT activity status:
0: ready (MT allows commands from DTE)
1: unavailable (MT does not allow commands from DTE)
2: unknown (MT is not guaranteed to respond to instructions)
3: ringing (MT is ready for commands from DTE, but the ringer is active)
4: call in progress (MT is ready for commands from DTE, but a call is in progress,
e.g. call active, hold, disconnecting)
5: asleep (ME is unable to process commands from DTE because it is in a low
functionality state)
Allowed values:
SARA-R4 / SARA-N4 - 0, 3, 4
5.2Module switch off +CPWROFF
+CPWROFF
Modules All products
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full No No No < 40 s +CME Error
5.2.1Description
Switches off the MT. During shutdown current settings are saved in module's non-volatile memory.
Using this command can result in the following command line being ignored.
See the corresponding System Integration Manual for the timing and the electrical details of the module
power-off sequence via the +CPWROFF command.
SARA-R4
The +UCPWROFF URC notifies that the module power-off is in progress. For more details on the module
power-off procedure, see the SARA-R4 series system integration manual [14].
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
5Mobile equipment control and status Page 32 of 425
5.2.2Syntax
Type Syntax Response Example
Action AT+CPWROFF OK
Test AT+CPWROFF=? OK
URC +UCPWROFF +UCPWROFF
5.2.3Notes
SARA-R404M / SARA-R410M-01B / SARA-R410M-02B / SARA-R410M-52B / SARA-R412M / SARA-N4
The +UCPWROFF URC is not supported.
5.3Set module functionality +CFUN
+CFUN
Modules All products
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
partial No No No Up to 3 min +CME Error
5.3.1Description
Selects the level of functionality <fun> in the MT.
SARA-R4 / SARA-N4
If the syntax AT+CFUN=15 or AT+CFUN=16 (resets) or AT+CFUN=127 is used (where supported), the rest
of the command line, placed after that will be ignored.
SARA-R4 / SARA-N4
A SW reset started via AT+CFUN=x,1 or AT+CFUN=16 triggers signalling attempts whose number is
internally counted by the FW and limited based on mobile network operators' thresholds. The AT&T RPM
feature limits the number of SW resets per hour, and might cause the AT command to return an error
result code.
5.3.2Syntax
Type Syntax Response Example
Set AT+CFUN=<fun>[,<rst>] OK AT+CFUN=1
OK
Read AT+CFUN? +CFUN: <power_mode>
OK
+CFUN: 1
OK
Test AT+CFUN=? +CFUN: (list of supported <fun>'s),
(list of supported <rst>'s)
OK
+CFUN: (0,1,4,15,16,19),(0-1)
OK
URC +UUFASTSHUTDOWN: <value> +UUFASTSHUTDOWN: 0
5.3.3Defined values
Parameter Type Description
<fun> Number Selected functionality:
0: sets the MT to minimum functionality (disable both transmit and receive RF
circuits by deactivating both CS and PS services)
1 (factory-programmed value): sets the MT to full functionality, e.g. from airplane
mode or minimum functionality
4: disables both transmit and receive RF circuits by deactivating both CS and PS
services and sets the MT into airplane mode. Airplane mode is persistent between
power cycles triggered by AT+CFUN=15, AT+CFUN=16 or AT+CPWROFF (where
supported).
10: fast and safe power-off, the command triggers a fast shutdown where the flash
memory is closed right away and no further files are saved to the memory, cached
settings are discarded and not saved. The "OK" final result code indicates the
command request was successful, while the +UUFASTSHUTDOWN URC provides
the status of the power-off process.
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
5Mobile equipment control and status Page 33 of 425
Parameter Type Description
15: MT silent reset (with detach from network and saving of NVM parameters),
without reset of the SIM card
16: MT silent reset (with detach from network and saving of NVM parameters), with
reset of the SIM card
19: sets the MT to minimum functionality by deactivating CS and PS services and
the SIM card. Re-enable the SIM card by means of <fun>=0, 1, 4.
Allowed values:
SARA-R410M-63B / SARA-R410M-73B / SARA-R410M-83B - 0, 1, 4, 15, 19
SARA-R404M / SARA-R410M-01B / SARA-R410M-02B / SARA-R410M-52B /
SARA-R412M / SARA-N4 - 0, 1, 4, 15
SARA-R410M-63B / SARA-R410M-73B / SARA-R410M-83B
On SARA-R410M-63B-00, SARA-R410M-63B-01, SARA-R410M-73B-00, SARA-
R410M-73B-01, SARA-R410M-83B-00, SARA-R410M-83B-01 the allowed values
are: 0, 1, 4, 15.
<rst> Number Reset mode:
0 (default value): do not reset the MT before setting it to the selected <fun>
1: performs a MT silent reset (with detach from network and saving of NVM
parameters) with reset of the SIM card before setting it to the selected <fun>
<power_mode> Number Power mode:
0: MT is switched on with minimum functionality
1: MT is switched on
4: MT is in "airplane mode"
5: MT is in "test mode"
19: MT is in minimum functionality with SIM deactivated
Allowed values:
SARA-R410M-63B / SARA-R410M-73B / SARA-R410M-83B - 0, 1, 4, 5, 19
SARA-R404M / SARA-R410M-01B / SARA-R410M-02B / SARA-R410M-52B /
SARA-R412M / SARA-N4 - 0, 1, 4, 5
SARA-R410M-63B / SARA-R410M-73B / SARA-R410M-83B
On SARA-R410M-63B-00, SARA-R410M-63B-01, SARA-R410M-73B-00, SARA-
R410M-73B-01, SARA-R410M-83B-00, SARA-R410M-83B-01 the allowed values
are: 0, 1, 4, 5.
<value> Number Allowed values:
0: fast power-off ongoing
1: fast power-off completed
5.3.4Notes
SARA-R4 / SARA-N4
The <power_mode> parameter is set to 5 (test mode) after the module enters the non-signalling mode
(AT+UTEST=1).
<fun>=15 resets the SIM card.
The command will provide an error result code while in Online Command Mode (OLCM).
5.4Indicator control +CIND
+CIND
Modules All products
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
partial No No No - +CME Error
5.4.1Description
Provides indication states related to network status, battery information and so on.
The set command does not allow setting the values for those indications which are set according to module
state (see <descr> parameter).
The list of indications for set and read commands follows the indexes reported in the <descr> parameter, so
that the first <ind> corresponds to "battchg" and so on.
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
5Mobile equipment control and status Page 34 of 425
For more details, see the 3GPP TS 27.007 [58].
5.4.2Syntax
Type Syntax Response Example
Set AT+CIND=[<ind>[,<ind>[,...]]] OK AT+CIND=
OK
Read AT+CIND? +CIND: <ind>[,<ind>[,...]]
OK
+CIND: 5,0,0,0,0,0,0,0,0,0,0,0
OK
Test AT+CIND=? +CIND: (list of <descr>s)
OK
+CIND: ("battchg",(0-5)),("signal",
(0-5)),("service",(0,1)),("sounder",
(0,1)),("message",(0,1)),("call",(0,1)),
("roam",(0,1)),("smsfull",(0,1)),("gprs",
(0-2)),("callsetup",(0-3)),("callheld",(0
,1)),("simind",(0-2))
OK
5.4.3Defined values
Parameter Type Description
<ind> Number Range of corresponding <descr> used to identify the service when an unsolicited
indication is provided
<descr> String Reserved by the norm and their <ind> ranges; it may have the values:
"battchg": battery charge level (0-5)
"signal": signal level. See mapping in the Notes below
"service": network service availability
o 0: not registered to any network
o 1: registered to the network
o 65535: indication not available
"sounder": sounder activity, indicating when the module is generating a sound
o 0: no sound
o 1: sound is generated
"message": unread message available in <mem1> storage
o 0: no messages
o 1: unread message available
"call": call in progress
o 0: no call in progress
o 1: call in progress
"roam": registration on a roaming network
o 0: not in roaming or not registered
o 1: roaming
o 65535: indication not available
"smsfull": indication that an SMS has been rejected with the cause of SMS storage
full
o 0: SMS storage not full
o 1: SMS storage full
"gprs": PS indication status:
o 0: no PS available in the network
o 1: PS available in the network but not registered
o 2: registered to PS
o 65535: indication not available
"callsetup": call set-up:
o 0: no call set-up
o 1: incoming call not accepted or rejected
o 2: outgoing call in dialling state
o 3: outgoing call in remote party alerting state
"callheld": call on hold:
o 0: no calls on hold
o 1: at least one call on hold
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
5Mobile equipment control and status Page 35 of 425
Parameter Type Description
"simind": SIM detection
o 0: no SIM detected
o 1: SIM detected
o 2: not available
5.4.4Notes
If the battery charging is not supported, "battchg" always returns 5 (full charge).
The <descr> values cannot be changed with +CIND set.
The following mapping of "signal" value to the power level exists:
"signal" value Power level
0 (< -105 dBm or unknown)
1 (< -93 dBm)
2 (< -81 dBm)
3 (< -69 dBm)
4 (< -57 dBm)
5 (>= -57 dBm)
5.5Configuration of indicator control +UCIND
+UCIND
Modules All products
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full No No No - +CME Error
5.5.1Description
Allows the configuration of unsolicited results for indications with +CIEV.
5.5.2Syntax
Type Syntax Response Example
Set AT+UCIND=[<conf>] OK AT+UCIND=7
OK
Read AT+UCIND? +UCIND: <conf>
OK
+UCIND: 7
OK
Test AT+UCIND=? OK
5.5.3Defined values
Parameter Type Description
<conf> Number The unsigned integer (0 to 4095) is a bitmask representing the list of the indications
active for +CIEV URC reporting. The bit position corresponds to the indicator order
number (see the <descr> parameter of +CMER). The least significant bit is used for
the first indicator.
The bits corresponding to unused indicator order numbers (greater than 13) must be
set to 0 (setting a <conf> greater than 4095 causes an error). The default value is 40
95 (all the indications are enabled).
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
5Mobile equipment control and status Page 36 of 425
5.6Mobile termination event reporting +CMER
+CMER
Modules All products
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
partial No No No - +CME Error
5.6.1Description
Configures sending of URCs from MT to DTE for indications. The <mode> parameter controls the processing
of URCs specified within this command.
The URC is generated each time an indicator which is defined in +CIND command changes status. The code is
actually submitted to MT according to the +CMER settings.
SARA-R4 / SARA-N4
The command +UCIND allows enabling or disabling indicators.
5.6.2Syntax
Type Syntax Response Example
Set AT+CMER=[<mode>[,<keyp>[,
<disp>[,<ind>[,<bfr>]]]]]
OK AT+CMER=1,0,0,2,1
OK
Read AT+CMER? +CMER: <mode>,<keyp>,<disp>,
<ind>,<bfr>
OK
+CMER: 1,0,0,0,1
OK
Test AT+CMER=? +CMER: (list of supported
<mode>'s),(list of supported
<keyp>'s),(list of supported
<disp>'s),(list of supported <ind>'s),
(list of supported <bfr>'s)
OK
+CMER: (0-3),(0),(0),(0-2),(0,1)
OK
URC +CIEV: <descr>,<value>
5.6.3Defined values
Parameter Type Description
<mode> Number Allowed values:
0 (default value): buffer URCs in the MT
1: discard URCs when the V.24 interface is reserved for data; otherwise directly
display them on the DTE
2: buffer URCs in MT when the V.24 interface is reserved and flush them after
reservation; otherwise directly display them on the DTE
3: same as 1
<keyp> Number Allowed values:
0: no keypad event reporting
<disp> Number Allowed values:
0: no display event reporting
<ind> Number Allowed values:
0: no indicator event reporting
1: indicator event reporting using the +CIEV URC. Only the indicator events which
are not caused by +CIND shall be indicated by the MT to the DTE.
2: indicator event reporting using the +CIEV URC. All the indicator events shall be
directed from MT to DTE.
<bfr> Number Allowed values:
0: MT buffer of URCs defined within this command is cleared when <mode> 1...3 is
entered
1: MT buffer of URCs defined within this command is flushed to the DTE when
<mode> 1...3 is entered (the OK final result code shall be given before flushing the
codes).
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
5Mobile equipment control and status Page 37 of 425
Parameter Type Description
<descr> Number Indicates the indicator order number. The name in the brackets indicates the
corresponding <descr> parameter of +CIND; <value> is the new value of indicator:
1 ("battchg"): <value> provides the battery charge level (0-5)
2 ("signal"): <value> provides the signal level
o 0: < -105 dBm
o 1: < -93 dBm
o 2: < -81 dBm
o 3: < -69 dBm
o 4: < - 57 dBm
o 5: >= -57 dBm
3 ("service"): <value> provides the network service availability:
o 0: not registered to the network
o 1: registered to the network
4 ("sounder"): <value> provides the sounder activity:
o 0: no sound
o 1: sound is generated
5 ("message"): <value> provides the unread message available in <mem1> storage:
o 0: no messages
o 1: unread message available
6 ("call"): <value> provides the call in progress:
o 0: no call in progress
o 1: call in progress
7 ("roam"): <value> provides the registration on a roaming network:
o 0: not in roaming
o 1: roaming
8 ("smsfull"): <value> provides the SMS storage status:
o 0: SMS storage not full
o 1: SMS Storage full (an SMS has been rejected with the cause of SMS storage
full)
9 ("gprs"): <value> provides the GPRS indication status:
o 0: no GPRS available in the network
o 1: GPRS available in the network but not registered
o 2: registered to GPRS
o 65535: PS service indication is not available
10 ("callsetup"): <value> provides the call set-up:
o 0: no call set-up
o 1: incoming call not accepted or rejected
o 2: outgoing call in dialing state
o 3: outgoing call in remote party alerting state
11 ("callheld"): <value> provides the call on hold:
o 0: no calls on hold
o 1: at least one call on hold
12 ("simind"): <value> provides the SIM detection:
o 0: no SIM detected
o 1: SIM detected
o 2: not available
5.7Clock +CCLK
+CCLK
Modules All products
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
partial No NVM No - +CME Error
5.7.1Description
Sets and reads the real-time clock of the MT.
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
5Mobile equipment control and status Page 38 of 425
5.7.2Syntax
Type Syntax Response Example
Set AT+CCLK=<time> OK AT+CCLK="14/07/01,15:00:00+01"
OK
Read AT+CCLK? +CCLK: <time>
OK
+CCLK: "14/07/01,15:00:00+01"
OK
Test AT+CCLK=? OK
5.7.3Defined values
Parameter Type Description
<time> String Format is "yy/MM/dd,hh:mm:ss+TZ". Characters indicate year, month, day, hours,
minutes, seconds, time zone.
SARA-R4 / SARA-N4 - The factory-programmed value is "80/01/06,00:00:00+00"
Values prior to the factory-programmed value are not allowed.
5.7.4Notes
If the parameter value is out of range, then the "+CME ERROR: operation not supported" or "+CME ERROR:
4" will be provided (depending on the +CMEE AT command setting).
"TZ": The Time Zone information is represented by two digits. The value is updated during the registration
procedure when the automatic time zone update is enabled (using +CTZU AT command) and the network
supports the time zone information.
The Time Zone information is expressed in steps of 15 minutes and it can assume a value in the range
that goes from -96 to +96.
SARA-R4 / SARA-N4
The command always reports the UTC time regardless of the current +CTZU AT command setting.
5.8Set greeting text +CSGT
+CSGT
SARA-R410M-02B SARA-R410M-52B SARA-R410M-63B SARA-R410M-73B SARA-R410M-83B
SARA-R412M
Modules
SARA-N4
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
partial No NVM No - +CME Error
5.8.1Description
Configures and activates/deactivates the greeting text. The greeting text configuration's change will be
applied at the subsequent boot. If active, the greeting text is shown at boot once, on any AT interface, the first
time the TE sets the DTR line to ON state.
5.8.2Syntax
Type Syntax Response Example
Set AT+CSGT=<mode>[,<text>] OK AT+CSGT=1,"Hello user"
OK
Read AT+CSGT? +CSGT: <text>,<mode>
OK
+CSGT: "Hello",0
OK
Test AT+CSGT=? +CSGT: (list of supported <mode>s),
<ltext>
OK
+CSGT: (0-1),49
OK
5.8.3Defined values
Parameter Type Description
<text> String Greeting text. The factory-programmed value is the empty string.
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
5Mobile equipment control and status Page 39 of 425
Parameter Type Description
<mode> Number 0: turn off the greeting text
1: turn on the greeting text
<ltext> Number Maximum length of the <text> parameter.
5.8.4Notes
SARA-R410M-02B
The command is not supported by SARA-R410M-02B-00.
5.9Automatic time zone update +CTZU
+CTZU
Modules All products
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full Yes NVM No - +CME Error
5.9.1Description
Configures the automatic time zone update via NITZ.
The Time Zone information is provided after the network registration (if the network supports the time
zone information).
5.9.2Syntax
Type Syntax Response Example
Set AT+CTZU=<on_off> OK AT+CTZU=1
OK
Read AT+CTZU? +CTZU: <on_off>
OK
+CTZU: 0
OK
Test AT+CTZU=? +CTZU: (list of supported <on_
off>s)
OK
+CTZU: (0-2)
OK
5.9.3Defined values
Parameter Type Description
<on_off> Number Automatic time zone update:
0: automatic time zone via NITZ disabled
1: automatic time zone update via NITZ enabled; if the network supports the service,
update the local time to the module (not only time zone)
2: automatic time zone update via NITZ enabled; if the network supports the
service, update the GMT time to the module (not only time zone)
Allowed values:
SARA-R4 / SARA-N4 - 0 (factory-programmed value), 1
5.10Time zone reporting +CTZR
+CTZR
SARA-R410M SARA-R412MModules
SARA-N4
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
partial Yes NVM No - +CME Error
5.10.1Description
Configures the time zone change event reporting. If the reporting is enabled, according with the <mode>
parameter the MT returns:
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
5Mobile equipment control and status Page 40 of 425
the +CTZV URC whenever the time zone changes and additionally the +CTZDST URC if the daylight saving
time information is available
the +CTZE URC
the +CTZEU URC whenever the universal time reporting is available
5.10.2Syntax
Type Syntax Response Example
Set AT+CTZR=<mode> OK AT+CTZR=1
OK
Read AT+CTZR? +CTZR: <mode>
OK
+CTZR: 0
OK
Test AT+CTZR=? +CTZR: (list of supported <mode>s)
OK
+CTZR: (0-1)
OK
URC +CTZV: <tz>[,<time>] +CTZV: +04,"12/12/31,23:46:33"
URC +CTZE: <tz>,<dst>[,<time>] +CTZE: +04,1,"12/12/31,23:46:33"
URC +CTZEU: <tz>,<dst>[,<utime>] +CTZEU: +04,1
URC +CTZDST: <dst> +CTZDST: 1
5.10.3Defined values
Parameter Type Description
<mode> Number Enables the time zone reporting URCs:
0: disable the time zone change event reporting
1: enable the time zone reporting by +CTZV and +CTZDST URCs
2: enable the time zone reporting by +CTZE URC
3: enable the time zone reporting and universal time reporting by +CTZEU URC
according with 3GPP TS 27.007 Release 13
Allowed values:
SARA-R4 / SARA-N4 - 0 (default value), 1. The +CTZDST URC is not supported.
<tz> Number Indicates the time zone. The range goes from -48 to +56.
<time> String Current local time in format "yy/MM/dd,hh:mm:ss". The characters indicate year,
month, day, hour, minutes, seconds.
<dst> Number Indicates the daylight saving time. The allowed values are:
0: no adjustments
1: +1 hour adjustment
2: +2 hours adjustment
<utime> String Universal time in format "yyyy/MM/dd,hh:mm:ss". The characters indicate year,
month, day, hour, minutes, seconds.
5.10.4Notes
The +CTZU AT command (automatic time zone setting) does not affect the time zone reporting.
The time zone information is expressed in steps of 15 minutes.
The reported <tz> reflects the <dst> offset: if time zone is +1 hour and the daylight saving time is +1 hour,
the reported <tz> is +08.
For the +CTZE URC, the local time <time> needs to be derived by the MT.
SARA-R4 / SARA-N4
The command setting is not stored in the NVM.
The <time> parameter is not supported.
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
5Mobile equipment control and status Page 41 of 425
5.11Report mobile termination error +CMEE
+CMEE
Modules All products
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full No No No - +CME Error
5.11.1Description
Configures the formatting of the result code +CME ERROR: <err> as an indication of an error relating to the
functionality of the MT. When enabled, MT related errors cause +CME ERROR: <err> final result code instead
of the regular ERROR final result code. The error result code is returned normally when an error is related to
syntax, invalid parameters or MT functionality.
5.11.2Syntax
Type Syntax Response Example
Set AT+CMEE=[<n>] OK AT+CMEE=2
OK
Read AT+CMEE? +CMEE: <n>
OK
+CMEE: 0
OK
Test AT+CMEE=? +CMEE: (list of supported <n>s)
OK
+CMEE: (0-2)
OK
5.11.3Defined values
Parameter Type Description
<n> Number 0: +CME ERROR: <err> result code disabled and ERROR used
1: +CME ERROR: <err> result code enabled and numeric <err> values used
2: +CME ERROR: <err> result code enabled and verbose <err> values used
5.11.4Notes
The following convention is valid:
Numeric error code Verbose error code Description
3 "operation not allowed" The MT is in a state which does not allow performing the
entered command.
4 "operation not supported" The error result code is related to a parameter not covered by
the GSM/ETSI or u-blox specification
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
6Call control Page 42 of 425
6Call control
6.1Dial command D
D
Modules SARA-R4
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full Yes No Yes Up to 3 min +CME Error
6.1.1Description
Lists characters that may be used in a dialling string for making a call (voice, data or fax call) or controlling
supplementary services in accordance with 3GPP TS 22.030 [60] and initiates the indicated kind of call. No
further commands may follow in the command line in case of data or fax calls.
SARA-R4
Voice calls are not supported.
Set the DTR line to ON state before making a data call.
6.1.2Syntax
Type Syntax Response Example
Voice call
ATD123456;
OK
Data / fax call
ATD123456
CONNECT 9600
Action ATD<number>[<I>][<G>][;] See Result codes
Supplementary services
ATD*#43#
+CCWA: 0,1
+CCWA: 0,2
OK
6.1.3Defined values
Parameter Type Description
<number> Number Dial string; the allowed characters are: 1 2 3 4 5 6 7 8 9 0 * # + A B C D , T P ! W @ (see
the 3GPP TS 27.007 [58]). The following characters are ignored: , T ! W @.
The first occurrence of P is interpreted as pause and separator between the
dialling number and the DTMF string. The following occurrences are interpreted
only as pause. The use of P as pause has been introduced for AT&T certification.
<I> String Set the CLI status; the allowed values are:
I (ASCII code 49 Hex): CLI presentation restricted
i: CLI presentation allowed
The CLIR supplementary service subscription is overridden for this call.
<G> String Configures the CUG supplementary service for the specific call:
G: CUG activated
g: CUG deactivated
6.1.4Notes
SARA-R4
This command is abortable.
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
6Call control Page 43 of 425
6.2Call answer A
A
Modules SARA-R4
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full No No No < 20 s +CME Error
6.2.1Description
Instructs the DCE to immediately connect to the line and start the answer sequence as specified for the
underlying DCE. Any additional command that appears after A on the same command line is ignored. The
command is abortable.
SARA-R4
The user is informed that an incoming call is waiting, by the RING IRC.
6.2.2Syntax
Type Syntax Response Example
Action ATA RING
OK
6.2.3Notes
SARA-R4
This command is abortable.
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
7Network service Page 44 of 425
7Network service
7.1Network parameters definition
Parameter Type Description Commands
<MCC> Number Mobile Country Code. The range is 0-999 (3 digits).
SARA-R4 - The FFF value is to be considered not
known or not detectable
+COPS, +UCGED
<MNC> Number Mobile Network Code. The range is 0-999 (1 to 3
digits).
SARA-R4 - the FFF value is to be considered not
known or not detectable
+COPS, +UCGED
<LAC> Number Location Area Code, The range is 0x0-0xFFFF (2
octets)
+COPS
<CI> Number Cell identity.
SARA-R4 - The range is:
o 2G cell: range 0x0-0xFFFF (2 octets)
o 4G cell: range 0x0-0xFFFFFFF (28 bits), 000
0000 if not known or not detectable.
+COPS
<RxLev> Number Received Signal Strength Indicator (RSSI) index as
defined in 3GPP TS 45.008 [73]:
0: less than -110 dBm
1..62: from -110 to less than -48 dBm with 1 dBm
steps
63: -48 dBm or greater
+COPS, +UCGED
<RAC> Number Routing Area Code, range 0h-FFh (1 octet); see the
3GPP TS 44.018 [144]
+COPS
<t_adv> Number Timing Advance, it is valid during a connection and
it will updated during the next connection; see the
3GPP TS 04.18 [84]. The special value -1 means not
valid.
+UCGED
<scrambling_code> Number Scrambling code. +COPS, +UCGED
<dl_frequency> Number Downlink frequency. The range is 0-16383. +COPS
<ul_frequency> Number Uplink frequency. The range is 0-16383. +COPS
<arfcn> Number Absolute Radio Frequency Channel Number
(ARFCN).
SARA-R4 - The range is 0-1023, 65535 if not
known or not detectable.
+COPS, +UCGED
<rscp_lev> Number Received Signal Code Power expressed in dBm
levels:
0: less than -115 dBm
1..90: from -115 dBm to less than -25 dBm with 1
dBm steps
91: -25 dBm
+COPS
<ecn0_lev> Number Energy per Chip/Noise ratio expressed in dB levels:
0: less than -24 dB
1..48: from -24 dB to less than 0 dB with 0.5 dB
steps
49: 0 dB
+COPS, +UCGED
<EARFCN> Number E-UTRAN Absolute radio frequency channel number
as defined in the 3GPP TS 36.101 [110]. As per 3GPP
TS 36.101 [110] the allowed values depend on the
module supported bands. See the corresponding
module data sheet for the complete list of the
bands supported by each module.
SARA-R4 / SARA-N4 - Special value 65535
means not known or not detectable
+UCGED, +VZWRSRP,
+VZWRSRQ
<PhysCellID> Number Physical cell ID. The range is 0-503. +COPS
<TAC> Number Tracking area code. +COPS, +UCGED
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
7Network service Page 45 of 425
Parameter Type Description Commands
SARA-R4 - The range is 0-0xFFFF (2 octets),
FFFF if not known or not detectable
<LcellId> Number E-UTRAN CI (cell identifier) in hexadecimal format;
the range is 0h-FFFFFFFh (28 bits), 0000000 if not
known or not detectable.
+UCGED
<dl_EARFCN> Number Downlink E-UTRAN absolute radio frequency
channel number in decimal format.
+COPS
<ul_EARFCN> Number Uplink E-UTRAN absolute radio frequency channel
number in decimal format.
+COPS
<RSRP> Number Reference Signal Received Power (RSRP) as defined
in 3GPP TS 36.133 [115]:
0: less than -140 dBm
1..96: from -140 dBm to less than -44 dBm with 1
dBm steps
97: -44 dBm or greater
SARA-R4 / SARA-N4 - The value 255 is return if
not known or not detectable
+COPS, +UCGED
<RSRQ> Number SARA-R4 / SARA-N4 - Reference Signal Received
Quality (RSRQ) as defined in 3GPP TS 36.133
[115]:
o 0: less than -19.5 dB
o 1..33: from -19.5 dB to less than -3 dB with 0
.5 dB steps
o 34: -3 dB or greater
o SARA-R4 / SARA-N4 - The value 255 is return
if not known or not detectable
+COPS, +UCGED
<BSIC> Number Base Station Identify Code (BSIC) in hexadecimal
format, the range is 0x0-0x3F (6 bits).
+COPS, +UCGED
<Lband> Number E-UTRAN band (see 3GPP TS 36.101 Table 5.5-1
[110]). Allowed values:
SARA-R4 - From 0 to 44, 255 if not known or not
detectable
+UCGED
<Requested_eDRX_cycle> String Requested eDRX cycle value to be allocated to
the UE. Half byte in a 4 bit format: the eDRX cycle
value refers to bit 4 to 1 of octet 3 of the extended
DRX parameters information element. For the
coding and the value range, see the extended DRX
parameters information element in 3GPP TS 24.008
table 10.5.5.32/3GPP TS 24.008 [67].
SARA-R410M-02B / SARA-R410M-52B /
SARA-R410M-63B / SARA-R410M-73B /
SARA-R410M-83B / SARA-R412M - For the
factory-programmed value, see Mobile Network
Operator profiles.
+CEDRXS, +CEDRXRDP
<Assigned_eDRX_cycle> String Assigned eDRX cycle value. Half byte in a 4 bit
format: the eDRX cycle value refers to bit 4 to
1 of octet 3 of the extended DRX parameters
information element. For the coding and the
value range, see the extended DRX parameters
information element in 3GPP TS 24.008 table 10
.5.5.32/3GPP TS 24.008 [67].
+CEDRXS, +CEDRXRDP
<Requested_paging_time_
window>
String Requested paging time window value to be
allocated to the UE. Half byte in a 4 bit format:
the paging time window (PTW) refers to bit 8
to 5 of octet 3 of the extended DRX parameters
information element. For the coding and the
value range, see the extended DRX parameters
information element in 3GPP TS 24.008 table 10
.5.5.32/3GPP TS 24.008 [67].
+CEDRXS
<Assigned_paging_time_
window>
String Assigned paging time window value. Half byte
in a 4 bit format: the paging time window (PTW)
refers to bit 8 to 5 of octet 3 of the extended
DRX parameters information element. For the
+CEDRXS, +CEDRXRDP
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
7Network service Page 46 of 425
Parameter Type Description Commands
coding and the value range, see the extended DRX
parameters information element in 3GPP TS 24.008
table 10.5.5.32/3GPP TS 24.008 [67].
<LTE_rrc> Number LTE radio resource control (RRC) state:
0: null
1: IDLE
2: ATTEMPT TO CONNECT
3: CONNECTED
4: LEAVING CONNECTED STATE
5: ATTEMPT LEAVING E-UTRA
6: ATTEMPT ENTERING E-UTRA
255: not known or not detectable
+UCGED
7.2Subscriber number +CNUM
+CNUM
Modules All products
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full Yes No No < 10 s +CME Error
7.2.1Description
Returns the MSISDNs related to this subscriber. If the subscriber has different MSISDN for different services,
each MSISDN is returned in a separate line.
MSISDN is read from the SIM.
7.2.2Syntax
Type Syntax Response Example
Action AT+CNUM +CNUM: [<alpha1>],<number1>,
<type1>
[+CNUM: [<alpha2>],<number2>,
<type2>
[...]]
OK
or
OK
+CNUM: "Mario Rossi","+39320
821708",145
+CNUM: "ABCD . AAA","1234567890
12",129
OK
Test AT+CNUM=? OK
7.2.3Defined values
Parameter Type Description
<alphax> String Associated with <numberx>
<numberx> String Phone number of format specified by <typex>
<typex> Number Type of address, octet in Number format (145 when <numberx> string includes '+',
otherwise 129)
7.3Signal quality +CSQ
+CSQ
Modules All products
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full No No No - +CME Error
7.3.1Description
Returns the radio signal strength <signal_power> and <qual> from the MT.
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
7Network service Page 47 of 425
SARA-R4 / SARA-N4
The radio signal strength <signal_power> will be also used to build and display the indicator "signal" i.e.
signal quality in the information text response of +CIND and in the +CIEV URC (see the +CMER command
description).
In dedicated mode, during the radio channel reconfiguration (e.g. handover), invalid measurements may be
returned for a short transitory because the MT must compute them on the newly assigned channel.
7.3.2Syntax
Type Syntax Response Example
Action AT+CSQ +CSQ: <signal_power>,<qual>
OK
+CSQ: 2,5
OK
Test AT+CSQ=? +CSQ: (list of supported <signal_
power>s),(list of supported <qual>s)
OK
+CSQ: (0-31,99),(0-7,99)
OK
7.3.3Defined values
Parameter Type Description
<signal_power> Number The allowed range is 0-31 and 99. Remapped indication of the following parameters:
the Received Signal Strength Indication (RSSI) in GSM and LTE RATs. For more
details on the RSSI values mapping in LTE RAT, see Notes.
the Received Signal Code Power (RSCP) in UMTS RAT.
When the RF power level of the received signal is the highest possible, the value 31
is reported. When it is not known, not detectable or currently not available, 99 is
returned.
<qual> Number The allowed range is 0-7 and 99. The information provided depends on the selected
RAT:
In 2G RAT CS dedicated and GPRS packet transfer mode indicates the Bit Error
Rate (BER) as specified in 3GPP TS 45.008 [138]
In 2G RAT EGPRS packet transfer mode indicates the Mean Bit Error Probability
(BEP) of a radio block. 3GPP TS 45.008 [138] specifies the range 0-31 for the Mean
BEP which is mapped to the range 0-7 of <qual>
In UMTS RAT indicates the Energy per Chip/Noise (ECN0) ratio in dB levels of the
current cell. 3GPP TS 25.133 [116] specifies the range 0-49 for EcN0 which is mapped
to the range 0-7 of <qual>
In LTE RAT indicates the Reference Signal Received Quality (RSRQ). TS 36.133 [115]
specifies the range 0-34 for RSRQ which is mapped to the range 0-7 of <qual>
See Table 3 for the complete parameter mapping.
7.3.4Notes
<qual> 2G RAT CS and GPRS 2G RAT EGPRS UMTS RAT LTE RAT
0 BER < 0.2% 28 <= MEAN_BEP <= 31 ECN0_LEV >= 44 RSRQ_LEV < 5
1 0.2% < BER < 0.4% 24 <= MEAN_BEP <= 27 38 <= ECNO_LEV < 44 5 <= RSRQ_LEV < 10
2 0.4% < BER < 0.8% 20 <= MEAN_BEP <= 23 32 <= ECNO_LEV < 38 10 <= RSRQ_LEV < 14
3 0.8% < BER < 1.6% 16 <= MEAN_BEP <= 19 26 <= ECNO_LEV < 32 14 <= RSRQ_LEV < 18
4 1.6% < BER < 3.2% 12 <= MEAN_BEP <= 15 20 <= ECNO_LEV < 26 18 <= RSRQ_LEV < 22
5 3.2% < BER < 6.4% 8 <= MEAN_BEP <= 11 14 <= ECNO_LEV < 20 22 <= RSRQ_LEV < 26
6 6.4% < BER < 12.8% 4 <= MEAN_BEP <= 7 8 <= ECNO_LEV < 14 26 <= RSRQ_LEV < 30
7 BER > 12.8% 0 <= MEAN_BEP <= 3 ECNO_LEV < 8 RSRQ _LEV >= 30
99 Not known or not detectable
Table 3: <qual> parameter mapping for each supported RAT
SARA-R4 / SARA-N4
Table 4 maps <signal_power> values reported from UE and the RSSI. RSSI includes the signal transmitted
by the network plus noise.
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
7Network service Page 48 of 425
<signal_power> RSSI
0 RSSI of the network <= -113 dBm
1 -111 dBm
2...30 -109 dBm <= RSSI of the network <= -53 dBm
31 -51 dBm <= RSSI of the network
99 Not known or not detectable
Table 4: Mapping between <signal_power> reported from UE and the RSSI
SARA-R4 / SARA-N4
The <qual> parameter is not supported, and will be always set to 99.
SARA-R404M / SARA-R410M / SARA-N4
Only LTE RAT is supported.
7.4Extended signal quality +CESQ
+CESQ
Modules All products
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full No No No - +CME Error
7.4.1Description
Returns the received signal quality and level:
If the current serving cell is not a GERAN cell, the <rxlev> and <ber> parameters are set to value 99
If the current serving cell is not a UTRA FDD cell, the <rscp> and the <ecn0> parameters are set to 255
If the current serving cell is not an E-UTRA cell, the <rsrq> and <rsrp> parameters are set to 255.
The Reference Signal Received Power (RSRP) is a LTE specific measure that averages the power received
on the subcarriers carrying the reference signal. The RSRP measurement bandwidth is equivalent to a
single LTE subcarrier: its value is therefore much lower than the total received power usually referred
to as RSSI. In LTE the RSSI depends on the currently allocated bandwidth, which is not pre-determined.
Therefore the RSSI is not useful to describe the signal level in the cell.
7.4.2Syntax
Type Syntax Response Example
Action AT+CESQ +CESQ: <rxlev>,<ber>,<rscp>,<ecn0
>,<rsrq>,<rsrp>
OK
+CESQ: 99,99,255,255,20,80
OK
Test AT+CESQ=? +CESQ: (list of supported <rxlev>s),
(list of supported <ber>s),(list
of supported <rscp>s),(list
of supported <ecn0>s),(list
of supported <rsrq>s),(list of
supported <rsrp>s)
OK
+CESQ: (0-63,99),(0-7,99),(0-96,
255),(0-49,255),(0-34,255),(0-97,
255)
OK
7.4.3Defined values
Parameter Type Description
<rxlev> Number Received Signal Strength Indication (RSSI).
SARA-R4 / SARA-N4 - The allowed values are:
o 0: less than -110 dBm
o 1..62: from -110 to -49 dBm with 1 dBm steps
o 63: -48 dBm or greater
o 99: not known or not detectable
<ber> Number Bit Error Rate (BER):
0..7: as RXQUAL values in the table in 3GPP TS 45.008 [138], subclause 8.2.4
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
7Network service Page 49 of 425
Parameter Type Description
99: not known or not detectable
<rscp> Number Received Signal Code Power (RSCP):
0: less than -120 dBm
1..95: from -120 dBm to -26 dBm with 1 dBm steps
96: -25 dBm or greater
255: not known or not detectable
<ecn0> Number Ratio of received energy per PN chip to the total received power spectral density (see
3GPP TS 25.133 [116] subclause):
0: less than -24 dB
1..48: from -24 dB to -0.5 dBm with 0.5 dB steps (i.e. 1: -24 dB <= Ec/Io < -23.5 dB)
49: 0 dB or greater
255: not known or not detectable
<rsrq> Number Reference Signal Received Quality (RSRQ):
0: less than -19.5 dB
1..33: from -19.5 dB to -3.5 dB with 0.5 dB steps
34: -3 dB or greater
255: not known or not detectable
<rsrp> Number Reference Signal Received Power (RSRP):
0: less than -140 dBm
1..96: from -140 dBm to -45 dBm with 1 dBm steps
97: -44 dBm or greater
255: not known or not detectable
7.5Operator selection +COPS
+COPS
Modules All products
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
partial No Profile Yes Up to 3 min +CME Error
7.5.1Description
Forces an attempt to select and register with the GSM/LTE network operator, that can be chosen in the list of
network operators returned by the test command, that triggers a PLMN scan on all supported bands. Through
<mode> parameter the network selection can automatically be performed or forced by this command: the
access technology is indicated in <AcT> parameter.
In manual PLMN selection mode, if the optional <AcT> parameter is not specified, the modules will select
the default access technology with the following priority order: LTE Cat M1, NB1 and GSM (not supported
technologies will be ignored).
u-blox cellular modules are certified according to all the capabilities and options stated in the Protocol
Implementation Conformance Statement document (PICS) of the module. The PICS, according to 3GPP
TS 51.010-2 [100], 3GPP TS 34.121-2 [101], 3GPP TS 36.521-2 [122] and 3GPP TS 36.523-2 [123], is a
statement of the implemented and supported capabilities and options of a device. If the user changes
the command settings during the certification process, the PICS of the application device integrating a
u-blox cellular module must be changed accordingly.
To be able to exploit all command functionalities, the SIM card verification is required. The set value can be
checked with the read command or by verifying the active profile with AT&V command if supported (parameter
<format> is then also visible).
The set command handling depends on the <mode> parameter value:
<mode>=0 and <mode>=1: the AT command setting is immediately stored in the current activated profile.
If the MT is set in automatic selection mode (<mode>= 0), only the mode will be saved. If the MT is set in
manual mode (<mode>= 1), also the format (<format>) and operator (<oper>) will be stored.
<mode>=4: the module starts a manual selection of the specified operator; if this operation is not
successful, the module will start an automatic network selection and will remain in automatic mode.
If the set command with <mode>=0 is issued, a further set command with <mode>=0 is managed as a user
reselection (see the 3GPP TS 23.122 [95]), i.e. the module triggers a search for the HPLMN or a higher order
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
7Network service Page 50 of 425
PLMN. This is useful when roaming in areas where the HPLMN or a higher order PLMN is available. If no HPLMN
or higher order PLMN is found, the module remains in the state it was in prior to the search (e.g. camped and/
or registered on the PLMN before the search).
The PLMN search cannot be performed in RRC connected state when the RAT is LTE, hence no PLMN list will
be returned at the end of the PLMN scan attempt.
SARA-R410M / SARA-R412M / SARA-N4
The manual PLMN selection can fail due to the MNO control on the network selection procedure via EFCSP
setting; for further details see +PACSP.
The user should not enter colliding requests (e.g. AT+COPS=0 and AT+COPS=2) on different
communication ports, because this might cause interoperability issues in case overlapping registration
and deregistration requests are not handled by the network, and could result in an unpredictable
registration state. Similarly, when notified of a GPRS mobile terminated detach event (e.g. via +CGEV
URC), it is recommended to wait a few seconds before entering AT+COPS=2 in order to let the pending
registration procedure (automatically triggered by the module in most cases) successfully end.
The user should not rely only on the set command "OK" final result code as a confirmation that the network
selection has been performed. To determine the current network registration status, +CEREG should be
also checked.
7.5.2Syntax
Type Syntax Response Example
Set AT+COPS=[<mode>[,
<format>[,<oper>[,
<AcT>]]]]
OK AT+COPS=0,0
OK
Read AT+COPS? +COPS: <mode>[,<format>,<oper>[,
<AcT>]]
OK
+COPS: 0,0,"vodafone IT"
OK
Test AT+COPS=? +COPS: [(<stat>, long <oper>, short
<oper>, numeric <oper>[,<AcT>])[,
(<stat>, long <oper>, short <oper>,
numeric <oper>[,<AcT>]),[...]]],(list of
supported <mode>s),(list of supported
<format>s)
OK
+COPS: (2,"vodafone IT","voda IT","22210
"),(1,"SI vodafone","vodafone SI","29340
"),(1,"I WIND","I WIND","22288"),(1,"I TIM",
"TIM","22201"),(1,"MOBITEL","MOBITEL",
"29341"),,(0-4),(0-2)
OK
7.5.3Defined values
Parameter Type Description
<mode> Number Is used to chose whether the network selection is automatically done by the MT or is
forced by this command to the operator <oper> given in the format <format>:
0 (default value and factory-programmed value): automatic (<oper> field is ignored)
1: manual
2: deregister from network
3: set only <format>
4: manual/automatic
<format> Number 0 (factory-programmed value): long alphanumeric <oper>
1: short format alphanumeric <oper>
2: numeric <oper>
<oper> String Given in format <format> this field may be up to 24 characters long for long
alphanumeric format, up to 10 characters for short alphanumeric format and 5 or
6 characters long for numeric format (MCC/MNC codes). The factory-programmed
value is FFFF (undefined).
<stat> Number 0: unknown
1: available
2: current
3: forbidden
<AcT> Number Indicates the radio access technology:
0: GSM
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
7Network service Page 51 of 425
Parameter Type Description
3: GSM/GPRS with EDGE availability
7: LTE
8: EC-GSM-IoT (A/Gb mode)
9: E-UTRAN (NB-S1 mode)
Allowed values:
SARA-R404M / SARA-R410M-63B / SARA-R410M-73B - 7
SARA-R410M-01B - 8, 9
SARA-R410M-02B / SARA-R410M-52B / SARA-R410M-83B - 7, 9
SARA-R412M - 0, 3, 7, 9
SARA-N4 - 9
SARA-R410M-02B
On SARA-R410M-02B-00 the allowed radio access technology are: 8, 9.
7.5.4Notes
SARA-R4 / SARA-N4
The command setting is not stored in the personal profile.
The set command is abortable, the test command cannot be aborted in the same line.
<format> and <oper> parameters are optional only if the <mode> parameter is set to 0, 2 or 3.
If the antenna is not connected, then the information text response to the test command is: +COPS: ,,
(0-4),(0-2)
If no network is available, the test command returns an error result code.
SARA-R410M-02B
<AcT>=8 is used for LTE Cat M1 on SARA-R410M-02B-00.
SARA-R410M-01B
<AcT>=8 is used for LTE Cat M1.
7.6Radio Access Technology (RAT) selection +URAT
+URAT
Modules All products
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
partial No NVM / OP No <10 s +CME Error
7.6.1Description
Allows to select the Radio Access Technologies (RAT) to be activated at next registration cycle and, in case of
multi-RAT configuration, defines the RAT priority order.
Depending on how many parameters are specified, it is possible to select single or multi-RAT behaviour. The
order of the RAT parameters defines the priority of the related radio access technologies selected at boot
or when entering full functionality from deregistered state. The <1stAcT> parameter identifies the RAT to
be selected firstly. If <2ndAcT> parameter is specified, it determines which RAT is selected if no cellular
service can be obtained by the module on the <1stAcT>. If <3rdAcT> parameter is specified, it determines the
remaining RAT selected when no service can be obtained in the preferred one(s).
SARA-R4 / SARA-N4
Any change in the RAT settings require the reboot of the module via AT+CFUN=15 to make the setting
effective.
u-blox cellular modules are certified according to all the capabilities and options stated in the Protocol
Implementation Conformance Statement document (PICS) of the module. The PICS, according to 3GPP
TS 51.010-2 [100], 3GPP TS 34.121-2 [101], 3GPP TS 36.521-2 [122] and 3GPP TS 36.523-2 [123], is a
statement of the implemented and supported capabilities and options of a device. If the user changes
the command settings during the certification process, the PICS of the application device integrating a
u-blox cellular module must be changed accordingly.
In dual mode and tri mode, due to lack of inter-RAT coordination, only the Access Stratum protocol of the
current selected RAT is active.
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
7Network service Page 52 of 425
SARA-R4
Every 60 minutes a periodic PLMN scan is performed whenever the module is attached to the <2ndAcT>
(or to the <3rdAcT>); if the current RPLMN is found on the <1stAcT> (or on the <2ndAcT>), the module
will select the higher priority RAT and register on it.
7.6.2Syntax
Type Syntax Response Example
Set AT+URAT=<1stAcT>[,<2ndAcT>[,
<3rdAcT>]]
OK AT+URAT=7,8
OK
Read AT+URAT? +URAT: <1stAcT>[,<2ndAcT>[,
<3rdAcT>]]
OK
+URAT: 7
OK
Test AT+URAT=? +URAT: (list of the supported
<1stAcT>s)[,(list of the supported
<2ndAcT>s)[,(list of the supported
<3rdAcT>s)]]
OK
+URAT: (7-9),(7-9),(7-9)
OK
7.6.3Defined values
Parameter Type Description
<1stAcT> Number Indicates the single or highest priority RAT enabled and may be:
3: LTE
7: LTE Cat M1
8: LTE Cat NB1
9: GPRS / eGPRS
Allowed values depend on the module series:
SARA-R410M-02B / SARA-R410M-52B / SARA-R410M-63B / SARA-R410M-73B /
SARA-R410M-83B - 7 (factory-programmed value), 8
SARA-R412M - 7 (factory-programmed value), 8, 9
SARA-R404M / SARA-R410M-01B - 3 (factory-programmed value)
SARA-N4 - 8 (factory-programmed value)
<2ndAcT> Number Indicates the second priority RAT enabled and has the same range as <1stAcT>. The
factory-programmed value is:
SARA-R410M-02B / SARA-R410M-52B / SARA-R410M-83B / SARA-R412M - 8 (LTE
Cat NB1)
SARA-R410M-63B / SARA-R410M-73B - By factory-programmed configuration the
second priority RAT is not defined.
SARA-R404M / SARA-R410M-01B / SARA-N4 - The parameter is not supported.
<3rdAct> Number Indicates the third priority RAT enabled and has the same range as <1stAcT>. The
factory-programmed value is:
SARA-R412M - 9 (GPRS / eGPRS)
SARA-R404M / SARA-R410M / SARA-N4 - The parameter is not supported.
7.6.4Notes
AT&T's EFRAT mode contains the RAT mode setting, that is the mode that the module shall be set to.
Thus this setting may override +URAT's parameters loaded at boot time.
SARA-R4
<1stAcT>, <2ndAcT>, <3rdAct>=9 does not support any of the GSM circuit switched services such as
voice, fax, CSD, etc.
SARA-R410M-63B / SARA-R410M-73B
Do not enable the LTE Cat. NB1 as highest priority RAT (<1stAcT>) or second priority RAT (<2ndAcT>) by
means of the set command.
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
7Network service Page 53 of 425
7.7CIoT Configuration - iRAT timer +URATSCAN
+URATSCAN
Modules SARA-R410M-02B SARA-R412M
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
Full No NVM No <10 s +CME Error
7.7.1Description
Configures the iRAT (timeout for better radio air technology search) in the CIoT configuration.
7.7.2Syntax
Type Syntax Response Example
Set AT+URATSCAN=<irat_timer> OK AT+URATSCAN=5
OK
Read AT+URATSCAN? +URATSCAN: <irat_timer>
OK
+URATSCAN: 5
OK
Test AT+URATSCAN=? +URATSCAN: (list of supported
<irat_timer>s)
OK
+URATSCAN: (5-120)
OK
7.7.3Defined values
Parameter Type Description
<irat_timer> Number The range goes from 5 to 120 minutes; the default and factory-programmed value is
60 minutes.
7.7.4Notes
SARA-R410M-02B / SARA-R412M
The command is not supported by SARA-R410M-02B-00, SARA-R410M-02B-01, SARA-R410M-02B-02,
SARA-R412M-02B-00, SARA-R412M-02B-01, SARA-R412M-02B-02.
7.8MAC QoS inactivity timer(s) +UMACQOSTMR
+UMACQOSTMR
Modules SARA-R410M-02B SARA-R412M
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full No NVM / OP No <10 s +CME Error
7.8.1Description
Sets MAC QoS inactivity timers for LTE Cat M1 and LTE Cat NB1.
If the corresponding parameter is omitted in the set command, the module applies the last set value.
If the NV file(s) is (are) not present for either timer, then the specific timer(s) is (are) disabled.
If the set command is issued and any of the optional parameters is omitted, the module applies the last
set values.
7.8.2Syntax
Type Syntax Response Example
Set AT+UMACQOSTMR=[<m1_tmr>],
[<nb1_tmr>]
OK AT+UMACQOSTMR=35,60
OK
Read AT+UMACQOSTMR? +UMACQOSTMR: <m1_tmr>,<nb1_
tmr>
OK
+UMACQOSTMR: 35,60
OK
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
7Network service Page 54 of 425
Type Syntax Response Example
Test AT+UMACQOSTMR=? +UMACQOSTMR: (list of supported
<m1_tmr>s),(list of supported <nb1_
tmr>s)
OK
+UMACQOSTMR: [(0,10-120)],[(0,10
-120)]
OK
7.8.3Defined values
Parameter Type Description
<m1_tmr> Number Represents the inactivity timer for LTE Cat M1. The range goes from 10 to 120 s, and
0 (zero) for deleting NV file containing value. If NV file is not present, timer will be
disabled. For the factory-programmed value, see Mobile Network Operator profiles.
<nb1_tmr> Number Represents the inactivity timer for LTE Cat NB1. The range goes from 10 to 120 s,
and 0 (zero) for deleting NV file containing value. If NV file is not present, timer will be
disabled. For the factory-programmed value, see Mobile Network Operator profiles.
7.8.4Notes
SARA-R410M-02B / SARA-R412M
The command is not supported by SARA-R410M-02B-00, SARA-R410M-02B-01, SARA-R410M-02B-02,
SARA-R412M-02B-00, SARA-R412M-02B-01, SARA-R412M-02B-02.
After having set the <m1_tmr> or <nb1_tmr> parameters to 0 (to delete the NV file containing the value)
the information text response to the read command is -1.
7.9Network registration status +CREG
+CREG
SARA-R410M-02B SARA-R410M-52B SARA-R410M-63B SARA-R410M-73B SARA-R410M-83B
SARA-R412M
Modules
SARA-N4
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
partial Yes No No - +CME Error
7.9.1Description
Configures the network registration URC related to CS domain. Depending on the <n> parameter value, a URC
can be issued:
+CREG: <stat> if <n>=1 and there is a change in the MT's circuit switched mode network registration status
in GERAN/UTRAN/E-UTRAN.
+CREG: <stat>[,<lac>,<ci>[,<AcTStatus>]] if <n>=2 and there is a change of the network cell in GERAN/
UTRAN/E-UTRAN.
+CREG: <stat>,[<lac>],[<ci>],[<AcTStatus>][,<cause_type>,<reject_cause>] if <n>=3 and the MT
registration status (<stat>) changes. The <cause_type> and the <reject_cause> parameters are returned
only if the MT is not registered, but it is currently searching a new operator to register to (<stat>=2) or if
the registration is denied (<stat>=3).
The parameters <AcTStatus>, <lac>, <ci> are provided only if available.
The read command provides the same information issued by the URC together with the current value of the
<n> parameter. The location information elements <lac>, <ci> and <AcTStatus>, if available, are returned
only when <n>=2 or <n>=3 and the MT is registered with the network. The <cause_type>, <reject_cause>
parameters are returned only if <n>=3 and the MT is not registered, but it is currently searching a new operator
to register to (<stat>=2) or if the registration is denied (<stat>=3).
When <n>=2, in UMTS RAT, unsolicited location information can be received if the network sends the
UTRAN INFORMATION MOBILITY message during dedicated connections; in the latter cases the reported
<ci> might be not correct because the UE in DCH state cannot read broadcast system information before
the change of serving cell. In contrast, in GSM RAT no unsolicited location information is received during
a CS connection.
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
7Network service Page 55 of 425
The DTE application should set a reasonable timer (10 s) when receiving the +CREG: 3 URC, since this
might be due to the fact that the LTE registration was rejected (SIM not enabled for LTE RAT, wrong APN
during the initial default bearer setup in the EPS attach procedure and other temporary reject causes).
If the MT also supports GPRS services and/or EPS services in E-UTRAN, the +CGREG / +CEREG set and
read command result codes, where supported, apply to the registration status and location information
for those services.
7.9.2Syntax
Type Syntax Response Example
Set AT+CREG=[<n>] OK AT+CREG=1
OK
Read AT+CREG? +CREG: <n>,<stat>[,<lac>,<ci>[,
<AcTStatus>]]
OK
+CREG: 0,0
OK
Test AT+CREG=? +CREG: (list of the supported <n>s)
OK
+CREG: (0-2)
OK
URC +CREG: <stat>[,[<lac>],[<ci>][,
[<AcTStatus>][,<cause_type>,
<reject_cause>]]]
+CREG: 1,"4E54","44A5"
7.9.3Defined values
Parameter Type Description
<n> Number Network registration URC configuration. Allowed values:
0 (default value and factory-programmed value): network registration URC disabled
1: network registration URC enabled
2: network registration and location information URC enabled
3: network registration and reject cause URC enabled
<stat> Number Network registration status. Allowed values:
0: not registered, the MT is not currently searching a new operator to register to
1: registered, home network
2: not registered, but the MT is currently searching a new operator to register to
3: registration denied
4: unknown (e.g. out of GERAN/UTRAN/E-UTRAN coverage)
5: registered, roaming
6: registered for "SMS only", home network (applicable only when <AcTStatus>
indicates E-UTRAN)
7: registered for "SMS only", roaming (applicable only when <AcTStatus> indicates
E-UTRAN)
8: attached for emergency bearer services only (see 3GPP TS 24.008 [67] and 3GPP
TS 24.301 [102] that specify the condition when the MS is considered as attached
for emergency bearer services)
9: registered for "CSFB not preferred", home network (applicable only when
<AcTStatus> indicates E-UTRAN)
10: registered for "CSFB not preferred", roaming (applicable only when <AcTStatus>
indicates E-UTRAN)
<lac> String Two bytes location area code or tracking area code (if <AcTStatus>=7) in
hexadecimal format (e.g. "00C3"). The value FFFF means that the current <lac> value
is invalid.
<ci> String From 2 to 4 bytes cell ID in hexadecimal format (e.g. "A13F" or "129080B"). The value
FFFFFFFF means that the current <ci> value is invalid.
<AcTStatus> Number Indicates the radio access technology:
0: GSM
1: GSM COMPACT
2: UTRAN
3: GSM/GPRS with EDGE availability
4: UTRAN with HSDPA availability
5: UTRAN with HSUPA availability
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
7Network service Page 56 of 425
Parameter Type Description
6: UTRAN with HSDPA and HSUPA availability
7: E-UTRAN
8: EC-GSM-IoT (A/Gb mode)
9: E-UTRAN (NB-S1 mode)
255: the current <AcTStatus> value is invalid
Allowed values:
SARA-R404M / SARA-R410M-63B / SARA-R410M-73B - 7
SARA-R412M - 0, 3, 7, 9
SARA-R410M-02B / SARA-R410M-52B / SARA-R410M-83B - 7, 9
SARA-R410M-01B - 8, 9
SARA-N4 - 9
<cause_type> Number <reject_cause> type. Allowed values:
0: indicates that <reject_cause> contains an EMM cause value, see 3GPP TS 24.30
1 [102] Annex A
<reject_cause> Number Cause of the failed registration. The value is of type as defined by <cause_type>
7.9.4Notes
The following is an overview of the values assumed by the <stat> parameter:
0: a technical problem could have occurred, the user is requested to intervene. It is still possible to make
emergency calls if some network is available. Possible causes:
o PIN not entered
o Invalid HPLMN found on the SIM (SIM read error)
o SIM card not present
The registration is not started
1: the MT is registered for circuit-switched services on the HPLMN (or on one of the equivalent HPLMN's,
whose list is provided by the SIM)
2: the module is searching a network to register on. Possible causes:
o No network available
o Available networks have insufficient Rx level
o HPLMN or allowed PLMN are available but the registration is rejected, e.g. roaming is not allowed
in this Location Area
It is still possible to make emergency calls if network coverage is available
3: the CS registration failed after a Location Update Reject; possible causes are:
o Illegal MS
o Illegal ME
o IMSI unknown at HLR
o PLMN not allowed
o Location area not allowed
o Roaming not allowed in this location area
o Network failure
o Network congestion
It is still possible to make emergency calls if network coverage is available.
If the registration type is manual, then no further attempt is made to search for a new PLMN or register
with it. If the registration type is automatic, the MS may look for an allowed PLMN if the rejection cause
was roaming restriction. In case of illegal MS /ME, there could be possible problems with either the SIM
card or with the ME's identity (IMEI): user intervention may be required
4: this value, usually transitory, is returned if the registration state does not belong to any of the following:
o Normal
o Limited
o No service
o Service detached
o Service disabled
It may be issued after the failure of a registration procedure, before starting a PLMN search, when
<stat>=2.
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
7Network service Page 57 of 425
5: the MT is registered for circuit-switched services on a VPLMN, in national or international roaming
6: in LTE, the MT is registered only for the SMS circuit-switched service on the HPLMN (or on one of the
equivalent HPLMN's)
7: in LTE, the MT is registered only for the SMS circuit-switched service on a VPLMN, in national or
international roaming
8: the MT is attached for emergency bearer services only.
9: in LTE, the MT is registered only for the SMS circuit-switched service on the HPLMN (or on one of the
equivalent HPLMN's). CS fallback is not supported for voice services, therefore if the device is configured
as "voice centric" (see +CEMODE) and does not support VoLTE, it will disable LTE and reselect 3G or 2G
RAT if supported.
10: in LTE, the MT is registered only for the SMS circuit-switched service on a VPLMN, in national or
international roaming. CS fallback is not supported for voice services, therefore if the device is configured
as "voice centric" (see +CEMODE) and does not support VoLTE, it will disable LTE and reselect 3G or 2G
RAT if supported.
SARA-R4 / SARA-N4
<n>=3 is not supported.
<stat>=6, 7, 8, 9, 10 are not supported.
SARA-R410M-01B
<AcTStatus>=8 is used for E-UTRAN (<AcTStatus>=7).
7.10Read operator names +COPN
+COPN
Modules SARA-R410M-02B SARA-R410M-52B SARA-R412M
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full Yes No No - +CME Error
7.10.1Description
Returns the list of operator names from the MT. Each operator code <numeric n> that has an alphanumeric
equivalent <alpha n> in the MT memory shall be returned.
7.10.2Syntax
Type Syntax Response Example
Action AT+COPN +COPN: <numeric 1>,<alpha1>
[+COPN: <numeric2>,<alpha2> [...]]
OK
+COPN: "21901","T-Mobile HR"
+COPN: "21910","HR VIP"
+COPN: "22201","I TIM"
+COPN: "22210","vodafone IT"
OK
Test AT+COPN=? OK OK
7.10.3Defined values
Parameter Type Description
<numeric n> String Operator in numeric format (see +COPS AT command)
<alpha n> String Operator in long alphanumeric format (see +COPS AT command)
7.10.4Notes
SARA-R4
The command is not supported by SARA-R410M-02B-00, SARA-R410M-02B-01, SARA-R410M-52B-00,
SARA-R410M-52B-01, SARA-R412M-02B-00, SARA-R412M-02B-01.
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
7Network service Page 58 of 425
7.11Network selection control +PACSP
+PACSP
SARA-R410M SARA-R412MModules
SARA-N4
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full Yes No No - +CME Error
7.11.1Description
If the EFCSP (Customer Service Profile) is available the +PACSP URC is provided in the following cases:
SARA-R4 / SARA-N4 - at the module registration
SARA-R4 / SARA-N4 - whenever the SIM/USIM issues the REFRESH proactive command related to the
EFCSP
For further information, see the AT&T Device Requirements [201].
The EFCSP is available on SIM/USIM cards from AT&T mobile network operator.
7.11.2Syntax
Type Syntax Response Example
Read AT+PACSP? +PACSP<bit_value>
OK
+PACSP1
OK
URC +PACSP<bit_value> +PACSP0
7.11.3Defined values
Parameter Type Description
<bit_value> Number PLMN mode bit value:
0: automatic network selection is forced (see Notes)
1: network selection mode unchanged (see Notes)
7.11.4Notes
If EFCSP is available, the PLMN mode bit forces the automatic network registration, according to the
+COPS <mode> value which is loaded at boot from the selected profile or from the non volatile memory.
The following table explains the behavior:
Autoregistration <mode> PLMN mode bit <bit_value> Autoregistration behavior
0 0 Automatic network selection
1 0 Automatic network selection
2 0 Disabled
0 1 Automatic network selection
1 1 Manual network selection (search for the PLMN
stored in the selected profile)
2 1 Disabled
SARA-R4 / SARA-N4
The read command is not supported.
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
7Network service Page 59 of 425
7.12Channel and network environment description +UCGED
+UCGED
SARA-R410M-02B SARA-R410M-52B SARA-R410M-63B SARA-R410M-73B SARA-R410M-83B
SARA-R412M
Modules
SARA-N4
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
partial No No No - +CME Error
7.12.1Description
Enables the protocol stack and network environment information collection.
The information text response of the read command reports only the current RAT (if any) parameters,
determined by the <rat> parameter value.
SARA-R4 / SARA-N4
The command provides only the information on the serving cell, unless <mode>=2 (short form reporting
enabled) and <rat>=2 (2G).
If <mode>=2 (short form reporting enabled) and <rat>=2 (2G), where supported, the module returns also
the information on the neighbor cells.
Table 5 lists the supported <mode> parameter values:
Modules <mode>=0 <mode>=2 <mode>=3 <mode>=5
SARA-R410M-63B /
SARA-R410M-73B /
SARA-R410M-83B
* * *
SARA-R410M-02B / SARA-R412M * *1*
SARA-R410M-52B / SARA-N4 * *
Table 5: <mode> parameter applicability
7.12.2Syntax
Type Syntax Response Example
Set AT+UCGED=<mode> OK AT+UCGED=5
OK
<mode>=0:
+UCGED: MODE_5_DISABLED
OK
+UCGED: MODE_5_DISABLED
OK
<mode>=2, <rat>=2:
+UCGED: 2
<rat>,<MCC>,<MNC>
<arfcn>,<band1900>,<GcellId>,
<BSIC>,<Glac>,<Grac>,<RxLev>,<t_
adv>,<C1>,<C2>,<NMO>,<channel_
type>
[N1: <MCC>,<MNC>,<arfcn>,
<GcellId>,<BSIC>,<Glac>,<RxLev>,
<C1>,<C2>
[N2: <MCC>,<MNC>,<arfcn>,
<GcellId>,<BSIC>,<Glac>,<RxLev>,
<C1>,<C2>
[...]]]
OK
+UCGED: 2
2,222,1
1009,0,5265,11,d5bd,00,36,-1,30,30
,1,1
N1: 222,1,1023,3a26,16,d5bd,29,23,
23
N2: 222,1,13,5266,17,d5bd,28,22,22
OK
Read AT+UCGED?
<mode>=2, <rat>=6 or <rat>=7: +UCGED: 2
1Not supported by SARA-R410M-02B-00, SARA-R410M-02B-01, SARA-R410M-02B-02, SARA-R412M-0
2B-00, SARA-R412M-02B-01 and SARA-R412M-02B-02
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
7Network service Page 60 of 425
Type Syntax Response Example
+UCGED: 2
<rat>,<MCC>,<MNC>
<EARFCN>,<Lband>,<ul_BW>,
<dl_BW>,<TAC>,<P-CID>,<RSRP_
value>,<RSRQ_value>,<NBMsinr>,
<esm_cause>,<emm_state>,<tx_
pwr>,<drx_cycle_len>,<tmsi>
OK
6,310,410
5110,12,10,10,830e,162,-86,-14,131,-1,
3,255,128,"FB306E02"
OK
<mode>=5:
+RSRP: <P-CID>,<EARFCN>,
<RSRP_value>,
+RSRQ: <P-CID>,<EARFCN>,
<RSRQ_value>,
OK
+RSRP: 162,5110,"-075.00",
+RSRQ: 162,5110,"-14.20",
OK
Test AT+UCGED=? +UCGED: (list of supported
<mode>s)
OK
+UCGED: (0,2,5)
OK
7.12.3Defined values
Parameter Type Description
<mode> Number Allowed values:
0: reporting disabled
2: short form reporting enabled
3: retrieve the short form text information report
5: RSRP and RSRQ reporting enabled
<rat> Number Current Radio Access Technology:
2: 2G
3: 3G
4: 4G
5: unknown. The parameter is set to a 5 until a network information update is not
successfully performed through +UCGED=2 or when the MT is set to minimum
functionality (+CFUN: 4, +CFUN: 19).
6: LTE Cat M1
7: NB1
<svc> Number Current radio service state:
0: not known or not detectable
1: radio off
2: searching
3: no service
4: registered
The radio service state is updated at each change from a valid network service state
(2G, 3G or 4G) to another valid network service state (2G, 3G or 4G). To retrieve the
network registration status information refer to +CREG, +CGREG and +CEREG AT
commands.
<MCC> Number See <MCC>.
<MNC> Number See <MNC>.
<EARFCN> Number See <EARFCN>.
<Lband> Number See <Lband>.
<ul_BW> Number Number of Uplink Resource Blocks (see 3GPP TS 36.101 table 5.6-1 [110]), 255 if not
known or not detectable.
SARA-R4
The parameter indicates the uplink bandwidth and it is expressed in MHz.
<dl_BW> Number Number of Downlink Resource Blocks (see 3GPP TS 36.101 table 5.6-1 [110]), 255 if not
known or not detectable.
SARA-R4
The parameter indicates the downlink bandwidth and it is expressed in MHz.
<TAC> Number See <TAC>.
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
7Network service Page 61 of 425
Parameter Type Description
<LcellId> Number See <LcellId>.
<mTmsi> Number 4 bytes MME Temporary Mobile Subscriber Identity in hexadecimal format; 0000000
0 if not known or not detectable.
<mmeGrId> Number 2 bytes MME Group Identifier in hexadecimal format; FFFF if not known or not
detectable.
<RSRP> Number See <RSRP>.
<RSRQ> Number See <RSRQ>.
<mmeCode> Number 1 byte MME Code in hexadecimal format; FF if not known or not detectable.
<Lsinr> Number E-UTRAN Signal to Interference and Noise ratio in dB.
<LTE_rrc> Number See <LTE_rrc>.
<RI> Number Rank Indicator value; 255 if not known or not detectable. It is updated every 480 ms
with the value which has been most often reported to the network in the previous 480
ms period. See 3GPP TS 36.213 [129] section 7.2 and 3GPP TS 36.212 [130] section
5.2.2.6 for more details.
<CQI> Number Channel Quality Indicator value; 255 if not known or not detectable. It is updated
every 480 ms with the value which has been most often reported to the network in
the previous 480 ms period. See 3GPP TS 36.213 [129] section 7.2 for more details.
<avg_rsrp> Number Average value of last 10th Reference Signal Received Power (RSRP).
<totalPuschPwr> Number Mobile output power for PUSCH transmission averaged over 480 ms in dBm.
<avgPucchPwr> Number Mobile output power for PUCCH transmission averaged over 480 ms in dBm.
<drx> Number Discontinuous Reception "drx-Inactivity-Timer" value in ms; 0 if not known or not
detectable.
<l2w> Number SIB3 LTE to WCDMA reselection criteria: (threshServingLow)x2 +(q-RxLevMin)x2;
255 if not known or not detectable.
<volte_mode> Number Reserved for future use.
<meas_gap> Number Measurement gap configuration:
0: disabled
40: 40 ms measurement gap repetition period corresponding to the measurement
gap pattern ID 0 (see table 8.1.2.1-1 of 3GPP TS 36.133 [115])
80: 80 ms measurement gap repetition period corresponding to the measurement
gap pattern ID 1 (see table 8.1.2.1-1 of 3GPP TS 36.133 [115])
<tti_bundling> Number TTi (Transmission Time interval) bundling status:
0: off
1: on
<NBMsinr> Number Logarithmic value of SINR values expressed in 1/5th of a dB. The range goes from 0 to
250 which translates to a range from -20 dB to 30 dB
<esm_cause> Number ESM cause value as defined in 3GPP TS 24.301 [102]
<emm_state> Number EMM state value as defined in 3GPP TS 24.301 [102]. Allowed values:
0: EMM-NULL
1: EMM-DEREGISTERED
2: EMM-REGISTERED-INITIATED
3: EMM-REGISTERED
4: EMM-TRACKING-AREA-UPDATING-INITIATED
5: EMM-SERVICE-REQUEST-INITIATED
6: EMM-DEREGISTERED-INITIATED
7: undefined (or invalid)
<tx_pwr> Number TX power value in 1/10 dBm if device is in traffic, 255 otherwise
<drx_cycle_len> Number Idle DRX cycle length in 10 ms radio-frame units
<tmsi> String TMSI in hexadecimal format, with most significant byte first
<P-CID> Number E-UTRAN cell Physical Cell ID; the range is 0-503, 65535 if not known or not
detectable.
<RSRP_value> String Current Reference Signal Received Power (RSRP) expressed in dBm, the range goes
from "-140.00" dBm to "-44.00" dBm.
<RSRQ_value> String Current Reference Signal Received Quality (RSRQ) expressed in dB, the range goes
from "-20.00" dB to "-3.00" dB.
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
7Network service Page 62 of 425
7.12.3.1SARA-R4 2G parameters
Parameter Type Description
<arfcn> Number See <arfcn>.
<band1900> Number Indicates whether the given <arfcn> in the range 512-810 is part of band 1900 or not,
to avoid ambiguity between bands 1800 and 1900:
0: the given <arfcn> is not part of band 1900
1: the given <arfcn> is part of band 1900
<GcellId> Number GERAN Cell Identifier (CI) in hexadecimal format; the range is 0h-FFFFh (2 octets).
<BSIC> Number See <BSIC>.
<Glac> Number Two bytes location area of the GERAN cell in hexadecimal format; FFFF if not known
or not detectable.
<Grac> Number One byte routing area of the GERAN cell in hexadecimal format; FF if not known or not
detectable.
<RxLev> Number See <RxLev>.
<t_adv> Number See <t_adv>.
<C1> Number Value of c1; see the 3GPP TS 05.08 [73]
<C2> Number Value of c2; see the 3GPP TS 05.08 [73]
<NMO> Number Network Mode of Operation (NMO); see the 3GPP TS 03.60 [154]:
0: NMO I
1: NMO II
2: NMO III
-1: invalid
<channel_type> Number Current channel type:
0: traffic channel / packet data traffic channel (TCH/PDTCH)
1: broadcast control channel (BCCH)
Table 6: 2G parameters
7.12.4Notes
SARA-R412M
Set the command to <mode>=5 only if the module is not registered on 2G RAT.
7.13Edit Verizon wireless APN table +VZWAPNE
+VZWAPNE
SARA-R404M SARA-R410M-01B SARA-R410M-02B SARA-R410M-52BModules
SARA-N4
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
partial No NVM No - +CME Error
7.13.1Description
Reads and writes the APN table stored in the NVM:
The set command causes the APN table on the DUT to be overwritten. Only Class 3, 6 and 7 APNs can be
overwritten to any customer defined string.
The read command queries the APN table that is currently on the DUT, starting from the first entry to the
last; it returns each APN entry in a new line.
7.13.2Syntax
Type Syntax Response Example
Set AT+VZWAPNE=<wapn>,<apncl>,
<apnni>,<apntype>,<apnb>,
<apned>,<apntime>
OK AT+VZWAPNE=1,1,"IMS","IPv6",
"LTE","Enabled",0
OK
Read AT+VZWAPNE? [+VZWAPNE: <apncl>,<apnni>,
<apntype>,<apnb>,<apned>,
<apntime> [..]]
OK
+VZWAPNE: 1,"IMS","IPv4v6","LTE",
"Enabled",0
+VZWAPNE: 2,"VZWADMIN",
"IPv4v6","LTE","Enabled",0
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
7Network service Page 63 of 425
Type Syntax Response Example
OK
Test AT+VZWAPNE=? +VZWAPNE: (list of supported
<wapn>s),(list of supported
<apncl>s),,(range of supported
<apntype>s),range of supported
<apnb>s),(list of supported
<apned>s),(list of supported
<apntime>s)
OK
+VZWAPNE: (0-4),(1-4),,("IPv6",
"IPv4v6"),("LTE"),("Enabled",
"Disabled"),(0-1023)
OK
7.13.3Defined values
Parameter Type Description
<wapn> Number APN list entry
<apncl> Number APN class
<apnni> String Network identifier:
"IMS" or "VZWIMS": Verizon IMS PDN, factory-programmed value for <apncl>=1
entry
"VZWADMIN": Verizon Administrative PDN, factory-programmed for <apncl>=2
entry
"VZWINTERNET": Verizon Internet PDN, factory-programmed for <apncl>=3 entry
"VZWAPP": Verizon Application PDN, factory-programmed for <apncl>=4 entry
"ENTERPRISE": Verizon Enterprise PDN, factory-programmed for <apncl>=6 entry
"THINGSPACE": Verizon Thingspace PDN, factory-programmed for <apncl>=7
entry
<apntype> String "IPv6": IPv6 type
"IPv4v6" (factory-programmed value): IPv4 and IPv6 type
<apnb> String APN bearer:
"LTE" (factory-programmed value): LTE bearer used
<apned> String Enable/disable the APN:
"Enabled" (factory-programmed value): APN enabled
"Disabled": APN disabled
<apntime> Number APN inactivity timer value in minutes.
SARA-R4 -The range goes from 0 to 122820.
The value '0' (factory-programmed value) sets the timer to infinity.
7.13.4Notes
SARA-R4 / SARA-N4
If the current MNO profile is not set to Verizon (see the +UMNOPROF AT command, <MNO>=3) and the
command is issued, the module returns an error result code.
SARA-R404M
The class 1 APN NI is "VZWIMS".
<apncl>=6 is not supported.
<apncl>=7 is not supported.
7.14Read RSRP values +VZWRSRP
+VZWRSRP
SARA-R404M SARA-R410M-01B SARA-R410M-02B SARA-R410M-52BModules
SARA-N4
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full No No No - +CME Error
7.14.1Description
Returns the RSRP (Reference Signal Received Power) values for all LTE cells which the module is measuring.
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
7Network service Page 64 of 425
7.14.2Syntax
Type Syntax Response Example
Read AT+VZWRSRP? +VZWRSRP:
[<cellID1>,<EARFCN1>,<RSRP1>[,
<cellID2>,<EARFCN2>,<RSRP2>[,
...]]]
OK
+VZWRSRP:
000,2175,"-61.00"
OK
7.14.3Defined values
Parameter Type Description
<cellIDn> Number nth cell physical cell identifier in "xxx" format. The range goes from 0 to 503.
<EARFCNn> Number nth cell EARFCN in decimal format, see <EARFCN>.
<RSRPn> String nth cell RSRP value in dBm/15 kHz where the format is "-XX.XX".
7.14.4Notes
SARA-R4 / SARA-N4
If the current MNO profile is not set to Verizon (see the +UMNOPROF AT command, <MNO>=3) and the
command is issued, the module returns an error result code.
7.15Read RSRQ values +VZWRSRQ
+VZWRSRQ
SARA-R404M SARA-R410M-01B SARA-R410M-02B SARA-R410M-52BModules
SARA-N4
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full No No No - +CME Error
7.15.1Description
Returns the RSRQ (Reference Signal Received Quality) values for all the LTE cells which the module is
measuring.
7.15.2Syntax
Type Syntax Response Example
Read AT+VZWRSRQ? +VZWRSRQ:
[<cellID1>,<EARFCN1>,<RSRQ1>[,
<cellID2>,<EARFCN2>,<RSRQ2>[,
...]]]
OK
+VZWRSRQ:
000,2175,"-11.00"
OK
7.15.3Defined values
Parameter Type Description
<cellID> Number nth cell physical cell identifier in "xxx" format. The range goes from 0 to 503.
<EARFCNn> Number nth cell EARFCN in decimal format, see <EARFCN>.
<RSRQn> String nth cell RSRQ value in dB/15 kHz where the format is "-XX.XX".
7.15.4Notes
SARA-R4 / SARA-N4
If the current MNO profile is not set to Verizon (see the +UMNOPROF AT command, <MNO>=3) and the
command is issued, the module returns an error result code.
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
7Network service Page 65 of 425
7.16Signalling connection status +CSCON
+CSCON
Modules SARA-R410M-02B SARA-R410M-63B SARA-R410M-73B SARA-R410M-83B SARA-R412M
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full No NVM No - +CME Error
7.16.1Description
Returns details of the current terminal's perceived radio connection status (i.e. to the base-station). The set
command configures the +CSCON URC. When enabled, the URC is sent from the MT at each change of the
MT connection mode.
The state is only updated when radio events, such as send and receive, take place. This means that the
current state may be out of date. The terminal may think it is "Connected" yet cannot currently use a base
station due to a change in the link quality.
SARA-R412M
The information text response of the read command returns only the URC configuration (<n>).
7.16.2Syntax
Type Syntax Response Example
Set AT+CSCON=<n> OK AT+CSCON=1
OK
Read AT+CSCON? +CSCON: <n>[,<mode>[,<state>[,
<access>]]]
OK
+CSCON: 1,1
OK
Test AT+CSCON=? +CSCON: (list of supported <n>s)
OK
+CSCON: (0,1)
OK
URC +CSCON: <mode>[,<state>[,
<access>]]
+CSCON: 0
7.16.3Defined values
Parameter Type Description
<n> Number URC configuration:
0: +CSCON URC disabled
1: URC +CSCON: <mode> enabled
2: URC +CSCON: <mode>[,<state>] enabled
3: URC +CSCON: <mode>[,<state>[,<access>]] enabled
Allowed values:
SARA-R4 - 0 (factory-programmed value), 1
<mode> Number Indicates the signaling connection status:
0: idle
1: connected
<state> Number Allowed values:
0: UTRAN URA_PCH
1: UTRAN Cell_PCH
2: UTRAN Cell_FACH
3: UTRAN Cell_DCH
4: GERAN CS connected
5: GERAN PS connected
6: GERAN CS and PS connected
7: E-UTRAN connected
<access> Number Indicates the radio access technology:
4: E-UTRAN FDD
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
7Network service Page 66 of 425
7.16.4Notes
SARA-R4
The <state> and <access> parameters are not supported.
SARA-R410M-02B
The command is not supported by SARA-R410M-02B-00, SARA-R410M-02B-01, SARA-R410M-02B-02.
7.17eDRX setting +CEDRXS
+CEDRXS
SARA-R410M-02B SARA-R410M-52B SARA-R410M-63B SARA-R410M-73B SARA-R410M-83B
SARA-R412M
Modules
SARA-N4
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full Yes NVM / OP No - +CME Error
7.17.1Description
Configures the UEs extended discontinuous reception (eDRX) parameters. The command controls whether the
UE wants to apply the eDRX or not, as well as the requested eDRX cycle and paging time window values for
each specified type of radio access technology.
The set command also enables the +CEDRXP URC, that is issued on any change in the eDRX parameters, when
enabled by the network.
The set command with <mode>=3 will disable the use of eDRX and reset all parameters to factory-programmed
values. Optional parameters are not provided in this form of command.
The read command returns the requested eDRX cycle and paging time window values. See the +CEDRXP URC
and the +CEDRXRDP AT command to see if eDRX is enabled by the network and retrieve the values assigned
by the network.
The parameters are omitted in the information text response to the read command when the eDRX is not
enabled on any RAT.
SARA-R4 / SARA-N4
Deregister the module from the network to change the command setting. Issue AT+COPS=2 or AT
+CFUN=0 to deregister from network, issue the +CEDRXS command and reboot the module (by means of
the AT+CFUN=15 command) in order to apply the +CEDRXS settings.
SARA-R4 / SARA-N4
If the set command is issued and any of the optional parameters is omitted, the module applies the last
set values.
7.17.2Syntax
Type Syntax Response Example
Set AT+CEDRXS=[<mode>[,<AcT_
type>[,<Requested_eDRX_
cycle>[,<Requested_paging_time_
window>]]]]
OK AT+CEDRXS=1,4,"0101","0101"
OK
Read AT+CEDRXS? +CEDRXS: [<AcT_type>,
<Requested_eDRX_cycle>,
<Requested_paging_time_window>
[...]
[+CEDRXS: <AcT_type>,
<Requested_eDRX_cycle>,
<Requested_paging_time_
window>]]
OK
+CEDRXS: 4,"0101","0001"
OK
Test AT+CEDRXS=? +CEDRXS: (list of supported
<mode>s),(list of supported
<AcT_type>s),(list of supported
+CEDRXS: (0-3),(3,4,5),("0000"-
"1111"),("0000"-"1111")
OK
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
7Network service Page 67 of 425
Type Syntax Response Example
<Requested_eDRX_cycle>s),(list
of supported <Requested_paging_
time_window>s)
OK
URC +CEDRXP: <AcT_type>[,
<Requested_eDRX_cycle>[,
<Assigned_eDRX_cycle>[,
<Assigned_paging_time_window>]]]
+CEDRXP: 4,"1010","1001","1101"
7.17.3Defined values
Parameter Type Description
<mode> Number Indication to disable or enable the use of eDRX in the UE. Allowed values:
0 (default and factory-programmed value): use of eDRX disabled
1: use of eDRX enabled
2: enable the use of eDRX and enable the +CEDRXP URC
3: disable the use of eDRX and reset all other parameters for eDRX to factory-
programmed values
<AcT_type> Number Indicates the type of access technology:
2: GPRS/eGPRS
4: E-UTRAN (WB-S1 mode)
5: E-UTRAN (NB-S1 mode)
Allowed values:
SARA-R410M-52B / SARA-R410M-63B / SARA-R410M-73B - 4
SARA-R410M-02B / SARA-R410M-83B - 4, 5
SARA-R412M - 2, 4, 5
SARA-N4 - 5
<Requested_eDRX_
cycle>
String See <Requested_eDRX_cycle>.
<Assigned_eDRX_
cycle>
String See <Assigned_eDRX_cycle>.
<Requested_paging_
time_window>
String See <Requested_paging_time_window>.
<Assigned_paging_
time_window>
String See <Assigned_paging_time_window>.
7.17.4Notes
SARA-R4
The <mode> and <AcT_type> parameters are mandatory in set command.
The +CEDRXP URC enablement by means of the AT+CEDRXS=2,<AcT_type> commands is not stored in
NVM. Issue AT+CEDRXS=2,<AcT_type> to enable the +CEDRXP URC after each power cycle.
The test command response is +CEDRXS: (0-3),<AcT-type(2-5)>,<Requested_eDRX_value(0-15) in bits>,
<Requested_PTW_value(0-15) in bits>.
SARA-R410M / SARA-R412M
<mode>=3 is not supported. To reset all the eDRX parameters to factory-programmed values (see
Mobile Network Operator profiles), follow the procedure described in the +UMNOPROF AT command
description.
The <Requested_paging_time_window> parameter is not supported in the read command. Use the
+CEDRXP URC or the +CEDRXRDP command to retrieve the <Requested_eDRX_cycle>, the <Assigned_
eDRX_cycle_value> and the <Assigned_paging_time_window>.
SARA-R410M-02B / SARA-R412M
On SARA-R410M-02B-00, SARA-R410M-02B-01, SARA-R410M-02B-02, SARA-R412M-02B-00,
SARA-R412M-02B-01, SARA-R412M-02B-02 the <Requested_paging_time_window> parameter
cannot be set by means of the set command.
SARA-R410M-52B
The <Requested_paging_time_window> parameter cannot be set by means of the set command.
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
7Network service Page 68 of 425
SARA-N4
The <mode> and <AcT_type> parameters are mandatory in set command.
The +CEDRXP URC enablement by means of the AT+CEDRXS=2,<AcT_type> commands is not stored in
NVM. Issue AT+CEDRXS=2,<AcT_type> to enable the +CEDRXP URC after each power cycle.
<mode>=3 is not supported. To reset all the eDRX parameters to factory-programmed values, follow the
procedure described in the +UMNOPROF AT command description.
The <Requested_paging_time_window> parameter is not supported in the read command. Use the
+CEDRXP URC or the +CEDRXRDP command to retrieve the <Requested_eDRX_cycle>, the <Assigned_
eDRX_cycle_value> and the <Assigned_paging_time_window>.
The <Requested_paging_time_window> parameter cannot be set by means of the set command.
The test command response is +CEDRXS: (0-3),<AcT-type(2-5)>,<Requested_eDRX_value(0-15) in bits>.
7.18eDRX read dynamic parameters +CEDRXRDP
+CEDRXRDP
SARA-R410M-02B SARA-R410M-52B SARA-R410M-63B SARA-R410M-73B SARA-R410M-83B
SARA-R412M
Modules
SARA-N4
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full No No No - +CME Error
7.18.1Description
Provides the information if eDRX is enabled by the network or not. If the eDRX is enabled by the network,
the command also provides the requested eDRX cycle value to be allocated to the UE (<Requested_eDRX_
cycle>), the assigned eDRX cycle value (<Assigned_eDRX_cycle>) and the assigned paging time window value
(<Assigned_paging_time_window>) for the latest valid radio access technology (<AcT_type>). If the eDRX is
disabled, the +CEDRXRDP: 0 information text response is returned.
7.18.2Syntax
Type Syntax Response Example
Action AT+CEDRXRDP +CEDRXRDP: <AcT_type>[,
<Requested_eDRX_cycle>,
<Assigned_eDRX_cycle_value>,
<Assigned_paging_time_window>]
OK
+CEDRXRDP: 5,"0010","1110","0101"
OK
Test AT+CEDRXRDP=? OK
7.18.3Defined values
Parameter Type Description
<AcT_type> Number Indicates the type of radio access technology:
0: use of eDRX disabled
2: GSM (A/Gb mode)
4: E-UTRAN (WB-S1 mode)
5: E-UTRAN (NB-S1 mode)
Allowed values:
SARA-R410M-52B / SARA-R410M-63B / SARA-R410M-73B - 0, 4
SARA-R410M-02B / SARA-R410M-83B - 0, 4, 5
SARA-R412M - 0, 2, 4, 5
SARA-N4 - 0, 5
<Requested_eDRX_
cycle>
String See <Requested_eDRX_cycle>.
<Assigned_eDRX_
cycle>
String See <Assigned_eDRX_cycle>.
<Assigned_paging_
time_window>
String See <Assigned_paging_time_window>.
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
7Network service Page 69 of 425
7.19Set MNO profile +UMNOPROF
+UMNOPROF
SARA-R410M-02B SARA-R410M-52B SARA-R410M-63B SARA-R410M-73B SARA-R410M-83B
SARA-R412M
Modules
SARA-N4
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
partial Yes NVM No - +CME Error
7.19.1Description
Automatically configures the module to be compliant to the requirements of various Mobile Network
Operators.
Follow this procedure to properly set up the configuration:
Deregister the module from the network (perform a AT+CFUN=0 or AT+CFUN=4 cycle or issue the AT
+COPS=2 command)
Issue AT+UMNOPROF=<MNO>
To apply the new configuration reboot the module
o SARA-R4 / SARA-N4 - by means of the AT+CFUN=15 AT command. If <MNO>=1 (SIM ICCID select),
reboot the module twice to apply the MNO profile configuration.
After setting a new configuration the module reconfigures the PDP context settings (e.g. APN of the initial EPS
bearer).
SARA-R410M-02B / SARA-R410M-52B / SARA-R412M
On SARA-R410M-02B-00, SARA-R410M-52B-00, SARA-R412M-02B-00 and SARA-R412M-02B-01 if
<MNO>=1 (SIM ICCID select), it is not necessary to reboot the module the second time. Immediately after
issuing the AT+CFUN=15 command the proper MNO profile configuration is applied.
SARA-R4 / SARA-N4
Changing the Mobile Network Operator (MNO) profile with the +UMNOPROF AT command overwrites
some AT command settings and applies the default MNO profile values. For the list of AT commands
affected by +UMNOPROF AT command, see Mobile Network Operator profiles.
Follow this procedure to restore the profile factory-programmed configuration:
SARA-R410M / SARA-R412M / SARA-N4 - Set a different profile than the current one and then set the the
profile back to the original. Reboot the module (AT+CFUN=15) to make the change effective.
SARA-R4 / SARA-N4
The version of the MNO profiles can be displayed by issuing the set command AT+UMNOPROF=,1 and
then the test command. The MNO profile version will be displayed after each profile in the list.
u-blox cellular modules are certified according to all the capabilities and options stated in the Protocol
Implementation Conformance Statement document (PICS) of the module. The PICS, according to 3GPP TS
51.010-2 [100], 3GPP TS 34.121-2 [101], 3GPP TS 36.521-2 [122] and 3GPP TS 36.523-2 [123], is a statement of
the implemented and supported capabilities and options of a device. If the user changes the command settings
during the certification process, the PICS of the application device integrating a u-blox cellular module must
be changed accordingly.
7.19.1.1SIM ICCID selection
If the <MNO> parameter is set to 1 (SIM ICCID select), the mobile network operator profile is selected according
to the recognized SIM Issuer Identifier Number (IIN). For more details on the recognized SIM IINs ranges, see
the SARA-R4 application development guide [16].
SARA-R410M-63B / SARA-R410M-73B
If a SoftBank or a NTT DoCoMo SIM is inserted the mobile network operator profile (<MNO>) is
automatically set according to the SIM. After that if the mobile network operator profile (<MNO>) is
modified to not match the SIM, the MT is set to minimum functionality (+CFUN: 0); it is not possible
to restore the MT to full functionality (+CFUN: 1), until the mobile network operator profile is not set
according to the SIM.
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
7Network service Page 70 of 425
7.19.2Syntax
Type Syntax Response Example
Set AT+UMNOPROF=<MNO>[,<reset>,
<urc_notification_enabled>]
OK AT+UMNOPROF=1,0,1
OK
Read AT+UMNOPROF? +UMNOPROF: <MNO>[,[<MNO_
detected>],<reset>,<urc_
notification_enabled>]
OK
+UMNOPROF: 3
OK
SARA-R4
Test AT+UMNOPROF=? +UMNOPROF:
<MNO_1>: supported MNO_1 name
<MNO_2>: supported MNO_2 name
...
<MNO_n>: supported MNO_n name
OK
+UMNOPROF:
0: SW default
1: SIM ICCID select
6: China Telecom
100: Standard Europe
4: Telstra
5: T-Mobile US
19: Vodafone
3: Verizon
31: Deutsche Telekom
OK
URC +UMNOPROF: <MNO>,<MNO_
detected>
+UMNOPROF: 1,2
7.19.3Defined values
Parameter Type Description
<MNO> Number Mobile Network Operator (MNO) profile:
0: undefined / regulatory. For more details, see Notes.
1: SIM ICCID/IMSI select
2: AT&T
3: Verizon
4: Telstra
5: T-Mobile US
6: China Telecom
8: Sprint
19: Vodafone
20: NTT DoCoMo
21: Telus
28: SoftBank
31: Deutsche Telekom
32: US Cellular
33: VIVO
39: SKT
43: Rogers
44: Claro Brasil
45: TIM Brasil
46: Orange France
90: global
100: standard Europe
101: standard Europe No-ePCO. The factory-programmed configuration of this
profile is the same of the standard Europe profile (<MNO>=100), but the ePCO is
disabled.
102: standard JP (global)
198: AT&T 2-4-12. The factory-programmed configuration of this profile is the same
of the AT&T profile (<MNO>=2), but the LTE band 5 is disabled.
RP
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
7Network service Page 71 of 425
Parameter Type Description
201: GCF-PTCRB. This profile is meant only for conformance testing.
206: FirstNet
Allowed values depend on the module series:
SARA-R410M-63B - 0, 1, 20, 28 (factory-programmed value), 102
SARA-R410M-73B - 0, 1, 39 (factory-programmed value)
SARA-R410M-83B - 0, 1, 4 (factory-programmed value), 100, 101
SARA-R412M - 0 (factory-programmed value), 1, 2, 19, 31, 33, 44, 45, 46, 100, 101, 198
SARA-R410M-52B - 0 (factory-programmed value), 1, 2, 3, 198
SARA-R410M-02B - 0 (factory-programmed value), 1, 2, 3, 4, 8, 19, 21, 31, 33, 43, 44,
45, 46, 100, 101, 198, 206
SARA-N4 - 0 (factory-programmed value), 1, 2, 3, 4, 5, 6, 21
SARA-R410M-73B
On SARA-R410M-73B-00 the allowed Mobile Network Operator (MNO) profiles
are: 0, 1, 20, 28, 39 (factory-programmed value).
SARA-R410M-63B
On SARA-R410M-63B-00 the allowed Mobile Network Operator (MNO) profiles
are: 0, 1, 20, 28 (factory-programmed value), 39.
SARA-R412M
On SARA-R412M-02B-02 the allowed Mobile Network Operator (MNO) profiles
are: 0 (factory-programmed value), 1, 19, 31, 100, 101.
On SARA-R412M-02B-01 the allowed Mobile Network Operator (MNO) profiles
are: 0 (factory-programmed value), 1, 2, 5, 19, 31, 100.
On SARA-R412M-02B-00 the allowed Mobile Network Operator (MNO) profiles
are: 0 (factory-programmed value), 1, 19, 31, 100.
SARA-R410M-52B
On SARA-R410M-52B-00, SARA-R410M-52B-01 the allowed Mobile Network
Operator (MNO) profiles are: 0 (factory-programmed value), 1, 2, 3.
SARA-R410M-02B
On SARA-R410M-02B-02 the allowed Mobile Network Operator (MNO) profiles
are: 0 (factory-programmed value), 1, 2, 3, 19, 21, 31, 100, 101, 198.
On SARA-R410M-02B-01 the allowed Mobile Network Operator (MNO) profiles
are: 0 (factory-programmed value), 1, 2, 3, 4, 5, 6, 8, 19, 21, 31, 100.
On SARA-R410M-02B-00 the allowed Mobile Network Operator (MNO) profiles
are: 0 (factory-programmed value), 1, 2, 3, 4, 5, 6.
<MNO_detected> Number If <MNO>=1 (SIM ICCID/IMSI select) and the SIM is inserted, it specifies the <MNO>
value that matches the SIM Issuer Identifier Number (IIN) or the <MNO> retrieved by
the IMSI and that is actually applied.
SARA-R4
If the SIM is not inserted or the SIM IIN does not match any <MNO>, the last valid
<MNO> remains active and is consequently shown.
<reset> Number Configure the automatic reset. Allowed values:
0: the automatic reset is disabled; the user shall reboot the module by itself
1: the automatic reset is enabled
It must be issued only if <MNO>=1.
<urc_notification_
enabled>
Number Configure the URC notification. Allowed values:
0: URC is not issued if the <MNO_detected> value changes
1: URC is issued any time the <MNO_detected> value changes
It must be issued only if <MNO>=1.
7.19.4Notes
The standard Europe profile should be used as the basis for all other MNOs in Europe outside of Vodafone
and Deutsche Telekom. However, there may be changes that need to be applied to the module for proper
operation with any given European MNO such as attach type, RAT preference, band selection, etc. Please
consult with the preferred network provider.
SARA-R410M / SARA-R412M / SARA-N4
If <MNO>=0 the profile selected is undefined.
The <reset>, <urc_notification_enabled> parameters are not supported.
(«4H4 QR?
SARA-R4 series-AT commands manual
UBX-17003787 - R20
C1-Public
7Network service Page 72 of 425
SARA-R410M-02B / SARA-R410M-52B / SARA-R412M
The <MNO_detected> parameter is not supported.
7.20Band selection bitmask +UBANDMASK
+UBANDMASK
SARA-R410M-02B SARA-R410M-52B SARA-R410M-63B SARA-R410M-73B SARA-R410M-83B
SARA-R412M
Modules
SARA-N4
Syntax PIN required Settings saved Can be aborted Response time Error referenceAttributes
full Yes NVM / OP No - +CME Error
7.20.1Description
Sets the supported LTE-M / NB-IoT / GSM bands for different Radio Access Technologies (RATs). The LTE
bands supported are set by means of bitmasks where each bit in an 64 bit integer corresponds to a LTE-M /
NB-IoT band. The GSM bands supported are set by means of a bitmask where specific bits correspond to 850 /
900 / 1800 / 1900 bands.
SARA-R4 / SARA-N4
Reboot the module (AT+CFUN=15) to make the setting effective.
u-blox cellular modules are certified according to all the capabilities and options stated in the Protocol
Implementation Conformance Statement document (PICS) of the module. The PICS, according to 3GPP
TS 51.010-2 [100], 3GPP TS 34.121-2 [101], 3GPP TS 36.521-2 [122] and 3GPP TS 36.523-2 [123], is a
statement of the implemented and supported capabilities and options of a device. If the user changes